splits

Speed running submitting a transaction from a shared team wallet.

26 seconds, lots of room for improvement.

this is dope !

how do u deal with ppl choosing the right/wrong passkey authenticator across devices + browsers?

totally clear. we do the same in mobile app by storing the credential id in server, but in theorizing extending to the browser it feels uncertain if the user will always have access to that same keychain/passkey manager?

We know which passkeys can sign txns for a given account, and then only prompt the user a challenge from one of theirs that they’re able to sign with. Lmk if that’s not clear.