Arca by Smart-Chain has 1 public audit report from CertiK; dated 23 Jan 2023; 1 critical finding, marked fixed by the firm.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
5 findings are still open or acknowledged in the firms’ reports: 1 high, 4 low (4 open, 1 acknowledged).
Centralization Related Risks
Arca by Smart-Chain - Audit · CertiK · 23 Jan 2023 · Report ↗
Incompatibility with Deflationary Tokens
Arca by Smart-Chain - Audit · CertiK · 23 Jan 2023 · Report ↗
Lack of Check the Number of Redeemed Assets
Arca by Smart-Chain - Audit · CertiK · 23 Jan 2023 · Report ↗
Missing Emit Events
Arca by Smart-Chain - Audit · CertiK · 23 Jan 2023 · Report ↗
Missing Zero Address Validation
Arca by Smart-Chain - Audit · CertiK · 23 Jan 2023 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Arca by Smart-Chain - Audit | Security firm: CertiK | Date: | Scope: Files listed | 1 critical finding, fixed | Findings: 1 critical · 1 high · 4 low 1 fixed · 1 acknowledged · 4 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 1 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 4 | 0 | 0 |
When transferring deflationary ERC20 tokens, the input amount may not be equal to the received amount due to the charged transaction fee. For example, if a user sends 100 deflationary tokens (with a 10% transaction fee), only 90 tokens actually arrived to the contract. However, a failure to discount such fees may allow the same user to withdraw 100 tokens from the contract, which causes the contract to lose 10 tokens in such a transaction. Reference: https://thoreum-finance.medium.com/what-exploit-happened-today-for-gocerberus-and-garuda-also-for-lokum-ybear-piggy-caramelswap-3943ee23a39f ```solidity=125 IERC20(indexedAssetAddress).safeTransferFrom( msg.sender, address(this), amountOfAssetToRedeem ); ``` - Transferring tokens by `amountOfAssetToRedeem`. ```solidity=130 IERC20(indexedAssetAddress).burn(amountOfAssetToRedeem); ``` - The `amountOfAssetToRedeem` appears to be used for bookkeeping purposes without compensating the potential transfer fees. - Note: `burn` is an external function and its behavior wasn't evaluated.
Open the reportIn the `redeemBasketForAssetAmount` function, a user can redeem assets by invoking the `redeemBasketForAssetAmount` function and burning the corresponding `indexedAssetAddress` token: ```solidity=104 function redeemBasketForAssetAmount(uint256 amountOfAssetToRedeem) external nonReentrant { ... IERC20(indexedAssetAddress).burn(amountOfAssetToRedeem); ... IERC20(assetBasketAddress).safeTransfer( msg.sender, redeemAmountForAsset ); ... ``` However, when the `redeemAmountForAsset` for each asset becomes zero, the `redeemBasketForAssetAmount` becomes a kind of `burn` function. A similar scenario happened in the `ArcaERC721` contract for the `redeemBasketForAssetAmount` function.
Open the reportThere should always be events emitted in the sensitive functions that are controlled by centralization roles.
Open the reportAddresses should be checked before assignment or external call to make sure they are not zero addresses. ```solidity=97 indexedAssetAddress = initialIndexedAssetAddress; ``` - `initialIndexedAssetAddress` is not zero-checked before being used. --- ```solidity=186 indexedAssetAddress = newIndexedAssetAddress; ``` - `newIndexedAssetAddress` is not zero-checked before being used. --- ```solidity=196 collectiveTreasuryAddress = newCollectiveTreasuryAddress; ``` - `newCollectiveTreasuryAddress` is not zero-checked before being used. --- ```solidity=98 indexedAssetAddress = initialIndexedAssetAddress; ``` - `initialIndexedAssetAddress` is not zero-checked before being used. --- ```solidity=189 indexedAssetAddress = newIndexedAssetAddress; ``` - `newIndexedAssetAddress` is not zero-checked before being used. --- ```solidity=199 collectiveTreasuryAddress = newCollectiveTreasuryAddress; ``` - `newCollectiveTreasuryAddress` is not zero-checked before being used.
Open the reportThe reports name a repository or files. Open a report to see its scope.
Trustblock holds 1 public audit report for Arca by Smart-Chain, dated 23 Jan 2023. The latest is by CertiK (“Arca by Smart-Chain - Audit”).
CertiK wrote the report Trustblock holds for Arca by Smart-Chain.
5 findings are still open or acknowledged in the firms’ reports: 1 high, 4 low (4 open, 1 acknowledged). Of 1 critical finding: marked fixed by the firm. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="arca-by-smart-chain"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us