Bitcoin should automatically purge them either when it starts, or when it exits.  Just restart now and then and they'll be fine.

Meh, I've registered on forums and news site comment sections over less before.

And I have to agree with the original post, sockpuppet or not, threats of violence aren't cool.  On the other hand, I consider internet forum threats to be about as serious as a drunk guy sitting at the bar telling his beer that "I'll show them".

So far, no one has figured out a way to pay them.  Also, the costs aren't great, and they are connecting to the network for their own purposes anyway, so why bother?

Don't let anyone trick you into posting pictures here on the forums when you are done.

Saying that there are no addresses is a slight exaggeration.  But a useful one.  Smile and think of the kid from the Matrix telling Neo that there is no spoon, while he is holding a spoon.

Lots of people get stuck in their thinking because they expect the address to be a proper entity that tracks the balance sent to and from it.

Your balance is the sum of the values of the transactions that you can spend, that is, transactions that you have the key to, and that haven't already been spent.  When you make a new spend, the client grabs one or more of them, completes them using private keys from your wallet, and creates one or more new outputs.

And yes, the private key is just a random number, the public key is just derived from multiplication (funny multiplication) from that private key, and the address is the hash of the (hash of the) public key.

If you want to really get into it, transaction outputs are actually scripts.  Addresses are used to create the (incomplete) scripts, and then redeeming them later involves adding the missing parts to complete it.  To complete the script, you sign the partial transaction with your private key and provide the public key that corresponds to it.  That way, anyone can verify that the script was signed by the holder of the private key that corresponds to the public key in the completion, and they can also hash the public key to get the address that it was sent to, to verify that the keypair used to sign it is the keypair that it was intended to go to.  Oh, except that there are other script types, and BIP16 P2SH lets you make complicated scripts that are presented at completion instead of at creation, and...

Really, dree12's chart explains it all very well.

Uh, I'm not exactly a pro, but I've done a lot of soldering work, and this seems very, very wrong to me.  Have you ever tried this technique?  On electronics?

If I were trying to remove an ATX power connector, I'd soak the area with a temperature controlled SMD rework gun at a very low setting, flux the shit out of one pin at a time, then use a decent quality suction iron on it.  Pause and resoak between pins to allow the heat to balance out.  If you are very good with wick, you could try that, but make sure you pre-heat and re-flux the wick too.

Removing a structure like that from a modern 4 or 6 layer board is not trivial, particularly when it was made in an industrial process using ROHS-compliant solder.

Huh?

There are no addresses.  Only transactions.

When you spend, you are spending a transaction that you hold the key to.  That transaction had previously been sent to an address that corresponds to a key you have, but the spend isn't from the address, it is from other transactions.

There are two ports.  Are you trying to change the RPC port, or the P2P port?

In your bitcoin.conf, make sure you have these two lines (but with your intended ports):


Also, double check the spelling of rpcport if that is the one you are trying to change.

For 50 BTC, I'll teach you how to use GPG and trade on MPEX.

Happy to help.  I think that bitcoin has huge potential, and I suspect that a mini-rig SC might be a good investment.  But the risk is HUGE.  These forums are full of people doing calculations based on difficulty numbers that are WAY too low, exchange rates that are WAY too high, or both.

There are too many factors that are totally unknown here.  Unless someone knows a lot more than what these forums know collectively, bitcoin is a gamble, not an investment.  A fun gamble, an important gamble, a gamble that could change the world.  But still a gamble.  And you never gamble what you can't afford to lose.

Go take the tour, check it out.  Let us know how it goes.

But do NOT spend your life savings on a mining rig.  Drop a couple of grand on a couple of of single SCs if you must dabble.  Absolutely do NOT drop 30 grand on bitcoin unless you can afford to kiss that money goodbye (and you can't).

For the love of god, do not do it.

I think that in one of his speeches, Gavin put it something like this:  Years from now, 1 bitcoin will be worth either a lot, or nothing at all.  It is very unlikely to be around the same price it is now.

I fully support that view.  It doesn't mean that bitcoin must be "all".  It doesn't mean that it has to be everywhere and do everything.  But it'll either take off and be pretty big, or it'll vanish into the mists of history.

Even better, there are optical M-of-N schemes too.  You can actually design a stack with holes that reveal the code only when you combine enough of them physically.

You have two choices.  Option 1, you ignore it and let the client merge transactions as needed.  Option 2, you use the raw transaction API (in the future) to manually create transactions that merge many small inputs.

Maybe someday, far into the future, the default client will support sweeping small old transactions automatically.  I wouldn't hold my breath.

By the way, I get a lot of small transactions from p2pool mining.  I'm writing a script to grab old transactions and merge them back into my wallet in even lumps.  For no particularly good reason.

Meh.  Didn't the first computer verify it already?

Ugh.  No one will accept changes of that sort in the first place.  We know better.  And by "we", I mean the bulk of current bitcoin users, and absolutely 100% of the people running virtually all of the important associated services (pools, exchanges, explorers, gambling sites, etc)

I thought you meant like UI changes and stuff, because making the UI annoying is literally the only thing they could really do.  If someone leaned on the devs to make them change the protocol for the worst, that fork would die on the vine and the old version would continue.

Redo your calculations at about 30x.  BFL is offering 3 sizes.  The smallest is 23 times more hashes/sec per dollar than what is commonly available with GPUs, the medium one is 30x, and the big one is 33x.  I'm projecting difficulty around 70 million.

I would make sure that those safes are in really different places, meaning different buildings, and hopefully different watersheds.

Most fire safes are designed for paper.  There are some that are "media rated", but that means "magnetic media", meaning they'll keep the items inside below the Curie point of most magnetic storage (tapes and hard drives).  I certainly haven't ever seen any that are "Flash Memory"-rated, and I'm not sure if such a thing even exists.

Personally, I generated a bunch of keys offline, encrypted them, burned them to M*Disc DVDs and printed the addresses (on paper) so that I could send to them.  I think that if my home, my bank, and my office (40 miles away) all burn down, I'll have more pressing problems to deal with.