Hi Paul,
What’s the thinking behind this version? StartOS do still publish ‘a’ version of Knots SHA256 although I think they said the project is stopped. ( I must be missing something but assume it’s cause LukeD is now 100% concerned with the hard-fork and all things Blake2B.)
So I guess at this stage what is the difference right now and what changes are envisioned on your branch? Is it just config or something more?
Thanks a lot
I have two plans here. One is that this will be the pruned “companion” for folks who want to use the BLAKE2b chain as their primary full node. This may become the preferred default configuration for most users if CSAM lands on the SHA256 chain, BTW.
The other item is that I will be maintaining a fork of Knots on the SHA256 chain which will fit into the “main” slot (where the Start9 one sits today). This will remain up to date with security updates, so folks don’t become vulnerable as pre-RDTS ages. You’ll see a “Bitcoin Knots (SHA256)” show up in my custom registry soon that will be the one that I maintain. This will also be the foundation from which I will be building my “Safe Node” implementation. Bitcoin Knots (SHA256) will remain as a traditional node implementation and a seprate “Safe Node” implementation will be built on top of it (similar to how historically Bitcoin Knots has been built on top of the canonical Bitcoin Core)