Ethereum

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Since L2 calldata is so cheap we can add way more metadata in the calldata suffix than just a 4 byte domain tag (app url, originating app, comments, etc)

Is anyone building a standard around this? Might be a good opportunity for farcaster to pioneer cc @horsefacts.eth

I think we can do a lot more than 16 bytes! Thinking more along the lines of a JSON object spec

You should checkout :) https://docs.base.org/identity/smart-wallet/sdk/make-web3-provider#datasuffix-optional

I played with it a bit and didn’t follow up after adding manual analytics for a few apps.

Would love to do something here so we can build dune dashboards etc cc @mats