Skip to content

docs(node): add ValidatorConfig V2 operator guide#190

Open
decofe wants to merge 20 commits intomainfrom
janis/docs-validator-config-v2
Open

docs(node): add ValidatorConfig V2 operator guide#190
decofe wants to merge 20 commits intomainfrom
janis/docs-validator-config-v2

Conversation

@decofe
Copy link
Member

@decofe decofe commented Mar 19, 2026

Adds operator documentation for TIP-1017 (ValidatorConfig V2 precompile).

New page: /guide/node/validator-config-v2 — covers querying validator state, self-service operations (IP updates, fee recipient, key rotation, ownership transfer), V1 vs V2 comparison, and migration.

Updated: /guide/node/operate-validator — cross-references V2 rotation guide, wraps legacy V1 instructions in a collapsible section.

Sidebar: Added entry under 'Run a Tempo Node' between 'Operating your validator' and 'Network Upgrades'.

Note: TIP page (protocol/tips/tip-1017.mdx) is auto-generated from the tempo repo and gitignored, so it will appear once the TIP is merged there.

Prompted by: Janis

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
@vercel
Copy link

vercel bot commented Mar 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Mar 19, 2026 7:07pm
tempo-docs Ready Ready Preview, Comment Mar 19, 2026 7:07pm

Request Review

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
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>
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>
decofe and others added 4 commits March 19, 2026 11:14
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
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>
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
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>
@vercel vercel bot temporarily deployed to Preview – tempo-docs March 19, 2026 11:26 Inactive
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
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>
decofe and others added 2 commits March 19, 2026 11:48
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
…s 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>
… of committee

Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
Copy link
Contributor

@jenpaff jenpaff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Broken cross-reference: In validator-config-v2.mdx, the link [V1 validator states](/guide/node/operate-validator#validator-states) points to operate-validator.mdx, but this PR removes the validator states section from that page and moves it to validator-config-v1.mdx. This will be a dead anchor. Should be /guide/node/validator-config-v1#validator-states.

Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>
…or' dropdown

Co-Authored-By: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com>

## Reading validator state

### Query active validators

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth noting here that active validators do not map to the active set of participants in the latest epoch

Fine leaving it out if it's an implementation detail


The simplest way to rotate is using the `tempo` CLI, which handles signature creation and the on-chain transaction in one step:

```bash

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prepend with the signature creation creation command as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants