New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signature Verification on testnet #9154
Comments
can you confirm if are you doing this in the cli or gui? you are trying to verify a signed message? (there is an open issue about this being not correctly implemented in the gui, or rather, for view only wallets* please confirm) sorry, you are using this rpc call correct? https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#verify |
wallet rpc testnet sign/verify works. i use the wallets main address:
|
Resolved. Thanks a lot. |
Paste the request data you used to obtain a good: true response |
Sorry, I've already replaced it with the above. It was most likely just incorrect params placement. But seems to work well now. |
I have a question regarding the signature verification behavior on testnet. I would like to understand whether the signature verification process on the testnet is intentionally lax or if there are specific settings or reasons for this behavior.
For instance, if I change my request data to a faked or even empty signature, rpc still responds with
'good': True
.Is the signature verification process on testnet intentionally less strict compared to mainnet? Is there a monerod or rpc flag I can use to force testnet sig ver to be strict like it would be on mainnet?
Thanks a lot
The text was updated successfully, but these errors were encountered: