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

# Chains

- [Solana](https://docs.triton.one/chains/solana.md)
- [Streaming](https://docs.triton.one/chains/solana/streaming.md)
- [Streaming Troubleshooting Checklist](https://docs.triton.one/chains/solana/streaming/streaming-troubleshooting-checklist.md)
- [Preconfirmations gRPC](https://docs.triton.one/chains/solana/preconfirmations-grpc.md): Triton Preconfs streams preconfirmed Solana transactions over gRPC, from the two block production systems that emit them: Harmonic and BAM.
- [Geyser](https://docs.triton.one/chains/solana/geyser.md)
- [Token Program](https://docs.triton.one/chains/solana/token-program.md): There are multiple methods to choose from when querying data from the Token Program.
- [Archival Data Access](https://docs.triton.one/chains/solana/old-faithful-historical-archive-1.md)
- [Improved Priority Fees API](https://docs.triton.one/chains/solana/improved-priority-fees-api.md)
- [For RPC Providers](https://docs.triton.one/chains/solana/improved-priority-fees-api/for-rpc-providers.md)
- [Transaction handling](https://docs.triton.one/chains/solana/cascade.md): Solana transaction handling advice.
- [Transaction Submission API](https://docs.triton.one/chains/solana/cascade/transaction-submission.md): Direct HTTP endpoint for submitting Solana transactions through Cascade without JSON-RPC overhead.
- [Transaction sending advice](https://docs.triton.one/chains/solana/cascade/sending-txs.md): Recommendations to optimize transaction delivery through our Cascade network.
- [Web3JS Socket/Connection Issues](https://docs.triton.one/chains/solana/web3js-socket-connection-issues.md): Dealing with Socket/Connection issues in Web3JS
- [Solana v2.0: Deprecated RPC Methods](https://docs.triton.one/chains/solana/deprecated-calls-solana-2.0.md)
- [Unsupported Account Queries](https://docs.triton.one/chains/solana/unsupported-account-queries.md): Account-related JSON-RPC methods that are disabled, restricted, or require dedicated infrastructure on Triton One shared mainnet RPC.
- [Agave - AccountsDB: Storage Files shrinking process](https://docs.triton.one/chains/solana/agave-accountsdb-storage-files-shrinking-process.md)
- [getTransactionsForAddress](https://docs.triton.one/chains/solana/gettransactionsforaddress.md): Transaction history API for retrieving address activity with server-side filtering, configurable sort order, pagination, and optional full transaction details.
- [Shred Streaming](https://docs.triton.one/chains/solana/shred-streaming.md)
- [SUI](https://docs.triton.one/chains/sui.md)
- [Walrus](https://docs.triton.one/chains/sui/walrus.md)
- [gRPC](https://docs.triton.one/chains/sui/grpc.md)
- [Archival Storage and Services](https://docs.triton.one/chains/sui/archival-storage-and-services.md)
- [GraphQL](https://docs.triton.one/chains/sui/graphql.md)
- [Monad](https://docs.triton.one/chains/monad.md): Monad is a Layer-1 blockchain delivering high performance, decentralization, and EVM compatibility with 10.000 TPS, 0.8s finality, and 0.4s block times
- [Pythnet](https://docs.triton.one/chains/pythnet.md)
- [Others](https://docs.triton.one/chains/others.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.triton.one/chains.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.