Networks and read modes
Keep chain identity, display reads, and wallet writes separate.
Network identity
| Network | Chain ID | Asset meaning |
|---|---|---|
| Sepolia | 11155111 | Test ETH/WETH; no monetary value |
| Ethereum mainnet | 1 | Real ETH/WETH |
The factory addresses are the same on the two included public deployments, but WETH, router, start block, RPC, explorer, and launch history remain network-specific. Always validate chain ID as well as address.
Two read modes
Direct RPC
The browser reads factory logs and contract getters from an RPC you configure. It is self-contained and needs no D17 server or database. HTTP handles first load and reconciliation; an optional RPC WebSocket reduces event latency.
Optional API
A local Node process indexes D17 lifecycle events into one JSON state file per network. The browser first loads complete REST snapshots, then uses an application WebSocket for notifications. REST reconciliation after reconnect or tab resume prevents missed notifications from becoming stale UI.
Transaction path
Both modes use the same transaction path:
browser form → wallet review/signature → Ethereum contractThe optional API is read-only. It has no write endpoint and never needs a wallet key.