How SyncSwap Swap Incentives Reward Activity

SyncSwap swap incentives reward eligible activity by attaching a reward hook to a swap and allocating points or tokens according to the fees that swap generates. The wallet is already connected, the ETH-to-USDC quote is on screen, and the important question is not whether a trade earns something, but whether its reward is worth the fee, slippage, and gas it consumes.

SyncSwap is a decentralized exchange on the zkSync Era network whose incentive system turns qualifying swap activity into a measurable loyalty balance. That matters when you already need to exchange supported assets: the reward can improve the trade's effective economics, but it is not a reason to manufacture volume. Trading fees, price impact, network gas, and the uncertain value or vesting conditions of the reward remain real costs.

The practical route starts on Syncswap, where the active pool and reward status are checked before the swap is submitted.

What SyncSwap actually measures

SyncSwap's documented loyalty model measures fees generated rather than treating every dollar of notional volume as identical. That distinction matters because pools can use different fee tiers, and SyncSwap supports dynamic fees. A trade in a higher-fee pool may generate more ySYNC than the same-sized trade in a lower-fee pool, even when both swaps have the same dollar value.

The protocol uses a hook mechanism in its smart-contract architecture. In practical terms, the swap reaches the pool and router, the fee is calculated, and the incentive logic records or mints the reward for an eligible trade. This is implemented through Solidity Programming Language contracts, so the reward is attached to defined on-chain conditions rather than awarded by a manual spreadsheet.

The usual loyalty unit is ySYNC, a non-transferable balance used to determine a participant's share of an epoch's reward. It is not a dollar balance and cannot simply be sold like an ERC-20 token. Under the documented model, the final reward is calculated roughly as follows: your eligible ySYNC for the epoch divided by the total eligible ySYNC for that epoch, multiplied by the epoch's reward allocation.

For illustration, a $10,000 swap through a pool charging 0.3% in fees would generate $30 of fee-based activity and therefore 30 ySYNC under the published example. That does not mean the trader receives $30 of SYNC. Other participants dilute the share, the epoch allocation can change, and the eventual reward is distributed according to the program's rules.

One eligible swap from start to finish

1. Fund the wallet. Use a wallet connected to zkSync Era and hold both the asset being sold and enough ETH for network gas. A token balance alone is not enough if the wallet cannot pay for the transaction.
2. Check the active incentive. Open the Rewards or loyalty area before choosing a pair. Confirm that an epoch is active, note the eligible tokens and pools, and check whether the reward is claimable immediately or only after the epoch closes. Eligibility is a program setting, not a permanent property of every SyncSwap pool.
3. Choose the actual pool. Select a supported pair such as ETH and USDC only if that pool appears in the current eligible set. Review the pool fee, route, price impact, and minimum received amount. SyncSwap's router can use multiple pools or token hops, but the reward condition still depends on the qualifying swap and its configured assets.
4. Submit the swap. Enter the amount, approve the token if required, inspect the final quote, and confirm the transaction. The ordinary swap fee is taken through the trade; the incentive does not make that fee disappear.
5. Verify the result. After confirmation, return to the rewards display and check the epoch balance. The balance should reflect the eligible fee activity, while the estimated final reward can move down as other traders add ySYNC to the same epoch.

What it works with—and what it will not take

The incentive works with the token pairs and pools explicitly enabled for the current program. SyncSwap supports ERC-20 assets on zkSync Era, and its documentation treats ETH and wrapped ETH as interchangeable for the relevant liquidity pool. It does not follow that every token listed on the exchange qualifies. A pool containing one eligible token and one unapproved token can still be excluded, as can an otherwise familiar pair outside the selected pool.

The reward is also not automatically attached to liquidity deposits, withdrawals, transfers, or arbitrary contract calls. Those are different actions with different accounting. ySYNC itself is not a tradable token, and an offer to buy or transfer it is a warning sign.

When the incentive is worth using

The sensible comparison is between the trade you already need and the same trade elsewhere. SyncSwap becomes more compelling when its route has acceptable price impact, the network cost is small, and the eligible reward adds value without forcing an expensive or unnecessary transaction. Curve Finance is a useful comparison for the incentive design: both systems make users think about fee generation, pool selection, and governance-linked rewards, but SyncSwap's trade reward is specific to the pools and epochs configured by SyncSwap.

The main limit is dilution. More activity can increase the program's total ySYNC supply while leaving your own balance unchanged, reducing your share of the final allocation. The original Genesis Epoch was a bounded launch campaign, not a permanent promise. Treat the current Rewards screen and active program rules as the authority, and calculate the ordinary swap cost before counting any incentive.

FAQ

Does larger trading volume always produce a larger reward?

Not necessarily. Larger volume usually creates more fee-based activity, but the relevant result depends on the pool's fee tier, eligibility, the epoch's total supply, and the number of competing participants.

Is ySYNC the same as SYNC?

No. ySYNC is a non-transferable loyalty accounting unit. It determines a share of the configured reward, while the final distribution and any conversion or vesting conditions follow the active program's rules.