I am bridging ICP with Ethereum. ICP has a smart contract, called a canister, called evm_rpc. This allows other ICP canisters (smart contracts) to call the evm_rpc contract which in turn can call a solidity contract.
With ICP there is the concept of logging in using an ICP id. Ideally what I want to do is generate an ethereum private / public key and store the private key on a decentralised network in the same way Web3Auth does.
The login to ICP would somehow dig out the “under the hood” Ethereum private key using Web3Auth apis. This could be used to perform operations needed via ethereum solidity contracts
Does this sound possible? - if yes any pointers or recommendations on how to go about doing this.
Thank you for your detailed inquiry! It sounds like you’re exploring an interesting integration between ICP and Ethereum using Web3Auth.
While the current capabilities of Web3Auth primarily focus on providing authentication solutions, the specific functionality you’re looking for—generating Ethereum keys from an ICP login—may not be directly supported at this moment. However, here are a few pointers that might help you move forward:
Custom Authentication: You may want to explore setting up custom authentication flows where you manage the key generation and retrieval after logging in with an ICP ID.
Key Management: Consider using a decentralized storage solution to store your private keys securely. You could potentially integrate it into your workflow following the authentication.
Utilize the SDK: Once you manage to retrieve the Ethereum keys, you could use the Web3Auth SDK for seamless operations with Ethereum contracts.
Community Support: Engaging in forums or communities that focus on ICP and smart contract integration might provide additional insights or similar use cases.
If you do decide to proceed further with your integration and encounter specific issues, please share any SDK details, along with code snippets, screenshots, or errors you face, and I’ll be glad to assist further!
Best of luck with your project!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.