Post
Topic
Board Project Development
Re: [ANNOUNCE] BuyBIT - Unofficial .bit registrar
by
someguy123
on 15/05/2012, 23:06:54 UTC
I've hit a small roadspike in the development of this...
The automation of setting off a name_firstupdate once the name_new has hit 12 blocks isn't too simple as I can't track the transaction ID.
name_new does return a long and short value, but there's no transaction ID returned, so it's not exactly easy to track the transaction to check whether it's hit 12 confirms or not.
I'm planning on a quick (possibly temporary) fix by storing the  block number at which the domain was pre-ordered, and then when the cron is ran in order to firstupdate all domains which are ready, checking which domains have been waiting at least 20 blocks after their name_new.
If anyone knows of a cleaner way of ensuring the domain has hit at least 12 confirms, your comments will be greatly appreciated.

Disregard that. I'm an idiot.

Also an update on the progress:
Done:
  • Namecoin/bitcoin deposits
  • Registration and login system
  • Obtaining domain information
  • (MOSTLY) Handling domain purchases
  • Bootstrap design

To-Do
  • Finishing the domain purchasing
  • Adding more javascript validation in order to make the user experience a little bit smoother
  • Adding more security to the login (Captchas after several failed attempts, and lockouts after too many)
  • Cleaning up dirty debugging hacks all over the code
the problem with .bit domains is that it is hard to access them.  I figured it out but it involved adding another DNS server, which is weird since, if I have a namecoin client running I have all the info in its blockchain and I should be able to pull the info from there.  If anyone has some experience working with firefox extensions it should be possible to make something like the TOR .onion domains extension.
I really do hope someone is able to create a firefox and/or chrome extension for namecoin, that way .bit's are more accessible.
Foxyproxy already allows DNS requests to be forwarded through a selected proxy, so I'm pretty sure it'd be possible to maybe create an extension that could check for http://*.bit/ and forward the DNS request through one of the existing namecoin DNS servers.