Namada

Governance and Network Metrics Dashboard

🚀 Setup

To set up the development environment, follow these steps:

1. Install the project dependencies:

   npm install
   

2. Run the development server:

   npm run dev

3. Run the checks:

   npm test
   npm run lint
   npm run build

Governance proposal source and reconciliation

The dashboard uses the official Namada indexer (https://indexer.namada.net) as the primary source for the current epoch and governance proposals. It follows the indexer's pagination and validates the returned proposal count before presenting the data as current.

If the live indexer cannot be reached, the UI falls back to the bundled summary snapshot in public/data/props.json and the richer records in public/data/proposals/propsDetails.json. That fallback is explicitly labeled as a historical snapshot rather than current network state.

Snapshot reconciliation is deterministic and does not depend on fetch or array order:

1. The detailed dataset has explicit authority over the summary dataset.
2. Within the same authority, the newest Last_committed_epoch wins.
3. Completeness and stable source identifiers break any remaining ties.
4. Missing fields are backfilled from lower-priority records, so an incomplete record cannot erase useful metadata.
5. Populated fields with different values are returned as conflicts, including their source provenance. Development builds log those conflicts for review.

This protects future dataset updates without claiming that the current snapshots contain incorrect dashboard results.

Learn More

Check out vite.dev to learn more about Vite.