← Back to HomePress Esc to return home

Founder Project

The Carbon Club

Trust infrastructure for the AI-native internet.

Audience

This page is written for technical readers, product builders, and platform operators who want to understand the system boundaries, data flow, and product surfaces without exposing sensitive operational details.

Visit External Project

The Carbon Club is centered on the Last Verifiable Human Registry, a system for issuing durable Proof of Pulse credentials after liveness verification and payment. The broader product vision is to turn that registry into a practical trust layer that can support filtering, verification, and account-claim checks across platforms.

This presentation intentionally stays at a public-safe level. It describes product behavior, verification flow, registry concepts, and public trust surfaces without exposing secrets, internal admin mechanisms, private credentials, or exploitable implementation details.

Technical Notes

  • Registry-safe data only: public status, issuance timing, chain anchor references, and claimed-account concepts where appropriate.
  • Core trust flow: verification event -> credential -> human record -> chain anchor -> public registry presence.
  • Downstream products rely on deterministic status checks rather than privileged biometric access.
  • The design favors idempotent processing, public verifiability, and clear separation between public records and sensitive verification data.

Core Product: The Registry

The core product is the Last Verifiable Human Registry, where a successful liveness verification and one-time payment result in a durable Proof of Pulse credential and a public registry record.

  • Issues a Proof of Pulse credential after verification and payment.
  • Creates a public registry record with status, issuance timing, and chain-anchor-backed proof.
  • Acts as the source of truth for downstream trust products rather than a one-off verification flow.

How The System Works

At a high level, the system captures a verification event, completes checkout, issues or updates the credential through an idempotent payment flow, anchors the record, and exposes a canonical public profile.

  • User enters a username, consents, and completes liveness verification.
  • A verification event is recorded and checked for duplicates before checkout continues.
  • Payment completion triggers credential issuance, human linking, and chain anchoring.
  • The resulting public record becomes the canonical trust surface for later lookups and integrations.

Solutions Built On Top

The Carbon Club is not just a registry. It is a platform for trust-oriented products built on top of that registry state.

  • Bot Filtering: a browser-extension trust layer for X/Twitter that labels, blurs, or hides content based on registry-backed lookups and stronger claim evidence.
  • Discord Sentinel: a registry-powered server verification flow that grants or removes verified roles based on active credential and claimed-account checks.
  • Verify API: a developer-facing verification surface for registry checks, claimed identities, and downstream platform integrations.

Trust and Safety Layers

The product also includes advisory and moderation-oriented capabilities that make the registry more useful in real-world platform conditions.

  • Advisory referrer checks compare incoming context with claimed accounts to surface possible impersonation mismatches.
  • Revocation and moderation are modeled as status changes that preserve historical issuance while updating current trust state.
  • Public profiles remain visible while current credential state and revocation context determine how trust is interpreted downstream.

Credential Pipeline

The verification and issuance pipeline is designed as a durable, retry-tolerant flow rather than a fragile single-step action.

  • Verification attempts are persisted as events before credentials are issued.
  • Credential issuance only happens after successful verification and payment completion.
  • The system is designed around duplicate protection, idempotent processing, and retryable anchoring flows.

Why It Matters

The Carbon Club explores how a verified-human registry can become a practical trust substrate in digital environments shaped by bots, synthetic identities, and low-cost content generation.

  • Useful for bot filtering and platform trust decisions.
  • Relevant to community moderation, developer tooling, and identity-aware products.
  • Positioned as an infrastructure layer for products that need stronger signals than anonymous activity alone can provide.