Topic: [announce] Namecoin - a distributed naming system based on Bitcoin - page 93. (Read 594428 times)
May 19, 2011, 01:11:30 PM
I do have another suggestion as well although this might be hard to get it to play nice with what's out there already but if we are going to have namecoin we also need to remember that IP addresses have their own ICAN known as IANA. We also need IPcoin.
May 19, 2011, 01:08:56 PM
The 512 value was an arbitrary choice. 290 is now the real difficulty :
http://dot-bit.org/forum/viewtopic.php?f=6&t=9
now it'shttp://dot-bit.org/forum/viewtopic.php?f=6&t=9
589.64331461
thanks for that.. I managed to do a couple of blocks at the old value.. has it gone up due to people actually mining it or has it just been changed again by someone?
May 19, 2011, 08:30:57 AM
The 512 value was an arbitrary choice. 290 is now the real difficulty :
http://dot-bit.org/forum/viewtopic.php?f=6&t=9
now it'shttp://dot-bit.org/forum/viewtopic.php?f=6&t=9
589.64331461
May 14, 2011, 12:08:51 PM
The 512 value was an arbitrary choice. 290 is now the real difficulty :
http://dot-bit.org/forum/viewtopic.php?f=6&t=9
http://dot-bit.org/forum/viewtopic.php?f=6&t=9
May 14, 2011, 11:02:43 AM
"difficulty" : 290.98376578, <---- Has it gone down it is it my fault for using the old version?
difficulty is just like bitcoin. if the block generation speed is too slow, it's decreased. May 14, 2011, 10:49:43 AM
Namecoin difficulty varies using the same algorithm as bitcoin. I started the difficulty at 512 to account for GPU mining being available.
Just got this today:
./namecoind getinfo
{
"version" : 32100,
"balance" : 1000.05000000,
"blocks" : 2843,
"connections" : 3,
"proxy" : "",
"generate" : false,
"genproclimit" : -1,
"difficulty" : 290.98376578, <---- Has it gone down it is it my fault for using the old version?
"hashespersec" : 0,
"testnet" : false,
"keypoololdest" : 1304239257,
"paytxfee" : 0.00000000,
"errors" : ""
}
May 12, 2011, 05:42:10 AM
Hi,
I will like create a debian/ubuntu package from namecoin.
* Can you suggest one short and one full description.
I have checked the git repository, but tags are from bitcoin not of namecoin, if you check one tag (any), you will see the bitcoin code only.
If possible get tags for namecoin only, to know the code of each release ?
not oficial debian/ubuntu packages, read more ...
https://bitcointalksearch.org/topic/not-oficial-bitcoin-apps-debianubuntu-packages-2207
Greeting's.
I will like create a debian/ubuntu package from namecoin.
* Can you suggest one short and one full description.
I have checked the git repository, but tags are from bitcoin not of namecoin, if you check one tag (any), you will see the bitcoin code only.
If possible get tags for namecoin only, to know the code of each release ?
not oficial debian/ubuntu packages, read more ...
https://bitcointalksearch.org/topic/not-oficial-bitcoin-apps-debianubuntu-packages-2207
Greeting's.
May 09, 2011, 09:32:05 PM
FYI: khal has opened up http://dot-bit.org/Main_Page for anybody that's still interested in namecoin!
May 07, 2011, 10:31:21 PM
ok is it ever likely to be merged in such a way that you could one the one daemon to mine bitcoin, namecoin or testcoin?
May 07, 2011, 09:49:30 PM
vinced: Other than the DNS code what are the major things you did to namecoin to make a new block?
you can check his commits 
May 07, 2011, 05:18:17 AM
vinced: Other than the DNS code what are the major things you did to namecoin to make a new block?
May 06, 2011, 10:46:44 PM
Lets split this thread into topic specific ones. See TLD poll here: https://www.bitcoin.org/smf/index.php?topic=7459.0
Also thanks grue for the binaries. I finally got it working with my limited knowledge.
Namecoin difficulty varies using the same algorithm as bitcoin. I started the difficulty at 512 to account for GPU mining being available.
By this, do you mean TOR and/or similar? I have access to 100mbps that I generally don't use! (PM me if so, this thread is freaking huge...)
I was talking about software rather than a service, although a DNS service makes sense. A public proxy has some privacy and abuse concerns.
I will merge with the latest bitcoin master branch in the next few days. As far as I know, that will give us this feature.
Can't believe diffuculty is already 512. It took Bitcoin almost two years to reach this. 
I guess I'll just have to buy them...
I believe it's always been permanently set to 512, and doesn't dynamically change as Bitcoin's does.I guess I'll just have to buy them...
Also thanks grue for the binaries. I finally got it working with my limited knowledge.
Namecoin difficulty varies using the same algorithm as bitcoin. I started the difficulty at 512 to account for GPU mining being available.
* We need proxies, browser plugins and DNS servers created to act as a bridge between Namecoin and users.
By this, do you mean TOR and/or similar? I have access to 100mbps that I generally don't use! (PM me if so, this thread is freaking huge...)
I was talking about software rather than a service, although a DNS service makes sense. A public proxy has some privacy and abuse concerns.
any idea on how to get unconfirmed blocks to show? i've been looking through the source code, but it's super hard to read, and i can't find the part where the block's maturation status is checked.
I will merge with the latest bitcoin master branch in the next few days. As far as I know, that will give us this feature.
May 06, 2011, 09:56:03 PM
any idea on how to get unconfirmed blocks to show? i've been looking through the source code, but it's super hard to read, and i can't find the part where the block's maturation status is checked.
May 06, 2011, 10:57:57 AM
This is so hard to read with individual backslashes...you can use single quotes around the entire string:
namecoind name_update d/example '{"map": {"": "1.2.3.4", "www": "4.3.2.1"}}'
namecoind name_update d/example '{"map": {"": "1.2.3.4", "www": "4.3.2.1"}}'
Much better indeed :p
I've launched the dot-bit project to spread .bit domains by providing ressources and tools for the developpers and the end users :
https://bitcointalksearch.org/topic/announce-dot-bit-project-namecoin-website-7412
May 06, 2011, 10:41:15 AM
Simple address mapping (example.bit → 1.2.3.4, www.example.bit → 4.3.2.1, etc.):
Code:
$ namecoind name_update d/example "{\"map\": {\"\": \"1.2.3.4\", \"www\": \"4.3.2.1\"}}"This is so hard to read with individual backslashes...you can use single quotes around the entire string:
namecoind name_update d/example '{"map": {"": "1.2.3.4", "www": "4.3.2.1"}}'
May 06, 2011, 04:25:37 AM
I'm a bit confused.
I've re-read thread and the github page but couldn't find an answer for this:
When is a domain name definitely tied to a namecoin address?
after ./namecoind name_new ?
or after ./namecoind name_firstupdate ?
how much does each of those actions cost?
I've re-read thread and the github page but couldn't find an answer for this:
When is a domain name definitely tied to a namecoin address?
after ./namecoind name_new ?
or after ./namecoind name_firstupdate ?
how much does each of those actions cost?
name_new & name_update costs 0.01 namecoins.
name_firstupdate costs 45,27 namecoins and reserves the name for you.
May 05, 2011, 10:12:22 PM
can we have a different irc boostrap channel? right now, it's #bitcoin. change it to something else, like namecoin
It should be 'namecoin' already. See CNamecoinHooks in namcoin.cpp.
May 05, 2011, 09:53:39 PM
can we have a different irc boostrap channel? right now, it's #bitcoin. change it to something else, like namecoin
Code:
hooks.cpp, line 110:
string CStandardHooks::IrcPrefix()
{
return "bitcoin";
}
May 05, 2011, 05:41:25 PM
ns.bit is up. It is a DNS bridge for Namecoin. Make 78.47.86.43 your primary DNS server to start using it right away. Note that khal is also running a DNS bridge.
The server can resolve ICANN and OpenNIC (.geek, .glue, etc.) domain names too, so it should be a drop-in replacement for whatever server you're using, though currently it's in an experimental state so you can experience downtimes. It maps Namecoin names to .bit, .c, .b and .n TLDs (i.e. ns.bit, ns.c, ns.b and ns.n are the same). This behavior will probably change as soon as there is a community decision on the standard TLD though, since it's not automatic in the case of DNS delegation (if you host your own DNS).
Configuration examples:
Simple address mapping (example.bit → 1.2.3.4, www.example.bit → 4.3.2.1, etc.):
Delegating the entire domain to a DNS server (like a DNS registry):
Delegating a subdomain to a DNS server:
As discussed on the IRC, nameserver addresses can be IPs or canonical names. IPv6 support is in an experimental state, you're welcome if you can help me test it.
A more capable scheme is in the works, so please contact me if you are working on a similar thing.
The server can resolve ICANN and OpenNIC (.geek, .glue, etc.) domain names too, so it should be a drop-in replacement for whatever server you're using, though currently it's in an experimental state so you can experience downtimes. It maps Namecoin names to .bit, .c, .b and .n TLDs (i.e. ns.bit, ns.c, ns.b and ns.n are the same). This behavior will probably change as soon as there is a community decision on the standard TLD though, since it's not automatic in the case of DNS delegation (if you host your own DNS).
Configuration examples:
Simple address mapping (example.bit → 1.2.3.4, www.example.bit → 4.3.2.1, etc.):
Code:
$ namecoind name_update d/example "{\"map\": {\"\": \"1.2.3.4\", \"www\": \"4.3.2.1\"}}"Delegating the entire domain to a DNS server (like a DNS registry):
Code:
$ namecoind name_update d/example "{\"map\": {\"\": {\"ns\": [\"ns1.example.net\", \"ns2.example.net\"]}}}"Delegating a subdomain to a DNS server:
Code:
$ namecoind name_update d/example "{\"map\": {\"\": \"1.2.3.4\", \"www\": {\"ns\": [\"2.2.2.2\"]}}}"As discussed on the IRC, nameserver addresses can be IPs or canonical names. IPv6 support is in an experimental state, you're welcome if you can help me test it.
A more capable scheme is in the works, so please contact me if you are working on a similar thing.
May 05, 2011, 12:04:53 PM
I'm a bit confused.
I've re-read thread and the github page but couldn't find an answer for this:
When is a domain name definitely tied to a namecoin address?
after ./namecoind name_new ?
or after ./namecoind name_firstupdate ?
how much does each of those actions cost?
updating is free, i believe. I've re-read thread and the github page but couldn't find an answer for this:
When is a domain name definitely tied to a namecoin address?
after ./namecoind name_new ?
or after ./namecoind name_firstupdate ?
how much does each of those actions cost?
Jump to: