Omen

Omen was the prediction market that DXdao governed and that most early DAO futarchy experiments ran on. It matters to a governance-tooling directory for two reasons. First, it established the stack – Gnosis conditional tokens, Reality.eth resolution, Kleros arbitration, Gnosis Chain settlement – that Seer rebuilt and runs on today. Second, its website still loads but shows no markets, while software agents create markets on its contracts every day.

Everything below was read first-hand on 16 August 2026 off keyless surfaces: the deployed frontend bundles at omen.eth.limo and aiomen.eth.limo, the GitHub API, the Gnosis Chain and Ethereum Blockscout APIs, and a public Gnosis RPC. Nothing here is taken from coverage.

The app answers 200 and cannot show you a market

omen.eth.limo returns HTTP 200 and a 4,001-byte application shell titled “Omen”. Every liveness check anyone runs – status code, content type, page title – reads green. The shell is a React app that fetches its markets on load, and each of the three things it fetches from is gone:

• The market index. The bundle reads markets from api.thegraph.com/subgraphs/name/protofire/omen-xdai. That host now answers 301 and redirects every query to error.thegraph.com/apierror.json – The Graph’s hosted service was retired, and the subgraph was never republished to the decentralized network under this name. The subgraph repository is archived, last pushed 24 January 2023.
• The chain connection. The same bundle points at rpc.xdaichain.com, which has no DNS A record at all. Gnosis Chain retired that hostname; the frozen build never learned the new one.
• Its own identity. Every og: and twitter: tag in the shell still points at http://omen.eth.link/, and the inline bootstrap script still branches on hostname.endsWith(".eth.link"). The build predates the ENS gateway migration that replaced .eth.link with .eth.limo.

This is a sharper form of a failure the wiki tracks across its citations: a resource can die at HTTP 200. Here it is an entire application rather than a page. The frontend repository, protofire/omen-exchange, was opened on 5 September 2019, last pushed on 20 September 2023 and never archived. No one announced Omen’s closure: its maintainers stopped updating it, and the services it depends on were retired around it.

The contracts kept taking writes for three more years

The market-maker factory on Gnosis Chain, FPMMDeterministicFactory at 0x9083A2B699c0a4AD06F63580BDE2635d26a3eeF0, was deployed on 4 September 2020 and is verified. Its lifetime counters read 2,035 transactions and 141,860 token transfers. Its code still returns from eth_getCode on a public RPC.

It also still gets used. The most recent direct calls to create2FixedProductMarketMaker landed on 1 April 2026 – roughly two and a half years after the frontend’s last commit, and long after the app could display anything. Reading the fifty most recent inbound transactions, spanning 16 December 2025 to 1 April 2026, they come from exactly two addresses: 0x677C86…Fd02D (47 of them) and 0x3Cc14F…cbe7A (3).

Ethereum mainnet is the control case. The mainnet factory at 0x89023D…76220 carries three transactions in its entire history, the last of them a market created on 8 May 2023. Omen was a Gnosis Chain product in practice from the start, and the mainnet deployment barely moved.

Why a dead venue kept getting writes: it became an agent substrate

The two addresses are explained by software that was, when this was first written, very much alive. Gnosis maintains prediction-market-agent-tooling – opened 8 February 2024, last pushed 22 April 2026, 60 stars – a Python library for deploying autonomous agents that trade and create prediction markets. It ships a full markets/omen/ module, and its factory class hardcodes the address above, character for character. Its supported-platforms table lists three venues, and the one it supports for reading, betting and creating is AIOmen.

aiomen.eth.limo is Omen’s frontend rebuilt for that audience, and the rebuild is almost literal: its HTML shell is byte-identical to omen.eth.limo’s except for the two JavaScript chunk hashes. The bundle inside was partly repaired – the chain connection now points at the working rpc.gnosischain.com (POST-only: it answers eth_blockNumber and 404s a plain GET) instead of the dead rpc.xdaichain.com – but it still reads its market index from the same retired hosted-service subgraph. Both browser frontends are blind for the same reason.

The agents are not. The Python library reads Omen through The Graph’s decentralized network instead, at gateway subgraph IDs behind an API key. That single migration is the whole divergence. The read path a human needs was left on a service that shut down; the read path a program needs was moved to one that did not. People can no longer reach Omen through a browser, and programs still can.

Re-read on 12 October 2026: the agents never stopped

This section said on 8 September 2026 that the agents had stopped too, and that was wrong. The August and September readings both counted only the transactions sent straight to the factory, and the last of those is still the 1 April call. A market created through a Safe multisig reaches the factory as an internal call, which never appears in that list. The factory’s own FixedProductMarketMakerCreation events record every market whichever route it took: 6,723 created between 1 April and 12 October 2026, at least 849 in every full calendar month, the latest on 12 October asking whether an FCC proposal would still be pending on 16 October.

Two Safes created 6,654 of them: 0x89c5cc…46Fec with 3,510 and 0xFfc802…3f557 with 3,144. The source of Olas Predict, the prediction dashboard of the Olas agent network, lists both as its market creators, under the names Quickstart and Pearl. Olas’s trader agent names Omen on Gnosis as the venue of its Omenstrat service and links aiomen.eth.limo for it; its repository was last pushed on 12 October 2026. Gnosis’s prediction-market-agent-tooling still has no commit since 22 April 2026, so the September reading was right about that library and wrong about the venue.

So the reading of 16 August stands: the browser frontends cannot show a market, and agents create and trade markets every day on the contracts underneath. The error generalises to any audit of a contract’s activity. A block explorer’s transaction list shows only calls made to an address directly, so a contract driven through multisigs or other contracts can look idle there for months while its event log records daily use.

What this changes about auditing a DAO’s tooling

Omen is a counterexample to two habits that DAO directories, this one included, fall into.

A live domain is not a live product, and a frozen repository is not a dead protocol. Checked from the outside, Omen looks maintained: the site resolves, the repository is unarchived, the social accounts still exist. Checked from the inside, its data layer has been gone for years. Meanwhile the part everyone treats as the archaeology – the deployed contracts – is the part still doing work. The two signals point in opposite directions, and the on-chain one is the one that is hard to fake.

The stack outlives the organization that paid for it. DXdao wound down; Omen’s frontend froze; and the conditional-tokens-plus-Reality.eth-plus-Kleros arrangement Omen proved out is exactly what Seer runs on Gnosis Chain today, carrying 441 futarchy markets of 2,003 Seer markets on that chain – up from 395 three weeks earlier, read from Seer’s own markets-search endpoint on 16 August and 8 September 2026. When a DAO winds down, the record should include which of its components other people picked up, a pattern the wiki treats at length in winding down a DAO.

How Caper approaches this

Omen’s frontends stopped showing markets to the people who used them, while anyone holding a contract address could still trade. A caper keeps a member’s exit on Caper’s own component on Radix, which a member calls from their own wallet, so leaving needs no website, indexer or hosted subgraph. If caper.network went offline, a member could still exit for their fair share; Leaving a caper covers what they receive.