Public record

@vadim_kesha1

Posts, receipts and the limits of the evidence.

keshxBlue checkmark (X Premium subscription) @vadim_kesha1

Polymarket Sports3,318 followers

obsessed with polymarket cs2 + crypto notes tg: cryptovadym

X (opens in a new tab)

Calls a FaZe win the start of its Polymarket journey, but the profile was funded from an older account then about $5,000 down.

  • Several accounts
  • Paid by apps it promoted
  • Cards without a matching trade
  • Labels some paid posts

@vadim_kesha1 says its Polymarket journey started with a $3,098 bet on FaZe. That profile was funded from an older account that was about $5,000 down. Wallets attributed to DG3 and Firefly paid $1,250 to an address its account withdraws to while it promoted both apps. Since August 2026, three of its seven DG3 posts carry X’s paid label.

In fairness

It marked three of its seven DG3 posts since August 2026 as paid partnerships, and wrote ‘when unsure, add paid partnership’.

It later wrote ‘i ended up down $13,000’. The older account is public and carries a near-identical name.

Show the record4 points and their sources

What the record shows

  1. 1It calls a $3,098 bet on FaZe, which won, the start of its Polymarket journey. The profile had been opened ten minutes before, with money from an older account then about $5,000 down.

    Image @vadim_kesha1 postedSee it whole
    View on X (opens in a new tab)Archived copy (opens in a new tab)

    The FaZe bet on its profile, as it posted it.

    3 more sources

  2. 2Wallets attributed to DG3 and Firefly paid $1,250 to an address its Polymarket account withdraws to, while it promoted both apps with its own links. No post says a payment came in.

    Post by @vadim_kesha1 on X, 1 July 2026See it whole
    View on X (opens in a new tab)Archived copy (opens in a new tab)

    One of its DG3 posts with its link, 2026-07-01.

    6 more sources

  3. 3On 2026-09-02, 52 minutes after DG3’s wallet sent $250 to that address, it posted ‘starting with $100 today’. The $100 came out of the $250. X’s paid-partnership label was not set.

    Image @vadim_kesha1 postedSee it whole
    View on X (opens in a new tab)Archived copy (opens in a new tab)

    The DG3 card in that post.

    2 more sources

  4. 4Two DG3 cards it posted with its link read ‘ORDER FILLED’. No matching trade was found: the money sat in its DG3 wallet until withdrawn. Whether the app misfired cannot be told; both picks won.

    Image @vadim_kesha1 postedSee it whole
    View on X (opens in a new tab)Archived copy (opens in a new tab)

    The two cards, posted on 2026-07-01 and 2026-07-11.

    5 more sources
    • Image @vadim_kesha1 posted

Accounts tied to @vadim_kesha1

Payments received

Deleted posts, for example

keshx@vadim_kesha1 · 1 Jul 2026
Deleted
XSE Pro League has started, and we already have another interesting CS2 match PARIVISION vs Alliance my pick: PARIVISION at ~63¢ i wouldn’t call it free money, because BO1 can always get chaotic, but their roster looks serious: Slaxejezzz + Hobbit already look fired up @DG3_terminal makes it easier to quickly check everything in one place jump in through my link: https://t.co/HuXb5pmULl
The post on X (deleted) (opens in a new tab)Archived copy (opens in a new tab)
keshx@vadim_kesha1 · 12 Feb 2026
Deleted
finally 💙 official: I'm a Polymarket sports affiliate. Big thanks to @PolymarketSport ! You’re really changing how people watch esports. https://t.co/jSv4LdZghL
The post on X (deleted) (opens in a new tab)Archived copy (opens in a new tab)

Everything that must be said with these points

  • The FaZe bet and its result are real, and the stake was money that had reached cryptokesh three hours earlier, not the remains of the earlier bankroll.
  • The earlier account is public and not disguised: its name and the X username shown on its profile (crypto_kesha) are the alias the handle has used in public since 2024 (referral code, video channel). That username belongs to another X account than @vadim_kesha1, which was not examined.
  • That one operator runs both accounts is strong, not proven: no key signs for both; the tie is the declared funding route 83 seconds after creation, payments in both directions afterwards, one exchange deposit address (0x8d24b2266f499a3b62b9234fc1128e69bfa89916) used by both accounts and by the cryptokesh owner key, and gas sent between the two owner keys.
  • Opening a second account breaks no rule shown here.
  • The handle later stated its loss in public (reply of 2026-03-25: ‘i ended up down $13,000’), and the CryptoKesha profile itself shows a loss of about 30,000 dollars (Polymarket’s figure: -30,243.88).
  • CryptoKesha is not a hedge leg of another handle’s book.
  • What the payments were for is not on the chain.
  • The receiving address is tied to the handle by money in both directions with the CryptoKesha account (the cryptokesh owner key sent it 2,895.32; CryptoKesha withdrew 12,800.00 to it; it paid the CryptoKesha deposit address 3,568.99 on Base and 14,709.76 on BNB chain) and by the handle’s own post of 2026-09-02, whose 100 dollars came from it; no key signs for both.
  • DG3 publishes a referral programme that pays 50 dollars per referred trader, monthly, in USDT on Polygon, and all four DG3 payments are multiples of 50; Firefly published prize pools with social rewards for sharing. Receiving such income is ordinary.
  • The handle’s links are shown as its own (‘jump in through my link’), one post describes the DG3 affiliate programme to readers, and the handle wrote on 2026-03-05 ‘when unsure, add paid partnership’.
  • X’s label can be read from public data only from 2026-08-09, so for the Firefly posts of June and the DG3 posts of June and July it is not known whether it was set.
  • The paying Firefly wallets are identified as Firefly’s with grade strong, the DG3 wallet with grade proven. The sums are small next to the account’s deposits (over 100,000 dollars).
  • The 170 of 2026-06-11 was the last transfer of a Firefly pay run that also paid @0xBumblebee.
  • Whether the app showed its success screen for an order that did not execute, or the screenshot was posted knowing there was no position, cannot be told from the record; a failed first order from a wallet funded 21 minutes earlier would fit the first card.
  • Both picks won, so the handle gave up a profit by not holding them and nobody who followed the calls lost. The sums are 49.86 and 99.59 dollars.
  • Four other DG3 posts of the handle are backed by fills of the same wallet.
  • On 2026-07-11 the buy of 9z came 67 minutes after the post, during the map, after the market had gone from about 50c for Alliance to above 95c and back to about 50c; the replies in which the handle stood by the pick were written within half an hour of the post, before that. The post was not updated.
  • A third, weaker instance, not established: on 2026-06-14 the handle wrote ‘I took Belgium on @thefireflyapp: $200 to win $327.86’ above a picture of a Firefly order form ($200, ‘$275 available’, 61c). No buy of that size routed through Firefly exists before the post, and none of the 17 buys of exactly 200 dollars at 61c came from a wallet holding about 275 dollars; the picture is an order form, not a confirmation, and a bet from a wallet not found here is not excluded. Belgium did not win.
  • The three Banana Gun cards the handle posted are backed by fills to the cent.
  • The label is the author’s own switch, and an unmarked post may be one the handle did not count as part of the deal.
  • What a transfer was for is not on the chain. DG3 announced on 2026-08-20 a referral programme that pays 50 dollars per activated trader, monthly, in USDT on Polygon; both payments of 250 came after that date and fit five such payments as well as a fee.
  • The referral code is in the link, and one unmarked post says ‘DG3 link’.
  • The handle wrote on 2026-03-05 ‘rule of the game: when unsure, add paid partnership’.
  • For its six DG3 posts and four Firefly posts of June and July 2026 the post text carries no words of disclosure and whether X’s label was set cannot be read; two of them say ‘jump in through my link’.
  • The address is tied to the handle by declared withdrawals of its profile; who holds its key is not shown.