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

[grue]

I started mining with a new wallet, and got five orphans in a row. Are these transactions simply worthless?

yep

[marcus_of_augustus]

So what's the rules with upper and lower case on domain names in the database?

Code:

$ ./namecoind name_scan d/bitcoin 1
[
    {
        "name" : "d/bitcoin",
        "value" : "webpagedeveloper.me/namecoin",
        "txid" : "ab1207bd605af57ed0b5325ac94d19578cff3bce668ebe8dda2f42a00b001f5d",
        "expires_in" : 3918
    }
]

Code:

$ ./namecoind name_scan d/Bitcoin 1
[
    {
        "name" : "d/abermud",
        "value" : "3e28f697d16264d7ca61058872846f673285d469aec66f1f04f0d84d364bf931RESERVED",
        "txid" : "77dc51b31aea6c57d072299c8f236975a7cfad34fc782844a7e3d4f729ae2aa0",
        "expires_in" : 11090
    }
]

Seems like "bitcoin" and "Bitcoin are treated as two different names, is that correct?

It will be pointless if you are allowed every variant in the upper/lower case space of even a single word.

e.g.

bitcoin
Bitcoin
bItcoin
biTcoin
bitCoin
bitcOin
bitcoIn
bitcoiN

and then many other permutations ...

[foo]

DNS is case insensitive. You've just found a bug in namecoind.

[marcus_of_augustus]

DNS is case insensitive. You've just found a bug in namecoind.

What's that worth ... a few namecoins? Anything like finding a block?

[gsan]

DNS is case insensitive. You've just found a bug in namecoind.

Namecoind is application-neutral, i.e. it doesn't do the conversions on behalf of the applications (domains being just one of them). We need a GUI tool to do all this. However, there already are online tools that can do the conversion, collision checking and even registration for you.

As for the standard, this is from the extended specification draft:

Name field

Name is a lowercase string, which begins with d/, followed by the domain name. Namecoin enabled resolvers will append the default TLD (.bit) to the name specified here.

Example: d/example

The IDNA standard encoding is used for internationalized domain names. This means that Unicode names need to be converted to ASCII compatible encoding according to IDNA, before registration. This can be done using the idn command-line tool:

Code:

$ idn -p Nameprep ŝtelo
xn--telo-u5a

Also, only valid domain names are allowed, which means characters other than lowercase letters, numerics and dash are not allowed, as well as names longer than 63 letters and names starting with a dash.

(Note: However, since this is a measure against compatibility issues with DNS, names consisting of all numeric values and underscore can be discussed.)

Meaning, if the registered name contains Unicode characters, capital letters or symbols, it will be rejected by resolvers.

[dingus]

While mining with namecoind and poclbm, every once in a while all my miners just seem to stop connecting. What resolves this is killing namecoind.exe and restarting it again.

version "32150" on windows 7 64bit

[grue]

Latest Windows binaries last commit: May 26, 2011
http://dl.dropbox.com/u/30252547/namecoin_2011-05-26.zip
SHA-1: 3CA7B40DCE4C846FB45B1F998F66B13EBD8A4D6B

commits since last release:
2011-05-26   advance version
2011-05-26   Merge branches 'master' and 'hooks'
2011-05-26   merge hooks
2011-05-26   missed lockin constant

[lebish]

Latest Windows binaries last commit: May 26, 2011
http://dl.dropbox.com/u/30252547/namecoin_2011-05-26.zip
SHA-1: 3CA7B40DCE4C846FB45B1F998F66B13EBD8A4D6B

commits since last release:
2011-05-26   advance version
2011-05-26   Merge branches 'master' and 'hooks'
2011-05-26   merge hooks
2011-05-26   missed lockin constant

thanks!

[Alex Beckenham]

Does this interfere with a bitcoin installation in any way, or is it 100% separate?

[marcus_of_augustus]

Does this interfere with a bitcoin installation in any way, or is it 100% separate?

They should run separately since they are different ports. There have been reports of people sending bitcoins to namecoin addresses and vice versa and apparently the client did not protest .... so be careful. Extracting namecoins from bitcoin wallets and vice versa would not be for the faint of heart.

[doublec]

Extracting namecoins from bitcoin wallets and vice versa would not be for the faint of heart.

I've done this and recovered the coins. If you've sent namecoins to a bitcoin address you can fix it by having the owner of the bitcoin address doing this:

1. Stop bitcoind and namecoind
2. Backup the namecoin wallet.dat somewhere
3. Copy the bitcoin wallet.dat into the ~/.namecoin directory, overwiting the existing wallet.dat (make sure you did step 2)
4. start namecoind with: namecoind -rescan
5. Assuming you have the full namecoin blockchain you'll see the coins in the balance. You can then 'sendtoaddress' to a real namecoin address
6. stop namecoind
7. copy your namecoin wallet.dat backup back into ~/.namecoin
8. start namecoind with: namecoind -rescan

If you've sent bitcoin addresses to a namecoin address follow the same steps, swapping namecoin and bitcoin around. Note that it's the recipient of the original send, the owner of the address, that must do these steps. It's probably even better to do all this in a virtual machine with clean wallets so you don't accidentally overwrite your own wallet.

[Alex Beckenham]

Does this interfere with a bitcoin installation in any way, or is it 100% separate?

They should run separately since they are different ports. There have been reports of people sending bitcoins to namecoin addresses and vice versa and apparently the client did not protest .... so be careful. Extracting namecoins from bitcoin wallets and vice versa would not be for the faint of heart.

So they use different installation directories, different 'appdata' directories, different copies (if any) of libeay32.dll... i.e. Installation and use are 100% separate?

I wasn't sure how much this relied on a bitcoin installation, if at all... I suppose that you could use Namecoins even if you have never installed or used bitcoin?

I guess it's the phrase 'based on Bitcoin' that has me asking all this.

[marcus_of_augustus]

Does this interfere with a bitcoin installation in any way, or is it 100% separate?

They should run separately since they are different ports. There have been reports of people sending bitcoins to namecoin addresses and vice versa and apparently the client did not protest .... so be careful. Extracting namecoins from bitcoin wallets and vice versa would not be for the faint of heart.

So they use different installation directories, different 'appdata' directories, different copies (if any) of libeay32.dll... i.e. Installation and use are 100% separate?

I wasn't sure how much this relied on a bitcoin installation, if at all... I suppose that you could use Namecoins even if you have never installed or used bitcoin?

I guess it's the phrase 'based on Bitcoin' that has me asking all this.

You should be able to run namecoin on a machine that has never had bitcoin on it, yes. Doesn't rely on a bitcoin install at all. (Never done it on windows though).

"Based on" is a bad term, they mean to say it uses the same block chain technology, with an extension to include naming transactions, including but not limited to, domain naming.

[penta]

what happends when you firstupdate before 12blocks? i lost the 25btc but cant see it in my list, is it lost or will it update when the blocks are done?

[marcus_of_augustus]

what happends when you firstupdate before 12blocks? i lost the 25btc but cant see it in my list, is it lost or will it update when the blocks are done?

Best if you ask that question over here http://dot-bit.org/forum/index.php "Technical Support"

[Crs]

nmc@nmcpc:~/namecoin$ sudo make -f makefile.unix
[sudo] password for nmc:
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DUSE_UPNP=0 -o obj/nogui/util.o util.cpp
In file included from util.cpp:5:0:
headers.h:43:20: fatal error: db_cxx.h: No such file or directory
compilation terminated.
make: *** [obj/nogui/util.o] Error 1
nmc@nmcpc:~/namecoin$ sudo make -f makefile.unix USE_UPNP=
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -o obj/nogui/util.o util.cpp
In file included from util.cpp:5:0:
headers.h:43:20: fatal error: db_cxx.h: No such file or directory
compilation terminated.
make: *** [obj/nogui/util.o] Error 1
nmc@nmcpc:~/namecoin$

Anyone now what's wrong with this ?

[jackjack]

nmc@nmcpc:~/namecoin$ sudo make -f makefile.unix
[sudo] password for nmc:
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DUSE_UPNP=0 -o obj/nogui/util.o util.cpp
In file included from util.cpp:5:0:
headers.h:43:20: fatal error: db_cxx.h: No such file or directory
compilation terminated.
make: *** [obj/nogui/util.o] Error 1
nmc@nmcpc:~/namecoin$ sudo make -f makefile.unix USE_UPNP=
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -o obj/nogui/util.o util.cpp
In file included from util.cpp:5:0:
headers.h:43:20: fatal error: db_cxx.h: No such file or directory
compilation terminated.
make: *** [obj/nogui/util.o] Error 1
nmc@nmcpc:~/namecoin$

Anyone now what's wrong with this ?

Install libdb4.8++-dev and it should be ok

[datguywhowanders]

I wanted to try this out, but I could use a little help.

I downloaded the Mac Binary, but since it appears to be console only, how can I tell once namecoind has finished downloading the namecoin blockchain?

[jackjack]

I wanted to try this out, but I could use a little help.

I downloaded the Mac Binary, but since it appears to be console only, how can I tell once namecoind has finished downloading the namecoin blockchain?

Run a miner with your server, it will download the blockchain and then tell you when it's done

[datguywhowanders]

Yep, I tried running Diablo against it, and it keeps saying:


[6/9/11 6:25:03 PM] ERROR: Can't connect to Bitcoin: Bitcoin returned error message: Bitcoin is downloading blocks...


But, it is also providing me with a hashing rate, which doesn't seem to make much sense...