Forkgen Tech

@bitcoin1776 You’re good, sir.

@ForkGenTech Is there any interest in allowing a final download of the latest release, version? I think last one I did was v38 - not sure if any significant changes, updates after that. Thanks for all the help!

So long, and thanks for all the fish. forkgen.tech

@alpacasw @Ragnarly @wtogami Splitting all forks is necessary as any other decision would be discriminatory. forkgen.tech/faq

@Ragnarly @wtogami I'm not sure it's that simple, they still could get sued for not giving customers forkcoins out without clear policies.

History: The 2x'ers were confusing exchanges calling it an "upgrade" while the majority of technical experts were warning it would be negligent to fork without replay protection. Calamity was imminent as many had done NO MANUAL REPLAY PREPARATION, ensuring accounting disaster.

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"

@SauceryCoin @Moon__Rekt @pierre_rochard @bitstein @MustStopMurad @stephanlivera @danheld @BitcoinTina @saifedean @MartyBent We hit 0.4% of this goal!

@Moon__Rekt @pierre_rochard @bitstein @MustStopMurad @stephanlivera @danheld @BitcoinTina @saifedean @MartyBent If forks/alts dilute bitcoin why dont you go make 1000000 of them?

What are perfect “gotcha questions” to ask bitcoin skeptics? @pierre_rochard @bitstein @MustStopMurad @stephanlivera @danheld @BitcoinTina @saifedean @MartyBent

#FGB35: Fixes issue where nodes would sometimes unwittingly become Bitcoin maximalists, adamantly refusing to fork despite consensus rule changes.

In other words, your code will have less changes which means less chances for it to break.

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.

See the full report on this here: forkgen.tech/incident1

Note that you may have to click update twice, once after entering a new password, and once for the BIP 9 fix choice.

#FGB30: An update that fixes several issues related to version bits, and BIP9 activation, was released today. Update is recommended but currently experimental.

@lightninginabox @DwConan @YassineEraman I once tried using an old USB miner and it worked fine.

@DwConan @YassineEraman @ForkGenTech How's for fork going? I called mine SHiZcoin, symbol SHZ. Have managed to mine with my CPU haven't figured out how to mine it with GPU yet.

Looks like the BCH folks are finally realizing that true decentralization can only be obtained through massive amounts of contentious hard forks over an extended period of time. About time I say! To celebrate, here's a 50% off coupon that lasts throughout the week: FORKTIME

@MayorOfBitcoin I don't believe you will need custom code for each version, but I am going to make doubly sure I don't push out a broken fix again, so hold on for a bit.

@ForkGenTech Something like that means this version would require custom code each time :( ... So I do not know if it's possible. HOWEVER ... my experience will be the same as anyone else who forked after ~500,000 blocks, and had used v15 to generate new blocks (we'd all be in the same boat).

#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%).

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.

@MayorOfBitcoin It’s fixable by moving the activations I believe, but the fix may be different depending on when the fork happened. What block did you fork?

@ForkGenTech "getblockchaininfo" now says: "difficulty": 1 "bip9_softforks": - "status": "active", "segwit": - "status": "active", I feel I'm in for a headache :/

@MayorOfBitcoin Thanks for the heads up! Investigating a fix.

@ForkGenTech I typed "getblockchaininfo" on v27 and got: "difficulty": 1.876556996821579 "bip9_softforks": - "possible": false "segwit": - "possible": false I then upgraded to v28 and now I've rejected all blocks since fork (about 6,000).