Skip to main content
Version: Current guides

Connect to DApps and review signatures

Before connecting​

A DApp is a third-party website. A recommendation, connection or app icon does not guarantee its safety. Connecting exposes an authorized address to the site. Signatures, token approvals and transactions have different consequences; they are not all simply “signing in.”

Connect in the built-in browser​

If your current version provides this entry, open a DApp from Discover or enter a verified URL.

  1. Check the complete domain. Watch for similar spellings and unfamiliar redirects.
  2. Select a specific browser network. All networks cannot execute a transaction. The browser network can be independent of the Home asset filter, so Home alone does not establish the site's network.
  3. When the site requests a connection, review the site and account list and choose the account you want to expose.
  4. Check the address and network displayed by the site before proceeding. A site may retain a previously authorized account rather than following Home account changes.
  5. After switching tabs, networks or addresses, review outstanding requests again. Do not approve an old prompt that no longer matches the current page.

If multiple tabs are available, they may share the browser network. Do not assume each tab has an independent network or that all tabs and forms will return after leaving the browser.

Review a signature or transaction request​

RequestWhat to inspect
Account connectionSite domain and address being exposed; it is not permission to transfer assets
Message signatureThe full message and purpose; even without network fees, a signature may grant permissions
Token approvalSpender, token and allowance; permission for later use is not a completed payment
TransactionNetwork, paying account, destination, amount, fees and understandable call details

Reject a message, allowance or call whose purpose you do not understand. Never enter a seed phrase, private key or unlock password into a webpage. Unlock only through the app's own verification interface. Typed signatures, external-wallet signing and automatic website network changes depend on actual version support. A successful connection does not establish support for every method.

Disconnect and troubleshoot​

If your version provides Connected sites, find the site in settings, check its account and disconnect. Choose the account again when reconnecting. Disconnecting does not revoke existing on-chain approvals or transactions. To manage token allowances, use a verified method compatible with that network.

For loading failures, check connectivity and the domain. If the unlock session expired, unlock in the app and let the site request again. If an external or read-only account cannot sign in the built-in browser, use a supported account and connection method rather than exporting a key to the site. If a webpage errors after submission, check the hash and transaction records instead of repeatedly paying.