Starknet shipped STRK20 on Tuesday, its note-based privacy layer for Ethereum-compatible ERC-20 tokens.
The feature does one main thing. It lets users “shield balances” and then move value via private transfers and swaps on Starknet’s layer-2 network. In other words, it aims to hide who is sending what to whom, even while the asset type stays ERC-20.
Starknet frames this as a phased rollout. The STRK20 release is the first phase of the framework Starknet has been building since its v0.14.2 protocol, according to The Defiant.
What STRK20 actually enables
From The Defiant’s description, STRK20 focuses on privacy for ERC-20 flows on Starknet. Users can:
- Shield ERC-20 balances on Starknet
- Execute private transfers
- Swap privately, still within the layer-2 environment
The “note-based” part matters. A note-based design typically means the system tracks value in encrypted, spendable units rather than exposing plain balances and transfer amounts. That tends to improve transaction-level privacy, because observers can’t trivially link inputs to outputs.
But privacy layers also shift complexity into the protocol. If you can’t see balances directly, correctness depends on the privacy system enforcing valid spends. That is where the “framework” language from The Defiant matters, because the rollout being only the first phase implies not all end-to-end behavior is live yet.
Phased rollout since v0.14.2
STRK20 is not a bolt-on feature Starknet invented overnight. The Defiant reports Starknet has been building the STRK20 framework since its v0.14.2 protocol.
That timeline hints at two practical points for users and developers.
First, STRK20 likely required plumbing changes before it could safely ship. Privacy layers usually need careful integration with token accounting and transfer logic so shielded balances behave like balances, just hidden.
Second, a “first phase” release usually means partial coverage. The Defiant’s wording does not list what is excluded yet, but the safest assumption is that not every edge case or feature will be identical to the fully transparent path.
Why “ERC-20 privacy on an L2” is a big deal
Starknet’s pitch is simple: bring privacy to a familiar asset format. ERC-20 is widely supported and easy to integrate with existing token ecosystems. Adding shielded balances and private transfers around that format lets privacy-aware applications work without demanding users abandon ERC-20 entirely.
The risk side stays the same as any shielded-asset system. If you shield tokens and the privacy mechanism fails to preserve spendability or enforce correct transfers, the damage is on-chain and final. The Defiant’s report doesn’t mention audits, parameters, or operational limits, so readers should treat STRK20 as a new system component, not a mere UI upgrade.
What to watch next
Because The Defiant describes STRK20 as a framework with a first phase live now, the next questions are about completeness and usability.
Expect follow-up information around:
- Which ERC-20 assets are supported for shielding and private swaps
- How swaps behave compared with transparent swaps
- Whether the phase limits any transfer types or smart contract interactions
For teams building on Starknet, the practical work starts now. Privacy features usually require new integrations, new assumptions about visibility, and new testing for flows that used to be publicly verifiable.
| Item | What Starknet says is live now |
|---|---|
| Product | STRK20 note-based privacy layer |
| Scope | ERC-20 shielded balances |
| Actions enabled | Private transfers and swaps |
| Network | Starknet, Ethereum layer-2 |
| Launch status | First phase of the STRK20 framework |
| Build timeline | Framework built since Starknet v0.14.2 protocol |
The newsroom takeaway is straightforward. Starknet just added a privacy layer for ERC-20 on its L2. That raises the privacy ceiling for users. It also raises the engineering and operational bar for everyone else in the stack.