Photon: speed lives inside a separate trading wallet

The short answer

Photon is a web and mobile trading terminal with live-pair and launch feeds, charts, token-risk fields, quick buy and sell controls, multiple wallets, limit orders, DCA, and configurable transaction submission. This guide focuses on Photon on Solana; Photon's public documentation also has a separate Ethereum section. The important setup detail is that connecting Phantom signs you in, then Photon generates a distinct trading wallet that must be funded before it trades.

Where it sits in mid-2026: Photon lost the desktop terminal war to Axiom and now competes as the lightweight, fast-loading option rather than the default. That is a legitimate niche — fewer surfaces means fewer settings to audit — but expect thinner feature velocity than the category leader.

The connected wallet is not the trading wallet

Photon's Solana setup guide tells users to connect Phantom, then generate a new Photon trading wallet. The private key for that generated wallet is revealed once, and the user is instructed to save it before continuing. Deposits move SOL from the sign-in wallet into the trading wallet; withdrawals send assets back out from the trading wallet.

That separation can protect a primary wallet if it is used deliberately, but it also creates a recovery obligation. Save the key offline at creation, import a copy into a reputable wallet only when needed, and treat the Photon wallet as a hot operational wallet. The public product pages do not fully document every server-side signing and recovery boundary, so do not store long-term assets there or assume that “shown once” means the key never exists in another system.

Discovery is organized for action

Photon's Live Pairs feed surfaces pair age, initial and current liquidity, FDV, transaction counts, volume, buys and sells, tax fields, audit results, and social links. Memescope adds launch-stage filters such as bonding progress, holders, developer holdings, liquidity, market cap, and activity. Token pages put a chart, trade tape, holdings, P&L, and security fields beside quick execution.

These fields shorten research time; they do not remove the need to identify the exact mint and pool. “Audit Results,” mint authority, LP burn, top-holder share, and deployer labels are indexer outputs. Confirm the raw authority, balances, and transfers on an explorer, and request a size-specific route before treating a displayed liquidity or price as executable.

Presets package several permissions together

Photon allows three profiles—S1, S2, and S3—to combine slippage, priority fee, bribe, and Smart-MEV settings. A token page can override slippage and priority for one transaction. Auto Speed can select priority and bribe values based on recent successful transactions, while the documented Fast and Secure paths choose between Jito and bloXroute according to the bribe amount.

A preset is not simply “fast” or “safe.” It authorizes a maximum price movement, explicit fees, and a submission route. Name presets by their actual numbers, not their mood. Before clicking Quick Buy, confirm the selected wallet, amount per wallet, maximum slippage, priority fee, bribe, and MEV path.

Automation triggers an order; it does not guarantee the target

Photon documents buy-dip, stop-loss, and take-profit orders triggered by market cap, price, percentage change, or a chart line. DCA orders split buys or sells by interval, count, market-cap range, and expiration. Multi-wallet orders can run across as many as five active wallets, with the entered amount applied to each selected wallet.

A trigger observes an indexed condition and then submits a swap. The fill can land later and worse, fail slippage, or encounter too little liquidity. Review every active order after a partial manual exit, wallet transfer, migration, or liquidity change. Multi-wallet mode multiplies exposure, terminal fees, network fees, and operational mistakes—it does not create a single atomic fill.

The 1% fee is only the first line

Photon's published Solana fee is 1% of the input value for every buy and sell, collected in SOL. Add the venue or launchpad fee, base network fee, priority fee, bribe, price impact, and slippage. A fixed priority fee or bribe is especially expensive as a percentage of a small trade, and multi-wallet execution repeats several of those costs.

Photon's P&L fields are convenient, but reconcile them with wallet deltas. Transfers, positions acquired outside Photon, unsold inventory, rent movements, and fees outside the displayed formula can change the economic result.

Product documentation can lag the product

Several official Solana pages reviewed here were last updated roughly one or two years ago. Memescope still describes Pump.fun-origin launches migrating to Raydium, even though the current canonical lifecycle uses PumpSwap. Treat the documentation as a description of concepts, then verify the live interface, current fee preview, launch program, and actual pool before trading.

A safer evaluation workflow

1. Bookmark the official domain. Never reach a wallet terminal through an ad, reply, or unsolicited support message.
2. Create and export a fresh trading wallet. Save the key offline, then fund only a small test balance.
3. Verify one feed result. Match the mint, pool, authorities, holders, and recent transactions against an explorer.
4. Make every preset explicit. Record slippage, priority, bribe, MEV mode, wallet count, and total intended spend.
5. Test one tiny manual trade. Compare expected output and fees with the signature and final wallet deltas.
6. Test automation separately. Measure trigger delay, landed price, failed orders, cancellations, and duplicate-attempt behavior.

What belongs in the journal

Record the Photon wallet address, mint and pair, feed and audit fields observed, explorer verification, selected preset, slippage, priority fee, bribe, MEV mode, automation trigger, platform charge, signature, actual deltas, and timestamp. For multi-wallet trades, record the intended and landed result for each wallet.

Primary sources