r4mscDrVMQz2on2px31aV5e5ouHeRPn8oy

I apologize. You're right about redeeming scripts being shorter.

Regardless, the issue of whether or not you use the full public key is practically negligible compared to the issue of sending each payout in a separate transaction.

Hmm, let's see:

Using the full public key:
04a39b9e4fbd213ef24bb9be69de4a118dd0644082e47c01fd9159d38637b83fbcdc115a5d6e970 586a012d1cfe3e3a8b1a3d04e763bdc5a071c0e827c0bd834a5 OP_CHECKSIG

Using the hash:
OP_DUP OP_HASH160 0568015a9facccfd09d70d409b6fc1a5546cecc6 OP_EQUALVERIFY OP_CHECKSIG

Each opcode is one byte.

Therefore, using the full public key requires 66 bytes while using the hash requires 24 bytes for the change output script.

That's to say, using the full public key makes the transaction about 233 bytes whereas using the hash would only require about 191 bytes. Your transactions are about 22% larger than they would be if you used the hash.

And you have littered the block chain with 321053 of them as of the writing of this post!

And you pay nothing to other miners who graciously include them in their blocks while giving them low priority in your own blocks.

Only satoshi dice comes close to polluting the block chain as much as deepbit...but one could argue that satoshi dice requires individual transactions per play whereas there is absolutely NO REASON WHATSOEVER for deepbit to be sending separate transactions for each payout.

Please fix your send code to use multisend and to use the public key hash for 1VayNert3x1KzbpzMGt2qdqrAThiRovi8 instead of the full public key for the change output while you're at it!

You're polluting the block chain unnecessarily and slowing down your own confirmations.

I've been proposing the following:


https://bitcointalk.org/index.php?topic=84585.msg937236#msg937236

Please, exchanges, implement this SOON. You cannot implement it soon enough.

Withdrawal to bitcoin address is the exchange function/API call that is most prone to theft.
Other withdrawal methods have at least some level of traceability and/or reversibility.

Therefore, I propose the following solution:
1) create a completely separate right for both the web and the API for withdrawal to bitcoin address, separate from all the other withdrawal methods.
2) allow the owner of the account to have a whitelist of bitcoin addresses to which it is allowed to withdraw from both the web AND the API.
3) require two-factor authentication for adding or removing addresses to and from the whitelist.

This simple feature means that even in the event of an attacker gaining access to the user's web dashboard or the user's API keys,
the attacker will not be able to withdraw bitcoins to addresses of his choice.

Simple fix to a significant security risk.

Yes, I would be very interested, too. I wrote all the code to interface the Genmega hardware.

Ah, interesting. Yes, you're right...I apologize. I'll take a look at this idea.

No, but thanks for throwing in a nice strawman.

I'm suggesting something along the lines of what people like Dan Kaminsky have suggested: that it would be possible to have proof-of-work that cannot be massively accelerated with GPUs or ASICs...but that has high memory and serialization dependencies or other resource requirements, too.

http://www.slideshare.net/dakami/bitcoin-8776098

cunicula, you're right. I should clarify.

I didn't mean to say that the concept of a public transaction history with a trusted timestamp mechanism should be tossed away. I just meant that proof-of-work as the mechanism for establishing trust would be rendered effectively useless.

You could still have a mechanism based on web-of-trust and reputation.

If it is possible for any single player to manage to amass that much computing power relative to the rest of the network, it seems to me that the whole proof-of-work concept is invalidated, fundamentally. We're just back to human webs of trust relations. Those who then claim that bitcoin has been hacked would be right to do so...and perhaps it would be best to abandon the block chain concept altogether.

Having said that, I believe it is possible to modify the proof-of-work algorithm to make it less likely to favor people with a particular type of specialized hardware.

I tried that script and I get this error:


What is this z library, why isn't it installed, and where can I get it?

For 10 btc, I'll give you a php script that can generate the addresses immediately. If you also want the component
that can generate and broadcast the transaction, we can negotiate that separately. Or make an offer.

Send to 1DKb46tHPGy7yLZKFrWYL7ifdrPS1eSprc

it's already done that way, sir...

The transaction inputs are in order and they are generated for you...and I even have an API that
can broadcast the transaction.

I have it coded up for you already

How much are you willing to pay?

Who do you think did this?

http://blockexplorer.com/tx/28ccf29cfcc9f82d42793db770e7c7894d61ccf3d18299f34bda2e54415da287

:}

I've got a complete API for generating these types of transactions from text...if the price is right, you can have it.

I hope you guys are trolling...but in case you're actually thinking about carrying on with this
line of reasoning, I thought I'd point out that you only need to consider prime n since if n is
composite, say n = pq, you have x^(pq) = (x^p)^q = (x^q)^p, so if a solution existed for n, it would also
exist for p and for q.

And no, you cannot prove FLT generally using simple congruences...but you can definitely prove it for
a bunch of small primes.

For the record, Jonathan and I put in many long hours getting his ATM machine working, often staying very
late nights at his place toiling away. Not only that - Jonathan found him a video production crew to document
his company and also found him a booth at a show after Todd soured his relationship with Play N Trade who
had offered him a retail location in which to debut his ATM.

We had an agreement...he was going to pay us cash for our work and he would get to keep the source code.
Well, he didn't come through on his side - we successfully got his machine working and got him a forum in which
to present it and promote it but he failed to pay us what he owed us. Not only that, the whole time we were there
he was secretly recording us and videotaping us...and acting generally paranoid...and seemed to have a rather
unstable personality.

Todd got upset at Jonathan because Jonathan had the nerve to tell Todd to his face how he felt about his creepy
ways...and I believe both of us had reason to be upset for the fact that he had failed to come through on his
side of the arrangement and trying to claim that he would pay less than he had originally said...and even admitted
that he knew it was more than he was saying it was.

So we both walked out of his garage. He still kept every single line of source code,
but despite his obsession for adding all sorts of superficial features, he didn't seem to want to give much priority
to ensuring the basic functionality was stable...nor to really understand how to even do as much as start the app.
If he wasn't able to figure out how to get the app running once we left it was only because he never even bothered
to ask us how to configure it and set it up.

Seeing that it was highly unlikely he would ever pay the full amount he owed us, I later even offered him that I'd
show him everything he needed to get it working again for less than half of what he owed...and that we'd consider
it a done deal. Well...he flaked, claiming that he was going to have some russian relatives redo the software instead.

Jonathan and I were nothing but nice to Todd until it became apparent that he was someone with which it was impossible
to do business. I regret that it had to end like that, but that's the story.

Just wanted to set the record straight.

Here is an example:

http://blockchain.info/tx-index/12752243/8f64d2b7a762767e3870c4aee95f8c7b5439cf02cf7d7e5d99b6e39967ecada8

etchablock.com is very inexpensive and will notify you the moment the transaction is sent and the moment it gets into a block.

You can leave tributes, write poems, or send love letters...How better to show someone your love is eternal! And your text can be read at blockexplorer.com or any other block chain viewer site.

Try etchablock.com!