DApp browser
A DApp browser inside the wallet
Open Web3 applications inside DWD Wallet with an EIP-1193 provider already connected.
What it does
The built-in browser opens Web3 applications without sending you to an external browser. A wallet provider is injected into the page, so a DApp can request an account and a signature the same way it would in a desktop wallet.
- In-app browsing — open a DApp URL inside the wallet.
- Provider injection — the page gets an EIP-1193 compatible provider.
- Explicit approvals — connection and transaction requests appear in the app for confirmation.
- ETH asset prerequisite — enable the ETH asset before using DApps.
How to use it
- Enable the ETH asset if you have not already.
- Open the DApp browser and enter the site address.
- Connect the site and review the account request.
- Approve or reject each transaction request in the app.
Boundaries worth knowing
- DApps are third-party code. A connection is not an endorsement and does not make a contract safe.
- Read every request: unlimited token approvals and unfamiliar contracts are worth rejecting.
- A DApp may work differently on mobile; some interfaces are not designed for a small screen.
- Clearing the app’s data or switching accounts disconnects the site.
A safer pattern
Use a separate account for new DApps, keep only what you need in it, and move funds back to your main account when you are done.
Questions
Why do I need to enable ETH first? +
The DApp provider uses the Ethereum-compatible account. The app asks you to enable the ETH asset before using DApps.
Does every DApp work? +
No. A DApp must support the provider the app exposes. Sites built for a different wallet or chain may not connect.
Are DApps reviewed by DWD Wallet? +
No. DApps are third-party applications. Connecting a site does not mean it is safe or endorsed.