Security: Custody, authority and evidence.

Explanation — not permission to act

Custody-specific explanation, not an audit or assurance of current policy enforcement. Native and legacy wallets have different dependencies.

The mechanics and diagram include historical specification design. Current gates and finalized evidence govern; configuration is not availability or execution proof.

Native wallets are server-managed: their custody and signing dependencies must not be confused with legacy Turnkey browser-owner access. Legacy recovery can depend on the original owner key, provider and evidence; signing in does not restore a missing key. The historical specification describes deny-by-default policies, guardians, multisig and timelocks, but that is not proof of universal current enforcement. Identity sessions and spending authority are different boundaries. Server, provider, device or key compromise can lose funds; no no-drain or compromise-proof guarantee is made.

Native versus legacy custody

Native custody is server-managed. Legacy Turnkey owner access may depend on original browser-held authority and provider availability. Do not clear owner storage or assume login recovers keys.

Identity is not spending authority

Account sessions, custody permissions, release admission and transaction evidence are separate. Historical independent-key, multisig and timelock designs cannot be generalized to every current wallet.

Limits of protection

Compromised servers, providers, browsers or keys can cause loss. Never share an exported key, seed or signature in support. Configuration and article text are not proof of security enforcement.

Historical direction-of-risk governance design, not verified current enforcement.
  1. Request

    An admin or runtime action is proposed.

  2. Classify

    Risk-reducing or risk-increasing.

  3. Reducing

    Guardian executes immediately; logged publicly.

  4. Increasing

    24 hour timelock, majority multisig, public queue.

Practical next reading

Use the native wallet safely · Legacy wallet recovery · Manage account sessions

The numbers that bound it.

Live configuration is not embedded in this guide. No values are shown rather than guessed. Local settings are not chain, provider or release evidence. Spec defaults are not provider proof.

    Platform spec reference

    Historical source summaries, not a statement of current enforcement.

    Applicability and precedence · §20 Security · §27 Decision Ledger (v6.6.1)