Concept in development

Paste an address. Get a plain-language read.

Dripcheck is a proposed fast-glance concept for liquidity-lock and owner-privilege signals — not yet a live scanning tool.

Read the concept Join on Telegram

Project signalRug pulls and stealth-mint tokens are spiking again with the new memecoin wave on fast launchpads; traders want a five-second gut check before every ape, not a 10-minute audit read.

How it works

Paste an address. See the lock status. Decide fast.

01

What Dripcheck is today

Dripcheck is currently a documented mechanism and design direction, not a running scanner. No contract-analysis engine, lock-contract reader, or public case log has been implemented yet.

02

The proposed mechanism

The intended flow: paste a token address, receive a plain yes/no on liquidity-lock status and owner-privilege flags in place of a raw audit. This on-chain checking and bytecode analysis is PLANNED, not built.

03

Why a heuristic, not a guarantee

Even if built, a lock-status flag would only be a heuristic glance. It could miss novel scam patterns entirely and would carry no liability or warranty of safety — this boundary is intentional and permanent.

04

What the token is for

DRIP's only proposed relationship to the product is a non-binding feature-priority poll on future direction — no equity, no revenue share, no guaranteed roadmap, and this polling mechanism itself is not yet implemented.

05

Open risks we're naming upfront

Possible misreading as investment advice, false negatives on novel contracts, gaming of any future public report log, and regulatory sensitivity around tools that imply safety signals — all acknowledged before any code ships.

Questions

Read before taking part.

Is Dripcheck live right now — can I scan a token today?

No. At this stage Dripcheck is a documented concept and mechanism design. No scanning engine, lock-contract reader, or public case log has been implemented or deployed.

Once built, would a 'locked' result mean a token is safe?

No, even in its intended future form Dripcheck would be a heuristic glance, not a safety guarantee. It could not catch every scam pattern, including novel contract structures, and would carry no liability for trading losses.

What would holding DRIP actually do?

The only proposed relationship is a non-binding feature-priority poll — for example voting on which chain or flag-type to prioritize if development proceeds. DRIP would carry no equity, revenue share, or governance rights beyond that, and even this polling mechanism is not yet built.

Which blockchains or languages would be supported?

Nothing is implemented yet. Any chain coverage, translation, or accessibility support beyond an initial English interface is PLANNED at best, and would depend on future engineering and community translation efforts that have not started.

How would the public incident log stay honest?

This is unresolved. A community-submitted case log is only a proposed feature; anti-gaming, moderation, and verification safeguards for it do not exist yet and would need to be designed before any such log could be trusted.