Prediction Market Software for Venues and the Teams Building on Them
Protofire builds prediction market software for EVM venues and for teams whose agents or market makers trade on them. We write the oracle adapter, Safe accounts with contract-enforced limits, the indexer, and market-making and agent code in your repository. Gnosis funded Protofire's front-end work on the Omen MVP.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Software around a market breaks when the venue's contracts change
Prediction market software reads a venue's contracts, and a venue can replace those contracts. Polymarket's migration guide set 23 November 2026 as the first trading day for markets on its Protocol V2. The guide says "Existing CTF holdings are not converted", and existing markets keep their current contracts.
A wallet flow, an indexer or a trading agent written for Polymarket's Conditional Tokens markets has to handle two position ledgers. Polymarket's guide for contract integrations says "V2 positions use a separate ledger" and "Existing CTF approvals do not carry over". That means each account grants new approvals before it trades on V2 markets.
The migration also changes how proposers submit results for Polymarket V2 markets. UMA's guide to the migration says proposers must submit V2 proposals through the API, and "Onchain proposal transactions will be blocked".
For example, your agent product places orders through a Safe on a venue you do not control. The venue announces new contracts. Which of your systems stops working first?
Protofire starts each build from one written list: each contract your systems call and each event they read, with the venue version next to it.
Who builds and who holds each part around a live market
Protofire builds the contracts, accounts, indexer and trading code in your repository. Third-party protocols answer each market's question.
Capital and trading limits
Signers and keys
Position contracts and oracle adapter
Accounts and limits
Indexer and data API
Market-making and agent code
Oracle answers and disputes
Account contracts and modules
Agent code and Mechs
The prediction market software Protofire writes in your repository
Protofire builds six parts around a live market.Your firm picks the parts it needs.
Position contracts with one documented interface
Your wallet flows, indexer and agents read one documented set of calls and events. Protofire builds the condition, split, merge and redemption calls on the Conditional Tokens Framework or on your own ledger. Our prediction market development page covers a venue's own market contracts in detail.
An oracle and dispute path your signers watch
Your signers learn when someone proposes, disputes or flags a result. Gnosis's ConditionalTokens contract accepts one payout report per condition and rejects a second with "payout denominator already set". Protofire writes the adapter for your oracle and a monitor of proposals, disputes and flags. Markets settled on a price read a feed, which our oracle integration service covers.
Safe accounts with limits for each agent
Your users and agents trade through Safe accounts, and a contract enforces the limits you set for each agent. Protofire sets up each Safe with token allowances and, for contract calls, a roles module scoped to the calls you list.
An indexer and a data API
Market-making code your firm controls
Your markets get liquidity from code in your own repository, with parameters your firm sets. Protofire writes LMSR or fixed-product AMM contracts funded from your liquidity account, or a quoting client for an order book.
Agent onboarding on open-source code
Your users fund and configure agents from your own screens. The agent code is an open-source fork that your engineers can read and change. Protofire builds the onboarding screens and adapts the agent to your venue.
Agent limits in configuration and in a contract
A trading agent's configuration limits its bets, and a limit that a contract enforces is separate work.
Valory publishes trader, the Olas prediction market agent, under the Apache 2.0 license. As published, the agent trades on Omen on Gnosis Chain and on Polymarket on Polygon. It asks an AI Mech for a probability estimate and executes through a Safe.
Valory's agent reads its bet bounds from its own configuration. One setting caps the size of each bet, and another stops trading if the Safe balance would drop below a floor. The agent's own code applies both settings.
Protofire sets up the agent's account as a Safe with Safe's Allowance module. The module gives the agent's key an allowance for each token, and the allowance can reset after a set number of minutes. The longest reset span is around 45 days. The module covers ERC-20 and Ether transfers, so it does not limit which contracts the agent calls.
Where the agent has to call a market's contracts, Protofire adds a roles module such as Zodiac Roles, published by Gnosis Guild. Gnosis Guild describes it as scoping "authorized addresses, designated functions, and allowed parameter values" for each role. Protofire configures the role for the contracts, functions and amounts you list.
Safe's documentation on modules warns that "A malicious module can take over a Safe". The owners of a Safe add or remove a module with their normal signing threshold.
Running Valory's agent on another venue needs an adapter to that venue's contracts and its own account setup. Protofire builds both in a fork for your firm. Valory maintains its own repository, so your firm keeps its fork current.
Additional security measures, such as spending limits, timelocks, and whitelists, can be easily added to safeguard transactions. This is especially crucial since many AI agents can be influenced by specific prompts.
Our record: the Omen MVP front end, Safe and the Conditional Tokens Explorer
Protofire worked on two apps for Gnosis's Conditional Tokens Framework, and Safe merged our module deployments into its registry.
The Omen MVP front end, funded by Gnosis
Gnosis funded Protofire to do the front-end development of the Omen prediction-market MVP, under Omen's designer. A DXdao contributor's post on the Gnosis forum of 20 January 2021 describes the arrangement. Omen is a prediction market on Gnosis's Conditional Tokens Framework.
Safe deployments on 120+ EVM networks
Protofire builds venue admin accounts and agent accounts as Safes. We deployed Safe on 120+ EVM networks, where it secures $2B+. Our Gnosis Safe case study describes the Safe work.
Safe module deployments, October 2025 to April 2026
Protofire added Safe module deployments (allowance, ERC-4337, passkey) to Safe's modules registry for networks including Chiliz, Morph, Shape, Sei, Moonbeam and Ethereal. Safe merged the 10 pull requests between October 2025 and April 2026, and six of them are for the Allowance module. The Allowance module gives an agent's key its token allowances.
The Conditional Tokens Explorer for Gnosis, 2020 to 2021
In 2020 and 2021, Protofire built the Conditional Tokens Explorer for Gnosis. The open-source web app runs the framework's operations from a screen: preparing conditions and splitting, merging, reporting and redeeming positions. Gnosis's announcement of the Explorer points readers to Protofire's account of its contribution to developing it. Our case study describes the app.
From one list of contracts and events to a handover
- Step 1
A proposal with the contract list, oracle and owners
Protofire's written proposal holds the list of contracts and events, with the venue version next to each entry. The proposal also names the oracle, the owner of each account and each limit that a contract enforces. - Step 2
Code in your repository, tested against each venue version
Protofire writes the code in your repository. The tests run against each venue version that the proposal lists. - Step 3
Outside audit and fixes
You pick an outside audit firm, and Protofire prepares the code and fixes the findings (smart contract audit). An audit lists findings and does not promise code free of faults. - Step 4
Deployment by your signers
Your signers deploy the contracts and create each Safe. You own the repository, the contracts and the agent fork. Code from third parties keeps its own license terms. Your signers hold the keys. - Step 5
Indexer and monitors after launch
Under a written scope, Protofire can run the indexer and the monitors that read the chain after launch (managed onchain operations).
How work with Protofire starts
Work on a market's software with Protofire starts from the contracts your product reads today.You send the venue's contract addresses or your repository, your oracle and one market to support from creation to payout.
- 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 build in your own repository does not fit
Protofire writes the software, and your firm runs the venue or the product on EVM networks.
- You want a white-label prediction market that a vendor licenses and hosts. Protofire licenses no packaged prediction market platform and hosts no matching engine.
- You want someone to trade, quote, fund liquidity or run your agents. Your firm or your users run the market maker and the agents with their own capital and keys. Protofire holds no client funds or keys, places no trades and does not propose, dispute or vote on results.
- You need a license or a legal opinion on event contracts. Protofire holds no financial, gambling, derivatives or crypto-asset license and gives no legal opinion. The CFTC's proposal, published on 19 October 2026, would further define "swap" to explicitly include event contracts. Your counsel advises where your venue may take users.
- Your venue runs outside the EVM. Protofire's contract work is Solidity for EVM networks.
FAQ
What is prediction market software?
Who can build prediction market software for a venue or an exchange that adds event markets?
Should we license a white-label prediction market or build on our own contracts?
What is the Conditional Tokens Framework?
What happens when someone disputes a prediction market result?
How do you limit what an AI trading agent can do with funds?
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.
