Objective
Reduce first-run friction and prove end-to-end value transfer with cryptographic receipts before any advanced configuration.
Quickstart and Day-0 Experience
Production TrackFrom install to first receipt in minutes: initialize identity, boot services, run a complete self-banking scenario.
Install + Initialize
OpeniBank ships with a CLI bootstrap path designed for deterministic local startup. Initialization creates config, keys, genesis artifacts, and default wallet scaffolding.
Identity generation is local. Key material is never uploaded by default. The first-run workflow sets explicit trust boundaries before network features are enabled.
Start Services
Startup advertises dashboard, API, chain status, and agent runtime in one terminal status frame so operators can verify health at a glance.
The runtime keeps critical path services visible: banking engine, ledger persistence, receipt signer, and local market interfaces.
Run the 10-minute Demo
The default demo sequence mints test balance, establishes permit constraints, executes escrowed transfer, settles, and verifies the resulting receipt.
The outcome is not just UI animation. It confirms ledger invariants, commitment flow, and signed evidence of execution.
Interfaces
CLI
`openibank init`, `openibank start`, `openibank demo run`
Dashboard
Local status, wallet balances, activity feed, and receipt explorer
Production Checkpoints
- ✓First boot under 2 minutes on development hardware
- ✓Receipt verification succeeds on every demo transfer
- ✓Dashboard and API ports are discoverable from terminal status
- ✓No required cloud dependency for day-0 operation
Continue exploring