Repository navigation
v2.6.1
A small patch release: an independent security audit of v2.6.0 found three bugs, and all three are fixed. Nothing about how antiRea works changes for normal users - no upgrade steps, no new settings.
- A borrowed "receipt number" no longer works. Every reservation carries an idempotency key - think of it as a receipt number for "I already paid for this". Before, anyone who learned another account's receipt number could present it as their own and spend from that account's budget. Now the receipt is checked against what it was first issued for, on both ledgers; a mismatch is refused, and reservations written by older versions (which carry no fingerprint yet) fail closed for the few minutes they have left to live.
- A broken database can no longer crash your app. If the storage behind the ledgers broke or returned garbage, the SDK used to throw raw errors into your request handling - in the audit's live test, a dead store killed the host process on its very first request. Now the SDK answers with a clean refusal instead (an HTTP 429 "store unavailable" style decision) and your process stays up.
- Huge record IDs are cheap again. The ledger used to keep a checklist with one box for every possible ID, so a single record with ID 100,000,000 bloated the saved state to 16.7 MB. It now keeps a sparse checklist that only grows with the number of records you actually have: that same case takes 3 ms and 1,745 bytes of state (was 1,439 ms), and states saved by older versions still load.
Full technical write-up: v2.6.1 deep dive (docs/v2.6.1-deep-dive.md in this repo).