Topic: What are the thresholds for blockchain spam? (Read 2126 times)

Yeah, I am thinking I might just set it to when the system as a certain built up value, otherwise slow times will end up wasting more.

I am working on a script to build a nice big send many now as that seems to be the best way. It is going to produce some impressive transactions if the site becomes popular.

You might find as you grow that using SendMany will save you some fees. You might send every hour for example, sending 15 tx at a time for only about double the fee of sending one singly.

If the transaction has any output less than 0.01 it is considered suspiciously spamlike and will need to provide a fee, at least by most of the software out there (see also: https://en.bitcoin.it/wiki/Transaction_fees). It isn't just mining nodes you need to worry about, without meeting this anti-DOS rule most nodes won't even forward your transactions along.

The unmodified reference client will automatically add the small fees it believes are _required_ by the network due to the anti-dos rules, even if you have paytxfee set to zero.

I encourage you to maintain a balance, and if you have auto-payout only pay when the users hit some fairly large threshold on the order of 0.1 to 1.0.  By maintaining some balances and doing bulk operations you'll also increase your ability to use sendmany, which will reduce chain traffic and require less fees from you (less risk of looking spamlike).

A great number of users only run their clients intermittently and if they've been offline for a bit no transaction is going to be instant to their client from their perspective as they'll need to catch up.  They probably won't see it at all until it's mined, which may be an especially long time if your payments look spammy.   Payments within your system will always look instant to your users of course.

More importantly, you do your users a disservice by paying them tiny amounts frequently.  When they go to respend those coins they'll each add to the input data size of their spending transaction— and the user will end up paying more fees overall then if they'd just been paid in bigger chunks a little less frequently.

Cheers,

I am running coinsmack.com, which uses bitcoin micro-transactions to vote things up, and the person who posted the article that is voted up gets a percentage of all bitcoins sent to vote things up.

I am working on an automated payout system, and would like to make it fairly instant (the second you get bitcoins on your post, the post will send bitcoins to you).

These transactions could be as low as 0.001 bitcoins.

Now I would like to maximize payouts to users, so I would like to minimize how much I pay in fees. These transactions are very small, so they are very difficult to distinguish from block-chain spam (though there won't be many of them).

Can anyone spell out what the most common mining software uses as an algorithm to ignore transactions it deems as likely spam? What is the calculation of the fee required, and is it based on the number of bitcoins in the transaction?

For simplicity, assume that these are all relatively new coins.