Wallet connection lets AlphaNet identify the account interacting with the platform. The documented workflow separates connecting a wallet from enabling trading and depositing funds; connecting alone should not be confused with deploying a strategy.
Connection, authorization and transfer
A basic connection generally lets a site see the selected public address and associated public blockchain information. Additional signatures, approvals or transactions can grant further permissions or move assets. The exact request—not simply the presence of a wallet pop-up—determines what is being authorized.
For example, a request to view an account is materially different from a request allowing a contract to spend a token. Familiar branding does not make the two requests equivalent.
Security checks that matter
The site address, account, network and requested permissions should all be understandable before an authorization is accepted. A request that cannot be explained is a reason to stop and verify, not to proceed automatically.
A recovery phrase or private key should never be entered into an onboarding form or sent to support.
Supported networks and wallet behaviour can change. A connection that works on one network does not establish that every token or trading route is supported. AlphaNet’s maintained user guide describes its documented interface and supported flow.