2026-04
open- events
- 18,604
- gross
- 1,823,400 · $1,732
- platform
- 364,680 · $346
- user earned
- +1,159,310
- rebate
- 299,410 · $284
§ developer · billing
every monthly invoice, every envelope, every sat.
invoices roll up the canonical envelopes your project signed in each period. the four-way split — site_paid · platform · user_earned · site_rebate — is computed from the same computeFees() production verifies against. anything you can't reconcile to an envelope id is a bug we want to know about.
§ sample data
this page renders representative integrator state so you can see what the dashboard looks like without signing up. it is not your project. to manage a real project, go to /developer and create one.
| period | events | gross | platform fee | user earned | site rebate | status | |
|---|---|---|---|---|---|---|---|
| 2026-04 | 18,604 | 1,823,400 $1,732 | 364,680 $346 | +1,159,310 $1,101 | 299,410 $284 | open | envelopes → |
| 2026-03 | 16,410 | 1,614,220 $1,534 | 322,844 $307 | +1,023,005 $972 | 268,371 $255 | paid | envelopes → |
| 2026-02 | 11,815 | 1,142,800 $1,086 | 228,560 $217 | +720,998 $685 | 193,242 $184 | paid | envelopes → |
2026-03
paid- events
- 16,410
- gross
- 1,614,220 · $1,534
- platform
- 322,844 · $307
- user earned
- +1,023,005
- rebate
- 268,371 · $255
2026-02
paid- events
- 11,815
- gross
- 1,142,800 · $1,086
- platform
- 228,560 · $217
- user earned
- +720,998
- rebate
- 193,242 · $184
§ how invoicing works
- > each envelope your project signs is admitted to the federation billing index in real time.
- > at the close of each month the federation rolls up every admitted envelope into a single content-addressed monthly invoice.
- > the invoice envelope is anchored to a bitcoin block via OpenTimestamps and republished on nostr alongside its event children.
- > settlement is on-chain or via Lightning to a project-controlled receive address — your choice in /developer/config > settlement.
§ disputes
Every line item resolves to an envelope id. If you believe the rolled-up number disagrees with the underlying envelopes, we'll always trust the envelopes — they're anchored. Open a dispute by emailing /contact with the envelope id range; we'll re-run the aggregator against them and post the diff.