Security at DUALKEEP

A payment platform is only as good as its custody. Here is how ours works.

How funds are protected

Per-invoice addresses

Every invoice gets its own deposit address derived from the platform treasury, so payments are isolated, attributable, and never commingled at the address level.

Cold storage by default

Deposits are swept on a schedule and the bulk of platform funds is moved to cold storage. Hot operating balances are kept deliberately lean and monitored against a hard threshold.

Continuous reconciliation

An automated process continuously compares on-chain holdings against the sum of all merchant balances. Any shortfall triggers an immediate alert - solvency is checked by software, not by promises.

Encrypted key material

Wallet seeds and secrets are encrypted at rest with AES-256-GCM. Production access is restricted, and secrets never appear in logs or client-side code.

Platform security

Buyer protections

Reporting a vulnerability

If you believe you have found a security issue in DUALKEEP, email [email protected] with "Security" in the subject. We read every report, respond quickly, and will not take legal action against good-faith research that avoids privacy violations and service disruption.