How often does a typical miner refresh their candidate block?

How often does a typical miner refresh their candidate block?

I realize that this is a general question with no "correct" answer, as every miner can operate differently.

Having said that, I'd like to be able to display a list of transactions that would be considered a fair representation of the transactions in the memory pool that are poised to be mined.

So far I have been:

  • Using getblocktemplate to get the list of transactions.
  • Refreshing the list when a new block arrives, or at 1 minute intervals.

Using getblocktemplate seems logical, as I imagine the majority of miners would like to get the most amount possible in fees from their blocks.

I'm then guessing that miners would want to refresh their candidate block at certain intervals to check for higher-fee transactions in the mempool.

Is it likely that miners would be inclined to refresh their candidate blocks much more (or less) than every minute?

https://ift.tt/2QloBOy

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more