INFRASTRUCTURE
FOR THE CHAINS
THAT NEED TO RUN.
Oryxen operates validators, relayers, and RPC endpoints for proof-of-stake networks. Non-custodial by design — keys stay ours, coins stay yours.
- networks validating
- 06
- regions online
- 03
- commission from
- 5%
- slashing events
- 0
01 — Networks
WHERE WE SIGN BLOCKS.
Mainnet validators we operate today. APR shown is the on-chain rate at time of writing — it floats, check the explorer before you delegate.
* more chains onboarding — infra capacity reserved per network, not per hype cycle
02 — Services for validators
TOOLS WE BUILT
BECAUSE WE NEEDED THEM.
Everything below runs in production against our own validators first. If it can't keep our keys safe, it doesn't ship.
Node Monitoring
Internal stack that watches consensus keys, vote windows, disk, and peer count on every box we run. Alerts page the on-call operator in under 30 seconds — before a missed block becomes a slash.
Network Overview Dashboards
Public-facing views of the chains we validate: stake distribution, governance turnout, upgrade schedules. Built for delegators who want to see what their validator actually sees.
Operator Tooling
Scripts and small services we wrote for our own operations — snapshot rotation, key backup, upgrade automation. Shared with other node runners when they stop being our edge.
03 — B2B solutions
INFRASTRUCTURE FOR TEAMS
SHIPPING REAL CHAINS.
Foundations and product teams hire us when the chain has to stay up during the only week anyone will remember. Scope, SLA, and pricing set per engagement — no pricing-page theater.
IBC Relaying
We run Hermes relayers on the channels we validate. Packets move when your users need them to — not when someone notices a stuck queue. Channel onboarding on request.
Dedicated RPC & API
Archive-capable endpoints for your chain, scoped to your workload. No shared rate limits, no surprise 429s during your token launch. Grows with your traffic, billed flat.
White-Label Validation
Your brand on the validator, our metal underneath. We operate the signer, sentries, and upgrades; your community delegates to a name they recognize.
04 — Why Oryxen
SIX THINGS WE
ACTUALLY DO.
Redundant by default
Sentry nodes in front of every signer, failover across providers, and an on-call rotation that answers pages at 3 AM. Uptime targets are set per chain and reported to delegators.
/01Keys stay cold
Consensus keys live on dedicated signers behind sentries — never on a VPS image someone else can snapshot. Access is hardware-token gated and logged.
/02Bare metal first
Cloud where it makes sense, owned metal where latency matters. We benchmark per network and re-provision when the chain outgrows the box.
/03Zero rate limits
B2B RPC endpoints are scoped per client, not throttled per IP. Your traffic spike is our capacity problem, agreed in advance — not a 429 on launch day.
/04Operators, not tickets
Delegators and partners reach the people who run the nodes. No tier-1 script readers — if you ask about a missed block, the person answering can check the signer.
/05We never touch funds
Delegation is an on-chain authorization, not a transfer. We hold zero user assets, so the worst we can lose is our own reputation — which is the point.
/0605 — Delegating
FIVE STEPS.
ZERO CUSTODY.
Pick a network
Choose a chain from the networks table above. Each links out to its official explorer.
Open the explorer
Every chain we validate has a public validator page there — commission, self-stake, and missed-block history included.
Find ORYXEN
Search our moniker in the active set. Check the numbers yourself before trusting anyone's homepage.
Delegate
Connect your wallet on the explorer and delegate. Non-custodial — coins stay in your address the whole time.
Track rewards
Rewards accrue per epoch or era, set by the chain's protocol. Compound or withdraw whenever the network allows.
06 — FAQ
ASKED. ANSWERED.
No. Delegation is an on-chain authorization — your coins never leave your wallet's control. We can't move, freeze, or spend them. Unbonding periods are set by each chain's protocol, not by us.
Hardware, bandwidth, monitoring, and the humans answering pages. Commission is set per network and visible on-chain before you delegate. Changes follow each chain's max-change-rate rules — no silent hikes.
Slashing burns a percentage of delegated stake, including ours — that's why we run sentries, isolated signers, and double-sign protection. Our operational history is public on every explorer we validate on.
Through your wallet or the chain's explorer — the same places you delegated. We don't run a custodial dashboard because we don't hold anything to show you a balance of.
Yes — that's the B2B side: relayers, dedicated RPC, white-label validation. We scope capacity per engagement and say no when we're full. Contact below with your chain and timeline.
Each chain gets dedicated hardware and an on-call owner. We'd rather run six networks properly than sixty on autopilot. New chains are added when we can staff them, not when they're trending.
The chain doesn't sleep. Neither does on-call.
TALK TO AN OPERATOR.
Delegation questions, B2B scoping, or a chain you think we should validate — pick a channel. Real operators read every one.
