PAXE Protocol security record
As of 23 Oct 2026, PAXE Protocol has 2 audit reports by 2 security firms on Trustblock; the latest is by CertiK, dated 24 Jul 2024. Those reports list no open critical findings. It also holds 2 deployed contracts on 1 chain.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits2
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Paxe | Security firm: CertiK | Date: | Scope: 1 address on BNB Chain | No open critical findings | Open · skynet.certik.com |
| Paxe Token | Security firm: Cyberscope | Date: | Scope: 1 address on BNB Chain | No open critical findings | Open · cyberscope.io |
Findings8
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 1 |
| Medium | 0 | 0 | 0 |
| Low | 2 | 0 | 4 |
HighInitial Token DistributionPaxe · CertiK · 24 Jul 2024Open
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.
Open the reportLowPotential Sandwich AttacksPaxe · CertiK · 24 Jul 2024Open
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); } ```
Open the reportLowUntitled findingPaxe Token · Cyberscope · 25 Jun 2024Open
The report gives no description here.
Open the reportContracts2
| Address | Chain | Source code |
|---|---|---|
| 0xb178f7b4d3be52b9c69cb386b3149371b8483e61 | Chain: BNB Chain | Source code: Verified source |
| 0xd2a3eec06719d5ac66248003b5488e02165dd2fa | Chain: BNB Chain | Source code: Verified source |
Show this on your site
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.
Content
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.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="paxe-token"></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