Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Crypto ExchangesExchange profile

SynFutures exchange profile

SynFutures runs Oyster perpetual markets and a separate tokenized-stock service. This profile explains execution, collateral exits, issuer restrictions and delegated trading authority.

By Editorial deskOperating status: ActivePublished Sources checked

Services and trading model

Sections ↑

SynFutures combines leveraged perpetual trading with a separate tokenized stock service. Its current site also promotes infrastructure for other trading venues. A market using SynFutures technology under another brand should not automatically be counted as a first-party SynFutures market or customer relationship. The profile below separates the perpetual contracts from the RWA cash, issuer and settlement arrangements.[1]

DefiLlama showed approximately $2.221 billion of perpetual notional traded over the preceding 30 days when checked on 20 October 2026. This measures leveraged contract turnover, not customer deposits, stock purchases or the number of people trading. The current series is predominantly Base activity; historical protocol totals can combine versions. No comparable current registered-user or active-person count was established.[39]

At a glance01

Two distinct trading arrangements

Two distinct trading arrangements
ServiceHow a trade reaches liquidityResult for the customer
PerpetualsOyster combines concentrated AMM ranges with resting limit liquidity; available limits at a price are consumed before the ranges.A margined derivative position, with funding and liquidation conditions.Source 3
Tokenized stocks and ETFsMarket makers obtain liquidity through the issuer relationship; this is a separate execution path from Oyster.An Anchored token exposure and associated cash or stock balance.Source 19

Oyster permits a market to use a single margin asset rather than requiring liquidity providers to supply two tokens. That simplifies the deposit composition, but it does not remove leverage or inventory risk. Exposure, margin and supported oracles belong to the selected pair; a parameter shown for one network or contract is not a platform-wide limit.[2]

At a glance02

Perpetual order mechanics

Perpetual order mechanics
InstructionExecution and continuing responsibility
Market tradeSet the maximum acceptable buy price or minimum sell price. The execution can include price impact and the pair’s trading charge; the requested size alone does not fix the final price.Source 4
Resting limitOrders sharing a price are allocated pro rata, rather than by arrival time. Price placement uses allowed tick increments. A taken order must be converted into a position; another address can perform that conversion for an execution payment without becoming its owner.Source 5
Take an order through to completionA taken limit cannot be cancelled merely because it still shows a Fill action. The documented remedy is to complete conversion; the resulting position then needs normal margin and exit management.Source 14

For RWA orders, regular-session market orders are supported from 9:30 a.m. to 4 p.m. Eastern Time. Limit orders can be submitted outside that interval and executed in supported overnight, pre-market, regular and after-hours sessions, broadly a 24/5 service subject to exchange holidays and early closures. Round-the-clock weekend execution remains a future objective. Availability must be checked for the particular symbol.[19]

Production RWA limit orders accept DAY validity only. Other time-in-force values revert on-chain. A transaction deadline is a separate validity condition, not a promise that an order will fill before that time. Cancellation is available for an open limit belonging to the relevant user and API key, with no cancellation already pending. A combined buy-and-deposit transaction also requires the cash deposit to qualify for instant processing.[30]

Trading charges and ongoing costs

Sections ↑
Pricing & charges03

Published Base perpetual examples

Published Base perpetual examples
ParameterBTC-USDC and ETH-USDC Chainlink pairsCommunity pairs
Initial / maintenance margin3% / 2%10% / 7.5%
Market trading charge0.05%0.10%
Maker rebate0%0.05%
Execution payment0.02 USDC0.0001 WETH
Minimum market / limit value166.66 / 333 USDC0.02 / 0.04 WETH
Pricing & charges04

Perpetual VIP schedule

Perpetual VIP schedule
Monthly qualifying taker volumeTaker chargeMaker charge / rebate
Below $1 million5 basis points0
$1 million or more4.5 basis points0
$10 million or more4 basis points0
$50 million or more3 basis points0.5 basis-point rebate
$150 million or more2 basis points1 basis-point rebate

Funding accrues for elapsed time, with a pair-defined interval that can be one, eight or 24 hours. An interaction updates the funding index, and payments are realised when the position changes, closes or its margin is adjusted. AMM range liquidity is excluded. The displayed paying-side rate is not necessarily the receiving-side rate per unit: unequal long and short open interest changes the amount distributed to receivers.[7]

The dynamic penalty documentation describes a price-deviation safeguard whose current configuration reverts a trade when the penalty condition is triggered. It should not be treated as an extra charge that always buys execution. A position can therefore remain open when an attempted close would move the market too far from the reference price.[11]

Pricing & charges05

Published RWA interface charges

Published RWA interface charges
OperationPublished charge
Cash deposit0 basis points
Cash withdrawal21 basis points
Stock purchase11 basis points
Stock sale1 basis point

For a hypothetical 1,000 mUSD cash withdrawal at the documented 0.9979 cash conversion rate, the payout is 997.90 USDC and the conversion deduction is 2.10 USDC. This illustrates the cash conversion alone: it assumes the balance is withdrawable and excludes stock trading costs, network charges and any settlement delay.[23]

Funding, cash balances and withdrawals

Sections ↑

Perpetual margin is collateral inside the relevant trading arrangement. Unrealised profit can support maintenance margin but cannot fund a new initial-margin requirement or be withdrawn as available cash. Opening losses require additional collateral. A large, highly leveraged position can also trigger a doubled initial-margin requirement. Margin removal remains constrained by initial margin and unrealised-profit exclusions, even when the headline account equity is positive.[6]

Specifications06

Position concentration can raise initial margin

Position concentration can raise initial margin
Published Base exampleOpen-interest thresholdPosition-value threshold
BTC-USDC50% of pair open interest$2 million
ETH-USDC50% of pair open interest$500,000
Default other pairs20% of pair open interest$100,000

The Base specifications separately allow throttling realised-profit withdrawals above 25,000 USDC for the two quoted major pairs, or 12.5 WETH for community pairs, with a published maximum wait of 24 hours. This is distinct from ordinary transaction confirmation and from RWA cash queuing. Community-pair delisting rules also allow a 24-hour Discord notice and settlement at the prevailing or fair price; a continuing wallet connection does not keep a delisted market open.[10]

At a glance07

RWA money and stock balances

RWA money and stock balances
Balance or stepWhere it sits and what happens next
Wallet USDC → mUSDThe user approves StockRouter; the cash token moves to Cashier. The service creates internal mUSD credit after instant or queued processing. Approval itself is not a deposit.Source 24
mUSD → stock exposuremUSD is non-transferable accounting credit. Bought stock is first credited to the Stock contract’s exchange balance, rather than automatically delivered to the external wallet.Source 22
Exchange stock → wallet stockStock withdrawal debits the exchange balance and transfers the token to the wallet. Depositing an existing wallet token is the reverse operation and requires the appropriate approval.Source 27
mUSD → wallet USDCA cash withdrawal consumes credit and requests delivery of the cash token. A recorded request can remain in processing before the cash reaches the wallet.Source 25

Instant cash settlement depends on current buffers. The published model permits an instant amount up to one fifth of the relevant buffer, subject to the other capacity conditions. A larger request takes the queued path. For a queued withdrawal, mUSD is deducted when requested while the cash arrives on settlement. Repeatedly submitting the same economic request is not a way to create buffer capacity. No universal completion deadline for that queue was established.[26]

The RWA production configuration identifies Base, Ethereum and Monad. Each network has its own cash token address and state, even where proxy addresses match. The documentation publishes a minimum cash amount of 90 units and example buffer settings; these are configuration values, not proof of immediately available liquidity for a particular withdrawal. A token existing on another issuer-supported chain does not by itself establish a SynFutures cash route there.[23]

Asset control, liquidity exposure and protection

Sections ↑

Perpetual liquidation can involve a third party taking over a position with its remaining margin or a forced AMM close. After the pair’s insurance fund is used, an uncovered deficit can be allocated to profitable positions on the opposite side. The insurance fund is part of loss settlement, not an individual insurance policy or a statutory deposit guarantee. Its presence does not establish that a profitable balance can never be reduced.[8]

Providing Oyster liquidity creates a changing net trading exposure. Removing a range, voluntarily or after it moves out of range, converts it into a position owned by the original provider. Closing that position is a separate step before the market exposure is fully exited. An out-of-range removal can be performed by another address for the execution payment. Narrow ranges concentrate exposure as well as fee opportunity; a range that has stopped supplying liquidity can still leave a position requiring margin.[9]

For RWA trading, wallet control does not describe the whole custody chain. Cashier holds deposited cash, Stock holds exchange stock balances, and a backend handles order execution and settlement asynchronously. The router is the transaction entry point and approved spender; it is not necessarily the final asset destination. A mined order transaction therefore does not prove that the stock trade has settled or that either balance has become withdrawable.[22]

SynFutures identifies Anchored as the tokenized-stock partner. The token gives economic exposure rather than direct legal share ownership, voting rights or shareholder reporting rights. Eligible dividend treatment is described as a USDC distribution, subject to the asset’s conditions. This product should be distinguished from a securities account in the holder’s own name at the underlying company’s transfer agent or broker.[21]

Anchored says the underlying shares are held through a licensed US broker-dealer and that Accountable checks the custody accounts against token supply, publishing reserve information on a 15-minute cycle. Those are the issuer’s stated backing and verification arrangements. They do not establish SynFutures customer insolvency priority, unrestricted redemption, or coverage of the trading interface by the broker’s regulatory permissions.[38]

Anchored stock tokens are ERC-20 assets and can be transferred on their deployed networks, but administrators can pause transfers in an emergency. During a pause, transfers, minting and redemption cannot occur. Having withdrawn a stock token to a personal wallet consequently removes the exchange-balance step without removing the issuer token’s control mechanisms.[37]

The SynFutures security index links a Quantstamp report for V3. An audit reference has a contract and version scope; that index does not establish that every later RWA component, issuer arrangement or deployment was reviewed in the same engagement. Neither audit publication nor visible on-chain positions establishes compensation for a contract failure.[12]

Eligibility and regional access

Sections ↑

SynFutures’ RWA FAQ names the United States, China and the Philippines as unavailable and presents that list as non-exhaustive. Its no-KYC description is an interface claim, not permission for every resident or investor to acquire the underlying issuer’s tokens.[20]

Anchored separately describes its products as intended for professional or qualified investors, with qualifying status assessed through KYC/KYB for onboarding. Its prohibited-person rules reach acquisition and redemption as well as direct subscription, and include citizenship, residence, location and certain controlled entities. The list includes Canada, mainland China, the United States, Russia, Belarus and several sanctioned or otherwise restricted jurisdictions. The complete issuer list and local investor category therefore matter even when a secondary interface does not ask for documents. The issuer may also reject inadequate verification or unsupported business activity.[36]

A complete current SynFutures interface contract could not be established from the terms route linked in the public application: it returned a Page Not Found body. That leaves the full perpetual-country rules, legal customer categories and contracting entity unresolved in the retrieved material. The RWA restrictions above should not be stretched into a complete perpetual eligibility list.[33]

Support, failed instructions and records

Sections ↑

Published contact routes

SynFutures community supportWebsite
https://discord.com/invite/synfuturesSource 17

Scope Official Discord route; no telephone dealing authority established.

Issuer eligibility questionsEmail
[email protected]Source 36

Scope Anchored product eligibility and onboarding.

For a perpetual close rejected because the market price deviates too far from the mark, the official troubleshooting guidance suggests a smaller staged close or waiting for the difference to narrow. Neither guarantees execution, and the position remains exposed. For missed transaction deadlines, it points to synchronising the device clock and reviewing the order deadline. A support message is not itself an order or a cancellation.[14]

For RWA operations, distinguish a transaction mapping, an open order and final history. An order marked placing or canceling is still in progress. Market orders may settle fully, partly with a refund, or without a fill. A cash operation marked processing is awaiting its settlement path; balances should be refreshed after settlement or closure. Closing the browser does not turn those pending states into completed withdrawals.[32]

RWA order records can include the transaction hash, order identifier, settlement transaction, execution price, actual payment and receipt, and mint or protocol fees. API access to an order depends on its mapping to the current key, so preserve the relevant identifiers as well as the wallet address. These records are useful for reconciliation; the inspected documentation did not establish a consolidated, jurisdiction-specific tax statement or a single export covering every SynFutures product.[31]

Operator and regulatory scope

Sections ↑

No entity-specific financial permission for the SynFutures interface was established from the retrieved legal route. The article therefore records no positive permission entry. This is a disclosure gap in the available interface evidence, not proof that all parties in its ecosystem share the same legal status or that a regulated upstream broker authorises every downstream token service.[33]

Anchored’s website distinguishes Anchored Labs Ltd as the technology website provider from Anchored Capital Ltd as the provider of products in its gated application. Those issuer-side identities do not identify the SynFutures interface operator. Investors need the actual product terms governing their token and route to assess redemption rights and claims; a brand partnership alone does not supply that contract.[35]

Brand, versions and service continuity

Sections ↑

The current SynFutures documentation lists V1 and V2 interfaces as legacy routes. Those labels identify earlier protocol versions, but do not establish an automatic transfer of positions, collateral or legal agreements into V3 or into RWA trading. An existing user should identify the original network and contract before treating a current dashboard balance as a complete record of earlier activity.[18]

Operator
SynFutures; legal interface operator not established in retrieved terms
Exchange model
Hybrid
Service scope
Oyster perpetual markets and RWA stock-token trading with distinct execution arrangements.
Client types
Not established
Pricing publication
Public pricing
Other names
SynFutures V3
Pricing scope
Pair-specific perpetual charges, funding, VIP rebates and separate RWA charges.
Funding scope
Network-specific crypto collateral and RWA USDC-to-mUSD cash operations.
Custody and asset handling
Perpetual collateral; RWA cash and stock contracts, plus issuer token controls.
Client eligibility
RWA interface restrictions and separate issuer eligibility apply; full perpetual-country terms remain unresolved.
Support
Official Discord and published operational documentation.
Authorisation and registration scope
No verified entity-specific financial permission for the interface established.

Exchange metadata checked 20 Oct 2026Source 3Source 22Source 1Source 33Source 39Source 19Source 2Source 21Source 20Source 8Source 24Source 13Source 4Source 17Source 12

Developer access, delegation and ecosystem products

Sections ↑

The perpetual data API is described as a beta service with access keys obtained by request through the official contact routes. It offers market, portfolio and funding information, with a documented IP rate limit of 1,200 requests per minute that can vary with endpoint or load. A data entitlement should not be mistaken for permission to move collateral or sign a trade.[15]

SynFutures publishes a V3 perpetual SDK and directs developers to its maintained code repository. Integrations still need to distinguish the selected chain, pair and signing wallet. The SDK link is an integration resource, not a managed account service, and it does not establish that a third-party bot or AI assistant can trade without the user’s separate transaction authority.[16]

At a glance08

RWA automation and account authority

RWA automation and account authority
LayerWhat the documentation permits
API keyREAD_ONLY keys allow GET requests; WRITABLE keys also permit the documented POST and DELETE operations. Keys are constrained by activation, expiry, product, chain and access scope. An empty IP whitelist rejects access.Source 28
One Click delegationA wallet signs typed authority bound to a chain, router, delegate, nonce and deadline. The documented router flows include order placement and cancellation and supported cash or stock operations, including withdrawals. This is meaningful execution authority.Source 29
Ending automationUse the documented disable or revocation flow and check pending operations separately. Removing an API connection is not evidence that a previously submitted on-chain instruction was cancelled or that a queued cash request has settled.Source 29Source 32

No independently defined AI advisory or copy-trading mandate was established in these API materials. The useful boundary is the authority actually signed: a service that can submit the documented One Click operations has a different role from a read-only analytics tool. Where credentials or devices change, the order and settlement records remain necessary to determine what was already authorised.[29]

The F staking page points to a separate foundation interface and describes ecosystem utilities. It does not publish enough current exit timing, reward entitlement and custody detail to treat staking as interchangeable with withdrawable trading cash. Token benefits, perpetual fee rebates, margin collateral and RWA mUSD are separate balances with different rules.[34]

Follow the evidence

Sources & further reading

  1. SynFutures platform SynFutures · Accessed 20 Oct 2026
  2. Perpetual trading overview SynFutures · Accessed 20 Oct 2026
  3. Oyster pricing SynFutures · Accessed 20 Oct 2026
  4. Market orders SynFutures · Accessed 20 Oct 2026
  5. Limit orders SynFutures · Accessed 20 Oct 2026
  6. Positions and margin SynFutures · Accessed 20 Oct 2026
  7. Perpetual funding SynFutures · Accessed 20 Oct 2026
  8. Liquidations SynFutures · Accessed 20 Oct 2026
  9. Perpetual liquidity provision SynFutures · Accessed 20 Oct 2026
  10. Base pair specifications SynFutures · Accessed 20 Oct 2026
  11. Dynamic penalty mechanism SynFutures · Accessed 20 Oct 2026
  12. Security audit index SynFutures · Accessed 20 Oct 2026
  13. VIP fee tiers SynFutures · Accessed 20 Oct 2026
  14. Perpetual trading questions SynFutures · Accessed 20 Oct 2026
  15. Perpetual data API SynFutures · Accessed 20 Oct 2026
  16. Perpetual SDK SynFutures · Accessed 20 Oct 2026
  17. Official contacts SynFutures · Accessed 20 Oct 2026
  18. Legacy interfaces SynFutures · Accessed 20 Oct 2026
  19. How RWA trading works SynFutures · Accessed 20 Oct 2026
  20. RWA questions and fees SynFutures · Accessed 20 Oct 2026
  21. RWA partners SynFutures · Accessed 20 Oct 2026
  22. RWA product and contracts SynFutures · Accessed 20 Oct 2026
  23. RWA environments and chains SynFutures · Accessed 20 Oct 2026
  24. RWA cash deposits SynFutures · Accessed 20 Oct 2026
  25. RWA cash withdrawals SynFutures · Accessed 20 Oct 2026
  26. RWA cash buffers SynFutures · Accessed 20 Oct 2026
  27. RWA stock deposits and withdrawals SynFutures · Accessed 20 Oct 2026
  28. RWA API permissions SynFutures · Accessed 20 Oct 2026
  29. One Click security and semantics SynFutures · Accessed 20 Oct 2026
  30. RWA order placement and cancellation SynFutures · Accessed 20 Oct 2026
  31. RWA order history SynFutures · Accessed 20 Oct 2026
  32. RWA status model SynFutures · Accessed 20 Oct 2026
  33. Interface-linked terms route SynFutures · Accessed 20 Oct 2026
  34. F staking overview SynFutures · Accessed 20 Oct 2026
  35. Anchored Finance legal footer Anchored Finance · Accessed 20 Oct 2026
  36. Anchored product eligibility Anchored Finance · Accessed 20 Oct 2026
  37. Anchored token specifications Anchored Finance · Accessed 20 Oct 2026
  38. Anchored trust and transparency Anchored Finance · Accessed 20 Oct 2026
  39. SynFutures protocol activity DefiLlama · Accessed 20 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