Repository navigation
In the event of a hard fork #353
T-Rex-Apache-Helicopter
started this conversation in
General
Replies: 1 comment
|
I don't know about a hard fork, but right now Knots is NOT updating the blocks past 961633 in the wallet!!! I have no idea what my miners are mining (I suspect NOTHING!) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I posted some of my questions to Luke on NOSTR and as a comment to one of Chris' PRs on the update to the hard fork code from 2017, but this is probably a better place to ask my questions. Worse case scenario and we must hard fork (I saw Chris' post on X), I have a couple questions and requests as a node runner.
First. Which algorithms are being considered? I am not sure if there is a secure algo for gpu and/or cpu mining, but I would prefer to use GPUs I have laying around as opposed to purchasing new non-SHA-256 miners. I'm sick of buying from China as it is. Is this an option?
Second. In the event of a hard fork, do we continue the current chain or revert back to the genesis block? I will likely run a node either way, but I would prefer to revert all the way back and have a clean chain. In the event there is already morally corrupt material on the blockchain, I would not be surprised to see bad actors use it against the true bitcoin chain in the event it competes with their spam chain. I think the downside would be a coin that is worthless in terms of fiat value for several years or decades, but on the upside, it would likely buy years or decades to prepare for the next attack on sound money.
All reactions