Moneyline
$49 Vol


$49 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
$0 Vol
| Event | Pick | Stake | Potential | Status |
|---|---|---|---|---|
| Counter-Strike: MORROW vs Invicta (BO3) - European Pro Leagu | Invicta | $500.00 | $1,041.67 | OPEN |
| Counter-Strike: FURIA vs FaZe (BO3) - IEM Beijing Group A | FaZe | $700.00 | $2,153.85 | OPEN |
| Counter-Strike: MOUZ vs TYLOO (BO3) - IEM Beijing Group B | TYLOO | $900.00 | $13,846.15 | OPEN |
| Counter-Strike: MASONIC vs MASQ (BO1) - Dust2.dk Ligaen Regu | MASQ | $400.00 | $1,428.57 | OPEN |
| Counter-Strike: Vitality vs Team Falcons (BO3) - BLAST Rival | Team Falcons | $500.00 | $1,562.50 | OPEN |
| Counter-Strike: Legacy vs FURIA (BO3) - BLAST Rivals Group A | Legacy | $400.00 | $1,194.03 | OPEN |
| Counter-Strike: DNK vs Wingman (BO3) - Exort Fiesta Group St | DNK | $100.00 | $215.05 | OPEN |
| Counter-Strike: Pandaric eSports vs BLUEJAYS.de (BO3) - DACH | Pandaric eSports | $100.00 | $588.24 | OPEN |
| Counter-Strike: Playing Ducks vs Huskies eSport (BO3) - DACH | Huskies eSport | $1,000.00 | $3,278.69 | OPEN |
| Counter-Strike: Growth Lab Esports vs Honvéd (BO1) - ESEA Ad | Growth Lab Esports | $900.00 | $1,666.67 | OPEN |
Comments
What about adding a Withdrawal Whitelist option in account settings?
Users could enable it and register trusted wallet addresses. Withdrawals to those addresses would work instantly, as usual.
However, adding a new wallet address or disabling the whitelist would trigger a mandatory 24-hour cooldown before withdrawals to new addresses become possible.
Users could also receive email notifications whenever someone tries to change these settings.
This would give users an extra layer of protection without affecting normal trading or withdrawals to trusted wallets.
Of course, the restriction would need to be enforced independently of the website's frontend to prevent malicious scripts from bypassing it.
I believe this could have significantly reduced the impact of yesterday's attack.
Just an idea! Would you mind forwarding this suggestion to your security or product team? Thanks!
Hide post
This comment will be hidden from your feed.