https://teapawt.org/t.co/sl7R94UT7L — So You Want To Fork Bitcoin Too™️
Joined November 2017
- Tweets150
- Following0
- Followers449
- Likes44
Feel cold and lonely in the dark wintry bear market? Why don't you make a fork! You can pretend it's bitcoin, even if it totally isn't. 40% off this week only! Coupon code "MyBatteryIsLowAndItsGettingDark"
#FGB35: Fixes issue where nodes would sometimes unwittingly become Bitcoin maximalists, adamantly refusing to fork despite consensus rule changes.
If you did not customise the POW target spacing / timespan, the latest build reverts a lot of the logic required to handle this particular feature for builds that do not need it.
#FGB30: An update that fixes several issues related to version bits, and BIP9 activation, was released today.
Update is recommended but currently experimental.
Note that you may have to click update twice, once after entering a new password, and once for the BIP 9 fix choice.
Update: the latest build is reportedly causing rejections of post-fork blocks. Looking into workaround, but this may take a bit as it may be different depending on when you forked. For now, stay on the current version.
#FGB28: Early block forks would not properly activate pre-existing softforks.
The intention was to set the activation threshold to 95/100 (95%) but instead it was set to 100/95 (105%).
People often get confused about the "sync time". This is happening because your coin is forking bitcoin (even if you fork at block 1, this is still the case under the hood), and the client has to assume the headers you receive are valid, until the actual fork.
So I created my own #shitcoin and called it SHiZcoin (SHZ). I wanted to start from block 1 with slightly different rules. 5 minute blocks, 100 coin reward to start, halving every two years. When I run the windows client it says them I'm 9 years behind. WTF!
A fork that forks at block 1 has the same issues as above, although there is now a race condition in play as well (the time to fork activation vs the received block headers from peers).
FGB27: Realized that forkgen builds currently use the default bech32 hrp (human readable part) for bech32 native addresses. As of build #27, forkgen will now use the lowercase, cleaned up coin ticker name. E.g. for "Bitcoin Cobalt Extreme (BCX)" the bech32 hrp is "bcx".