Skip to content

feat: reorder PayloadStatus enum (consensus-specs#4948)#7

Open
lodekeeper wants to merge 1 commit intounstablefrom
feat/payload-status-reorder
Open

feat: reorder PayloadStatus enum (consensus-specs#4948)#7
lodekeeper wants to merge 1 commit intounstablefrom
feat/payload-status-reorder

Conversation

@lodekeeper
Copy link
Owner

Motivation

Reorder PayloadStatus enum values to match ethereum/consensus-specs#4948.

Changes

  • PayloadStatus enum: EMPTY=0, FULL=1, PENDING=2 (was PENDING=0, EMPTY=1, FULL=2)
  • GloasVariantIndices type updated to fixed-length tuple: [EMPTY, FULL|undefined, PENDING]
  • All variant array accesses now use explicit PayloadStatus.* enum values instead of raw indices
  • Test hardcoded values updated to use enum

Split from alpha.3 upgrade PR #6.

Reorder PayloadStatus enum values to match spec change:
- EMPTY=0, FULL=1, PENDING=2 (was PENDING=0, EMPTY=1, FULL=2)

Update GloasVariantIndices type to fixed-length tuple:
- [EMPTY, FULL|undefined, PENDING] indexed by enum values

All variant array accesses now use explicit PayloadStatus.* enum values
instead of raw numeric indices for clarity and correctness.
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