Ethereum Key Derivation & Signing Features 🔑 ✍️

[teddyjfpender]

Ethereum Key Derivation & Signing Features

Because Mina is a zk-native chain, there is a world of possible features to build. One emerging and evolving area is the ability to scale Ethereum. This includes:

1. Bridging state from Mina to be verified on Ethereum using the Lambda Class bridge
2. ECDSA w/o1js, per the o1js documentation:

To interact with other blockchains and verify data from the outside world, o1js needs to be able to verify signatures. ECDSA is a widely used algorithm that is supported by many libraries and tools. For example, Ethereum transactions are signed using ECDSA over the secp256k1 curve. As a zkApp developer, when you want to verify an Ethereum transaction and make a statement about it, you must be able to verify the signature of the transaction which is why ECDSA is important for zkApps.

Pallad would greatly benefit its users by including the ability to derive Ethereum addresses and sign data using secp256k1 for Mina's zkApps.

Feature: Ethereum Key Derivation & Signing for Pallad
  In order to enhance interoperability and functionality,
  As a user of Pallad,
  I want the ability to derive Ethereum addresses and sign data using secp256k1.