Documentation Index Fetch the complete documentation index at: https://dev-docs.multihopper.com/llms.txt
Use this file to discover all available pages before exploring further.
What is a Route? A route is the fundamental unit of MultiHopper. It defines a complete token transfer pipeline: a sequence of recipients and execution times that play out automatically on-chain after the route is funded.
Think of a route as a smart payment program you deploy once and let run.
RouteConfig Fields The RouteConfig on-chain account stores the full route definition:
Field Type Description route_id[u8; 32]Unique 32-byte route identifier creatorPubkeyWallet that created the route original_mintPubkeyMint address of the deposited token (or native SOL mint) route_token_mintPubkeyToken2022 wrapper mint address mint_authorityPubkeyPDA with authority to mint/burn wrapper tokens source_ownerOption<Pubkey>Optional source wallet — used by the abstraction path to link the route to an origin wallet hopsVec<Hop>Ordered list of transfer steps (up to 64 hops) hop_amountu64Single token amount shared across all hops (in base units) is_finalizedboolWhether the route has been fully initialized and locked created_ati64Unix timestamp of route creation prepaid_hopsu8Number of hops that protocol fees have been paid for — execution is rejected beyond this limit provider_idOption<[u8; 16]>Optional integrator identifier from a registered Provider account reference_idOption<[u8; 16]>Optional external reference ID set by the integrator
Hops Each hop within a route specifies:
Field Description recipientSolana wallet address receiving tokens at this step execute_atUnix timestamp — the earliest this hop can execute
Route Variants Two route creation instructions exist depending on the asset type:
Instruction Use Case initialize_routeSPL token routes initialize_route_solNative SOL routes (uses a dedicated sol_vault PDA) initialize_route_providerSPL route with a registered provider and optional reference ID initialize_route_provider_solSOL route with a registered provider and optional reference ID
Route Constraints
Routes are immutable after finalization. The hop sequence, recipients, and timing cannot be changed.
Hops execute in strict order . Hop N cannot run until hop N-1 is complete.
Timing is enforced by the Solana clock on-chain. No hop can run before its execute_at time.
Execution is gated by prepaid_hops
Route Limits Constraint Value Maximum hops per route 64 Supported tokens SOL, SPL, Token2022
Closing a Route Once a route is fully settled (all hops complete, vault emptied), the close_route instruction reclaims the RouteConfig account rent and returns lamports to the creator.
Identifying Routes Each route is identified by its route_id (a 32-byte value). The on-chain account address is derived as:
PDA: [b"route", route_id]
Use this ID to query route status via the API or track on-chain state.
Route Lifecycle See how routes move from creation through settlement.
