Counterparty.io

Counterparty Developer Timeline and Asset Timeline (2014-2024)

New release! Counterparty Core v11.0.4! Much faster node startup / shutdown time; less memory consumption + DB connection management; bugfixes too

Horizon Wallet 2.0 just dropped.🚀 Complete redesign, smart token swaps, deep Horizon Market integration. Plus a whole lot more. Your wallet just got way smarter. Go check it out. 👇

Another big release! Horizon Wallet 2.0 is a modern Chrome extension that integrates deeply with Horizon Market (@hznmarket) and offers a *super* friendly interface for swapping Counterparty assets with BTC and other Counterparty assets.

GIVEAWAY TIME! This Bitcoin Stamp by @mikeinspace honors the very first blockchain spammer: Satoshi Nakamoto! Like, Retweet and Follow @hznmarket for your chance to win. Random draw will take place on October 1st. horizon.market/assets/A301200…

I'm proposing the XCP-420 Standard for Fairmints • 10M supply • 4.2M soft cap • 0.1 XCP burned per mint • 35 mints max/address Fairminter refunds XCP if it fails to "bond". Burns XCP if it succeeds. All enforced at protocol level. 🔥 The homepage of XCP[.]FUN is setup to feature them.

✨ Counterparty Core v11.0.2 Lots of bugfixes and a node API improvements! Plus Bitcoin Core cookie authentication, and a new Alpine-based Docker image. Check it out! github.com/CounterpartyXC…

Next @CounterpartyXCP community Twitter space with @agkrellenstein is on for August 29th at 8am Central.

The Counterparty DEX on Horizon.Market has just been upgraded to full feature support. ⚡️

Atomic swaps on Counterparty are a game-changer in terms of ease-of-use and security! But a lot of people don't quite understand how simple they are to create on Horizon Market. Have a look at the following walk-thru -- no need to feel intimidated! 😅

GM Pham! 🚀 We’re building a DEX for Counterparty tokens powered by the Internet Computer. Thanks to the support of the @dfinity Developer Grant, we're bridging Bitcoin native assets with ICP. More updates coming soon, but here’s a first look at what we’re building 👇

FULL EPISODE WITH CO-FOUNDER & LEAD MAINTAINER OF COUNTERPARTY @AGKRELLENSTEIN DROPS TOMORROW AT 2PM PST 🔥

Discussing the history and future of Counterparty with Adam Krellenstein youtu.be/CgIM-0xnwhQ?si… via @YouTube

I'm excited to share my recent interview with @agkrellenstein , co-founder of @CounterpartyXCP . We discuss his intro to bitcoin, the inspiration and creation of counterparty, his decision to leave, and his return. We also discuss some of the community concerns and more.

We finished upgrading to @CounterpartyXCP v11 🧭 Reflections on v11.0.0 and the Path Forward for Counterparty Governance Over the past few weeks, we’ve seen some intense discussion around the introduction of CBOR encoding in v11.0.0 and the subsequent v11.0.1 hotfix. This post is not meant to assign blame, but rather to reflect on what happened and explore how we can improve the process moving forward as a protocol and as a community. 🔍 What Happened The shift to CBOR encoding was technically sound and offers real benefits (better compatibility with Taproot, cleaner code, and reduced fees for larger transactions). However, it introduced a breaking change that affected client-side composers and tooling. The change was released in v11.0.0 without broader visibility outside GitHub PRs. There was no CIP or formal public comment period. Several developers (JDog, Loon3, MasterOnChain) raised concerns about compatibility, rollout speed, and testing, especially with short notice before activation. v11.0.1 was eventually released to address a bug and reintroduce partial backwards compatibility a positive step, though it happened reactively rather than proactively. 🧠 What We Can Learn This situation reveals a gap between technical progress and community governance: Community members want to contribute but are often unaware of changes until after they’re implemented. Breaking changes, even minor-seeming ones, require a clear communication pipeline especially for protocols with many independent implementations. Personal tone and interpersonal dynamics can derail productive dialogue, even when both sides raise valid points. 🛠 Suggestions for a Healthier Process To help avoid future misalignment, I propose the following steps: All protocol-breaking changes should go through a formal CIP process, with: Clear labeling (e.g., [Breaking Change], [Compatibility Impact]). A discussion window in public forums like counterparty-talk or a dedicated governance Telegram/Discord. A changelog summary that’s shared across key community channels (XCP dev chat, Telegram, etc). Version activation windows should allow for migration, especially when tools need updates. A 4–6 week runway from final release to activation would help. Document encoding formats formally, even if the reference is the code. Developers appreciate even minimal guidance when dealing with critical infrastructure. Create a neutral community steering group (possibly tied to the foundation) to help review CIPs, moderate tone, and guide long-term strategy. 🤝 A Final Word Everyone involved here, whether core devs or community contributors, deeply cares about the project. Let’s use this moment not to fracture further, but to strengthen our processes and create a more collaborative environment. Counterparty was born as a community protocol, and if it is to thrive in its second decade, transparent governance and inclusive development will be more important than ever.

Less than 1 week to go until Taproot envelope data encoding activates on Counterparty. Block 902,000. How long before the first Counterparty 4Megger? 👀

🤘**Announcing Counterparty Core v11.0.1**🤘 Note: This release is a protocol upgrade. All nodes must upgrade by block 902000 (in ~1 week). t.me/counterpartyge…

As part of the Counterparty Core v11.0.0 release, we changed the transaction encoding scheme to use the CBOR standard. Some community members have expressed dissatisfaction that this would break compatibility with existing client-side transaction construction libraries. We're reviewing the situation and figuring out the best path forward. Please see the ongoing discussion here: #issuecomment-2923607500" target="_blank" rel="nofollow noopener">github.com/CounterpartyXC…

Here's where I started the first OP_RETURN war in 2014 by calling the Bitcoin Core devs a "cabal". Then they were being too conservative. Now it's too little too late. #msg5793103" target="_blank" rel="nofollow noopener">bitcointalk.org/index.php?topi…

Counterparty did this in 2014... only it went the other way, and we got OP_RETURN shrunk from 80 bytes to 40 bytes in what has now been proven to be an ill-fated attempt to prevent the community from building on top of Bitcoin.