CHIP Glass Ledger

The public money tape.

Aggregate chip-ins, expenditures, corrections, and outcomes shown line by line. No donor names. No dark spending.

Read how the ledger works Jump to demo ledger Download sample CSV

Demo/static ticker strip

CHIP-00042 +$847.20 Platform fee revenue CHIP-00041 -$312.50 Payment processing CHIP-00040 -$1,240.00 Infrastructure CHIP-00039 +$2,480.00 Aggregate chip-ins

Demo state: static HTML.

CHIP has not connected this page to a live transaction source yet. The sample lines below show the public fields the Glass Ledger will expose once real money is moving. When the live source exists, this page should read from that source without changing the privacy boundary.

Status: Demo data
Source: Static HTML
Refresh: None yet
Privacy: Aggregate only

Aggregate snapshot.

Total aggregate chip-ins

$2,480.00 Demo sample

Published expenditures

$1,552.50 Demo sample

Correction lines

1 Append-only

Open outcomes

2 Linked when available

Demo ledger feed.

These rows are aggregate examples. They do not represent live CHIP transactions, individual donor records, receipts, or payment processor data. The same sample is available as CSV and JSON for review.

Demo CHIP Glass Ledger lines
Line ID	Posted	Direction	Amount	Category	Boss / Earmark	Description	Status / Outcome
CHIP-00042	2026-06-04 14:30 ET	In	+$847.20	Platform fee revenue	CHIP operations	Platform fee revenue - Flagship Arcade May volume	Posted
CHIP-00041	2026-06-04 14:20 ET	Out	-$312.50	Payment processing	CHIP operations	Payment processing sample costs for May sample volume	Posted
CHIP-00040	2026-06-04 14:10 ET	Out	-$1,240.00	Infrastructure	CHIP operations	Database and hosting infrastructure for May	Posted
CHIP-00039	2026-06-04 13:55 ET	In	+$2,480.00	Aggregate chip-ins	Sunlight FOIA Batch	Aggregated player chip-ins for the sample objective	Outcome pending
CHIP-00038-C1	2026-06-04 13:45 ET	Correction	$0.00	Correction	Sunlight FOIA Batch	Corrects category label on CHIP-00038; original line remains visible	Corrected

Field definitions.

The live ledger source is pending. These public fields define the proof contract before launch.

CHIP Glass Ledger public field definitions
Field	Meaning	Public boundary
line_id	Stable public identifier for the posted line.	Safe to expose.
posted_at	Timestamp when the public aggregate line is posted.	Rounded or batched if needed to protect donor privacy.
direction	In, out, or correction.	Safe to expose.
amount	Aggregate money amount for the public line.	No individual donor amount when that could identify a person.
category	Revenue, expense, correction, outcome, or other campaign-approved category.	Safe to expose after review.
boss_or_earmark	The public objective the money is tied to.	Safe to expose when the objective itself is public.
description	Plain-English explanation of the movement.	Must not contain donor identity, payment references, or private notes.
status	Posted, outcome pending, corrected, or linked outcome state.	Safe to expose.
correction_of	Original line id corrected by a later line.	Safe to expose; original line stays visible.

What this page will never expose.

The Glass Ledger publishes money movement, not people. Public lines are aggregated and categorized so anyone can audit the arcade without turning donors into public records.

Donor names
Donor IDs
Player emails
Payment identifiers
Personal receipt history
Player-set caps
Player preferences
Individual donation timing that can identify a person

Corrections are new lines, not edits.

A posted line is never edited or deleted. If a category, description, or outcome needs correction, the ledger appends a correction line that references the original line ID. The mistake and the fix stay visible together.

Example: if CHIP-00038 was posted under the wrong category, CHIP appends CHIP-00038-C1 with correction_of=CHIP-00038. The corrected category appears in the new line; the original remains part of the public record.

Future real-source implementation should preserve stable line IDs, correction references, downloadable exports, and the readable table structure shown here.

Real source later. Same public contract.

For this marketing-site slice, ledger rows are static demo HTML. When the CHIP platform exposes the real public read source, replace only the data population layer. Keep the same route, canonical URL, field names, privacy exclusions, no-tracking posture, and accessible table structure.

The future source should still degrade to readable HTML. If fetch behavior is added in another issue, it should be progressive enhancement, not a required app shell.