How does desktop activation work?
The intended flow starts with the installed desktop app. You authenticate and approve web access, then return to the browser. A verified session is required before wallet data or authorized functions become available.
Why use both desktop and web?
Desktop provides the authentication and approval step. The web workspace provides a convenient place to review assets, collectibles and activity for the connected account.
Does opening the app sign me in?
No. App availability, authentication and transaction approval are separate steps. Opening the app or returning to the website does not by itself establish an authenticated session.
Which assets and networks are supported?
The connected release and its integrations determine support. Check the available network, asset contract and permitted actions in the authenticated workspace; a familiar ticker alone is not enough.
Can I enter a recovery phrase on the website?
No. Never enter recovery phrases or private keys here. Use the recovery process provided by your verified desktop release.
Is the desktop-to-web connection live here?
The website describes the product workflow. Desktop authentication, callback verification and live asset access still require the production integration. The current connection check cannot grant web access.
