New · Shielded Space

Private cash, built for the post-quantum era.

Mazze gets a third space alongside native and eSpace. It works like digital cash: nobody can see who paid whom or how much. Not today, and not in 50 years.

How it works Follow on GitHub
STARK · Plonky3 No trusted setup No elliptic curves No view keys 100% fees burned
// Why it matters

Most privacy systems rest on elliptic curves that a large enough quantum computer will break. Shielded Space relies only on hashes and keeps nothing on-chain that could be decrypted later.

// Six guarantees

Designed like cash. Secured like a chain.

  1. 01 / 06

    Post-quantum from day one

    • Hash-based STARK proofs (Plonky3): no elliptic curves, no trusted setup, no secret keys for anyone to keep.
    • Spending relies only on hash-based secrets, with no signatures inside the shielded space.
    • Proof systems can be swapped: if one ever looks weak, a hardfork replaces it and funds stay where they are.
  2. 02 / 06

    Everlasting privacy

    • The chain stores only statistically hiding commitments and nullifiers.
    • Even unlimited computing power, quantum or not, can't recover amounts or recipients.
    • Zero public-key ciphertext on-chain, so "harvest now, decrypt later" gets nothing.
  3. 03 / 06

    Its own chain, secured by the whole DAG

    • Shielded transactions form a dedicated linear chain inside the DAG: one shielded block every 5–10 seconds, protected by Mazze's full hashrate.
    • Every node verifies every proof before accepting a block. No shortcuts, no "already verified" flags.
    • Proofs travel alongside the block, SegWit-style. Permanent history keeps only ~440 bytes per transaction.
  4. 04 / 06

    Every transaction looks the same

    • Fixed shape, fixed size, fixed fee. Transactions in a shielded block share one timestamp, and interior transfers emit no logs.
    • Payment details go to the recipient off-chain: QR, file, or sealed with hybrid post-quantum encryption (ML-KEM + Classic McEliece + X25519) over any channel.
    • Wallets claim incoming payments automatically and keep themselves consolidated. Everything restores from the seed.
    • Dandelion++ hides which node a transaction came from.
  5. 05 / 06

    Cash rules

    • Deposits and withdrawals are public, like a bank. Everything inside is private.
    • No view keys, no backdoors, no disclosure features. Every coin is equal.
    • The total value in the pool is publicly auditable at any time.
    • 100% of shielded fees are burned. No tips, no miner share.
  6. 06 / 06

    Safety built in

    • Supply checks every epoch.
    • A circuit breaker on outflows and an emergency pause.
    • Upgradeable pool versions.
    • Formal proofs and independent audits are part of the launch plan.
// How it works

A shielded payment, step by step.

01

Deposit

Move MAZZE from native or eSpace into the shielded pool. Visible on-chain, like walking into a bank.

Public
02

Pay

Your wallet builds a STARK proof. The transaction has a fixed shape, size and fee, so it looks like every other one.

Private
03

Deliver

Payment details go to the recipient off-chain: QR, file, or sealed with hybrid post-quantum encryption (ML-KEM + Classic McEliece + X25519).

Off-chain
04

Claim

The recipient's wallet claims incoming payments automatically and keeps itself consolidated. Everything restores from the seed.

Private
05

Withdraw

Move funds back to a public space whenever you want. Visible on-chain, like leaving the bank.

Public
// What the chain sees

Same payment. Two very different records.

Left: a transfer in a public space. Right: the same transfer inside Shielded Space. Scroll and watch what's left.

Public spaceNative / eSpace
Sender
0x71C7…3A9f
Recipient
0x9a2B…e41C
Amount
125.40 MAZZE
Fee
Varies
Timestamp
Per transaction
Event logs
Transfer(from, to, value)
Origin node
Traceable
Shielded SpacePrivate
Sender
nullifier · unlinkable
Recipient
commitment · hidden
Amount
hidden
Fee
fixed, burned
Timestamp
one per shielded block
Event logs
none
Origin node
hidden by Dandelion++

The total value in the pool stays publicly auditable at any time.

~6 ms
Proof verification
~440 B
Permanent history per transaction
5–10 s
Per shielded block
100%
Of shielded fees burned
// Where we are

Already running as a real STARK.

The full spend circuit runs as a real zero-knowledge STARK, and the complete payment flow (pay, deliver, claim, restore) works end to end in our prototype.

  • Full spend circuit running as a zero-knowledge STARKDone
  • Pay, deliver, claim and restore working end to endDone
  • Code and specs on GitHub for public reviewSoon
  • Shielded Space on testnetNext
  • Formal proofs and independent auditsBefore launch
Follow on GitHub Get updates