
⛓️ Blockchain & Web3 · Deployment · Pro
Where a decentralised app's parts run: frontend on IPFS, contracts on a layer-2 chain, and supporting services like RPC providers and an indexer.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Deployment of a Web3 dApp: the React frontend is built and pinned to IPFS and served via a gateway and ENS name. Users' wallets send transactions to contracts on a layer-2 network (Arbitrum) through an RPC provider. A subgraph indexer (The Graph) reads contract events and serves GraphQL to the frontend. A small backend on a cloud VM sends notifications.
flowchart TB
U[User with Wallet] --> GW[IPFS Gateway and ENS name]
subgraph IPFS[IPFS Network]
FE[React Frontend - pinned]
end
GW --> FE
subgraph L2[Arbitrum Layer-2]
C1[Vault Contract]
C2[Token Contract]
end
RPC[RPC Provider]
subgraph GRAPH[The Graph]
SG[Subgraph Indexer]
end
subgraph CLOUD[Cloud VM]
NOTIF[Notification Service]
end
FE --> RPC
RPC --> C1
RPC --> C2
SG -.reads events.-> C1
FE --> SG
NOTIF --> SGThe main parts of a centralised crypto exchange: a matching engine, wallets split between hot and cold storage, deposits and withdrawals, and compliance checks.
How an exchange processes a crypto withdrawal safely: balance hold, 2FA, risk and address screening, signing, broadcast and confirmations.
How an NFT marketplace works: listings signed off-chain, metadata on IPFS, and sales settled by a marketplace smart contract.
How a team safely upgrades a smart contract behind a proxy: audit, testnet rehearsal, multi-signature approval and a timelock before the change goes live.
The states a blockchain transaction goes through from signing to final confirmation, including replacement and dropped transactions.
How a custodian separates internet-connected hot wallets from offline cold storage, with signing hardware and an air-gapped transfer process.