As of 3 Nov 2026, Mazimatic has 1 audit report on Trustblock, by CertiK, dated 27 Mar 2023. That report lists 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 |
|---|---|---|---|---|---|
| Mazimatic - New 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 | 0 | 0 | 0 |
| Medium | 0 | 0 | 2 |
| Low | 4 | 0 | 14 |
The function `setAntisnipeDisable()` is set in a way that the flag `antisnipeDisable` (that has a default value of false) can only be set as `true` once by the owner. ```solidity function setAntisnipeDisable() external onlyOwner { require(!antisnipeDisable); antisnipeDisable = true; } ``` The audit team would like to check if this is intended and whether there should be a method to toggle between turning on and off the `antisnipeDisable` flag.
Open the reportThe audit team would like to better understand how the `liquidityTimestamp` is used. In the following codeblock, it is used to determine the eventual value of `amount2` in function `_transfer()`. ```solidity=138 if (to == pairAddress && liquidityTimestamp != 0) { if (block.timestamp < liquidityTimestamp + 24 hours) { return (amount * 1000) / 10000; } else if ( liquidityTimestamp + 24 hours < block.timestamp && block.timestamp < liquidityTimestamp + 48 hours ) { return (amount * 500) / 10000; } return 0; ``` Once the `liquidityTimestamp` has passed, the value of `amount2` will always be 0, therefore the value of `liquidityTimestamp` must be reset to another value to re-enable the other conditions. The audit team would like to check if this aligns with the intended design.
Open the reportThe logic currently only manages one `pairAddress()` which is the one that is created in the `initialize()` function of the contract. If other users create new uniswap pair addresses, the amount handling in the `_botManager()` will be bypassed. The audit team would like to know if this implementation matches the intended design.
Open the reportThe MaziToken implemented a cool down mechanism, meaning that two consecutive token transfers within certain time interval may cause the second transfer to revert. For example, if the token is used in a vault contract, the withdraw function may need to invoke the two transfers (the first time to transfer fees and the second time to transfer tokens to users), which may lead to a potential revert of the function and prevent withdrawals. Therefore, the token may be not compatible with many protocols.
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="mazimatic"></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