What problem it solves

Fintech applications need a reliable system of record for wallets, payouts, marketplaces, billing, and agent-initiated payments. They also need exact monetary arithmetic, enforceable spending controls, and evidence that the recorded history has not been altered.

Key features

• Exact double-entry accounting — Records transfers, payouts, billing activity, reservations, and refunds in exact integer units. Each applied transfer balances debits and credits, while deterministic splits distribute amounts across ledger legs.

  Source: README

• Verifiable audit chain — Provides read-only accounting replay, versioned audit chains, and exportable checkpoints. Verification can compare audit roots against independently retained anchors and report pending coverage or tampering separately.

  Source: README

• Server-enforced agent guardrails — Applies per-key currency and precision limits, allowlists, daily budgets, reservations, and approval holds. Delegated keys inherit restrictions and share ancestor budgets, while independent approver credentials remain outside an agent's authority.

  Source: README

• Multiple integration surfaces — Can be used through an HTTP API, a Go library, or a local MCP server. PostgreSQL stores financial records, while Redis supports queues and background workers.

  Source: README

• Financial lifecycle workflows — Supports inflight reservations, partial settlement, refunds, split and bulk transfers, reconciliation, lineage, and snapshots. Idempotent references allow safe retries after timeouts without changing prior balances.

  Source: README

Quick start

Copied verbatim from the project's README.

git clone https://github.com/devaccuracy/ledgerforge.git
cd ledgerforge
./examples/quickstart/start.sh
./examples/quickstart/transfer.sh

Who it may suit

Inference: may suit teams building wallets, payout systems, marketplaces, usage-based billing, or AI-agent payment workflows that need an open-source ledger with explicit accounting and spending controls.

Topics to discuss

• Which accounting models and external payment rails should the community document next?

• How should delegated API keys and independent approval workflows be structured for AI agents?

• Which verification and audit-anchoring workflows should receive community examples and tooling?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/devaccuracy/ledgerforge#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.