Milestones and follow-ups¶
After a call is delivered, we keep tracking the token and post updates as it crosses multiples of its entry. The two channels use different schedules, because they entered at different prices.
The baseline¶
Every multiple is measured against the immutable baseline frozen when the call was delivered — the same price and market cap printed on the call card.
This matters more than it sounds. The baseline is committed in the same transaction
as the call itself, so an x4 on a milestone message is always four times the number
you actually saw on the original card. It is never silently re-based against a later
price.
Premium milestones¶
Premium updates are dense early, where a step still means something, and spread out as the numbers grow:
x2 · x4 · x6 · x8 · x10 · x14 · x20 · x30 · x40 · x50 · x60 · x80 · x100
x150 · x200 · x300 · x400 · x500 …
Internally the token is tracked at every even multiple — the schedule above only decides when a message is worth sending. By x60, an update at every even step would mark moves of under two percent, and a channel that posts sixty times about one token has stopped being readable. The best calls used to be the noisiest ones; now they get roughly fifteen well-spaced updates instead.
Each message still shows the actual multiple crossed, not the nearest rung — a token that jumps from x94 to x104 is announced as x104.
Milestone messages reply to the original call, so the thread stays together in the channel. They use outcome-first copy showing the Premium entry market cap alongside the current one.
The original card is updated too¶
Alongside the milestone message, the original call card is edited in place — both the image and the caption — to carry the peak the token has reached.
This is why: the card is what gets screenshotted and forwarded, and a card still showing the entry numbers hours later is the version that travels. Editing it means scrolling back to the original call shows what actually happened, not a frozen first impression.
The figures that were only true at call time — holder count, top-10 share, token age — are dropped from the updated card rather than carried forward, because a call-time number displayed next to a peak reached six hours later is a wrong claim, not a stale one.
Free milestones¶
The Free channel's first message about a token is the x2 call — sent when a Premium call reaches twice its entry. That x2 message is the Free entry point.
Free then receives follow-ups at these multiples of the Free entry:
x2 · x3 · x5 · x10 · x25 · x30 · x40 · x50 · x60 · x70 · x80 · x90 · x100
x150 · x200 · x300 · x400 · x500 …
That is: x2, x3, x5, x10, x25, then every x10 from x30 through x100, then x150 and x200, then every x100 thereafter. The early rungs matter — a Free x2 is a Premium x4, which is where a large share of the winners top out.
Reading the dual baseline¶
Because Free enters at Premium's x2, the same price is a different multiple for each channel. Free follow-ups therefore print both:
| Price relative to Premium entry | Premium sees | Free sees |
|---|---|---|
| 2× | x2 |
the Free call (entry) |
| 4× | x4 |
FREE x2 |
| 10× | x10 |
FREE x5 |
| 20× | x20 |
FREE x10 |
The Free multiple is always the Premium multiple halved, because Free's entry was Premium's x2.
Jumps only send the highest milestone¶
If a token moves fast enough to cross several milestones between two observations, you get one message for the highest milestone crossed — not a burst of five.
Why only the highest is sent
The lower milestones are not lost; they are recorded as superseded audit evidence. They are simply not sent, because five notifications in the same second are noise, not information.
The Free x2 call is the one exception: as the Free entry point it is never superseded. A jump straight past x2 can therefore produce the Free call plus one highest follow-up.
Duplicate protection¶
How duplicate sends are prevented
Telegram has no native idempotency key for outbound messages, so duplicate prevention is handled on our side: every notification is a durable outbox row with a uniqueness key over the token, channel, milestone and rules version, and each sender holds a lease while it works.
The practical result is that you should not see the same milestone twice. If a send genuinely fails or its outcome is ambiguous, the row is marked and left for manual reconciliation rather than being blindly retried into a duplicate.
When tracking stops¶
Milestone monitoring for a delivered call ends at whichever comes first:
- 24 hours after the call, or
- 6 hours with no trading activity.
After that the call is complete and stops emitting milestones. Its recorded outcome is retained.
Autotrader positions are not bound by this
The 24-hour horizon is the notification lifecycle. If you hold an autotrader position, its exits keep watching live on-chain prices after call tracking has ended. See Exit rules.
Milestones vs. outcomes¶
A milestone message means a price was actually observed at that multiple. It does not mean you could have sold size there.
For the same reason, our headline statistic is deliberately conservative: it is the share of calls that reached at least x2 at least once. A call that reached x2 and later collapsed still counts as having reached x2 — and the later collapse is reported separately rather than quietly subtracted. We would rather publish both numbers than one flattering blend of them.