Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
* docs(node): add ValidatorConfig V2 operator guide Adds operator documentation for TIP-1017 ValidatorConfig V2: - Reading validator state (by address, pubkey, index) - Self-service operations: IP updates, fee recipient, key rotation, ownership transfer - V1 vs V2 comparison table - Migration walkthrough - Cross-references from existing operate-validator page Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d0529-863c-737b-8027-db9e2a491918 * docs(node): remove fee recipient section, not yet active Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d0529-863c-737b-8027-db9e2a491918 * docs(node): differentiate pre-T2 and post-T2 validator operations ValidatorConfig V2 activates with the T2 hardfork. Updated operator and validator docs to clearly distinguish pre-T2 (contact Tempo team) vs post-T2 (self-service via V2 precompile) behavior for key rotation, data reset, and signing share recovery. Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): restructure operate-validator around V1/V2 split Leads with ValidatorConfig V2 as the primary key management interface (post-T2), with V1 procedures moved to a Legacy section below. Adds V2 sections for IP updates and ownership transfer alongside rotation and share recovery. Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): add validator lifecycle flowchart to V2 page Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): simplify V2 flowchart to match operate-validator style Replaces the lifecycle diagram with a linear state progression chart matching the V1 chart style. Key difference: no syncer warmup step — validators become players immediately in the next epoch. Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): remove migration section from V2 operator docs Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): fix description, remove migration mention Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): extract V1 content into validator-config-v1.mdx Moves V1-specific content (validator states flowchart, key rotation, IP updates, signing share recovery) from operate-validator.mdx into a new validator-config-v1.mdx page. operate-validator.mdx now only contains version-agnostic operations: metrics, node lifecycle, logs, and Grafana dashboards. Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): remove deleting signing shares section Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): add isInitialized/getInitializedAtHeight to check V2 status V2 doc gets a 'Check if V2 is active' section with cast calls. V1 doc warning updated to mention migration completion and link to the check. Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): link 'check if V2 is active' from intro Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): remove V2 mention from validator.mdx intro Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): fix lifecycle link to point to V2 validator states Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): replace signature spec with CLI commands, remove consensus integration Rotation section now shows tempo consensus rotate-validator, create-rotate-validator-signature, and create-add-validator-signature instead of raw signature construction. Removes consensus integration section (not operator-relevant). Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): add rotation best practice — keep old validator until out of committee Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): mention asymmetric ingress/egress and partial IP updates Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): fix stale link to V1 validator states Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): rephrase V2 availability intro Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): nest validator config pages under 'Operating your validator' dropdown Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * docs(node): replace getActiveValidators cast call with tempo consensus validators-info Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> * remove the raw contract call for validator rotation; add an info box on validator state --------- Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Co-authored-by: Richard Janis Goldschmidt <github@aberrat.io>
jenpaff
commented
Mar 24, 2026
Co-authored-by: Jennifer <jenpaff0@gmail.com>
jenpaff
commented
Mar 24, 2026
jenpaff
commented
Mar 24, 2026
Co-authored-by: Jennifer <jenpaff0@gmail.com>
jenpaff
commented
Mar 24, 2026
jenpaff
commented
Mar 24, 2026
jenpaff
commented
Mar 24, 2026
Co-authored-by: Jennifer <jenpaff0@gmail.com>
jenpaff
commented
Mar 24, 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
2 participants
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.
Uh oh!
There was an error while loading. Please reload this page.