Skip to content
bankhood.
Launch App

Quick start

Connect a wallet, acquire BANK, and take your first airdrop claim.

On this page

The interface is live even though the protocol is not. You can connect a wallet, watch accrual tick, and run a claim end to end against simulated state. Nothing in this flow ever asks you to sign or send a transaction.

Prerequisites

  • An Ethereum wallet. Any injected browser wallet works, as does Coinbase Wallet. WalletConnect appears as an option when the deployment has a project id configured.
  • Nothing else. No ETH is required to use the app in its current state, because no transaction is ever broadcast.

1. Connect a wallet

Open the app and use Connect wallet in the header. Pick a connector from the dialog. The app requests your public address and the current chain id, and nothing else. If your wallet is on a network other than Ethereum mainnet you will see a Wrong network control that switches it for you.

2. Acquire BANK

Once the token is live, BANK will trade against ETH in a single primary pool on Ethereum mainnet. Buying and selling in that pool is what generates the fee that funds the reserve, so the acquisition step is also the funding step.

Until then the app derives a stable pseudo-balance from your address so the accrual and claim mechanics can be inspected. Every panel showing derived data is badged Simulated.

Transfers are untaxed

Moving BANK between your own wallets costs nothing beyond gas. The fee applies to pool trades only, which means consolidating a position or moving to a hardware wallet does not leak value.

3. Claim your accrual

Your accrual grows continuously with your share of supply. The claim button unlocks when the 300-second cooldown since your last claim has elapsed; on a first visit it is already open.

  1. Watch the ring around the accrual figure fill as the window closes.
  2. Press Claim. The button reports the signing and settlement phases in sequence.
  3. A row appears in Your claim history and the cooldown resets to 5:00.

The cooldown is stored per address in localStorage, so a page reload does not hand you a free claim. Clearing site data resets it, which is fine in a simulation and impossible against a real distributor.

Verifying what happened

Nothing in the simulated flow reaches a chain, so the explorer stays empty on purpose. Once the protocol is deployed, the same three feeds will show your claim, the fee payments that funded it, and the batch that bought the shares. Cross-check a claim like this:

verify a claim
# the claim itself
curl -s https://api.bankhood.xyz/v1/claims/0xYourAddress | jq '.[0]'

# the distribution batch that funded it
curl -s https://api.bankhood.xyz/v1/distributions?limit=1 | jq '.[0]'

# reserve totals, which should move by the same share count
curl -s https://api.bankhood.xyz/v1/reserve | jq '.hoodShares'

Field definitions for each endpoint are in integrations and API.

Running the interface locally

The site is a single Next.js application with no backend. Every figure it displays comes from a typed module under lib/mock/, so it runs offline apart from the HOOD chart embed.

local development
npm install
npm run dev

# optional: enable the WalletConnect connector
echo "NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=your_project_id" >> .env.local

Swapping a mock for real data is a one-line change per module because each mock exports the same shape as the endpoint that will replace it. The mapping is listed in the project README.

15 pages match