A protocol and its clients are symbiotic, but their interests are not always 100% aligned.

For example, a protocol may want to introduce a feature that requires significant changes by the clients. Or, other times, clients may want to offload some of their complexity to the protocol.

There should be a tension between them.

- Add this feature
- No, you can implement it yourself, I'm not adding more complexity to my codebase.
- If you don't, I will leave.
- Well, ok, but how about me doing half of it?

This tension helps reach a better equilibrium. We need it.

Dad, geek, conversation liquidity provider. vrypan.net | @l--o--l | $lemon3 | @wdimapp

"clients" in this case is a generic term. 

For example, for Ethereum the "clients" may be smart contract developers, or L2s, who may demand more features, more space, more speed.

For Snapchain, clients may be Farcaster, TBA, or miniapps, or bots.