> 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/home/why-dcn.md). # Why DCN > **Digital assets have transformed ownership and value, but interacting with them remains almost entirely digital. DCN introduces the missing physical interface—making digital assets easier to hold, recognize, verify, transfer, and use in the physical world.** *** ## The Missing Physical Layer Blockchain introduced a fundamentally new model of ownership. For the first time, individuals can directly own and transfer digital assets without depending entirely on centralized financial infrastructure. Yet the way people interact with these assets remains complicated. Today, using digital assets often requires: ``` Smartphone ↓ Application ↓ Wallet ↓ Network Selection ↓ Address / QR Code ↓ Transaction Details ↓ Gas ↓ Signature ↓ Blockchain ``` This works for experienced users. It is not necessarily the ideal interface for billions of everyday users. DCN asks a different question: > **What if interacting with a digital asset could be as natural as holding and tapping a physical object?** *** ## Cash Solved Something Important Cash has survived centuries of technological change because its user experience is extremely simple. A person can: * See it * Hold it * Understand its value * Give it to another person * Receive it * Carry it * Spend it There is almost no technical knowledge required. Crypto introduced powerful capabilities that cash cannot provide: * Programmability * Global settlement * Digital scarcity * Cryptographic ownership * Tokenization * Smart contracts * Transparent verification But much of the physical simplicity disappeared. DCN attempts to combine these two strengths. ``` PHYSICAL MONEY DIGITAL ASSETS Simple Programmable Tangible Global Portable Verifiable Familiar Cryptographic Easy to hand over Network connected ↓ DCN ↓ PHYSICAL DIGITAL ASSET ``` *** ## Crypto Has an Interface Problem The blockchain itself is not necessarily the biggest obstacle to adoption. The interface around blockchain can be. Users encounter concepts such as: * Wallet addresses * Seed phrases * Private keys * Gas fees * Network selection * Token contracts * Bridges * Signing requests * QR codes These concepts are important technically, but users should not always need to understand them simply to use digital value. The infrastructure can remain sophisticated while the interface becomes simpler. That is one of the fundamental motivations behind DCN. *** ## From Scan to Tap QR codes have become an important bridge between physical and digital payments. But QR-based interaction usually requires several steps. ``` Unlock Phone ↓ Open Application ↓ Select Scanner ↓ Align Camera ↓ Scan QR ↓ Enter / Verify Amount ↓ Approve Transaction ``` A standardized DCN experience could enable: ``` Tap ↓ Authenticate ↓ Verify ↓ Authorize ↓ Complete ``` The complexity moves from the user interface into the protocol. *** ## Physical Ownership Matters Human beings naturally understand physical possession. We understand: > "I have this." That mental model has enormous value. Digital ownership works differently. A user technically controls cryptographic credentials that authorize changes to a distributed ledger. While powerful, this model is abstract. DCN introduces a physical interface that can make certain digital ownership experiences more intuitive. The physical object does not replace blockchain ownership. Instead, it becomes a secure interface to it. *** ## Beyond Hardware Wallets Hardware wallets provide excellent protection for cryptocurrency private keys. But DCN serves a different purpose. A traditional hardware wallet is primarily designed for: > **Secure custody of cryptocurrency.** DCN is designed as: > **A standardized physical interface for digital assets.** That distinction allows DCN to support much broader applications. ``` Hardware Wallet │ └── Secure Crypto Custody DCN │ ├── Digital Cash ├── Stablecoin Notes ├── Identity ├── Credentials ├── Tickets ├── Loyalty ├── Benefits ├── Transit ├── Certificates └── Collectibles ``` DCN therefore should not be viewed simply as another hardware wallet format. *** ## Why Not Just Use NFC Cards? NFC cards already exist. The challenge is that most are built for individual proprietary ecosystems. A transit card may work only with one transit authority. A hotel key may work only with one hotel system. A bank card follows a particular payment network. A loyalty card belongs to one brand. DCN proposes something different: > **A common open framework for Physical Digital Assets.** The objective is not simply to add NFC to cryptocurrency. It is to standardize: * Hardware identity * Asset discovery * Authentication * Ownership * Publisher identity * Verification * Wallet interaction * Merchant interaction * Lifecycle management * Blockchain connectivity NFC is only one component of that architecture. *** ## Why an Open Standard? Imagine every Publisher creating its own physical crypto format. One uses proprietary NFC commands. Another requires its own wallet. Another uses a different authentication method. Another requires specialized merchant hardware. Another creates an incompatible certificate system. The result would be fragmentation. DCN attempts to establish a common foundation. ``` Publisher A ─┐ Publisher B ─┤ Publisher C ─┤ Bank ────────┤ Government ──┤ Stablecoin ──┤ Enterprise ──┤ Game ────────┘ │ ▼ DCN STANDARD │ ┌─────┼─────┐ ▼ ▼ ▼ Wallet POS Apps ``` Publishers remain independent. The interaction standard becomes common. *** ## Why Multi-Chain? Digital assets will not exist on one blockchain. Different ecosystems optimize for different requirements. DCN therefore should not force users or Publishers into a particular network. The architecture separates the physical standard from blockchain infrastructure. ``` Bitcoin │ Ethereum ───────────────┤ │ Solana ───────── Blockchain Adapters │ TON ────────────────────┤ │ CBDC Networks ──────────┤ │ Future Networks ────────┘ │ ▼ DCN │ ▼ Physical Digital Asset ``` The user interacts with the asset. The infrastructure handles the network. *** ## Why Secure Hardware? A printed blockchain address alone cannot establish trustworthy physical authenticity. Anything printed can potentially be copied. For valuable Physical Digital Assets, the physical object needs a cryptographic identity that cannot simply be reproduced by photocopying its appearance. DCN therefore introduces the concept of a **Hardware Root of Trust**. A Secure Element can protect cryptographic keys and respond to authentication challenges. ``` Reader Generates Challenge ↓ DCN Secure Element ↓ Cryptographic Operation ↓ Signed Response ↓ Certificate Verification ↓ Authentic / Invalid ``` The goal is simple: > **Don't trust the appearance of the note. Verify the note.** *** ## Why Publishers? DCN separates the **standard** from the **asset issuer**. The DCN Foundation should not need to issue every Physical Digital Asset. Instead, organizations become Publishers. A Publisher could be: * A bank * A stablecoin provider * A government * A university * A corporation * A gaming company * A retailer * A transit authority This creates an open ecosystem. ``` DCN Foundation ↓ Defines Standard Publisher ↓ Defines Product Manufacturer ↓ Creates Physical Asset Developer ↓ Creates Applications Merchant ↓ Accepts Asset User ↓ Uses Asset ``` Each participant has a clearly separated responsibility. *** ## Why Merchants Need a Standard Merchant adoption becomes difficult when every digital asset requires a different integration. DCN aims to provide a common acceptance architecture. Instead of integrating independently with every Publisher: ``` Merchant ├── Publisher A Integration ├── Publisher B Integration ├── Publisher C Integration ├── Publisher D Integration └── Publisher E Integration ``` a standardized architecture could move toward: ``` Merchant ↓ DCN Merchant SDK ↓ DCN Verification ↓ Publisher / Blockchain ``` This is critical if Physical Digital Assets are ever expected to achieve broad acceptance. *** ## Why Developers Need DCN Standards create developer ecosystems. Developers should not have to understand every Secure Element, blockchain, manufacturer, or Publisher implementation. DCN therefore defines common SDK layers: ``` Wallet SDK Merchant SDK Publisher SDK Blockchain Adapter SDK ``` Applications can then interact with standardized interfaces while lower-level complexity remains abstracted. *** ## Why Governments and Enterprises May Need It The physical-digital problem exists far beyond cryptocurrency. Governments still issue: * Identity documents * Benefit cards * Certificates * Transit credentials Enterprises still issue: * Employee IDs * Membership cards * Gift cards * Loyalty cards * Access credentials Many of these systems remain isolated. A standardized Physical Digital Asset architecture could eventually provide common infrastructure for securely connecting such objects with modern digital systems. *** ## Why Now? Several technologies have matured simultaneously. #### Blockchain Programmable digital ownership is now globally deployed. #### NFC Billions of consumer devices already support contactless communication. #### Secure Elements Tamper-resistant cryptographic hardware is widely available. #### Smartphones Users already understand tap-based interaction. #### Digital Identity DIDs and Verifiable Credentials are creating new identity models. #### Tokenization Real-world and digital assets are increasingly represented digitally. These technologies create the conditions for a standardized physical interface. *** ## The Opportunity The opportunity for DCN is not simply: > **Put cryptocurrency inside a note.** The larger opportunity is: > **Create the interoperability standard connecting trusted physical objects with digital assets.** That distinction fundamentally changes the scope of the project. *** ## The Missing Layer The evolution can be viewed as three major layers. ``` INTERNET ────────────── Standardized Information BLOCKCHAIN ────────────── Standardized Digital Ownership DCN ────────────── Standardized Physical Interaction with Digital Ownership ``` Blockchain created the digital ownership layer. DCN seeks to create a standardized physical interaction layer above it. *** ## Why DCN Because digital assets need a physical interface. Because users need simpler interactions. Because physical objects need cryptographic authenticity. Because Publishers need a common framework. Because merchants need interoperability. Because developers need standardized SDKs. Because blockchain infrastructure must remain multi-chain. Because identity, value, credentials, and ownership are increasingly becoming digital. And because the transition from physical to digital does not necessarily mean the physical world disappears. It means the physical world becomes **cryptographically connected**. *** ## Our Objective DCN's objective is to establish: > **A secure, open, blockchain-neutral, manufacturer-neutral, and interoperable standard through which any compatible digital asset can be represented or accessed through a trusted physical object.** The Digital Crypto Note is the beginning. The larger destination is a global ecosystem of **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/home/why-dcn.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.