Repository navigation
Conversation
…ction The main page awards best CPU, best memory and smallest size, but none of them is what a dApp developer asks first: what does one execution cost, and how many fit in a transaction? The total fee (execution plus reference-script fee) prices CPU, memory and size the way the ledger does, and scripts per transaction is a limit no fee can raise. Both are already in every metrics.json. Each card now shows these two first, in their own row, and the three medals below unchanged. A legend under the header says what each means. When the most expensive case exceeds one transaction for every submission, as in fibonacci_naive_recursion, the card says so instead of naming a tie at 0.
nau
force-pushed
the
feat/report-lowest-fee
branch
from
November 4, 2026 15:15
4625709 to
cf0bc33
Compare
nau
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The main page awards best CPU, best memory and smallest size. None of them answers the two questions a dApp developer asks first: what does one execution cost, and how many fit in a transaction?
ecd: Plinth 1.64/1.65 win the CPU and memory medals, but their 502-byte script costs 13,002 lovelace in total, against 7,886 for the lowest-fee rows.Both values are already in every
metrics.json. Each card now shows them first, in their own row; the CPU, memory and size medals follow unchanged, and a short legend under the header explains both. When no submission fits in one transaction, as infibonacci_naive_recursion, the card says so instead of naming a tie at 0.Checked by generating the full report with
cape submission report --all.