Gohealthme

• 

  Landing page

• 

  Bountry Pools page

• 

  Create a bounty pool page

• 

  Spotter (AI Agent) Page

• 

  User Dashboard Page

Insurers, employers, even your friends already pay people to be healthy. They do it through opaque points, gift cards that arrive weeks later, and bets settled on trust. GoHealthMe puts that on-chain and makes it private. Anyone funds an initiative: a sponsor puts USDC behind flu shots, or your friend bets you can't add 50 pounds to your bench in a month. You get paid the moment you prove you did it. No claim forms. No waiting. Nobody deciding whether you "really" earned it.

The catch nobody solves: a health reward is a tiny, frequent payment, but if it settles to your public wallet, anyone watching the chain can link "this address" to "hit a goal in the addiction-recovery pool." That is a medical disclosure. GoHealthMe closes that leak. Your document is judged inside a confidential hardware enclave and never touches the chain. Only a signed pass/fail verdict does.

Inspiration

Two months ago our own settlement was a human remembering to run a shell script. That is not a product. The real problem underneath was worse: the person who does the healthy thing is not the one who saves the money, and every "get paid to be healthy" scheme either pays weeks late or quietly leaks your health status on a public ledger. We wanted both fixed, instant and private, with the entire money loop handed to an agent so no human is in it.

What it does

Sponsors (or friends) fund USDC pools for verified health goals. You sign in with an email, no seed phrase and no app to install, join a pool, and upload your proof. From there an autonomous agent named SPOTTER runs the whole economy. It buys the verification it needs per claim with x402 nanopayments from its own budget, judges the evidence, decides pay-or-no-pay with Gemini, and settles the payout from its own Circle wallet on Arc. No human approves anything, and one wallet, one entry is enforced on-chain. Your raw health data never leaves the enclave. Only the verdict does.

How we built it

• Contracts (Solidity, Foundry) on Arc testnet hold the pooled USDC and gate payout on a verified verdict.
• SPOTTER is a Circle developer-controlled wallet acting as a real economic actor. It purchases verification over x402, reasons with Gemini 2.5 Flash on Vertex AI, and calls settle() itself.
• Verification runs in a confidential AI attester we built ourselves: Ollama serving Gemma inside an AMD SEV-SNP hardware enclave on a GCP Confidential VM. When the hosted attester we designed against went down, we stood up our own in a day.
• The part we are proudest of: every verdict is signed by a key that lives inside the enclave, and an AMD hardware attestation proves it. The app pins our code's measurement and refuses to pay on any verdict it cannot prove came from that exact measured enclave. It is an unbroken cryptographic chain from AMD silicon to the settlement contract, with zero trust in us.

Challenges we ran into

• A green transaction is not money. Our worst bug was pools that settled successfully and paid nobody. We now assert on the on-chain USDC balance delta, never on transaction success.
• The attester went dark. The confidential-AI service we planned to use returned 503 between events. We rebuilt it on real SEV-SNP hardware instead of faking it.
• Ephemeral keys break trust silently. The enclave's signing key was reborn on every restart, which would quietly break verification for real users. We sealed it to the hardware with a firmware-derived, measurement-bound key that survives restarts, and added measurement-anchored auto-repin so a key rotation recovers with no operator. Real users is the standard, not "demo."
• Privacy is a boundary, not a slogan. We were ruthless about what crosses the enclave wall. Raw bytes never leave, only a verdict, and every claim is scoped so no on-chain data links back to a health status.

Built With

• claude