Data Dictionary
Shared schema registry for Bitcoin SV on-chain data. Declare payload formats. Validate conformance. Interoperate across services.
How it works
01 Declare
Each schema defines a payload type: its protocol, prefix, required fields, and data types. The schema is the contract between producer and consumer.
02 Validate
Test vectors provide known-good and known-bad payloads. A validator checks raw OP_RETURN bytes against the schema and reports conformance.
03 Interoperate
Any encoder that produces conformant payloads is compatible with any parser that consumes them. The schema is the shared vocabulary.
Schemas
| Type | Protocol | Description |
|---|---|---|
| catalog_entry_v1 | MAP | Announces an item for sale on-chain. Discoverable by any MAP-aware indexer. |
| peer_v1 | MAP | On-chain announcement of a peer endpoint for discovery and federation. |
| proof_v1 | MAP | General-purpose on-chain attestation. Used for auth proofs, provenance anchors, and signed assertions. |
| receipt_v1 | MAP | On-chain proof of a completed transaction. The receipt is the transaction. |
| tax_v1 | MAP | On-chain record of tax collected and remitted in a transaction. Enables real-time municipal tax visibility. |
Transaction taxonomy
Standard types
| P2MS (bare multisig) | Bare m-of-n multisig. The locking script lists ... |
| P2PK | Pay to public key. The original Bitcoin output ... |
| P2PKH | Pay to public key hash. The default Bitcoin out... |
| P2SH | Pay to script hash (pending) |
| OP_RETURN | Data carrier (pending) |
| Coinbase | Block reward (pending) |