HeartBadge works when everything else fails.

No signal? No problem. We built a badge that verifies itself, carries its own proof, and works everywhere — even offline.

The problem.

We run live events. We've watched thousands of people scan in, collect, go on quests, care about each other, and bond with strangers over three days in a field. We've also watched what the industry breaks on: 50,000 people at a festival, 5,000 people at a subway station, venues with unreliable Wi-Fi, remote areas with no signal. The moment there's congestion or no connectivity, access systems fail. You're locked out when you need to be let in.

Most systems rely on asking a server: "Is this person allowed?" That round trip to the internet is your vulnerability. The server has to be fast, always reachable, and able to handle peak load. It rarely is.

The insight.

What if the badge didn't ask? What if it proved?

Instead of "Am I allowed?" the badge would say "I am allowed, and here's the proof." The proof would be cryptographic, self-contained, and verifiable offline. No API latency. No network dependency. No loading screens. Just scan → verify → go.

This is how Bitcoin works. It's why a payment can be verified without calling your bank. We took that principle — Simplified Payment Verification, SPV — and built it into the badge. Every scan carries everything needed to verify it. The proof is in the payload.

What we built.

A self-verifying badge. Not a ticket (tickets get scanned and thrown away). Not a loyalty card (loyalty cards are about the next transaction). Not an NFT profile picture (those are performance, not memory).

A badge is something you carry forward. When you scan it at an event, you're not checking in — you're leaving a cryptographically signed mark that you were there. That mark travels with the badge and can be verified by anyone, anywhere, without calling a server. Your proof is portable. Your access doesn't depend on connectivity. Your identity is yours.

The technical foundation.

The badge lives on-chain as a CAT-721 token under a covenant contract. The chain isn't a ledger. It's a medium — the way light travels. It ensures your badge is verifiable six months later, from São Paulo, by someone who wasn't there. The proof outlasts the event.

When you scan:

• Your badge sends a BEEF payload (self-proving data)
• The reader verifies a Merkle proof of your current state
• Access is granted, all offline
• Sub-500ms verification. No API calls.

This works at festival gates, transit turnstiles, and packed venues — places where the internet fails but the system still needs to work.

Where you are right now.

You're in the documentation. If you run events, there's a path for you under Programs. If you build software, there's a path for you under Developers. If you're a member, most of what you need is one click away under Members.

The system you're learning about solves for a specific failure mode: every system that requires internet to verify identity. We built something that doesn't.

— HeartChain Labs