How DOP works

One layer, one responsibility, one source of truth. Trust is proven, not assumed.

The real digital ownership infrastructure behind every DOP transaction.

Applications

Commerce, Licensing, and Commodity — each a domain-specific engine built on the same underlying protocol. None of them is the ownership authority; each consumes it. See which solutions each engine powers →

DOP API

The application-facing orchestration layer. Every domain engine consumes it; it never gets bypassed, so no engine can quietly become its own, competing source of truth.

DOP Foundation

Protocol authority and canonical ownership logic — the single source of truth for what’s genuinely owned, by whom. Deliberately minimal, with no dependencies of its own: new capability is built around the Foundation, never into it.

Wallet & Proof Layer

Cryptographic wallet interaction and proof of ownership, independent of any single application.

Radix

The underlying ledger (Radix), deliberately kept separate from DOP’s own ownership logic above it. That separation is a real architectural choice, not just convenience.

Adapters

WordPress, WooCommerce, and future game-engine and enterprise integrations — consuming the same interfaces available to any external developer. An integration can be replaced without ever touching the Foundation underneath it.

Three separations that hold throughout

  • Proof, ownership, and access stay distinct. Proving you control a wallet, holding genuine ownership, and being granted runtime access are three separate, independently-verified facts — never assumed from one another.
  • Ownership is separate from commerce. A sale is an economic event; ownership is a constitutional one. No marketplace, checkout, or payment becomes the owner-authority by default.
  • Evidence before trust. DOP doesn’t take an application’s word that something happened — it verifies the underlying transaction itself before treating anything as settled.

[Link to technical specification, once written]

[Link to architecture research documentation, once written]

See DOP’s solutions  |  Build with DOP

Ready to move forward? Apply for a licence →