Verify Once,
Accepted at every anchorReusable identity layer
for Stellar ecosystem

Building on Stellar ecosystem

Join WaitlistAbout us

The Problem

For Users

Users uses the same document every single time to verify a new Stellar Anchor. Most users drop before completing KYC that lead to 40–50% drop-off rate.

For Anchors

Anchors cannot reuse verified identity from other providers, so they pay for the same KYC again and again, even when users abandon midway.

For Ecosystem

Duplicate checks drain tens of millions of dollars yearly across every Stellar Anchor and waste time for users to reverify. The network is missing shared identity infrastructure.

How we solve it

StellarProof creates a reusable ZK credential tied to your Stellar wallet.
Anchors verify the proof, not your documents — ever.

1

User signs SEP-10 challenge

Authentication

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

2

Routes to cheapest govt rail

Routing

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

3

KYC provider verifies identity

Verification

The licensed KYC provider performs 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 is passed to the zero-knowledge proof layer, which runs entirely client-side on the user's own device. StellarProof's servers never see the data.

5

ZK proof generated locally

BN254 + Poseidon

A zero-knowledge proof is 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 is recorded on-chain as permanent, tamper-proof evidence that verification occurred. No personal data ever touches the chain.

7

ZK credential stored in user's wallet

User-owned

The full ZK credential lives exclusively in the user's own wallet. StellarProof never stores, sees, or has access to it.

8

Anchor receives proof — not PII

Privacy-first

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

Result: User is verified, credential lives in their wallet, anchor received proof — not PII. StellarProof never stored or saw the identity data.

Why use StellarProof?

For Anchors, dramatically cut KYC costs

Stop paying for the same user twice. StellarProof reuses 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.35
Returning user$1.35 again
Drop-off rate60 – 80%
With StellarProof
First verification$1.35
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

Join Waitlist

Be the first anchor to go live.
Early Anchors get a surprise when we launch 😉

Unsubscribe anytime.