Replying to @SamuelAdcock @Polymarket
All of my evidence is public. Check it yourself:
drive.google.com/drive/folde…
So here's my question, and it's the only one I need answered:
HOW WAS MY PRIVATE KEY REVEALED WHEN I NEVER LOOKED AT IT, AND THERE ARE ZERO
LOGS SHOWING IT REVEALED BEFORE THE ATTACK?
@Polymarket why are you silent?
Meanwhile 223,596.97 PUSD has sat untouched for over 50 hours:
0x826712fe1bc7b2B90D797168D5B992d2b5B4803C
Polymarket hold the upgrade key on the PUSD contract and control the gate that lets it be redeemed. They can act.
I've asked them to. They haven't.
So the question I still can't get answered:
When did my private key leave their provider's custody, and to whom?
If it was never revealed, it wasn't phishing. Something else happened.
@Polymarket @PolymarketHelp
I have never viewed or exported my private key.
I was targeted once before, and because of that I made a deliberate point of never revealing it — precisely so this couldn't happen.
It was custodied by their wallet provider. Never by me.
Laundering route:
Router 0xfb7C744DA69aef11DfB54F31D9dB12A3B086b025
(skims ~0.875% to 0xe3478b0BB1A5084567C319096437924948Be1964)
PUSD → USDC.e → USDT, bridged to BSC via @MayanFinance and @lifiprotocol / @AcrossProtocol
