Trading service and execution choices
Sections ↑Rango combines access to decentralised exchanges, bridges and cross-chain liquidity systems. A user selects an asset on one network and a desired asset on the same or another network; the routing service constructs a path between them. Execution can involve multiple independent protocols, so the Rango interface is only one part of the trade’s operational chain.[2]
Its homepage displayed more than US$9.83 billion in cumulative volume, 13.40 million swaps, 3.47 million wallets and 150 business clients when checked. These are company counters without a clearly stated measurement cut-off. Wallets are not unique people, and cumulative swaps are not a count of currently active traders.[1]
Independent activity snapshot, 21 October 2026
| Metric | Rolling 24 hours | Rolling 7 days | Rolling 30 days |
|---|---|---|---|
| DEX aggregator volume | US$916,614 | US$6.96 million | US$39.55 million |
| Bridge aggregator volume | US$9.94 million | US$83.23 million | US$399.26 million |
How instructions move through Rango
| Model | Execution pattern | What the distinction changes |
|---|---|---|
| Public app | Wallet-based interface for selecting token and chain pairs. | Availability of a route depends on the selected networks, assets and underlying services.Source 3 |
| Basic API | Designed around a single principal transaction, with separate approval or prerequisite actions where required. | Fewer user execution steps do not remove destination-chain completion risk.Source 11 |
| Main API | The selected route is confirmed and its transaction steps are executed in sequence. | Later steps require their own successful preparation and signing flow.Source 18 |
The quote API accepts slippage tolerance and inclusion or exclusion of particular swappers. Its documented default is 0.5% when the parameter is omitted. That number filters acceptable routes; it is not an unconditional fee or a guarantee that a route will fill. Minimum and maximum trade sizes are returned for the particular swapper and asset, rather than established by one account-wide deposit minimum.[13][12]
Direct-app, route and partner costs
Sections ↑Charges that can coexist
| Charge | Published basis | Who or what determines it |
|---|---|---|
| Direct Rango app | The fee guide describes app.rango.exchange as charging no additional swap fee. | This does not remove network or underlying-protocol charges. |
| Underlying swapper | A DEX, bridge or liquidity protocol can charge for execution. | The selected route and its component protocols. |
| Rango protocol and partner | API and monetised integrations can add percentage fees. | Commercial configuration and affiliate settings. |
Rango’s monetisation page describes a 15-basis-point protocol charge alongside the affiliate’s configured amount. On a hypothetical eligible 10,000 USDC input with a 10-basis-point partner fee charged on that same basis, the components are 15 USDC and 10 USDC, or 25 USDC combined. Gas, bridge charges, liquidity fees and price movement remain outside this illustration. Enterprise arrangements can differ.[5]
Gas shown in a preview is an estimate, while transaction construction may allow a larger gas limit or bridge-fee allowance to reduce execution failures. A higher limit is not necessarily the final amount consumed. Rango’s gas documentation distinguishes peak execution requirements from the net amount ultimately charged and discusses refunds of unused allowances where the underlying mechanism supports them.[6]
Slippage and price impact require separate attention. A percentage service fee describes an explicit charge; the exchange rate determines the tokens obtained. The Main API flow recommends refreshing a route that has not been selected within its timeout, giving 30 seconds as an example, and comparing the confirmed output with the earlier quote. A displayed route is therefore not an indefinitely valid dealing commitment.[18]
Wallet assets, destination requirements and refunds
Sections ↑Rango’s asset notation combines the chain and token identity. Native ETH on Ethereum and a representation of ETH on another chain are different transferable assets even when their names look similar. Before funding a route, establish the source network, the exact token contract or denomination, the destination network and the receiving address. A familiar ticker does not establish that the recipient can use that version.[3]
Funding and execution stages
| Stage | Requirement | Why it matters |
|---|---|---|
| Prepare the source | The swap request specifies the source asset, amount and sender; final transaction data is generated separately from a preview. | A quote alone has not moved funds.Source 14 |
| Prepare the destination | Some non-native Stellar or XRP Ledger assets require a trustline before the source transaction starts. | A correct destination address alone may be insufficient.Source 16 |
| Approve where required | Use the route’s returned spender and approval transaction; some bridge addresses are generated dynamically. | A generic hard-coded approval target can be wrong for the route.Source 17 |
| Sign and submit | The wallet authorises the principal transaction after prerequisites are complete. | API access itself does not provide the wallet signature.Source 17 |
Destination setup can require a separate signature on that network. Rango specifically documents Stellar ChangeTrust and XRP Ledger TrustSet prerequisites for certain issued tokens. The instruction must be satisfied before sending into the route; it should not be treated as a problem that will necessarily be repaired after funds have already crossed the bridge.[16]
Possible end states of a cross-chain route
| Recorded result | What may be received | Follow-up |
|---|---|---|
| Desired output | The requested destination token. | Verify destination completion. |
| First swap reverted | Original input token remains or is returned. | Reconcile the failed source transaction and gas. |
| Bridge step failed | An intermediate asset on the source chain. | Check the actual output rather than expecting the original asset automatically. |
| Final destination swap failed | An intermediate asset on the destination chain. | A further swap may be needed; the original route did not deliver its intended token. |
A bridge refund may require user action. The status response can provide a diagnosis URL and inbound/outbound explorer links. Verify the transaction identity before following its recovery procedure; a failed route does not guarantee repayment of the original cash value.[15]
Wallet control, protocol exposure and security
Sections ↑The settlement architecture describes a Diamond contract for swap and bridge functions and middleware that handles tokens and messages at the destination. A route can combine a swap, bridge and another contract call. This explains why wallet ownership and transaction exposure are separate issues: a signature can authorise assets to move through several contracts even though the user has not opened a centralised custody account.[20]
Rango says its routing system monitors underlying protocols, removes unhealthy routes, and can pause affected integrations. It also describes multisignature administration where needed and checks for problematic tokens using external services. These are company-described controls. They cannot guarantee that a bridge, issuer, token contract or third-party execution venue will remain available or solvent.[7]
Public security documentation
| Document | What is disclosed | What it does not establish |
|---|---|---|
| Audit index | PeckShield reports and AstraSec versions dated September 2024 and October 2025. | An index alone does not establish complete coverage of every later integration or deployed version.Source 9 |
| Bug-bounty scope | Vulnerability reporting with exclusions for categories including liquidity and centralisation risks. | A researcher bounty is not reimbursement insurance for ordinary users.Source 8 |
| Private-key responsibility | Rango states it cannot access or restore the user’s private key. | There is no exchange-password reset that restores a lost self-custody wallet.Source 23 |
The inspected audit index links a Rango V2.1.1 AstraSec report dated 15 October 2025. This profile records that published version without claiming that every finding was resolved or that all current code was independently retested. No named customer insurance policy with a verified beneficiary and loss limit was established from the inspected security materials.[9]
Territorial restrictions and data handling
Sections ↑The May 2025 terms require users to be at least 18 and exclude US-connected restricted persons, listed prohibited territories and sanctioned persons. VPN circumvention is prohibited. Underlying providers can impose additional eligibility restrictions. A no-KYC marketing statement does not override these conditions.[23]
The privacy policy describes collection of IP addresses, device and browser information, usage data, wallet addresses and public blockchain activity. Connecting a wallet should not be understood as anonymous use of the website or infrastructure. Third-party applications using Rango can also have their own data relationship with the user.[24]
Failed routes, support channels and records
Sections ↑Published contact routes
| Purpose | Contact | Scope |
|---|---|---|
| Transaction follow-up | Discord support linked from the contact page. | Swap status and integration tickets. |
| General questions | [email protected] | General service enquiries. |
| Security disclosure | [email protected] | Vulnerability reporting. |
| Legal matters | [email protected] | Legal enquiries. |
| Partnerships | [email protected] | Commercial integrations and collaboration. |
Keep the request ID, transaction hash, chain names, tokens and amounts for an unfinished route. Rango’s error framework supplies a trace ID that support can use to locate a request. Error 1202 identifies a route-specific size limit; 1203 means the service could not retrieve a required balance. Neither should be interpreted simply as an executed trade that has disappeared.[12]
The failure-report endpoint is an optional diagnostic message. The documentation says it does not alter the swap flow. In particular, a client event named USER_CANCEL records an interface outcome; it does not prove that a transaction already submitted to a blockchain has been reversed. Reconcile execution before retrying, especially after an RPC or wallet error.[19]
Preserve source and destination explorer records together with actual output assets. One route can create several transactions. The status documentation did not establish a tax-ready consolidated statement or cost-basis certificate.[15]
Permissions and contractual recourse
Sections ↑No entity-specific financial permission was established. The terms include individual arbitration, broad liability exclusions and a damages provision referring to fees paid or a US$5 maximum. They do not identify a customer compensation scheme.[23]
Security monitoring can disable routing to an affected protocol, but that is an operational control rather than an adjudication process for a customer claim. Availability of an audit, a public API or a bridge integration does not itself supply a regulated complaint body or an entitlement to reimbursement.[7]
Brand, investment and operator disclosure
Sections ↑The inspected contract identifies the service as Rango Exchange without establishing a separately named incorporated operator. This limits entity-specific verification of its permissions and recourse arrangements.[23]
Binance Labs announced an investment in Rango on 19 June 2024. The announcement describes a cross-chain DEX and bridge aggregator; it does not say Binance acquired it or became the contracting exchange for its users. That investment is therefore kept separate from the ownership and operational identity of the Binance trading platform.[25]
The current homepage lists YZi Labs among investors. Its product navigation leads to Rango’s own public app and developer infrastructure. An investor name, an integrated liquidity venue and a corporate operator are different relationships; none is used here to merge Rango with another exchange profile.[1]
- Operator
- Rango Exchange brand; incorporated operator not established
- Exchange model
- Decentralised
- Service scope
- Same-chain and cross-chain spot routing through a public app, APIs, SDK and widget.
- Client types
- Retail clients; Institutional clients
- Pricing publication
- Public and quoted pricing
- Other names
- Rango Exchange
- Pricing scope
- Direct-app fee claim differs from API and affiliate monetisation; underlying routes also charge.
- Funding scope
- Source-wallet tokens and route-specific gas; outputs or refunds reach the designated chain.
- Custody and asset handling
- Wallet-controlled routing; bridges and settlement contracts introduce separate execution exposure.
- Client eligibility
- Adults; US, sanctions and other territorial exclusions apply.
- Support
- Discord tickets, transaction explorer and dedicated general, security and legal contacts.
- Authorisation and registration scope
- No entity-specific financial permission established.
Exchange metadata checked 21 Oct 2026Source 1Source 23Source 2Source 4
Developer access, automation and referral economics
Sections ↑API keys identify an integration and carry rate limits by key and IP address. Rango directs production applicants to a Discord ticket describing the application, intended chains and domain. The public test key is expressly unsuitable for production, while dedicated endpoints can be arranged for enterprise users. Access limits are separate from the transaction fees described earlier.[10]
What an integration can and cannot establish
| Function | Documented reach | Authority boundary |
|---|---|---|
| Quote and route selection | Choose source/destination assets, amount, slippage and allowed swappers. | The returned quote is preparatory data.Source 13 |
| Transaction construction | Return final transaction data, including contract-routing options. | Review sender, recipient and the actual transaction to be signed.Source 14 |
| Failure reporting | Send an optional error or cancellation event to Rango. | It does not cancel an on-chain transfer.Source 19 |
The mobile integration page says JavaScript SDKs and APIs are currently supplied, with native Android, iOS and other frameworks available for discussion with the team. That wording does not establish a separately maintained Rango mobile SDK in every listed language or a standalone retail mobile app. Browser and wallet compatibility remain application-specific.[21]
The homepage places gasless intents, AI-assisted execution and a wider action layer within its vision section. Those statements are not used here to assert a currently available autonomous investment mandate. The inspected execution instructions establish wallet-authorised routes, not a right for an AI assistant to sign from a user’s wallet.[1]
Affiliate earnings are transaction-based. The monetisation guide describes direct settlement on supported routes and an older monthly model now largely deprecated except for special enterprise cases. Where monthly settlement is retained, it describes a payout threshold exceeding US$10. An advertised referral opportunity is not withdrawable account credit before its route, amount and settlement conditions are met.[5]
Sources & further reading
- Rango service and reach Rango · Accessed 21 Oct 2026
- Routing architecture overview Rango · Accessed 21 Oct 2026
- Assets and routing FAQ Rango · Accessed 21 Oct 2026
- Fee structure Rango · Accessed 21 Oct 2026
- Affiliate monetisation Rango · Accessed 21 Oct 2026
- Gas estimates Rango · Accessed 21 Oct 2026
- Security controls Rango · Accessed 21 Oct 2026
- Vulnerability reporting Rango · Accessed 21 Oct 2026
- Contract audit reports Rango · Accessed 21 Oct 2026
- API access and rate limits Rango · Accessed 21 Oct 2026
- API model comparison Rango · Accessed 21 Oct 2026
- Routing and API errors Rango · Accessed 21 Oct 2026
- Quote parameters Rango · Accessed 21 Oct 2026
- Transaction construction Rango · Accessed 21 Oct 2026
- Swap status and recovery Rango · Accessed 21 Oct 2026
- Transaction prerequisites Rango · Accessed 21 Oct 2026
- Basic API execution flow Rango · Accessed 21 Oct 2026
- Multi-step API execution flow Rango · Accessed 21 Oct 2026
- Failure reporting Rango · Accessed 21 Oct 2026
- Settlement contract architecture Rango · Accessed 21 Oct 2026
- Mobile integration availability Rango · Accessed 21 Oct 2026
- Support and legal contacts Rango · Accessed 21 Oct 2026
- Terms of use Rango · 7 May 2025 · Accessed 21 Oct 2026
- Privacy policy Rango · 10 Aug 2023 · Accessed 21 Oct 2026
- Binance Labs investment in Rango Binance · 19 Jun 2024 · Accessed 21 Oct 2026
- Rango activity metrics DefiLlama · Accessed 21 Oct 2026
This profile reports dated public information, including exchange-published services and terms. It does not independently test or guarantee trading, custody, pricing or withdrawals. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.
Report an error or submit an update