[announce] Namecoin - a distributed naming system based on Bitcoin

[snailbrain]

the .bit spec only recognizes lower case.. ? so waste of time registering capitals.. probably

Only for domain names. For other purposes it may still makes sense to use capitals.

also it might show you still have the name, but it's expired?

Nope. It's still 3400 blocks before it expires.

yes, you can do any (upper or lower).. but for .bit, only lower will matter

not sure how someone took your name, maybe ask Khal.. edit: the new client shouldn't be any difference than how it was.. is your problem not just with block explorer?


the GUI looks like this :


You can right click on a name to configure with json string.. (will eventually implement "for dummies" .bit standard fields to easily configure)

ignore click for larger view (not doing it again :d)

[snailbrain]

the gui auto-firstupdating a name still seems a bit unstable.. but please report any and all bugs

don't forget to backup your wallet..  

edit: noticed a few bugs..

wait before upgrade imo.. or please test with wallets without a lot of coins

[khal]

I've added the "dumpprivkey" rpc call to namecoin : https://github.com/namecoin/namecoin/commits/master
Could be useful to test namecoin-qt :p

Branch of namecoin-qt has been updated too :
https://github.com/namecoin/namecoin/commits/namecoin-qt


I'm trying namecoin-qt, starting to import addresses only but it seems to freeze on big addresses... and then I need a new blockchain to launch again (but, it was bootstraping at the same time I import addresses).
I'll make new tests when the blockchain will be updated :p

[snailbrain]

I've added the "dumpprivkey" rpc call to namecoin : https://github.com/namecoin/namecoin/commits/master
Could be useful to test namecoin-qt :p

there is some bug with failed auto-firstupdates at the moment, can cause balance to display incorrect (just visibly).. deleting failed firstupdate transaction seemed to fix..

cassini's problem : it's just blockexplorer shows all as lower case, i just tested earlier.. i have d/xx and d/Xx .. both seem to show in block explorer as lower case even though 1 had a capital.. so you still have the domain.

[peonminer]

Looking for someone to come represent NameCoin at the Bitcoin EU conference (http://theconference.eu) on a panel of alternative currencies. Anyone available to come to Amsterdam September 27-29 and sit on the panel with Charles Lee (coblee) and others?

Is it an expenses paid trip?

[Matthew N. Wright]

Looking for someone to come represent NameCoin at the Bitcoin EU conference (http://theconference.eu) on a panel of alternative currencies. Anyone available to come to Amsterdam September 27-29 and sit on the panel with Charles Lee (coblee) and others?

Is it an expenses paid trip?

That depends on the relevance of the person's involvement and the budget at the time. Right now, no, it wouldn't be.

[marcus_of_augustus]

snailbrain and coder : 500nmc bounty sent for first tranche of namecoin-qt gui

ba41af08809cbe5b993b6313b4f9735efed3b60c3e5bdb3c1f4d9daa67249c0c

... for next tranche, debugging and merge into namecoin/namecoin master on github.

[snailbrain]

snailbrain and coder : 500nmc bounty sent for first tranche of namecoin-qt gui

ba41af08809cbe5b993b6313b4f9735efed3b60c3e5bdb3c1f4d9daa67249c0c

... for next tranche, debugging and merge into namecoin/namecoin master on github.

thank you

[marcus_of_augustus]

snailbrain: testing the latest branch and it looks like (from the debug.log) the name_new pop-up is creating the "Automatic name_firstupdate ... " transaction twice?

Code:

Automatic name_firstupdate created for name d/bluewall, created tx: 5a6efa37eab3399d808365632257493d3313e47af8a7f5ed2e687205fe64cefb
sending: inv (37 bytes) 
updateWallet da6f03cbfc3bbddf80a4451adab890435b47ebe35e764c32aa7ce77a5edefd8c 1
   inWallet=1 inModel=1 Index=12-13 showTransaction=1 derivedStatus=1
updateWallet c41ad2083ef317d14400c8e1c829cf81470a8e4f29a8954ff69596becf834103 1
   inWallet=1 inModel=0 Index=12-12 showTransaction=1 derivedStatus=0
updateWallet da6f03cbfc3bbddf80a4451adab890435b47ebe35e764c32aa7ce77a5edefd8c 1
   inWallet=1 inModel=1 Index=13-14 showTransaction=1 derivedStatus=1
sending: inv (37 bytes) 
sending: inv (37 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
sending: inv (37 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
sending: inv (37 bytes) 
sending: inv (37 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
sending: inv (37 bytes) 
14/06/13 22:29:11 Flushing wallet.dat
Flushed wallet.dat 87ms
received: inv (37 bytes)
  got inventory: tx c41ad2083ef317d14400  have
sending: inv (37 bytes) 
keypool added key 134, size=101
keypool reserve 34
keypool keep 34
total value = 1500000
keypool added key 135, size=101
keypool reserve 35
keypool keep 35
Automatic name_firstupdate created for name d/bluewall, created tx: 156e4aa85ea82f56be91245bac112195e9f597c2ad5fa16692987648c298347f

and they have different tx number? Is this expected behaviour?

Edit: I should say also that the automatic name_firstupdate worked and used the second TX number. I had another one that failed (I used the worng JSON syntax for the name so gui needs some error checking on this before form submission) and it showed as being completed in the TX list ... but sits there not confirming of course. I dug the rand: value out of debug.log (it shows up next to message about automatic name_firstupdate failure) and fixed it manually in debug console.

[snailbrain]

snailbrain: testing the latest branch and it looks like (from the debug.log) the name_new pop-up is creating the "Automatic name_firstupdate ... " transaction twice?

Code:

Automatic name_firstupdate created for name d/bluewall, created tx: 5a6efa37eab3399d808365632257493d3313e47af8a7f5ed2e687205fe64cefb
sending: inv (37 bytes) 
updateWallet da6f03cbfc3bbddf80a4451adab890435b47ebe35e764c32aa7ce77a5edefd8c 1
   inWallet=1 inModel=1 Index=12-13 showTransaction=1 derivedStatus=1
updateWallet c41ad2083ef317d14400c8e1c829cf81470a8e4f29a8954ff69596becf834103 1
   inWallet=1 inModel=0 Index=12-12 showTransaction=1 derivedStatus=0
updateWallet da6f03cbfc3bbddf80a4451adab890435b47ebe35e764c32aa7ce77a5edefd8c 1
   inWallet=1 inModel=1 Index=13-14 showTransaction=1 derivedStatus=1
sending: inv (37 bytes) 
sending: inv (37 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
sending: inv (37 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
sending: inv (37 bytes) 
sending: inv (37 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
received: getdata (37 bytes)
received getdata for: tx c41ad2083ef317d14400
sending: tx (257 bytes) 
sending: inv (37 bytes) 
14/06/13 22:29:11 Flushing wallet.dat
Flushed wallet.dat 87ms
received: inv (37 bytes)
  got inventory: tx c41ad2083ef317d14400  have
sending: inv (37 bytes) 
keypool added key 134, size=101
keypool reserve 34
keypool keep 34
total value = 1500000
keypool added key 135, size=101
keypool reserve 35
keypool keep 35
Automatic name_firstupdate created for name d/bluewall, created tx: 156e4aa85ea82f56be91245bac112195e9f597c2ad5fa16692987648c298347f

and they have different tx number? Is this expected behaviour?

there is a few problems with it atm (the auto first update)..

it signs a transaction, but if within 12 blocks you send NMC, the transaction may become invalid. So coins for firstupdate have to be locked somehow.

Example: you have 100 NMC on a single address, create a name_firstupdate. Then you spend 1 NMC. 99 NMC are sent to you onto a new address (the change) and the firstupdate becomes invalid, since its tx-in refers to the old 100 NMC address.

also some other issues.. working on them (will get the log looked at thanks)

[phelix]

Before adding new features this list should be considered....

https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures

[snailbrain]

auto first update seems to be working..

please check for any bugs.. seems to be working fine atm.. props to the coder

binaries (mac needs updating, asking maxpower)
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

https://github.com/namecoin-qt/namecoin-qt

please check and "happy name registering"

"There's a small issue - if you reopen the client after 12 blocks, it sends firstupdates immediately (before getting enough connections) and fails to relay the transaction. After some time it relays normally though (no user intervention is required). Maybe need to add some delay."

anyone have any expired names? to make sure it doesn't show in the table (i can't find any old wallets with one)

[snailbrain]

Mac Files - Thanks to MaxPower -:
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

[erk]

auto first update seems to be working..

please check for any bugs.. seems to be working fine atm.. props to the coder

binaries (mac needs updating, asking maxpower)
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

https://github.com/namecoin-qt/namecoin-qt

please check and "happy name registering"

"There's a small issue - if you reopen the client after 12 blocks, it sends firstupdates immediately (before getting enough connections) and fails to relay the transaction. After some time it relays normally though (no user intervention is required). Maybe need to add some delay."

anyone have any expired names? to make sure it doesn't show in the table (i can't find any old wallets with one)

The Binary crashes on Snow Leopard. Where is the makefile.mac it's missing from the src dir?

[coinedBit]

awesome project idea, but I am not going to read through 40+ pages of postings just to catch up with things - maybe someone could copy/paste the most important stuff over to a website/wiki for the project, so that things will be easier to review ?

Also, I'd like to see a discussion if and how this relates to tor's onion addresses and hidden services in particular.

thank you

[virtualmaster]

On WinXP, Namecoin-qt 3.56
by console command unlocking wallet for 30s and after it trying to transfer namecoins, client crashed and after it the wallet password was not any more valid.
  only 0.3 NMC lost
Now I will try with 3.62. This looks really impressive.

[maxpower]

auto first update seems to be working..

please check for any bugs.. seems to be working fine atm.. props to the coder

binaries (mac needs updating, asking maxpower)
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

https://github.com/namecoin-qt/namecoin-qt

please check and "happy name registering"

"There's a small issue - if you reopen the client after 12 blocks, it sends firstupdates immediately (before getting enough connections) and fails to relay the transaction. After some time it relays normally though (no user intervention is required). Maybe need to add some delay."

anyone have any expired names? to make sure it doesn't show in the table (i can't find any old wallets with one)

The Binary crashes on Snow Leopard. Where is the makefile.mac it's missing from the src dir?

This is a known problem, unfortunately. I only have access to build tools for OS X Lion and beyond at the moment, and they don't produce backwards-compatible code. I'm looking into setting up a VM with Snow Leopard, but may not be able to get to it for a while.

[snailbrain]

awesome project idea, but I am not going to read through 40+ pages of postings just to catch up with things - maybe someone could copy/paste the most important stuff over to a website/wiki for the project, so that things will be easier to review ?

Also, I'd like to see a discussion if and how this relates to tor's onion addresses and hidden services in particular.

thank you

we are going to sort all this stuff out asap (wiki, new thread etc etc)

[snailbrain]

On WinXP, Namecoin-qt 3.56
by console command unlocking wallet for 30s and after it trying to transfer namecoins, client crashed and after it the wallet password was not any more valid.
  only 0.3 NMC lost
Now I will try with 3.62. This looks really impressive.

hmm, never had a problem like that..
there was some crash fix in the latest version.. how is that one doing? 3.62?

have not properly tested on XP, let us know how it goes
edit: maybe wait till all the blockchain downloaded (if you hadn't)

[gomados]

I tested 0.3.62 version and it works like a charm!!!!!

Good Coin and great project...