$LUXRASYNCING
GUIDE

How it works

Luxra is a reading layer. Your browser asks for a token, a pool or a trade; the server collects the answer from public Solana sources, keeps it for a few seconds so every visitor shares one read, and returns numbers with their origin attached. No step signs anything.

01
Find
search or paste
02
Read
mint account
03
Map
every pool
04
Quote
six routes
05
Check
published rules
06
Decide
in your wallet

The pieces

Your browser
Asks for a reading and draws it. Keeps your watchlist and theme in local storage, nothing else. A wallet connection, if you make one, only shares your public address.
Luxra server
Calls public sources on your behalf, spaces those calls out so free rate limits are respected, caches each answer for seconds to minutes, and refuses requests that are too large or too frequent.
Public sources
A Solana RPC node for mint accounts and balances, a public pair index for pools, a public token index for symbols and reference prices, and a public quote aggregator for routes. Listed on Data sources.
Your wallet
Stays yours. Luxra never asks it to sign a message or a transaction. When you act on a reading, you do it in the wallet or venue you already use.

A risk report, in order

  1. 01
    Paste a mint
    Any SPL or Token-2022 mint. The address is checked locally first: base58, 32 to 44 characters. Anything else never leaves the page.
  2. 02
    The mint account is read
    Supply, decimals, mint authority, freeze authority and any Token-2022 extensions come from one getAccountInfo call. Metadata comes from the Metaplex account or the token's own metadata extension.
  3. 03
    Holders are read when the node allows it
    The largest token accounts are asked for on chain and grouped by owner, with pool and curve accounts labelled. Free public nodes often refuse this call; then the report uses the token index's top-holder share and says so.
  4. 04
    Pools are mapped
    The public pair index lists every Solana pool for the mint. Liquidity is summed, venues are counted, the largest pool's share is measured and the oldest pool's age is noted.
  5. 05
    The rules run
    Each rule compares one measured value with a fixed threshold and prints both. The full list is on Risk rules. The report adds no score and draws no conclusion.
  6. 06
    The answer is shared for a minute
    The same report is served to anyone who asks for that mint within sixty seconds, which keeps the public sources usable for everyone.

A route comparison, in order

  1. 01
    You choose a pair, an amount and a slippage
    The amount is converted to the token's smallest unit exactly; an amount with more decimals than the token allows is refused rather than rounded.
  2. 02
    Six quotes are requested
    Best route across every venue, a single pool with no hops, and four venue families on their own. Requests are spaced and alternate between two public hosts of the same aggregator.
  3. 03
    The rows are lined up
    Output, difference to the best route in basis points, the aggregator's price impact figure, and the minimum you would receive at your slippage setting.
  4. 04
    You decide elsewhere
    The page shows no swap button. If a route looks right, you take it in your own wallet or venue, where the final amounts are shown again before you sign.

Lines Luxra does not cross

  • Hold your tokens, your keys or any approval over your accounts.
  • Ask your wallet to sign a message, a transaction or a permit.
  • Build or forward a swap. The quote endpoint returns numbers only.
  • Store who looked at which token. Caches hold public data, keyed by mint or pool, never by visitor.
  • Call any token safe, or tell you to buy or sell one.
  • Fill a gap with an estimate. A missing value is shown as a dash.

Interfaces for builders: Public API. Thresholds in detail: Risk rules.