Changelog
0.1.15606 · 5 November 2026
Store upkeep that keeps up, and a transaction database that stays small.
- Fix Some ledgers were saved incomplete, which stalled store upkeep. When a flag ledger (every 256th) changed the network's list of temporarily disabled validators, part of it wasn't written to disk; this came in with 0.1.15325. A compaction round then failed on the missing piece and backed off for up to six hours while the store grew. Those ledgers are now saved whole, and the node can also recover such a piece it still holds in memory during later saves. On our mainnet test Mac, with that recovery alone, 32 rounds in a row passed over 15 hours across two test builds of this release; before, 76 of 513 had failed since 17 October.
- Fix Transaction history stays small, pruned in small batches. The node prunes old history on its own schedule and gives the space back to the disk. On mainnet, transaction.db measured about 100 to 275 MiB when sampled, plus a write-ahead log of up to about 230 MiB; before, it had reached about 24 GiB. Deleting a long stretch in one go had once stalled our test node for 72 seconds and taken it out of sync; in our two test runs the 68 recorded prunes took 0.05 to 2 seconds each, 0.9 typically.
- Fix A possible crash when loading a ledger that is missing a piece, and a bug that skipped every attempt to recover missing ledger data after the first.
- Change Turning transaction history off removes the history kept so far, the next time the node starts. Before, the file stayed at its old size.
- Change Updated the bundled transaction-queue settings (a minimum and target of 256 transactions a ledger, a maximum of 500).
- Correction, in 0.1.15447's entry below: the order-book scan doesn't repeat every 25,600 ledgers; it runs again only when the node returns to full that long after its last successful scan. And its 40 seconds was on a freshly synced store; on a store that upkeep had rewritten we observed about 16.
0.1.15447 · 19 October 2026
Order books are back, on a much lighter scan.
- New Order books are back on. Pathfinding and order-book subscriptions can use the ledger's books again. The node scans the current state once it first reaches full after startup, and again only when it returns to full 25,600 or more ledgers (about 28 hours) after its last successful scan; offers and AMMs it applies add their books in between. In our mainnet tests the scan took 16 to 40 seconds, quicker once store upkeep has rewritten the store, and retained an index of about 11 MiB. (Corrected in 0.1.15600: this said the scan ran "every 25,600 ledgers" and took "about 40 seconds".) The old scan peaked above 500 MiB and left roughly 250 MiB above its pre-scan footprint five minutes later.
- Better Less retained cache memory after large bursts. The ledger-node cache now releases excess hash-table capacity during its sweeps.
- Fix Upstream allocator fixes for unused pages that could remain held after their purge delay.
0.1.15411 · 18 October 2026
Better use of limited memory, with less repeated work while syncing.
- Change The first sync works through nearby branches of the ledger in small groups, keeping related data together, so it copes much better when memory is tight. With memory to spare it takes about as long as before.
- Better Less repeated work while syncing and catching up: fewer repeated storage reads and checks, and no flush when nothing new needs saving.
- Fix Fewer repeated requests to peers. While streaming is making progress, the node keeps recent requests instead of immediately asking for the same data again.
- Fix An unfinished first index build can be cancelled when quitting and rebuilt from saved data later.
- Fix A possible crash as the first sync finishes.
- Better Click RAM for a fuller explanation of the node's memory, macOS's file cache, and why syncing slows down when memory is tight.
- Better A shorter About window, with a link to the full story on pocketxrp.com/about.
0.1.15325 · 17 October 2026
Catches up on less CPU after your Mac sleeps, and peaks much lower while syncing.
- New Stream when far, pounce when close. A state machine now fetches ledgers.
- Far: when the node falls a few ledgers behind (say, after your Mac sleeps), it streams straight to disk, as only the first sync did before, until it's within a couple of ledgers.
- Close: it pounces, fetching the rest the ordinary way, concurrently and in RAM.
- While streaming: it ignores relayed transactions it can't use yet.
- Better A tiny build cache. For the majority of ledgers, KeyDom reads are fast enough to do without a standing cache, but we introduced a tiny cache that speeds up processing spiky, large ledgers using minimal heap.
- Better Click RAM in the menu for how to read it, and how it compares with Activity Monitor and top.
- Fix The menu holds still while it updates. The item under your pointer no longer loses its highlight as the numbers tick.
- Change Live Ledger after a sleep. It jumps to the newest ledgers. The ones missed while asleep aren't fetched, apart from the last few.
0.1.15281 · 17 October 2026
- New The node restarts itself if it stops unexpectedly (on; in Settings).
- New Transaction history can be turned off in Settings.
- New A setting to map the store into memory for faster reads (off; uses more RAM).
- Fix A rare hang at start-up.
- Fix Log rotation retries if it fails.
0.1.15248 · 17 October 2026
- Fix Very busy ledgers apply about 25% faster again.
0.1.15230 · 16 October 2026
- Fix Very busy ledgers were slow to apply; they're now about 4× faster.
- New An update notice (checked once a day; off in Settings).
- Better Clearer start-up status.
- Fix Logs stay small.
0.1.15218 · 16 October 2026
The first public release.
- A full XRP Ledger node for Apple silicon Macs, in the menu bar. It applies each ledger's transactions itself and checks the result against the network's trusted validators: a full node, not a light client.
- Runs in the macOS App Sandbox: the app and its node can reach the network and the app's own data folder, and nothing else.
- Signed with a Developer ID and notarized by Apple.
- Keeps its own store tidy, in the background, without stopping: soon after its first sync it rewrites the store, then trims it each time it has grown by the amount set in Settings (2 GB by default).
- A simple menu: "Following mainnet" once the node holds validated ledgers, "full" once it's in step with the network, then the latest ledger, the ledgers it holds, uptime, RAM, disk, and what the store's upkeep is doing.
- A Live Ledger window: the ledgers and transactions your node is following, as they close, from its own stream (ws://127.0.0.1:16006). Click one to open it on xrplwin.com.
- Settings in plain words, and an About window that explains the trade-off: fast reads and low RAM, paid for with a little extra disk.
- Uses 75–175 MB of RAM (~250 MB peak on a 1,800-tx ledger) and 6–11 GB of disk (~20 GB peak while rewriting). A 19 MB download.