- Hacken
- Audits
- griffin-ai-ag
- [SCA] Griffin AI AG | Griffin-Ai-Token | Nov2024
Audit name:
[SCA] Griffin AI AG | Griffin-Ai-Token | Nov2024
Date:
Dec 18, 2024
Table of Content
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 a decentralized platform that enables users to build, deploy, and monetize AI agents for blockchain applications.
Client | |
|---|---|
| Name | Griffin AI AG |
| Company registration code | FL-0002.731.888-1 |
| Address | Birkenweg 6, 9490, Vaduz, Liechtenstein |
| Website | https://www.griffinai.io/→ |
Client
- Name
- Griffin AI AG
- Company registration code
- FL-0002.731.888-1
- Address
- Birkenweg 6, 9490, Vaduz, Liechtenstein
- Website
- https://www.griffinai.io/→
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for Griffin AI AG |
| Audited By | Adam Idarrha |
| Approved By | Viktor Raboshchuk |
| Changelog | 22/11/2024 - Preliminary Report , 18/12/2024 - Final Report |
| Platform | Ethereum |
| Language | Solidity |
| Tags | ERC20, Fungible Token |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Griffin AI AG
- Audited By
- Adam Idarrha
- Approved By
- Viktor Raboshchuk
- Changelog
- 22/11/2024 - Preliminary Report , 18/12/2024 - Final Report
- Platform
- Ethereum
- Language
- Solidity
- Tags
- ERC20, Fungible Token
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://github.com/griffinai-io/griffin-ai-token→ |
| Commit | e504a35→ |
Review Scope
- Commit
- e504a35→
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
Documentation quality
Functional requirements are fully provided.
Technical description are fully provided.
Code quality
The code mostly conforms with the Solidity Style Guide.
The code does follow best practices for readability & gas efficiency.
The development environment is configured.
System Overview
Griffin AI is a simple ERC20 token protocol with the following contracts:
Griffin Token — simple ERC-20 token. It has the following attributes:
Name: Defined during deployment.
Symbol: Defined during deployment.
Decimals: Defined during deployment.
Total supply: Capped at deployment.
Mint Functionality: Not implemented or exposed, ensuring no new tokens can be created after deployment.
Burn Functionality: Only token holders can burn their own tokens; tokens owned by others cannot be burned.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2024-7315 | Immutable Variables Lack Mutability Modifier | fixed | Observation | |
| F-2024-7313 | Floating Pragma | fixed | Observation |
Appendix 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/griffin-ai-token→ |
| Commit | b82722b5dca9e39c9b33f07dc89dcbb14c12e047 |
| Whitepaper | |
| Requirements | |
| Technical Requirements | Technical Specification for GriffinToken Smart Contract-141124-151740.pdf→ |
Scope Details
- Commit
- b82722b5dca9e39c9b33f07dc89dcbb14c12e047
- Whitepaper
- Requirements
- Technical Requirements
- Technical Specification for GriffinToken Smart Contract-141124-151740.pdf→