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

Hum, I tested sendtoalias (which is another command, only in my branch), so it may not have helped you...
But I confirm that sendtoname works for me too.

weird.. have had this problem for a long time.. just tried to recreate, to get the log
sendtoname d/khal 0.0001 .. always caused crash (Even a couple of days ago)... now it's working. nevermind

Ok, will try to test it a bit, but will try to compile it first :p

I tested it again on my computer (linux) and it was ok.
Command used: ./namecoind sendtoalias khal 0.0001
Result: 0.0001NMC sent to N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
Namecoin record: ./namecoind name_show id/khal
{
    "name" : "id/khal",
    "value" : "{ \"email\" : \"[email protected]\", \"bitcoin\" : \"1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T\", \"namecoin\" : \"N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9\" }",
}

An adjustment proposal for .bit registration/renewal to make more:
- justice by the registration - shorter name, more fee
- more traffic - it should increase the namecoin traffic and animate the consumption of namecoins
- limit mass holding of good names

Possible Solution:
1. Domain registration and renewal fee for .bit changes depending how long is the domain name. Namecoin destruction could also change or remain the same for everybody.
- names with up to 3 letters, 10 times higher fee, anyway they are not many of them
- names with 4 to 5 letters, 5 times higher fee
- names with 6 to 7 letters, double fee
- names with more than 7 letters remains with the same fee - so everybody can afford a .bit name
2. Domain registration and renewal fee for .bit remains the same for everybody but it should be introduced a namecoin binding which will be received back at the end of the registration/renewal period on a change address. That could be solved with the time shifted transaction in the future. Namecoin binding 1 year.
- names with up to 3 letters, 10 namecoin binding, anyway they are not many of them
- names with 4 to 5 letters, 5 namecoin binding
- names with 6 to 7 letters, 2 namecoin binding
- names with more than 7 letters, 1  namecoin binding

I believe so, but need people to test/feedback to fix any issues.. it compiles in mingw in windows

_______

if the qt is completed soon (with full nmc commands) + NMC goes on mtgox (as is the rumour for mid June?) .. this may wake up some NMC users .. maybe


I think changing the fees need to be thought about thoroughly (after the above?)...

Need to reduce spam, but also think about NMC's potential value in the future:

What makes a coin Valuable?

Hash Rate(security)? - NMC is second to bitcoin (due to merge mining)
Total Number of Coins? - < 21 million (less than BTC.. less due to lost coins.. not a lot though)
Is it going to die? - highly unlikely, unless btc does?
Age (stability)? The Oldest Altcoin and not just a copy.. actually does something unique... and has infinite possible uses.
Usage? - lots of things, but nothing which really increases it's value (unless .bit domains take off)..  would be good if some system was used in which users have to "top up" their NMC accounts with say 1 or 10 NMC, to be able to use some features (e.g. send a message), maybe it costs 0.0001... this would go to the miners... of course if we used the NMC block chain for messaging, it would increase the blockchain size.. another problem...

Personally i think NMC is massively under valued.. in a logical sense you would think nmc should be valued at 1:1 BTC (at a minimum) .. but you can't use it for anything which would "increase" it's value.... currently...
I remember when it was once at 0.1 nmc/btc..

Khal:
Do you know why sendtoname is causing the client to crash (even on original namecoind 3.50), windows only (well, me only).. same problem with QT and original namecoind 3.50.

We shouldn't make more changes than those already present in the 0.8 version, to facilitate the beta phase and limit the cause of potential bugs and to find them faster.

So, all this should go in the v3.50 and we will publish a new release.

Those changes require a hard fork, so we need to decide a block number after which they will take effect (how much time you think is needed to wake up all namecoin users ? :p).

Concerning the fees, what is the best model to choose for :
- default fees of the client for standard transactions
- required minimum fees for standard transactions
- default fees of the client for name transactions
- required minimum fees for name transactions

For infos :  https://dot-bit.org/forum/viewtopic.php?f=2&t=503


Should it work with mingw (cross-compiling for windows under linux) and linux ? (I didn't try and I don't have required lib/tools yet)



Edit: my opinion on fees : simplier = better => Force normal fees on all name_* tx (no free tx) + keep the 0.01 locked NMC on name_new.

=> 1NMC = near 1$. Parity soon :p (http://dot-bit.org/tools/domainCost.php?unit=USD&cost=1)

The 0.8 version "disconnect" from a node as soon as it receives an invalid block. As merged mined blocks are transmited with other blocks while you bootstrap the network, I didn't get all blocks I could've download.

After restarting namecoind several times, here are the last blocks accepted :
- mainnet : 19199 (19120 is a merged mined block with a non standard hash : d8a7c3e01e1e95bcee015e6fcc7583a2ca60b79e5a3aa0a171eddd344ada903d
- testnet : 4031 (4032 has not the required difficulty. Maybe another testnet rule has been changed)

should compile now.. please try again

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.

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.

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

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.

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)

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

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

Interesting extension of the ID namespace usage :p

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

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

not sure if anyone saw this

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

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! 

Hi everybody !

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

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

Nakanames .... you might be onto something 

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