Starknet Shadow Accounts Go Live for Unlinkable Per-App DeFi Identities
By Node Zero
October 22, 2026
StarkWare and the Starknet stack put Shadow Accounts live on mainnet as a STRK20 privacy primitive — persistent, per-dApp identities that can call DeFi contracts without publishing an on-chain link back to a user’s main wallet. StarkWare’s October 13 thread framed it as a Public → Private switch for apps; StarkWare CEO Eli Ben-Sasson called the design a fit for Privacy × DeFi. Official docs and STRK20 Wallet API notes treat the feature as shipped infrastructure, not a research vote. This is a Dev & Protocol Pulse chapter: unlinkable app identity, distinct from Bramble’s Chrome wallet shield UX and from the post-quantum L1 Snapshot research beat.
How it works, in desk terms: value leaves the STRK20 privacy pool into a deterministically deployed shadow address via the ShadowAccountAnonymizer (mainnet 0x04f3…88a7 per STRK20 contract docs). The shadow account can approve, swap, lend, stake, and hold positions across transactions — vault shares, LP tokens, open orders — while observers see only that address’s activity. Balances, calls, and protocol positions on the shadow account stay public; what disappears is the graph edge to the controlling main account. Each (user, dapp_name, nonce) tuple maps to a different address so one wallet can keep separate identities per app, or multiple identities for the same app.
Builder cut: Wallet API 0.10.4 with starknet.js 10.8.0 (and Privacy SDK 0.14.3-rc.8 for low-level paths) expose shadow_account_invoke / shadowAccounts(...). A shadow account has no keys and cannot sign; only the anonymizer drives it after a proven pool transaction. Secondary wraps cite early Vesu Prime vSTRK and Ekubo private-liquidity paths as first integrations — treat those as product demos unless explorers show sustained private-position volume. Selective disclosure / viewing-key paths in the wider STRK20 stack remain the compliance story; do not sell Shadow Accounts as absolute anonymity.
Keep the three Starknet privacy chapters separate: Bramble is a Foundation Chrome wallet that shields balances; Shadow Accounts are protocol-level per-dApp identities whose own balances stay public; the L1 Snapshot is governance research into an independent post-quantum chain — none of those three substitutes for the others.
Next protocol beat: Watch Wallet API adoption in live dapps, whether Vesu/Ekubo-style private positions show measurable mainnet volume, and whether Foundation or StarkWare publish audit notes for the anonymizer path — the desk cares about unlinkable call volume and verified privacy limits, not the “private mode” marketing label alone.
Bottom line: Starknet Shadow Accounts are live STRK20 infrastructure for unlinkable per-dApp DeFi identities — balances on the shadow stay public; the main-wallet link does not.
Disclaimer: This article is provided for informational and educational purposes only. It does not constitute financial, investment, legal, or trading advice. The cryptocurrency and NFT markets are highly volatile, and past performance is not indicative of future results. Readers should conduct their own research and consult qualified professionals before making any decisions related to digital assets. The cover image for this article may have been created using artificial intelligence (AI).
