Guide to using Sign.net's Dapp

Access https://dapp.sign.net/login on any browser or even on Pera Wallet's in-built browser and login using Pera Wallet

Scan the QR code to login using your wallet, be sure not to close the first notification until the app ask you to confirm a transaction

On your Pera Wallet, approve the transaction, no ALGOs is used in this transaction as it is only just to sign a transaction that will be used as a token for authentication

On the main page, you can choose to Mint your NFDs or to Sign and Mint NFDs. We will show how to mint NFDs at the end. In order to mint or sign any documents, a minimum of 50 SIGN tokens is required. Be sure to have some ALGOs as well which will be used as gas fees (0.001)

You can choose to generate a key to use for encrypting your documents which we highly recommend if you are going to choose to store the documents on the IPFS

Drag and drop your selected document or click to upload them and press "Next"

On this page, you can choose to create your own signature, stamp or add in any other annotations to the document

Clicking on "Signature" or "Stamp" will allow you to place them anywhere on the document. You can also delete any annotations by selecting them and clicking on the "Delete Annotation" button

Add in your email, your recipient(s)' emails and wallet addresses

You can select the type of annotations you require from each individual recipient and place them on the document where you need them to be. You can delete any annotations by selecting them and clicking on the "Delete Annotation" button

For this example we will be uploading a key to encrypt our document

If you decide not to encrypt your document, you can just remove the key you have uploaded

Once you have uploaded the document, you and your recipients will receive and email notifying you about the signing request

As the recipient, after logging in using Pera Wallet, you will find the document under "Received Documents"

If the document is encrypted, you will be required to upload your own key before proceeding

Once you have uploaded your key, you can click "Approve". This step is to authorized the signing between both the receiver and the sender before the receiver can sign the document

Back to the sender, they will have a document under "Sent Documents"

Upload your original key used to encrypt the file

Click "Approve" to allow the receiver to begin the singing process

Back to the receiver, upload the key you used to decrypt the file

You can begin filling in the required annotations set by the sender on the right side of the screen

If there are multiple recipients, another set of approval process is required but now it is between the most recent signer and the receiver as designated during the sending process. Once every receiver has signed the document, the document can be found on everyone's "Completed Documents"

You can choose to mint the document as a NFD

You can choose to encrypt the NFD, enter custom fields such as the document name, description, and other fields

You can choose to store the document on the IPFS as well. If you choose to store it on the IPFS without encryption, anybody with the direct link can view the document. If the document is encrypted, and you want to view it without Sign.net's Dapp, you have to use a third party application to decrypt it

Now you are all set, you have your own NFD! If you only want to mint your documents, the process is similar to the minting process of signed documents