Mezcal

A fungible-token protocol whose transfer instructions are written as a compact JSON payload in an OP_RETURN output.

Chain

Bitcoin

Carrier

OP_RETURN carrying a JSON payload

Ownership model

hybrid

Decimals

asset-defined

Operations

deploy, mint, transfer

Where it came from

Created outside Bitcoin Universe by The Mezcal project, 2025.

Where the specification lives

The specification and reference documentation for Mezcal live in bitcoinuniverseio/mezcal and are published at https://bitcoinuniverseio.github.io/mezcal/. That site is the authority. This page exists so you can find it and compare it with the rest of the estate.

Bitcoin Universe indexes or implements it in bitcoinuniverseio/index-mezcal.

Support in Bitcoin Universe products

Read only

You can see this protocol in the product. No trade action is implemented.

Execution model: Read paths only.

Where it appears

• Core: view, view-collection, view-activity
• Wallet: view, send, receive
• Inscribe: etch, mint, transfer

Implemented

• viewread-only
• view-collectionread-only
• view-activityread-only

Not implemented, and why

list

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

update-listing

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

unlist

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

buy

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

make-offer

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

accept-offer

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

cancel-offer

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

sell

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

settle

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

reconcile

Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

Operational behaviour

Indexing

State is read from mezcal.sh API. Supporting reads come from Configured mempool/Esplora providers for UTXO and settlement reads.

What must be true before any change is accepted: Mezcal mutations remain read-only until authoritative ownership, transferability, builder, signed-transaction validation, broadcast, settlement, and reorg recovery are deployed and proven.

Confirmation

No supported mutation reaches confirmation or settlement.

Reorganisation

Read state follows the authority; no executable order state exists to roll back.

Freshness

No node-tip/indexer-tip comparison or maximum observation age is enforced.

Provenance

Capability facts on this page were generated from backend/packages/ecosystem-contracts/lib/protocols.js in bitcoinuniverseio/core at 15dd03b5986a. Implemented behaviour is not the same as production availability: see how to read our status.