CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Blockchain & Web3

⛓️ Blockchain & Web3 Β· Deployment Β· Pro

Web3 dApp Deployment

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.

More Blockchain & Web3 templates

Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.

Drawing diagram…

What this diagram shows

  • The frontend is hosted on IPFS and served through a gateway
  • Contracts run on a layer-2 network for low fees
  • An indexer makes on-chain data fast to query

Prompt used

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.

Mermaid code
flowchart TB
  U[User with Wallet] -->|"HTTPS / ENS lookup"| GW[IPFS Gateway and ENS name]
  subgraph IPFS[IPFS Network]
    FE[React Frontend - pinned]
  end
  GW -->|"Static app from IPFS"| 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 -->|"JSON-RPC over HTTPS"| RPC
  RPC -->|"Signed transactions"| C1
  RPC -->|"Signed transactions"| C2
  SG -.->|"reads events"| C1
  FE -->|"GraphQL queries"| SG
  NOTIF -->|"Event queries, GraphQL"| SG

Inside this diagram

A deployment diagram with 8 components in 4 environments and 8 connections.

Environments and what runs in them

  • IPFS Network: React Frontend - pinned
  • Arbitrum Layer-2: Vault Contract and Token Contract
  • The Graph: Subgraph Indexer
  • Cloud VM: Notification Service

Outside these environments

  • User with Wallet
  • IPFS Gateway and ENS name
  • RPC Provider

Connections

  • User with Wallet β†’ IPFS Gateway and ENS name: HTTPS / ENS lookup
  • IPFS Gateway and ENS name β†’ React Frontend - pinned: Static app from IPFS
  • React Frontend - pinned β†’ RPC Provider: JSON-RPC over HTTPS
  • RPC Provider β†’ Vault Contract: Signed transactions
  • RPC Provider β†’ Token Contract: Signed transactions
  • Subgraph Indexer β†’ Vault Contract: reads events
  • React Frontend - pinned β†’ Subgraph Indexer: GraphQL queries
  • Notification Service β†’ Subgraph Indexer: Event queries, GraphQL

Make your own diagram like this

Describe your own system in plain English and the AI cloud architecture diagram generator draws it in seconds, in the same style as this template.

Related templates

C4 ArchitectureProBlockchain & Web3

Crypto Exchange Architecture

The main parts of a centralised crypto exchange: a matching engine, wallets split between hot and cold storage, deposits and withdrawals, and compliance checks.

SequenceBlockchain & Web3

Crypto Withdrawal Sequence

How an exchange processes a crypto withdrawal safely: balance hold, 2FA, risk and address screening, signing, broadcast and confirmations.

C4 ArchitectureProBlockchain & Web3

NFT Marketplace

How an NFT marketplace works: listings signed off-chain, metadata on IPFS, and sales settled by a marketplace smart contract.

FlowchartBlockchain & Web3

Smart Contract Upgrade Process

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.

State MachineBlockchain & Web3

Blockchain Transaction States

The states a blockchain transaction goes through from signing to final confirmation, including replacement and dropped transactions.

NetworkBlockchain & Web3

Hot and Cold Wallet Custody

How a custodian separates internet-connected hot wallets from offline cold storage, with signing hardware and an air-gapped transfer process.