Security

Balance monitoring begins with public data and protected accounts.

Public addresses, read-only requests

The service only reads blockchain state. It has no transaction-signing or broadcast functionality.

Verified accounts and ownership controls

Users must sign in and verify their email before scanning. Wallets, imports, results, and exports are authorized against their owner.

Two-factor protection

Authenticator-based two-factor authentication is available for users and required for administrators.

Secret-safe imports

If advanced key import is enabled, cryptographic libraries derive public addresses. Plaintext keys are discarded and never put in job payloads, results, exports, or administrator screens.

Protected operations

Encrypted provider credentials, throttling, HTTPS configuration, session protection, and audit events support operational security.