Bitcoin: EVM Key derivation [closed]

Bitcoin: EVM Key Derivation – Is It Possible?

Starting from Nostr private and public 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 Nostr private and public keys has sparked debate among enthusiasts and developers. In this article, we’ll delve into the topic and explore if such 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 for signing transactions, while pubkeys are used for interacting 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 straightforward. 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 for 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 priv/public key pair.

Can anyone derive an equivalent EVM key?

In theory, yes, any user with access to the Nostr identity data (private and public keys) could potentially derive 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’s 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 a seed, there might be limitations in terms of the amount of data that can be used to derive an EVM key. For example, 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 private and public keys can use them as a seed 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 Ethereum’s standard Keccak-256-based 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’re interested in exploring this further, I recommend checking out the Nostr documentation and experimenting with their API or code examples.

References

• [Nostr Documentation](

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

understanding decentralized stablecoins