> For the complete documentation index, see [llms.txt](https://docs.dcn.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dcn.foundation/part-x-reference/10-reference/25-appendices/architecture-diagrams.md). # Architecture Diagrams > *This appendix provides high-level reference diagrams illustrating the architecture of the Digital Crypto Note (DCN) ecosystem. These diagrams are intended to help developers, solution architects, manufacturers, governments, and enterprises understand how the various components interact within a standards-compliant implementation.* *** ## Introduction Throughout this Vision Paper, individual diagrams have been presented to explain specific topics such as: * Wallet Architecture * Publisher Platform * Payment Protocol * Certificate Infrastructure * Ownership * Merchant Acceptance * Manufacturing * Security * SDK Architecture This appendix consolidates the complete ecosystem into a set of reference architecture diagrams. These diagrams are **informative** and are intended to support implementation planning rather than prescribe a single deployment model. *** ## 1. Complete DCN Ecosystem The DCN ecosystem consists of independent participants connected through open standards. ```mermaid flowchart TB Users["Consumers"] Wallet["Companion Wallet"] DCN["Physical Digital Asset"] Merchant["Merchant"] Publisher["Publisher Platform"] Verification["Verification Service"] Foundation["DCN Foundation"] Manufacturer["Certified Manufacturer"] Blockchain["Blockchain Networks"] SDK["Developer SDKs"] Users --> Wallet Wallet --> DCN Merchant --> DCN Merchant --> Verification Publisher --> Verification Publisher --> Blockchain Wallet --> Blockchain Manufacturer --> Publisher Foundation --> Manufacturer Foundation --> SDK SDK --> Wallet SDK --> Merchant SDK --> Publisher ``` *** ## 2. Publisher Architecture Every Physical Digital Asset originates from a Publisher. ```mermaid flowchart LR Publisher Policy["Business Policies"] Issuance Certificates Lifecycle Provisioning Publisher --> Policy Publisher --> Issuance Publisher --> Certificates Publisher --> Lifecycle Publisher --> Provisioning ``` The Publisher controls issuance, lifecycle management, and business rules without controlling the underlying blockchain. *** ## 3. Wallet Architecture The Companion Wallet serves as the user's management interface. ```mermaid flowchart TB Wallet Assets Identity Payments Recovery Settings Blockchain Wallet --> Assets Wallet --> Identity Wallet --> Payments Wallet --> Recovery Wallet --> Settings Wallet --> Blockchain ``` The wallet never stores sensitive Secure Element secrets. It acts as the user interface for interacting with Physical Digital Assets and blockchain services. *** ## 4. Payment Architecture ```mermaid sequenceDiagram participant User participant DCN participant Merchant participant Verification participant Blockchain User->>Merchant: Tap DCN Merchant->>DCN: Authenticate DCN-->>Merchant: Secure Response Merchant->>Verification: Verify Verification->>Blockchain: Validate Blockchain-->>Verification: Status Verification-->>Merchant: Approved Merchant-->>User: Payment Complete ``` This sequence demonstrates the interaction between the physical asset, merchant, verification service, and blockchain. *** ## 5. Trust Architecture The DCN ecosystem establishes trust through a hierarchical certificate model. ```mermaid flowchart TB Root["DCN Root CA"] Manufacturer Publisher Device["Physical Digital Asset"] Wallet Merchant Verification Root --> Manufacturer Root --> Publisher Manufacturer --> Device Publisher --> Device Device --> Wallet Device --> Merchant Merchant --> Verification ``` Every trust decision is based on cryptographic verification rather than visual inspection. *** ## 6. Ownership Architecture ```mermaid flowchart LR Publisher --> Issue Issue --> Owner1 Owner1 --> Owner2 Owner2 --> Owner3 Owner3 --> Recovery Recovery --> NewOwner ``` Ownership may change throughout the asset lifecycle while maintaining a verifiable history according to Publisher policy. *** ## 7. Manufacturing Architecture ```mermaid flowchart LR SecureElement Manufacturer Provisioning Certification Publisher Distribution User SecureElement --> Manufacturer Manufacturer --> Provisioning Provisioning --> Certification Certification --> Publisher Publisher --> Distribution Distribution --> User ``` Every compliant device passes through secure manufacturing and provisioning before entering the ecosystem. *** ## 8. Blockchain Adapter Architecture ```mermaid flowchart TB Wallet Publisher Merchant BlockchainAdapter["Blockchain Adapter SDK"] Ethereum Polygon TON Solana Bitcoin Future["Future Networks"] Wallet --> BlockchainAdapter Publisher --> BlockchainAdapter Merchant --> BlockchainAdapter BlockchainAdapter --> Ethereum BlockchainAdapter --> Polygon BlockchainAdapter --> TON BlockchainAdapter --> Solana BlockchainAdapter --> Bitcoin BlockchainAdapter --> Future ``` Applications communicate with one adapter interface while blockchain-specific logic remains isolated. *** ## 9. Developer Architecture ```mermaid flowchart LR Developer Portal["Developer Portal"] SDK API Sandbox ReferenceApps["Reference Apps"] Developer --> Portal Portal --> SDK Portal --> API Portal --> Sandbox Portal --> ReferenceApps ``` The developer platform provides the tools required to build interoperable DCN applications. *** ## 10. Complete Technology Stack ```mermaid flowchart TB Applications SDKs APIs Protocols Verification Certificates SecureElement NFC Hardware Blockchain Applications --> SDKs SDKs --> APIs APIs --> Protocols Protocols --> Verification Verification --> Certificates Certificates --> SecureElement SecureElement --> NFC NFC --> Hardware Hardware --> Blockchain ``` This layered architecture separates responsibilities while maintaining interoperability. *** ## Architectural Principles The DCN architecture follows several guiding principles. #### Modular Each subsystem operates independently through standardized interfaces. *** #### Layered Applications, protocols, hardware, and blockchain infrastructure remain loosely coupled. *** #### Interoperable Independent implementations communicate using common standards. *** #### Secure Trust is established through cryptography, certificates, and Secure Elements. *** #### Extensible New blockchains, hardware platforms, and application categories can be added without redesigning the architecture. *** ## Summary These architecture diagrams provide a consolidated technical view of the Digital Crypto Note ecosystem. Together they illustrate how Publishers, Wallets, Physical Digital Assets, Merchants, Verification Services, Manufacturers, Developers, Blockchain Networks, and the DCN Foundation interact through open standards to create a secure, interoperable infrastructure for Physical Digital Assets. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dcn.foundation/part-x-reference/10-reference/25-appendices/architecture-diagrams.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.