
Web3 startup
13 Followers
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
Thanks for linking this, I must be doing something wrong. It is failing to add the event to my Google (Android) Calendar.
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.