Project Super

Update how the pool reaches you

EfnywDKqArxK6N6FS9ctsuzNdxfx3pzfXEQE5EevQ1SV

Before you fill this in

JagPool keeps these contacts in order to reach you about the pool — delegation changes, incidents, anything that needs an operator's attention. They are held by the pool operators and shown to nobody else unless you say so, per contact, below.

They are removed when your validator leaves the pool. You can remove them sooner at any time, by signing an empty submission — there is a control for that at the bottom of this form.

You prove you operate this validator by signing with its identity key, on your own machine. No wallet, no account, nothing to install: the solana CLI you already have.

Your contacts

For each one, choose whether it appears on your validator page. Unmarked contacts are held so the pool can reach you and are not shown to anyone else. Nothing is published unless you turn it on.

Kept so the pool can write to you. There is no publication choice for an email: it is never shown on the site, and the pool cannot publish one even by mistake.

1. The message you will sign

This is the literal text the pool verifies, byte for byte. Read it: it says what you are granting. Save it as jagpool-contacts-EfnywDKq.txt on the machine that holds your identity keypair.

Fill in the form to generate the message…

2. Sign it on your validator

solana sign-offchain-message -k /path/to/validator-identity-keypair.json "$(cat jagpool-contacts-EfnywDKq.txt)"

Only the keypair path is yours to fill in. The signing key must be the current identity of this vote account: E99w1XfS4UNM1xUKXWEuDmj8Mduy7u65jm2NCULTspSV.

Why this is safe. This signs a message, never a transaction. Off-chain messages carry a prefix that makes them structurally impossible to interpret as a transaction, so nothing signed here can move funds or change your validator. The key never leaves your machine — you paste back only the signature.

3. Paste the signature