Home › Base › LINGO

Is LINGO safe to buy? Lingo security analysis on Base

Automated honeypot, tax, liquidity and contract-permission analysis of LINGO on Base. 0xfb42da273158b0f642f59f2ba7cc1d5457481677
Last scanned: 2026-09-10 05:30 UTC

77/100

SAFE

9 signals · 90% data completeness

Recursio scores LINGO 77/100 — the SAFE band — from 9 signals at 90% data completeness. The score is held back mainly by Owner permissions (50/100), Market activity (40/100), LP safety (15/100).

There is no buy or sell tax, and sell simulation succeeded for 818 of 818 real wallets (0.0% fail rate).

$146.5K of liquidity across 2 pairs is deep enough for retail-size trades.

The owner can still mint new supply, change the tax. That is not a prediction that they will — only that nothing stops them, and it happens without warning.

Key risks for LINGO

Owner can change the tax
Supply can be minted
Hidden owner
Only 0% of LP is locked

LINGO market & liquidity

Price	$0.0143
24h change	-0.7%
Market cap	$8.5M
24h volume	$4.4K
DEX liquidity	$146.5K
Holders	30.6K
Trading pairs	2

LINGO contract security checks

Honeypot	No
Verified source code	Yes
Mintable supply	Yes
Transfers pausable	No
Blacklist function	No
Proxy contract	No
Owner can change balances	No
Hidden owner	Yes
Ownership can be reclaimed	No
Self-destruct	No
Tax modifiable by owner	Yes
Trading cooldown	No
Cannot sell all	No
Buy tax	0%
Sell tax	0%
Owner holdings	0.0%
Creator holdings	0.0%
LP holders	7
LP locked	0.0%

Real-holder sell simulation for LINGO

Recursio replays actual sell transactions for real LINGO 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	818
Sold successfully	818
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	low

How the LINGO 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	75/100	13%
Owner risk	100/100	11%
Owner permissions	50/100	11%
Holder distribution	100/100	9%
Liquidity	70/100	13%
Market activity	40/100	9%
ERC-20 compliance	no data	0%
Clone / fake token	100/100	6%
LP safety	15/100	6%

LINGO token security scorecard: 77/100, SAFE, on Base — Shareable LINGO scorecard.

Run a live LINGO 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.

Re-scan LINGO in Telegram View on BaseScan

Frequently asked

Is LINGO a honeypot?

Automated checks did not flag LINGO as a honeypot at the time of this scan, with a 0.0% fail rate across simulated real-holder sells.

What are the LINGO buy and sell taxes?

Buy tax 0%, sell tax 0% when scanned. This contract lets the owner change the tax, so treat these numbers as a snapshot only.

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