Supported assets

Robinhood Chain assets only#

The intended product handles assets on its configured Robinhood Chain environment. A token symbol or icon is not enough to identify an ERC-20 asset. Use the chain identity and contract address. The native gas asset is a separate native-asset type rather than an invented ERC-20 address.

What support requires#

A token can exist on a network without being supported by QuiverDex. Support depends on the asset registry policy, adapter compatibility, token behavior, and whether a valid route can be quoted and executed. Liquidity in an arbitrary pool alone is not sufficient to imply support.

Metadata and decimals must be reliably known before building a real transaction. A symbol, name, or decimals field may be missing in some token contracts; ERC-20 defines these metadata methods as optional.^[1] The interface must not silently assume an unverified precision.

How the registry should be displayed#

The asset view should include the name, symbol, contract or native identity, decimals, support status, route status, and a last-updated timestamp. If the registry is unavailable, show Supported asset registry unavailable rather than filling the page with sample listings.

Recognized metadata means the application recognizes an identity. Route available means a supported quote is available for the relevant amount and direction. Restricted means an applicable rule prevents that operation. None of these labels is an investment endorsement or proof that an asset is risk-free.

Finding an asset#

Search by symbol, name, or contract address. For similarly named assets, compare the full contract identity. If an asset is not recognized, inspect the warning and support status before proceeding. Do not treat a pasted address as automatically safe.

A “no route” result can depend on amount, direction, stale state, restricted transfers, or unsupported pool types. It should not always be interpreted as “the token does not exist.”

Special token behavior#

Transfer fees, pausing, allowlists, rebasing, or other restrictions can affect execution. The product must explicitly support relevant behavior rather than assume every token follows a simple transfer model. Any tokenized-stock listing needs its own verified asset identity, eligibility information, and integration support; a Robinhood Chain network label alone does not establish these.

Listing policy#

A documented listing process should identify the required technical evidence and any review criteria. This draft does not announce automatic listings, a listing fee, or a guaranteed turnaround. It also does not announce a Robinhood token or a QuiverDex token.

Read Routing to understand indirect paths and Safety before approving unfamiliar assets.