Lunareth Core

Sample receipt ledger

Three fictional entries appear in one normalized ledger for demonstration. Entries show a pseudonymous agent identifier, a generic rail label, a sample amount, a status, and a date only.

SAMPLE Rail A · rct_SAMPLE_001

Agent (pseudonymous ID only): agt_SAMPLE_7f3a91

0.25 USDC Illustrative pricing, not an offer.

Status: recorded · Occurred: 2026-10-01

SAMPLE Rail B · rct_SAMPLE_002

Agent (pseudonymous ID only): agt_SAMPLE_c24e07

49.00 USD Illustrative pricing, not an offer.

Status: recorded · Occurred: 2026-10-02

SAMPLE Rail C · rct_SAMPLE_003

Agent (pseudonymous ID only): agt_SAMPLE_e9b3d5

12.50 USDC Illustrative pricing, not an offer.

Status: recorded · Occurred: 2026-10-03

Demo only

How verification is planned to work (not live)

  1. Canonicalize (planned) Each receipt would be serialized to a canonical, deterministic byte form.
  2. Sign (planned) Lunareth would sign the record server-side. Signing scheme: Ed25519 v1. Signing is planned, not live, and nothing is deployed or live.
  3. Verify (planned, server-side only) Lunareth would check its own signed record on its server and return only confirmed public verification fields: valid, signature_valid, public_id, rail, amount_minor, currency, occurred_at, signed_at, and agent as a pseudonymous ID only.