Loading Vitality…
Loading Vitality…
Provider architecture, secure authentication boundaries and account-readiness in one operational view.
What can I do here, and what remains outside wallet authentication?
Wallet guidance is always available. Browser wallet connection and server-issued SIWE are available only when the wallet-auth runtime gate is enabled. Balance reads, transactions, contract calls, authorization and entitlement remain outside this authentication surface.
Wallet guidance is always available; connection and server-issued SIWE follow the explicit wallet-auth runtime activation gate.
When the runtime gate is disabled, wallet connection and SIWE are unavailable. Even when enabled, authentication does not activate balances, transactions, authorization, entitlement or economic execution.
Production wallet authentication remains subject to approved architecture, supported-network policy, security validation and explicit runtime release controls.
Explain wallet connection status, server-authoritative authentication boundaries and safety prompts from one controlled place.
Show browser-wallet preparation, exact-provider guidance and the runtime activation boundary without implying authorization or entitlement.
Keep the route clear that wallet authentication proves wallet control only and does not activate balance reads, transactions, authorization, entitlement or treasury actions.
Read the static purpose, official-source, and safety guidance without connecting a wallet.
Wallet connection and SIWE can operate only when the wallet-auth runtime gate is enabled; static page copy does not declare the live runtime state.
Any future wallet activation requires separately approved architecture, testing, warnings, and release controls.
Wallet connection and SIWE are runtime-gated.
Wallet authentication proves wallet control only.
No authorization or entitlement is granted by wallet authentication.
No balance read, transaction, contract mutation or treasury action is activated by this surface.