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

virtualmaster

hero member

Activity: 504

Merit: 500

Quote from: snailbrain on June 16, 2013, 04:22:46 PM

the commands should still be there.. are you sure using the correct version?

I think so. This is staying there.
Namecoin version 0.3.62
Copyright © 2009-2013 The Bitcoin and Namecoin developers

help

backupwallet
buildmerkletree ...
createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...}
decoderawtransaction
deletetransaction
dumpprivkey
encryptwallet
getaccount
getaccountaddress
getaddressesbyaccount
getauxblock [ ]
getbalance [account] [minconf=1]
getblockbycount height
getblockbyhash hash
getblockcount
getblocknumber
getconnectioncount
getdifficulty
getgenerate
gethashespersec
getinfo
getmemorypool [data]
getnewaddress [account]
getrawtransaction [verbose=0]
getreceivedbyaccount [minconf=1]
getreceivedbyaddress [minconf=1]
gettransaction
getwork [data]
getworkaux
help [command]
importaddress [label] [rescan=true]
importprivkey [label] [rescan=true]
listaccounts [minconf=1]
listaddressgroupings
listreceivedbyaccount [minconf=1] [includeempty=false]
listreceivedbyaddress [minconf=1] [includeempty=false]
listtransactions [account] [count=10] [from=0]
listunspent [minconf=1] [maxconf=9999999] ["address",...]
move [minconf=1] [comment]
name_clean
name_debug
name_debug1
name_filter [regexp] [maxage=36000] [from=0] [nb=0] [stat]
name_firstupdate []
name_history
name_list []
name_new
name_scan [] []
name_show
name_update []
sendfrom [minconf=1] [comment] [comment-to]
sendmany {address:amount,...} [minconf=1] [comment]
sendrawtransaction
sendtoaddress [comment] [comment-to]
sendtoname [comment] [comment-to]
setaccount
setgenerate [genproclimit]
setmininput
settxfee
signmessage
signrawtransaction [{"txid":txid,"vout":n,"scriptPubKey":hex},...] [,...] [sighashtype="ALL"]
stop
validateaddress
verifymessage

that's all
---------
walletpassphrase
Error: running with an unencrypted wallet, but walletpassphrase was called. (code -15)

It seems that the command is there only help is not listing it.

snailbrain

legendary

Activity: 1807

Merit: 1020

Quote from: virtualmaster on June 16, 2013, 03:34:07 PM

Quote from: snailbrain on June 16, 2013, 10:44:36 AM

Quote from: khal on June 16, 2013, 10:38:28 AM

A small bug report :

I transfered a name to a fresh namecoin-qt wallet, and in the transaction list it appears as "(n/a)" 0.00NMC (without the namecoin icon).
This wallet does not have the change address for that tx (it is in the other wallet) nor the input addresses.

However, the name appears in the "Manage names" tab.

Then, I've done a name_update from the GUI, and this one has the right label and icon in the transaction list (not yet confirmed, but should be ok).

did you try 3.62?

Yes.
without wallet encryption
I tried now transaction and domain registration from GUI. It works fine. Importprivkey, importaddress and dumpprivkey works from the console.
By dumpprivkey first time remained hanging but second time worked.
As I see walletpassphrase and walletpassphrasechange was removed from the command list. In 3.56 was there.

I will try with encrypted wallet also to make transaction but from the console is difficult without the removed commands.
Transaction fee to move less then 1 namecoin inside of my wallet was 0.005 NMC, 1/3 of a domain registration fee. Was the same with the old wallet ?

the commands should still be there.. are you sure using the correct version?

virtualmaster

hero member

Activity: 504

Merit: 500

Quote from: snailbrain on June 16, 2013, 10:44:36 AM

Quote from: khal on June 16, 2013, 10:38:28 AM

A small bug report :

I transfered a name to a fresh namecoin-qt wallet, and in the transaction list it appears as "(n/a)" 0.00NMC (without the namecoin icon).
This wallet does not have the change address for that tx (it is in the other wallet) nor the input addresses.

However, the name appears in the "Manage names" tab.

Then, I've done a name_update from the GUI, and this one has the right label and icon in the transaction list (not yet confirmed, but should be ok).

did you try 3.62?

Yes.
without wallet encryption
I tried now transaction and domain registration from GUI. It works fine. Importprivkey, importaddress and dumpprivkey works from the console.
By dumpprivkey first time remained hanging but second time worked.
As I see walletpassphrase and walletpassphrasechange was removed from the command list. In 3.56 was there.

I will try with encrypted wallet also to make transaction but from the console is difficult without the removed commands.
Transaction fee to move less then 1 namecoin inside of my wallet was 0.005 NMC, 1/3 of a domain registration fee. Was the same with the old wallet ?

khal

hero member

Activity: 540

Merit: 500

Quote from: phelix on June 16, 2013, 12:08:00 PM

vote for namecoin!

https://bitcointalksearch.org/topic/most-promising-alt-coin-other-than-bitcoin-235025

Done !

phelix

legendary

Activity: 1708

Merit: 1020

vote for namecoin!

https://bitcointalksearch.org/topic/most-promising-alt-coin-other-than-bitcoin-235025

khal

hero member

Activity: 540

Merit: 500

Quote from: snailbrain on June 16, 2013, 10:44:36 AM

Quote from: khal on June 16, 2013, 10:38:28 AM

A small bug report :

I transfered a name to a fresh namecoin-qt wallet, and in the transaction list it appears as "(n/a)" 0.00NMC (without the namecoin icon).
This wallet does not have the change address for that tx (it is in the other wallet) nor the input addresses.

However, the name appears in the "Manage names" tab.

Then, I've done a name_update from the GUI, and this one has the right label and icon in the transaction list (not yet confirmed, but should be ok).

did you try 3.62?

I should have using it, but did not finished the compilation (not enough ram at that moment)...
Sorry if it is already fixed.

* khal is compiling

[edit: it's ok with 3.62]

snailbrain

legendary

Activity: 1807

Merit: 1020

Quote from: khal on June 16, 2013, 10:38:28 AM

A small bug report :

I transfered a name to a fresh namecoin-qt wallet, and in the transaction list it appears as "(n/a)" 0.00NMC (without the namecoin icon).
This wallet does not have the change address for that tx (it is in the other wallet) nor the input addresses.

However, the name appears in the "Manage names" tab.

Then, I've done a name_update from the GUI, and this one has the right label and icon in the transaction list (not yet confirmed, but should be ok).

did you try 3.62?

khal

hero member

Activity: 540

Merit: 500

A small bug report :

I transfered a name to a fresh namecoin-qt wallet, and in the transaction list it appears as "(n/a)" 0.00NMC (without the namecoin icon).
This wallet does not have the change address for that tx (it is in the other wallet) nor the input addresses.

However, the name appears in the "Manage names" tab.

Then, I've done a name_update from the GUI, and this one has the right label and icon in the transaction list (not yet confirmed, but should be ok).

gomados

member

Activity: 96

Merit: 10

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

Good Coin and great project...

snailbrain

legendary

Activity: 1807

Merit: 1020

Quote from: virtualmaster on June 16, 2013, 08:12:33 AM

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.
Grin

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)

snailbrain

legendary

Activity: 1807

Merit: 1020

Quote from: coinedBit on June 16, 2013, 07:50:06 AM

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)

maxpower

sr. member

Activity: 456

Merit: 250

Quote from: erk on June 16, 2013, 07:09:59 AM

Quote from: snailbrain on June 15, 2013, 09:22:55 AM

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.

virtualmaster

hero member

Activity: 504

Merit: 500

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.
Grin

only 0.3 NMC lost
Now I will try with 3.62. This looks really impressive.

coinedBit

newbie

Activity: 14

Merit: 0

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

erk

hero member

Activity: 826

Merit: 500

Quote from: snailbrain on June 15, 2013, 09:22:55 AM

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?

snailbrain

legendary

Activity: 1807

Merit: 1020

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

snailbrain

legendary

Activity: 1807

Merit: 1020

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)

phelix

legendary

Activity: 1708

Merit: 1020

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

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

snailbrain

legendary

Activity: 1807

Merit: 1020

Quote from: marcus_of_augustus on June 14, 2013, 05:44:48 PM

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)..

Quote

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)

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

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.

Topic: [announce] Namecoin - a distributed naming system based on Bitcoin - page 66. (Read 596107 times)