Key facts
- StarkWare's STRK20 framework on Starknet allows users to shield balances and transaction data.
- STRK20 provides mechanisms for disclosure under specific circumstances.
StarkWare and Sui have launched new privacy features enabling users to shield transaction data while maintaining auditability. These developments signal a shift in crypto privacy towards models that incorporate regulatory oversight, contrasting with purely anonymous systems.

These developments indicate a significant trend in the cryptocurrency space towards balancing user privacy with regulatory compliance, potentially paving the way for greater institutional adoption and integration with traditional financial systems.
StarkWare and Sui have introduced new privacy features aimed at making cryptocurrency transactions more compliant with regulatory oversight. StarkWare announced STRK20, a privacy framework for ERC-20 tokens on its Starknet platform, which allows users to shield their balances and transaction data. Eli Ben-Sasson, StarkWare's co-founder and CEO, clarified that while the framework is "compliance-ready," it does not guarantee legal compliance or regulatory approval on its own. The system operates on a risk-based model where privacy is conditional, with entry screening and disclosure available upon lawful request.
Concurrently, Sui has launched a public beta for its confidential transfers feature. This system conceals the amounts of transactions but permits authorized parties to access the information for auditing and compliance purposes. These initiatives signify a broader industry movement away from absolute anonymity towards privacy models that incorporate auditability and disclosure mechanisms, aligning with institutional preferences.
This shift occurs as privacy-focused projects face increased scrutiny. Zama, a blockchain privacy project, announced an accelerated compliance roadmap after a court-ordered freeze of approximately $12.5 million in its confidential USDC wrapper was resolved. Separately, Zcash developers addressed a bug in its shielded pools that had raised concerns about the potential creation of counterfeit tokens. While no exploitation was confirmed, the nature of shielded transactions makes post-vulnerability reconstruction challenging.