[{"t":"blockspace.wiki","u":"/","s":"Everything about Bitcoin blockspace, written down.","k":"","a":"","h":"","x":"A place to write all information and documentation about blockspace: the projects of Blockspace Holdings and their glossaries, the concepts behind them, the token protocols that write to Bitcoin, how their bytes are measured, and the data and APIs anyone can read. Every page cites its sources. Theory is labelled as theory: Blockspace Value Theory is a living document and an untested thesis, and BTP and BYTES are drafts describing things that do not exist. A figure is always given"},{"t":"Bitcoin blockspace basics","u":"/basics/","s":"A short primer: blocks, weight, vbytes, fees, the mempool and the witness discount.","k":"Bitcoin blockspace basics","a":"","h":"","x":"The on-ramp for newcomers and agents: what a block holds, how it is sized, and how its space is priced."},{"t":"Concepts","u":"/concepts/","s":"The ideas behind the meter: Blockspace Value Theory, BTI, the books, attribution, carriage and the rest.","k":"Concepts","a":"","h":"","x":"The ideas the projects are built on. Theory pages are marked as theory."},{"t":"Projects","u":"/projects/","s":"Every Blockspace Holdings project, one page each, with its own glossary and FAQ.","k":"Projects","a":"","h":"","x":"Each project is a domain. A project that isn't live yet says so, with its \"as of\"."},{"t":"Protocols","u":"/protocols/","s":"One page per token family BTI measures: how it writes to Bitcoin, how its bytes are attributed, and its live share.","k":"Protocols","a":"","h":"","x":"Every token family BTI measures."},{"t":"How it's measured","u":"/methodology/","s":"The methodology: null is never zero, the frontier, the conservation identity, and what each board ranks.","k":"How it's measured","a":"","h":"","x":"How block.space turns Bitcoin's bytes into the figures it publishes."},{"t":"Data and APIs","u":"/data/","s":"Every public API across the estate, its fields and examples, and the machine surfaces.","k":"Data and APIs","a":"","h":"","x":"For developers and agents: where the data lives and how to read it."},{"t":"Glossary","u":"/glossary/","s":"Every term, A to Z, defined once, linked everywhere, filterable by project.","k":"Glossary","a":"","h":"","x":"Each term has its own page for linking. Project pages list the terms that belong to them."},{"t":"Answers","u":"/answers/","s":"One question each, answered in 40 to 60 words, with its sources.","k":"Answers","a":"","h":"","x":"Short answers to the questions the projects are asked. All of them are also on the FAQ /faq/ page."},{"t":"Research","u":"/research/","s":"Blockspace Labs projects, one short page each, linked to blockspacelabs.com.","k":"Research","a":"","h":"","x":"Blockspace Labs is the research and development arm, at blockspacelabs.com https://blockspacelabs.com . These pages describe its projects."},{"t":"About this wiki","u":"/about/","s":"What blockspace.wiki is, who writes it, and the rules every page follows.","k":"","a":"","h":"The rules · For machines","x":"blockspace.wiki is the knowledge hub of Blockspace Holdings: \"a place to write all information and documentation about blockspace\". It went live on 2026-10-20. The rules - Invent nothing. Every page is written from Blockspace Holdings' published documents and records and from the live data of Blockspace Holdings' node and indexers, and cites them. A claim with no source is not written. - Theory is labelled as theory. Blockspace Value Theory is a living document and an untested thesis. BTP and"},{"t":"Block weight and the limit","u":"/basics/block-weight-and-the-limit/","s":"Why a block's capacity is counted in weight units, the 4,000,000 WU consensus limit, and the 400,000 WU limit on a standard transaction.","k":"Bitcoin blockspace basics","a":"","h":"How weight is counted · What the limit allows · A smaller limit for relay · Is the limit fixed? · What the chain actually used","x":"A block's capacity is not counted in bytes. It is counted in weight units WU , and consensus caps a block at 4,000,000 WU . This page is the short version; the formulas and worked transactions are on weight units and vbytes /concepts/weight-units-and-vbytes/ . How weight is counted block.space's data-types reference, citing BIP 141, gives the rule: weight = stripped size × 3 + total size Here total size is the whole transaction and stripped size is the transaction without"},{"t":"Fees and the mempool","u":"/basics/fees-and-the-mempool/","s":"Where a transaction waits before it is mined, how its fee is quoted in sat/vB, and what Blockspace Holdings' own node and fee estimates read.","k":"Bitcoin blockspace basics","a":"","h":"How a fee is quoted · What Blockspace Holdings' node keeps · A fee estimate · Fees over the whole chain","x":"A transaction is not mined the moment it is sent. It waits in the mempool, \"the waiting room of unconfirmed transactions that miners choose from\", in the words of the Scribbit glossary. Blocks have capacity limits, and Blockspace Value Theory notes that transactions \"must compete for inclusion\"; the fee is the bid. Once a block includes it, it has its first confirmation. How a fee is quoted A fee is paid in sats, but it is compared as a fee"},{"t":"Halvings and the subsidy","u":"/basics/halvings-and-the-subsidy/","s":"The block subsidy, what Blockspace Holdings' documents say about it and the halving schedule, the fees beside it, and the sats coinbases never claimed.","k":"Bitcoin blockspace basics","a":"","h":"The subsidy now · The halving schedule, as BVT uses it · When fees become the reward · Sats a coinbase never claimed","x":"In Blockspace Value Theory's account, a miner's revenue for a block has two parts: the block subsidy and the fees of the transactions it includes. This page gives what Blockspace Holdings' documents record about the subsidy. They do not give the halving schedule's interval or its dates, so this page does not either. The subsidy now Blockspace Value Theory v3.0, July 2026 lists the current block subsidy as 3.125 BTC , in its table of measured network figures. It describes"},{"t":"The witness discount","u":"/basics/the-witness-discount/","s":"A witness byte weighs a quarter of a base byte, so it costs a quarter as much at the same fee rate. The short version, with links to the full page.","k":"Bitcoin blockspace basics","a":"","h":"In one line · What it changes · How much each protocol takes · Two readings","x":"The witness discount is the rule, from segwit, that a byte in a transaction's witness counts 1 weight unit and every other byte counts 4. The full page, with the measurements and the theory, is the witness discount /concepts/witness-discount/ . This is the short version. In one line block.space's data-types reference: \"witness bytes are real bytes on disk and on the wire, but count 1/4 toward the 4,000,000 WU consensus block limit.\" Because fees are priced in vbytes, a witness"},{"t":"Vbytes","u":"/basics/vbytes/","s":"The virtual byte: a quarter of a transaction's weight, the unit fee rates are quoted in, and why it differs from a transaction's raw size.","k":"Bitcoin blockspace basics","a":"","h":"The definition · Two real transactions · Why the difference matters · The chain in both units","x":"A transaction has a size in bytes and a size in vbytes vB, virtual bytes . The second is the one fees are priced in. This page is the primer; the exact formulas are on weight units and vbytes /concepts/weight-units-and-vbytes/ . The definition block.space's data-types reference gives it: vsize = ceil weight / 4 So a vbyte is a quarter of the weight, rounded up for the transaction as a whole. Since a base byte weighs 4 WU and a"},{"t":"What is a block","u":"/basics/what-is-a-block/","s":"Blocks, transactions and the chain: what a Bitcoin block holds, how its size is counted, and how many there are.","k":"Bitcoin blockspace basics","a":"","h":"What a block holds · What a transaction holds · The chain · Where to go next","x":"Bitcoin's history is a chain of blocks. Each block holds a batch of transactions. The space those transactions take up is what this wiki calls blockspace. What a block holds block.space's data-types reference states a block's size exactly: an 80-byte header, then a count of its transactions, then the transactions themselves. Its size in bytes is the header plus the count plus the sum of the transactions' sizes. BTI uses that sum as a check: what it attributes inside a"},{"t":"Why blockspace is scarce","u":"/basics/why-blockspace-is-scarce/","s":"The fixed weight limit is the fact; what limits blockspace underneath it is Blockspace Value Theory's argument, labelled as theory.","k":"Bitcoin blockspace basics","a":"","h":"The fact: a fixed limit · What BVT proposes · Open questions","x":"Every block has a fixed capacity, and a byte that is in a block stays in it. Those two facts make blockspace limited. Why the limit sits where it does, and what it protects, is argued by Blockspace Value Theory, a living document and an untested thesis. This page keeps the two apart. The fact: a fixed limit Consensus caps every block at 4,000,000 weight units. block.space's data-types reference states it as \"the 4,000,000 WU consensus block limit\". No block"},{"t":"Atomicals as a natural experiment","u":"/concepts/atomicals-natural-experiment/","s":"An observation offered to BVT: Atomicals kept its consumed blockspace and lost its community, so its market is a test between Reading B and Reading C.","k":"Concepts","a":"","h":"The observation · 1. The consumption is permanent · 2. The interpretation layer died and can be rebuilt · 3. The live ledger decays · What each reading predicts · What BTP would change · What can be measured · The one-line version","x":"This page reports a companion observation to Blockspace Value Theory, noted on 2026-07-28 and aimed at BVT Part VII and its three readings. It is an argument about what a market should show, not a measured result. The observation The observation's claim is that Atomicals and its ARC-20 tokens are \"the first blockspace-token protocol where the consumption layer and the community layer have fully decoupled \". That, it says, \"makes it the control group BVT has been missing.\" It describes"},{"t":"Attribution and the Shared Claim Axiom","u":"/concepts/attribution-and-the-axiom/","s":"The Shared Claim Axiom: when several tokens claim the same consumed bytes, they share them equally. Plus the B19 draft, which proposes a different test.","k":"Concepts","a":"","h":"The axiom · Batches, enablers and fungible tokens · Why share equally · What counts as a claimant · The consequence principle · Worked cases and dust claims · Unclaimed and burned blockspace · The proposed revision to BVT · Amendments of 2026-08-11 · The B19 draft","x":"The Shared Claim Axiom is the accounting rule under Blockspace Value Theory. It answers one question: when a token is said to represent consumed kilobytes, which kilobytes, and what happens when several tokens claim the same ones. It was noted on 2026-07-28 as a proposed refinement of BVT's definition of a blockspace token. Its own text says \"'Shared equally' is explicitly a rule of thumb, not a derived result.\" This page describes the rule as the documents state it. It"},{"t":"Blockspace Value Theory","u":"/concepts/blockspace-value-theory/","s":"BVT, a living document and an untested thesis: that tokens built on consumed Bitcoin blockspace form one commodity, priced in kilobytes.","k":"Concepts","a":"","h":"The claim in brief · Part I: what blockspace is · Part II: one commodity · Part III: the supply constraint · Part IV: the floor · Parts V and VI: energy and utility · Part VII: where theory and price diverge · Parts VIII and IX: risk and the thesis · Critiques · Companions","x":"Blockspace Value Theory BVT is a framework for valuing consumed Bitcoin blockspace. The public text is version 3.0, last updated July 2026, with the status \"Living document, subject to revision\". It describes itself as \"an emerging theoretical position, not established consensus, and several of its central claims are untested.\" Everything on this page is what BVT proposes, not a finding. The claim in brief BVT proposes that blockspace tokens BTs , tokens linked to files committed on the Bitcoin blockchain,"},{"t":"Blockspace","u":"/concepts/blockspace/","s":"What blockspace is: the bytes Bitcoin's blocks hold, as BTI counts them, and what Blockspace Value Theory proposes about them.","k":"Concepts","a":"","h":"What is counted · How it is divided · How the use of blockspace changed · What BVT proposes blockspace is · What BVT proposes limits it · Tokens and blockspace · A limit on measurement","x":"Blockspace is the space in Bitcoin's blocks: the bytes of every transaction a block holds. This page keeps two things apart. The first half is what is measured: how many bytes the chain holds and how the Blockspace Token Indexer /concepts/bti/ counts them. The second half is what Blockspace Value Theory proposes about those bytes. That half is theory, and it is attributed to BVT. What is counted BTI \"walks every Bitcoin transaction, from the genesis block forward, and counts"},{"t":"The books (T3)","u":"/concepts/books-t3/","s":"BTI's third layer: a pure function of T1 and T2 that divides shared bytes among tokens, allocates fees and writes the book entries, the aggregates and the consensus hash.","k":"Concepts","a":"","h":"Derived, never facts · The division formula · What a book entry holds · A worked division · The checks · Aggregates and the hash · Live figures","x":"T3 is the third of BTI's three layers: accounting. It is a pure function of T1 and T2. It counts claimants per byte interval, applies the dedication gate, splits remainders by the division formula, allocates fees, writes the book entry rows and aggregates, and emits the consensus hash. The layers document's phrase for it: T3 \"judges worth\". Derived, never facts The design document is firm that this layer carries no information of its own. It exists because the questions are"},{"t":"BTI, the Blockspace Token Indexer","u":"/concepts/bti/","s":"The instrument behind every block.space number: it counts every byte, catalogues every token operation, and writes three books of attribution.","k":"Concepts","a":"","h":"What it does · The design: what BTI must answer · The three layers · The engine · The law it applies · Every byte counted once · Names","x":"BTI, the Blockspace Token Indexer, is the instrument that produces every number the block.space meter displays. In the words of its site documentation it does three things: it counts the bytes, it catalogues the operations, and it writes the books. This page describes what it does, the design it follows and its three layers. What it does It counts the bytes. BTI walks every Bitcoin transaction from the genesis block forward and records each one's raw size, virtual size, weight"},{"t":"BTP, the Blockspace Token Protocol","u":"/concepts/btp/","s":"BTP is a draft (0.1, 2026-07-29) of a protocol whose subject is blockspace itself: which token owns which consumed bytes. It does not exist.","k":"Concepts","a":"","h":"What the draft describes · The operations · Succession and conservation · The burn taxonomy · Consensus and the reference indexer · What the draft says it does to the theory · OPEN decisions · Risks the draft states","x":"BTP, the Blockspace Token Protocol, is a design draft. Blockspace Holdings' records hold draft 0.1, dated 2026-07-29. It describes something that does not exist: its marker encoding, op codes and composition rules are, in its own word, \"unwritten\". The draft says of itself: \"Status: design draft; decisions marked OPEN are undecided.\" This page reports what the draft describes. What the draft describes The draft calls BTP \"an attribution-layer protocol \". It works on backing, the claim layer defined by the"},{"t":"The byte census (T1)","u":"/concepts/byte-census-t1/","s":"BTI's first layer: one protocol-blind pass recording every transaction's size, vsize, weight and fee, and where in each block the data sits.","k":"Concepts","a":"","h":"What it records · Protocol-blind by law · The checks · An example · Live figures · What the census has shown · Its place in BTI","x":"T1 is the first of BTI's three layers: observation. It makes one pass over the chain and records, for every transaction, its size, vsize, weight and fee, plus the byte census: where the data carriers are. T1 knows only bytes. In the layers document's words, its totals are \"the ground truth everything above must conserve against.\" What it records The design document names three products from one decode of each block: - the ledger : per transaction, its size, vsize,"},{"t":"BYTES, a fungible blockspace token","u":"/concepts/bytes/","s":"BYTES is a draft (0.2, 2026-07-29) of a token minted one per byte of consumed blockspace. It does not exist; its economics are analysed in a companion document.","k":"Concepts","a":"","h":"The idea · Why it matters to the theory · Minting · The clean-mint rule (proposed) · Ledger, price and supply · Decisions and open questions · BYTES economics · Risks the draft states","x":"BYTES is a draft design for a fungible blockspace token. Blockspace Holdings' records hold draft 0.2, dated 2026-07-29; it was called BITS in draft 0.1 earlier the same day. The token does not exist. Nothing has been minted and its carrier encoding is unwritten. This page reports what the draft describes and what a companion analysis, BYTES economics 2026-07-29 , concludes about it. The draft's notation: \"all-caps BYTES = the token; lowercase bytes = the unit.\" The idea BYTES is"},{"t":"Carriage and the free-ride index","u":"/concepts/carriage-and-the-free-ride-index/","s":"Bought or riding: why bytes a token merely rode are measured but never backing, and how B/A shows how much of a token's inclusive claim is its own.","k":"Concepts","a":"","h":"Bought and riding · What each books · The free-ride index · Measured cases · Where carriage sits in the block","x":"A token can be in a transaction in two ways. The transaction can have been bought for it, or the token can merely ride a transaction that would have happened anyway. BTI keeps the two apart. Bytes a token rode are carriage: measured in full, and never backing. The site documentation puts it this way: carriage answers what moved through the blockspace; backing answers what the blockspace was bought for. Bought and riding A transaction is bought for a token"},{"t":"Claims (T2)","u":"/concepts/claims-t2/","s":"BTI's second layer: metaprotocol adapters and BTI's own decoders turn each protocol's records into append-only facts about which token touched which bytes.","k":"Concepts","a":"","h":"What T2 writes · What makes a claim · Adapters, decoders and indexers · How the stage runs · An example of a co-claim · Live figures","x":"T2 is the second of BTI's three layers: the catalogue stage. It converts protocol knowledge into facts: token X touched transaction Y at these regions, with this consequence . It reads T1's observations and each protocol's own record, and it writes claims. Judgment, meaning who shares what with whom and what a byte is worth, happens above it, in T3. In the T2 document's words, \"T2 records\". What T2 writes - token : anything separately ownable. Its identity is the"},{"t":"Fee rate","u":"/concepts/fee-rate/","s":"What a transaction pays per vbyte, why a witness byte costs a quarter of a base byte, and how BTI divides fees among the tokens a transaction was bought for.","k":"Concepts","a":"","h":"What a rate buys · Fee rates in the documents · Two real transactions · How the books carry fees · Live figures","x":"A transaction's fee rate is what it pays per virtual byte, written in sats per vbyte sat/vB . Fee markets price vbytes, not raw bytes. This page covers what a rate means for different kinds of bytes, the figures Blockspace Holdings' documents record, and how BTI carries fees in its books. What a rate buys block.space's data-types reference states the rule: at a fee rate of f sat/vB, a witness byte costs f/4 sats and a non-witness byte costs f"},{"t":"Holders and share of backing","u":"/concepts/holders/","s":"Who holds the tokens BTI measures, and how each token's bytes divide among its holders: the holders appendix, the rule of shares, coverage, and the leaderboard population.","k":"Concepts","a":"","h":"The holders appendix · Share of backing · What it can and cannot see · The leaderboard population · Sats decide the top","x":"BTI attributes bytes to tokens, never to addresses. To say how much blockspace stands behind an address, something has to know who holds each token. At Blockspace Holdings that is the job of the holders appendix. This page covers what the appendix is, the rule by which a token's bytes divide among its holders, what it can and cannot see, and the population the block.space leaderboard ranks. The holders appendix For every protocol the books measure, it answers who holds"},{"t":"Inscriptions","u":"/concepts/inscriptions/","s":"Files bound to sats by ord: the witness envelope that carries them, the commit and reveal, recursion and delegation, cursed inscriptions, and how BTI books their bytes.","k":"Concepts","a":"","h":"Content, not a token · The envelope · Commit and reveal · Inscriptions that carry tokens · Recursion · Delegation · Cursed inscriptions · The largest","x":"An inscription is a file bound to a sat. Blockspace Value Theory's protocol roster dates ordinals inscriptions to January 2023 and describes them as arbitrary files bound to individual sats, carried in a Taproot witness envelope. This page covers how the bytes are carried, how BTI books them, and the variants BTI's documents cover: recursion, delegation and cursed inscriptions. Content, not a token Under BTI's law an inscription is content, and the sat it is bound to is the token"},{"t":"Relay policy","u":"/concepts/relay-policy/","s":"What a node will relay, as opposed to what is valid: the fee floor and sub-1 sat/vB relay, the standard size, data-carrier limits and full-RBF, from Blockspace Holdings' own node.","k":"Concepts","a":"","h":"Blockspace Holdings' node · The fee floor and sub-1 sat/vB relay · Standard transaction size · Data-carrier limits · Full-RBF · The research around it","x":"Bitcoin has two kinds of rules. Consensus rules decide what is valid in a block. Relay policy decides what a node will pass on to its peers and keep in its mempool before a block is found. block.space's data-types reference puts the difference as \"what relays, not what's valid\". This page describes the policy settings of Blockspace Holdings' own Bitcoin node, from its live readings and blockspacelabs.com, and what Blockspace Holdings' documents say about each. Blockspace Holdings' node The live"},{"t":"Sats and ordinals","u":"/concepts/sats-and-ordinals/","s":"Every sat is separately ownable and numbered by ord. How BTI treats the sat as a token, why rarity is not one, and the Ordinal Sats family on block.space.","k":"Concepts","a":"","h":"Numbering: ord · The sat as a token · The positional appendix · Ordinal Sats on block.space · Where sats are · Lost sats","x":"BTI's token table calls the sat \"the base token\": every sat is separately ownable and moves with the output that holds it. This page covers how sats are identified, how BTI treats them as tokens, and what block.space shows of them under the family name Ordinal Sats. Numbering: ord Sat identity is ord's numbering. ord gives each sat an ordinal number, and BTI uses that number as the sat token's identity, its canonical ref ruleset B11 . The token table"},{"t":"Spent sats (blockspace.to)","u":"/concepts/spent-sats/","s":"blockspace.to is an ord explorer and indexer that also keeps the sat ranges of spent outputs. What that adds, what uses it, and the live state of its index.","k":"Concepts","a":"","h":"What the fork keeps · What uses it · Live state · Research on it · Related","x":"blockspace.to's line on the project list is the owner's: \"Tracks spent sats. A Blockspace Labs product.\" blockspacelabs.com describes it as \"an ord explorer and indexer that also tracks which sats have been spent\", running a fork of ord with --index-spent-sats . The project list marks it live since 2026-10-20 08:32 UTC, when the owner moved its nameservers. This page covers what spent sats are in Blockspace Holdings' documents, what uses them, and the live state of the index. What the"},{"t":"The frontier and \"as of block H\"","u":"/concepts/the-frontier/","s":"How far each stage of BTI and its appendix has got, why the cursors are ordered books ≤ claims ≤ census, and why every block.space figure carries its height.","k":"Concepts","a":"","h":"Three cursors · What moves a cursor, and what stops it · \"As of block H\" · Several heights at once","x":"Every figure BTI publishes is true up to some block. The frontier is the name for that block. Ruleset v1 gives its core meaning: the frontier is the height every registered protocol has been searched to. On block.space the rule for readers is plain: a board says as of block H, and a number without its height is not shown. Three cursors BTI's design runs three stages, and each keeps its own cursor, a saved height recording how far that"},{"t":"The three books","u":"/concepts/the-three-books/","s":"Book A (inclusive), Book B (regional) and Book C (content): three answers to how many bytes back a token, with C ≤ B ≤ A on every entry.","k":"Concepts","a":"","h":"The three books · How they are stored: the partition · Live totals · Worked examples · Which book a board uses · Why three","x":"BTI gives three answers to the question \"how many bytes back this token?\", from the widest to the narrowest. They are Book A, the inclusive book; Book B, the regional book; and Book C, the content book. The site documentation says they answer three different questions about the same token: how much blockspace was consumed by transactions that touched it, how much was consumed for it, and how much of that is substance. No single number answers all three, which"},{"t":"Weight units and vbytes","u":"/concepts/weight-units-and-vbytes/","s":"Three ways to size a Bitcoin transaction (raw bytes, weight units and vbytes), the exact formulas, and why BTI's books count raw bytes.","k":"Concepts","a":"","h":"The formulas · The block limit · Two worked transactions · Which one BTI counts · Fees are priced in vbytes · Size limits beyond the block","x":"A Bitcoin transaction has three sizes. Its raw bytes are its full serialized length. Its weight, in weight units WU , is what the block limit counts. Its virtual size, in vbytes vB , is what fee markets price. This page gives the formulas from block.space's data-types reference and says which one BTI uses where. The formulas The data-types reference citing BIP 141 gives: stripped size = serialized size without marker/flag/witness bytes total size = full serialized size bytes ←"},{"t":"The witness discount","u":"/concepts/witness-discount/","s":"SegWit weighs witness bytes at a quarter of base bytes. What that does to fees, how BTI measures it per protocol, and what Blockspace Value Theory proposes it means.","k":"Concepts","a":"","h":"The mechanism · What it does to data on Bitcoin · Measured per protocol · What BVT proposes (theory) · Why BTI counts raw bytes","x":"The witness discount is the rule, introduced with SegWit, that a byte in a transaction's witness counts 1 weight unit while every other byte counts 4. The first half of this page is the mechanism, from block.space's data-types reference, and the measurements BTI has taken of it. The second half is what Blockspace Value Theory proposes it means. That half is theory, and it is labelled as such. The mechanism A segwit transaction carries one witness stack per input, after"},{"t":"bitmap.holdings","u":"/projects/bitmap.holdings/","s":"Bitmap Holdings: \"Bitmaps turn each Bitcoin block into digital land—programmable, ownable, eternal.\"","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is bitmap.holdings is the site of Bitmap Holdings. Its own headline is \"The New Data Layer of Civilization\", and its line: \"Bitmaps turn each Bitcoin block into digital land—programmable, ownable, eternal.\" It says Bitmaps turn each Bitcoin block into a coordinate that can be owned and programmed. Status Live at https://bitmap.holdings as of 2026-10-20 . It is a Blockspace Holdings property, hosted separately from the other projects. Blockspace Holdings counts it among its holdings 2026-10-20 . A planned"},{"t":"block.space","u":"/projects/block.space/","s":"The Bitcoin Blockspace Meter: how much of Bitcoin's blockspace is attributed to tokens, token by token, byte by byte.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures · Links","x":"What it is block.space calls itself \"The Bitcoin Blockspace Meter\": \"how much of Bitcoin's blockspace is attributed to tokens, token by token, byte by byte.\" the Meter displays the numbers that BTI, the Blockspace Token Indexer, produces. The site states its limits in its own footer: every figure is read live from the books and bounded by the height they are written to; nothing is modelled, extrapolated or filled in; and where a measurement does not exist yet, the site"},{"t":"blockspace.holdings","u":"/projects/blockspace.holdings/","s":"Blockspace Holdings' own page: \"We acquire & Hodl Blockspace Assets. We serve public Blockspace Infrastructure.\"","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is blockspace.holdings is the page of Blockspace Holdings. In its own words: \"We acquire & Hodl Blockspace Assets. We serve public Blockspace Infrastructure.\" Its heading reads \"The byte unit of value.\" Beside it sits a 1 kB Bitbar, \"Exactly 1,024 bytes on Bitcoin Mainnet.\" The tagline, the 1,024-byte bitbar and the \"Hodl\" wordplay are fixed parts of the page. Its scope, in Blockspace Holdings' words 2026-10-19 : \"we will display all these projects as holdings. The most important"},{"t":"blockspace.loans","u":"/projects/blockspace.loans/","s":"A parked domain of Blockspace Holdings; no concept announced as of 2026-10-20.","k":"Projects","a":"","h":"What it is · Status · How it works","x":"What it is A domain of Blockspace Holdings with no project yet. The project list gives it no name and no line as of 2026-10-20 . Status Coming soon, as of 2026-10-20. The project list marks it \"soon\". The domain serves a generated \"Coming soon\" page. How it works Nothing is built, as of 2026-10-20. The concept under consideration, not confirmed, is \"What blockspace is worth as collateral: today's sats/KB floor per family, from blockspace.markets\": an information page only, with"},{"t":"blockspace.markets","u":"/projects/blockspace.markets/","s":"Blockspace for sale, priced per kilobyte.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures · Links","x":"What it is blockspace.markets is \"blockspace for sale, priced per kilobyte\". In its own words, it shows every asset listed for bitcoin on the venues the block.space buy board watches, ranked by what a kilobyte of its blockspace costs. Status Live, as of 2026-10-20. The project list marks it live from 2026-10-19. How it works A static page is rebuilt every 10 minutes from the buy board's public listing data. The wallet and buying flow stay in one place, at"},{"t":"blockspace.news","u":"/projects/blockspace.news/","s":"The day in Bitcoin blockspace, in numbers, from block.space.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures · Links","x":"What it is blockspace.news is \"the day in Bitcoin blockspace, in numbers, from block.space\": a daily edition of numbers and links. In its own words, every figure is read from block.space's public API, and nothing is estimated. Status Live, as of 2026-10-20. The project list marks it live from 2026-10-19. The first edition appeared at 00:15 UTC on 2026-10-20. How it works Each day at 00:15 UTC the site saves a snapshot of block.space's public API https://block.space/api/meter, /api/summary and /api/protocols,"},{"t":"blockspace.space","u":"/projects/blockspace.space/","s":"A parked domain of Blockspace Holdings; no concept announced as of 2026-10-20.","k":"Projects","a":"","h":"What it is · Status · How it works","x":"What it is A domain of Blockspace Holdings with no project yet. The project list gives it no name and no line as of 2026-10-20 . Status Coming soon, as of 2026-10-20. The project list marks it \"soon\". The domain serves a generated \"Coming soon\" page. How it works Nothing is built, as of 2026-10-20. The concept under consideration, not confirmed, is \"Where the space in Bitcoin's blocks goes: every byte of the chain by what it carries frames, outpoints,"},{"t":"blockspace.to","u":"/projects/blockspace.to/","s":"\"Tracks spent sats. A Blockspace Labs product.\"","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is blockspace.to \"tracks spent sats\". It is \"a Blockspace Labs product\": an ord explorer and indexer that also tracks which sats have been spent see spent sats . Blockspace Labs lists it as a Live product. It indexes inscriptions and runes on Bitcoin mainnet. Status Live at https://blockspace.to since 2026-10-20 08:32 UTC; the page there reads \"Ordinals\" as of 2026-10-20 . How it works blockspace.to runs a fork of ord, \"ord server + indexer spent-sats fork \", with"},{"t":"blockspace.wiki","u":"/projects/blockspace.wiki/","s":"\"A place to write all information and documentation about blockspace.\"","k":"Projects","a":"","h":"What it is · Status · How it works","x":"What it is blockspace.wiki is this site: \"everything about Bitcoin blockspace, written down\". In Blockspace Holdings' words 2026-10-20 , it is \"a place to write all information and documentation about blockspace\". It has a page for each project with its own glossary and FAQ, the concepts Blockspace Value Theory, BTI, the three books and more , the protocols, the basics, how it's measured, the data and APIs, answers, research and a timeline. It is the knowledge hub of Blockspace Holdings,"},{"t":"blockspacelabs.com","u":"/projects/blockspacelabs.com/","s":"Blockspace Labs: \"Research and development for Bitcoin blockspace.\"","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is Blockspace Labs is, in its own words, \"research and development for Bitcoin blockspace\", a part of Blockspace Holdings. Its card on block.space/projects reads \"Research and development R&D .\" Its projects are cards with a status. The Live ones run today on Blockspace Holdings' own Bitcoin node and indexers: the sub-1 sat/vB relay, blockspace.to and its spent sats, the Blockspace Token Indexer, the byte census, who holds blockspace, and the blockspace price. The Research ones are descriptive studies:"},{"t":"counters.fun","u":"/projects/counters.fun/","s":"Counters with XCP liquidity pools. On-chain files only.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is counters.fun is the market layer for Bitcoin Counters. In its own words: \"Counters are files in Bitcoin witness data, owned through Counterparty assets. This is where they get markets. Nothing here is hosted: every image is read out of a Bitcoin block.\" Its card line is \"Counters with XCP liquidity pools. On-chain files only.\" It shows the counters that have XCP pools, the ones on their way to one, and pages to mint or pool one yourself."},{"t":"counters.gallery","u":"/projects/counters.gallery/","s":"Bitcoin Counters explorer: numbered inscriptions in Bitcoin witness data, owned through Counterparty assets.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is counters.gallery is the explorer for Bitcoin Counters. In its own words: \"Explore Bitcoin Counters: numbered inscriptions stored in Bitcoin witness data and owned through Counterparty assets, numbered from zero.\" A counter is \"a numbered file event\": a file committed permanently to Bitcoin as the description of an XCP asset, carried in a Counterparty taproot envelope. Counterparty carries identity, ownership, naming, transfer and the content itself; the counters protocol only says which events qualify and how they are"},{"t":"degent.club","u":"/projects/degent.club/","s":"The Decentralized Gentlemen Club: a community-driven ordinal collection of unique Pepes in tuxedos, built on Bitcoin, with a non-custodial mint.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is degent.club is the Decentralized Gentlemen Club. In its own words it is \"a community-driven 10K ordinal collection of unique Pepes in tuxedos, built on Bitcoin\". The collection is 10,000 when fully minted: inscribed . Its README describes the project as the collection plus \"the automated, non-custodial mint that lets anyone add a Degent, up to a block-sized one, from the website with no human in the loop\". Each piece is a Degent. The project is maintained by"},{"t":"devcash.dev","u":"/projects/devcash.dev/","s":"Devcash: \"Cash for the developer economy: a bounty platform and a decentralized exchange.\"","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is Devcash is, in its card's words, \"Cash for the developer economy: a bounty platform and a decentralized exchange.\" Its own site says: \"Devcash DEV is cash for the developer economy. It is the official currency of Blockchain Developers United.\" It is a project of Blockspace Holdings listed on block.space/projects. Status Live at https://devcash.dev as of 2026-10-20 . It is the one project hosted separately from the others. It is left off blockspace.holdings but stays on block.space/projects. How"},{"t":"litepedia.space","u":"/projects/litepedia.space/","s":"\"Wikipedia on Litecoin. The encyclopedia uploaded to Litecoin, where anyone can pay LTC to make an edit, with a robust editing system.\"","k":"Projects","a":"","h":"What it is · Status · How it works","x":"What it is In Blockspace Holdings' words 2026-10-20 , Litepedia is \"a litecoin wikipedia project where we will upload wikipedia to litecoin and let people pay LTC to make edits while having a robust editing system \". Its card reads: \"Wikipedia on Litecoin. The encyclopedia uploaded to Litecoin, where anyone can pay LTC to make an edit, with a robust editing system.\" LTC is Litecoin's coin. litepedia.space belongs to the research group, beside Blockspace Labs and blockspace.to, under Blockspace Holdings."},{"t":"mintbitbars.xyz","u":"/projects/mintbitbars.xyz/","s":"Bitbar minting app.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is mintbitbars.xyz is, in its own title's words, the \"Bitbar Minting App\": a page that shows a bitbar and a \"Mint Bitbar\" button. Its card line on block.space/projects is \"Bitbar minting app.\" No other description of it exists in Blockspace Holdings' records. Status The page is live at https://mintbitbars.xyz as of 2026-10-20 . Since 2026-10-19 it has been served from the code of antron3000/Bitbar-Minting-App, page and image only. The server that the Mint button's QR code comes from"},{"t":"scribb.it","u":"/projects/scribb.it/","s":"Scribbit: a planned way to write a document or record directly into Bitcoin. \"Write it once. Keep it forever.\"","k":"Projects","a":"","h":"What it is · Status · What is planned · How it works (planned) · Cost, by the three books (planned) · Limits (planned)","x":"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"},{"t":"spaceblocks.art","u":"/projects/spaceblocks.art/","s":"Space Blocks: one image that fills a 1 MB block, inscription #83,851,681, 1,047,584 bytes.","k":"Projects","a":"","h":"What it is · Status · How it works · Key figures","x":"What it is spaceblocks.art is the home of Space Blocks. In its own words: \"Space Blocks: one image that fills a 1 MB block. Inscription 83,851,681, 1,047,584 bytes, 99.9 % of a 1 MB block.\" Its second page shows the other works that fill a block. Status Live at https://spaceblocks.art since 2026-10-19 as of 2026-10-20 . How it works It is a static site, built from block.space's public API https://block.space/api/largest-inscriptions , with the thumbnails copied into the site, so the"},{"t":"Alkanes","u":"/protocols/alkanes/","s":"Contract tokens called through protostones inside a runestone. metashrew's trace is the record; every contract that ran claims the bytes.","k":"Protocols","a":"","h":"How Alkanes puts data on Bitcoin · How BTI attributes the bytes · Live figures · Holders · Not covered by a source","x":"An alkane is a token of the Alkanes protocol. BTI's token table calls alkanes \"protostone VM tokens\" and names each one by its AlkaneId, written block:tx . DIESEL is 2:0 . How Alkanes puts data on Bitcoin Alkanes messages are protostones. They ride inside a runestone, in the OP RETURN output that Runes uses, under the protorunes field, tag 16383. The case studies note that the tag is odd, so plain runes ignores it and never treats it as a"},{"t":"ARC-20 and Atomicals","u":"/protocols/arc-20-and-atomicals/","s":"Atomicals' fungible ARC-20 tickers, whose units ride sats, and its NFTs (containers and dmitems). One definitional indexer, one quarantine, one named gap: realms.","k":"Protocols","a":"","h":"How Atomicals puts data on Bitcoin · How BTI attributes the bytes · Live figures · The natural experiment · Not covered by a source","x":"Atomicals defines two kinds of token that BTI measures. ARC-20 tickers are fungible, and the books keep them under the key arc20 . Atomicals NFTs, containers and dmitems, are a second family, atomicals-nft . Both are catalogued by one adapter, as BTI's rule of one adapter per indexer requires: \"atomicals catalogues ARC-20 AND the NFTs\". How Atomicals puts data on Bitcoin Atomicals writes to the witness. The data-types reference lists it among the envelope protocols and gives its marker, atom"},{"t":"Bitmap","u":"/protocols/bitmap/","s":"Bitmap districts are labels on inscribed sats: BTI's opi-bitmap adapter adds a source under Ordinal Sats, never a family of its own.","k":"Protocols","a":"","h":"How Bitmap writes to Bitcoin · How BTI attributes its bytes · Quirks on record · What the live data shows","x":"In bitmap.holdings' own words, \"Bitmaps turn each Bitcoin block into a piece of digital land. Each Bitcoin block becomes a coordinate. Each coordinate becomes ownable.\" Bitmap writes a claim to a block, a district, as an inscription. In BTI a district is not a token. It is a label on an inscribed sat, and Bitmap's bytes are counted under Ordinal Sats. Bitmap has no family of its own in the books, so this page has no live share. How Bitmap"},{"t":"BRC-100","u":"/protocols/brc-100/","s":"An inscription-borne tick ledger with a two-step transfer; its only mirror died, so BTI was ruled its indexer on 2026-08-11.","k":"Protocols","a":"","h":"How BRC-100 writes to Bitcoin · How BTI attributes its bytes · Findings of the August review · Live figures","x":"BRC-100 is a fungible tick ledger written in inscriptions. In BTI's token table its tokens are BRC-100 ticks, each identified as brc100: