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

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

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.

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?

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.

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

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?

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.

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?

reverted patch and seems to test working:

now start with 5xx

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.

When will come out the .new domains for Namecoin ?

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

This code may be responsible of that :

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.

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.

Okay, here's a technical question; I've got an issue trying to get my namecoin port to validate the block at height 24192. That's a point where the difficulty target changes (24192 % 2016 = 0), and it looks to me like the difficulty moved incorrectly, and yet it's in the blockchain as valid.

The logic (as I understand it) for the difficulty changes are: [old target] * [actual time] / [expected time] = [new target].

Here's the old target (what block 24191 has) and the new target (what block 24192 has):

But here's what my math arrives at:
The timestamp on block 24191 is 1319487998. Block 22176 (2016 blocks before 24192, the first one with the difficulty bits of 0x1a6b32b1) has a timestamp of 1318761282. The difference of those two (actual time spent) is 726716, which makes [actual]/[expected] = 0.600790343915344. Hence I get a new target of:


Close, but not quite. Taking the new difficulty that apparently is valid, I get a ratio of 0.6008515185394, arriving at an actual timestamp of 1319488072. 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)?

Thanks, I need to fork bytecoin and I have a bounty up.

not me

but a "few" people do.. doublec? (think that's how you spell his name)

yeh it seems so

will leave like this for now.. and see what as many peoples thoughts are (Nelisky?)

Somewhat related, does anyone know how to patch bytecoin to merged mine just like namecoin did?

It's a sticky one 

Pros and cons either way I think. Clearly there is increased chance for confusion using same prefix as bitcoin priv key, but if we use the same then there is no need for an intermediate tool to convert formats when moving shared bit/namecoin priv keys between wallets.

Looks like the prefix 2 is already reserved for testnet script hash so there is potential for confusion/conflict there. https://en.bitcoin.it/wiki/List_of_address_prefixes

Lowercase n is already taken also ... pick a base58 character and go with it?

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