Silex Trust Center

Transparency is part of the product.

Silex provides discovery, market intelligence, verification and monitoring tools for the Cronos ecosystem. This page explains how our signals are produced, where data comes from and how to inspect the rules behind them.

Trust topics

Explore how Silex handles its signals, data and public responsibilities.

Human-reviewed · Separate states

Verification

See what Listing, Contract Verification and Project Verification mean, what a project review checks and where its limits remain.

Verification methodology

Source attribution · Freshness states

Data Integrity

Learn where on-chain, market and project-submitted information comes from, and how Silex labels delayed or unavailable data.

Data methodology

Organic signals · Disclosed placements

Editorial Independence

Understand how listing, sponsorship, verification payments, Trending and Watch remain distinct platform signals.

How independence works

Security & Privacy

Review the documented limits on public data, account information and verification submissions, alongside Silex’s Privacy Policy.

Privacy & security

Anonymous · Read-only API

API & Developers

Build with documented access to supported public project, market, verification, Watch and Trending data.

Developer documentation

Public methodology · Contact

Policies & Accountability

Find the terms, privacy information, product methodology, verification reports and ways to reach Silex.

View policies

Three different states

Do not read one as proof of another.

Listing

Editorial approval for a project profile to appear in public Silex discovery. It does not confer verification or imply investment quality.

How public listings work

Contract Verification

A contract-level state in the project record. It does not by itself verify the project team, identity or claims.

Verification distinctions

Project Verification

A separate project review. An automated pre-scan is followed by human review of identity evidence, official channels, submitted information and relevant contract findings.

Project Verification process

The Project Verification review fee is 400 CRO. Verification fees pay for the review process. They do not purchase or guarantee approval.

A Silex listing or verification is not an endorsement, investment recommendation or guarantee that a project is safe. The review can contain unknowns; inspect the report and verify contract details independently.

Project Verification requests Example verification report

Data integrity

Values retain their source, time and limits.

Silex combines observations from the Cronos chain and RPC, third-party market providers, project-submitted evidence and Silex-maintained listing and verification records. These sources are not interchangeable.

On-chain & RPC: Used where configured to observe chain identity, contract code and supported contract characteristics. Unsupported capabilities remain unknown.
Market providers: Normalized market values may be partial or delayed when upstream data is incomplete or unavailable.
Project submissions: Submitted links and evidence are reviewed as evidence; a submission alone is not treated as an independently confirmed fact.
Freshness: Last observation times and freshness labels help distinguish current data from retained or incomplete observations. Missing API numbers are returned as null, not zero.

When a value is stale, incomplete or unsupported, Silex aims to label it delayed or unavailable rather than present it as current.

Market data guide API freshness & data semantics Observed provider status

Editorial Independence

Commercial activity is a separate signal from platform decisions.

Project Verification is a reviewed process; a fee is not an approval outcome. Sponsorship is not verification, and appearing in listings is not an endorsement.

Silex documentation describes Trending as a relative ranking where sponsorship, Verification and Watch do not change ranking scores. Watch reports observed changes and does not determine listing or verification decisions.

Sponsored placements, when offered, should be identified as sponsored. Sponsorship does not establish project identity, change verification status or guarantee inclusion in Trending or Watch. This page describes the separation reflected in current product rules; it is not a claim of a separate formal independence policy.

Sponsorships & signals Trending methodology Watch & alerts

Security & Privacy

Specific boundaries, without unsupported assurances.

The public API returns an allowlisted projection and excludes account identities, Watchlists, notifications, verification evidence and administrator records. Project Verification submissions require an authenticated session; submission requests use same-origin CSRF checks and field validation.

See the Privacy Policy for how personal information is handled. Silex does not publish a security certification or claim uninterrupted availability on this page.

API & Developers

Public access to supported Silex data.

The Silex Public API is anonymous and read-only. It supports documented GET and HEAD requests, with request limits described in the API guide. Missing numerical values are represented as null; dates use ISO 8601 UTC.

Developer tools also publish observed Cronos RPC and market-provider information. These observations describe their sources; they are not a guarantee of uninterrupted platform availability.

Developer & API documentation RPC status Provider status

Policies & accountability

Read the source material and contact the community.

Last updated: 29 September 2026