See what happened.
Know what comes next.
A testnet receipt, a missing image, and an unavailable market mean different things.
Check the scene
The Robinhood public-testnet demo uses chain 46630 and the local scene uses 31337. Both use test assets and demo market infrastructure. Neither is a production launch.
If the app is waiting for a deployment or runtime connection, a static frontend alone cannot transact. The runtime, deployed contracts, and network connection must be available.
Bots are part of the demonstration
Seven named bot accounts generate actual test transactions. Their activity and prices come from mined actions rather than a decorative ticker. They mint, trade, and convert eligible inventory under operator controls. Automatic bot moves use the seeded showcase collections; newly uploaded creator collections are available for manual exploration.
Bots start paused. Pausing lets an in-progress move finish. An unresolved transaction or error stops further work for inspection. Bot volume is synthetic participation, even when its transactions are real.
Find the relevant next step
| What you see | What to check |
|---|---|
| Conversion locked | The collection’s opening timestamp; sellout does not override it. |
| Mint or trade failed | Test balances, gas, approvals, available supply, and execution limit. |
| Selected NFT unavailable | Refresh vault inventory; another account may have redeemed it. |
| Artwork pending | Reveal and content availability separately from NFT ownership. |
| Submission uncertain | Transaction hash and canonical receipt before another attempt. |
| Supply left, quote checkout unavailable | Purchasable FLOOR and liquidity. The one-token buffer is not a guarantee. |
Keep useful details
Record the chain, public wallet address, collection address, transaction hash, and exact visible message. These let an operator diagnose the issue without asking for secret material.