You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The emulator throws an error when it receives in an invalid transaction signature, but does not specify why the signature was invalid. Given that the emulator is a development tool, it should be able to perform an extra check to provide more diagnostics information to help the developer.
(Optional): Suggest A Solution
A transaction signature can be invalid for one of the following reasons:
signature was generated with the wrong private key
signature was generated by hashing the transaction with the wrong hash algorithm (e.g. on-chain account says SHA2, client used SHA3)
transaction was mutated after the signature was generated (e.g. sign the transaction, then set the gas limit, but submit the old signature)
Scenario 1 is difficult to report without knowing the original private key.
Scenario 2 can be detected by attempting to verify the signature with each other hash algorithm.
Scenario 3 cannot be reliably detected, but the emulator can print out a log of the transaction structure that was signed, which the developer can then compare against the transaction that their client prepares.
The text was updated successfully, but these errors were encountered:
Issue To Be Solved
The emulator throws an error when it receives in an invalid transaction signature, but does not specify why the signature was invalid. Given that the emulator is a development tool, it should be able to perform an extra check to provide more diagnostics information to help the developer.
(Optional): Suggest A Solution
A transaction signature can be invalid for one of the following reasons:
Scenario 1 is difficult to report without knowing the original private key.
Scenario 2 can be detected by attempting to verify the signature with each other hash algorithm.
Scenario 3 cannot be reliably detected, but the emulator can print out a log of the transaction structure that was signed, which the developer can then compare against the transaction that their client prepares.
The text was updated successfully, but these errors were encountered: