Free above: contract permissions, sell test and tax when data is available.
Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.
| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 18 Nov 2026 |
| Buy tax | 0% | Contract | 18 Nov 2026 |
| Sell tax | 0% | Contract | 18 Nov 2026 |
| Admin mint | Not present | Contract | 18 Nov 2026 |
| Transfers pausable | Not present | Contract | 18 Nov 2026 |
| Address blacklist | Not present | Contract | 18 Nov 2026 |
| Upgradeable proxy | No | Contract | 18 Nov 2026 |
| Source verified | Yes | Block explorer | 18 Nov 2026 |
| Liquidity locked | 100% burned | LP holders | 18 Nov 2026 |
| Holders | 27 | Token contract | 18 Nov 2026 |
| Deployed by | 0x379b7e…3323c5 |
| Holders | 27 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x379b7e…3323c5 | 100.00% |
| #2 · Uniswap v4 pool · contract | 0x000000…e08a90 | 99.74% |
| #3 · contract | 0x410144…0ea4a3 | 5.53% |
| #4 | 0x17c27e…caa52c | 0.18% |
| #5 · contract | 0x47e198…4cd9e2 | 0.05% |
This automated check scanned LUCIA's contract mechanics on Ethereum and did not detect several behaviours that are commonly used to trap or drain holders. A transfer simulation found the token sellable, with no buy or sell tax applied at the contract level. No admin mint function was found, meaning the current code does not expose a way for the owner to create new tokens and dilute holders. No pause function was detected, so the ability to freeze all transfers was not found in the contract. No blacklist function was found, which would otherwise let an address be blocked from selling while everyone else trades freely. The contract is not upgradeable through a proxy, so the logic deployed today cannot be swapped out later for different rules. The source code is verified on the block explorer, meaning the logic is publicly readable rather than hidden behind an unverified bytecode blob. Liquidity is reported as 100% burned, which means the LP tokens were sent to a dead address and cannot be withdrawn by whoever added them — a common way early liquidity gets pulled out from under buyers.
It's worth being clear about what this does not cover. This check reads contract code and on-chain state; it says nothing about who is behind the project, whether the team has a history, how the token's supply is distributed in practice, what any whitepaper or roadmap claims, or whether there's a legal entity standing behind it. A clean set of mechanical findings does not mean the people controlling the project will act in holders' interests, and intent is not something code alone can reveal. Score and flags here reflect what was detectable on the date of the check — they are not a certification and can't rule out risks that live outside the contract itself.
With only 46 holders recorded, concentration risk is worth looking at directly: check how the supply is split across wallets, since a small number of large holders can still move the market even with no malicious code present. It's also worth checking whether the contract owner's privileges have been renounced or still sit with an active address, looking at the wallet that deployed the contract and its transaction history, and searching for any independent discussion of the project outside its own channels. None of this replaces doing your own research into the team, the tokenomics, and the broader context before deciding what, if anything, to do with this information.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 12 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.