sign in
oc · me
§ compliance · charter §1 monitor

Every federation. Every property. Checked live.

Every federation in the registry, checked against the charter's §1 custody properties, pass or fail per property. The admin console runs the same validator, and anyone holding the spec can re-implement it and reach the same answer.

/api/public/charter-compliance ↗charter ↗/economics/scale
§ network-wide rollup
federations
3
charter-compliant
2
with issues
1
with warnings
1

> snapshot computed at Thu, 01 Oct 2026 14:29:21 GMT

§ per-federation compliance

OC-Me Federation v1

oc-me-v1 · status recruiting · threshold 3-of-4 · seats 0/4
✓ compliant
charter_hash
—
last_attestation_at
pending

OC Testnet (bootstrap)

oc-testnet-v1 · status live · threshold 1-of-1 · seats 0/1 · bootstrap mode
✗ 3 issue(s)
§ issues (blocking)
  • live.seats_incompletelive federation must have 1 seats filled; got 0
  • live.charter_hash_missinglive federation must have a charter_hash set
  • live.attestation_missinglive federation must publish last_attestation_at
§ warnings (non-blocking)
  • live.invite_unparseablelive federation publishes an invite that is not a fedimint invite · no wallet can join it
charter_hash
—
last_attestation_at
pending
§ how this is computed

Charter compliance is computed live against the published Federation row + the same validator the admin UI uses. Property checks: oc_residual_bps cap, target_guardian_count, threshold shape, threshold ≤ guardian count, seat roster size, distinct operator pubkeys (charter §1.1), and for live federations: invite present, seats complete, charter_hash, last_attestation_at within 30 days. Bootstrap-mode federations get warnings rather than issues for some properties; v1 launch reality with a documented path to ≥4 distinct operators.