We're Not Trying to Build a Better Bitcoin
An outside review of this project named a specific failure pattern and put it bluntly: "You want to improve on Bitcoin by:" and then four bullets, "Adding identity", "Adding smart contracts", "Adding governance", "Making it 'fair'". Its verdict was not soft: "Bitcoin's strength IS its simplicity and immutability. Every 'Bitcoin 2.0' has failed because they tried to 'fix' what wasn't broken." And it had a specific recommendation instead: "Your approach of building ON Bitcoin (Lightning, Stacks) is smarter than building your own chain." That critique is stated here at full strength because weakening it would be dishonest.
Grant the critique first
The graveyard the critique is pointing at is real, and there is no honest version of this page that pretends otherwise. Bitcoin's minimalism (a base layer that does one thing, moves value, and refuses to be extended at the protocol level) is not an accident or a limitation someone forgot to lift. It is a deliberately hard-won design property, defended for over a decade against pressure to add exactly the features the critique lists. Every "Bitcoin 2.0" project that tried to bolt smart contracts, governance, or an identity layer onto that model as an afterthought has, in fact, mostly failed or faded, not because the additions were poorly coded, but because a base layer optimized for simplicity and immutability actively resists being turned into something else. That pattern is well documented and this page grants it without qualification.
The trap has a specific shape, and Solidus isn't in it
Look closely at what the critique's own list describes: a project trying to make one chain do four different jobs, payments, programmability, governance, and a fairness property, all at once, on top of Bitcoin's architecture, which was never designed to carry any of the four. That is the actual shape of the trap: general-purpose ambition grafted onto a single-purpose base layer. It is not "building a new chain is always the Better Bitcoin trap." It is "trying to make one chain do everything is."
Solidus is not attempting that. It is not adding smart contracts, governance, or a fairness mechanism to anything, Bitcoin or otherwise. It has one job: an identity-native chain, where a decentralized identifier and a verifiable credential are first-class objects at the consensus layer, and where value transfer is deliberately kept separate from identity. A registered identity anchor cannot hold or move value, and that separation is enforced as a consensus rule, not a suggestion. That is a single-purpose design answering a single-purpose critique's target with a different shape, not a rebuttal of the critique's logic.
What Solidus actually is: composed, not invented
The honest description of what's underneath that single job is not "a new blockchain philosophy", it's a bill of materials. Solidus composes roughly forty-four existing open standards and cryptographic primitives, W3C's DID and Verifiable Credential specifications, IETF's SD-JWT VC, two decades of published cryptography, DIF's protocols, ISO's mobile-document formats, and contributes no original primitive of its own. The closest thing to one, Proof-of-Identity, is a validator-eligibility rule rather than a new consensus algorithm, and even the phrase predates this project by roughly a decade. Ordinary Byzantine agreement underneath is plain HotStuff BFT, borrowed research throughout. The full inventory, every composed standard, credited by name, lives at /composition; this page won't re-derive it, because the point here isn't the count, it's that the design instinct behind it is the opposite of "improve Bitcoin by adding four things." It's "borrow forty-four things and narrow one of them."
Why not build on Bitcoin instead, conceding the recommendation has real merit
The critique's alternative, build on Bitcoin via Lightning or Stacks rather than a separate chain, is not a weak suggestion. Lightning is a proven, live payment layer; Stacks is a real, running smart-contract layer anchored to Bitcoin's security. Either would have inherited a security budget and existing liquidity that a new chain has to earn from nothing, and a new chain earning that trust is exactly the unproven part of this bet, which this page is not going to round up into proof it worked.
The specific reason Solidus didn't take that path: the identity guarantees it wants, DID/value decoupling enforced by the executor, a validator-eligibility rule bound to verified identity rather than capital alone, need to be consensus-level rules, checked by every validator on every block, not an application built on top of someone else's base layer where those guarantees would be advisory at best. That is an architectural bet about where identity-native rules need to live, stated as a bet. It is not evidence the bet was right.
What this leaves open
The critique's Bitcoin-2.0 pattern is real, and it is not being denied here, only shown to describe a different kind of project than the one Solidus built. What remains unproven is the harder question: whether a single-purpose identity-native chain, forgoing Bitcoin's liquidity and security budget for consensus-level identity guarantees, was worth the trade. That verdict isn't in. For the rest of this critique, scope, cold start, biometric verification, token design, and the uncomfortable comparison to Worldcoin, Civic, and Solid, see the hub page for this track.