Key management

Stridge settles every deposit straight to your destination, so there is no standing pool of customer funds to guard. The keys that do exist are operational: the Routing Engine uses them to sign the settlement transactions that move funds in flight. Those are held by the Stridge KMS.

How keys are held

• Split into shares. A signing key is never stored whole. It is split into shares across separate servers; a threshold of shares is combined only at the moment of signing, then discarded from memory.
• Never exported. Private keys do not leave the KMS — not to your application, not to Stridge operators.
• Policy-checked. Every signature is checked against configured policy — spending limits and address rules — before it is produced.

The takeaway

KMS is infrastructure for moving funds safely, not for holding them. Because Stridge is non-custodial, there is no customer balance behind these keys — only transactions in flight toward the destination you set.

Next

• Non-custodial by design — why there is no balance to guard.
• Universal Deposit Addresses — the settlement model the keys serve.