I wrote a blog post about how consumer hardware (a.k.a. Secure Enclave) based wallets (e.g., @getclave @coinbase Smart Wallet, @daimo) differ from Hardware and Traditional Wallets.  

Enjoy!

Your own bank, on ethereum
https://github.com/daimo-eth/daimo

One-click onboarding to onchain payments. Experience smartest self-custody and hardware-level security. Backed by @thematterlabs | ERC-4337 Grantee

I wrote a blog post about how consumer hardware (a.k.a. Secure Enclave) based wallets (e.g., @getclave @coinbase Smart Wallet, @daimo) differ from Hardware and Traditional Wallets.  

Enjoy! 
https://mirror.xyz/0x8958D0c419BCDFB8A86b8c0089552bE015fbe364/hvpY_houtY9gGDnT8-jthCmE963EawYnyITogyNP_ZU

Researcher at Clave and
Co author of EIP-7212 

It is great, for those who already have a yubikey. However I think using it on a smart wallet requires a different wallet UI and functionality:

- a UI that designed to track portfolio 
- it should be multi chain from day 0
- it should have minimal functionality on UI like hw wallets 


Why?

how does yubikey stack up as a passkey provider in your view here?

Nope, Clave uses consumer hardware which means only user can access the keys. Unlike other aws or cloud based TEE’s, this is fully self custodial and can only be accessed by user.

Cope dealer 🙏 eng + product  @ axelar.network 🔲

Building interchain. Web3 UX flippening 




Nope, Clave uses consumer hardware which means only user can access the keys. Unlike other aws or cloud based TEE’s, this is fully self custodial and can only be accessed by user.


https://support.apple.com/en-ca/guide/security/sec59b0b31ff/web

Does clave work like AWS secret manager and other similar where the seed is generated in the enclave and can never be exposed?

ie can I still export my seed phrase for cold backup etc?