#2509 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.
Show More
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?
dataphysicistWe'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
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.
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.
How do you plan to do a post-delivery payment?
-
You could either do a first referendum with a $0 payment and then a second one with the payment extrinsic included
-
Or you could use a bounty intermediary. This is currently being discussed/worked on after the recent treasury rugs. If you choose to go via this route then you would only need one referenda. Here you would have a transfer extrinsic to the bounty as opposed directly to you. The bounty curators would then pay out your funds as you meet your milestones.
dataphysicistWe're open to either option. It sounds like the community is looking for a new model and would like to see more of the second option (use a bounty intermediary).
Did you also reduce scope as well?
No, we will deliver what is in the proposal without compromises.
dataphysicistWhen the improved process via bounty intermediary has been fully flushed out we're happy to go that route. Until then I think it's best for us to use the known/current process, especially since we are new to the process to begin with.
Our plan is to submit a referendum asking for only 1KSM upfront and the remainder to be paid out upon completion (a second referendum). This should remove any concern over a rug pull.
Hey dataphysicist,
Thank you for posting the proposal.
Please note the [Audit report]is reflecting only the quality of information presented in the proposal and not the Quality of the project/idea itself. I will create another report when proposal goes onchain. Please refer to the feedback in the areas with possible improvements.
The following proposal Audit is created as a part of Proposal #67. More information about Treasury proposal template and the Audit process can be found on the link above. All templates are free for everyone to use. For any questions or feedback regarding the Audit templates use discussion link from above.
Please note that views and opinions presented in the Audit report are my personal and they do not represent general community opinion.
dataphysicistThis is great, it highlighted some areas for improvement for the draft proposal. We will update shortly.
Progress has been made on the discussion around payout bounties and things are now moving to set payout bounty 1 into motion.
An update incase you are interested.
dataphysicistSome updates to the proposal from the audit
- Reformatted the document to more closely align to the newer Kusama Treasury Proposal Template format.
- Updated project description, category, and requested allocation
- Updated to use a final payment rates to present a clear and transparent budget.
- Updated price to use KSM EMA7 from https://kusama.subscan.io/tools/charts?type=price
- Updated deliverables section to include objectives/success critera, conditions that may affect the project schedule, a reporting process including where, when, and who is going to present the information as well as a separate list with final deliverables
I started to review the updated document and most of the mentioned updates are not there i.e. there is no mention of deliverables in the proposal. Did you revert to the old version?
dataphysicistYes, apologies. I somehow reverted after accepting a suggestion. The correct one should say V2 in the title.
Hey dataphysicist,
Thank you for updating your proposal.
Please note the [Audit report] is reflecting only the quality of information presented in the proposal and not the Quality of the project/idea itself. Please refer to the feedback in the areas with possible improvements. Please use the latest price and update the budget before going onchain.
The following proposal Audit is created as a part of Proposal #67. More information about the Treasury proposal template and the Audit process can be found on the link above. All templates are free for everyone to use. For any questions or feedback regarding the Audit templates, use the discussion link above.
Please note that the views and opinions presented in the Audit report are personal and do not represent general community opinion.
Discover similar proposals
