Summary: Tokenized Protocol is a Bitcoin-family tokenization control stack, not just a tokenization on Bitcoin pitch. The real note is the full issuer workflow: message grammar, oracle-signed transfer approval, field-level governance permissions, and explicit freeze or confiscation powers embedded into one OP_RETURN-based operating model.
What it does:
Defines Tokenized actions and messages as envelope-wrapped, protobuf-encoded OP_RETURN payloads so wallets, contract agents, and other services can parse a shared message grammar
Models tokenized assets through contract-level and instrument-level request/response flows, where user or administration actions are answered by settlement, rejection, governance, or enforcement actions
Uses identity oracles to sign contract approval, transfer approval, and identity verification messages, letting issuers restrict ownership based on KYC, AML, accreditation, residency, age, or similar offchain eligibility checks
Encodes field-level permissions for contracts and instruments so specific parameters can be changed unilaterally, by issuer referendum, by token-holder initiative, or by administrator-only matters under specific voting systems
Includes a governance system with proposals, votes, ballot casting, ballot counting, and result actions tied to authorisation flags and voting-rule templates
Includes explicit enforcement flows for freeze, thaw, confiscation, and reconciliation orders, with room for linked legal-order hashes and authority signatures
Supports richer transfer patterns than a basic single-recipient token move, including multi-recipient settlement, token-for-bitcoin sales, and cross-contract atomic swaps
Key claims:
The protocol-intro and specification repositories make clear that Tokenized is not just a wallet format or smart-contract app. It standardizes the message layer itself: envelope metadata identifies action types, protobuf structures define payloads, and versioned YAML definitions generate language bindings.
The rules document surfaces a distinctive control model: contract-initiated actions are only valid as responses to user or administration requests, and every valid token must sit inside a contract/instrument lifecycle anchored to a contract address. This request/response framing is a more specific operating model than generic token standard language.
The oracle documentation is the most important mechanism source. Tokenized currently supports identity oracles that sign transfer approvals over receiver address, contract address, instrument code, quantity, recent block hash, and an approved flag. That makes identity gating a separate signed service layer rather than a simple onchain allowlist.
The permissions and governance docs expose another useful split: every mutable field can specify whether unilateral issuer action, administration-led referendum, token-holder initiative, or administrator-only governance may change it, with voting-system references encoded per field. That is more granular than most tokenization stacks that describe governance only at the whole-contract level.
The enforcement docs show that Tokenized treats issuer intervention as a first-class protocol surface rather than an implicit admin backdoor. Freeze, thaw, confiscation, and reconciliation are named action families with explicit request/response flows and legal-order linkage.
The transfer docs add a second important insight: the protocol tries to preserve a regulated-asset workflow while still supporting exchange-style and cross-contract settlement patterns. Atomic swaps and token-for-bitcoin purchases are handled through message-mediated transaction templates and contract-coordinated settlement, not only by direct holder transfers.
The reusable insight is that Tokenized Protocol is best understood as a full issuer-governed asset-management protocol whose real control surfaces are message grammar, oracle trust, field-level permission settings, enforcement rights, and contract-operator workflow. Filing it merely as a BSV tokenization project would lose the point.
Whitepaper: No standalone Tokenized Protocol whitepaper surfaced in this pass. The strongest reviewed primary materials were the official documentation and specification repositories collected in ../whitepapers/tokenized-protocol-primary-sources-2026-05-13.md.