SynFutures (F)

SynFutures (F): A Protocol for User-Created Perpetual Futures

SynFutures presents itself as a decentralised derivatives protocol built around perpetual futures, with a stated aim of letting users trade and create contracts for a broad range of assets. Its V3 design combines two market structures, but important details about the F token and practical adoption remain unspecified in project materials.

SynFutures targets open-ended perpetual futures markets

SynFutures is described as a decentralised finance protocol for perpetual futures. Its stated objective is to broaden access to derivatives by allowing users to trade assets and create futures contracts without relying only on a fixed list of markets. project materials attributes this flexibility to the protocol itself; it does not establish how many markets are active, which assets have meaningful liquidity, or what restrictions apply to new contracts.

Perpetual futures are derivatives designed to track an underlying asset without a fixed expiry date. That structure creates a need for a market mechanism that can support trading, pricing and position management over time. public materials identifies perpetual futures as SynFutures’ central product, but does not provide operating parameters such as leverage limits, collateral assets, liquidation rules, funding calculations or insurance arrangements. Those omissions matter when assessing how the protocol functions in practice.

V3 combines an automated market maker with an order book

The project says its V3 release introduces a unified automated market maker, or AMM, alongside an on-chain matching order book. An AMM normally provides liquidity through a programmed pricing mechanism, while an order book matches buy and sell orders at selected prices. SynFutures presents the combination as a single market structure intended to bring both approaches into the same trading environment.

This description explains the architectural direction, but not the precise division of responsibilities between the two components. public materials does not specify how orders move between the AMM and order book, how prices are formed when their available liquidity differs, or how fees and execution priority are determined. It also does not document the safeguards used during sharp market moves. These are practical dependencies for anyone trying to understand execution quality and the risks of using the system.

User-created contracts are a stated part of the product model

SynFutures says users can create arbitrary futures contracts within seconds. In principle, that model shifts market creation from a centrally selected catalogue toward permissionless or broadly accessible contract deployment. It could allow markets to be proposed around assets that are not yet supported by conventional derivatives venues, although public materials does not confirm the precise access rules or the review process for new markets.

A user-created contract still depends on more than a contract template. It requires a reliable reference price, sufficient collateral, liquid counterparties and rules for settlement when the underlying asset is volatile or difficult to value. project materials does not identify its oracle design, collateral framework, liquidation engine, dispute process or criteria for removing an inactive market. It also does not establish whether every supported asset can be created by any user or whether additional permissions apply.

F is named as the project token, but its function is not documented here

The project is listed as SynFutures (F), establishing F as the associated token symbol. project materials does not state whether F is used for governance, staking, fee payment, incentives, collateral, insurance or another protocol function. It also gives no token supply, distribution, unlock schedule or rights attached to ownership. As a result, the relationship between the token and the perpetual-futures product cannot be described beyond the project’s name and symbol.

This distinction is material. A protocol can operate a trading product while its token serves a separate or limited role, and public materials does not show which model applies to F. Readers examining the project need primary documentation on token utility, governance powers, emissions, custody requirements and any dependencies between token ownership and access to protocol features. None of those details should be inferred from the existence of the F ticker alone.

Ethereum, BNB Chain and Base are the recorded network environments

SynFutures is recorded across Ethereum, BNB Chain and Base. These network listings identify the ecosystems associated with the project, but they do not by themselves confirm that every feature is available on each chain or that liquidity and user activity are distributed evenly between them. Cross-chain deployment can also create practical differences in transaction costs, available collateral, contract versions and market depth.

public materials lists official link types including a homepage, whitepaper, blockchain site, chat channel and code repositories, but it does not provide the contents of those materials. It therefore cannot establish the current deployment status of individual contracts, the scope of any audits, the identities of contributors, or the governance and upgrade arrangements. Those details remain necessary for a fuller assessment of how the multi-network system is maintained.

Key takeaways

• SynFutures is presented as a decentralised protocol focused on perpetual futures.
• Its stated V3 design combines a unified AMM with an on-chain matching order book.
• The project claims users can create futures contracts for arbitrary assets, but the access and risk controls are not documented here.
• F is the named token, while its utility, supply structure and governance role remain unspecified in public materials.
• The project is recorded on Ethereum, BNB Chain and Base.
• Historical observations show substantial variability and a predominantly high-risk recorded market profile.

Risks and unresolved questions

• project materials does not specify leverage, collateral, liquidation, funding or insurance rules for perpetual futures.
• Oracle design, settlement procedures and safeguards for user-created markets are not documented.
• The interaction between the V3 AMM and on-chain order book, including pricing, routing and fee rules, remains unclear.
• F token utility, supply, distribution, unlocks and governance rights are unspecified.
• Deployment across three networks may involve differences in liquidity, contract versions, costs and available markets; public materials does not quantify them.
• The description mentions funding from investors but provides no information about current operations, governance, audits or adoption.