Starknet's Shadow Accounts Hide Your Wallet, Not Your Trades

Starknet, the Ethereum layer-2 network, has shipped a wallet privacy feature called Shadow Accounts. It lets a user interact with DeFi apps from addresses that are not publicly tied to their main wallet.

For anyone holding a position in a Starknet DeFi app, the change is narrow but real. The trade still happens in public. Your main wallet just stops being the thing it is attached to.

StarkWare said the feature creates separate, persistent addresses for individual applications. Starknet's builder documentation describes them as persistent pseudonymous identities, where each (user, dapp, nonce) tuple maps to a deterministic address with no public onchain link to the user's main wallet.

That is per app, not one private identity for everything. A user could run one shadow account for lending, another for providing liquidity and a third for trading, with nothing onchain tying them to each other or back to the main address.

Users fund the accounts from shielded balances held in the STRK20 privacy pool, which Starknet introduced in June. Movement inside the pool hides sender, receiver, token, amount and spent notes from public observers. Deposits and withdrawals, by contrast, move between public addresses.

One mechanic worth knowing: a shadow account has no keys. Only a contract called ShadowAccountAnonymizer can execute through it, and that contract is what cuts the connection back to the funding wallet.

What Stays Public: Everything Except the Link

Starknet's own documentation is blunt about the limits. As it puts it:

The shadow address, balances, calls, and positions are public. What stays private is the link back to the user's main wallet.

So an observer can still watch a shadow account's positions and read every call it makes. What they cannot do, from the chain alone, is prove which main wallet it belongs to. Starknet says the protection does not cover a user's entire financial history: deposits, withdrawals and external app activity can remain visible, and authorized auditing still applies.

The problem being targeted is address reuse. When one wallet handles everything, anyone watching can piece together a person's positions, habits and holdings.

Deposits, Timing and Round Amounts Can Give You Away

Privacy pools leak at the edges, and Starknet's own security documentation lists the ways a link can be rebuilt:

• Opening a new channel and depositing or withdrawing in the same transaction, or with tight timing, can link a recipient to public address activity. The docs suggest wallets separate those flows where possible.
• Distinctive amounts, or money that goes in and straight back out, weaken privacy. Starknet notes this is common to all pools.
• Reverted transactions can link activity if the same note ID is reused.
• External observers see the paymaster as the sender, and the paymaster may see a user's IP address.

The documentation also flags app interactions, channel setup and transaction timing as things that can reveal information. Starknet's guidance to developers is to be explicit about what remains public, including deposits, withdrawals, timing and some app-side activity.

A Viewing Key, Held by Somebody Else

Privacy here comes with an audit path, and it is mandatory rather than optional. Deposits are screened on every route, with the depositing address evaluated by Elliptic, and running a self-hosted prover does not bypass that screening.

Each user must create a viewer key to deposit into the pool and prove it was created correctly. Without that proof, a wallet cannot interact with the pool at all. Starknet says viewer keys support scoped disclosure, so a single counterparty transfer can be reencrypted for an authority without exposing anything else.

Viewer keys are encrypted to a master key held inside a dual-enclave TEE operated by Financial Privacy Inc. That key is backed by a 3 of 4 multisig with two signatories from StarkWare and two from FPI, plus a 7 of 12 multisig backup controlled by the Starknet Security Council. Changing the compliance model itself needs 7 of 12 signatures from that council.

Starknet's blog makes the argument for forcing the key on everyone: with opt-in viewing keys, if even one user declines, there is no compliance, and a regulator would treat that as no compliance at all.

What It Runs On, and What Is Not Known

Starknet lists the wallets and apps STRK20 works across, including Ready, Xverse, AVNU, Ekubo, Vesu, Circle, Troves, Endur.fi, ForgeYield and DashX. StarkWare said the functionality could eventually reach beyond vaults to liquidity provision, lending, borrowing, staking, derivatives trading, prediction markets and NFT marketplaces.

A demonstration integration with Vesu Prime's vSTRK vault went live on mainnet shortly after launch. Reports disagree on the date of the first production integration, with one outlet saying October 14, 2026 and two others saying October 15. That gap has not been reconciled.

What is genuinely unestablished is use. No usage, TVL, volume or fee figure attributable to Shadow Accounts has been published. The available evidence describes the mechanism and how activity routes through STRK-denominated balances and fees, not adoption or fee capture. A privacy switch shipping is not the same as people flipping it.

This is a product launch, and it sits apart from STRK's supply and unlock schedule, which is its own story.