Quote from: Matt Corallo on September 05, 2012, 05:06:16 PM

Oh god, thats awful...that is quite possibly the worst way to implement messages in terms of network load...

I'm not sure it's *the* worst way. Look at the Mitt Romney extorters address which someone sent 30 transactions just to try embed an imgur link (http://blockchain.info/address/1HeF89wMjC48bWNgWvVo7Wu3RaLW8XVsE8).

Quote from: Gavin Andresen on September 05, 2012, 05:13:59 PM

Yes, please don't create lots of unspendable scriptPubKeys. There are more prunable ways of embedding messages into transactions. And there are even better ways of associating messages with transactions, so only people involved with the transaction can read the message (if that's desired).

In other words, lets figure out how to do this the right way. The way you're doing it now will stop working as soon as the network upgrades anyway (0-value outputs are nonstandard as of the 0.7 release).

I someways making the transaction un-prunable is better for messaging, but I understand your concern.

One way to do it could be to use an M-Of-N 1 of 2 multi-signature transaction and have the 2nd public key as the message. The tx would then still be spendable with the first public key, but not many clients would be able to redeem it. I'm open to suggestions?

Quote from: GCInc. on September 05, 2012, 07:09:38 PM

Cannot spend from wallet, getting error "ReferenceError: Undefined variable: fee_policy". We have spent without problems from this wallet before. Please advise.

Please try and clear your browsers cache and reload the page. fee_policy is defined at line 32 in the latest version).

Quote from: 2weiX on September 05, 2012, 01:03:33 PM

because it's simple like that: you send coins, et voila....! that's it.

Yeah I know, but by putting it on the website blockchain is semi-endorsing it so it a least has to have some presence or accountability.