Are you looking at every output or only outputs that are 0 BTC then seeing if they have a Message: prefix?
Yes scans for the prefix "Message:" and checks the first chunk of the script is ASCII.
Actually, message doesn't appear to have worked from "custom" page. Is it the usual "clear cache" routine?
Looks like a bug with the encode function. Should be fixed now.
Can't send BTC, getting the following error:
ReferenceError: fee_policy is not defined.
Using the custom send mode.
Please clear your browsers cache and see if that helps. (Any problems with the interface the first port of call should always be to clear the cache).
Wouldn't it be possible to use the destination address to encrypt the message such that only the receiver with the private key could actually read it? I thought there was a method for recreating the public key from the address and that should be enough to encrypt to the private key. I could see a private message being very useful in many cases such as tagging payments with invoice # or order details. Or for political donations for id info.
Yes this should be possible. I think the public key can only be can only be found using an input script so the address receiving the message would have to used at least once. Decryption might be difficult as well with lack of client support.
Damn, didn't notice that. Should be a while before miners upgrade.
Is there a way with the blockchain.info wallet to separate wallets? For example, I'd like to have a spending wallet, but also multiple savings wallets, like retirement, health, vacation, bicycle savings wallets. And then I can choose which wallet to spend from. Know what I mean?
Unfortunately not without using multiple accounts. As others suggest a desktop client can always be used for savings.
BTCDice.com addedI'm down already. QQ.