Depositing Assets

Deposit assets from Ethereum to Aztec.

Deposits have 2 steps:

1. The user sends a transaction specifying an amount of ETH to deposit to the Aztec rollup contract by calling depositPendingFunds. When deposit DAI with this function, the rollup processor must be approved to spend the user's DAI. Or a user sends a transaction with DAI to the rollup contract by calling depositPendingFundsPermitNonStandard. Read more about using the DAI permit flow here.
2. The user creates a proof on Aztec to claim the pending deposit. The proof includes information about the Ethereum account that made the deposit, the amount of the deposit, the Aztec transaction fee and the recipient account on the Aztec network.

When using an externally owned account on Ethereum, this flow is managed by the SDK. You can read more about using the SDK to deposit funds into Aztec on the SDK deposit page.

If the depositing account is a smart contract (e.g. a smart contract wallet), a proof hash corresponding to the hash generated by the DepositController must be passed to depositPendingFunds (or similar). For more detail about how to execute deposits from a smart contract, refer to the Advanced Usage section of the SDK page on deposits.

Here is the interface for depositPendingFunds.

function depositPendingFunds(
        uint256 assetId,
        uint256 amount,
        address owner,
        bytes32 proofHash
    ) external payable;

depositPendingFundsPermitNonStandard works similarly to depositPendingFunds but with the permit flow instead of the approve flow. DAI requires a non-standard flow because their implementation of permit requires a nonce.