New Book: The Bitcoin Economy , Read free online or get your own copy. Read Now Buy on Amazon
Public AttestoBind demo

Verify an identity binding without exposing secrets.

Choose an identity adapter and inspect the normalized state, deterministic SHA3-512 digest, and Proofnet BTC post-quantum binding claim. Every adapter is presented here as a Phase 4 / network-scale path, with KERI as one selectable adapter rather than a permanent dependency.

Private Identity Review Engineer Docs Build List 3-min Script ↓
Scheme
Dependency
License
Subject
State digest
Binding digest
Verification output
Loading KERI verification fixture...
Phase 4 deep path

Real KERI evidence is represented.

The private room carries the full KERI review packet. The public page keeps the claim visible without exposing operational details beyond safe fixture evidence, while the adapter spread below shows every path as Phase 4 / network-scale.

OOBIresolved
KEL eventsicp -> rot
Final sequence1
KERIpydeps/keripy, Apache-2.0
Phase 4 spread

Network-scale adapter paths, all under one Proofnet binding contract.

Each adapter below is framed as a Phase 4 path: proof layer, workflow layer, enterprise deployment, and cross-organization scale. The public demo stays static and safe while still showing the full adapter surface.

Phase 4

Proofnet Native

Core node identity with native Proofnet record handling.

Network scalecorememory blocks

Memory Block replication, Toshi PQ1 policy, optional Bitcoin anchor.

Phase 4

KERI / KERIpy

Identity replay with OOBI, KEL, and rotation evidence.

Network scaledeps/keripyApache-2.0

OOBI resolution, KEL replay, witnesses, recovery, and KERIA agent boundaries.

Phase 4

DID / DIDKit

Portable DID resolution and verification state.

Network scaledeps/didkitApache-2.0

DID documents, presentation state, revocation checks, and federation policy.

Phase 4

SPIFFE / SPIRE

Workload and service identity for federated systems.

Network scaledeps/spireApache-2.0

SPIFFE IDs, SVID state, trust-domain policy, and service mesh verification.

Phase 4

Sigstore / Rekor

Supply-chain provenance with transparency-log evidence.

Network scaledeps/sigstore-pythonApache-2.0

Artifact digest, inclusion proof, release policy, and cross-org software verification.

Phase 4

C2PA

Content provenance for media, assets, and assertions.

Network scaledeps/c2pa-rsApache-2.0 OR MIT

Manifest digest, signer identity, asset lineage, and chain-of-custody replay.

Phase 4

OpenID4VC

Issuer, holder, and verifier credential exchange.

Network scaledeps/openid4vcApache-2.0

Credential offers, presentation proofs, status checks, and enterprise trust policy.

Phase 4

X.509

Enterprise PKI and device identity bindings.

Network scaledeps/cryptographyApache-2.0 OR BSD-3-Clause

Certificate chains, subject and issuer state, revocation checks, and mTLS policy.

Phase 4 execution

Every adapter now shows what gets verified and what gets bound at each track.

These are public-safe sample artifacts and statuses only. They describe the concrete Proofnet BTC execution path without exposing secrets, runtime credentials, or external service calls.

1

Adapter proof layer

Normalize the upstream identity state, digest it with SHA3-512, and bind the verified result with ML-DSA-87.

2

Workflow layer

Show the operational flow for the adapter: selection, replay, issue, receive, present, revoke, or rotate as relevant.

3

Enterprise deployment

Carry policy, audit, access, and operator boundary details without leaking credentials or private keys.

4

Network scale

Preserve replayable Memory Blocks, optional Bitcoin anchoring, and partner or federation scale paths.

Why this matters

The upstream identity layer can change. The Proofnet record stays replayable.

01

Live identity

KERI, DID, X.509, SPIFFE, Sigstore, C2PA, OpenID4VC, or native Proofnet state answers who the subject claims to be now.

02

Accepted state

Proofnet records the exact verified state accepted at binding time.

03

PQ binding

The canonical record is digested with SHA3-512 and bound with ML-DSA-87.

04

Durable proof

Memory Blocks preserve the accepted proof packet even if the upstream service later rotates, expires, or disappears.