Quote from: Biodom on February 23, 2016, 11:10:35 PM

Quote from: philipma1957 on February 23, 2016, 07:01:54 PM

Quote from: cryptichermit on February 23, 2016, 06:08:48 PM

Quote from: philipma1957 on February 23, 2016, 05:30:24 PM

https://blockchain.info/tx/df60741e004f63c13d07eb422f89b3fbc1a2b270cccd35c05d0daeb35af5f20f

now 10 blocks have skipped the .0013 fee transaction due to it having 52 small parts of coin and 3 big parts.
thus 55 parts of coin which takes up space so it gets skipped.

even though the fee is .0013 I got skipped here for this block.

These funds were sent to me and there are 3 big parts in the send about 7.5 and 52 small parts around 0.05

This is tough as small payments take up space and the large fee of .0013 is not big enough.

55 pennies is large fee to send $4,400 ?
Last week I spent $46.00 to wire $1,700 at the bank.
Sticking to .0001 per kb should still assure relatively fast acceptance.

First off I understand the fee mechanism, but many don't..

Many people think 0.0001 or 0.0002 just works.

From your post I am inclined to think you realize BTC size means nothing kb size means everything.

So a 1 btc send consisting of 75 x 0.02 is expensive to send. 0.0013 is too small
While a 25.2 btc send consisting of a confirmed virgin block is cheap to send. 0.0004 will do the trick almost everytime

The problem is a lot of people don't understand this.
Most people do not understand that btc amount means nothing.
Here is one of my kano.is payment addresses:

it has .20453225 in it

https://blockchain.info/address/16yLHLoeyuCLPMXkVpC3gyrRYvwRGwjKJr

that is from 1 avalon6 and is the last 20 rewards from kano.is pool

to empty this and send to someone will cost 0.0004 to 0.0006 due to the fact it is 20 payments or so.

.204 is under 90 bucks and this is why I would like 1 payment a day since it would be 6 payments not 20 plus and sending the coins out would be

0.0002 or 0.0003 tops.

I think the rec I have seen was to check how many bits are in your transaction, then multiply by 20 sat.
So, for 700bits, 700X20=14000 sat or 0.00014 btc
So far it worked for me. If need comes, i will bump it to 30sat/bit, but I haven't done any transactions in a week or two.

At this risk of continuing this off topic discussion, doesn't your wallet software automatically compute a reasonable fee for size of the transaction? I remember the first time I bought something with mined coins and was shocked by the fee. Then I realized how huge the transaction was due to tons of tiny inputs, after which it made sense.

I've only used Bitcoin-Qt and a Trezor for receiving mined income. Both of them seem to do a decent job of computing reasonable fees when spending. Never seen a stuck transaction. Maybe other wallets don't automatically do as good a job, or maybe people think they know what they're doing and they override the wallet and low ball the fee?

Note that in the Trezor's case I periodically transfer from my mining account to my main one so that I can consolidate my bazillion tiny inputs. One drawback of the Trezor is that its signing is slow, so big transactions can take a long time to sign (many minutes sometimes). By consolidating I can pick when I want to spend that time.