Skip to content

Fix base-0004 migration notes #73

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.

Sign up for GitHub

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

Open
leonschh wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix base-0004 migration notes #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion app/upgrades/data/changes.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ export const changes: Change[] = [
summary:
"At and after Azul activation, block production and import use the following Engine API methods: <ul class='my-2 flex flex-col gap-1 list-disc pl-5'><li><code>engine_forkchoiceUpdatedV3</code> for starting block builds and forkchoice synchronization.</li><li><code>engine_getPayloadV5</code> for fetching built payloads.</li><li><code>engine_newPayloadV4</code> for importing payloads into the execution engine.</li></ul><code>engine_getPayloadV5</code> returns a V5 envelope, but the contained execution payload is still V4-shaped. As a result, payload insertion continues through <code>engine_newPayloadV4</code> (there is no <code>engine_newPayloadV5</code> path used by Base Azul clients).<p class='mt-2'>Azul constraints for this flow:</p><ul class='mt-2 flex flex-col gap-1 list-disc pl-5'><li>Blob-related Engine API inputs are constrained to empty values:</li><ul class='mt-2 flex flex-col gap-1 list-disc pl-5'><li><code>expectedBlobVersionedHashes</code> MUST be an empty array.</li><li><code>blobsBundle</code> in <code>engine_getPayloadV5</code> responses is expected to be empty.</li></ul><li><code>executionRequests</code> in <code>engine_newPayloadV4</code> MUST be an empty array.</li></ul>",
migrationNotes:
'Use the registry as the source of accepted TEE signer identities instead of hard-coding Nitro prover signers.',
'Node clients and libraries should handle the V5 payload envelope with an empty blobsBundle, continue inserting payloads through engine_newPayloadV4, and send empty expectedBlobVersionedHashes and executionRequests arrays.',
lastUpdated: '2026-04-12',
relatedRepos: [],
githubIssues: [],
Expand Down