@Anton__BTC@venorusprime Before the time exchanges will have to prepare and alert their users about a potential upcoming spilt.
I’m hoping that that will be the time users wake up and start asking the right questions.
@saifedean Don't gaf about florida man.
BIP-110 activation and miner decentralization are the only things in Bitcoin worthy of mention right now.
Otherwise forget about the bitcoin standard, welcome to forever fiat slavery.
@LukeDanielsan@venorusprime@mattkratter If plebs get priced out by spam and can’t get their transactions mined they have no incentive to run a node, and will leave the network.
It’s plebs who make Bitcoin decentralised, not spammers and suits.
@getnirvati@jimmysong@ProductionReady Yes. Another good initiative.
If big names like @jimmysong and @Excellion want to make it count:
* Get behind this or another solid looking project like @BtcCommons, OR
* Create something better from scratch
Just don’t think forking Core is anything worth writing home about.
Bitcoin has had forks. It has not had alternative implementations. Not real ones. And forks don't solve the problem.
A Core fork is not an alternative implementation. It inherits everything. The technical debt, the undocumented behavior, the monolithic architecture. Change the team, keep the structure, and the structure wins. That's not an exit from the problem. That's the same castle with a different flag.
Node diversity matters. But nodes don't mine blocks. Without a value proposition for miners, implementation diversity remains a preference signal rather than a security guarantee. No Core fork has given miners a reason to switch.
The hardening problem is real, but the solution isn't forking Core. It's building from an independent mathematical specification and proving consensus validity through fuzzing and differential testing across the full chain history. That's verifiable safety. Everything else is institutional trust with better branding.
That's why we're building. @BtcCommons
@UglyOldGoat1@jimmysong@ProductionReady 100%. What might be needed is definitive protocol documentation defining what Bitcoin actually is.
But even if you had this, you only know for sure it’s correct by implementing it.
@1914ad@jimmysong@ProductionReady I’m not saying it’s easy.
Bitcoin transactions are just binary data structures. The Bitcoin protocol (explicitly or implicitly by current implantation) says how to generate propagate and validate them.
Bitcoin is a generational project. It needs another way of doing this.
@UglyOldGoat1@jimmysong@ProductionReady Bitcoin is a protocol. A Bitcoin client is an implementation of the protocol.
The Core / Knots source code is not the protocol, but we’re treating it as if it is.
@1914ad Luke may not win a popularity contest but he’s still the safest pair of hands in Bitcoin. Knots is already doing about as good a job as possible of being what Core should be.
A high profile new node implementation with a fundraising foundation needs to offer something more.