Automating a gateway will require reworking NuBot.
How much depends on how NuBot works in such an environment.
At least the wrappers need to be updated.
If you operate two NuBots on the same account, but with different API credentials, it might be possible to have one
- trade only on the NBT/BTC pair and the other NuBot
- trade only on the BTC/USD pair (in case you want to convert some BTC to USDT)
It would be useful, that they can’t delete the orders of each other when shifting walls, but only move their own orders.
I don’t know how deleting orders works.
If it’s related to the account, it won’t work this way.
If it’s related to the API credentials, it should work.
The fallback option would be to synchronize the order shifts. As they are triggered by a change of BTC price, it should be possible to synchronize them via
"multiplecustodians":true,
configuration parameter.
It’s further required to have a corridor between a “reserve” value parameter and a “lower limit” parameter
The “reserve” prevents BTC funds from being traded to USDT; this way you can keep, say $5,000 in BTC on T2 to have it ready for trades.
The “lower limit” starts trading USDT for BTC, once the BTC on T2 start to run low.
Summarizing this:
as soon as BTC/USDT is supported by the NuBot wrapper on Poloniex, we can start testing 
