TRANSPARENT BY DESIGN
What goes into the index.
Five measures of Kadena Community Edition activity, each compared with one fixed baseline.
Five signals, one daily reading.
Each input is divided by its own fixed baseline, weighted, summed and multiplied by 50. Baseline activity therefore scores 50. The index has no upper limit: if all five inputs match their baselines it scores 50, if all double it scores 100, if all triple it scores 150, and if all fall 20% below baseline it scores 40.
Current values are trailing 7-day averages for active addresses, TVL in KDA and hashrate, and trailing 7-day counts for new contracts and commits. The composite is rounded once to one decimal. The public score card shows a whole number; Pro shows one decimal.
The first six collected days (29 June to 4 July 2026) use the 1 to 6 days available, compared with the same number of baseline days, and are labelled as shorter windows rather than full weeks. Missing observations prevent publication; weights are never redistributed.
The fixed baseline
The first 30 verified days, 29 June to 28 July 2026, set one permanent baseline for each input: the 30-day mean of daily observations for average-based inputs, and 7 × the 30-day mean daily count for weekly counts. New highs never change a baseline or restate an earlier score. Daily summaries are kept permanently and the history grows as each completed day is added.
| Input | Baseline (index level 50) | Observed, 29 Jun to 28 Jul | Rule |
|---|---|---|---|
| Active addresses | 374.9 accounts per chain, daily average | 374.9 accounts, daily average | Observed |
| New contracts | 7 new modules per 7 days | 14 in 30 days (0.47 per day) | Minimum of 1 per day applied |
| TVL | 13,222,255.1 KDA, daily average | 13,222,255.1 KDA, daily average | Observed |
| Network hashrate | 15.2 PH/s, daily average | 15.2 PH/s, daily average | Observed |
| GitHub commits | 7 human commits per 7 days | 24 in 30 days (0.8 per day) | Minimum of 1 per day applied |
Small and zero baselines: a count below one event per day is too sparse for a stable 7-day ratio. Such a count baseline uses the documented minimum of one per day (7 per 7-day window), and the observed value stays visible above. An average-based baseline of zero cannot be divided by and stops publication. No arbitrary divisor is used and no weight is changed.
The inputs
01 Daily active addresses 30%
Distinct senders and receivers within each UTC day and each of the 20 Pact mainnet chains, summed across chains and averaged over seven days. A gas-paying sender counts even when their included transaction fails. Transfer recipients come from executed token events; mining rewards are excluded.
Community Edition ChainwebAn account on two chains counts once on each chain. Accounts are not people.
02 New contracts 25%
Unique new Pact modules over seven days. Identity includes the chain, namespace and module name. Upgrades and redeployments are stored separately; failed transactions and identified test artifacts are excluded.
A module inventory immediately before collection began distinguishes existing modules from new ones; older transaction history is not collected. Unresolved identities and unreviewed test candidates prevent the affected data from being published.
03 Total value locked 20%
Balances read directly from historical Pact state for a versioned registry covering Mercatus, KDSwap, KDLaunch staking, Chips, Cabinet and BroDEX. Pool assets, staked principal and funded order escrow are valued in KDA. Receipt tokens are not counted again.
The index uses the seven-day mean in KDA. The USD display uses Mercatus’s KDA/USDT price, treating USDT as one USD; this is an approximation and does not affect the index.
The registry defines coverage. Pool-implied prices, particularly for illiquid tokens, are valuations rather than guaranteed sale proceeds. DefiLlama is a cross-check only.
04 Network hashrate 15%
The sum of proof of work from canonical block targets across all 20 chains, divided by the observed time and expressed in PH/s. The index uses its seven-day average.
Community node source05 Developer activity 10%
Seven-day human commit totals across public kda-community repositories, including forks. GitHub API records are collected at captured default-branch heads. Merge commits, identified bots and duplicate commit hashes are excluded. Dates use the UTC committer timestamp.
kda-community on GitHubCommits measure development activity, not its quality or eventual adoption.
Reading the index
The score card states the position against the baseline, for example “12% above baseline”. There are no fixed bands and no ceiling. Changes are index points against exactly seven and thirty days earlier; unavailable comparisons show a dash. Contract and commit cards show 7-day totals against a 7-day baseline.
When a score is published
- Collection begins with 90 completed UTC days, starting 29 June 2026. The current partial day is excluded.
- Daily summaries are retained permanently. Raw block payloads may be discarded after validated summaries and supporting evidence have been stored.
- The daily job starts at 00:00 UTC, waits for finality and publishes the previous completed day after all five inputs pass coverage checks. Earlier days are never recalculated.
- Canonical records since collection began, precise TVL state boundaries and bounded source pagination are checked before computing the index.
- If an update fails, the last verified score retains its date and is marked stale.
Collection began 29 June 2026; earlier history not yet included. This is the configured first observation date. No score is published until initial collection is verified and the required checks pass.