The Mint

What it is

The Mint is The Cellar with an append-only ledger riding along in the same transaction: every accepted write posts a new assay entry, and each entry carries the fingerprint of the one before it — so an edited row breaks the chain and shows up immediately. Replay a table to any timestamp (AS-OF), export an incident window for an auditor, and ask for a signed receipt proving a row existed exactly as it was at a moment. Spend-once cartridge warrants from The Armory post one ledger entry and then expire, so a bulk import cannot quietly rewrite history. SQL, REST, live hatch, Studio, encryption, and row rules stay exactly as they are in The Cellar. Not a blockchain — no tokens, no mining, no public network: it is a signed ledger on your own database. Not Cloud SQL with separate audit logs bolted on the side — the ledger is part of the transaction, not a file that can go missing. Not a replacement for The Armory’s documents and crypto-shredding, and more than a plain Cellar once you need to prove your history.

Closest analogue: append-only ledger database. SLA 99.95% · p99 60ms. Admins read the ledger and issue receipts. Operators replay and export. Row rules still apply.

• ▸Ledger posting inside the write transaction
• ▸Hash-chained assay entries
• ▸AS-OF replay to any timestamp
• ▸Signed prove-a-row receipts
• ▸Spend-once cartridge warrants
• ▸Cellar SQL, REST, live hatch parity
• ▸AES-256-GCM and row rules stay on

How it works

The Mint is The Cellar with an append-only ledger riding along: every accepted write posts a new assay entry inside the same transaction, so the row and its history can never disagree.

Each assay entry carries the fingerprint of the one before it (your chosen hash chain). Edit a row behind the library’s back and the chain breaks where the edit happened.

Replay a table AS-OF to any timestamp inside the retention window, export an incident window for an auditor, or issue a signed prove-a-row receipt that verifies offline.

Bulk imports post one spend-once cartridge entry each and then expire — a reused write returns 409, so a history cannot be rewritten twice.

SQL, REST, live hatch, Studio, AES-256-GCM, and row rules behave exactly as they do in The Cellar. Not a blockchain: no tokens, no mining, no public network.

Use cases

Concrete ways teams use this service on day one.

Set it up in the dashboard

Dashboard → Database → The Mint → Overview: chain height, last entry, retention window.

Ledger tab: browse assay entries, filter by table or actor, jump to any timestamp.

Replay tab: pick a table and a moment → preview rows as they were → export.

Receipts tab: request a signed prove-a-row receipt and copy the verification link.

Configure tab: hash chain, retention, receipts, and spend-once warrants (ledger itself cannot be turned off).

API

Control-plane: GET|PATCH /api/v1/services/mint. Send Authorization: Bearer tz_live_YOUR_TOKEN.

Creates count against the plan quota. A 402 plan_limit means you are at the cap — upgrade or delete an unused resource.

curl -sS https://tinyzipper.com/api/v1/services/mint \
  -H "Authorization: Bearer tz_live_YOUR_TOKEN"

curl -sS -X PATCH https://tinyzipper.com/api/v1/services/mint \
  -H "Authorization: Bearer tz_live_YOUR_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"ledgerRetentionDays":3650,"proveReceipts":true}'

const res = await fetch("https://tinyzipper.com/api/v1/services/mint", {
  method: "GET",
  headers: {
    Authorization: `Bearer ${process.env.ZIPPER_TOKEN}`,
    "Content-Type": "application/json"
  }
});
const json = await res.json();
if (!res.ok) throw new Error(json.error ?? res.statusText);
console.log(json);

Tips

The ledger is part of the write transaction — there is no “ledger off” switch, by design.

Retention bounds AS-OF replay: entries older than the window are pruned on schedule.

Receipts embed the chain fingerprint at issuance — verify them without touching the database.

Not Cloud SQL with separate audit logs: losing a log file is not possible when the log is the transaction.

Need documents and crypto-shredding? That is The Armory. Need provable history? That is The Mint.

• ▸SOC 2
• ▸AES-256-GCM
• ▸Append-only ledger

Runbook

The Mint rides on The Cellar: every accepted write posts a hash-chained assay entry in the same transaction. Replay a table AS-OF to any timestamp, export an incident window, and issue prove-a-row receipts for auditors. Spend-once cartridge warrants post one entry and then expire. Ledger retention bounds the replay window. Not a blockchain — a signed ledger on your own database.