# Garbi Protocol {% hint style="info" %} Garbi Protocol is A decentralized exchange for stablecoins that uses an automated market maker (AMM) to manage liquidity on Arbitrum. It is running here: {% endhint %} At the time we started to learn about the blockchain, we got a concept about Garbi Protocol, which used to build all core of blockchain network. It is a machine that will reward anyone who helps it run to process a job (math), a very cool idea, so we picked this name to build our Garbi Protocol version with the Logo as a ROBOT Garbi Protocol now has 5 sub-products: GarbiSwap (Stablecoin AMM), GarbiFarms, Garbi Equity Certificate (GEC), Garbi Stable Bridge, and Garbi Game Garbi Swap (our main product for now), Liquidity Providers will not earn only from trading fees. The protocol is also supplied to AAVE v3 protocol or other DeFi pools to create more interest. Garbi Swap Contract will move the liquidity around to do both works (trading and farming)
## Why Arbitrum? When we found the Arbitrum network, it is a nice blockchain layer 2 networks that supported Solidity (cheaper, faster compared with ETH) Arbitrum is a Layer 2 solution with a mission to help ease the burden on Ethereum by reducing the number of transactions on the Ethereum network and reducing transaction fees. The platform is designed to allow developers to easily bring dApps from Ethereum to Arbitrum. While still benefiting from Ethereum's security. Besides, Arbitrum owns a transaction speed of 40,000 transactions/second. --- # Agent Instructions: 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: ``` GET https://garbi-protocol.gitbook.io/docs/garbi-protocol/garbi-protocol.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.