Skip to content

Onchain Treasury Management for DAOs, Foundations and Companies

A DAO or company that holds tokens in a Safe still needs passed votes executed, spenders capped and a quarter-end file for the books. Protofire builds those parts of onchain treasury management, and the file shows each Safe's owners and threshold. Our Safe work goes back to 2018.

Diego Torres

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

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

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

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

Why a treasury needs records the wallet does not show

A treasury wallet shows balances and signatures, but not the records behind them. The wallet does not show the vote behind a payment, or a spending limit that nobody has reviewed since it was set. It also does not show the owners and threshold as they stood at the close. Protofire builds onchain treasury management around the Safe, so that a treasury has those records.

For example, a grant vote passed last month, and the funds have not moved. The three signers who must execute the vote work in three time zones. One of them stepped down in the spring without a replacement. This week the finance lead also needs the position as of the quarter close, and the auditor asks who generated each signer key. None of those answers is in the wallet.

How an onchain treasury links governance, signers and the books

Governance decides and the signers approve. The layers Protofire builds prepare transactions and read the chain. None of those layers holds a signer seat.

The treasury

Governance or board

Token holders vote, a foundation's directors decide, or a company acts under its authority matrix.

Treasury Safe and signers

The Safe contract enforces the owners, the threshold, the modules and the guards.
Custody provider

Custodian or MPC platform

The provider manages keys and an approval policy for a company that holds tokens through it.
Protofire builds

Vote execution and scoped roles

Protofire prepares transactions for passed votes and sets the capped spenders and role scopes that the signers approved.

Data feed for the books and the auditor

Balances, lots, owners and threshold are taken at one cut-off block per chain, then priced and posted.
Finance and its auditor

Ledger and auditor

The entries go to the general ledger or a crypto subledger, and the auditor tests that ledger.

What a Safe enforces, and what a treasury is still asked to show

A Safe enforces who signs, but a treasury is asked for more than signatures.Safe's contracts require "a configurable threshold of owners" to approve each transaction. The contracts do not send a passed vote to a signer, record the vote behind a spending limit or post a balance to a ledger. Where nobody writes those parts, people do them by hand. The manual work leaves a spreadsheet at the close, a module nobody remembers enabling and a signer change that no minute explains.

An auditor examines manual treasury steps closely. PCAOB staff wrote in June 2023 that an auditor may need to test controls over "the generation and maintenance of the keys, including segregation of duties". The Spotlight states that it is "not a rule, policy, or statement of the Board".

A US GAAP filer measures in-scope crypto assets at fair value and records the changes in net income (ASU 2023-08). The standard applies to fiscal years beginning after 15 December 2024. So each close needs a priced position at one named block, next to the Safe's owners and threshold at that same block.

[...] performing substantive procedures to verify that a public company has access to the private keys [...] may not provide sufficient evidence that the public company has sole ownership rights over the crypto assets, as access does not necessarily imply ownership.
PCAOB staff, Spotlight, Public Company Accounting Oversight Board · Inspection Observations Related to Public Company Audits Involving Crypto Assets, June 2023

What onchain treasury management gives your treasury

Your treasury can trace each vote, each spender and each balance to a record.

A passed vote executes as it was voted

The grant or payout that your token holders approved reaches the chain as the transaction that the vote described. The vote then links to the hash of the transaction that moved the funds. For an onchain Governor, Protofire prepares the proposal calldata, the timelock queue and the execution call. For an offchain vote, we prepare a Safe transaction that matches the vote text. UMA's docs say oSnap stopped executing DAO Safe transactions after 15 December 2025. Our DAO tooling page covers governance contracts beyond the treasury.

Spending without a vote has a cap and a record

You get a register of the addresses that can move funds without the signers. For each address, the register records its token, cap and reset period, and the vote behind it. A Safe's spending limit lets "a chosen address (can be non-signers) spend a capped amount of a token". Protofire sets those limits for contributor payouts and grants. We also set Zodiac Roles scopes for an outside manager that the DAO appoints.

Signers and threshold that follow your governance documents

The Safe's owners and threshold follow your governance documents or authority matrix. Where limits differ, each approval tier gets its own Safe. A written rule says how a departing signer is replaced. Our Safe multisig deployment page describes the Safe build itself.

One quarter-end file the auditor can test

Balances, lots, prices and each Safe's owners and threshold arrive as one file at a named block on each chain. A signer change with no matching vote or minute goes on an exceptions list. Protofire builds the indexer over your addresses, the lots per wallet and the cut-off for each chain. We also build the pricing from the source your policy names, and the journal lines for the ledger or a crypto subledger. A custodian's data maps to the same lots. One route is Fireblocks events booked to the ledger.

An alert when control of a Safe changes

The people your treasury names get an alert when an owner, threshold, module, guard or fallback handler changes. They also get an alert when a spending limit appears or a transaction waits for signatures. The monitors only read the chain. Protofire can run them under a written scope through managed onchain operations.

Stablecoin supplier payments released from your TMS

A corporate treasury team keeps its approvals in the TMS. A licensed provider handles the stablecoin payment where a bank handles the wire. The stablecoin treasury payments page covers the connector, payee wallet checks and the cash-equivalent question. Teams on Kyriba start from Kyriba's interfaces.

Platforms we integrate for treasuries

A treasury holds tokens in a Safe, with a custodian or MPC platform, or in both, and it pays from its treasury system.

Safe

Multisig smart accounts.

Left to you: Deployment on networks where Safe is not live yet, the Transaction Service that collects signatures, owner and threshold setup, Safe modules and guards, and monitoring.

Safe service page

Fireblocks

MPC wallet infrastructure with a transaction policy engine.

Left to you: Booking client positions in a custody subledger, approvals tied to your mandates, fiat legs, and a daily match of positions against Fireblocks vault accounts and the chain.

Fireblocks integration

BitGo

Wallet software, or a custodian holding your assets.

Left to you: Your app and booking, reconciliation, and any move from your current custodian.

BitGo integration

Kyriba

Treasury management system with payment and reporting SPIs for outside providers.

Left to you: Payment and statement services on Kyriba's SPIs for any rail or custodian without a Kyriba app, wallet payees under second approval, screening through the Fraud Detection SPI, and posting in your ERP.

Kyriba integration

All 76 platforms we integrate

Our record: Safe work since 2018 and Aragon's Payroll UI

120+
EVM networks where we deployed Safe
$2B+
secured by Safe on those networks
2018
the year our Safe work began

A treasury signs with a Safe, and Protofire's Safe work goes back to 2018.We deployed Safe on 120+ EVM networks, where it secures $2B+. The Safe Ecosystem Foundation wrote in a forum post of 27 May 2026: "Protofire has been contributing to Safe since 2018, touching the first versions of the codebase and helping expand Safe to over 100 chains."

From 2019 to 2021, Protofire engineers helped build the Gnosis Safe web app, as its contributors graph shows. Our Safe multisig deployment page lists public examples from the networks' own docs.

For DAOs, Aragon merged the pull request "Payroll: UI Milestones 2-4 (Protofire)" into its apps repository on 14 May 2019.

Protofire's Safe record applies to a treasury build, because the data feed for the books reads a Safe's owners, modules and guards. The execution path prepares transactions for that same Safe.

How the work runs, from your addresses to signed transactions

The work starts from your treasury's addresses.

  1. Step 1

    You send your addresses and one closed quarter

    A company sends its Safe and custody addresses with their owners and modules, under NDA and with counterparty names removed. It also sends a ledger extract for one closed quarter. A DAO sends its addresses and its last payout or grant report.
  2. Step 2

    Protofire reads the settings of each Safe

    For each Safe, Protofire reads the signer set, the threshold, the enabled modules and the guards. Then we list what has drifted. Examples are a module nobody remembers, a limit with no vote behind it and a threshold that too few signers can reach.
  3. Step 3

    The first scope depends on the kind of treasury

    DAO treasuries tend to start with vote execution and capped spenders. A company tends to start with the data feed for its books. The first written proposal names each service and the read access that each service needs.
  4. Step 4

    Your signers receive each prepared transaction

    Each Safe transaction that Protofire prepares reaches the signers as a file or a queued proposal. Treasury staff load it with their own key.

How work with Protofire starts

The treasury keeps its RPC and custodian API keys in its own vault.Protofire holds no signer, proposer or delegate key.

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 Protofire is not the right fit for a treasury

Some treasury jobs belong to people the treasury appoints.

  • The job is allocation, or a seat among the signers. A manager that the DAO appoints handles allocation, and people that its governance elects hold the signer seats. Protofire takes no signer, proposer or delegate seat.
  • The company needs an accounting opinion, a tax position, an audit or advice on a legal wrapper. Protofire gives none of these and holds no license. The company's auditors, advisers and counsel give them, and Protofire supplies the data they ask for.
  • A packaged subledger is enough. The treasury holds mainstream tokens on chains and custodians that packaged subledgers already connect. Our reconciliation guide names Cryptio and Bitwave, and such a treasury should buy one of them first.
  • Another Protofire page fits better. The DeFi protocols page covers a protocol's contracts and upgrade keys. The L1 and L2 chains page covers a chain foundation's keys. The asset managers page covers money managed for clients.

Call us when signers, token holders or the auditor ask for more than the wallet screen shows. They may ask for a vote executed as passed, or for a capped spender with its vote on record. They may also ask for a cut-off balance with its owners and threshold.

FAQ

What is onchain treasury management?
Onchain treasury management is the set of rules and records that decide who may move a treasury's tokens. The rules and records also decide how each movement and each quarter-end position reaches the books. They cover signers and threshold, capped spenders, executed votes and an audit trail. Protofire builds the parts around the Safe, custodian and governance contracts that a treasury has chosen.
Who can build vote execution and a feed to the books for a DAO or a company treasury?
Protofire does. We build the steps from a passed vote to an executed transaction, and we set up capped spenders and scoped roles. We also build a feed of cut-off balances, lots, prices and each Safe's owners and threshold. The feed connects to the Safe, Fireblocks, BitGo and governance contracts that the treasury uses. The treasury's signers approve each transaction that Protofire prepares.
What happens to a DAO's Safe when signers step down?
The Safe keeps working while the remaining signers can still meet the threshold. Adding an owner or lowering the threshold needs the same number of signatures as any other Safe transaction. Once too few signers remain to reach the threshold, the owners can no longer move funds or change the signer set. Enabled modules can still act within their own rules, such as a spending limit, a Roles scope or a recovery module. A DAO writes into its governance documents who appoints replacements before the count falls that low.
What does an auditor ask for on a position held in a Safe?
The evidence pack for a position in a Safe holds the address list with owners and threshold at the cut-off, and the signer history. The pack also holds custodian statements, any service auditor's report on the custodian's controls and the price file. The company adds its own key-generation and key-control records. The auditor decides what suffices.
Which accounting standard covers the crypto a treasury holds?
Under US GAAP, a fungible token falls under ASU 2023-08 when it meets all six scope criteria (paragraph 350-60-15-1). A token with a claim on underlying assets fails one of those criteria, and many stablecoins have such a claim. Under IFRS, a cryptocurrency that no party issued falls under IAS 2 when it is held for sale in the ordinary course of business. Otherwise it falls under IAS 38, according to the Interpretations Committee's June 2019 agenda decision. The company and its auditor classify any token outside those texts.

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.