<blockquote>
  <p>If so, what would be the max amount that a mining client can increment the ntime value?</p>
</blockquote>

<p><code>bitcoind</code> will accept a block and push it out to the network as long as it is valid. Because of that, it's incredibly lenient. Quoting from bitcoin wiki:</p>

<blockquote>
  <p>A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours</p>
</blockquote>

<p>It almost never matters. Because <code>bitcoind</code> is a single-user mining program, it's almost always on the same computer as the mining agent. If the mining agent needs to get more work units, it doesn't use up extra bandwidth.</p>

CC BY-SA 3.0
2013-06-29T12:35:21.763Z
Except mining via `getwork` doesn't submit a full block, only the header. Bitcoind still combines it with the transaction data in remembered when creating the work. I'm not sure if this works if you modify the timestamp yourself.
Pieter Wuille
CC BY-SA 3.0
2013-06-29T15:36:39.953Z
`I'm not sure if this works if you modify the timestamp` But what else would "Supported, but not adverstised." mean?
Nick ODell
CC BY-SA 3.0
2013-06-29T18:14:46.343Z
Where do you read that?
Pieter Wuille
CC BY-SA 3.0
2013-06-30T04:16:36.470Z
@PieterWuille Look at the bitcoin wiki page, and scroll down to the row that says "rollntime". Click the footnote.
Nick ODell
CC BY-SA 3.0
2013-05-30T06:23:08.667Z
2013-05-30T06:23:08.667Z
Nick ODell
<p>According to this page: <a href="https://en.bitcoin.it/wiki/Poolservers" rel="noreferrer">https://en.bitcoin.it/wiki/Poolservers</a> bitcoind's rollntime support is 'Supported, but not advertised'.  I am taking that to mean that it doesn't provide the X-Roll-NTime header that would advertise this support, but you can increment the ntime value to get extra nonce space and still submit found blocks after doing this.</p>

<p>Is this correct?  If so, what would be the max amount that a mining client can increment the ntime value?</p>

<bitcoind><getwork>
bitcoind and rollntime support
Burton Samograd
# bitcoind and rollntime support

(Asked by: username_0 on 2013-05-30)

According to this page: <https://en.bitcoin.it/wiki/Poolservers> bitcoind's rollntime support is 'Supported, but not advertised'. I am taking that to mean that it doesn't provide the X-Roll-NTime header that would advertise this support, but you can increment the ntime value to get extra nonce space and still submit found blocks after doing this.

Is this correct? If so, what would be the max amount that a mining client can increment the ntime value?

**Tags:** bitcoind, getwork


---

## 1 answers

### Answer by username_1 on 2013-05-30. Score: 1

> If so, what would be the max amount that a mining client can increment the ntime value?

`bitcoind` will accept a block and push it out to the network as long as it is valid. Because of that, it's incredibly lenient. Quoting from bitcoin wiki:

> A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours

It almost never matters. Because `bitcoind` is a single-user mining program, it's almost always on the same computer as the mining agent. If the mining agent needs to get more work units, it doesn't use up extra bandwidth.

> **Comments:**
> **username_2**: Except mining via `getwork` doesn't submit a full block, only the header. Bitcoind still combines it with the transaction data in remembered when creating the work. I'm not sure if this works if you modify the timestamp yourself.  
> **username_1**: `I'm not sure if this works if you modify the timestamp` But what else would "Supported, but not adverstised." mean?  
> **username_2**: Where do you read that?  
> **username_1**: @username_2 Look at the bitcoin wiki page, and scroll down to the row that says "rollntime". Click the footnote.  

---

