5 ms·
The secure enclave uses secp256r1 while blockchain typically use secp256k1. Since private keys can't be imported, blockchain devs still require software interf
by yyzhero 9y ago
The secure enclave uses secp256r1 while blockchain typically use secp256k1. Since private keys can't be imported, blockchain devs still require software interface until one or the others adopts the scheme.
- bluesign 9y agoI think use case for blockchain will be private key derived from a key stored in secured enclave. Which is not the ideal case of course.
- DennisP 9y agoAh, too bad. Ethereum is supposed to be adding signature abstraction, so you can use whatever signature scheme you want; maybe using secp256r1 with phones would be a good application of that.
- onetom 9y agohttps://www.trustedkey.com https://www.trustedkey.com actually uses the Enclave and also the equivalent component (Secure Element) in Android phones. Both of these modules use the secp256r1 curve at least, so the signature verification algo which runs on the blockchain can be the same for both types of devices. (You can find some more details on this topic here: http://blog.enuma.io/update/2016/11/01/a-tale-of-two-curves-hardware-signing-for-ethereum.html http://blog.enuma.io/update/2016/11/01/a-tale-of-two-curves-...) Since the Byzantium fork there are some precompiles available for curve operations. Using those for the r1 curve signature verification in EVM code brought down the gas cost to practical levels.