# Incident Response (Blacklist) ### Context Certain token contracts, such as USDC, implement a blocklist that allows the owner to freeze funds in specific accounts. If any of the deployed sales or auction contracts are blocklisted from the bid token, legitimate investors' funds will be locked. ### Options If this occurs, we have no options to resolve the issue single-handedly. What we should do in this case is contact the stable coin issuer to learn why they blocked this address, explain the implications to them, and ask for an unblock since they are blocking more than a single individual. ### Plan * Contact stable coin issuer to explore options. * Inform the users, either before or after the stable coin issuer provides an answer. An announcement should be made, preferably in a private manner, to all affected investors, informing them that issuer has blocked our sale contract and that we are working to resolve the situation. --- # 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://legion-1.gitbook.io/legion/security/incident-response-blacklist.md?ask= ``` 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.