> For the complete documentation index, see [llms.txt](https://docs.slingshotdao.com/slingshot-dao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slingshotdao.com/slingshot-dao/tokenomics/slingshot-l3.md).

# Slingshot L3

Slingshot is deployed on it's own dedicated [Arbitrum Orbit ](https://arbitrum.io/orbit)Layer 3 chain. On this chain $SLING is also the native gas token.

This allows for **incredibly fast** and **cost-effective** transactions, with good security guarantees, ultimately rolling up to the Ethereum mainnet (layer 1).

Transactions are so cheap, Slingshot sponsors the gas payments for all transactions on its layer 3 chain. 

This allows users to interact with Slingshot, without needing to worry about slow transactions or gas fees.

## Chain Details

**Chain ID:** 33401

**RPC**: rpc.slingshotdao.com

**Block explorer:** explore.slingshotdao.com

## Chainlist Listing

{% embed url="<https://chainlist.org/chain/33401>" %}


---

# 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.slingshotdao.com/slingshot-dao/tokenomics/slingshot-l3.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.