| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 19 Nov 2026 |
| Buy tax | 0% | Contract | 19 Nov 2026 |
| Sell tax | No data | Contract | 19 Nov 2026 |
| Admin mint | No data | Contract | 19 Nov 2026 |
| Transfers pausable | No data | Contract | 19 Nov 2026 |
| Address blacklist | No data | Contract | 19 Nov 2026 |
| Upgradeable proxy | No data | Contract | 19 Nov 2026 |
| Source verified | No | Block explorer | 19 Nov 2026 |
| Top-10 holders | 80% | Holder distribution | 19 Nov 2026 |
| Liquidity locked | No | LP holders | 19 Nov 2026 |
| Holders | 2242 | Token contract | 19 Nov 2026 |
| Deployed by | 0x378fe8…a62710 |
| Holders | 2,242 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x11de5d…cba38d | 19.44% |
| #2 | 0xb38e8c…82891d | 10.00% |
| #3 | 0x0d0707…b492fe | 10.00% |
| #4 | 0x01c42e…34b4d3 | 8.89% |
| #5 | 0x4b5f90…1a3a32 | 8.69% |
This check returned a score of 0 out of 18 for DECLB, and the central reason is that an automated simulation detected honeypot behaviour: the contract blocked an attempted sell. In practice, this means that once tokens are bought, the contract's current logic does not allow them to be sold back — the holder can end up with tokens that are effectively stuck, regardless of what the price chart shows. On top of that, the contract's source code is not verified, so there is no readable code to confirm what the owner can and cannot do — the findings are based on bytecode behaviour only, not on a human-readable explanation of the rules. Liquidity is also not locked, meaning whoever controls the liquidity pool retains the ability to withdraw it at any time, which would affect the ability to trade the token even if selling were otherwise possible. Combined with the fact that the top 10 holders control 80.4% of supply, a small number of addresses hold the ability to move large portions of supply, which can affect price and liquidity conditions significantly.
It's important to be clear about what this check does not cover. This is an automated, mechanical read of contract behaviour on Arbitrum as of the date tested — it does not assess who the team behind DECA Labs is, whether their stated plans or roadmap are credible, how the tokenomics are designed to play out over time, or any legal or regulatory status of the project. No person reviewed this contract or the project's intent; the findings reflect only what the code and on-chain data showed during an automated pass. A score of 0 reflects detected contract-level risk indicators, not a judgement on the people or business behind the token.
Given that selling was blocked in simulation, this is not a situation where a small test purchase would help confirm anything — if transfers out are genuinely restricted, funds put in can stay in regardless of amount. Rather than testing with real funds, next steps that don't involve putting money at risk include looking for the contract source on the relevant block explorer to see if it has since been verified, checking whether the liquidity pool tokens are locked or held by a known locking service, reviewing the distribution of the top holder addresses to understand concentration, and searching for any independent commentary or audits referencing this specific contract address on Arbitrum. Any decision about whether to interact with this token at all should weigh these unresolved findings carefully.
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 18 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.