On-chain security analysis — is it a scam or legit?
BNB ChainThe Succinct contract implements an Omnichain Fungible Token (OFT) standard on BSC.
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 30, 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.
0x89cf…3fa50x5160…f1eb0x031a…3dc6No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The functions send, lzReceiveSimulate, and lzReceive allow for the minting of new tokens as part of the cross-chain transfer process. While restricted to the LayerZero endpoint, this mechanism allows the total supply to increase, which could dilute existing holders if the cross-chain bridge is compromised or misconfigured.
Implement a hard cap on the total supply or a rate-limiting mechanism on cross-chain minting to mitigate the impact of potential bridge exploits. Monitor the LayerZero endpoint interactions closely for unusual minting patterns.
Unresolved
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 2 address(es) other than the owner/deployer. One of them — a wallet, 0x89cf…3fa5 — holds 92.3% 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 95.3% of supply. Of that, 15.3% in DEX pools — not holders that can sell, so excluded from the concentration score. What remains: 76.3% in wallets, 3.6% in other contracts. 3,672 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 Succinct (PROVE), market cap $37M, rank #544. 3,672 holders.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $234K (DexScreener, all pools). 24h trading volume $8.2M (CoinGecko, all markets, daily snapshot). 24h trading volume $524K (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 representing another asset's units 1:1, backed by a wrapping contract, a custodian or a bridge. The class itself adds no points; the contract and market facts decide the score. Basis: a copy of the coin from its home chain (ethereum), minted here by LayerZero (lzReceive). Tokenomics — Supply: minted here by LayerZero (lzReceive) against tokens locked or burned on other chains. Control: a 3-of-5 multisig. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $234K of DEX liquidity across 3 pools. Launch: 452 days of market history.
The backing is the risk: check who holds the underlying asset and how redemption works.
Acknowledged
The Succinct contract implements an Omnichain Fungible Token (OFT) standard on BSC. The architecture relies on the LayerZero endpoint for cross-chain messaging and token minting/burning. While the implementation follows standard library patterns, the ability to mint tokens via cross-chain messages introduces inherent economic risks regarding supply inflation.
The contract utilizes established LayerZero OFT libraries for cross-chain interoperability. 7.1 Architecture is modular, 7.2 Code Security is robust, and 7.3 Access Control is correctly implemented for administrative functions. 7.6 External dependencies are limited to the LayerZero endpoint, which is a trusted component in this architecture.
7.4 Economic risks are present due to the minting capabilities inherent in the OFT standard. 7.5 Governance is managed via a 3-of-5 multisig, providing a reasonable balance of security and operational agility. The protocol lacks explicit circuit breakers for cross-chain minting, which is a common trade-off in OFT implementations.
7.7 Upgrades are not supported as the contract is not a proxy. 7.8 Operations are managed by a multisig owner, ensuring that administrative changes require consensus. No further upgradeability concerns are noted.
The protocol should implement a monitoring system to track cross-chain minting events and total supply changes in real-time to detect anomalous activity.
Ensure that the multisig signers are geographically and organizationally distributed to maintain the integrity of the administrative functions. Regularly audit the LayerZero peer configurations to ensure only authorized chains can trigger minting operations. Consider implementing a global supply cap if the tokenomics model does not explicitly require unbounded cross-chain minting.
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? Add your links and get it Verified
