HoodSpin/Technology
Protocol design

A clean separation between UI and settlement.

The frontend handles wallet interaction and wheel animation. Eligibility, quota enforcement and reward settlement are designed as independent verifiable layers.

Wallet layer

HoodSpin uses a standard EVM wallet provider. On connection, the site requests the selected account and checks Robinhood Chain mainnet (chain ID 4663). If the wallet is on another network, the app can request a switch to 0x1237, with ETH as the native gas asset.

network configuration
chainId: 0x1237
network: Robinhood Chain
nativeAsset: ETH
rpc: rpc.mainnet.chain.robinhood.com
explorer: robinhoodchain.blockscout.com

Token-gated eligibility

Once the $HOODSPIN token address is configured, the frontend can call the standard ERC-20 balanceOf(address) function. The launch configuration defines the minimum token units required to unlock the wheel.

Important: the public website currently ships with the token contract field intentionally blank until the final deployment address is supplied. This prevents the interface from pretending to verify a contract that does not yet exist in configuration.

Spin quota

The interface exposes a maximum of three spins. For a production launch, spin usage must be persisted outside the user's browser—either through a smart contract mapping, a signed backend ledger, or another tamper-resistant source.

A simple model is wallet → spinsUsed. The system checks the value before issuing an outcome and increments it only after a valid spin is accepted.

Reward settlement

The production design expects a secure endpoint or contract to return the authoritative reward result. The frontend then rotates the wheel, reveals the selected mystery box and displays settlement status.

1

Request

Wallet address + chain state are submitted to the settlement layer.

→
2

Validate

Eligibility and unused spin quota are checked before accepting the spin.

→
3

Settle

The selected Robinhood Stock Token reward is recorded and transferred or made claimable.

Security boundaries

  • The website never needs a seed phrase or private key.
  • Wallet connection alone must not authorize token transfers.
  • Outcome authority should not live in client-side JavaScript.
  • Spin quota should not rely on local storage in production.
  • Reward transactions should be independently inspectable on Robinhood Chain Blockscout.
  • Contract addresses and treasury addresses should be published before launch.