> For the complete documentation index, see [llms.txt](https://canza.gitbook.io/asynchronous-liquidation-auction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canza.gitbook.io/asynchronous-liquidation-auction/diagrams.md).
# Diagrams
**Figure 1:** Depicts the relationship between the ALA user, the aggregated network of liquidation (Open Auction Pool), and their interaction with the smart contract management system (Controller Contract) and the DeFi Protocol where the liquidation events occur. The ALA user's activities are limited to deposits (inflows) and claims/withdrawals (outflows). The Controller Contract functions as the system manager, creating and managing liquidation pools, overseeing the state of liquidations, and directing collateral flow across the specific DeFi protocol and its associated ALA liquidation pools.
**Figure 2:** Depicts the overall logic flow of the ALA implementation. Once a liquidation event is authenticated by the Controller Contract, the system proceeds with liquidations by performing a balance check and moving sequentially through pools with available liquidity. This process depends on the specific network and associated DeFi protocol, following the principle of liquidating smaller pools first before progressing to larger ones. This approach ensures an efficient liquidation process and prevents cascading effects.
**Figure 3:** Depicts the relationship and process flow across all smart contracts, from the DeFi protocols contracts to the ALA controller contract managing the liquidation process. This diagram also illustrates the collateral flow across the liquidation pools to the designated DeFi protocol in the liquidation state.
**Figure 4:** Depicts cross-chain liquidation across AVAX and SOL pools for the Baki.exchange Protocol
**Figure 5:** Depicts cross-chain liquidation across different networks while upholding the ALA liquidation mechanism.
---
# 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://canza.gitbook.io/asynchronous-liquidation-auction/diagrams.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.