Use new TomP2P build 3784b7a
Update UtilsDHT2
Cleanup
Update README.md

Added a link to the Bitsquare website
Update to verison 91276e8
Merge remote-tracking branch 'origin/master'
Use testnet and server seed as default, fix logs
Add chaching flag to tests
Strip trailing whitespace
Support code coverage using JaCoCo and Coveralls

The Gradle build now supports generating code coverage reports using
JaCoCo. The reports can be run with:

    ./gradle jacocoTestReport

and then view the HTML output at:

    build/reports/jacoco/test/html/index.html

The bitsquare repository has now also been registered with a (free)
account at http://coveralls.io. Our Travis CI configuration has been
updated to publish JaCoCo XML test report data to coveralls.io, which
results in the reports found at:

 - https://coveralls.io/r/bitsquare/bitsquare

For more information on the JaCoCo and Coveralls Gradle plugins, see:

 - http://www.gradle.org/docs/current/userguide/jacoco_plugin.html
 - https://github.com/kt3k/coveralls-gradle-plugin
Merge pull request #251 from bitsquare/coverage

Support code coverage using JaCoCo and Coveralls
Refactor BitcoinModule to extend AbstractBitsquareModule
Remove UI test runner classes and .fxml files

These classes were used during individual screen creation but are now
effectively dead test code.
Introduce #close hook
Simplify references to stylesheets
Remove use of final modifier on local variables
Remove commented code
Refactor ViewLoader construction in src/main
Handle IOException within ViewLoader#load

Prior to this change, all callers of ViewLoader#load were forced to
handle the (checked) IOException declared by the #load method signature.
This resulted in a significant amount of duplicate handling logic where
nothing more than logging the error occured.

Failing to load a view represents a catastrophic error in the
application; i.e. it is not something that can be handled in any way
other than shutting the application down, fixing what is broken and
restarting the application. For this reason, any IOException raised
within ViewLoader#load is now caught, wrapped and re-thrown as an
(unchecked) RuntimeException. This will be handled by the platform's
UncaughtExceptionHandler, and a dialog will be raised to inform the user
that a fatal error has occured.

As a result all try/catch blocks around calls to ViewLoader#load have
now been removed, making for tighter, more readable, and easier to test
code.

In the future, the distinction between errors that are programmatically
recoverable and those that are catastrophic (typically developer errors)
will be used to determine whether methods in the Bitsquare API throw
checked or unchecked exceptions.
Introduce FatalException

Rather than throwing a generic RuntimeException for fatal / catastrophic
exceptions (which are typically due to developer error) throw
FatalException.