Bot commands · Which signals are traded

/setMinCoinAge: skip coins that were listed recently

/setMinCoinAge sets how many days a coin must have been listed on Binance Futures before the bot trades it, from 0 (off, the default) to 365, Tier 2 and 3.

Command
/setMinCoinAge
Also on this page
/myMinCoinAge
Who can use it
Tier 2 and Tier 3, with auto-trading switched on
Where
In your chat with @hafizebot on Telegram

Newly listed coins often move in ways older ones do not. With a minimum coin age set, the bot skips every signal on a coin that has been on Binance Futures for fewer days than that. Signals on other coins are not affected.

Examples

/setMinCoinAge 30
Minimum coin age updated to 30 days.
/myMinCoinAge
Your Minimum coin age: 30 days

A signal on a coin that is too new, in /lastsignals:

Oct 12 09:42 UTC NEWUSDT LONG, strength 3: skipped: the coin was listed on Binance more recently than your minimum (/setMinCoinAge)

Values

Setting Value
Range 0 to 365 days
Starts at 0 (off)

Questions

How is the age counted?

In whole days from the moment Binance listed the coin on its futures market until the signal arrives.

What if the listing date cannot be read?

The coin is skipped, and /lastsignals says the listing date could not be read. A signal is never traded on a minimum the bot cannot check.

Why is this a Tier 2 and 3 setting?

It is one of the filters that come with those plans, next to /banGroup and /banSignal. Your plans and what they include: /plans.

Updated 2026-10-12.

Related commands

More help

Not a member yet? Try VIP free for 3 days, auto-trading included. No Telegram yet? Get a code by email.

A question this page does not answer? Send /support to @hafizebot, or write to [email protected]. Futures trading carries a high risk of loss; nothing here is investment advice.