# Signature

Our Tokenization Signature Process is designed with two primary functions to boost the security and efficiency of the signature process. The first function, "Sign," enables users to begin the signing process by clicking the sign button on our Notarizations interface. Signing a document requires the user's password and is securely executed on the Algorand Blockchain. The second function, "Forward," allows users to enter the email addresses of one or more recipients, who are then invited to sign the document. Recipients receive a "Request of Signature" email, inviting them to either register or log into our platform. Here, they can view detailed information about the file, download the document for review, and sign it on the blockchain, completing the process.

### Signature <a href="#pdf-page-42njyale0ilxlzapqoku-signature" id="pdf-page-42njyale0ilxlzapqoku-signature"></a>

The signature includes a robust process for users to sign Tokenized files on the blockchain using their Algorand wallets. This process ensures the integrity and authenticity of the transactions and involves several critical security steps.

The Hash sha-256 of the file is signed using the user's private key with the Algorand SDK function `sign_bytes(to_sign, private_key)`, ensuring the signature's security and uniqueness.

The outcome is a verifiable base64 signature string that is intrinsically linked to both the document and the signer's identity. This signature is then incorporated into the metadata and recorded on the blockchain.

The metadata of the notarization is modified and the list of signers and their corresponding signatures are added. Each time a new signature is added, the signer and their signature are appended to this list.

Then, a transaction to reconfigure the Asset associated with the notarization is executed, linking this new metadata to the asset. This step integrates the signature details directly into the blockchain, providing a transparent and secure record.

### Let's See How to Sign Your Notarization <a href="#pdf-page-42njyale0ilxlzapqoku-lets-see-how-to-sign-your-notarization" id="pdf-page-42njyale0ilxlzapqoku-lets-see-how-to-sign-your-notarization"></a>

{% content-ref url="/pages/LxDCWudxMqPrlv237UCP" %}
[Sign your Tokenization](/toknox.docs/signature/sign-your-tokenization.md)
{% endcontent-ref %}

### To Request a Signature on Toknox

{% content-ref url="/pages/xGzRncdjahB8QZGKkOm3" %}
[Request a signature](/toknox.docs/signature/request-a-signature.md)
{% endcontent-ref %}

### Received a Signature Request on Toknox? Let's Review!

{% content-ref url="/pages/PsWLR9cxb06ZUvKnzZFY" %}
[Received signature request](/toknox.docs/signature/received-signature-request.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://toknox.gitbook.io/toknox.docs/signature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.