Profile
Back to NewsBack
GitHub Trending 3 min
Reader Mode
Stellar-Clear/clearledger: Invoice finance infrastructure on Stellar: Soroban contracts, a Next.js app, TypeScript SDK and CLI, and Go indexer for USDC-backed workflows.

Stellar-Clear/clearledger: Invoice finance infrastructure on Stellar: Soroban contracts, a Next.js app, TypeScript SDK and CLI, and Go indexer for USDC-backed workflows.

14 hours ago

ClearLedger

Invoice finance infrastructure, built on Stellar and powered by Soroban.

ClearLedger is an open-source invoice-finance platform built on Stellar. Its Soroban smart contracts coordinate participant verification, invoice lifecycle state, USDC liquidity pools, and settlement flows. The complete stack brings together on-chain contracts, a web application, TypeScript SDK and CLI, and a Go indexer/API.

Launch the Stellar Testnet app · Explore the Soroban contracts · Read the documentation · View Testnet contracts

Built for Stellar

ClearLedger uses Soroban, Stellar’s smart-contract platform, to coordinate business identity, invoice records, pool shares, and USDC flows on Stellar. The TypeScript SDK and web app connect to Soroban contracts, while the Go indexer follows contract events to make network activity available to applications.

The workflow

  1. Onboard participants. Register SME issuers and trade buyers through the participant registry.
  2. Create invoice records. Issuers record invoice terms and progress through explicit on-chain lifecycle states.
  3. Coordinate liquidity. USDC pool contracts account for liquidity, invoice funding, LP shares, and repayment flows.
  4. Follow activity. The Go indexer consumes Soroban events for API access and application views.
The protocol records submitted transaction state. It does not independently verify commercial documents, guarantee that an invoice will be funded, or guarantee repayment or returns.

Project map

| Path | What lives here | | --- | --- | | apps/web/ | Next.js application and public product experience | | packages/sdk/, packages/sdk-react/ | TypeScript contract clients and React hooks | | packages/cli/ | Developer command-line tools | | indexer/ | Go Soroban event indexer and HTTP API | | examples/ | SDK and integration examples | | docs/ | Protocol, user, and developer documentation, including analytics metric definitions |

Soroban contract source and deployment details live in the companion contracts repository.

Run locally

Requirements: Node.js 20+, pnpm 9+, and Docker for the complete local stack. For wallet interactions, install Freighter and select Stellar Testnet.

pnpm install
cp .env.example .env.local
pnpm dev

The web app starts at http://localhost:3000. For a guided Testnet walkthrough covering Freighter and a read-only Soroban call, see the Stellar Testnet quickstart. For the web app, Go indexer, and PostgreSQL together:

cp .env.docker.example .env.docker
docker compose --env-file .env.docker up --build

The hosted app is a testnet web deployment. The Go API/indexer must be run separately; configure NEXT_PUBLIC_API_BASE_URL for the API endpoint when using API-backed features. For the complete variable reference, see environment configuration.

Development

From the repository root, the main checks are pnpm build, pnpm lint, pnpm typecheck, and pnpm test. Run Go checks from indexer/ with go test ./... and go vet ./....

Start with the local setup guide, architecture overview, and contribution guide. For protocol details, see how it works, the invoice lifecycle, and the economic model.

Network and security

The web application and contracts are currently deployed on Stellar Testnet for evaluation and integration. This is not a mainnet financial service. The contracts have not been formally audited, and testnet assets have no promised redemption value. Do not use real funds. Review the contract limitations and security policy before integrating.

Before planning any Mainnet deployment, read the production readiness gates. They record the audit, deployment, RPC, API, monitoring, wallet, recovery, and compliance work that is still required; the current Testnet setup does not satisfy them.

Use testnet wallets and assets only. Never put private keys or recovery phrases in environment files or source control.

For tested keyboard flows, known limitations and the reporting route, read the accessibility statement.

Chat with me