We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Bitcoin transaction types
Every output on chain follows a pattern: a payment, an object, a token, a record, or a contract. Each type here has its script pattern with every part labelled, how it is spent, where it came from, and real transactions from our index.
The same definitions, with their counts, are at /api/v1/types .
Counts cover blocks 0 to 169,755 of 974,914 known. Every block in that range is verified complete and typed, so the counts grow as the sync climbs toward the tip. Blocks 169,756 to 312,754 are complete and not typed yet.
A transaction with several types counts once under each, and anything no type matches counts as custom. Computed by type counts v6 at , from the block tallies.
Building on Bitcoin
Four layers, each resting on the one below.
- 4 Application protocols Data protocols and applications.
- 3 Transactions Inputs, outputs, scripts and signatures. The types below describe this layer.
- 2 Blocks Block header, merkle tree, timestamp and difficulty.
- 1 Blockchain The ledger, proof of work and the chain of blocks.
Cash
Sats a key can spend. Most outputs on chain are this.
Objects
One sat that stands for a thing. Spending the sat moves the thing.
- Bare 1-sat output 1 sat A P2PKH output holding exactly one sat, with no envelope. It may carry an object made earlier. 6,895 txs since block 115,789
- 1Sat Ordinals inscription Inscription A P2PKH lock plus an envelope that carries a file. The file is the object; the sat carries it. none yet in the blocks counted
- Inscription with MAP Inscription + MAP An inscription with a MAP tail after the lock, naming the object's fields. none yet in the blocks counted
- OrdLock listing OrdLock An object offered for sale. The lock itself is the offer: it names the price and who gets paid. none yet in the blocks counted
Tokens
Token ledger entries: an inscription whose JSON names the amount (BSV-20, BSV-21), or a contract whose sats are the amount (STAS).
- BSV-20 BSV-20 Fungible tokens named by ticker, written as JSON inscriptions. First deploy of a ticker wins. none yet in the blocks counted
- BSV-21 BSV-21 Fungible tokens with no ticker race. One output creates the token and its whole supply, and its outpoint is the token's id. none yet in the blocks counted
- STAS token STAS A token whose amount is the output's sats, held by a contract that keeps it a token on every spend. none yet in the blocks counted
Data
Records with no lock. They hold no value and can never be spent.
- OP_RETURN data OP_RETURN Data with no lock. Anything at all can follow it; nothing on chain says how to read it. none yet in the blocks counted
- B:// file B:// A file on chain: the data, its media type, its encoding and an optional name, under the B prefix. none yet in the blocks counted
- MAP record MAP Key-value pairs that say what a transaction is for: its app, its type, and any fields the app needs. none yet in the blocks counted
- AIP signature AIP A signature over the data before it, so a record names its author. none yet in the blocks counted
- SIGMA signature SIGMA A signature over a record and the transaction's inputs, so it cannot be copied into another transaction. none yet in the blocks counted
Conditions
Locks that ask for more than one signature, for time to pass, or for nothing at all.
- Pay to script hash P2SH Locks to the hash of a script, which the spender reveals. Retired from Bitcoin at the Genesis upgrade. none yet in the blocks counted
- Bare multisig Multisig Lists several keys and asks for a number of them to sign, such as any two of three. 6 txs since block 164,467
- Cosign Cosign The owner signs, then a named cosigner. A service can approve each transfer without ever holding the funds. none yet in the blocks counted
- Time lock Lock Sats the owner cannot move until a chosen block height. none yet in the blocks counted
- Transaction lock time nLockTime A transaction no block may include until a chosen block height or time has passed. none yet in the blocks counted
- Anyone can spend OP_TRUE OP_TRUE and nothing else. Whoever sees it first can take it. none yet in the blocks counted
Applications
Protocols that link many transactions into one structure: a tree of nodes, or a set of objects.
- Metanet node Metanet A transaction that is a node in a tree of on-chain content, linked to its parent by the parent's signature. none yet in the blocks counted
- Run jig Run A JavaScript object that lives on chain. Each update is a transaction, and its owner is whoever holds its output. none yet in the blocks counted
- HodLocker post or like HodLocker A post or a like backed by sats in a time lock. The lock is the vote: what it holds, and for how long. none yet in the blocks counted
Everything else
The catch-all for what has not been typed yet.
Registered protocols
11 application protocols, each named by a Bitcoin address placed first in its data. Some are also a type above, and each of those links to its type.
Who owns an address is on the Bitcom registry , with on-chain proof. The same list is at /api/v1/protocols with an API key.
-
15DHFxWZJT58f9nhyGnsRBqrgwK4W6h4Up Other Proven
No description yet.
This address proved ownership on chain with a useradd it funded itself.
Proven by its useradd transaction . See its Bitcom namespace .
15DHFxWZJT58f9nhyGnsRBqrgwK4W6h4Up
-
1HA1P2exomAwCUycZHr8WeyFoy5vuQASE3 Other Proven
No description yet.
This address proved ownership on chain with a useradd it funded itself.
Proven by its useradd transaction . See its Bitcom namespace .
1HA1P2exomAwCUycZHr8WeyFoy5vuQASE3
-
19HxigV4QyBv3tHpQVcUEQyq1pzZVdoAut Other Proven
No description yet.
This address proved ownership on chain with a useradd it funded itself.
Proven by its useradd transaction . See its Bitcom namespace .
19HxigV4QyBv3tHpQVcUEQyq1pzZVdoAut
-
15PciHG22SNLQJXMoSUaWVi7WSqc7hCfva Other Proven
No description yet.
This address proved ownership on chain with a useradd it funded itself.
Proven by its useradd transaction . See its Bitcom namespace .
15PciHG22SNLQJXMoSUaWVi7WSqc7hCfva
-
BSV20 Token Beta
BSV-20 / BSV-21 fungible token inscriptions (1Sat Ordinals). Indexes deploy+mint, transfer (BSV-21, id-based) and detects classic BSV-20 ticker ops. Read-only: composing and broadcasting mints lives in the wallet layer.
bsv20
-
BCat Data storage Curated
BCat large-file protocol. Splits data across multiple chunk transactions referenced by a head transaction. Head tx has info/mime/encoding/filename/flag metadata then raw txid bytes for each chunk; chunk txs carry a single "c" discriminator after the prefix.
Reviewed and listed by hand. No on-chain proof yet.
15DHFxWZJT58f9nhyCA3mREYYzkVDetm6A
-
OrderBook Multi party Curated
Open Order Book protocol: a permissionless marketplace for BSV-20 Ordinal tokens. Supports listing, cancellation, and atomic settlement of token trades.
Reviewed and listed by hand. No on-chain proof yet.
orderbook
-
Metanet Data storage Curated
Metanet protocol: a directed acyclic graph (DAG) layered on BSV transactions. Nodes are identified by public key and linked to parents via signature, forming content hierarchies with domain-like paths.
Reviewed and listed by hand. No on-chain proof yet.
meta
-
RelayX Other Proven
RelayX transfer and payment protocol used by the RelayX wallet and exchange.
This address proved ownership on chain with a useradd it funded itself.
Proven by its useradd transaction . See its Bitcom namespace .
1LtyME6b5AnMopQrBPLk4FGN8UBuhxKqrn
-
Run Token Curated
Run token and smart contract protocol. Identified by OP_0 OP_RETURN 72756e (hex for "run") envelope prefix.
Reviewed and listed by hand. No on-chain proof yet.
run://.
-
Twetch Data storage Curated
Twetch social media post protocol. OP_RETURN data includes post content, reply references, and payment routing.
Reviewed and listed by hand. No on-chain proof yet.
19nknDdM3ueaAt7nFLFQ3aS3PVHVnJoMmU