Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove ChunkBody backward-compatibility #6773

Open
3 tasks
Tracked by #6772
jordanschalm opened this issue Dec 2, 2024 · 0 comments
Open
3 tasks
Tracked by #6772

Remove ChunkBody backward-compatibility #6773

jordanschalm opened this issue Dec 2, 2024 · 0 comments
Labels
Preserve Stale Bot repellent Protocol Team: Issues assigned to the Protocol Pillar.

Comments

@jordanschalm
Copy link
Member

jordanschalm commented Dec 2, 2024

Context

During Mainnet26, we plan to deploy a change to the ChunkBody data structure, implemented in #6744. This introduces a new field in a backward-compatible manner:

  • The field is nil-able, and instances where the value is nil are interpreted as the old data model
  • Business logic operating on the data structure have 2 codepaths: one for the old data model (nil field), one for the new data model (non-nil field).

Backward-compatibility is necessary to support a downtime-free upgrade, however we do not want to maintain this extra logic longer than necessary. This issue is to remove extra logic needed for backward-compatibility.

Hints

Changes to remove are implemented in #6744 and #6796. They are annotated with //TODO(mainnet27, #6773).

Definition of Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Preserve Stale Bot repellent Protocol Team: Issues assigned to the Protocol Pillar.
Projects
None yet
Development

No branches or pull requests

1 participant