I have no clue about the inner workings of NuBot, I only use it for some purposes (modPuddle, Poloniex gateways).
@desrever might be able to answer the question for the capability of being a T3 tool as well.
With my limited knowledge I can imagine that it’s possible without to much effort.
re 1) NuBot already records price in the logs. It should be fairly simple to get a log that only contains time stamps and BTC exchange rates based on different sources.
re 2) that’s what NuBot is currently made for - albeit only for T1 and (if enabled) T2 at the moment. Should be possible to extend that to T3 reports/broadcasts.
re 3) if the liquidity that gets broadcast by NuBot is recorded, that’s pretty much all that’s required for audit. Broadcasting BTC or NBT liquidity of the registered addresses on T3 requires API access to block explorers that can be queried for the UTXO of certain addresses. If somebody doubts the validity of the NuBot reports, the UTXOs can be read from the blockchains directly and aligned with the data NuBot reported. Would be convenient to have the block height reported in the NuBot log.
I’m speaking of adjustments of NuBot although I don’t know whether it’s possible to do that with the current design of NuBot or how much effort it would be. I’m just trying to project the current features of NuBot into a future version that’s capable of doing T3 stuff.
I think it’s useful if T3 custodians are able to put orders on T1 even if they normally have all funds on T3. It’s way faster if they can just send the T3 funds to their exchange deposit address than to arrange a deal with somebody - their NuBot is already running (because of broadcasting the T3 liquidity information)!
You can run a single NuBot only on one exchange. So a T3 custodian would not necessarily active be on the exchange in need of T1 funds. But if there are T3 custodians for the most important exchanges that shouldn’t be much of a problem.
I think improving NuBot to support T3 custodians means using well-tested software and add features to it. And it saves the Nu landscape from creating a completely new software, that needs to be tested, maintained and that introduces additional complexity to the environment.
Just my thoughts…