About
You would not hand your bank statement to a stranger. Yet every payment on a public blockchain is permanently visible to anyone who looks. Lucent fixes that without hiding who you paid, only how much.
The problem
Public blockchains expose every transaction to everyone, forever. Salaries, vendor payments and treasury moves are readable by competitors, data harvesters and anyone with a block explorer.
Existing privacy tools such as mixers, shielded pools and opaque coins hide everything. You lose the auditability that makes a blockchain useful, and compliance becomes impossible.
The approach
Addresses stay visible on-chain. Amounts are held as Pedersen commitments and moved with zero-knowledge proofs. You can verify that wallet A paid wallet B, but not how much.
Payroll goes out without exposing salaries. Escrow settles without revealing the locked sum. Your history never becomes a public business-intelligence dataset.
Trust model
Every proof is generated in your browser and verified natively by Stellar's Protocol 26 host functions. There is no separate privacy infrastructure to trust.
No private key exists that could be stolen to decrypt your balances. The encryption is enforced by mathematics, not by a trusted party.
Your USDC stays in Soroban contracts on Stellar. There is no bridge, no wrapped token and no custodian holding your funds.
Who it is for
Pay contributors and vendors without publishing your treasury's payment history to competitors.
Run payroll with per-person confidential salaries. No member can see another's compensation.
Invoice and get paid in USDC without your client list and rate card becoming public record.
Need confidential escrow in your settlement layer? Integrate PrivateEscrow into your Soroban contracts.
Built on
Protocol 26 shipped native ZK host functions that verify UltraHonk proofs on-chain without a coprocessor. Lucent builds on OpenZeppelin's confidential-token module, Pedersen commitments, Poseidon2 hashing and a Rust contract stack to bring amount-hidden payments to Stellar.