ArticleListing

With frequent security incidents, why should projects and exchanges improve the disclosure of information?

RRootData Editorial Team
Published 5 minUpdated

After a security incident occurs, how to verify the project's public information with the exchange? This article introduces the RootData information update process and the reference value and boundaries of information disclosure.

After a security incident occurs, what should users first verify?

When asset theft, phishing, system anomalies, or major security incidents occur, users should first confirm which real entity they are dealing with and whether the platform continues to disclose important information. The publicly available information related to the exchange's entity and license, proof of reserves, core team, official announcements, and security upgrade records are different dimensions that help readers verify the facts; they cannot replace each other and do not equate to platform security or solvency.

What information should project parties and exchanges actively maintain?

Project parties should timely maintain public sources for their official website, official social media, core products, team, financing, audits, and important milestones. Exchanges should supplement public disclosures related to the platform entity and applicable regions, product rules, reserve or audit explanations, official announcement channels, and publicly available security upgrade records. All content should be based on published, verifiable official sources.

Why is it necessary to maintain consistency on public information pages?

When the information on official websites, social media, data platforms, and media information pages is consistent, users, researchers, and partners can more easily find and verify the official version. For projects and exchanges, this helps reduce outdated links, incorrect introductions, and confusion with similarly named entities, establishing a clearer and traceable brand public image rather than obtaining any form of credit guarantee.

How to submit updates in RootData

If a listed project or exchange needs to supplement, correct, or update public information, it should submit through the "Modify Information" page and attach relevant source links. New projects can submit basic information through the "Create Project" page. For matters involving public disclosure time windows that require urgent attention, please refer to the current rules and applicable scope of RootData Boost.

Boundary Explanation

The display and update of information in RootData are subject to data review and current page rules. The completeness of information, public disclosure, or third-party page display does not constitute a guarantee of the project's or exchange's security, compliance, solvency, service quality, or investment value.

Next Steps

Modify Information:

https://www.rootdata.com/projects/submit?ft=modifi

Create Project:

https://www.rootdata.com/projects/submit?ft=create

RootData Boost:

https://www.rootdata.com/projects/submit/rd-boost

Related content

ListingArticle

How to maintain a public milestone timeline for Web3 projects?

This article introduces how Web3 projects organize and submit key development events, covering event timelines, source verification, information updates, and historical record maintenance, enhancing the accuracy of publicly available project information.

RRootData Editorial Team
5 min
ListingArticle

RootData Boost is what? Applicable scenarios and boundaries.

This article introduces the service positioning, applicable scenarios, and data submission requirements of RootData Boost, helping project parties understand the project inclusion, information modification, and expedited processing procedures, as well as the related service boundaries.

RRootData Editorial Team
5 min