What it does not show

Prediction markets on X

What the posts showed, and what the accounts held

Seven handles post picks, slips and results to their followers on X. The public record of their accounts, of the apps they promote and of the money between them shows what the posts left out, what the handles told their audience themselves, and what the record does not show.

Aug 2022202420252026
225 dated events110 payments from app-side wallets205 posts quoted on this page

Records read up to 2026-10-02, 00:00 UTC. Live figures carry their own capture time.

Read the story

The numbers, each with what must be said beside it

@_kate_lv

153

opposite pairs

Times two accounts of the group around @_kate_lv held opposite outcomes of one market in matching size, 2024-09-26 to 2026-09-28.

Also true

  • The handle described the two-account method in public in 2025; what the record adds is how often and with which accounts.
  • No two accounts share an owner key; 27 pairs sit only on accounts with other owner keys, which may be other people.
  • The legs were filled by other traders, not against each other.
  • 12 pairs win either way and 32 ended with a gain; the 75 % size rule is a choice made for this count (a strict screen gives 42).
How it is counted

Two positions of two of the 21 accounts on opposite outcomes of one market, share counts within 75 % of each other, both open at the same time; 2024-09-26 to 2026-09-28. Same-wallet pairs (12) not included.

As of 1 Oct 2026, 00:00 UTC

@_kate_lv

95 of 149

posted positions with the other side in the group

Positions @_kate_lv posted between 2025-10-25 and 2026-09-30 whose other outcome another account of the group, or the same wallet, bought.

Also true

  • 54 posted positions had no such pair.
  • The handle spoke of a hedge in 5 of the 95 posts and described the method in public in 2025.
  • For heooo, butzki and gracechase the tie is money between keys and the matched trades; two or more people acting together are not excluded.
How it is counted

Positions @_kate_lv posted 2025-10-25 to 2026-09-30 (combination bets left out) whose other outcome was first bought within 24 hours by another account of the group or the same wallet, share count between half and double.

As of 30 Sep 2026, 00:00 UTC

@gusik4ever

-$5,349.53

result of @gusik4ever’s six wallets

After fees, up to 2026-10-01 19:00 UTC, on 235,184.05 dollars of buys.

Also true

  • The handle said in words more than once that it loses, and Polymarket’s profit figure for its visible profile shows the loss publicly.
  • Two-sided betting between its accounts was tested and not found.
  • The figure includes the owner key’s +50.20; the five accounts whose results it posted account for -5,399.72 of it.
How it is counted

Result after fees of every position of the six wallets (lolxdkek, its owner key, lostnpeace, iluvdubnation, the Bagel wallet 0xf595d7f0dcf9cb1b39c420b6f041c19b89f7fd9e (opens in a new tab) and the Polysights-card wallet 0xfc1d517912d1e87cf1902a40be737c00b88a5ac4 (opens in a new tab)), from their first trade to the cut-off, rebuilt from fills and on-chain resolutions; unredeemed losers at zero; includes the 4.92 loss resolved at 2026-10-01 12:14:42 UTC.

As of 1 Oct 2026, 19:00 UTC

@gusik4ever

5 of 959

losing positions in @gusik4ever’s result images

Against 959 positions its five posted accounts closed with a loss.

Also true

  • Its Telegram channel once showed a large loss with its figure; what was not posted on X is the amounts.
  • The count depends on the reading of the images (172 to 186 winners) and on the images kept in the record.
  • Posting wins more often than losses is a common habit; the count states the pattern, not an intent.
How it is counted

Losing positions of the five accounts that appear in images the handle posted on X after the result (32.76 dollars together).

As of 1 Oct 2026, 19:00 UTC

@0xBumblebee

-$8,329.34

result of Uiom, @0xBumblebee’s unshown second account

Funded from the visible profile; no post of the handle shows its trades.

Also true

  • The handle posted its losses in aggregate many times; what it did not show is this account and the size of its loss.
  • It posted a market link carrying the referral name r=Uiom on 2026-05-29, and Uiom’s profile is public.
  • Two-sided betting between its accounts was tested and not found.
How it is counted

Uiom (0x88e8875b0319a46e7c277d266a2362543b6c90dc (opens in a new tab)), 109 fills 2026-04-03 to 2026-05-29, by collateral moved; Polymarket’s own figure -8,324.87.

As of 1 Oct 2026, 00:00 UTC

@itskkoma

$30,362.66

on one outcome when @itskkoma posted a $700 card

2026-07-05: 709.48 on the public profile, 29,653.18 on an account the handle had not named.

Also true

  • Both accounts were on the same side: this is not a hedge.
  • The handle did not present the win as its result; it wrote ‘Looks like this over will not happen’ before the large block was sold.
  • It is one night, not a standing practice, and the handle said in public that it has ‘Like 7’ accounts.
How it is counted

Stake on the same outcome across the public profile (709.48) and nononononoononono (29,653.18) at the time of the post of 2026-07-05 19:52:12 UTC. Both matches of the night together: 100,624.71 (0.71% on the public profile).

As of 5 Jul 2026, 00:00 UTC

@itskkoma

8% vs 23%

of @itskkoma’s losing positions posted with figures

Against about 23% of its winners, over the six accounts whose plays it posted.

Also true

  • The handle stated losses in words, for example ‘Lost about 4.5k today’ (2026-06-10).
  • A result card exists only for a win, so posts made after the result lean towards wins.
  • The calls a reader could have followed at entry time won more often than the book as a whole.
How it is counted

Losing positions of the six posted accounts posted with figures: 54 to 57 of 696.

As of 1 Oct 2026, 00:00 UTC

The platform and the apps

2,900 USDT0

from DG3’s affiliate wallet to four handles

@_kate_lv 350, @0xBumblebee 800, @gusik4ever’s exchange address 850, the @vadim_kesha1 side 900; 2026-05-29 to 2026-09-29.

Also true

  • What a payment was for is not on chain, and being paid by an app is ordinary.
  • The links in the DG3 posts carry DG3’s own affiliate tag, and DG3 publishes an affiliate programme; a fixed fee and a per-referral payout cannot be told apart.
  • X’s label can be read only for posts from 2026-08-09; the June launch posts are older. @vadim_kesha1 labelled 3 of its 7 DG3 posts since that date.
  • For @gusik4ever and @vadim_kesha1 the paid address is where the profile sends its money; who holds it is not shown.
How it is counted

Whole-sum transfers of 0x39861ad41e6e4c43ed8c3423be5ef6faf91a3f84 (opens in a new tab) to the owner keys of the katelv and 0xBumblebee profiles, the exchange deposit address the lolxdkek profile withdraws to and an address the CryptoKesha profile withdraws to.

As of 2 Oct 2026, 00:00 UTC

The platform and the apps

$5,072.98

from Firefly-attributed wallets towards three handles

@_kate_lv 4,047.98, @gusik4ever’s exchange address 850, @0xBumblebee 175; the @vadim_kesha1 side received 350 more.

Also true

  • What the payments were for is not on chain; Firefly publicly offers rewards for sharing its events.
  • @_kate_lv’s 4,047.98 includes 347.98 of published prizes; the forwarding wallet’s 4,532.40 is the same money path and is not added.
  • @_kate_lv said on 2026-07-20 that it traded its Firefly wallet ‘while doing some paid deals’, and its Firefly post of 2026-08-20 carries X’s label.
  • Firefly’s paying wallets are attributed with grade strong, not proven.
How it is counted

Firefly wallets towards @_kate_lv (4,047.98: 1,500 to the owner key, 2,200.01 to the forwarding wallet, 347.98 prizes), the exchange address of @gusik4ever (850 through a pass-through wallet) and the owner key of the 0xBumblebee profile (175); not to be added to the forwarding wallet’s 4,532.40

As of 2 Oct 2026, 00:00 UTC

The platform and the apps

7

days the two Bagel accounts got paired exchange transfers

Six Mondays from 2026-07-06 to 2026-08-10 and 2026-10-01, minutes apart; the sender is not known.

Also true

  • Every transfer came from a Binance-labelled hot wallet; whose exchange account sent them is not known.
  • The holders’ own withdrawals and a weekly payment by a third party would leave the same record; that Bagel sent them is a reading without a receipt.
  • An exchange hot wallet serves every customer and connects nobody by itself.
How it is counted

days on which both deposit addresses received an exchange transfer less than 6 minutes apart: six Mondays 2026-07-06 to 2026-08-10 and Thursday 2026-10-01; the first week (2026-06-29/30) is not paired

As of 2 Oct 2026, 00:00 UTC

@vadim_kesha1

3 of 7

of @vadim_kesha1’s seven DG3 posts since 2026-08-09 carry X’s paid label

The unlabelled post of 2026-09-02 went out 52 minutes after 250 USDT0 from DG3’s wallet.

Also true

  • The label is the author’s own switch; an unmarked post may be one the handle did not count as part of a deal.
  • What a transfer was for is not on chain; DG3 announced a 50-dollar-per-referral programme on 2026-08-20.
  • The handle wrote ‘rule of the game: when unsure, add paid partnership’ (2026-03-05).
How it is counted

Own DG3 posts of @vadim_kesha1 since 2026-08-09 (when the label becomes readable): labelled 2026-09-16, 09-17, 09-23; not labelled 09-02, 09-07, 09-10, 09-25 (nor the link reply under 09-07).

As of 1 Oct 2026, 00:00 UTC

@aenews

$494,360.09

bought by @aenews’s accounts after its wallet’s own proposals

In 67 of 403 proposals, inside the two-hour challenge window.

Also true

  • Proposing is open to anyone and carries a bond; the oracle, not the proposer, decides a disputed outcome.
  • 45 of the 67 cases, about 394,000 of the 494,000 dollars, were bought at an average of 95c or more, when the outcome was already treated as settled.
  • That the wallet is the handle’s rests on money in both directions and the handle’s own words; the key that signs for aenews2 is a different key.
How it is counted

Buys by aenews2 or aenews-915 of the outcome the wallet had proposed, inside the two-hour challenge window, over 67 proposals; aenews2 alone 455,305.27 over 59.

As of 1 Oct 2026, 00:00 UTC

The posts showed one account or one side at a time. The public record shows further accounts behind them, for one handle’s group the other side of most posted positions, losses the result posts left out, and wallets of the apps the handles promoted sending whole sums around those posts; it shows no single paymaster behind them.

For 95 of the 149 positions @_kate_lv posted between 2025-10-25 and 2026-09-30, another account of the same group, or the same wallet, bought the other outcome of the same market in a matching share count, a median 158 seconds apart.

Also true

  • 54 posted positions had no such pair.
  • The handle described the two-account method in public in 2025 and spoke of a hedge in 5 of the 95 posts.
  • All accounts have different owner keys; two or more people acting together are not excluded.
  • Two-sided betting was tested and not found for @itskkoma, @gusik4ever and @0xBumblebee.

On 2026-07-05 @itskkoma posted a $700 card from the public profile it had published the night before, while 29,653.18 dollars on the same outcome had been bought 57 minutes earlier on an account it had not named.

Also true

  • Both accounts were on the same side: this is not a hedge.
  • The handle did not present the win as its result; it wrote ‘Looks like this over will not happen’ before the large block was sold.
  • It is one night, not a standing practice, and the handle said in public that it has ‘Like 7’ accounts.

The result images @gusik4ever posted show 172 to 186 winning positions and 5 losing ones; up to 2026-10-01 its six wallets lost 5,349.53 dollars.

Also true

  • The handle said in words more than once that it loses, and its visible profile shows its loss publicly.
  • Two-sided betting between its accounts was tested and not found.

@0xBumblebee’s visible profile sent 6,471.16 dollars to a second account, Uiom, which ended at -8,329.34 dollars; no post of the handle shows its trades.

Also true

  • The handle posted its losses in aggregate many times; what it did not show is this account and the size of its loss.
  • On 2026-05-29 it posted a market link carrying the referral name r=Uiom, and Uiom’s profile is public.

DG3’s affiliate wallet and wallets attributed to Firefly sent whole sums to addresses tied to four of the handles around posts that promoted the two apps; the post texts carry no words saying that the app paid.

Also true

  • What a payment was for is not on chain, and being paid by an app is ordinary.
  • The links in the DG3 posts are affiliate-tagged by DG3 itself, and Firefly publicly rewards sharing.
  • X’s paid-partnership label can be read only for posts from 2026-08-09; the launch posts of June 2026 are older.
  • @_kate_lv says openly that it takes paid deals and has set X’s paid-partnership label on its posts since August 2026.

The money comes from Polymarket’s published programmes and from separate apps whose wallets never paid each other: the record shows no single paymaster.

Also true

  • What connects the sources is a shared list of payees and Polymarket’s builder incentive, not a common wallet.
  • The sender of the paired weekly transfers into two Bagel accounts is not known.

How the money moves

The money cycle

Polymarket pays the apps that route orders to it; the apps pay their own users and some handles; the handles’ links earn a small share of fees. Arrow by arrow, with what is published, what is on chain and what is inferred.

Polymarket pays the apps that route orders to it: a weekly reward pool split by the volume each app routes, and the fees each app charges its own users, passed on the next day. Published programme; the payments are on chain.

Wallets attributed to DG3 and Firefly (and PolyHelper) sent whole sums to addresses tied to the handles, around posts that promote the app. What a payment was for is not on chain.

Each handle is tied to one or more trading accounts: some it showed or declared itself, others only by money.

The handles post picks, slips, links and referral codes to their followers. A referral earns a small share of fees; the record does not name who followed a call or signed up.

Also true

  • There is no single paymaster: the wallets of different apps never paid each other.
  • Programme income and app pay are not misconduct by themselves.
  • The sender of the paired weekly transfers into two Bagel accounts is not known.
  1. 1Polymarket Apps

    Weekly reward pool and fees

    1,025,009.37 USDC.e in 44 weekly rounds · 9 Nov 2025 to 15 Sep 2026

    • 1,025,009.37 USDC.e weekly builder rewards, 44 rounds to 150 wallets, 2025-11-09 to 2026-09-15
    • 3,820,634.67 PUSD apps’ own fees passed on daily, 157 batches to 537 wallets, 2026-04-29 to 2026-10-01

    Polymarket pays the apps that route orders to it: a weekly reward pool split by the volume each app routes, and the fees each app charges its own users, passed on the next day. Published programme; the payments are on chain.

    Published programme Published programme: Polymarket publishes weekly rewards by routed volume and a builder fee each app sets for its own users; it does not publish the weekly pool or the formula. The payments are chain facts: 44 weekly rounds from Polymarket’s programme wallets and daily fee batches, read from the chain; that these wallets pay the Builders Program is graded strong.

    Also true

    • A published offer is not a payment; Polymarket publishes neither the weekly pool nor the formula.
    • Builder ‘volume’ counts shares, both sides of a trade, a one-cent share like a dollar share.
  2. 2Apps The handles

    Whole sums to handles

    30 Apr 2026 to 29 Sep 2026

    • 2,900 USDT0 DG3’s affiliate wallet to addresses tied to @_kate_lv (350), @0xBumblebee (800), @gusik4ever (850) and @vadim_kesha1 (900), 2026-05-29 to 2026-09-29
    • $5,072.98 in USDC and PUSD Firefly-attributed wallets towards @_kate_lv (4,047.98, of it 347.98 published prizes), @gusik4ever (850) and @0xBumblebee (175), 2026-04-30 to 2026-08-20
    • $350 Firefly-attributed wallets to the @vadim_kesha1 side (170 USDT0 and 180 USDC), 2026-06-11 and 2026-06-14
    • 650 USDC PolyHelper’s builder profile and owner key to the exchange address @gusik4ever’s profile withdraws to, 2026-07-06 and 2026-07-19

    Wallets attributed to DG3 and Firefly (and PolyHelper) sent whole sums to addresses tied to the handles, around posts that promote the app. What a payment was for is not on chain.

    Chain fact Chain fact: every transfer is on chain between identified addresses. That the paying wallets are the apps’ is graded on its own: DG3’s affiliate wallet proven, PolyHelper’s builder profile and its owner key proven, Firefly’s loader and hub strong. What any payment was for is an inference, not on chain.

    Also true

    • What a payment was for is not on chain, and being paid by an app is ordinary.
    • The sums do not follow the handles’ trading through the apps.
    • That a paying wallet is the app’s is graded: DG3 proven, Firefly strong.
  3. 3The handles Accounts tied to the handles

    The accounts behind a handle

    • 21 @_kate_lv: trading accounts tied to its profile by money (1 visible profile, 11 staked by its declared wallet or key, 9 with other owner keys)
    • 10 @_kate_lv: accounts whose fills equal slips or cards the handle posted
    • 9 @itskkoma: wallets that traded behind its record
    • 7 @itskkoma: of these, tied by the handle’s own posts (it said it has ‘Like 7’ accounts)
    • 6 @gusik4ever: wallets of its book
    • 5 @gusik4ever: linked or shown by the handle, or behind its posted slips and cards
    • 9 @0xBumblebee: trading addresses tied to the handle
    • 8 @0xBumblebee: by owner keys it posted or app accounts it showed

    Each handle is tied to one or more trading accounts: some it showed or declared itself, others only by money.

    Inference strong indication The ties are of two kinds: the handles’ own posts (a profile that names the handle, keys and wallets the handle posted as its own, slips that equal fills) and money on chain (stakes, withdrawals, transfers between keys). Ties by money alone are graded and may be other people’s accounts.

    Also true

    • Funded is not controlled: no two accounts share an owner key, and accounts tied only by money may be other people’s.
    • Several handles told their audience that they use more than one account.
  4. 4The handles Followers

    Posts, links and codes

    2,273.48 PUSD of referral rewards

    • 1,033.47 PUSD referral rewards to the accounts tied to @itskkoma
    • 894.51 PUSD referral rewards to the accounts tied to @0xBumblebee
    • 193.54 PUSD referral rewards to the accounts tied to @_kate_lv
    • 151.96 PUSD referral rewards to the accounts tied to @gusik4ever

    The handles post picks, slips, links and referral codes to their followers. A referral earns a small share of fees; the record does not name who followed a call or signed up.

    Published programme Published programme: Polymarket’s referral programme pays a referrer a share of the referred account’s fees. The reward transfers are chain facts; which referred account a reward came from is matched from the fee logs.

    Also true

    • Most of it, 1,732.95 of the 2,273.48 PUSD, was a share of fees paid by the handles’ own further accounts; at most 540.53 came from other people.
    • The record does not name who followed a call or signed up through a link; no sum is stated as a follower’s loss.
    • Referral rewards are a published programme: receiving them is ordinary.

The cast

Who is on this page, and which accounts the record ties to them

Seven handles on X: @_kate_lv, @itskkoma, @gusik4ever, @0xBumblebee, @vadim_kesha1, @0xd1namit, @aenews. For each: the label or badge it carries, the accounts and addresses the record ties to it, how each tie is established, and what must be said in its favour.

shown or named by the handlenot shown by the handlea wallet of an app or of the platform

@_kate_lv

Xthe account (opens in a new tab)
Posts, as the account states
91,218 as of 1 Oct 2026, 11:40 UTC
Affiliation label on X
Polymarket Sports (@PolymarketSport) dates not on record; read in copies of the account

X showed the label “Polymarket Sports” on the account in readings from 2026-10-01 to 2026-10-01. When it was first set is not on record here.

Polymarket profile fields
verified badge: yescreator flag: not on recordcommunity moderator flag: not on record as of 1 Oct 2026. These are Polymarket’s own profile fields; the record does not say what they entitle.

What the record shows

@_kate_lv posts trades from the wallets of many apps and tells its readers that it takes paid deals. The record ties 21 trading accounts to its profile in three tiers; 153 times two of them held opposite outcomes of one market in matching size, and for 95 of the 149 positions the handle posted, the other outcome sat in another account of the group or in the same wallet. The handle described the two-account method in public in 2025 and has set X’s paid-partnership label on its posts since August 2026.

Also true

  • The handle described the two-account method in public in 2025 and wrote of hedging its own trades.
  • It says openly that it takes paid deals, and since 2026-08-09 it has set X’s paid-partnership label on its Bagel posts and its Firefly post of 2026-08-20.
  • It listed five wallets as its own on 2026-07-20, losing ones included.
  • No two accounts share an owner key; heooo, butzki, gracechase and the small accounts may be other people.
  • The legs were filled by other traders; deleting losing calls was tested and not found.

What must be said in its favour

11 accounts and addresses tied to the handle, and how each tie is established

Read the chapter on @_kate_lv

@itskkoma

Xthe account (opens in a new tab)
Posts, as the account states
42,698 as of 1 Oct 2026, 22:24 UTC
Affiliation label on X
Polymarket Sports (@PolymarketSport) dates not on record; read in copies of the account

X showed the label “Polymarket Sports” on the account in readings from 2026-10-01 to 2026-10-01. When it was first set is not on record here.

What the record shows

@itskkoma linked one Polymarket profile from 2026-07-04; nine wallets traded behind its record, seven tied to it by its own posts. The plays it posted came from accounts used one after another, and on 2026-07-05 it posted a $700 card while 29,653.18 dollars on the same outcome sat on an account it had not named. Two-sided betting between its accounts was tested and not found, and it told readers that it has several accounts.

Also true

  • Two-sided betting between its accounts was tested and not found.
  • It said in public that it has several accounts (‘Like 7’) and announced each change of account.
  • On 2026-07-05 it did not present the win as its result, and that night is not a standing practice.
  • Its July totals match all its wallets, losing ones included.
  • DG3’s payments into its accounts are published rebates, which the handle told readers it collects.

What must be said in its favour

7 accounts and addresses tied to the handle, and how each tie is established

Read the chapter on @itskkoma

@gusik4ever

Xthe account (opens in a new tab)
Posts, as the account states
62,689 as of 1 Oct 2026, 22:24 UTC
Affiliation label on X
Polymarket Sports (@PolymarketSport) dates not on record; read in copies of the account

X showed the label “Polymarket Sports” on the account in readings from 2026-10-01 to 2026-10-01. When it was first set is not on record here.

Polymarket profile fields
verified badge: nocreator flag: not on recordcommunity moderator flag: not on record as of 1 Oct 2026. These are Polymarket’s own profile fields; the record does not say what they entitle.

What the record shows

@gusik4ever posted result images showing 172 to 186 winning positions and 5 losing ones while its six wallets lost 5,349.53 dollars; on 2026-04-07 it posted its own visible profile’s figures as a friend’s account. Wallets attributed to Firefly, DG3 and PolyHelper paid the exchange address its accounts cash out to around posts praising each app that say nothing of payment. The handle said in public that it has a second account, that it loses, and that it is a Polymarket affiliate; two-sided betting between its accounts was tested and not found.

Also true

  • It said in public that it has a second account, that it is a Polymarket affiliate and Sports Community Lead, and that it loses.
  • Two-sided betting between its accounts was tested and not found, and so was deleting losing calls.
  • What the app payments were for is not on chain; the codes and links in its posts showed a commercial tie, not a payment.
  • Its posts about Firefly, DG3 and PolyHelper predate 2026-08-09, so whether X’s label was set cannot be read.

What must be said in its favour

5 accounts and addresses tied to the handle, and how each tie is established

Read the chapter on @gusik4ever

@0xBumblebee

Xthe account (opens in a new tab)
Posts, as the account states
89,467 as of 1 Oct 2026, 11:40 UTC
Polymarket profile fields
verified badge: nocreator flag: not on recordcommunity moderator flag: not on record as of 1 Oct 2026. These are Polymarket’s own profile fields; the record does not say what they entitle.

What the record shows

@0xBumblebee posted its losses in aggregate many times and told readers in general terms that its X account was paid. A second account funded from its visible profile, Uiom, lost 8,329.34 dollars without any post showing its trades, and DG3’s affiliate wallet sent 800 USDT0 to the key it posts as its own while it published DG3 promotions that carry no words of disclosure. Two-sided betting between its accounts and offsetting slips on other apps were tested and not found.

Also true

  • It posted its losses in aggregate many times and told readers in general terms that its X account was paid.
  • Two-sided betting between its accounts and offsetting slips on other apps were tested and not found.
  • What the DG3 and Firefly payments were for is not on chain; its DG3 posts carry its own code.
  • One paymaster is not supported: two app wallets and several unidentified payers paid it.

What must be said in its favour

10 accounts and addresses tied to the handle, and how each tie is established

Read the chapter on @0xBumblebee

@vadim_kesha1

Xthe account (opens in a new tab)
Posts, as the account states
12,368 as of 1 Oct 2026, 22:24 UTC
Affiliation label on X
Polymarket Sports (@PolymarketSport) dates not on record; read in copies of the account

X showed the label “Polymarket Sports” on the account in readings from 2026-10-01 to 2026-10-01. When it was first set is not on record here.

Polymarket profile fields
verified badge: nocreator flag: not on recordcommunity moderator flag: not on record as of 1 Oct 2026. These are Polymarket’s own profile fields; the record does not say what they entitle.

What the record shows

@vadim_kesha1 presents a 3,098-dollar FaZe bet as the start of its Polymarket journey; the profile was funded 83 seconds after creation from an earlier account that stood at -4,975.63. DG3 and Firefly wallets paid 1,250 dollars to an address of its account’s cluster while it promoted both apps with its own links; it set X’s paid-partnership label on three of its seven DG3 posts since 2026-08-09 and not on four. Two DG3 ‘ORDER FILLED’ cards it posted have no fill behind them. Two-sided betting was tested and not found.

Also true

  • The FaZe bet and its result are real; the earlier account is public under the alias the handle uses.
  • It wrote ‘when unsure, add paid partnership’ and labelled three of its DG3 posts.
  • Two-sided betting was tested and not found; CryptoKesha is not a leg of another handle’s pairs.
  • Whether DG3’s app showed ‘ORDER FILLED’ for orders that did not execute cannot be told from the record.

What must be said in its favour

1 account or address tied to the handle, and how each tie is established

Read the chapter on @vadim_kesha1

@0xd1namit

Xthe account (opens in a new tab)
Posts, as the account states
9,617 as of 1 Oct 2026, 11:40 UTC
Affiliation label on X
Polymarket Traders (@PolymarketTrade) dates not on record; read in copies of the account

X showed the label “Polymarket Traders” on the account in readings from 2026-04-17 to 2026-10-01. When it was first set is not on record here.

Polymarket profile fields
verified badge: nocreator flag: not on recordcommunity moderator flag: not on record as of 1 Oct 2026. These are Polymarket’s own profile fields; the record does not say what they entitle.

What the record shows

@0xd1namit builds PolyHelper and has said so in public since January 2026; it told readers in 2025 that it is a Polymarket affiliate, from March 2026 added notes to some threads that its link posts are sponsored, and since 2026-08-09 has set X’s paid-partnership label on most posts that carry its link. PolyHelper money reached the exchange address used by @gusik4ever’s profile hours before two livestreams during which @0xd1namit posted that @gusik4ever was using PolyHelper; what the money was for is not on chain.

Also true

  • It has said in public since January 2026 that it builds PolyHelper, and since 2025 that it is a Polymarket affiliate.
  • What PolyHelper’s 650 dollars were for is not on chain; part may be prize money for the streams, which were not examined.
  • Two-sided betting was tested and not found.

What must be said in its favour

1 account or address tied to the handle, and how each tie is established

Read the chapter on @0xd1namit

@aenews

Xthe account (opens in a new tab)
Posts, as the account states
469 as of 1 Oct 2026, 20:36 UTC
Affiliation label on X
Polymarket Traders (@PolymarketTrade) dates not on record; read in copies of the account

X showed the label “Polymarket Traders” on the account in readings from 2026-10-01 to 2026-10-01. When it was first set is not on record here.

Polymarket profile fields
verified badge: nocreator flag: not on recordcommunity moderator flag: not on record as of 1 Oct 2026. These are Polymarket’s own profile fields; the record does not say what they entitle.

What the record shows

A wallet that exchanges money with the aenews2 account in both directions filed 403 outcome proposals on the oracles that resolve Polymarket’s markets; in 67 of them an account of @aenews bought the proposed outcome inside the two-hour challenge window, for 494,360.09 dollars. Proposing is open to anyone, most of that buying was at prices that already treated the outcome as settled, and the handle has said in public that it disputes.

Also true

  • Proposing is open to anyone and carries a bond; the oracle, not the proposer, decides a disputed outcome.
  • 45 of the 67 cases, about 394,000 of the 494,000 dollars, were bought at an average of 95c or more, when the outcome was already treated as settled.
  • That the wallet is the handle’s rests on money in both directions and the handle’s own words; the key that signs for aenews2 is a different key.

What must be said in its favour

  • Proposing is open to anyone and carries a bond; a proposer who holds a position has every reason to propose the true outcome, and the oracle, not the proposer, decides a disputed one.
  • It is the handle’s own account of one episode four years ago, with an apology, an offer to reimburse and a donation to a union fund.
  • When each post was removed is not known: every removal was first seen on 2026-10-01.
3 accounts and addresses tied to the handle, and how each tie is established

Read the chapter on @aenews


The story

What was posted, and what the accounts did

Seven handles, one chapter each, then the chapters that concern them all. 270 dated events: what was posted, set next to what the accounts did, with what must be said in each handle’s favour. Every event links to its records.

Loading the story…


Shown versus the record

What the audience saw, next to what the accounts did

For each handle, the figure its followers were shown and the same figure from the record of the accounts, on one scale. Where the figure shown is true for the account shown, the text beside it says so first.

@_kate_lv

@_kate_lv: what was shown and what the record holds

The chapter on @_kate_lv

profit curve

What the audience saw

+$6,818.71 (the handle: ‘publicly made 7k profit’)

profit of the visible profile the handle cited

as of 26 Dec 2025

Also true

  • The profit is real for that profile, the leaderboard states it correctly, and the handle told readers to track it (‘i usually post my main bets and u can always track my polymarket page’, 2025-12-26).
  • Which leg of a pair wins cannot be chosen in advance: the katelv leg was the dearer one in 32 of 65 pairs and won 38, within what chance gives, so the record does not show that wins were steered to the visible profile.
  • The four profiles have four different owner keys; butzki and gracechase never appear in the handle’s posts; heooo’s owner key was given as a wallet by the handle once and by a second X handle 16 times. That the opposite legs belong to the same purse rests on the money links (transfers between the keys in both directions, $17,906.32 between the heooo and katelv keys and wallets; a common exchange deposit address; the run of remainder transfers of 2026-03-05) and, for heooo, on the handle’s own words; it is an inference, not a key. A group of people who pool money would leave the same record.
  • Not every loss of the three profiles is the other side of a katelv position (for heooo the pairs are 27.5 % of its positions).
  • The handle reported losses in public (‘had over 10k all time high pnl and was on a loosing break’, 2026-01-30; ‘i just lost a big ass $1800 trade’, 2026-08-02) and showed seven negative profit widgets.
  • When the copy invitation of April 2026 was posted, none of the 18 positions posted in those months was paired; the profit it advertises was made in the paired months. The handle had described the two-account volume method in a public reply on 2025-10-16.
  • The group result over the whole history (21 accounts) differs in definition from the 2025-10-25 to 2026-09-30 figures of stated separately (twelve accounts); the two are kept apart. Curve points are daily values at 00:00 UTC.
How both figures are counted

Sum of Polymarket profit curves of katelv, heooo, gracechase and butzki at 2025-12-26 00:00 UTC.

stated profit

Also true

  • The handle said ‘five wallets’, listed two losing ones, and had shown the Tailgate account’s stats card on 2026-06-25; the Tailgate account’s last World Cup trade was on 2026-06-26, three weeks before the tally.
  • With the tool’s own figures the total stays positive even with the Tailgate account (about +$275 including the $300 prize). The tool’s method is not published; for the Bagel wallet it shows -$210.34 where the fills give -$633.18, a gap of $422.84 that fees do not explain; the other four cards agree with the fills within $53.
  • The handle’s earlier statements (‘i believe i just crossed $2,000 in profits trading the world cup’, 2026-07-03; ‘around $2,5-$3k’, 2026-07-13) match no combination of the identified accounts (those in profit sum to +$1,151.41 and +$1,051.35) but cannot be shown false: the handle named a wallet that is not identified (‘vision wallet’, 2026-07-22).
  • 1,000 USDC of the Firefly stake came from Firefly’s hub wallet on 2026-07-03 and the $300 from Firefly’s prize wallet; the $300 is part of the 347.98 PUSD of prizes separately and is not counted twice.
  • The same post says the handle was ‘doing some paid deals’ while trading these wallets.
How both figures are counted

Fills and resolutions of all identified accounts in World Cup markets to 2026-07-20, before the $300 prize ($33,310.59 bought); the five listed wallets alone +$197.13.

@itskkoma

@itskkoma: what was shown and what the record holds

The chapter on @itskkoma

stake

What the audience saw

$700 card (fill 709.48)

stake shown on the night of 2026-07-05

as of 5 Jul 2026

Also true

  • Both accounts were on the same side (Over): this is not a hedge, and no fill between them exists.
  • The handle did not present the small win as its result: five minutes before the large block was sold it told its readers ‘Looks like this over will not happen’ (20:52:45 UTC), and it posted no result of a bet on either match.
  • What the post showed was the size: the $700 card was a real position, and the post did not say it was the whole stake.
  • It is one night, not a standing practice: after 2026-07-05 the only positions found on the other accounts are two of $10.00 (2026-07-24) and one of $227.07 (2026-08-20), plus 1,831.67 dollars of buys on the app wallet on 2026-09-26 and 2026-09-27, while the public profile bought for 203,167.01 dollars up to 2026-09-28.
  • From the moment the public profile record existed the other wallets opened 8 positions costing 102,016.55 (result +16,943.22); one more, 10,008.41 on ‘Paraguay vs. France: O/U 1.5’, was opened and lost in the hour before the profile record was created.
  • Two days later (2026-07-07) the handle wrote of its results ‘around the same across multiple accounts net net’, and on 2026-07-11 that it has ‘Like 7’ accounts.
  • ‘-.-x’ has its own owner key (0x7de5ea7dd428cbc1df8680b45c9fbdcb7c2e1879 (opens in a new tab)) and no image of it was ever posted; it is tied to the handle by the money route only: funded only from the public profile, winnings withdrawn to the key the handle had linked as ‘My collection’ on 2024-06-24, 89,171.42 paid from that key into the public profile 42 minutes later, and its last 60.00 sent to the same key on 2026-09-28.
  • Splitting a stake across accounts has ordinary reasons (size on a watched profile, order size, rebates per wallet); the handle had said it did not want copy traders, and the large order carried DG3’s builder code on the wallet DG3’s public table lists under the username itskkoma2.
  • The card is read from the image of the post of 19:52:12 UTC (‘itskkoma / Over / Cost $700 / Odds 57% / To win $1,229’); the post text itself names no stake.
How both figures are counted

Stake on the same outcome across the public profile (709.48) and nononononoononono (29,653.18) at the time of the post of 2026-07-05 19:52:12 UTC. Both matches of the night together: 100,624.71 (0.71% on the public profile).

@gusik4ever

@gusik4ever: what was shown and what the record holds

The chapter on @gusik4ever

count

Also true

  • The handle said in words that it loses, more than once: ‘this is my main account, and yeah, it’s in the red right now’ (2025-11-11, when the linked profile stood at about -72 dollars), ‘of course i’ve had losing picks too ... i’ve had to rebuild my deposit twice’ (2026-01-26), ‘i blew up twice’ (2026-01-27), ‘I post a lot of screenshots with profits, but that’s only the tip of the iceberg ... plenty of losses along the way’ (2026-07-19).
  • Its Telegram channel marked missed picks with crosses and once showed a large loss with its figure while the position was open (Travaglia at -424.09 on 2026-05-04; it ended at -539.44). What was not posted on X is the amounts.
  • No deleted losing slip was found (see the deleted-posts entry).
  • The visible profile shows its loss: Polymarket’s profit figure for lolxdkek is -3,205.29, public on its profile.
  • ‘≈ $700’ is the before-fee figure the Bagel app shows (see the Bagel-figures entry).
  • The statements about the ‘new acc’ were true or close when made: Polymarket’s profit series for iluvdubnation reads +1,357.96 at the post of 2026-05-01 (‘$1,000+ in 8 days’) and +1,510.73 at the reply of 2026-04-28 (‘+$2k for now’; the series had peaked at +2,169.64 the evening before); the account ended at -724.20.
  • The closed-positions list of lostnpeace and iluvdubnation sums to +4,413.95 and +2,419.83 because Polymarket leaves unredeemed losers out of that list for every account; nobody is shown to have cited it.
  • The count of shown positions depends on the reading of the images (172 to 186 winners) and on the images kept in the record (90% of the handle’s posts are in the table). Polymarket’s profit chart leaves fees out and sums to about -4,350 for the five accounts (chart values read on 2026-10-02, not a rebuilt result).
  • Posting wins more often than losses is a common habit; the entry states the pattern, not an intent.
  • The figures include a 4.92-dollar position of the Bagel wallet that resolved as a loss at 2026-10-01 12:14:42 UTC, before the cut-off; one position (cost 5.18) was still open.
How both figures are counted

Closed positions with a loss of the five accounts whose results the handle posted, from the first trade to the cut-off (1,066 closed with a gain).

profit

Also true

  • The handle said in words that it loses, more than once: ‘this is my main account, and yeah, it’s in the red right now’ (2025-11-11, when the linked profile stood at about -72 dollars), ‘of course i’ve had losing picks too ... i’ve had to rebuild my deposit twice’ (2026-01-26), ‘i blew up twice’ (2026-01-27), ‘I post a lot of screenshots with profits, but that’s only the tip of the iceberg ... plenty of losses along the way’ (2026-07-19).
  • Its Telegram channel marked missed picks with crosses and once showed a large loss with its figure while the position was open (Travaglia at -424.09 on 2026-05-04; it ended at -539.44). What was not posted on X is the amounts.
  • No deleted losing slip was found (see the deleted-posts entry).
  • The visible profile shows its loss: Polymarket’s profit figure for lolxdkek is -3,205.29, public on its profile.
  • ‘≈ $700’ is the before-fee figure the Bagel app shows (see the Bagel-figures entry).
  • The statements about the ‘new acc’ were true or close when made: Polymarket’s profit series for iluvdubnation reads +1,357.96 at the post of 2026-05-01 (‘$1,000+ in 8 days’) and +1,510.73 at the reply of 2026-04-28 (‘+$2k for now’; the series had peaked at +2,169.64 the evening before); the account ended at -724.20.
  • The closed-positions list of lostnpeace and iluvdubnation sums to +4,413.95 and +2,419.83 because Polymarket leaves unredeemed losers out of that list for every account; nobody is shown to have cited it.
  • The count of shown positions depends on the reading of the images (172 to 186 winners) and on the images kept in the record (90% of the handle’s posts are in the table). Polymarket’s profit chart leaves fees out and sums to about -4,350 for the five accounts (chart values read on 2026-10-02, not a rebuilt result).
  • Posting wins more often than losses is a common habit; the entry states the pattern, not an intent.
  • The figures include a 4.92-dollar position of the Bagel wallet that resolved as a loss at 2026-10-01 12:14:42 UTC, before the cut-off; one position (cost 5.18) was still open.
How both figures are counted

Result after fees of the Bagel wallet 0xf595d7f0dcf9cb1b39c420b6f041c19b89f7fd9e (opens in a new tab) at the time of that post (+692.02 before fees); its 164 positions of 11 dollars or less had lost 79.00 and its 58 positions above 100 dollars had made 340.33.

profit

Also true

  • The channel did show one of the two losses of 4 May: a photo of the Travaglia position at -$424.09 with the words ‘a good reminder to manage your size more carefully’, fourteen minutes after a message ‘sold Travaglia’.
  • The withdrawal on the screenshot of 4 May (3,002.00) was real, made on 2026-04-27, when the account had paid out 397.97 more than had been paid in; so ‘withdrew with profit’ was true of the week before. ‘Keep just $150’ matches no balance: the account held 0.10 dollars and received 1,035.13 the next morning.
  • Those channel messages had 100 to 120 views. The record does not show who followed a pick; no loss of a follower is stated.
  • The Sinner post of 2026-04-28 (‘I placed $10,675 to win $156 ... It feels like a free money’) describes a real position that won 139.53; the 9,292.30 that paid for it arrived 78 seconds before the buy and 9,300.00 left 162 seconds after the sale, to the exchange address the other accounts use, and the same sum went in and out twice more that day. That is the holder moving its own money in for single bets: context, not misconduct.
  • The ‘new acc’ was shown openly as the handle’s account, and the handle’s reply of 2026-04-28 (‘+$2k for now’) was close to the account’s chart at that moment (+1,510.73).
How both figures are counted

Final result after fees of iluvdubnation (86 positions, last fill 2026-05-12 13:38:38 UTC), rebuilt from fills; not shown on X after 2026-05-01.

@0xBumblebee

@0xBumblebee: what was shown and what the record holds

The chapter on @0xBumblebee

result

Also true

  • The handle posted its losses in aggregate and often: -$2,704.06 (‘PnL is down only ... By the way someone is me’, 2026-02-12), -$4,501 (2026-03-10), -$6,300 (2026-03-28), a day of -$23,061.46 and down $25,000 from a peak of about $45,000 (2026-04-02), ‘i took a needed break from trading on Polymarket due to big losses’ (2026-04-19), ‘-$3,200’ for a losing streak (2026-06-13), ‘i lost the whole bankroll’ (2026-07-17) and ‘still net negative’ (2026-08-04). What it did not show is this account and the size of its loss.
  • On 2026-05-29 the handle posted a market link carrying the referral name r=Uiom, and Uiom’s profile is public.
  • The winnings on the two claim cards the handle posted (‘Claim $22,358.24’ on 2026-03-31, ‘Claim 37,597.79’ on 2026-04-01) were real. The public figure of the visible profile is accurate for that account (-8,112.34 dollars by cash).
  • A comparison of single positions (113 positions shown one by one made +34,478.31 dollars, the 442 others lost 52,623.83) leaves out the aggregate loss cards above and is not a measure of what was disclosed; 36 of its matches rest on a market name without a figure.
  • The two credits of 292.802 dollars that the handle asked followers about on 2026-04-19 (‘i found $585.6 on my account however i didn’t make any deposits’) were labelled ‘Deposited funds’, with no source, in the app screen it posted. They are best read as the referral payout for Uiom’s largest fee day, 2026-04-04 (30% of 950.62 = 285.19, plus about 7.6 from other referrals), paid two weeks late and twice. Asked whether it matched referral volume, the handle answered ‘nope, no referral volume yesterday’, which was true; nothing shows that it knew where the money came from.
  • That Uiom is the handle’s referral is inferred from the two exact 30% matches; the referral relation itself is not public. Polymarket’s referral help page (archived 2026-03-24, before Uiom existed) reserves the right to disqualify self-referrals; nothing shows that Polymarket did so.
  • Referral income is ordinary programme income and is context here, not the accusation: of the 894.51 dollars of referral rewards, up to 861.27 arrived on days tied to Uiom’s trading if the payout that came twice is counted twice.
  • Komacsi’s -787.96 predates the handle’s Polymarket posts. Two-sided betting between the accounts was tested and not found.
How both figures are counted

Collateral actually moved, fees included, of the eight accounts tied to the handle (visible profile, Uiom, Demion, Komacsi, and the Bagel, DG3, Stride and Firefly accounts), to the snapshot of 2026-10-01; -18,178.66 with the ninth address.


Replays

The cases, step by step

Each replay runs one case in order, to the second: the posts, the trades and the transfers, each in its own lane, with a clock. Press play, drag the slider or tap a step. Every step links to its record.

Loading the replays…


Payments and disclosure

Each payment, the post beside it, and what the post disclosed

122 transfers from wallets on the side of the apps to addresses tied to the handles. Receiving such money is ordinary. Each payment is set next to the post it sits beside, and that post’s disclosure state. What a payment was for is not on chain.

Loading the payments…


The connected map

What the records connect, and what they do not

Every line is a link a record establishes: a payment, a funding transfer, a pair of opposite positions, a post about an account. Red lines connect the parts of two handles. Tap a line or a dot for its records. Shared public infrastructure is never a link.

Loading the map…


The deleted record

Deleted posts

X’s public embed endpoint answers ‘This Post was deleted by the Post author’ for a post its author removed. A deleted retweet is not a deleted statement by the handle. When a post was removed is known only as a window between the last time a source shows it up and the first time a source shows it gone. The list holds the posts with recovered text; retweets, posts whose text could not be read and posts with a withheld passage are counted and not listed.

Loading the deleted posts…


The limits

What the evidence does not show

The tests that were run and found nothing, the questions the public record cannot answer, and the readings the evidence does not support. They count as much as what was found.

Tested, not found@_kate_lv

@_kate_lv described the two-account method in public in 2025 and wrote about hedging its own trades in five posts and four replies

The handle described the method in its own public replies before the pairs of its posted trades began: ‘i have my accs ready since last 2 years already’ under ‘we farming for poly airdrops?’ (2025-10-15) and ‘try finding like sports bets where yes and no goes for 51/49 u bet equal monies and make volume on both accs and basically won’t loose any’ (2025-10-16). Later it wrote ‘you could literally do limit orders on a multiple accs’ (2026-01-31), ‘you can always hedge from a diff wallet’ (2026-02-26), ‘hedge accs and sell the winning one’ (2026-08-26) and ‘just dont go public, make another acc and thats it side wallet etc’ (2026-09-03). About its own trades it wrote of hedging in five posts on its own timeline (2025-12-02, 2026-01-13, 2026-06-15, 2026-08-02, 2026-08-05) and in four replies (three on 2026-06-16, one on 2026-07-22, ‘also hedged some on vision wallet’).

What was tested. method described in public: 2025-10-15, 2025-10-16, 2026-01-31, 2026-02-26, 2026-08-26, 2026-09-03; own hedge mentions: 5 posts on the own timeline + 4 replies; Clippers vs. Heat 2025-12-01: heooo’s Heat buy 8 seconds after the visible profile’s Clippers buy; legs together -$36.73

Tested, not found@_kate_lv

@_kate_lv says openly that it takes paid deals, and from 2026-08-09 it set X’s paid-partnership label on 11 of about 160 readable own posts, among them all its Bagel posts

@_kate_lv says openly that it takes paid deals (‘this X account has made me over $10k in two months since i started taking paid deals’, 2026-06-01; ‘i was actively trading across 5 wallets (including my main Polymarket one) while doing some paid deals’, 2026-07-20; ‘we get paid for being public i guess’, 2026-08-29) and that ‘everything i collab with based on prediction markets is on top of polymarket’ (2026-06-11). X’s own paid-partnership label can be read in archived post objects from 2026-08-09. From that date the handle had set it on 11 of about 160 readable posts on its own timeline, among them all its Bagel main posts and its Firefly post of 2026-08-20; six of the seven readable posts since that date in which it shows a trade are labelled.

What was tested. X paid-partnership label from 2026-08-09: 11 of about 160 readable own-timeline posts (all Bagel main posts, the Firefly post of 2026-08-20); posts since 2026-08-09 that show a trade: 6 of 7 readable labelled; 215 own-timeline posts naming an app other than Polymarket since 2026-03-01: 2 say in words partnership or gift

Tested, not foundAll handles and the apps

Deleted losing calls were tested and not found: no removed post of @_kate_lv whose text could be read is a losing call or slip, and about half were re-posted within 15 minutes

Deleted losing calls were tested and not found. 336 posts of @_kate_lv in the record were removed by the author. About half of its 292 own removed posts were put back within 15 minutes in the same or nearly the same words (33 word for word, 150 at 0.8 text similarity).

What was tested. 336 removed posts; 292 own removed posts, about half put back within 15 minutes (33 identical, 150 at 0.8 similarity); removed losing calls or slips whose text could be read: 0; unreadable: 13 posts plus the image of one image-only post

Tested, not found@itskkoma

Two-sided betting between the accounts was tested and not found: no two of the nine wallets ever held opposite outcomes of a market or traded with each other

Two-sided betting between the accounts was tested and not found: in 4,662 fills and 1,942 positions no two of the nine wallets ever held opposite outcomes of a market, and none ever traded against another (0 exchange fills with wallets of the book on both sides). They met in 4 markets, each time on the same outcome. Opposite legs in different markets of one match were checked as well: six matches were traded by two wallets of the book and none is an offset.

What was tested. markets shared by two wallets of the book: 4, all on the same outcome; opposite outcomes: 0; fills between two wallets of the book: 0; positions: 1,942 costing 1,428,195.75 (plus 4 parlays, 40.50); both outcomes inside one wallet: 18 markets, 14,815.99 (1.04% of buys), result +700.75

Tested, not found@itskkoma

Apart from DG3 rebates and Polymarket programme money, no payment from an identified app or KOL payer reached the nine wallets or their keys

Every deposit of 1,000 dollars or more into the nine wallets was paid by an owner key of the book, and every withdrawal went to such a key, except 45.00 dollars (2026-02-17, from mememez to 0xf7cd89be08af4d4d6b1522852ced49fc10169f64) and the 23,318.70 taken on 2026-09-28. Identifiable income from outside is small: 943.98 from DG3-linked wallets (rebates, stated separately) and 2,877.04 from Polymarket’s published programmes (maker rebates 856.59, taker rebates 630.73, liquidity rewards 356.08, referral rewards 1,033.47, 0.18 from one more payer). No prize, batch payout or other app payment reached the wallets or their owner keys.

What was tested. Polymarket programme money: 2,877.04 (maker rebates 856.59, taker rebates 630.73, liquidity rewards 356.08, referral rewards 1,033.47, other 0.18); DG3 rebates: 943.98 PUSD; one-hop transfer: 1,000 USDT0; withdrawals not to a key of the book: 45.00 (2026-02-17) and 23,318.70 (2026-09-28)

Tested, not found@itskkoma

Nothing in the record changes on 2026-08-04 in a way that reads as a reaction: the other accounts had stopped before, and the public profile kept trading

Nothing in the record reads as a reaction to 2026-08-04. The other accounts had stopped before it (mememez on 2026-06-20, nononononoononono on 2026-07-05 apart from one parlay on 2026-07-24); after it the other wallets made 6 fills (alwayslosings 1 of 227.07 on 2026-08-20, the app wallet 5 on 2026-09-26 and 2026-09-27). The public profile bought more in the four weeks after that date (94,874.34 dollars, result -4,610.00) than in the month before (85,624.02, result +4,632.07) and less in September (22,668.64, result +6,781.82); no two wallets held opposite sides before or after.

What was tested. public profile buys: 85,624.02 (2026-07-05 to 08-03), 94,874.34 (08-04 to 08-31), 22,668.64 (September); results +4,632.07, -4,610.00, +6,781.82; other wallets after 2026-08-04: 6 fills (alwayslosings 1, the app wallet 5); opposite positions between wallets: 0 before, 0 after

Tested, not found@gusik4ever

The handle said in public that it had more than one account, that it was Polymarket’s Sports Community Lead and an affiliate, and that it also loses

In public posts the handle said that it trades from more than one account (‘i literally shared it publicly’, 2026-01-20; ‘I have different accs’, 2026-04-28), announced its role (‘Excited to join @Polymarket as Sports Community Lead’, 2026-01-30; its X bio carried ‘ambassador of @Polymarket’ from 2026-01-18 to 2026-02-11 and ‘Community Lead in @PolymarketSport’ from 2026-01-31 to 2026-08-07, and X shows the label ‘Polymarket Sports’ on the account), called itself an affiliate (‘my opinion would be the same even if i wasn’t an affiliate’, 2026-04-24), listed its blog and ads and KOL programmes among its sources of income (2025-09-13), and said in general words that it loses (‘this is my main account, and yeah, it’s in the red right now’, 2025-11-11; ‘over the last few months i’ve had to rebuild my deposit twice’, 2026-01-26; ‘i blew up twice’, 2026-01-27; ‘I post a lot of screenshots with profits, but that’s only the tip of the iceberg’, 2026-07-19).

What was tested. bio ‘ambassador of @Polymarket’ 2026-01-18 05:06:20 UTC to 2026-02-11 21:26:09 UTC; ‘Community Lead in @PolymarketSport’ 2026-01-31 05:17:46 UTC to 2026-08-07 12:27:01 UTC, absent on 2026-08-09 06:03:38 UTC; ‘nfa’ / ‘dyor’ in 85 X posts and 65 Telegram posts; 38 quotations (31 X + 7 Telegram) checked against the stored text

Tested, not found@gusik4ever

Two-sided betting between the handle’s accounts was tested over their whole history and not found: when two of them traded one market they mostly bought the same side

Two-sided betting was tested and not found for this handle: its accounts did not bet against each other. In 2,721 fills and 137 markets that two of the nine wallets shared (the six wallets and the three candidates), two accounts held different outcomes of one market 10 times, with unequal stakes (the smaller leg a median 30.3% of the larger) worth 4,124.15 dollars, 1.8% of the 233,759.09 dollars they bought single markets with. None is a size-matched pair, and no fill was made between the accounts.

What was tested. 10 opposite pair-markets in 137 shared; legs 4,124.15 = 1.8% of 233,759.09; size-matched pairs: loose rule 0, strict rule 0; fills between two of the accounts: 0; median smaller/larger leg 30.3%; combined result of the ten cases +259.72

Tested, not foundAll handles and the apps

PolyHelper is a payer of the handle’s exchange address, not a co-user: no key, funding or trade ties the handle to the PolyHelper team’s accounts or to its X account

What ties @gusik4ever to PolyHelper is 650 USDC paid by the app’s two wallets into the exchange deposit address its accounts cash out to (150 on 2026-07-06 by a withdrawal of PolyHelper’s builder profile 0x2a1f579283c87c4574102bbf6e4b39f7a12fe77e (opens in a new tab), 500 on 2026-07-19 from that profile’s only owner key 0x8ecb4b228e07b6ddc58a32997093032a6907b8f6 (opens in a new tab)), both on livestream days, and three trades of about five dollars the lolxdkek profile placed through the app on 18 and 19 July 2026 (15.40 dollars). Tested and not found: no owner key is shared, no money moved between the handle’s accounts and the PolyHelper team’s accounts, none of the handle’s wallets is among the users PolyHelper paid in its batches, and their trades never met (19 shared markets, 0 size-matched pairs, 0 fills against each other). An X account of PolyHelper’s team, which writes as a member of the team, is not a second handle of @gusik4ever: it names the handle once in a list of tagged accounts, and the two never reply to each other.

What was tested. PolyHelper builder profile -> exchange address 150 USDC (2026-07-06 17:31:46 UTC); owner key -> exchange address 500 USDC (2026-07-19 16:20:33 UTC); lolxdkek fills with PolyHelper’s code: 3, 15.40 dollars, 2026-07-18 22:05:27 UTC to 2026-07-19 19:22:21 UTC; transfers between the handle’s accounts and the PolyHelper-side accounts: 0; the handle’s wallets among the app’s 72 batch recipients: 0

Tested, not found@gusik4ever

The DG3 ‘test it live’ screen of 2026-07-23 shows a real 25-dollar bet, placed through DG3 from a wallet funded minutes earlier by an exchange withdrawal

The DG3 ‘test it live’ screen of 2026-07-23 shows a real bet: one wallet, 0xc50a827c07b28e49db383d37404876db83f58539 (opens in a new tab), bought 25 dollars of the 1-1 exact score at 0.15 through DG3 at 10:03:21Z, the only buy of that size at that price in the market. The wallet was funded eight minutes earlier with 50 USDC withdrawn from a Bybit hot wallet, made two trades, lost 31.23 dollars and was not used again. The stake came from an exchange withdrawal, not from DG3.

What was tested. 50.0 USDC from Bybit Hot Wallet 6 at 2026-07-23 09:55:21 UTC -> 49.862472 PUSD credited at 09:55:57Z -> bet of 25.00 at 10:03:21Z (8 minutes after the withdrawal); 2 fills, both DG3-coded; result -31.23; stablecoin movements in the wallet’s life: 3

Tested, not found@gusik4ever

Deleting losing calls was tested and not found: the handle’s deleted posts are mostly edits put out again within minutes

Tested and not found: the handle did not delete its losing calls. Of its 305 deleted posts with recovered text, the 125 that were original posts or quotes are mostly edits put out again within minutes (41 to 46 of them within two hours, median gap about three minutes), and no deleted post carries a result card or a call that later lost, apart from one 12-dollar parlay posted for subscribers.

What was tested. 305 own deleted posts with text (96 originals, 29 quotes, 180 replies); 41 to 46 of 125 originals and quotes re-posted within 2 hours, median 173 to 180 s; deleted posts with a slip or call that later lost: 1 (the 12-dollar subscriber parlay of 2026-07-16); deleted replies with bet wording: 0

Tested, not found@0xBumblebee

Two-sided betting between the accounts of @0xBumblebee was tested and not found: in the 12 markets they shared, they always held the same outcome

For @0xBumblebee two-sided betting between accounts was tested and not found. Across the nine addresses tied to the handle (36 pairs) there are 12 markets in common, and in every one of them the accounts held the same outcome (the visible account and Demion in 9, Demion at about a tenth of the size); none of the 5,628 fills of these accounts was matched against another of them, and no outcome token moved directly between them. Uiom and the visible account never traded the same market.

What was tested. address pairs: 36; markets in common: 12; same outcome: 12; opposite outcome: 0; fills matched between the accounts: 0 of 5,628; outcome tokens moved between them: 0; same account, both outcomes held at once: 1 market, 3.50 against 319.43 dollars

Tested, not found@0xBumblebee

A slip on one app offset by a bet elsewhere was tested for @0xBumblebee and not found, across five Polymarket front-ends it promoted in June and July 2026

Between 2026-06-01 and 2026-07-08 @0xBumblebee promoted five front-ends for Polymarket in posts of its own: Share (8 posts and 8 replies with its link share.xyz/r/0xbumblebee), DG3 (6 posts, code BEE), Firefly (2 posts and 2 cards), Bagel (2 cards) and Stride (1 post with its referral link). In four of the apps it bet from a separate account, 20 to 40 dollars a time (one Bagel card of 305.52); the Share bets were made from the visible account (12 fills with Share’s builder code). No bet was offset in another account: for this handle the idea of a slip on one app and the opposite leg elsewhere was tested and is refuted.

What was tested. front-ends promoted in own posts: Share 8 posts and 8 link replies, DG3 6 posts, Firefly 2 posts and 2 cards, Bagel 2 cards, Stride 1 post; results of the app accounts: Bagel -823.17, DG3 +32.66, Stride -31.99, Firefly -249.38; bets offset in another account: 0

Tested, not found@0xBumblebee

@0xBumblebee told its audience in general terms that its X account was paid; its own month list matches the chain for May (610 dollars) and June (1,427)

@0xBumblebee told its audience roughly what its X account earned: ‘on April i secured my first paid deals’ (2026-04-22), ‘this $100 deal’ the same day, ‘earned mid 3 figs from gigs’ for May, and on 2026-08-13 ‘may: 3 figs june: 4 figs july: 0 figs aug: 0 figs’. Transfers that look like pay to its wallet and app accounts total 3,251.84 dollars in 23 payments, 610 in May and 1,427 in June, which fits those statements. In July the DG3 wallet paid its key 250 and Firefly’s hub sent 200 to the wallet that feeds its Firefly account.

What was tested. pay-like transfers: 3,251.84 dollars in 23 payments (February 100, March 120, April 100, May 610, June 1,427, July 476.84, August 123, September 190, October 105); from named app wallets: 1,201.84 (DG3 800, Firefly 389.95 including a 14.95 prize, Bagel 11.89); payers named by the handle: 362; unidentified round-amount payers: 1,688; Polymarket programme income of the accounts: 1,389.38 dollars, plus a 500-dollar contest prize

Tested, not foundAll handles and the apps

One paymaster behind @0xBumblebee is not supported: two app wallets and several unidentified payers paid it, and the app wallets also paid other handles

The money that reached @0xBumblebee’s wallets as pay came from two app wallets, the DGBet/DG3 payout wallet (800.00 USDT0, stated separately) and Firefly’s wallets (175.00 USDC from the loader; 200.00 from the hub to a wallet that fed its Firefly account, stated separately), plus Bagel and Firefly contest prizes and several payers that are not identified. The same app wallets also paid wallets of @_kate_lv and @gusik4ever (see their chapters). A Bagel prize batch of 100 legs on 2026-07-23 paid 8.0 PUSD to the handle’s Bagel account, 40.0 to the Bagel account 0xddf387340282fc9bd388d699f35f10735b66b7b5 (opens in a new tab) whose slips @_kate_lv posted, and 8.0 to 0xf595d7f0dcf9cb1b39c420b6f041c19b89f7fd9e (opens in a new tab), the wallet behind @gusik4ever’s Bagel slips.

What was tested. DG3 payout wallet to this handle: 800.00 USDT0 in 4 payments; Firefly loader to this handle: 175.00 USDC in 1 payment; Bagel prize batch of 2026-07-23: 100 legs; 8.0 PUSD to this handle’s Bagel account

Tested, not found@0xd1namit

@0xd1namit builds PolyHelper and has said so in public since January 2026; its account’s owner key funds PolyHelper’s signer and its trades carry PolyHelper’s code

@0xd1namit calls PolyHelper ‘my project’ and says so in its Polymarket bio (‘Add new features in Polymarket interface by using polyhelper.io’) and in its X bio (‘Building @Poly_Helper’, from 2026-01-22). The owner key of the d1namit account (0x7f77b9ffe1813632fb7e7ee508f0bab7b65617f5 (opens in a new tab), the only owner of 0xc974c6ab4032e89aef89bf2489709905ef41eb16 (opens in a new tab)) funds the PolyHelper signer 0x8ecb4b228e07b6ddc58a32997093032a6907b8f6 (opens in a new tab) (4,108.64 USDC in six transfers on Base, 2026-03-16 to 2026-08-17), and 3,419 of the account’s 3,420 fills since 2026-04-28 (287,068.31 dollars) carry PolyHelper’s builder code.

What was tested. owner key to PolyHelper signer: 4,108.64 USDC in 6 transfers (25.64, 824, 814, 1,192, 295, 958), 2026-03-16 to 2026-08-17; fills with PolyHelper’s builder code: 3,419 of 3,420 since 2026-04-28 (287,068.31 dollars); PolyHelper all-time builder volume 280,587,960.67 dollars, rank 7; team accounts’ share 0.17%

Tested, not found@0xd1namit

@0xd1namit told readers in September 2025 that it is a Polymarket affiliate, has marked its link posts as paid since March 2026, and sets X’s label on most of them

@0xd1namit, which told its readers in September 2025 that it is a Polymarket affiliate, has put its affiliate link (?via=d1namit) in about 170 posts and replies since 2025-09-09. In September 2025 it ran a 300-dollar giveaway that required signing up through the link (paid in full: ten transfers of 30.00 USDC.e on 2025-09-24, eight of them to profiles created after the announcement), and on 2025-10-14 it offered 10 dollars to new users who signed up through the link and deposited 20 dollars. From 2026-03-03 it adds notes under its threads such as ‘Second one includes ref link = it’s sponsored’, and since 2026-08-09 X’s paid-partnership label is set on 26 of the 30 replies under its own posts that carry a link, read in archived copies.

What was tested. ?via=d1namit in about 170 posts and replies since 2025-09-09 (89 before 2026-03-03, 54 from 2026-03-03 to 2026-08-08, 27 since 2026-08-09); notes calling a link post sponsored or paid: 10 (2026-03-03 to 2026-04-03); X’s label since 2026-08-09: 26 of 30 link-carrying replies under its own posts; 26 of 30 link-carrying replies under its own posts

Tested, not foundAll handles and the apps

Two-sided betting was tested for @vadim_kesha1 and @0xd1namit and not found; CryptoKesha is not a hedge leg of another handle’s book

For @vadim_kesha1 and @0xd1namit two-sided betting was tested and not found. CryptoKesha is not a hedge leg of another handle’s book: money between it and the katelv account is three small transfers, and in the few markets it had in common with accounts of @_kate_lv’s group it held the side @_kate_lv called, with 73 to 203 dollars. For each of the 760 buys of 100 dollars or more by the CryptoKesha cluster, no other wallet bought the opposite outcome in matching size within five minutes in more than five markets.

What was tested. buys of 100 dollars or more of the CryptoKesha cluster screened: 760; the most frequent mirroring wallet: 5 of 334 markets; Banana Gun wallet: 7 fills, bought 200.51, result -94.72; cards = 3 fills to the cent; d1namit and oxvoodoo: same outcome in 63 markets, opposite in 3

Tested, not foundAll handles and the apps

Tested and not found: no account of the four groups filled another’s order, and buying both outcomes across accounts is absent for @itskkoma and @0xBumblebee

No account of any of the four groups of accounts tied to @_kate_lv, @gusik4ever, @itskkoma and @0xBumblebee ever filled an order of another account of the same group (0 direct fills in each, from 2026-04-28 to 2026-10-01). Buying both outcomes of a market across the accounts of a group was tested on all four: nothing for the accounts tied to @itskkoma and @0xBumblebee, and 6 small markets for those tied to @gusik4ever (139 shares a side, 324 if an account’s own two-sided buys are counted; under 0.7% of 97,166 bought shares). It is found only for the accounts tied to @_kate_lv.

What was tested. direct fills between two accounts of one group: 0 in each of the four groups; @gusik4ever’s accounts: 6 markets with opposite outcomes bought by different accounts, 139 shares a side (324 with accounts’ own two-sided buys), under 0.7% of 97,166 bought shares; @itskkoma’s and @0xBumblebee’s accounts: 0 such markets

Tested, not foundAll handles and the apps

Follower harm through the referral links was tested on the seven referred accounts the fee logs reveal and not found: they did not trade what the handles traded

Seven accounts that signed up through the handles’ Polymarket referral links can be found from the fee logs, because each daily reward equals a fixed share of the fees they paid the day before; they explain 330.31 of the 444.05 PUSD of rewards that the handles’ own accounts do not. They did not trade what the handles traded: of the 203,811.62 dollars they spent on buys, 396.51 dollars (0.2%) went into an outcome that an account tied to the referring handle also bought since April 2026, and five of the seven share no outcome with it at all. Together they traded 307,610.59 dollars and their trades ended 23,113.78 dollars down; almost all of it is one heavy, automated-style account, so the result says nothing about followers acting on the handles’ calls.

What was tested. 35 fee days scanned (74,550,009 crossing-order logs); 7 referred accounts matched on two or more reward days; explained: 330.31 of the 444.05 PUSD of rewards not explained by the handles’ own accounts; their buys in outcomes the referring handle’s accounts also bought: 396.51 of 203,811.62 dollars (0.2%); 5 of 7 share no outcome

Tested, not found@_kate_lv

@_kate_lv has set X’s paid-partnership label since August 2026 (14 posts) and has told its readers since 2026-06-01 that it takes paid deals

@_kate_lv has set X’s paid-partnership label on posts since August 2026: 14 flagged posts between 2026-08-10 and 2026-09-28 (11 original posts or quotes and 3 self-replies; 6 about Bagel, 1 about Firefly, 4 about Polymarket or products built on it, 3 about other products). No readable post of the handle with a referral link or code since 2026-08-09 stands unmarked under an unmarked first post. In words it named a partner, a reward or a gift four times, and it has said in public since 2026-06-01 that it takes paid deals (‘this X account has made me over $10k in two months since i started taking paid deals’).

What was tested. flagged posts since 2026-08-09: 14 of 69 readable posts that name a product (11 original posts or quotes, 3 self-replies); posts with the literal ‘my code’, ‘my link’ or ‘my ref’: 15; posts coded as naming the link or code its own: 26; partner, reward or gift named in words: 4 posts

Tested, not found@gusik4ever

@gusik4ever told its readers of its tie to Polymarket: it announced its Sports Community Lead role on 2026-01-30 and called itself an affiliate

@gusik4ever told its readers of its tie to Polymarket: it announced on 2026-01-30 ‘Excited to join @Polymarket as Sports Community Lead’, wrote on 2026-03-07 ‘my first month working at Polymarket Sports’, carried ‘Community Lead in @PolymarketSport’ in its bio from 2026-01-31 to 2026-08-07 and counted itself among ‘Polymarket Sports affiliates’ (2026-07-30). When a reader called it one of Polymarket’s own affiliates on 2026-04-24 it answered ‘my opinion would be the same even if i wasn’t an affiliate’. Its invite code is written out in the posts that carry it (‘code: WINCY’), and two posts of 2025 announce ambassador roles for other projects.

What was tested. posts stating a tie in words: 3 (two ambassador announcements of 2025 and one more); 17 call the link or code its own; readable posts since 2026-08-09: 94, flagged 0; affiliation badge ‘Polymarket Sports’ on all 238 post objects read since 2026-08-09; bio role lines: ‘ambassador of @Polymarket’ 2026-01-18 to 2026-02-12; ‘Community Lead in @PolymarketSport’ 2026-01-31 to 2026-08-07

Tested, not found@0xBumblebee

@0xBumblebee announced its first paid deals in public, says it always sets X’s paid-partnership label, and calls its referral link its own in 41 posts

@0xBumblebee told its readers when it began to take paid deals (‘on April i secured my first paid deals’, 2026-04-22), says it always sets X’s paid-partnership label when a post is paid (2026-04-29 and 2026-07-21) and named a sponsor in words in two posts of July 2025. It calls its referral link its own in 41 posts (‘my ref link’).

What was tested. posts that name or link a product: 1,319; disclosed in words 4 (3 in the post, 1 in the thread); 41 call the link its own; readable since 2026-08-09: 22, flagged 0

Tested, not found@vadim_kesha1

@vadim_kesha1 flagged four posts as paid partnerships in September 2026, announced its Polymarket Sports affiliation, and wrote ‘when unsure, add paid partnership’

@vadim_kesha1 flagged four posts as paid partnerships in September 2026 (three about DG3, one with its Polymarket referral link), announced on 2026-02-12 ‘official: I’m a Polymarket sports affiliate’ (the post was later removed), listed ambassador roles in its bio in 2024 and 2025 and announced three such roles in posts of those years. On 2026-03-05 it wrote ‘rule of the game: when unsure, add paid partnership’.

What was tested. flagged posts since 2026-08-09: 4 of 34 readable (DG3 2026-09-16, 09-17, 09-23; Polymarket 2026-09-18); readable posts with a referral link not flagged: 12; posts naming or linking a product: 903; 17 call the link its own; 3 posts of 2024 and 2025 state an ambassador role in the first person

Tested, not found@itskkoma

@itskkoma marked deals and unpaid mentions in words: 12 posts name a sponsor, its own product or a benefit, and 10 say ‘not sponsored’ or the like

@itskkoma marked deals and unpaid mentions in words: 12 posts state a sponsor, its own product or a benefit received (four of them its DG3 rebates) and 10 say ‘not sponsored’ or the like. It wrote on 2026-07-07 ‘Anything I posted related to prediction markets projects, I did not get paid (unless disclosed)’ and on 2026-08-01 ‘I rather be washed than do undisclosed shills’. No direct payment from an identified app wallet outside a published scheme reached its accounts.

What was tested. disclosures in words: 12 (11 in the post, 1 in the thread); denials: 10; posts naming or linking a product: 4,201, 3,486 of them only products outside prediction markets; 151 call the link its own; readable since 2026-08-09: 82 of 88, flagged 0

Tested, not found@0xd1namit

@0xd1namit marks the posts that carry its Polymarket affiliate link: by footers from 2026-03-03 and with X’s label on 26 of its 30 link-carrying replies since 2026-08-09

@0xd1namit marks the posts that carry its Polymarket affiliate link. It did so in words on single posts from November 2025, and from 2026-03-03 by footers such as ‘Second one includes ref link = it’s sponsored’ and, on 2026-04-03, ‘This post is not sponsored, but I have to flag it as a paid partnership because of ref link’ (9 link posts sit in such a thread); since 2026-08-09, 26 of its 30 link-carrying replies under its own posts carry X’s paid-partnership label. It told its readers in September 2025 that it is a Polymarket affiliate, and its bio has read ‘Building @Poly_Helper’ since January 2026.

What was tested. posts naming or linking Polymarket: 752; with a tracked link (via=): 176, 95 of them before 2026-03-03; link posts in a thread with a ‘sponsored’ or ‘paid’ footer: 9 (2026-03-03 to 2026-04-03); a tenth footer thread carries another app’s link; readable tracked-link posts since 2026-08-09: 27, flagged 25; with any referral link or code: 30 readable, 26 flagged

Tested, not foundAll handles and the apps

One paymaster was tested and not found: the money comes from Polymarket’s programmes, DG3 and Firefly (plus Bagel and PolyHelper), whose wallets never pay each other

The hypothesis of one paymaster was tested and is refuted. The payments into the accounts in this story come from separate sources between which no stablecoin has moved: three named sources carry nearly all of it, Polymarket’s own published programmes (builder rewards, contest prizes, rebates), the betting app DG3 (DGBet) and the app Firefly; Bagel and PolyHelper pay smaller sums from their own wallets. A scan of 14 app wallets found no transfer between wallets of different apps, and pair filters over the whole history found none between the DG3 side, the Firefly side and the Polymarket payer wallets.

What was tested. transfers between wallets of different apps: 0 (14 app wallets scanned); between the DG3 side, the Firefly side and the Polymarket payer wallets: 0 (pair filters, whole history); handles in this story on more than one app’s list: 4 (@_kate_lv and @0xBumblebee by owner key; @gusik4ever and @vadim_kesha1 by withdrawal address); DG3 and Firefly payments to the three shared payees, 2026-05-29 to 2026-06-12: 13 payments in 10 transactions (8 DG3 legs in 5 transactions, 5 Firefly transfers)

Tested, not foundAll handles and the apps

The handles announced their Polymarket badges and roles themselves; archived copies show the label from 9 August 2026 on four of them and not on @0xBumblebee

The handles announced their Polymarket badges and roles in public: @_kate_lv on 2026-01-05 (“new badge who dis”, with X’s notice that Polymarket Sports had added it as an affiliate), @gusik4ever on 2026-01-30 (“Excited to join @Polymarket as Sports Community Lead”), @vadim_kesha1 on 2026-02-12 (“official: I’m a Polymarket sports affiliate.”, removed since), @0xBumblebee on 2026-04-01 and 2026-04-02 (“acquired a Polymarket’s badge”) and @itskkoma on 2026-05-01 (“New badge @PolymarketSport”). On 2026-08-04 @0xBumblebee’s verification tick disappears between archived copies of 05:31 and 06:50 UTC, and at 11:27 UTC it wrote “I have no badge anymore”. Archived post objects carry the author’s affiliation label from 2026-08-09 03:30 UTC: from then to 2026-09-29 every archived copy of @gusik4ever (335 copies, first 2026-08-09 05:29 UTC), @vadim_kesha1 (76, from 08:55 UTC), @itskkoma (95, from 20:54 UTC) and @_kate_lv (122, from 2026-08-10 11:22 UTC) carries ‘Polymarket Sports’, and none of @0xBumblebee’s 408 copies carries a label.

What was tested. badge or role announced: @_kate_lv 2026-01-05 22:04:07 UTC; @gusik4ever 2026-01-30 20:44:12 UTC; @vadim_kesha1 2026-02-12 11:11:58 UTC; @0xBumblebee 2026-04-01 10:34:07 UTC; @itskkoma 2026-05-01 14:01:26 UTC; label field in archived post objects from 2026-08-09 03:30:15 UTC (last copy without it 00:04:25 UTC); archived copies with ‘Polymarket Sports’ to 2026-09-29: @gusik4ever 335, @_kate_lv 122, @itskkoma 95, @vadim_kesha1 76; @0xBumblebee 0 of 408

Tested, not foundAll handles and the apps

The handles answer each other daily, but as part of a mass-reply habit: 3.0% of @_kate_lv’s 39,665 answers in 125 days went to the other five handles

Six of the handles answer each other’s posts every day: the record holds 4,171 answers, 32 quotes and 24 reposts between handles of the X record read for this story. Between 2026-04-01 and 2026-08-03 @_kate_lv answered 200 of 302 (66.2%) of @gusik4ever’s own posts and 201 of 332 (60.5%) of @0xBumblebee’s. In the same 125 days @_kate_lv posted 39,665 answers to 2,806 accounts, and the other five handles received 3.0% of them; @0xBumblebee made 24,787 answers to 1,634 accounts (2.7% to the other handles) and @gusik4ever 13,754 to 1,690 (4.1%). Tested as a sign of one system, the reply circle is the footprint of a mass-reply habit.

What was tested. 4,171 answers, 32 quotes, 24 reposts between handles read (repaired build of 2026-10-02); @_kate_lv on @gusik4ever’s own posts: 21 of 253 (8.3%) Oct-Dec 2025; 71 of 257 (27.6%) Jan-Mar 2026; 200 of 302 (66.2%) 2026-04-01 to 2026-08-03; 90 of 172 (52.3%) afterwards; @_kate_lv on @0xBumblebee’s: 201 of 332 (60.5%) then 29 of 99 (29.3%); on @vadim_kesha1’s: 64 of 187 (34.2%) then 24 of 62 (38.7%)

Tested, not foundAll handles and the apps

The accounts’ post counters show no burst of removals after 2026-08-03; one removed post of that week speaks to several accounts

Tested for a burst of removals after 2026-08-03 16:46 UTC, the accounts’ own post counters show none. Every archived copy of a post carries the account’s post counter, so the posts known to have been made minus the counter’s rise is the least number removed. Over 2026-08-03 @_kate_lv’s counter rose by 231 against 231 posts known, @gusik4ever’s by 129 against 130, @itskkoma’s by 19 against 21, @vadim_kesha1’s by 4 against 4 and @0xd1namit’s by 6 against 6; per ISO week 29 to 35 of 2026 the least numbers removed stay in each handle’s usual range (@_kate_lv 4, 7, 11, 0, 3, 4, 6).

What was tested. 2026-08-03: counter rise against posts known: @_kate_lv +231 / 231; @gusik4ever +129 / 130; @itskkoma +19 / 21; @0xBumblebee +159 / 170; @vadim_kesha1 +4 / 4; @0xd1namit +6 / 6; least removals per ISO week 29 to 35 of 2026: @_kate_lv [4, 7, 11, 0, 3, 4, 6]; @gusik4ever [21, 9, 14, 7, 4, 28, 17]; @itskkoma [7, 8, 6, 2, 3, 1, 2]; @0xBumblebee [35, 13, 35, 11, 29, 35, 30]; removed own posts and answers of five handles posted after 2026-08-03: 109, of which 49 re-posted edits

The record cannot answer@_kate_lv

Who holds the keys of heooo, butzki, gracechase and the six small tier-3 accounts, and whether one holder or several people sharing money stand behind the group

Who holds the keys of heooo, butzki, gracechase and the six small tier-3 accounts, and whether one holder or several people sharing money stand behind the group.

The record cannot answer@_kate_lv

What the 500.00 USDC.e from the Tailgate-side key on 2026-04-01 was for (trading credit, grant or fee)

What the 500.00 USDC.e from the Tailgate-side key on 2026-04-01 was for (trading credit, grant or fee).

The record cannot answer@_kate_lv

Whose exchange accounts stand behind the common deposit addresses 0x8810783bc7b02ba1e22ee2a72320ae392badc20e and BUucwWkSFFSCpB8y3kdjbyA9t6P5AaNyTBgmWs5nJkJa, and whose exchange account sent the weekly transfers into the Bagel account

Whose exchange accounts stand behind the common deposit addresses 0x8810783bc7b02ba1e22ee2a72320ae392badc20e (opens in a new tab) and BUucwWkSFFSCpB8y3kdjbyA9t6P5AaNyTBgmWs5nJkJa (opens in a new tab), and whose exchange account sent the weekly transfers into the Bagel account.

The record cannot answer@itskkoma

Who holds the owner keys of ‘-.-x’ (0x7de5ea7dd428cbc1df8680b45c9fbdcb7c2e1879) and of the app wallet 0x51493ab016e399e887ec5161bfa3e779d1927030; both are tied to the handle by money routes only

Who holds the owner keys of ‘-.-x’ (0x7de5ea7dd428cbc1df8680b45c9fbdcb7c2e1879 (opens in a new tab)) and of the app wallet 0x51493ab016e399e887ec5161bfa3e779d1927030 (opens in a new tab); both are tied to the handle by money routes only.

The record cannot answer@itskkoma

Whose wallet 0xa94db8518f755ae8c2891a77c020c2bda6311587 is and what the 1,000 USDT0 it sent to the owner key of mememez on 2026-07-09 was for; whether DG3 paid the show gmPM

Whose wallet 0xa94db8518f755ae8c2891a77c020c2bda6311587 (opens in a new tab) is and what the 1,000 USDT0 it sent to the owner key of mememez on 2026-07-09 was for; whether DG3 paid the show gmPM.

The record cannot answer@itskkoma

Whether X’s paid-partnership label was set on the DG3 posts of June to August 2026 (not readable before 2026-08-09)

Whether X’s paid-partnership label was set on the DG3 posts of June to August 2026 (not readable before 2026-08-09).

The record cannot answer@itskkoma

What the unexplained transfers into owner keys are: 5,002.682001 USDT0 from 0x08b00ceee2fb66029b53d76110b19eeaabfd1e65 (2026-08-13) and 825.00 USDT0 from 0x6a4b37be413b00f81826e12793790756cc67d954 (2026-04-04)

What the unexplained transfers into owner keys are: 5,002.682001 USDT0 from 0x08b00ceee2fb66029b53d76110b19eeaabfd1e65 (2026-08-13) and 825.00 USDT0 from 0x6a4b37be413b00f81826e12793790756cc67d954 (2026-04-04).

The record cannot answer@itskkoma

What was bet at the venue, and whose venue account the shared forwarding address 0x8eae9e55a963898e5785d194c276c2c73381e928 credits

What was bet at the venue, and whose venue account the shared forwarding address 0x8eae9e55a963898e5785d194c276c2c73381e928 (opens in a new tab) credits.

The record cannot answer@itskkoma

Polymarket’s referral terms before 2026-05-28 (no capture found) and whether Polymarket treated any of the 825.16 PUSD as a breach

Polymarket’s referral terms before 2026-05-28 (no capture found) and whether Polymarket treated any of the 825.16 PUSD as a breach.

The record cannot answer@itskkoma

Effect of the 414 images the post record withholds (among them the card of the post of 2026-07-05 19:52:12 UTC, a slip withheld under the face screen) on the shares of winners and losers shown

Effect of the 414 images the post record withholds (among them the card of the post of 2026-07-05 19:52:12 UTC, a slip withheld under the face screen) on the shares of winners and losers shown.

The record cannot answer@gusik4ever

Who sent the seven weekly transfers into the Bagel account’s deposit address and the 999.93-USDT0 pair of 2026-10-01: a third party’s weekly payment or one exchange account topping up two wallets

Who sent the seven weekly transfers into the Bagel account’s deposit address and the 999.93-USDT0 pair of 2026-10-01: a third party’s weekly payment or one exchange account topping up two wallets.

The record cannot answer@gusik4ever

Who holds the exchange account behind 0x720191fcd3c1802a303173732ea9d165d8c2e2d5: it behaves as one customer’s deposit address and the handle’s accounts cash out there, but the holder is not on chain

Who holds the exchange account behind 0x720191fcd3c1802a303173732ea9d165d8c2e2d5 (opens in a new tab): it behaves as one customer’s deposit address and the handle’s accounts cash out there, but the holder is not on chain.

The record cannot answer@gusik4ever

What the payments of the wallets attributed to Firefly, DG3 and PolyHelper and of the Polysights-card sponsor were for (fee, prize, programme), and whether part of PolyHelper’s 500 USDC was prize money passed on during the stream of 2026-07-19; the streams were not watched

What the payments of the wallets attributed to Firefly, DG3 and PolyHelper and of the Polysights-card sponsor were for (fee, prize, programme), and whether part of PolyHelper’s 500 USDC was prize money passed on during the stream of 2026-07-19; the streams were not watched.

The record cannot answer@gusik4ever

Who paid the Polysights-card wallet’s packages: the builder code is not in Polymarket’s directory and Polysights is only the likely payer, which is not established

Who paid the Polysights-card wallet’s packages: the builder code is not in Polymarket’s directory and Polysights is only the likely payer, which is not established.

The record cannot answer@gusik4ever

Whether X’s paid-partnership label was set on the Firefly, DG3, PolyHelper and early Bagel posts of April to early August 2026: it cannot be read before 2026-08-09

Whether X’s paid-partnership label was set on the Firefly, DG3, PolyHelper and early Bagel posts of April to early August 2026: it cannot be read before 2026-08-09.

The record cannot answer@gusik4ever

Whether the three further wallets (one funded by the Bagel wallet, one behind the DG3 test screen, one funded by the gusik4ever.eth wallet) belong to the handle

Whether the three further wallets (one funded by the Bagel wallet, one behind the DG3 test screen, one funded by the gusik4ever.eth wallet) belong to the handle.

The record cannot answerAll handles and the apps

The origin of four BNB-chain deposits (1,077.25 dollars), five small deposits and a Tron service wallet (about 15,000 dollars of deposits) into the visible account of @0xBumblebee: a further account could sit there

The origin of four BNB-chain deposits (1,077.25 dollars), five small deposits and a Tron service wallet (about 15,000 dollars of deposits) into the visible account of @0xBumblebee: a further account could sit there.

The record cannot answerAll handles and the apps

What the DG3 and Firefly payments to @0xBumblebee and to the CryptoKesha-side address were for: referral or campaign rewards, or pay for promotion

What the DG3 and Firefly payments to @0xBumblebee and to the CryptoKesha-side address were for: referral or campaign rewards, or pay for promotion.

The record cannot answerAll handles and the apps

Who holds the key of 0x2f3f09ba0c72ce39cdadd86188ab87cbbd2de8cd, the wallet between Firefly’s hub and the Firefly and DG3 accounts @0xBumblebee showed

Who holds the key of 0x2f3f09ba0c72ce39cdadd86188ab87cbbd2de8cd (opens in a new tab), the wallet between Firefly’s hub and the Firefly and DG3 accounts @0xBumblebee showed.

The record cannot answerAll handles and the apps

Whether DG3’s app showed ‘ORDER FILLED’ for orders that did not execute, and which wallet held the 275 dollars of the Firefly order form of 2026-06-14

Whether DG3’s app showed ‘ORDER FILLED’ for orders that did not execute, and which wallet held the 275 dollars of the Firefly order form of 2026-06-14.

The record cannot answerAll handles and the apps

What the 650 dollars from PolyHelper were for, and whether the two livestreams said so; the videos were not examined

What the 650 dollars from PolyHelper were for, and whether the two livestreams said so; the videos were not examined.

The record cannot answerAll handles and the apps

The label state of posts made from 2026-03-01 to 2026-08-08 is unknown

Archived posts of the apps’ own accounts made after 2026-08-09 embed the posts they quote with their flag: @thefireflyapp and @bagel_win were partly searched, @DG3_terminal (715 captures) and @Poly_Helper not. 5,308 in-scope captures since 2026-08-08 are not yet read.

The record cannot answerAll handles and the apps

Who holds the heavy accounts: the 33 Firefly prize-receiving wallets, PolyHelper’s largest account 0xb687f00464e33934f5d591f224e71c3559ecaee5 and DG3’s September account 0x5a2751e8d2c31b45c0ab96663f17e71548933404 (deposit trails not followed)

Who holds the heavy accounts: the 33 Firefly prize-receiving wallets, PolyHelper’s largest account 0xb687f00464e33934f5d591f224e71c3559ecaee5 (opens in a new tab) and DG3’s September account 0x5a2751e8d2c31b45c0ab96663f17e71548933404 (opens in a new tab) (deposit trails not followed).

The record cannot answerAll handles and the apps

Whether Polymarket’s weekly reward counts DG3’s September round trips: no round for those epochs had been sent by 2026-10-02 (the last round, of 2026-09-15, is for the epoch of 2026-08-30)

Whether Polymarket’s weekly reward counts DG3’s September round trips: no round for those epochs had been sent by 2026-10-02 (the last round, of 2026-09-15, is for the epoch of 2026-08-30).

The record cannot answerAll handles and the apps

Why the weekly rounds stopped paying PolyHelper after the epoch of 2026-06-14, and what the 1.00 and 2,012.50 USDC.e sent directly on 2026-09-24 were for

Why the weekly rounds stopped paying PolyHelper after the epoch of 2026-06-14, and what the 1.00 and 2,012.50 USDC.e sent directly on 2026-09-24 were for.

The record cannot answerAll handles and the apps

Round sums from unidentified senders reached @_kate_lv’s owner key (100, 100, 200 and 199.98 between 2026-03-28 and 2026-04-09; 513.12 on 2026-06-10; 2,455.09 on 2026-08-28; 60 on 2026-09-29)

The sender of the 60 USDC, 0x8d8efac8308440dbd106d143e06d6d35e21c40e3 (opens in a new tab), also sent 150 USDC to the exchange address used by @gusik4ever’s profile lolxdkek on 2026-05-09: one sender, two handles’ addresses, not identified or followed.

The record cannot answerAll handles and the apps

What the 500.00 USDC.e from a key on Tailgate’s side into the account behind @_kate_lv’s Tailgate posts (2026-04-01) was for: a trading credit or pay

What the 500.00 USDC.e from a key on Tailgate’s side into the account behind @_kate_lv’s Tailgate posts (2026-04-01) was for: a trading credit or pay.

The record cannot answerAll handles and the apps

The 900.72 PUSD of self-referral from the earlier exchange (854.20 @0xBumblebee, 46.52 @gusik4ever) and 33 of the 35 fee-day scans behind the referred accounts were not repeated

The 900.72 PUSD of self-referral from the earlier exchange (854.20 @0xBumblebee, 46.52 @gusik4ever) and 33 of the 35 fee-day scans behind the referred accounts were not repeated.

The record cannot answerAll handles and the apps

Whose exchange account sent the weekly paired transfers and the pair of 2026-10-01 into the two Bagel accounts: the holders’ own withdrawals or a weekly payment by a third party

The public record cannot tell; Bagel is a reading without a receipt.

The record cannot answerAll handles and the apps

What the DG3 and Firefly payments to the handles were for: a fixed fee under DG3’s affiliate programme, a per-referral payout, a discretionary tip or a creator fee cannot be told apart on chain

What the DG3 and Firefly payments to the handles were for: a fixed fee under DG3’s affiliate programme, a per-referral payout, a discretionary tip or a creator fee cannot be told apart on chain.

The record cannot answerAll handles and the apps

Whether Firefly’s loader and hub are held by the app’s team or by an agent running its campaigns, and who the prize wallet’s largest funder 0xafd13cbdb9e1b19431872e63867a57789884e945 is

Whether Firefly’s loader and hub are held by the app’s team or by an agent running its campaigns, and who the prize wallet’s largest funder 0xafd13cbdb9e1b19431872e63867a57789884e945 is.

The record cannot answerAll handles and the apps

Whether the badges of @_kate_lv, @gusik4ever, @itskkoma and @vadim_kesha1 were off for some days in early August 2026: no archived post object carries the label field before 2026-08-09 03:30 UTC

Whether the badges of @_kate_lv, @gusik4ever, @itskkoma and @vadim_kesha1 were off for some days in early August 2026: no archived post object carries the label field before 2026-08-09 03:30 UTC.

The record cannot answerAll handles and the apps

Whether X’s paid-partnership label was set on posts made between 2026-03-01 and 2026-08-08, including the 34 same-day campaign posts: no later capture of those posts exists

Whether X’s paid-partnership label was set on posts made between 2026-03-01 and 2026-08-08, including the 34 same-day campaign posts: no later capture of those posts exists.

The record cannot answerAll handles and the apps

Whether the unflagged app posts since 2026-08-09 (for example @gusik4ever’s nine Bagel posts) were paid: the X record cannot show it; only the payment entries could

Whether the unflagged app posts since 2026-08-09 (for example @gusik4ever’s nine Bagel posts) were paid: the X record cannot show it; only the payment entries could.

The record cannot answerAll handles and the apps

What Polymarket pays X for its affiliation badges, and whether any badge holder of this story is paid for the badge

What Polymarket pays X for its affiliation badges, and whether any badge holder of this story is paid for the badge.

The record cannot answerAll handles and the apps

The weekly pool and formula of the builder rewards, and who was accepted into the Dub affiliate programme

The weekly pool and formula of the builder rewards, and who was accepted into the Dub affiliate programme.

The record cannot answerAll handles and the apps

Why the referral payouts fell by about 96% on 2026-07-08, six weeks after the documented date of the new terms

Why the referral payouts fell by about 96% on 2026-07-08, six weeks after the documented date of the new terms.

Not connectedThe connected map

No single paymaster: the money comes from Polymarket’s programmes, DG3, Firefly, Bagel and PolyHelper, and the wallets of different apps never paid each other.

Not connectedThe connected map

Shared public infrastructure connects nobody: the batch-payment contract is the public Disperse tool, and the payers’ trails end at exchanges.

Not connectedThe connected map

No account of one handle’s group filled another group’s order, and buying both outcomes across accounts was not found for @itskkoma and @0xBumblebee.

Not connectedThe connected map

Two-sided betting was tested for @vadim_kesha1 and @0xd1namit and not found; the CryptoKesha account is not a leg of another handle’s pairs.

Not connectedThe connected map

Two-sided betting between @gusik4ever’s accounts was tested and not found.

Not connectedThe connected map

Two-sided betting between @itskkoma’s accounts was tested and not found.

Not connectedThe connected map

Two-sided betting between @0xBumblebee’s accounts was tested and not found.

Not connectedThe connected map

The handles answer each other daily, but as part of a mass-reply habit: 3.0% of @_kate_lv’s answers in 125 days went to the other five handles. That is no connection of money or keys.

Not connectedThe connected map

The sender of the paired weekly transfers into the two Bagel accounts is not known: they came from exchange hot wallets, and whose exchange account sent them is not on the chain.


Every wallet

The wallet list

Every address on this page, printed in full, with what the records show about it, how it is tied to a handle or an app, and its explorer page.

Loading the wallets…


Glossary

The words used on this page

Owner key
The address that signs for a Polymarket account. A Polymarket account is a small contract wallet; its owner key is the address allowed to move its money.
Deposit address
An address that forwards whatever it receives into one Polymarket account. Who pays into it is on chain.
App wallet
A Polymarket account created by an app for its user. It has no public profile; the app shows its own slips and cards.
Builder code
The tag an app puts on every order it routes to Polymarket. It says which app routed the order, not who typed it.
Opposite pair
Two accounts of one group holding the two opposite outcomes of one market in matching size at the same time. Whichever side wins, one leg loses.
Share
The unit traded on Polymarket. A share of the winning outcome pays one dollar; a share of the losing outcome pays nothing.
Paid-partnership label
A flag X lets an account set on a post to mark it as paid promotion. This page states it only for posts from 2026-08-09 on; for earlier posts it treats the label as not readable.
Affiliation label
The small badge of an organisation next to an account’s name on X.
Grade
How firmly a tie or a payment is established: proven (it can be re-read from the primary records), strong (several independent indicators, alternatives tested) or candidate (a real signal with alternatives open).
Internet Archive copy
A stored copy of a page or post at web.archive.org, taken at the time printed in its address. It shows what the page said at that moment.

Check it yourself

Every claim here links to a public record

Nothing on this page needs to be taken on trust. Download the tables, open the explorers, read the archived posts.

Three ways to check a claim

  1. Open any transaction link. The explorer shows the sender, the receiver, the token, the amount and the time, to the second.
  2. Open any post. Each links to its address on X and to the Internet Archive copy made while it was up. A deleted post is marked; X now reports it as deleted.
  3. Read an account. Each address is printed in full in the wallet list above, with its explorer page and, where it has one, its Polymarket profile.

When each record was read

  • @_kate_lv. The latest reading behind the live figures of these chapters. 1 Oct 2026, 00:00 UTC
  • @itskkoma. The latest reading behind the live figures of these chapters. 2 Oct 2026, 00:00 UTC
  • @gusik4ever. The latest reading behind the live figures of these chapters. 1 Oct 2026, 19:00 UTC
  • @0xBumblebee, @vadim_kesha1, @0xd1namit, @aenews. The latest reading behind the live figures of these chapters. 1 Oct 2026, 00:00 UTC
  • The platform, the apps and X. The latest reading behind the live figures of these chapters. 2 Oct 2026, 00:00 UTC