Quote from: Chicago on November 14, 2018, 01:21:49 AM

Quote from: number435398 on November 14, 2018, 01:12:14 AM

Have you been periodically bridging your fork with the explorer to keep it in sync?

Hi number435398,

As reported on October 16th in this thread:

Quote from: Chicago on October 16, 2018, 07:16:31 AM

This client is a clean break from the v0.8.6.1 network.
There was approximately a 12 hour difference between the snapshot at height 1314626 and this public release.

If I picked the wrong fork of the chain, let me know and we can do this experiment again with another chain.
I selected this chain because it is the one which His Holy Noodliness's code identifies with in the peer swarm.

There have been no reports of being on a wrong fork of the chain and the hash at block 1314626 for the snapshot matched the explorer.

The Linux binary is here.
The Windows binary is here.
The bootstrap.dat is here.

addnode=23.253.205.134
addnode=[2001:4801:7825:102:be76:4eff:fe10:3d29]

Best Regards,
-Chicago

I mean since then. If you take the blockchain folder for your fork and open another wallet that is on the main network (explorer), then they would sync up. Then if the explorer's chain was stronger than yours, you'd just close that (explorer) wallet and open your wallet, and then it'd sync your fork with the explorer.

I'm ready, if I get everyone's consent, to declare my new v15.1 w the new pchmessage of NDLY, the new official wallet. Your fork should be synced with the explorer to minimize confusion. My wallet will hardfork the network as the new blocks created will be confusing to old wallets. When necessary I've been relying on the explorer as the indicator of the "main" network.

Does anyone object to moving to my new wallet? Does anyone still want to test it further? I'm trying to avoid any issues and get everyone's consent but no one's telling me yes or no.