Hi yes I can confirm this. Please everyone update your clients for both QT and Halo from the links on the official site(Halo will link to pcloud download).

For QT it will take some time to update the peg database so just let it do it's thing when loading and eventually it should be synced.

The same is true for Halo. You may get a message when running Halo/Markets client that it didn't connect or bitbayd is busy. Actually just don't even click anything and let that message hang for a day. Clicking continue to connect early may make it compulsively reset the daemon and slow down the peg database update. I had not taken that into account on this build but it works if you just boot it up and totally ignore it for a day. This is the best way to let it re-calibrate. Then come back later and click to continue trying to connect and it should sync.

Then we will wait for network adoption of 4.0 client to hit 80% and then we can make sure everyones block height matches and only then fork is triggered by a transaction.
However the bridge itself will take some time in the audit phase maybe some weeks so only after changes are made to those contracts and thoroughly checked by other coders through an audit would it be live on AMM exchanges such as Uniswap or whatever is available on Polygon.

So BitBay web markets are live, BAY also trades on NightTrader DEX which is live, BitBay bridge is also undergoing the fork and in about a months time we should have some AMM exchanges with trading capacity based on audit results.

Thanks everyone for your patience.