Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Treasury Proposal: web3metrics made clear and easy to access
Original forum post here
Organizations have a need for a variety of web3 data and information (e.g., number of active users); however, the sources of this data are disparate, contain discrepancies, and lack both detailed descriptions and information on how the metrics are derived (i.e., the source and/or the calculation/transformation).
It is important for the ecosystem to effortlessly access and compare metrics from multiple sources while understanding the precise definition of the metrics.
We validated the need/desire from the community through this forum post and have created full proposal based on our proposed solution for discussion. We look forward to feedback on our first proposal!
Cheers.
Comments (9)
I am super supportive of the effort itself! I find the price point to be very high however. We built a governance dashboard with the same architecture, so I know the work involved. Definitely a big team to achieve the deliverables. Are you open to a post delivery payment? There is a discussion going on in the Kusama direction channel about potentially using child bounties for milestone based payouts. Alternatively a post delivery proposal or a delayed payout proposal might also work?
We're happy you're super supportive, it's much appreciated. We have a big vision for this over time and want to lay a really solid foundation for growth.
After discussing in the telegram channel, we have discounted it 50%. The proposal has been updated to reflect this. We're also fine with a post delivery payment, which is also reflected in the proposal.
Great area of focus - that is fundamental to us all pushing towards treasury spending that can objectively impact on-chain metrics.
Without this work, we're all building on sand.
One question
Did you also reduce scope as well? You mentioned in the TG that the initial pricing was based on work done elsewhere - are you making any compromises to make this work? Pricing is a very touchy/feely subject right now - and everyone is trying to find referencing to assess requests.