Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[rpc] Add dryRunMoveCall #4967

Closed
Jordan-Mysten opened this issue Oct 4, 2022 · 2 comments
Closed

[rpc] Add dryRunMoveCall #4967

Jordan-Mysten opened this issue Oct 4, 2022 · 2 comments
Assignees

Comments

@Jordan-Mysten
Copy link
Contributor

Jordan-Mysten commented Oct 4, 2022

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).

@exalate-issue-sync
Copy link

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

@gegaowp
Copy link
Contributor

gegaowp commented Nov 16, 2022

this is blocked by #5836

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants