Security
Built on watch-only monitoring
No private signing keys live in the frontend or the database. Balances are derived from immutable journal entries.
No private keys
No signing key exists in the frontend, the database or the logs.
Confirmation policy
A broadcast transaction is not a payment. Each network has a required depth.
Immutable ledger
Balances derive from double-entry journals. There is no balance-edit field.
Hashed keys
API keys are stored as a SHA-256 hash and shown exactly once.
Duplicate protection
An idempotency key per request and a unique key per chain event.
Daily reconciliation
Cached balances are compared against journals; drift raises an alert.
We make no claim that the platform is unhackable or 100% secure. This page describes only what is genuinely implemented.