Real-time charts for every market, in one place
Trade smarter with real-time market insight.
Every chart, every market, one workspace.
Fast, clean charts with built-in indicators, drawing tools, and layouts that just work.
Cryptocurrency Heatmap
Real-time market cap visualization for top crypto coins
See which cryptocurrencies are gaining or losing at a glance — bubble size reflects market cap, color reflects 24h price change.
SYN to USDT Converter
1 SYN = 0.18994 USDT · updated 06:19 UTC
Volume Bubbles Chart (1h)
Each 1-hour candle's volume is signed by its direction (up candles count as net buying, down candles as net selling) and drawn as a bubble at the closing price, green for buying and red for selling. Bubble size and colour intensity show how strong that flow is compared with the last 300 candles: the strongest 30% get full bubbles with their USD value, the rest stay as small dots. Unusually large bubbles flag aggressive buying or selling worth a closer look, often near breakouts, reversals or key levels.Seasonal Chart
Plots one line per calendar year showing the % change since the start of that year, with the current year highlighted against up to four previous years. Lining the years up on the same calendar shows whether the price tends to rise or fall in the same months, helping you spot recurring seasonal patterns. Treat it as context rather than a forecast: past seasonality does not guarantee future moves.Synapse Markets
Synapse Historical Data
About Synapse (SYN)
Synapse combines a token-governed protocol with cross-chain bridge and router software. Its docs describe several bridging methods, including liquidity pools, canonical routes, and CCTP for qualifying USDC transfers.
A protocol for moving assets between chains
Synapse offers cross-chain routing tools for moving supported tokens between networks. Its bridge docs describe a transfer in three steps: assets enter a bridge contract, move through a selected route, and reach the destination chain. The router chooses an available method based on the origin, destination, asset, and route requirements. Synapse documents canonical bridging, liquidity-pool routes, and Circle’s Cross-Chain Transfer Protocol for USDC. Which option appears depends on the selected route; the presence of SYN in a token list does not guarantee that every chain pair is available.
How liquidity routes work
Some Synapse liquidity-pool routes use intermediate assets called nexus USD (nUSD) and nexus ETH (nETH). The docs say both are backed by corresponding liquidity pools on Ethereum. In a liquidity-pool transfer, the source asset can be converted into an intermediate token, moved across the route, and converted back to the destination asset. That path differs from a canonical bridge, which uses wrapped tokens. The router docs explain how a quote estimates the token and amount to be received. An app can inspect that route before asking a user to confirm.
What SYN is used for
Synapse’s token docs identify SYN as the governance token for Synapse Protocol. Holders can take part in DAO decisions concerning the protocol and the associated Hypercall and Cortex Protocol initiatives. The same page says future SYN emissions are governed by the DAO. That is a governance role rather than a claim that SYN is required for every bridge transfer. Bridging fees, asset liquidity, route support, and token governance are separate aspects of the system, and should not be treated as one combined measure.
Supported networks and route checks
Synapse lists supported tokens by chain. Its docs tell users to check the bridge page for a route between the two chains they chose. Route access can depend on the amount being moved. The bridge docs also describe a Solana Bridge alongside EVM and non-EVM chain support. So the same token or route may not be offered on every network. The token ticker alone cannot indicate that a particular SYN form or bridged asset is the one selected in a wallet.
Risks in cross-chain use
Synapse routes use smart contracts across networks. The result depends on the chosen route and the contracts that run it. The official router docs say some routes use token swaps before processing the destination-chain transfer. A route can be unavailable for an asset pair, and a quoted output can differ from the amount finally received because a route uses swaps. SYN governance use does not remove bridge, liquidity, contract, or destination-network risks. Market charts describe SYN’s traded price, not the safety of a particular bridge transaction.
Last reviewed: Oct 9, 2026
Synapse (SYN) FAQ
What is SYN’s circulating supply?
For SYN, the live field lists 219,066,529 tokens in circulation. Synapse’s official token page names SYN as the governance token for Synapse Protocol, Hypercall, and Cortex Protocol, with future emissions governed by the DAO. Circulating supply is not the same as tokens held in governance or liquidity contracts.
What is SYN’s current price?
FMchart’s current composite quote for SYN is $0.1896. Synapse’s token page assigns SYN a governance role across Synapse Protocol, Hypercall, and Cortex Protocol. The quote combines supported market venues, but it does not show whether a bridge route exists for a selected chain pair or how much a transfer will deliver.
What is the SYN token used for?
SYN is the governance token for Synapse Protocol. The project’s documentation says holders can participate in DAO decisions affecting Synapse Protocol, Hypercall, and Cortex Protocol, and that future SYN emissions are controlled by the DAO. The docs also list SYN among assets used in the ecosystem. That governance role is different from the router software that determines a cross-chain transfer path.
What is SYN’s all-time high?
SYN’s all-time market peak is $4.92, with the recorded date Oct 23, 2021. Synapse’s bridge docs list canonical transfers, liquidity-pool paths, and CCTP for supported USDC transfers. Those route types describe bridge software; the high is a separate record of the token’s traded price.
How has SYN performed over time?
Synapse’s bridge offers distinct route types, including canonical bridging, liquidity-pool paths, and CCTP for supported USDC. Route selection and transfer results depend on that path; neither item is summarized by the monthly price result. The return field describes SYN’s market history, not bridge success or DAO votes.
How does the Synapse Bridge work?
Synapse’s bridge docs say user assets are sent to a bridge contract, moved along the selected route, and returned on the destination chain. Its router can select canonical bridging, liquidity-pool swaps, or CCTP for supported USDC transfers. Users need to check whether a path exists for the selected origin, destination, token, and amount, because not every pair is supported.
What are nUSD and nETH in Synapse?
Synapse’s bridge documentation identifies nexus USD (nUSD) and nexus ETH (nETH) as intermediate tokens used by some liquidity-pool routes. The docs say they are backed by their corresponding liquidity pools on Ethereum. A route can convert the source asset into an intermediate token before bridging and then convert it back on the destination chain. That path differs from canonical bridging.
Who controls future SYN emissions?
Synapse’s official SYN token page says all future emissions are governed by the DAO. The same page gives token holders participation rights for decisions about Synapse Protocol, Hypercall, and Cortex Protocol. This is a statement about governance authority; it does not provide a fixed timetable for future emissions or guarantee that any proposal to change emissions will be approved.
Does every chain pair have a Synapse route?
No. Synapse’s supported-routes documentation says route availability depends on the amount being bridged and directs users to check the bridge interface for a specific pair. The supported-token list is organised by chain, which means a token present on Ethereum does not automatically have a route to every other network. A route quote is specific to the selected asset and destination.
Is SYN required for every bridge transaction?
Synapse’s documentation identifies SYN as a governance token, while the bridge supports transfers of other assets through routes and liquidity pools. That distinction means the existence of SYN does not establish that every bridge action must use it as the transferred asset. The selected token, origin chain, destination chain, and route determine which assets and steps a transaction uses.