Deposit
A deposit moves a supported token from your public wallet into your private SEAL balance. Lending assets can then earn variable Aave yield; custody assets do not earn lending yield.
Mainnet deposits are not yet available. Use demonstration funds in the sandbox or the selected deployment's test tokens on testnet.
Make a deposit
- Open your SEAL account and check the selected network. For Google-created or passkey accounts, connect any supported EVM wallet to fund it; changing funding wallets preserves your SEAL address and balances.
- Save a current account backup.
- Choose a supported asset and amount.
- Approve token spending if requested, then review and confirm the deposit.
- Wait for confirmation and account synchronization before using the balance.
A sufficient existing approval can be reused. Some tokens require resetting an old approval first. Keep native gas for wallet-submitted approvals and deposits.
When the token supports permits and the selected intent service is online and supports deposits, ZK Intent Service is selected by default to deposit without ETH. You can opt out by choosing Wallet and paying gas in ETH; the dialog keeps that choice while you edit the amount or asset. Review the execution fee in the deposited token, then sign the deposit authorization and, if needed, the token permit. Neither signature sends a wallet transaction. The service pays network gas and deducts the authorized execution fee from the gross deposit; any protocol deposit fee applies to the remainder. An existing allowance to the deposit adapter requires only the deposit signature.
Permit support belongs to a specific token contract and network. Ethereum USDC, EURC, PYUSD, wstETH and XAUT accept standard EIP-2612 permits. DAI uses a different, boolean authorization format; the standard permit flow must not be used for it. USDT, WETH and WBTC use wallet approvals. The app verifies the configured permit domain before requesting a signature.
The nine SEAL test tokens on Sepolia all support EIP-2612, including test USDC. These mintable test contracts are separate from issuer tokens and let you test both permit deposits and wallet-paid deposits.
Keep the saved account data while execution is pending. If the page reloads or the service response is interrupted, the app reconciles the saved intent with the chain. Check or resume that intent before signing a replacement. Closing the dialog does not cancel an already submitted authorization.
When funds become available
A wallet confirmation prompt is not confirmation onchain. The app checks the confirmed deposit and its private records before making the balance spendable. Cached balances shown during synchronization cannot authorize spending.
Aave reserve capacity, liquidity and token restrictions can limit an operation. The app checks the transaction before submission, but an estimate cannot reserve future capacity.
What is public
The deposit's submitting address, asset, amount and timing are public. Your private spending keys and account records stay encrypted. Depositing does not make the original wallet history disappear. See Privacy.
Costs and payment addresses
New pools start with zero SEAL protocol fees. Network gas and any authorized execution fees are separate; see Fees & Costs.
A SEAL payment address is used inside SEAL. Sending an ordinary ERC-20 transfer to it does not create a private payment. Deposit into your own account, then use Send & Receive.