Security Model

Tangle’s security model is service-scoped: the parties who can trigger enforcement are tied to the service owner, blueprint owner, and (optionally) a blueprint manager contract.

Slashing: Authorization + Exposure Scaling

Slashes are proposed on a per-service basis and can be disputed within a window before execution. When a service declares per-asset security requirements, “effective exposure” can be scaled by the operator’s commitments.

Liveness (Heartbeats)

Heartbeats are emitted by operators (or their manager) and can be consumed for monitoring and, depending on policy, escalated to slashable status.