square / beancounter / 131

38%

master: 41%

Pull #17

travis-ci-com

Make accounter schedule transactions explicitly

This should:
  a) simplify backend logic. There are now AddrRequest<->AddrResponses and
     TxRequest<->TxResponses pipelines. Backends don't have to track
     transactions that are seen in order to avoid sending duplicate
     entries to the accounter.
  b) make sure accounter stops when all the transactions are received
     from the backend. The accounter keeps track of derived and processed
     addresses. It can now see how many transactions each address has
     and then schedule those transactions accordingly with the backend.
     Then it knows, how many (non-duplicate) transactions it has to receive
     before completing the fetchTransactions step and moving to
     processing all the transaction information.

140 of 140 new or added lines in 5 files covered. (100.0%)

417 of 1066 relevant lines covered (39.12%)

0.85 hits per line