[01]
No token. Ever.
OrangeCheck does not and will not issue a token, points balance, airdrop, or any unit of account other than sats and USD. The economic loop closes on Bitcoin. Anyone proposing otherwise is not OrangeCheck.
§ charter
What we commit to. In writing.
A commercial entity built on top of an open protocol family has obligations the protocol layer cannot enforce on its own. These are the ones we accept publicly. The full text is committed to git so the diff is auditable; this page is the canonical published version.
[02]
No custody. Period.
Console never holds customer Bitcoin private keys, never holds customer funds, and never operates a custodial wallet. Bonded reputation is attestation-of-unspent — sats stay in the customer's wallet. Enforcement is by exposure, never by slashing.
[03]
The protocol stays open.
The wire format, scope grammar, audit-bundle structure, and Bitcoin-anchoring rules are defined by the open oc-agent-protocol and oc-pledge-protocol specs. Any change Console wants goes through an open PR. No private extensions, no closed conformance vectors.
[04]
The protocol sites stay free.
agent.ochk.io, pledge.ochk.io, and every sibling protocol site remain free, self-hostable, no-account public goods forever. Console is the managed tier, never the only tier. If we ever change this, the spec stewardship governance ratifies first.
[05]
Audit verifies without us.
Every audit bundle Console issues is verifiable offline, against Bitcoin headers, by anyone, forever. If Console disappears tomorrow, every receipt continues to verify. We sell operations, not lock-in. The protocol is the API.
[06]
No agent-replacing-humans positioning.
We sell authority infrastructure. We do not market agents as labor displacement. The pitch is that compliance teams can sign off on agents taking real authority — which is human work being elevated, not erased.
[07]
Sat-denominated economics, first-class.
Lightning customers are not a footnote. Every USD price is published with its sat equivalent on the same row. We do not surcharge Lightning, do not require fiat onramp, and do not treat sat-paid customers as a niche segment.
[08]
Spec stewardship is public.
Material changes to the spec stewardship structure are announced publicly and discussed in the oc-protocol governance forum before being adopted. Console has one seat at that table; it is not the chair.
§ signatures
These commitments are made by the OrangeCheck founding team. Names will be appended here as public commitments are formalized.
§ founding team
signatures pending — published when public commitments are formalized.
§ ratified
v1 · 2026-04-28
next review: 2026-12-01 (or earlier if material change proposed)
next review: 2026-12-01 (or earlier if material change proposed)
if we ever break one of these
The protocol layer continues to work without us. Every receipt we ever issued continues to verify. The spec repos remain MIT, the npm packages remain published. Customers can fork the managed components and run them themselves on day one. This is the whole point of the design.
Spec stewardship and family governance live at github.com/orangecheck. The protocol PRs are the canonical mechanism by which any of the rules on this page can change.