Skip to content

Blockdaemon Integration for Firms That Stake Client Assets

Firms staking client assets through Blockdaemon need four parts its reports leave to them. Each reward is posted once, days close at a processed epoch, rewards are split per client and exits reach their signer. Protofire builds them. Protofire was a top-3 Graph indexer by indexing rewards, 2020 to 2024.

Luis Medeiros

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

On this page
  1. Overview
  2. Why ledgers disagree
  3. What you get
  4. Event delivery
  5. Blockdaemon facts
  6. Keys and addresses
  7. Why Protofire
  8. How the project runs
  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

What Blockdaemon provides and what it leaves to your firm

A Blockdaemon integration starts from one gap: none of Blockdaemon's services knows your client. You have chosen Blockdaemon to run your validators, and month-end shows whether Blockdaemon's reward feed and your client ledger agree.

Blockdaemon operates the validators and keeps their keys in a remote signing service, apart from the nodes. Blockdaemon's Staking API hands your signer unsigned transactions to complete. The Staking Reporting API serves rewards "for addresses, validators, and plans".

From a Blockdaemon validator to a client's statement

Stake transactions go out from the firm's signer. Reward data comes back through Blockdaemon, and the firm's allocation splits that data before anything is posted.

The firm

Client ledger and statements

The ledger records each client's staked, pending and exiting positions, reward entries and fees.

Signer and withdrawal address

The custodian or MPC wallet signs stake and exit transactions, and the withdrawal address receives rewards.
Blockdaemon

APIs, events and validators

Blockdaemon runs the validators and serves unsigned stake transactions, rewards per validator and epoch, a health status and reward events.
Protofire builds

Stake connector

The connector sends intents with idempotency keys, routes unsigned transactions to the signer and tracks exits.

Event receiver and backfill

The receiver checks each signature, drops repeats and fills gaps, and it posts each reward once in whatever order it arrives.

Allocation and close

The allocation job splits each validator's reward among clients, closes the day at a processed epoch and posts to the ledger.

Why Blockdaemon reward data and client ledgers disagree

A ledger that posts each Blockdaemon message on arrival counts some rewards twice and closes a month on partial data.Blockdaemon's Event Streaming delivers "at least once, not exactly once". Event Streaming promises no order and keeps messages for one week. Reward processing can also lag behind the chain. The Reporting API marks itself DEGRADED when it runs two or more epochs behind.

The split of rewards per client is a second gap. Blockdaemon reports by address, validator and plan, and its reward events do not name a client. A report shows a client's share when that client stakes from its own withdrawal address. When many clients share one address, the split has to come from the firm's own records.

What you get from a Blockdaemon integration with Protofire

Rewards posted once per client

Each reward is posted once, per client, in your core banking system or client ledger. Each entry records the validator public key and the epoch the reward came from. Protofire builds the event receiver, which checks the signature, stores each message by uuid and drops repeats.

Days closed at a processed epoch

Finance sees which days are final. Before posting, the close job reads Blockdaemon's health endpoint. A day closed while processing lags gets a provisional flag, and late epochs restate that day.

Rewards split per client from an allocation record

Each validator is tied to one client, or to a client's share of a pooled address. That share is taken from the record as it was when the epoch began. Protofire builds the allocation record, the wei and gwei conversion, and the reversals for blocks that a reorg event names.

Stake transactions checked before your signer receives them

Protofire's connector checks each unsigned stake transaction before it reaches your signer. The connector decodes the transaction and checks the contract address and the amount. It also checks each validator's withdrawal credentials against your withdrawal address. Blockdaemon's Post Stake Intent holds validators "for 90 days or until the returned transaction is signed and confirmed". The connector removes an intent older than your age limit from the signer queue.

Exits sent under a credential you hold

Your staff record a client's exit instruction. The instruction is relayed under an exit-capable credential that you hold and can revoke. The Staking API key made in the Blockdaemon app "will not be able to exit ETH validators". The position keeps its exiting status until the full withdrawal arrives at your withdrawal address.

How the receiver handles Blockdaemon's event delivery

Blockdaemon's event feed can repeat messages, does not follow chain order and keeps messages for one week.The receiver that Protofire builds turns that feed into a complete record.

Repeats

Blockdaemon's delivery contract: The same event can arrive more than once. The uuid "is the only field guaranteed to uniquely identify a message".

What your receiver does: The receiver stores each uuid and drops repeats before posting logic runs.

Order

Blockdaemon's delivery contract: Blockdaemon does not promise that block N arrives before block N+1.

What your receiver does: The receiver posts each reward once per validator key and epoch. Completeness is left to the epoch close.

Failures

Blockdaemon's delivery contract: A non-2xx response counts as failed. After 10 failures in a row, the target's status changes to failed, and delivery stops until the target verifies again.

What your receiver does: The receiver stores each message first, answers 2xx and alerts on the first failed status.

Retention

Blockdaemon's delivery contract: Events are kept for one week on the broadcaster topic. After that, events "are permanently lost".

What your receiver does: The receiver fills older reward gaps from the Reporting API. It keeps its own store, which can be replayed after the window closes.

Origin

Blockdaemon's delivery contract: The signature is HMAC-SHA256, sent in x-bd-webhooks-signature.

What your receiver does: The receiver rejects a message whose signature fails.

Blockdaemon products, reporting coverage and terms

Products
Blockdaemon offers the Staking API, the Staking Reporting API and validator operation (docs). Blockdaemon also offers Event Streaming for staking status and reward events on Ethereum Mainnet and Hoodi.
Reporting coverage
The Reporting API covers Cardano, Cosmos, Ethereum, NEAR, Polkadot, Polygon and Solana, at epoch level and in roll-ups. It returns newline-delimited JSON, JSON or CSV (docs).
Slashing in the terms
Blockdaemon's terms were updated 19 December 2025. They exclude liability for slashing, missed rewards or other penalties unless caused "directly and solely" by Blockdaemon's gross negligence or willful misconduct. The clause comes with listed exclusions (section 16.2, terms). The firm's counsel reads its own order form against the terms.

Checked November 2026 against Blockdaemon's documentation and terms. Protofire integrates Blockdaemon for firms that have chosen it.

Who holds the validator keys and the withdrawal address

Blockdaemon keeps the keys of the validators it runs, and the firm keeps the withdrawal address.The withdrawal address is the setting you cannot undo. It is set in the stake intent and fixed for the validator's life. Blockdaemon's Customer Success can map the address, on a ticket, to "a regionally-pinned staking plan". After that mapping, validators created with the address deploy in the plan's region. Plan the addresses before the first deposit.

With Blockdaemon's MPC signer, who holds which key depends on the deployment. Blockdaemon offers the MPC stack in the client's perimeter, on dedicated Blockdaemon infrastructure, or as a hybrid with signing inside the client's perimeter. After launch, Blockdaemon holds the validator keys. Blockdaemon's terms exclude its liability for slashing except in the narrow case the terms name. You keep the signer, the exit credential and the client records.

Each validator account can only be assigned a single withdrawal address, one time. Once an address is chosen and submitted to the consensus layer, this cannot be undone or changed again.
ethereum.org, Open-source Ethereum community website · Staking withdrawals page, read November 2026

Our record: Graph indexing and Glif Nodes RPC on Filecoin

Protofire's record applies to a Blockdaemon integration in two ways.Protofire has worked as a staked network operator, and it built and runs a public RPC service.

Protofire was a top-3 Graph indexer by indexing rewards, 2020 to 2024. The indexer role is a staked operator role on The Graph's network. The Graph's community introduced Protofire as an indexer in 2021, and the Graph case sets out the work.

Protofire built Glif Nodes, which answers public RPC calls on Filecoin, and runs it today. Filecoin's newsletter thanked Protofire "for running Glif Nodes RPC" in May 2024.

How a Blockdaemon project with Protofire runs

  1. Step 1

    Tracing one validator before the build

    Protofire follows one validator's rewards from your exports to the validator's client entries. We write down where the exports and the client entries disagree, and that list sets the build order.
  2. Step 2

    Event receiver and event store, built first

    The event receiver and the event store come first. The receiver verifies each signature with a secret held in your vault and stores each message by uuid. Backfill jobs map Reporting API records to the event fields. So backfilled and live rewards get the same posting key.
  3. Step 3

    Allocation, posting rules and close next

    The allocation record, the posting rules and the processed-epoch close arrive together. Accruals are matched against the Reporting API and each validator's beacon-chain balance. Month-end totals show their epoch range, and provisional figures are labeled as provisional.
  4. Step 4

    Stake and exit routing with each client launch

    The stake connector and the exit workflow go live as each of your client products launches.
  5. Step 5

    Access, records and operation after launch

    The connector calls Blockdaemon with API keys that your staff create, hold in your vault and can withdraw. The event store, the allocation record and the posting rules are kept in your systems. Your team runs the integration, or Protofire operates it under a written scope. That scope names each write call the integration sends.

How work with Protofire starts

You send your signer setup and your withdrawal addresses, with client counts per address.You also send your networks and a month of Blockdaemon reward exports. The terms 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.

When a Blockdaemon project with Protofire does not fit

Blockdaemon's own tools, or another service, are enough in five cases.

  • Your app needs a staking screen, and Blockdaemon's "codeless, white-label widget" covers it.
  • You want Blockdaemon's engineers across the whole stack. Blockdaemon's Build, Operate, Transfer track provides that.
  • You stake through a custody platform that already offers Blockdaemon staking, such as Fireblocks, Taurus or Colossus Digital. The platform's reports already reach your ledger.
  • Each client stakes from its own withdrawal address and volumes are small. Finance books from the dashboard's CSV in local time.
  • You need someone to run validators. Blockdaemon provides that service. The validator operations offer also sets nodes up for your team or runs them for you under a written scope.

Protofire runs no validators under its own name or stake, and it holds no license. Your tax advisers handle the tax treatment of rewards.

FAQ

What is a Blockdaemon integration?
A Blockdaemon integration is the engineering that connects Blockdaemon's staking APIs and Event Streaming to a firm's signer and ledger. The integration sends stake intents to the firm's signer and splits rewards among the firm's clients. It keys each Ethereum reward on the validator public key and the epoch. Protofire builds Blockdaemon integrations for firms that have chosen Blockdaemon.
Who can build a Blockdaemon integration for a custodian or a bank?
Blockdaemon offers its own engineers, and Protofire, an engineering firm, builds the firm's side instead. Blockdaemon sells a "Build, Operate, Transfer" engagement in which its engineers "work alongside yours throughout". On the custodian's or bank's side, Protofire builds the event receiver and the epoch close. Protofire also builds client allocation and exit routing. The firm's staff keep the keys and approvals.
Do we need Blockdaemon's MPC wallet to stake through Blockdaemon?
No. Blockdaemon's Staking API returns unsigned transactions that another signer can complete. Blockdaemon names Fireblocks among its supported routes. Taurus announced Blockdaemon staking in its platform in February 2026. Colossus Digital has announced the same integration.
What happens if a Blockdaemon stake intent is not signed?
Blockdaemon holds the reserved validators, but it may free them early if the deposit is not confirmed in time. Meanwhile, your books show the client order as pending. Protofire's connector pulls an old intent from the signer queue and requests a new one. So a late signature does not fund a freed reservation.
Can a firm move its stake from Blockdaemon to another operator, and keep its reward history?
Yes, and the firm moves its reward history out first. Blockdaemon's exit endpoints return the stake to the firm's withdrawal address. From that address, the firm can stake it with another operator. On Ethereum, the move follows the exit queue: "Unbonding Time: It depends on the exit queue". If Blockdaemon's API is unavailable, the firm can trigger the exit from its own withdrawal address through an EIP-7002 request. Blockdaemon's dashboard holds 90 days of reward history, so the firm's event store is the copy it keeps.
Where does Protofire appear in our DORA register of information?
Protofire appears in the same register as Blockdaemon, as ICT development (S02) for the build. Blockdaemon is an ICT third-party service provider under DORA, and your register names Blockdaemon. If Protofire also runs the integration, Protofire adds S14 (Annex III of Implementing Regulation 2024/2956). Your risk and legal teams decide what is filed. Protofire's DORA third-party risk guide covers the classes.

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.