> 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/protocol-flow.md). # Protocol Flow > *This appendix illustrates the operational message flows used throughout the Digital Crypto Note (DCN) ecosystem. These protocol flows are informative reference models that demonstrate how Physical Digital Assets interact with Wallets, Publishers, Merchants, Verification Services, Secure Elements, and Blockchain Networks.* *** ## Introduction The DCN ecosystem consists of multiple protocols working together. These protocols enable: * Asset Issuance * Device Provisioning * Authentication * Payments * Ownership Transfer * Verification * Recovery * Lifecycle Management Although implementations may differ internally, compliant systems should preserve the same logical sequence of operations. *** ## Protocol Overview ```mermaid flowchart LR Provisioning Issuance Activation Authentication Payment Verification Transfer Recovery Retirement Provisioning --> Issuance Issuance --> Activation Activation --> Authentication Authentication --> Payment Payment --> Verification Verification --> Transfer Transfer --> Recovery Recovery --> Retirement ``` Every Physical Digital Asset progresses through one or more of these protocol stages during its lifecycle. *** ## 1. Device Provisioning Protocol Before a Physical Digital Asset leaves the factory, it must be securely provisioned. ```mermaid sequenceDiagram participant Manufacturer participant SecureElement participant Publisher Manufacturer->>SecureElement: Initialize Secure Element SecureElement-->>Manufacturer: Generate Hardware Keys Manufacturer->>Publisher: Register Device Publisher-->>Manufacturer: Device Certificate Manufacturer->>SecureElement: Install Certificate SecureElement-->>Manufacturer: Provisioning Complete ``` Provisioning establishes the hardware identity and trust relationship before deployment. *** ## 2. Asset Issuance Protocol A Publisher creates and assigns a new Physical Digital Asset. ```mermaid sequenceDiagram participant Publisher participant Blockchain participant Wallet participant DCN Publisher->>Blockchain: Lock or Mint Digital Asset Publisher->>DCN: Personalize Device Publisher->>Wallet: Register Asset Publisher-->>DCN: Issue Complete ``` Issuance binds the digital asset to the Physical Digital Asset according to Publisher policy. *** ## 3. Wallet Pairing Protocol The Companion Wallet establishes a trusted relationship with the Physical Digital Asset. ```mermaid sequenceDiagram participant Wallet participant DCN participant SecureElement Wallet->>DCN: Tap Device DCN->>SecureElement: Authentication Request SecureElement-->>Wallet: Signed Challenge Wallet->>Wallet: Verify Certificates Wallet-->>DCN: Pairing Successful ``` Pairing enables future management operations while preserving device security. *** ## 4. Authentication Protocol Every sensitive interaction begins with mutual authentication. ```mermaid sequenceDiagram participant Reader participant DCN participant SecureElement Reader->>DCN: Authentication Challenge DCN->>SecureElement: Sign Challenge SecureElement-->>Reader: Cryptographic Response Reader->>Reader: Validate Certificate Chain Reader-->>DCN: Session Established ``` Only authenticated devices proceed to secure messaging. *** ## 5. Payment Protocol The payment protocol enables secure merchant acceptance. ```mermaid sequenceDiagram participant User participant Merchant participant Verification participant Blockchain User->>Merchant: Tap DCN Merchant->>Verification: Verify Asset Verification->>Blockchain: Validate Status Blockchain-->>Verification: Asset Valid Verification-->>Merchant: Approved Merchant-->>User: Payment Completed ``` Payment approval depends on Publisher policy, asset status, and verification results. *** ## 6. Ownership Transfer Protocol Ownership can be transferred between users when permitted by the Publisher. ```mermaid sequenceDiagram participant OwnerA participant WalletA participant Publisher participant WalletB participant OwnerB OwnerA->>WalletA: Initiate Transfer WalletA->>Publisher: Transfer Request Publisher->>WalletB: Assign Ownership WalletB-->>OwnerB: Ownership Accepted Publisher-->>WalletA: Transfer Finalized ``` Ownership changes are recorded according to the Publisher's asset model. *** ## 7. Verification Protocol Verification confirms authenticity before trust is granted. ```mermaid sequenceDiagram participant Merchant participant DCN participant Verification participant PKI Merchant->>DCN: Read Device Merchant->>Verification: Validate Device Verification->>PKI: Verify Certificate Chain PKI-->>Verification: Certificate Valid Verification-->>Merchant: Authentic ``` This protocol protects against counterfeit and unauthorized devices. *** ## 8. Recovery Protocol If a Physical Digital Asset is lost or damaged, recovery follows Publisher policy. ```mermaid sequenceDiagram participant User participant Wallet participant Publisher participant Blockchain User->>Wallet: Request Recovery Wallet->>Publisher: Verify Identity Publisher->>Blockchain: Freeze Existing Asset Publisher->>Wallet: Issue Replacement Wallet-->>User: Recovery Complete ``` Recovery procedures vary by Publisher and asset type. *** ## 9. Lifecycle Management Protocol ```mermaid flowchart LR Manufactured Provisioned Issued Activated InUse["In Use"] Suspended Recovered Retired Manufactured --> Provisioned Provisioned --> Issued Issued --> Activated Activated --> InUse InUse --> Suspended Suspended --> Recovered Recovered --> Retired ``` Lifecycle operations ensure assets remain manageable throughout their operational life. *** ## Protocol Design Principles All DCN protocols follow common principles. #### Secure by Default Every critical operation begins with cryptographic authentication. *** #### Stateless Communication Each transaction contains sufficient information for verification without relying on long-lived sessions where practical. *** #### Interoperable Protocols are independent of hardware vendor, wallet provider, or blockchain implementation. *** #### Modular Each protocol can evolve independently while preserving compatibility. *** #### Auditable Protocol events can be logged and audited according to Publisher policy and regulatory requirements. *** ## Summary The protocol flows described in this appendix illustrate how the Digital Crypto Note ecosystem operates from manufacturing through retirement. Together, these reference flows demonstrate secure provisioning, issuance, authentication, payment, ownership transfer, verification, recovery, and lifecycle management using open standards, cryptographic trust, and interoperable architecture. --- # 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/protocol-flow.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.