SPECTER

Private payments on Ethereum and Sui, built for a post-quantum world

Your wallet address shouldn’t be your identity

Every time someone pays you on Ethereum, your address becomes a little less private. Employers, clients, strangers on Etherscan… they can all follow the money back to you.

SPECTER fixes the receiving side. You publish one public profile. Every sender derives a fresh, one-time address from it. To the rest of the world, those payments look completely unrelated to you.

And the privacy layer is built with ML-KEM-768, a NIST-standardized post-quantum algorithm. So even if quantum computers arrive in 10 years, the payments you receive today stay private.

Try it right now

Hit the API, generate keys, create a stealth payment. Takes 2 minutes.

How does this work?

The full payment flow, step by step. No PhD required.

Launch the app

Use SPECTER in your browser.

---

Pick your starting point

Not everyone reads docs the same way. Here’s where to go based on what you care about.

New to this

Start with The Problem to understand why blockchain privacy matters, then read How SPECTER Works for the plain-language version.

If you’re curious about post-quantum stuff, PQ Crypto for Humans breaks it down without the jargon.

Builder

Jump to the Playground and hit some endpoints. Then read the API Quickstart and Integration Guide.

The full API reference lives in the API reference tab up top.

Evaluating / Investing

Read The Problem and SPECTER vs Others for positioning. Check Security Boundaries for honest limitations. The ERC Proposal shows the standardization path.

PQ crypto expert

Go straight to Post-Quantum Crypto for ML-KEM-768 implementation details, Security Boundaries for the receiving-vs-spending split, and the ERC Proposal for the formal specification.

---

The 30-second version

1. Bob generates ML-KEM keys and publishes a meta-address (like a public profile)
2. Alice uses that meta-address to derive a fresh one-time stealth address
3. Alice sends ETH/tokens to that address and posts a coded announcement
4. Bob scans announcements with his private key, finds the payment, and spends it

Nobody watching the chain can link the stealth address back to Bob.

---

What makes SPECTER different

	SPECTER	Classical stealth (Umbra/Fluidkey)
Discovery crypto	ML-KEM-768 (post-quantum)	ECDH (broken by quantum)
Harvest-now-decrypt-later safe	Yes	No
View tag scanning	~1-2s for 100k announcements	10-15s
Multi-chain	Ethereum + Sui	Ethereum only
Name service integration	ENS + SuiNS	ENS
NIST standard	FIPS 203	N/A

If you only read three pages, make them The Problem, Protocol Flow, and Security Boundaries.

---

Get in touch

GitHub

Source code, issues, and feature requests.

Email

[e-mail] for questions, partnerships, or support.

SPECTER on X

Follow @specter_PQ for protocol updates.

Built by Pranshu Rastogi (@pranshurastogii). Questions, ideas, or collab? Reach out anytime.