v0.4.6 - Quality of life improvements

This release improves on some small things and fixes a minor bug:

• Added support for Basic HTTP Auth when using a custom RPC URI (see user_data/config.example.yml)
• Fixed dex.guru links which did not support URIs without the -bsc suffix anymore
• Added link for DEXT (dextools.io)
• Normalized amounts display in status messages to have the code markup everywhere (easier to copy-paste on some clients)
• Added BNB price in summary status message
• Fixed orders' type icon in /removeorder conversation and added list of orders at order selection step.

v0.4.5 - Bug fixes and small improvements

This released focused on ironing out a few bugs that were discovered.

Fixed:

• A bug was present when the configurable monitor_interval was set to a value not divisible by 5. #9
• The config's RPC-URI validation regex did not accept URIs without a port number 45a24e2
• When an token returns a zero price, due to not having a PcS LP or the LP being empty, creating and order would spam messages in the chat every monitor_interval seconds. This message is now only logged in console. db5d03d
• The prompt for the wallet's private key, when not defined in environment, was displaying the now removed wallet address config item, resulting in a cyclic dependency. This has been fixed. 08f1b98
• There was a division by zero error when user edits effective buy price for a token that has zero balance 2687e8b

Modified:

• The python-telegram-bot library dependency has been upgraded to latest
• Added emojis to the buttons for order type selection and display #4 (comment)

v0.4.4 - Faster status messages, wallet address not needed

This version includes the following changes:

• The summary status message now includes the wallet's BNB balance, total balance of tokens in BNB, and the sum of both
• The status messages have been optimized to make fewer network requests, thus being overall faster now
• The way the bot handles transaction receipts has been improved, to use the event data defined in the ABI for each contract (this is used to extract the amount of received tokens/BNB).
• The config file doesn't include the wallet address anymore, as it can be inferred from the private key which is anyway provided. You can remove the wallet item in your config file. This item, as well as bscscan_api_key, are deprecated and will raise an error in version 1.0.0.

v0.4.3 - Docker images!

This version now adds automatic docker builds. Refer to the Readme for instructions on how to run this bot using docker.

A bug was also fixed, whereby the effective buy price after a transaction was not shown in the token status message until another order was added to that token, or the bot was restarted. This is now fixed.

v0.4.2 - More charts and bug fix

This version fixes a critical bug where status messages would not update anymore.

Links to Poocoin, Bogged and Dex.Guru charts are now displayed for each token.

v0.4.1 - Structure modfication, new token editing command and more

IMPORTANT MIGRATION NOTE

If you are updating from 0.3.x, please note that you need to move your config.yml and pancaketrade.db files inside the new user_data directory before starting the bot. This was done in preparation for the release of docker images.

This version comes with a few very nice changes:

• Added missing /sellall command to the commands list dropdown
• Prepared files for future docker release, please don't use yet as it's not been thoroughly tested
• Approval requests now check proper gas limit estimate before submitting transaction (in the past, a hardcoded value was used)
• Revamped /edittoken command to have a branching flow instead of linear.
• Added option to manually edit the effective buy price for each token, via the /edittoken command. Can be calculated from BNB amount or directly input as price value (#2)
• Total value of all tokens is shown in the last message of the status command.

v0.3.0 - Price tracking

This version adds price tracking to the bot (#2).

When making a buy order, the effective buy price (after tax) gets saved together with the token record in the database.
In the status message, the effective buy price, as well as difference to current price (in percent), is shown, allowing to see if the position increased or decreased since buy.

When a sell order is made, this price is not changed. However, if a second buy order happens, a weighted average between the new effective price and old effective price is calculated and replaces the old price.

v0.2.4 - BscScan API no longer needed

This update and 0.2.3 from earlier today improve and normalize the token amounts rendering.

What's more, BscScan API is no longer needed as the script now uses local default ABIs for all contracts. This should be faster and more reliable. We only use a couple of functions for tokens and these are defined in the BEP-20 token interface so all tokens should have them implemented. This makes it seamless to interact with proxy contracts also.

If you have the bscscan_api_key entry in your config file, you can remove it now.

v0.2.2 - Better auto-approval process

The auto-approval process is now smarter. If a buy order is placed, the tokens are first bought, then the wallet is approved for selling. If a sell order is placed while the address is not yet approved, it's mandatory to approve first, before selling.

This is only done once per token and per pancakeswap version. The process is smart and only approves on the version that will be used for selling at the best price (when both versions are available).

Added "Buy/sell now" and "Create order" buttons to the "Token added" confirmation message, for even faster buy after adding a new token.

v0.2.1 - Small fix for cancel command

There was a bug with the "cancel" button on the list of tokens that would catch all cancel commands for other commands.