Repository navigation
docs: Engine API secret note on the Update a DV page - #653
Merged
Merged
Conversation
CDVN, LCDVN and CDVC now generate the Engine API secret per node. Say that the normal update recreates the execution and consensus clients once, and what to do when git pull stops on a changed jwt/jwt.hex. Applied to docs/ and versioned_docs/version-v1.11.
|
KaloyanTanev
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an "Engine API secret" note to the Update a DV page, in the charon-distributed-validator-node and charon-distributed-validator-cluster tabs.
Details
CDVN, LCDVN and CDVC stop shipping a shared
jwt/jwt.hexand generate the Engine API secret per node in a Docker volume (PRs onsecurity/per-deployment-jwtin each repo, with backports to CDVNmain-v1.11and LCDVNmain-v0.3). The note tells operators:git pull,docker compose up -d) is all that is needed. It recreates the execution and consensus clients once, with the new secret.git pullstops on a locally changedjwt/jwt.hex, and how to keep an own secret.Applied to docs/ (next) and versioned_docs/version-v1.11. No other page documents the JWT path of these repos (the only other match is Sedge's
jwtsecretin create-a-dv-with-a-group).Merge after the compose PRs, since the note describes their behaviour. Not tested: the site build was not run. The note uses the
:::info[title]admonition form the page already uses for:::warning[...].ticket: none