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.

Sign up for GitHub

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

Jump to bottom

Introduce a new parameter that replaces minFeeA #4263

Open
lehins opened this issue Apr 12, 2024 · 0 comments
Open

Introduce a new parameter that replaces minFeeA #4263

lehins opened this issue Apr 12, 2024 · 0 comments
Labels
dijkstra Ledger era that will follow after Conway

Comments

@lehins
Copy link
Contributor

lehins commented Apr 12, 2024 •
edited

minFeeA is packed by a Word64 and suspicion is that in the future it will not have enough precision to specify a correct multiplier for the fee.

We need to introduce a new protocol parameter that and deprecate minFeeA. New parameter will work similarly to minFeeRefScriptCostPerByte: it will be of type NonNegativeInterval and will use rounding during the fee calculation.

The name for the parameter will be similar to minFeeA after the rename due to #4264, but will end on [new name]CostPerByte

Related ticket that will be resolved before this one: #4262
@lehins lehins added the dijkstra Ledger era that will follow after Conway label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dijkstra Ledger era that will follow after Conway
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lehins