bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 14쪽 중 1쪽
# 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.
***
## What is S.I.G.N.?
S.I.G.N. is a layered stack that unifies:
* **execution**: money movement and program logic
* **identity**: credentials and verification
* **evidence**: cryptographic records of what happened, when, and under which authority
Sovereign deployments must satisfy constraints that typical consumer systems do not:
* privacy by default for sensitive payloads
* lawful auditability and inspection readiness
* strict operational control (keys, upgrades, emergency actions)
* interoperability across agencies, vendors, and networks
* performance and availability under national concurrency
S.I.G.N. is designed so that policy and oversight remain under sovereign governance while the technical substrate stays verifiable.
Start here:
* [S.I.G.N. Overview](/s.i.g.n./sign)
* [Reference Architecture](/s.i.g.n./reference-architecture)
* [Security & Privacy](/s.i.g.n./security-privacy)
* [Governance & Operations](/s.i.g.n./governance-ops)
***
## The three systems
### New Money System
A sovereign digital money rail supporting CBDC and regulated stablecoins across public and private rails.
Common requirements:
* real-time settlement and deterministic finality targets
* policy controls (limits, approvals, emergency controls)
* supervisory visibility and reporting
* optional confidentiality for retail flows
* interoperability across rails and networks
Read: [New Money System](/national-systems/new-money-system)
### New ID System
A national identity and credential layer supporting reusable verification without central "query my identity" APIs.
Common requirements:
* W3C Verifiable Credentials (VC) and Decentralized Identifiers (DID)
* selective disclosure and privacy-preserving proofs
* trust registry and issuer accreditation
* revocation and status checks
* offline presentation patterns where required (QR, NFC)
Read: [New ID System](/national-systems/new-id-system)
### New Capital System
A programmatic capital and distribution layer for benefits, grants, incentives, and compliant capital programs.
Common requirements:
* identity-linked targeting and duplicate prevention
* schedule-based distributions (one-time, recurring, vesting)
* deterministic reconciliation and budget traceability
* evidence manifests for audits and disputes
Read: [New Capital System](/national-systems/new-capital-system)
***
## The evidence layer
All three systems rely on a shared trust and evidence layer to answer questions like:
* who approved what
* under which authority
* when the action occurred
* what ruleset version applied
* what evidence supports eligibility and compliance
* what settlement references prove execution
In the Sign ecosystem, this evidence layer is implemented by **Sign Protocol** using two primitives:
* **Schemas**: templates defining how structured data is represented
* **Attestations**: signed, verifiable records conforming to schemas
Sign Protocol supports multiple data placement models:
* fully on-chain attestations
* fully off-chain payloads with verifiable anchors (for large or sensitive data)
* hybrid models combining on-chain references and off-chain payloads
* privacy-enhanced modes including private and ZK attestations where applicable
SignScan provides unified querying across supported chains and storage:
* REST and GraphQL APIs
* SDK-based access patterns
* explorer and dataset visibility for non-programmers
Product overview: [Sign Protocol](/products-sign-ecosystem/sign-protocol)\
Developer entrypoint: [Getting Started](/for-builders/getting-started)
***
## Sign products and how they relate to S.I.G.N.
S.I.G.N. is the sovereign system architecture. Sign products are deployable offerings that can be used independently and are often combined in sovereign and regulated deployments.
* **Sign Protocol**: schemas, attestations, privacy modes, indexing and querying
* **TokenTable**: allocation, vesting, and large-scale distribution for capital programs
* **EthSign**: agreement and signature workflows producing verifiable proof of execution
These products share core primitives, but they are not defined as "subsystems of S.I.G.N.". They are components that can support S.I.G.N. deployments when the program requires their specific capabilities.
Products overview: [Products Overview](/products-sign-ecosystem/products)
***
## Technical snapshot (standards and interfaces)
This is a reference snapshot of standards commonly used in S.I.G.N. deployments.
Identity:
* W3C Verifiable Credentials (VC) and W3C DIDs
* issuance via OpenID for Verifiable Credential Issuance (OIDC4VCI)
* presentation via OpenID for Verifiable Presentations (OIDC4VP)
* revocation via W3C Bitstring Status List
* offline presentation patterns (QR, NFC) where required
* compatibility targets for mobile drivers license patterns (ISO/IEC 18013-5/7) when relevant
Evidence:
* schema-driven structured data models
* cryptographic signatures (ECDSA, EdDSA, RSA depending on deployment)
* privacy-preserving proofs (selective disclosure, ZK systems where applicable)
* indexing and query layers for operational reporting and audits
Money rails (deployment-dependent):
* public mode via L1 smart contracts or sovereign L2 deployments
* private mode via permissioned CBDC rails for confidentiality-first requirements
* controlled interoperability via bridging or messaging gateways
***
## Deployment modes (public, private, hybrid)
S.I.G.N. is designed for deployment realities, not ideology.
Public mode:
* optimized for transparency-first programs, public verification, and broad accessibility
* governance is expressed via chain parameters (L2) or contract governance (L1)
Private mode:
* optimized for confidentiality-first programs and regulated domestic payment flows
* governance is enforced through permissioning, membership controls, and audit access policy
Hybrid mode:
* combines public verification and private execution where required
* interoperability must be treated as critical infrastructure with explicit trust assumptions
***
## How to read these docs
### If you are exploring S.I.G.N. (systems, architecture, governance)
Start with:
* [S.I.G.N. Overview](/s.i.g.n./sign)
* [Reference Architecture](/s.i.g.n./reference-architecture)
* [Security & Privacy](/s.i.g.n./security-privacy)
* [Governance & Operations](/s.i.g.n./governance-ops)
Then:
* [New Money System](/national-systems/new-money-system)
* [New ID System](/national-systems/new-id-system)
* [New Capital System](/national-systems/new-capital-system)
### If you are building (developers, integrators)
Start with:
* [Getting Started](/for-builders/getting-started)
Then go deeper:
* writing data: [Writing Data](/for-builders/index-1)
* querying data: [Querying Data](/for-builders/index)
* advanced topics: [Advanced Topics](/for-builders/advanced-topics)
* supported networks: [Supported Networks](/for-builders/address-book)
### If you are evaluating products
Start with:
* [Products Overview](/products-sign-ecosystem/products)
***
## Tenets that guide S.I.G.N. (and Sign)
### Keep it simple, Signer.
Sovereign systems are already complex (policy, compliance, privacy, interoperability). Infrastructure should reduce complexity, not add it. The goal is to make verifiable systems intuitive to integrate and difficult to misuse.
### Improvise. Adapt. Excel.
The path to real infrastructure is never linear. Deployments evolve with policy, adoption, interoperability constraints, and emerging threats while remaining governable and auditable.
### An open stack
Verification is most valuable when it is portable. S.I.G.N. embraces open standards and interoperable primitives so systems can evolve without locking policy into one vendor or one network.
### Evidence maketh governance
Identity primitives establish representation. Evidence establishes history. Attestations are the bedrock of accountability: who approved what, under which authority, when, and according to which rules.
***
## Where to go next
* Start with S.I.G.N.: [S.I.G.N. Overview](/s.i.g.n./sign)
* Explore national systems:
* [New Money System](/national-systems/new-money-system)
* [New ID System](/national-systems/new-id-system)
* [New Capital System](/national-systems/new-capital-system)
* Build with Sign Protocol:
* [Getting Started](/for-builders/getting-started)
* Evaluate products:
* [Products Overview](/products-sign-ecosystem/products)
# FAQ
This FAQ answers common questions about S.I.G.N. and the Sign ecosystem, with an emphasis on how the system is structured and how to use it correctly. It is not a replacement for the architecture and security documentation.
If you are new to the ecosystem, start with:
* [S.I.G.N. Overview](/s.i.g.n./sign)
* [Reference Architecture](/s.i.g.n./reference-architecture)
* [Security & Privacy](/s.i.g.n./security-privacy)
* [Governance & Operations](/s.i.g.n./governance-ops)
***
## S.I.G.N.
<details>
<summary>What is S.I.G.N.?</summary>
S.I.G.N. is a sovereign digital infrastructure framework for deploying national-scale systems for money, identity, and capital. It focuses on enforceable policy controls, controllable privacy, and inspection-ready evidence so institutions can operate systems that hold up under oversight, disputes, and audits.
See [S.I.G.N. Overview](/s.i.g.n./sign) for the full narrative and design goals.
</details>
<details>
<summary>What are the three national systems in S.I.G.N.?</summary>
S.I.G.N. organizes national digital infrastructure into three system domains:
* New Money System: policy-controlled digital money rails for CBDC and regulated stablecoins
* New ID System: verifiable identity and credential issuance and verification across agencies and regulated operators
* New Capital System: regulated real-world asset and programmable capital infrastructure for issuance, distribution, and reporting
These are described in detail under:
* [New Money System](/national-systems/new-money-system)
* [New ID System](/national-systems/new-id-system)
* [New Capital System](/national-systems/new-capital-system)
</details>
<details>
<summary>Is S.I.G.N. a blockchain, a single ledger, or a vendor platform?</summary>
No. S.I.G.N. is a system architecture and operating model that can use one or more ledger and data availability options, depending on sovereignty, privacy, performance, and compliance requirements.
The goal is to avoid coupling national policy and oversight to a single vendor or ledger design. See [Reference Architecture](/s.i.g.n./reference-architecture) for the layering model and trust boundaries.
</details>
<details>
<summary>How do Sign Protocol, TokenTable, and EthSign fit under S.I.G.N.?</summary>
S.I.G.N. is the top-level narrative and architecture. The products are implementation components that align to parts of the stack:
* Sign Protocol provides the evidence and attestation layer used for verification, authorization proofs, and audit trails.
* TokenTable provides capital allocation and distribution primitives, typically for regulated issuance and program distribution workflows.
* EthSign provides agreement and signature workflows that can integrate with identity and evidence primitives.
See [Products](/products-sign-ecosystem/products) for the product map and intended use.
</details>
***
## Sign Protocol
<details>
<summary>What is Sign Protocol?</summary>
Sign Protocol is an evidence and attestation layer for producing and verifying structured claims. A claim can represent a statement, an authorization, an eligibility result, an approval, a verification outcome, or other system-relevant facts that must be inspectable later.
The core idea is to make verification reusable across applications by standardizing how claims are structured, signed, stored, queried, and referenced.
See [Sign Protocol](/products-sign-ecosystem/sign-protocol).
</details>
<details>
<summary>Is Sign Protocol a blockchain?</summary>
No. Sign Protocol is not itself a base ledger. It can use underlying chains and storage layers for anchoring, settlement, and tamper-evidence, but it is best understood as a protocol layer that defines how attestations and related proofs are produced and verified.
This separation supports interoperability and reduces coupling between application workflows and any single ledger environment.
</details>
<details>
<summary>What is an attestation?</summary>
An attestation is a signed, structured statement about a subject, typically bound to a schema that defines its fields and semantics. An attestation is meaningful only relative to its verification context, including who signed it, what authority they had, what schema it conforms to, and how revocation and updates are handled.
For precise definitions, see:
* [Glossary: Attestations](/reference/index/attestations)
</details>
<details>
<summary>What is the difference between an attestation and "evidence"?</summary>
An attestation is the signed statement. Evidence is the supporting material that makes the statement credible and inspectable, such as references to documents, cryptographic proofs, verification transcripts, or audit artifacts.
A well-designed system treats evidence as a first-class input to verification and dispute resolution. Evidence handling is closely tied to privacy and access control. See [Security & Privacy](/s.i.g.n./security-privacy).
</details>
<details>
<summary>What is a schema?</summary>
A schema defines the structure and semantics of an attestation. It specifies what fields exist, how they are encoded, and how verifiers should interpret them.
Schemas are critical for interoperability because they make attestations machine-verifiable and comparable across applications and organizations.
See:
* [Glossary: Schema](/reference/index/schema)
</details>
<details>
<summary>What is the Schema Registry?</summary>
The Schema Registry is the system for registering and discovering schemas used by Sign Protocol. It enables reuse, consistent interpretation, and ecosystem interoperability, while providing a stable reference for verifiers.
See:
* [Glossary: Schema Registry](/reference/index/schema-registry)
</details>
<details>
<summary>Where does attestation data live, on-chain or off-chain?</summary>
Both patterns are supported, and the correct choice depends on privacy, cost, latency, and audit requirements.
Common approaches include:
* On-chain anchoring for integrity and global verifiability
* Off-chain storage for sensitive or large payloads, with cryptographic binding to an on-chain commitment or identifier
See [Reference Architecture](/s.i.g.n./reference-architecture) and the developer documentation sections on writing and querying data.
</details>
<details>
<summary>How do I verify an attestation?</summary>
Verification typically includes:
* Schema verification: confirm the attestation conforms to the referenced schema
* Signature verification: confirm the signer and the signing domain
* Authority verification: confirm the signer was authorized to issue that type of statement in the relevant governance model
* Status verification: confirm revocation, expiration, supersession, or dispute status
* Evidence verification: confirm referenced proofs or artifacts meet the verifier's acceptance policy
For implementation, see:
* [Querying Data](/for-builders/index)
* [Writing Data](/for-builders/index-1)
</details>
<details>
<summary>Can attestations be edited or deleted?</summary>
In general, you should treat attestations as append-only records. Instead of mutating history, systems typically:
* Revoke attestations
* Issue a superseding attestation
* Attach dispute or correction attestations under defined rules
The correct approach depends on your governance and audit requirements. For operational guidance, see [Governance & Operations](/s.i.g.n./governance-ops).
</details>
<details>
<summary>What networks and runtimes are supported?</summary>
Network support evolves over time and depends on deployment and operational requirements.
For the authoritative list, see:
* [Supported Networks](/for-builders/address-book)
</details>
<details>
<summary>How is Sign Protocol different from EAS?</summary>
EAS is commonly used in EVM environments and is tightly shaped by the EVM execution and data model.
Sign Protocol is designed as an attestation and evidence layer that can be deployed across multiple environments and can support different storage, privacy, and verification models. The practical differences typically show up in interoperability, data-location strategies, and how the protocol integrates with non-EVM systems.
If you are ch프로젝트로 돌아가기