Accurate Transaction Verification Costing #1156
Closed
Conversation
This file contains 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
|
It's much easier if I don't need to worry about the correct combinations of inputs x outputs but then I need to know when a bench fails that should be correct. It would be nice to print something out on failure with the input so this is clear |
freesig
force-pushed
the
freesig/bench-transaction
branch
3 times, most recently
from
02e8b86
to
ca87c63
Compare
freesig
force-pushed
the
freesig/bench-transaction
branch
from
ca87c63
to
b16f78e
Compare
|
We close this PR for now, but the work done here is useful in the future to finish #1402. |
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.
Improved Transaction Costing Specification
Related #4
Objective
Create a more accurate transaction costing model by identifying and addressing areas where costs are not adequately captured, thus minimizing risks such as liveness failures, unsynchronizable nodes, and unanticipated DA expenses.