etomic-swap VS ccxt

Taker Sends >B pays the dex fee so that A will start the process by locking his coins.2) Maker Successfully Sends >A picks randomNumber: `secret_A`A creates a utxo on the Bitcoin blockchain with value: 1 BTC encumbrance: the value can be claimed by A after 20 hours or by B if he knows the secret `secret_A`3) Taker Successfully Sends After seeing the above utxo, B creates the following utxo on the KMD blockchain: value: 100 KMD encumbrance: the value can be claimed by B after 10 hours or by A if he knows the secret `secret_A`4) Maker Spends A uses the `secret_A` and claims the KMD, thereby revealing the secret5) Taker Spends B now uses the public `secret_A` to claim the BTCThe times can be adjusted based on requirements of security and "ease of use" Normally, A should have a longer locktime so that B can have sufficient time to get his coins back if A doesn't reveal the secret `secret_A`for eth, CLTV and other bitcoin specific OP\_CODES are replaced by a smart contract, whose code is here: [https://github.com/artemii235/etomic-swap](https://github.com/artemii235/etomic-swap))the cross-platform implementation of the protocol is here: [https://github.com/KomodoPlatform/atomicDEX-API/](https://github.com/KomodoPlatform/atomicDEX-API/))Its [android GUI is in beta and can be tested right now](https://play.google.com/store/apps/details?id=com.komodoplatform.atomicdex&hl=en), iOS version is in [testflight](https://testflight.apple.com/join/c2mOLEoC)You can read about the Komodo team's implementation of the protocol [here](https://developers.komodoplatform.com/basic-docs/start-here/core-technology-discussions/atomicdex.html#introducing-taker-and-maker) and instructions to use the DEX through the CLI [here](https://developers.atomicdex.io)The atomicDEX application needs access to privkeys currently, but they never leave your device. We are also planning Hardware wallet support in the 0.6.0 release. This should alleviate most concerns with privkey access.

Deploy the 1.0 release of EtomicSwap contract to SmartBCH mainnet: https://github.com/artemii235/etomic-swap/releases/tag/1.0.

CCXT

I would sincerely advise you to use a ready to use python library for this like https://github.com/ccxt/ccxt

CCXT has good documentation on what exchanges and API's are supported which is very helpful. https://github.com/ccxt/ccxt/wiki/Exchange-Markets-By-Country

Consider using https://github.com/ccxt/ccxt for crypto exchange interaction, which of course will support Binance too

Check out https://github.com/hummingbot/hummingbot (disclosure: my project). We just added a Binance candles feature where you can construct custom OHLCV candles and TA indicators. You should also check out https://github.com/ccxt/ccxt which has broader exchange support but less order book data management than Hummingbot.

Or if you stick to JavaScript and willing to learn the programming part, then https://github.com/ccxt/ccxt (which is now merged with CCXT Pro but still for free).

Ccxt works great for me and it's free and open-source. You can connect and execute on multiple exchanges. It works with Javascript, Python and PHP.

if you're going crypto, try CCXT https://github.com/ccxt/ccxt

Essentially, to create an automated trading system using TradingView strategies, you would need to acquire the signal using webhooks. Once you acquire the signal, you can use whatever data send with it to manage orders, using the API of your broker. Usually, there are SDKs available to make this process easier. For crypto, one of the most well known SDKs is called CCXT. There are also some made for traditional brokers too. It is a simple process but it does take some experience with programming systems to set up.