Starknet's Shadow Accounts hide the owner of a DeFi position while publishing the position

A shadow account's usefulness and its weakness are the same property. The address is persistent ^[1], and according to Starknet its balances, transactions and positions remain publicly visible onchain ^[3], so a single public pseudonym accrues each deposit and withdrawal, plus every change in position size, inside one app. Someone watching can see a position build and exit. The feature obscures only the link back to the funding wallet ^[6].

We think the gain is substantial for the problem Crypto Briefing says the feature targets. That problem is wallet address reuse: when one wallet handles everything, anyone watching can piece together a user's positions, habits and holdings, and that exposes users to unwanted tracking and targeted attacks ^[12]. Per-app addresses cut at exactly that. A user could keep one identity for lending, another for providing liquidity and a third for trading, with no onchain thread tying them together or to the main address ^[8], so a watcher who finds the lending address sees just that lending position.

The view fails if an analyst can pair a withdrawal from the shielded pool with a deposit into a shadow account by amount and timing; if a position is large or odd enough to identify its owner with no wallet link at all; or if so few apps integrate that the unlinking covers a sliver of what users do. The sources do not report how many users hold shielded STRK20 balances, and that count sets how hard the first pairing is. The framework behind those balances is only a few months old, introduced in June ^[9].

Developers reach the feature through two tools, Starknet Wallet API version 0.10.4 and starknet.js version 10.8.0 ^[14]. Crypto Briefing wrote, citing what it called "the research findings", that apps can plug in the feature without being reworked ^[15]. That is a single-source claim about integration cost, and the first production integration will test it.