Bitcoin: EVM Key Derivation – Is it Possible?

Given our private and public Nostr keys, is it possible to derive equivalent EVM (Ethereum Virtual Machine) keys?

The question of whether Bitcoin users can derive equivalent EVM keys from their private and public Nostr keys has sparked debate among enthusiasts and developers. In this article, we will delve deeper into the topic and explore whether such a derivation is feasible.

What are EVM keys?

In Ethereum, EVM keys are used to interact with smart contracts on the network. There are two types of EVM keys: privkeys (private keys) and pubkeys (public keys). Privkeys are used to sign transactions, while pubkeys are used to interact with smart contracts.

Using Nostr Private and Public Keys

Nostr is a decentralized identity platform that offers an alternative to traditional Ethereum wallets. Nostr users can generate private and public keys using their identities. These keys are then used to interact with the Nostr network.

Now, when it comes to deriving EVM keys from Nostr private and public keys, the answer is not simple. The reason lies in the way EVM keys are generated and managed on the Ethereum network.

EVM Key Generation

In Ethereum, privkeys are derived using a process called “Keccak-256-based derivation”. This involves using the Keccak-256 hash function to derive a new private key from an existing public key. The resulting private key can then be used to sign transactions and interact with smart contracts.

However, Nostr uses a different approach to deriving EVM keys. According to Nostr documentation, users can use their identities as a “seed” to generate an EVM priv/pubkey pair. This means that if a user has a Nostr private key, they can use it as a seed to generate an equivalent EVM private/public key pair.

Can anyone get an equivalent EVM key?

In theory, yes, any user with access to Nostr identity data (private and public keys) could obtain an equivalent EVM key. This is because the derivation process used in Nostr can be reversed using the same seed values.

However, there are a few caveats to consider:

• Nostr-specific implementation: The way Nostr implements its private key derivation algorithm may differ from Ethereum’s standard Keccak-256-based derivation.

• Identity Data Limitations: While users can use their identities as seeds, there may be limitations on the amount of data that can be used to derive an EVM key. For instance, if a user has a large number of identity entries, it may not be feasible to generate an equivalent EVM key.

• EVM Key Management: Even with Nostr’s private key derivation algorithm, users would still need to manage their own EVM keys on the Ethereum network.

Conclusion

In conclusion, while anyone with access to Nostr’s private and public keys can use them as seeds to derive an equivalent EVM priv/pubkey pair, the question of whether this is feasible remains open. The specific implementation used by Nostr may differ from the standard Ethereum derivation based on Keccak-256, which could affect the ease of deriving equivalent EVM keys.

As with any complex subject, more research and experimentation is needed to fully understand the capabilities and limitations of Nostr’s private key derivation algorithm. If you are interested in exploring this further, I recommend consulting the Nostr documentation and experimenting with their API or code samples.

References

• [Nostr Documentation](

• [Ethereum 2.x EVM Key Derivation Guide](

SOLANA ANCHOR DEPENDENCY