XRPL Ledger

The Ledger Backpack tracks your 5 core supplies as tokens on the XRPL Testnet. Every town checkpoint records a settlement receipt on-chain. At the end of your run, your trail ledger includes transaction IDs anyone can verify.

Completely optional. The game plays identically with it off (the default).

Token types

Token	Resource	What it tracks
FOOD	Food supply	Consumption, hunting gains, trading
WATR	Water supply	Auto-refill at towns, terrain drain
MEDS	Medicine	Party health recovery
AMMO	Ammunition	Hunting costs, event rewards
PART	Spare parts	Repair action costs, trading

Enabling the backpack

From the TUI, press L to open the ledger menu. Or via CLI:

# Enable the backpack
trail ledger enable

# Check status
trail ledger status

# View wallet details
trail ledger wallet

Settlements

At each town checkpoint, the game batches all supply changes since the last settlement into a single XRPL transaction. This keeps costs low and the ledger clean.

# Manually trigger a settlement
trail ledger settle

# Retry failed settlements
trail ledger reconcile

Parcels

Players can trade supplies with each other on the XRPL Testnet:

# Share your address so others can send you supplies
trail wallet share

# Send supplies to another traveler
trail parcel send <address> food 10

# List received parcels
trail parcel list

# Accept a pending parcel
trail parcel accept <id>

# See what you've sent
trail parcel sent

Parcels arrive as pending and must be explicitly accepted before supplies are added to your inventory. You can also refuse parcels.

Reconciliation Proof (Audit Mode)

The settlement receipts make a claim: this is what your supplies did, recorded on a public ledger. The reconciliation proof checks that claim against the ledger itself.

Audit mode replays a run’s settlement receipts and reads the memos back off the XRPL Testnet — pulling the transactions through AccountTx and verifying the on-chain memos directly, rather than trusting whatever the local save happens to say. The check is genuinely external: the engine reports against the chain, not against its own copy. The supply history of a run can be independently audited, and the engine cannot fake the ledger — anyone with the transaction IDs can walk the same trail of memos and confirm or refute it.

This sits on top of the optional backpack — itself optional. It is for runs where the on-chain history is the point: proof that the supplies moved the way the journal says they did, settled and checkable by a stranger.

If a settlement failed and left the chain incomplete, trail ledger reconcile retries the pending settlements first; the proof is only as complete as the receipts that actually landed.

Run Artifacts

Every finished run leaves a keepsake. The end-of-run screen surfaces an XRPL postcard — a small on-chain memento of the journey — alongside the run’s stats and an export/share path, so a finished run leaves something you can keep and pass along. The postcard is drawn from the same ledger that recorded your supplies, which is why it lives here rather than in the engine alone.

Requirements

• pip install -e ".[xrpl]" for the xrpl-py dependency
• XRPL Testnet only — no real value, no mainnet support
• Internet connection for settlement transactions

Security

• All XRPL operations use Testnet exclusively
• Wallet keys are stored locally, never transmitted except for signing
• No telemetry, no accounts, no cloud state
• See SECURITY.md for the full threat model