{"componentChunkName":"component---src-pages-stps-stp-markdown-remark-frontmatter-stp-tsx","path":"/stps/stp-2/","result":{"data":{"markdownRemark":{"fileAbsolutePath":"/vercel/path0/content/stps/stp-2.md","frontmatter":{"stp":2,"sip":null,"sccp":null,"title":"Data Analytics Working Group","network":null,"author":"Carrot Anderson (@carrotanderson), Kain Warwick (@kaiynne)","type":null,"proposal":null,"implementor":null,"release":null,"created":"2023-06-07T00:00:00.000Z","updated":null,"status":"Implemented"},"html":"<h2 id=\"simple-summary\" style=\"position:relative;\"><a href=\"#simple-summary\" aria-label=\"simple summary permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Simple Summary</h2>\n<!--\"If you can't explain it simply, you don't understand it well enough.\" Simply describe the outcome the proposed change intends to achieve. This should be non-technical and accessible to a casual community member.-->\n<p>This STP proposes spending up to $250k to fund a data analytics working group. This group will be responsible for ensuring all important data about the Synthetix protocol is available, up to date, and displayed on a custom dashboard.</p>\n<h2 id=\"abstract\" style=\"position:relative;\"><a href=\"#abstract\" aria-label=\"abstract permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Abstract</h2>\n<!--A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what _will_ be done if the STP is implemented, not _why_ it should be done or _how_ it will be done. If the STP proposes sending X tokens to Y each week, write, \"we propose to send X tokens to Y each week\".-->\n<p>This STP proposes spending $250k over three months to fund a dedicated working group tasked with handling Synthetix data analytics initiatives.</p>\n<p>The responsibilities of the working group will be as follows:</p>\n<ol>\n<li>\n<p><strong>Data sources and APIs</strong>\nManaging the subgraph and APIs that are upstream of any data analytics artefacts. This data layer must be available and up to date after each protocol upgrade. It will become the source of truth for any analytics artefacts (Synthetix live dashboards, third party platforms, and direct data consumption) in turn ensuring information about Synthetix corroborates across the internet.</p>\n</li>\n<li>\n<p><strong>Official Synthetix artefacts</strong>\nCreating and maintaining Synthetix branded data analytics artefacts (like live dashboards and key metrics displayed on <a href=\"https://synthetix.io/\">synthetix.io</a>) as has previously been done by CCs and community members.</p>\n</li>\n<li>\n<p><strong>Third party analytics</strong>\nIt will be the responsibility of the working group to coordinate with any third-party analytics providers that currently report on Synthetix (e.g. Token Terminal), or that should report on Synthetix but do not (e.g. CoinGecko <a href=\"https://twitter.com/kaiynne/status/1653784645006155781?s=20\">derivatives exchanges</a>). The working group should ensure these third parties are provided any data or endpoints needed to display accurate information about Synthetix.</p>\n</li>\n</ol>\n<h2 id=\"motivation\" style=\"position:relative;\"><a href=\"#motivation\" aria-label=\"motivation permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Motivation</h2>\n<!--This is the problem statement. This is the *why* of the STP. It should clearly explain *why* the current state of the protocol is inadequate.  It is critical that you explain *why* the change is needed, if the STP proposes changing how something is calculated, you must address *why* the current calculation is innaccurate or wrong. This is not the place to describe how the STP will address the issue!-->\n<p>Taken from Kain's <a href=\"https://mirror.xyz/kain.eth/EB9DQldVEb0F74-LmrVau6YbjEtr8dsj1qVn6muYuXw\">blog post</a>:</p>\n<blockquote>\n<p>\"I propose is an analytics group, which will be responsible for ensuring that all data about the protocol is available and up to date. As well as ensuring we have live dashboards for all key metrics. Historically this has failed due to low prioritisation as well as technical complexity.\"</p>\n</blockquote>\n<p>By the nature of building with upgradable contracts, any changes made to the Synthetix protocol mean subgraph and downstream analytics artefacts need to be updated. Low prioritisation has meant that emitted events haven't been designed specifically for data analytics. Without resources dedicated to managing these changes it is difficult to build reliable artefacts and consume information about Synthetix.</p>\n<p>Additionally, there is currently no canonical source of truth. Different applications (<a href=\"https://dune.com/synthetix_community/synthetix-stats\">dune</a>, <a href=\"https://synthetix.io/\">synthetix.io</a>, <a href=\"https://defillama.com/protocol/synthetix\">defilama</a>) display different numbers for key metrics such as TVL.</p>\n<h2 id=\"specification\" style=\"position:relative;\"><a href=\"#specification\" aria-label=\"specification permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Specification</h2>\n<!--The specification should describe the syntax and semantics of any new feature, there are five sections\n1. Overview\n2. Rationale\n3. Technical Specification\n4. Test Cases\n5. Configurable Values\n-->\n<h3 id=\"overview\" style=\"position:relative;\"><a href=\"#overview\" aria-label=\"overview permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Overview</h3>\n<!--This is a high level overview of *how* the STP will solve the problem. The overview should clearly describe how the new feature will be implemented.-->\n<p>A working group will be allocated a $250k budget solely for the responsibilities detailed above.</p>\n<ul>\n<li>The first task would be to build a data layer (APIs, subgraph) that can be used for any data analytics projects.</li>\n<li>Once we have reliable up-to-date data, the working group can begin building artefacts on top of the data layer – for example, a Synthetix branded dashboard to display key metrics on synthetix.io.</li>\n</ul>\n<p>An application process will be defined by the TC enabling interested teams and individuals to apply for the working group. The working group will need close access to the CCs and/or come from within the Synthetix community to have the requisite contextual understanding of these challenges and previous attempts at solving them.</p>\n<h3 id=\"rationale\" style=\"position:relative;\"><a href=\"#rationale\" aria-label=\"rationale permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Rationale</h3>\n<!--This is where you explain the reasoning behind how you propose to solve the problem. Why did you propose this use of funds – what were the considerations. The rationale fleshes out the motivation and reasoning behind decisions that were made. It should describe any alternate ideas that were considered and related work. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->\n<p>Data analytics has been challenging for Synthetix in the past, due to technical complexity and low prioritisation. Various dashboards have been built, however the upstream data itself has not been given sufficient attention.</p>\n<ul>\n<li>By the nature of upgradable contracts, re-indexing the subgraph to access historical data requires understanding of past state of the Synthetix contracts and how they have evolved – this is complex work for anyone who is not dedicated to the task full-time.</li>\n<li>When upgrades are designed, data analytics is often not the top consideration for emitting events. A dedicated working group can work with the CCs to ensure their perspective is considered in new releases.</li>\n</ul>\n<h3 id=\"financial-specification\" style=\"position:relative;\"><a href=\"#financial-specification\" aria-label=\"financial specification permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Financial Specification</h3>\n<!--The financial specification should outline the the tokens, amounts, destinations, and schedule of funds to be moved. If appropriate, any technical considerations should also be included here – that is, changes to any of the interfaces Synthetix currently exposes or the creations of new ones.-->\n<ul>\n<li>\n<p>$250k will be transfered into a pool to be allocated to the working group over a three-month trial period.</p>\n</li>\n<li>\n<p>This budget has been established to ensure there is sufficient interest from potential working group members. Ideally the budget should be more than sufficient to cover any anticipated costs during this period.</p>\n</li>\n</ul>\n<h2 id=\"copyright\" style=\"position:relative;\"><a href=\"#copyright\" aria-label=\"copyright permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>Copyright</h2>\n<p>Copyright and related rights waived via <a href=\"https://creativecommons.org/publicdomain/zero/1.0/\">CC0</a>.</p>"}},"pageContext":{"id":"898edbe4-cc7a-53ff-a680-d7fa946a428b","frontmatter__stp":2,"__params":{"frontmatter__stp":"2"}}},"staticQueryHashes":[]}