§ economics · public ledger

every sat tracked. every flow visible.

The live aggregate of what the per-event fee split has produced. No per-user or per-operator detail: every figure is one an integrator could reach by replaying the public ledger.

/api/public/economics-summary ↗/api/federations ↗/audit

§ federations · live snapshot

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.

federations

1 live

accrued · pending

≈ $0.00 · awaits next distribution

distributed · lifetime

≈ $0.00 · paid to operators

accrued · 30d

≈ $0.00 · last 30 days

distributed · 30d

≈ $0.00 · last 30 days

§ per-federation breakdown

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 · north-star metric

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.

§ treasury · oc commercial books

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.

balance · current

≈ $0.00

inflows · 30d

≈ $0.00 · last 30 days

outflows · 30d

≈ $0.00 · last 30 days

inflows · lifetime

≈ $0.00

outflows · lifetime

≈ $0.00

net · lifetime

inflows − outflows

§ charter parameters

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.

§ the four parties

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. They don't have to know about Bitcoin to earn it. OrangeCheck holds your accrued sats during bring-up — it is operating every role until independent operators take them. Federation custody and graduation to your own keys are what replace it.
· 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.