Bug :
    possible bug in the upnp refresh, when refreshing after a too long time
    
To be done :
    Choose the db size and how peers are deleted
    find out who to have an automatic recovery without declare
    Test the package

    at the beggining a node tries to find 10 other nodes so ask for 10 bootsrap nodes
    This slow the beginning and might overload the server
    If their is too many nodes flaged as bad, the node never ask for some bootstrap peer

    When a node arrive it is in nobody DB => very slow beginning. It should advertise itself more.

    check the ips attributed
    remove decalre
    how do we make sure that none inject some false packets ?
    how do we make sur that noone is declaring too much false nodes ?

---------------------------------------------------------------------------------

    Put more information in the token mail ( registry ), such as :
        - the ip address of the network being built
        - the creator of the network ( add option in registry ? )

    Fix bootstrap problem :
        registry & --private option ( see re6stnet man page HOW TO ).
        one have to start the registry twice, the first time without
        the --private option

    Put a section about how to build the package from the sources in the README

http://pdos.csail.mit.edu/p2psim/kingdata/
http://www.eecs.harvard.edu/~syrah/nc/king/lats.n8.gz
http://www.cs.cornell.edu/People/egs/meridian/data.php