Daily Crypto Briefs 
October 15, 2026
Starknet has introduced Shadow Accounts to separate users’ main wallets from their public DeFi positions, as STRK fell 9.92% in its latest completed UTC trading session amid volatile trading in the Ethereum scaling network’s token.
The feature, announced October 13, gives each application a persistent pseudonymous address funded from a shielded balance. It protects the connection to the primary wallet while leaving the resulting account’s activity visible, a distinction central to assessing what the launch actually changes.
ChartExchange’s composite history showed STRK closing October 14 at $0.0768, with a $0.0865 high, a $0.0720 low and reported volume of about 78.45 million STRK. These figures describe the market backdrop; they do not establish that the privacy release caused the decline.
The official STRK20 overview says the system supports separate identities for different applications while keeping positions public. Shielded transfers inside its pool have broader confidentiality than activity conducted through a shadow address outside it.
The launch follows Starknet’s separate discussion of a possible quantum-resistant independent network. Shadow Accounts operate within the existing Starknet environment and do not establish that the proposed architectural transition has been approved.
Starknet
STRKSource: ChartExchange. Sampled composite daily closes across one month; the unfinished October 15 session is excluded.
Shadow Accounts protect the wallet link
Public wallet addresses can connect a person’s holdings, trades and borrowing across applications. Reusing one address makes those relationships easy to follow even when a block explorer shows no real-world name.
Shadow Accounts change the address an application sees. A lending position can remain associated with the same pseudonymous caller over time, allowing the application to recognize a returning user without displaying that user’s main wallet as the position owner.
The Starknet.js account guide distinguishes this persistent identity from a shared helper contract used for a single operation. The latter can complete an exchange and return proceeds immediately; a shadow address can retain balances and positions between transactions.
The address is derived from the user, the application name and an additional identifier. Changing that identifier permits another identity within the same application. The shadow address has no independent signing keys; execution passes through the designated anonymizer contract.
This is narrower than making public DeFi invisible. Someone watching a shadow address can still see its balances, transactions and positions. The intended protection concerns attribution to the main wallet, rather than secrecy for every action taken through the address.
For example, an observer could follow a loan’s size and repayment history at the application address. The feature is designed to prevent that observation from automatically revealing the borrower’s main wallet and its unrelated holdings. That potential separation does not remove the public record of the loan or guarantee that distinctive behavior cannot identify its owner.
That distinction also separates the feature from a new privacy coin. STRK20 works with token balances on Starknet, using encrypted records inside a pool. It does not require a separate blockchain or turn every publicly held token into a confidential asset.
Mainnet vault demo carries an unaudited warning
The Shadow Accounts integration guide now links a demonstration comparing public and private deposits into the Vesu Prime STRK vault. In private mode, the shadow account owns the vault shares, and withdrawals return to a shielded balance.
The page describes a mainnet demonstration using real assets, while explicitly labeling it an educational example that has not been audited as production software. Its availability provides a concrete example of the flow, without establishing readiness across the wider lending market.
No network-wide adoption total, aggregate deposits or number of active Shadow Accounts was disclosed in the reviewed launch materials. A linked demonstration should not be counted as evidence that every advertised application category has integrated the feature.
The current Wallet API guidance specifies starknet.js 10.8.0 and Wallet API 0.10.4. A compatible connected wallet must also support the privacy methods; installing a software library alone does not enable the feature for every user.
Applications ask the wallet to perform an action, while the wallet handles private records, proofs and submission. The guide says applications should not receive users’ viewing keys and should check wallet capabilities before presenting supported actions.
A separate Privacy SDK guide describes how integrations can retain assets at a shadow address or collect proceeds back into the pool. The options include collecting the entire token balance, only the amount gained during an interaction, or an exact amount. Returning funds to a shielded balance is therefore a specific application flow, rather than an automatic property of every public position.
The product question is whether applications can make that sequence understandable without overstating privacy. Similar demand for confidentiality underlies Ethereum-based settlement tools for banks, although the users, controls and integrations differ.
STRK20 backups and disclosure limit privacy
Recovery introduces another responsibility. The viewing-key guide warns that a normal seed phrase may not independently reconstruct the viewing key already registered for an account. Losing that key can prevent discovery and use of shielded funds.
The guide calls for a separate protected export for each account. A leaked viewing key exposes private balances and activity but does not authorize spending; the ordinary account signature remains necessary. The auditor’s encrypted copy is not presented as a personal recovery service.
The compliance documentation describes deposit screening by Elliptic, with an FPI-managed signer providing an attestation verified by the pool. It also says FPI operates the current auditor role, allowing selective disclosure under lawful process through an encrypted viewing-key copy.
Those controls make public confidentiality and regulatory visibility distinct properties. They address a different model from the restrictions in the Philippines’ privacy-coin exchange rules; the comparison does not establish how any jurisdiction will classify Shadow Accounts.
The same documentation acknowledges that recognizable amounts, closely timed deposits and withdrawals, and channel setup can weaken unlinkability. Public entry and exit transactions therefore remain relevant even when movement within the pool is encrypted.
Fear & Greed Index
October 15, 2026; checked 05:59 UTCAlternative.me’s Bitcoin-focused sentiment index read 53, or neutral, against 62 the previous day. It is a broader market indicator, not a measure of Shadow Accounts adoption or STRK sentiment.
The next evidence to watch is audited application support, wallet compatibility and disclosed usage beyond demonstrations. Until those figures are available, the documented advance is a new way to separate wallet identity from persistent public positions, with explicit limits on confidentiality and recovery.
Stay up to date
Get the latest crypto insights delivered to your inbox
Primary sources and further reading
| Source | Title |
|---|---|
| | Starknet: STRK20 privacy overview |
| | Starknet: Shadow Accounts and mainnet demo status |
| | Starknet: Wallet API integration and compatibility |
| | Starknet.js: WalletAccount and persistent public positions |
| | Starknet: Viewing keys and recovery |
| | Starknet: Compliance, auditing and privacy limitations |
| | ChartExchange: STRK/USD composite historical prices |
| | Alternative.me: Crypto Fear and Greed Index |
Fact-checked by: Daily Crypto Briefs Fact-Check Desk
Related Articles
Frequently Asked Questions
What are Starknet Shadow Accounts?
They are persistent application-specific addresses funded through STRK20 shielded balances. They separate public DeFi positions from the public identity of a user's main wallet.
Do Shadow Accounts hide balances and transactions?
No. The shadow address's balances, calls and positions remain public. The protected connection is between that address and the main wallet; public funding edges and recognizable patterns can still weaken privacy.
Is the Shadow Account vault demo production software?
Official documentation describes a mainnet demonstration using the Vesu Prime STRK vault and real assets, while explicitly labeling it an unaudited educational example.
Which software supports Shadow Accounts?
The current STRK20 guide specifies starknet.js 10.8.0 and Wallet API 0.10.4, plus a connected wallet supporting the relevant STRK20 methods. Support must be checked for each wallet and application.
Can a viewing key move Starknet funds?
A viewing key reveals private activity but cannot authorize spending. The official guide warns that losing an account's viewing key can make shielded funds inaccessible even when the ordinary seed phrase remains available.