Mentioned in This Article
1. Starknet Shadow Accounts: what was unveiled on October 13
Starknet and StarkWare unveiled Shadow Accounts on October 13, a feature that lets people use decentralized finance applications through separate addresses that are not publicly linked to their main wallet. The tool is part of STRK20, the privacy framework built for the Starknet network, and its aim is to make a user's DeFi activity much harder to trace back to a single identity.
Each Shadow Account is a persistent, pseudonymous address. It is funded from shielded STRK20 balances, which means the money enters the account from a privacy pool rather than directly from the user's visible wallet. A smart contract named ShadowAccountAnonymizer sits between the pool and the new address, and its job is to sever the on-chain connection to the primary wallet.
The announcement describes the problem in plain terms: every time a person reuses one wallet across DeFi, they leave a trail that anyone with a block explorer can follow. Shadow Accounts are meant to cut that trail.
2. Why does wallet address reuse matter in DeFi?
Public blockchains record every transaction permanently, and each entry is attached to an address rather than a name. That arrangement is often described as pseudonymous, but it is not anonymous. When one address is used to lend, trade, provide liquidity and receive payments, an observer can piece together what the owner holds, which protocols they favour and how they behave over time.
The consequences go beyond curiosity. Once an address is linked to a real person, whether through an exchange withdrawal, a public post or an ENS-style name, the entire history becomes readable. Observers can reconstruct positions, habits and holdings, and that information can enable unwanted tracking and targeted attacks. Large holders are particularly exposed, since their activity can be watched and copied or used to single them out.
Shadow Accounts address this specific weakness. Rather than asking users to avoid DeFi or to juggle many wallets manually, the framework builds the separation into the account design.
Consider how this plays out for an ordinary user. Someone who deposits into a lending market, swaps tokens on an exchange and later supplies liquidity to a pool will, with a single wallet, produce one continuous record covering all three activities. Anyone studying that record can estimate the person's net worth, judge their risk appetite and see when they are active. Splitting the activities across unconnected addresses breaks that single record into pieces that do not point to one another.
Businesses have a similar concern. A company that pays suppliers or manages treasury funds on a public chain may not want competitors to read its balances and payment patterns. Separate addresses for separate purposes are a common-sense precaution, and building them into the account framework makes the precaution easier to follow.
3. How do Shadow Accounts work?
A Shadow Account works by splitting the act of funding from the act of using. The user begins with a balance held in the STRK20 privacy system, where amounts and transfers are shielded. Value is then moved from the privacy pool into the shadow address, with the ShadowAccountAnonymizer contract acting as the intermediary that breaks the visible link between the two.
After that, the shadow address interacts with DeFi applications like any ordinary account. It can lend, trade or provide liquidity, and the protocols it touches see only the shadow address.
Accounts are created per application. A user could keep one identity for lending, another for liquidity provision and a third for trading, with no on-chain connection among them or to the main address. Separating activities in this way limits what any observer can learn, because compromising or tracking one identity does not expose the others.
The design also changes how a user thinks about risk. Under a single-wallet habit, one phishing attack or one malicious application approval can put everything in the wallet within reach. Keeping each application on its own address confines the exposure of a mistake to the funds assigned to that address, which is a security benefit in addition to the privacy benefit.
Because the shadow address is persistent, it can hold a position over time instead of being created for a single transaction. That matters for lending and liquidity provision, where a position may stay open for weeks or months and where a throwaway address would be impractical.
4. What do Shadow Accounts not hide?
The feature is deliberately narrow in what it conceals. Balances and transactions of a Shadow Account stay publicly visible, as they would for any address on the network. What is removed is the on-chain link between that address and the owner's main wallet.
That distinction is important for anyone assessing the privacy it provides. A third party can still see what a given shadow address is doing, but cannot readily tell who stands behind it or connect it to the same person's other activity. The design therefore targets unlinkability rather than complete secrecy, which is a different goal from tools that attempt to hide amounts or counterparties altogether.
It is worth being precise about the trade-off. Fully hiding amounts and counterparties offers stronger secrecy but is harder to square with oversight and with the transparency that many DeFi protocols rely on to calculate risk. By leaving shadow-address activity visible, the design keeps those protocols working normally and concentrates its privacy gain on the link to the owner.
5. How does the design handle compliance and audits?
Privacy tools on public blockchains face constant scrutiny from regulators, who worry about illicit finance, so STRK20 includes a selective disclosure feature. With it, users can share their financial details with a specific party when required, such as an auditor or an authority, without publishing those details for everyone to see.
The approach reflects a broader effort in the sector to show that confidentiality and oversight need not be opposites. Rather than an all-or-nothing system, the framework allows a holder to prove what is needed to the party entitled to ask while keeping the rest of the information away from the public.
For institutions and cautious individuals, this option may be as important as the privacy itself. A shielded balance that cannot be explained to an auditor is of limited use to a business, whereas one that can be disclosed on demand is easier to fit into existing reporting duties.
The same logic applies to ordinary users who are asked to show proof of funds or the origin of their money. Selective disclosure gives them a way to produce that evidence for the relevant party while leaving their other activity unpublished.
6. How can developers add Shadow Accounts to their apps?
Developers connect to the feature through the Starknet Wallet API, with version 0.10.4 referenced for the launch. The wallet side handles the mechanics, and applications supply the actions they want the shadow address to take.
A demonstration integration with the Vesu Prime vSTRK vault went live on Starknet's mainnet at launch, showing a lending position held through a shadow address. Vesu is a lending protocol on the network, and the vault example illustrates how an ordinary DeFi product can be used while the depositor's main wallet stays out of view.
The demonstration is an example of what is possible rather than a full product rollout. How many applications adopt the feature, and how quickly, will determine whether it becomes a routine part of using Starknet or remains a tool for a small group of privacy-minded users.
For wallet makers, the arrangement places the burden of handling signing, viewing keys and proof generation on the wallet rather than on every individual application. That division of labour is intended to keep the work required from application teams small, since they provide the actions while the wallet manages the cryptography.
7. How does this build on STRK20?
STRK20 is the privacy layer for assets on Starknet. It lets people hold shielded balances and make shielded transfers, so that the amounts moved do not have to be broadcast to the entire network. Shadow Accounts extend that foundation from private transfers to private use.
In earlier steps, privacy meant moving value without revealing details. The new feature allows shielded balances to fund addresses that can then interact with DeFi protocols. That closes a gap: a person could previously hide a transfer but would still expose themselves as soon as they used the funds in an application from their usual wallet.
The result is a sequence in which a user shields funds, moves them into a per-application address and then acts in DeFi without tying the activity back to their main identity.
Taken together, the pieces describe a privacy stack with several layers: shielded balances at the base, a pool that holds them, an intermediary contract that separates funding from use, and per-application addresses on top. Each layer handles one part of the problem, and the whole is designed to be used without requiring the person to understand the cryptography underneath.
8. What to watch after the launch
The immediate question is adoption. Privacy features are only as useful as the number of applications that support them, and the early test will be whether more DeFi protocols on Starknet integrate the Wallet API route and offer shadow-address access to their users.
A second question concerns scrutiny. Tools that sever links between wallets tend to draw attention from regulators and analytics firms, and the selective disclosure feature will be tested by how institutions and authorities respond to it in practice.
A third is how much privacy users actually gain. Because Shadow Account balances and transactions remain public, patterns in timing or amounts could still help observers guess who is behind an address. The strength of the unlinkability will become clearer as researchers and users examine the system in real conditions.
There is also the question of how the feature will be used in practice. If people adopt a separate shadow address for each protocol, the number of addresses they manage will grow, and the wallet's ability to present them clearly will shape how convenient the system feels. Convenience often decides whether a privacy feature sees everyday use or remains a specialist option, and that will be visible in the months following the launch.