Hardened Namecoin Peer Bootstrapping

More zeronet onion peers are needed in the Config.py "trackers" boostrap list. I would like to propose a solution that involves the "zeronet" entry in Namecoin support (in ZeroName, for which I do not have the source code) as such. Instead of being a map of subdomains --> ZeroNet site addresses, it would be an array of 2 elements, the first one being the current ZeroNet site map, and the second being an array of zeronet peer addresses, as such:

`{ "zeronet": [
{
"" : "1MZTSurvwBMiVGcMgRQTtM1tGnjBbQKA3z",
"penis" : "17xzX33PL2o3GEjX8rNmWJBZgzQypoSA7G",
"nouveauvloggeur" : "1AFFsmTYqeQMdPgfic2BGGHWgEy8R1i9Gu",
"cherjournal" : "1HhZuTC1oN8fFzwyN4RytAPruhyyMEM8Pe",
"tuetamere" : "1qyRZgfeRstryNAKPFQJnNtRdNaSY1n1B"
},
[
"zero://boot3rdez4rzn36x.onion:15441",
"zero://boot.zeronet.io#f36ca555bee6ba216b14d10f38c16f7769ff064e0e37d887603548cc2e64191d:15441",
"udp://tracker.coppersurfer.tk:6969",
"udp://tracker.leechers-paradise.org:6969",
"udp://9.rarbg.com:2710",
"http://tracker.aletorrenty.pl:2710/announce",
"http://explodie.org:6969/announce",
"http://torrent.gresille.org/announce"
]
]}`

Start with Config.py and its trackers bootstrap list, then trace the Namecoin/ZeroName "zeronet" entry; the issue notes that ZeroName source is unavailable. Determine how the proposed peer-address data would be represented and verify that additional ZeroNet onion peers are included in bootstrapping.

Escrito por el modelo de indexación a partir del texto del issue.