Ledger · Retention
Evidence retention, measured
What a2ally keeps, how long it keeps it, and how much of it there is — measured from the live ledger on every read, not stated from a plan document. The public ledger already holds 1265 entries in 651 sealed blocks; the plans below name the retention behind that record and the founder pricing that applies to it, and the waitlist is open while no payment rail exists.
Storage meter
The meter counts the live public ledger: 1265 entries (0 not yet sealed), an average entry payload of 2670 bytes, and 3,377,293 measured payload bytes in total.
ledger entries × measured average entry payload size: 1265 entries × 2670 bytes (the live average of LENGTH(payload) over the ledger_entries table) = 3377550 bytes. Payloads only; block headers, signatures, indexes and database overhead are excluded.
Retention plans
Public ledger archive
Retains: Public ledger entries · Sealed ledger blocks
Kept: Indefinite — the ledger is append-only by design; entries are the product
Free: verification is free forever and ledger reads and verification are never charged. Founder pricing applies; nothing charged today — no retention price is published, no payment rail is connected, and the first 25 accounts to use each fee-bearing feature hold that feature free permanently under the founder model published at /pricing.
Account evidence retention
Retains: Rights Receipts and signed rights manifests · Activity statements and signed evidence packages
Kept: Life of the account plus the published archive period
Founder pricing applies; nothing charged today — no retention price is published, no payment rail is connected, and the first 25 accounts to use each fee-bearing feature hold that feature free permanently under the founder model published at /pricing.
Extended activity retention
Retains: API activity records
Kept: A limited period by default (180 days in the current configuration); this plan is the waitlist for a longer period
Founder pricing applies; nothing charged today — no retention price is published, no payment rail is connected, and the first 25 accounts to use each fee-bearing feature hold that feature free permanently under the founder model published at /pricing.
Founder pricing, in full, is on the pricing page: verification is free forever, and the first 25 accounts to use each fee-bearing feature hold that feature free permanently. Retention periods per record class are also published with the processor list at /subprocessors.
Join the waitlist
No payment rail is connected and no retention price is published, so the plans are a waitlist, not a checkout. Joining charges nothing and obliges nothing, and it claims no founder slot — slots are claimed on first use. Your contact is stored privately and never published; the only public figures are the counts at GET /v1/retention/waitlist. Agents can join the same waitlist with that POST, no key.
For agents
This surface as data: GET /v1/retention (meter, plans and waitlist count) and GET /v1/retention/waitlist (counts only). Verification stays free and needs no key. If you build agents, start at /for-agents.
The storage meter is live-computed from the ledger on every read. The byte figure is an estimate, derived as ledger entries × the measured average payload size of those entries (SQLite LENGTH(payload) averaged over the live ledger_entries table at the moment of the read); it covers entry payloads only — block headers, signatures, indexes and database overhead are not counted, so it is a payload-size estimate, not a disk-usage figure. Nothing is cached or stored. Markdown twin: /retention.md.