Stop paying for the same user twice

ZK Proof Reusable KYC infrastructure for Stellar anchors

Get Early Access
StellarProof

Problem

For Users

Users have to re-upload the same documents every time they use a new Stellar anchor. Most abandon the process before finishing, industry estimates put drop-off as high as 60%.

For Anchors

Anchors can't reuse verified KYC from other providers already completed, so they pay for the same KYC again and again, even for users who are already compliant elsewhere.

For Ecosystem

Every duplicate check costs real money and real time, for anchors paying repeatedly, and for users waiting again. Stellar has no infrastructure for reusing a verification once it's done.

How we solve it

StellarProof is building a reusable ZK credential tied to User Stellar wallet.

1

User will sign a SEP-10 challenge

Authentication

Wallet-native authentication — the user will prove ownership of their Stellar account with a single signature. No passwords, no accounts to create.

2

Will route to cheapest govt rail

Routing

StellarProof will automatically route the user to the fastest, cheapest government-backed KYC provider for their country — DigiLocker, PhilSys, Smile ID, and more.

3

KYC provider will verify identity

Verification

The licensed KYC provider will perform the actual verification. Compliance copy retained by the provider under their own regulatory obligations (FATF/AML).

4

Verified data → ZK proof layer

Client-side

Verified credential data will be passed to the zero-knowledge proof layer, which will run entirely client-side on the user's own device. StellarProof's servers will never see the data.

5

ZK proof will be generated locally

BN254 + Poseidon

A zero-knowledge proof will be generated on the user's device using BN254 + Poseidon cryptographic primitives, leveraging Stellar Protocol 25's native support.

6

SHA-256 proof hash anchored on Stellar

On-chain

A SHA-256 hash of the proof will be recorded on-chain as permanent, tamper-proof evidence that verification occurred. No personal data will ever touch the chain.

7

ZK credential will be stored in user's wallet

User-owned

The full ZK credential will live exclusively in the user's own wallet. StellarProof is designed to never store, see, or have access to it.

8

Anchor will receive proof — not PII

Privacy-first

The anchor will receive a cryptographic proof that the user is verified — never the underlying documents, passport scans, or personal information.

Result: User will be verified, credential will live in their wallet, anchor will receive proof — not PII. StellarProof is designed to never store or see the identity data.

Why use StellarProof?

For Anchors, dramatically cut KYC costs

Stop paying for the same user twice. StellarProof is built to reuse verified credentials under a flat subscription — returning-user checks are included at no extra per-verification cost.

Exact cost-reduction percentage to be published once subscription pricing is finalized.

Without StellarProof
Per verification$1
Returning user$1 again
Drop-off rate60 – 80%
With StellarProof
First verification$1
Returning userIncluded in subscription
Drop-off rate2 - 5%

For Users, cut time by 90%

Verify once with any Stellar anchor. Reuse your credential across the ecosystem.

Without StellarProof
KYC submissionsEvery app, every time
Verification wait1 - 3 days
Time per verification3 - 5 mins
With StellarProof
KYC submissionsVerify once
Verification waitNear instant
Time per reuse verification10sec

Get Early Access

StellarProof is building toward an initial anchor pilot. Early collaborator anchors get first access once the system is live, and direct input into what gets built next.

Unsubscribe anytime.