Figment

• Name: Figment
• URL: https://www.figment.io/
• Category: institutional staking infrastructure / validator operations / staking API and embeddable UI platform
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Figment is a staking operations platform with a validator business attached. Running validators across many networks is not the interesting part; plenty of firms do that. The useful cut is the control plane around APIs, embeddable staking UI, reporting, permissions, and custody integrations that institutions can end up depending on.
• What it does:
  • Operates validator and staking infrastructure for institutions, wallets, custodians, and applications across a wide set of Proof-of-Stake networks
  • Provides a staking API for staking flows, rewards, statements, validator lifecycle actions, and protocol-specific transaction construction across multiple chains
  • Offers Elements, a React component library for embeddable staking flows on Ethereum, Solana, and Babylon
  • Documents integrations with custody and operating platforms such as Fireblocks, BitGo, Coinbase Prime, Ledger, Anchorage, Taurus, and Zodia
  • Supports both public-validator and whitelabel-validator operating models, with first-party docs covering reward flow, commission choices, validator software, and deployment-location considerations
• Key claims:
  • The official site says that on Ethereum Figment is one of the largest independent protocol staking providers and that it supports over 40 established and emerging protocols
  • The Getting Started docs say Figment offers an API for staking and reporting across multiple protocols including Ethereum, Solana, Polkadot, Polygon, Cosmos, Cardano, Avalanche, and NEAR, with published rate limits of 200 requests/second and 3500 requests/minute
  • The Authentication docs say the Figment API uses https://api.figment.io, authenticates with x-api-key, and publishes an OpenAPI 3.1 YAML spec
  • The Elements docs describe a library of embeddable staking UI components with default wallet integrations for Ethereum, Solana, and Babylon plus custom-wallet support
  • The public-vs-whitelabel validator docs make clear that Figment is not only a public staking endpoint: it also supports branded or custom validator deployments with configurable reward flow, software choices, and jurisdiction/location considerations
  • The Fireblocks guide and app role-permissions docs show Figment as an operational platform for teams, not just a validator brand, because they expose custody integrations, API/app split, and role-based controls
• Whitepaper: No classic standalone whitepaper or litepaper was found in the official materials reviewed during this pass. The strongest primary sources were Figment’s official website, docs index, API/authentication pages, Elements docs, validator-model docs, custody-integration guides, app-permissions docs, and public GitHub organization; see ../whitepapers/figment-primary-sources-2026-04-26.md.
• Sources:
  • https://www.figment.io/
  • https://docs.figment.io/llms.txt
  • https://docs.figment.io/reference/getting-started-1.md
  • https://docs.figment.io/reference/authentication.md
  • https://docs.figment.io/docs/elements.md
  • https://docs.figment.io/docs/public-vs-whitelabel-validator.md
  • https://docs.figment.io/docs/fireblocks.md
  • https://docs.figment.io/docs/figment-app-roles-and-permissions.md
  • https://github.com/figment-networks

Internal linkages

• Keep this note on the clearest adjacent reads: liquid-collective, stakewise, and chorus-one.

• Do not spend stronger-note graph budget validating every validator, custodian, or DVT branch. The point here is institutional staking operations as a control plane.

• Last reviewed: 2026-06-05 UTC