<p>Take a look at the Bitcoin wiki page on <a href="https://en.bitcoin.it/wiki/Transaction_fees" rel="nofollow">Transaction Fees</a>.</p>

<p>First of all, a transaction fee is not always required. Miners decide whether to accept transactions without a fee and most miners follow the same decision protocol for that.</p>

<blockquote>
  <p>A transaction may be safely sent without fees if these conditions are met:</p>
  
  <ul>
  <li>It is smaller than 10,000 bytes.</li>
  <li>All outputs are 0.01 BTC or larger.</li>
  <li>Its priority is large enough (see the Technical Info section below)</li>
  </ul>
</blockquote>

<p>The priority basically adds the notion of age. Outputs that are created some time ago can mostly be sent for free. Very young outputs cannot be spent free. This is to prevent someone from spamming the blockchain with consecutive transactions.</p>

<blockquote>
  <p>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).</p>
</blockquote>

<p>So this basically means that the fee increases as the transaction size increases. Considering this, it is not a good solution to add thousands of inputs and outputs to a transaction.</p>

<p>I believe the best solution for a service like a market is to try to make as much as possible free transactions. A typical single-input-single-output transaction is 500 bytes. When you always use the oldest outputs available in your hot wallet pool, you can try to always create 10KB transactions that are free.</p>

CC BY-SA 3.0
2013-12-03T22:36:35.407Z
2013-12-03T22:36:35.407Z
Steven Roose
<p>For example, on the late SilkRoad market, or in bitcoin mixing services.
They supposedly have a "pool" account (or escrow acct, etc) where all the coins go in to, and from which withdrawals are made.</p>

<p>Wouldn't such a setup be a nightmare regarding how large the transaction fees would be during a withdrawal, due to the large amount of input addresses? At least, from what I understand from fee calculation (honestly, a lot of bitcoin concepts go over my head, no matter how much I reread related articles).</p>

CC BY-SA 3.0
2013-12-03T12:54:13.123Z
If I understood the question correctly: a mixer service or any shared web wallet can bundle several outgoing bitcion transfers to one single transaction with a single transaction fee payment. This is because bitcoin transactions do not need to be 1 input address -> 1 output address, but they can combine any number of inputs and outputs.
Mikko Ohtamaa
CC BY-SA 3.0
2013-12-03T16:08:50.897Z
Although theoretically the more they stuff into a transaction, the larger it gets in bytes and therefore the fee increases.
Neil Neyman
CC BY-SA 3.0
2013-12-03T16:09:19.837Z
@mikko why not make that an answer?
Neil Neyman
CC BY-SA 3.0
2013-12-03T18:22:56.347Z
My bitcoin-fu is still weak, but let's try and let others fix it if I am wrong.
Mikko Ohtamaa
<transaction-fees><escrow><mixing>
How do big sites/markets handle the intrinsic "transaction fees"?
blurp
# How do big sites/markets handle the intrinsic "transaction fees"?

(Asked by: username_0 on 2013-12-03)

For example, on the late SilkRoad market, or in bitcoin mixing services.
They supposedly have a "pool" account (or escrow acct, etc) where all the coins go in to, and from which withdrawals are made.

Wouldn't such a setup be a nightmare regarding how large the transaction fees would be during a withdrawal, due to the large amount of input addresses? At least, from what I understand from fee calculation (honestly, a lot of bitcoin concepts go over my head, no matter how much I reread related articles).

**Tags:** transaction-fees, escrow, mixing

> **Comments:**
> **username_1**: If I understood the question correctly: a mixer service or any shared web wallet can bundle several outgoing bitcion transfers to one single transaction with a single transaction fee payment. This is because bitcoin transactions do not need to be 1 input address -> 1 output address, but they can combine any number of inputs and outputs.  
> **username_2**: Although theoretically the more they stuff into a transaction, the larger it gets in bytes and therefore the fee increases.  
> **username_2**: @username_1 why not make that an answer?  
> **username_1**: My bitcoin-fu is still weak, but let's try and let others fix it if I am wrong.  

---

## 1 answers

### Answer by username_3 on 2013-12-03. Score: 2

Take a look at the Bitcoin wiki page on [Transaction Fees](https://en.bitcoin.it/wiki/Transaction_fees).

First of all, a transaction fee is not always required. Miners decide whether to accept transactions without a fee and most miners follow the same decision protocol for that.

> A transaction may be safely sent without fees if these conditions are met:
>
> * It is smaller than 10,000 bytes.
> * All outputs are 0.01 BTC or larger.
> * Its priority is large enough (see the Technical Info section below)

The priority basically adds the notion of age. Outputs that are created some time ago can mostly be sent for free. Very young outputs cannot be spent free. This is to prevent someone from spamming the blockchain with consecutive transactions.

> 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).

So this basically means that the fee increases as the transaction size increases. Considering this, it is not a good solution to add thousands of inputs and outputs to a transaction.

I believe the best solution for a service like a market is to try to make as much as possible free transactions. A typical single-input-single-output transaction is 500 bytes. When you always use the oldest outputs available in your hot wallet pool, you can try to always create 10KB transactions that are free.


---

