web3 1.0 introduced eth_subscribe api for watching events, this API is not compatible with http providers and requires a web socket provider.
Currently, the compatibility check doesn't account for that making the TimeNode to silently fails and thus not discover incoming transactions.
The immediate fix is to enable websocket endpoint on your node and use it to connect.
web3 1.0 introduced eth_subscribe api for watching events, this API is not compatible with http providers and requires a web socket provider.
Currently, the compatibility check doesn't account for that making the TimeNode to silently fails and thus not discover incoming transactions.
The immediate fix is to enable websocket endpoint on your node and use it to connect.