> For the complete documentation index, see [llms.txt](https://fagot.gitbook.io/fagot.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fagot.gitbook.io/fagot.ai-docs/markdown.md).

# HOW $FAGOT WORKS

$FAGOT is a <mark style="background-color:green;">**decentralized, open sourced, AI-powered blockchain transaction verification platform**</mark>

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

$FAGOT is engineered to address four common blockchain interaction scenarios, each with tailored background data retrieval and risk analysis workflows:

1. **Smart Contract Interaction (Type 1):**
   * **User Action:** Initiating a transaction to interact with a smart contract.
   * **Required Data:**
     * Contract code
     * Contract ABI
     * Transaction data (tx data)
   * **Analysis Process:**\
     The system retrieves the contract code and ABI using our dedicated “Contract Data Retrieval Tool” and then combines this information with the user’s transaction data to perform a comprehensive audit.
2. **ERC20 Token Operations (Type 2):**
   * **User Action:** Executing token operations such as approvals or transfers.
   * **Required Data:**
     * Historical transaction records of the target address
     * If the target is a smart contract, its contract code and ABI are also fetched
   * **Analysis Process:**\
     Our “Transaction History Retrieval Tool” queries the target address’s past transactions. If the target is identified as a smart contract, the “Contract Data Retrieval Tool” is additionally employed to analyze the contract’s code and ABI.
3. **ETH Transfer (Type 3):**
   * **User Action:** Initiating an ETH transfer.
   * **Required Data:**
     * Historical transaction records of the target address
     * If the target is a smart contract, an analysis of its contract code and ABI is also performed
   * **Analysis Process:**\
     Similar to ERC20 operations, the system examines the target address using our Transaction History Retrieval Tool and, if necessary, the Contract Data Retrieval Tool.
4. **Signature Request (Type 4):**
   * **User Action:** Signing a message (e.g., for authorization or granting permissions).
   * **Required Data:**
     * The raw content of the message to be signed
   * **Analysis Process:**\
     The “Message Analysis Tool” extracts and examines the raw message content, assessing whether the action could impact your wallet assets.