Implement a validation to check if a transaction is submitted
to a node id
which is not present in the Client's
list
#2124
Milestone
submitted
to a node id
which is not present in the Client's
list
#2124
Description
Recently there were increased complaints for
INVALID_NODE_ACCOUNT
error. After debugging with the team it turns out if a transaction is built to be a submitted to a specific node, but that node is not listed in theClinet's
list instead of throwing an error the SDK will send the transaction to a random node and it will reach the consensus node where it will fail atPRECHECK
. This is possible because of a this logic in the JS SDK code.Fix
We must introduce a new error to the user indicating that they are trying to submit a transaction to a node id which is not available in the Client's list and the user will have to adjust its setup. This way the user experience when using the JS SDK and interacting with the Hedera network will be improved.
Example of the new error:
By introducing the new error we will prevent sending it to the consensus node and failing at
PRECHECK
How to reproduce
Steps
Run the following example. The whole setup can be found in this repository and example - Four.js
The text was updated successfully, but these errors were encountered: