I guess it should be possible to send them anyway if you modify the client. Or just wait a few more days. It's just 0.01 BTC and they won't go anywhere.


Yes, it's possible to receive bitcoins on an address that has never been connected to the network. It's also possible to send btc to non-existing addresses that are in the correct format (we had that question in another thread yesterday).

That's the tricky part with this currency. I'm convinced of the technical security of a transaction but everyone who wants to trade is a suspected thief and scammer. The mental threshold of people to try fucking over users in this forum and elsewhere is notably low.

Have you tried smoking a Bitcoin yet?

I didn't try building a dummy plug myself but I heard that a DVI dummy is way more likely to destroy the card when done wrong. You're probably right though, 1 resistor should do the trick.

It's not too long. Go get a book and train your reading skills.

As for the thread: I don't see a problem with Bitcoin being a "shadow currency". That's the whole purpose. Why would I want to buy or sell BTC for USD/EUR if I happen to mine an accepted currency without any money trails?

They are lost. Look at the Address Astro posted above. The right to transfer (= the ownership) of a coin is granted by the possession of the private key of the address where the coin was last transferred to.

With Layer 1 being 1 Person, Layer 2 10 Person and Layer 6 20.000 person, the whole profit of Layer 7 would go to you (or who ever starts this scheme) = 20.000 btc. But I really doubt that you can find 200.000 idiots for this.

Yeah you might want to take that comment with a grain of salt. Your particle analogy seems a bit exaggerated though.

Yes, it's like with cash and washing machines. So much gets destroyed, they even need to print new notes all the time!

If that happens on a regularly basis I might switch to "mine" addresses by creating new ones until I get one of those "forever lost" coins.

I'm pretty sure they're lost in that case. AFAIK the network doesn't know about addresses that never received anything so there's no way to tell you that the address is invalid. An address could have been created offline and would still be able to get coins. It just has to download the blockchain later to get the transaction information and can then proceed to redeem the coins in new transactions.

If you believed for more than a second that such a thing would be possible then Bitcoin clearly isn't for you. Seriously.

Use Paypal or something else where you can get your money back after it has been stolen by simple social engineering and a file you shouldn't have executed or a link you shouldn't have visited.

In the meantime I'll continue using Bitcoin because I don't fall for shit like that.

So the card in slot #1 always gets hotter than the rest?
You can't really say 77°C is OK on all cards or manufacturers. I suspect your airflow to be in a way that the card in slot #1 is getting all the hot air from the other 2 cards.
Are the fans at 100%? Also try underclocking the card in slot #1 and see if it gets any better.

I've experienced a lot of freezes with default clock and default autospeed of the fans with temps of about 70°C. Runs way more stable at 65°C max.
Temperature sensors aren't always reliable. They only measure at one specific point.

Run the client with the -rescan parameter. That will take a while. The balance isn't stored in the wallet, it's in the blockchain. Your wallet is basically the authorization to redeem the coins.

What ever you do you should always save it in different physical locations. The redundancy will minimize the risk of loosing all those passwords.

Also you shouldn't register all important accounts on the same e-mail address. You can make more than one GMail account for example.

For the encryption I'd choose a password container with encryption like KeePass and a small Truecrypt container. Put the password container into the Truecrypt volume and sync it (the Truecrypt container) with other services. If your dropbox gets compromised they'd still have to crack the Truecrypt container. The password database is encrypted too, so you can have the Truecrypt volume mounted all the time. The passwords would only be exposed if KeePass (or LastPass or whatever) is currently running.

Not an expert in P2P but:
At least one of the 2 participants needs to be able to accept incoming connections (NAT forwarding, Firewall exceptions etc).

If most of the nodes don't open their ports then some of those that do would need to connect to a lot more than the current maximum (about 60? I doubt the client tries to connect to more).

The new version might have changed in a way that you connect to max 8 other nodes on your own and wait for additional 52 connections on the incoming port. Just guessing from a technical point of view.

You'll most likely have to make the dummy plug yourself. One DVI-VGA adapter and 3 resistors. Doesn't look that hard to make in the link I posted earlier in this thread.

I currently have the same problem with 2x 5770. My board doesn't support crossfire but they should work on their own.

Apparently you can try either a) changing something in your registry or b) connect another monitor or a DIY dummy plug.

I'm rather pessimistic about my case because I can't even find the second card in the device manager or anywhere else. The fan is active but that's about it. Maybe not enough power from the supply or something.

Have you tried port forwarding in your router? It's not necessary according to the wiki but I get way more connections that way. Currently about 60, without NAT forwarding <10.

That can't really be the reason why it drops to 0 but maybe the problem just vanishes with that change.

Nice to hear it's working.
Here's my address: 14BML4Soif6FNRmhECe27a8yGFsMSUZWAc