I added a FAQ to the code repository:
https://github.com/vinced/namecoin/blob/master/FAQ.mdIt answers some of the questions brought up in this thread and more.
@memvola @dmp1ce - a DNS bridge would be great. Yes, the value should be a zone file, and can have either addresses or a DNS delegation. I don't know if DNS delegation works well behind Tor, so maybe addresses are better.
@dmp1ce - thank you for the offer. I'd be ever grateful if you could register the name d/v . This would end up being v.bit after the DNS piece is available.
A couple of design questions to think about:
- right now the expiration is set to 12000 blocks, or about 3 months. Is that too short? Renewal will be automatic if your client is connected.
- should the TLD be .bit or something that ICANN is unlikely to ever register, like .b, .n or even .-b?
Thank you for writing the software and explaining how it works. I'd be happy to reserve d/v for you.
I had some questions about the faq though, it says:
Q: How long are names good for?
A: You have to execute an update on a name every 12000 blocks (normally about three months), or it expires. There is no network fee for updates.
Does that mean I can spend all of my NC on domains and not have to worry about leaving leftovers for updates? I thought that updates cost 50 NC but decreased over time.
About the design questions, I have not a clue. I think 3 months is reasonable, especially if it auto renews. Why do we have to decide on the TLD? Is it possible that Namecoin names could specify the TLD to use as well?