Understanding the Usecase - How to sign transactions/ make RPC calls?

[yashovardhan]

Question by NeoGoku | Kalvi#0222 on discord:

I would like to understand the use case. When we onboard web2 users using Web3Auth, they get a random wallet address associated with their social account. Once they login into the dApp, they may have a scenario where they need to sign/approve transactions. How do we solve this? Generally, user accounts generated in Metamask has private key linked within it and we make use of them to sign transactions. I can't wrap my head, how to do the same signing functionality when implementing Web3Auth. Do I need to export private keys for wallet created by Web3Auth and import them in Metamask for signing transactions. I'm clueless.

[yashovardhan]

To make RPC Calls, like signing transactions or messages, or even checking balance, see accounts etc. you can either directly use the private key or use the available providers.

You can see our provider documentation on how to use the private key/ and or ethereum and solana providers to make the RPC calls once the user has logged in

https://web3auth.io/docs/sdk/web/providers/