Everything about HoodPay

1. Connect a wallet. HoodPay reads the Robinhood Chain token balances of the connected wallet and shows only tokens you actually hold.
2. Pick a token, amount and X handle. Add an optional note it shows up on the gift card and the claim page.
3. Sign one transfer. The tokens move from your wallet into the HoodPay escrow contract. Nothing else is signed.
4. The recipient verifies X. They sign in with X; HoodPay checks the handle matches the one on the gift exactly.
5. They add a Robinhood Chain wallet. Escrow releases the exact gift amount to that address on-chain and the gift is marked claimed.

Sending requires a connected Robinhood Chain wallet (any Robinhood Chain compatible wallet works). Token selection is intentionally gated behind connection, HoodPay does not present a catalog of tokens to buy, only what is already in your balance.

You need a small amount of the Robinhood Chain network token for fees, and the escrow may need a one-time token account for a token it has never held before. Both are ordinary Robinhood Chain costs, not HoodPay charges.

After signing you get a claim link. Share it with the recipient or just tag them, the gift is discoverable from the Activity feed by handle either way.

Anyone can open a claim link, but only the X account named on the gift can claim it. Verification uses X OAuth 2.0 with PKCE and requests the minimum scope needed to read your username, HoodPay cannot post, follow, read DMs or see your email.

If you sign in with the wrong account, the claim page says so and offers to re-verify as the correct handle. Once verified, paste or connect a Robinhood Chain wallet address; the release transaction is submitted by the escrow and the resulting transaction ID is shown so you can confirm it on a Robinhood Chain explorer.

Claims are idempotent: repeated attempts on the same gift cannot release funds twice, and a gift can only ever be in one of held, claimed or refunded states.

Between sending and claiming, tokens live in the HoodPay escrow contract on Robinhood Chain. The escrow authority lives only on the server; it is never exposed to the browser, and every release is authorized by a server function after handle verification succeeds.

Every deposit and release is an ordinary on-chain transfer, so the escrow contract's full history is publicly auditable. Balances, held vs. released totals and current holdings are summarized on the escrow transparency view.

Gifts are not refundable. Once you send, the tokens are locked in escrow for that handle and stay held indefinitely until the recipient verifies and claims them. Double-check the handle before sending.

Token metadata, name, symbol, logo, decimals and price, is pulled live from Robinhood Chain and cached server-side so pages stay fast. If a token has no logo published upstream, HoodPay falls back to a generated ticker mark.

Trending on HoodPay is native: rankings are driven by how many gifts a token has received on HoodPay, not by market cap or volume elsewhere. The same is true for the leaderboards, top tokens, top gifters and most-gifted accounts all come from HoodPay activity.

Claiming is free. HoodPay never charges fees.

• No platform fee on sending, no platform fee on claiming, ever.
• Recipients pay nothing to claim, the escrow contract covers the release transaction.
• Senders only pay the standard Robinhood Chain network fee for their own transfer.
• Gifts are limited to what your wallet actually holds, there is no credit, lending or leverage.

• HoodPay never asks for your seed phrase or private key.
• The only thing you sign is a token transfer to the escrow contract address.
• Gift and handle records are not publicly readable from the database; all reads go through server functions.
• X sessions are signed server-side and scoped to reading your username only.
• Wallets may warn on shared preview domains. Use the published HoodPay domain for transactions and always confirm the escrow contract address before signing.