Co-Authoring the Bitcoin Private Whitepaper: Lessons from the Crypto Frontier
In 2018, I co-authored the Bitcoin Private (BTCP) whitepaper — a first-of-its-kind fork-merge of Bitcoin and Zclassic. Here is what that experience taught me about blockchain, privacy, and building in public.

In early 2018, I co-authored the Bitcoin Private whitepaper alongside Jacob Brutman, Giuseppe Stuto, Jon Layton, and Christopher Sulmone. Bitcoin Private (BTCP) was a first-of-its-kind "fork-merge" — combining Bitcoin's security and market awareness with Zclassic's baked-in privacy features.
The project was originally proposed by Rhett Creighton, founder of Zclassic, and quickly grew to over 200 contributors and 20 engineers. The 1:1 airdrop took place on February 28, 2018.
What We Built
Bitcoin Private was not just another altcoin. It was an experiment in combining two blockchain paradigms:
From Bitcoin: The UTXO model, the hash power, the network effects, and the brand recognition. Bitcoin proved that decentralized digital money works. What it did not solve was privacy.
From Zclassic (and by extension, Zcash): zk-SNARKs — zero-knowledge proofs that allow transaction validation without revealing sender, receiver, or amount. Privacy is not a feature; it is a right.
The fork-merge mechanism itself was novel. Rather than forking a single chain, we merged the UTXO sets of two chains into one, creating a new genesis block that honored both communities.
The Whitepaper Process
Writing a cryptocurrency whitepaper is an exercise in translating dense cryptography into accessible prose without sacrificing technical rigor. Our team brought different strengths:
- Cryptographic foundations — the zk-SNARK implementation, proof generation, and verification
- Economic modeling — supply dynamics, mining incentives, and fee structures
- Governance design — how the community would make decisions post-launch
- Technical architecture — block size, transaction throughput, and network topology
My contribution focused on the intersection of enterprise adoption and privacy technology — specifically, why businesses need transaction privacy and how blockchain privacy protocols could serve legitimate business use cases.
What I Learned
1. Privacy Is Not Optional
The argument for financial privacy is not about hiding wrongdoing. It is about competitive intelligence. If every transaction on your blockchain is public, your competitors can see your supplier payments, your customer contracts, and your treasury management in real time. Enterprise blockchain adoption requires privacy by default.
2. Community-Driven Development Is Powerful — and Chaotic
With 200+ contributors and no traditional corporate structure, Bitcoin Private was governed by consensus, reputation, and shared mission. The energy was incredible. The coordination challenges were real. This experience directly informed how I think about open-source project management today.
3. The Technology Matters Less Than the Use Case
BTCP had elegant cryptography. What it lacked was a clear enterprise use case beyond "private Bitcoin." The projects that survived the 2018 crypto winter were the ones with specific, defensible utility. This lesson shaped my approach to every technology evaluation since — start with the problem, not the solution.
The Microsoft Connection
My blockchain work directly feeds into my current advisory practice:
- Azure Confidential Computing — hardware-based privacy for sensitive workloads, conceptually similar to the privacy guarantees we were building in BTCP
- Azure Blockchain Service (now sunset, but the learnings persist) — enterprise blockchain infrastructure
- GitHub — every line of BTCP code lived on GitHub, and the collaboration patterns I learned there inform how I use GitHub for enterprise projects today
Why This Matters for PE
Private equity firms increasingly encounter blockchain-related assets in their portfolio companies. Having actually built blockchain technology — not just read about it — gives me a fundamentally different perspective in diligence. I know what questions to ask, what claims to be skeptical of, and what technical debt looks like in a blockchain codebase.
The whitepaper is still available. The codebase is still open source. And the lessons continue to compound.

