Assuming an interval where no block is found, do we know how often the typical miner updates his block transaction list with new transactions from the mempool?
I found a reference which suggests that the default update time is 60 seconds, but I'm not sure what software the pools are using to generate their block transaction lists.
Welcome to the site!
It depends on the protocol being used.
Some protocols have the pool dictate how often the list of transactions is updated, and others have it defined by the mining client.
In Stratum, the pool sends the miner a new merkle branch when it sees a new block or when a certain amount of time has passed. By default, it updates the list of transactions every 60 seconds.
Of course, this is only a default; a pool operator can change this.
In getblocktemplate with longpoll, the pool sends new work on block change, or after 60 seconds. (For bitcoind, at least.)
// Wait to respond until either the best block changes, OR a minute has passed and there are more transactions
...
checktxtime = boost::get_system_time() + boost::posix_time::minutes(1);
In getblocktemplate without longpoll, the miner looks for new work every so often. 'Every so often' is miner-defined.
cgminer does it every 60 seconds:
static void gen_gbt_work(struct pool *pool, struct work *work)
...
if (now.tv_sec - pool->tv_lastwork.tv_sec > 60)
bfgminer is user-configurable, but defaults to 60 seconds:
--scan-time <arg> Upper bound on time spent scanning current work, in seconds (default: 60)
Changing work every after the network finds a new block and every 60 seconds is by far the most common way of doing things.
stratum protocol doesn't have a default interval to push new work Technically, the Stratum protocol doesn't define how often you push new work. In practice, everyone uses slush's implementation, and slush's implementation does it, by default, every 60 seconds.
Dec 7, 2014 at 1:11
