Choose tokens
Understand discovery, stock tokens, address imports, and the checks behind an executable basket.
Addresses establish identity
Identify every asset by chain ID and contract address. Names, symbols, and pictures can be copied. Confirm addresses using the issuer’s trusted source and the selected chain’s explorer.
The basket supports 2–10 distinct contract tokens. Each weight must be positive and the weights must total 10,000 basis points, or 100%. There is no minimum market capitalization, creator allowlist, or buyer-demand requirement.
Browse tokens
The app offers discovery lists and address inspection. On mainnet, market discovery can use Codex volume and liquidity data. Those lists make assets easier to find; they do not approve or endorse their safety, value, or transfer behavior.
Testnet can use the explorer’s ERC-20 directory and the connected wallet’s indexed holdings. Newly deployed tokens may take time to appear. Pasting an address allows an RPC inspection without waiting for indexing.
Stock tokens
The mainnet stock picker reads Robinhood’s issuer registry and accepts active deployments for chain 4663. Verify the issuer registry entry and exact deployed address; a matching stock ticker alone is insufficient.
Stock tokens provide economic exposure and do not convey ownership of the underlying shares. Their raw token quantity may differ from the underlying share quantity. Transfers can also be subject to token-level restrictions.
A registry match does not bypass onchain inspection or ETH-route checks. See Robinhood’s Stock Token APIs for issuer information.
Import a contract address
Paste the address and inspect the returned token metadata and network. Missing names or symbols can be displayed using address-based labels. Missing decimals require care with raw units; the interface must not invent decimals.
Curation does not gate the permissionless contracts. However, the ETH-funded app flow requires routes and exact-transfer compatibility. An asset that cannot pass those checks may require a different funding method or may be unsuitable for these vaults.
Compatibility is more than a balance
Vault accounting checks observed transfer amounts. Transfer-tax tokens can fail these checks. Rebasing, blocking, pausing, issuer-controlled upgrades, and other unusual token behavior can break later deposits, swaps, or claims even if creation once succeeded.
Token metadata and market discovery cannot prove long-term compatibility. The creator cannot remove a broken constituent from a fixed community basket after launch. Read security and trust before making a selection.
A quote needs real liquidity
An indexed or curated asset can have no executable route. Native funding and ETH trading check routes through the configured venue, including pool identity, liquidity, slippage, price impact, and shared-pool conflicts.
If the route is missing, choose another asset. If a route exists but the intended amount fails its execution bounds, adjust the amount or allocations. Two token selections that quote independently may still conflict when they share a pool.
Direct in-kind funding does not need swap liquidity, but still requires supported token transfers and correct backing. It is a contract/SDK flow; it is not a way to bypass accounting checks.