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.
SIGN to USDT Converter
1 SIGN = 0.0103498 USDT · updated 06:22 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.Sign Markets
Sign Historical Data
About Sign (SIGN)
Sign Protocol is an attestation system for creating and verifying structured claims across blockchains and other data systems. An attestation is a signed statement about a person, event, document or other claim, formatted according to a schema. The protocol is designed to make such records easier for applications to query and verify. SIGN is the token associated with Sign Global, but the protocol's data model should not be confused with a token transfer or a guarantee that every claim is true.
Sign Protocol and attestations
A schema defines the fields and structure that an attestation must follow. Sign Protocol documentation describes attestations as signed structured data that can include context, issuer identity and cryptographic proofs. A verifier can check whether a record follows the expected schema and whether its signature or proof is valid. That process confirms technical properties of the record, not necessarily the truth of the underlying real-world statement.
Schemas and verification
Sign Protocol supports multiple storage arrangements. Its documentation describes on-chain records, off-chain storage using systems such as Arweave or IPFS, and hybrid approaches that store references on-chain while keeping larger payloads elsewhere. The choice affects cost, availability and privacy. IPFS content is not guaranteed to remain available forever without pinning or other storage support, so applications should plan for data retention.
Where data is stored
Sign's developer docs position the protocol as infrastructure that applications can use for identity, eligibility, reputation, credit-related claims and other attestations. A schema hook can add application rules such as whitelisting attesters or charging fees. These tools do not make a claim legally binding by themselves. Trust depends on who issued the attestation, what evidence they used and whether the consuming application checks it correctly.
The SIGN token identity
Token information and protocol capabilities should be assessed separately. A protocol can provide attestation infrastructure while the token's exact roles depend on official token documentation and live contracts. Users should verify the contract address and network for SIGN before interacting, because ticker reuse is common. Attestations can be false, outdated or revoked under a schema's rules, so verifiers should check issuer trust and validity conditions. Verifiers should check the attester, schema version, validity period and revocation status, not merely the presence of a record. Verifiers should check the attester, schema version, validity period and revocation status, not merely the presence of a record. Verifiers should check the attester, schema version, validity period and revocation status, not merely the presence of a record. Verifiers should check the attester, schema version, validity period and revocation status, not merely the presence of a record.
Verification depends on context
A well-formed attestation is only as useful as its issuer, evidence and validation rules. Applications should confirm schema versions, revocation and expiration, and they should not treat a signed claim as legal proof unless the relevant process supports that conclusion.
Last reviewed: Oct 10, 2026
Sign (SIGN) FAQ
What is the current price of SIGN?
SIGN's composite quote is $0.0103. Sign Protocol is designed to create and verify structured attestations across chains and data systems. That technical function is separate from the token's market price, and token identity should be confirmed by the official contract and network.
What is Sign Protocol?
Sign Protocol is an attestation infrastructure for creating and verifying structured claims across chains and data systems. It uses schemas and signed attestations so applications can query records in a consistent format. The protocol is infrastructure rather than a single end-user application.
How much SIGN is in circulation?
The circulating-supply field for SIGN is 2,843,333,332 SIGN. Market-data estimates may change and should be distinguished from total allocations or tokens held by contracts. The Price Statistics panel shows the available figure when market data is present; consult official token documents for supply rules.
What is SIGN's all-time high?
SIGN's recorded market high is $0.1311, dated Sep 23, 2025. This is a price-history metric and does not measure the number or accuracy of attestations created by Sign Protocol. Technical verification and real-world truth are separate questions. This matters because iPFS availability is not permanent without storage support.
How has SIGN performed historically?
FMchart's composite history begins on the date shown in the chart and converts available exchange prices to USD. schemas define fields and validation structure. The Monthly Returns section summarizes that series, which can differ from one venue or another currency.
What is the difference between SIGN and Sign Protocol?
Sign Protocol is the attestation infrastructure described in the developer documentation, while SIGN is the token associated with Sign Global. Protocol features do not by themselves establish token utility. Verify the official token documentation and deployed contract before inferring how the asset is used.
Can attestations be stored off-chain?
Yes. Sign Protocol documents on-chain, off-chain and hybrid storage. Large payloads can use systems such as Arweave or IPFS, while on-chain references preserve a way to locate the record. Off-chain availability depends on storage providers and retention arrangements. This matters because attestations can be on-chain, off-chain or hybrid.
Can an attestation be revoked?
Sign Protocol schemas can define whether attestations are revocable and can include validity rules. A verifier should check the schema, expiration and revocation state before relying on a record. The exact behavior depends on the schema and contract implementation. This matters because schemas define fields and validation structure.
What are schema hooks?
Schema hooks let a contract apply additional rules when attestations are created or revoked. Documentation gives examples such as whitelisting attesters or charging fees. Developers must ensure the hook's logic matches the schema; incorrect encoding or configuration can cause verification to fail.
What risks affect Sign Protocol users?
Risks include false claims from untrusted issuers, outdated or revoked attestations, schema mistakes and off-chain storage failures. A valid signature confirms who signed data, not whether the real-world claim is true. Applications need issuer checks and clear validation rules. This matters because technical signature validity does not prove the real-world claim is true.