> For the complete documentation index, see [llms.txt](https://ethsignals.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ethsignals.gitbook.io/wiki/tennagraph/specs/exporting-database-to-github.md). # Exporting Database to Github ### 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ethsignals.gitbook.io/wiki/tennagraph/specs/exporting-database-to-github.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.