Weekly update 10.5.

[chimp1984]

I moved the torify lib into the misq project to make it easier for code changes. The torify lib serves now only for providing the pom file for resolving the tor binaries. As that is done in non trivial maven tasks I did not spend time to try to get the converted to gradle or to find the solution how to add a maven pom into a gradle project.
It is also not clear yet if we leave the tor library in misq or if it will be moved back once its final.

I cleaned up the torify lib a bit and added better error handling. It would still require some work and specially testing to get it production ready. If any dev experienced with tor want to take those tasks would be welcome.

I am working on the peer exchange and bootstrapping.
The asynchronous bootstrapping from the nodes with the request/response protocol makes it difficult to test. Wondering about better design to make it less complex.
The basics are decribed here:
https://github.com/chimp1984/misq/wiki/P2P-network---peer-domain
Code is not checked in yet as its still too much in testing but will get checked in soon.

I improved the POC model structure for the contract execution and added the basics for the offer domain. Very preliminary and was only intended to see if its managable. Beside that I needed a more clear picture for the offer domain as background for the project proposal for an UX prototype: bisq-network/projects#57

[chimp1984]

Pushed my current code base to https://github.com/chimp1984/misq

I think the peer management will require a different approach using network graphs for testing and network simulations.
I tested manual boostrap up to 4 nodes, but that approach does not scale of course. Testing it with a loop of 10 nodes did not result in the expected states, but it gets quickly complex to define the expected state.