Quote from: DeepBit on June 15, 2012, 12:28:43 AM

Quote from: TT on June 15, 2012, 12:00:15 AM

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!

Actually using public key makes those transactions on average 9% smaller than with a key hash, so I'm using full key for a reason.

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.