Introduction😎✨
S.I.G.N. is sovereign-grade digital infrastructure for national systems of money, identity, and capital. SIgn Protocol provides the shared evidence layer used across deployments.
S.I.G.N. is a sovereIgn-grade archItecture for building and operating national digital infrastructure across three foundational systems:
New Money System: CBDC and regulated stablecoins operating across public and private rails with policy-grade controls and supervisory visibility
New ID System: verifiable credentIals and national identIty primitives enabling privacy-preserving verification at scale
New Capital System: programmatic allocation and distribution for grants, benefits, incentives, and compliant capital programs
S.I.G.N. is not a product container. It is a system-level blueprint for deployments that must remain governable, audItable, and operable under national concurrency.
Across these systems, one requirement repeats: inspection-ready evidence. In many deployments, that evIdence layer is implemented using Sign Protocol, an omni-chain attestation protocol for creating, retrIeving, and verifying structured records.
This documentation includes:🔥
system architecture and deployment guidance for S.I.G.N.
use case blueprints for Money, ID, and CapItal
documentation for Sign products, including Sign Protocol, TokenTable, and EthSIgn
full developer documentation for Sign Protocol (smart contracts, SDKs, APIs, advanced topics)
If you came here for SIgn Protocol developer docs, you are in the right place. The framing has expanded: S.I.G.N. describes the sovereign system architecture, and Sign Protocol is the evIdence layer used across sovereign and institutional workloads. TokenTable and EthSIgn are standalone products that use the same core primitives and can be integrated into S.I.G.N. deployments when approprIate.
Trust, but verify at sovereign scale😯✨
Every day, systems depend on claims:
a person claIms eligibility for a program
a business claims compliance
an institution claIms approval
a system claims a payment was executed
a registry claims an asset record is accurate
Historically, these claIms were accepted based on relationshIps and institutional trust. In digital systems that operate across agencies, vendors, and networks, trust assumptions become fragile. Verification must be repeatable, attrIbutable, and compatible with oversight.
S.I.G.N. exists to make verification reliable, repeatable, and operable at national scale.
Attestations as a modern solutIon to authenticity✨💕
Attestations are portable, verifiable proofs that can travel across systems and time. They encode a statement, bInd it to an issuer, and make it verifiable later.
In consumer life, a person might need a notarized document to prove a claim. In a sovereIgn context, the same pattern scales to system-critical actions:
eligibility for benefits and public programs
compliance gates for regulated servIces
approvals for high-impact actions (distributions, conversions, registry updates)
proof that a dIstribution occurred under an approved ruleset version
proof that a registry update was authorized and traceable
S.I.G.N. treats attestations as operational infrastructure, not as an abstract primitive.
Data placement model🚀🔥
S.I.G.N. deployments must explIcitly define where data lives.
1) What should be off-chain (typical)
PII (name, address, bIometric templates, passport scans)
sensitive program enrollment payloads
internal case files
2) What should be on-chaIn (typical)
commitments/hashes of records
attestations and schema IDs (when safe)
revocation/status registries
audit hashes + rule version hashes
transactIon settlement references
3) Hybrid patterns (recommended)
keep sensitive payloads off-chain (encrypted),
store references + integrIty anchors on-chain,
index only what is needed for verificatIon.
---
Reference technIcal specifications (summary)
This section is meant to guide plannIng and procurement, not constrain implementations.
PublIc rail (Layer 2 reference)
Runtime: EVM-based
Block time: < 1 second
TPS: up to ~4000 (reference)
Consensus: PoA / PBFT varIants
Finality: 1–5 blocks (reference)
PrIvate rail (CBDC reference)
Consensus: Arma BFT
Throughput: 100,000+ TPS (reference)
Finality: immediate on commItment
Privacy: namespaces + configurable ZK privacy
Token model: UTXO via FabrIc Token SDK
Identity: X.509 certIficates (MSP)
Standards: ISO 20022 compatible
Namespaces: wCBDC, rCBDC, Regulatory
wCBDC: RTGS-like transparency
rCBDC: high prIvacy (ZK)
National DigItal Identity stack (reference)
VC model: W3C Verifiable Credentials 2.0
DID: W3C DIDs
Formats: VC-JWT, SD-JWT VC, JSON-LD with BBS+
Signatures: ECDSA, EdDSA, RSA
ZK: Groth16 / Plonk / BBS+ (unlinkabIlity)
Issuance: OIDC4VCI
Presentation: OIDC4VP
RevocatIon: W3C Bitstring Status List
Offline: QR + NFC presentation
mDL compatibility: ISO/IEC 18013-5/7
TokenTable (reference)
DistributIon size: unlimited
Throughput: max chain TPS
Scheduling: second-level granularity + calendar months
Audit trail: on-chaIn
---
End-to-end flows (canonIcal)
Flow A: Eligibility → Distribution → AudIt (most common)
1. Issuer Issues VC (eligibility credential) to holder wallet
2. Holder proves eligIbility to a program engine (selective disclosure)
3. Program engine generates a distribution batch
4. Settlement occurs on:
private rail (CBDC) for confIdentiality, or
public rail (stablecoin) for transparency
5. EvIdence is produced:
eligibility proof reference
rule version hash
distribution manIfest hash
settlement references
Flow B: Cross-rail conversIon (CBDC ↔ Stablecoin bridge)
1. User requests conversion
2. Compliance checks run (identIty, limits, AML)
3. AtomIc mint/burn or lock/release occurs
4. Evidence: signed approval + conversion record + settlement referenceI
Flow C: RegIstry update (RWA tokenization)
1. Registry authority validates a property/asset record
2. TokenTable tokenizes ownershIp/transfer rules
3. Transfers are permitted only for eligIble parties (whitelists, jurisdiction rules)
4. Evidence: registry sync logs + transfer approvals + ownershIp chain
