CertiK reviewed PAXE Protocol (Paxe) on 24 Jul 2024: 7 findings, 0 critical; 5 marked fixed, 2 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 1 |
| Medium | 0 | 0 | 0 |
| Low | 1 | 0 | 4 |
All of the `100_000_000 * 10 ** 18` `PAXE` tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.
A sandwich attack may happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (executing before the target) a transaction to purchase one of the assets and make profits by backrunning (executing after the target) a transaction to sell the asset. The cited function is called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions is vulnerable to sandwich attacks, especially when the input amount is large. ```solidity=945 try uniswapV2Router.swapExactTokensForTokensSupportingFeeOnTransferTokens( tokenAmount, 0, path, destination, block.timestamp ) {} catch { emit SwapTokensForUSDTFailed(tokenAmount); } ```
| Address | Chain | Source code |
|---|---|---|
| 0xb178…3e610xb178f7b4d3be52b9c69cb386b3149371b8483e61 | Chain: BNB Chain | Source code: Verified source |
1,044 projects reviewed · 1,375 reports · latest May 2025
See CertiK’s auditsSomething 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