Skip to content

Figment Integration for Omnibus Staking Batches and Statement Tie-Out

When staking firms, custodians and exchanges stake client assets through Figment, Protofire builds batching and per-client reward splits. We also build a month-end tie-out to Figment's statement and controls on exit calls. Protofire was a top-3 Graph indexer by indexing rewards, 2020 to 2024, and built a Safenet staking interface.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. What Figment reports
  3. Figment facts
  4. What you get
  5. Keys and exits
  6. EU firms
  7. Why Protofire
  8. How the work goes
  9. How work starts
  10. Not the right fit
  11. Related guides and services
  12. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

Matching client rewards to Figment's statement

A Figment integration closes the gap between the client rewards in a firm's own books and Figment's statement. For example, your clients' ETH is staked through Figment, and finance asks why the client rewards do not add up to the statement.

Figment's API covers Ethereum, Solana, Polkadot, Polygon, Cosmos, Cardano, Avalanche and NEAR. Figment's docs walk through staking from eight custody and wallet platforms.

Figment's omnibus guide lists four systems that the staking firm runs itself. They are batching, balance monitoring, per-user accounting and reward distribution, and the guide marks the last three "off-chain".

Figment reports rewards per validator or Solana stake account, and it keeps Solana epoch detail for 60 days. Figment's reports leave out an address staked outside Figment's transaction builder until someone registers that address. Figment also has two Ethereum reward endpoints. A ledger fed late, or fed from the wrong endpoint, shows clients figures that the firm cannot match to its wallet.

Who owns each layer between Figment and the client ledger

Figment builds each staking transaction, and the firm's custodian signs it. Figment reports rewards per validator or stake account, and the firm's books split them per client.

The firm

Client ledger

The ledger holds each client's stake, rewards, penalties and pending withdrawals, together with client statements.

Wallet or custodian

The firm's wallet holds the withdrawal rights and the approval policy behind each deposit, withdrawal and exit.
Figment

Validators

These are Ethereum validators whose keys Figment keeps, plus validators that clients delegate to.

Figment API

The API provides unsigned transactions, validator status, rewards data and the monthly statement CSV.
Protofire builds

Batching and pre-sign checks

It covers the daily netting run and the checks on Figment's data before the custodian signs.

Rewards ledger

It pulls rewards each day, archives them, splits them per client and ties them out at month end.

Exit and status monitor

It polls validator states, requires a second approver on exit calls and alerts on stalled exits.

Figment reports per validator, and the firm reports per client

Figment's reports cover delegations made through Figment and stop at the validator, stake account or withdrawal address.

Rewards

From Figment: Figment reports rewards per Ethereum validator or Solana stake account and rolls them up by withdrawal address (Figment).

On the firm's side: Each period is split by client share, starting from Figment's own formula.

Penalties

From Figment: Missed attestations are netted against Ethereum rewards. With include_penalties=true, the API returns a separate consensus_penalty entry, with data from 12 February 2026 (Figment).

On the firm's side: The books show a penalty line that clients can read, and a rule covers earlier periods.

Statements

From Figment: Figment issues one CSV a month, with FIGMENT_COMMISSION, NET_REWARDS_USD and REBATE columns (Figment).

On the firm's side: The books produce client statements, and ledger totals are matched to that CSV at month end.

Address coverage

From Figment: Coverage is automatic for addresses staked through Figment's transaction builder and manual on NEAR, Cosmos, Polkadot and Vaulta (Figment).

On the firm's side: A track call registers each wallet staked elsewhere.

Figment's interfaces, data timing and status page

Interfaces
Figment's API is REST at api.figment.io, with an x-api-key header. Keys are Read/Write or Read-Only, and test or production (Figment).
Rewards data
Figment publishes rewards within 3 hours of period end, in UTC days, with slashing and penalties as negative rewards (Figment).
Statements
Figment issues a monthly CSV in the Figment app and through GET /statements, on the 5th business day (Figment).
Status
A public status page covers validators, app, API, docs and trust center. The docs give no SLA figure (status).

Checked November 2026 against Figment's developer documentation, API reference and status page. Protofire integrates Figment for firms that have chosen it.

What your finance team and key holders get from a Figment integration

Client rewards that add up to Figment's statement

Finance gets client rewards that match Figment's monthly figures per address, and a break list for the periods that differ. Protofire pulls the rewards for each UTC day after Figment publishes them. We split them by client share, archive them and book a Solana rebate on its own line.

One batch a day, traced to each client request in it

Operations can show which batch included which client request. Figment's omnibus guide closes a day at 00:00 UTC. Protofire builds the netting run, the target balance per validator and the choice between a top-up, a partial withdrawal and a full exit. Provisioning calls send our batch ID as the X-Figment-Idempotency-Key.

Transactions checked before your custodian signs

Figment warns that a valid deposit signature can still come from a man-in-the-middle validator. So the connector that Protofire builds checks figment_signature against Figment's public key. Next, the connector hands your signer the format that the signer accepts. For example, for Fireblocks it is contract call data, and for an HSM it is a 32-byte digest. On Solana, a blockhash expires in about 60 to 90 seconds. A nonce account replaces the blockhash, so a slow approval chain can finish.

Exit calls that wait for a second person

A Read/Write key can start an exit that Figment signs. Protofire builds an exit service that holds that key. The service calls Exit Validators after a second person at your firm approves. Your firm can revoke the key. Your key holders run an exit drill, and Figment's lifecycle states are logged during the drill.

An alert when a staking activity stalls or fails

Figment's states are read by polling, so someone has to watch them. An alert goes to a named person when an activity is stuck in_progress or ends failed or expired. An exit request that does not reach active_exiting also goes to a named person.

Keys and exits on Ethereum, Solana and other networks

On Ethereum, Figment holds the validator signing keys, and the firm's wallet holds the right to withdraw.The firm's wallet also signs each deposit and withdrawal. For each network, Figment documents how a firm unstakes if Figment's own tools go away.

Figment creates the validator keypairs on its infrastructure and manages the BLS key for attestations and proposals. Figment documents three exits and supports two of them. The firm itself sends the third exit, which is triggered on the execution layer. Pre-signed exit messages are encrypted to one GPG or RSA key per chain, and the firm holds that key. An on-demand exit works differently. It starts from an Exit Validators call, which a Read-Only key cannot make. Figment signs an on-demand exit with the validator key. Figment approves exits for fewer than 100 validators automatically and submits them two hours later. An exit before 256 epochs of activity can look successful on the execution layer and be ignored.

Our record: Graph reward data and a Safenet staking interface

Two pieces of Protofire's work are backed by third-party pages, and the third is our own blueprint.

A Graph indexer ranked by its rewards

Protofire was a top-3 Graph indexer by indexing rewards, 2020 to 2024. On The Graph's Ethereum network, Protofire ranked third of 638 by cumulative indexing rewards from December 2020 to January 2024. Protofire's indexer is inactive today. The indexer work applies to a Figment integration, because a network's reward data is the record that a ledger has to match. The Graph case describes Protofire's work on The Graph.

A staking interface for SAFE holders

Protofire built an alternative interface for staking SAFE on Safenet, with development supported by a grant from the Safe Foundation. The Safe Foundation selected us in May 2026.

A blueprint for custody clients

Protofire's staking blueprint for custody clients sets out the method behind the client books. The blueprint covers consent and client reporting.

How the work goes, from statement review to exit drill

  1. Step 1

    A month of Figment statements read against your ledger

    An engineer reads one month of Figment's statement CSV against your ledger and wallet model. A written proposal follows. It picks a gross or net booking basis and maps your networks to the modules that Protofire builds.
  2. Step 2

    The rewards archive first, then batching and the exit service

    The rewards pull and the archive go in first, because Figment's 60-day window for Solana epoch detail starts closing on day one. Batching, the pre-sign checks and the exit service come next. Protofire builds them for the signer you use. Your key holders run the exit drill last.
  3. Step 3

    What your firm owns and who runs the integration

    The code, configuration and runbooks are yours. Your staff create the API keys in the Figment app, store them in your vault and may revoke them. Your key holders keep the GPG or RSA key that decrypts exit messages. Your team runs the integration, or Protofire operates it under a written scope. That scope lists each Figment endpoint that a Protofire service writes to.

How work with Protofire starts

You send your networks, custodian and wallet model, plus one month of Figment's statement CSV.Figment holds the Ethereum validator keys that it generates, on the terms of its contract with you. Your firm or custodian controls each withdrawal_address and each Solana stake authority. The terms in this section apply to each phase, as set out on how we work.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

Four cases where Figment's own tools are enough

  • Your custodian already stakes with Figment in its console, and Figment's monthly statement is enough for your finance team.
  • One entity stakes through Figment's API with no client ledger behind the stake. Figment's recipes for Fireblocks or a hot wallet cover that case.
  • You want to run your own validators under your own keys. Protofire's validator operations page covers that case.
  • Your legal position on client staking is still open. Your counsel answers that question before a build starts.

On a Figment project, Protofire takes no part in license applications or legal opinions.

FAQ

What is a Figment integration?
A Figment integration connects Figment's staking API, rewards data and monthly statements to a firm's custodian and client ledger. Figment builds unsigned transactions and reports rewards per validator or stake account. Protofire builds the rest of the integration. Protofire's part includes batching and the routing of each transaction to the firm's signer. It also includes per-client reward splits and a month-end match to Figment's statement CSV.
Who can build a Figment integration for a custodian, a bank or an exchange?
Protofire builds the firm's own side of a Figment integration. That side is the client ledger and batching, plus the signing path and the exit controls. Figment's "sales engineering team" helps banks, asset managers and exchanges implement the API itself, according to Fireblocks. So the split is Figment for the API and Protofire for the books.
Should a firm book Figment's gross or net Ethereum rewards?
The choice depends on what the firm reports to its clients. Figment's rewards endpoint returns gross rewards, including consensus rewards not yet swept to the wallet. The net endpoint returns swept consensus rewards and execution-layer rewards after Figment's onchain split, dated when the wallet received them. The firm's ledger picks one basis and reconciles to it.
Which Figment API key does each job need?
Reporting, status polling and the statement pull run on a Read-Only key, which cannot call Create Validators or Exit Validators. The batching run and the exit service need a Read/Write key. A Read/Write key can start an exit that Figment signs, with no step in your custody. Your staff store the Read/Write key in your vault, and the batching run and the exit service read it from there.
How does Figment record slashing and penalties?
Figment records slashing and penalties as negative rewards in its data. A slashed Ethereum validator moves to active_slashed, then to exited_slashed for 2^13 epochs, about 36 days, before withdrawal (Figment). The firm's contract with Figment and the firm's terms with clients set who bears the loss.

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.