DeFi Protocol Engineering for Teams With Audited Contracts and a Launch Date
Protofire does DeFi protocol engineering for teams with audited contracts and a launch date. We build the role map, oracle adapters, keeper code and indexers, and your timelock or Safe holds each role. In 2020 Kyber Network announced a contract we built.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Who controls a protocol once the audit is done
An audit report does not say who can change, pause or liquidate once a protocol is live. That answer depends on the setup around the audited commit. Protofire does DeFi protocol engineering for that setup, and the team's timelock or Safe holds each permission.
For example, the audit report is in and launch is set for Thursday. In the deploy channel, someone asks who can pause the lending market if a price feed freezes. Three people give three answers. The report does not say which of them is right, because the answer is in the setup around the commit it covers.
Who holds each permission once a protocol is live
The protocol team holds each role and key from deployment. Its engineers deploy the code that Protofire builds.
Governance or signers
Timelock and access manager
Front end and terms
Price sources
Downtime signal
Role map and deploy scripts
Oracle adapters
Keeper and liquidation code
Indexers
What an audit report covers and what the launch team decides
An audit report covers one commit, the files it lists and the trust assumptions its authors write down.For example, OpenZeppelin's report on Uniswap v4 core states "We audited the Uniswap/v4-core repository at commit d5d4957" (OpenZeppelin, 27 August 2024). The same report names two privileged roles, the protocol fee controller and the owner, as "trusted to not behave maliciously". A report lists what its authors found in that scope, but it does not guarantee that the code has no bugs.
Four things are outside an audit report's scope. The first is a TimelockController deployed with its optional admin. With that admin, one key can grant and revoke the proposer, executor and canceller roles with no delay. The second is an oracle read that has no maximum age. The third is a lending market that waits for liquidations that nobody calls when gas spikes. The fourth is monitoring written for OpenZeppelin Defender, which stopped when OpenZeppelin retired the hosted platform on 1 July 2026. Voters, auditors and counterparties can read the first two from the contracts on launch day.
Regulators have started to read the same facts about who controls a protocol. The European Commission's MiCA review consultation closed on 30 September 2026. It asked respondents to rate "Presence of control by an identifiable person or group of persons (e.g. via admin keys)" as one criterion for a protocol that is not fully decentralized. In June 2026 the UK's FCA said it will apply its crypto rules "to firms engaging in DeFi where a clear controlling person undertakes cryptoasset activities" (FCA PS26/11). Your counsel decides how each text applies to your roles.
The optional admin can aid with initial configuration of roles after deployment without being subject to delay, but this role should be subsequently renounced in favor of administration through timelocked proposals.
Our record: Kyber, Swarm Markets, The Graph and Solhint
Kyber, Certora, the Graph Foundation and the Ethereum Foundation have named Protofire's work on their own pages.The Swarm Markets case is our own record. In May 2020 Kyber Network announced the pool master proxy contract we built. The contract let KyberDAO pool operators run non-custodial KNC staking and voting delegation.
In 2021 Protofire built the DEX core and subgraph for Swarm Markets and contributed to its dOTC contracts. Swarm Markets was a BaFin-licensed DEX at launch where only KYC-verified wallets trade. Swarm held the license and ran KYC and permissioning.
In 2023 and 2024 Protofire built the open-source ve8020 Launchpad, a vote-escrow staking framework. Certora audited its Solidity contracts and published its report in March 2024.
On The Graph, Protofire was a top-3 Graph indexer by indexing rewards, 2020 to 2024. The Graph Foundation funded our subgraph development and support in its second grant wave of July 2021.
Solhint, Protofire's open-source Solidity linter, has been downloaded 25M+ times from npm. The Ethereum Foundation's Ecosystem Support Program funded our work on Solhint in three allocations: Q4 2022, Q4 2023 and Q1 2025.
Role maps and price reads use Safe and Chainlink, and Protofire's work covers both. We deployed Safe on 120+ EVM networks, where it secures $2B+. Our work on Safe goes back to 2018. Protofire is a Chainlink core contributor and helps maintain Chainlink CCIP.
What DeFi protocol engineering gives a team at launch
Your team launches knowing who holds each permission.Each price read has checks, and each bot's code is in your own repository.
Each permission has a named holder and delay
Your docs can show who can upgrade, pause or change a parameter, and behind which delay. Protofire writes the role map and the deploy scripts, which run from a key you hold. In one run, the scripts grant each role to your timelock or Safe and revoke the deployer. A check script then reads each holder from the chain after a release.
Oracle adapters that reject a stale price
Protofire writes one adapter per feed, with a maximum age, bounds and decimals. On rollups that have Chainlink's uptime feed, the adapter also includes the sequencer check. As of November 2026, Chainlink "is no longer expanding L2 Sequencer Uptime Feeds to additional networks". So on other chains, you choose the downtime signal. Our oracle integration page covers the checks.
Liquidation and keeper bots that your team runs and can stop
Protofire writes the code for liquidation, keeper and price-push bots, with their alerts, in your repository. Your engineers review, merge and deploy the code on your hosts, with your key and capital. Protofire cannot reach the host or the signing key. Our white-label lending page covers a lending market that you own.
A subgraph or indexer for the app and the books
Protofire builds a subgraph or indexer that gives the front end current positions. It also writes a record for each event, with that event's log index and transaction hash. A lag check compares the indexer with the chain head.
A fix or written risk acceptance for each audit finding
Protofire freezes the commit and the file list for the auditor. For each finding, we write a fix commit or a written risk acceptance. We also check that the deployed bytecode matches the reviewed commit. Our smart contract audit page covers the review itself.
Monitors and a runbook that names who responds
The monitors watch role grants and scheduled timelock calls. They also watch pause events and price moves. A runbook names who holds each response permission. Rules written for Defender move to OpenZeppelin Monitor or to the tool you run today, as our managed onchain operations page describes. Other pages cover each kind of protocol in more detail. DEX development covers a DEX or AMM, perps DEX development covers a perps venue, and native stablecoin covers a stablecoin.
Four steps from the audited commit to a published role map
The work starts from what you already have.
- Step 1
You send the commit and today's role holders
You send the repository at the audited commit, the deploy scripts and today's holder of each role. You also send bot logs under NDA, with user addresses removed. - Step 2
The written proposal names each role holder
The written proposal names each role holder at launch and the price source for each asset. The proposal also lists the write calls that a service run by Protofire would be allowed to make. - Step 3
Your engineers review our pull requests
Protofire opens pull requests in your repository. Our scripts can prepare and simulate governance calldata, and the proposer submits that calldata. Your engineers review, merge and deploy the code. - Step 4
Your timelock or Safe holds each role after deployment
The deployment run grants each role to your timelock or Safe and strips the deployer's rights. As a result, Protofire holds no proposer, executor, canceller, admin or pause role. Where Protofire runs a monitor or an indexer that only reads the chain, we run it under a written scope. Each response is signed with your keys.
How work with Protofire starts
Bots and indexers connect to the chain through RPC endpoints and keys that your team issues.
- 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 this work is not the right fit
- You have a new protocol with no contracts yet. Protofire's DeFi development service covers that case. DeFi protocol engineering starts from contracts you already have.
- You need someone to hold power or capital. You may want a signer, voter or proposer for the protocol. You may also want an emergency key holder or liquidity for liquidations. Protofire provides none of these, and the bots trade with your capital.
- You need an independent review or risk parameters. An independent review is an audit by a firm with no part in the build. Risk parameters are collateral factors, caps and liquidation incentives. Your risk staff or an appointed risk manager sets those parameters, and our scripts include them. Vendors such as Hypernative build detection products that watch and respond on their own. Protofire's monitors alert the role holder who answers.
- You have legal or license questions. Legal structure, token classification and a license waiver for Aave or Uniswap code are questions for counsel and each licensor.
Protofire's work fits a protocol team whose contracts are written or forked and whose launch date is set. A team gets the most from the work when nobody yet owns the role map, the oracle checks or the keeper code.
Platforms we integrate for DeFi protocols
A protocol team picks an oracle network, a multisig for its roles and a monitoring tool.
Chainlink
Oracle feeds and CCIP for cross-chain transfers.
Left to you: Choosing feeds, the contracts that read them, and monitoring.
Chainlink integrationSafe
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 pageHypernative
Real-time threat detection with automated response.
Left to you: Which role, module or keeper may act and who revokes it, who can unpause, who administers the Hypernative account, the hooks into your Safe or MPC signing, and the incident runbook.
Hypernative integrationFAQ
What is DeFi protocol engineering?
Who can build the role map, oracle guards and keeper code for a DeFi protocol?
Who runs our liquidation bot, and whose capital does it use?
We used OpenZeppelin Defender. What happens to our monitors and relayers?
Can we fork Uniswap or Aave code for our protocol?
Can Protofire build our front end, and who hosts it?
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.
