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

Every federation. Every property. Checked live.

OC publishes a charter — federation custody is bound by §1 properties (≥4 guardians, threshold > N/2, distinct operators, signed content-addressed charter, non-OC LN gateway, OC not a guardian, exit clause, fresh attestation). This page walks every federation in the registry through those property checks and publishes pass/fail per property. The same validator the admin UI runs; the same code anyone with the spec can re-implement 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
0

> snapshot computed at Mon, 17 Aug 2026 11:23:39 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
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.