Pages:
Author

Topic: My thoughts about the blocksize thing - page 4. (Read 3565 times)

legendary
Activity: 2184
Merit: 1056
Affordable Physical Bitcoins - Denarium.com
February 21, 2013, 03:14:56 PM
#12
There are other ways to go around the fact that the blockchain becomes massive. Not everyone needs to have the whole blockchain of all Bitcoin existence. Why wouldn't the last 6 months be quite sufficient, for example, and maybe have the rest as SPV? Or something like that. We could have separate archive nodes that just store the whole thing.

It isn't needed that all full nodes store all transactions ever done. Only the ones done in recent history are critical.
sr. member
Activity: 310
Merit: 250
February 21, 2013, 03:11:21 PM
#11
I don't understand why some people want a hard limit to encourage fewer potential transactions. Fewer transactions equals higher fees per transactions and less useful technology (at least in the role of a payment network) which then equals a less valuable and used technology (in all other roles).

A raised max block limit that increases at a slower rate than corresponding increases in commodity hardware and bandwidth does not mean that the majority of people wishing to act as full nodes cannot do so. The original 1MB limit is completely arbitrary and should scale as all other resources scale. The only reason that 21,000,000 total coins is not considered a problem is because of divisibility. Blocks also need to be continually divisible for Bitcoin to be valuable. Taking that ability away is incredibly shortsighted.
sr. member
Activity: 310
Merit: 250
February 21, 2013, 02:56:20 PM
#10
i'll hop on the bandwagon too...more transactions per block means more fees for the miners

While you're hopping on the bandwagon you might to...actually read the posts in the Development & Technical Discussion forum regarding block size instead of merely regurgitating your view that "hard coded limits are bad." More transactions per block means less fees for miners. I'll leave it as an exercise for you to figure out why.


If this is true, and miners have the option currently of including fewer (or 0) transactions in their blocks, why do current blocks not have minimal numbers of transactions?

It seems to me that to maximize transaction revenue, a miner would want to include the max number of paying transactions that he could, and a higher number per block would equal higher fees.
sr. member
Activity: 430
Merit: 250
February 21, 2013, 01:22:47 PM
#9
Wich is exactly what i was thinking. But so far there is no real work done about that. If we want to speak about increasing the blocksize, then pruning must be considered too.
I absolutely agree.
legendary
Activity: 1064
Merit: 1001
February 21, 2013, 12:22:10 PM
#8
i'll hop on the bandwagon too...more transactions per block means more fees for the miners

While you're hopping on the bandwagon you might to...actually read the posts in the Development & Technical Discussion forum regarding block size instead of merely regurgitating your view that "hard coded limits are bad." More transactions per block means less fees for miners. I'll leave it as an exercise for you to figure out why.
legendary
Activity: 2940
Merit: 1090
February 21, 2013, 12:18:44 PM
#7
One of the other threads started out with exactly the concern that increasing the block size before all the pruning and so on are even being used just makes less incentive to actually do the damn pruning and so on and so on.

Until all those other things are in use, the space and bandwidth we already have/use is not being efficiently used so throwing good space after bad is just silly.

When the size we already have is being used in the most efficient way, which by the way involves bandwidth stuff as well as disk space utilisation stuff, we can look then at whether, given all those miracle cures that the moar size moar size moar size crowd point to as solutions to the problem of moar size but still have not actually put into place are in place, moar size is actually even needed.

I wonder what the average block size, not counting free transactions, is for the last difficulty-adjustment period?

-MarkM-
legendary
Activity: 1806
Merit: 1003
February 21, 2013, 12:17:13 PM
#6
For regular clients, we don't really have to store old transactions, who really care about a transaction happened 5 years ago? for those who care, you can have the option of storing the
full chain. For the rest of us, we'll just store recent transactions. So for example, on installation of the client, you can have the option of:

* store recent transactions
* store full chain

For those who want to look up a transaction 10 years ago, blockchain.info or blockexplorer.com etc... can provide that service by storing the full chain.
legendary
Activity: 1400
Merit: 1013
February 21, 2013, 12:10:26 PM
#5
But so far there is no real work done about that. If we want to speak about increasing the blocksize, then pruning must be considered too.
Depends on your definition of "work".
legendary
Activity: 1148
Merit: 1008
If you want to walk on water, get out of the boat
February 21, 2013, 11:55:33 AM
#4
Wich is exactly what i was thinking. But so far there is no real work done about that. If we want to speak about increasing the blocksize, then pruning must be considered too.
sr. member
Activity: 430
Merit: 250
February 21, 2013, 11:47:28 AM
#3
Also don't forget that the majority of the blockchain can be pruned when it becomes too large.
sr. member
Activity: 381
Merit: 255
February 21, 2013, 11:43:49 AM
#2
Thing is new tech can solve this and we wont need to have the same debate: http://www.thinlinedata.com/dna-storage-harddrives/

But then again, Bitcoin is ahead of its time, unless some synthetic biologist moves his ***  Grin
legendary
Activity: 1148
Merit: 1008
If you want to walk on water, get out of the boat
February 21, 2013, 11:33:45 AM
#1
Since everyone and his dog is openin thread about that, i'll hop on the bandwagon too  Cheesy

But my doubt is another one, right now, with the 1MB limit, the blockchain at max can grow of like 55GB per year. If we have the necessity to increase the block size, this mean that every block is already 1MB and that in a year the blockchain will be like 60GB.
If we double the blocksize, it will be 110GB per year. In 4 years it will be like 440GB. With the current limit, 220GB, still a lot

I am not against increasing the blocksize, if we have lot of transactions, it must be done. Also more transactions per block means more fees for the miners, after all it is not expensive to make a 1mb or a 2mb block, but a 2mb block will have more transactions. Yes, the 1mb block would have less transactions but with higher fees but i think the 2mb block in total would have more fees.

And as i said, having a blockchain of 220 or 440gb is not a big difference, it is a huge chain anyway. The problem is that it is huge, even with the current limit. A bit too huge.
Pages:
Jump to: