Is LEO safe to buy? Bitfinex LEO Token security analysis on Ethereum
Automated honeypot, tax, liquidity and contract-permission analysis of LEO on Ethereum. 0x2af5d2ad76741191d15dfe7bf6ac92d4bd912ca3
Last scanned:
CAUTION
9 signals · 90% data completeness
Recursio scores LEO 65/100 — the CAUTION band — from 9 signals at 90% data completeness. The score is held back mainly by Liquidity (30/100), Market activity (20/100), LP safety (15/100).
There is no buy or sell tax, and sell simulation succeeded for 94 of 94 real wallets (0.0% fail rate).
Pools hold just $3.1K across 2 pairs. A few hundred dollars of selling already moves the price; a few thousand collapses it.
The owner can still pause transfers, rewrite balances. That is not a prediction that they will — only that nothing stops them, and it happens without warning.
Key risks for LEO
- Owner can pause all transfers
- Owner can rewrite balances
- Thin liquidity ($3.1K)
- Only 0% of LP is locked
- Almost no 24h trading volume
LEO market & liquidity
| Price | $9.6600 |
|---|---|
| 24h change | 0.4% |
| Market cap | $8.9B |
| 24h volume | $8 |
| DEX liquidity | $3.1K |
| Holders | 3.8K |
| Trading pairs | 2 |
LEO contract security checks
| Honeypot | No |
|---|---|
| Verified source code | Yes |
| Mintable supply | No |
| Transfers pausable | Yes |
| Blacklist function | No |
| Proxy contract | No |
| Owner can change balances | Yes |
| Hidden owner | No |
| Ownership can be reclaimed | No |
| Self-destruct | No |
| Tax modifiable by owner | No |
| Trading cooldown | No |
| Cannot sell all | Unknown |
| Buy tax | 0% |
| Sell tax | 0% |
| Owner holdings | 0.0% |
| Creator holdings | 0.0% |
| LP holders | 3 |
| LP locked | 0.0% |
Real-holder sell simulation for LEO
Recursio replays actual sell transactions for real LEO holders. This catches dynamic honeypots that pass a static contract audit — a token can look clean and still block most wallets from selling.
| Holders simulated | 94 |
|---|---|
| Sold successfully | 94 |
| Failed to sell | 0 |
| Fail rate | 0.0% |
| Simulated buy tax | 0.0% |
| Simulated sell tax | 0.0% |
| Highest tax seen | 0.0% |
| Risk level | unknown |
How the LEO safety score is calculated
The score is a weighted composite. Missing data lowers confidence rather than being silently skipped, and hard caps apply — a token with almost no liquidity or a failed sell simulation cannot score well no matter how clean its source code looks.
| Signal | Score | Weight |
|---|---|---|
| Honeypot risk | 100/100 | 22% |
| Contract security | 85/100 | 13% |
| Owner risk | 60/100 | 11% |
| Owner permissions | 75/100 | 11% |
| Holder distribution | 80/100 | 9% |
| Liquidity | 30/100 | 13% |
| Market activity | 20/100 | 9% |
| ERC-20 compliance | no data | 0% |
| Clone / fake token | 100/100 | 6% |
| LP safety | 15/100 | 6% |
Run a live LEO check
This page is a cached snapshot. Contract owners can change taxes, pause transfers or pull liquidity minutes later — always re-scan immediately before you trade.
Frequently asked
Is LEO a honeypot?
Automated checks did not flag LEO as a honeypot at the time of this scan, with a 0.0% fail rate across simulated real-holder sells.
What are the LEO buy and sell taxes?
Buy tax 0%, sell tax 0% when scanned.
Can I trust this score?
It aggregates GoPlus contract security, honeypot.is real-holder sell simulation and DexScreener market data into one number. It measures contract and liquidity risk — not whether a price will go up. Nothing here is investment advice.
How to check a token yourself · What is a honeypot token
Recently checked tokens
- USDtb safety check (Ethereum) 94/100
- crvUSD safety check (Ethereum) 10/100
- OFC safety check (Base) 10/100
- UNKNOWN safety check (Base) 7/100
- Aurora safety check (Base) 10/100
- WAI safety check (BNB Chain) 10/100
- CAN safety check (BNB Chain) 80/100
- WCT safety check (Base) 75/100