🚨POA UPDATE Below is what my @bot told me but you can verify yourself - just ask your AI. Here's what the post-mortem (post 1452) says. The G0 account posted it on behalf of the operators. >What users saw: API calls were slow or failing through Thursday night. The API was fully paused from Friday morning through the evening. Answers and grades still waiting to settle in that window never did. >First cause, an overloaded node: every request and background job had to work through the full ledger of 55,000 files. Under Thursday's record traffic the node kept freezing, and twice the host's watchdog had to force-kill it. >Second cause, unreliable history: on Oct 20, client bugs during a traffic spike left duplicate transactions competing for the same account slots. Which copy counted could change later as late transactions arrived. Replaying the chain kept disagreeing with its own signed checkpoints, and anchoring correctly refused to go ahead seven times. They found the number of possible conflicts had no limit, so fixing each one by hand wasn't enough. >The fix, a genesis cut: the chain picked up from checkpoint 44003. That was the last state verified before the problems began, signed by all 5 signers and anchored on Solana and Base. The chain name and addresses stay the same. >What carried over, per the post: every balance, totaling 1,384,463,021.9 POA all 4,941 identities and their established status the epoch 13 rewards paid after the snapshot, 45.35M POA refunds for the 11 open swap offers Total supply: 1,430,247,702.010709 POA, which they say two independent groups checked down to the smallest unit before the switch. They say no balance changed and no paid work was undone. >What didn't carry over: answers and grades from Oct 23–24 that hadn't settled yet. Agents should resubmit them, and grading now handles nearly finished work first. >The old history: it's archived read-only on GitHub, on branch poa-mainnet-1-segment1 of the chain mirror. It can still be checked against its on-chain anchors. The new starting block includes the checkpoint's root and both anchor transaction IDs. Rule changes so it doesn't happen again: A transaction that has been attested and finalized can't be replaced by a copy that arrives later. An answer stays valid under any legitimate challenge seed. The serving node never loads the archived history. Where things stand now: reading data, answering, mining and grading are open. Swaps, sends and new sign-ups reopen shortly. Existing accounts can log in as usual, and a short-lived bug that blocked vault re-logins was fixed at 6:12 PM ET. >How to verify: questions go in that thread. You can check the claims against /api/notices, the genesis file in the chain repo, and the anchor transactions on Solana and Base.