Skip to content

Commit

Permalink
GITBOOK-50: change request with no subject merged in GitBook
Browse files Browse the repository at this point in the history
  • Loading branch information
Victoria Calmon authored and gitbook-bot committed Nov 3, 2023
1 parent 21a4b8c commit 60ebe02
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions protocol-concepts/asset-exchanges/broker.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
# Broker

The **Broker** is responsible for orchestrating swaps in the Mento Protocol. It does that by fulfilling three main responsibilities: 
The **Broker** is responsible for orchestrating swaps in the Mento protocol. It does that by fulfilling three main responsibilities: 

* **Discoverability**: It maintains a list of all [**exchange providers**](exchange-providers.md) registered in the system.
* **Treasury management:** It has spending rights on the [**Reserve**](../reserve.md) and can mint and burn any stable asset in the system, thus it is responsible for moving around assets during a trade.
* **Treasury management:** It has spending rights on the [**Mento Reserve**](../reserve.md) and can mint and burn any stable asset in the system, thus it is responsible for moving around assets during a trade.
* **Safety**: In service of [stability](../stability.md), it enforces [trading limits](trading-limits.md) in the protocol, constraining the volume of assets that can be traded over time.

While it is responsible for moving around assets during a swap, it doesn't know how to price swaps. For that, it relies on [**exchange providers**](exchange-providers.md). These abstract components implement a unified interface and can be plugged into the **Broker** to provide exchanges between two or more assets. The first exchange provider that we implement is the [BiPoolManager](../../developers/smart-contracts/bipoolmanager.md).  
While it is responsible for moving around assets during a swap, it doesn't know how to price swaps. For that, it relies on [**exchange providers**](exchange-providers.md). These abstract components implement a unified interface and can be plugged into the **Broker** to provide exchanges between two or more assets. The first exchange provider implemented is the [BiPoolManager](../../developers/smart-contracts/bipoolmanager.md).  

0 comments on commit 60ebe02

Please sign in to comment.