Fairshake spent $10.0M — over half its 2026 war chest — trying to stop Juliana Stratton. She won anyway.

Basesolo bountyalbum: politics

proposed starting reward

0.0025 ETH

description

Chart: https://raw.githubusercontent.com/gmlokie/poidh-1544-proof/main/chart-stratton.png

THE DISCOVERY

In the 2026 cycle, crypto super PAC Fairshake spent $10,000,409.45 in independent expenditures opposing a single candidate — Juliana Stratton, in the Illinois Democratic primary for U.S. Senate. That is 51.5% of everything Fairshake spent independently in the entire 2026 cycle ($19,412,478.15). The industry's flagship political operation put more than half its war chest into stopping one Democrat in one primary — and she won the primary anyway (March 17, 2026: 507,689 votes, 40.4%, beating Rep. Raja Krishnamoorthi by 96,539 votes), then won the general election on November 3, 2026 (AP called the race at poll close; about 61–62% against Republican Don Tracy).

WHY IT'S SURPRISING

The crypto industry presents its political spending as decisive — the money that picks winners. On the numbers, Fairshake in 2026 was mostly an anti-candidate operation: it spent $13,296,611.79 opposing candidates and only $6,115,866.36 supporting them (2.17x more oppose than support). And its largest oppose campaign — $10.0M against Stratton, roughly triple what it spent opposing every other candidate combined ($3,296,202.34) — failed completely. Two giant spends landed in the three weeks before the primary ($4.79M on February 25 and $4.40M on March 4), and Stratton still won the primary by nearly 8 points. The money didn't just underperform; the candidate it spent the most to stop is now a U.S. Senator.

METHODOLOGY (reproducible)

All spending figures come from the FEC API (api.open.fec.gov), committee C00835959 (Fairshake), cycle 2026, Schedule E (independent expenditures). Endpoints, all with api_key=DEMO_KEY (works with no signup): GET /v1/committees/?q=Fairshake — identifies the committee; GET /v1/committee/C00835959/totals/?cycle=2026 — official totals (receipts $138,243,957.16; independent expenditures $19,412,478.15); GET /v1/schedules/schedule_e/?committee_id=C00835959&cycle=2026&per_page=100&sort=-expenditure_amount — the itemized spending.

The trap: every expenditure appears twice — once in a 24-hour report (F24) and once in the monthly report (F3X), under the same transaction_id. Naive sums give $66M. The correct rule is one row per transaction_id, with the F3X amount preferred. That rule reproduces the FEC's own published independent-expenditure total to the cent: $19,412,478.15 (difference $0.00). It also resolves an amended amount (transaction VCACEC3CE1EBF514072F: first reported $290,103.00, corrected to $109,091.64) and same-transaction rows reported under different dates in the F24 vs the F3X. One more quirk: the API's page=2 returns page 1 again, so the 7 smallest rows were recovered with sort=expenditure_amount (3 transactions, $2,030 — immaterial). The 19 Stratton transactions, with transaction_ids, are listed in the evidence package: https://github.com/gmlokie/poidh-1544-proof

Note on precision: these are independent expenditures — money spent for or against a candidate without coordinating with the campaign — not direct contributions to the candidate. Every dollar above is oppose (O) spending; Fairshake gave Stratton's campaign $0 directly.

EVIDENCE

WHAT THIS DOES NOT CLAIM

Correlation is not causation. Stratton also had powerful backing — Gov. J.B. Pritzker supported her with about $10M in the primary — and a popular progressive message in a Democratic primary. This finding is not "Fairshake caused a loss" (it didn't — she won) and not "money never matters." It is narrower and stranger: the industry's biggest single bet of the cycle, $10.0M against one candidate, bought nothing. Final certified general-election margins were still pending at publication; the winner is settled, the final margin is not.

draft author

creating a bounty submits an onchain transaction from your wallet. editing changes only your copy; the shared draft stays the same.

this is a reusable bounty draft. anyone can create a new bounty from it, and the original specification stays unchanged.

discussion

0 comments

loading comments...