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

iirc, the current attribution can tell you what client the user completed the transaction from

attributing to a cast is also useful but does lose this original meaning

Building @warpcast and @farcaster, new dad, like making food

that is the client the cast was sent from

current attribution is client that the frame interaction is happening from no?

Couldn’t I work backwards from cast hash to signer key to key metadata to client FID?