You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Verify automatic state-buffer finalization across v2 consumers #217
WriteStateBuffer owns hashing and freezing the completed upload in #216. Verify that the final write freezes the buffer and later writes cannot mutate it; no separate FinalizeStateBuffer or seal instruction is needed.
Consumers must reject incomplete buffers and validate the buffer's account, commit id, and authority for their flow. Keep the API consistent with finalization during upload. This issue covers that integration contract, not a parallel implementation of buffer finalization.
changed the title [-]Finalize MagicBlock Protocol v2 state buffers during upload[/-][+]Verify automatic state-buffer finalization across v2 consumers[/+]on Sep 17, 2026
Activity
snawaz commentedon Aug 29, 2026
We do not need
FinalizeStateBuffer(orSealStateBuffer) asWriteBufferStateitself finalizes the state whenuploaded_payload.len() == total_len.[-]feature(fraud-proofs): Implement FinalizeStateBuffer[/-][+]Finalize DLP v2 state buffers during upload[/+][-]Finalize DLP v2 state buffers during upload[/-][+]Finalize MagicBlock Protocol v2 state buffers during upload[/+][-]Finalize MagicBlock Protocol v2 state buffers during upload[/-][+]Verify automatic state-buffer finalization across v2 consumers[/+]