scribb.it

Status

Coming soon app coming soon; the domain is not yet public

As of

2026-10-20

What it is #

scribb.it is the home of Scribbit, a project of Blockspace Holdings. Its site calls it "a planned way to write a document or record directly into Bitcoin. You pay the network fee, and the bytes sit in a Bitcoin block that every archival node keeps." The line on the site, "Write it once. Keep it forever.", comes from Blockspace Holdings' design brief and is not yet confirmed as Scribbit's line (as of 2026-10-20). block.space/projects carries the line "Built in-house."

Blockspace Holdings names Scribbit one of its three most important holdings, beside block.space and degent.club (2026-10-19), and it is featured on blockspace.holdings.

Status #

Coming soon (as of 2026-10-20). Scribbit is a planned set of apps, and none of them exists yet: no Scribbit code has been written.

• The site was built on 2026-10-20. It is static: six pages and a facts list that gives every figure with its source. It describes; it does not transact.
• The domain shows the registrar's placeholder page (as of 2026-10-20). The site goes public once the domain's nameserver change at the .it registry completes.
• The direction of the product is open. Which of the planned promises are commitments, and the content policy and terms of use, are not yet set (as of 2026-10-20).

What is planned #

Everything in this section is planned. It comes from Blockspace Holdings' design brief (October 2026), and none of it is a confirmed commitment yet.

• A non-custodial write path onto Bitcoin L1. The user's own wallet funds and signs; Scribbit would never hold the user's money or keys.
• The network fee only, zero platform fee. The user would pay what miners charge to put the bytes in a block, and nothing else.
• Up to about 400 KB per payload (see the limits below).
• For records and collectibles alike. The site lists signed agreements, records that must not change later, proof that a file existed at a given block, and JSON, CSV or plain text, beside the collectible inscribers below.

The apps (planned) #

Scribbit is a set of apps, all coming soon (as of 2026-10-20):

• Ordinals Inscriber. Write one file to Bitcoin as an ordinal inscription: pick the file, see the fee, sign with your own wallet.
• 4MB Inscriber. Up to a whole block, about 4 MB. Past 400,000 weight units a transaction is non-standard, so it goes straight to a miner instead of through the network.
• Batch Inscriber. Write several files in one commit and reveal, so they share the fixed cost of the transactions.
• Counters Inscriber. Write a Bitcoin Counter: a numbered inscription in witness data, owned through a Counterparty asset.
• Bitbar Inscriber. Write a bitbar: a 1,024-byte SVG.
• Degent Inscriber. Inscribe a Degent, from the Decentralized Gentlemen Club: Pepes in tuxedos, 10,000 when fully minted.
• Litecoin Inscriber. Write a file to Litecoin as an inscription, paying in LTC.
• Dogecoin Inscriber. Write a file to Dogecoin as an inscription, paying in DOGE.
• Hash Attestation. Write only a file's SHA-256 hash: proof the file existed at that block, without making it public.
• Citation Checker. Give an inscription id and a file, and check that the bytes on chain are that file.

How it works (planned) #

The planned flow has five steps: payload, commit and reveal, batch, settle, cite. The mechanics are those of ord, the inscription indexer Blockspace Holdings runs at blockspace.to.

1. Payload. The user chooses the file. It is stored with a content type such as application/pdf. The site advises recording the file's SHA-256 hash first: it is how anyone later proves the bytes on chain are that file.
2. Commit and reveal. The payload goes inside an envelope, a piece of taproot script that never runs, in data pushes of at most 520 bytes each. The commit transaction pays to a Taproot address whose script holds the envelope; the reveal transaction spends it and publishes the script, payload included, in its witness.
3. Batch. One commit and one reveal can carry several inscriptions, so they share the fixed cost of the transactions. Whether a batch would hold several customers' payloads in one reveal is not decided.
4. Settle. The reveal waits in the mempool until a miner includes it in a block: its first confirmation. A reorg can undo recent confirmations, so how many to wait for is a choice.
5. Cite. The user keeps a citation: the inscription id, the block, the content type, the length and the SHA-256 hash.

Cost, by the three books (planned) #

The cost is best read with block.space's three books: the payload is Book C, the operation is Book B, and the whole transaction is Book A. The fee is the transaction's size in vbytes times the fee rate. A payload sits in the witness, so every 4 bytes of payload cost about 1 vB.

A real example. Inscription 2e2fd1b1ea70bc719eefd8efeaf224287409004cb3645d59bb2ef936a8aa358ci0, a PDF titled "Forms Explained", was mined in block 965,177.

The fee, sizes and hash are read from the ord server at blockspace.to; the books are block.space's, as of block 972,199 (the inscription on block.space). For one large file, the gap between the three books is small: the whole reveal is 0.8 % more than the payload alone.

Limits (planned) #

• Why about 400 KB. Bitcoin Core's MAX_STANDARD_TX_WEIGHT is 400,000 weight units (in Bitcoin Core 28.2.0, the version Blockspace Holdings runs), and witness bytes weigh 1 WU each (BIP 141). So a standard transaction can carry a little under 400,000 bytes of payload once its own framing is counted. Bigger inscriptions exist: the largest block.space ranks is 3,969,429 bytes, in block 873,893, in a transaction of 3,993,319 WU (as of block 972,199). A transaction that big is non-standard: default nodes do not relay it. Scribbit plans to stay inside the standard limit.
• Permanence is Bitcoin's, not Scribbit's. Once mined, the bytes cannot be edited or deleted by anyone; archival nodes keep every block.
• Resolvability depends on indexers. Bitcoin nodes store the bytes but do not know what an inscription is; an indexer such as ord finds them. The ord index at blockspace.to counts 128,169,401 inscriptions (127,697,358 blessed, 472,043 cursed), as of block 972,304, 2026-10-20 10:17:29 UTC.
• Everything is public. For a confidential document, the site suggests writing its SHA-256 hash instead.
• "Permanence defeats takedown, not liability." Whoever writes content remains responsible for it (the design brief).
• Fees change with demand for blockspace; a quote holds only for the moment it is made.

Glossary #

archival node

A Bitcoin full node that keeps every block, as opposed to a pruned node, which discards old block data (Bitcoin Core's -prune). The permanence of inscriptions rests on archival nodes.

batch

Several inscriptions written by one commit transaction and one reveal transaction, so that they share the transactions' fixed cost: the inputs, outputs and signatures. ord writes one with its wallet batch command.

Bitcoin L1

Bitcoin's base layer: the blockchain itself, not a sidechain or second-layer network.

Blockspace Holdings

The holding company behind block.space and every project listed on block.space/projects; its own page is blockspace.holdings. The owner named it "Blockspace Holdings" on 2026-10-20.

Book A

The inclusive book: the whole transactions bought for a token, shared where shared. When several tokens share a transaction, its bytes divide among them under the Shared Claim Axiom. In the partition it is content + structure + overhead, "bytes bought for you at all", and it is the backing measure. Fees follow Book A.

Book B

The regional book: the measured regions a token's operations wrote, read or moved through, the transaction's relevant structure and nothing else. In the partition it is content + structure, "bytes bought exclusively for you".

Book C

The content book: the artifact bytes alone, the body of the file or message with all framing removed. In the partition it is content only, "the artifact itself".

citation

What a writer keeps after writing an inscription: its inscription id, the block height, the content type, the length in bytes and the SHA-256 hash of the content. Anyone with an ord index can resolve the id and check the hash.

confirmation

A block that contains the transaction. Each later block adds one more confirmation, and each one makes a reorg that undoes it less likely.

content type

The MIME label stored with an inscription (for example application/pdf) that tells readers how to open its bytes.

cursed inscription

An inscription ord numbers apart from the blessed ones, with a negative number (such as #−10,508). ord /status counts the two separately.

envelope

A data carrier inside a taproot script-path witness, holding content as pushes of at most 520 bytes each. ord's envelope carries the marker 6f7264; Counterparty and Counters have envelopes of their own.

fee rate

The fee a transaction pays per vbyte, in sats per vbyte (sat/vB). At a rate f, a witness byte costs f/4 sats and a non-witness byte f sats.

indexer

Software that reads every block and builds a searchable view of it. ord is the indexer for inscriptions.

inscription

Content bound to a sat by ord, carried in a witness envelope. Under BTI's law the inscription is content, not a token: the inscribed sat is the token that claims the bytes.

inscription id

The reveal's transaction id, then the letter i, then the inscription's position in that transaction.

mempool

The waiting room of unconfirmed transactions that miners choose from.

non-custodial

Never holding the user's funds or keys: the user's own wallet funds and signs.

ord

The ordinals indexer and explorer. Its fork, run by Blockspace Holdings, serves blockspace.to and is the definitional source for BTI's inscription-to-sat binding, sat numbers and inscription numbers.

payload

The file or data being written into an inscription. In block.space's books it is Book C, the content book.

reorg

When a competing chain with more work replaces recent blocks, undoing their transactions' confirmations.

reveal transaction

In a Counterparty taproot mint, the commit transaction pays to a taproot address committing to the envelope tapscript. The reveal transaction spends that output by the script path, exposing the envelope in input 0's witness, and carries an OP_RETURN holding only the literal marker CNTRPRTY. The reveal is the transaction Counterparty parses and the one a counter is keyed to. An unrevealed commit is nothing.

sat

One hundred-millionth of a bitcoin, the unit fees are paid in.

Scribbit

The product at scribb.it, a project of Blockspace Holdings: a planned set of apps for writing files, records and collectibles directly into Bitcoin (and Litecoin and Dogecoin), all coming soon as of 2026-10-20. Its features are planned, not yet confirmed.

SHA-256

A cryptographic hash. The same file always gives the same 64-character hash, and any change gives a different one.

standard transaction

A transaction Bitcoin Core's policy will relay, as opposed to one that is merely valid. One limit: a standard transaction weighs at most 400,000 WU (about 100,000 vB); larger ones are non-standard: default nodes will not relay them, but one can still reach a block by arrangement with a miner, like the 3,969,429-byte inscription in block 873,893.

Taproot

The 2021 Bitcoin upgrade whose script-path spends carry inscription envelopes.

vbytes

Virtual bytes: a transaction's weight divided by four, rounded up. Every non-witness byte costs 4 weight units and every witness byte 1, so a witness byte counts as a quarter of a vbyte. Fee markets price vbytes. BTI's canonical measure is raw serialized bytes with no weight discounting, and every book entry is kept in both bytes and vbytes.

weight unit

The unit of the block limit (BIP 141): every non-witness byte costs 4 WU and every witness byte 1 WU, so weight = stripped size × 3 + total size. A block may hold 4,000,000 WU.

witness

The segwit section of a transaction (BIP 141/144) holding one stack per input. It is hashed into the wtxid but not the txid, and each of its bytes weighs 1 WU instead of 4.

FAQ #

Can I use Scribbit today? #

No. Its apps are coming soon (as of 2026-10-20) and no Scribbit code exists. The scribb.it site describes the planned product only: it connects no wallet, takes no payment and sends no transaction.

Will Scribbit hold my money? #

As planned, Scribbit is non-custodial: your own wallet funds and signs the transactions. This is not yet a confirmed commitment (as of 2026-10-20).

What will it cost? #

As planned, the network fee only, with zero platform fee (not yet confirmed, as of 2026-10-20). For scale, a real 387,641-byte PDF paid 49,842 sats for its whole reveal transaction in block 965,177.

Why about 400 KB? #

Bitcoin Core relays a transaction only up to 400,000 weight units, and a witness byte weighs one unit. So a standard reveal can carry a little under 400,000 bytes of payload.

Can I delete or change what I write? #

No. Once a reveal is mined, nobody can edit or delete its bytes. To correct a record, the site suggests writing a new one that refers to the old one by its inscription id.

Sources #

1. The project list at block.space/projects · block.space/projects
2. The blockspace.holdings page (site/index.html) · blockspace.holdings
3. ord /status (the blockspace.to ord server) · blockspace.to/status
4. Blockspace Holdings records