Key Notes
- Shadow Accounts let users interact through persistent app-specific addresses without publicly linking activity to their main wallets.
- Balances, transactions and DeFi positions held by a shadow account remain visible onchain, with STRK20 protecting the funding connection.
- Starknet expects the first application integration on October 14, while its broader list of use cases remains planned.
Starknet has introduced Shadow Accounts, allowing users to interact with public DeFi applications through separate addresses without publicly exposing the link to their main wallets. The feature protects that connection while leaving each shadow account’s balances, transactions and application positions visible onchain.
StarkWare announced the capability on October 13, describing it as a new part of the STRK20 privacy framework. Starknet’s own announcement says the first application integration is planned for October 14, with more to follow. It does not identify which app will be first.
Starknet introduces Shadow Accounts, with the first integration planned for October 14.
The accounts are funded from users’ shielded STRK20 balances and remain under their control. StarkWare describes a persistent pseudonymous identity for each app, letting users keep positions open and return to them over time without presenting their primary wallet as their public identity.
The wallet link is private; the DeFi position is public
The scope of the protection is central to the launch. In a follow-up, Starknet explicitly says that a shadow account’s balance, transaction history and positions remain public. STRK20 protects the relationship between that address and the main wallet funding it.
For example, an observer can still inspect a lending position or trading activity held by a shadow account. What the design aims to remove is the public connection that would place that activity alongside the user’s primary wallet history and other holdings.
Persistence also matters. These are not described as addresses discarded after every transaction. An app can maintain a continuing relationship with a pseudonymous account, which is useful for positions that need to be managed or closed later. Activity within that public account remains observable over time.
The feature therefore serves a different purpose from making an entire DeFi application confidential. Its public contracts and account-level activity remain available for inspection, while the user can separate that activity from the main-wallet identity.
A wallet-driven route into existing applications
StarkWare’s launch thread outlines a vault example: connect a wallet, select the app’s private mode, deposit into a vault, manage the position through the shadow account, and withdraw back to the shielded balance. Availability depends on an application integrating the feature and a compatible privacy-enabled wallet.
Developers can add the capability through the Starknet Wallet API using shadow_account_invoke. StarkWare says the wallet handles private state, proof generation and transaction submission, while the application can maintain positions without receiving the user’s viewing keys.
The company’s integration explanation identifies support in Wallet API v0.10.4, starknet.js v10.8.0 or later, and compatible wallets. Those requirements distinguish a feature available for developers to integrate from an automatic privacy upgrade across every existing Starknet interface.
The underlying privacy stack predates this release. Starknet’s June STRK20 launch introduced wallet-enabled shielding, private transfers and private swaps. The framework represents shielded assets as encrypted notes, with zero-knowledge proofs validating private actions without exposing all of their details to public observers.
In July, Starknet opened its SDK and wallet interfaces to builders, while describing private sub-accounts as a forthcoming component. The October announcement adds persistent app identities to that progression. Shielded balances inside the pool and public positions held by a shadow account remain distinct parts of the flow.
First integration expected October 14
Starknet names several planned uses: providing liquidity on Ekubo, taking positions on SuperVega, bringing USDC from EVM networks into a private balance through Chance, and adding collateral or borrowing on Opus. These are examples of intended integrations, rather than confirmation that every listed product is already enabled.
StarkWare also points to staking, recurring purchases, limit orders, options, perpetual futures, prediction markets and NFT marketplaces as potential applications. The common requirement is a continuing account that can interact with public contracts while keeping its main-wallet connection confidential.
CoinScreamer’s earlier strkBTC coverage examined Starknet’s effort to bring asset shielding into Bitcoin-based DeFi. Shadow Accounts extend the discussion to application identity: users can maintain public positions without making their primary wallet the address those apps publicly recognize.
The immediate next milestone is the first integration expected on October 14. Until application support arrives, the launch establishes the account capability and developer path; it does not turn all DeFi positions private or establish universal availability across the ecosystem.
Disclaimer: CoinScreamer is an independent media brand owned and operated by NuvexMedia LLC, publishing news, research, and market insights on digital assets and related technologies. NuvexMedia LLC invests in and collaborates with companies across the digital asset, blockchain, and technology sectors. These relationships do not influence CoinScreamer’s editorial coverage, and the publication maintains full editorial independence to provide accurate, timely, and objective information. © 2025 NuvexMedia LLC. All rights reserved. This content is for informational purposes only and should not be considered legal, tax, investment, financial, or other professional advice.
