<p>Though bitcoind won't mine blocks with gen=0, while connected to peers it will still relay transactions and send historic blocks to peers, which is an important function in the network.</p>

<p>"Processing transactions" is a fairly generic term and is not a particularly useful term to use because it's not specific about what sort of processing is meant. It's better to talk about "relaying transactions" (not fee earning) and "mining" (which generally includes transactions in a block, and earns both transaction fees plus the block reward).</p>

<p>Using 'gen=1' can only CPU mine which, due to it's inefficiency, will:</p>

<ol>
<li>cost you a substantial amount extra on your power bill</li>
<li>reduce the life of your CPU</li>
<li>probably never manage to mine a single block within your lifetime</li>
</ol>

<p>I believe it's only the older versions of the standard client that are actually capable of CPU mining, because it's not really a sensible thing to do.</p>

<p>Look into GPU, or preferably, ASIC mining if you want to mine.</p>

CC BY-SA 3.0
2013-02-22T18:44:32.533Z
It seems like running a client in this configuration provides free bandwidth to the network for no (BTC) reward. Which is actually fine by me, but not obvious.
jwd
CC BY-SA 3.0
2013-02-23T03:06:02.953Z
@jwd, that's pretty much true. I've seen one debate about whether transaction relaying should earn fees, but generally people seem to accept it. I know the Bitcoin-QT client has a setting for the number of peers it's allowed to connect to, but I don't remember hearing about bandwidth throttling. Generally I think people who don't like the level of data usage just don't leave the client open.
Highly Irregular
CC BY-SA 3.0
2013-02-21T02:56:11.573Z
2013-02-21T02:56:11.573Z
Highly Irregular
<p>"gen" is by default 0 (off), so you should not really need to specify "gen=0" anywhere.</p>

<p>"gen" will generate bitcoins (mining), but you should only do this if you know what you are doing (you probably want to mine in a pool, and use proper tuned hardware/software).</p>

<p>And yes, you will only get transaction fees if you mine a block.</p>

CC BY-SA 3.0
2013-02-21T00:56:28.397Z
2013-02-21T00:56:28.397Z
Nicolai
<p>I have read that when running a simple standalone instance of 'bitcoind', you should generally use 'gen=0', since it's highly unlikely you'll ever mine a block on your own.</p>

<p>What I don't fully understand is how this relates to transaction procssing.</p>

<p>If I use 'gen=0', does that mean I have no hope of getting transaction fees, either?</p>

<p>In other words, with 'gen=0', is my client not really participating in processing transactions at all?</p>

<p>Is block mining (to generate new bitcoins) a somehow separate process from processing transactions?</p>

<transactions><miner-configuration>
The bitcoind 'gen=0' setting - implications?
jwd
# The bitcoind 'gen=0' setting - implications?

(Asked by: username_0 on 2013-02-21)

I have read that when running a simple standalone instance of 'bitcoind', you should generally use 'gen=0', since it's username_1 unlikely you'll ever mine a block on your own.

What I don't fully understand is how this relates to transaction procssing.

If I use 'gen=0', does that mean I have no hope of getting transaction fees, either?

In other words, with 'gen=0', is my client not really participating in processing transactions at all?

Is block mining (to generate new bitcoins) a somehow separate process from processing transactions?

**Tags:** transactions, miner-configuration


---

## 2 answers

### Answer by username_2 on 2013-02-21. Score: 5 | Accepted answer

"gen" is by default 0 (off), so you should not really need to specify "gen=0" anywhere.

"gen" will generate bitcoins (mining), but you should only do this if you know what you are doing (you probably want to mine in a pool, and use proper tuned hardware/software).

And yes, you will only get transaction fees if you mine a block.


---

### Answer by username_1 on 2013-02-21. Score: 3

Though bitcoind won't mine blocks with gen=0, while connected to peers it will still relay transactions and send historic blocks to peers, which is an important function in the network.

"Processing transactions" is a fairly generic term and is not a particularly useful term to use because it's not specific about what sort of processing is meant. It's better to talk about "relaying transactions" (not fee earning) and "mining" (which generally includes transactions in a block, and earns both transaction fees plus the block reward).

Using 'gen=1' can only CPU mine which, due to it's inefficiency, will:

1. cost you a substantial amount extra on your power bill
2. reduce the life of your CPU
3. probably never manage to mine a single block within your lifetime

I believe it's only the older versions of the standard client that are actually capable of CPU mining, because it's not really a sensible thing to do.

Look into GPU, or preferably, ASIC mining if you want to mine.

> **Comments:**
> **username_0**: It seems like running a client in this configuration provides free bandwidth to the network for no (BTC) reward. Which is actually fine by me, but not obvious.  
> **username_1**: @username_0, that's pretty much true. I've seen one debate about whether transaction relaying should earn fees, but generally people seem to accept it. I know the Bitcoin-QT client has a setting for the number of peers it's allowed to connect to, but I don't remember hearing about bandwidth throttling. Generally I think people who don't like the level of data usage just don't leave the client open.  

---

