MINTAT

Mints a new authenticator token. This action does not require a zero knowledge proof. Authenticator tokens do not (directly) represent real assets and thus have no leaves in the merkle tree. Instead, the corresponding $\mathsf{NoteCommit}$ of an authenticator token is used as an identifier for third party smart contracts where assets are privately deposited. By proving knowledge of the secret randomness of an authenticator token, the deposited assets asociated with this token can be withdrawn from the third party smart contract at a later point in time.

Privacy Implications

No assets are being moved by this action.

Flow

The following steps specify the flow of MINTAT.

Step 1

Create a new UTXO tuple $\mathsf{not}{\mathsf{e}}_{\mathsf{b}}$ representing the permission:

• $\mathsf{d}=$ Diversifier index of the ZEOS wallet address which owns this permission
• $\mathsf{p}{\mathsf{k}}_{\mathsf{d}}=$ Public key of the ZEOS wallet address which owns this permission
• $d1=0$
• $d2=0$
• $\mathsf{sc}=$ EOSIO/Antelope account of the third party smart contract where this permission is valid
• $\mathsf{nft}=1$
• $\rho =$ Choose a random value
• $\psi =$ Choose a random value
• $\mathsf{rcm}=$ Choose a random value

Step 2

Generate UTXO ciphertext ${\mathsf{not}{\mathsf{e}}_{\mathsf{b}}}_{\mathsf{enc}}$ of $\mathsf{not}{\mathsf{e}}_{\mathsf{b}}$ for the owner of the permission (see section 4.19.1 of the Zcash Protocol Specification)

Step 3

Execute the MINTAT action of the ZEOS smart contract. This action takes the following arguments:

• ${\mathsf{not}{\mathsf{e}}_{\mathsf{b}}}_{\mathsf{enc}}$: The UTXO ciphertext which is transmitted to the receiver of $\mathsf{not}{\mathsf{e}}_{\mathsf{b}}$

Step 4

The ZEOS smart contract performs the following operations:

• Add ciphertext ${\mathsf{not}{\mathsf{e}}_{\mathsf{b}}}_{\mathsf{enc}}$ to the Transmitted UTXO Ciphertext List