Privacy model.

Your wallet holds the authority

SHADOW is noncustodial. Your connected wallet signs transactions; SHADOW receives signed transaction bytes for submission and never receives your wallet private key. This protects signing authority, not transaction privacy. Standard Solana trades reveal addresses, amounts, tokens, program calls and timing.

Choose your account controls

• Normal trading: direct, public execution from the connected account.
• Isolated accounts: separate accounts managed by your wallet. Public funding transfers and transaction patterns can still link them. The mode label does not switch or create a wallet.
• Privacy-enhanced trading: unavailable. SHADOW has no integrated shielded-balance, confidential-swap or stealth-address provider.

The SHADOW / NEAR pair

The proposed liquidity pair is SHADOW / NEAR. Token pairing does not hide trades, protect funding links or activate confidential execution. The chain, exact token contracts and pool have not been configured. This is separate from SHADOW’s privacy protections.

Read the links with context

The dashboard reads the most recent 20 transactions referencing your active account. Edges show observable native transfers. Token transfer links preserve token-account addresses without guessing their owners. Repeated funding is a possible linkage signal, not proof of common ownership. Exchanges, relayers and shared programs can create similar patterns. Missing edges do not mean an account is untraceable.

NEAR Intents access

The NEAR Intents page opens the provider’s independent cross-chain application. NEAR documents public and confidential routing. SHADOW has not integrated its confidential execution or private balances. Current terminal swaps use public Solana transactions through Jupiter; external provider trades are separate from Arena activity.

Confidential execution

Privacy Cash publishes a Solana SDK, and Arcium provides encrypted-computation infrastructure. Token-2022 confidential balances require issuer, asset and application support. None is presented here as a verified SHADOW private-trading integration. Audit reports must be mapped to the exact deployed code and complete deposit, swap and withdrawal flow before activation.

Sources: Privacy Cash SDK, Arcium documentation, Solana confidential balances. Detailed research and integration gates are recorded in PRIVACY_MODEL.md.

Where information goes

RPC providers receive queried addresses. Market providers receive token and pool requests. Jupiter receives route requests, taker addresses and signed swaps. Hosting providers can observe IP addresses and request metadata. Local preferences and account labels remain in browser storage in this release. Clearing browser storage removes those local records.

Keys never belong in terminal settings

Core trading uses service API keys on the backend and signatures from your wallet. Keep user trading keys, seed phrases and recovery files out of SHADOW, Supabase and hosting variables. The separate optional Railway creator-fee service has a dedicated creator-authority signer configuration; it must never use your trading or developer wallet. Read operator setup before configuring that service.