Does the same product rule cover every asset on the site?
Current SynFutures materials describe a broader 2026 platform stack than the earlier V3-only framing, with a newer mainnet architecture, API access and separate product surfaces. Perpetual trading remains distinct from tokenized/RWA offerings.
Why it matters: Identify the exact current product/version before carrying over older V3 workflow or fee assumptions. A perpetual remains synthetic exposure, not ownership of the referenced asset.
SynFutures product introductionInspect evidence trail
- Evidence type
- Provider documentation
- Review scope
- Current SynFutures product, tutorial and historical fee evidence, including broader 2026 mainnet/API/network scope. No live execution, liquidity-removal, withdrawal or eligibility test.
- Underlying review
- 2026-10-24 · brief v1.1.0
- Recorded reviewer
- Decentralised News editorial research. This does not identify an independent auditor.
- Stable claim ID
dn:claim:synfutures:product
Sources and their limits
1 linked document from one publisher origin (synfutures). Multiple documents do not establish independent corroboration.
- SynFutures product introductionReviewed 2026-10-24. Source publication/update date: not recorded in this snapshot.
What would change this conclusion?
An updated product specification distinguishing Perps Engine mechanics from RWA integration and asset rights.
Panel published 2026-10-24. The underlying review date is unchanged. No new live test or named independent reviewer is implied.
Open annotation data v1.8.0