docs: expand initial registration section with all required values#209
Open
docs: expand initial registration section with all required values#209
Conversation
Moves the initial registration guide from the ValidatorConfig V2 page to the operator overview page and lists every value a new operator must provide: validator address, public key, ingress, egress, fee recipient, and the ed25519 add-validator signature. Includes the full CLI command. Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
…uide Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
…itial registration Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
Co-authored-by: Richard Janis Goldschmidt <701177+SuperFluffy@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d3f9e-0620-773b-a54e-d0732af7ea03
kuyziss
reviewed
Mar 31, 2026
|
|
||
| The public key should match the output of the `generate-private-key` command. | ||
|
|
||
| #### Creating the add-validator signature |
Contributor
There was a problem hiding this comment.
if we add this, should we also add a section for create-rotate-validator-signature, or at least mention it?
kuyziss
reviewed
Mar 31, 2026
| ``` | ||
|
|
||
| If you are not prepared to accept fees, we recommend setting the `--consensus.fee-recipient` field to `0x0000000000000000000000000000000000000001` as that will funnel the funds to a non-user controllable wallet (there is no known private key for the address). | ||
| If you are not prepared to accept fees, we recommend setting the `--consensus.fee-recipient` field to `0x0000000000000000000000000000000000000000` as that will funnel the funds to a non-user controllable wallet (there is no known private key for the address). |
Contributor
There was a problem hiding this comment.
aren't we deprecating this field? as it was moved to contract
kuyziss
reviewed
Mar 31, 2026
| The simplest way to rotate is using the `tempo` CLI, which handles signature creation and the on-chain transaction in one step: | ||
|
|
||
| ```bash | ||
| tempo consensus rotate-validator \ |
Contributor
There was a problem hiding this comment.
i think its missing --private-key:
Usage: tempo consensus rotate-validator [OPTIONS] --validator-address <ETHEREUM_ADDRESS> --public-key <IDENTITY_KEY> --ingress <IP:PORT> --egress <IP> --private-key <FILE> <--signature <SIGNATURE>|--signing-key <FILE>>
And its only possible if we enabled self service for them. Otherwise, we need to point them to create-rotate-validator-signature and then we can run that for them
emmajam
reviewed
Apr 1, 2026
| Generate an ed25519 keypair: | ||
|
|
||
| ```bash | ||
| tempo consensus generate-private-key --output <path> |
Member
There was a problem hiding this comment.
can we add a note to say 'never ever share your private key with anyone'
emmajam
reviewed
Apr 1, 2026
| | **Public key** | `0x`-prefixed 32-byte hex | Your ed25519 identity key. Generate one with `tempo consensus generate-private-key` (see [below](#generating-a-signing-key)). | | ||
| | **Ingress** | `IP:port` | The inbound address other validators use to reach your node. Must be unique across all active validators. | | ||
| | **Egress** | `IP` | The outbound IP address your node uses to connect to other validators. | | ||
| | **Fee recipient** | Ethereum address (`0x…`) | The address that receives transaction fees from blocks your validator proposes. If you are not prepared to accept fees, use `0x0000000000000000000000000000000000000000`. | |
Member
There was a problem hiding this comment.
there are some changes to fee recipient no? arent we making it so a proper value is required ?
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
4 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.
Moves the initial registration guide from the ValidatorConfig V2 page to the operator overview page and lists every value a new operator must provide: validator address, public key, ingress, egress, fee recipient, and the ed25519 add-validator signature. Includes the full CLI command with all flags.
Prompted by: janis