Introduction

Boon

Boon is onchain USDC gratitude for useful work. A sender tips a GitHub or X handle, the contract either pushes the USDC to an already linked wallet or escrows it by handle, and the recipient later proves account ownership to claim.

The default surface is human-first:

• Senders use /send for a normal one-time wallet checkout.
• Recipients use /claim to prove GitHub or X ownership and choose a receiving wallet.
• Agent operators use the Boon CLI with a small funded OWS wallet when an agent should propose and execute approved thank-yous.
• API consumers use free aggregate endpoints by default and x402-paid endpoints only for detailed graph reads.

The 5-minute mental model

1. A handle is canonicalized as github:alice or x:bob.
2. The sender approves exactly the USDC amount and calls Boon.tip(handleHash, displayHandle, amount, note).
3. If the handle is already linked, USDC is pushed to the linked wallet.
4. If the handle is cold, USDC is escrowed against the handle hash.
5. The recipient signs in with GitHub or X, links a wallet, and claims the escrow.
6. Future boons to that handle push automatically.

What stays free

Sending, viewing aggregate Boon Points, viewing a specific receipt, linking, and claiming are free product surfaces. Boon does not put recipient claim-help or viewing escrow behind x402.

Detailed who-paid-who graph reads are the paid API surface. See x402 paid endpoints.

Current live anchors

Surface	URL / address
App	boonprotocol.com
API	api.boonprotocol.com
Base contract	0xfb6662AdaF0611a94322634d5B86203Cfb59d5e8
Base USDC	0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Repository	github.com/velinussage/boon

Boon is live on Base mainnet but still unaudited. Use small amounts until the public end-to-end send/claim smoke and audit posture are stronger.

Next steps

• New sender: send a tip
• Recipient: claim a boon
• Agent operator: tip from an agent
• Integrator: API overview