Bitcoin SV Protocols

Bitcoin SV enables unlimited data storage on-chain through OP_RETURN outputs, creating a foundation for diverse, interoperable Application Layer protocols that build functionality on top of the blockchain.

Building on Bitcoin

LEVEL 4: APPLICATION PROTOCOLS
Data Protocols & Applications
5 registered protocols including B://, 1SAT Ordinals, MAP, AIP, and more
DEVELOPER FOCUS
Use Application Layer protocols to create innovative solutions - from storing data and minting tokens to establishing identity systems and crafting decentralized applications.
4
LEVEL 3: TRANSACTIONS
Transaction Structure
Inputs, Outputs, Scripts (OP_RETURN, P2PKH, etc.), Signatures
3
LEVEL 2: BLOCKS
Block Structure
Block Header, Merkle Tree, Timestamp, Difficulty
2
LEVEL 1: BLOCKCHAIN
Bitcoin SV Blockchain
Immutable Ledger, Proof of Work, Chain of Blocks
1

Protocol Registry

5 registered protocols. Click on a protocol to learn more.

Data Storage (2)

Metanet

Verified

Metanet protocol: a directed acyclic graph (DAG) layered on BSV transactions. Nodes are identified by public key and linked to parents via signature, forming content hierarchies with domain-like paths.

meta
Documentation

Twetch

Verified

Twetch social media post protocol. OP_RETURN data includes post content, reply references, and payment routing.

19nknDdM3ueaAt7nFLFQ3aS3PVHVnJoMmU
Documentation

Token (1)

Run

Verified

Run token and smart contract protocol. Identified by OP_0 OP_RETURN 72756e (hex for "run") envelope prefix.

run://.
Documentation

Multi Party (1)

OrderBook

Verified

Open Order Book protocol: a permissionless marketplace for BSV-20 Ordinal tokens. Supports listing, cancellation, and atomic settlement of token trades.

orderbook
Documentation

Other (1)

RelayX

Verified

RelayX transfer and payment protocol used by the RelayX wallet and exchange.

1LtyME6b5AnMopQrBPLk4FGN8UBuhxKqrn
Documentation

How Application Layer Protocols Work

OP_RETURN Outputs

Most Application Layer protocols use OP_RETURN outputs to embed data directly in transactions. Bitcoin SV has no practical limit on OP_RETURN size, enabling protocols to store everything from simple metadata to complete files.

Protocol Identifiers (Bitcom)

Protocols use a unique Bitcoin address as their identifier (Bitcom convention). This address is placed as the first field in OP_RETURN data, allowing parsers to efficiently recognize and decode protocol-specific data. This approach prevents namespace collisions.

Covenant Enforcement

Some protocols use Bitcoin script covenants to enforce rules on-chain. These "enforced" protocols guarantee that state transitions follow the protocol specification - the rules are literally physics, not promises. Look for the "Enforced" badge on protocol cards.

Data Encoding

Protocol data can be encoded in various formats: UTF-8 text, JSON, CBOR, or custom binary encodings. The protocol specification defines how to structure and interpret the data. Data is public by default but can be encrypted for privacy-sensitive applications.

Protocol Registry API

Access protocol information programmatically via our REST API.

GET /api/v1/protocols - List all protocols
GET /api/v1/protocols/:address - Get protocol by address
POST /api/v1/protocols/identify - Identify protocol from address
GET /api/v1/protocols/stats - Protocol usage statistics