Behind the bet17 SEP 2026

The September file / 02

The code
has a name.

The builder code in the farm’s orders resolves to Firefly. Firefly’s payment profile appears on the same payroll. And a funding wallet connects two treasuries already in the investigation.

01 / An old unknown, resolved

One builder code.
One name. One payee.

The original investigation called 0xe67c1c79…22f77 an unlisted code. The September 16 directory maps that exact 32-byte value to Firefly, marked verified. The profile receiving payroll payments is Firefly-EverythingApp.

Onchain orders

39 farm wallets
+ ghost

One maker-side fill rechecked for every farm-sample wallet. All 18 archived ghost fills rechecked.

Inspect the order logs ↗
Official directory

Firefly

Exact builder-code match.
Directory logo references Polymarket user 4090895.

Open directory data ↗
Payment profile

Firefly-
EverythingApp

Public-profile API returns user 4090895 and wallet 0xd3ea…ee97.

Open profile data ↗

26 August / two payments

584.10 USDC.e from the payroll.

The documented operator 0xc012…59efe sent two ClipperPayout batches containing 286.94 and 297.16 USDC.e for the Firefly profile. Both payment legs match the token contract, recipient, amount and log index in successful transaction receipts.

Open both payments ↗

What the code records

Order attribution to Firefly.

The exchange’s OrderFilled event puts the builder code on each order. The verified logs record attribution to Firefly for these wallets. Polymarket’s builder program uses attribution for volume and reward accounting.

Read the exchange event definition ↗
Read the sample reconciliation

The older “40-wallet” export contains 39 farm-sample wallets and ghost. Its archived tally is 19,959 Firefly-coded fills out of 26,704 for the 39 farm wallets, plus 18 of 18 for ghost. This update independently rechecks 39 farm examples and all 18 ghost logs: 57 unique fills across 40 wallets.

The current builder directory contains 543 entries across 11 pages. The published historical wording remains in the archive; this finding updates the identity of its previously unnamed code.

Download every example check ↓

02 / The funding wallet

Two money trails
meet at 0x2d507.

0x2d507…dea54 sent 2,100,001 USDC.e to the documented payroll money-mover across four transfers in March and April. On September 9, it sent 75,000 PUSD to the machine treasury.

Common sender0x2d507…dea54Open wallet ↗

78 seconds later

47,006 PUSD to User1244322.

The machine treasury sent 47,006 PUSD to the public-profile wallet 0xe558…fdcd2 at 23:28:58 UTC. Its PUSD balance was 3,937.141718 before the 75,000 deposit, 78,937.141718 after it, and 31,931.141718 after the payment.

Inspect the payment and balances ↗

The earlier reverse transfer

100,000 USDC.e went back.

On January 10, the machine treasury sent 100,000 USDC.e to 0x2d507. This is a two-way financial relationship, spanning eight months and two token contracts. The transfer table preserves each direction and denomination.

Open the January transfer ↗
Read the funding-wallet census

Pagination reached the January 1 boundary: 1,959 explorer transfer records, including 1,736 transfers of the allowlisted tokens. The counterparties export shows every incoming and outgoing total separately by token. This is a high-volume funding wallet with many counterparties.

The balance check reads the PUSD contract at the block before and after each September transfer. Block timestamps put the two transfers 78 seconds apart. The machine treasury had insufficient PUSD for the 47,006 payment before the deposit arrived.

Download the counterparty census ↓

03 / Open the evidence

Click a connection.
Read its receipts.

Each row names the relationship established by its source: builder attribution or a token transfer. Amounts remain in the token actually transferred.

All nine verified payment legs
UTCFromToAmountTokenReceipt
2026-01-10 20:40:58Machine treasury0x2d507…dea54100,000.00USDC.eLog 562 ↗
2026-03-20 22:59:530x2d507…dea54Payroll money-mover100,000.00USDC.eLog 5913 ↗
2026-04-28 21:29:160x2d507…dea54Payroll money-mover1.00USDC.eLog 1264 ↗
2026-04-28 22:05:240x2d507…dea54Payroll money-mover1,000,000.00USDC.eLog 486 ↗
2026-04-29 21:48:240x2d507…dea54Payroll money-mover1,000,000.00USDC.eLog 2102 ↗
2026-08-26 16:59:30ClipperPayoutFirefly profile286.94USDC.eLog 206 ↗
2026-08-26 17:02:06ClipperPayoutFirefly profile297.16USDC.eLog 1025 ↗
2026-09-09 23:27:400x2d507…dea54Machine treasury75,000.00PUSDLog 965 ↗
2026-09-09 23:28:58Machine treasuryUser124432247,006.00PUSDLog 236 ↗

04 / Reproduce the findings

The joins.
The logs. The checks.

Official Polymarket metadata, raw Polygon receipt checks and a pinned wallet-control sweep. Forty of 47 traced histories reached their requested date boundary. Individual coverage is recorded in the downloads.

1,157 wallets checked for control.

At Polygon block 93,916,082, the owner and Safe checks returned two shared-controller groups. Both are public infrastructure: Polymarket contracts and Stargate contracts. These checks produced no new shared customer controller.