Design review · Section 3 of 4

The live demo as a three-act story

The audience sees every command, every test, and every state transition. The operations console mirrors the chain without controlling it.

Act 1 · Prepared V1

Establish trust

make demo-v1
  1. Deploy MockUSDC, BankV1, and proxy
  2. Mint demo funds to Alice and Bob
  3. Deposit 1,000 + 500 USDC
  4. Alice withdraws 100 USDC
Console proves
Proxy: 0x8B…42
Version: V1
Reserves: 1,400
Liabilities: 1,400
→
Act 2 · Codex live

Change the system safely

Ask Codex to add customer-to-customer transfers while preserving all V1 state.
  1. Implement BankV2
  2. Add unit, fuzz, and invariant tests
  3. Add upgrade and transfer scripts
  4. Update ABI and console timeline
  5. Explain the storage-safety choices
forge test --force
No upgrade runs until tests and layout validation pass.
→
Act 3 · V2 reveal

Prove state survived

make upgrade-v2
make demo-transfer
  1. Owner upgrades proxy to BankV2
  2. Proxy address remains unchanged
  3. Alice transfers 250 to Bob internally
  4. No MockUSDC moves during transfer
Console proves
Alice: 900 → 650
Bob: 500 → 750
Reserves = liabilities = 1,400
Version: V2
Failure behavior
Optional public encore
✓

Demo sequence approved

Continue to testing, documentation, and presentation safeguards.

↺

Needs changes

Select this and describe what should change in the terminal.