You can't verify without a node. Without one, you're trusting someone else, and the whole point of Bitcoin is that you don't have to. Keeping the cost of running a node low enough that ordinary people can do it isn't optional. It's what keeps Bitcoin decentralized.

The response to our launch has been overwhelming. A lot of people are asking good questions: who are the developers, how is this different from Core, why not contribute upstream? We welcome the scrutiny. Bitcoin development should have a high bar, and so should we. More to come.

Fair point on the tags, we're just getting started here.

Building on Core is the point. The most battle-tested codebase doesn't need to be rewritten, it needs a different development process around it. Built-from-scratch implementations serve a different purpose.

Bitcoin is too important to depend on a single implementation. Today we're launching ProductionReady, a 501(c)(3) nonprofit funding a new conservative Bitcoin client — built on Core, focused on stability, security, and sound money. Board: @jimmysong @Excellion Parker Lewis, John W. Ratcliff. https://productionready.org/blog/productionready-launches

Agreed, that's the most important question. We're in conversations with experienced developers now. More to share soon.

Different development process, different policy defaults, different priorities. Same consensus code. Think of it as a check on the direction of development, not a competing protocol.

Every debate about what belongs in a Bitcoin block is really a debate about what Bitcoin is. If it's money, act like it.

Node operators are Bitcoin's final check on power. If they don't like a change, they don't upgrade. That's not a flaw in the system — that's the system working.

Bitcoin has mass adoption by nation-states, trillions in value on the network, and a development process that hasn't scaled to match. More implementations isn't a threat — it's infrastructure.

Different development process, different policy defaults, different priorities. Same consensus code. Think of it as a check on the direction of development, not a competing protocol.