How do I install the Bitcoin L2 Counterparty skill?

Run npx skillmds@latest add claude-dev-suite/bitcoin-l2-counterparty in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bitcoin L2 Counterparty safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bitcoin L2 Counterparty?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bitcoin L2 Counterparty free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bitcoin L2 Counterparty?

claude-dev-suite (@claude-dev-suite) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bitcoin L2 Counterparty by claude-dev-suite

Name: Bitcoin L2 Counterparty
Rating: 4.5 (4 reviews)
Author: claude-dev-suite

Bitcoin L2 Counterparty

Counterparty: legacy Bitcoin meta-protocol (2014) for assets, DEX, betting using OP_RETURN. Largely historic; still alive with niche use. USE WHEN: dealing with legacy Counterparty assets, understanding pre-Ordinals asset ecosystem, evaluating obsolete patterns.

claude-dev-suite Updated Sep 8, 2026 28 repo stars

File contents

Counterparty (XCP)

Counterparty is one of Bitcoin's earliest meta-protocols (2014). It embeds asset / smart-contract metadata in Bitcoin transactions via OP_RETURN, enabling token issuance, DEX trades, betting, and asset management.

Mechanics

All Counterparty data is embedded in OP_RETURN outputs of Bitcoin txs.
A separate Counterparty parser reads Bitcoin blockchain, extracts Counterparty events, maintains state.
Native token: XCP (used for issuance fees, betting).
Asset issuance: lock 1 XCP to issue named tokens.

Major past events

Rare Pepes (2016-2017): NFT-precursor on Counterparty (long before Ordinals).
SaruTobi (mobile game with XCP economy).
PEPECASH and other community tokens.

Status

Network is still operational.
Activity is dramatically lower than 2014-2017 peak.
Most users have migrated to Ethereum / Stacks for new asset issuance.
Ordinals + Runes effectively replaced Counterparty for new "Bitcoin native asset" use cases (with much higher activity).

Why mostly historic

Pre-SegWit / Pre-Taproot — fees on OP_RETURN-only txs are not competitive.
No DEX innovation since 2017.
No major dev-team activity (occasional patch releases).
Newer protocols (Stacks, Liquid, Taproot Assets, RGB) provide better UX + more functionality.

Architecture

Counterparty federated server: maintains the parsed state, answers queries.
counterparty-cli — interact with the network.
Counterwallet — historical web wallet (still functional).

Asset model

Numerical asset names (anyone-can-issue) and named assets (1 XCP fee, owner-controlled).
Subassets (MAIN.SUB) supported.
Asset transfers, issuances, callbacks via Counterparty txs.

Use cases (current, niche)

Rare Pepe collection trading.
Legacy XCP-based games.
Historical preservation — early-NFT history runs through Counterparty.

Compared to Ordinals

Aspect	Counterparty	Ordinals
Year	2014	2023
Storage	OP_RETURN	Inscriptions in witness
Token spec	Native	BRC-20 (overlay)
Active use	Niche	Very active
New issuance	Rare	Constant

---name: bitcoin-l2-counterpartydescription: Counterparty: legacy Bitcoin meta-protocol (2014) for assets, DEX, betting using OP_RETURN. Largely historic; still alive with niche use. USE WHEN: dealing with legacy Counterparty assets, understanding pre-Ordinals asset ecosystem, evaluating obsolete patterns.---# Counterparty (XCP)Counterparty is one of Bitcoin's earliest meta-protocols (2014). Itembeds asset / smart-contract metadata in Bitcoin transactions via`OP_RETURN`, enabling token issuance, DEX trades, betting, andasset management.## Mechanics- All Counterparty data is embedded in `OP_RETURN` outputs of Bitcoin txs.- A separate Counterparty parser reads Bitcoin blockchain, extracts Counterparty events, maintains state.- Native token: **XCP** (used for issuance fees, betting).- Asset issuance: lock 1 XCP to issue named tokens.## Major past events- **Rare Pepes** (2016-2017): NFT-precursor on Counterparty (long before Ordinals).- **SaruTobi** (mobile game with XCP economy).- **PEPECASH** and other community tokens.## Status- Network is still operational.- Activity is **dramatically lower** than 2014-2017 peak.- Most users have migrated to Ethereum / Stacks for new asset issuance.- Ordinals + Runes effectively replaced Counterparty for new "Bitcoin native asset" use cases (with much higher activity).## Why mostly historic- Pre-SegWit / Pre-Taproot — fees on `OP_RETURN`-only txs are not competitive.- No DEX innovation since 2017.- No major dev-team activity (occasional patch releases).- Newer protocols (Stacks, Liquid, Taproot Assets, RGB) provide better UX + more functionality.## Architecture- **Counterparty federated server**: maintains the parsed state, answers queries.- **counterparty-cli** — interact with the network.- **Counterwallet** — historical web wallet (still functional).## Asset model- Numerical asset names (anyone-can-issue) and named assets (1 XCP fee, owner-controlled).- Subassets (`MAIN.SUB`) supported.- Asset transfers, issuances, callbacks via Counterparty txs.## Use cases (current, niche)- **Rare Pepe collection trading**.- **Legacy XCP-based games**.- **Historical preservation** — early-NFT history runs through Counterparty.## Compared to Ordinals| Aspect | Counterparty | Ordinals ||--------|--------------|----------|| Year | 2014 | 2023 || Storage | OP_RETURN | Inscriptions in witness || Token spec | Native | BRC-20 (overlay) || Active use | Niche | Very active || New issuance | Rare | Constant |## See also- [../metaprotocols/ordinals/SKILL.md](../../metaprotocols/ordinals/SKILL.md)- [stacks/SKILL.md](../stacks/SKILL.md)- [liquid/SKILL.md](../liquid/SKILL.md)

Frequently asked questions