-
Notifications
You must be signed in to change notification settings - Fork 125
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
Question: new_coins_per_byte
& ref_script_coins_per_byte
cost values to use
#694
Comments
It's a protocol parameter that can be updated on-chain by a governance action. To get your latest protocol parameters, you can use:
The difference between |
ah yes, fantastic, thank you. I see both For |
@gmoratorio right |
Thanks so much for the help! Really useful info. Much appreciated. |
Thanks for the help! |
I'm refactoring our CSL code from 11.5.0 to 12.1.0 and I've come across a few places where I'm not sure what we should use for cost values.
new_coins_per_byte
In our codebase we used
34482
forcoins_per_utxo_word
and I see in other places we have4310
forcoins_per_utxo_byte
, but I'm not sure ifA. value for
coins_per_utxo_word
can be directly translated tocoins_per_byte
(or what the translation math should be) andB. if our existing usage of
4310
in other places forcoins_per_utxo_byte
is the best value to use, or if there is a better recommended defaultref_script_coins_per_byte
(now required to work with thescript_size
arg introduced innew_ref_input
)I found
"minFeeRefScriptCostPerByte": 15
in our Stake Pool'sconway-genesis.json
file, but I'm not sure if this is the right value to use, and alsoref_script_coins_per_byte
expects an interval, so I'm not sure what thenumerator
anddenominator
should be in this case.Any insights into cost values to use for
new_coins_per_byte
andref_script_coins_per_byte
or links to docs where these recommended values are stored would be very helpful.Thanks in advance!
The text was updated successfully, but these errors were encountered: