Activation of SegWit v1 The segregated witness soft fork of August 2017 included a versioning field which would allow for future incrementation. Anthony Towns has recently posted an early draft of the proposal for the SegWit v1 upgrade to the mailing list . Although the devil is of course in the details, how could such an upgrade process look like? What are the different upgrade mechanism for the major [v1 - v16] and minor [v1.0 - v1.127] version changes? How is the soft fork signaled? How is the consensus change enforced? Is the v1 change as "contentious" and time consuming as v0 was? What are the tasks of node operators and miners? Thank you in advance for the answer! https://ift.tt/2VrPDpG
Insta-mining problems, how to prevent being outgunned? And difficulty + adjustments I created a new coin to learn something about Bitcoin. I cloned the source code, called it something different, put a new logo on it, nothing major. Then I made some nodes available, and put the source on github. The number of connections (aside from me) to the nodes reflected the number of git clones. I'm sure I had an instamine problem, where the hashrate went up and the difficulty went up so that I wasn't able to catch up quick enough and outgun the miners. Even when I did point significant hashpower at my new pool, I just made the difficulty go way up. I mined blocks, but they were orphaned. So was I mining on a different chain? i.e. the "wrong" one that broke off from the original that I wanted to catch up with? There have been some ideas on preventing an instamine. One is to mine a large number of blocks, and before putting out the source code and making it available for anyone...
Comments
Post a Comment