As of 3 Nov 2026, ShadowFi has 2 audit reports by 2 security firms on Trustblock; the latest is by Cyberscope, dated 20 May 2024. Those reports list 2 open critical findings. It also holds 1 deployed contract on 1 chain.
Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| ShadowGold | Security firm: Cyberscope | Date: | Scope: 1 address on Polygon (POS) | 2 open critical findings | Open · cyberscope.io |
| Shadowfi | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 2 | 0 | 0 |
| High | 0 | 1 | 0 |
| Medium | 2 | 0 | 0 |
| Low | 28 | 0 | 8 |
The report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportAccessing storage variables in a loop can be costly in terms of gas consumption. As the amount of holders grow, the more expensive it becomes to call these functions.
Open the reportThe following functions are never called internally within the contract and should have external visibility: In `[ShadowFi.sol]`: - `authorizeFor()` - `authorizeForMultiplePermissions()` - `unauthorizeFor()` - `unauthorizeForMultiplePermissions()` - `isAuthorizedFor()` - `transferOwnership()` - `getPermissionNameToIndex()` - `isLocked()` - `lockPermission()` - `unlockPermission()` - `burn()` --- In `[ShadowFiLiquidityVault.sol]`: - `transferOwnership()` - `endLock()` - `extendLockTime()` - `withdrawBNB()` - `withdrawTokens()` - `shadowStrike()` - `shadowBurst()` - `getLPOwnershipPercent()` - `getLiquidTokens()` - `getLiquidPercent()` - `getShadowStrikeAmount()` - `getShadowBurstAmount()` - `injectBNB()` - `getLockTime()`
Open the reportFunctions should be grouped together based on their functionality. For example: - All centralized user functions should be listed together. - All trading or swapping mechanisms should be listed together.
Open the reportThere are three different ways to gain access to certain admin functions: - `authorized` - `authorizedFor` - `onlyToken` This can make it difficult for users to keep track of centralized roles.
Open the reportIf `totalShares()` is set to zero, then the tx will revert. This will happen due to a compiler erorr.
Open the reportThe contract is serving as the underlying entity to interact with one or more third-party `AMM` 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.
Open the reportThe Try-Catch pattern is used for external function calls to the `dividendDistributor` contract. This can lead to unintended behaviour. For example: if there is not sufficient gas to call the external function `setShare` then the loop will continue. This will result in some shareholders from not receiving rewards.
Open the reportThe `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.
Open the reportThe return value of an external call is not stored in a local or state variable. ```solidity=792 try router.addLiquidityETH{ value: amountBNBLiquidity }( address(this), amountToLiquify, 0, 0, autoLiquidityReceiver, block.timestamp ) { emit AutoLiquify(amountToLiquify, amountBNBLiquidity); } catch { emit AutoLiquify(0, 0); } ``` --- ```solidity=508 pancakePairToken.approve(address(pancakeRouter), removeAmount); ``` --- ```solidity=541 pancakePairToken.approve(address(pancakeRouter), removeAmount); ``` --- ```solidity=611 shadowFiToken.approve(address(pancakeRouter), _amountToken); ```
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x8bc3…60fe0x8bc3ec2e7973e64be582a90b08cadd13457160fe | Chain: Polygon (POS) | Source code: Verified source |
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="shadowgold"></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