Yes, same chain.

The hash at height 1314626 from the FSM bootstrap.dat in the new peer swarm matches the hash on the explorer.
be76cac6a6c69b2eedbb2972722ffdbb5e18a0b83a5f59f9cc5cb5adc992bfc6

Divergence begins at 1314626 +1 because obviously I couldn't magically upgrade software remotely for everyone around the planet.

Best Regards,
-Chicago

I created a linear bootstrap.dat for the chain I'm synced with near height 1314626.

You can download it here.

Next, I'll see about trying that thing with the Network ID change as a proof-of-concept.

Hello,

    In my experiment, I set the Network ID to FSM1.

    It wasn't too much effort to render a linear bootstrap.dat using the new Network ID.

    After that was done, I used His Holy Noodliness's code and made the following updates.

        - Update Gitian Recipes
        - Upgrade UPnP Support
        - Set Client Version to Noodlyappendagecoin v0.8.6.2
        - Update Copyright Year to 2014-2018
        - Set Checkpoint at Height 1314626
        - Main Network 0x46534d01
        - Test Network 0x46534d02
        - Remove Legacy DNS Seeds
        - Remove pnSeed Array

    The source code is in the 4Q18 branch here.

    I have also produced Windows binaries.
    These Windows binaries use Berkeley DB v5.3.

    Here is how to try the "new peer swarm network".

    You must backup your current wallet.dat and data directory.
    Keep your backups!

    Next, move your current data directory someplace out of the way so you can sync the chain using the new FSM Network ID.
    You may use the newly prepared FSM bootstrap.dat to load the blocks from disk during the initial sync.

    Noodlyappendagecoin v0.8.6.2 for Windows is available here.

    It is noted as EXPERIMENTAL on the the repository releases page.

    There is one full node only and it is not mining.
    addnode=23.253.205.134
    addnode=[2001:4801:7825:102:be76:4eff:fe10:3d29]

    If you would like to participate, just run the new code and start your miner.

    I am hoping this solves the network problems we discussed over the weekend and acts as a stop-gap until we perform another network upgrade to implement BIP 34 and BIP 66.

    This interim client should make things easier on future development so there are less exceptions written into the code.
    This interim client is not meant to hinder other development efforts.

    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.

Best Regards,
-Chicago