Starknet launches Shadow Accounts, with first production integration going live on Oct. 14

Starknet launches Shadow Accounts, with first production integration going live on Oct. 14

N
News Editor
2026-10-14 08:30:58
Starknet and core developer StarkWare said on Oct. 14, 2026 that they have launched Shadow Accounts, a wallet privacy feature built into the STRK20 privacy framework introduced in June. The feature lets users interact with decentralized finance applications through isolated addresses that do not show any visible on-chain link to a user’s main wallet. At the same time, Starknet released Starknet Wallet API 0.10.4 and starknet.js 10.8.0 for developers, and said the first production deployment would go live the same day. The design assigns a separate persistent address to each dApp interaction, using shielded balances in the main wallet to derive per-dapp addresses. Starknet said this keeps DeFi transactions, call data, and state changes publicly verifiable on-chain while hiding the relationship between a user’s main wallet and specific protocols. The project also said dApps do not need to rewrite smart contracts or rebuild liquidation logic to support the feature. According to the report, lending protocol Vesu Prime has already completed a demo integration for its vSTRK vault. Shadow Accounts also inherit STRK20’s selective disclosure model, allowing users to provide proof of ownership for a transaction to compliance bodies or auditors through an encrypted viewing key. StarkWare said the feature is expected to expand from single-asset vaults to lending, staking networks, on-chain perpetuals, prediction markets, and NFT trading platforms.

Starknet and its core development company StarkWare said on Oct. 14, 2026 that they have officially launched Shadow Accounts, a wallet privacy feature for the Ethereum layer-2 network.

The feature is built into the STRK20 privacy framework that went live in June 2026. It allows users to interact with decentralized finance, or DeFi, applications through dedicated isolated addresses, with no visible on-chain link between those interaction addresses and a user’s main wallet. The team also released Starknet Wallet API 0.10.4 and starknet.js 10.8.0 for developers. The first production integration was scheduled to go live on Oct. 14, 2026.

Per-dapp addresses separate application activity from the main wallet

In the current public blockchain account model, address reuse has long been treated as a major privacy weakness. The report said that when institutions or large holders use the same main wallet for liquidity market making, collateralized lending, and derivatives settlement, on-chain analytics tools can reconstruct a user’s net asset distribution and real-time position exposure.

Shadow Accounts split on-chain activity into what Starknet describes as per-dapp addresses. When a user interacts with different decentralized applications, the system automatically derives separate persistent sub-addresses from shielded balances held in the main wallet.

The article gave a simple example: one isolated address can be assigned for lending, while another can be assigned for liquidity provision. Those addresses do not connect to each other on-chain and cannot be traced back to the original funding wallet. At the same time, transaction execution, call data, and state changes inside DeFi applications remain publicly visible and verifiable on-chain, while the relationship between the main wallet and specific protocols is hidden.

Wallet-side integration instead of contract rewrites

According to TechFlowPost, Starknet’s design takes a different route from mixers that break up funds or fully anonymous chains that cut off state verification entirely. The architecture is presented as balancing application compatibility with compliance boundaries.

On the developer side, decentralized applications do not need to rewrite existing smart contracts or rebuild liquidation logic. Support can be added through wallet interface upgrades in a plug-in style. Ahead of the mainnet release, lending protocol Vesu Prime completed a demo integration for its vSTRK vault, validating that deposit and withdrawal flows can take effect immediately.

On the compliance and audit side, Shadow Accounts inherit the selective disclosure mechanism under the STRK20 framework. Users can use an encrypted viewing key to provide a one-way proof of ownership for a specific transaction to compliance institutions or designated auditors. The report said this is meant to avoid the delisting and anti-money-laundering sanction risks that fully black-box anonymous assets can face on centralized trading platforms and across multiple jurisdictions.

Privacy moves beyond transfers into smart contract activity

The launch of Shadow Accounts marks another privacy building block for Starknet after the release of the STRK20 shielded token standard and private KYC in June 2026.

Over the past four months, STRK20 had mainly operated as the base protocol for private transfers. With Shadow Accounts, that privacy model now extends into high-frequency smart contract interactions.

Next rollout targets

Under the roadmap published by StarkWare, the feature is set to expand from the current single-asset vault model to decentralized lending, staking networks, on-chain perpetual contracts, prediction markets, and NFT trading platforms.

After the first decentralized application completes production integration on Oct. 14, the team plans to push protocol-level native integration updates to more mainstream self-custodial wallet clients during the fourth quarter of 2026.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
7000

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.