DocsDevelopment

Security and controls

Authority boundaries keep custody, trading access, treasury operations and confidential data permissions distinct.

Authority boundaries#

User withdrawal authority stays separate from session, keeper, treasury and deployment keys. Operational permissions require narrow scopes and limits. Sensitive upgrades need a disclosed approval and delay policy.

An emergency control can stop new risk without granting unrestricted authority over trader funds.

Recovery and accountability#

The system needs durable, private recovery data, an enforceable owner exit and a defined treatment of open positions during an outage. Emergency settlement requires a stated price source and loss rule.

Independent accounting review should reconcile custody against trader liabilities, vault capital, insurance and reward escrow.

Economic controls#

  • Credit creator revenue only after receipt and settlement.
  • Fund token rewards before creating claims.
  • Never pay holders from trader margin.
  • Never count insurance twice as trading capital.
  • Recognize losses and reserve requirements before discretionary rewards.

Access and disclosures#

Market access, sanctions controls, custody and token distributions need a jurisdiction-specific operating plan. Confidentiality doesn't remove those obligations.

This site describes a proposed protocol. It doesn't claim a completed independent audit, regulatory approval or availability for live deposits.

Design documentation · October 2026