-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Implement transaction dependencies estimation #701
Comments
I will try having a go at this one @digorithm |
After doing some digging around this, I found this function in our codebase: Do you think we still need to create another function? I might be missing something so please correct me if I'm wrong 😅 cc @digorithm |
We currently have this solution working by simulating the tx. @digorithm @Dhaiwat10, if is now possible to know missing dependencies ahead of time without the need to call the tx then the work, is to replace the current solution. |
@luizstacio sorry, just seeing this when browsing the todo list. I missed your response among my Github notifications. You mentioned replacing the current solution. Why do we need to do that? Is the current solution not good enough? Or are we specifically looking for a solution that does not involve having to simulate the tx? Thanks. |
Unfortunately, we still have to simulate the transaction to be able to estimate the transaction dependencies. So, is this feature live or not? I can't seem to find the documentation for it yet! |
@digorithm I would say yes the feature is live, but documentation around it is missing. Our |
Ah, I see. Then I'll ask you two things: Can we rename |
|
Similar to the Rust SDK, the TS SDK should be able to estimate the transaction dependencies (contract input set and variable outputs).
This removes the guesswork of setting the variable outputs and contract input set when performing a call.
The text was updated successfully, but these errors were encountered: