Soroswap combines a Stellar swap interface, its own AMM and an aggregation API. Current documentation lists four Soroban venues plus the classic Stellar DEX, with a 0.10% protocol fee for non-partner swaps or an alternative partner fee. These execution paths have different requirements: a classic SDEX path payment cannot be combined with Soroban contract hops in one quoted route.[1][2][4]
Markets & services
Sections ↑Reference table01
Services and execution paths
| Item | Published terms |
|---|---|
| Retail app | Wallet-authorised token swapsSource 1Source 4Source 6 |
| Soroswap AMM | Constant-product liquidity sourceSource 1Source 4Source 6 |
| Aggregation | Compares supported venues and constructs transactionsSource 1Source 4Source 6 |
| SDEX route | Classic path payment, separate from Soroban contract executionSource 1Source 4Source 6 |
Reference table02
Current listed venues
| Item | Published terms |
|---|---|
| Soroswap | Constant-product AMMSource 4Source 6 |
| Aquarius | Multiple pool designs, including stable and concentrated liquiditySource 4Source 6 |
| SushiSwap V3 | Concentrated-liquidity poolsSource 4Source 6 |
| Comet | Weighted poolsSource 4Source 6 |
| SDEX | Classic Stellar order books and liquidity pools; opt-inSource 4Source 6 |
Reference table03
Route selection
| Item | Published terms |
|---|---|
| Exact input | API selects the higher output from available quoted pathsSource 6 |
| Exact output | API selects the lower input requirementSource 6 |
| SDEX versus Soroban | One returned quote uses one execution familySource 6 |
| Contract-only assets | Cannot trade through classic SDEX without a corresponding classic assetSource 6 |
Reference table04
Aggregator v3 transition
| Item | Published terms |
|---|---|
| Current contract family | Typed routes across supported Soroban venuesSource 7 |
| Legacy retirement | API stopped quoting/sending against the previous aggregator on 24 September 2026Source 7 |
| Minimum received | v3 reverts if actual output misses the required boundSource 7 |
| Exact-output mode | Unspent input is returned; recipient is the authorising userSource 7 |
Fees & commercial terms
Sections ↑Reference table05
Swap service rates
Reference table06
Fee calculation and disclosure
| Item | Published terms |
|---|---|
| Collection | Input token before routingSource 2Source 7 |
| Net quote | Quoted output already accounts for the swap service feeSource 2Source 7 |
| Pool example | Soroswap AMM fee is 0.30%; other venues can differSource 2Source 7 |
| Direct contract ceiling | 1,000 bps is a contract bound, not the API’s 300-bp maximumSource 2Source 7 |
Reference table07
Illustrative service-fee comparison
Reference table08
API subscription plans
Reference table09
Partner and API commercial terms
| Item | Published terms |
|---|---|
| Partner split | Standard documentation specifies 50/50 fee sharingSource 2Source 3 |
| Plan inclusion | Signed partner integration includes Starter accessSource 2Source 3 |
| Activation | Paid plans are requested from the team; self-service billing is not yet described as liveSource 2Source 3 |
| Rate limits | Excess requests return 429; observe the retry instructionSource 2Source 3 |
Deposits, withdrawals & settlement
Sections ↑Reference table10
Wallet and transaction format
| Item | Published terms |
|---|---|
| Classic account | G-address can sign SDEX path paymentsSource 6Source 1 |
| Smart-contract wallet | C-address cannot execute a classic path payment within its contract callSource 6Source 1 |
| API behaviour | SDEX is dropped for contract-address transactionsSource 6Source 1 |
| Funding asset | Supported wallet-held input token; no general fiat deposit account is describedSource 6Source 1 |
Reference table11
Gasless trustline economics
| Item | Published terms |
|---|---|
| Eligibility | First acquisition of an asset when the output trustline is absentSource 5 |
| Reserve | Sponsor fronts approximately 0.5 XLMSource 5 |
| Repayment | Swap buys XLM to reimburse the sponsor in the same transactionSource 5 |
| User output | Reduced by that repayment costSource 5 |
Reference table12
Gasless trustline constraints
Reference table13
What sponsorship changes
| Item | Published terms |
|---|---|
| User’s starting balance | Can avoid needing XLM in advance for this flowSource 5 |
| Quote disclosure | Shows reserve cost in input and output asset unitsSource 5 |
| Atomic flow | Trustline, swap and repayment are assembled togetherSource 5 |
| Economic meaning | Reserve reimbursement remains a cost to the userSource 5 |
Custody & asset handling
Sections ↑Reference table14
Asset handling
| Item | Published terms |
|---|---|
| App terms | State that custodial services are not providedSource 1Source 4 |
| Swap | Contracts or path-payment operations transfer the authorised assetsSource 1Source 4 |
| Liquidity provision | Deposits create pool exposure and a claim on pooled assetsSource 1Source 4 |
| Issuer assets | Redemption and transfer controls depend on the particular assetSource 1Source 4 |
Reference table15
Contract and upgrade controls
| Item | Published terms |
|---|---|
| v3 administration | Documented admin can pause swaps and change fee configurationSource 7Source 9 |
| Token/venue upgrades | Can alter code invoked by a transactionSource 7Source 9 |
| Signature scope | Nested authorisations deserve attention, not only displayed outputSource 7Source 9 |
| Slippage protection | Does not by itself prevent a malicious authorised subcontract actionSource 7Source 9 |
Reference table16
Audit evidence
| Item | Published terms |
|---|---|
| Project statement | Says aggregator contracts were reviewed by Runtime VerificationSource 8Source 9 |
| Available link | Documentation links an audit reportSource 8Source 9 |
| Version boundary | The statement alone does not prove coverage of every current v3 componentSource 8Source 9 |
| Residual exposure | Audits do not eliminate upgrade, issuer or token risksSource 8Source 9 |
Client eligibility & restrictions
Sections ↑Reference table17
User conditions
| Item | Published terms |
|---|---|
| Age | 18 or the applicable local age of majoritySource 1Source 2 |
| Legal access | User must comply with applicable laws and sanctions restrictionsSource 1Source 2 |
| Wallet authorisation | Transactions require the appropriate signing authoritySource 1Source 2 |
| API partnership | Commercial partner configuration is separate from wallet accessSource 1Source 2 |
Support & contacts
Sections ↑Reference table18
Published support information
| Item | Published terms |
|---|---|
| API/partner contact | [email protected]Source 2Source 3Source 6Source 1 |
| Fee identification | Partner ID and configured rate should match the quote and executionSource 2Source 3Source 6Source 1 |
| Troubleshooting | Transaction hash, route platform and wallet type distinguish failuresSource 2Source 3Source 6Source 1 |
| Settlement | Support access does not make an executed blockchain transfer reversibleSource 2Source 3Source 6Source 1 |
Authorisations & registrations
Sections ↑Reference table19
Regulatory and protection boundaries
| Item | Published terms |
|---|---|
| Interface disclosure | No specific exchange licence is identified in the inspected user termsSource 1 |
| Protocol access | Does not establish permission to offer every token in every countrySource 1 |
| Asset claims | A token issuer or anchor’s obligations remain separateSource 1 |
| Protection | No deposit-insurance or investor-compensation arrangement is established by the cited materialsSource 1 |
Operator & entity scope
Sections ↑Reference table20
Identity and responsibilities
| Item | Published terms |
|---|---|
| Public brand | SoroswapSource 1Source 2Source 6Source 5 |
| Commercial developer contact | API documentation uses the paltalabs.io domainSource 1Source 2Source 6Source 5 |
| Legal company | Full contracting-company identity is absent from the inspected app termsSource 1Source 2Source 6Source 5 |
| Execution participants | User, app, selected venues, token issuers and any sponsor have different rolesSource 1Source 2Source 6Source 5 |
- Operator
- Soroswap interface and protocol; a full contracting company name is not specified in the inspected user terms
- Exchange model
- Decentralised
- Service scope
- Stellar swap interface, Soroswap AMM and aggregation API covering Soroswap, Aquarius, SushiSwap V3, Comet and opt-in SDEX routes. Soroban routes and classic SDEX path payments execute separately.
- Client types
- Retail clients; Professional clients
- Pricing publication
- Public pricing
- Other names
- Soroswap DEX; Soroswap AMM; Soroswap Aggregator
- Headquarters
- Contracting company and incorporation jurisdiction not established from the inspected app terms
- Covered jurisdictions
- Stellar services; user terms and applicable restrictions apply
- Pricing scope
- Current non-partner protocol fee is 10 bps (0.10%). API partner rates of 25–300 bps replace that fee, rather than adding to it. Pool, network and sponsored trustline costs can be additional; API subscriptions have separate published prices.
- Funding scope
- Wallet-held Stellar or Soroban assets fund trades. Gasless trustline sponsorship is SDEX-only and repaid from the same swap; it is not a free reserve grant.
- Custody and asset handling
- User-authorised contract swaps or classic path payments. The app terms disclaim custody; liquidity deposits and execution involve contracts and issuer assets. Upgrade and authorisation risks can exceed an ordinary slippage bound.
- Client eligibility
- User terms require 18 or the local age of majority, applicable-law compliance and no prohibited sanctioned use. Partner/API onboarding and wallet type affect technical access.
- Support
- Developer and partner requests: [email protected], as published in the API documentation. The app terms and project documentation provide product guidance.
- Authorisation and registration scope
- The inspected terms do not identify a specific financial-services authorisation or compensation arrangement. Stellar infrastructure and API access do not establish a regulated custodial exchange relationship.
Exchange metadata checked 27 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9
Additional Information
Sections ↑Current supported-venue documentation lists five sources, including SDEX. The v3 type definitions still contain a Phoenix hop, but that code reference does not establish current API routing support. The public venue list and returned quote are the more useful descriptions of what a specific trade can use.[4][7][6]
Sources & further reading
- Soroswap user terms and noncustody representation Soroswap · Accessed 27 Oct 2026
- Soroswap current swap fees and partner revenue sharing Soroswap · Accessed 27 Oct 2026
- Soroswap API plans and request limits Soroswap · Accessed 27 Oct 2026
- Soroswap supported liquidity venues Soroswap · Accessed 27 Oct 2026
- Soroswap gasless trustline reserve repayment Soroswap · Accessed 27 Oct 2026
- Soroswap classic SDEX routing and execution Soroswap · Accessed 27 Oct 2026
- Soroswap Aggregator v3: contracts, fees and legacy retirement Soroswap · Accessed 27 Oct 2026
- Soroswap published aggregator audit statement Soroswap · Accessed 27 Oct 2026
- Soroswap protocol and token-upgrade risk disclosure Soroswap · Accessed 27 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.