Skip to content

Status

What actually works right now

This page is generated from configuration and live on-chain reads, not from marketing copy. If something says blocked, the button for it is disabled everywhere in the app.

Live deployment checks

Read directly from the chain each time this page loads: address format, bytecode, interfaces, registry↔factory pointers, roles, pause state and implementation lock.

Querying Robinhood Chain Testnet…

Uniswap v3 liquidity (mainnet only)

Waiting for the live check…

Feature configuration

  • Active network — configured

    Robinhood Chain testnet (46630)

  • Mainnet writes — not configured

    Disabled until the deployed contracts pass every live check and VITE_ENABLE_MAINNET=true

  • Item Passport registry contract — not configured

    VITE_ASSET_REGISTRY_ADDRESS not set

  • Companion token factory — not configured

    VITE_TOKEN_FACTORY_ADDRESS not set

  • Expected administrator — not configured

    VITE_EXPECTED_ADMIN_ADDRESS not set (optional on testnet)

  • Escrow contract — not configured

    VITE_ESCROW_ADDRESS not set — on-chain purchases stay disabled

  • Liquidity locker — not configured

    VITE_LIQUIDITY_LOCKER_ADDRESS not set — liquidity locking stays disabled

  • WalletConnect — not configured

    Optional. Injected browser wallets still work.

  • IPFS pinning — not configured

    Set the server secret PINATA_JWT to pin passport photos and metadata to IPFS. Until it is set, passports cannot be frozen at all: a passport only ever references permanent ipfs:// content IDs, never a storage copy.