Evaulate Developer Experience With Passkey Shared Singleton Signer
nlordell opened this issue · comments
We are a bit indecisive about whether or not we should push for the current implementation with a WebAuthnSignerFactory
vs. the previously experimental shared WebAuthnSingletonSigner
method that we played around with in the context of 4337.
As such, we want to evaluate which one is nicer from a developer experience perspective.
Expected Outcome
- Clone the
4337-passkeys
example project - Replace the launchpad signer with the
WebAuthnSingletonSigner
implementation - if time permits adds the EOA as an additional owner
- Decide what we want to do.
The main thing we want from this issue is to answer the question:
What do we want to do?
Closed by #404