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
0 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

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

No protocols found matching your criteria.

Try adjusting your search or filter settings.

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