> For the complete documentation index, see [llms.txt](https://docs.galaxyhub.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.galaxyhub.ai/how-it-works/contract-scanner.md).

# Contract Scanner

Smart contracts are the engine of Web3, but also one of its main sources of attack. NOVA's **Contract Scanner** allows you to analyze contracts directly from the extension before granting permissions or signing any transaction.

When scanning a contract, **NOVA** checks:

* The overall security level
* Whether it contains risky functions (such as `transferFrom`, `approve`, `selfDestruct`, etc.)
* The contract's reputation (history, creators, users who have used it)
* Whether it has been used in known scams or malicious strategies

NOVA not only reports, but also explains (if AI Assistant is enabled) why a contract is risky, what could happen if you sign it, and how to prevent a common error like **infinite approval**.

**Use Cases:**

* *Auditing new token contracts before buying*
* *Checking if a staking contract has backdoors*
* *Detecting contracts with "fake claims" or fraudulent migrations*


---

# 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.galaxyhub.ai/how-it-works/contract-scanner.md?ask=<question>&goal=<endgoal>
```

`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.