Ghost mode

Figures blurred on screen

With ghost mode on, balances, amounts and addresses are blurred until you point at them or focus them. It protects against the person behind you, a screen share or a screenshot, not against the chain. Toggle it from the top bar of the app, by tapping the screen with two fingers on a phone, or by pressing G on a computer when you are not typing in a field. The choice is kept in this browser under ghostdex:ghost-mode.

Sharing your mix

Share mix, on Portfolio, turns what the address holds into a card of whole percentages: up to six positions by name and Other for the rest, with anything under 3% counted in Other. The card shows no amounts, no address and no ghost name. Posted on X, the link opens as the card.

• Everything on the card is in its link, for example /mix/NVDA-38.TSLA-22.USDG-15.OTHER-25. Ghostdex keeps no copy and does not know who made it.
• The link only accepts listed stock symbols, USDG, ETH, Earn and Other, in whole numbers that add up to 100, so nobody can put their own text on a Ghostdex card.
• Stocks only leaves ETH, USDG and vault deposits out of the card.
• Percentages still say something. An unusual mix is easier to match to a wallet by someone who compares it with the holdings on the explorer.

The relay

To show a balance or send a transaction, a browser normally talks straight to a node, and the node sees the browser's IP address next to the addresses it asks about. On Ghostdex, the page sends its chain reads and broadcasts to the Ghostdex relay at /api/rpc first. The relay forwards each request unchanged to a public node and returns the answer, so the node sees our server instead of you.

• The relay accepts only standard read methods and eth_sendRawTransaction, which carries a transaction already signed in your tab. It holds no key and cannot sign anything.
• Every transaction a ghost, a link or the Ghostdex wallet sends is filled in completely in your tab (nonce, gas, fees) before it is signed, so no node is ever asked to fill one in. Until 22 October 2026, the signing library asked nodes to, and when the relay refused, it retried on public nodes from the browser.
• The route stores nothing and logs nothing about the requests it forwards.
• Vercel, which hosts Ghostdex, may keep standard request logs (such as IP address, time and path), as any host does.
• If the relay does not answer, the page falls back to public nodes directly, so the app keeps working.

What does not go through the relay

• Transactions signed by a browser wallet extension are sent by that wallet, through its own provider. Ghost transactions are signed in your tab and go through the relay.
• Reads on Ethereum, Base, Arbitrum and BNB Chain also go through the relay first, with public nodes as the fallback. That covers a ghost funded from an exchange as well as your wallet's balances when you bridge.
• Quotes come from LI.FI through Ghostdex's server, so LI.FI sees our server, but each request contains the addresses and amounts of the route.

The relay itself sees the requests it forwards, including the addresses your tab reads, which in one session are often your main wallet and your ghosts. That is why it keeps nothing, and why Privacy model lists it among the parties that could see something.

No analytics

Ghostdex runs no analytics, sets no tracking cookies and embeds no third-party pixels or widgets. What the site keeps in your browser is listed in the Cookie policy.