Hubra
Validator · Philosophy

Three principles,and the validator behind them.

A validator is more than uptime. It is the choices an operator makes - what to ship, where to run, which counterparties to trust. Six years into building on Solana, these are ours, written down so they can be held to.

Tenet № i
Safety, first

Native delegation is the protocol's job. Where we exercise judgment is raSOL - and the LST routes only through audited, mature, transparent protocols.

Tenet № ii
Decentralization, in practice

We move the validator between regions to keep stake out of hot zones. The network is measurable; we follow what it measures.

Tenet № iii
Innovation, when it is right

Among the first to run Jito-Solana. Among the first on Frankendancer. Among the first to ship the DoubleZero sidecar.

Volume № I · Safety

Where judgmentactually lives.

Native delegation is the runtime's job. Stake accounts are custodial only by their owner; the validator never moves a lamport, never holds keys, never decides where SOL goes. That part of the system is beyond debate.

Counterparty discipline begins one layer up - at raSOL. The moment our LST routes through a smart contract, the protocol's solvency becomes our concern. Every venue raSOL touches, and every venue raSOL liquidity is paired into, passes the same four filters. None are negotiable, none are waived for partners, narratives, or short-term yield.

01
Audited code, in public
Multiple independent audits, with reports we can read. Private audits are not a route raSOL takes.
02
Tenured TVL
raSOL does not write the first cheque. A protocol earns its place by surviving a full market cycle.
03
Identifiable team
Public reputations and shipping history. Anonymity is fine; un-accountability is not.
04
Reversible governance
Documented signers, time-locked upgrades, on-chain proposal trails. We need to know who can change the rules, and how fast.
The roster

Where raSOL is allowed to route.

The list is intentionally short. New names are added only after a full review cycle - never on momentum, never on a partnership.

  • Sanctum
    LST liquidity layer

    Audited router, verifiable reserves, public governance - the layer raSOL is built on.

  • Kamino
    Lending & structured yield

    Solana's most battle-tested lending market. Every raSOL position is bound by its liquidation engine, not by trust.

  • Jupiter
    On-chain aggregator

    Solana's deepest on-chain exchange - consolidated liquidity, open-source, audited, and transparent in incident response.

  • Orca
    Whirlpools / spot routing

    Long-running concentrated-liquidity venue with a predictable fee model and one of the cleanest incident histories on Solana.

What we will not do
  • Be the first money in an unaudited contract.
  • Route through anonymous, undocumented teams.
  • Take yield that we cannot trace to a protocol mechanic.
  • Vendor a partner because of stake or co-marketing.
The trade-off, openly

A short roster means raSOL sometimes lists later than the field, or skips a pool that is paying more this week. That is the cost of running an LST built to compound for years, not quarters.

Volume № II · Decentralization

We movewhere the stake isn't.

Most operators pick a datacenter once and stay there for years. Solana's decentralization score punishes that: every region that crowds reduces the network's resilience. We treat geography as an operating variable, not a fixture - and we move when the math says we should.

Validator hubs · concentration map
Where Solana stake clusters today
Saturated · avoidModerateSparse · candidate
  • Frankfurt
    DE
    AVOID
  • Amsterdam
    NL
    AVOID
  • Tokyo
    JP
    AVOID
  • New York
    US
    MOD.
  • Vienna
    AT
    MOD.
  • Singapore
    SG
    CAND.
  • Helsinki
    FI
    CAND.
  • Lisbon
    PT
    CAND.
  • Warsaw
    PL
    CAND.
  • Tel Aviv
    IL
    CAND.
Reading the chartBars rank validator hubs by stake density. We operate in the sparse tier and rotate through it. The saturated tier is where our delegation does not go, regardless of incentive.
  1. 01

    We move, on a schedule

    Stake concentration is a measured, public number. When the region we operate in trends toward saturation, we relocate - not as a marketing gesture, but as part of normal operations.

  2. 02

    We follow the Nakamoto coefficient

    Solana scores datacenters as well as operators. A validator in a region with three other heavyweights weakens the network's resilience score; the same validator in a quieter zone strengthens it.

  3. 03

    We diversify jurisdictions

    Geography is also legal exposure. Rotating across regulatory regimes - EU, EFTA, APAC, Middle East - reduces the chance that one ruling, one outage, one censorship event silences a meaningful slice of stake at once.

Concentration figures shown are illustrative orderings of well-known Solana validator hubs. Real-time numbers are tracked in public on stakeview.app and validators.app - both worth bookmarking.

Volume № III · Innovation

First wave,when first wave is right.

New validator clients only earn delegated stake after they earn it. But once they have - through audits, testnet hardening, and a credible team - we move quickly. Early adoption is how operators help the network test its own future.

Validator stack · adoption ledger
What the Hubra validator has run, and when
ReferenceEarly waveFirst wave
202020232026
  • Solana Labs / Agave
    REFERENCE CLIENT
  • Jito-Solana
    2022
    MEV REDISTRIBUTION
  • Frankendancer
    2024
    INDEPENDENT CLIENT
  • DoubleZero sidecar
    2025
    NETWORK TRANSPORT
  • Jito-BAM
    2025
    BLOCK-ASSEMBLY STACK
  1. 01Genesis cohort

    Solana Labs / Agave

    The reference client.
    2020 - present

    Live on Agave since launch, upgraded through every major release. The default is the floor, not the ceiling.

  2. 02First wave · both releases

    Jito-Solana → Jito-BAM

    MEV redistributed, then formalized.
    Adopted early · BAM live today

    Adopted Jito-Solana early to redirect MEV back to delegators. Now running Jito-BAM, the formal block-assembly stack that succeeds it.

  3. 03Early validator wave

    Firedancer / Frankendancer

    Independent client diversity.
    Adopted on testnet, then mainnet

    Joined the Frankendancer cohort early, fed bug reports back to Jump Crypto, and moved stake forward as builds matured.

  4. 04Day-one cohort

    DoubleZero

    A faster, fairer transport.
    Sidecar, day-one cohort

    Day-one cohort on the sidecar - cuts tail-latency, lowers bandwidth pressure, and helps the network test the design at scale.

The discipline

Innovation answers to safety, never the other way around.

Adopting early without breaking is a research discipline. We track client release notes, run staged rollouts on testnet first, keep rollback paths warm, and we hold a public commitment never to advance a release without confirming it on a fresh hardware unit outside the production cluster. That is the only way early can also be safe.

Volume № IV · Lineage

Six years on Solana,one team, three names.

Hubra is not a fresh validator hunting for stake. It is the latest chapter of a studio that has been shipping Solana infrastructure since 2020 - first as Avaulto, then as SolanaHub, now consolidated under one brand. The track record is public; the GitHub history is unbroken.

  1. Genesis
    2020

    Validator goes live.

    The team brought the validator online in Solana's first year and has run continuously since. The early years were quiet, technical work - keeping the node up, watching the runtime mature, learning the network from the inside.

    Mainnet validatorContinuous uptime
  2. Avaulto
    2021 - 2023

    Public-good tooling, in the open.

    Operating under the Avaulto name, the team published open-source utilities for the Solana validator community: a Rust-based metrics exporter for Prometheus, a reward-history lookup keyed by vote account, and a modular monitoring stack that other operators still run today.

    solana-monitor-2solana-reward-historyPrometheus exporter (Rust)
  3. SolanaHub
    2023 - 2024

    From operators to users.

    SolanaHub launched as the consumer side of the same studio: a unified dashboard for portfolio, swaps, staking, NFTs, and DeFi positions. It earned a place in the Solana ecosystem the slow way - by shipping, listening, and iterating in public.

    solanahub.appWallet & DeFi dashboardOpen-source frontend
  4. raSOL
    2024

    An LST on Sanctum.

    raSOL - the team's liquid staking token - launched on Sanctum's liquidity layer, integrated across Kamino, Meteora, Orca, and the wider Solana DeFi map. The principles from the validator carried straight into the product: audited counterparties, transparent reserves, and no surprises.

    raSOL · Sanctum LSTKamino · Meteora · loopscale · OrcaVerifiable reserves
  5. Hubra
    2025 - present

    One brand, one focus.

    The validator, the LST, the dashboard, and the upcoming product line consolidated under Hubra - a single name with a single thesis. Same team, same six-year body of work, now finished arguing with a long brand and free to build the next chapter.

    Hubra validatorNative staking · LSTUSDC Stake
6years
Continuous validator uptime
3brands
Avaulto · SolanaHub · Hubra
1team
Same operators, same thesis
Volume № V · Receipts

Don't take our word for it.Take the keys.

Two addresses identify this validator on Solana - one for the node, one for the stake. They are open primary keys: any explorer will return the full record. Verify everything written on this page.

№ IValidator identity

The signing key.

The keypair the node signs blocks and votes with. Same identity since the validator went live in 2020 - never rotated, never re-issued.

Base58 · Ed2551943 characters
RAuSNo4DRjo83uGhdgg4fPqYBVszi1KsrQGpqcPHK1D
View on chain
№ IIVote account

The stake address.

Where stake delegates and where credits accrue. Resolve it on any explorer to read the full block-production and reward history.

Base58 · Ed2551944 characters
7K8DVxtNJGnMtUY1CQJT5jcs8sFGSZTDiG7kowvFpECh
View on chain
Live on mainnet

If you delegate to anything other than the addresses on this page, you are not staking with Hubra.

Volume № V · Common questions

Principles, examined.

The questions allocators ask once they have read the philosophy - and the answers we are willing to publish.

It applies to raSOL - our LST - not to native stake accounts. Delegated SOL is governed entirely by the Solana stake program; the validator never holds, moves, or has any say over it. Counterparty discipline matters one layer up: when raSOL is paired into liquidity, deposited into a lending market, or routed through a DEX, we are choosing protocols on behalf of holders. That is where the four filters live.

Multiple independent audits with public reports, sticky TVL across at least one full market cycle, an identifiable team with on-chain history, and reversible governance with documented signers. All four. We do not waive any of them for incumbents, partners, or short-term yield.

Solana publishes datacenter and operator concentration in real time. When the region we operate in trends toward saturation, we relocate the validator - physical hardware, peering, and all - into a less-stake-dense zone. The aim is to strengthen the network's resilience score, not to chase cheaper hosting.

Done badly, yes. We rotate by bringing up the new node alongside the old one, syncing it on testnet first, hot-cloning ledger state during a low-skip window, and only switching identities once the replacement is stable. Stake never sees a gap. Six years of operating means we have done this enough times to make it routine.

Networks earn resilience by running independent clients in production, not by reading audits. Early adoption - after a credible audit and testnet hardening - is how an operator helps the network test its own future. We have done it for Jito, Frankendancer, and the DoubleZero sidecar, and we will do it again when the next credible client arrives.

Same team, three brand chapters. The studio launched the validator and shipped open-source operator tooling under Avaulto, then built the SolanaHub consumer dashboard, then consolidated the validator, the LST, and the upcoming product line under Hubra. The GitHub history is continuous and public.

We exit. If a protocol on the roster fails an audit, replaces its team without disclosure, or loses governance hygiene, it leaves the roster - and any of our routes that depend on it are unwound on a published schedule. Counterparty selection is not a one-time decision; it is the discipline.