Farcaster Devs

Reading the Snapchain doc: https://warpcast.notion.site/Snapchain-Public-0e6b7e51faf74be1846803cb74493886

Going to cast all my stupid questions in this thread as they come up 🧵👇

> When a new snap is received each state change is applied onto the relevant trie which will add or remove items.

Is there any concern around tree traversal for diff operations if users are reverting actions frequently? Ie. is this a spam vector? I like and unlike things wantonly

This is already a spam vector, but now you have the ability for protocol level enforcement of rate limits by knowing exactly how many operations a user took over the last n blocks

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

Also the insertion and deletion times for Merkle tree operations are O(log n) (roughly), and since this is a per account tree it's not too bad

It is indeed a problem we already see on the protocol today, with some bots willingly grinding many times over through their storage slots for casts or reactions, the subsequent purges of old state and thrash on synchronization is a strong basis for why this model is net better for addressing the issue.

That's very cool

Now a social network can throttle a user at a global level and for a verifiable reason