Add compatibility layer for Binance.us API

[NightWalkAX]

Currently, the bot only supports the global Binance platform. Many users in the United States are unable to use Binance.com and instead use Binance.us, which has some differences in its API and available endpoints.

It would be great to add a compatibility layer or adapter that allows the bot to operate seamlessly with Binance.us. This may require handling API differences, authentication changes, and ensuring all features work as expected on both platforms.

I would like to contribute to this project by implementing a compatibility layer that allows the bot to operate seamlessly with Binance.us. This will require handling API differences, authentication changes, and ensuring all features work as expected on both platforms.

Why this matters:

• Expands the user base to include US-based traders
• Future-proofs the project against regional restrictions
• Makes the bot more flexible and inclusive

What I plan to implement:

• Create an abstraction layer for exchange-specific logic
• Handle any missing features or endpoints in Binance.us
• Add thorough testing for both Binance.com and Binance.us

I'm ready to start working on this feature and would appreciate any guidance or feedback from the maintainers. Looking forward to contributing to this project!

cc: @asavinov

[asavinov]

The current binance Client support access from special regions like us or jp in its arguments. I implemented the possibility to pass arbitrary arguments to the client by adding a new attribute to the config file, for example:

"client_args": {"tld": "us"}

Actually, all other attributes can be specified via client_args:

"client_args": {"api_key": "<binance-key>", "api_secret": "<binance-secret>", "tld": "us", testnet=true}

In this case, the old dedicated attributes api_key and api_secret are not needed (they will overwrite the corresponding attributes in the client_args.