[ANN] Namecoin v3.50 : faster & better

[phelix]

when you browse .bit sites you can still be tracked and everything is unencrypted

Correct.

namecoin is just another DNS system.
[...]

you could hardly be more wrong. namecoin is a coin accounting and generic key/data storage system.

[1715022683]

1715022683

[1715022683]

1715022683

[1715022683]

1715022683

[Deafboy]

Sorry, I thought we were speaking just about browsing regular websites through the .bit domains. In this point of view it is just another dns.  And your connection to http server is as vulnerable to middle man as always. I know that lot of other data can be also stored in blockchain.

[marcus_of_augustus]

Sorry, I thought we were speaking just about browsing regular websites through the .bit domains. In this point of view it is just another dns.  And your connection to http server is as vulnerable to middle man as always. I know that lot of other data can be also stored in blockchain.

No sorry, you are still wrong because it can provide for fully-autonomous (i.e. local look-up of regular .bit domains) also. You are correct that data can be stored in the namecoin blockchain, unlike bitcoin.

It is not in any way shape or form, "just another DNS" ... but yes it can do regular DNS as one small part of its total functionality. How about that?

[rjk]

My favorite use-case that I hope can be widely implemented is that of storing a public key fingerprint in the Namecoin system. This is how you can kill off the CA system and still be secure.

[Bitinvestor]

My favorite use-case that I hope can be widely implemented is that of storing a public key fingerprint in the Namecoin system. This is how you can kill off the CA system and still be secure.

What needs to be done to make this happen? I'm not familiar with how the CA system works in detail, but I do know that the cost of it can be a real burden for smaller websites.

[rjk]

My favorite use-case that I hope can be widely implemented is that of storing a public key fingerprint in the Namecoin system. This is how you can kill off the CA system and still be secure.

What needs to be done to make this happen? I'm not familiar with how the CA system works in detail, but I do know that the cost of it can be a real burden for smaller websites.

The main thing is a way to validate it on the client side. The storage of the fingerprint in the Namecoin system already works.

[K1773R]

donwloaded the 3.5 to a fresh VM, namecoind gets stuck at 10500 blocks, there is no output nothing.

Code:

{
    "version" : 35000,
    "balance" : 0.00000000,
    "blocks" : 10500,
    "connections" : 10,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 3767.78158122,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1354097808,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

EDIT: nvm, the one sending me the chain got stuck, after restarting namecoind it works now

[phelix]

[...]
3. The existing alias is "khal" (stored in namecoin as "id/khal") and contains that data :

{
 "email" : "khal@dot-bit.org",
 "bitcoin" : "1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T",
 "namecoin" : "N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9"
}

4. Use the command below to send me 2NMC :

Code:

namecoind sendtoalias khal 2

The coins will be sent to my namecoin address N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9.
[...]

completely missed the sendtoalias command.

would be interesting to also add a sendbtctoalias command that would open a bitcoin uri: bitcoin:1bitcoinaddress

[khal]

completely missed the sendtoalias command.

Yes, it's working (it as a beta version, may still change, so it is only present in my github tree : https://github.com/khalahan/namecoin)

would be interesting to also add a sendbtctoalias command that would open a bitcoin uri: bitcoin:1bitcoinaddress

Indeed, it could be a simple way to start managing bitcoin aliases.
Does the main client bitcoin client support uri schemes ?

[phelix]

completely missed the sendtoalias command.

Yes, it's working (it as a beta version, may still change, so it is only present in my github tree : https://github.com/khalahan/namecoin)

would be interesting to also add a sendbtctoalias command that would open a bitcoin uri: bitcoin:1bitcoinaddress

Indeed, it could be a simple way to start managing bitcoin aliases.
Does the main client bitcoin client support uri schemes ?

good to see you alive. I thought you had been kidnapped by the cia.

I don't usually use bitcoin-qt any more but I think it has. Just noticed URI support does not work any more on my own machine with latest electrum and multibit 0.5.7 installed so this is a problem.

Also looking into shared namecoin/bitcoin private keys. I was not aware it is possible to calculate the corresponding namecoin address from a bitcoin address and vice versa.