ledger.ternent.dev

Append entries. Preserve history. Verify the chain.

Ledger is a browser-first append-only record format for signed, replayable history. Create entries, link them together, and verify integrity and authorship without a backend dependency.

Open settings View template

Theme: ledger-dark
Surface: Signed ordered history
Input: Entries linked in sequence
Output: Replayable JSON ledger

Features

Ordered signed history without a backend

Ledger focuses on one job well. Keep an append-only history of records that can be replayed and verified later.

Append-only records

Add new entries without mutating the history that came before them.

Signed entries

Attach integrity and authorship to each record using portable signing primitives.

Linked history

Chain entries together so ordering and continuity can be verified over time.

Replayable exports

Export a ledger file that can be checked, replayed, and reasoned about anywhere.

1: Create an entry
2: Link and sign it
3: Replay and verify

How it works

Build a verifiable chain of history

Create the entry
Capture the event, payload, or record you want to append to the ledger.
Link and sign it
Reference the previous ledger state and sign the new entry with the local identity.
Replay and verify
Validate ordering, continuity, and signer integrity by replaying the exported ledger.

Use cases

Built for ordered history

Audit trails

Keep an append-only history of actions, approvals, and changes that can be verified later.

Signed timelines

Preserve not just what happened, but who appended each step in the chain.

Browser-native logs

Build local-first histories inside web apps without needing immediate server infrastructure.

Export histories

Package a portable timeline of records alongside exports, backups, or snapshots.

Reproducible state

Rebuild state by replaying ordered entries instead of trusting hidden mutable storage.

Foundation layers

Use Ledger as the history primitive beneath richer tools, demos, and protocols.

Developers

A browser primitive for ordered signed history

Ledger sits alongside signing and encryption as the history layer in the ternent suite. It gives browser-native systems a portable append-only record model.

Web app

CLI

Docs

ledger:
  entries:
    - id: entry-0001
      prev: null
      type: note.created
      payload:
        title: First entry
      signature:
        keyId: key:demo

Keep ordered history in a portable structure so the ledger can be exported, replayed, and verified safely.

Open the template source

Ledger is

An append-only record format
A way to preserve ordered signed history
A replayable browser-native primitive

Ledger is not

A blockchain
A consensus network
A database replacement
A hidden server dependency

Ready to start?

Start building verifiable history

Create entries, append them to a signed chain, and export a ledger that can be replayed and verified anywhere.

Open settings Inspect template

Append entries. Preserve history. Verify the chain.

Signed ledger record