Proof of Reserve Pipelines for Asset-Backed Token Issuers
Protofire builds a pipeline that reads, values and matches a token's reserves to supply at one cut-off for your accountant and a Chainlink feed. We built and operated the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens for a large auditing firm.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Why a proof of reserve needs one cut-off
Without one cut-off rule, your contract, your accountant and your holders read three reserve figures, and you cannot say which one is right. For example, a lender asks for your proof of reserve. The answer takes three people, two exports and a guess about when each number was taken. The custodian closed its statement at its own time. Supply has changed with each block since then. The feed on your contract reports a third timestamp.
On Ethereum, 17 of the 20 Chainlink reserve feeds listed on 9 November 2026 have a 24-hour heartbeat (Chainlink). From 18 January 2027, the US Office of the Comptroller of the Currency (OCC) sets a fixed cut-off for the issuers it supervises. Each such issuer must state its reserves as of noon on one named day. If its reserves fall below the minimum, the issuer must notify the OCC that day. The issuer is then barred from new issuance, with narrow exceptions (OCC).
Where a reserve figure comes from and who reads it
Custodians and banks own the sources. Protofire builds the layers between the sources and the readers.
Reserve sources
Source connectors
Valuation and supply match
Report and accountant's file
Feed and mint check
Accountant's opinion
What a reserve pipeline gives your team
One reserve figure for treasury, accountant and contract
Your treasury, your accountant and your contract read a reserve figure stated at the same moment. Protofire builds the connectors for your custodian APIs, bank statement files and vault records. We also build the valuation step and the supply read on each chain.
Timing differences listed with their transactions
Reserves and supply can differ at one cut-off because of timing. A mint awaiting custody or a bridge transfer in flight is listed with its transaction. An unlabeled difference holds the figure back until your treasury clears it.
A reserve API for the Chainlink feed and your mint check
A contract can refuse a mint that exceeds fresh reserves. Protofire builds the API that serves the reserve total, in the feed's units, to the external adapter that Chainlink's node operators run. We write down the units, the decimals and the staleness threshold. We wire the mint check as oracle integration work, in the same proposal when you need both.
A file per reference date for your accounting firm
For each reference date, your accounting firm gets the raw sources, hashes, valuation inputs and labels. The firm also gets a change log that records who approved each change. A hash shows that the file has not changed since capture. A hash does not show who sent the file, so the firm can still confirm balances with each custodian.
A runbook for a stale feed or a shortfall
Alerts fire on missed heartbeats and on the age of each source. They also fire on address-list changes and on reserve-to-supply breaches. The runbook names who at your firm stops minting, who notifies the regulator and who may change a threshold.
Our record: the reserve-data pipeline for a large auditing firm
Protofire built and operated the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens for a large auditing firm.
Protofire is a Chainlink core contributor. Under Chainlink Community Grants from 2020 to 2022, we built External Adapters that connect node jobs to web APIs (Chainlink integration case).
Protofire's public euro EMT issuance blueprint sets out which disclosures MiCA requires and which are market practice.
What a proof of reserve feed does not prove
A proof of reserve feed reports a number from its configured source, without an accountant's opinion.The feed shows no pledges or liabilities. Chainlink leaves the review of the data with the integrator: "You are solely responsible for reviewing the quality of the data" (Chainlink). In Chainlink's terms, a feed that reads an API you host counts as self-reported. So holders need an accountant's report on a stated date beside such a feed. Protofire is not an auditor, gives no attestation or assurance opinion and does not certify or guarantee reserves. The opinion comes from the firm that signs.
Chainlink reserve feed
Who stands behind it: Node operators report a value from the configured source, and nobody gives an opinion on it (Chainlink)
What it leaves out: Pledges and liabilities
Accounting firm's examination
Who stands behind it: The firm signs on the issuer's report
What it leaves out: The days between one named date and the next
MiCA reserve audit
Who stands behind it: An independent auditor, mandated by the issuer, tests compliance with the reserve rules (MiCA Art. 36(9))
What it leaves out: Reserve movements between audit dates
Monthly report under the GENIUS Act
Who stands behind it: The CEO and CFO certify it from 18 January 2027, with an accounting firm's examination of the previous month-end report (GENIUS Act s.4(a)(3))
What it leaves out: The days between month-ends
[...] a proof of reserves is not as rigorous, or as comprehensive, as a financial statement audit and may not provide any level of assurance.
How a month-end figure reaches your contract and your accountant
This example follows a fiat-backed token with one custodian bank and supply on two chains.
- Step 1
You set the cut-off date, time and time zone
Each report has one cut-off date, time and time zone. Under the OCC rule, the cut-off is noon on the last day of the previous month. The rule names no time zone, so you record yours (OCC). - Step 2
Connectors read each reserve source
Each connector stores the raw file or response, its hash and the source's own as-of time. A camt.053 statement gives a booked end-of-day balance. So a noon cut-off needs the bank's intraday report, or the prior close rolled forward. Chainlink sources offchain reserves "from APIs through an external adapter" (Chainlink), so a statement file needs a small API in front of it. A wallet list that misses an address understates reserves, and an extra address counts someone else's coins. So Protofire adds an ownership check, such as a message your wallet signs for each address. - Step 3
Valuation turns balances into one figure
A balance held in anything other than the token's own unit gets a price. The price is recorded with its source and time. - Step 4
Supply is read at a finalized block
Each chain's supply is read at the last finalized block timestamped at or before the cut-off. The read is stored with its block number, hash and time. Tokens still in your inventory get their own line, because the OCC leaves them out of outstanding issuance value. Tokens locked on a home chain are subtracted. Transfers in flight are listed by bridge message ID, because a burn can be recorded before its mint. - Step 5
The match labels each difference
MiCA allows a window after issuance to place reserve assets in custody (MiCA Arts. 37(3) and 58(1)). So a mint awaiting custody gets a label with its transaction and its expected custody date. Under the OCC rule, a token "must be backed by identifiable reserve assets" on issuance. For OCC-supervised issuers, a gap counts as a shortfall, and no label clears it. - Step 6
The report, the file and the feed receive the figure
The accountant's file and the public report show the cut-off stamp. A Chainlink feed picks up the latest figure under its own heartbeat and deviation rules. So the feed's timestamp can differ from the report's. A month-end run cannot feed a daily heartbeat, so the pipeline also runs on the feed's cadence.
When the feed goes stale or reserves fall short
A heartbeat can refresh an old figure, so a stale source needs its own limit.Chainlink's SecureMintPolicy rejects old data once a staleness threshold is set. A threshold value of 0 "disables the check entirely" (Chainlink). Protofire sets the source's as-of limit. Past that limit, the reserve API returns an error and no number. The feed then misses its heartbeat, and the threshold rejects the mint.
An OCC-supervised issuer must notify the OCC on the day its reserves fall below the minimum (12 CFR 15.11(g)). So the reserve test runs daily on the latest custodian balances, and again before each mint and withdrawal.
A stolen mint key can create tokens that no reserve backs. The mint check rejects a mint above a fresh reserve figure, as long as the attacker cannot change the policy. A per-period mint cap covers the headroom below the reserve figure.
Who keeps the keys and runs the feed after launch
Chainlink's node operators run a Chainlink feed after launch, and you arrange the feed with Chainlink directly.You keep the bank and custodian credentials. The address-list contract, the reporter contract and the mint policy are deployed from your keys. You also hold the key that posts to the reporter.
A written scope can ask Protofire to run the connectors or the report job. The jobs then run in your cloud account under a role limited to deploying and restarting them. The jobs fetch credentials from your secrets vault at run time, and Protofire's role cannot read those credentials.
Protofire does not take these roles:
- owner of the mint policy
- administrator of the address list
- holder of the reserves or of a mint key
- signer on the feed
The policy owner is a multisig that your team holds. For the multisig itself, see Safe multisig deployment. MiCA and the OCC rule place the reserve and reporting duties on the issuer, whoever built the pipeline.
How work with Protofire starts
Work with Protofire starts from the details of your reserves and your token.You send us the reserve assets, the custodians and banks, and the token with its chains. You also send your latest reserve report and your accountant's cut-off. From those details, Protofire writes down each source, the cut-off rule and the path to the feed or the mint check. We also write down the credentials that you keep. Our how we work page sets out the full process.
- 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 reserve pipeline is not the right fit
A reserve pipeline does not fit these four situations.
- You mint in scheduled batches and publish a monthly accountant's report. No contract reads the figure at mint time, so an onchain feed has nothing to gate.
- Your bank or custodian exposes no API or statement file. Protofire says so in scoping, and the fix starts with that bank or custodian.
- You run an exchange, and customers must verify their own balances. A customer-liability Merkle tree is a separate build.
- You need a contract to read an existing feed and nothing else. That read is oracle integration work.
FAQ
What is proof of reserve?
Who can build a proof of reserve pipeline for a token issuer?
Is proof of reserve required under MiCA or the GENIUS Act?
Do we need Chainlink to publish proof of reserve?
How do you handle a token on several chains?
Does a reserve pipeline go in a DORA register?
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.
