Each me.ochk federation has its own platform-account · sats accrue from each billable event's 20% slice and distribute weekly to the federation's operators (with OC's charter-ratified residual carved out first). Numbers below sum across every federation in the directory.
every sat tracked. every flow visible.
me.ochk.io is OC's commercial product, and the four-way per-event split — integrator pre-fund → user cashback → site rebate → OC platform fee → operator distribution → OC residual — is the math on every billable envelope. This page is the live snapshot of what that math has produced. No PII, no per-user, no per-operator detail; the aggregates are what an integrator could compute themselves by replaying the public ledger.
One row per federation in the directory · status, charter parameter, accrued and distributed totals. Same data as the live snapshot above, broken out so integrators evaluating which federation to bind to can see the per-fed economics.
| slug | name | status | oc_residual | accrued · 30d | accrued · life | distributed · life |
|---|---|---|---|---|---|---|
| oc-testnet-v1 | OC Testnet (bootstrap) | live | 0.00% | 0 ≈ $0.00 | 0 ≈ $0.00 | 0 ≈ $0.00 |
Graduation is a custody transition out of federation custody (fedimint_threshold / fedimint_client) into BIP-322 self-custody. The user's OC identity is stable across the rebind; only the signing_method changes. Every transition lands as an anchored envelope — independently verifiable via /verify/[id]. Graduation rate is the network's published north-star.
loading graduation snapshot…
Source · the rebind envelope chain (kind=oc-me-rebind, to=bip322). Anyone can reach the same numbers by listing rebinds and filtering. CORS-open JSON at /api/public/graduation-rate.
OC's own ledger · participation fees from operators + treasury withdrawals from federation platform-accounts vs vendor invoices, payroll, cold-wallet sweeps. Distinct from federation-side ledgers; this is what funds OC the company. Per- operator detail and PII excluded by construction; only category aggregates surface here.
- platform fee · charter constant
- 20%
- Of every billable event's gross fee. The remaining 80% splits between the user (cashback) and the site (rebate) per the integrator's published config. Constant across every federation; a v2.5 minimal-invariant Fedimint module enforces this in consensus.
- oc_residual · avg across federations
- 0.00%
- OC's share of the 20% platform fee · ratified per-federation in their charter as a basis-points value. Carve-out lands on OC's commercial treasury before per-operator distribution. Tier-1 launch federations ship at 0bps (full pass-through) during the bootstrap-retainer phase; v2 baseline is 1000bps (10%). See FEDERATION-ECONOMICS.md §9.
Every billable event splits four ways. Each party's share is carved from the fee the integrator pays · this is OC's revenue model and the operator's revenue model and the user's revenue model, all simultaneously, by design.
- · integrator · pays a per-event fee (sat-denominated, set in their IntegratorPriceConfig). The fee buys them a verifiable, real-time event stream + a built-in cashback incentive for their users.
- · user · receives a cashback share denominated in sats. The user's share is federation-custodied by default (they don't have to know about Bitcoin to earn) and graduates to self-held BIP-322 on demand.
- · site (rebate) · the integrator can route a portion of the fee back to the user's favorite creator / podcaster / merchant on the same event. Pure pass-through · OC takes nothing on the rebate slice.
- · platform (operators + oc) · the 20% platform fee accrues on the federation. The federation cron distributes it weekly · OC takes its charter-ratified residual (oc_residual_bps, above), the rest splits per-operator. OC is its own customer of the federation infrastructure.