Jun 7, 2025

Software changes over time -- personally, I wouldn't speculate on this. That may be true for current rates, but I expect that will change in time before any kind of crisis point.

I think it has less to do with the chain size and more to do with the utxoset size. Given that, I'd say it depends mostly on how bad the spam attacks get

Yeah it makes sense it's pretty difficult to forecast

Core kinda cheats by not validating most of the chain during IBD though. So given that weaker security model it could last quite a lot longer

Yeah that's what I worry about

Bitcoin takes off, gets captured by institutions, and fights the plebs trying to fully validate

Fortunately, libbitcoin is here for a reason, and if you've ever tried building something on Bitcoin (core), core is a large web and doesn't play that well (imho).

Core is a sinking ship. Glad libbitcoin exists 🧡

This is an incredible weak point. I wish more of the op_return/knots energy would be directed to development here. Is there a roadmap for V4 release?

No, not officially a roadmap (that I know of), but I believe the v4 node is on track for a release by the end of the year. It's been completely overhauled so many times since v3, so it's hard to track exactly, but it appears we're narrowing the functionality down

Bring it? 🤷‍♂️

I'm on both teams haha Knots+libbitcoin=win

Yes! I'm not as good with C++, but maybe I can help with documentation or developer relations

If they don’t rearchitect it then eventually it won’t be able to validate. They resisted doing this forever, instead working toward mechanisms that weaken the security model by not validating. But now that we have shown that it’s a software issue and not a Bitcoin issue, they have been forced to face these design flaws. @neillm is right, someone will eventually do this work at some point. They are working on a technique that allows someone to download the uxto state produced by someone else, and assume valid faster by relying on this. But of course this presumes someone can actually produce it. And it assumes there’s a reasonably trustworthy source for it. Then they will eventually do the significant amount of work required to not only validate concurrently, but do so at full capacity. This means making the network stack asynchronous, and creating a massively concurrent store.

Hi @neillm , I'm a designer (with a background in product management/ business analysis), currently helping knots with branding and to improve their UX. I want to help here too. If anyone building wants input on anything, ping me - would be glad to help