How can Web3 projects establish more comprehensive public information disclosure?
This article outlines methods for organizing and disclosing public information for Web3 projects—covering entity details, records of key events, ongoing maintenance, and the boundaries of disclosure—to help enhance the verifiability of publicly available information.
The goal of disclosure is to make facts verifiable.
The purpose of public information is not to create a "seal of credibility," but rather to enable users, researchers, and partners to locate a project’s official sources and understand what information has been disclosed versus what remains restricted.
Three Categories of Foundational Information
Identity and Entity Information: Project name, official website, official social media channels, and public profiles of the team or the entity itself. Events and Records: Information regarding funding, product launches, audits, partnerships, and significant milestones. Ongoing Maintenance: Update logs, archived announcements, and a clear historical timeline.
How Information Should Be Organized
For every key fact, include the date, a link to the source, and necessary context whenever possible. For details prone to change—such as funding, team composition, or tokenomics—ensure consistency across all channels; in the event of a name change or migration, provide an official statement clarifying the connection.
The Limits of Disclosure
Projects should not publicly disclose sensitive personal information, undisclosed business plans, materials subject to non-disclosure agreements (NDAs), or details that could pose security risks. Comprehensive information does not constitute a guarantee of a project’s quality, regulatory compliance, or investment value.
Next Steps
Modify Information:
https://www.rootdata.com/projects/submit?ft=modifi
Create a Project:
https://www.rootdata.com/projects/submit?ft=create
RootData Boost:



