# v1.1 Update (Minor)&#x20;

**V1.1**

**Official Update Notes For BENiBOT**

Contributors: *Beni CTO Development Team* @Benionbase,

Date: 20 DECEMBER 2024

Schedule: MINOR unplanned update.

**Update Overview**\
We have successfully deployed an update for BENiBOT. Due to the significant volume at launch, we needed to ensure our servers could manage the demand while simultaneously providing users with the fastest and most cost-effective transactions. BENiBOT will now route to the DEX / LP with the highest ratio of tokens-to-ETH per swap with limited to no downtime. This is in addition to laying our V2 MEV framework which was packaged into this update.

**This update includes the following upgrades or modifications:**

1. **Upgraded service providers**\
   We have upgraded our service providers to ensure maximum uptime. We now leverage leading platforms like Gecko API to deliver the fastest and most consistent portfolio data currently available on the market.
2. **BENiBOT Smart Routing**\
   BENiBOT now employs smart routing to direct your trades to the most liquid pools or DEXs, ensuring you receive the maximum number of coins per ETH traded. This is in response to a bug where BENiBOT would select an incorrect pool and the transaction would fail making seem like a token was not tradable. This “smart routing” feature leverages computational power and automated decision making to allow BENiBOT to instantly compare prices across all available DEXs, routing your transactions to the best match without the need for manual selection, thus maximizing tokens for your ETH and saving users’ time.
3. **MEV Infrastructure Upgrade:**\
   In preparation for our V2.0 launch, we have taken a brief downtime to fortify our infrastructure. This upgrade focuses on enhancing our MEV capabilities, which will be fully operational in BENiBOT V2. This essential groundwork was necessary to support our anticipated infrastructure and will reduce downtime for a V2 update.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://organizations.gitbook.io/benibotdocs/documents/release-notes/v1.1-update-minor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
