Repository navigation
Derive proof domains from supply and execution-work limits - #79
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
Summary
Derive the numerical fee/counter domains from two readable limits: circulating funds below 10^50 ETH at each actual transaction input, and lifetime executed work below 2^128 events. The new history induction starts the existing funding proof at each transaction, so inner calls and ancestor rollback are covered without bounding total historical issuance.
ResourceAssumptions.from_deploymentderives initialization, physical queues, committed effects and the three local observations from actual factory/history inputs.completed_callalso consumes the derived domain for a next completed call, including SYSTEM. No safe-fee formula or intermediate queue invariant is a premise of the deployment-facing result.The work count conservatively includes completed LOG0 instructions with length >=68 bytes across the actual execution trees, including unrelated matching logs and rolled-back work. Documentation states this definition, corrects the description of the 2893 intermediate multiplication overflow, and retains the open canonical installation, scheduling, admission and protocol-history bindings. Registered parents and kill-lines are unchanged.
Validation
Validation receipts and exact source hashes:
audit/receipts/resource-assumptions.json.LEAN_NUM_THREADS=2 make checkpassed: 3,678 default build jobs and 3,608 mutation-target jobs.propext,Classical.choiceandQuot.sound.