Claim a boon
Section titled “Claim a boon”Use /claim if someone sent a boon to your GitHub or X handle.
- Open boonprotocol.com/claim.
- Sign in with the provider for the tipped handle.
- Review the proven handle and pending amount.
- Connect the wallet that should receive this and future boons.
- Confirm that the v1 handle-to-wallet link is permanent for normal self-serve use.
- Let the relayer submit link/claim if it is enabled.
Wallet choices
Section titled “Wallet choices”- Coinbase: passkey/no-seed path for new wallet users.
- Metamask/injected: use an existing browser wallet.
- WalletConnect: use mobile wallets, Safe, Ledger Live, and other compatible wallets.
What the link means
Section titled “What the link means”After your handle is linked:
- current escrow can be claimed to the linked wallet
- future boons to the same handle push directly to that wallet
- already-pushed funds cannot be moved by Boon
Manual fallback
Section titled “Manual fallback”If the hosted relayer is not enabled, the public UI should fail closed. Do not trust a flow that claims success without a transaction or receipt.
For help, send the receipt or handle to the sender, or open an issue in github.com/velinussage/boon.
Recipient FAQ
Section titled “Recipient FAQ”The repo ships a dedicated recipient FAQ that covers the questions claimers
most often have — custodial posture, lost passkeys, gas, changing wallets
(relink()), the privacy of tip notes, what happens if you never claim,
and pre-claim verification. See
HOW_TO_CLAIM.md
for the full answers and the contract address you can verify on BaseScan
before connecting a wallet.
If a hosted claim does not match what the FAQ describes (for example a UI that claims success without showing a tx hash), stop and ask the sender or operator rather than retrying.