Summary
Launch of an Analytics Working Group (AWG) within the DAO to support our growth, define further and execute the Data Strategy as proposed below by @naoufel .
Background
Inverse has now entered a phase of rapid growth and is expanding its activities in several areas. In order to sustain this growth, Inverse DAO committees and WG members (Growth, Marketing, Treasury…) need to rely on accurate, fit-to-need data, as well as user-friendly analytical systems to operate at full efficiency.
Objectives
The analytics department would brand itself as a customer-oriented area, in charge of providing the data and tools critical to Inverse different business areas operations and to ensure its transparency. The objective of this WG will be to define further and develop Inverse DAO Data Strategy.
State-of-play
As it stands there are no protocol data sources and DAO members or third parties have to rely on external data providers (Etherscan, Dune) where the data is not fully available, extractable and the reports not customisable.
On another hand, we do not have unified tools to measure our influence on social media and adapt our strategy or communication accordingly.
Moving Forward
After comparing the solutions available on the market this proposal offers to investigate further and develop the possibility of using Google Data Studio combined with The Graph to ensure our systems rely on powerful and decentralized infrastructures (a mock-up version is available here : Inverse Finance Analytics).
The Graph would provide the infrastructure for a decentralized indexing solution and would allow us to make our data available to the greater through a GraphQL API. This latter is critical in incentivizing other protocols to integrate us by providing them with an in-house, and easy to use data source.
Google Data Studio would provide us with a powerful Data engine (Google BigQuery) combined with customization and web integration capabilities never seen anywhere else in data industry, this would allow us to combine all of our data analytics into one single place while keeping the data decentralized into The Graph. (Think Tableau + Excel + PowerBI + Wordpress combined into one tool)
On the Public Relation and Marketing side many social media (Google Analytics, Twitter, Linkedin…) already provide API or direct integration solutions that are accessible by Google Data Studio and could be integrated seamlessly together with on-chain metrics.
Dune Analytics is to remain a DAO tool for our analytics, but should be used rather on ad-hoc requests or urgent and specific data needs than on periodical reporting and should not be reflected anymore in official communications.
Responsibilities & Tasks
- Follow up with the development of the current subgraph developed by Compound and forked by @naoufel, integrate financial reporting into a new interface,
- Integrate social media data to the DAO strategy and make it available into a new interface,
- Assist DAO members in periodical reporting efforts, answer ad-hoc data requests,
- Continuously follow up with others DAO areas activities, improve current and develop new fit-to-need metrics and solutions,
- Research data and deliver insights.
Members
@naoufel will act as lead of this Working Group, DAO members interested in contributing can get in contact directly.
Budget & Execution
The budget for this proposal is 16,170 DOLA broken down as follows :
-
1,170 DOLAs to compensate @naoufel in order to account for the Dune premium passed costs (390 $ / month x 3 months)
-
5,000 DOLAs to market buy around 10,000 GRT tokens, 50 to 75% of this amount would be dedicated to ‘signaling’ The Graph and influence on-chain indexing politics. The remainder of this amount would be used as a first batch to pay for the query fees as well as provide our users with an API key to query on this subgraph, allowing us to promote full transparency to other protocols and users. Besides, this amount invested would be withdrawable and can constitute a DAO investment onto The Graph infrastructure. Context : the current amount of 1,000 GRT signaling the graph has been provided by @naoufel when initiating the subgraph but is not important enough to get the data indexed widely. Some outages occurred when testing and we had to directly contact some indexers to get the data online. This can not happen when in production.
-
10,000 DOLAs to temporarily recruit a contractor from the Graph community in order to get the subgraph updated and running in a short amount of time. The estimated schedule would be a 2-3 weeks development sprint followed/intertwined with a 2-3 weeks testing, query building and analytics design where @naoufel would also play a part (advise, testing, query building). Context : The Graph uses GraphQL, which is not a database language but rather client-to-middleware language. This means we do need a developer comfortable with not only TypeScript to build schemas, but also with the Graph infrastructure to help us ensure a good basis to a long term data source while minimizing updates and bugs.
-
Any unspent budget will be returned to the Inverse Treasury.