Or, maybe the Namecoin can use the same approach of "supernode / light client", or, more or like the Bitcoin Lightweight Client, called Electrum.

What about adding support for multiple currencies to Electrum? Like Namecoin or even Litecoin?!

Cheers,
Thiago

Namecoin is very-very raw project in current time. It has no strict rules for name resolution and name resolution is actually tricky there.

I am fall into namecoin -> I2P integration development (fully anonymous domain and destination) https://bitcointalk.org/index.php?topic=60879.0 and found there many questionable points.

Overall question is: how many terabytes will eat local domain database if there will be more that 1 million domains changing their records. Each resolution record is recorded forever. Will the regular users want to install such heavy software on their computers in the future?

Hi there,

started using litecoin yesterday and I am interested in it.

I am mining and it does work, but the gui stays at "Synchronizing with netowrk.... 0%".
I have tried playing with firewall rules in windows to no go, and removing all the files but wallet and then starting litecoin again and still no go...

I have received ltc from my mining pool, but the GUI won't show them, and since I don't know where litecoind is, I cannot query it


I have played with my litecoin.conf to no go, here is my current one:



testnet=0
server=1
rpcuser=miner
rpcpassword=litecoin
#gen=1
#rpcport=8337
#daemon=1

block_nTime=1317972665
block_nNonce=2084524493

(I used to have different user/password but since there is no option in the gui for that, I thought maybe I need stock ones, but no go...).

Same issue on 2 computers, both running Win7.

Thanks

Hey guys !!

Been off the radar for a while dealing with real life. Was thinking about reopening this project for something to ease myself back into things. Anyone interested ? Was going to leave the mining stuff to someone else and start with a fresh platform and all source made public.

If anyone's interested in getting involved PM me and get involved. Even if it's maintaining a few packages it would make the dev of this project more pleasurable lol !!

It's not quite that simple; typical captive portals require that you trust them with your credit card number, but you would never want to give a captive portal your private key.

FWIW, I've run a local DNS server since my client was OS2 2.0 and my connection was dial up, with a slow connection it did a lot for reducing perceived latency when web browsing.

These days there are a lot of alternatives, but the standard is a program called BIND, which can be had for just about any platform. Linux distributions provide it universally, and it's pretty tolerable to set up on Windows as well. It does things beyond simple caching that the built-in Windows DNS cache does not.

http://www.isc.org/software/bind

The simplest thing to set up with BIND is a caching server with forwarding, the last time I installed it under Windows ( sometime in the 1990s ) this was the default configuration. You do have to add the IP addresses for your forwarding servers ( e.g. your ISP ) and then point your local IP configuration to query the local name server at 127.0.0.1 .

The reason I mention all this is that I had a hard time replicating the problem described here, I'd never seen it. It had been so long since I did my set up I had to consider why.

As it turns out, my DNS forwarders are Comcast and Google. Here's a portion of my named.conf, one of the configuration files for bind ( the program executable is usually "named" or "named.exe" ).

        forward first;
        forwarders {
                75.75.75.75;
                75.75.76.76;
                8.8.8.8;
                8.8.4.4;
        };

Beyond that BIND will identify the authoritative name servers for a given name and query those directly, in this case NS1.XWAYLAB.COM and NS2.XWAYLAB.COM for bitcoinica.com .

So, using BIND can provide robust name resolution from multiple sources, it worked transparently for me with the bitcoinica .com DNSSEC issue present, most likely by using Google to resolve the authoritative servers and then using those to resolve the actual name.

zone "bit" {
        type forward;
        forwarders {
                178.32.31.41; // French bit DNS
                78.47.86.43;  // German bit DNS
        };
};
zone "onion" {
        type master;
        file "named.empty";
        allow-update { none; };
};

I wrote them asking if they were interested in a $500 share of the hologram order, and they declined.  Those holograms could have been used as the squares they already put in their prior batch of BitBills, would have added a neat touch.

They said they don't want to commit "that much money" until they know for sure what they want to do.

I suppose it's a matter of priorities.  Their product seemed to be of pretty high quality such that I wouldn't think of the producers of such a good product to be worried about $500, knowing full well there's a demand for it.  I take it as a sign that they might not produce them for whatever reasons of their own.

how does openDNS or googleDNS work?

I disagree...

Probably not worth the trouble. Most people who are interested in Bitcoin do have the know how on how to secure their wallet, or at least they're able to follow your tutorial (which is very nice btw).

Even if there are 5-10 people interested in your project, there will just not be enough people using it in the end to justify your efforts.

I apologize for this technical issue. Apparently 3% of global DNS servers couldn't resolve bitcoinica.com properly due to DNSSEC settings.

I have investigated into this issue carefully and found that the problem was with the DNS provider we are using. They stopped signing for DNSSEC after a recent domain transfer out of GoDaddy.

I have fixed the problem now and the domain is being signed again. Comcast users, please verify that you're able to access bitcoinica.com.

Again, sorry for the issues that cause constant troubles. And thumbs up to Comcast, because one of their engineers sent us the detailed problem trace and assisted us in the resolution.

$ dig @75.75.75.75 bitcoinica.com

; <<>> DiG 9.7.3-P3 <<>> @75.75.75.75 bitcoinica.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48531
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;bitcoinica.com.			IN	A

;; ANSWER SECTION:
bitcoinica.com.		3600	IN	A	50.56.4.62

;; Query time: 151 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Mon Jan 23 09:12:08 2012
;; MSG SIZE  rcvd: 48
$ dig @8.8.8.8 bitcoinica.com

; <<>> DiG 9.7.3-P3 <<>> @8.8.8.8 bitcoinica.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19751
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;bitcoinica.com.			IN	A

;; ANSWER SECTION:
bitcoinica.com.		515	IN	A	50.56.4.62

;; Query time: 21 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jan 23 09:13:03 2012
;; MSG SIZE  rcvd: 48

Sadly, neither of these approaches will work. P2Pool queries namecoin using the "getauxblock" RPC call instead of the normal "getwork" call. It'd be possible for a Namecoin mining pool to implement "getauxblock", but I doubt that any do. Pointing P2Pool at another P2Pool will not work for the same reason - P2Pool only presents "getwork" to miners. Fairly complex changes to P2Pool are needed to make pooled merged mining work.

is that good or bad? does not compute.

armory sounds interesting, but i'm put off by the fact that the wallet file is not compatible with the satoshi client.

I still believe not only stats are necessary, but basic GPU control as well...

SNMP exposes management data in the form of variables on the managed systems, which describe the system configuration. These variables can then be queried (and sometimes set) by managing applications.