Compliance
Every federation, every property, checked live.
Each federation in the registry, checked against the charter's custody properties, pass or fail. The admin console runs the same validator, and anyone holding the spec can reimplement it and reach the same answer.
Across the network
Each federation
OC-Me Federation v1
Recruiting · threshold 3-of-4 · 0 of 4 seats filled · oc-me-v1
- Charter hash
- Not published yet
- Last attestation
- None yet
OC-ME-FEDERATION-BOOTSTRAP-1
Recruiting · threshold 3-of-4 · 0 of 4 seats filled · oc-me-federation-bootstrap-1
- Charter hash
- Not published yet
- Last attestation
- None yet
OC Testnet (bootstrap)
Live · threshold 1-of-1 · 0 of 1 seats filled · oc-testnet-v1
Blocking
executor.invite_presentan executor rail has no mint, so a stored invite is joinable by nothing · re-register the record to clear it
Warnings, not blocking
executor.custodialOrangeCheck holds the only settlement key · custodial bootstrap until a federation replaces it
- Charter hash
- Not published yet
- Last attestation
- None yet
How this is computed
Each federation's published record is checked live, with the same validator orangecheck's admin console uses: its share of the fee is under the cap, its threshold and seat count fit the charter, and every seat has a distinct operator key. A live federation must also have a current invite, a full roster, a charter hash and an attestation from the last 30 days. The exact checks are in the JSON.