So, the basic escrow works by two people working through a third party to exchange (usually money) for some other form of goods or services. In a transaction where both people are honest, the escrow business can essentially be automatic since the buyer gets his goods and approves release of […]
Read moreRe: Flood attack 0.00000001 BC
Quote from: bytemaster on August 05, 2010, 16:46:52 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 to build the block. If you’re only going to have one […]
Read moreRe: Transaction Overload Solution
In another thread I posted the comment below, but I felt that it was an important enough flaw that it should be addressed asap before bitcoin is overrun with huge numbers of automated non-micro payments. The real issue is that even a simple legitimate automated payment negotiation system could overload […]
Read moreRe: bitcoind transaction to ip address
I cant figure out how to send a transaction to an ip address from bitcoind command line interface. Has the function been implemented yet? (linux 64 if it matters) It’s not implemented. It turned out nobody liked that mode of transfer anyway, so it hasn’t had much development attention. Related […]
Read moreRe: Who’s the Spanish jerk draining the Faucet?
I just shut down freebitcoins.appspot.com; it looks like somebody in Spain is being a jerk and getting a new IP address, bitcoin address, and solving the captcha. Over and over and over again: Code: 79.154.133.217 – – [04/Aug/2010:12:46:55 -0700] “POST / HTTP/1.1” 200 1294 “https://freebitcoins.appspot.com/” “Opera/9.80 (Windows NT 6.0; U; […]
Read moreRe: Flood attack 0.00000001 BC
Quote from: bytemaster on August 05, 2010, 15:39:19 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 intended) result is that each client would need to pay […]
Read moreRe: Flood attack 0.00000001 BC
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 further transactions. One alternative is to use a round-up system. You pay […]
Read moreRe: Flood attack 0.00000001 BC
Quote from: Insti on August 04, 2010, 14:58:31 It seems to do more harm than good because it prevents micropayment implementations such as the one bytemaster is suggesting. Bitcoin isn’t currently practical for very small micropayments. Not for things like pay per search or per page view without an aggregating […]
Read moreRe: Flood attack 0.00000001 BC
Quote from: Insti on August 04, 2010, 14:58:31 It seems to do more harm than good because it prevents micropayment implementations such as the one bytemaster is suggesting. Bitcoin isn’t currently practical for very small micropayments. Not for things like pay per search or per page view without an aggregating […]
Read moreRe: Building initial transaction trust through “coin ripping”
I’m certainly not a cryptographer by trade or anything so I’m not sure if this idea holds any water. As I browse the forums I am noticing that perhaps one of the bigger issues when transacting with BC is building reputation between the transacting parties. In particular, the very first […]
Read more