> For the complete documentation index, see [llms.txt](https://superfluid.gitbook.io/superfluid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://superfluid.gitbook.io/superfluid/resources/superfluid-on-ethereum-mainnet.md). # Superfluid on Ethereum Mainnet Ethereum L1 is a different environment from other places that Superfluid is been deployed. This is due to the fact that performing any operation on L1 is much more expensive in terms of gas cost than it is on other networks. ### Minimum Deposits Keep in mind that the [Superfluid sentinel network](/superfluid/sentinels/liquidations-and-toga.md) is responsible for closing Superfluid streams when an account's balance hits zero before they close it themselves. To cover additional costs incurred by sentinels, tokens on L1 have been deployed with minimum deposit values. This means that the buffer on each of these tokens will not always be calculated as 4 hours worth of the stream as it is on lower cost networks. You can see current parameters on buffer amounts for Ethereum L1 [here](/superfluid/sentinels/liquidations-and-toga.md). ### Using Ethereum Mainnet in Superfluid Tooling Additionally, while Superfluid is an open smart contract framework, Ethereum mainnet is not currently openly supported across our developer tooling. --- # 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://superfluid.gitbook.io/superfluid/resources/superfluid-on-ethereum-mainnet.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.