Compare

How privacy-focused networks compare.

Whether the network can be stopped, whether anyone can read your data, what a contract can keep private, and who can take part.

Who controls your privacy?

It depends on more than what is hidden.

Is the network unstoppable?

Check who produces blocks, who can admit or remove operators, and whether anyone can halt, reset, or censor the chain. A public base chain and its privacy service may have different answers.

Is there a privacy backdoor?

Check whether an operator, a validator group, a co-signer, or a key holder can read private data now or decrypt it later, and whether the application rules add a backdoor of their own.

Do they have private smart contracts?

Check whether builders can write contracts with private state and private logic alongside public logic, or are limited to a particular payment or token design.

Who can build and participate?

Deploying an application and operating infrastructure are different permissions. Check the requirements for each role.

Seven approaches, side by side.

CompanyUnstoppable networkPrivacy backdoorPrivate smart contractsParticipation
AztecNo one can stop itNo backdoorPrivate + public contractsPermissionless to use, build, and operate
NEARPermissioned privacy shardShard validators and a TEEIntents, not contractsPermissionless to use
StarknetPermissioned sequencingAudit key held by a companyPublic contracts, private poolPermissionless to use
MidenInvite-only, Miden-runValidators hold the keysPrivate accounts and notesPermissionless to use
ZcashNo one can stop itNo backdoorPayments onlyPermissionless to use and operate
ZamaOperators can pause itThreshold decryptionEncrypted types in SolidityPermissionless to use
TempoWhitelisted validatorsZone operator reads everythingPublic Solidity, private ledgersPermissioned to use

The detail, with sources.

What each network does well, its documentation, and the date it was last checked.

  1. Aztec vs NEAR

    A sharded proof-of-stake Layer 1

  2. Aztec vs Starknet

    A validity rollup on Ethereum

  3. Aztec vs Miden

    A client-side-proving rollup, spun out of Polygon

  4. Aztec vs Zcash

    A proof-of-work Layer 1 for private money

  5. Aztec vs Zama

    An FHE confidentiality layer for public EVM chains

  6. Aztec vs Tempo

    A payments-first Layer 1, incubated by Stripe and Paradigm

Privacy shouldn't depend on permission.