Early-stage security check — honeypot & rug-pull analysis
The PangeaOFT contract implements an Omnichain Fungible Token (OFT) standard on the Base network.
Read the full analysisEach factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
Holder balances as recorded by the audit of Oct 21, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0x5fe5…7e38No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The functions send, lzReceiveSimulate, lzReceive, and reportSupply allow privileged roles (endpoint or supplyReporter) to mint new tokens or adjust the total supply. This capability can lead to the dilution of existing token holders if the privileged addresses are compromised or act maliciously.
Restrict the 'supplyReporter' role to a multi-signature wallet or a decentralized governance contract. Implement a strict upper bound on supply increases and consider adding a timelock to any supply-altering operations.
Unresolved
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 1 address(es) other than the owner/deployer. One of them — a wallet, 0x5fe5…7e38 — holds 100.0% and can remove that share at once; who controls it is not visible on-chain, so it is not treated as an independent provider. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
The ten largest holders own 16.6% of supply. What remains: 9.1% in wallets, 7.4% in other contracts. 294 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
294 holders. Not listed by CoinGecko or any exchange GoPlus tracks. Nothing independent confirms who is behind this token, so every power its contract grants is scored at face value.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $161K (DexScreener, all pools). 24h trading volume $1.2M (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: mintable with no on-chain cap found. Control: a contract. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $161K of DEX liquidity across 4 pools. Launch: under a day of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The token's oldest DEX pool is less than a day old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
The PangeaOFT contract implements an Omnichain Fungible Token (OFT) standard on the Base network. The architecture relies on LayerZero for cross-chain messaging and utilizes specific roles for metadata management and supply reporting. While the code follows standard library patterns, the presence of privileged minting capabilities requires careful monitoring of the designated roles.
The contract leverages established LayerZero OFT standards for cross-chain interoperability. 7.1 Architecture is modular, utilizing OApp components for secure message handling. 7.2 Code Security is high, with clean implementation of ERC-20 standards. 7.3 Access Control is strictly enforced via role-based modifiers for sensitive functions.
7.4 Economic and 7.5 Governance risks are centered on the supplyReporter role. This role has the authority to influence supply reporting, which impacts tokenomics. 7.6 External dependencies are limited to the LayerZero endpoint, which is a trusted infrastructure component.
7.7 Upgrades are not implemented via proxy patterns in this contract. 7.8 Operations are managed through owner-restricted functions for configuration. The contract is immutable regarding its logic, reducing upgrade-related attack vectors.
The protocol should ensure that the addresses assigned to the 'supplyReporter' and 'metadataAuthority' roles are secured via multi-signature wallets or timelock contracts.
This mitigates the risk of unauthorized supply adjustments or metadata manipulation. Regular monitoring of the 'reportedSupply' and 'metadataURI' changes is advised to ensure transparency for token holders. No further code changes are required as the current implementation adheres to the intended design patterns.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit Is this your token? Publish your own audit on this page
