CGPT

• 100,000 CGPTPro

  topic freedom · 100 credits a month

• 500,000 CGPTPro+

  for people who make things all day · 7,500 credits a month

• 2,000,000 CGPTMax

  the heaviest use we support · 22,500 credits a month

Privacy is not for sale here. Staking unlocks the same thing money does — topic freedom and credits — and never gates the sealed tier, attestation, receipts, the verifier. Those are on every plan, including free, including anonymous.

Where this is against its own targets

Read from the running system, not written here. One number is a ceiling, one a floor, and one supports no inequality at all; a gate counts as met only when the number clearing it cannot be an overstatement.

• External developers integrated≤ 0 / 10

  api_keys — distinct owners of a live key that has been used at least once

  Cannot see: Every visitor gets an anonymous account, so a person calling their own key from their own script counts here exactly like an external integrator — nothing in the data tells them apart. The real number is somewhere at or below this one, which is why this gate does not read as met on it.

• Tokens delivered under a sealed mode4,045 / 1,000,000

  sealed_tokens counter, bumped on DELIVERY, not on request; agentic answers excluded — the runner reports no token counts on delivery

• Independent verifications by third parties≈ 0 / 50

  verification_reports — voluntary, each backed by a receipt whose signature we checked

  Cannot see: Wrong in both directions.

  It UNDERCOUNTS because verification happens offline against a published address — that is the point, and it is why we cannot observe it; anyone who verified without telling us is missing, and making them visible would mean phoning home on every check, which would defeat the property being verified. It also OVERCOUNTS what this gate asks for: the gate asks for fifty INDEPENDENT parties, and a report carries no identity by design, so fifty reports could be fifty people or one person with fifty receipts and we cannot tell. Every report is backed by a receipt we signature-checked, which stops someone holding no receipts from sending any — it does nothing to establish that two reports came from two people. So this number can never mark the gate met; what would is evidence of independence, which we do not have and are not willing to collect.

• CGPT burned0

  no burn has run

  Burn tracker →

Verified a receipt yourself? POST /api/verifications with it. Anonymous, one report per receipt, and a failed verification counts and is published exactly like a successful one.

Burn tracker

The intended arrangement, not something running today: 20% of subscription revenue buying and burning CGPT. There is no subscription revenue yet, because no plan on this product can currently be purchased, so no share of it has been routed anywhere and nothing in this codebase computes one. Untold pays an arm's-length licence fee to a ChainGPT entity, which independently conducts any buybacks, so our Terms commit to no schedule and no amount, and this page should not imply otherwise.

No burn has happened yet, so this ledger is empty. The first entry will appear here with its transaction hash on the day there is one.

Every burn is published with its transaction hash. A burn nobody can check is a press release.