Scores are deterministic, versioned and derived from measured market activity. Generated commentary is added afterwards and never changes the score, publication decision or recorded outcome.
View signal receipts →Current public rule version: v1.0.0
Published rules| Input | What is measured | Base cap |
|---|---|---|
| Buyer expansion | Unique buyers in the current window relative to the token's recent norm. | 30 |
| Volume expansion | Trading volume in the current window relative to the same token's baseline. | 25 |
| Transaction burst | Transaction count accelerating above its recent baseline. | 10 |
| Social velocity | A bounded contribution when measured mentions accelerate. | 10 |
| Early movement | A bounded alternative bonus when wallets move before social activity. | 8 |
When the underlying data is available, bounded adjustments account for holder concentration, liquidity depth, developer posture and unusually concentrated early buying. Missing context remains missing; it is not replaced with an estimated value.
Comparison rule
A token is compared with its own recent activity, not ranked by size alone. The active version's publication threshold determines whether a scored candidate becomes a public signal.
A score expresses measured signal strength. It is not a price target or recommendation.
The score, rule version, reasons, timestamp and reference price are stored together.
When price data is available, the reference price is compared at +1 hour and +24 hours.
A move of at least +15% at either checkpoint is a Bullseye. If neither checkpoint reaches it, the result resolves as a Miss.
Pending means the required checkpoint has not resolved yet. Misses remain in the public record and count in the hit rate once decided.
Computed hashes and on-chain anchors are not the same claim.
Transaction required for on-chain proofGEIGER groups that day's signal records and computes a Merkle root. A root stored without a transaction hash is an internal integrity record; by itself, it is not on-chain proof.
Only a row with a transaction hash has committed its root to Robinhood Chain. For those rows, the explorer transaction provides the independent reference used to check that the recorded batch has not changed.
On-chain anchoring may be paused. The Receipts page labels computed-only rows explicitly and provides an explorer link only when a transaction hash exists.
Historical Bullseyes and Misses may be used by an in-house logistic-regression process to propose a new weight set. A proposal first runs as a challenger in shadow mode. It cannot promote itself: human approval is required before a new public version becomes active. Existing signals keep the version that produced them.
Published versions and their recorded changes.
| Version | Changes | Activated |
|---|---|---|
| v1.0.0 | Initial rule set: baseline-relative volume/buyers/tx scoring, social velocity layer, early-signal bonus, 1h dedup per token. | Initial |