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
What the Firefly-attributed loader payments (1,500 USDC) were for, and who runs the wallet that sent 550 PUSD into the Parity account
What the Firefly-attributed loader payments (1,500 USDC) were for, and who runs the wallet that sent 550 PUSD into the Parity account.
The record cannot answer@_kate_lv
The ‘vision wallet’ (2026-07-22) and the ‘side wallet’ the handle named are not identified: pair counts and World Cup totals are lower bounds
The ‘vision wallet’ (2026-07-22) and the ‘side wallet’ the handle named are not identified: pair counts and World Cup totals are lower bounds.
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@_kate_lv
Whether X’s paid-partnership label was set on the handle’s app posts before 2026-08-09 cannot be read
Whether X’s paid-partnership label was set on the handle’s app posts before 2026-08-09 cannot be read.
The record cannot answer@_kate_lv
The recap tool’s Bagel figure (-$210.34 against -$633.18 by fills) is not reconciled
The recap tool’s Bagel figure (-$210.34 against -$633.18 by fills) is not reconciled.
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
When the reply of 2026-08-03 and the post of 2026-03-30 were removed (only windows are known)
When the reply of 2026-08-03 and the post of 2026-03-30 were removed (only windows are known).
The record cannot answer@itskkoma
Whether the transfers of 2026-09-28 were a theft; the chain cannot show who held the key
Whether the transfers of 2026-09-28 were a theft; the chain cannot show who held the key.
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
Which wallet stands behind the ‘available’ balances on the Firefly order screens (213 to 1,400 dollars)
Which wallet stands behind the ‘available’ balances on the Firefly order screens (213 to 1,400 dollars).
The record cannot answer@gusik4ever
What subscriber-only posts said (the challenge and the picks were announced as going there in full); they are not public
What subscriber-only posts said (the challenge and the picks were announced as going there in full); they are not public.
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
Whether @0xBumblebee knew that the two credits of 292.80 of 2026-04-18/19 were referral rewards earned on Uiom’s fees
Whether @0xBumblebee knew that the two credits of 292.80 of 2026-04-18/19 were referral rewards earned on Uiom’s fees.
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
Who the round-amount payers of @0xBumblebee are (1,688 dollars) and whether they are pay at all
Who the round-amount payers of @0xBumblebee are (1,688 dollars) and whether they are pay at all.
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
Who holds the account lovep
Who holds the account lovep.
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
Whether the payments-provider runs are Polymarket affiliate payouts
Whether the payments-provider runs are Polymarket affiliate payouts.
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
Router blind spot: DG3 paid some recipients through a swap router, so the token sender is a pool and sender-based ledgers miss the payment
The same may hold for other payers; Firefly’s wallets have not been tested for it.
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
9,638.95 USDC in 8 small batches of the Combo Cup account is not explained, and the official Combo Cup rules page could not be retrieved
9,638.95 USDC in 8 small batches of the Combo Cup account is not explained, and the official Combo Cup rules page could not be retrieved.
The record cannot answerAll handles and the apps
34 payees of the Builders Program batches (362,181.36 USDC.e) do not join to Polymarket’s builder directory
34 payees of the Builders Program batches (362,181.36 USDC.e) do not join to Polymarket’s builder directory.
The record cannot answerAll handles and the apps
Who runs the seven plain wallets outside the four apps that pay several of the apps’ payees
Who runs the seven plain wallets outside the four apps that pay several of the apps’ payees.
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.
The record cannot answerAll handles and the apps
Whether the parameter c=00z00ykj in @vadim_kesha1’s perps link is a personal code
Whether the parameter c=00z00ykj in @vadim_kesha1’s perps link is a personal code.
The record cannot answerAll handles and the apps
When @itskkoma’s reply of 2026-08-03 18:19 UTC was removed (known only as a window ending 2026-10-01)
When @itskkoma’s reply of 2026-08-03 18:19 UTC was removed (known only as a window ending 2026-10-01).
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.