# Transfers Transfers enable the transmission of up to two commitments of the same asset between two parties by nullifying the previous commitments and creating up to two new commitments. To ensure a recipient receives the secret information required to spend their commitments, the sender encrypts the secrets of the commitment sent to the recipient. A Transfer ZK Proof proves that the prover has nullified up to two old commitments which existed in the Merkle Tree, created a new one, and encrypted its information for the recipient. In either case, the information broadcasted on chain will be that an Ethereum address has nullified commitments among the commitment pool owned by the transmitter, and that new commitments have been created. Information on the new owner, which commitments were spent or the amount transferred remain discreet.\ \ Check out Hinkal's current [fee structure](broken://pages/sgX0WvO2Y3IRFQ3g6rKh) used to fairly compensate for the costs. --- # 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://hinkal-team.gitbook.io/hinkal/technical-description/transactions/transfers.md?ask= ``` 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.