Curve Gauge Voting Analytics Dashboard

**Background**

BadgerDAO has had great success with CRV LP vaults alongside its auto-compounding CVX and cvxCRV vaults. [You can read the details of their launch here](https://badgerdao.medium.com/overview-f9e404f08882).

**The Goal**
To win this bounty you must create a dashboard that will display detailed analytics on Curve gauge voting.
The analytics should be displayed in a web interface and show quantitative results in text and in graphic form, i.e. Charts. There should also be qualitative descriptions with each statistic to help users understand why the statistic is interesting.

**Details**

This analytic system should query data from onchain sources that may or may not include: web3, subgraphs, dune, and any other trusted transformed data sources.

The analytics system will ingest these data and perform any further required transformations for analysis.
Analysis will be run on the data and the final results will be displayed in a web interface.

The system should display details related to Curve gauge voting:
• Who is voting how
• Historical voting patterns including address tagging
• How much veCRV is responsible for allocating x CRV over the two week period
• How does CVX look in the same regard
• Bribing analytics would be immensely helpful as well

_Optional/Bonus:_

Any other statistics or visualizations that help clarify the behavior of participants of Curve gauge voting.
Based on the results of the analysis suggest any changes that can be made to how veCRV and CVX are used in the Badger ecosystem. Bonus points if you also incorporate convex voting analytics which should also be going live over this hack-a-thon. Note that we will be more likely to use/publish such a thing.

**Bounty Payout Details**

Upto 8000 USD in Badger will be awarded to up to 4 highly diligent and complete and insightful dashboards. Any dashboard we publish or use will be awarded with $4000 in BADGER minimum.
You'll do much better at this bounty if you come talk to us on our [Builder Discord](https://discord.gg/Tf2PucrXcE)

The issue names no repository files, tests, or implementation entry points; start by defining the trusted on-chain data sources and the dashboard scope. Done means a web interface presents quantitative text and charts with qualitative explanations for voting, historical, veCRV, CVX, and bribing analytics.

Written by the indexing model from the issue text.