Title: Micropayments and antiflooding questions Post by: xuxu on November 17, 2014, 02:21:30 AM "If you want to send small amounts of bitcoin around, your best bet is to use something like Coinbase or Changetip." Reference: https://bitcoinj.github.io/working-with-micropayments From the above page, there is a statement which makes me wonder how services like Changetip are all able to exists: "If you send too many transactions too fast, they will get down-prioritised or not relayed by various anti flooding algorithms built into the Bitcoin network." Q6. Is the "you" in this statement a single wallet instead of an IP where the service may be running? I hope this isn't too much to ask! Title: Re: Micropayments and antiflooding questions Post by: xuxu on November 17, 2014, 02:43:41 AM Someone from the IRC channel responded to a few of these questions:
Q1. It can be an infinite amount of satoshis. Q2. I had a fundamental misunderstanding of what a micropayment was: "A micropayment channel allows you to "increment" the amount you have paid them until they redeem it and pay a fee." Yes it could be used for tipping, ideal though is the wrong wording. Q4. Coinbase and others keep their transactions offchain until they are ready to broadcast. Q5. This question, too, shows a misunderstanding of micropayments. Still requesting an answer to Q6. Title: Re: Micropayments and antiflooding questions Post by: readerbtc on November 17, 2014, 12:34:05 PM "If you send too many transactions too fast, they will get down-prioritised or not relayed by various anti flooding algorithms built into the Bitcoin network." Q6. Is the "you" in this statement a single wallet instead of an IP where the service may be running? I don't know in detail what exactly anti-spam algorithms are there, but if we are talking about the P2P network, it must be based on IP address or similar identification of your node. I also don't know in detail how services like Coinbase work, but I understood the customers send their transactions to the network, not the merchant, and each customer has his/her IP. I also can point it's not possible to do anti-flooding or anti-spam "on a single wallet" if the wallet creates a new public address for each transaction, like is recommended. |