Can Starknet's STRK20 bring ZK privacy to ERC-20?
Published 6/10/2026, 6:40:31 PM
Answer
Yes, Starknet's STRK20 can bring ZK privacy to ERC-20 tokens — but the framework is still maturing, and several key claims lack independent verification.
What STRK20 Is
STRK20 is a privacy framework/standard (not a token) that enables any ERC-20 token on Starknet to have shielded balances and private transfers. It launched June 9, 2026, as part of Starknet's protocol-level privacy upgrade [Source: https://www.starknet.io/blog/].
Technical Architecture
| Component | Function |
|---|---|
| Privacy Pool | Single shared pool supporting all ERC-20 tokens; users deposit → transact privately → withdraw |
| ZK Proofs (Stwo prover) | Client-side proof generation, verified at sequencer level; up to 28x faster than other ZK VMs [Source: https://www.starknet.io/blog/] |
| Cairo VM | Unified codebase for client-side proof + on-chain contract logic |
| Viewing Keys | Encrypted keys allowing selective disclosure for legal/regulatory requests |
The privacy pool contract holds assets while concealing ownership, using ZK proofs to hide sender, receiver, and amount [Source: https://eprint.iacr.org/2026/474].
How Private Transfers Work
- User deposits ERC-20 tokens into the Starknet Privacy Pool
- Transact within the pool using ZK proofs (sender, receiver, amount hidden)
- Withdraw when ready
- No separate wrapped tokens required — privacy embedded in asset flow itself
Compliance Built-In
STRK20 includes a risk-based compliance model:
- Auditing entities can reconstruct a specific user's activity after valid legal request
- Other accounts in the pool remain hidden
- Threshold encryption available for quorum-based key decryption
Starknet explicitly distinguishes STRK20 from mixers: privacy operates as a native mode of activity rather than a specialist detour [Source: https://www.starknet.io/blog/].
Live Integrations (as of June 2026)
| Use Case | Platform |
|---|---|
| Anonymous swaps | Ekubo Protocol |
| Anonymous staking | Endur (via Ekubo) |
| Shielded Bitcoin | strkBTC (live May 12, 2026) |
| Private payments/donations | Supported |
Performance
- Current TPS: ~1,000 TPS with solid L2 finality
- Target TPS: 10,000+ TPS
- Client-side proving: Mobile-ready via Stwo prover
- Account compatibility: Works with existing Starknet accounts (multisig, hardware wallets, smart accounts)
Comparison to Ethereum's zERC20 (EIP-7503)
| Aspect | STRK20 (Starknet) | zERC20 (Ethereum) |
|---|---|---|
| Architecture | Privacy pool | Proof-of-burn |
| Anonymity set | Pool participants | All fresh addresses |
| Compliance | Viewing keys | Limited (plausible deniability) |
| Regulatory risk | Untested | Lower |
Open Questions (Claims c1–c3: UNRESOLVED)
| Gap | Details |
|---|---|
| No formal EIP/SIP number | STRK20 lacks a formal Ethereum Improvement Proposal or Starknet Improvement Proposal number |
| No independent TPS verification | The ~1,000 TPS figure is self-reported; no on-chain benchmarking confirmed |
| No on-chain private transfer volume data | No public data confirms actual private transfer volumes |
| No independent audit | The privacy pool contract has not been audited by a third-party firm |
| No quantitative privacy metrics | Anonymity set size and correlation resistance remain unquantified |
| No regulatory precedent | The compliance model's legal acceptance remains untested |
Bottom Line
STRK20 successfully brings ZK privacy to ERC-20 tokens by integrating privacy into normal asset flows rather than requiring separate services. The framework addresses the historical limitation that ZK-rollups provide scalability but not privacy, adding a proper privacy layer while maintaining compliance mechanisms for institutional adoption. The infrastructure is live but the ecosystem is still maturing.
Suggested Next Steps
- Technical Analysis — Request a deep-dive on STRK token price structure, support/resistance levels, and volume profile given the ~$0.034 price point and ~$214–223M market cap.
- Contract Security Check — Audit the privacy pool contract address on Starknet to verify the compliance model and withdrawal logic independently.