ServicesBuilt to keep networks honest.

Mainnet & testnet validators on redundant, geo-distributed nodes with automated failover and remote signers.

All services →
NetworksOne operator. Every chain that matters.

Validators across six regions, live mainnets, active testnets, and the networks we're standing up next.

All networks →
CompanyThe people behind the validators.

Who we are, where we have been, and where OriginStake goes next.

Journey →
Operational · 8 mainnets · Rank AA/01, Validator operations

Every block signed.Never two at once.

We run proof-of-stake validators for networks that cannot afford a missed block, or a duplicate one. Private nodes, one live signer per key, failover that is verified before it happens, and a team that has done this since 2021.

Live model, not a video.Every few blocks a stale proposal shows up for a height already signed. The scan stops and it never gets sealed.
2021Signing since
0Slashing events
AAStakingRewards rank
15+Networks, mainnet and testnet
/02, Track record
0

Five years. Nothing to report.

We signed our first block on Casper in 2021. Since then: no double-sign, no slashing, no key leaving our custody. The record is short because nothing happened. That is the whole job.

double-sign · 0
slashing · 0
keys lost · 0
2021

First block

Casper mainnet. Still in the active set today.

2024

Network halt, 12 hours

Casper stalled network-wide. We worked the restart with CasperLabs and the other operators until it moved.

2025

Monad mainnet

In the set from launch on a chain that finalizes blocks in under a second.

2026

Canton mainnet, Penumbra restart

Joined Canton as a regular validator. Coordinated the Penumbra chain restart with the other operators, genesis hash verified by hand.

Today

OriginStake

8 mainnets · 0 slashing · one operating team

/03, Monitoring

Someone is always watching. Usually a machine, first.

Every node streams metrics into our monitoring stack: signed blocks, peers, lag, disk, the signer itself. Thresholds page a human within seconds. By the time the phone rings, most issues are already being handled.

Missed blocksconsecutive ≥ 5
Node unreachable> 3 minutes
Jailed or inactiveimmediately
Signer latencyp99 > 200 ms
/04, Upgrades

Upgrades land at a height, not in a window.

Chains upgrade at a height voted by governance. We stage the new binary ahead of time, rehearse on testnet, and at the halt height the node swaps and is signing again before the next block. Five years of upgrades across 15+ networks, no blip.

/05, Networks

Where we sign today.

Mainnet validators across the networks below, plus testnets and genesis sets we join early. Each one gets the same setup: private node, single signer, verified failover.

/06, Working with us

Three ways in.

01

Delegate

Stake to our public validator on any network we run. Non-custodial: your keys, your wallet, our signature. Commission is set per network.

Choose a network →
02

Dedicated validator

Your own node, operated by us. Isolated infrastructure, named engineers, an SLA that is written down. For funds, treasuries and foundations.

Talk to our team →
03

Co-branded or white-label

A validator under your name, run by our team. You bring the brand and the community, we bring the metal and the on-call rota.

Institutional staking →
/07, Questions

What people ask before they delegate.

Ready when you are

Your stake.Our signature.Every block.

Tell us the network and the size. We will come back with how we would run it.

Talk to our team →[email protected]

No. Delegation is non-custodial on every network we run. Your tokens stay in your wallet, you can undelegate at any time, and we never see a private key that is not our own consensus key.

On most networks a short outage costs a few missed blocks and nothing else. Monitoring pages us within seconds, and failover follows the procedure above: confirm, move state, restart. We would rather miss ten blocks than sign one twice.

Signing two different blocks at the same height. Networks treat it as an attack: a slice of the stake is burned and the validator is removed permanently. It almost always happens by accident, during a failover, when a key is live in two places. Our signer setup makes that state unreachable.

Mainnet validators today include Monad, Pharos, Canton, NEAR, Casper, Penumbra, Aura and Data, with more in testnet and genesis sets. The list on this page is kept current.

Public delegation has no minimum beyond what the network requires. Dedicated and co-branded validators are scoped per conversation; write to us and we will reply with specifics, not a brochure.