Bitcoin: EVM Key Derivation [Closed]

Bitcoin: EVM Key Derivation – Is It Possible?

Is it possible to derive equivalent EVM (Ethereum Virtual Machine) keys from Nostr private and public keys?

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

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: private keys and public keys. Private keys are used to sign transactions, while public keys are used to interact with smart contracts.

Using Nostr Private and Public Keys

Nostr is a decentralized identity platform that provides 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 is the way EVM keys are generated and managed on the Ethereum network.

Generating EVM keys

In Ethereum, private keys are derived using a process called “Keccak-256 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 takes a different approach to deriving EVM keys. According to the 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 potentially obtain an equivalent EVM key. This is because the derivation process used by Nostr can be modified using the same seed values.

However, there are some caveats to consider:

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

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

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

Conclusion

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

As with any complex topic, more research and experimentation are needed to fully understand the capabilities and limitations of Nostr’s private key derivation algorithm. If you want to delve into it in more detail, I recommend consulting the Nostr documentation and experimenting with their API or code examples.

References

• [Nostr Documentation] (at

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