> For the complete documentation index, see [llms.txt](https://docs.topledger.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.topledger.xyz/data-tables/solana-data.md).

# Solana Data

## Introduction

[Solana](https://solana.com/) is a public, open-source blockchain that aims to deliver scalability and support smart contracts without sacrificing decentralization and security. It accomplishes this through a novel timestamp mechanism called [Proof-of-History](https://medium.com/solana-labs/proof-of-history-a-clock-for-blockchain-cf47a61a9274) (PoH). Using PoH, the network can order and batch transactions before they’re processed through a Proof-of-Stake (PoS) mechanism.

At full capacity, the Solana network will generate 1gb/s \* 365 days = 4 petabytes of data every year. This is huge and requires a solid backend infrastructure for performing day to day analytics. 

Also, the web3 analytics will move from SQL to higher order in near future and thus any analytics infrastructure on Solana should have the capability to accommodate these advanced use cases as well.

Here are the tables available on Top Ledger for raw Solana blockchain data.


---

# 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://docs.topledger.xyz/data-tables/solana-data.md?ask=<question>&goal=<endgoal>
```

`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.