Wallet-connect is becoming the default deposit route
Deposit flows on crypto betting sites have converged noticeably. A couple of years ago, many platforms layered a conventional account system, with email, password and a deposit address, on top of a blockchain backend. Increasingly, the wallet is the account. A visitor connects, the interface reads the balance and the first wager can be placed without a registration form.
The shift is driven by user expectation as much as by ideology. People who already hold assets in a browser wallet or a mobile app do not want to create another credential, and they do not want to move funds to an operator-controlled address just to place a bet. Self-custodial books such as Dexsport have built their onboarding around this assumption, and the pattern is spreading.
It changes the support model. There is no password to reset, but there is also no account recovery. A user who loses access to a wallet has lost access to the funds, and no help desk can restore them. Good interfaces now warn about this explicitly and encourage hardware wallets for larger balances, rather than burying the point in terms and conditions.
For operators, the trade-off is data. Wallet-only onboarding collects little personal information, which reduces compliance overhead in some respects and complicates it in others, particularly where licensing regimes expect identity checks. The direction of travel is clear enough: the wallet is becoming the front door, and the email form is becoming the exception.