How to Use SynX Privacy Features: The Shadow Tier and the Ephemeral View Key

Read this part carefully, because most chains lie about it and we will not. SynX is dual-tier: transparent by default, shadow on demand. An ordinary send is public on the block explorer — amount, sender, recipient — the same as Bitcoin. Privacy is something you invoke, not something you are silently told you already have.

That honesty is the point. A privacy claim you cannot verify on the explorer is not a privacy feature. It is a slogan.

See also: Quantum Resistant Wallet with Privacy: The Shadow Tier & the Ephemeral View Key.

The Two Tiers

The Shadow Tier

A shadow send is Kyber-768 encrypted — NIST FIPS 203 ML-KEM, the same lattice standard the federal government is migrating to — and routed through a rotating burner address: a fresh address for that transaction, never reused.

The mechanism that matters is where the masking happens. The explorer is not a polite service that holds your data and declines to show it. There is nothing in that database to leak, sell, or hand over.

• Private balances return as "Private"
• Private transaction lists return as "Private"
• The address renders masked

And note what this is not: not a mixer, not a tumbler, not CoinJoin. Rotating burner addresses are protocol-native. There is no external service to sanction and no pool to drain. Tornado Cash taught the whole industry what happens to privacy that lives outside the protocol.

Sending and Receiving

Ordinary send:

1. Open the wallet and navigate to Send
2. Enter the recipient address and amount
3. Confirm — the transaction settles publicly, sub-second

Private send:

1. Open the wallet and choose the private send option
2. Enter the recipient address and amount
3. The wallet derives a fresh burner address and encrypts under Kyber-768

No address reuse, either direction. That single discipline defeats more chain analysis than most "privacy coins" achieve with far heavier machinery.

The Ephemeral View Key

This is the piece nothing else in the market has, and it deserves the whole section.

Zcash view keys are permanent and transferable. Give one to an auditor, an exchange, or a court and you have granted lifetime surveillance — to them, and to whoever they pass it to afterward. One disclosure, forever. That is not disclosure; that is an identity grant with no expiry.

SynX issues an expiring capability instead:

• Scoped to a single transaction. Not an account. Not a history. One.
• Lives thirty minutes, then it is gone. Not revoked, not archived — there is no record left to subpoena.
• Two factors, or nothing. Disclosure requires the transaction hash and the view key. Neither alone reveals anything.
• Amount only. Even holding both, what surfaces is a number — never the graph. Not who paid whom, not balances, not history. The identity layer is never assembled in the first place.

Practically: you can prove one payment happened, to one party, for thirty minutes, and then the capability ceases to exist. That covers the honest auditor, the tax question, the supplier who needs a receipt — and it covers none of the surveillance the permanent-view-key model quietly enables.

Burns Are Public on Purpose

Burns are verifiable by anyone on the Pyre Altar page of the explorer. The chain proves a burn happened without knowing who made it. Public supply math, private participants. That is not a contradiction in the privacy model — it is the model working exactly as designed.

Frequently Asked Questions

Are all my SynX transactions private?

No. SynX is dual-tier. Ordinary sends are transparent on the block explorer — amount, sender, recipient. Privacy is invoked per transaction through the shadow tier. Any project telling you every transaction is automatically private is either confused or lying.

Does the explorer store my private transaction data?

It never receives it. The explorer returns "Private" for shadow balances and transaction lists.

How long does a view key last?

Thirty minutes, scoped to one transaction. After that it is gone — not revoked, not archived. And even inside that window, holding both the transaction hash and the view key reveals the amount only, never the transaction graph.

Is this a mixer?

No. Rotating burner addresses are protocol-native, not post-hoc mixing. There is no pool, no tumbler, no external service to sanction.

Does privacy slow down transactions?

No. Sub-second finality holds on both tiers, and there are zero gas fees on either — which also means zero fee metadata for chain-analysis firms to fingerprint you with.