Neptune Privacy

Quantum-safe layer 1 combining zkSTARKs and PoW. Providing a private, programmable ecosystem built for global scale.

[Neptune Privacy @NeptunePrivacy]

$XNT is live.

The network is running, the code is public.

Thank you to everyone who tested, supported, and helped shape this launch.

The release of a public GPU miner and pool are next.

Links:

Source code: https://t.co/bBPXYzvxbV

Releases: https://t.co/fRz1w66JSy

Website: https://t.co/uoQgTANbzz

Explorer: https://t.co/ayVXIQUUzV

[Neptune Privacy @NeptunePrivacy]

https://t.co/OQoSYlmzM7

[Neptune Privacy @NeptunePrivacy]

NEPTUNE PRIVACY: MANDATORY UPGRADE

XNT Core v0.3.0 is live, bringing a major set of feature upgrades alongside important security enhancements.

All node operators must upgrade before the consensus changes activate at block 97,000.

Updated Android and iOS apps have also just been published. Mobile users: please update your apps ASAP.

Special thanks to @t_allfather for discovering and reporting the security issue addressed in this release. His contribution has helped strengthen Neptune’s security.

This is the final core upgrade before the Leviathan update.

Details below👇

[Neptune Privacy @NeptunePrivacy]

Two major upgrades are coming as we prepare for Leviathan.

The first is on the way, bringing a range of new features.

Thank you for your patience with any temporary exchange interruptions during this process. More updates to follow.

[Neptune Privacy @NeptunePrivacy]

NEPTUNE AMA RECAP: PRIVATE VALUE, PROGRAMMABLE APPLICATIONS, AND CONFIDENTIAL AI

In our latest AMA with @ourcryptotalk, we explored what Neptune Privacy is building and where the ecosystem is heading next.

The discussion centered on three connected priorities: privacy by default, post-quantum security, and programmability. Check out the key takeaways below:

PRIVACY STARTS AT THE FOUNDATION

Neptune’s Layer 1 is secured by proof of work, with privacy built into the protocol for all transactions, including $XNT mining rewards.

Leviathan extends that foundation with programmability. Its account model defaults to private accounts, while allowing users to choose public accounts for applications and integrations that require transparency.

The goal is to make privacy the starting point while giving developers flexibility in what they build.

SECURITY DESIGNED FOR THE LONG TERM

Neptune uses hash-based zk-STARK proofs.

This architecture is central to its approach to post-quantum security: building around cryptographic foundations designed to withstand future quantum threats.

On Leviathan, Falcon-512 signatures extend that approach to wallet authentication.

EXPLORE THE LEVIATHAN PUBLIC TESTNET

The Leviathan public testnet gives users a practical way to explore the ecosystem through a familiar wallet and application experience.

Participants can:
• Set up the Chrome extension wallet.
• Claim test tokens through the faucet.
• Send and receive assets.
• Explore private swaps on NeptuneSwap.
• Provide and remove liquidity.
• Access Private AI using their Leviathan wallet.

You don’t need to be a developer to participate. Testing these workflows and sharing feedback helps improve the experience as development progresses. Testnet assets have no real-world value.

PRIVATE AI BEYOND THE PAYMENT LAYER

The AMA also explored how privacy extends to computation.

Private AI runs open-weight models inside a trusted execution environment, with prompts and responses encrypted between the user and the enclave. Access uses a Leviathan wallet, without requiring an email address or KYC.

The aim is to protect sensitive conversations, including discussions involving intellectual property, development plans, and new ideas.

Early testers are already exploring it as a tool for their own development work.

CONNECTING NEPTUNE AND LEVIATHAN

Another development discussed was the proof-based bridge between Layer 1 and Layer 2.

The bridge enables XNT to move into Leviathan as wrapped XNT and return to Layer 1, connecting Neptune’s private settlement layer with Leviathan’s programmable environment.

That connection allows users to move between private settlement and programmable applications within the same ecosystem.

WHAT BUILDERS CAN EXPLORE NEXT

The broader vision includes private lending and borrowing, additional exchanges, cross-chain connectivity, and other applications built on this infrastructure.

The discussion also touched on research into private key exchange: an approach to exchanging control of digital assets that could extend beyond assets native to Neptune.

These are areas for further development, with builders helping shape what comes next.

A central message from the AMA: privacy is about having control over your financial activity, your information, and how you participate online.

We’re building the infrastructure to make that control usable.

We encourage you to explore the testnet, read the docs, and connect with the Leviathan Pioneers community on Telegram.

[Neptune Privacy @NeptunePrivacy]

GOING LIVE IN 20 MINUTES

We’re joining @ourcryptotalk to talk about what we’ve been building at Neptune.

Tune in and catch up with the team.

https://t.co/55OcqdeLmt

[Neptune Privacy @NeptunePrivacy]

GOING LIVE IN 20 MINUTES

We’re joining @ourcryptotalk to talk about what we’ve been building at Neptune.

Tune in and catch up with the team.

https://t.co/55OcqdeLmt

[Neptune Privacy @NeptunePrivacy]

Leviathan Chrome wallet extension: https://t.co/e0CTAg8c9k

Hosted web wallet: https://t.co/8zBYVIsH46

[Neptune Privacy @NeptunePrivacy]

DID YOU KNOW?

You can already access the Leviathan public testnet through both our Chrome wallet and hosted web wallet.

There are two ways to start exploring Leviathan. Choose the Chrome extension or access the hosted wallet directly through your browser.

Both are live, marking two more completed milestones on our roadmap.

The roadmap is becoming reality, one milestone at a time.

[Neptune Privacy @NeptunePrivacy]

Appreciate the inclusion and recognition of our hash-based approach.

Neptune Privacy was a gentleman’s fork, and we remain in good contact with the original developers.

The project is community-run, with active contributors continuing to grow the ecosystem and improve the technology.

[Neptune Privacy @NeptunePrivacy]

X SPACE ANNOUNCEMENT: LEVIATHAN PROGRESS

Join us on October 16th at 11:30 AM ET for an AMA with @ourcryptotalk.

We’ll discuss Leviathan, public testnet progress, and the roadmap milestones completed so far.

Set your reminder below.

[Our Crypto Talk @ourcryptotalk]

Join us for Talk With Builders Episode 5 ft. @NeptunePrivacy

Live Space on privacy-first L1 and post-quantum tech.

Set your reminder 👇

https://t.co/uWjcLINkUR

[Neptune Privacy @NeptunePrivacy]

PRIVATE SMART CONTRACTS ARE LIVE ON LEVIATHAN PUBLIC TESTNET

We’ve been quiet, but development keeps moving forward.

Private smart contracts are live on the public testnet. This marks another completed milestone on our roadmap.

Developers can now build applications that enforce rules for how funds are used while keeping sensitive transaction details private.

Programmable rules.
Verifiable execution.
Private value.

Progress is measured in milestones, not dates.

[Neptune Privacy @NeptunePrivacy]

Plenty of big names on this list. Yet only three projects are live with hash-based security.

$XNT is one of them.

Neptune Privacy launched with hash-based STARK verification built into its core.

Vitalik’s emphasis on hash-based cryptography puts the spotlight on the foundation behind quantum resistance. For Neptune, that foundation has been in place since day one.

[Chain INK @0xchainink]

Vitalik just ranked the math. Hash-based beats lattice-based.

Here's what 13 quantum resistant tokens actually run on 👇

Hash-based, live

→ $QRL : XMSS since 2018
→ $XNT : STARK hash lock since genesis
→ $CKB : SPHINCS+, opt-in

Lattice-based, live

→ $ABEL : lattice ring signatures, mandatory
→ $CELL : Dilithium by default
→ $QTC : ML-DSA only, mainnet Sep 2026
→ $ALGO : Falcon-1024, opt-in
→ $NEAR : ML-DSA-65, opt-in

Not live yet

→ $STRK : ECDSA accounts, Falcon planned
→ $NAORIS : Dilithium L1, ERC-20 token
→ $QANX : Dilithium testnet, ERC-20 token
→ $ZEC : scheme unpicked, 2027 target
→ $QUBIC : SchnorrQ, no PQ plan

Only 3 of the 13 are live on the math he trusts.

[Neptune Privacy @NeptunePrivacy]

This is the split that matters. Where a system can be hash-based, it should be.

Neptune Privacy already settles that way. Validity is hash-based STARKs on Triton VM. No trusted setup. No ECDSA under the proof. Privacy comes from the Mutator Set, which makes transaction inputs and outputs unlinkable, rather than relying solely on encrypted data staying unreadable while it waits for a better attack.

Leviathan is our L2, bringing programmability to that foundation. The public testnet brings the stack together: private L1, programmable L2, a post-quantum DEX and Private AI inside attested TEEs.

Testnet assets have no real-world value. Find the limits. Help us strengthen the stack.

[vitalik.eth @VitalikButerin]

I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography.

The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices.

(and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation)

So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math.

The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be?

This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-.

For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption.

And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10.

To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety.

And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all.

Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems.

For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size).

Concrete TLDR, my own personal views:

* Hash-based > lattice-based, in those situations where hash-based is possible at all
* For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ...
* For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism.
* If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**.
* For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money"
https://t.co/oVjwZog2lL

[Neptune Privacy @NeptunePrivacy]

PRIVACY THAT CAN BE PROGRAMMED

Sending money privately is the foundation. Being able to build applications around it is the next step.

That’s why private smart contracts are a key part of the Leviathan roadmap.

Neptune provides the private Layer 1, with $XNT as its native asset. Leviathan adds private smart contracts: programs that enforce rules for how funds can be used, without requiring users to make all the underlying transaction details public.

Think of a payment released only when agreed conditions are met, or a swap that completes only when both sides fulfil their part.

The technical difference is how those rules are verified. Transactions can be executed and proved locally, with the network checking cryptographic proofs that the rules were followed. Sensitive inputs can stay private while the result remains verifiable.

This gives developers a foundation for private swaps, conditional payments, escrow and other financial applications.

Private smart contracts make privacy something developers can build with, and something users can do more with.

Private value. Programmable rules. Verifiable execution.

That’s the direction we’re headed with Leviathan on Neptune Privacy.

[Neptune Privacy @NeptunePrivacy]

Quantum DeFi just became the timeline. Leviathan’s Public Testnet is where you can actually touch it.

$XNT

[Neptune Privacy @NeptunePrivacy]

@qlyphsxyz @QuantusNetwork $XNT belongs in this conversation. Public testnet is live for @NeptunePrivacy’s Leviathan, bringing together a private Layer 1, a post-quantum DEX and private AI inside attested TEEs.

Check it out!

https://t.co/e0CTAg8c9k

[Neptune Privacy @NeptunePrivacy]

@qlyphsxyz @QuantusNetwork $XNT belongs in this conversation. Public testnet is live for @NeptunePrivacy’s Leviathan, bringing together a private Layer 1, a post-quantum DEX and private AI inside attested TEEs.

Check it out!

https://t.co/e0CTAg8c9k

[Neptune Privacy @NeptunePrivacy]

LEVIATHAN PUBLIC TESTNET IS LIVE!

Private value on Layer 1.
Private apps on Layer 2.
A proof-backed bridge between them.

A wallet, a post-quantum DEX, and Private AI inside attested TEEs. The stack is running and ready to test.

Testnet assets have no real-world value. That’s the point. Use it. Push it. Try to break it.

START HERE

Docs: https://t.co/mxHkUfNe3Q
Explorer: https://t.co/YlzWEgVze6
Post-quantum DEX: https://t.co/j9pVxbfY6S
Private AI: https://t.co/WiFPS6tJXo

The Chrome wallet ZIP is on the docs installation page. Download it, load it as an unpacked extension, and get started.

FOUND SOMETHING? HAVE A REQUEST?

Bugs and feature requests: https://t.co/OUb2Fmd483
Leviathan Pioneers on Telegram: https://t.co/MeW47KOu84

Fider turns bugs into tickets. Telegram is where you can get help, share feedback, and talk with other builders.

The next chapter of Leviathan starts with you.

[Neptune Privacy @NeptunePrivacy]

THE NEXT ERA OF NEPTUNE PRIVACY HAS ARRIVED.

Today, we are unveiling the roadmap for Leviathan: Neptune Privacy’s private execution layer and the foundation for what comes next.

$XNT’s privacy-first Layer 1 is already live. Core components of the Leviathan stack are built, others are nearing completion, and every milestone shown is planned for the network.

Next: public testnet, private smart contracts, NeptuneSwap, Confidential AI and cross-chain interoperability.

And on the horizon: a flagship private key exchange enabling private, permissionless peer-to-peer swaps.

This is more than a roadmap. It is the path toward private, programmable money built for a post-quantum future.

Leviathan is rising.

[Neptune Privacy @NeptunePrivacy]

Behind the scenes, the next chapter of Neptune Privacy is taking shape.

We’ve been refining our vision, reimagining the website, and preparing a roadmap that shares the full scope of what we’re building with $XNT.

To everyone who has continued to believe in Neptune’s potential: we think you’ll be pleased with where it’s headed.

The roadmap will speak for itself.

[Neptune Privacy @NeptunePrivacy]

From one of Neptune’s early Pioneers:

Neptune’s Miden-based execution layer opens the door to something much bigger than another privacy wallet: a private, programmable ecosystem where your wallet also becomes a secure access point for Confidential AI.

No separate API keys. No unnecessary identity trail. Prompts are encrypted and processed inside a Trusted Execution Environment (TEE), preventing the infrastructure between the user and the AI from seeing the data it handles.

This is where @NeptunePrivacy’s pieces come together: quantum-resistant architecture, wallet based authentication, private applications, and Confidential AI, all built around privacy at its core.

Check out this thoughtful excerpt and thread about what the Pioneers have been quietly testing and why Leviathan deserves far more attention ahead of the launch of its public testnet.

[Pretoria (♟️,♟️) @Pretoria01]

3. A Miden-based execution layer:

this is what turns Neptune from “just a private coin” into a place where developers can actually build things.

it gives builders a zero-knowledge virtual machine to create private smart contracts, exchanges and apps, without needing to be cryptography experts themselves.