The Frame Transactions spec is ready for feedback! 

Please share your thoughts in replies, comments or DMs. Your feedback is very important to help us get the design right.

The Frame Transactions spec is ready for feedback! 

Please share your thoughts in replies, comments or DMs. Your feedback is very important to help us get the design right.

https://www.notion.so/warpcast/Frames-Transactions-Public-Draft-c2e0d3210d684b4cb7803de1810db36d?pm=c

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Read on mobile, had trouble commenting. Great work, some feedback:
- Consider adding optional authorized_hosts to transaction JSON; limit Frame URLs that can request
- Could you support follow-up handlers to "reverts" from transaction, something akin to ERC-3668

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

terminally.online

Sure, an example flow:
1. Attempt transaction, find that user isn't approved, or whitlelisted, etc. Revert in the special way, to specific Frame
2. Frame notifies the user of what is needed to get approved/whitelisted (some Web2 process), guides the user.
3. User follows the process, and attempts transaction again.

Tell me more about what revert handlers might enable.