Hal Finney
Running BIP-110.bip110.run

A free public service · Follow Bitcoin through the hard fork.

One fee -> every validating node

What is every node being made to carry?

The sender pays once. Every validating node downloads and checks the block. Archival nodes retain it.

-- carried an OP_RETURN script above 83 bytes Reading the house node...

Recent blocks

at or below 83 B larger script one square = one block

House node · reading the current block field...

Read the payloads

Decoded bytes, grouped only when identical, with block receipts you can inspect.

Receipt source and limits

Reading the receipt range...

These are selected decoded finds, not a claim that every above-default payload has the same meaning.

Where data lands changes the cost

Fake keys

Disguised data can create outputs that burden the UTXO set.

Witness

Witness data receives Bitcoin's four-to-one weight discount.

OP_RETURN

Provably unspendable data stays out of the UTXO set and remains explicit in the block.

Bitcoin Core's former 83-byte standard-policy default was part of that compromise. Raising the ceiling changes the price and permission of the lane. The choice is where data lands, what it costs, and who carries the result.

Payload text is quoted as found and is evidence of what was written, not a claim by this site. Email addresses inscribed by strangers are masked; nothing else is altered. If someone objects that this should not be shown here: then it should not be on the blockchain.

Report an error

Your page and browser details are attached automatically.

jpg · png · webp · gif · heic