Skip to content

Parametric RWA Protection for Issuers, Lenders and Capital Providers

For issuers, lenders and capital providers, Protofire builds trigger contracts and payout logic for measured events on tokenized assets. The capital provider's keys release each payout. 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.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. What you get
  3. How a trigger works
  4. Why Protofire
  5. Funding and authorization
  6. Not the right fit
  7. How work starts
  8. Related services and guides
  9. FAQ

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

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

Parametric RWA protection starts with written trigger terms

Parametric RWA protection starts by writing down which onchain state counts as the event, on which clock, from which source, and who may post it. For example, a capital provider agrees to fund a buffer for the holders of a tokenized fund. The term sheet says the capital provider pays if redemptions freeze. Until the freeze is written down in those terms, the payout is a sentence in a document.

The data that a trigger reads is thinner than it looks. Chainlink writes that many of its SmartData feeds, "including Proof of Reserve, NAV, and AUM feeds, rely on a single data source or provider such as an issuer, fund administrator, custodian, or auditor" (Chainlink). A trigger can follow its terms and still miss a real loss. It can also fire when there is no loss behind it. Supervisors call both gaps basis risk.

A trigger pays what the written terms say about a measured event. That amount can differ from the loss a holder suffered, so the terms decide who bears the difference. In the plain case, the protected party bears a missed event and receives nothing. The capital provider bears a false trigger and pays without a loss.

Protofire turns the written trigger terms into software: a specification, adapters for each source, trigger contracts and payout logic. The capital provider funds the buffer and controls each release. The issuer controls its token. We call the offer RWArmor.

Consumer protection concerns regarding basis risk focus on events when an adverse event occurs and the index is not triggered so no payment is made (adverse basis risk).
International Association of Insurance Supervisors (IAIS), Issues Paper, para. 64, IAIS · Issues Paper on Index-based Insurances, particularly in Inclusive Insurance Markets, June 2018

Layers of a parametric payout and who owns each one

The issuer and the data providers own the inputs. A watcher that the parties appoint posts each result. The capital provider owns the money and the release.

Issuer and data providers

Tokenized asset and vault

The asset has an ERC-3643 share token, an ERC-7540 redemption queue, and pause and freeze roles.

Data sources

The inputs are NAV, reserve data, oracle feeds and asserted notices.
Protofire builds

Source adapters

Each adapter reads a value together with its block and its age.

Trigger contracts, payout module and log

The contracts accept a result from the runner's key or a settled proposal, apply the terms, prepare the transfer and log each run.
Watcher that the parties appoint

Evaluation runner

The runner executes the adapters at a final block and posts each result under its own key.
Capital provider

Buffer and release

The buffer holds segregated funds, and the capital provider's keeper or Safe signers release them.

What Protofire builds for parametric RWA protection

Trigger terms written one line per event

Protofire writes the specification and a map of who publishes each value. Each event gets one written line in the specification. The line names the source, the threshold, the window and the clock. It also sets the staleness rule, the amount, the recipient and the cap. The capital provider, the issuer and their counsel review the specification before code exists.

Source adapters that show each value's source and age

Each NAV or reserve value arrives with its block, source and age. So a stale feed is logged as a data failure and cannot pass as a deviation. Protofire builds adapters for ERC-7540 request state and for ERC-3643 pause and freeze state. We also build adapters for Chainlink NAV and reserve reads, checked against each heartbeat, and for a second NAV reference from the appointed watcher.

Payout code tested on missed events and false triggers

Before launch, the capital provider sees the code run through a missed event and a false trigger. The tests use past vault and feed data where it exists. Protofire writes the evaluation contracts and the payout module. We also write deployment scripts that the capital provider's engineer runs with its own key. Code that Protofire writes goes to an outside review that the capital provider chooses. Our smart contract audit reviews code that another team wrote.

One run log with replay and alerts

Each run leaves an entry in one log, and a replay script re-runs it. So auditors, the issuer and the protected party see one record. Alerts flag stale sources and near-threshold conditions. Under a written scope, Protofire can run the alerts with read access to data credentials that the client holds. Protofire offers the wider service as managed onchain operations.

How a redemption freeze trigger leads to a payout

A redemption freeze trigger fires on the vault's own state.It fires when requests are stuck past the agreed window, as read at a final block. The example below is a fund with an ERC-7540 vault and an ERC-3643 share token.

  1. Step 1

    The terms set the event, the source and the clock

    The capital provider and the issuer agree one line per event. For a freeze, the line says how old a pending request may get. A dealing cut-off runs in local time, but block timestamps are in UTC, so the line names both clocks.
  2. Step 2

    The adapter tracks each open redemption request

    ERC-7540 tells requests apart by the requestId together with the controller address (ERC-7540). The vault emits RedeemRequest when a request opens. It emits nothing when the request becomes Claimable, and the standard leaves that transition to each vault. So the adapter indexes RedeemRequest events. It then reads pendingRedeemRequest and claimableRedeemRequest for each open pair of requestId and controller. Requests with different ids "MAY transition to Claimable at different times and exchange rates", so age is counted per request.
  3. Step 3

    The watcher evaluates the result at a final block

    The adapters run off-chain, in a watcher that the parties appoint. The watcher evaluates against a block past the chain's finality threshold. So the result does not depend on a block that can still reorganize. The watcher posts each result under its own key. Or the watcher proposes the result to an optimistic oracle, where it can be disputed during the challenge period. The trigger contract accepts a result from the watcher's key or a settled proposal.
  4. Step 4

    The issuer's own pause and forced transfers

    An ERC-3643 token must support a pause and wallet freezes, and holders' transfers fail while the token is paused (ERC-3643). The standard also requires that an agent can force a transfer. A forced transfer skips the compliance rules and needs a whitelisted, verified receiver. The issuer's owner and agent roles control these powers, so the issuer can create the event itself.
  5. Step 5

    The payout module prepares the transfer

    Once the condition holds for the whole window, the payout module computes the amount. The module then prepares a transfer from the buffer to the protected party's wallet. A keeper on the capital provider's own key calls the release. Or the capital provider's Safe signers approve the transfer.

Our record: reserve data, oracle feeds and price scrapers

Protofire's public work covers the data that a trigger reads: reserve figures, oracle feeds and scraped prices.

Reserve data 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. A reserve attestation trigger reads the figure that a pipeline like this one publishes. We sell that pipeline work as proof of reserve.

Chainlink integrations funded by Community Grants

Chainlink Community Grants funded Protofire's Chainlink integrations on Celo, Plasm, Avalanche and xDai (now Gnosis Chain). Chainlink's archived post of 27 August 2021 records those grants (Chainlink, archived). That integration work applies to the Chainlink side of a feed.

Price scrapers merged by DIA

Protofire wrote data scrapers for Bitflow and Velar on Stacks, Bifrost and Hydration on Polkadot, and an Alephium DEX. From June 2024 to January 2025, DIA merged those scrapers into its main repository. A scraper that turns one source's values into a feed has the shape of a source adapter.

Who funds the buffer, releases payouts and rules on disputes

Which party funds the buffer decides which authorization questions apply to each party.Where an insurer or reinsurer funds payouts, Solvency II (Directive 2009/138/EC) makes direct insurance or reinsurance business "subject to prior authorisation" (Art. 14(1)). In the UK, a regulated activity needs authorization or an exemption (FSMA s.19). Effecting insurance contracts as principal is one such activity (RAO art. 10). New York requires a license or an exemption for insurance business (Insurance Law §1102).

An insurer or reinsurer funds payouts

Capital and release: The insurer's own funds back the buffer, and its Safe signers or approvers release each payout

Disputed trigger: The insurer's own process, or an outside path that the terms name

Authorization question: The Solvency II, UK and New York texts apply to that firm

Outside capital providers fund a pool

Capital and release: The pool funds a segregated buffer, with the protected firm's share where agreed. The pool's Safe or governance releases payouts

Disputed trigger: The path that the terms name, such as an optimistic oracle's dispute vote

Authorization question: The IAIS, 2018: "It is often noted that index based insurance products might or might not be considered to be insurance at all" (IAIS)

An issuer or lender funds its own buffer

Capital and release: The firm's treasury Safe holds the buffer and the release role

Disputed trigger: The firm's process, written into its offering or loan documents

Authorization question: The firm's counsel reads each market's texts against the promise the firm makes to holders

When a trigger contract from Protofire does not fit

Trigger contracts help where an event can be measured and a party stands ready to fund the payout.

  • You need each actual loss assessed and paid case by case. That is indemnity from an authorized insurer.
  • You want a firm to bear the risk and hold the capital, or to approve payouts and offer protection to holders. Protofire is not an insurer and holds no insurance license. Protofire acts as no broker or loss adjuster, holds no capital and decides no disputed trigger. After launch, Protofire holds no payout key, result-posting key or token key.
  • No chain state, feed or assertable notice measures the event.
  • You need reserve figures published with no payout (proof of reserve). Or you need a contract that reads a feed safely (oracle integration).

How work with Protofire starts

Work starts with three things: a named event, a source that proves it, and a party ready to fund and release payouts.That party can be your own treasury. You send the redemption and suspension rules and the NAV and attestation sources. You also send the vault and token addresses and the capital provider's payout rules. If you share past vault and feed data under NDA, without holder addresses, Protofire tests the code against the terms before launch. The parties keep the specification, the adapters, the contracts and the log in their own repositories. Each data-provider subscription is in your name. The written proposal pairs each event with the source that its trigger would read.

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.

FAQ

What is parametric RWA protection?
Parametric RWA protection pays an agreed amount from a funded buffer when a measured event meets written terms. The event can be a redemption freeze, a NAV deviation or a failed reserve attestation. Protofire builds the trigger contracts, oracle adapters and payout logic. A capital provider funds the buffer and controls each release.
Who can build parametric protection for a tokenized fund or a collateral token?
Protofire builds the software for an issuer, lender, platform or capital provider that has a funding party. The parties keep the funding, the release keys and the authorization question.
Which authorization does a parametric payout arrangement need, and who holds it?
Each party's counsel decides, market by market. EIOPA's 2021 discussion paper describes parametric insurance as "a type of insurance" that agrees "to make a lump sum payment upon the occurrence of a triggering, objective and predefined event" (EIOPA). A 2018 IAIS paper adds that such products might or might not count as insurance at all. Protofire's part is the software.
Who pays when a redemption freeze triggers a payout?
The capital provider's buffer funds the payout, under the capital provider's own rules and keys. The buffer includes the protected firm's share where the terms include one. The payout module prepares the transfer to the protected party's wallet. The capital provider's keeper or Safe signers then release the transfer.
What stands between the event and the payout?
The payout waits for the observation window in the terms, block finality and the capital provider's release. An asserted event, such as a default notice, also goes through the request's challenge period. A disputed assertion goes to UMA's DVM, which settles it in commit and reveal rounds (UMA).
Does an issuer's own pause count as a redemption freeze?
The terms decide whether an issuer's own pause counts as a redemption freeze, and the tests include both outcomes. For a lender, a liquidation that needs a holder transfer fails while the pause lasts. A gate trigger can signal the lender's risk role to stop new borrowing first. The lender's Safe or risk administrator holds that role. The lending against tokenized assets guide compares the venues.
Can a NAV trigger use more than one source?
Yes, and a NAV trigger usually needs a second source. A deviation test compares two values for the same valuation point, such as the feed and the administrator's published NAV. The terms say which value governs when the two values differ.

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.