As of 3 Nov 2026, DancingSeaHorse has 2 audit reports by 1 security firm on Trustblock; the latest is by CertiK, dated 26 Oct 2022. Those reports list no open critical findings.
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 |
|---|---|---|---|---|---|
| DancingSeaHorse - Audit 2 | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| DancingSeaHorse - Audit | 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 | 0 | 0 | 0 |
| High | 1 | 1 | 1 |
| Medium | 0 | 1 | 0 |
| Low | 7 | 0 | 9 |
The `_safeMint()` in ERC721 contract contains an `_checkOnERC721Received()` function, if the `to` address is a smart contract, a reentrancy attack can occur when `_checkOnERC721Received()` makes an external call to this untrusted contract before resolving any effects. If the attacker can control the untrusted contract, they can make a recursive call back to the original function, repeating interactions that would have otherwise not run after the external call resolved the effects. e.g. The attackers could use the attacking contract to call `premintNFT()` as many times as they want, and the `premintSaleCounter < premintlimit` check will always be `true` for the `premintSaleCounter` would only be added once at the end of the function. Besides, if `premintNFT()` is called while the `for` loop in `makeNft` is in progress, the `tokenid` for the next round of `for` loop will be occupied, causing the function to revert.
Open the reportAddresses should be checked before assignment or external call to make sure they are not zero addresses. ```solidity=164 tokenAddress = _tokenAddress; ``` - `_tokenAddress` is not zero-checked before being used.
Open the report`makeNft()` and `premint2Nft()` is using same variable `price` as the price of the NFT token.
Open the reportState variables that never change should be declared as `constant` to save gas. ```solidity=17 uint256 public premintPrice = 2 ether; ``` - `premintPrice` should be declared `constant`. --- ```solidity=18 address vaultAddress = 0x3C10D90796Ce828644951c0682012B3fabA52F8f; ``` - `vaultAddress` should be declared `constant`. --- ```solidity=19 uint256 public maxSupply = 8888; ``` - `maxSupply` should be declared `constant`. --- ```solidity=20 uint256 public maxMintSupplySale = 7000; ``` - `maxMintSupplySale` should be declared `constant`. --- ```solidity=31 uint256 public userLimit = 10; ``` - `userLimit` should be declared `constant`.
Open the reportThe `msg.value` should equal to the `cost * _mintAmount` to prevent investors transferring excess ETHs to the contract.
Open the reportThe `maxSupply` check should be changed from `supply <= maxSupply` to `supply + _mintAmount <= maxSupply` to guarantee the `maxSupply` will not be exceeded.
Open the reportAddresses should be checked before assignment or external call to make sure they are not zero addresses. ```solidity=156 tokenAddress = _tokenAddress; ``` - `_tokenAddress` is not zero-checked before being used.
Open the reportThe function `giftNft()`, `OTC()`, and `vault()` seem exactly the same, hence two of them are redundant.
Open the reportThe function `withdrawAll()` is used to withdraw a fixed amount of BNBs from the contract, which is the balance of `t1` address. However, the function would be reverted if the balance of `t1` is large and the BNBs in the contract are not enough, while in the other case it may take many times to withdraw all the BNBs in the contract.
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. ```solidity=14 using SafeMath for uint256; ``` - `SafeMath` library is used for `uint256` type in `Nft` contract. --- ```solidity=14 using SafeMath for uint256; ``` - `SafeMath` library is used for `uint256` type in `Nft` contract. ```solidity=151 addBrandCount(count.add(_mintAmount)); ``` - `SafeMath.add` is called in `brandNft` function of `Nft` contract. *Note: Only a sample of 2 `SafeMath` library usage in this contract (out of 5) are shown above.*
Open the reportThe reports name a repository or files. Open a report to see its scope.
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="dancingseahorse"></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