Tokemak Deposit Requirements

An Autopool has a specific network and base asset. Select the pool before checking the connected wallet’s network and the asset balance available there. The app prompts for a wallet connection or network change when needed.

The app’s deposit controls let you choose an input asset and amount. An input asset can be swapped into the pool’s base asset as part of the deposit, so supplying a different token doesn’t change the vault’s denomination or underlying strategy. Review the available conversion and its slippage tolerance before authorizing it.

A token deposit can require a separate spending approval before the deposit transaction. Approval gives permission to spend the token; the deposit transaction supplies the assets to the vault. Auto-Stake can add receipt-token staking transactions to this flow, so a first deposit can involve more than one wallet authorization.

The expected share amount matters because entry slippage can affect the shares received. Check the deposit amount, expected shares, and chosen slippage tolerance before signing the deposit transaction. Network gas is another execution cost to consider alongside any asset conversion.

View image file

An Autopool receipt token represents shares in its vault. With Auto-Stake off, the deposit delivers those receipts to your wallet. With Auto-Stake on, the flow includes staking them for additional pool incentives where offered. The Portfolio view distinguishes staked, partially staked, and unstaked positions.

View image file

Autopool deposits have no lock-up or cooldown under the app guide’s withdrawal terms. Redemption requires enough unstaked receipt tokens for the amount being withdrawn. If part of the required balance is staked, that portion must be unstaked first. Execution remains subject to onchain liquidity and slippage.

Receipt-token staking for pool incentives is separate from staking the protocol token AUTO into sAUTO. The absence of an Autopool deposit lock doesn’t describe the withdrawal terms of a locked sAUTO position.

A Fireblocks wallet may need additional configuration depending on its transaction policy. If transactions with destinations outside its allowlist are blocked, both the Autopool and its router need to be allowlisted on the appropriate blockchain. The policy must also permit the transfers, approvals, and contract calls the selected flow uses.

Gasless approvals require typed-message signing permission in Fireblocks. The app also provides an option to disable gasless approvals and use standard approvals. These settings should remain consistent with the wallet’s security policy.

An Autopool can allocate assets among its configured destinations, including destinations it isn’t currently using. Those eligible assets and protocols define the exposure a depositor accepts; a current allocation alone doesn’t show every destination the strategy may use.

Vault shares can change in value as the underlying positions earn returns or incur losses. The documented entry and exit slippage also means a valuation estimate isn’t a guaranteed execution amount. A withdrawal exceeding the vault’s idle assets may require removing liquidity from destinations and swapping assets.

• If the wallet network differs from the pool’s network, resolve the mismatch before depositing.
• If the input asset needs conversion, check the base asset, expected shares, and slippage tolerance.
• Choose Auto-Stake according to whether you want wallet-held receipts or receipt-token staking for available incentives.
• If the deposit quote or requested permissions are unacceptable, decline the corresponding wallet request.