Supported assets & addresses

A Robinhood-Chain launch can be quoted in - and can pay its holders in - the US dollar stable USDG, any of 157 world currencies (the fx family: fxEUR, fxJPY, fxINR, and every other major and emerging-market unit), a curated crypto major, or a tokenized US equity. Pairing and reward payouts draw from the same asset universe. Robinhood is the only chain with the full stock-native suite; Base and BSC carry tokenized-stock payouts and pairs as described in their sections below.

Dollar stable

USDG

Currencies

157 (fx*)

Stocks

41

Pair quotes total

199

Reward payouts

196+

Decimals (fx)

18

What a launch's Paired with field offers on Robinhood Chain. The pair is permanent at launch. Addresses are ERC-20 contracts on chain 4663.

The assets a Robinhood reward token can pay its holders in. A currency- or stock-paired reward token pays its pair asset directly (no conversion); a native (ETH) launch converts its fee stream into the elected asset each keeper cycle. Native ETH itself is also a payout option on Robinhood.

Graduated PONS-venue tokens on Robinhood trade in-app through the permissionless DegenPonsSwapRouter at 0xcaf5b3356119789b8de68d7df07c5218b63ed2f3. See Trading.

Arc's gas coin is USDC, so an Arc launch is paired against native USDC and a reward token there pays holders in USDC as-is (no swap), in the launch token itself, or in a Circle asset bought on Arc's canonical Uniswap V4 USDC pool. Arc has no custom LP-pair quotes and no tokenized stocks. Addresses are ERC-20 contracts on chain 5042.

A routed asset on this shelf is gated by a live route check: if its USDC pool is not seeded, the wizard hides it until liquidity appears.

A Base launch is quoted in native ETH by default, or paired against USDC or one of the Coinbase tokenized stocks (AAPLc, GOOGLc, MSFTc, NVDAc, TSLAc). Reward tokens pay holders in USDC, cbBTC or a routable Coinbase stock, converted from the ETH fee stream each keeper cycle. Addresses are ERC-20 contracts on chain 8453.

Dollar stable

USDC (6 dec)

Pair quotes

6

Stock pairs

5 (8 dec)

Reward payouts

5

Stock payouts

3

Native payout

none

What a launch's Paired with field offers on Base. A stock-quoted pair pays its quote to holders directly, with no swap. TSLAc is routeless: launchable and tradeable in the stock itself, but with no ETH zap.

The assets a native-ETH Base reward token can pay holders in. Every one is converted through Uniswap V3 on Base (USDC and cbBTC in one hop from WETH; the stocks via WETH to USDC to stock). Native ETH is not a payout option on Base: holders receive the launch token by default, or one of these.

MSFTc and TSLAc are pair quotes but not payouts: one is too thin for fee-sized swaps, the other has no route at all. A payout a swap cannot fill is a fee stream lost to slippage, so they are left off this shelf on purpose.

The degen.zone contracts a Base launch touches, all on canonical Uniswap V4. Copied from the deployment record; the launch page reads the same addresses at runtime.

BSC is a three-venue chain: a direct launch opens its pool in a plain PancakeSwap V3 pool, in canonical Uniswap V4 (the default), or in PancakeSwap Infinity (where BSC liquidity and the bStocks live). The native coin is BNB. A BSC launch is quoted in BNB; custom LP-pair quotes are not on BSC yet (the pair suite is not deployed there), so stock exposure on BSC means bStocks as reward payouts on Infinity launches. Addresses are BEP-20 contracts on chain 56.

The PancakeSwap V3 venue is different in kind: the pool has no fee hook, which is exactly why every BSC trading bot, sniper and chart already supports it. There is no per-trade creator fee, no referral rail and no reward-token or buyback&burn model. The creator picks the pool fee tier instead (0.25% or 1.00%) and earns a share of the pool's LP fees: PancakeSwap keeps 32% of every LP fee at protocol level, the position minted with the whole supply earns the rest, and the fee vault splits that 65% to the creator and 35% to the platform on collect - about 0.44% of volume on the 1% tier before any third-party liquidity dilutes it. Reward payouts below do not apply to this venue.

Native coin

BNB

Dollar stable

USDT (18 dec)

Payouts (Infinity)

7

Payouts (Uniswap V4)

3

bStocks

3 (18 dec)

LP pair quotes

none yet

The assets a BSC reward token can pay holders in, converted from the BNB fee stream each keeper cycle through a V3 DEX: the Infinity venue's factory spends through PancakeSwap V3, the Uniswap V4 venue's through Uniswap V3 on BSC. There is no BNB payout option (no ERC-20 view of the gas coin) - holders receive the launch token by default, or an elected asset.CAKE and the bStocks are Infinity-only because Uniswap V3 on BSC has no usable pool for them.

Two address sets, one per liquidity venue. The launcher, router and bundler ABIs are identical across the two; the venue only decides which set a call goes to. Copied from the deployment record on 2026-09-19.

A Solana launch opens directly into a Raydium pool quoted in SOL, a curated stablecoin, a tokenized stock (xStock), or a Pre-IPO unit. Reward tokens (Token-2022) pay holders in their pair asset or an elected reward asset. Addresses are SPL mint accounts.

The curated Paired with shelves on Solana. SOL carries no mint by construction (the partner config owns its own wSOL). Additional community quotes can be verified from a pasted mint at launch time and are not listed here.

The assets a Solana reward token can pay holders in, harvested and swapped by the keeper each cycle. xStocks are only bought while the US equity market is open.

The asset tables are rendered straight from the platform's live asset registries at build time - the very lists the launch page's pickers read. A currency or stock that appears here is offered; one that does not, is not. Community-verified custom quotes and custom reward assets (pasted at launch) are deliberately omitted - they are proven per launch, not curated here.

The contract tables are copied from the deployment records in the repository. The app itself reads every launcher, router and fee value from the chain at runtime, so if a redeploy ever moves an address, the wizard is right and this page lags until its next build.