Understanding arbitrage
Arbitrage aims to buy an asset in one market and sell an equivalent amount in another at a price that covers both trades and their costs.
Arbitrage includes manual route analysis, a configurable atomic Solana adapter and a configurable prefunded cross-chain cycle. Saved quote cycles can be monitored automatically through Alerts while the worker is running. Market-wide opportunity discovery is not available. Funded acceptance of these execution adapters remains outstanding.
Atomic Solana cycles
The atomic form prepares SOL → classic SPL token → SOL as one transaction, capped at 0.01 SOL input. Supply the intermediate mint address and your minimum profit in SOL. Preparation checks the encoded swap accounts and amounts, both routes, account rent, network fees and the combined RPC simulation.
The final swap instruction requires an output covering the starting SOL, the quoted network fee, any new intermediate token-account rent and your requested minimum profit. Both swaps execute together or revert together. An on-chain failure can still charge network fees. A positive price snapshot alone is not enough to prepare an order, and a profitable route may not exist.
Initial requirements:
- The wallet must have enough SOL for the input, gas and token-account creation.
- Its wrapped-SOL associated account must not already exist. Temporary rent for this account is returned when a successful transaction closes it.
- The intermediate associated token account must be absent or empty, unfrozen, and have no delegate or close authority. The trading wallet must not control that mint's minting or freezing authority.
- Token-2022, extra signers, unsupported instruction formats, routes requiring excluded program access, and transactions exceeding Solana size limits are rejected.
A successful first swap may leave intermediate tokens beyond the amount consumed by the second swap. Those tokens remain in your wallet and are not counted toward the minimum SOL profit. A non-empty intermediate account prevents another cycle through this initial adapter.
Review the mint, fees, temporary rent and return requirement. The review expires after 20 seconds. Approval signs the whole transaction; the server verifies the signed message and records its signature before one RPC submission. If the response is lost, use Activity to check that signature. Do not repeat the trade to recover an uncertain submission. Pausing the integration leaves history and status checks available.
Manual price analysis
Select a starting asset, an intermediate asset, an amount and your public addresses. SANVIO requests A → B, then B → A using the first quote's minimum output as the return input. The route must end in the identical registry asset, with matching decimals. Solana pairs use Jupiter; other pairs use NEAR Intents. A provider may decline a route even when both assets appear in its registry.
Read the result
The result shows the difference at the two quoted minimums, before source-chain gas. Provider costs reflected in quote outputs are already included. Source gas and inventory recovery costs are not verified, so net profit remains unknown. A positive difference is not an executable opportunity or a promise of profit.
Both quotes are snapshots. They do not lock the return price through settlement, and combining their minimums does not create an atomic guarantee. Results are marked stale after 30 seconds. Editing any input clears the result. This check does not generate a deposit address, request a wallet signature or move funds.
What makes an opportunity executable
A comparison needs actual quotes for the intended trade size, enough liquidity, verified asset identities, current balances and all costs. Matching tickers or different reference prices alone do not establish an opportunity.
Trading across chains
Transactions on different networks can finish at different times or have different outcomes. A cross-chain strategy needs an inventory model and a way to track settlement and handle an unfinished leg. Restoring inventory can add cost.
Prefunded opposing routes
Connect two wallets that already hold native funds. The supported assets are native SOL on Solana, native ETH on Robinhood Chain, and native NEAR. The adapter requests two signed NEAR Intents quotes and verifies their signatures, exact asset identities, recipients, refund addresses, amounts and deadlines. A listed asset does not guarantee a working route.
The first side converts A to B. The second independently converts B to A using existing B inventory. Its input equals the first side's minimum B output minus the B network fee reserve. Preparation requires a positive minimum A gain after the A fee reserve and a nonnegative B change. If these conditions fail, no cycle review is created. These are opposing provider conversions; the app does not discover a direct buy/sell discrepancy between local DEX pools on different chains.
Each wallet approves its own native deposit. The quote review expires after 60 seconds, and the second side may expire while the first is in progress. There is no transaction that rolls back both networks together. A provider refund can also leave an incomplete cycle. Quoted gains are conditional on both settlements and on actual network costs staying within the displayed reserves.
Transfers and recovery
Use Rebalance for a single native transfer. The initial deposit limits are 0.01 SOL, 0.01 ETH on Robinhood Chain, and 1 NEAR. SPL tokens, ERC-20 tokens and arbitrary NEP-141 tokens are outside this execution adapter's current scope. Launching tokens with the same name on three networks does not add routes or make them interchangeable.
Before wallet handoff, SANVIO records a claim. Solana signatures are recorded before one server broadcast; EVM and NEAR wallets broadcast directly. If a handoff is interrupted, open Activity and attach the existing transaction hash from your wallet. An uncertain handoff is retained and cannot be resent through the order. Only a leg that has never been handed to a wallet can be cancelled.
Use Check deposit and settlement to verify the origin transaction and refresh provider status. A provider success report becomes a settled record only after the native destination amount and recipient are independently verified against finalized RPC receipts. Some internal payouts require receipt or trace methods the public RPC may not support; these remain unverified. A failed provider report alone is not proof that your funds were refunded. Checks and history remain available while new transactions are paused.
When exactly one side has settled and the other has failed, been refunded, or been cancelled before handoff, Prepare recovery review requests a fresh reverse conversion of the received inventory, reserving another source network fee. Recovery needs its own wallet approval and can realize a loss. It does not repeat the completed leg or undo fees already paid. If a recovery itself fails, inspect its receipts before taking further action; automatic repeated recovery is not provided.
Download the transaction record from Activity. It includes the signed provider quote, recorded hashes, per-leg outcomes and verified native cashflows separately for each network. Pending receipts are excluded. History belongs to the current browser session; export it before clearing cookies.
Existing NEAR Intents deposits can be looked up at Rebalance. Saved status and refund reports remain available when new transactions are paused. These are provider reports; SANVIO does not independently verify the destination or refund receipt, and the lookup cannot initiate or repeat a transfer.
Current alternatives
Use workspace features to explore provider assets and request real quotes. Check Availability for execution scope. There is no guarantee that a future opportunity can be closed profitably.