Welcome!

Dash Watch July 25th 2019 Report on
Dash Watch 10th Proposal by paragon
https://beta.dashwatch.org/r/JUL19/dash-watch-10th-proposal-july-2019-funding-request

To help Masternodes evaluate your proposal and make an informed decision can you provide information on the following:

- Dash Watch website traffic data and other metrics?
- Before you start work on future plans can you please clearly detail how you plan to integrate or work with Dash Nexus?

Also how can the masternode network verify the data and metrics Dash Watch provide are accurate? Can an external DFO like DCG confirm the data you present is true.

This data request is the only way masternodes can truly know if the masternode network is utilizing your service and deserves continued funding. The network needs to be able to evaluate your performance and value to the network.

For example if it turns out that masternodes are not reading your reports or visiting your website. I would suggest to put a hold on proposed future plans listed in proposal description. As a network we would then first need to ask ourselves hard questions to learn and understand why the network is not reading reports or visiting site if that was the case etc.

Proposal reporting is Dash Watch's main objective. The network needs to take a long-term outlook and factor in future plans on how you are going to collaborate / integrate with Dash Nexus to help masternodes with the decision process. Can you please elaborate on this.

Thank you.

Hi BlueMoon,

Thanks for your feedback, we’ll try our best to answer your questions/concerns below - please feel free to let us know if we miss anything:

- --Dash Watch website traffic data and other metrics?---

These are available in our monthly report, we have website traffic and engagement metrics on page 2 of 5 in the KPIs section. Link to June report: https://reports.dashwatch.org/JUN19/dash-watch-9th-proposal-june-2019-fundin.pdf

Link to previous months: https://dashwatchbeta.org/proposals?search=dash%20watch


- --Before you start work on future plans can you please clearly detail how you plan to integrate or work with Dash Nexus?---

Together, we are optimistically planning to start the initial phases of reporting integration this next month. This initial phase would include information from our Dash Watch Airtables Database which covers metrics such as schedule status, budget status, and communication status. We will still need to discuss more logistical details such as housing the data and report documents.

We have a meeting with the Nexus team next Tuesday (7/30/2019) to further plan the roadmap of the integration. There are many opportunities for us to talk through, but we think the ones that make the most sense to do first are the proposal statues and proposal reports.

To give additional context, Dash Watch and Dash Nexus had constant communication through proposal reporting. Dash Watch has always been ready and open to integrate with the Nexus platform. Both our team and Nexus’ have not received feedback (until recently) indicating that the community would like to see this prioritized. For example, the Nexus team informed us that they were prioritizing other milestones, such as the MNO dashboard, which was driven by their community feedback tool. The DW team has been prioritizing KPI and data metrics (Dash Labs) to help better gauge proposal impact, carrying out initiatives like the Trust and Investment Foundation elections, and building out our verified MNO polling method (which we expect will help the community arrive at consensus faster without going to the treasury for non-funding matters). If the community wants the two teams to prioritize the Dash Watch and Nexus integration, it can and will be done. We just need the community feedback, like you have given here.

---Also how can the masternode network verify the data and metrics Dash Watch provide are accurate? Can an external DFO like DCG confirm the data you present is true. ---

There are several data types, and we’ll try our best to touch on each:

Dash.org Web Traffic, Dash Core Android/iOS Wallet Download data: We get this data directly from DCG’s Google Analytics platform. DCG can verify this information at any time.

Proposal KPIs/Verification - Most of this data can be corroborated with proposal owners. All our reports are made public, so if a proposal owner sees information that is inaccurate, he or she can always reach out to Dash Watch to inform us at any time. We also often send out our final draft for review before publishing as long as the proposal owners have submitted their answers to us on time.

Poll Data - We will release the full vote results at the end of every election, similar to what DCG has done for the past two elections. Voters can, at any time, verify their vote with Dash Watch by providing a vote signature. How the data is provided during the vote will depend on the results of this consensus poll: poll.dashwatch.org

Almost every data point and metric that Dash Watch provides can be validated by one party or more, whether that be DCG, Proposal Owners, or Voters. We are working on getting all our data into public APIs so that anyone can easily pull the raw data.

- --This data request is the only way masternodes can truly know if the masternode network is utilizing your service and deserves continued funding. The network needs to be able to evaluate your performance and value to the network. ---

Via this link, you will find our June 2019 metrics for the beta.Dashwatch.org site (and does not include the original DashWatch.org site): https://docs.google.com/document/d/1AqLD7oHNLDgpSfjHOgeYG8i6bLTs72VkmkqyCiamVKs/edit?usp=sharing

Here’s a summary of our Website Analytics:

Unique Monthly Users: 436
Sessions: 3,196
Pageviews: 3,824
Av. Session Duration: 6:48
Bounce Rate (Excluding Report Downloads): 31.50%

A few things to note in the GA Screenshot: you can see an increase in sessions around June 12 which corresponds with when we released DIF candidate information. You also see an increase in traffic June 23-26th which corresponds to the reports we are releasing end of the month. The high bounce rate is due to the fact that when someone clicks on a report, that is considered a “bounce”, since they are going off of our website and onto the reporting document download. The true bounce rate for June excluding the reporting document downloads is 31.5%.


---For example, if it turns out that masternodes are not reading your reports or visiting your website. I would suggest to put a hold on proposed future plans listed in proposal description. As a network we would then first need to ask ourselves hard questions to learn and understand why the network is not reading reports or visiting site if that was the case etc. ---

We post our reports through announcements on both Discords, the official DashPay Reddit, the Dash Hyperspace, and our Twitter account. Our team members can also be seen regularly engaging in Discord conversations/inquiries and can be reached anytime through a ping, email or private message.

Dash Watch tries it’s best to make sure the MNOs are readily aware of when reports are posted and are readily available to answer any questions or clarifications. If there’s anything Dash Watch can do to improve the reports to get more engagement we are open to do so - we just need the feedback and directive from the MNOs. For example, this month in our future plans, you will see a line item “Original Milestones/Deliverables Tracker” , that was directly a result of MNO and community feedback.

Considering there are about 600-1000 total votes cast for your average proposal of which many of those votes belong to one person, 400 unique views would arguably be quite a high percentage of the masternode votingbase (if we assume the majority of users are MNOs).

--- Proposal reporting is Dash Watch's main objective. The network needs to take a long-term outlook and factor in future plans on how you are going to collaborate / integrate with Dash Nexus to help masternodes with the decision process. Can you please elaborate on this. ---

We’ve tried our best to elaborate above in paragraph 2. Please let us know if you were looking for a different response between this comment and your earlier question.

We've mimic'ed this response in a formatted Google Doc for ease of viewing: https://docs.google.com/document/d/1i-BtAfItPs2D3vZxByqBfJoiGQcFqhMSK4vWbmcoDMA/edit

Please let us know if you have any additional questions or clarification. Thanks!

Yes from me.