ConceptsRisk checks

Risk checks

Limits stop a payment that is too big. Risk checks catch behaviour that is unusual even when each payment is small, such as a sudden burst of payments to new recipients.

How it works

  1. Arcanum holds the oracle’s signing key (the oracleSigner) and decides when to sign a risk score for a wallet.
  2. Anyone can submit that signed score to the AnomalyOracle contract. The contract checks the signature.
  3. If the score is above the wallet’s threshold and is still fresh, anyone can call triggerFreeze and the wallet freezes.
  4. A frozen wallet makes no payments until the owner reviews it and calls unfreeze.

The oracle can only freeze. It cannot move funds, change rules or unfreeze. Each score can freeze a wallet once, so the same score cannot freeze it again after the owner unfreezes.

Owner settings

  • Threshold: new wallets start at a threshold of 500. A score must be above the threshold to freeze the wallet. The owner can change it with setAnomalyFreezeThresholdBps.
  • Switching it off: the owner can turn risk checks off by setting the wallet’s oracle module to the zero address with rotateModule.

Risk checks are a circuit breaker for review, not a replacement for limits. Keep your caps and vendor list tight either way.