As of 3 Nov 2026, MagicCraft has 1 audit report on Trustblock, by CertiK, dated 28 Sep 2022. That report lists no open critical findings. It also holds 1 deployed contract on 1 chain.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Magiccraft - MagicMarketplace | Security firm: CertiK | Date: | Scope: 1 address on BNB Chain | 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 | 0 | 2 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 3 | 0 |
In the contract `MagicMarketplace` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and update the sensitive settings and execute sensitive functions of the protocol. 
Open the reportTransparentUpgradeableProxy is an upgradeable contract, the owner can upgrade the contract without the community's commitment. If an attacker compromises the account, he can change the implementation of the contract and inject malicious implementation into the implementation contract behind the proxy .
Open the reportIn function `_escrow()` and `_transfer()`, `ftContract.transferFrom(address(this), _receiver, _tokenId);` is assumed to throw if any error. However, this is an incorrect assumption because the address of `_nftContract` cannot guarantee a NFT address nor the `transferFrom()` cannot guarantee to revert if the transfer fails. This is because that the value of `_nftAddress` is from input argument and there's no check to validate if `_nftAddress.transferFrom()` is correctly implemented.
Open the reportThe goal of function `_getNftContract()` is designed to check if the contract in given `_nftAddress` address is a valid ERC721 deployment with correct ERC721 functionality. However current function can not validate the implementation in `_nftAddress`
Open the reportIn function `createAuction()`, `_owns` is implemented to validate ownership of the token in NFT contract in `_nftAddress` address. However due to the value of `_nftAddress` being from input argument, the implementation correctness of `_nftContract.ownerOf` cannot be guaranteed.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x76ae…615d0x76ae87e1c364ead343251ee7dfa2415b4678615d | Chain: BNB Chain | 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="magiccraft"></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