@maciejsoltysiak Hi @maciejsoltysiak - development is temporarily paused because of other competing priorities, but we're hoping to make progress later this year. The code got too complicated around IBD sync, especially for pruned nodes, so we're planning to refactor towards greater simplicity.
@jimmysong We built a node implementation with Claude in a couple weeks. Our minds were similarly blown.
The community may finally have the tools we need to produce a hundred different implementations, with none controlling a majority of the network.
https://t.co/R4DhJqZ7oq
@michelleweekley We believe no single implementation should control a majority of nodes, just like no single mining pool should control a majority of global hashrate.
The solution is a hundred protocol implementations, all sharing consensus, each representing a small minority of node runners.
@SatsScholar A single centralized implementation controlling a majority of the network is a threat to Bitcoin; same as a single mining pool with a majority of global hashrate.
The solution is anarchy not governance - a hundred implementations - each representing a minority of the network.
@CryptoJiven@bensig No single implementation should control a majority of nodes; just like no single mining pool should control a majority of global hashrate. Core is a centralized threat to the decentralized protocol.
@no_coinor@wJ3Hs5c4hKajSnk@ClaudeCodeLog We have Max. We hit limits all the time with Opus 4.5 w/Thinking ... bro. It was nice when they gave 2x limit over the holidays.
@wJ3Hs5c4hKajSnk@ClaudeCodeLog Usage limits reset every few hours. If you're using Opus 4.5, especially with Thinking enabled, hitting your limit after 2 hours is a reasonable expectation.
If you want more usage before hitting the limit, switch back to Sonnet 4.5 and disable Thinking.
LOL @ legal threat 🤣
@julianhosp Whoever gets the most global hashrate wins.
This moat will never be crossed by another project, regardless of technical fundamentals.
It's already game over for altcoins. Bitcoin won a decade ago.
https://t.co/JmaPwYwgwB
@trq212 Started earlier in December and still have a long way to go, but have been constantly amazed by Claude Code (Opus 4.5 w/Thinking) while working on https://t.co/JS3rx8bNxW
This weekend we're focused on performance of Initial Block Download sync with Pruning. After dozens of iterations, we just validated past the First Halving at a current rate of ~20 blocks per second. 🎉
We think node runners experiencing a delightful first sync is important.
@nic_carter@DPGSpurs The elephant in the room is that Bitcoin development itself is not decentralized. Even Core's primary rival is just an opinionated spinoff of Core maintained by a Core contributor.
Today we're working on Initial Block Download (IBD) optimization, somewhere between Bitcoin PIzza Day and P2SH Activates milestones. Balancing swiftness with thoroughness as we sync.
Completing this phase of development will be a significant milestone for Bitcoin Echo. 😎
Headers-first initial sync is happening, with our GUI showing details like a progress bar and Bitcoin historical milestones as we prepare to validate the full chain for the first time.