Kusama Shield Comparison to Tracked Protocols

Comparison of Kusama Shield against other privacy protocols in the ecosystem.

PropertyKusama ShieldPrivacy PoolsRailgunHinkalCurvyFluidkey
ConfidentialityYesNoYesYesPartialNo
AnonymityYesLinkabilityYesYesPartialLinkability
Asset PrivacyYesNoPartialPartialPartialNo
Plausible DeniabilityNoNoNoNoNoYes
Censorship ResistanceYes(strong)Yes (ragequit)YesNoNoYes
Compliance GatesNoneASP (withdraw)POI (app)ChainalysisPredicateNone
Client-side ProvingYesYesYesOptional/TEENoN/A
Partial WithdrawalsYesYesYesYesYesN/A
Implementation Maturity2: Testnet + Mainnet <1 year4: Mainnet 1+ yr5: Mainnet 2+ yr3: Mainnet <1 yr3: Mainnet <1 yr4: Mainnet 1+ yr

Key Differentiators

Kusama Shield Advantages

  • No compliance gates — fully permissionless withdrawals
  • Strong censorship resistance — no centralized control points
  • Full asset privacy — all shielded assets maintain confidentiality
  • True anonymity set — unlinkable deposits/withdrawals

Implementation Notes

  • Uses Groth16 ZK proofs (snarkjs)
  • Merkle root is public input (must match on-chain tree) — unlike v4 where root is private
  • Supports native tokens and pallet assets (ERC20-like)
  • 128-depth LeanIMT tree (256 leaves max before upgrade)

Performance Benchmarks (PolkVM)

Powered by 30x customized Poseidon on PolkVM (Rust → PVM):

OperationPaseo GasEthereum GasImprovement
Single Poseidon hash2,70632,80012x cheaper
Depth-20 Merkle path37,956605,00016x cheaper
Groth16 verification3,990202,21651x cheaper
Shielded pool deposit~45K ($0.19)~$54270x cheaper
Shielded pool withdrawal~7K ($0.03)~$15~500x cheaper

Max Poseidon hashes per block: 39 (Solidity: 1, exceeds limit) Architecture: Solidity logic + Rust Poseidon + Groth16 verification

Reference

Protocol data and maturity ratings sourced from https://private-transfers.pse.dev/.