Tokenized Protocol primary sources

Reviewed: 2026-05-13 UTC

Core project framing

Protocol and serialization layer

Identity-oracle and compliance layer

Governance and permissions layer

Enforcement and operating rules

Transfer and settlement workflow

Main takeaways from this pass

  • Tokenized Protocol is best understood as a full tokenized-asset operating environment, not just a Bitcoin token format.
  • The most useful lower-layer split is between the message grammar itself and the issuer/governance/compliance logic carried inside that grammar.
  • Identity approval sits in signed oracle responses rather than only in token-local policy state, which makes oracle trust and oracle plurality first-class control surfaces.
  • Governance is unusually field-specific: amendment authority can be configured per field and tied to different vote mechanisms rather than only to one global admin role.
  • Enforcement is explicit and protocol-native. Freeze, thaw, confiscation, and reconciliation are described as named action families rather than informal admin capabilities.
  • Tokenized belongs in comparison sets with ERC-3643, ONCHAINID, Tokeny, Chainlink ACE, and Dusk because it exposes a different architecture for the same broader problem: how regulated asset control, identity gating, governance, and settlement get composed.