Counterparty launched on January 2, 2014, in an announcement on the Bitcoin Talk forum by Adam Krellenstein, Evan Wagner, and Robby Dermody. The protocol has been continuously running on Bitcoin since then. It has issued and transferred non-fungible assets the entire time. By any honest reading of the historical record, it is the original Bitcoin NFT protocol.

Most popular NFT histories skip past Counterparty entirely or mention it as a footnote. The reasons are partly cultural (the Ethereum-centric NFT writers of 2021 didn't know it existed), partly architectural (Counterparty is a metaprotocol, which feels less "native" to Bitcoin maximalists), and partly timing (the Rare Pepe community that built Counterparty's most-cited use case got swallowed by the Pepe-as-hate-symbol political moment in late 2016). None of those reasons changes the underlying fact: Counterparty was there first, by years.

The metaprotocol approach

Counterparty does not have its own blockchain. It extends Bitcoin by encoding protocol messages inside Bitcoin transactions that regular Bitcoin nodes ignore but Counterparty nodes parse. From the Counterparty whitepaper, the architecture treats the Bitcoin blockchain as a store for new protocol messages and derives Counterparty's state machine from those messages.

Concretely, Counterparty uses Bitcoin's OP_RETURN output field to embed encoded protocol data. When you issue a Counterparty asset, you broadcast a Bitcoin transaction with an OP_RETURN output containing the encoded issuance message. Bitcoin miners include that transaction in a block; Bitcoin full nodes validate it as a perfectly legal Bitcoin transaction; Counterparty nodes additionally parse the embedded data and record the asset's existence.

This has a specific consequence that matters: Counterparty inherits Bitcoin's security model directly. Every Counterparty transaction is a Bitcoin transaction. The complete history of Counterparty operations is secured by Bitcoin's proof-of-work. There is no separate validator set to bribe, no Counterparty-specific consensus to attack. To rewrite Counterparty's history, you have to rewrite Bitcoin's history.

XCP and proof of burn

XCP is the protocol's native currency. It exists because Bitcoin can't directly serve as a working currency for Counterparty operations. Bitcoin miners aren't aware of Counterparty, so they price transactions by byte size alone. XCP is used wherever Counterparty itself needs to charge for something, most notably named asset issuances (which is what gives a Counterparty asset a human-readable name like HOMERPEPE rather than a numeric identifier).

The XCP distribution was unusual. Instead of an ICO, Counterparty used proof of burn. For a one-month window in early 2014, users sent Bitcoin to a verifiably unspendable address and received XCP in return at a fixed exchange rate. Roughly 2,140 BTC were burned in the process. The XCP supply is fixed at that distribution; there is no inflation, no token unlock schedule, no treasury allocation.

This is one of the cleaner token launches in crypto history. The team didn't keep an allocation. The burn was on-chain and verifiable. No new XCP can be created beyond what came out of the burn window. By 2026 standards, the design looks like a curio; in 2014 it was a deliberate response to the early ICO scams already happening in the space.

What the protocol actually supports

Counterparty's feature set is richer than most modern Bitcoin NFT protocols:

  • Asset issuance. Named (with XCP fee) or numeric (without). Supply set at issuance, fixed thereafter unless explicitly mintable.
  • Transfers. Standard send between any two Bitcoin addresses, with Counterparty parsing the encoded transfer message.
  • Decentralized exchange. An on-chain DEX that matches orders entirely through Bitcoin transactions. Live since 2014. Any asset can be paired against any other.
  • Dividends. Native support for distributing XCP, BTC, or any Counterparty asset to all holders of a given asset proportionally. This is what powered the original PEPECASH airdrop to early Rare Pepe holders.
  • Asset destruction. Verifiable burn of tokens by sending to an unspendable address.
  • Broadcasts. Signed messages embedded in transactions, originally used for prediction-market oracle feeds.
  • Callbacks. Time-locked redemptions, used historically for asset issuances with redemption schedules.

By comparison, Ordinals supports inscription and transfer; that's it. Everything else (BRC-20 tokens, marketplaces, naming) is layered on top. Counterparty has all of this native to the protocol.

What got built on Counterparty

The most-recognized Counterparty project is the Rare Pepe directory, which emerged in September 2016 and grew into the first significant cryptoart movement on any chain. The Rare Pepe community curated 36 series of cards, deployed a custom marketplace currency (PEPECASH), and built a wallet that handled the underlying Counterparty transactions. Major historical pieces like the Artnome January 2018 article on the birth of CryptoArt credit Counterparty as the origin of the entire NFT category.

Spells of Genesis, a trading card game, used Counterparty for its in-game asset issuance starting in 2015. The cards are on-chain Counterparty assets, the game is played outside of Bitcoin, and the assets are tradeable independently of the game. This was an early example of the "true digital ownership" model that NFT marketing on Ethereum would later popularize.

Other Counterparty projects across the decade include early prediction markets, decentralized betting, and assorted experimental token launches. The protocol's ability to support these without modification is part of what gives it longevity.

Why most NFT histories skip Counterparty

Three reasons, mostly.

First, the Ethereum-centric framing of NFT history that took hold in 2021 was written by people who came in during the boom. They learned the Ethereum side first because that's where the action was that year. Counterparty was a footnote in their reading because it was a footnote in their experience.

Second, the Pepe-as-hate-symbol controversy that landed in late September 2016, three days after the first Rare Pepe was minted, made mainstream press coverage of Counterparty awkward for years. CryptoPunks in 2017 carried none of that baggage, and the path of least resistance for journalists writing about NFT origins was to start the story with the Punks.

Third, the metaprotocol design feels alien to people coming from Ethereum-style smart contract chains. There's no contract to read on Etherscan. There's no transparent ABI. You have to run a Counterparty node (or trust an indexer) to verify state. For a generation of NFT users used to MetaMask and OpenSea, this is friction that Ordinals and the modern Bitcoin NFT marketplaces have only partly removed.

Why Counterparty still matters in 2026

The Rare Pepe directory still trades. Spells of Genesis assets still trade. Modern Bitcoin NFT marketplaces have integrated Counterparty support alongside Ordinals, so a single bitcoin nft marketplace can list assets from both protocols on a unified interface. Historical Counterparty assets command premiums that reflect their documented provenance.

For collectors interested in the longest-lived on-chain art, Counterparty is the answer. For developers building on Bitcoin, it's a working example of how metaprotocol design can deliver richer functionality than colored-coin approaches. For NFT historians, it's the foundation that every later protocol implicitly or explicitly built on.

Twelve years in. Same chain. Same protocol. Same assets, still tradeable. That's the case for Counterparty in 2026, and it's a stronger case than most of the protocols that have come and gone in the intervening years.