What is dApp?
An application whose logic runs in smart contracts on a public blockchain rather than on a company's servers, with a website as the front end only.
Not yet verifiedHow we verify
3 min read
In this entry
An application whose logic runs in smart contracts on a public blockchain rather than on a company's servers, with a website as the front end only.
You connect a wallet instead of creating an account. There is no password, no signup, and no account recovery, because the application does not hold anything belonging to you. The contract keeps running even if the website disappears, and a flaw in it cannot be quietly patched away.
The word covers a very wide range of decentralization. Many applications called dApps have an upgradeable contract, an admin key, a centrally operated front end, and a hosted indexer, any one of which is a point of control. Reading a name as a guarantee is the mistake.
How it works
The split is between a front end and the contracts. The front end is ordinary web code, usually hosted on ordinary infrastructure and sometimes on ipfs. It builds transactions and hands them to your wallet to sign. It holds no funds and enforces no rules.
The contracts hold state and enforce rules, and they are the application in any meaningful sense. Anyone can interact with them directly, bypassing the website entirely, which is why a dApp can survive its own team disappearing.
Three points of centralization survive in most of them. An upgradeable contract lets the developer change the logic after deployment. An admin key can pause the contract, change fees, or move funds depending on what the code permits. And the front end is a normal website that can be taken down, seized, or replaced with a malicious copy.
The permission model is different from a web app in a way worth internalizing. Instead of granting an account access to your data, you grant contracts a token approval over your tokens, and that approval persists until revoked, long after you stop using the site.
Example
Illustrative. You visit a decentralized exchange, connect a wallet, and swap a token. Two transactions occur: an approval letting the router contract spend the token, and the swap itself. The website computed a route and presented it, and your wallet signed. If the site vanishes tomorrow, the tokens are still yours, the approval is still live, and someone controlling that router contract could still spend the approved amount. Revoking the approval is a separate transaction that most people never make.
Why it matters when you buy
Buying through a dApp requires you already to hold crypto for gas, so it is not usually a first purchase route. When it is relevant is for assets no centralized exchange lists, which the buyability grades show, and where a swap's cost is set by pool depth rather than an exchange fee, shown on the liquidity pages.
Related terms
smart contract — where the logic lives; token approval — the permission you grant and rarely revoke; dex — the most common category; upgradeable contract — the developer's remaining control; wallet drainer — the malicious version of the same signature flow.
Questions
Do I need an account?
No. Connecting a wallet proves you control an address, and there is no stored account, no password, and no recovery. Lose access to the wallet and there is no support channel that can restore it.
Is a dApp safer than an exchange?
It removes custody risk and adds smart contract risk, front-end risk, and the risk that you sign something you did not understand. Neither is strictly safer, and the failure modes are entirely different.
How do I know a dApp is what it claims?
Check the contract address against the project's own documentation and a block explorer, and confirm the contract is verified and audited. A polished interface is not evidence of anything.