Wallets and networks
Connecting, network validation and what EXDATE never asks for.
EXDATE discovers installed wallets through EIP-6963, so every wallet in the browser is listed by name rather than competing for a single injected provider. A legacy injected provider is offered as a fallback.
What connecting shares
Connecting requests your accounts and reads the connected chain id. Nothing else is requested.
EXDATE does not request token approvals, message signatures, or transactions. Preview actions settle in local session state.
Network validation
The expected chain is read from environment configuration and validated against the chain your wallet reports. A network switch is only ever offered when complete, verified chain metadata is present: a chain id, an RPC endpoint and a native currency definition. Without those, EXDATE runs read-only rather than inventing a chain configuration.
Reading without connecting
Markets, event pages, baskets, the protocol and this documentation are fully available without a wallet. Connecting personalises the interface; it does not unlock it.