Fracton Protocol contract 0x7a83…1315 on Ethereum

0x7a83ff237e7870d8d6c3485920ebe654d2841315

As of 21 Nov 2026, Trustblock’s record holds 0x7a83ff237e7870d8d6c3485920ebe654d2841315 on Ethereum as a contract of Fracton Protocol. 1 audit report on Trustblock lists this address: CertiK, 30 Jan 2023. 9 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on Ethereum.

AuditSecurity firmDateCommit named in the reportReport
Fracton ProtocolCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports9

1 High, 1 Medium, 7 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighCentralization Risks in FractonFFT.solFracton Protocol · CertiKAcknowledged

In the contract `FractonFFT` the role `IFractonTokenFactory(_factory).getDAOAddress()` has authority over the following functions: - `updateFee()` - `batchExcludeFromFee()` - `includeInFee()` - `excludeFromFee()` Any compromise to the `IFractonTokenFactory(_factory).getDAOAddress()` account may allow the hacker to take advantage of this authority and 1) Change the `vaultPercent` and `pfVaultPercent` variables, that decide the amount of tax deducted on transfer of tokens, by calling the `updateFee()` function. 2) Exempt multiple users at once from paying the tax by using the `batchExcludeFromFee()` function. 3) Include an exempted user to pay tax on transfer of tokens by using the `includeInFee()` function. 4) Exempt a user from the tax on transfer of tokens using the `excludeFromFee()` function. --- In the contract `FractonFFT` the role `IFractonTokenFactory(_factory).getSwapAddress()` has authority over the `swapmint()` function. Any compromise to the `IFractonTokenFactory(_factory).getSwapAddress()` account may allow the hacker to take advantage of this authority and mint as many tokens as they want and send them to any address.

The audit on Trustblock · Open the report
MediumMissing ChecksFracton Protocol · CertiKAcknowledged

1) The parameter `vaultPercent_` and `pfVaultPercent_` do not have an upper bound check. This means there is no upper bound on the tax that can be charged on a transfer of tokens. Moreover, the `transferFrom()` and `transfer()` function do not check if the tax deducted from the `value` is greater than the `value` itself or not. Since the tax does not have any upper limit, it is possible to have the `vaultFee` or `pfVaultFee` greater than the `value` being transferred. 2) In the function `multiTransfer()`, it is not checked if the length of the `receivers[]` array is equal to the length of the `amounts[]` array.

The audit on Trustblock · Open the report
LowImproper Usage of `public` and `external` TypeFracton Protocol · CertiKOpen

The `public` functions `multiTransfer()`, `transferFrom()`, and `excludeFromFee()` are never called by the contract and could be declared as `external`.

The audit on Trustblock · Open the report
LowThird Party DependencyFracton Protocol · CertiKOpen

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assume their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. The contract `FractonFFT` interacts with third party contract with `IFractonTokenFactory` interface via `_factory`.

The audit on Trustblock · Open the report
LowTypoFracton Protocol · CertiKOpen

The name of the variable should be `swap`, to keep it consistent with the comment in the require statement.

The audit on Trustblock · Open the report
LowUnnecessary Use of SafeMathFracton Protocol · CertiKOpen

The `SafeMath` library is used unnecessarily. With Solidity compiler versions 0.8.0 or newer, arithmetic operations will automatically revert in case of integer overflow or underflow.

The audit on Trustblock · Open the report
LowUnused ModifierFracton Protocol · CertiKOpen

The modifier `onlyOwner()` is not used in the contract.

The audit on Trustblock · Open the report
LowUsage of Magic NumberFracton Protocol · CertiKOpen

The magic number `10000` is used instead of a constant, which reduces the code readability.

The audit on Trustblock · Open the report
LowVariables That Could Be Declared as ImmutableFracton Protocol · CertiKOpen

The variable `_factory` assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

The audit on Trustblock · Open the report

The Fracton Protocol security record · Every Fracton Protocol address · This address on the explorer