sodium lamp · warming up
Smarta.BNB Smart Chain · smart money consensus

calibration

window: 24 h48 h168 h· machine readable: /api/calibration · how all of it is computed: methodology

enough data both for the conversation about gates and for score thresholds
setups in the window
402
chain 56
passed every gate
80
only these are compared with the threshold
held by one condition
99
the ceiling on what any tuning can give
held by several
223
one threshold changes nothing here
outcome measured
361
at one hour · among gate passers 78
born expired
46
the executor never sees them

46 of 402 setups were already expired when they were written down: the engine finds a cluster after the fact, and lifetime counts from the first buy. Correct as a record, useless as an offer — such a setup never reaches the executor at any score. Detection takes 6 min, at worst 120 min. States: rejected: 248, expired: 151, watch: 3.

what holds setups back

gate table, holds alone

Holding back means the condition was the only one not passed — one failed among five holds nothing. The last column decides what to do: measured and did not fit is about the threshold, not measured is about the data.

conditionpassedfailednot measuredholds aloneof those, measured
market cap14925304646 · not measured 0
entry not late20220003636 · not measured 0
second source38517066 · not measured 0
risk level297119465 · not measured 1
taxes39101140 · not measured 4
24h volume31287311 · not measured 0
liquidity291111000 · not measured 0
audit3953400 · not measured 0
consensus4020000 · not measured 0
no honeypot3980400 · not measured 0
market cap: why$# against a minimum of $# × 253
entry not late: whyprice moved #% against a limit of #% × 200
second source: whytags against a buy: High Tax Token, Insider Wash Trading × 5tags against a buy: High Tax Token, Smart Money Remove Holdings, Insider Wash Trading × 4Binance closed its own signal (exitRate), the move already happened × 4#% of wallets left the Binance signal against a limit of #% × 3метки против покупки: High Tax Token, Smart Money Remove Holdings, Insider Wash Trading × 1
risk level: whythe risk level did not arrive × 94# against a limit of # × 11
taxes: whythe audit did not name the taxes × 11
24h volume: why$# against a minimum of $# × 87Token Info did not answer, no turnover visible × 3
liquidity: why$# against the $# needed (# positions of $#) × 111
audit: whythe risk level did not arrive × 3mechanisms found: #, Contract Not Renounced, Mintable Detected × 1the audit answered but gave no result × 1mechanisms found: #, Contract Not Renounced, Mintable Detected, Low Liquidity × 1найдено механизмов: # — Contract Not Renounced, Mintable Detected, Low Liquidity × 1
no honeypot: whyupstream did not declare the safety check ready, and there is no audit either × 4

what the price did after the setup

three horizons, medians

Not profit and not trades: this is the token price movement from the moment the setup appeared — the price we could have entered at, not the price the wallet paid. A move counts as a win above 2.0% of costs. Three horizons because one always flatters: fifteen minutes says whether we were in time, four hours whether the token survived its own pump.

Read measured together with the median. The longer the horizon, the fewer tokens live to a second price point — a dead token has no price — so the four-hour median is computed over survivors and flatters. We cannot remove that bias, only name it.

horizon 15msetupsmeasuredmedianabove costbestworst
rejected248207-8.5%25%+434.5%-82.9%
watch145131-7.6%32%+396.6%-89.1%
trade setup98-2.6%25%+7.7%-54.2%
horizon 1hsetupsmeasuredmedianabove costbestworst
rejected248219-22.4%13%+648.1%-99.3%
watch145134-20.6%24%+1558.8%-99.2%
trade setup98-6.0%25%+47.5%-51.0%
horizon 4hsetupsmeasuredmedianabove costbestworst
rejected24844-9.4%32%+899.6%-99.3%
watch14546-11.5%30%+323.5%-86.2%
trade setup96-14.5%17%+6.2%-58.5%

does the score rank

score in five parts

Setups with a measured outcome, split by score into five equal parts. If the formula works, the median grows from top to bottom — the main question to ask of a score.

scoresetupsmedian at one hourabove cost
25 to 3972-27.3%6%
39 to 4872-30.6%15%
48 to 5472-12.3%15%
54 to 5972-15.2%28%
59 to 7773-25.8%22%

wallets in clusters

addresses and their clusters

One cluster has one outcome and several participants, so crediting it to each counts one event many times. The modest question here: are there addresses that turn up only in bad clusters. A reason to look, not to retire.

addressscoreclusterswith outcomemedian at one hour
0xc70a…e37a65.46462-35.8%
0x2ae2…bad455.14141-34.7%
0x7852…326b59.63936-36.7%
0x68cd…b24457.03533-35.3%
0x7711…c9ba67.12322-31.3%
0x78ad…b9a740.72019-42.5%
0x81d9…1ef761.32016-39.0%
0xb226…006e53.61916-20.5%
0x0f51…9be149.51815-43.8%
0x1b2e…008f40.51818-44.5%
0x2025…8d9f52.51818-28.7%
0x3701…667150.81815-21.6%
0x9cce…ef2248.61817-32.9%
0xc900…4b9d47.71817-28.1%
0x5894…9c3f49.21615-20.9%
0x5e83…318a59.91616-31.7%
0xf03a…75a854.11616-41.4%
0xad24…e21248.81513-20.9%
0xc41c…e2f655.51515-34.7%
0xc908…9ac944.71513-55.6%

universe

subscription, bench, silence

A subscription socket holds a hundred addresses. An address that gave no trades takes a slot for nothing — but dropping it helps only if there is a replacement. Bench at zero means a cleanup would shrink the universe, not improve it.

addresses in total
390
active 383
beyond the subscription
233
the bench
subscribed
150
these are the ones judged on silence
gave a cluster
122
of 150 over the window
silent
3
longer than 48 h
retired
7
dropped from the subscription

silent: 0x8187…78510xd770…c5090x4ee0…6dac

what follows from this

conclusions and report time
  • "market cap" holds 46 setups, and in 46 cases the value was measured and did not fit — here the threshold decides.
  • "entry not late" holds 36 setups, and in 36 cases the value was measured and did not fit — here the threshold decides.
  • "second source" holds 6 setups, and in 6 cases the value was measured and did not fit — here the threshold decides.
  • Most setups (223 of 402) are held by several conditions at once: tuning any single threshold will not give one new trade.
  • 46 of 402 setups were born already expired: found later than their lifetime ran out, so they reach the executor at no score.
  • 3 of 150 subscription addresses gave no trade at all over the window. There is a replacement: 233 addresses beyond the subscription.

Report built 2026-08-25 14:04:34 UTC. No number here was picked by hand — this page and npm run calibrate call the same function. What it deliberately does not do is name the number you should set: that is a human choice, and advice fitted to one week is not a calculation.