Pages:
Author

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

legendary
Activity: 1807
Merit: 1020
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
legendary
Activity: 3920
Merit: 2349
Eadem mutata resurgo
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.
hero member
Activity: 588
Merit: 500
Hero VIP ultra official trusted super staff puppet
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.
hero member
Activity: 798
Merit: 531
Crypto is King.
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?
legendary
Activity: 1807
Merit: 1020
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.
hero member
Activity: 540
Merit: 500
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
legendary
Activity: 1807
Merit: 1020
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
legendary
Activity: 1807
Merit: 1020
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)
member
Activity: 112
Merit: 10
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.
legendary
Activity: 1807
Merit: 1020
if the auto firstupdate doesn't work, you can get the Hex numbers from debug.log. Search for "Automatic name_firstupdate".
the transaction for firstupdate is created and signed immediately (when entered pw), but not broadcasted, still debugging why it crashed.

As firstupdating a name can be done in two different ways:
a) name_new, and instantly issue the name_firstupdate
b) name_new, then wait for 12 blocks before a name_firstupdate
Which one is implemented in the new client?

Both (a) and (b) have worked flawlessly in the old client, where (a) has a few disadvantages (may take longer than 12 blocks to be integrated in the blockchain due to some Repeat Broadcast feature every 30 minutes, I think.)

you can still do all that from console window still .. but now the GUi (will eventually) do this automatically (so b but automatic)


Quote
There is something that makes me feel a bit more uneasy, though: how does the new client handle uppercase names?
According to explorer.dot-bit.org, someone took over my d/cara name after some 30000 blocks. My local namecoind client still says I own this name. I had asked phelix if his client shows anything different. He found out, that there are d/cara and d/Cara, which are two completely different things. It's just explorer.dot-bit.org that doesn't discriminate. What about the new client?


it (the GUI in Manage Names Tab) will let you register both upper and lower

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

also it might show you still have the name, but it's expired?
member
Activity: 112
Merit: 10
if the auto firstupdate doesn't work, you can get the Hex numbers from debug.log. Search for "Automatic name_firstupdate".
the transaction for firstupdate is created and signed immediately (when entered pw), but not broadcasted, still debugging why it crashed.

As firstupdating a name can be done in two different ways:
a) name_new, and instantly issue the name_firstupdate
b) name_new, then wait for 12 blocks before a name_firstupdate
Which one is implemented in the new client?

Both (a) and (b) have worked flawlessly in the old client, where (a) has a few disadvantages (may take longer than 12 blocks to be integrated in the blockchain due to some Repeat Broadcast feature every 30 minutes, I think.)



There is something that makes me feel a bit more uneasy, though: how does the new client handle uppercase names?
According to explorer.dot-bit.org, someone took over my d/cara name after some 30000 blocks. My local namecoind client still says I own this name. I had asked phelix if his client shows anything different. He found out, that there are d/cara and d/Cara, which are two completely different things. It's just explorer.dot-bit.org that doesn't discriminate. What about the new client?
legendary
Activity: 1807
Merit: 1020
it's ok with fresh wallet it seems.. maybe it's something to do with your wallet.. looking again though

All addresses in this wallet are without privkey (from importaddress), so maybe that's one problem.

On the other hand, even using only imported addresses without priv keys this works perfectly if I send from one address to two others (i.e. no address reuse). I will try with a fresh wallet and importaddress, and if that still fails I'll try a fresh wallet and importprivkey.

Ok, so with a fresh wallet and importaddress it fails still, but with importprivkey it works fine.

looking at it now.. didn't test address without privkey.

PLEASE TEST
NAMESPACE REGISTRATION ADDED + Transactions will show name txs (new tab, Manage Names)

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

Binaries
(MAC NOT UPDATED YET (but should be able to compile from repo), will ask Maxpower when finalized).
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

will add name filter soon + some more tweaks

would be great if someone with quite a "few" names could test


bugs:
auto-firstupdating after 12 blocks causes crash.. working on it... possibly due encrypted wallet .. sorry.. should have checked... when you submit a new name it will automatically do this, so there is no way out.. maybe don't submit a new name till we sort (hopefully by tomorrow)

right clicking on a name-tx may show some funny values

will sort ASAP
res/icons/tx_nameop.png is missing from sources.

please try now..


you can try the submit button for a name_new (did not crash this time).. if the auto firstupdate doesn't work, you can get the Hex numbers from debug.log. Search for "Automatic name_firstupdate".
the transaction for firstupdate is created and signed immediately (when entered pw), but not broadcasted, still debugging why it crashed.

hero member
Activity: 540
Merit: 500
it's ok with fresh wallet it seems.. maybe it's something to do with your wallet.. looking again though

All addresses in this wallet are without privkey (from importaddress), so maybe that's one problem.

On the other hand, even using only imported addresses without priv keys this works perfectly if I send from one address to two others (i.e. no address reuse). I will try with a fresh wallet and importaddress, and if that still fails I'll try a fresh wallet and importprivkey.

Ok, so with a fresh wallet and importaddress it fails still, but with importprivkey it works fine.

looking at it now.. didn't test address without privkey.

PLEASE TEST
NAMESPACE REGISTRATION ADDED + Transactions will show name txs (new tab, Manage Names)

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

Binaries
(MAC NOT UPDATED YET (but should be able to compile from repo), will ask Maxpower when finalized).
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

will add name filter soon + some more tweaks

would be great if someone with quite a "few" names could test


bugs:
auto-firstupdating after 12 blocks causes crash.. working on it... possibly due encrypted wallet .. sorry.. should have checked... when you submit a new name it will automatically do this, so there is no way out.. maybe don't submit a new name till we sort (hopefully by tomorrow)

right clicking on a name-tx may show some funny values

will sort ASAP
res/icons/tx_nameop.png is missing from sources.
legendary
Activity: 1807
Merit: 1020
it's ok with fresh wallet it seems.. maybe it's something to do with your wallet.. looking again though

All addresses in this wallet are without privkey (from importaddress), so maybe that's one problem.

On the other hand, even using only imported addresses without priv keys this works perfectly if I send from one address to two others (i.e. no address reuse). I will try with a fresh wallet and importaddress, and if that still fails I'll try a fresh wallet and importprivkey.

Ok, so with a fresh wallet and importaddress it fails still, but with importprivkey it works fine.

looking at it now.. didn't test address without privkey.

PLEASE TEST (WILL BE BUGS)
NAMESPACE REGISTRATION ADDED + Transactions will show name txs (new tab, Manage Names)

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

Binaries
(MAC NOT UPDATED YET (but should be able to compile from repo), will ask Maxpower when finalized).
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

will add name filter soon + some more tweaks

would be great if someone with quite a "few" names could test


bugs:
auto-firstupdating after 12 blocks causes crash.. working on it... possibly due encrypted wallet .. sorry.. should have checked... when you submit a new name it will automatically do this, so there is no way out.. don't submit a new name till we sort (hopefully by tomorrow), as you wil not be able to "easily" get the hex values

right clicking on a name-tx may show some funny values

will sort ASAP
legendary
Activity: 1540
Merit: 1002
it's ok with fresh wallet it seems.. maybe it's something to do with your wallet.. looking again though

All addresses in this wallet are without privkey (from importaddress), so maybe that's one problem.

On the other hand, even using only imported addresses without priv keys this works perfectly if I send from one address to two others (i.e. no address reuse). I will try with a fresh wallet and importaddress, and if that still fails I'll try a fresh wallet and importprivkey.

Ok, so with a fresh wallet and importaddress it fails still, but with importprivkey it works fine.
legendary
Activity: 1540
Merit: 1002
are you trying this on namecoin.exe or "namecoin.exe - testnet" ?

i got no idea of code but i can sure test gui's,
if someone can send me some nmc's testnet in my direction i can try reproduce the bug.

myTH1TgaSsJ2SsVpwTjXMaKKEzuoWahEB9

maybe create a thread where people can test this, receive nmc testnets and links to latest binaries and  qt download.

i assume nmc testnet will be forked soon? make sure to say if present .exe should be used in real or testnet.
nmc regular blockchain downloads fine in my ssd laptop, nmc testnet is super-slow.

I'm not sure if you mean the bug I'm reporting or just generic testing, but if the former you'll not be able to test using the GUI as there's no means to controlling the change address there.
member
Activity: 106
Merit: 10
are you trying this on namecoin.exe or "namecoin.exe - testnet" ?

i got no idea of code but i can sure test gui's,
if someone can send me some nmc's testnet in my direction i can try reproduce the bug.

myTH1TgaSsJ2SsVpwTjXMaKKEzuoWahEB9

maybe create a thread where people can test this, receive nmc testnets and links to latest binaries and  qt download.

i assume nmc testnet will be forked soon? make sure to say if present .exe should be used in real or testnet.
nmc regular blockchain downloads fine in my ssd laptop, nmc testnet is super-slow.
legendary
Activity: 1540
Merit: 1002
it's ok with fresh wallet it seems.. maybe it's something to do with your wallet.. looking again though

All addresses in this wallet are without privkey (from importaddress), so maybe that's one problem.

On the other hand, even using only imported addresses without priv keys this works perfectly if I send from one address to two others (i.e. no address reuse). I will try with a fresh wallet and importaddress, and if that still fails I'll try a fresh wallet and importprivkey.
legendary
Activity: 1807
Merit: 1020
Important Update:

Fixed name_firstupdate crash in GUI console, and another important bug with encrypted wallet. Upgrade highly recommended. Version 3.57

https://github.com/namecoin-qt/namecoin-qt
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt
(mac bin not updated atm)


Is there a windows makefile? I can't seem to find it.


Yes, makefile for namecoin-qt is in "project"
Makefile for namecoind is in "src".
requires MinGW.
thanks.



To speed up downloading of the blockchain we might consider this patch:
https://github.com/bitcoin/bitcoin/pull/964/files   dbcache option    Maybe even change default to 100MB

Tried it on a machine with a relatively fast hard disk drive (but not my regular machine with ssd). Downloading the blockchain is thrashing the disk so hard I can barely stand it. Really think this option is necessary for the next release or only people with ssd can use it.



added this


Bounty #2:

Based on snailbrain's latest namecoin-qt I have the following problem:
- manually create and submit a tx to send full balance of addr1
  -> part to addr2
  -> part back to addr1 (think change back to sending address)
- The transaction is sent correctly but the wallet is updated only for the debit of addr1 and credit of addr2. For some reason the credit of addr1 is ignored, even when the the tx is included in a block
- restarting namecoind with -rescan gets that balance back

I need the above to work as in bitcoin, i.e. when sending to the address the output belongs to, both debit and credit to that address get processed by the wallet.

I have 1 BTC up for grabs for that fix, and I'll also try to fix it myself time permitting.

Yesterday I asked for pointers on #bitcoin-dev and instead of tech advice I got a "you shouldn't do that"... oh well.

maybe try the update..

testing "seemed" to show the correct amounts?

I have just tried again updated to commit 8166101ae213932a3f1aa095514eb682b3afb10e, and the behaviour still exists.

Code:
$ namecoind getrawtransaction 9846d830e40493c0c72147e959a66d2769589d69dd3d05946868f1a48649fd9e 1
{
    "hex" : "0100000001806b08da2f9175701c49a17492756030d1dc23d12f6c55f3a1c4dd53965fc6d1010000008c493046022100dc04b4e883bb15e46743c1298998223174fa73a175a1b4b461a366767282acf2022100ae2a7be906546f11a27f4d111e63aa585d0d7298a38c4de8ee07360aec13589d0141043cadb089ec6f22fafe75e859b593dc6ef9d896a2960254f847c1ab9009b9e9880e4ef55db17d7f17bdaeb523c7290e34f4c5e8779147b5d236562f794ab0426dffffffff0200943577000000001976a9146f577163208cbc1b624d248bc768bcdb49e0dce688ac00ca9a3b000000001976a914bc744a8542b08214d604efefafc5cf743e369c8c88ac00000000",
    "txid" : "9846d830e40493c0c72147e959a66d2769589d69dd3d05946868f1a48649fd9e",
    "version" : 1,
    "locktime" : 0,
    "vin" : [
        {
            "txid" : "d1c65f9653ddc4a1f3556c2fd123dcd13060759274a1491c7075912fda086b80",
            "vout" : 1,
            "scriptSig" : {
                "asm" : "3046022100dc04b4e883bb15e46743c1298998223174fa73a175a1b4b461a366767282acf2022100ae2a7be906546f11a27f4d111e63aa585d0d7298a38c4de8ee07360aec13589d01 043cadb089ec6f22fafe75e859b593dc6ef9d896a2960254f847c1ab9009b9e9880e4ef55db17d7f17bdaeb523c7290e34f4c5e8779147b5d236562f794ab0426d",
                "hex" : "493046022100dc04b4e883bb15e46743c1298998223174fa73a175a1b4b461a366767282acf2022100ae2a7be906546f11a27f4d111e63aa585d0d7298a38c4de8ee07360aec13589d0141043cadb089ec6f22fafe75e859b593dc6ef9d896a2960254f847c1ab9009b9e9880e4ef55db17d7f17bdaeb523c7290e34f4c5e8779147b5d236562f794ab0426d"
            },
            "sequence" : 4294967295
        }
    ],
    "vout" : [
        {
            "value" : 20.00000000,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 6f577163208cbc1b624d248bc768bcdb49e0dce6 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a9146f577163208cbc1b624d248bc768bcdb49e0dce688ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "N6j5xaeunEBQmDtZ5XzXH8TyWaqMWKdmFz"
                ]
            }
        },
        {
            "value" : 10.00000000,
            "n" : 1,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 bc744a8542b08214d604efefafc5cf743e369c8c OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a914bc744a8542b08214d604efefafc5cf743e369c8c88ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "NDkpYkwmfPeS5hTqiSm2E4YQp1XrEu8j4y"
                ]
            }
        }
    ],
    "blockhash" : "4545e816172b83a89fffc93c691f1ec4c48a0b4f1549b2e05b2a2149dbc33ce5",
    "confirmations" : 1,
    "time" : 1371119317,
    "blocktime" : 1371119317
}
Code:
$ namecoind listunspent 0 9999999 '["N6j5xaeunEBQmDtZ5XzXH8TyWaqMWKdmFz"]'
[
    {
        "txid" : "9846d830e40493c0c72147e959a66d2769589d69dd3d05946868f1a48649fd9e",
        "vout" : 0,
        "scriptPubKey" : "76a9146f577163208cbc1b624d248bc768bcdb49e0dce688ac",
        "amount" : 20.00000000,
        "confirmations" : 1
    }
]

$ namecoind listunspent 0 9999999 '["NDkpYkwmfPeS5hTqiSm2E4YQp1XrEu8j4y"]'
[
]
Code:
$ namecoind listaddressgroupings
[
    [
        [
            "N6j5xaeunEBQmDtZ5XzXH8TyWaqMWKdmFz",
            20.00000000,
            "\"\""
        ],
        [
            "NAoLHrukBrGH8NbSMyL9sw4kBAyDN2s31L",
            0.00000000,
            ""
        ],
    ]
]


it's ok with fresh wallet it seems.. maybe it's something to do with your wallet.. looking again though
legendary
Activity: 1540
Merit: 1002
Bounty #2:

Based on snailbrain's latest namecoin-qt I have the following problem:
- manually create and submit a tx to send full balance of addr1
  -> part to addr2
  -> part back to addr1 (think change back to sending address)
- The transaction is sent correctly but the wallet is updated only for the debit of addr1 and credit of addr2. For some reason the credit of addr1 is ignored, even when the the tx is included in a block
- restarting namecoind with -rescan gets that balance back

I need the above to work as in bitcoin, i.e. when sending to the address the output belongs to, both debit and credit to that address get processed by the wallet.

I have 1 BTC up for grabs for that fix, and I'll also try to fix it myself time permitting.

Yesterday I asked for pointers on #bitcoin-dev and instead of tech advice I got a "you shouldn't do that"... oh well.

maybe try the update..

testing "seemed" to show the correct amounts?

I have just tried again updated to commit 8166101ae213932a3f1aa095514eb682b3afb10e, and the behaviour still exists.

Code:
$ namecoind getrawtransaction 9846d830e40493c0c72147e959a66d2769589d69dd3d05946868f1a48649fd9e 1
{
    "hex" : "0100000001806b08da2f9175701c49a17492756030d1dc23d12f6c55f3a1c4dd53965fc6d1010000008c493046022100dc04b4e883bb15e46743c1298998223174fa73a175a1b4b461a366767282acf2022100ae2a7be906546f11a27f4d111e63aa585d0d7298a38c4de8ee07360aec13589d0141043cadb089ec6f22fafe75e859b593dc6ef9d896a2960254f847c1ab9009b9e9880e4ef55db17d7f17bdaeb523c7290e34f4c5e8779147b5d236562f794ab0426dffffffff0200943577000000001976a9146f577163208cbc1b624d248bc768bcdb49e0dce688ac00ca9a3b000000001976a914bc744a8542b08214d604efefafc5cf743e369c8c88ac00000000",
    "txid" : "9846d830e40493c0c72147e959a66d2769589d69dd3d05946868f1a48649fd9e",
    "version" : 1,
    "locktime" : 0,
    "vin" : [
        {
            "txid" : "d1c65f9653ddc4a1f3556c2fd123dcd13060759274a1491c7075912fda086b80",
            "vout" : 1,
            "scriptSig" : {
                "asm" : "3046022100dc04b4e883bb15e46743c1298998223174fa73a175a1b4b461a366767282acf2022100ae2a7be906546f11a27f4d111e63aa585d0d7298a38c4de8ee07360aec13589d01 043cadb089ec6f22fafe75e859b593dc6ef9d896a2960254f847c1ab9009b9e9880e4ef55db17d7f17bdaeb523c7290e34f4c5e8779147b5d236562f794ab0426d",
                "hex" : "493046022100dc04b4e883bb15e46743c1298998223174fa73a175a1b4b461a366767282acf2022100ae2a7be906546f11a27f4d111e63aa585d0d7298a38c4de8ee07360aec13589d0141043cadb089ec6f22fafe75e859b593dc6ef9d896a2960254f847c1ab9009b9e9880e4ef55db17d7f17bdaeb523c7290e34f4c5e8779147b5d236562f794ab0426d"
            },
            "sequence" : 4294967295
        }
    ],
    "vout" : [
        {
            "value" : 20.00000000,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 6f577163208cbc1b624d248bc768bcdb49e0dce6 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a9146f577163208cbc1b624d248bc768bcdb49e0dce688ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "N6j5xaeunEBQmDtZ5XzXH8TyWaqMWKdmFz"
                ]
            }
        },
        {
            "value" : 10.00000000,
            "n" : 1,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 bc744a8542b08214d604efefafc5cf743e369c8c OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a914bc744a8542b08214d604efefafc5cf743e369c8c88ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "NDkpYkwmfPeS5hTqiSm2E4YQp1XrEu8j4y"
                ]
            }
        }
    ],
    "blockhash" : "4545e816172b83a89fffc93c691f1ec4c48a0b4f1549b2e05b2a2149dbc33ce5",
    "confirmations" : 1,
    "time" : 1371119317,
    "blocktime" : 1371119317
}
Code:
$ namecoind listunspent 0 9999999 '["N6j5xaeunEBQmDtZ5XzXH8TyWaqMWKdmFz"]'
[
    {
        "txid" : "9846d830e40493c0c72147e959a66d2769589d69dd3d05946868f1a48649fd9e",
        "vout" : 0,
        "scriptPubKey" : "76a9146f577163208cbc1b624d248bc768bcdb49e0dce688ac",
        "amount" : 20.00000000,
        "confirmations" : 1
    }
]

$ namecoind listunspent 0 9999999 '["NDkpYkwmfPeS5hTqiSm2E4YQp1XrEu8j4y"]'
[
]
Code:
$ namecoind listaddressgroupings
[
    [
        [
            "N6j5xaeunEBQmDtZ5XzXH8TyWaqMWKdmFz",
            20.00000000,
            "\"\""
        ],
        [
            "NAoLHrukBrGH8NbSMyL9sw4kBAyDN2s31L",
            0.00000000,
            ""
        ],
    ]
]

Pages:
Jump to: