Ekubo Launches Shadow Accounts for Starknet Liquidity Providers
Ekubo adds persistent shadow addresses for liquidity providers
Ekubo has enabled STRK20 Shadow Accounts on Starknet, letting liquidity providers open and manage fee-earning positions without publicly linking that activity to their main wallet.
The feature was announced on Oct. 14. Instead of tying positions to a user's primary address, providers use a persistent, app-specific address. They still deposit assets into Ekubo's existing pools, so the update does not require a new private pool of liquidity.
The privacy protection applies to the wallet link, not to the position itself. Token balances, contract calls and protocol positions remain visible onchain. Anyone can still follow the pseudonymous address and see which pools it interacts with.
What the interface looks like
Ekubo's Starknet mainnet create-position page now shows a Public/Private selector alongside the token-pair, fee and price-range controls. The default page displays ETH and USDC.
Using Shadow Accounts requires a wallet that supports the shadow-specific STRK20 methods, according to the developer guide.
How the technology works
The update follows StarkWare's launch of Shadow Accounts on Oct. 13. The key difference from earlier workarounds is permanence.
Previously, helper contracts completed an operation and returned proceeds within a single transaction. A shadow account can retain balances and positions across multiple transactions, according to the starknet.js guide.
Under the documented design, funds move from a shielded balance to the shadow address, which then makes ordinary calls to application contracts. Proceeds can return to the privacy pool. The shadow account has no signing keys; only the ShadowAccountAnonymizer contract can execute calls through it.
Privacy has clear limits
Amounts and transaction timing remain observable. The developer example linked from STRK20's launch guide warns that those observations, along with infrastructure-level information, can create correlations. A separate address is not a guarantee of anonymity.
Viewing keys are also possible. STRK20 stores a user's private viewing key encrypted to an auditor's public key onchain at registration. An auditor acting under lawful process can recover that key and decrypt the user's history. The viewing key provides read access only, not authority to move funds.
Audit scope leaves questions open
Audit coverage for the end-to-end Ekubo integration remains unconfirmed. The published OpenZeppelin report dated May 29 covers privacy-pool code at a specified commit. Its listed scope does not include the ShadowAccountAnonymizer contract or Ekubo's interface.
Why this matters for DeFi users
The update gives liquidity providers a way to separate their main wallet identity from their fee-earning activity on Ekubo. It is a step toward longer-term privacy in decentralized finance, but the approach does not fully obscure onchain behavior. Balances, pool interactions and transaction patterns remain visible, and lawful audits are still possible.
Sources
Newisty Editorial Team covers technology, cryptocurrency, digital products, online platforms, developer tools and the wider digital economy. Our content is researched from official sources, company announcements, public documentation, market data and other primary or reputable sources. Articles are reviewed and edited before publication for clarity, accuracy and useful context.
Related Posts
Aptos Token Surges 51% in Four Weeks, Outperforming Bitcoin and Ether
Anthropic Plans $518 Billion AI Spend as Crypto Traders Stay Calm
