frames-devs

how are frame devs doing ERC20 approval flows?

Like this

Both actions same screen, approve loops back on route and mint proceeds to a watch tx stage

*I should have made he button actions change to highlight actions better

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs

Like this

Both actions same screen, approve loops back on route and mint proceeds to a watch tx stage

*I should have made he button actions change to highlight actions better

https://mint.enjoyment.network

Mini apps will eat the internet | Latest drop: /clankermon | Building : /miniapps /large /fctrivia jeeves /source @degentip @playsource /jump

what if the user approved once and then tries to mint again? have you figured out a way to check for approvals or you just make the user do it every time?

toka

I do this in my /toka frame. Before rendering the "Approve" button, my code checks the allowance of the user's verified address: const allowance = await degen.allowance(userAddress, spenderAddress); Then if the allowance is sufficient, I skip the "Approve" button and go straight to the Mint button.

frame developer, web3 developer, long distance runner /streme /pixelnouns /frm /degendogs /degenfers /toka /maxis

True. But 99% of the time they do. (Yes, this is just a guess.) The other option that was suggested in this thread is dual txn button like "approve/mint" that is a "txn" button. With "txn" buttons, you get the user's connected address, and then you can check the allowance, and return either approve or spend txn data.

But you don’t know if the user is going to end up transacting with their verified address, right?

I can have 0x1234 as a verification but transact in a frame from 0x5678