Method
How OpenGrade turns Web3 project context into readable records.
The method is simple: follow a focused set of ecosystems, structure project data, and keep community experience signals separate from source-backed fields.
Tracked networks
Ethereum, Base, Soneium and Arbitrum are followed first.
Project records
Each project is represented as one readable record across identity, chains, campaigns and sources.
User signals
Utility, Community and Trust ratings sit separately from source-backed data.
Record workflow
From fragmented inputs to project updates.
01
Collect
Gather official links, public metrics, chain coverage and campaign context.
02
Normalize
Turn fragmented inputs into comparable project fields and explicit missing states.
03
Separate
Keep source-backed records, campaign visibility and community feedback distinct.
04
Review
Refresh records over time and surface changes as project updates.
Principles
What the method protects.
Source-awareImportant fields should stay close to their source context or show an explicit missing state.
ComparableRecords should be structured enough to compare projects without flattening their differences.
Consumer-readableMetrics should help users understand context, not turn OpenGrade into a trading terminal.