Wouldn't it be more useful to create a separate P2P backup of the exising TLD's (and expirations) so that all people would need to do is redirect their existing dns settings to some kind of internal proxy that dealt with the p2p dns lookup in a seamless way? This way, basically all people would have to do is install a client (which would set up the dns proxy for them) and then start funneling requests through that proxy when domains are removed from the system pre-expiration. If it could be anonymized, the client could also watch outgoing DNS requests to ICANN and then adjust IP's in supernodes with some kind of consensus (to help prevent poisoning) model accordingly. I'm all for the idea though.
I like the idea, I haven't touched programming in years as I'm working mainly on support now but if there is a way I could contribute please let me know.
Almost gave you a thumbs down, but decided to see what happens first. Because I like the idea. I really do. But if all you're doing is adding a new TLD of .p2p, it's not going to go anywhere. It'll be just another dead or dying alternate DNS project. So I hope you have bigger plans for this. _MUCH_ bigger. And I pray that the .p2p TLD is just a starting test. I mean, the idea should be to replace ICANN...or at least providing a backup to it. And to do that, you need to show that it can handle the entire load of ICANN. And for some reason I highly doubt that .p2p will even hit anywhere near the load of even some of the smallest ICANN TLDs. Anyway, sorry to be a downer, I'm sure you've already considered that. Best of luck to you, and I look forward to trying it out.