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 idea is that the VM would ignore some rules and just dry-run the TX as best it can to completion. Each time some asset amount, contract, or variable UTXO is missing, it adds that to a log of missing data and continues the estimation run. All the missing data pieces encountered during the estimation call are discovered and returned in a single request to the API.
Implementing this solution would significantly reduce the number of total dry runs, relieving the burden on the SDK and node and allowing them to operate much faster, thereby enhancing execution efficiency for the users.
Note
One alternative is to run the VM via WASM to calculate everything. Still, since the WASM can be heavy in the MBs ballpark, it's currently not a feasible solution for front-end environments, so a change in the API could be a realistic solution.
The idea is that the VM would ignore some rules and just dry-run the TX as best it can to completion. Each time some asset amount, contract, or variable UTXO is missing, it adds that to a log of missing data and continues the estimation run. All the missing data pieces encountered during the estimation call are discovered and returned in a single request to the API.
Implementing this solution would significantly reduce the number of total dry runs, relieving the burden on the SDK and node and allowing them to operate much faster, thereby enhancing execution efficiency for the users.
Note
One alternative is to run the VM via WASM to calculate everything. Still, since the WASM can be heavy in the MBs ballpark, it's currently not a feasible solution for front-end environments, so a change in the API could be a realistic solution.
cc @Voxelot @luizstacio
The text was updated successfully, but these errors were encountered: