Back in November, Uniswap and Paradigm introduced new approach for token approvals, Permit2 (general information here: https://blog.uniswap.org/permit2-and-universal-router) . As rightly pointed out, the standard ERC-20 token approval mechanism might be suboptimal in situations when an application requires authorization for multiple different tokens (authors focus on trading UX in the first place, but other smart contract types may have the same problem). Maybe we should consider adding similar authorization mechanics to the built-in token contract?
#Permit2-like token authorization
fading pawn
ashen yarrow
the hope is that for the most contracts you don't need to use approvals/allowance at all (I've been actually advocating for making allowances transient, but there are seemingly some use cases people are still interested in)
I don't understand this well enough though, so some example of what can be done via permit2, but not with soroban tokens would be appreciated. one thing that comes to mind is time-bound allowance, but I'm not sure what exactly is the use case for these and if they're necessarily better than no allowance at all
fading pawn
@ashen yarrow I revisited the documentation, and after more thorough examination, it seems to me that Permit2 will not play well with Soroban considering the differences in auth models. Sorry for bothering.