Scoring Update: Tighter Creator-Control Checks and Fairer Data Gaps

This scoring update closes a few narrow edge cases that showed up at the tail end of QA. The goal was simple: push clearly creator-controlled danger patterns down more decisively, while avoiding unnecessary punishment when missing sellability data came from provider infrastructure rather than the market itself.

What Changed

• Tokens with strongly corroborated creator control now get pushed into the danger range more consistently when severe concentration signals also line up.
• Clearly bad exit patterns remain a separate hard override instead of being blurred into generic missing-data behavior.
• Pure provider blind spots can now flow into a narrower neutral path when the surrounding market evidence still looks real and tradeable.
• Young transfer-hook launches still default to the hard-risk path, with only a very narrow exception for launches that look protocol-governed rather than creator-controlled.

What This Means for You

If a token still looks tightly controlled by the same party, BarryGuard now reacts faster when that control is backed by large supply concentration or other strong warning signs. That makes the danger band stricter where it should be strict.

At the same time, a temporary provider outage is less likely to drag an otherwise real market down as if sellability had actually failed. That makes cautious scores fairer in edge cases without turning missing data into a free pass.

What Did Not Change

• No token-specific exceptions were added.
• Confirmed unsellable tokens still stay hard negative.
• Missing data still lowers confidence and can still hurt the final score.
• The broad coverage system was not globally softened just to make edge cases look nicer.

Why This Matters

Traders need two things from a risk engine: strong reactions to real control patterns and honest handling of missing information. If the engine is too soft, dangerous tokens slip through. If it is too harsh, temporary provider failures look like real market failure.

This update is about getting that balance tighter at the edges, not making the whole system looser.

Check the Live Result

You can inspect the current scoring behavior in the checker and read the wider scoring rules in the methodology.