Bitcoin Forum
May 11, 2024, 11:12:28 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: Effects of Forcing Miners to Fill Full Blocks on: February 05, 2020, 11:37:16 AM
I think it isd a bad idea. If implemented, miners would just create big wasteful messages to fill the block.

But still they would have to create transactions for that because they can't insert garbage bits in transactions. Even if they do so by using OP_RETURN opcode, those are not spendable transactions. So they are anyway doing something fruitful to system (Creating more transactions).
2  Bitcoin / Development & Technical Discussion / Re: Effects of Forcing Miners to Fill Full Blocks on: February 05, 2020, 11:30:12 AM
I was wondering if Miners are forced to fill full blocks or almost full block (according current block limit of 1MB) in bitcoin network (assuming that they all are honest enough to do so), what will be its effect on bitcoin network and transaction throughput? Which aspects I am missing on, that this change would be affecting? Even if miners are honest enough to do so, will it affect their profit? (In case of segwit, we can assume we are running older nodes.) Any comments will be helpful..

"forced" doesn't seem like a good word.  What if there isn't 1MB worth of transactions to put in a block?  The community more/less tries to hold pools responsible that don't make an effort to fill blocks when they are able as it is.  Any outstanding backlog in the mempool would certainly put more pressure on pools to fill blocks.

Mempool data at https://www.blockchain.com/en/charts/mempool-size?timespan=24h says, sometimes waiting transactions size even reaches upto 14MBs during day time. Provided every node has their own mempool, I think this data only depicts the transactions that are in mempool of connected peers. And on the other hand there is so much concern about increasing blocksize in community, that shows there are enough transactions waiting in the mempool every time a new block is created. And this "forced" thing might lead miners to be connected to more peers for receiving mempool transactions, in turn increase in block syncing speed as well. What do you say?
3  Bitcoin / Development & Technical Discussion / Effects of Forcing Miners to Fill Full Blocks on: February 05, 2020, 09:57:35 AM
I was wondering if Miners are forced to fill full blocks or almost full block (according current block limit of 1MB) in bitcoin network (assuming that they all are honest enough to do so), what will be its effect on bitcoin network and transaction throughput? Which aspects I am missing on, that this change would be affecting? Even if miners are honest enough to do so, will it affect their profit? (In case of segwit, we can assume we are running older nodes.) Any comments will be helpful..
4  Bitcoin / Bitcoin Discussion / How to prove improvement in transaction throughput on: February 05, 2020, 09:17:00 AM
I am working on a research in bitcoin blockchain where I am making some hypothetical changes in policies of bitcoin blockchain. Due to this, it helps to increase the transaction throughput of bitcoin blockchain (or at least a thing I want to claim through my research). Or one can think of this research as an identical PoW blockchain to bitcoin, with some changes in its policies and structure. I am already working on a simulator called btcd - https://github.com/btcsuite/btcd. It is a full node implementation of bitcoin blockchain or what I understand of it. I was wondering how can I prove using btcd that transaction throughput have been increased through new policies. Other possible simulator names with suitable abstraction level will also be helpful. If we think of a scenario where it is absolutely necessary for miners to fill the blocks at its fullest (Apparently,  It will improve transaction throughput.), can this improvement be proved using any mathematical aspect?
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!