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

[daemondazz]

I've just read through most of the thread after setting up merged mining in my p2pool node. Regarding the hash rate increase and difficulty jump, how long is it expected to be between blocks at the moment with slightly under 2GH/s ?

[1714217539]

1714217539

[1714217539]

1714217539

[marcus_of_augustus]

sorry github will have to wait (I'm not the coder, it will be put on github when complete, he is a busy man)

Latest Namecoin-qt + Win Binaries
(should compile in linux/osx)

should be working bar Encrypt Wallet (fix soon)

Still Use with Caution

Namecoin-qt
http://www.mediafire.com/folder/b8qo76o7d8w6vda,l1lohaglao45023/shared

Just a note here for linux builds, if you are not using Cygwin you will have to comment out the following like so in the file namecoin-qt.pro

Code:

# Regenerate src/build.h
#!win32|contains(USE_BUILD_INFO, 1) {
#    genbuild.depends = FORCE
#    genbuild.commands = cd $$PWD; /bin/sh share/genbuild.sh $$OUT_PWD/build/build.h
#    genbuild.target = $$OUT_PWD/build/build.h
#    PRE_TARGETDEPS += $$OUT_PWD/build/build.h
#    QMAKE_EXTRA_TARGETS += genbuild
#    DEFINES += HAVE_BUILD_INFO
#}

then you can just do

Code:

qmake "UPNP=-"

and

Code:

make

and binary is namecoin-qt ... remember to install all the dependencies first. Good luck ... it appears to be genuine.

[snailbrain]

I've just read through most of the thread after setting up merged mining in my p2pool node. Regarding the hash rate increase and difficulty jump, how long is it expected to be between blocks at the moment with slightly under 2GH/s ?

http://dot-bit.org/tools/namecoinCalculator.php?difficulty=2470852.6797697&hashrate=2000000

?

[daemondazz]

Ouch

Thanks for the link

[snailbrain]

I didn't think the merged mining issue through, you are correct. I was going for "no need to allow mining" but obviously full merged POW is needed to verify blocks, so that's moot.

So the only viable option is improve on the current 0.3.50 codebase, I guess. I would still think it possible to hook into the latest bitcoind to support NMC, but that's likely much less trivial than I assumed from the start.

How's this for a plan? I need the following RPC calls added:
- importprivkey
- dumpprivkey
- importaddress (from codeshark's PR, I can dig the number if needed)
- listunspent
- createrawtransaction
- decoderawtransaction
- getrawtransaction
- sendrawtransaction
- signrawtransaction
- signmessage
- verifymessage
- listaddressgroupings (I can live without this one, but it is useful)

I also need all the tx to be available for querying, not just those for wallet addresses (I think that's already the way it is).

still good to your word if we get these rpc commands added?

[nelisky]

still good to your word if we get these rpc commands added?

Most certainly! I'll, of course, need proper source code so I can diff and compile myself, but if you can put this together (at least) my part of the bounty is yours.

[snailbrain]

still good to your word if we get these rpc commands added?

Most certainly! I'll, of course, need proper source code so I can diff and compile myself, but if you can put this together (at least) my part of the bounty is yours.

it's being worked on (will keep you updated)

[midnightlightning]

I got a nodejs implementation able to connect and download the namecoin blockchain up until the merged mining fork at block 19200. Looks like I'll have to delve into the Aux-POW logic to make any more progress.

After diving through source code for quite a while, I think I've finally wrapped my head around the merged mining/Auxiliary Proof-of-Work methodology. As such, I've updated the Merged Mining specification on the Bitcoin wiki to give quite a bit more technical information, and some examples. Some of the existing content was corrected (calling the last attribute of the merkle branch object an "index" was throwing me for a while; it's really a bitmask field, to be interpreted bit by bit, not as an integer index value). Hopefully that helps others who are trying to get clients to validate the Namecoin AuxPOW blocks. And let me know (or just re-edit the wiki) if I've gotten anything wrong!

[marcus_of_augustus]

http://www.aaronsw.com/weblog/squarezooko

Just found this piece from Aaron Swartz, Jan 2011.

Sounds like he is describing namecoin ... I wonder, could he have?

Also read his comments in the FAQ .... https://squaretriangle.jottit.com/faq

[lunarboy]

http://www.aaronsw.com/weblog/squarezooko

Just found this piece from Aaron Swartz, Jan 2011.

Sounds like he is describing namecoin ... I wonder, could he have?

Also read his comments in the FAQ .... https://squaretriangle.jottit.com/faq

Nakanames .... you might be onto something 

[khal]

Hi everybody !

I'm glad to see some activity in the namecoin world :p

http://www.aaronsw.com/weblog/squarezooko

Just found this piece from Aaron Swartz, Jan 2011.

Sounds like he is describing namecoin ... I wonder, could he have?

Also read his comments in the FAQ .... https://squaretriangle.jottit.com/faq

Surprising :p

snailbrain & co : continue this good work, and don't forget to release the source code as soon as possible (otherwise there will be a loss of credibility, fear that you'll stole coins and less commits from other developpers).

On my side, I've started to try to use bitcoin 0.8.2 on the namecoin network. It is a very long work and if the namecoin GUI could bring more people to namecoin it is a good solution while all this is not fully ready (and it will take some time).

It seems some people try without success, and I may say that, indeed, there are some really small details that need to be adjusted in the code before it works on the namecoin network.

I'm also happy to see that midnightlightning has improved that wiki about merged mining, that will be less work for the one who will implement it :p

So, after some hours of work, here is what has been done :
- b94b68b Change ports for Namecoin 8336 : rpc calls 8334 : peer communication
- 3d39d31 Change defaultDataDir for Namecoin
- 137bcf4 Update Genesis infos for Namecoin main-network
- 3d172b8 pchMessageStart update for Namecoin
- a852cdd Update genesis infos & pchMessageStart for namecoin testnet
- 8c7622a Disable testnet ability to change difficulty before 2k blocks / Incompatible with the current namecoin testnet / Will be activated back when we will do a testnet reset

Here is what works :
- peer connections & first message exchange (sort of handshake with pchMessageStart)
- mainnet & testnet genesis blocks support
- block downloads (standard bitcoin blocks only)

Here is what doesn't work yet :
- "bitcoin" is written everywhere (a simple search and replace will not work)
- checkpoints are still bitcoin's one
- same for dnsSeed
- same for irc channel
- same for all different fees
- transaction with names (so blocks will be refused too)
- blocks with merged mining
- name_* rpc calls
- alert private keys
- I don't know if the GUI will use name tranctions as standard transactions or not (if the coin tied to the name is spent, you may loose the name)
- a current namecoin node should be upgradable to the 0.8.2 release (do you see reasons why it won't be possible ?)

One important thing to know before coding more is what is the best way of adding namecoin features in this bitcoin base code while allowing easy integration of future bitcoin releases into namecoin.

Satoshi... oops.. Vinced, has done it with hooks to minimize the number of changes in the bitcoin code.
The namecoin code itself is a list of functions with duplicated code and other good programming practices :p

So, next step may be to take some time to do things well for the future.

Last blocks validated by my 2 nodes :
- mainnet : 11110 (block rejected by checkpoint lock-in at 11111)
- testnet : 545   (block rejected by checkpoint lock-in at 546)
Next blocking points will be transaction with name registration :p

Code is available in my tree in the namecoin_v0.8.2rc2 branch :
https://github.com/khalahan/namecoin/tree/namecoin_v0.8.2rc2

Remember, it's not usable in production or with your main wallet.
So, do not use them with your current namecoin data dir (use: ./bitcoind -datadir=a_new_folder, and backup everything in case of mistake :p).

[jonytk]

I found people using bitcoin to timestamp...   
when namecoin becomes more user-friendly we should start a publicity campaign!   

http://news.techworld.com/security/3449015/could-the-bitcoin-network-be-used-as-an-ultrasecure-notary-service/

keep the good work going! 

[snailbrain]

Hi Khal,
excellent

namecoin-qt will be on github soon, properly (as good as we can, maybe a day or 2).

Encrypt Wallet is now working.. will only work in GUI, RPC command will be added very soon along with extra RPCs..
concentrating on doing github first to gain some credibility (as you say).

"don't store any significant amounts, for now"

link removed

[snailbrain]

http://p2pconnects.us/2013/05/10/namecoin-cryptographic-login-that-doesnt-suck/

not sure if anyone saw this

[khal]

namecoin-qt will be on github soon, properly (as good as we can, maybe a day or 2).

Encrypt Wallet is now working.. will only work in GUI, RPC command will be added very soon along with extra RPCs..
concentrating on doing github first to gain some credibility (as you say).

"don't store any significant amounts, for now"

http://www.mediafire.com/folder/6io0jlym38ef02k,xgep8ud48q2rj1c/shared

Good :p
I'm interested on the way you did that mix on namecoin 3.5 and boitcoin-qt 0.8

http://p2pconnects.us/2013/05/10/namecoin-cryptographic-login-that-doesnt-suck/

not sure if anyone saw this

Interesting extension of the ID namespace usage :p

I found people using bitcoin to timestamp...   
when namecoin becomes more user-friendly we should start a publicity campaign!   

http://news.techworld.com/security/3449015/could-the-bitcoin-network-be-used-as-an-ultrasecure-notary-service/

keep the good work going! 

I added both your use cases on the wiki : https://dot-bit.org/Use_cases

[khal]

I've updated checkpoints in the code to go further in block downloads.

Last blocks validated by my 2 nodes :
- mainnet : 11610 (block rejected with bad PoW)
- testnet : 1045  (block rejected with bad PoW)

One important thing to know before coding more is what is the best way of adding namecoin features in this bitcoin base code while allowing easy integration of future bitcoin releases into namecoin.
Satoshi... oops.. Vinced, has done it with hooks to minimize the number of changes in the bitcoin code.
The namecoin code itself is a list of functions with duplicated code and other good programming practices :p

Some coders here to give their opinion ? :p

Code is available in my tree in the namecoin_v0.8.2rc2 branch :
https://github.com/khalahan/namecoin/tree/namecoin_v0.8.2rc2

[virtualmaster]

Great news Khal.
You are the best Namecoiner.
 
I will test it may be next week, after I have a final version of my merged bitcoin/namecoin address generator.

[phelix]

khal, you are the man. Will you increase the fees and the space limit for the new version? Should we have a poll maybe?

Namecoin offensive 2013 gaining speed.

I was thinking about a windows installer for the Acrylic method (with remote DNS).

[snailbrain]

Namecoin-qt-3.50-alpha

Backup wallet first etc

https://github.com/namecoin-qt/namecoin-qt
http://www.mediafire.com/folder/3aa8ukj7v6m5d/Namecoin-qt

I will create a new thread for the GUI soon.


New rpc commands in progress
All name space commands usable from console only (for now)
wallet encryption will only work in GUI (don't use namecoind with encrypted wallet [for now], and don't forget to backup, once you encrypt you may not be able to go back to your old wallet without losing coins...).. maybe just don't use encrypt wallet for now.
if you use wallet encryption you may be unable to use the name_* commands (or any console tx for now, until rpc added [walletpassphrase])
name purchases just show as transactions (for now)

Please review/test and provide feedback.

[marcus_of_augustus]

khal ; ... good stuff with the v0.8.2 update work.

snailbrain ; checking over new code now, great to see you forking code off old namecoin and working through adding the new stuff, that should make it much easier for khal to pull back into mainline namecoin so both namecoin-qt and namecoind are in same repo like bitcoin-qt and bitcoind.