ADApolis Methodology

How we score DReps on participation, consistency, and accessibility to delegation.

Last updated: June 2026Phase 1: Participation Rate

1. Overview

ADApolis GovScore is a composite participation metric computed from on-chain Cardano governance data. It measures how actively and consistently a DRep participates in governance, adjusted to surface high-quality DReps who are under-delegated.

In Phase 1, GovScore focuses on a single dimension: participation rate — the percentage of eligible governance proposals a DRep voted on. Future phases will add dimensions measuring rationale quality, consistency, delegator alignment, and more.

All scores are computed from publicly available on-chain data and are fully auditable. The entire computation pipeline is deterministic and reproducible.

2. Phase 1 Score: Participation Rate

Formula

Raw GovScore = (Votes Cast / Eligible Proposals) × 100

Definitions

  • Votes Cast: The number of governance actions (proposals) a DRep voted on (YES, NO, or ABSTAIN).
  • Eligible Proposals: Any governance action that was active during an epoch where the DRep was registered on-chain.
  • Raw GovScore: Participation rate scaled to 0–100.

Data Source

Koios API ( api.koios.rest) — a decentralized, community-maintained Cardano chain indexer. All vote records, proposal metadata, and DRep registration status are fetched directly from the blockchain.

Worked Example

DRep registered in epochs 550–600
Eligible proposals during this period: 100
Proposals DRep voted on: 93

Raw GovScore = (93 / 100) × 100 = 93.0

This DRep voted on 93% of governance actions they were eligible to vote on, earning a Raw GovScore of 93.0.

3. Quadratic ADA-Power Dampening

A DRep's Adjusted GovScore is the Raw GovScore multiplied by a dampening factor based on how much ADA is delegated to them. This creates a gentle curve that surfaces high-quality, under-delegated DReps without punishing large DReps for receiving delegation.

Formula

Adjusted GovScore = Raw GovScore × D

where D = 1 / (1 + log₁₀(ADA_M + 1) / 4)
and ADA_M = ADA delegated in millions

Dampening Table

ADA DelegatedDampening FactorExample: Raw 90.0 → Adjusted
01.00090.0
100K0.94184.7
1M0.85777.1
10M0.75067.5
100M0.66760.0

All calculations use base-10 logarithm. The divisor of 4 was chosen to create a smooth, gentle curve that avoids discontinuities.

Design Rationale

Behavioral score (participation) always dominates. Dampening is a tiebreak mechanism, not a primary ranking criterion. A DRep with worse participation cannot outscore a better one purely through ADA dampening — the math prevents this.

Proof by Example:

DRep A: 93% participation, 100M ADA delegated
Adjusted Score = 93.0 × 0.667 = 62.0

DRep B: 60% participation, 0 ADA delegated
Adjusted Score = 60.0 × 1.000 = 60.0

DRep A still ranks higher despite the dampening.

Purpose: Distribute delegation toward high-quality DReps who haven't yet received community recognition. A 93%-participation DRep with 0 ADA delegated will rank above all except the most highly-participated-in large DReps. This creates a discovery mechanism for excellent under-delegated DReps.

4. What GovScore Does NOT Measure (Phase 1)

Be explicit about what this score is not. Clarity on limitations is essential to credibility.

  • Does not measure vote direction or outcomes. ADApolis does not care whether a DRep voted YES or NO on any proposal. Only whether they voted.
  • Does not measure rationale quality. While a DRep may have published detailed reasoning for their votes (CIP-100 rationales), Phase 1 GovScore does not evaluate them. (Coming in Phase 2.)
  • Does not measure cross-channel consistency. Whether a DRep's Forum posts, Twitter statements, and GitHub activity align with their votes. (Coming in Phase 2+.)
  • Does not measure delegator alignment. Whether delegators agree with or are satisfied by a DRep's voting record. (Coming in Phase 2+.)
  • Does not measure responsiveness or community engagement. How quickly or thoroughly a DRep responds to delegator questions. (Coming in Phase 2+.)

The Cardinal Rule

ADApolis never scores based on HOW a DRep votes — only WHETHER they vote.

This is a deliberate design choice to preserve DRep independence and platform neutrality. ADApolis takes no position on policy outcomes, treasury allocation, or governance direction. We measure participation and transparency, not correctness.

5. Planned Score Expansions

Phase 1 is intentionally narrow. Future phases will add richer signals to GovScore, all while maintaining the Cardinal Rule above.

Phase 2 — Rationale Quality

AI-scored analysis of CIP-100 rationales for clarity, evidence citation, reasoning depth, and novelty. Dimensions added to GovScore: rationale publication rate, rationale quality, consistency (voting aligned with stated positions).

Phase 2+ — Delegator Alignment

Match rate between DRep votes and aggregated pre-vote signals from delegators. Measures whether a DRep represents the values of their delegator base.

Phase 2+ — Growth Normalization

Recent activity weighted higher; gentle decay for inactivity. Surfaces DReps who are currently active over those who participated historically but have gone dormant.

Phase 2+ — Forum & Social Consistency

Cross-channel consistency score: do a DRep's Forum posts, Twitter statements, GitHub activity, and actual votes align? Penalizes opportunism and rewards intellectual coherence.

All expansions will be published in advance with full transparency. Phase 1 scores will never be retroactively changed; new dimensions will be added as separate metrics.

6. Data Sources and Transparency

Primary Data Source

Koios API ( api.koios.rest) — Community-maintained, decentralized Cardano chain indexer. Open source, auditable, no single point of failure.

Transparency Commitments

  • All underlying data is on-chain and publicly verifiable. Every vote, every proposal, every DRep registration can be audited on the Cardano blockchain.
  • Open governance explorer: gov.tools provides an independent view of all on-chain governance data.
  • Sync frequency: Daily (automated), with 1–2 block lag time before data appears in Scoreboard.
  • Open API access: All computed scores will be available via ADApolis API (launching Phase 2). No paywall, no rate limits beyond fair-use.
  • Code is open source: The entire ADApolis codebase is available on GitHub. The scoring algorithm is not proprietary.

7. Limitations and Known Issues

Intellectual honesty requires naming the shortcomings of this approach.

  • Phase 1 Scope

    Participation rate alone is not a complete picture of DRep quality. A DRep could attend every vote but provide poor reasoning, miss nuance, or vote counter to delegator interests. Phase 1 deliberately omits these dimensions. Do not interpret a high Raw GovScore as an endorsement of a DRep's wisdom — only their attendance.

  • DRep Metadata Coverage

    DReps who have not published CIP-119 metadata appear on the Scoreboard with a generated avatar and no bio. This does not mean they are inactive — only that they haven't registered metadata on-chain.

  • New DReps

    A newly-registered DRep may have excellent recent performance but rank lower than an old DRep with mediocre participation — because they had fewer eligible proposals to vote on. This bias favors seniority. Future phases will add "growth normalization" to weight recent activity higher.

  • Koios API Lag

    Koios is decentralized and community-maintained. Data may lag the chain by 1–2 blocks. In rare cases, if the Koios infrastructure experiences downtime, scores may not update on schedule.

  • Proposal Timing

    Governance actions do not occur on a fixed schedule. Some epochs have many proposals; others have none. A DRep in a quiet epoch may appear less active than one in a busy epoch, even if their consistency is identical. This is a feature of Cardano governance, not a measurement error.

Feedback on limitations? We take these issues seriously. If you find a bug, have a suggestion for improvement, or want to report a data anomaly, please open an issue on GitHub or reach out to the ADApolis team.

Last updated: June 2026 | Phase: Phase 1 MVP

Citation: ADApolis GovScore v1 Methodology. ADApolis. 2026. Retrieved from adapolis.net/methodology