It is smaller than 10 thousand bytes. All outputs are 0.01 BTC or larger. Its priority is large enough

Otherwise, the reference implementation will round up the transaction size to the nearest thousand bytes and then add a fee of 0.0005 BTC per thousand bytes. Users may override the default 0.0005 BTC/kb fee setting, but cannot control transaction fees for each transaction. Bitcoin-Qt does prompt the user to accept the fee before the transaction is sent (they may cancel the transaction if they are not willing to pay the fee).

It is smaller than 10 thousand bytes. All outputs are 0.01 BTC or larger. Its priority is large enough

Otherwise, the reference implementation will round up the transaction size to the nearest thousand bytes and then add a fee of 0.0005 BTC per thousand bytes. Users may override the default 0.0005 BTC/kb fee setting, but cannot control transaction fees for each transaction. Bitcoin-Qt does prompt the user to accept the fee before the transaction is sent (they may cancel the transaction if they are not willing to pay the fee).

Some mining pools require fees to process transactions, and will not publish a no-fee transaction under any circumstance. Others will process transactions even without fee so long as there is space available in the block. I know that BitMinter used to process no-fee transactions, and I think they still do. So you might have to wait for them (or an equally nice pool) to publish a block

Some mining pools require fees to process transactions, and will not publish a no-fee transaction under any circumstance. Others will process transactions even without fee so long as there is space available in the block. I know that BitMinter used to process no-fee transactions, and I think they still do. So you might have to wait for them (or an equally nice pool) to publish a block