Wallet Isolation and Accounting Boundaries

WAproxy isolates each wallet_id (WID) as an independent accounting domain.

A WID represents:

• a logical wallet boundary

• isolated balance tracking

• independent transaction history

• separate idempotency scope

Operations inside one WID must not affect another.

Isolation guarantees:

• no cross-wallet balance leakage

• no shared state mutation

• deterministic accounting per project

• safe multi-tenant execution

Example:

WID_A:
balance = 50000

WID_B:
balance = 120000

Sending from WID_A must not:

• read from WID_B

• deduct from WID_B

• reuse idempotency from WID_B

Each wallet maintains:

• its own balance

• its own idempotency keys

• its own transaction set

Concurrency rule:

Multiple sends from the same WID
must be serialized at execution layer.

Race conditions must not produce:

• negative balance

• duplicate broadcast

• inconsistent state

WAproxy enforces wallet-level boundaries
to preserve deterministic accounting.

Isolation is mandatory for:

• marketplace models

• bot payments

• multi-user systems

• API-driven SaaS integrations

A WID is an execution boundary.
Not just a label.