§ federation discovery

federations seeking guardians.

Slots OC is actively recruiting into. Read the §1 requirements, check the geography fit, decide. Submit your application via the portal upload (auth-gated) or via the kit-only email path — same review queue either way.

slug · oc-me-v1

OC-Me Federation v1

§ recruiting

target guardians

threshold

3-of-4

seats open

—

§ geography requirements

four guardians across at least three legal jurisdictions; at least one each in the Americas, Europe, and Asia-Pacific. Distinct hosting providers. Distinct legal entities.

§ charter

draft v0.1 — published at oc-guardian-kit/CHARTER-FORMAT.md; final hash baked at DKG.

§ ceremony window

opens once 4 accepted operators are on file. Operators in the queue are notified and given a 14-day window to confirm availability before the DKG schedule freezes.

§ why this slot

this is the federation OC the company will bind to me.ochk.io's email-OTP wallet flow as Path B + D. OC is not a guardian. Apply here if you want to operate the federation that backs the consumer product.

Apply via the portal (auth-gated upload) or via the kit-only email path. Same review queue, same review SLA, same signed acceptance envelope back.

apply for OC-Me Federation v1 →

§ public registry

Every operator whose application is accepted appears in the anonymous registry at /api/operator/registry. Strictly the cryptographic identifiers federations need — operator_id, pubkey, accepted_at. No handles, no contact info, no envelope details. Federations include accepted pubkeys in their charter; verifiers check signed envelopes against them.

§ kit-only equivalent

Same data without authenticating to the portal. The page above reads the same JSON the kit fetches.

# inspect via curl:
curl -s https://me.ochk.io/api/operator/federations | jq

# (kit equivalent · v0.2):
oc-guardian federations list
oc-guardian federations inspect oc-me-v1
oc-guardian federations apply --slug oc-me-v1 --envelope ./application.json

← back to operator overview