Skip to content
Signalcrest
← Back to entity feed
devtoolsentity · corroborated across sources

web3

for web3 devs

Cooling

9

signal score

as of 16d ago

1

live items

Too early

trajectory — needs a few more snapshots

devto

Why this scored 9

every term, weighted
Velocity+0.0 / 40 max

Its fastest-moving item, measured against the pace of its own source

Acceleration+0.0 / 25 max

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+0.0 / 25 max

How many independent communities its own items come from

Recency+9.5 / 10 max

Decays to zero over 14 days, counted from when we first saw it

Saturation penalty0.2 / 30 max

Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it

Composite9.3

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology

Signal history

7-day window (free)
Not enough history yet — the trend line fills in as snapshots accrue (every 30 min).

The evidence

The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.

  1. 135

    The RPC said Base was healthy. The first contract read still failed.

    Contract read failed — for web3 devs

    devtodevtoolsSteady🔗 3 · python17d ago
  2. 235

    The API promised industry keywords. Modern sites kept returning [].

    API returned empty — for web3 devs

    devtodevtoolsSteady🔗 3 · javascript17d ago