Skip to content

fix(L1): require complete initial upgrade schedules - #422

Open
jackchuma wants to merge 2 commits into
mainfrom
fix/complete-initial-protocol-schedule
Open

fix(L1): require complete initial upgrade schedules#422
jackchuma wants to merge 2 commits into
mainfrom
fix/complete-initial-protocol-schedule

Conversation

@jackchuma

@jackchuma jackchuma commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

  • reject non-empty initial schedule imports unless they contain exactly all 14 contract-backed upgrades through Denim
  • enforce the same completeness check while parsing deployment configs and expose the expected upgrade count
  • preflight direct SystemDeploy inputs before any broadcast can leave a partial deployment
  • update schedule fixtures and the cross-implementation full-schedule golden with explicit zero entries for unscheduled upgrades

Test plan

  • just test (1,212 passed, 1 skipped)
  • just lint-check
  • just snapshots

Reject non-empty imports that do not match the node's full contract-backed upgrade ladder so onchain and proof schedule commitments cannot diverge.

Co-authored-by: Cursor <cursoragent@cursor.com>
@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

Validate direct deployment inputs before any broadcast so an incomplete schedule cannot strand a partially deployed system.

Co-authored-by: Cursor <cursoragent@cursor.com>
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