A newly traced hub funds Kate’s recurring payer and a route into Wincy’s documented withdrawal endpoint. The original batch operator paid that endpoint four times. A separate August trail reaches Kate’s Safe owner.
Select a finding to open its route. The receipt table below follows your selection. Every amount keeps its token and chain; addresses remain visible beside their labels.
New connection / hub 0x8e50…18887
One distributor. Two branches.
The previously documented ring loader sent this hub 12,835 USDC in thirteen transfers. The hub then paid both Kate’s recurring payer and a second routing wallet. Its outgoing record also includes 400 USDC to the previously documented farm sender.
The hub paid the recurring payer 1,000 USDC on July 9. With no intervening USDC transfer in its complete history, the payer sent 1,000 USDC to Kate’s Safe owner on July 20. Historical balances reconcile both legs.
The other hub payments took a different path: the payer sent 999.895271 USDC on July 3 and 199.974384 USDC on August 20 to 0x6747…facb5. The full 2,200.005037 USDC is the amount paid to the payer wallet.
The second wallet has four token transfers: 200 in, 200 out; 650 in, 650 out. Both outgoing payments reached 0x7201…2e2d5 on Polygon. Pinned USDC balances read zero → 200 → zero and zero → 650 → zero.
The original operator paid the endpoint four times.
The earlier story recorded the June 10 payment of 150 USDT0. Three additional payments bring the verified total to 850 USDT0. The same operator signed all four transactions; two were direct token transfers and two used ClipperPayout.
In the June 10 transaction, ClipperPayout sent 175 USDT0 to Kate’s Safe owner at log 156, then 150 USDT0 to the endpoint at log 157. The previous-block Safe read returns that recipient as Kate’s sole owner.
The operator sent the tokens directly. The endpoint then transferred the full 275 USDT0 to the documented exchange sweep wallet. Its token balance reads zero before the deposit, 275 afterward and zero after the sweep.
At 11:41:12 UTC, the staging wallet sent 1,136.29 PUSD to a previously unlisted intermediary. Thirty seconds later, the converted amount reached Kate’s recurring payer as native USDC. At 11:48:12, the payer emptied its USDC balance into Kate’s Safe owner.
The request records 0xa51e…ac3b as sender and 0x75e8…f1ae9 as recipient. Its input and output transaction hashes, token contracts, chains and amounts all match the independently checked receipts.
The PUSD reserve’s transfer is the redemption step. Relay’s liquidity wallet performs the conversion’s settlement.
The staging wallet also appears in the verified Firefly order-attribution finding. This August route adds a new intermediary and a later payment to that existing record.
02 / Transaction desk
Open the transfer. Check the exact log.
Search a wallet, label, date, amount or transaction hash. Choose all routes to inspect the full 51-transfer Polygon record. The eight cross-chain withdrawal logs are in the next section and its download.
51 verified Polygon transfers in the full record
Time
From
To
Amount
Evidence
Previously documented ring loader0x1bd8425db3fcf8dbe6521ed24677e93a4657aeaf
New distribution hub0x8e50b06cbdd162dfaaa4e7b7449d06e9dc918887
No receipts match. Try another term or show all routes.
03 / The public identities
The handles. The profiles. The endpoint.
Polymarket’s public-profile responses explicitly return the X handles supplied for this investigation. A historical Safe read connects Kate’s profile wallet to the payment recipient. Relay connects Wincy’s named account to the withdrawal address.
@_kate_lv → katelv
Kate
Polymarket user 809850. The response lists _kate_lv, a verified badge and users[0].communityMod: true. Her profile wallet is 0xefbd…065fa.
At the blocks immediately before the cited June 10, July 20 and August 28 payments, getOwners() returns only 0x0275…a2ff9, with a signing threshold of one.
Polymarket user 3496988. The response lists gusik4ever and the profile wallet 0xd95f…6adfd.
Four successful Relay requests explicitly route that wallet’s Polygon USDC.e into 2,066.875670 USDC on Base at 0x7201…2e2d5. Both legs of each request were rechecked against raw receipts.
The identity of the exchange customer behind 0x7201…2e2d5 remains unresolved. The finding is repeated use of this exact address across the documented routes. The newly traced hub and intermediary are labeled by their transactions.
04 / The evidence bundle
Receipts first. Follow every step.
The wider refresh screened 114 published address / chain pairs and 38 public profiles. Of those feeds, 113 reached the requested start or the end of history. The five histories supporting the new routes are complete. Every published transfer passed a raw-receipt check.