Know your private side.

The $VELUNE model connects creator fees to three destinations: a shared privacy reserve, holder utility, and protocol operations. The reserve is designed to help cover eligible privacy costs. Final allocations and the rules for using that balance belong in the token’s release record.

Workspace and Agent use a $150 holder-access threshold. Terminal, documentation, and the local file vault are open to everyone. Holder access reads a public wallet balance; it does not request a signature or move funds.

The terminal brings together major-asset reference markets and Robinhood Chain tokens. CoinGecko supplies prices and candle history for majors; DexScreener supplies public pool data for chain assets. The board opens on Memes and separates Memes, Majors, and Stocks, with search by name, symbol, or token contract.

Candlestick and area views support crosshairs, panning, zoom, selectable history ranges, and a 20-period moving average. Prices are quoted in USD. Majors are reference markets and their swap controls are disabled. Cached candle history shows its capture time. An embedded chain chart can have no history even when its pool has a current price.

Choose an amount and slippage in the order panel, then review the action. Transaction availability is checked before any approval or transfer request.

The private-transfer flow is organized into Connect, Unlock, Prepare, and Review. ETH and USDG are the assets presented in the workspace. Deposit and withdrawal preparation keep the amount, destination, and review step separate from wallet connection.

A connection is not permission to spend. Any future deposit or token approval must be explicitly reviewed. A withdrawal must also confirm the recipient and any relay payload before submission. Public timing, amounts, wallet history, and provider metadata can still reveal associations: privacy is not a guarantee of anonymity.

Velune’s guide explains the fee model, wallet connection, private-transfer flow, and local file vault. It answers supported questions from the documentation included in the application and links to the relevant tool or section. Conversations remain in the current tab.

The guide cannot inspect a live private balance, produce an executable quote, sign a message, approve a token, or move funds. Financial decisions and their review steps remain in the terminal and workspace.

Wallet connection uses installed EVM providers discovered through EIP-6963, with a fallback to an injected browser wallet. Connecting requests a public account address only. Velune does not ask for a recovery phrase or import a private key.

Disconnecting clears the displayed account. Wallet permissions are managed in your wallet. Private-account key derivation and note recovery depend on the pool implementation used for execution; those details must be verified before enabling transfers. File-vault recovery is separate and depends on keeping your encrypted file and passphrase.

Files up to 20 MB are encrypted entirely in your browser with AES-256-GCM. A fresh 16-byte salt and 12-byte nonce are generated for every file. PBKDF2-SHA256 derives the key with 600,000 iterations. The versioned VLN1 payload encrypts the original filename, file type, and contents.

The file and passphrase are not uploaded. Downloaded encrypted file size remains observable. Keep a long, unique passphrase separate from the encrypted .velune file and test decryption before deleting the original. There is no passphrase recovery service. A compromised browser, malicious extension, or compromised device can undermine local encryption.

Chain assets are identified by their token contracts and pool addresses. A matching name or ticker does not establish identity. The terminal exposes the selected token’s contract and a link to the source market so you can inspect it independently.

Major-asset reference prices do not establish that a corresponding token exists on Robinhood Chain. Tokenized assets follow their issuers’ terms. Public market providers can be delayed or unavailable, and pool depth can affect quoted prices.

Velune’s interface uses React and TypeScript. Its scene combines GPU particle lettering, a rotating 3D sculpture, and a canvas fallback for browsers without WebGL. Market history is rendered with TradingView Lightweight Charts. Public data is requested through Velune’s server endpoints.

The file vault processes files locally. Connecting a wallet reads its public account. Market requests go to their respective public data providers. The current guide uses local documentation; it does not send your conversation to a hosted language model.

Review the release record before relying on financial execution. A rendered interface, wallet connection, or market price is not evidence that a transaction route has been audited or tested with funds.

Velune is an independent project. It does not claim Robinhood endorsement, protocol affiliation, an independent audit, a funded privacy reserve, or a completed funded transaction.