Kiln Integration That Checks Each Staking Transaction Before Your Custody Signs
Protofire builds Kiln integrations for custodians, exchanges, wallets and fintechs that offer staking. The integration checks each transaction before custody signs, syncs Kiln data to the ledger and prepares ETH exits. Our engineers helped build the Gnosis Safe web app from late 2019 to mid 2021.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Your firm is responsible for checking each Kiln transaction
In a Kiln integration, someone has to read the payload of a client's staking transaction before the first approver in your custody quorum signs. Kiln's docs name that someone, and it is your firm: "it is YOUR responsibility to check and verify all the transactions you are signing" (Kiln).
Kiln's Connect API crafts the stake, unstake and withdraw transactions for 23 protocols (Kiln). Your custody signs them, following Kiln's staking guide for your custody platform. Kiln runs the validators. Your firm owns the check, the client's books and the exit.
What Kiln supplies for the check and the data
Kiln supplies a Transaction Decoding route for each protocol, but the check itself falls to your firm.Your firm has to run that route on each request and judge its output against your client's instruction. Without that step, your approvers sign whatever Kiln's API returned.
Your firm also has to pull Kiln data, because Kiln's API reference lists no webhooks. ETH and SOL rewards refresh about once a day (Kiln API). So a client statement cut before the daily pull misses that day.
Kiln products, protocols and data delivery
- Products
- Kiln Connect (REST API and JS SDK), Dashboard, Widget, Kiln Onchain pooled ETH and validators, and Lido V3 stVaults (Kiln).
- Protocols
- Connect lists 23. On 11 of them, Connect also reports stakes on other operators' validators. Kiln scopes the other 12 to its own validators (Kiln).
- Data delivery
- Polling. Average refresh times range from seconds for stake states to about a day for ETH and SOL rewards (Kiln API, page updated 10 Sep 2025).
- Custody guides
- 15 platforms, among them Anchorage, BitGo, Copper, Dfns, Fireblocks, Ledger Enterprise, Taurus and Zodia (Kiln).
- Change policy
- Each major version comes with a transition of at least 3 minor versions (Kiln API).
Checked November 2026 against Kiln's documentation. Protofire integrates Kiln for firms that have chosen it.
What Protofire builds in a Kiln integration
A check of each Kiln payload against the client's instruction
Protofire builds a service that checks each Kiln payload. Only that service submits Kiln payloads to your custody, so an unchecked payload does not reach your approvers. For example, a Solana unstake takes two signed transactions, a deactivation and then a withdrawal. The check accepts one deactivation of the named stake account by your stake authority. It then accepts a withdrawal to an allowlisted firm address. If the check finds a changed withdraw authority or an extra instruction, it stops the request and alerts your security team. Protofire writes the decoder separately from Kiln's code, because Kiln's own decoder runs Kiln's code.
Custody policy rules for staking through Kiln
Approval of each Kiln stake comes from your own custody policy. For API staking from Fireblocks, Kiln's guide asks for the Raw Signing API (Kiln). The guide also asks for rules that limit which users, vaults and assets may raw-sign. For the Dashboard route, the guide adds an allowlist of Kiln's IP addresses. Protofire writes that policy set for Fireblocks, BitGo, Taurus, Dfns or another platform on Kiln's list. The set includes a larger quorum for a change of stake authority. Your administrators enter and approve the policy set. Protofire's tests show that each rule blocks what it should.
Client positions in your ledger that match Kiln's reports
Finance gets client positions and reward postings in Temenos, another core banking system or a ledger you built. Each day of Kiln data that arrives late is flagged. Each Kiln account maps to a client ID. When a finalized refresh restates a day, that day is reposted with a reversal.
An exit runbook your operators can follow without Kiln's API
You get a runbook that your operators can follow without Kiln's API. The runbook is rehearsed on Kiln's testnet before go-live. Protofire fetches Kiln's exit messages and checks that the key UID Kiln names matches the GnuPG key you hold. We track pooled exit tickets from request to claim. We also prepare request-exit transactions for your withdrawal address to sign.
How old Kiln data can be at the close
At the close, Kiln data can be one refresh cycle old.For ETH and SOL, a cycle is 12 to 30 seconds for stake states and about 24 hours for rewards. Kiln calls its refresh times "indicative and subject to change" (Kiln API).
Stakes
Average refresh Kiln publishes: 12 to 30 seconds on ETH and SOL, then a finalized refresh, "typically 1 hour for most protocols"
What the sync does with the data: Shows state changes at once and posts from the finalized value
Rewards, ETH and SOL
Average refresh Kiln publishes: About 24 hours, as a daily figure per stake
What the sync does with the data: Books each day once the figure arrives. Kiln's pages do not name the time zone of that day, so the sync confirms the time zone before go-live
Operations
Average refresh Kiln publishes: 12 seconds to a couple of minutes on ETH, and about 24 hours on SOL
What the sync does with the data: Matches each deposit and exit request to the custody transaction already booked
Fee Splitter payouts
Average refresh Kiln publishes: The contract splits the execution-layer fee between the firm and Kiln onchain (Kiln)
What the sync does with the data: Books the client's reward and the firm's fee as separate entries
[...] the Node Operator does not guarantee or otherwise set or fix the amount of the rewards owed to Owners, although the Node Operator may subtract from such amount its fees (whether fixed or a percentage of such amount).
Keys, withdrawal rights and losses in each Kiln model
Kiln splits keys, withdrawal rights and exits differently in each model.On delegation networks, your wallet holds the stake. On native ETH, Kiln holds the validation keys. In pooled ETH, a receipt token is the withdrawal credential.
On Solana and the Cosmos chains, the stake is in an account that your wallet controls. The account is delegated to a validator that Kiln runs. Kiln's Solana tutorial sets your wallet as both stake authority and withdraw authority, and Kiln holds no key over that stake (Kiln).
Kiln creates the validation keys on its own infrastructure. Your withdrawal address receives consensus rewards. Kiln's ETH page says that the depositing wallet alone can withdraw the stake: "Kiln or any other party cannot do that" (Kiln). Where you charge a fee of your own, Kiln's Fee Splitter contract takes that fee from execution-layer rewards. The contract splits the fee with Kiln onchain (Kiln).
Each holder gets an ERC-20 token that "represents their stake ownership and serves as the withdrawal credentials" (Kiln). The integration contract belongs to you. Kiln recommends a multisig or MPC wallet for the contract's pause, fee and upgrade roles.
You create the vault with Kiln as Node Operator. Kiln's docs state that "Kiln never has access to your Vault Owner keys" (Kiln). If you mint stETH, the matching collateral is locked until repayment, and your books record a liability.
Your agreement with Kiln governs who bears a slashing loss. This page does not say what that agreement provides.
What your firm keeps to exit without Kiln
Native ETH and the delegation networks allow an exit without Kiln if your firm keeps what Kiln's docs hand over.These are the withdrawal address, the stake authorities and the exit messages. Kiln writes that "B2B customers of Kiln can retrieve pre-signed Ethereum validator exit messages which enables them to unilaterally unstake" (Kiln). Each message arrives encrypted with GnuPG. So a message helps once your firm can decrypt it and submit it to a beacon node. Pooled ETH exits go through the pool's queue.
An EU financial entity that treats Kiln as an ICT third-party provider enters Kiln in its DORA register. If Kiln supports a critical or important function, DORA requires an exit strategy (DORA Article 28). In the same register, Protofire appears as ICT development (S02) while Protofire builds. Protofire's entry adds ICT operation management (S14) when Protofire also operates the sync (Implementing Regulation (EU) 2024/2956, Annex III).
Our record: Gnosis Safe signer screens and Safenet staking
Protofire's record covers the screen where signers review a transaction and an interface for staking.
Gnosis Safe web app, late 2019 to mid 2021
Protofire engineers helped build the Gnosis Safe web app from late 2019 to mid 2021. In that app, the signers of a multisig review a transaction before they approve it. Our Safe multisig work has its own page.
An alternative interface for staking SAFE on Safenet
In 2026 Protofire built an alternative interface for staking SAFE on Safenet (GitHub). A grant from the Safe Foundation supported its development. The Foundation's Q3 2026 report says the Foundation signed grant agreements with four teams to build independent Safenet staking interfaces. Protofire is one of those four teams. The repository calls the interface an independent project and not an official Safe product.
Steps of a Kiln project with Protofire
- Step 1
A proposal with a check rule for each Kiln route
You send your custody platform, the Kiln models and networks you use, and your ledger layout. The first written proposal gives each Kiln route a check rule, a ledger posting and an exit step. - Step 2
The check and the policy set come first
The check and the policy set run against Kiln's testnet. Kiln opens its testnet on request and does not put it under an SLA (Kiln API). - Step 3
The ledger sync and exit runbook follow your launches
The poller runs on the schedule of Kiln's refresh table. The exit runbook is rehearsed on testnet. - Step 4
Who holds the keys, the API key and the code
Kiln holds the validation keys it generates, under your contract with Kiln. You or your custodian hold the withdrawal addresses and stake authorities. Kiln's docs describe no read-only API key. A Kiln API key can make "any API call on behalf of your account" (Kiln API). So the key belongs in your secrets vault. Code that Protofire writes for you is yours by contract, within the license of any third-party software involved. Either your engineers run the sync and the check, or we operate them under a written scope. That scope lists each Kiln route that the sync and the check call.
How work with Protofire starts
The shared terms below apply to each phase.Protofire's how we work page has the detail.
- 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 Kiln's console and widget are enough
Kiln staking is already available inside the Fireblocks console, Ledger Enterprise and Zodia.That covers a firm with no client books.
- Finance books the firm's own treasury stakes from Kiln's Excel reports, and there is no ledger per client behind those stakes.
- A wallet or app that accepts Kiln's interface can ship the Kiln Widget instead.
- Staking on one network through Kiln's SDK and Fireblocks is a small project that your engineers can run.
- Protofire's validators page covers validators of your own, without Kiln. A staking product inside your own app starts with the native staking module.
Protofire runs no validators under its own name or stake today. On a Kiln project, Protofire operates no validators either. We write no legal opinions on how staked client assets are held.
FAQ
What is a Kiln integration?
Who can build a Kiln integration for a custodian or an exchange?
Does Kiln report on stakes that run on other validators?
Does Kiln send webhooks when a stake or reward changes?
Which custody platforms can sign Kiln transactions?
What happens when Kiln changes its API?
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.
