Currently arbiter polls /bounties/pending in a loop with a time.sleep(1) at the end, should use the websocket event route instead similar to microengine
This will remove the need to set up web3 and get the block number as well. Only component that should need to talk to the eth client directly is polyswarmd.
Currently arbiter polls /bounties/pending in a loop with a time.sleep(1) at the end, should use the websocket event route instead similar to microengine This will remove the need to set up web3 and get the block number as well. Only component that should need to talk to the eth client directly is polyswarmd.