EthSignals
  • EthSignals Manifesto
  • MGP-14: $9600 for EthSignals
  • Reports
  • Tacticals
    • 2018
      • August 14
      • Sep 6
      • Sep 11
      • Sep 25
      • Sep 28
      • Oct 2
      • Oct 5
      • Oct 9
      • Oct 16
      • Oct 28
      • Nov 6
      • Nov 13
      • Nov 20
      • Nov 26 (Retro)
      • Dec 4
      • Dec 11 (Retro)
      • Dec 18
      • Dec 24 (Retro)
      • Outstanding Payments and Budget Feb2019
    • 2019
      • Jan 14
      • Apr 22
      • Tactical 06.05.2019
      • Tactical 21.05.2019
      • Tactical 28.05.2019
      • Tactical 04.06.2019
      • Tactical 18.06.2019
      • Tactical 02.07.2019
      • Tactical 16.07.2019
      • Tactical 30.07.2019
      • Tactical 13.08.2019
      • Tactical 27.08.2019
  • About
  • TennaGraph
    • TennaGraph – Ethereum Signal Aggregator
    • Roadmap & Specifications
      • Exporting Database to Github
      • Filter/Sorting Specifications
      • Stakeholder Admin Module
      • Voting
      • TennaGraph 0.1
      • TennaGraph 0.3
      • TennaGraph 0.4
      • Data Analysis
    • Other Solutions / Long Shots
    • Try it out
Powered by GitBook
On this page
  • User Story
  • Overview
  • Problem
  1. TennaGraph
  2. Roadmap & Specifications

Exporting Database to Github

PreviousRoadmap & SpecificationsNextFilter/Sorting Specifications

Last updated 6 years ago

User Story

As a Researcher or Historian I would like to see how a decision was made about the network (Statements , coinvotes, etc...) at the time it was made in order to better understand the decision making process and inform how it may be improved.

Overview

One of our core principals is "Historical Data Transparency". This is because Tennagraph sits in the center of the decision history of Ethereum itself. To often retrospectively the answers to "why did we do that?" get lost and has little supporting data resulting in anecdotal accounts of what happened. Without good data on the decision making process there is no good way to evaluate the mechanisms for making those decisions. It isn't within our scope to provide the evaluation, but it is within our scope to provide the means to do this. Thus we provide an open historical archive that shows the changes overtime on the site.

Problem

While Git provides a great way to view a history over time and JSON is easy to work with it is too slow to run Tennagraph on natively. A solution is some hybrid system.

https://docs.google.com/drawings/d/e/2PACX-1vRp9R87ew8cyJKss8vleKNRyoG5mFUfqQJzY9gQL6ltGTd7PVKWiBa1dLEvJwo3ILsey-7LAu8f4kJY/pub?w=960&h=720