> For the complete documentation index, see [llms.txt](https://docs.mutuum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mutuum.com/protocol-stability/address-screening-and-wallet-blocking.md).
# Address Screening and Wallet Blocking
Mutuum anticipates leveraging external blockchain intelligence services to prevent interactions from wallets suspected of engaging in illicit activities. These services combine on-chain analytics with real-world investigative data to identify behaviors associated with financial crimes, fraud, or other prohibited conduct. If a wallet is flagged, it may be blocked from accessing Mutuum’s front-end, helping ensure compliance with applicable regulations and maintaining a safe environment for legitimate users.
When users attempt to connect a wallet, Mutuum’s interface sends the wallet address to a proxy endpoint maintained by the protocol’s infrastructure. This endpoint forwards the address directly to the third-party screening service without storing additional user metadata or IP information. The screening platform evaluates whether the address is connected to potentially unlawful or restricted activities. If a high-risk status is detected, the wallet is denied access to the protocol’s user interface.
* **No IP Sharing**: Mutuum does not share user IP addresses with the third-party intelligence provider.
* **No Extra Metadata**: Aside from the wallet address itself, no other personal or transactional data is transmitted.
* **Regulatory Compliance**: By blocking flagged addresses, the protocol aims to align with relevant laws and regulations in various jurisdictions, reducing potential liability and safeguarding user funds against misuse.
---
# 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://docs.mutuum.com/protocol-stability/address-screening-and-wallet-blocking.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.