The BriunArmstrung token contract is a standard ERC20 implementation built upon battle-tested OpenZeppelin libraries. The contract's ownership has been renounced, making it immutable in terms of administrative control. The primary risk identified is the centralized initial distribution of the entire token supply to the deployer, which is an economic rather than a technical vulnerability.
On-chain security analysis — is it a scam or legit?
Is Briun Armstrung Safe?
Not verified
This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →The BriunArmstrung token contract is a standard ERC20 implementation built upon battle-tested OpenZeppelin libraries.
Read the full analysis- Top-10 concentration > 30%
- Liquidity < $10k
- 1 Low finding(s) from audit
Exact factors
- Top-10 concentration > 30% (45.6% total → 33.1% effective; 24.7% in EOAs, 20.9% in contracts — moderate)
- Liquidity < $10k ($1,168 across 1 pairs — easily drained)
- 1 Low finding(s) from audit
Each 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
Security Checklist
as of audit · Sep 4Holders
as of audit · Sep 4, 2026- Contractstreasury, vesting, bridge, staking20.9%
- Walletsanonymous holders, free to sell24.7%
- Everyone elsethe rest of the supply54.4%
How holder types affect the score
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 Sep 4, 2026
Liquidity
as of audit · Sep 4The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
0xb583…952c0x0b18…80afNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Security Findings
LowCentralized Initial Token Distribution
The contract's constructor mints the entire initial supply of 1,000,000,000 tokens (1 billion) to the deployer address. This results in 100% of the token supply being held by a single address immediately after deployment (7.4 Economic).L-01
Issue
The contract's constructor mints the entire initial supply of 1,000,000,000 tokens (1 billion) to the deployer address. This results in 100% of the token supply being held by a single address immediately after deployment (7.4 Economic).
Fix
While not a technical vulnerability in the contract code, this represents a significant centralization risk for the token's economic model. Future distribution strategies should aim for broader decentralization to mitigate potential market manipulation or single points of failure, aligning with principles of decentralized finance.
Status
Unresolved
InfoOwnership Renounced
The contract's Ownable ownership has been renounced, as indicated by the ownership_renounced: true flag in the provided metadata. This means the owner() function will return the zero address, and any functions protected by the onlyOwner modifier are no longer callable. This affects transferOwnership and renounceOwnership functions.I-01
Issue
The contract's Ownable ownership has been renounced, as indicated by the ownership_renounced: true flag in the provided metadata. This means the owner() function will return the zero address, and any functions protected by the onlyOwner modifier are no longer callable. This affects transferOwnership and renounceOwnership functions.
Fix
Confirm that renouncing ownership was an intentional design choice. This makes the contract immutable in terms of administrative control, preventing future changes to ownership or other onlyOwner protected functions. This is often a desired state for fully decentralized tokens.
Status
Unresolved
InfoStandard OpenZeppelin ERC20 Implementation
The contract is a standard implementation of the ERC20 token specification, leveraging well-audited OpenZeppelin Contracts (v4.9.3). This includes robust handling of transfers, approvals, and supply management. The use of battle-tested libraries significantly reduces the risk of common vulnerabilities (7.2 Code Security).I-02
Issue
The contract is a standard implementation of the ERC20 token specification, leveraging well-audited OpenZeppelin Contracts (v4.9.3). This includes robust handling of transfers, approvals, and supply management. The use of battle-tested libraries significantly reduces the risk of common vulnerabilities (7.2 Code Security).
Fix
Continue to rely on battle-tested libraries for core functionalities. Ensure any custom logic introduced in future versions maintains the same security standards and undergoes thorough testing and auditing.
Status
Unresolved
Analysis
AI Copilotas of audit · Sep 4The contract demonstrates high technical quality, primarily due to its reliance on OpenZeppelin's well-audited ERC20 and Ownable implementations (7.2 Code Security). There are no complex custom logic, external calls, or reentrancy vectors. Standard Solidity 0.8.0+ features mitigate integer overflow/underflow risks. The architecture (7.1 Architecture) is straightforward, representing a basic token contract.
The contract's ownership has been renounced (7.3 Access Control), which removes a single point of administrative control and enhances decentralization for contract functions. However, the entire initial token supply is minted to the deployer (7.4 Economic), presenting a centralized distribution risk. There are no explicit governance mechanisms beyond the renounced Ownable pattern (7.5 Governance).
The contract is not designed to be upgradeable (7.7 Upgrades). This eliminates upgrade-related risks such as proxy implementation vulnerabilities or administrative key compromise. The immutability provides certainty regarding the contract's future behavior.
The BriunArmstrung token contract is a robust and secure ERC20 implementation, largely due to its reliance on OpenZeppelin's battle-tested libraries and the renounced ownership.
The primary area for consideration is the initial token distribution strategy, which is currently centralized. Future token distribution should aim for broader decentralization to enhance community trust and mitigate potential market manipulation risks.
Contract & Record
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
- Sep 4, 20268Low
- Jul 28, 20262Low
- Jul 24, 202632Low
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Would You Like a More Detailed Audit of Briun Armstrung?
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