Timelines are still being worked out. We want to get this right rather than rush it because that's the whole point of a conservative implementation. We have a few ideas, though, so stay tuned.
We're also aware of the other implementations you've mentioned, but we feel building on Core gives us the most battle-tested starting point and lets us differentiate on process and defaults rather than architecture. Regardless, more implementations are a good thing.
Multiple implementations are good for protocol health. Every serious software stack with real stakes eventually gets a second client. Ethereum has four. Bitcoin treating this as controversial in 2026 is kind of funny.
Do you all have a roadmap or a timeline along which you expect to see development of this implementation?
Also, did you consider trying to put resources towards Hornet Node or Libbitcoin or perhaps libbitcoinkernal?
Timelines are still being worked out. We want to get this right rather than rush it because that's the whole point of a conservative implementation. We have a few ideas, though, so stay tuned.
We're also aware of the other implementations you've mentioned, but we feel building on Core gives us the most battle-tested starting point and lets us differentiate on process and defaults rather than architecture. Regardless, more implementations are a good thing.
Thanks for the response. It sounds like a very cool initiative. I'll be excited to hear about further developments!
So Knots, but without the autistic psycho religious dictator?
Multiple implementations are good for protocol health. Every serious software stack with real stakes eventually gets a second client. Ethereum has four. Bitcoin treating this as controversial in 2026 is kind of funny.