> For the complete documentation index, see [llms.txt](https://tristero.gitbook.io/hourglass-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tristero.gitbook.io/hourglass-docs/layerzero.md). # LayerZero Hourglass is designed to be a trustless protocol, which means that users can interact with it without needing to trust any third parties for the core functionalities. However, there are certain assumptions around LayerZero. #### Assumptions 1. **LayerZero Uptime**: Users should trust that LayerZero messages, once sent, will be reliably delivered to their intended destination. 2. **Remote Address Configuration**: Users should trust that the contract owner has correctly configured the LayerZero remote address. #### Non-Blocking Standard App The protocol adheres to the non-blocking standard application (app) model. This ensures that transactions and messages among chains are processed efficiently and securely. #### LayerZero Endpoints We set remote addresses based on the guidelines provided in the [LayerZero Technical Reference](https://layerzero.gitbook.io/docs/technical-reference/testnet/testnet-addresses#layerzero-endpoints-testnet). #### Why These Assumptions Matter While the Hourglass protocol itself is designed to minimize trust requirements, these LayerZero assumptions are essential for ensuring that cross-chain messages and transactions are executed as expected. Users should be aware of these assumptions when interacting with the protocol. #### A Note on Recovery If for some reason these conditions fail and the message can not be re-delivered, we can activate a recovery system. If this does happen, please contact .