August 5

A transaction can be written that requires two signatures to spend it next. You write a payment that requires the signature of both the recipient and the sender to spend it. To release the escrow, you give the recipie…

It's not implemented. It turned out nobody liked that mode of transfer anyway, so it hasn't had much development attention.

Quote from: bytemaster on August 05, 2010, 04:46:52 PM Right now the transaction fee address is left "blank" and the block generator fills it out. Now you would fill it in with the address of the person you are asking…

Quote from: bytemaster on August 05, 2010, 03:39:19 PM The only solution to this problem is to make broadcasting of a transaction "non free". Namely, if you want me to include it you have to pay me. The net (no pun in…

Quote from: bytemaster Payments would generally be advanced, say 1 BTC at a time and when the connection closes any "change" would be returned. This rule makes it impossible to pay for a simple "search query" with no…

Forgot to add the good part about micropayments. While I don't think Bitcoin is practical for smaller micropayments right now, it will eventually be as storage and bandwidth costs continue to fall. If Bitcoin catches…

I can't think of a way to implement that. All the transaction fees would be additional transactions. What about the transaction fees for the transaction fee's transaction?

Silently failing would look bad. Quote from: gavinandresen on August 04, 2010, 08:40:55 PM 1. Rate limit based on the first byte of the IP address (79. or 81. in this case). Definitely needed. What rate are you thinki…