Yannick Nick

> This isn't a solution. I should be able to sync from scratch using the latest version, not jumping around versions. this is sloppy code. I'm having this same problem...

> Hello @duncand0nuts , I have the same problem on version 3.5.0 with chain-id pacific-1. I updated and checked configs according to docs. I use the genesis file from [here](https://github.com/sei-protocol/testnet/blob/main/pacific-1/genesis.json)....

> A few pointers that would help: > > * You're using a old set of state-sync peers, you should update to our new list here: https://docs.sui.io/guides/operator/sui-full-node#set-up-from-source > * Looks...

I've updated my list of state-sync peers, setup an archival fallback with an AWS account, and ensured it has the correct policies, but it seems my 2nd node sync cannot...

> cc @phoenix-o for the panic > > > Also I don't quite understand the following from the docs: > > What those docs are describing is a fullnode which...

> > My initial two Sui nodes were synced since mainnet launch, and I recall some people in the Discord stated they were unable to sync today from checkpoint 0....

> > I'm hoping your team could provide a solution for our 2 nodes that are unable to resume syncing, as it wouldn't make sense for a blockchain node to...

> > I'm hoping your team could provide a solution for our 2 nodes that are unable to resume syncing, as it wouldn't make sense for a blockchain node to...

> I've updated my list of state-sync peers, setup an archival fallback with an AWS account, and ensured it has the correct policies, but it seems my 2nd node sync...

`>` they don't think it be like it is but it do Upgrade to v2.0.0 which uses the latest op-geth & op-node. My node was also broken for days until...