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

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Quote from: nelisky on June 10, 2013, 05:32:16 AM

Quote from: snailbrain on June 09, 2013, 06:49:17 PM

<3 MzkyUxTvvQzzBaBwxGeGSosSmUF1Ctk34i
much appreciated

Bounty paid, tx c9dd9f1074b40c049ebc53c804377e1200201792dd6473a002a0059712eff98d

nelisky : so I just wanted to check that you're satisfied that your requirements have been fulfilled and tested for the namecoin-qt client, extra functions, open source, no hidden code, etc? If so I've agreed to put 500 nmc for namecoin-qt client code to get in to this state which I will happily pay.

Also I have another 250nmc for this namecoin-qt to get merged back into official namecoin/namecoin github repository and another 250 nmc for it to rebased on top of the v0.8.2 bitcoin-namecoin compatability (i.e. leveldb, etc) mods that khal is currently working on.

Thanks for all your work so far snailbrain, this is excellent

nelisky

legendary

Activity: 1540

Merit: 1002

Quote from: snailbrain on June 09, 2013, 06:49:17 PM

<3 MzkyUxTvvQzzBaBwxGeGSosSmUF1Ctk34i
much appreciated

Bounty paid, tx c9dd9f1074b40c049ebc53c804377e1200201792dd6473a002a0059712eff98d

snailbrain

legendary

Activity: 1807

Merit: 1020

Quote from: nelisky on June 09, 2013, 03:09:40 PM

Been testing snailbrain version with all the RPC commands added. So far everything is working pretty well, there's just one small issue which I'm not sure relates to snailbrain's updates or not, but is kind of problematic for me.

Regardless, I'm calling the 1000 NMC bounty I offered as fulfilled. Can you provide an address for sending it, snailbrain?

Now, the problem I'm having is (using addresses imported without private key, not sure if that's relevant) when sending a transaction that has the same address in inputs and outputs, for example returning change to the sending address. When I do that the sending address is empty as far as the daemon is concerned even though the transaction is properly formed. The only way to see the unspent output again is by rescanning.

Addr1 10 NMC
-> Addr2 9 NMC
-> Addr1 1 NMC

Addr2 has 9 NMC, Addr1 is empty until I restart with -rescan

Addr1 10 NMC
-> Addr2 9 NMC
-> Addr3 1 NMC

Addr1 is empty, Addr2 has 9 NMC, Addr3 has 1 NMC as expected.

looking into this.. doesn't seem related to changes we have done.. but still checking..

edit: removed some stuff for now

<3 MzkyUxTvvQzzBaBwxGeGSosSmUF1Ctk34i
much appreciated

Hopefully Khal can add to proper repo to get the rest of bounty to fulfil moa's bounty too xXx (or can wait for next update)
The dev has been working extremely hard

Quote from: bitpop on June 09, 2013, 06:34:31 PM

Snailbrain could you help out bytecoin? We have a bounty.

the coder is very busy atm .. concentrating on NMC above all.. but you can send a link in PM

bitpop

legendary

Activity: 2912

Merit: 1060

Snailbrain could you help out bytecoin? We have a bounty.

nelisky

legendary

Activity: 1540

Merit: 1002

Been testing snailbrain version with all the RPC commands added. So far everything is working pretty well, there's just one small issue which I'm not sure relates to snailbrain's updates or not, but is kind of problematic for me.

Regardless, I'm calling the 1000 NMC bounty I offered as fulfilled. Can you provide an address for sending it, snailbrain?

Now, the problem I'm having is (using addresses imported without private key, not sure if that's relevant) when sending a transaction that has the same address in inputs and outputs, for example returning change to the sending address. When I do that the sending address is empty as far as the daemon is concerned even though the transaction is properly formed. The only way to see the unspent output again is by rescanning.

Addr1 10 NMC
-> Addr2 9 NMC
-> Addr1 1 NMC

Addr2 has 9 NMC, Addr1 is empty until I restart with -rescan

Addr1 10 NMC
-> Addr2 9 NMC
-> Addr3 1 NMC

Addr1 is empty, Addr2 has 9 NMC, Addr3 has 1 NMC as expected.

maxpower

sr. member

Activity: 456

Merit: 250

Quote from: cassini on June 08, 2013, 04:30:52 PM

Quote from: snailbrain on June 08, 2013, 01:13:28 PM

Mac binaries (may not work on OS X versions prior to Lion) - thanks to MaxPower for fixes
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

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

Indeed, on a SnowLeopard the N logo shows up for half a second, and then it "quits unexpectedly" with an
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000028

That's just a compilation problem, I think. Apparently there must be a makefile for the Mac somewhere?
(I know, SnowLeopard is not relevant anymore. It's just I can't get hold of a Lion/MLion machine at the moment Cry

)

Yeah, unfortunately a lot changed in Lion with the introduction of the LLVM compiler and its libraries, and now it's hard to compile anything on Mountain Lion to be backward-compatible. Getting wallets compiling on a VM running Snow Leopard is definitely on my to-do list.

cassini

member

Activity: 112

Merit: 10

Quote from: snailbrain on June 08, 2013, 01:13:28 PM

Mac binaries (may not work on OS X versions prior to Lion) - thanks to MaxPower for fixes
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

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

Indeed, on a SnowLeopard the N logo shows up for half a second, and then it "quits unexpectedly" with an
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000028

That's just a compilation problem, I think. Apparently there must be a makefile for the Mac somewhere?
(I know, SnowLeopard is not relevant anymore. It's just I can't get hold of a Lion/MLion machine at the moment Cry

)

snailbrain

legendary

Activity: 1807

Merit: 1020

Mac binaries (may not work on OS X versions prior to Lion) - thanks to MaxPower for fixes
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

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

jonytk

member

Activity: 106

Merit: 10

Quote from: infested999 on June 07, 2013, 03:32:57 PM

Quote from: virtualmaster on June 07, 2013, 02:38:28 PM

Quote from: infested999 on June 07, 2013, 01:46:57 PM

So what exactly determines the cost of a .bit domain? Is it hardcoded into the miners software?

Most sites will say it costs 15 NMC per year, is this a coincidence that converted to USD it costs the same as a .com domain?

With 15 NMC you can register over tausend .bit domains for a year if you make yourself from your wallet.
You can make it from your Namecoin client and there is a description how to make. But if you prefer the easiest way then you pay 0.1 BTC for a service and they do it for you.
So if you make yourself it will be 1000 times cheaper then a .com domain and will not take more time.

Over 1000, as in you just started speaking German halfway through the sentance? I found this graph http://dot-bit.org/HowToRegisterAndConfigureBitDomains and the chart says the it will in total cost 0.015 NMC. So where are there services that charge 15 NMC for a .bit domain, if all they are doing is hosting a node, keeping the blockchain, and making it easier for you to register a domain?

i think you mean "why" there are services, that charge more...

well, they are services... you pay for the easy of use,

hopefully this will be fixed soon, the wallet upgraded and nmc will become more popular.

keep in mind nmc is more complex than btc!

btw, i just opened nmc testnet and its stuck on block 23152 (3days ago) and not downloading, even thought it's conected to 5 nodes.

infested999

hero member

Activity: 854

Merit: 500

Quote from: virtualmaster on June 07, 2013, 02:38:28 PM

Quote from: infested999 on June 07, 2013, 01:46:57 PM

So what exactly determines the cost of a .bit domain? Is it hardcoded into the miners software?

Most sites will say it costs 15 NMC per year, is this a coincidence that converted to USD it costs the same as a .com domain?

With 15 NMC you can register over tausend .bit domains for a year if you make yourself from your wallet.
You can make it from your Namecoin client and there is a description how to make. But if you prefer the easiest way then you pay 0.1 BTC for a service and they do it for you.
So if you make yourself it will be 1000 times cheaper then a .com domain and will not take more time.

Over 1000, as in you just started speaking German halfway through the sentance? I found this graph http://dot-bit.org/HowToRegisterAndConfigureBitDomains and the chart says the it will in total cost 0.015 NMC. So where are there services that charge 15 NMC for a .bit domain, if all they are doing is hosting a node, keeping the blockchain, and making it easier for you to register a domain?

virtualmaster

hero member

Activity: 504

Merit: 500

Quote from: infested999 on June 07, 2013, 01:46:57 PM

So what exactly determines the cost of a .bit domain? Is it hardcoded into the miners software?

Most sites will say it costs 15 NMC per year, is this a coincidence that converted to USD it costs the same as a .com domain?

With 15 NMC you can register over tausend .bit domains for a year if you make yourself from your wallet.
You can make it from your Namecoin client and there is a description how to make. But if you prefer the easiest way then you pay 0.1 BTC for a service and they do it for you.
So if you make yourself it will be 1000 times cheaper then a .com domain and will not take more time.

nelisky

legendary

Activity: 1540

Merit: 1002

What about normal transfer fees (not name related), what's the schedule there? I'm feeling too lazy to go through the code, unforgivable I know, but it is Friday...

infested999

hero member

Activity: 854

Merit: 500

So what exactly determines the cost of a .bit domain? Is it hardcoded into the miners software?

Most sites will say it costs 15 NMC per year, is this a coincidence that converted to USD it costs the same as a .com domain?

khal

hero member

Activity: 540

Merit: 500

Quote from: midnightlightning on June 06, 2013, 09:33:34 PM

Thanks! That seems to have fixed it, but for right now the three hard-coded IP seed nodes for Namecoin are all refusing connections, so my client isn't finding any peers to connect to. Was there a new version adopted that change the ports or magic bits of network communications?

Check commits from days 24/05 (mainnet) & 25/05 (testnet) to find the right magic numbers : https://github.com/khalahan/namecoin/commits/namecoin_v0.8.2rc2 (but they have not changed).
If you reject merged mined blocks, this is another reason why your peer disconnects itself from remote nodes.

midnightlightning

member

Activity: 68

Merit: 10

Quote from: khal on June 04, 2013, 05:48:47 PM

Quote from: midnightlightning on June 04, 2013, 04:22:14 PM

That's 74 seconds after the timestamp of 24191. My retargeting math has worked for all the previous retargets, so why did this one go wonky? Was there some different logic in place for this block round that allowed a slightly different difficulty retarget? Is this a rounding error (after multiplying the old target by the actual time spent, do I need to truncate it before dividing it out)?

Block 22175 is 74s before block 22176 (time of block 22175 = 1318761208).

It is related to a bug known as "retarget hole"/timetravel due to merged mining :
https://github.com/namecoin/namecoin/commit/436f571d41cc53844d482eeef0069a3ca94e08f8
https://bitcointalksearch.org/topic/namecoin-attack-threat-please-withdraw-your-namecoins-asap-43719
https://bitcointalksearch.org/topic/delete-43465 (first post erased...)

So, after block 19200, go back 2016 instead of 2015.

Thanks! That seems to have fixed it, but for right now the three hard-coded IP seed nodes for Namecoin are all refusing connections, so my client isn't finding any peers to connect to. Was there a new version adopted that change the ports or magic bits of network communications?

snailbrain

legendary

Activity: 1807

Merit: 1020

Quote from: nelisky on June 05, 2013, 03:10:15 AM

Quote from: marcus_of_augustus on June 04, 2013, 05:02:49 PM

Nelisky : what's the logic behind your patch that has the priv key prefix "2xxx" ? Is it done this way anywhere else? Why not use the "5xxx" prefix for interchangeability with bitcoin priv keys?

Thanks if you can shed some light.

I'm a little ashamed to say I think I jumped the gun with this change... I thought I was changing the address version and I now, on closer inspection, see I changed the private key prefix... oops.

There is no reason not to use bitcoin's version (128) instead for the private key, but I had some problem that prompt me to fix is like this, and now I can't remember what that was.

Feel free to revert that but do try to do a newaddress -> dumpprivkey | new wallet | -> importprivkey to make sure it is working as expected.

reverted patch and seems to test working:

now start with 5xx

nelisky

legendary

Activity: 1540

Merit: 1002

Quote from: marcus_of_augustus on June 04, 2013, 05:02:49 PM

Nelisky : what's the logic behind your patch that has the priv key prefix "2xxx" ? Is it done this way anywhere else? Why not use the "5xxx" prefix for interchangeability with bitcoin priv keys?

Thanks if you can shed some light.

I'm a little ashamed to say I think I jumped the gun with this change... I thought I was changing the address version and I now, on closer inspection, see I changed the private key prefix... oops.

There is no reason not to use bitcoin's version (128) instead for the private key, but I had some problem that prompt me to fix is like this, and now I can't remember what that was.

Feel free to revert that but do try to do a newaddress -> dumpprivkey | new wallet | -> importprivkey to make sure it is working as expected.

virtualmaster

hero member

Activity: 504

Merit: 500

When will come out the .new domains for Namecoin ?

khal

hero member

Activity: 540

Merit: 500

Quote from: midnightlightning on June 04, 2013, 04:22:14 PM

That's 74 seconds after the timestamp of 24191. My retargeting math has worked for all the previous retargets, so why did this one go wonky? Was there some different logic in place for this block round that allowed a slightly different difficulty retarget? Is this a rounding error (after multiplying the old target by the actual time spent, do I need to truncate it before dividing it out)?

Block 22175 is 74s before block 22176 (time of block 22175 = 1318761208).

This code may be responsible of that :

Code:

main.cpp: GetNextWorkRequired line 671
   // Go back the full period unless it's the first retarget after genesis. Code courtesy of ArtForz

   int nBlocksBack = nInterval-1;
   if(pindexLast->nHeight >= hooks->GetFullRetargetStartBlock() && ((pindexLast->nHeight+1) > nInterval))
   nBlocksBack = nInterval;

It is related to a bug known as "retarget hole"/timetravel due to merged mining :
https://github.com/namecoin/namecoin/commit/436f571d41cc53844d482eeef0069a3ca94e08f8
https://bitcointalksearch.org/topic/namecoin-attack-threat-please-withdraw-your-namecoins-asap-43719
https://bitcointalksearch.org/topic/delete-43465 (first post erased...)

So, after block 19200, go back 2016 instead of 2015.

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Nelisky : what's the logic behind your patch that has the priv key prefix "2xxx" ? Is it done this way anywhere else? Why not use the "5xxx" prefix for interchangeability with bitcoin priv keys?

Thanks if you can shed some light.

Quote from: snailbrain on June 04, 2013, 03:33:41 AM

i tested it.. working fine it seems (dumpprivkey and importprivkey)

we used Nelisky's patch.. (which gives 2xxx)

https://github.com/namecoin-qt/namecoin-qt/commit/95ca4f8dc800a203f65613afe5c9c79894d6c6a7
Before that it was 5xxx.

let me know thoughts

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