The first quantum-proof privacy chain with full compliance. That's the aim.

Europe didn’t ban private money.

Read MiCA closely and you find something narrower: trading platforms can’t admit crypto-assets with an inbuilt anonymisation function unless the holders and their transaction history can be identified. The EU’s anti-money-laundering regulation (AMLR) follows in July 2027 and restricts how supervised intermediaries handle anonymity-enhancing assets.

So privacy coins aren’t being delisted across European exchanges because privacy is illegal. They’re being delisted because they hand exchanges an impossible job. A service provider that can never establish anything about the assets it touches can’t meet its own obligations, so it walks away. The privacy was built as an absolute, and absolutes don’t negotiate.

Most projects respond by giving up the privacy: transparent ledgers, optional shielding nobody uses, or wrapped versions that quietly drop the point. We think that’s the wrong trade, and we’re building NYKS to prove there’s another one.

What NYKS is

NYKS is a self-developed Layer-1. Transactions are shielded by default: amounts, balances and counterparties stay private on-chain. Validity is enforced by zk-STARKs, transparent zero-knowledge proofs that need no trusted setup. Consensus is Nakamoto proof-of-work. Smart contracts run at the base layer.

One property runs through the whole stack: the cryptography is hash-based. No elliptic curves waiting for a large quantum computer to arrive. That’s what we mean by quantum-proof, and it isn’t a bolt-on. It’s the reason the chain can promise that what’s private today stays private in twenty years.

The second property matters just as much: privacy on NYKS is holder-controlled, not absolute. Every holder has viewing keys, per address or per wallet. You can grant a chosen party scoped access to your own transaction data, and only yours, and only as much as you choose. Nobody else can. That capability is live today, and it stands on its own. The compliance framework below is a separate design that asks for even less: nobody gets standing access to your data, a policy just gets an answer.

The attestation framework

Here’s the part built for MiCA’s identifiability condition. NYKS is designed to support a compliance-attestation framework with four pieces:

• A public attestor registry. Attestation providers, organisations or individuals admitted on an open, merit-based basis, publish their public key, the screening policies they support, their jurisdiction, their audit status, and their revocation status. Attestors are accountable: registered, jurisdiction-bound, audited, removable.
• Service-provider policy. Each exchange or custodian publishes which attestors and which policies it accepts. Providers make this choice independently; nobody is forced to trust any particular attestor.
• Holder attestation. To transact with a service provider, you pick an accepted attestor and either reveal the relevant transaction context to it, or answer a challenge program, for example proving that none of your coins descend from a flagged address. The attestor checks your history against the published policy and issues a signed certificate bound to that policy’s identifier. A new attestation can reference an earlier one instead of repeating the work.
• Verification. The service provider checks two things: the attestor’s signature and the policy identifier. That’s all it ever receives. Your transaction data never reaches the exchange, and it never becomes public.

We call the result auditable privacy. The exchange gets a certificate from an accountable party instead of a copy of your financial life. You get to keep your history to yourself. The regulator gets a supervised chain of accountability with revocation built in. Compliance is established by proof, not by data handover.

To be direct about status: this framework is planned, not live. The attestor registry and compliance certificates are on the NYKS roadmap for 2027, ahead of AMLR’s application date, and the design is described in our MiCA-format crypto-asset white paper. Its effectiveness will depend on qualified attestors joining the registry and on service providers accepting them. We’d rather say that plainly than pretend it’s shipped.

Why “quantum-proof” belongs in a compliance article

Because disclosure only works if secrecy holds.

Every certificate, every scoped disclosure, every shielded transaction on any privacy chain rests on one assumption: the cryptography protecting everything else stays unbroken. Adversaries already run harvest-now-decrypt-later collection, recording encrypted traffic today to break it when the hardware exists. A privacy chain built on elliptic curves is making a promise it may only keep for a decade.

NYKS’s proofs and primitives are hash-based end to end. The same choice that protects a holder’s privacy for the long term also protects the integrity of the compliance certificates built on top of it. One design decision, both halves of the promise.

The aim

No chain today combines all three: shielded by default, post-quantum cryptography, and a compliance pathway that European service providers can actually use. Transparent chains give up the first. Existing privacy coins give up the third and are losing their listings for it. Everyone gives up the second.

That empty intersection is exactly where NYKS is aimed. We’ve written the MiCA crypto-asset white paper, the attestation framework is specified and scheduled, and the base chain’s cryptography is already the post-quantum kind. The aim, stated once more without hedging: NYKS intends to be the first quantum-proof privacy chain with full compliance.

Privacy that survives regulation. Regulation that doesn’t demand your history.