"Do you want a hand? Are you downsized? You're in luck, we have FAQs"

Another semi Cit.

Pablock Web-app

Pablock is a web-app that allows you to use the blockchain as easily as using a regular web-app. With Pablock you can certify files and create NFTs on blockchain quickly.

Pablock’s client platform is a React web-app that resides under the bcode.cloud domain.

Pablock uses Polygon, a sidechain of Ethereum. Files are first notarized on Polygon and then anchored on Ethereum’s mainnet. This means that your files will be visible on a blockchain explorer of both Ethereum and Polygon. Etherscan is Ethereum’s main blockchain explorer.

Blockchain explorers are blockchain search engines. Just like the search engine you’re using right now, blockchain explorers allow you to search, within a given blockchain, for transactions made on that blockchain, thus including your own, by means of an identifying hash

To use Pablock, a blockchain wallet (Ethereum) is generated during account creation so that transactions can be signed and files certified. The wallet also proves that the person who signs transactions, and thus certifies files and creates NFTs, is the owner of those files and NFTs.

The creation of a Pablock account takes place as in a classic application: the classic fields for user profiling will be requested during login/authentication.
classic fields for user profiling during login / authentication. The key point of
profile creation is the wallet management. In fact, during the creation of the profile, the user will be asked whether to import an existing wallet already owned by the user, or whether to create a new one. The generation of the wallet is client-side on the user’s device through ethers.js,
ensuring the total randomness of the calculated wallet. The creation of the profile involves the insertion
in addition to the password for account protection, also a secondary password and complete management of the user. At the time of account registration the wallet will be encrypted in two versions,
one with the primary password and one with the secondary password, the encryption will always take place on the
user’s device. The encrypted wallets are then saved and restored on the client side at each login
of the application, making Pablock non custodial and ensuring the user the exclusive management of the
wallet. The primary password will be treated as a classic password, so the hash is saved on our servers, while the secondary password is held only by the user and will be required in the
moment of password reset to reconstitute the encrypted wallet.

After linking the wallet with the account, the user can choose whether to remain in
pseudo-anonymity (using only username and password) or linking his identity to the account. In order to link his identity, the user can choose to use a
PSD2 authentication with cell phone and email, or by digitally signing a pdf that certifies the possession of the wallet
and sending it by pec. The notarization has legal value, the link between identity and possession
of the wallet is what allows, in the evidentiary phase, not to leave the link between digital identity of a person and
the address of the wallet to the free interpretation of the judge, as happens in the case
of pseudo-anonymity.

Pablock uses Polygon and Ethereum as its blockchain. Polygon is a permissionless layer
2 of Ethereum that is highly adopted and efficient in terms of speed and number of transactions executed.
When the user notarizes a file, the transaction is executed directly from their client-side wallet.
The main transaction takes place on Polygon and then, through the checkpoint mechanisms provided by the Polygon’s validators, on the Ethereum mainnet.
Unlike other file notarization platforms on the blockchain that use a centralized database to store the files, the documents notarized via Pablock are stored on the
decentralized IPFS database. The entire process of notarizing and uploading the file to the IPFS node takes place on the
client side, which will send the response data to the Pablock server, which will save the IPFS address references of the file and the transaction data.
On the interface side the user will get a receipt with verifiable data of the correct transaction on both
Polygon and Ethereum and the IPFS reference CID.

To certify a file, of any type (audio tracks, texts, images…), the user must only upload the
file on Pablock, enter a title and a description and confirm the notarization of the file.
contract written and deployed by BCode will be issued an event containing the hash of the notarized document. The first notarization confirmation the user receives is the one from Polygon. Once the file is notarized on Polygon, the user can download the notarization receipt and the file will be
always visible on Pablock, in the archive of notarized files. Then the file is notarized
on the Ethereum mainnet. In addition, you can independently verify the certification of files
from an Ethereum blockchain explorer, such as Etherscan, or any other blockchain explorer
independent of Pablock.

The strength of a notarization carried out through Pablock is that it takes place completely on the device of the user. When a user chooses to notarize a document, the transaction is managed locally on the client along with the upload of the document to the IPFS node, the data received in the transaction receipt and the IPFS address of the document will be sent to the Pablock backend to be saved.

It is possible to create NFTs (ERC721) to be associated with a file, and to send them to your contacts, or to keep them in your wallet, or to export them outside Pablock: to give them away, sell them, or do what the user thinks is best. Before certifying the file you can choose the number of NFTs to generate. Once created, the file will be associated with its NFT and will always remain the property of the user, until the user gives it up or sells it.

The report is a notarization receipt that provides the user with all the information needed to independently verify that the file has been notarized correctly, using an explorer from Polygon or Ethereum, and view the file on IPFS.

Once data is notarized on Polygon and Ethereum, Pablock provides a notarization report. The following information can be found within this document:

Notarization title: title of the notarized file.
Hash of the file: hash of the notarized file. Before being notarized, the file hash is calculated. This way any changes made to the file will produce a different hash.
IPFS Address: IPFS address of the file to search for the file on IPFS.

Matic Transaction (Polygon):
Sender address: address of the user’s wallet.
Recipient Address: address of the recipient’s wallet (Smart Contract)
Transaction hash: Hash of the transaction.
Block number: number of the block in which the transaction is inserted.
Block Hash: Hash of the block added to the network.

Ethereum transaction:
Sender address: address of the user’s wallet.
Recipient Address: Address of the recipient’s wallet (Smart Contract).
Transaction hash: hash of the transaction.
Block number: number of the block in which the transaction is inserted.
Block Hash: Hash of the block added to the network.

Once a file is uploaded, after entering the title and description, the user can choose to use the the multi-signature option of a file, allowing his contacts to sign files jointly, securely and without cheating. This option allows you to manage the signing of your files within your network in a totally transparent way. This option allows you to manage the signing of your files within your network of contacts in a totally transparent way. Using the multi-signature option you deploy a contract representing the document is deployed with the IPFS address of the document and the address of the contacts who must sign. It will then be up to the invited contacts to sign the document through the web-app.

With Pablock it is possible to choose, when notarizing a file, whether to make the contents of the document public or not. This feature allows you to manage your files and network in the most optimal way for you. In fact, choosing to protect the content of the file you can choose to encrypt it with a password, through a symmetrical encryption algorithm, and give the possibility of viewing a document by another user only if in possession of the password; or it is possible to encrypt in an asymmetric way with the public key of the wallet in order to make the consultation of the document possible to the author. 

If you don’t want to notarize the file, you can always just notarize the hash of the file, without ever having to upload the file to Pablock. Each change made to the file generates a different hash, which must be notarized again. This way you can be sure that each notarized hash corresponds to only one version of the file.

Since the user is the sole owner of the wallet, in case of loss of password by the user, the account If the user loses his password, the account can be recovered in two steps:

  1. If a user loses the primary password, he/she can request through the application interface the If a user loses the first password, he can request through the application interface the recovery of the primary password using the secondary password for wallet recovery.
  2. If both passwords are lost, the user resets the password and a new wallet is generated. a new wallet is generated. In our DB the old and new addresses are saved and the change of address is noted. The identity and account of the user will be connected with the the new wallet.

In order to leave ample room for management and flexibility to the user, we decided to base our subscription plans on transactions. Depending on the plan, the user can perform a maximum limit of operations per month. What are operations? An operation is any of the following actions performed by the user within Pablock:

  • Certify a file.
  • Create an NFT.
  • Exchange/export an NFT.

Each of these actions corresponds to an operation. So creating a file and associating an NFT with the file corresponds to two operations. If you decide to create two NFTs then the operations will be two, as a single NFT corresponds to a single operation. We decided to use this system to give the user total room for maneuver in the management, according to their needs, of the operations to be carried out monthly.

No difference, they mean the same thing.

Pablock cannot access your wallet in any way. Within our database the wallet is encrypted by your password. The only one who knows the private key of the wallet is the user. When the user logs into Pablock his wallet is retrieved encrypted with the user’s password.

Pablock does not use any database to store your files. We use a decentralized IPFS database to store your files. The IPFS (or InterPlanetary File System) decentralized database is a decentralized, peer-to-peer data storage and sharing communication protocol. We do not sell disk space or store any documents on our servers.

Pablock API

BCode in addition to having developed the Pablock web-app, also provides the API service for those who already had a functioning system and would like to integrate notarization on blockchain or the creation of NFTs.
Through this service, customers can notarize data on blockchain in two different ways:

  • By directly providing the data they want to notarize to Pablock.
  • By providing the hash of the data they want to notarize to Pablock.

In both options, Pablock notarizes the data, signing with their wallet, and returns to the client the notarization confirmation and the IPFS address where to find the notarized data. Via API, customer files and data files and data are notarized by Pablock, i.e. signed with the Pablock wallet.

In addition to the service described in the previous point it is possible for customers to sign data with their own wallet. This is done by means of SDK (Software Development Kit), a package with more tools provided by Pablock for notarization of data. It includes functionalities of file hash calculation, data encryption and decryption, and integrates notarization functionality in various modes. The advantage of using the SDK is the ability to use your own wallet to perform the The advantage of using the SDK is the ability to use your own wallet to perform notarizations, making integration into systems more customizable.


A public address suitable for distinguishing the Wallet, which is derived from the Public Key and consists of an alphanumeric code.

A private key consisting of a unique alphanumeric code (i.e. mathematically generated strings of random characters) that can be considered as a password that gives access to the Wallet

A public key, also consisting of a unique alphanumeric code that is generated from the Private Key through a cryptographic function.

“Content identifier” assigned by IPFS to a given Digital File using cryptographic Hash functions.

Block encryption algorithm with symmetrical (private) or asymmetrical keys (a public key to encrypt and a private one to decrypt) of predetermined length that allow you to “hide” the content of a dataset, transforming it into a sequence of numbers and letters, which only those who know the private (and therefore secret) keys are able to decrypt.

Digital files of any format (text, image, music file, etc.).

Methods of subscription pursuant to articles 1, letter (s), and 24 of Legislative Decree no. 82 of March 7, 2005.

Subjects identified by the User to collect the relevant signatures on the Digital File through the Wallet, in case of Multi-Signature Validation.

Function of the Platform that allows, via Encryption performed with the Public Key, to not make visible to the public, including other Users, the content of the Digital File as well as the title and description of the Digital File entered by the User on IPFS when uploading the Digital File to IPFS.

Function of the Platform that allows to store on Blockchain only the Hash of the Digital File and not the Digital File itself, so that the latter is not in any way accessible to subjects other than the owner of the File. Digital

“Fingerprint” of the Digital File, obtained through a cryptographic function that transforms a dataset, regardless of its relative size, into a unique alphanumeric code with a predefined length.

Jointly or severally, Identification by PEC and Identification by Mobile.

The method of identification of the User via Pablock, which consists in the User being asked, via Pablock, to send a 6-digit pin code (of which 3 digits are sent to the cell phone number, and 3 digits to the email address, communicated by the User to BCode), and the User entering said complete pin code on Pablock.

The method of identification of the User through Pablock, which consists in the User’s request for the creation, by Pablock, of the User Card, signing of the User Card by the User by means of a valid Digital Signature and sending of the signed User Card from the User’s PEC address to BCode’s PEC address.

The InterPlanetary File System distributed registry.

“Non-fungible tokens” – i.e. crypto-assets constituted by a unique series of digital information recorded within a Blockchain, which embody a non-fungible right in favour of their owner (e.g. certificates attesting the ownership of a certain asset in favour of the owner of the relative NFT), and which can be stored in wallets operating on Blockchain or sold or exchanged on third party platforms of so-called “exchange” – associated with the Digital File.

La Blockchain Polygon-Matic.

Private writing that makes full evidence, until a suit for forgery, of the origin of the statements from the person who signed it, if the person against whom the writing is produced recognizes the signature, or if this is legally considered as recognized, pursuant to and for the purposes of Article 2702 Civil Code.

The form containing the indication of the Public Key, the Address and the personal and/or corporate data of the User, prepared by BCode for the purpose of identification by Pec of the User.

Computer program, which operates on Technologies Based on Distributed Records, and the execution of which automatically binds two or more parties based on effects predefined by them (see Article 8b, paragraph 2, of the Simplification Decree 2018).

Information technologies and protocols that use a shared, distributed, replicable, simultaneously accessible, architecturally decentralized registry on a cryptographic basis, such that data can be recorded, validated, updated, and stored both in plain text and further protected by encryption that is verifiable by each participant, cannot be altered, and cannot be modified (see Article 8b(2) of the 2018 Simplification Decree).

Technologies based on Distributed Registries of third parties, such as IPFS, Polygon and Ethereum.

A set of digital information recorded on Distributed Records Based Technologies and representing some form of value or right, such as, but not limited to, ownership of an asset, truthfulness of a piece of information, access to a service, attestation of receipt of a payment, or attestation of the existence of a fact, event.

Jointly and severally, Digital File Validation, NFT Validation, and Multi-Signature Validation.

Blockchain storage of the Digital File with the date and time of such storage, to demonstrate at a later time that the Digital File has not been modified.

Storage on Blockchain of the signatures collected via Wallet on the Digital File of both the User and the Signatories, including the date and time of collection of each Signatories’ signature, to demonstrate at a later date that the Digital File signed by each individual Signatory has not been modified.

Storage on Blockchain of each NFT with the date and time of such storage, to demonstrate at a later time that the NFT has not been modified.

“Ethereum Wallet”, i.e. a digital wallet on Ethereum, which gives the User a cryptographic identity, accessible through a double key mechanism, i.e. the Private Key, which can be considered as a password that gives access to the Wallet, and the Public Key. Each Wallet is characterized by the Address.

Do you want to become a superhero?

Follow us on our social channels to stay updated on the latest news!