Rango

• Name: Rango
• URL: https://rango.exchange/
• Tags: ethereum-ecosystem bitcoin-ecosystem solana-ecosystem
• Category: cross-chain routing middleware / venue-selection layer
• Summary: Rango is route-packaging middleware. The useful read is route ranking, partner admission, fee and middleware defaults, and whitelisted message-passing policy — not the universal aggregator slogan.
• What it does:
  • Aggregates bridges, DEXs, and other onchain venues to build swap and transfer paths across 50+ chains according to the docs and 70+ chains according to the homepage marketing surface
  • Offers API, SDK, widget, and mobile SDK integration surfaces for dapps, wallets, and other products that want outsourced route construction and execution packaging
  • Supports single-step and multi-step API flows, route quotes, transaction creation, approval/status tracking, and monetization or referral-fee tooling
  • Exposes message-passing flows so integrators can bridge tokens plus a custom payload to whitelisted receiver contracts that implement Rango’s interface
  • Publishes open-source contracts and architecture docs describing a diamond-proxy-based contract system with per-bridge facets and middleware contracts on destination chains
• Key claims:
  • The homepage calls Rango the “#1 Universal Cross-Chain DEX & Bridge Aggregator” and says users can move assets across 73+ chains from a single interface powered by Rango’s API
  • The docs describe Rango as “a new layer on top of all Bridges and DEXs,” which is directionally right so long as the note stays on routing and middleware defaults rather than on brand-level universal rhetoric
  • The docs and llms index show a broad integrator surface: basic API, main API, SDKs, widget, mobile SDK, rate limits, monetization, message passing, and smart-contract architecture docs
  • The “How It Works” docs say Rango’s routing engine searches combinations of 100 DEXs and 24 bridges across more than 50 blockchains and uses message-passing systems such as GMP, LayerZero, and IBC Memos
  • The smart-contract docs and public rango-contracts-v2 repo indicate that the contract layer is open source and centered on an EIP-2535 diamond architecture with per-bridge facets and middleware contracts
• Whitepaper: No canonical standalone whitepaper or litepaper was found in this pass. The strongest primary-source surface was the official site, the docs index and architecture pages, the message-passing docs, and the public SDK/contracts repositories; see ../whitepapers/rango-primary-sources-2026-04-26.md.
• Sources:
  • https://rango.exchange/
  • https://docs.rango.exchange/
  • https://docs.rango.exchange/llms.txt
  • https://docs.rango.exchange/how-it-works
  • https://docs.rango.exchange/smart-contracts/architecture
  • https://docs.rango.exchange/smart-contracts/message-passing.md
  • https://raw.githubusercontent.com/rango-exchange/rango-sdk/master/README.md
  • https://raw.githubusercontent.com/rango-exchange/rango-contracts-v2/master/README.md

Internal linkages

• Best upward reads for routing and hidden-defaults contrast: across and li-fi.
• Keep this note on route ranking, partner admission, middleware permissions, and whitelisted receiver policy rather than spending graph budget on every venue Rango can call.

Control surface

• The leverage sits in venue admission, route ranking, fee insertion, fallback behavior, and which message-passing or receiver-contract paths Rango keeps first-class.

• The whitelisted receiver requirement matters because it turns bridge plus payload into a policy surface, not just a convenience feature.

• Treat Rango as route-packaging middleware, not as a neutral bridge or verification layer.

• Last reviewed: 2026-06-14 UTC