You can use mine. Just add my Umbrel app store
Well StartOS community knots is no longer supported as Electrs now only supports core 31
So I guess its time to switch to Paul’s knots SHA256 companion if you want to continue to run that chain.
What do I need to update?
- Bitcoin Knots (SHA256) Companion
- Datum Gateway (SHA256) Companion ( I assume Community Datum wont work with knots companion?
- Electrs with .. Electrs Pruned? ( I don’t want a pruned node however )
- Mempool?
I suspect this was all already asked and answered if someone can link it that would be awesome
Thanks
I was wondering about this as well, seems they’re trying to squeeze the Knots crowd back to Bcore. Paul - do you intend to keep maintaining your software for the SHA256 chain? If someone moved from Electrs to Fulcrum would they need to download the blockchain again?
Yes, despite what my current work might imply, I am in the “stay and fight” camp after the split in the BIP-110 supporters after its failure to activate. The reason for all of the BLAKE2b work is that I want that camp to be as successful as possible. If the SHA256 chain fails in the future (which is more likely than not), I’d like to either have a place to fall back to on the BLAKE2b chain, or if they fail first (also more likely than not) to have hopefully learned something useful along the way about what mistakes they made and to avoid them in a future hard fork.
No, but they would need to re-index (and Fulcrum is much slower at that than electrs, unfortunately, so you’d be looking at 2-3 days typically)
I also mentioned it on another thread, but adding it here in case the two timelines diverge – I will be maintaining a SHA256 fork of Bitcoin Knots that remains updated from Bitcoin Core releases (basically the same work that Luke was doing prior to the hard fork) This will be the foundation of my “Safe Nodes” implementation (the two will be maintained separately, so those who want a more traditional node rather than switching to the new zero-knowledge verification scheme can pick Knots instead of Safe Nodes)
One caveat – if CSAM lands in the blockchain, I will not be testing Bitcoin Knots on mainnet anymore (I do not want that garbage on my computer). I’ll still maintain the codebase, but at that point, it will be advisable to run the future Safe Node implementation which I actually will be fully testing on mainnet. Hopefullly I get it implemented in time (otherwise I will be leaving the SHA256 camp since it will be impossible to run a node at that point without violating my own conscience)