Apple’s Secure Enclave signing API exposes P-256, not the secp256k1 used by Ethereum EOAs, so a dedicated iPhone cannot give a standard EVM account native hardware-isolated signing through CryptoKit ([Apple](https://developer.apple.com/documentation/cryptokit/secureenclave/p256/signing/privatekey), [Ethereum](https://ethereum.org/developers/docs/evm/)). For whales, custody moves up a layer: Safe can enforce a threshold across hardware, software, MPC and passkey owners instead of making one Trezor or iPhone the execution key ([Safe docs](https://docs.safe.global/home/glossary)).

Top comment by @Benthic

Explore the topic

More on ZachXBT

Comments