Stake
Contents
Stake - REKT
They say the house always wins.
Not in crypto.
On-chain casino Stake lost over $41M from its hot wallets yesterday.
Suspicious transactions were initially flagged by Cyvers, with losses on mainnet of around $16M. Then came another round of transactions, with a further $25.6M lost on BSC and Polygon.
The platform took four and a half hours (or just three, according to Stake themselves) to publish an acknowledgment, despite managing to put out a tone-deaf promo tweet in the meantime.
However, the announcement fails to mention the transactions on Polygon, or address reports that user withdrawals are currently suspended.
After another four hours, the team tweeted again, informing users that deposits and withdrawals had resumed.
Surely $41M must be a drop in the ocean for Stake, with co-founder Bijan Tehrani earlier stating that there would be no impact on customer funds.
So why the delay, and the omissions, in official comms?
Credit: tayvano, PeckShield
Given that the transactions, …
They say the house always wins.
Not in crypto.
On-chain casino Stake lost over $41M from its hot wallets yesterday.
Suspicious transactions were initially flagged by Cyvers, with losses on mainnet of around $16M. Then came another round of transactions, with a further $25.6M lost on BSC and Polygon.
The platform took four and a half hours (or just three, according to Stake themselves) to publish an acknowledgment, despite managing to put out a tone-deaf promo tweet in the meantime.
However, the announcement fails to mention the transactions on Polygon, or address reports that user withdrawals are currently suspended.
After another four hours, the team tweeted again, informing users that deposits and withdrawals had resumed.
Surely $41M must be a drop in the ocean for Stake, with co-founder Bijan Tehrani earlier stating that there would be no impact on customer funds.
So why the delay, and the omissions, in official comms?
Credit: tayvano, PeckShield
Given that the transactions, …
IoC
3130662aece32f05753d00a7b95c0444150bcd3c
3C5c2F4bCeC51a36494682f91Dbc6cA7c63B514C
4464e91002c63a623a8a218bd5dd1f041b61ec04
fe3f568d58919b14aff72bd3f14e6f55bec6c4e0
3C5c2F4bCeC51a36494682f91Dbc6cA7c63B514C
4464e91002c63a623a8a218bd5dd1f041b61ec04
fe3f568d58919b14aff72bd3f14e6f55bec6c4e0