Gnosis Conditional Tokens Explorer
Gnosis built the Conditional Tokens Framework, the on-chain primitive behind prediction markets such as Omen: a way to lock collateral against a future outcome and split it into tradable position tokens. The contracts were public, but there was no plain interface for the operations they exposed, so a developer had to script raw calls to prepare a condition, split a position, or redeem after a result was reported.
Protofire built the Conditional Tokens Explorer, an open-source web application that puts that whole lifecycle behind a browser interface on Ethereum and Gnosis Chain. Users connect a wallet and work through the framework's operations without writing code. The source Protofire built is public and now hosted in the Gnosis org at github.com/gnosis/conditional-tokens-explorer.
“The framework lived as a set of contracts, so every action meant assembling and signing low-level transactions by hand.”
Why the Conditional Tokens Framework is hard to operate directly
Gnosis designed the Conditional Tokens Framework as a general primitive for conditional, outcome-based tokens. A team defines a condition (a question, an oracle that will answer it, and a fixed set of outcome slots), locks collateral against it, and receives position tokens that pay out once the oracle reports. That model is what lets Omen and similar markets exist, and it is flexible enough to nest positions for combinatorial outcomes.
That flexibility came at a cost in usability. The framework lived as a set of contracts, so every action meant assembling and signing low-level transactions by hand. The operations are not simple transfers: preparing a condition ties together an oracle address, a question identifier, and an outcome-slot count; splitting turns collateral into ERC-1155 position tokens across those slots and can split from raw collateral, from an existing position, or into deeper collections; merging reverses it; redeeming only works once payouts are reported, and reporting is a distinct on-chain action tied to the oracle; positions can also be wrapped into ERC-20 to trade on standard venues, then unwrapped.
Each step has its own arguments, ordering, and failure modes, and none are legible from a generic block explorer that shows only transactions and balances. For a developer evaluating conditional tokens, or an operator managing live positions, there was no way to see current state or act on it without custom tooling. That friction sat in the path of the adoption Gnosis wanted for the framework.
How Protofire built the Conditional Tokens Explorer
Protofire built the Conditional Tokens Explorer as an open-source web application that maps each framework operation to a screen. Users connect through MetaMask or WalletConnect and work directly against the contracts on Ethereum or Gnosis Chain. The interface covers the full position lifecycle described above: preparing a condition, including conditions shaped for Omen; splitting positions from collateral, from an existing position, and into different collections; merging back into collateral or another position at the same level; reporting payouts; redeeming a resolved position; listing the positions a wallet holds; and wrapping or unwrapping a position into an ERC-20 token.
The build is TypeScript and React, and the repository carries the Docker and Node tooling to run it. Because it is open source, a team integrating conditional tokens can read exactly how each operation is constructed and run its own instance.
What shipped
The Explorer exposes the complete conditional-token lifecycle through a browser, so the operations above are reachable without hand-built transactions. The source Protofire built is public and inspectable for any team building on the framework; it is now hosted in the Gnosis org and was last updated in 2023.