Safe Monitoring

Threshold, owner-set and transaction monitoring for the protocol's Safe in the official Safe Global app.

EXTERNAL DEPENDENCY UNAVAILABLE

Safe monitoring status

EXTERNAL DEPENDENCY UNAVAILABLE

EXTERNAL_DEPENDENCY_UNAVAILABLE

The BOLT admin Safe is pending creation and validation through the official Safe Global app at app.safe.global. No Safe roster is available from the read-only API. After validation, monitoring is enabled by configuring a Safe address (BOLT_SAFE_ADDRESS) and a Safe Transaction Service endpoint. When a Safe address is configured it joins the critical-contract watchlist, and its on-chain threshold and owner count are checked against policy (expected 2-of-2) — a mismatch is raised as a SEV-1 finding.

Required inputs
  • Safe contract address on BOT Chain
  • Safe Transaction Service endpoint (for queued-transaction visibility)
  • Signing policy (expected threshold and owner set) to diff against
Why it matters

All Foundation payment batches require Safe approval before execution. Monitoring the Safe threshold, owner set and signing queue is the control that keeps batch execution and privileged upgrades under multi-party approval.