Make existing financial accounts provable.
xln starts with the structure of existing finance: Jurisdictions, Entities and bilateral Accounts (J/E/A). It makes their state replicable and verifiable, and their account obligations signed and disputable on programmable J-machines. The Reserve-Credit Provable Account Network (RCPAN) combines chosen credit, collateral and programmable conditions in one account model.
MML: by 2050, make the accounts supporting 51% of world GDP provable. Ordinary payments and swaps update accounts locally; the underlying jurisdiction enforces registration, collateral, settlement and disputes. GDP coverage, economic turnover and technical throughput are separate measurements.
- xln in five minutes — existing finance, J/E/A, MML and the three protections: proof, collateral and Delta Transformers.
- Unified Financial Theory — the financial model and its implementation through xln.
- RCPAN invariant — the bilateral financial bound.
- Runtime → Entity → Account → Jurisdiction — the canonical implementation model.
- Documentation index — theory, specs, runtime, security, operations, and release evidence.
For comparisons, read the architecture argument. Implementation and release claims require evidence about the actual candidate.
xln/
├── core/ deterministic Runtime, Entity, Account, and boundaries
├── rscore/ Rust implementation of the canonical financial machines
├── brainvault/ standalone deterministic wallet-derivation package
├── jurisdictions/ Solidity settlement and dispute contracts
├── ui/ React wallet at /ui/; presentation and user input
├── frontend/ Svelte wallet at /app; presentation and user input
├── tests/ browser and full-stack E2E evidence
├── docs/ canonical documentation and immutable release evidence
├── scripts/ build, release, and operator tools
├── tools/ repository checks and evidence tooling
├── ops/ deployment and operating configuration
└── .archive/ historical source implementations; never live authority
core/runtime.ts is the narrow public facade. Core behavior belongs to its
owning Runtime, Entity, or Account module; physical I/O remains outside the
deterministic state-machine transitions.
BrainVault V1 is an independently packable, installable,
and auditable memory-hard wallet-derivation module. It has its own package,
frozen byte specification, vectors, native sources,
binaries, manifest, CLI, and tests entirely inside brainvault/; it does not
import XLN runtime, storage, network, frontend, or consensus code.
XLN is one consumer. Its terminal onboarding, browser wallet creation, remote runtime adapter, and recovery tests call BrainVault's public derivation and worker interfaces. Engine choice and XLN state never enter the frozen root.
Run and audit only BrainVault without starting XLN:
cd brainvault
bun install --frozen-lockfile --ignore-scripts
bun ./brainvault --smoke
bun ./brainvaultThe exact minimal and expanded reading paths are in BrainVault's audit surface. Coding agents must also load its package-local contract.
bun install
bun run dev
open https://localhost:8080The canonical release identity is VERSION, mirrored by
package.json. Do not infer the current version from prose or historical
changelog entries.
RuntimeInput
├─ RuntimeTx[]
└─ routed EntityInput[]
└─ EntityTx[]
├─ accountInput → exact child AccountInput
└─ financial intent → local AccountTx[] admission
Each live replica follows one deterministic transition law:
(previous replica, input) → { next replica, outputs }
- Runtime is the single writer and owns WAL commitment before external effects.
- Entity certifies organization-level state and routes exact child inputs.
- Account owns bilateral financial mutation, proposals, ACKs, and dispute proof.
- Jurisdiction enforces registration, collateral, settlement and disputes; J adapters bring verified jurisdiction observations into Runtime inputs.
- Outputs move upward as deterministic data; network and chain I/O begin only after the enclosing Runtime frame is durable.
The complete vocabulary and ownership rules are in the canonical cascade guide.
bun run dev # full local stack
bun run check # repository verification gate
bun run build # browser runtime bundle
bun run test:e2e:fast # focused browser/full-stack bar
bun run test:e2e:full # complete E2E suite
bun run test:contracts # Solidity testsUse Bun throughout the repository. Solidity and frozen-core changes have separate owner-controlled integrity gates.
- Architecture comparison
- Canonical cascade
- Payment and HTLC flow
core/runtime/frame/process.ts— Runtime transition and WAL orderingcore/entity/consensus/input/consensus.ts— Entity transition entrycore/account/consensus/index.ts— bilateral Account consensuscore/account/tx/apply.ts— financial validation and mutation dispatchcore/storage/commit/commit.ts— durable Runtime commit boundary
Audit reports and release artifacts are evidence about particular bytes and dates. They are not live architecture documents and are not a substitute for reading the current canonical path.
- Active work and blockers
- Minimum remaining work and accepted timing policy
- Current status
- Mainnet release bar
- Mainnet acceptance gate
- Signed release manifest
- Security evidence
These sources intentionally remain separate from the architecture verdict.
AGPL-3.0 · xln.finance