
⛓️ Blockchain & Web3 · Flowchart
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.
Drawing diagram…
Smart contract upgrade flowchart: write the new implementation, run unit and fuzz tests, get an external audit and fix findings, deploy to testnet and rehearse the upgrade, then propose it to the multi-signature wallet. When 3 of 5 signers approve, it enters a 48-hour timelock, then the proxy is pointed to the new implementation and monitored.
flowchart TD
A[Write new implementation] --> B[Unit and fuzz tests]
B --> C[External security audit]
C --> D{Critical findings?}
D -->|Yes| A
D -->|No| E[Deploy to testnet]
E --> F[Rehearse upgrade on testnet]
F --> G[Propose upgrade to multisig]
G --> H{3 of 5 signers approve?}
H -->|No| I[Upgrade not executed]
H -->|Yes| J[48-hour timelock]
J --> K[Point proxy to new implementation]
K --> L[Monitor events and balances]The 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.
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.
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.