The amount is
the only secret.

Sender and receiver are public. Only the number is encrypted — with ZK proofs verified natively on Stellar. Same chain, same finality, different visibility.

Powered byStellar Protocol 26·Soroban testnet

How it works

Private payments in three steps

01

Deposit USDC

Move public USDC into a confidential balance in one transaction. From then on your balance is a Pedersen commitment, not a number.

02

Pay Privately

Send, run payroll, lock escrow. Every amount is proven with a zero-knowledge proof generated right in your browser.

03

Stay Auditable

Sender and receiver stay on-chain and public. The auditor key can decrypt every amount for compliance — nobody else can.

Features

The relationship stays public. The number doesn't.

Private Payments

Sender and receiver are public. The amount is not — hidden behind a commitment and a proof, not an assumption.

Confidential Payroll

Employee addresses are on-chain. Salary amounts are not. No colleague can read another's, even on a public explorer.

Encrypted Escrow

The locked amount stays hidden through creation, dispute, and release. Parties and finality are public. The number is private.

Selective Disclosure

Prove a specific transfer paid exactly one amount to one counterparty — without revealing anything else, on-chain or off.

Live on testnet

Real activity, verifiably private

Registered Addresses

Confidential accounts bound to a Grumpkin key

Confidential Transfers

Send, payroll, and escrow payments — amount hidden

Merges

Receiving balance folded into spendable

View full stats

Privacy that works for real payments.

Most privacy tools hide identity and break compliance. Lucent encrypts only the amount — the relationship stays auditable, on the same chain, with the same finality. No off-chain operators, no custodians, no separate infrastructure.

Stellar Protocol 26 · Soroban testnet