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

New Endpoint: script_execution_units_evaluation #237

Closed
fallen-icarus opened this issue Oct 3, 2023 · 1 comment
Closed

New Endpoint: script_execution_units_evaluation #237

fallen-icarus opened this issue Oct 3, 2023 · 1 comment

Comments

@fallen-icarus
Copy link

fallen-icarus commented Oct 3, 2023

Is your feature request related to a problem? Please describe.
Trying to build a transaction without a local node using cardano-cli transaction build-raw requires the user to specify the budget necessary for each plutus script in the transaction. Getting the budgets wrong will result in the transaction failing. If there is only one script, the user can just set it to the max available but if there are multiple scripts in the transaction, that approach may not work (eg, one script may require most of the available budget while other scripts barely use any). Knowing the exact budget required for each script would dramatically improve the experience of composing plutus scripts without relying on a local node.

Describe the solution you'd like
I am looking for something like what blockfrost has here. The user should be able to submit a transaction created with cardano-cli transaction build-raw and the query should return the breakdown of execution units used for each script. The user would then take those budget numbers and recreate the transaction using the build-raw command for actual submission to the blockchain.

Describe alternatives you've considered
The only current alternatives I am aware of are to use a local node or use blockfrost.

@rdlrt
Copy link
Contributor

rdlrt commented Oct 4, 2023

Duplicate being tackled already via #227 for v1

@rdlrt rdlrt closed this as completed Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants