Starknet launches Shadow Accounts to keep DeFi wallets unlinkable
Starknet's Shadow Accounts enhance DeFi privacy, potentially reshaping user anonymity and security, while balancing compliance needs.
This article may contain affiliate links. Commercial relationships are disclosed in the affiliate policy.
What happened
Starknet and Starkware unveiled Shadow Accounts on October 13, 2026, a privacy feature that lets users interact with DeFi applications through separate addresses that are not linked on-chain to their main wallet. The feature lives inside STRK20, Starknet’s privacy framework, and each Shadow Account is a persistent pseudonymous address funded from shielded STRK20 balances through a contract called ShadowAccountAnonymizer.
Reported details
- Funding flows out of a privacy pool and into the shadow address, with ShadowAccountAnonymizer sitting in the middle to break the link back to the primary wallet.
- A shadow account’s balances and transactions stay visible on-chain, exactly like any other address. What disappears is the link between that account and its owner’s main wallet.
- The accounts are built to be per-application. A user could keep one identity for lending, another for providing liquidity, and a third for trading, with no on-chain thread tying them to each other or to the main address.
- Each account is persistent rather than one-time, so the separation survives across sessions rather than resetting on every interaction.
- STRK20 also includes a selective disclosure feature aimed at compliance and audit needs, allowing a user to open the books for a specific counterparty.
Why it matters
The honest framing here is that this is link unlinking, not anonymity. Crypto Briefing is explicit that the feature does not hide everything: balances, amounts, and contract calls remain public, which The Defiant repeats in its own summary line. Anyone reading the Starknet explorer can still see what a shadow address holds and what it does. What changes is whether an observer can connect those actions to a main wallet that the user controls.
That distinction matters for how a security team should treat it. Per-application identities can raise the cost of building a durable profile across lending, liquidity, and trading venues, since the three activity streams no longer converge on one address in a block explorer. But a shadow address that holds a position and then transacts with a protocol the user also interacts with from the main wallet reintroduces the link by a different route. Selective disclosure is the pressure valve here: it is the feature that lets a user prove something about a shadow account to an auditor or counterparty, which is also the feature that makes the privacy claim testable rather than absolute.
What to verify
Before treating this as a meaningful privacy improvement for a given protocol, check whether the dapps a user actually touches accept the shadow address as an entry point, and whether any of them publish an on-chain link back to the funding source. Also worth confirming is when the feature reaches mainnet versus a test environment, because a launch announcement and a deployed contract are different milestones.
Sources and check time
-
Crypto Briefing: https://cryptobriefing.com/starknet-shadow-accounts-private-defi/
-
The Defiant: https://thedefiant.io/news/blockchains/starkware-launches-shadow-accounts-on-starknet
-
Editorial check time: 2026-10-17T00:24:00.000Z
This information is educational and does not constitute financial, legal, or tax advice.