frames

Frames can now optionally omit the client calldata attribution suffix. Return "attribution: false" in your transaction data to disable it.

This fixes errors related to parsing token approvals in some wallets.

The suffix is enabled by default: you don't need to make any changes unless you're bumping into an error.

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

terminally.online

23. Co-founder of @beliefs - @launchtokenbot (beliefs.social). Collaborator at /frogfm.

Haven't seen it from any other wallets. So far, I think it's Metamask specific. But I also wouldn't be surprised to discover other tools that make the same assumption. 

Yeah, once MM supports it there's no need to omit it.

was it only affecting metamask or some other wallets too?
i've seen your pr in metamask repo and curious if you've reached any other wallets for this issue.
as i suppose as soon as they support it devs shouldn't optionally omit attribution suffix?

degenfers

Thank you for this. This was major issue for my /degenfers frame last Thursday. Glad to have this "opt out" setting, at least until MM handles things properly.

ran into this, thank you so much for the fix 🔥🔥

wait a minute, was that ever merged to frog?

Is there a specification for this json format?