We've discussed the option to setup an initial and stable network. We have the possibility to use the EmanicsLab project and their infrastructure. This requires some improvements in our library. The ultimate goal would be that several different applications using H2H are sharing the same network. This would lead to a more stable network. Currently we have to target following limitations/issues:

• Secure bootstrap. See issue Secure Bootstrapping #61.
• H2H currently uses only three (location, content, version) key ranges of TomP2P's key ranges (containing four key ranges). We could use the forth key range (domain key) so that different applications are using they own domain (additionally domains can be protected). This would avoid possible (but very very rare) collisions. The largest benefit would be a clear separation which would make development and usage of the H2H library more understandable.
• Messages sent between H2H nodes should be distinguishable between the different applications. This would require to refactor the current MessageReplyHandler class (which is responsible for handling the received massege) into a more generic way. E.g. applications may register with an prefix or something.