# Communication

An important point to make the service run smoothly was to make fault-resilient communication between each entity in our protocol. 

From smart contract to platform, or from platform to backend service, we took time to create a robust inter-related communication protocol. 

Each stage of a loan request is handled by multiple levels of checkups to avoid the loss of any assets and the closing of each loan. Therefore, communication acknowledgements were placed between each entity. \
\
These entities are the SmartContract, The Bi-level Web3 API we’ve created, The Front-end platform, the back-end services and the Database.

<figure><img src="/files/PTUjC0HRKUc3ktWL8C1L" alt=""><figcaption></figcaption></figure>


---

# 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://nftuloan.gitbook.io/nftuloan-whitepaper/protocol/communication.md?ask=<question>
```

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.