So why doesn't they simply chose transactions from it's size proportionated to it's fee? Sounds like the more sane approach.
I understood that. What i ask is why the miners doesn't include transactions based on the fee AND the size. I mean when they include a big transaction only because it has a bigger fee than others then they will lose either because they could have include many small transactions that in total could create more fees for him and because such a big block can be propagated through the nodes more slowly. They risk getting their block orphaned.
That was what i was wondering about.
Fees are per size in Bitcoin Core as follows:
A transaction may be safely sent without fees if these conditions are met:
- It is smaller than 1,000 bytes.
- All outputs are 0.01 BTC or larger.
- Its priority is large enough (see the Technical Info section below)
Otherwise, the reference implementation will round up the transaction size to the next thousand bytes and add a fee of 0.1 mBTC (0.0001 BTC) per thousand bytes. As an example, a fee of 0.1 mBTC (0.0001 BTC) would be added to a 746 byte transaction, and a fee of 0.2 mBTC (0.0002 BTC) would be added to a 1001 byte transaction. Users may increase the default 0.0001 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).
Note that a typical transaction is 500 bytes, so the typical transaction fee for low-priority transactions is 0.1 mBTC (0.0001 BTC), regardless of the number of bitcoins sent.
https://en.bitcoin.it/wiki/Transaction_fees
Yes, but that doesn't mean the miners are using the same model. It's only a minimum fee that a transaction has to meet in order to be able to be accepted by the miners.
But miners should care about fee per satoshi or millibit. And about the general size of the block, leading to faster or slower propagation. It might be that the spamtransactions would not be worth it then.