pinata

Pinata’s snapchain node is now live!! 

- Public
- Free
- Writes enabled 

https://hub.pinata.cloud/v1/info

grpc coming shortly!

Yesterday, we introduced a bug into Snapchain related to signer revocation which we have now fixed. If you are running a node, please upgrade to v0.2.20. If your node is halted despite the upgrade, please DM me. The fix is likely redownloading from a new snapshot. 

Timeline
- May 15, 2:40pm ET: Deployed a [change](https://github.com/farcasterxyz/snapchain/commit/866074d844c6919c819b5df85c78cc8610458ae1) that caused signer removes to not result in revoked messages
- May 15, 7:30pm ET: Rolled this change back
- May 15, 8:30pm ET: Rolled forward to a version that includes the bug
- May 16, 1:36pm ET: Rolled forward to a [version](https://github.com/farcasterxyz/snapchain/commit/dba51e9fd923af74f52b063ae8056879f7f7fcc9) that processes signer removes correctly.

Impact
All signer removes published from May 15 2:40pm ET-7:30pm ET and May 15 8:30pm ET- May 16 1:36pm ET will not have resulted in any revoked messages. We estimate that there are ~40 impacted signers. We will resolve this over the next few days.

@stevedylandev @kyletut the snapchain node is out of sync

probably caused by
https://farcaster.xyz/dynemyte/0x20813f71

think it requires a full sync from snapshots

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links | opinions are my own

Everyone is from somewhere. Cofounder and CEO of Pinata. https://www.pinata.cloud/

@stevedylandev.eth @kyletut the snapchain node is out of sync

probably caused by
https://farcaster.xyz/dynemyte/0x20813f71

think it requires a full sync from snapshots

hamst.art $hamster /hamster 
martinvr.eth 
deploy.degen.eth

It’s actually an issue @sanjay has identified and there will be a patch in the next snapchain version

Will have it out tomorrow. Testing this turned out to be complicated. If you need a fix now, you can restore from snapshot.

No idea lol Sanjay said it will be simplest to wait for the release that will fix it permanently

ouch oke hope it goes out soon

the peers from the docker-compose are in sync, would a full sync from snapshot still help solve it?