Inside the RIFT Routing Terminal

A visual workspace for comparing routes, reviewing moves and exploring with virtual assets.

Before a swap, there is a pair, an amount and a decision about the path. The output matters, but so do the steps that produce it: the route, its costs, the review and the resulting balance.

RIFT puts that path at the center of the experience. Its terminal brings a route map, a trade ticket, a virtual portfolio and a local operation history into one workspace. You can change the pair, compare alternatives, review a move and follow its effect on the virtual balances.

The trade flow uses virtual assets and fixed fixture rates. A separate network panel reads actual public Solana information, with a source and observation time for every successful update. You can explore the trading interface while seeing a real pulse from the network around it.

The route becomes part of the interface

RIFT takes its visual language from a transport map. Lines divide, turn, reconnect and arrive at an output. Selecting a path changes the highlighted rail and the details in the trade ticket, so the diagram follows your choice.

The website introduces that idea through a short animated opening and a scroll sequence covering quote, comparison and review. The same sequence also works through direct controls and keyboard navigation. Inside the terminal, the map becomes a practical way to understand which path is selected and where the operation is in its local progress.

The design keeps the essential information close to the action. Your virtual portfolio sits beside the route workspace. The trade ticket shows the selected pair and estimated result. The history records the local outcome after confirmation.

Black, paper white and orange give the routes a clear hierarchy. Motion follows a scroll, a selection or a confirmation. Reduced-motion support keeps the same information available without the animated opening or moving effects.

Start with a pair and an amount

The current virtual portfolio includes SOL, USDC, wBTC and a RIFT virtual asset. Choose what to pay with, choose what to receive and enter an amount. You can reverse the pair or use Max to explore the available virtual balance.

RIFT calculates the comparison from fixed, documented rates. These give the workspace a repeatable foundation: changing a pair or amount changes the result according to the same known rules. They are fixture values rather than current market prices.

The terminal offers three model paths: Direct rail, Crosslink and Split path. Each has a different fixture fee, and the comparison shows the resulting virtual output. The displayed lanes describe the model path; they do not identify real exchanges or available liquidity.

For example, the fixture values one SOL at 150 USDC. With an input of one virtual SOL, the three paths produce:

Crosslink: 0.18% fixture fee; 149.73 virtual USDC output.
Split path: 0.24% fixture fee; 149.64 virtual USDC output.
Direct rail: 0.30% fixture fee; 149.55 virtual USDC output.

Crosslink has the highest output under these fixture rules. Selecting another path changes the map and the trade ticket together. The comparison is a way to inspect the model, rather than an executable exchange quote.

Slippage tolerance changes the minimum output displayed for the selected quote. At 0.5% tolerance, the Crosslink example shows a minimum of 148.98135 virtual USDC. That lets you inspect how a tolerance setting relates to an estimate within the simulator.

Review the move before confirming

The trade ticket is the place to check the proposed action. It brings together the input, output, selected path, fixture fee and minimum amount before the review opens.

The review then gives the move its own moment. You can inspect the same information and decide whether to continue. Changing the pair, selecting a route and confirming the result are distinct actions, rather than one automatic chain of clicks.

When you confirm, the terminal runs a simulated swap through its visible stages. It checks the current virtual ledger and applies the result locally. The portfolio changes, the new history entry appears and the completion screen identifies the operation as a local simulation.

In the one-SOL Crosslink example, the virtual SOL balance changes from 18.5 to 17.5. The virtual USDC balance changes from 2,400 to 2,549.73. Those exact changes make the result inspectable: the input was debited, the modeled output was credited and the history contains the corresponding record.

The interface also handles invalid amounts and an insufficient virtual balance. A review based on an obsolete ledger cannot simply be applied again. These controls give the simulator a consistent flow you can use and revisit.

Keep the result in a local ledger

A completed move creates a reference such as RIFT-SIM-000001. It identifies a local operation in the browser ledger. It is not a blockchain transaction signature.

Open an entry to inspect its pair, virtual quantities and selected path. Reload the page to return to the saved session. Export the ledger to download a JSON record, or reset the workspace to its starting portfolio and try a different sequence.

The saved ledger is validated before the terminal restores it. If its contents fail validation, the app starts a fresh virtual portfolio rather than accepting an altered balance as a valid session. If browser storage is unavailable, the interface identifies the session as lasting only for the current tab and offers export as a way to keep the local record.

This makes history useful during exploration. You can follow a single move, compare a series of choices or start over deliberately. No account registration, wallet connection or real deposit is needed for that workflow.

Read an actual pulse from Solana

The network panel has a separate source of information. It requests public Solana mainnet observations directly from RPC providers and verifies the network genesis before displaying a slot.

The primary configured endpoint is api.mainnet-beta.solana.com, with solana-rpc.publicnode.com as a fallback. A successful read shows the confirmed slot, the responding source and the observation time. The panel keeps a small list of recent slot observations so you can see subsequent updates arrive.

The slot request uses Solana's getSlot method at confirmed commitment. The method returns the highest slot reached at the requested commitment, as described in the official Solana documentation (https://solana.com/docs/rpc/http/getslot).

When available, the panel also reads a recent network performance sample. It calculates a period average from the sample's transaction count and duration. The displayed figure includes validator vote transactions and is labeled accordingly. Solana documents the sample fields in its getRecentPerformanceSamples reference (https://solana.com/docs/rpc/http/getrecentperformancesamples).

These observations describe the network. They are separate from RIFT's virtual swaps, local history and fixture asset values. A new observed slot does not mean a RIFT trade occurred, and the performance sample is not RIFT trading volume.

The panel attempts slot reads every ten seconds and performance sample reads at most every thirty seconds. It pauses when the page is hidden. Connection failures, provider limits and browser access restrictions can affect availability; a failed read produces a stale or unavailable state instead of replacement numbers.

Know where the data lives

The virtual ledger stays in this browser's local storage. The short opening sequence uses session storage to avoid replaying on every visit in the same session. Export downloads a local ledger file for you to inspect.

Those records belong to the current site and browser profile. Clearing site data removes the saved virtual session. Resetting the terminal changes its own local portfolio and history; it has no effect on a real wallet.

The live network feed does make external requests. The hosting service receives ordinary connection information when you load the site. A direct RPC provider receives the network query and information about the browser connection. The panel does not need a wallet address to read slots or performance samples.

The RIFT field notes (https://rift-route-terminal.vercel.app/guide/) explain the fixture rates, review flow, local records and network feed together. Keeping those responsibilities visible helps you understand which information comes from the local model and which comes from a public network response.

An experience checked from input to result

The terminal was exercised at desktop and mobile widths, including 320 pixels. The checks covered pair selection, reversal, route comparison, slippage, review, confirmation, the exact virtual balance change, history details, export, reload and reset.

The ledger checks also covered an insufficient balance, obsolete reviews and rejection of altered saved data. Separate network-panel checks covered provider fallback, invalid responses, truthful unavailability and stopping requests when the view is no longer active.

These checks establish the behavior of the current interface and its local model. They are functional verification of the virtual workspace, rather than evidence of real financial execution or an independent security audit.

Connecting this experience to financial execution would require additional work: actual executable quotes, available liquidity, supported assets, consented wallet signatures, transaction simulation, verified costs, submission and reconciliation of real receipts. Those requirements remain separate from what the current virtual terminal does.

Find your next route

Open the terminal and choose a pair. Compare the paths, adjust the amount and inspect the review. Follow the virtual portfolio change, open the history entry and try another route.

RIFT brings the path into view before the move and keeps the result available afterward. Its value as an experience is in making those choices concrete: an amount you can change, a path you can select and an outcome you can inspect.

Every turn. In view.

Explore the RIFT terminal (https://rift-route-terminal.vercel.app/app/) or start with the website introduction (https://rift-route-terminal.vercel.app/).