ochk.app · Federation custody
Status: this is the design, not today. No guardian federation is bound.
/api/federations (opens in a new tab) is the
machine-readable answer. It lists two entries, neither with an invite, so no
client can join one: oc-me-v1, recruiting with no guardian seats, and
oc-testnet-v1, a single-key test federation on testnet that orangecheck
operates. While it is in testing, orangecheck holds every user's accrued
balance and is the party that moves it. That is a stage, deliberately:
orangecheck operates every role until independent operators take them. Read
the rest of this page as the destination, and
ochk.app/custody (opens in a new tab) as the present tense.
In the design, independent guardians hold the bitcoin. A Fedimint federation — an M-of-N set of independent guardians that threshold-sign together — holds the bitcoin. orangecheck's executor holds your claim on it, as ecash it can spend, until it pays you out to a Lightning wallet you choose. The executor sends payouts and holds the key that signs settlements; with a federation, it pays from the ecash it holds, and a gateway only routes the payment. None of that is in force: no guardian federation is bound.
If you run a guardian, read the operator runbook. If you're a user, this page is enough.
What "federation custody" actually meansLink to this section
A Fedimint federation is a small group of independent operators (the guardians) running coordinated software. The federation as a whole holds the bitcoin and issues ecash notes — bearer-form claims on it. In this design orangecheck's executor holds that ecash for you, not your browser. Moving the bitcoin itself takes the guardians' threshold signature.
| If this party | tries to | the result is |
|---|---|---|
| orangecheck's executor | spend the ecash it holds | possible: that is how it pays you out |
| orangecheck | move the federation's bitcoin | possible only with enough seats to reach the threshold; /custody (opens in a new tab) shows whether it can |
| Fewer than M guardians | move the federation's bitcoin | impossible — threshold not met |
| M+ colluding guardians | move the federation's bitcoin | possible (this is what M-of-N means) |
| You | get paid out | a payout sends your sats to a Lightning wallet you choose |
How much this leaves with orangecheck depends on the specific federation. Specifically:
- At least 4 guardian seats filled, threshold strictly greater than half (so 3-of-4, 4-of-7, etc.). A production federation needs 4, so one guardian can fail.
- A different operator key in every seat, held by separate legal entities in 3 or more countries. Operator-key diversity is the property that counts; spreading hosting providers helps with incidents but is not a trust gate.
- A published, content-addressed charter, signed by the guardians, with an on-chain way out written into it.
- A Lightning gateway run by someone other than orangecheck.
- orangecheck holds no seat.
ochk.app/custody (opens in a new tab) checks each of these live, derived from the seat roster and the signed charter.
A live federation's guardians also have to keep running. Each guardian's kit posts a signed runtime attestation every 5 minutes, and a quorum of them dates the federation, since one guardian alone can sign nothing. What counts is the signing key, the machine key that signed: a delegated attestation key, or the operator key if that signed. Each signing key counts once, at its newest attestation, and the federation's time is the M-th newest of those, M being the threshold's M of M-of-N. A seat that changes hands stops counting the attestation made before. With no quorum in 7 days the charter check warns; with none in 30 it fails, and a project can't be rebound to that federation. A federation where fewer than M signing keys have posted one yet fails the check as "no quorum of runtime attestations yet", not as stale, and a project can still be rebound to it, with a warning.
This measures machines being alive, not operators being independent. That is the diversity check's job: two seats with one operator key fail it outside bootstrap. So a §1A bootstrap federation, one operator with a separate attestation key on each machine, can reach a quorum.
/api/public/federations/<slug> (opens in a new tab)
and
/api/public/charter-compliance (opens in a new tab)
give the quorum's time as quorum_attestation_at and the newest from any seat
as last_runtime_attestation_at. seats_attested_within_window is
{ attested, of, window_days }: the distinct signing keys whose newest
attestation is inside 7 days, out of the roster's seats. invite_published_at
is when the invite was published, and last_attestation_at is a deprecated copy
of last_runtime_attestation_at. Both answer a query string with 308 to the
bare path and allow 60 reads a minute per IP. A slug no federation has answers
404 with federation_not_found.
Where to find your federation's charterLink to this section
Once a federation is bound, the charter (with all of the above disclosed) is published in three places:
- The federation's own site / status page.
- ochk.app's
/custody(opens in a new tab) page, including the SHA-256 hash of the charter so you can verify the copy you read against the one OC bound. https://me.ochk.io/api/operator/charter?federation=<slug>, with the hash and each guardian's signature over it.
Hash mismatch between any of those three is a red flag. If the federation amends its charter without re-publishing the new hash on ochk.app, tell us at ochk.app/contact (opens in a new tab).
What your browser doesLink to this section
Nothing, for custody. In this design your browser holds no Fedimint wallet and no mnemonic: orangecheck's executor holds the ecash and pays you out. ochk.app has no browser-side Fedimint client, and binding a federation would not add one. See Current state.
What if a guardian goes down?Link to this section
The federation continues to operate as long as at least threshold of the
guardians are reachable. With a 3-of-4 federation, one guardian can be down
indefinitely without affecting payouts.
If (N - threshold + 1) guardians go down at once, the federation itself can't
reach threshold and payouts pause until guardians are restored. This is the
federation's responsibility to communicate.
/custody (opens in a new tab) shows who holds each role and the
federation's trust posture, read live; it does not mirror the federation's
status page.
What if OC sunsets?Link to this section
The oc-me-v1 charter's exit clause was written for a design in which each user held a Fedimint wallet and its mnemonic in the browser. ochk.app has no such wallet or mnemonic: in this design orangecheck's executor holds your claim as ecash and pays you out to a Lightning wallet you choose. Today orangecheck holds what you earn, and no real sats move yet.
Moving to your own keysLink to this section
Not open. In this design, your sats reach keys you hold as a payout to a
Lightning wallet you choose;
/me/balance (opens in a new tab) shows whether that is
open.
Your OC identity stays the same, and so does the signing_method on your
/api/auth/me payload: it says only whether you sign with your own Bitcoin key,
never where your sats sit. Sat-earning continues unchanged.
Current stateLink to this section
No guardian federation is bound, and the browser-side Fedimint client that would
have joined one was removed from oc-me-web in September 2026 — it could only
ever reach its own error path, and code that demonstrates a money movement which
cannot happen reads as a feature someone forgot to link up. The guardians that
once ran this were torn down in July 2026. Who will run the guardians is not
decided yet.
So today orangecheck holds what you accrue. There is no stored balance to hold, strictly speaking — it is recomputed from your signed billable envelopes on every read — but the party who owes it is orangecheck, and that is the honest way to say it.
We are not soft-pedaling this. ochk.app/custody (opens in a new tab) says who holds what today.
Signing in via BIP-322 gives you a real, live self-custody property — your signing key never reaches OC. It does not make your earned sats self-custodied. Those are two different questions, and conflating them is the mistake this page used to make.