Managed validator

Move your validator to us, identity intact.

Running your own Solana validator and ready to stop? We bring up a new node, catch it up, and move your identity across in one planned swap. Your stake stays delegated, and your delegators do nothing.

$3,200/mo

Frankfurt Amsterdam USDC, USDT, SOL

A validator taking in stake and sending out its voteAn abstract drawing of light on the page's dark ground. Faint streams, the stake, flow in from the left toward a bright stepped block, the validator; from its top a single bright stream, its vote, rises and runs away to the upper right.A validator taking in stake and sending out its voteAn abstract drawing of light on the page's dark ground. Faint streams, the stake, flow in from the left toward a bright stepped block, the validator; from its top a single bright stream, its vote, rises and runs away to the upper right.

Five steps

  1. Pre-flight

    We review your setup with you: identity, vote account and its authorities, client and version, stake. Together we pick a cutover window and write down how to roll back.

  2. Build and catch up

    We bring up your new host in Frankfurt or Amsterdam, start it from a recent snapshot, and let it follow the chain under a spare identity. It casts no votes for you yet.

  3. Swap the identity

    In the agreed window, your old node stops voting first. Then your identity and its voting history move across and the new node takes over. One identity votes on one machine, never two.

  4. Verify

    We check the new node's votes and leader slots, and that your stake is still delegated to your vote account. You sign off when you are satisfied.

  5. Decommission

    Your old host stays stopped until then. After sign-off it is yours to retire, with no validator keys left on it.

What moves, what stays

What stays yours

  • Identity and vote account

    The same validator, with its on-chain history.

  • Withdraw authority and commission

    Still set by you, still paid to you.

  • Delegators

    Their stake stays delegated. They do nothing.

What moves to us

  • Hardware

    Dedicated bare metal in Frankfurt or Amsterdam.

  • Watching it

    Monitoring and alerting, with our 24/7 NOC behind it.

  • Running it

    Voting, client upgrades and restarts.

Questions

Can I really migrate without missing a vote?

The swap is short and planned, but we won't promise zero missed votes: the old node has to stop voting before the new one starts. What does not change is your identity, your vote account and the stake delegated to it.

How long does the full migration take?

We agree the timeline with you during pre-flight. Most of it is the new node catching up; the swap itself happens in one short, scheduled window.

Do I keep my on-chain identity and my delegators?

Yes. Your identity and vote account move with you. Delegators do nothing, and your validator's on-chain history stays attached to it.

What if something goes wrong during cutover?

Pre-flight produces a rollback plan. Because the old node is stopped, not wiped, it can take the identity back. It never votes at the same time as the new one.

Do I need to be involved hands-on?

Mostly at the ends: pre-flight, where you share access and agree the window, and verification, where you sign off. The work in between is ours.

What about the MEV (Jito) configuration?

We review your client and its settings in pre-flight and agree what the new node runs. Nothing changes from what you run today unless you ask for it.

The managed validator