Nulify roadmap.
We're entering testnet prep. Target: public testnet within ~7 days (estimated)
Where we are:
- Phase 0 (done): ZK core works end to end on a local chain. Forged proof, double spend, and bad-root are all rejected.
Now:
- Phase 1: deploy the shielded pool + verifier to a public testnet (Base Sepolia), bring a relayer online against it, ship a browser proving flow.
Before any mainnet, still ahead:
- a public multi party trusted setup ceremony
- an external audit
- trust minimized cross-chain attestation
Testnet means test funds only. No real value at risk, no token, no sale. It's where you get to break things safely, and I want you to.
Building in the open.
https://t.co/EWtCJqcIwJ
https://t.co/OYSmY3i7M4
Introducing Nulify.
A cross-chain privacy bridge. Deposit on one chain, withdraw on another, with nothing on-chain connecting the two. Zero-knowledge proofs sever the link between source and destination.
What's built so far:
- ZK withdrawal circuit (PLONK / BN254, Poseidon)
- Shielded pool + verifier contracts
- TypeScript SDK
- Relayer for gasless, unlinkable withdrawals
- Whitepaper, docs, live site
Status, honest: pre-testnet. The core works end to end on a local chain. Forged proof, double-spend, and bad-root are all rejected. Not deployed yet. No token.
Built in the open. Read it, break it, tell me where I'm wrong.
https://t.co/EWtCJqcIwJ
https://t.co/OYSmY3i7M4
Nulify the trace.
Withepaper V0.1 realease
It covers the whole design: the threat model, the ZK construction (commitments, nullifiers, the Merkle accumulator, the PLONK circuit), how cross-chain attestation is meant to work, and an honest privacy analysis, including what leaks and what doesn't.
I wrote a full section on where the project actually is: what works, what isn't built, and the trust assumptions that still need removing before mainnet (real ceremony, audit, trust-minimized attestation).
Read it:
https://t.co/t8RZ95d5ux