Session Keys

Sail uses Session Keys to execute on your behalf without broad, permanent authority.

• Least privilege: Keys only cover approved actions and assets.

• Explicit consent: The first time you use Sail, you sign the permissions that allow the agent to act. Any new integration (yield source, network, stablecoin, or operation) requires a fresh signature from you.

• Bounded risk: Notional caps, frequency limits, and hard allow-lists prevent abuse.

• Short-lived & rotatable: Keys expire and can be rotated. Revoking them halts all agent activity until new permissions are signed.

• Defense in depth: Off-chain policy checks mirror on-chain guards to catch malformed or out-of-policy transactions before they’re sent.

If a key were ever compromised, its scope and expiry contain the impact. Since users must re-sign when new powers are added, there is no silent privilege creep.