Speed On-Chain Risk Check

Speed's Coin · Base · 0xe260967121360def3f5290e2c7e63919fb718080
0 / 4 On-chain Check
Checked 13 Nov 2026. On-chain Check, 4 of the 100-point ChainSift Score — what it covers. Contract function analysis and holder distribution were unavailable for this contract, so those signals are excluded from the total.

Evidence

Risk factorFindingEvidenceDate
Sellable Yes ChainSift simulation 13 Nov 2026
Buy tax 0% Contract 13 Nov 2026
Sell tax 0% Contract 13 Nov 2026
Admin mint No data Contract 13 Nov 2026
Transfers pausable No data Contract 13 Nov 2026
Address blacklist No data Contract 13 Nov 2026
Upgradeable proxy No data Contract 13 Nov 2026
Source verified No Block explorer 13 Nov 2026
Holders 0 Token contract 13 Nov 2026

What this means

This automated check looked at Speed (Speed's Coin) on Base and scored it 0 out of 4, mainly because the contract's source code is not verified on the block explorer. In practice, this means the check could only examine the bytecode that actually runs on-chain, not human-readable code, so several mechanics simply could not be confirmed one way or the other: whether the owner can mint new tokens at will (which would dilute existing holders), whether transfers can be paused (which would freeze trading for everyone), whether specific wallets can be blacklisted (which would block individual holders from moving or selling their tokens), and whether the contract sits behind an upgradeable proxy (which would let the owner swap in entirely different logic after launch). None of these were detected as present — but "no data" is not the same as "confirmed absent." A simulated sale went through successfully and buy/sell tax both came back at 0%, which means no honeypot behaviour or trading tax was detected on the date of this check. The holder count showing as zero is also worth noting as unusual and may reflect a data-source limitation or a very early-stage token.

It's important to be clear about what this check does not cover. This is a purely mechanical read of contract code and simulated transactions — it says nothing about who is behind the token, how the team plans to use funds, whether token supply is concentrated in a few wallets, whether there's a liquidity lock, or whether any marketing claims about the project are accurate. Intent, tokenomics design, legal structure and team credibility are all outside the scope of an automated contract scan like this one. No human has reviewed this token; the findings above come entirely from automated analysis of on-chain data.

Given the unverified source code, a sensible next step is to treat the unknowns as unknowns rather than assuming they're favourable. You could look up the contract directly on the Base block explorer to see if verification has since been added, check whether liquidity is locked and for how long, review how tokens are distributed across holder addresses once that data is available, and search for any independent commentary or audit of the project. Because verified source code is what allows mechanics like mint, pause and blacklist functions to be properly assessed, its absence here is a meaningful gap, and decisions made without that information carry more uncertainty than they would for a fully verified contract.

Team, tokenomics and legal structure are not assessed here — that is the other 96 points of the ChainSift Score. How this check works and what it misses.

Watch this contract

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 send one confirmation message and nothing else until something changes.

We checked 4 points out of 100.

A deep check also reviews the project's public materials, team, tokenomics and disclosures.

Related guides

Contract data read from GoPlus Security and the Base block explorer. The trade simulation (a buy, then a sale an hour later) is run by ChainSift directly on Base — our data source returned none for this contract. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 13 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.