Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Crypto ExchangesExchange profile

SyncSwap exchange profile

SyncSwap combines four pool models for wallet-based spot trading. The profile explains route-dependent fees, version-specific custody and LP exits, network coverage, contract controls and the limits of its published audit and token claims.

By Editorial deskOperating status: ActivePublished Sources checked

Spot swaps, pool models and trade controls

Sections ↑

SyncSwap routes wallet-funded token swaps through several automated pool designs. A trader chooses the assets and execution limits; a liquidity provider commits capital to a pool and receives a claim on its assets. Its published network coverage includes ZKsync Era, Linea, Scroll, Sophon and Creator Chain. Pool availability and contract versions must be checked within the chosen network.[1]

DefiLlama’s combined SyncSwap Protocol page, captured on 21 October 2026, displayed approximately US$8.93 million of rolling 30-day spot volume, US$2.51 million over seven days and US$159,090 over 24 hours. The combined parent includes the legacy and V3 components. These are token-swap values, not registered customers or unique active people; they do not establish a worldwide exchange rank.[28]

Reference table01

Four liquidity models

Four liquidity models
ModelHow liquidity is usedPractical distinction
ClassicConstant-product, two-token pools, conventionally balanced by value.Broad pair support; execution changes with reserves.Source 3
StableA hybrid curve concentrates liquidity near the relationship between pegged assets.Efficient near the intended peg; a depeg remains an economic risk.Source 3
AquaA Curve V2-derived design adjusts its liquidity concentration and pricing parameters.Automated rebalancing differs from manually selecting a fixed range.Source 4
Range / V3Liquidity providers select price ranges.Capital exposure depends on the selected bounds and subsequent price movement.Source 5

The router can combine pool models, use intermediate tokens and split one trade across different paths. Multiple Hops and Path Splits are separately configurable. A route therefore need not be a single direct pool exchange. Disabling a routing feature changes the paths considered; it does not guarantee a better final price or deeper liquidity.[7]

Reference table02

Before approving a swap

Before approving a swap
Display or controlMeaning
Quoted outputThe estimated token amount includes trading fees; it depends on the pool state used for the quote.
Price impactThe effect of the proposed trade on its achievable price. It differs from later market movement.
Slippage / minimum receivedSets the minimum acceptable output. A swap that cannot satisfy it reverts rather than completing below that bound.
ExecutionAn estimate becomes a completed exchange only after successful network execution.

Pool fees, network costs and liquidity economics

Sections ↑

There is no single maker/taker tariff covering SyncSwap. Its fee system permits model defaults, individual-pool settings and different rates for opposite trading directions. The documentation’s maximum configurable fee is 10%; that is a configuration ceiling, not the normal charge. Project fee delegation and proposed token-holder discounts must be distinguished from the rate actually returned for a trade.[9]

Reference table03

Cost components

Cost components
ComponentHow it affects the transaction
Configured swap feeInspect the pool, direction and current route quote. A remembered rate from another pair is insufficient.Source 9
Liquidity entry or exitThe Fee Manager documentation describes charges when deposits or withdrawals change the pool balance. A balanced Stable withdrawal is treated differently from a conversion through one asset.Source 11
Network executionApproval, swap and liquidity-management transactions can require separate gas payments.Source 25
ZKsync PaymasterSupported ERC-20 assets, including documented USDC/USDT examples, can pay gas. Fully sponsored swaps apply only under the relevant campaign conditions.Source 12

For a transparent fee illustration, the liquidity guide uses a Classic rate of 0.10%, divided into 0.07% for liquidity providers and 0.03% for the protocol. Applied hypothetically to US$20,000 of compatible fee-base value, those components are US$20, US$14 and US$6. This is the guide’s example structure, not a verified universal current pool rate; price impact, gas and asset-price changes are excluded.[10]

Suppose a fee-inclusive quote returns 1,000 USDC and the chosen slippage tolerance is 0.5%. The corresponding minimum is 995 USDC. That five-USDC allowance is an execution boundary, not an extra fee automatically charged. A tighter bound can cause a revert; a reverted transaction can still consume gas.[8]

Aqua fees can respond to pool imbalance through minimum, maximum and gamma parameters. Integrators must use the current fee-data interface for Aqua rather than assume an older single-rate query describes the entire fee calculation. The integration guide also warns that the Fee Manager address can change: obtain it from the relevant Pool Master.[4]

Wallet funding, liquidity withdrawals and bridges

Sections ↑

A swap spends assets from the signing wallet through the selected contracts. Token approval and trade execution are distinct authorisations; the published router also supports permit-based approval. Confirm the spender, token, amount, recipient and network. A wallet connection by itself is not authority to spend a balance, while a previously granted allowance can remain after the browser closes.[25]

Reference table04

Liquidity entry and exit

Liquidity entry and exit
PositionDocumented processWhat can change
Classic LP tokensMint LP tokens when adding liquidity; burn them to redeem the underlying pair.The redemption is a pool share, not repayment of the original quantities.Source 13
Classic single-asset exitburnSingle converts the other withdrawal component into the selected asset.The embedded swap adds pricing and fee exposure.Source 13
Aqua LP tokensThe pool exposes proportional burn and single-token burnSingle exits.Pool state, rebalancing and the chosen withdrawal mode affect the result.Source 14
Range positionThe Portfolio provides remove/rebalance controls for Range positions; deployments identify a Position NFT Manager.Check the position and displayed assets. A full current Range-specific exit walkthrough was not established.Source 23Source 6

For example, a hypothetical 1% pro-rata claim on a Classic pool holding 100 ETH and 200,000 USDC corresponds to 1 ETH and 2,000 USDC before applicable fees and rounding. If trading changes the reserves, the same percentage produces different quantities. Choosing a single-token exit then adds a conversion; it does not preserve the original two-asset example.[13]

The Vault reference concerns the older shared-vault design. It records ETH and WETH against a common balance, unwraps incoming WETH and can return native ETH or wrapped WETH according to the withdrawal mode. This internal bookkeeping is not a bank balance. Later deployments expressly omit the V1 vault, so its instructions should not be applied indiscriminately to V2, V2.1 or V3 positions.[15]

SyncSwap Move is documented as an Ethereum–ZKsync ERC-20 bridge, with additional bridge providers linked separately. Bridging into a network and swapping within it are different operations. An Ethereum withdrawal can require a claim step; check the source transfer, destination asset and final claim status. A listed third-party bridge has its own execution, liquidity and recovery conditions.[16]

Contract custody, administration and audit scope

Sections ↑
Reference table05

Where control sits

Where control sits
LayerRelevant control
V1 versus later poolsThe deployment page lists a V1 vault and expressly no vault for V2, V2.1 and V3.Source 6
Pool registryPool Master registers pools and restricts which factories can create them.Source 17
ConfigurationPool Master exposes changes to the Fee Manager, forwarder registry and factory whitelist. Decentralised execution does not mean every setting is fixed.Source 17
Aqua parametersThe reference exposes amplification/gamma ramping values and timing. Changing parameters can alter future pool behaviour.Source 14

The Aqua assessment explains that V2 moved assets from the shared vault into individual pool contracts. Retaining the wallet key therefore coexists with contract custody of committed liquidity. Recovery of a browser or wallet display does not itself redeem a position; an exit still needs a valid transaction against the relevant contract.[19]

Reference table06

Audits inspected

Audits inspected
ReportScope and limitation
Zellic, 4 May 2023Reviewed Classic Pool, Stable Pool and Vault at a specified repository commit. Router, front end, infrastructure and key custody were excluded. The report identified one low-impact finding.Source 18
Zellic, 26 January 2024Examined the Aqua port of Curve twoCrypto V2. It found one medium- and one low-impact issue, and stated that the underlying Curve mathematics and full differential testing were outside or incomplete within its scope.Source 19
Current security inventoryLists further V2/Aqua and other-product reviews. This inventory does not by itself establish that all current V3 deployments have been independently reviewed.Source 20

An audit evaluates defined code and assumptions; it does not establish a per-customer insurance limit or compensation fund. The inspected reports do not promise reimbursement following a wallet compromise, price loss or failure outside their reviewed scope.[18]

Eligibility and territorial restrictions

Sections ↑

The website terms require legal contractual capacity, no previous service suspension and lawful use in the user’s residence. They exclude Bosnia and Herzegovina, Burundi, China, DR Congo, Cuba, Ethiopia, Guinea, Guinea-Bissau, Iraq, North Korea, Libya, Mali, Nicaragua, Niger, Somalia, South Sudan, Sudan and Syria, plus specified OFAC-sanctioned jurisdictions. Representatives must have authority for an entity they use the service for.[21]

Support, unfinished transactions and records

Sections ↑

The Community page links the official Discord entry point through syncswap.xyz/discord. That is an assistance route, not evidence of a telephone dealing desk, fixed response time or power to undo a confirmed transaction. For an unresolved operation, retain the chain, public wallet address and transaction hash; distinguish an unsigned request, pending transaction and confirmed failure before repeating it.[22]

Portfolio tracks token holdings, price trends and active positions across Classic, Stable, Aqua and Range pools, with links to DeBank and Zerion. This can help locate a position but is not an independently verified tax statement. Keep transaction hashes, input/output quantities, gas and LP changes across the relevant chains. A native consolidated tax certificate or complete CSV export was not established from the inspected dashboard documentation.[23]

The terms assign tax determination to users and permit partial or complete website suspension without notice. They provide individual JAMS arbitration, with intellectual-property exceptions.[21]

Legal counterparty and financial permission scope

Sections ↑

The agreement names SyncSwap Labs, called the Foundation, without establishing an incorporation jurisdiction or entity-specific financial permission. A protocol contract address cannot resolve that legal-entity gap.[21]

Technical modularity explains how the service operates, rather than who carries a regulated customer obligation. The exchange overview separates pool models and replaceable components; it does not supply a financial licence or an insured cash account.[2]

Protocol versions and deployment continuity

Sections ↑

V1 launched on ZKsync Era in 2023. The integration documentation describes later V2/V2.1 changes, including Aqua and protection against read-only reentrancy. It specifically warns against using V1 pools as price oracles. That limitation matters for applications building on pool prices; an available swap route does not establish suitability as collateral-pricing infrastructure.[4]

Reference table07

Version distinctions in the current deployment register

Version distinctions in the current deployment register
NetworkDocumented scope
ZKsync EraV1, V2/V2.1 and V3 components; the V3 router can route earlier pool versions.
Linea and ScrollV1 and later router/Aqua components are listed; do not assume complete V3 parity.
Sophon and Creator ChainV2.1 and V3 components, including Range factories and Position NFT Managers.

The 1 January 2025 V3 announcement introduced Range pools, initially on ZKsync. It was an extension of SyncSwap’s pool family, not a separate exchange operator. Its prospective token and incentive statements are historical plans; current token status needs separate evidence.[5]

Operator
SyncSwap Labs; incorporation jurisdiction not established by the linked terms.
Exchange model
Decentralised
Service scope
Wallet-based spot swaps and liquidity provision across Classic, Stable, Aqua and Range pools; deployment varies by network.
Client types
Retail clients
Pricing publication
Public pricing
Other names
SyncSwap Protocol; SyncSwap V3
Pricing scope
Pool and direction-dependent fees, price impact and network costs; the displayed route determines the actual quote.
Funding scope
Crypto assets on the selected network; bridges are separate transfers. ZKsync Paymaster can accept supported tokens for gas.
Custody and asset handling
Users retain wallet keys. Committed liquidity is held in protocol contracts; V1 vault accounting differs from later pool custody.
Client eligibility
Legal capacity and lawful residence are required; the website terms exclude specified jurisdictions and sanctioned locations.
Support
Official Discord and documentation; a staffed emergency execution service was not established.
Authorisation and registration scope
The linked terms identify SyncSwap Labs but establish no entity-specific financial permission or customer compensation entitlement.

Exchange metadata checked 21 Oct 2026Source 1Source 4Source 6Source 9Source 12Source 22Source 21

Developer access, token plans and reward displays

Sections ↑
Reference table08

Programmatic responsibilities

Programmatic responsibilities
TaskPublished integration method
Find candidate poolsQuery the applicable Pool Master for the token pair and pool type. Different protocol versions need separate discovery.
Read executable inputsObtain reserves, amplification and current fee information before applying the pool’s own pricing algorithm.
Produce a quoteAn output calculation describes a particular state and amount; it does not sign or execute a transaction.

The published router code checks deadlines and minimum output and offers permit-based authorisation. These are concrete controls in that code; integrations must verify the deployed version rather than copy an address from an old example. Keeping a bot online is not the same as maintaining valid balances, approvals and transaction parameters.[25]

The SYNC token documentation still says the token has not been created and its contract address is to be announced. A proposed supply or future staking utility is therefore not an established tradable token, current fee discount or redemption promise. No active staking service is included in this profile’s structured service list on that evidence.[26]

The loyalty documentation describes non-transferable ySYNC accounting, with eligible fees contributing to an epoch reward share. The displayed points are not a withdrawable dollar balance or a guaranteed one-for-one token entitlement. Reward availability, epoch eligibility and any claim must be verified in the current programme; historical genesis and projected veSYNC descriptions do not establish a funded October 2026 payout.[27]

Follow the evidence

Sources & further reading

  1. About SyncSwap SyncSwap · Accessed 21 Oct 2026
  2. Exchange architecture SyncSwap · Accessed 21 Oct 2026
  3. Classic and Stable pools SyncSwap · Accessed 21 Oct 2026
  4. Protocol integration introduction SyncSwap · Accessed 21 Oct 2026
  5. SyncSwap V3 launch SyncSwap · 1 Jan 2025 · Accessed 21 Oct 2026
  6. Mainnet contract deployments SyncSwap · Accessed 21 Oct 2026
  7. Smart routing SyncSwap · Accessed 21 Oct 2026
  8. Trading controls SyncSwap · Accessed 21 Oct 2026
  9. Dynamic fee configuration SyncSwap · Accessed 21 Oct 2026
  10. Providing liquidity SyncSwap · Accessed 21 Oct 2026
  11. Fee Manager overview SyncSwap · Accessed 21 Oct 2026
  12. Paymaster SyncSwap · Accessed 21 Oct 2026
  13. Classic pool contract SyncSwap · Accessed 21 Oct 2026
  14. Aqua pool contract SyncSwap · Accessed 21 Oct 2026
  15. Legacy Vault reference SyncSwap · Accessed 21 Oct 2026
  16. Token bridge SyncSwap · Accessed 21 Oct 2026
  17. Pool Master SyncSwap · Accessed 21 Oct 2026
  18. Zellic SyncSwap assessment Zellic · 4 May 2023 · Accessed 21 Oct 2026
  19. Zellic Aqua assessment Zellic · 26 Jan 2024 · Accessed 21 Oct 2026
  20. Security references SyncSwap · Accessed 21 Oct 2026
  21. Website terms SyncSwap · Accessed 21 Oct 2026
  22. Official community routes SyncSwap · Accessed 21 Oct 2026
  23. Portfolio dashboard SyncSwap · Accessed 21 Oct 2026
  24. Calculating a route SyncSwap · Accessed 21 Oct 2026
  25. Published router contract SyncSwap · Accessed 21 Oct 2026
  26. SYNC token documentation SyncSwap · Accessed 21 Oct 2026
  27. Loyalty programme SyncSwap · Accessed 21 Oct 2026
  28. Combined protocol 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