The claims register — how it works

What this registry produces, what it doesn't, and how a pseudonymous ledger becomes a tool a committee or claims agent can actually use. ← Back to main page

What the register is

A claims register is the aggregate answer to three questions: how many claimants are there, in which categories, and for roughly how much. When an exchange goes quiet, that number is the difference between "an unquantified crowd of angry users" and "a claim pool a lawyer, committee, or court can engage on day one."

This register is pseudonymous by design: rows are identified by random receipt IDs, not names. It is also sealed: your answers are encrypted in your browser before they leave it, and the server stores ciphertext only.

Two layers, your choice

1. The sealed layer (default). Your full submission — narrative, withdrawal IDs, holdings detail, contact — is sealed to the organizers' key before transmission. It feeds the private ledger and is released only under the consent state you choose:

Licensed (default): releasable to a duly-constituted claimants' committee, its counsel of record, or a court-appointed claims agent / insolvency officeholder.
Sealed private: ciphertext only; no one reads it.
Revoked: deleted everywhere it's hosted; a content-free tombstone marks the removal.

You switch between these yourself, any time, with your receipt: manage your submission.

2. The public layer (opt-in only). If you tick the opt-in box, exactly four fields appear on the public status board: your claim-status bucket, asset class, amount range, and a "registered" marker — plus the submission date. Never your name, contact, IDs, or narrative. It's the difference between "we think there are hundreds of us" and a live count anyone can watch.

How it hands off

A community register is not a legal claims process — it's the raw material one consumes. The handoff paths:

To a claimants' committee. A committee with counsel (see the directory) can receive the ledger under the consent states claimants chose — giving it a headcount, a category split, and an amount distribution on day one instead of month six.
To a claims agent or insolvency officeholder. If a formal process opens, each claimant still files their own proof of claim in it — but the register's normalized rows (structured holdings, withdrawal IDs, categorized status) map directly onto the fields a claims agent asks for. Your sealed record, released by you, becomes your claim packet.
To counsel evaluating the case. A quantified, categorized pool is what makes contingency representation viable — firms take documented pools, not vibes.

What the register never does: it does not hold or move funds, does not issue distributions, does not charge fees, and does not replace filing in any official process that opens. Anyone claiming otherwise — in either direction — is wrong about what this is.

Integrity properties

Self-service lifecycle. Release, seal-private, and revoke are all claimant actions — nobody has to approve your deletion.
Tombstoned revocations. Deletion writes a timestamp-only tombstone so the ledger's consent history stays honest without retaining content.
Local verification. The verify page decrypts your own record entirely in your browser — you can confirm what the register holds without trusting this page's word for it.
Ciphertext at rest. Even a full backend disclosure exposes only sealed records — see SECURITY.md in the repository.

Register a claim

The form takes a few minutes and stays private unless you opt into the public row: register on the main page or use the structured packet. Save the receipt it gives you — it is the only credential for your record.