Try it on testnet

What this trial does

The local trial runs the frontend and API on your computer while transactions use Robinhood Chain testnet, chain 46630. The browser wallet signs deployments and basket transactions. The backend does not need your private key.

Testnet tokens and test ETH are separate from mainnet assets. Use a test account and verify the network in your wallet.

Start the application

With Node 24, Foundry, and the source repository’s dependencies installed, build the contracts:

forge build --root contracts --offline

Run these in separate terminals from the source repository:

npm --prefix backend run trial

npm --prefix frontend run dev

Open http://localhost:3000. The default local trial uses the API on port 8787 and chain 46630. If you have overrides, set the frontend to those trial values. See local development for installation and environment details.

Prepare the deployment

Open Testnet setup in the footer or Testnet setup & transactions in the wallet dialog. Select Connect wallet & prepare, choose your wallet, and switch to testnet.

Use the official Robinhood testnet faucet if you need ETH. Return to the app and select Prepare / resume setup.

A fresh local setup can request five sequential wallet transactions: the community factory, two manual test tokens, the native funding factory, and the native trading router. The app requests only missing deployments and reuses valid existing setup.

Keep the same wallet account and browser storage while preparing. If interrupted, explicitly resume; do not start replacement deployments simply because an RPC temporarily cannot verify a previous transaction.

Launch a test basket

Once preparation is ready, choose compatible testnet assets with active routes, set weights, name the basket, choose an issuance fee, and enter an ETH backing budget.

Preview allocations, inspect minimum token amounts, sign the metadata request, and confirm the launch transaction. A confirmed launch should have actual backing and one gross initial share before the issuance fee is split.

Follow create your first ETF and use the testnet explorer to verify the transaction. Token availability and pool liquidity can change, so treat example tickers as illustrations rather than promises of executable routes.

Exercise the exits

Preview a small ETH buy or sell where routes are available. Choose Basket mint / redeem to exercise the vault route. Then expand Underlying tokens, select Redeem, and test a direct redemption followed by individual token claims in Claims.

The two manual faucet tokens created during setup do not come with swap liquidity. They are intended for lower-level in-kind funding and accounting tests, not automatic native ETH funding. The trial’s manual-token panel makes them available for those tests.

Preserve the trial state

The ignored local trial data directory stores deployment sessions, metadata, and index state. Keep it when restarting so the trial can revalidate and reuse its existing contracts.

Fork smoke tests run against a local Anvil fork and do not broadcast their signed transactions to the public chain. They establish execution and accounting behavior for the tested state, not expected returns or production qualification.