Content
@
https://warpcast.com/~/channel/eth
0 reply
0 recast
0 reaction
Hoot 🎩
@owl
7702/5792 investigations - Metamask supports 7702 and 5792 multi calls already but is buggy (can't upgrade after rejecting once) - Ambire supports everything but implementation is outdated and reports wrong information (confirms atomic batching even if it's not possible) - Privy claims support on their demo page but it's not working - Dynamic planning to support it day one - Warpcast wallet tbd depends on privy and Merkle's work - Coinbase smart wallet supports 5792 but it's a traditional deployed smart account not an EOA
7 replies
2 recasts
9 reactions
whyduck
@kryptosebek
Ambire always announce support for batching because it is abstracted in a way for better user UX it's simply more convenient to sign all transactions at once
1 reply
0 recast
0 reaction
Hoot 🎩
@owl
It’s good UX true, but shouldn’t advertise atomic batching in 5792 wallet_getCapabilities if it can’t do so. I think it just does because it checks if the 7702 account contracts are deployed on the chain and they’re already pre deployed even if the chain hasn’t upgraded yet? It’s also not following the latest version of the spec which has a soecial kind of capability for atomic which shows if account is already upgraded or can be
1 reply
0 recast
0 reaction
