> For the complete documentation index, see [llms.txt](https://airbotfarm.gitbook.io/airbot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://airbotfarm.gitbook.io/airbot/how-airbot-works/zksync.md). # zkSync zkSync is a layer-2 scaling solution for Ethereum that employs zkRollups, a zero-knowledge proof technology, to enhance the network's scalability. By bundling numerous transactions off-chain into a single proof submitted to Ethereum, zkSync drastically reduces fees and transaction times while maintaining security, making it suitable for various applications like DeFi and NFTs. AIRBOT has seamlessly integrated automation for zkSync, a prominent layer-2 network.\ \ Currently, AIRBOT effectively automates the following zkSync dApps: * Bridge: zkSync Portal * Swap: SyncSwap, Mute, Maverick * Mint: Tevaera * Liquidity: SyncSwap, Mute * Lending: Eralend * Stake: Mute Our automation handles actions such as bridging, swapping, minting NFTs, yield farming, lending, and staking within the zkSync protocols. --- # 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://airbotfarm.gitbook.io/airbot/how-airbot-works/zksync.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.