On this page
The RealValidator Team Editorial team

Figment and Binance Staking are two of the largest single-validator stake positions in this wiki's directory at epoch 971 — 15,439,773 SOL and 13,530,771 SOL respectively, per Stakewiz — but the comparison splits cleanly on three axes: Figment is an independent staking-infrastructure operator on OVH Canada at 7% base and 7% Jito MEV commission, while Binance Staking is an exchange-operated, custodial validator on AWS Ashburn at 0% base and 0% Jito MEV commission.

At a glance

Metric Figment Binance Staking
Active stake 15,439,773 SOL — 1.000% of network (Stakewiz, epoch 971) 13,530,771 SOL — 0.876% of network (Stakewiz, epoch 971)
Wiz Score 46.67 (Stakewiz, epoch 971) 61.51 (Stakewiz, epoch 971)
30-day trailing skip rate 0.028% — vs 0.14% network median (Stakewiz, epoch 971) 0.12% — vs 0.14% network median (Stakewiz, epoch 971)
Base commission 7% (Stakewiz, epoch 971) 0% (Stakewiz, epoch 971)
Jito MEV commission 7% (jito_commission_bps: 700, epoch 971) 0% (jito_commission_bps: 0, epoch 971)
Total APY estimate 5.48% — 5.36% staking + 0.12% Jito MEV (Stakewiz, epoch 971) 5.92% — 5.79% staking + 0.13% Jito MEV (Stakewiz, epoch 971)
ASN + city AS16276 OVH Infrastructures Canada — Toronto, Canada (Stakewiz, epoch 971) AS14618 Amazon Data Services Northern Virginia (AWS) — Ashburn, United States (Stakewiz, epoch 971)
Software version Agave 3.1.14 — version_valid: true (Stakewiz, epoch 971) Agave 4.0.0-rc.1 — version_valid: true (Stakewiz, epoch 971)
SFDP eligibility 7% base commission exceeds the 5% SFDP cap; 15.44M SOL external stake above the 1,000,000 SOL ceiling — Foundation residual and matching withdrawn (per solana.org/delegation-criteria) 0% base commission within the 5% SFDP cap; 13.53M SOL external stake above the 1,000,000 SOL ceiling — Foundation residual and matching withdrawn (per solana.org/delegation-criteria)

Where they're similar

  • Both run the Jito client (is_jito: true at epoch 971 per Stakewiz) and route MEV through the Jito Block Engine.
  • Both sit above the 1,000,000 SOL external-stake ceiling at which SFDP Foundation residual delegation and matching are withdrawn — neither receives Foundation stake under the current parameter set, irrespective of commission.
  • Both post sub-network-median 30-day trailing skip rates (0.028% Figment, 0.12% Binance Staking) against a 0.14% Stakewiz network median at epoch 971.
  • Both carry a Stakewiz superminority_penalty of -20, applied to validators whose stake contributes to the network's superminority risk threshold.
  • Both are above Stakewiz's above_halt_line marker — the bucket where further concentration imposes score-level cost — and both receive a 0 stake_weight_score (Stakewiz components, epoch 971).
  • Neither is delinquent at the epoch 971 snapshot.

Where they diverge

Operator type and custody model. Figment is an institutional staking-infrastructure operator with multi-chain coverage — stakers delegate to Figment from self-custodied wallets. Binance Staking is the on-chain endpoint for SOL delegated through Binance's staking product, where exchange customers stake SOL held in custody on the platform. The on-chain metrics describe the operator-of-record either way; the trust model exposed to the end-user is materially different — a Binance Staking delegator faces exchange custody risk in addition to validator-operator risk, a Figment delegator faces only the latter.

Commission stack. Figment retains 7% on base and 7% on Jito MEV (700 bps each). Binance Staking retains 0% on both. The structural meaning differs: Figment's commission is the operator's validator revenue; Binance Staking's 0% on-chain rate is the validator-level pass-through, with Binance separately retaining a platform fee from the customer-facing yield on its custodial product. The Stakewiz total APY estimate gap is 0.44 percentage points (5.48% vs 5.92%, epoch 971), but a Binance customer's realized yield depends on the platform-level fee — not visible in on-chain data.

Wiz Score composition. Figment's 46.67 reflects strong skip-rate (9.88/10) and vote-success (29.86/30) components, a 6/20 commission drag from the 7% rate, and a -20 superminority penalty. Binance Staking's 61.51 reflects 9.46/10 skip-rate, 29.82/30 vote-success, 20/20 commission, and the same -20 superminority penalty. The gap is primarily the commission component — Figment's 7% rate costs it 14 points relative to Binance Staking's 0% (Stakewiz components, epoch 971).

Skip rate. Figment posts 0.028% trailing 30-epoch; Binance Staking posts 0.12%. Both are below the 0.14% network median, but Binance Staking's figure is approximately 4x Figment's at this snapshot. The absolute gap is small in either direction; for SFDP threshold purposes, both sit well below the network-average + 5pp ceiling.

ASN profile. Figment is on AS16276 (OVH Canada), Toronto — 2.79% ASN concentration, well below the 25% SFDP threshold. Binance Staking is on AS14618 (AWS Ashburn) — Stakewiz reports 0% asn_concentration, reflecting AWS's broad infrastructure footprint not concentrating Solana validator stake on this ASN. Hyperscaler-hosted validators face a separate decentralization question at the cloud-provider level rather than the ASN level; the SFDP rule operates on ASN, so AWS passes the specific threshold.

Software version. Figment runs Agave 3.1.14; Binance Staking runs Agave 4.0.0-rc.1. Both flagged version_valid: true; neither incurs a version-recency penalty at epoch 971.

Public information surface. Figment's Stakewiz description and website fields are empty; published material lives off-chain at figment.io. Binance Staking publishes no operator description on Stakewiz either, with website: https://www.binance.com populated. Both operators provide less on-chain identity information than smaller, brand-forward validators in this directory.

Infrastructure

Figment is on AS16276 (OVH Canada) in Toronto (43.65°N, 79.38°W) at TPU IP 72.251.11.24, running Agave 3.1.14. The ASN carries 2.79% of network stake; Toronto carries 0.17% — both sparsely populated.

Binance Staking is on AS14618 (AWS Northern Virginia) in Ashburn (39.04°N, 77.49°W) at TPU IP 67.202.63.79, running Agave 4.0.0-rc.1. AWS Ashburn carries 0% asn_concentration per Stakewiz; Ashburn city carries 0.24%.

Neither validator runs Frankendancer at epoch 971. Both pass the May 1, 2026 SFDP ASN-concentration threshold cleanly.

Stake-pool inclusion and SFDP

Figment's 7% base commission exceeds the 5% SFDP cap, placing it outside SFDP eligibility on commission grounds — independent of its 15.44M SOL stake being above the 1,000,000 SOL Foundation-delegation ceiling. First epoch with stake: 80, spanning approximately 891 epochs at epoch 971.

Binance Staking's 0%/0% commission meets the SFDP caps, but the 13.53M SOL external stake is above the 1,000,000 SOL ceiling — Foundation residual and matching are withdrawn under current parameters. First epoch with stake: 253, spanning approximately 718 epochs at epoch 971.

Stake-pool inclusion across Marinade SAM, the Jito Stake Pool, and SolBlaze is governed by each pool's independent selection criteria — Stakewiz does not surface pool inclusion in the API fields used here.

Trade-offs for stakers

  • A staker prioritizing self-custody delegation from a self-managed wallet (Figment is third-party-operator-only; Binance Staking is exchange-custodied at the user-facing layer) → Figment.
  • A staker prioritizing the highest Stakewiz total APY pass-through (5.92% vs 5.48%, epoch 971) → Binance Staking.
  • A staker prioritizing the lowest 30-day trailing skip rate (0.028% vs 0.12%, Stakewiz, epoch 971) → Figment.
  • A staker prioritizing Wiz Score as a composite (61.51 vs 46.67, Stakewiz, epoch 971) → Binance Staking.
  • A staker prioritizing operator independence from a single-jurisdiction exchange entity → Figment.
  • A staker prioritizing exposure to a non-hyperscaler ASN (OVH Canada vs AWS Ashburn) → Figment.
  • A staker for whom the 5,000 SOL-and-above bracket of self-custodied exposure is the binding constraint → both validators are above 13M SOL stake and neither receives Foundation residual delegation; the pairing does not change SFDP exposure either way.

Metrics sourced from Stakewiz cache at epoch 971, snapshot 2026-05-15. Skip rate, commission, and APY values update at epoch boundaries; verify against the live Stakewiz profile when citing for current decisions.