On-chain security analysis — is it a scam or legit?
The OrderOFT contract implements a cross-chain token bridge using the LayerZero OFT standard.
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 24, 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.
0x647c…c73aNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The contract lets its controller — a 2-of-3 multisig — pause all transfers. Nothing independent vouches for whoever holds them, so each is a live risk to holders.
Check who holds these powers and whether a timelock or multisig stands between them and holders.
Acknowledged
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, 0x647c…c73a — 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 _removeDust function performs division before multiplication, which can lead to minor precision loss during token calculations.
Reorder operations to perform multiplication before division to maintain maximum precision.
Unresolved
The ten largest holders own 80.1% of supply. What remains: 11.3% in wallets, 68.8% in other contracts. 4,880 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
Listed on CoinGecko as Orderly (ORDER), market cap $14M, rank #1004. 4,880 holders.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $173K (DexScreener, all pools). 24h trading volume $3.6M (CoinGecko, all markets, daily snapshot). 24h trading volume $1.1M (DexScreener, all pools). CoinGecko's record for this coin: all-time high $0.492 on 2025-10-06; the price is now 92.9981% below it.
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: fixed — the contract has no mint function. Control: a 2-of-3 multisig. Code: upgradeable proxy. Fees: no buy or sell tax. Market: $173K of DEX liquidity across 8 pools. Launch: 396 days 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 OrderOFT contract implements a cross-chain token bridge using the LayerZero OFT standard. The architecture relies on a UUPS proxy pattern and is managed by a 2-of-3 multisig. The codebase demonstrates high adherence to standard library patterns, though minor rounding risks exist in dust removal logic.
The contract utilizes a robust modular architecture inheriting from LayerZero's OApp and OFT standards. 7.1 Architecture is well-structured using UUPS proxies for upgradeability. 7.2 Code Security is high, with clear separation of concerns between messaging and token logic. 7.6 External dependencies are limited to the verified LayerZero endpoint, ensuring reliable cross-chain communication.
7.3 Access Control is centralized under a 2-of-3 multisig, providing a balance between security and operational agility. 7.4 Economic parameters are governed by the owner, who can pause the contract or set enforced options. 7.5 Governance is currently restricted to the multisig, which is appropriate for the current deployment phase.
7.7 Upgrades are handled via the UUPS pattern, which is the industry standard for gas-efficient and secure proxy management. 7.8 Operations are supported by pause/unpause functionality, allowing for emergency mitigation. The implementation is correctly initialized, preventing unauthorized initialization attacks.
The protocol is well-architected and follows secure development practices.
We recommend maintaining the multisig threshold and ensuring that any future changes to the 'enforcedOptions' or 'peers' are subject to a rigorous multi-signature review process before execution. For the identified rounding issue, ensure that the frontend or integration layer accounts for potential dust accumulation during cross-chain transfers to prevent minor balance discrepancies for end-users.
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.
Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Publish your own audit on this page
