The code and protocol, as designed, put a hard limit of around 21M bitcoins total.

I don't have any hashing power I want to sell ATM, but I'll keep this in mind. Might also want to *buy* hashing power.

Ok, thanks. That's what I wanted to know.

Woah, ok, that changes everything.  Thanks for letting us know.

Also, what is the weight and composition of the coin?

I checked my spam folder, but I might have missed it.  Thanks for activating, I will now give it a try.

Edit: I still get "Login failed You haven't authorised your email account yet" when I try to log in.

Is the coin 1 oz of 99.99% silver?  If so, and if the auction is not over, I bit 6.9 BTC.

Thanks kjlimo. What pool do you use? Or is devcoin.org the only pool (I ask because I can't seem to get the conf. email).

Agreed.  But for above-mentioned reasons, all keys that have been swept should be kept hidden in an advanced interface somewhere, where you can periodically (or automatically) check and see if funds have been added to any of them.

What if I sweep the private key and transfer my 20 BTC, at a later date you assume you can send me an additional payment using the same public address as before, but I no longer have the private key? Of course, YOU personally wouldn't do this, but people might.  This is why I'd like to keep the insecure private keys around to check/resweep them at a later date, if necessary.

Easy.  I generate a (secure) vanity address to receive donations.  I publish the address all over the place and people start donating to it.  I then inadvertantly/unthinkingly/stupidly email the private key as plain text to myself for whatever reason.  The private key is now no longer secure, but I would still like to keep sweeping it to get any additional funds sent to it.  Even if I change my public donation address, it is cached all over the place and people have it saved, etc, so I will keep receiving donations there for some time or even indefinitely. 

Emailing the private key as plain text is only one example. What if the computer storing your unencrypted wallet.dat gets a virus/trojan?  What if the computer gets stolen?  I know you and I would never mail a plain text private key, not would we ever get viruses (we're careful, after all), but there are dozens of scenarios where the secure private keys that correspond to public keys that may continue to receive funds could become compromised and fall into the "insecure" private key category.

You forgot to add that you can only buy whole dollar amounts of Linden and you can only buy whole bitcoins, so you will be left with the change in USD and in Linden dollars in your virwox account.

BTW, I just signed up for pool.devcoin.org and I never got the email to confirm my email address.  Is the server sending email correctly?

Thanks, that's what I wanted to know. So if I want to mine at pool.devcoin.org, I would just use any bitcoin miner and point it to the pool IP and port?

Given the current difficulty of 57.3, is it practical to mine devcoins with a CPU?  How long would you estimate it would take to find a block this way?

The abstraction was definitely intentional, but I'm not sure it was good. It works well for casual users (the majority), but for one has fundamental privacy concerns.  So for some (most?) it would be noise, and for others it would be essential.  I don't see the problem with having the funds to address breakdown in an advanced tab that casual users can ignore. 

I assume a redeemed phone card can never have funds placed in it again.  If I were to publish an address for payment, then sweep the private key to get the funds, who is to say that someone will never send funds to that (published) address again?

I agree mostly.  Why not have:

1. IMPORT and keep the key as a first-class citizen in your wallet.
2. SWEEP key and TRANSFER any funds to your wallet (or another arbitrary address). There would be a separate interface (completely independent from the wallet) in the program showing a list of all keys that have been swept, and showing any balance in each of them. This would not be included in the wallets balance, unless you SWEEP them again.

For private keys that are known to be secure, I want the option to import them as first-class citizens in my wallet (think a securely-generated vanity address I want to be using).  For private keys given to me by someone else, I want to transfer the funds to a new key in my wallet, but I want to keep a list of those private keys that have been transferred from, so that if any more funds ever shows up in any of them, I can also transfer those funds to my wallet.

I think part of the inherent problem is that the Satoshi client shows transactions and your total balance. This is fundamentally wrong. It should show all your key pairs and the funds that are in each. When you send a payment, you choose one or more keys to send the funds from. If it was done this way, each key/address pair could be marked as generated in the client or imported.

If I have a bunch of USD in my wallet in my pants, the actual physical selection of bills I have is important to some degree. What if I want to tip someone with a small bill? What if I need to make a small purchase where large bills are not accepted? What if one of the bills might be counterfeit and worthless? All of this is important information and if shown in the client, mitigates many of the problems of how to deal with imported/swept private keys.

I think they identified themselves with the path requested in the first hit. Probably it was an auto-scanner that just follows links?

As does this thread.

Recognizing one's mistakes and trying to correct them is a wonderful quality to see in someone.

What *nix OSes do you offer?

Still not following, sorry.