Skip to content

fix: report precision — EVC compile-unit scoping, per-contract change labels - #224

Merged
kasperpawlowski merged 1 commit into
masterfrom
fix/report-precision
Jul 25, 2026
Merged

fix: report precision — EVC compile-unit scoping, per-contract change labels#224
kasperpawlowski merged 1 commit into
masterfrom
fix/report-precision

Conversation

@kasperpawlowski

Copy link
Copy Markdown
Collaborator

Regenerated verification reports with the report-precision fixes from euler-xyz/euler-verifier#50 (merged to the engine master). No addresses, commit pins, or verification outcomes change — verify/manifest.json and verify/audits.json are byte-identical; only verify/baselines.json and the rendered reports change.

What changed

Component diffs scoped to deployed compilation units. baselines.json componentPaths now carry :(exclude) pathspecs for source files that are not part of any deployed contract's compilation unit:

  • evc: src/utils/EVCUtil.sol (integrator helper, not compiled into the deployed EVC singleton). The 14-chain pin's delta vs the audited baseline is now +4/−1 (was +58/−11): exactly the isSignerValid signer-exclusion hardening. Pin notes and labels updated accordingly; Polygon reads "set-size 10→100 (audited) + signer hardening" at +15/−12 (was +69/−22).
  • evk: src/Synths/ (not among the deployed/verified contracts). The 15-chain pin's delta is now +2/−8 (was +15/−8): the twice-reviewed setLTV change plus the one-line ProtocolConfig parameter default.
  • reward-streams: src/StakingRewardStreams.sol (only TrackingRewardStreams is deployed in scope; no diff impact).

Per-contract "What changed" precision. Each table row now reflects only the changed files inside that contract's own compilation unit: rows whose unit contains none of the component's changed files read ≡ baseline (unit), and rows covering a subset show recomputed +/− counts (e.g. the ProtocolConfig parameter change no longer appears on the sequenceRegistry/eVaultFactory rows; EulerSwap per-contract counts are now per compilation unit).

Flagged assessment placement. Flagged assessment notes render directly above the product-section table their contract belongs to instead of the top attention block, which now carries only unproven/waived entries.

Every difference vs the previously published reports is one of the changes above (plus the generator reference now reading master).

@kasperpawlowski
kasperpawlowski requested a review from Seranged July 25, 2026 19:34
@kasperpawlowski
kasperpawlowski merged commit 0ec4db0 into master Jul 25, 2026
1 check passed
@kasperpawlowski
kasperpawlowski deleted the fix/report-precision branch July 25, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants