The FlapTaxTokenV3 is a minimal clone (EIP-1167) implementation of an ERC-20 token with tax-enforced transfer logic. The contract ownership has been explicitly renounced on-chain, rendering all privileged administrative functions (such as migration controls) permanently inaccessible. The architecture is immutable, and the code follows standard OpenZeppelin patterns for upgradeable contracts, though the clone pattern itself prevents future logic upgrades.
Early-stage security check — honeypot & rug-pull analysis
Is TeslaSI a Scam?
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 FlapTaxTokenV3 is a minimal clone (EIP-1167) implementation of an ERC-20 token with tax-enforced transfer logic.
Read the full analysis- Liquidity not locked
- Liquidity < $50k
Exact factors
- Liquidity NOT locked (100% of the pool; this pool is 100% of DEX liquidity) — held by independent providers — market-depth risk
- Liquidity < $50k ($40,106 across 3 pairs — thin market)
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 · Oct 20Holders
as of audit · Oct 20, 2026- Contractstreasury, vesting, bridge, staking18.3%
- Walletsanonymous holders, free to sell8.2%
- Burnedout of circulation9.0%
- Everyone else84,158 holders64.5%
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 Oct 20, 2026
Liquidity
as of audit · Oct 20The 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.
0x8f57…57ebNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Security Findings
InfoNo issues identified in the reviewed source
The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (mint/owner authority, mint capability, holder concentration) were applied separately and feed the risk score.I-01
Issue
The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (mint/owner authority, mint capability, holder concentration) were applied separately and feed the risk score.
Fix
Re-check after any contract upgrade or ownership change, both of which can alter behaviour without changing this page.
Status
Acknowledged
Analysis
AI Copilotas of audit · Oct 20The contract utilizes a robust EIP-1167 minimal clone architecture, ensuring consistent logic across deployments. 7.1 Architecture is sound, utilizing standard ERC-20 and EIP-712 interfaces. 7.2 Code Security is high, with no identified reentrancy or overflow vulnerabilities. 7.3 Access Control is effectively locked due to the renounced ownership status.
7.4 Economic parameters are fixed by the current state and cannot be altered by any party. 7.5 Governance is effectively non-existent as the owner has renounced control. 7.6 External dependencies are limited to standard OpenZeppelin libraries, which are widely audited and secure.
7.7 Upgrades are impossible for this contract due to the EIP-1167 clone pattern and the renounced ownership. 7.8 Operations are stable, as the contract logic is immutable and cannot be modified by any administrative entity. The contract is effectively 'frozen' in its current state.
No security vulnerabilities were identified. Because ownership has been renounced, the contract is immutable and no further administrative actions can be taken.
Users should be aware that the current tax and migration state is permanent and cannot be adjusted by any developer or owner.
Contract & Record
Frequently Asked Questions
Is TeslaSI a scam?
There is no definitive evidence to label TeslaSI as a scam. The contract is verified, ownership is renounced, and there is no mint function. However, the lack of locked liquidity and significant token concentration among the top 10 holders are common red flags in decentralized finance that investors should carefully evaluate before committing any capital to the asset.
Is TeslaSI safe to buy?
Safety is subjective in decentralized finance. While the project features a verified contract with no minting capabilities, the lack of locked liquidity means funds are not technically protected from removal. Additionally, the 37.5% concentration in the top 10 wallets increases risk. Perform thorough due diligence, as these structural factors could impact your ability to exit positions at desired prices.
Has TeslaSI been audited?
While the TeslaSI contract is verified on the BNB Chain explorer, this confirms the code matches its published source but does not equate to a professional security audit. Investors should understand that verification does not guarantee the absence of logic vulnerabilities or hidden risks within the smart contract architecture.
Would You Like a More Detailed Audit of TeslaSI?
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