dApp Frontends for Blockchain and Web3 Developers
A dApp frontend is the web interface that lets users interact with smart contracts. It connects to a wallet such as MetaMask, asks the user to approve and sign transactions, and reads chain data through a JSON-RPC provider using libraries like ethers.js, viem or wagmi. The wallet holds keys, so the page never sees a private key.
Stage: Applications · Part of the Blockchain and Web3 Developer roadmap · Last reviewed 19 November 2026
What to learn in dApp Frontends
- Connect a browser wallet and read the selected account and chain
- Send a contract write and show pending, confirmed and failed states
- Request an off-chain signature and verify it on a server
- Read contract state and logs through an RPC provider
- Handle a user switching networks or rejecting a request
dApp Frontends interview questions
What is the difference between signing a message and sending a transaction?
Signing a message produces a signature off-chain, costs no gas and changes no state, which suits login and approvals. Sending a transaction is broadcast to the network, pays gas and changes on-chain state when it is mined.
How does a dApp read data from a blockchain without a wallet?
It calls a node through a JSON-RPC provider, such as a hosted endpoint, using read-only methods like eth_call. No signature or gas is needed. For history across many blocks, apps usually query event logs or an indexer instead.
Where dApp Frontends fits in the Blockchain and Web3 Developer roadmap
dApp Frontends belongs to the Applications stage (intermediate level), which takes about 9 hours. From contract to product.
Other units in this stage
Back to the full Blockchain and Web3 Developer roadmap