- Hacken
- Audits
- griffin-ai-ag
- [SCA] Griffin AI | Token | Sep2025
Introduction
We express our gratitude to the Griffin AI AG team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Griffin AI is an advanced framework designed for the integration of Large Language Models (LLMs) and AI agents within the blockchain and Web 3.0 domains. Griffin AI enables developers to integrate their AI solutions into the Web 3.0 environment. The Griffin AI protocol simplifies the process of developing, deploying, and monetizing AI agents by offering seamless access to both centralized and distributed AI services.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for Griffin AI AG |
| Audited By | Kornel Światłowski, Khrystyna Tkachuk |
| Approved By | Ivan Bondar |
| Website | https://www.griffinai.io/→ |
| Changelog | 26/09/2025 - Final Report |
| Platform | Ethereum, Binance Smart Chain (BSC) |
| Language | Solidity |
| Tags | ERC20, Omnichain Fungible Token |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Griffin AI AG
- Audited By
- Kornel Światłowski, Khrystyna Tkachuk
- Approved By
- Ivan Bondar
- Website
- https://www.griffinai.io/→
- Changelog
- 26/09/2025 - Final Report
- Platform
- Ethereum, Binance Smart Chain (BSC)
- Language
- Solidity
- Tags
- ERC20, Omnichain Fungible Token
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://github.com/griffinai-io/gain-oft-token→ |
| Commit | d85b159f5adf5848cfd4907aa33b6c8996a8933c |
| BSC deployment address | 0xa890F8BA60051ec8a5B528F056DA362Ba208a96F |
| Ethereum deployment address | 0xe0ff1b0584d63cb74a78537f1fe0d17564e741d4 |
Review Scope
- Commit
- d85b159f5adf5848cfd4907aa33b6c8996a8933c
- BSC deployment address
- 0xa890F8BA60051ec8a5B528F056DA362Ba208a96F
- Ethereum deployment address
- 0xe0ff1b0584d63cb74a78537f1fe0d17564e741d4
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
{Finding_Table?columns=title,severity,status&setting.filter.type=Vulnerability}
Documentation quality
Functional requirements are partially missed.
The technical description is detailed.
Run instructions are provided.
Technical specification is provided.
The NatSpec documentation is sufficient.
Code quality
The code leverages OpenZeppelin and LayerZero contracts and follows established patterns.
The development environment is configured.
Test coverage
Code coverage of the project is 100% (branch coverage).
Deployment and basic user interactions are covered with tests.
Interactions by several users are not tested thoroughly.
System Overview
GainOFT is an Omnichain Fungible Token (OFT) that mints its entire initial supply to the deployer. No additional minting is permitted. The implementation uses the LayerZero V2 OFT standard, which enables the token to exist across multiple blockchains while maintaining a unified supply. This is achieved by debiting tokens from the sender on the source chain and crediting the same amount of tokens to the receiver on the destination chain.
Privileged roles
The contract owner receives the total supply on contract deployment and can modify OFT configurations, such as adjusting library or DVN parameters, overriding default libraries, whitelisting remote OFT addresses, assigning a different delegate address, and setting mandatory execution options.
Potential Risks
The project concentrates token minting during deployment into a single address, with no additional minting possible afterward (the only exception being cross-chain transfers, where new tokens are minted on the destination chain). Concentrating the total supply in one address increases the risk of fund mismanagement or theft, especially if the private key storage is compromised. Distributing the tokens across multisig wallets would help mitigate this risk.
The project is fully or partially centralized, introducing single points of failure and control. This centralization can lead to vulnerabilities in decision-making and operational processes, making the system more susceptible to targeted attacks or manipulation.
The functioning of the system significantly relies on specific external contract _lzEndpoint which is the designated LayerZero endpoint contract. The LayerZero Endpoint is the immutable, permissionless protocol entrypoint for sending and receiving omnichain messages. Any flaws or vulnerabilities in this contract adversely affect the audited project, potentially leading to security breaches or loss of funds.
Findings
No vulnerabilities were foundAppendix 1. Definitions
Severities
When auditing smart contracts, Hacken is using a risk-based approach that considers Likelihood, Impact, Exploitability and Complexity metrics to evaluate findings and score severities.
Reference on how risk scoring is done is available through the repository in our Github organization:
Severity | Description |
|---|---|
Critical | Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation. |
High | High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation. |
Medium | Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category. |
Low | Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution. |
Severity
- Critical
Description
- Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.
Severity
- High
Description
- High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.
Severity
- Medium
Description
- Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.
Severity
- Low
Description
- Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution.
Potential Risks
The "Potential Risks" section identifies issues that are not direct security vulnerabilities but could still affect the project’s performance, reliability, or user trust. These risks arise from design choices, architectural decisions, or operational practices that, while not immediately exploitable, may lead to problems under certain conditions. Additionally, potential risks can impact the quality of the audit itself, as they may involve external factors or components beyond the scope of the audit, leading to incomplete assessments or oversight of key areas. This section aims to provide a broader perspective on factors that could affect the project's long-term security, functionality, and the comprehensiveness of the audit findings.
Appendix 2. Scope
The scope of the project includes the following smart contracts from the provided repository:
Scope Details | |
|---|---|
| Repository | https://github.com/griffinai-io/gain-oft-token→ |
| Commit | d85b159f5adf5848cfd4907aa33b6c8996a8933c |
| BSC deployment address | 0xa890F8BA60051ec8a5B528F056DA362Ba208a96F |
| Ethereum deployment address | 0xe0ff1b0584d63cb74a78537f1fe0d17564e741d4 |
| Whitepaper | https://www.griffinai.io/whitepaper→ |
| Requirements | ./README.md |
| Technical Requirements | ./README.md |
Scope Details
- Commit
- d85b159f5adf5848cfd4907aa33b6c8996a8933c
- BSC deployment address
- 0xa890F8BA60051ec8a5B528F056DA362Ba208a96F
- Ethereum deployment address
- 0xe0ff1b0584d63cb74a78537f1fe0d17564e741d4
- Whitepaper
- https://www.griffinai.io/whitepaper→
- Requirements
- ./README.md
- Technical Requirements
- ./README.md
Assets in Scope
Appendix 3. Additional Valuables
Additional Recommendations
The smart contracts in the scope of this audit could benefit from the introduction of automatic emergency actions for critical activities, such as unauthorized operations like ownership changes or proxy upgrades, as well as unexpected fund manipulations, including large withdrawals or minting events. Adding such mechanisms would enable the protocol to react automatically to unusual activity, ensuring that the contract remains secure and functions as intended.
To improve functionality, these emergency actions could be designed to trigger under specific conditions, such as:
Detecting changes to ownership or critical permissions.
Monitoring large or unexpected transactions and minting events.
Pausing operations when irregularities are identified.
These enhancements would provide an added layer of security, making the contract more robust and better equipped to handle unexpected situations while maintaining smooth operations.