Content
@
0 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Is there an good consumer UX for EIP-712 for 4337 wallets? i.e. if we wanted to suggest people use a 4337 wallet for people to register an FID and get an FNAME https://github.com/farcasterxyz/protocol/blob/main/docs/SPECIFICATION.md#5-fname-specifications
5 replies
8 recasts
101 reactions
greg
@gregfromstl
@thirdweb is very focused on making AA UX as smooth as possible, and if there’s anything specific you need we’d love to accommodate
1 reply
0 recast
3 reactions
Joaquim Verges
@joaquim
the UX for 712 is not dependent on the 4337 wallet but rather the underlying admin EOA. one thing that is worse though is 4337 wallets usually 'wrap' the 712 data into their own to add replay protection, so the signature confirmation screen is even harder to parse (though its not great even with regular EOAs)
0 reply
0 recast
4 reactions
Christian Montoya 🦊
@m0nt0y4
Why is a 4337 wallet needed? Regardless, a 4337 account could be enabled in a Snap. Happy to discuss this use case more in depth.
0 reply
0 recast
1 reaction
Philippe Castonguay
@phabc
Not sure I understand why the UX for 712 would be different for AA wallets?
0 reply
0 recast
1 reaction
gtscottyyy 🎩
@gtscottyyy
third web maybe? I can't tell if you're looking for underlying contracts or solution though so apologies if this is on the wrong track https://portal.thirdweb.com/contracts/build/base-contracts/erc-4337 https://blog.thirdweb.com/smart-contract-deep-dive-building-smart-wallets-for-individuals-and-teams/
0 reply
0 recast
3 reactions
