Skip to content

Liquid Staking Development for Chains, Staking Providers and Protocol Teams

Protofire builds liquid staking tokens over one network's stake for chains, staking providers and protocol teams. We build the receipt token, rate report, exit queue and fee split, and the issuer's governance holds the contract roles. In 2024 we built the staking module behind Aethir's stATH receipt token.

Diego Torres

Reviewed by Diego Torres, Offer Owner at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. What you get
  3. Token design
  4. Why Protofire
  5. How it runs
  6. How work starts
  7. Not the right fit
  8. Related guides and services
  9. FAQ

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

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

Who signs the rate and how a holder gets out

A lending market asks two questions before it lists a token issued against your network's stake. Who signs the rate, and how does a holder get out? Liquid staking development settles both before launch, because both answers have to hold on a bad day.

A rate posted from balances the chain has not finalized gets corrected after holders have traded against it. Lido's oracle reports finalized epochs. When the chain has no finality, Lido's integration guide says "the daily rebase won't occur".

The exit side of a liquid staking token has its own limit. As of November 2026, Ethereum lets at most 256 ETH of stake exit per epoch. The Electra upgrade set that cap. EIP-8061 is scheduled for the Glamsterdam upgrade and ties that limit to total stake instead. Until EIP-8061 takes effect, a large redemption waits behind the other exits on the network. So a queue that promises a faster exit than the network allows cannot keep that promise.

If you use a staking pool or hold liquid staking tokens, you don't interact with the protocol's withdrawal mechanism directly [...]. Instead, you typically either redeem your tokens through the provider (subject to its redemption queue and available liquidity) or sell them on the open market.
ethereum.org, Staking withdrawals page, Ethereum community website · Staking withdrawals page, read November 2026

Roles and contracts around one liquid staking token

Holders sign their own deposits and redemptions. Your governance holds the contract roles and appoints the oracle members.

Holders

Holders' wallets

Holders sign deposits, redemption requests and claims, and hold the token and any queue ticket.
Your Safe or DAO

Contract roles

The deploy transaction assigns the roles for upgrades, pausing, fees, the operator registry, guardians and oracle membership.
Protofire builds

Token, share ledger and queue contracts

These contracts mint and burn shares, apply accepted reports and hold redemption requests.

Report software, indexer and staking app

This software computes the report each member signs, groups unbonding requests and prepares holders' transactions.
Operators you appoint

Oracle members

Each member runs its own copy of the report software and signs the report hash. A report is accepted once a quorum signs it.
Node operators you select

Validators

Validators run consensus for the pooled stake under the network's bonding, exit, unbonding and slashing rules.

What liquid staking development gives your holders and integrators

The token, deposit and queue contracts change little between networks, but the report software and the exit batching are written for each network.

ERC-20 receipt token over a share ledger

Lending markets and indexers get a token whose design they can read: rebasing, exchange-rate or both. Protofire builds the ERC-20 over a share ledger, and the deposit and queue contracts hold the right to mint and burn. We test the token against a negative report, a paused queue and a 1 wei transfer.

Oracle report software and quorum contract

A holder or an auditor can rebuild each report from public chain data. Protofire builds the software each oracle member runs, and the quorum contract. We also build in a limit on how far one report can move the rate. Each member's software checks finality before it signs.

Deposit contract, operator registry and guardian check

New stake goes from the buffer to the operators on your registry. On Ethereum, the first deposit for a validator key fixes its withdrawal credentials, so an operator could front-run the pool. Protofire builds the deposit contract, the registry your governance edits and a guardian check. The contract refuses a deposit if the deposit root your guardians signed has changed, as Lido's Deposit Security Module does.

Exit queue built on your network's exit path

A holder who asks to leave gets a request ID and a claim. Protofire builds the requests, their finalization by report and the claims, following your network's exit path. On Ethereum, the withdrawal contract triggers exits under EIP-7002. On a Cosmos SDK chain, unbonding is grouped under the chain's entry limit.

Fee split with a notice period

A fee change reaches holders through the next report. So the contracts hold the change back for a notice period that you set above the longest exit delay you expect. A holder who disagrees with the change can leave first. Protofire builds the fee split between operators and treasury, and a fee event for each report that your treasury can book.

Staking app with rate history and queue positions

Holders see the rate history and where their request stands. Protofire builds the subgraph and the staking app. The app prepares each transaction for the holder's wallet and shows no projected figures.

Rebasing token or exchange-rate token: what integrators handle

Integrators choose between a rebasing and an exchange-rate design first, because each design changes what they must handle.

After each report

Rebasing token: Balances change. stETH balances get "recalculated daily when the Lido oracle reports" (Lido).

Exchange-rate token: Balances do not change, and the value per token moves. rETH's rate is "updated approximately every 24 hours" (Rocket Pool).

What indexers read

Rebasing token: stETH "does not emit Transfer() on rebase", so indexers read the report.

Exchange-rate token: Indexers read ordinary ERC-20 transfers and read the rate from the contract.

Where integrations fail

Rebasing token: A lending contract does not record a rebase, or a transfer leaves 1 or 2 wei behind.

Exchange-rate token: Lido's guide says to use rebasing stETH when an app "intentionally supports its share and rebase semantics; otherwise, prefer wstETH".

Our record: Aethir's stATH receipt token and Vana's staking app

In 2024 Protofire built the staking module for Aethir.The module's lock issues a transferable receipt token.

Aethir's staking module and stATH, June 2024

Protofire built Aethir's staking module, a ve8020 vote-escrow design (case study). Locking ATH in the module issued stATH. When Aethir's mainnet launched on 12 June 2024, staking ATH gave holders two tokens. Aethir's announcement says stATH transfers while veATH does not. To redeem the principal, Aethir's staking guide has a staker deposit back "the same amount of both stATH and veATH". That module was a timed lock. Its stATH is an ERC-20 whose holders keep a transferable claim.

Vana's staking dApp and subgraph

Protofire built Vana's staking dApp, with delegation to pools and a leaderboard. We also built the subgraph that the dashboard reads (case study). A liquid staking token's rate history and queue positions come from the same kind of indexer.

How a liquid staking token build with Protofire runs

  1. Step 1

    Proposal and build order

    The proposal puts the share ledger, the report software and the exit queue into phases. The proposal also names the module to build first. Each module is then tested against the paths your design names, such as a report at the sanity limit.
  2. Step 2

    Outside audit of the core contracts

    An outside auditor you choose reads the share ledger, queue and quorum contracts, and Protofire fixes each finding. A review reports what it finds and does not certify the token.
  3. Step 3

    Your engineer deploys the contracts

    Your engineer runs Protofire's scripts in your environment and signs with your key. The scripts assign each role to your Safe or governance contract, with a timelock where you want a delay on upgrades.
  4. Step 4

    Each oracle member runs its own report software

    Each oracle member runs the report software in its own environment. The role table names each member and the quorum. You can publish the role table for exchanges and lending markets that review the token.
  5. Step 5

    Repository, role table and keys after launch

    The repository and the role table are yours. Protofire signs no report and holds no oracle seat. After launch, no contract role names a Protofire address, including the oracle, guardian, fee, minter, pauser, upgrade and owner roles. Holders keep their wallet keys. The operators you select keep the validator signing keys.

How work with Protofire starts

To start, you send Protofire the network, the token design you lean toward and the operator set.Reports or queue exports from a live token help. Send them under NDA, with holder addresses removed. Commercial terms are on our how we work page.

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 liquid staking build with Protofire does not fit

Some jobs near a receipt token need a different build.

  • A vault over several liquid staking tokens, with weights that a manager sets, is index vault work. Staking recorded in your own contracts or app, with no tradable receipt, is staking module development.
  • Protofire runs no validators under its own name or stake today, so there is no Protofire operator to stake through. Nodes for your token are a separate engagement. Protofire offers validator nodes run for you under a written scope, or set up for your own team.
  • A firm that stakes through a provider and wants no token of its own starts on the provider's page: Kiln, Figment or Blockdaemon.
  • A restaked token adds each service's slashing conditions on top of the base stake. Our restaking protocols guide compares EigenLayer, Symbiotic and Babylon.

FAQ

What is liquid staking development?
Liquid staking development is the engineering of a token issued against stake deposited on one network. It also covers the contracts and software that keep the token tied to that stake. Those parts are the share ledger, the deposit and redemption paths, the rate report and the fee split. Protofire builds the token and these parts, and the issuer's governance holds the contract roles.
Who can build a liquid staking token for a chain, a staking provider or a protocol?
Protofire builds the token contracts, report software, exit queue and staking app for one network's stake. For a chain foundation, the build starts from the chain's staking module and is written in Solidity for EVM chains. On a chain without an EVM, the build is the report software, the indexer and the app. For a staking provider, the build gives running validators, signing reports and controlling exits to separate parties. Rocket Pool publishes one such split, in which the rETH rate is "reported by the Oracle DAO". A protocol team often gets a rebasing token and a fixed-balance wrapper over one share ledger. A Solana pool that the stock Stake Pool Program covers needs configuration, an indexer and an app, with no custom contracts.
What happens to a redemption request if validators are slashed while it waits, and who bears the loss?
A redemption request can lose value while it waits. Lido's docs allow a request to finalize "by the rate lower than 1:1" after a large loss. The token's contracts record the loss through the rate or the rebase. The contracts do not prevent the loss or make it good. Holders bear the part of the loss that operator bonds do not cover. On validator nodes that Protofire runs for you, the written scope names who bears a slashing loss.
Who reports the rate, and what happens if the report stops?
The oracle members you appoint report the rate, each signing with its own key, and they decide by quorum. At Lido, a report is accepted once "more than half of the oracles submitted the same hash". If the chain stops finalizing, Lido's daemons send no report. The rate then does not change, and waiting requests are not finalized. The next report covers the longer period.
Can holders get out if the node operators stop cooperating?
On Ethereum, yes: your withdrawal contract can trigger exits through EIP-7002 without the operators' signing keys. A Solana stake pool hands back a stake account through withdraw-stake when its reserve is empty. Under Cosmos SDK staking, the account that the token's contracts control is the delegator. That account unbonds without the validator's signature, within the chain's entry limit.
Who runs the validators behind the token?
The operators you select run the validators behind the token. Protofire's part is the token, the report software, the queue and the app. The token's contracts hold no validator key, and the withdrawal credentials name your contract. When you change operators, exited stake returns to your contract and is deposited again with the new operator, through the exit and activation queues.
Which rules cover a liquid staking token?
The rules differ by jurisdiction, and applying them to your token is work for your counsel. In the US, the SEC treats a staking receipt token as a receipt for the deposited asset. The SEC set this out in its interpretive release 33-11412 of 17 March 2026. A provider that chooses "whether, when, or how much" to stake falls outside that release. In the EU, ESMA says a separate liquid token "may require an independent classification assessment". ESMA wrote this in its response of 30 September 2026 to the Commission's MiCA review. In the UK, the FCA's cryptoasset rules in PS26/11 come into force on 25 October 2027.

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.