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
We currently have dryRunTransaction which takes a complete transaction and simulates it without committing it. For Wallets and Explorers, we also need a dryRunMoveCall. This shouldn't require a complete valid transaction like dryRunTransaction does.
Should not require a signed transaction.
Should not validate owned objects.
Should not require a gas object.
As an example use-case for explorer, we want users to be able to inspect the result of function calls on published packages (essentially treating them as a view function).
The text was updated successfully, but these errors were encountered:
ge commented: This is now blocked by [https://github.com//issues/5836|https://github.com//issues/5836|smart-link]
TL;DR is the original impl idea of dryRunMoveCall will not be very useful b/c of a Move entry function limitation, we pivoted it to be used on Move public functions which need some prerequisite work on sui-adapter.
the original workload was estimated to be about 1 week’s work, I will probably need another a couple of days to finish it
We currently have
dryRunTransaction
which takes a complete transaction and simulates it without committing it. For Wallets and Explorers, we also need adryRunMoveCall
. This shouldn't require a complete valid transaction likedryRunTransaction
does.As an example use-case for explorer, we want users to be able to inspect the result of function calls on published packages (essentially treating them as a
view
function).The text was updated successfully, but these errors were encountered: