Overview
Silex is an editorial discovery and reputation interface for projects on Cronos. It brings public project identity, market context, Listing state, Contract Verification, Project Verification and community signals into one consistent view.
Silex has no platform token. Silex does not currently offer a Silex token, token sale, staking programme or token-based rewards.
Public listings
Listing is the Silex editorial decision about whether a project profile appears publicly. The Silex editorial token store is authoritative; a record is public only while its listing state is LISTED. Request a Listing.
Other internal review states—including discovered, pending, hidden, rejected and delisted—are not public listings. Listing approval means that a profile may be displayed; it is not a statement about investment quality, safety or future performance.
Canonical identity
Silex identifies a token by its chain ID and normalized contract address. This avoids ambiguous names and tickers. Always compare the contract shown on Silex with an independent chain explorer before interacting with a token.
Contract Verification and Project Verification
The concepts are distinct and may be considered in this order: Listing → Contract Verification → Project Verification. This is an explanatory relationship, not an automatic progression or guarantee that a listed project receives either verification.
A Listing controls whether the project profile is public. A project can be listed without either verification state.
Contract Verification
Contract Verification records a contract-level verification state. It does not automatically verify the people, organization or claims behind a project.
Project Verification
Project Verification records a separate project-profile verification state. Listing or verification is not an endorsement or investment recommendation.
An authenticated user can start a Project Verification review from a listed project's information card. Silex carries the canonical chain ID and contract into a separate request page, where the requester must confirm the full contract before submitting contact details, official links and supporting evidence.
The Project Verification review fee is 400 CRO for new requests. The request page shows the applicable CRO amount before submission. Payment confirmation is handled manually. Verification fees pay for the review process. They do not guarantee approval. Silex performs an automated pre-scan and an administrator makes the final authenticity decision.
Market data
Liquidity value changes and CRO history
Liquidity Flows compares the same measured pools at both times. The default list includes rises, falls and small changes, ranked by absolute USD change, with percentage and measurement dates. Missing values are never zero. A separately labelled 7-day group is available when recent comparisons are limited. Last valid results remain visible during temporary request failures. No change, insufficient history and unavailable data have distinct messages. USD liquidity changes can reflect prices and are not confirmed LP deposits or withdrawals.
The CRO price in the market strip opens real historical WCRO-derived USD quotes on hover, focus or tap. Point inspection shows time and price. Cached history is reused; when history is missing the current price remains available.
Token liquidity is the sum across unique valid active current Cronos pools, and token 24-hour volume is the corresponding sum of provider-normalized USD volume. Silex counts each canonical pair address once. Price and price-change fields continue to use the canonical primary/reference market and are never summed or naively averaged across pools. This mutable state is separate from immutable Silex Watch history. Values may be delayed, partial or unavailable when an upstream source is degraded; the previous valid observation is retained with its honest timestamp.
Silex shows unavailable values as unavailable rather than inventing estimates. Market snapshots must not be used as proof that a project is listed or verified; those decisions come only from Silex editorial and verification state. See the Ecosystem and data coverage guide for supported source coverage.
Watch
Silex Watch reports meaningful observable changes in market and on-chain facts over time. Every public severity is paired with the specific event that triggered it, such as MAJOR · Liquidity decreased 46.2%. Event detail shows when the change was detected, available previous/current values, the measured change, the configured threshold or structural rule, and restrained factual context.
Event severity and project Watch state are different. An event is classified as INFO, NOTABLE, MAJOR or CRITICAL. A project is summarized as NORMAL, CAUTION, HIGH_RISK or INACTIVE. For example, a project may be CAUTION because it currently has a MAJOR liquidity event; that severity is not a permanent project rating.
| Event severity | Meaning |
|---|---|
INFO | Meaningful but relatively small observed change. |
NOTABLE | Material observed change worth attention. |
MAJOR | Large observed change crossing a major configured threshold or structural rule. |
CRITICAL | Extreme observed change crossing Silex's highest configured threshold. |
Default quantitative thresholds
| Observed change | Info | Notable | Major | Critical |
|---|---|---|---|---|
| Liquidity | 10% to <20% | 20% to <40% | 40% to <70% | 70% or more |
| Top-10 holder concentration | 2 to <5 percentage points | 5 to <10 percentage points | 10 to <20 percentage points | 20 percentage points or more |
| Total supply | Any known non-zero change below 1% | 1% to <5% | 5% to <20% | 20% or more |
Grouped changes remain one event. Expanded detail presents immutable revisions chronologically and calls out escalation, resolution and available stable related facts instead of producing a stream of unrelated revision alerts. Notification links open the exact event on the canonical project page.
Silex Watch reports observable on-chain and market changes. An event does not by itself prove malicious intent or constitute investment advice.
Community Points
Community Points let authenticated users allocate a limited daily point budget to public Listings. They power community leaderboards and contribute recent activity to Trending; they do not change Listing, Contract Verification, Project Verification or Watch states. The complete allocation, analytics and reactions rules are maintained in the Community Points guide.
XP, Levels and non-transferable Shards are described in the progression guide. Trending's inputs and ranking semantics are documented in the Trending methodology.
Sponsorships
Silex may display clearly labelled, first-party sponsored placements. Sponsorship does not influence organic Trending, Verification, Watch findings, editorial listing visibility or project ordering.
Sponsored content is optional website content and is kept separate from the Silex Public API. If a placement is unavailable or blocked, core project discovery continues normally.
Limitations and responsible use
Silex is an information product, not an exchange, broker, wallet, financial adviser or security auditor. Cryptoassets are high risk and project information can change quickly.
Before acting, independently review the contract, explorer history, official project channels, liquidity conditions and relevant professional advice. See the Terms of Service and Privacy Policy for more detail.
Community Hub: Trending publications
Latest remains the default. Trending ranks approved public project publications by recent external participation. It is separate from Token Trending, voting, Community Points, Watchlist, XP, Shards and rewards.
For each publication, only the most recent qualifying like or visible comment from each account counts. Under 24 hours earns 3 points; 24–72 hours earns 2; 72 hours to seven days earns 1. Each account contributes at most 3 points, even with repeated comments. Editing a comment does not refresh its date.
Publication authors, current project representatives and representatives at the time of their interaction do not count as external participation. Official team comments, hidden or deleted comments, inactive accounts and accounts restricted from commenting are excluded. Removing a like removes its contribution, unless that account still has a qualifying comment. Badges, payments and follower counts have no ranking weight. This does not guarantee the absence of bots or multiple accounts.
Ties use unique participating accounts, latest qualifying interaction, original publication date, project ID and publication ID, in that order. Publications with no qualifying participation are omitted. An empty feed offers Latest instead of inventing popularity.
Search, project and category filters apply to the full eligible set before pagination. Load more keeps the feed's starting time; newer interactions appear after refreshing. If removals, moderation, account status or project rights change the ranked results, reload Trending to start a new sequence. Current publication visibility is always respected. Pagination expires after 24 hours.