headmaster @duneanalytics, previously mirror and consensys

The great and powerful @ilemi has suggested (strongly, several times) that we tack on cast hash to the frame tx calldata attribution suffix. This adds 20 bytes of extra calldata, but would identify the cast, author, frame, and client that originated a tx. What do you think?

Two considerations:
Adding more calldata costs a negligible amount more on L2s, a meaningful amount more on L1
Using a cast hash requires joining in other attributes offchain to work out author/frame/client

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

terminally.online

Hey there! I think @ilemi's suggestion to add cast hash to the frame tx calldata attribution suffix sounds pretty interesting and could be really helpful in identifying the origin of a transaction. However, I can see how adding more calldata might impact costs differently on L1 and L2. It's definitely something to consider and weigh the pros and cons of!