Starknet launches Shadow Accounts to keep DeFi wallets unlinkable

Starknet launches Shadow Accounts to keep DeFi wallets unlinkable

The new STRK20 privacy feature gives users separate per-app addresses that can't be traced back to their main wallet on-chain

Every time you use the same wallet across DeFi, you leave a trail. On a public blockchain, that trail is open to anyone with a block explorer and some spare time.

Starknet and StarkWare want to make that trail much harder to follow. On October 13, 2026, the pair unveiled Shadow Accounts, a privacy feature that lets users interact with DeFi apps through separate addresses that aren’t linked on-chain to their main wallet.

How Shadow Accounts work

Shadow Accounts live inside STRK20, Starknet’s privacy framework. Each one is a persistent pseudonymous address.

Funding comes from shielded STRK20 balances. Value flows out of a privacy pool and into the shadow address, with a contract called ShadowAccountAnonymizer sitting in the middle to cut the connection back to the primary wallet.

Advertisement

What the feature does not do is hide everything. A shadow account’s balances and transactions stay visible on-chain, just like any other address. The thing that disappears is the link between that account and its owner’s main wallet.

The accounts are built to be per-dapp. A user could keep one identity for lending, another for providing liquidity, and a third for trading, with no on-chain thread tying them to each other or to the main address.

STRK20 also includes a selective disclosure feature aimed at compliance and audit needs. In practice, that means a user can open the books to a specific party when required, without publishing their entire financial life to everyone else.

Developer access and the first integrations

For builders, the integration runs through two tools: the Starknet Wallet API version 0.10.4 and starknet.js version 10.8.0. According to the research findings, apps can plug in the feature without being reworked.

A demonstration integration with Vesu Prime’s vSTRK vault went live on mainnet right after the launch. The first production integration was scheduled for October 14, 2026, a single day after the unveiling.

Building on the STRK20 privacy layer

Shadow Accounts are a second step rather than a first. The STRK20 privacy layer arrived in mid-2026 and introduced shielded transfers, letting users move value without broadcasting the details to the whole network.

Shadow Accounts take that idea a step further, from moving money privately to actually using it privately. Shielded balances become the funding source for addresses that can go out and interact with DeFi protocols.

The specific problem in Starknet’s sights is wallet address reuse. When one wallet handles everything, anyone watching can piece together a user’s positions, habits and holdings, exposing users to unwanted tracking and targeted attacks.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.
Starknet launches Shadow Accounts to keep DeFi wallets unlinkable
Starknet launches Shadow Accounts to keep DeFi wallets unlinkable

The new STRK20 privacy feature gives users separate per-app addresses that can't be traced back to their main wallet on-chain

Every time you use the same wallet across DeFi, you leave a trail. On a public blockchain, that trail is open to anyone with a block explorer and some spare time.

Starknet and StarkWare want to make that trail much harder to follow. On October 13, 2026, the pair unveiled Shadow Accounts, a privacy feature that lets users interact with DeFi apps through separate addresses that aren’t linked on-chain to their main wallet.

How Shadow Accounts work

Shadow Accounts live inside STRK20, Starknet’s privacy framework. Each one is a persistent pseudonymous address.

Funding comes from shielded STRK20 balances. Value flows out of a privacy pool and into the shadow address, with a contract called ShadowAccountAnonymizer sitting in the middle to cut the connection back to the primary wallet.

Advertisement

What the feature does not do is hide everything. A shadow account’s balances and transactions stay visible on-chain, just like any other address. The thing that disappears is the link between that account and its owner’s main wallet.

The accounts are built to be per-dapp. A user could keep one identity for lending, another for providing liquidity, and a third for trading, with no on-chain thread tying them to each other or to the main address.

STRK20 also includes a selective disclosure feature aimed at compliance and audit needs. In practice, that means a user can open the books to a specific party when required, without publishing their entire financial life to everyone else.

Developer access and the first integrations

For builders, the integration runs through two tools: the Starknet Wallet API version 0.10.4 and starknet.js version 10.8.0. According to the research findings, apps can plug in the feature without being reworked.

A demonstration integration with Vesu Prime’s vSTRK vault went live on mainnet right after the launch. The first production integration was scheduled for October 14, 2026, a single day after the unveiling.

Building on the STRK20 privacy layer

Shadow Accounts are a second step rather than a first. The STRK20 privacy layer arrived in mid-2026 and introduced shielded transfers, letting users move value without broadcasting the details to the whole network.

Shadow Accounts take that idea a step further, from moving money privately to actually using it privately. Shielded balances become the funding source for addresses that can go out and interact with DeFi protocols.

The specific problem in Starknet’s sights is wallet address reuse. When one wallet handles everything, anyone watching can piece together a user’s positions, habits and holdings, exposing users to unwanted tracking and targeted attacks.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.