MultiHopper is built as a layered system. The protocol layer enforces all routing guarantees on-chain; the application layer provides the tooling to create and monitor routes.
7ukX5xXys5nekSfvWxqfCJpjJxF9ymvJz9v9wSCR6fkeHandles route creation, hop execution, wrap/unwrap operations, fee collection, provider registration, and fee schedule management. This is the primary program for all route interactions.
Orchestrator
4TPCmR2uN3hDM1FbTsf7ZtFXwXGSz4u1Kxv5YHj6eruXA permissionless execution engine that breaks route deployment into discrete keeper-executable steps. Manages the multi-transaction sequence needed to fund and initialize a route on behalf of the creator.
Distribution and execution are intentionally separated. The abstraction layer handles asset routing and intermediate wallet coordination. The hop execution engine handles sequenced transfers. This separation allows each layer to evolve independently and makes the security boundary cleaner.Permissionless execution. No single entity controls whether a route executes. Any keeper can trigger orchestrator steps or hop executions — the program validates correctness, not identity.Off-chain indexing, on-chain authority. The indexer and API provide a convenient read layer, but they hold no authority over funds. All state that matters for settlement is on-chain.Provider extensibility. Integrators can register as providers via register_provider, attach a provider_id to routes, and configure per-provider fee tiers via initialize_fee_schedule / update_fee_schedule.