
How to price a tokenized asset that has no market
Dillon Hanson, DIA
Moment at 28:37Episode 2 · Ghost Town Markets: Building Secondary Liquidity for Real-World Assets
Protofire builds oracle integrations for chains and protocols that depend on oracle prices. The integration includes checks that stop a contract from acting on a stale or wrong value. Chainlink's archived 2021 post records our grant-funded integrations, and DIA merged our price scrapers in 2024 and 2025.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
Work shipped for 60+ networks and 95+ protocols, including
Protofire's blockchain oracle integration work covers both ends: the chain's readiness for an oracle network and the contracts that read its prices.
For example, your lending market reads a Chainlink price, and the borrow goes through. Can your team say what the contract does when that price stops updating?
A chain team has the same problem from the other side. Chainlink integrates a new chain against a published list. On a self-managed feed, the chain publishes the prices and watches them.
The oracle network signs the reports. The chain meets the network's list, and your contract decides what to do with each price.
A feed that stops updating usually does not say so, and its last price keeps coming back.Chainlink feeds update on a price move or a heartbeat, and "some heartbeats are configured to last several hours" (Chainlink). The latestRoundData() function returns the stale price with no error. Only its updatedAt time shows how old the price is. Chainlink makes developers "solely responsible" for "data quality checks, circuit breakers, and appropriate contingency logic" (Chainlink).
On a new chain, the same problem is larger. The chain or its designated operator writes a Chainlink self-managed feed. Chainlink Labs gives no SLA for that feed and does not check "Heartbeat compliance" or "Whether the correct data was written onchain" (Chainlink). So someone on the chain's side has to watch the feed.
Leaving a feed unchecked has a public record. In February 2026, a misconfigured cbETH feed priced the asset at $1.12 instead of about $2,200 on Moonwell. Fixing the feed took a governance vote and a timelock, and bad debt reached $1.78M (Moonwell).
Third parties record most of Protofire's oracle work, on the chain side and on the data-source side.The checks that Protofire writes into contracts draw on this engineering.
Chainlink's blog post of 27 August 2021 says Protofire had completed several grants for the integration of the Chainlink stack into blockchains (Chainlink, archived). The post names xDai (now Gnosis Chain), Avalanche, Plasm and Celo as examples. Our Chainlink node repositories for five networks, Avalanche among them, are public and now archived. Our Chainlink case describes the work.
In 2022, Chainlink's blog announced a Community Grant to Protofire to develop a Hardhat plugin. The post says the plugin "will allow developers to spin up a local Chainlink node with a single command" (Chainlink, archived). Protofire built the plugin (case).
DIA merged Protofire's scrapers for five data sources into its main repository between June 2024 and January 2025. The sources are Bitflow and Velar on Stacks, Bifrost and Hydration on Polkadot, and an Alephium DEX. For DIA, we also re-expressed DIA's oracle contract logic in Compact, the contract language of Midnight, a non-EVM chain. We built the feeders on the MidnightJS SDK (Midnight case). Our case page says that the Midnight oracle served 25 asset price feeds.
Before Chainlink integrates a new EVM chain, the chain has to meet the requirements that Chainlink publishes. Protofire compares your chain with each requirement and hands the oracle network's team a readiness file. We host RPC nodes as one of the providers and deploy a Blockscout explorer. We deployed Safe on 120+ EVM networks, where it secures $2B+. A chain without an audited multisig gets a Safe deployment.
On a self-managed feed, your chain or its operator writes Chainlink Data Streams prices to feed contracts through a Chainlink Runtime Environment (CRE) workflow. Protofire builds the workflow and a receiver contract. The receiver contract rejects a report meant for another chain and a report no newer than the last one. Your chain's multisig owns the feed contracts from deployment, so the multisig can replace the operator, Protofire included. When Protofire stops operating the feed, the scope covers the move to your next operator or a retirement notice to readers of the feeds. A workflow deployment also needs Chainlink's approval.
Your contracts check the age, sign, scale and range of a price before they act on it. Liquidations and repayments get their own stale-feed rule, because blocking them on a stale feed lets bad debt grow. Protofire writes the consumer contracts for Chainlink, Pyth or RedStone feeds. For pull feeds, we add keepers and a server-side proxy, so no API key ships in a front end.
A tokenized fund strikes its NAV once a day, so lending venues cap the feed. A stablecoin issuer can check a reserve figure onchain before each mint. A reserve check before minting fails in three known ways. First, the check compares reserves with totalSupply() on one chain while the token is deployed on several chains. Second, the check accepts a reserve figure older than the feed's heartbeat. Third, the check scales a reserve with the wrong decimals, which Chainlink says can allow "over-minting" (Chainlink). Protofire wires the feeds into minting and lending with caps and tests the reserve check against those three failures. We also build a daily match of the onchain NAV against the fund administrator's figure. Our proof of reserve page covers the data pipeline. A Protocol Roundtable episode covers pricing tokenized assets.
Alerts fire on a missed heartbeat, a price jump or disagreement with a second source. Each alert has an owner and a runbook. Protofire's engineers run the monitoring under a written scope (managed onchain operations). Otherwise, your team runs the monitoring once your team has the runbooks.
Source: Chainlink's network integration page, read November 2026. Chainlink calls the list a reference that can change, and single services may add their own requirements.
A chain team sends its RPC, multisig and explorer setup.A protocol team sends the contracts that read prices, or a repository. A Protofire engineer goes through the material before the first call. The full process is on how we work.
How we work shows a worked proposal.
An outside oracle team adds little to your project in four cases.

Dillon Hanson, DIA
Moment at 28:37Episode 2 · Ghost Town Markets: Building Secondary Liquidity for Real-World Assets
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.