Operational Security

Operational security

Operational security protects the keys and the people who operate Tydro. This page describes the key management, access controls, and operational posture behind the protocol.

Key management

The keys that hold protocol authority are the highest-value target in any deployment, so they are protected accordingly.

• Multi-party computation, so no single party holds a complete key and no single device is a point of failure.
• Dedicated, hardened signing devices rather than general-purpose machines.
• Multi-factor authentication across the systems that operate the protocol.
• Encryption of sensitive material at rest and in transit.

These controls sit behind the governance roles, so the powers in Smart contract security can only be exercised through this protected path.

Access control

The protocol runs on role-based access control. Each role has a defined set of actions and clear limits, authority is separated so no individual can act alone where it matters, and access follows least privilege. The same model extends to vaults, where curator and allocator permissions are explicit. See Governance and Vault Curation.

Custody

Where assets are held through Kraken qualified custody, they sit with a regulated custodian under institutional controls for segregation and operations, which removes much of the self-custody risk institutions carry elsewhere. See Qualified Custody.

Personnel and physical security

Operational security extends to people. Tydro applies controls around the identities and physical security of key personnel.

Incident response

If an incident occurs, the Guardian can pause an affected market or the protocol while a response is carried out, then resume once the threat clears. See Smart Contract Security.

For the residual risk these controls reduce, see Custody and Counterparty Risk.