Methodology Hash

A methodology hash guarantees that the same input data and calculation rules will always produce the same result. This determinism is enforced by the underlying cryptographic hash function (e.g., SHA-256), making the output verifiable and reproducible by any third party.

The hash is generated from a structured document (e.g., a JSON schema) that defines the metric's entire logic, including:

• Data sources (APIs, subgraphs, RPC nodes)
• Aggregation methods (sum, average, time-weighted)
• Filtering and transformation rules Once published on-chain, this definition cannot be altered without generating a new, distinct hash.

Every data point calculated using a methodology hash carries a cryptographic link back to its exact rule set. This creates a complete audit trail, allowing analysts to verify not just the data, but how it was derived. It answers the critical question: "Which version of the rules produced this metric?"

Standardized methodology hashes enable composable analytics. A DeFi protocol can publish its TVL hash, and other dashboards or smart contracts can trust and incorporate that verified metric. This creates an interoperable layer of verified on-chain data, moving beyond siloed reporting.

By removing reliance on a single centralized data provider, methodology hashes enable trust-minimized analytics. The integrity of the data is secured by cryptography and open-source code, not by the reputation of an institution. Users verify the hash, not the publisher.

A TVL methodology hash might encode rules to:

• Query token balances from specific smart contract addresses.
• Use oracle prices from a defined source at a specific time.
• Exclude illiquid or wrapped assets.
• Sum values in USD. Any platform using this hash calculates an identical, verifiable TVL figure.

A Methodology Hash is a unique, deterministic cryptographic hash (e.g., SHA-256) generated from the complete specification document that defines how a metric is calculated. Its primary purpose is to provide immutable proof of the exact methodology used at a specific point in time, enabling verifiable and reproducible analysis across different platforms and audits.

The hash is computed from a canonical representation of the methodology document, which includes:

• Scoring algorithms and formulas
• Data sources (specific smart contracts, RPC nodes, subgraphs)
• Weighting parameters and thresholds
• Time windows (e.g., 30-day rolling average)
• Any exclusion or inclusion rules This creates a content-addressable identifier; any change to the methodology produces a completely different hash.

When a protocol or rating agency (like Chainscore) publishes a score, they can publish the accompanying Methodology Hash. Analysts and users can then:

• Replicate the calculation using the same hashed methodology.
• Verify that the published score matches the result of the defined process.
• Detect undisclosed changes if a future score uses a different hash without announcement.

Methodology Hashes act as a robust versioning system. Instead of vague "v1.2" labels, each iteration has a unique, verifiable hash. This allows for:

• Transparent evolution: Tracking precise changes between methodology versions.
• Historical consistency: Querying scores calculated under a specific, frozen methodology hash.
• Dispute resolution: Providing an immutable reference point for audit trails.

To maximize trustlessness, Methodology Hashes can be published via on-chain attestation protocols like Ethereum Attestation Service (EAS) or stored on decentralized storage (IPFS, Arweave). This creates a public, timestamped, and tamper-proof record that links a data output (a score) to its governing rules (the hashed methodology).

A lending protocol's collateral risk score might be calculated using a methodology that hashes to 0x8a3f...c21d. The methodology specifies:

• Volatility sourced from a 90-day TWAP oracle.
• Liquidity depth from Uniswap V3 fee tiers.
• Concentration risk from top 10 holder analysis. Any user can audit this exact process using the public hash.

The hash creates a permanent, unchangeable record of the research methodology. This includes the data sources, filtering logic, aggregation functions, and time parameters. Any change to the methodology produces a completely different hash, making manipulation immediately detectable.

By sharing the methodology hash, any researcher can independently verify findings. They can re-run the exact same query logic against the same on-chain data to confirm the results, eliminating the "black box" problem in data analysis and ensuring findings are not artifacts of a specific, opaque process.

It mitigates p-hacking (tweaking analysis until a desired result appears) by locking the methodology before results are known. Researchers can commit a hash of their planned analysis to a public registry, proving the methodology was not altered post-hoc to fit a narrative.

For metrics like Total Value Locked (TVL) or Daily Active Users (DAU), a methodology hash defines the exact calculation. This allows different entities (e.g., DeFi protocols, analysts) to use a standardized, verifiable definition, enabling apples-to-apples comparisons and building trust in industry-standard KPIs.

The methodology is separated from the entity publishing the results. A protocol can publish data about itself using a pre-committed, hash-verified methodology, making the data credibly neutral. Auditors and users trust the data because they can verify the logic, not just the source.

Methodology hashes are critical infrastructure for decentralized autonomous organizations (DAOs) making treasury decisions or oracles providing data feeds. They ensure the data triggering multi-million dollar actions is generated by a transparent, agreed-upon, and unchangeable process.