OB
OpeniBank
Launch Terminal
TradeMarketsEarniBankerEcosystemDocs
GitHubLoginRegister
OB
OpeniBank

Trade like a fund. Bank like the future.

Product

  • Trade Terminal
  • Markets
  • Earn Vaults
  • iBanker Web
  • Mission Control
  • Desktop

Platform

  • Platform Overview
  • Markets
  • Nodes
  • Enterprise
  • Documentation
  • GitHub

Control

  • Organization
  • Receipts
  • Security Center
  • Settings
  • Wallet
  • Downloads

Trust

  • Local Portal Package
  • Validators
  • Docs
  • License (Apache 2.0)

© 2026 OpeniBank. Apache 2.0 License.

Built with Rust. Secured by cryptography. Powered by community.

Preview release: market data is live; execution, balances, and vault yields are simulated. Nothing on this site is an offer of banking, custody, or investment services, or financial advice. Digital assets are volatile — trade responsibly.

Docs/Self-Banking Engine/Wallet and Ledger Architecture

Wallet and Ledger Architecture

Production Track

Compartmentalized balances and journal-backed accounting enforce strict movement semantics across all value paths.

Objective

Guarantee that all wallet mutations are reconcilable, balanced, and scoped by explicit compartment intent.

System Context

Self-Banking Engine

Personal financial operating system with deterministic controls

View full system documentation

Compartment Model

Vault handles long-horizon reserves, Operational supports active spending, Escrow tracks pending settlement, and Delegated isolates agent-managed limits.

Each compartment keeps independent balances and policy hooks, enabling safer automation and least-privilege execution.

Double-entry Guarantees

All state transitions produce balanced debit/credit entries. There is no direct balance mutation outside journal pathways.

Fixed-point Amount(i128) with 8-decimal scaling removes floating-point drift and ensures deterministic reconciliation across nodes.

Operational Auditability

Each transaction path includes idempotency metadata to prevent duplicate effects under retry conditions.

Wallet-level history is reconstructible from journal entries and WorldLine references, enabling post-incident replay.

Interfaces

Wallet API

Create wallet, compartment balance lookup, scoped transfer initiation

Ledger API

Journal query, entry reconciliation, idempotency lookup

Production Checkpoints

  • ✓Debit = credit invariant holds in all transfer and settlement flows
  • ✓Compartment-specific restrictions are enforced before commitment
  • ✓Replay from journal + worldline reproduces final balances
  • ✓Idempotency keys suppress duplicate side-effects

Continue exploring

Self-Banking Engine

System HomeAll Systems