Aditi Srinivasan
@dynemyte
101 Following
813 Followers
Casts
Casts + replies
Aditi Srinivasan
@dynemyte
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.
0 reply
1 recast
4 reactions
Aditi Srinivasan
@dynemyte
PSA: All hubs will automatically shut down on Friday (UTC). If you have any remaining dependencies on hubs, please make sure you remove them!
1 reply
3 recasts
8 reactions
Aditi Srinivasan
@dynemyte
Warpcast has not been submitting to hubs for ~2 days now and things look good! We will be taking down some of the Farcaster-owned (non-bootstrap) hubs today to surface any remaining dependencies on hubs. Please let me know if you have concerns!
0 reply
2 recasts
15 reactions
Aditi Srinivasan
@dynemyte
PSA: We will stop submitting messages from Warpcast to hubs for a few hours today to surface cases where people are still dependent on hubs. We will be submitting all messages from Warpcast to Snapchain. Please DM me or reply here if you have any concerns!
0 reply
2 recasts
9 reactions
Aditi Srinivasan
@dynemyte
The location migration is complete. All location data on user profiles on Warpcast is on hubs. As a part of the migration, user profile location was cleared for ~400 users because we could not compute a location using the 2dp lat, long value derived from the existing location. For ~3k users, location has been migrated to a region with < city level granularity because we could not infer a city-level location with the rounded 2dp lat, long. If your location has been set to a value you're not happy with please try to re-set your location manually. If you're running into a case where you're unable to set your location manually, please reach out!
2 replies
5 recasts
39 reactions
Aditi Srinivasan
@dynemyte
As a part of the project to publish user location to hubs, we will be migrating existing user location data to match the criteria that new location data must satisfy and publishing it to hubs. New location data is restricted to ~city level granularity and sublocalities (e.g. Brooklyn, NY) will not be presented as options. If your location is set to e.g. Brooklyn, NY we will make an attempt to translate it to the encompassing city (e.g. New York, NY).
3 replies
20 recasts
55 reactions
Aditi Srinivasan
@dynemyte
Warpcast now publishes locations set in user profiles to hubs as per the FIP below. If you set your location on Warpcast, expect it to get published to the farcaster network! https://github.com/farcasterxyz/protocol/discussions/196
2 replies
62 recasts
165 reactions