Protocol

BCID overview

Soulbound identity with dynamic reputation — complements ENS, EAS, and ERC-8004.

BCID — Building Culture Identity

One-page overview · v1 draft · Lite paper · RFC


What is BCID?

Building Culture Identity (BCID) is a soulbound, portable identity standard for builders, DAOs, and agents. It complements ENS (names), EAS (attestations), World ID (human proof), and ERC-8004 (agent registry) — it does not replace them.

DID format: did:bcid:human:{id} · did:bcid:company:{id} · did:bcid:asset:{id} · did:bcid:agent:{id}

Live today: app.buildingcultureid.space/bcid · bridge from .culture · grant verifier at /grant-proof


Problem

PainWho feels it
Credentials are not portable across platformsBuilders, freelancers
Wallet address ≠ human-readable trust signalAll Web3 users
Sybil attacks undermine grants and DAO programsProtocol operators
No standard for accountable AI agent identityAgent developers
Reputation rewards followers, not shipped workBuilders

Solution — dynamic soulbound identity

The identity anchor is non-transferable (soulbound). Reputation and credentials evolve — Builder, Trust, Contribution, and Verification scores update as you ship; credentials can be issued or revoked.

LayerBCID approach
IdentitySoulbound ERC-721 in BcidRegistry on Base
CredentialsSoulbound catalog + optional EAS attestations on Base
ReputationFour verifiable scores (off-chain compute, on-chain anchors)
Recovery2-of-3 guardian timelock (72h delay)
PrivacyEncrypted credential storage; ZK selective disclosure (roadmap)
Interop.culture bridge, ENS link, Farcaster FID, World ID, ERC-8004 agent card

Four BCID types

TypeNamespacePrimary use
Humandid:bcid:human:*Individual identity, credentials, reputation
Companydid:bcid:company:*Org identity, delegated admins
Assetdid:bcid:asset:*Tokenized property, certs, RWAs
Agentdid:bcid:agent:*AI agent wallet, reputation, revenue split

Why not ENS / Farcaster / EAS alone?

  • ENS — great namespace, transferable, no native reputation or credentials
  • Farcaster — social graph, not portable credential wallet
  • EAS — schema-agnostic attestations, no identity namespace or dynamic scores
  • World ID — human uniqueness, not builder reputation
  • BCID — soulbound DID + dynamic scores + credential catalog + agent-native ownership

See competitor analysis for the full matrix.


Integrate BCID (DAOs & protocols)

Free pilot package for 3–5 DAOs:

  1. BCID mint for core contributors (or bridge from .culture)
  2. Credential types: dao-member, grant-applicant, bcid-builder
  3. Public leaderboard at /bcid/leaderboard
  4. Feedback shapes RFC v1.1 via /voice

APIs: GET /api/bcid/resolve · POST /api/bcid/bridge/culture · GET /api/bcid/catalog · GET /api/bcid/scores

Partnership brief: DAO_PARTNERSHIP_BRIEF.md

Contact: hello@buildingcultureid.space · Grant proof


Roadmap (v1)

PhaseDeliverable
NowHuman BCID mint, .culture bridge, 6+ credential types, leaderboard
Month 1–2BCID Spec RFC public comment; EAS schema pack on Base Sepolia
Month 2–3100 Human BCIDs on Base mainnet; 3 DAO pilots
Month 4+Company/Asset BCID; ZK selective disclosure; W3C DID method doc

Standards path

BCID does not claim to be the global standard on day one. Path: public spec → RFC feedback → pilot DAOs → EAS schema registry → ecosystem co-publication.

We cite and interoperate with EAS, ENS, World ID, and ERC-8004 in all external materials.

Give feedback: /voice · GitHub Discussions · RFC comment deadline in BCID_SPEC_RFC.md