Find the Exact Collateral Token a Vault Accepts

To supply a vault, match the token’s network and contract address to the collateral asset the vault accepts. A ticker such as USDC or ETH is only a label; different contracts can use the same label, and a vault may accept only one of them. Start with the vault’s deposit screen or its documentation, then compare the token details with the asset in your wallet.

How do I identify a vault’s accepted token?

A vault’s accepted token is set by its contract or the deposit route connected to it. The network tells you which blockchain to use; the contract address identifies the token on that chain. Both must match. A token with the right address on the wrong network is a different asset for this purpose.

Open the vault’s deposit details and find the accepted asset’s network and address. If the interface shows only a ticker, look for a token-details view or an official address in the vault’s documentation. For a cross-chain deposit, the route can deliver a wrapped representation rather than the token the vault accepts. The separate explainer on the bungee bridge follows how route selection and transfer delays affect that step.

Then inspect the token in your wallet on the destination network. Compare the full contract address, not just the first and last few characters. A token list can help identify an asset, but the vault’s accepted address is the reference point.

Why can the right ticker still be the wrong collateral?

Tokens can share a ticker while having different contracts. One may be issued directly on a network; another may be bridged, wrapped, or issued by a different organization. They can have different redemption paths and different liquidity. A vault that accepts one contract does not automatically accept the others.

Think of the ticker as a name on a parcel and the contract address as its delivery address. The name helps you recognize it, but the address determines where it goes. For a vault deposit, verify these details before approving a transaction:

• Network selected in the wallet and on the vault.
• Full token contract address on that network.
• Vault’s listed collateral asset or deposit-token address.
• Any wrapper or bridge route between the token you hold and the one the vault accepts.

If a vault uses a deposit adapter, it may convert an accepted input into another token as part of the transaction. The deposit screen should show the input asset and destination vault. Check both: the input must be supported, and the destination must be the vault you intend to use.

What should I check before depositing?

Before sending funds, confirm that the wallet is on the vault’s network and that the selected asset matches the accepted contract. Check the amount and destination in the transaction preview. If the vault requires a swap or bridge, review the route and the token that will arrive; a route can complete successfully while delivering an asset the vault cannot take.

For a first deposit, a small test amount can reveal a network or asset mismatch, though it may incur the same transaction costs as any other deposit. If the address shown by the vault and the token details do not agree, pause and verify them through the vault’s official interface or documentation. The practical rule is simple: network plus contract address identifies the collateral; the ticker is only a clue.