SUN / SunSwap exchange profile

Universal Router can combine V1, V2, V3, V4, SunCurve and PSM operations. Its command structure supports route composition, wrapping and unwrapping TRX, and conditional partial execution. Minimum outputs, permitted partial fills and handling of leftover assets therefore belong in the complete transaction review. The documentation describes this router as ownerless and non-upgradeable; that statement does not cover every pool, hook or SunX vault.[4]

A hook is attached when a V4 pool is created and cannot subsequently be replaced for that pool. Some hooks act automatically during swaps or liquidity changes; others use a separate authorization for a strategy or asset-management function. The platform permits outside developers to create hooks. A programmable limit-order or strategy capability should not be assumed to be an identical standard order offered by every pool or interface.[5]

Contract count must be converted using the contract’s face value before interpreting exposure or fees. These specifications are separate from the available collateral and current risk limit. A familiar ticker alone is insufficient to size an instruction correctly.[6]

SunX charges fees on executed notional in USDT on both opening and closing fills: contract count × face value × execution price × applicable rate. Placement alone does not reserve the fee. At the base public rates, a 10,000 USDT fill costs 1.50 USDT as maker or 4 USDT as taker. Another equally sized closing fill creates another charge; funding and price movement are separate.[7][8]

SunX also documents an approximately 100-millisecond additional matching delay for taker orders; makers and cancellations do not receive this extra delay. Market conditions can change before matching, including partial or unfilled results. An automated retry needs reconciliation with the original order to avoid unintended duplicate execution.[7]

Funding is exchanged between perpetual holders present at the settlement timestamp. The documented basis is position size × index price × funding rate. Opening and closing between settlements differs from carrying a position across one; the interval is not a borrowing-rate promise fixed for the lifetime of a trade.[9]

The formula effective 30 January 2026 normalizes the premium and interest component by 8/N, where N is the funding interval in hours from one to eight, before applying rate caps and floors. Intervals can change immediately. A switch from an eight-hour schedule to hourly settlement can bring the next payment forward, so both the displayed rate and next timestamp matter.[10]

For a SunSwap trade, choose the input token, output token and amount, review the quoted result and authorize the required transaction in the wallet. An initial token approval may be a separate action. A successful approval is not itself the swap. Wait for the actual trade confirmation and reconcile the resulting wallet balances before treating the conversion as complete.[11]

SunX documents a platform-wide withdrawal ceiling of $2 million per hour for all users combined. It is not a personal allowance. The deposit guide also requires native network assets for transaction costs and warns that unsupported tokens can be permanently lost. The inspected materials do not establish a SUN-operated bank deposit or bank withdrawal channel.[12]

The documented SunX API withdrawal workflow requires Withdraw permission, an address corresponding to the deposit address and an additional user signature over the returned content. Its nonce expires 120 seconds after issuance. The TRC-20 USDT request schema specifies a zero withdrawal fee, which should not be read as a promise that every network interaction costs nothing or that a request has already settled.[13]

Only in-range V4 liquidity earns current swap fees. Collected fees must be added back through another liquidity action if the owner wants to compound. Consider the network cost of repeated claims and the changing token mix when assessing a quoted annualized return. Merely leaving the website does not collect fees or terminate the position.[14]

Permit2 has two permission layers: the token’s underlying allowance to Permit2, and a signed authorization for a particular spender. AllowanceTransfer limits amount and duration; SignatureTransfer authorizes a one-time transfer. The documented workflow still relies on the initial token allowance. Expiry of an individual permit does not itself revoke that underlying approval, and disconnecting a website does not revoke either layer. Permit2 also supports batch revocation of spender allowances.[15]

These reports concern specific vault implementations, rather than a universal audit of the entire SUN brand. The TRON report’s operator and validator path means control cannot be described solely by who holds the login wallet’s private key. Current contract deployment, administrator ownership and recovery arrangements were not independently verified in this profile.[16]

SunX’s current margin guide describes cross margin and says isolated margin is temporarily unsupported. Positions share the account’s USDT equity. This lets one losing position consume collateral that also supports another; it is not a set of separately ring-fenced balances. Maximum leverage must be checked for the actual market and account conditions.[17]

The liquidation guide defines its margin ratio using maintenance margin relative to net position value, with liquidation at the stated 100% threshold. It says remaining margin after liquidation enters the insurance fund. That fund supports the platform’s liquidation and shortfall process; it is not a named customer insurance policy with a verified per-person insured limit.[18]

If the insurance fund is depleted or falls rapidly, SunX can automatically reduce positions on the profitable counterparty side. The ADL ranking combines profit and risk, and the resulting closure price can differ from current market execution. A trader can therefore lose an intended position through system deleveraging even without that position reaching its ordinary liquidation threshold.[19]

Linked terms assign wallet-key custody to the user; support key restoration is not established.[20]

Linked SUN terms exclude citizens, residents and organizations in Mainland China, Taiwan, Hong Kong, the United States and Singapore. Adulthood and sanctions rules also apply.[20]

SunX’s login guide uses a wallet signature to establish a session, without a spending authorization or gas fee. Browser extensions and compatible mobile connectors are described. Switching accounts requires selecting the wallet account and reconnecting. The guide does not establish identical device features, automatic synchronization of local preferences or a complete product-specific verification matrix. Connection does not verify eligibility.[21]

SunX describes a usual email response of one to two business days and around-the-clock community coverage. That is not a guaranteed complaint-resolution deadline. Staff should not request private keys or a transfer to verify an account. The inspected channels establish no emergency telephone dealing desk authorized to close a position during an outage.[22]

For that agreement, the 60-day informal dispute period starts with the notice email; binding Singapore arbitration under Singapore law follows.[20]

SunX’s Read-permission wallet-records endpoint retrieves deposit and withdrawal histories with status information, in pages of at most 50 rows. Pending, failed and completed requests must be reconciled with actual transfers rather than counted alike. These records do not by themselves establish a complete tax statement or complete trading-profit calculation.[23]

SUN’s OpenAPI exposes protocol, pool, wallet-position and transaction data through read-only requests. It ordinarily needs no authentication and has a documented 10-query-per-second limit; higher capacity requires an API key. Such data can support an export or reconciliation, but separate acquisition costs, off-platform transfers and any SunX derivatives activity must also be retained. Address-based activity metrics do not establish numbers of individual people.[24]

The agreement states no MAS registration. No exchange licence or customer compensation scheme was established.[20]

veSUN represents a time-weighted SUN lock used for incentives and voting. Its documented benefits are distributions, liquidity-mining boosts and pool-weight votes; those functions should not be interpreted as an equity ownership or bank-deposit claim.[25]

The current SunX app links the 4 January 2022 SUN agreement, which names the SUN team without identifying a corporate counterparty or expressly describing SunX. Product-specific contracting scope remains unestablished.[26][20]

Operator

Corporate contracting party not identified in linked agreement

Exchange model

Hybrid

Service scope

Pool trading and related SunX derivatives, with distinct custody models.

Client types

Not established

Pricing publication

Public and quoted pricing

Other names

SUN.io; SunSwap; SunX; SunPerp; JustSwap

Pricing scope

Public pool and tier schedules; dynamic routes, funding and eligibility vary.

Funding scope

Crypto transfers; documented SunX USDT deposit and wallet withdrawal.

Custody and asset handling

Wallet permissions, pool positions and operator-mediated derivatives vaults.

Client eligibility

Territory and sanctions restrictions in the linked SUN agreement.

Support

SUN notice email and separate SunX support channels.

Authorisation and registration scope

No service licence established in inspected materials.

Exchange metadata checked 20 Oct 2026Source 1Source 2Source 20Source 8

SUN can be locked for 26 weeks to four years. All of one user’s locks share an unlock date, which a later lock can extend. veSUN weight declines with remaining time. The documentation allocates half of weekly stablecoin-pool fees to veSUN holders as TUSD and describes a liquidity-mining boost of up to 2.5×. Locked principal, voting weight and claimed rewards are different balances; mining withdrawal instructions do not establish an early exit from the SUN lock.[25]

veSUN time decay and out-of-range fee eligibility are product conditions. The inspected materials do not establish a personal account-inactivity fee or deactivation clock.[25][14]

The SunX notice published 19 October 2026 changes its advertised staking split from 5% base plus 5% trading bonus to 4% plus 6%, effective 20 October at 00:00 UTC+8. The advertised combined ceiling remains 10%; the notice expressly leaves eligibility and distribution to the staking and campaign rules.[27]

In hedge mode, bonus above 60% of available balance can restrict opening against the net position direction; closing or reducing positions remains unaffected. One-way mode is excluded from that rule. Bonus-financed trading does not earn fee rebates, including negative-maker rebates.[28]

SunX API credentials distinguish Read, Trade and Withdraw authority, using HMAC-SHA256 or Ed25519 request authentication. A read key is not a trading or withdrawal grant. Signing timestamps have a documented five-minute validity window. Permission scope and any separately required wallet signature should be assessed together; an API login label alone does not define the asset authority.[29][23][30][13]

Its optional automatic order-cancellation timer requires Trade permission. The documented minimum and default are 5,000 milliseconds; the client must refresh it before expiry. Expiry cancels pending opening and closing orders, not existing positions. Ordinary browser disconnection does not itself enable this protection, and cancelling a protective closing order can leave its associated position open.[30]

SUN MCP offers read tools in cloud or local mode; asset-changing tools appear only in a local deployment with a configured wallet. Those tools can swap, manage V2/V3/V4 liquidity and send arbitrary contract calls. They can execute transactions rather than merely propose unsigned instructions. The documented defaults include mainnet and 5% slippage for V4 liquidity when omitted, so an assistant’s implicit defaults can affect real assets.[31]

SUN CLI uses agent-wallet or configured key material for write operations. It supports encrypted wallet storage, while a confirmation-bypass option can suppress the usual prompt. A local automation’s credentials and launch settings therefore determine whether a person reviews each transaction. Removing an AI integration from a device does not itself revoke on-chain permissions or withdraw a liquidity position.[32][15]