Bitcoin-native event streams

Opstream

A lightweight Bitcoin-native event stream protocol.

Op_stream

live replay

1
Operator address

bc1q...event-stream

2
Valid txs

OP_RETURN verified

3
Run state

index rebuilt

Protocol comparison

Built to make Bitcoin NFTs easier to index, own, and monetize.

Opstream is designed around one simple advantage: state is an explicit event stream. Indexers read clear OP_RETURN instructions, creators get paid by valid operations, and ownership is replayed from addresses instead of fragile UTXO movement.

One address, not the whole chain

Opstream indexers follow the operator address event stream instead of decoding every inscription or tracking every wallet.

Creator fees are part of validity

A canonical mint or transfer includes the operator payment, so creator economics live inside the protocol rules.

Ownership is harder to break

Ownership is replayed from address anchors and protocol events, not accidentally moved by spending the wrong UTXO.

PointOpstreamOrdinals
IndexerOne operator addressGlobal inscription index
Creator feesRequired for valid eventsMarketplace policy
Fractional NFTsNative unitsNot native
MarketplacesOptionalOften index-dependent
Data layerOP_RETURN JSONWitness data
DecodingSurface-level payloadWitness decoding
OwnershipAddress-based stateUTXO-carried item

The comparison focuses on the default ownership and indexing models.Opstream's goal is not to replace Bitcoin primitives; it keeps the protocol layer smaller by making state transitions explicit, address-anchored, and replayable.

Lightweight by design

Opstream avoids smart contracts, global NFT indexers, marketplace APIs, and external consensus. Bitcoin transaction history is the event log.

Operator event stream

Indexers follow one Bitcoin operator address, parse valid protocol transactions, and replay them in canonical order.

Deterministic transactions

Mint and transfer flows use stable output positions for operator payment, protocol JSON, and ownership anchors.

Rebuildable state

The database is only a cache. Ownership, balances, and collection state can be rebuilt from Bitcoin history.