Is Binance engaging in Insider trading? The announcement page delay and crypto trading bot

For the past two or so months I’ve been building and testing a crypto trading algorithm that looks at the Binance announcement page, in order to quickly buy a new coin listing and make some nice gains on that. The tool went through several changes until reaching its latest form. This python crypto trading bot scrapes the Binance announcement page looking for new coin listing announcement, and if one is found, it will buy it on If you’re interested in trying out the tool – this guide can get you started on the crypto trading bot

Since the last re-write of this tool, me and several other people who were testing this tool came across something potentially suspicious regarding the Binance announcement page and how Binance handles its timestamps.

I also talked about this in my recent video, so feel to check this out, or keep on reading:

But first, it’s important to understand why the bot works by scraping the announcement page, as this will offer a better understanding into why it’s possible that Binance might be manipulating their announcement page.

While testing previous iterations of this bot, it turned out that big spike in the price of  newly listed coins on Binance actually happens once the announcement is made, and not when the coin is listed – that is just the tip of the iceberg. So naturally, after observing this, it was time to adjust the tool to do just that. The reason it uses is because this exchange is more relaxed with their listings compared to Binance so there’s a good chance that a coin about to be listed on Binance, is already available for trading on

 Have a look at the time this coin spiked, and the announcement timestamp for CHESS/USDT – the most recent announcement that the bot actually caught:

You can clearly see in the image above that the coin started pumping on other exchanges at 03:36 – exactly when the announcement was made. The good news is that the trading algorithm successfully managed to place an order on after detecting this announcement.

Now here’s the thing though – It’s actually possible that Binance is backdating this announcement timestamp. According to the logs generated by me and everyone else who happened to run this bot at that time, the bot detected this announcement 5 minutes later at 03:41. Naturally, this was too late to make any profit.

Everyone who was running my bot at that time confirmed the same thing – there is a 5 minute delay between Binance’s Announcement timestamp and the time at which the bot detected this announcement. I’ve inspected my code and there’s nothing to show that it would have been delayed. The bot was checking this page normally every 10 seconds.

Although unlikely, it could have just been an unexplainable issue with the bot, right? Wrong. There are not of results online about this, but sure enough someone came across this exact issue 5 months ago:


The replies on the stackoverflow state that it might be one of two things:

  •  The CDN is caching page content locally, crating the 5 minute delay
  • Binance is purposefully restricting and delaying this information so that an exclusive group of people can make money on this before everyone else.

If the second option is true, then Binance is engaging in insider trading – and I’m hoping that’s not the case.

Whether it’s the first or the second option, the truth is that, if this issue is consistent, the vast majority of us won’t be able to make money on new coin listings.

Though one thing is clear – someone must be making a huge profit in the first minute before the delay, the question is who?

In anticipation of another “delay” the bot now has a lot more logging installed so we can all understand what exactly is going on on their page. (thank you to everyone who contributed to the codebase!)

Did you enjoy this article? Here’s what to do next…

Consider donating at the widget next to the top of the page or via the brave browser. Your donations help keep this content free and open source.
If  you’re looking for a custom-built cryptocurrency trading algorithm, shoot me a message and let’s talk
Subscribe to the newsletter for more awesome content!

9 thoughts on “Is Binance engaging in Insider trading? The announcement page delay and crypto trading bot

  1. Fantastic articles!!!

    Could the delay also not be down to 5 mins of waiting for emails to arrive through the email gateways especially if a large number are being sent. Could some regions get there emails through quicker than others. Would an email server in Tokyo recieve an email quicker than one in the UK or USA?

    Is there an announcement on the Binance website that is more accurate regarding timings?

    Is there still enough price scope to buy on say 24 hours or more later when the price has gone down somewhat and still make a sensible profit selling on the Binance listing?

    Just some thoughts,

    Keep up the great work,



  2. You should be able to test #1 by appending s timestamp to the url. I believe CDNs use the URL as the cache key. So if you want to force a fresh copy of the page and skip the cache, modify the url to be Wouldn’t that force to not http// timestamp={time.time()}

  3. I think if you can link your code with official Binance telegram, it will pick up the information faster. I checked the last listed coin which is BNX in the website (9:55 am) and in telegram (9:57 am). If you think the website is delayed by 5 minuets then with telegram you will save 3 minuets.

  4. Hello Andy,

    at first sorry for my bad english.

    Many thanks for your good job of the bot. It is very interesting.

    I have the same problem as you. Every day I check the Binance Listings with auto-refresh and everytime I see the new Listing 2 minutes later. The timestamp ist everytime 2 minutes earlier as the announcement appears on the Listing Page.
    Because of this I searching with google and found your website.

    Do you have new findings and works it now better with the bot after the lateset update?

    Kind regards


Leave a Reply

Your email address will not be published. Required fields are marked *