Starknet Adds a Privacy Layer for DeFi Users
Starknet, an Ethereum Layer 2 network, has launched Shadow Accounts, a feature intended to make it harder to connect a user’s main wallet with their activity across decentralized finance (DeFi) applications.
The feature creates separate, persistent addresses for individual applications. Users can fund these accounts through shielded balances held in Starknet’s STRK20 privacy pool, allowing them to manage activities such as lending and trading under different onchain identities. The launch was announced by StarkWare on X, the company behind Starknet.
The goal is to obscure the direct connection between a primary wallet and the DeFi activity conducted through a Shadow Account. However, this is not complete transaction anonymity: the account’s balances, transactions and positions remain visible on the blockchain. Users should therefore distinguish between hiding the link to a funding wallet and concealing transaction data itself.
How Shadow Accounts Work
Shadow Accounts provide a separate account identity for an application rather than requiring users to conduct every activity directly through their main wallet. Once the feature is integrated into a supported DeFi application, a user can connect a wallet, switch from public mode to private mode and deposit assets into a vault.
The Shadow Account can then maintain its position independently of the main wallet’s publicly associated activity. When the user wants to exit, funds can be withdrawn back into a shielded balance. The separation is designed to reduce the ease with which observers can associate a user’s main address with particular DeFi positions.
Starknet’s wallet account documentation provides technical information about wallet-account functionality. The level of privacy available in practice depends on how the feature is implemented by an application and what information remains visible onchain.
What the Feature Does—and Does Not—Hide
Public blockchains make transaction information available for inspection. Although wallet addresses are not automatically tied to real-world names, analysts can sometimes connect addresses by examining transaction histories, funding flows and repeated activity.
Shadow Accounts aim to make one particular link—the relationship between a main wallet and activity in a DeFi application—less apparent. Using separate addresses for different applications may make it more difficult for outside observers to build a complete picture of a user’s activity from a single address.
However, the feature does not make every transaction or position confidential. Balances and transaction histories associated with Shadow Accounts remain publicly visible onchain. The distinction is important for users who need to understand the limits of blockchain privacy before moving funds or relying on the feature for sensitive activity.
Potential Uses Across DeFi
The initial workflow focuses on DeFi applications that support vaults, where users deposit assets and maintain positions over time. Keeping those positions separate from a primary wallet could provide an additional layer of address-level privacy for people who do not want all their financial activity linked to one public identity.
StarkWare has indicated that the functionality could eventually expand to other use cases, including liquidity provision, lending, borrowing, staking, derivatives trading, prediction markets and NFT marketplaces. These are potential areas of expansion, not confirmation that every category is already supported at launch.
The practical reach of Shadow Accounts will depend on integration by individual applications and the availability of compatible wallets and infrastructure. Broader adoption could give users more options for separating onchain identities, while the public nature of blockchain transactions would continue to place limits on what the feature can conceal.
Shadow Accounts Build on Starknet’s STRK20 Privacy Framework
The launch follows StarkWare’s broader work on blockchain privacy. In June, the company introduced STRK20, a framework designed to support private transfers and shielded token balances on Starknet. Shadow Accounts use shielded balances from this privacy infrastructure as part of their funding process.
The framework is relevant because address separation and shielded balances address different aspects of privacy. Separate accounts can help reduce visible connections between a user’s primary wallet and application activity, while shielded balances are intended to provide privacy for supported transfers or holdings. The precise protections depend on the mechanisms used and how they are integrated.
StarkWare has also demonstrated a private Know Your Customer (KYC) system intended to let users verify personal information without disclosing their full identity documents. Such approaches seek to limit unnecessary exposure of sensitive personal information while still allowing specific checks to be completed. Details of the implementation and the protections it provides should be assessed through the project’s own technical materials and announcements.
What Starknet’s Privacy Push Means
Shadow Accounts add another option for users who want to separate their DeFi activity from their main wallet identity without leaving Starknet’s ecosystem. The feature’s application-specific addresses and shielded funding are intended to make those connections less obvious, while allowing supported accounts to maintain positions and later withdraw funds.
The main limitation remains clear: Shadow Accounts do not make all onchain activity invisible. Transactions, balances and positions can still be inspected, so users should not treat the feature as a guarantee of complete anonymity.
As Starknet’s privacy tools develop, adoption will depend on application integrations, technical implementation and how effectively the feature meets users’ needs. For now, Shadow Accounts represent a step toward more flexible address-level privacy for DeFi activity on Starknet.
