Expose explicitSignerData for simulation method and reduce rpc node requests #1606
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment when we want to perform a simulation, using the
simulate
method exposed in theSigningCosmWasmClient
andSigningCosmWasmClient
classes, it is not possible to specify thesequence
, but a request is made each time to get it.However, this in practical use results in sending multiple requests to the RPC nodes, for example when we go to use the
signAndBroadcast
method at the moment three requests are made to the nodes:simulation
method)sign
method)So we make the same request twice in a row to get the account details, specifically
sequence
andaccountNumber
.The goal of this PR is to remove this redundancy and reduce the number of requests made to nodes in the chain, also for anyone who build libraries based on cosmjs it's a good way to control this kind of node requests.