I needed some guidance as me and my friend are stuck figuring out a solution.
We are running virtual nodes as validators.
The Prv rewards generated from these vnodes are withdrawn in Multiple Incognito Wallets on different devices.
I got an app developed for personal use, which I used to monitor the PRV balance of these Multiple Incognito wallets
We used “getbalancebyprivatekey” RPC to read wallet balance.
After the Privacy V2 update, I am not able to fetch the prv balance using that app because the “getbalancebyprivatekey” RPC won’t work just by submitting the private key as it did earlier.
So we have been trying to run the “getbalancebyprivatekey” RPC call by submitting the OTA Key
We tried submitting the OTA key using the “submitkey” method ie Default Mode but got a Full Cache Error
Then we tried using the community fullnode (https://beta-fullnode.incognito.org/fullnode ) with the following access token: 0ec910a54ffbf2a0bdfc0c8b05e8b5445e51a2ae54f659a35ac7ad9980e4fd2c and still got the same error ie Full Cache Error. Please find the attached screenshot.
I saw developers suggesting not to sending a private key via an RPC call as it is NOT SECURE.
Please help me out by addressing the below-mentioned queries.
Question 1. Am I on the right track ie trying to fetch wallet balance using “getbalancebyprivatekey” RPC? Is there any other RPC?
Question 2. Do I need to configure my virtual nodes(validators) for caching first? For the OTA Key Submission to work?
Question 3. Is there a way to set up a testing node so that I can send test private keys and Test OTA keys and don’t have to worry about the information being stolen? (Please note we are aware of the CLI tool or the go-sdk options)
Any guidance would be of great help. @Gaurav_Saini