> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chance.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# Private records

> Anchor a verification so it stays permanent and provable without publishing that it happened — one setting, no loss of proof.

Anchoring is what makes a verdict permanent and independently checkable. It is also what makes it visible.

An anchored record holds only commitments — hashes — never the content of a decision. But a hash on a public chain still says something: that a verification happened, when it happened, and how often. For a fund whose trading cadence is proprietary, or a treasury whose activity is not public information, that pattern is itself the sensitive part.

The old answer was *then don't anchor*, which trades away the guarantee that a record cannot be quietly rewritten later. **Private records remove the trade:** a record can be anchored so that it is provably permanent, provably yours, and opaque to everyone else.

## One setting

In **Settings**, choose where new verification records anchor.

|                                | Base *(default)*                                   | Starknet                                           |
| ------------------------------ | -------------------------------------------------- | -------------------------------------------------- |
| On the public chain            | the record's commitments, in the clear             | one opaque commitment                              |
| What an observer learns        | that a verification happened, when, and how often  | that *something* was anchored                      |
| The decision's content         | never on-chain; the transcript is yours to release | never on-chain; the transcript is yours to release |
| Proves the record is unaltered | yes                                                | yes                                                |
| Proves *when* it happened      | yes                                                | yes                                                |
| Independently verifiable       | yes                                                | yes                                                |

The difference is **not** whether outsiders can read your decisions — they never can, on either chain. A Chance record on Base is already only commitments: hashes, the judge that signed, a timestamp, and a transcript link that only you can open. What a public anchor still exposes is the *shape* of your activity: that a verification occurred, at what time, and at what rate.

On Starknet even that goes away. The commitments collapse into one cryptographic value and the record fields ride alongside it encrypted, so an observer cannot tell which decision it was, what it concerned, or what the verdict said — only that an entry exists.

Nothing else about verification changes: the same attested judge produces the verdict, signs it with the same key, and the same in-browser check re-derives every claim. The choice applies to future records — receipts already issued keep the chain they were anchored to.

## Why a sealed record still proves something

If the on-chain entry is opaque, what does anchoring it prove? The two things that matter.

<CardGroup cols={2}>
  <Card title="This record has not changed" icon="fingerprint">
    The commitment is derived from the record's contents. Produce a different record later and it no longer matches what the chain has held since the moment it was anchored.
  </Card>

  <Card title="It came from the attested judge" icon="shield-check">
    The same key that signs every Chance verdict — held inside [attested enclave hardware](/concepts/proofs), never in the hands of an operator — signed this one, and the chain verified that signature before accepting the record.
  </Card>
</CardGroup>

So the guarantees in [Provable verdicts](/concepts/proofs) survive intact: integrity, attribution, permanence, and independent verifiability. What is removed is the public's ability to *correlate* your records — not anyone's ability to prove one is genuine.

Disclosure stays under your control. When a counterparty, auditor, or LP needs to see a particular decision, you share that record and they verify it against the same public chain entry. The proof works for whoever you choose to show it to, and for nobody else.

<Note>
  **Sealing is currently custodial.** The sealed fields are unreadable to any observer of the chain, but Chance holds the key that unseals them. A user-held key — where not even Chance can read a record — is the next step, and the design already anticipates it.
</Note>

## Availability

The registry that receives sealed records is **live on Starknet mainnet**. The setting turns on once the attested judge is redeployed to sign Starknet records; until then every record anchors publicly on Base, exactly as it does today.