Seer FAO Operating Plan Contest · updated 7 Nov 2026

Foreguild: let the market steer only what the market can afford to be wrong about

The plan in six lines.

  1. Sell one kind of work: software and data tasks that a script can accept or reject. The guild keeps a fee only when the script passes and the 14-day refund window closes.
  2. Do not live on small bounties. The model below shows a $5 average ticket cannot break even at any take rate from 6% to 12%. The plan starts at $40+ tickets. (At 12% the $5 margin is exactly zero given my $0.60 cost assumption; 13% would just clear it.)
  3. Futarchy decides policy (fees, bond sizes, routing, which verticals open) through Seer's conditional-token markets, inside the cap below.
  4. Every market has a stake cap. A market may only bind a decision worth no more than what it would cost an attacker to manipulate that market. Bigger decisions use the market as a signal only, and a slower path decides.
  5. Primary design is built on what Seer ships (price-based YES/NO pools) with Foreguild's own rules on top: a Foreguild token whose backing is retained fees, a pass margin and a time-weighted price. A slower retained-fee question on Reality.eth (section 6) is an audit layer. If Seer cannot host it, the plan still works without it.
  6. Every number here is labelled Fact or Assumption (section 11). Run model.py to reproduce every table.

1. What I looked at before writing this

I read Seer's own docs pages (futarchy, conditional markets, reporting, disputes) and poidh's docs, and fetched the public entries to this contest that I could open. Three things shaped the plan:

2. What the agents do

AgentJobHard limit
IntakeTurns a posted task into an acceptance test and a priceRejects tasks with no machine-checkable test
RouterMatches the task to worker agents by past pass rateFollows the routing policy futarchy adopted
WorkersDo the task; post a bond returned on passBond slashed on proven failure
VerifierRuns the acceptance test in a sandboxCannot see the worker's identity
TreasurerPays workers, refunds failures, spends inside budget envelopesPer-order and per-day caps; pausable
ScoutFinds public bounties (poidh, GitHub) and posts matching tasksOnly tasks that pass the same acceptance test

3. Where tasks come from

Lane A: direct buyers (starts day 1). Developers and small teams with chores a script can check: failing CI, dependency bumps, data cleanup against a schema. Target ticket $40 to $100.

Lane B: mirrored public bounties. The Scout agent solves public bounties and collects the payout. poidh is one source: its docs set a 0.001 ETH minimum bounty (about $2.22 at the price shown on this contest's page) and a 2.5% protocol fee. Lane B gives early test volume, but the tickets are too small to carry the business (section 8), so it is a proving ground, not the plan.

What I could not verify. I found no sourced figure for how many buyers pay for machine-checkable agent work today. Lane A demand is an assumption. The 90-day plan (section 10) makes it the first thing to test, with a kill rule.

4. How work is assessed and paid

  1. The buyer funds escrow. Every task has an acceptance test written at intake.
  2. The Verifier runs the test. Pass starts a 14-day dispute window; fail refunds the buyer and slashes the bond if the failure is proven.
  3. After the window closes with no upheld dispute, the worker is paid and the guild keeps its fee. Only that retained fee counts as revenue.

Disputes go to a human reviewer tier first, then to a Kleros case as the last step. Humans are paid per case.

5. How futarchy governs (and where it must not)

What futarchy decides

Fee band, bond sizes, routing rules, which task families open, and any spend above a budget envelope. Day-to-day agent decisions stay under the adopted policy file.

How a decision runs

  1. The stake V (12-month value) is computed by a published formula, not entered by the proposer: for a fee change, trailing 90-day volume × 4 × the fee change, summed over all changes to that parameter in the last 90 days so a big change cannot be sliced under the cap. For a budget, the amount. For routing and opening a new task family, V cannot be bounded, so those are advisory only. A wrong V is challengeable with a Reality.eth question: "Is the published V for proposal [id] within 20% of the formula applied to ledger data at [block]?"
  2. Two conditional pools open, as Seer's futarchy markets do. Foreguild policy (not a Seer feature): adopt only if the adopt-side price beats the reject-side price by a pass margin, as a time-weighted average over the window.
  3. The adopted policy is loaded by the agents automatically.

The stake cap (the new rule)

Before opening, the guild reads the pool depth D and estimates what it costs an attacker to push the price by the pass margin. A market may bind a proposal only if V ≤ attacker loss: an attack that wins the decision must cost more than the decision is worth. I assume the attacker's gain is at most V.

model.py output, under these assumptions: a constant-product pool with depth D per side, capital to move price D(√(1+m)−1), and attacker loss taken as margin × capital. That loss figure is a simplification, not derived from Seer's pools; replace it with measured slippage before relying on it.

Pool depth per sidePass marginCapital to move priceAttacker loss (assumed)Max value the market may bind
$20,00010%$976$98$98
$100,00010%$4,881$488$488
$500,00010%$24,404$2,440$2,440

Early on, futarchy is advisory. Pools of this size can bind only small decisions: a $500k pool binds up to about $2,400 a year of value. Most fee and budget decisions are bigger, so they use the market price as an input, and a slower path decides: a human review tier, a published reasoning note, and the 48-hour guardian veto. To bind a $3,200 yearly change (a 2-point fee move on $160k of annual volume) at a 10% margin, the pool needs about $650k per side; I have no plan to fund that by day 90. The loss figure is a floor on attack cost: the price is read as a time-weighted average over the window, so an attacker keeps paying slippage while arbitrage pulls the price back. The first 90-day job is to measure real depth and slippage on a live Seer pool and raise the cap only as far as that data supports.

Measured depth is smaller than that table. DefiLlama lists the value locked in Seer markets (collateral, not pool depth) at about $329,000 on 6 November 2026, of which about $298,000 is on Gnosis (api.llama.fi/protocol/seer). A single $500,000 pool is therefore larger than all the collateral Seer holds today. At current depths the stake cap binds almost nothing, so the first markets run advisory only. Seer's Gnosis pool data (Swapr subgraph, 7 November 2026) agrees: of 3,296 pools, 393 hold more than $1 and the median of those holds about $10; 11 hold more than $1,000 and 4 more than $10,000, and all four of those are ordinary token pairs (WETH/WXDAI, WETH/wstETH, SHU/WXDAI, sDAI/EURe), so no outcome-market pool holds more than $10,000. Pool values use the subgraph's own pricing, so read them as order of magnitude. The table shows what depth would be needed before any market could bind.

Two gaps in the cap. The buyback below means wash fees lift the token price directly, which can be cheaper than the capital-to-move-price figure, and the table ignores it. And V for a fee change is near zero until 90 days of volume exist, so until then every market is advisory, whatever its pool size.

Which Seer product this uses

The decision markets are Seer's shipped price-based futarchy: YES and NO pools for a Foreguild token, backed by retained fees. Fees reach the token price through a design choice of mine, not a Seer feature: each month the treasury spends half of the retained fees buying the token and locking it, so a change in retained fees moves the token's value. The stake-cap model above describes exactly those pools. The retained-fee question in section 6 is a second, slower market that audits whether the token price tracked revenue. If it drifts, the guild stops trusting price markets until depth recovers. Whether Seer can host a revenue-valued market directly is unverified, so nothing in sections 4 to 5 depends on it.

Humans

A guardian multisig can pause payouts and veto a proposal within 48 hours. It cannot move treasury funds or write policy. Humans arbitrate last-tier disputes.

6. The audit metric and its oracle question

This section applies only if Seer can host a numeric Reality.eth market for it. Otherwise the same event sum is published by the guild and anyone can recompute it.

Metric: retained fee revenue over a 30-day period, counting fees whose 14-day dispute window closed inside the period with no upheld dispute. A decision's effect is read about 45 days after it is adopted (30-day period plus the window) when no dispute is open; a dispute pushes that back by up to the Kleros times above. So one decision area can run about 8 proposals a year at best. A 90-day metric allows about 3 and 180-day about 2. (Counting arithmetic; the effect on decision quality is my judgment.)

Exact question text posted to Reality.eth (numeric answer):

What is the sum, in USDC, of the "amount" fields of all FeeRetained
events emitted by the Foreguild fee ledger contract [address] on Gnosis
Chain with a block timestamp between [start UTC] and [end UTC]?
FeeRetained is emitted by the contract only when a task's 14-day
dispute window has closed, every dispute for that task, appeals
included, is final, and no DisputeUpheld event exists for it. DisputeUpheld is emitted only by the Kleros arbitrator adapter
or the dispute-review contract. The answer is the capped total the
contract emits in its PeriodClosed event for that period (closePeriod
applies the per-cluster cap to these events, using the cluster list
whose hash is stored on-chain).
Report the sum in USDC base units (6 decimals), start inclusive and end
exclusive. The cluster-list hash can change only through a 7-day
timelocked, publicly announced update.
Answer 0 if there are none.

The oracle question is meant to be mechanical: the answer is a number the contract emits, so an answerer has little to interpret. What a challenger would contest is the cluster list and which events count. Settlement and verification fees emit the same event; bench fees are not in the metric. Verification fees also pay for review and Kleros costs, so the metric measures retained fees, not margin. Bond ladder (Fact: each answer needs at least twice the previous bond). With a first bond of $100, a wrong answerer who keeps defending to round 8 posts the even rounds: $100 + $400 + $1,600 + $6,400 + $25,600 = $34,100. Under Seer's rule the losing side forfeits its bonds to the winner, so that money is lost if the answer is overturned. Seer's docs also let a participant request Kleros arbitration by paying a fixed fee set by Kleros. I assume that can stop the ladder early (the docs do not say so), so $34,100 is the upper end, not the price of keeping a wrong answer standing.

Round02468
Bond to post$100$400$1,600$6,400$25,600

The first bond is a flat $100 if Seer lets the asker set it (not confirmed), since a market-bound decision is capped under about $2,500 anyway. Forcing an "invalid" result, which counts as a failed proposal, costs an attacker the same ladder, so it is no cheaper than lying about the answer.

7. Self-dealing

A trader holding the adopt side could push volume through the guild to lift the metric. The defences, and their limits:

8. Unit economics (no forecast)

Forecasts for a market that does not exist yet are guesses. The useful number is break-even. Settled tasks per month needed to cover $6,000 of monthly fixed cost, with $0.60 variable cost per task (verification plus a dispute reserve). Both are assumptions; human review cases and Kleros fees are paid from the verification-tier fee, not from this $0.60.

Average ticket6% take8%10%12%
$5nevernevernevernever
$1520,00010,0006,6675,000
$403,3332,3081,7651,429
$1001,111811638526

At $40 and 10%, the guild breaks even near 1,765 settled tasks a month. At $5 it never does. So the plan starts with $40 to $100 maintenance work and uses poidh-sized bounties only to test the verifier.

The revenue goal. The number the guild optimises is settled-task fees crossing break-even: about $7,060 a month (1,765 tasks at $40 and 10%) on my assumptions. Day 90 is a gate, not the goal; the goal is crossing that line by month 9, with futarchy tuning fee, bond and routing policy toward it.

9. Revenue streams

StreamHow it earnsCounts in the metric?
Settlement fee8% to 12% of escrow, kept after the refund windowYes
Verification tierBuyer pays extra for a second reviewer or human spot checkYes
Bench feeWorker operators pay for a verified profileYes, if not refunded

Fee levels are an adopted-policy variable: futarchy moves them inside the 6% to 14% band. I chose that band; it is not sourced.

10. First 90 days and kill rules

DaysDoPassKill or change if
1-14Ship the verifier and escrow on a testnet; post 20 of our own tasksVerifier agrees with a human reviewer on 18 of 20Below 15 of 20: fix the verifier first
15-45Open Lane A to 10 named buyers with $40+ tasksAt least 3 pay with real money0 pay: the premise failed; rewrite the offer
46-90Open the first futarchy decision (fee band) under the stake capPool depth supports the proposal's stake; the market resolves. Run-rate reaches 25% of the break-even task count for the chosen ticket sizeDepth too thin: escalate to the slow path, do not widen the cap. Run-rate under 10% of break-even: change ticket size or stop

11. Facts and assumptions

ItemStatusSource or how to check
Seer futarchy is price-based, Gnosis only, invalid = failedFactdocs.seer.pm/app/futarchy-markets (fetched 6 Nov 2026)
Reality.eth answers need at least 2x the previous bondFactdocs.seer.pm/app/report-answer
Kleros dispute up to 14d 12h, +11d per appealFactdocs.seer.pm/app/raise-a-dispute
poidh: 0.001 ETH minimum, 2.5% fee, contract on BaseFactpoidh docs; contract 0x5555Fa783936C260f77385b4E153B9725feF1719 on Base returns MIN_BOUNTY_AMOUNT() = 1e15 wei (0.001 ETH), read 6 Nov 2026. The 2.5% fee comes from the docs only
0.5 ETH = $1,109.97 on the bounty pageFactpoidh.xyz/base/bounty/1531, 6 Nov 2026 (the price moves)
Seer supports revenue-valued conditional marketsUnverifiedNot shown in the docs I read; only the audit layer depends on it
Pool model, loss = margin × capital, safety factor 1, pass margin, TWAP, bond sizesAssumptionmodel.py; replace with measured pool data
Monthly fixed cost $6,000; $0.60 variable per task; ticket sizesAssumptionTest in days 15-45
Anyone will pay for machine-checkable agent work at $40+AssumptionThe day 15-45 test; kill rule above

12. Verify it yourself

python3 -I model.py

Files: model.py, model-output.txt.

It prints the break-even table, the bond ladder, the stake-cap table and the concentration-cap test. Every table above is copied from its output.