-
Notifications
You must be signed in to change notification settings - Fork 16
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
[FR] - Command to calculate the correct Plutus Script Costs
offline
#945
Labels
Comments
Does this make sense as a standalone command and, is it possible to work offline? e.g.
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
3 tasks
3 tasks
3 tasks
9 tasks
9 tasks
3 tasks
This was
unlinked from
pull requests
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I came across a problem while adding new features in the scripts to automatically use the guardrail scripts for submitting a protocol-parameter or treasury-withdrawal action on conway (v10). The problem is, that there is no way to calculate the correct execution units costs for a given plutus script (file) without a synced live node running.
Because the only implementation we currently have is within the
transaction build
command.By using the
transaction build
command and the option--calculate-plutus-script-cost FILE
we get an output like:Which is super nice, and the values for the execution units can than later be used for a transaction building via
transaction build-raw
for example. BUT, this does not work in offline mode.When it comes to governance, we need a feature in cardano-cli to calculate the correct execution units for a governance action that involves the guardrails script.
Two possible options to integrate that?
protocol-parameters
file, theaction-file
and thecompiled plutus-script
file.--calculate-plutus-script-cost
parameter option into thebuild-estimate
command.So we can do such calculations also offline without a connected online node, which would also come in handy of doing automated tests or optimizations via iterations.
The text was updated successfully, but these errors were encountered: