Topic: Gold collapsing. Bitcoin UP. - page 43. (Read 2032266 times)

See this is exactly what I'm talking about. Pretending you can predict future transaction demand and set an arbitrary limit "much greater". Sounds like something out of the FED.

To then go back to our previous argument, let's pretend that your 8 MBs blocks get filled a year before your scheduled doubling then what happens?

I guess my point is that modeling transactional demand based on historical growth is a surefire way to shoot yourself in the foot.

That seems like a strange way of wording what I already said: "As long as the limit is far above the transaction demand (much greater than Q* in the figure), then the supply is constrained economically rather than algorithmically."

That is all true only if Q* stays within the range of your assumptions.

In classical economics, one defines a "supply curve" where the unit cost of the commodity (block space) is a monotonically increasing function of the quantity produced.  If demand grows, producers increase production to meet it (at an increased price).  This is how the free market works.



Your comment that "blocksize limit = supply" is false except in the case where the supply is constrained by the protocol rather than by economics (this continues the debate we had earlier).  As long as the limit is far above the transaction demand (much greater than Q* in the figure), then the supply is constrained economically rather than algorithmically.  The limit thus serves as only an anti-spam measure--that is, it continues to serve the original purpose it was designed for.  

Blocksize limit = supply.

Unless you advocate lifting it completely most block increase suggestions amounts to a control of supply based on projected demand.

(of course 1MB is an equally arbitrary quota but that is beside the point I was making)

So would this still require a further hard fork 'if and when needed' to remove the 32MB limit?

Presumably the whole industry would be more comfortable with block size changes at that point. so it would hopefully  be less controversial.

Man, I'm so tired of the block size debate.

really? I must have missed something along the way, couldyou  please share pointers to evidence on which the bolded claim is based? (serious question)

There is no doubling schedule or initial ramp in BIP100. It just gives the miners the vote on any block size they like, but their consensus can't go further than double or halve the limit at any one time. So they might mostly go for a size like 1450000 then 2100000 then 1790000 depending on their capacity to handle larger blocks or the amount of fee-paying tx which are consistently in mempools.
The BV800000 is just an example but some miners are using this as a signal that they like BIP100, or that they want *something* over 1MB
The 90% is a one-off to get the process going. After that the limit chosen might be a number that has 30% support, but it is the floor of the set of votes with the extremes removed.

so miners only vote once by signalling the next block size doubling into the Coinbase?  the progression has to be 1 to 2 to 4 to 8 to 16MB, correct?  if so, the example given above is just for illustrative purposes only as to the encoding, and not an initial ramp from 1MB to 8MB?

it's also true that these doublings can take place at any time interval as long as 90% consensus is achieved, correct?

Jeff is saying that miner voting via BIP100 will be submitted (merged in the BIP library?) implemented (pull request?) within two weeks.

This is great news. I see it as compatible with BIP 101 if a mined block size conforms to the least of the prevailing maximum of 100 and 101.

http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf

Protocol changes proposed:
1. Hard fork, to
2. Remove static 1MB block size limit.
3. Simultaneously,​addanewfloatingblocksizelimit,setto1MB.
4. The historical 32MB limit remains.
5. Schedule the hard fork on testnet for September 1, 2015.
6. Schedule the hard fork on bitcoin main chain for January 11, 2016.
7. Changing the 1MB limit is accomplished in a manner similar to BIP 34, a one­way lock­in
upgrade with a 12,000 block (3 month) threshold by 90% of the blocks.
8. Limit increase or decrease may not exceed 2x in any one step.
9. Miners vote by encoding ‘BV’+BlockSizeRequestValue into coinbase scriptSig, e.g.
“/BV8000000/” to vote for 8M. Votes are evaluated by dropping bottom 20% and top 20%, and then the most common floor (minimum) is chosen.

edit: point 7 with 90% would IMHO be improved with 75% + 2 week grace period.

Jeff is saying that miner voting via BIP100 will be submitted (merged in the BIP library?) implemented (pull request?) within two weeks.

This is great news. I see it as compatible with BIP 101 if a mined block size conforms to the least of the prevailing maximum of 100 and 101.

http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf

Protocol changes proposed:
1. Hard fork, to
2. Remove static 1MB block size limit.
3. Simultaneously,​addanewfloatingblocksizelimit,setto1MB.
4. The historical 32MB limit remains.
5. Schedule the hard fork on testnet for September 1, 2015.
6. Schedule the hard fork on bitcoin main chain for January 11, 2016.
7. Changing the 1MB limit is accomplished in a manner similar to BIP 34, a one­way lock­in
upgrade with a 12,000 block (3 month) threshold by 90% of the blocks.
8. Limit increase or decrease may not exceed 2x in any one step.
9. Miners vote by encoding ‘BV’+BlockSizeRequestValue into coinbase scriptSig, e.g.
“/BV8000000/” to vote for 8M. Votes are evaluated by dropping bottom 20% and top 20%, and then the most common floor (minimum) is chosen.

I'm saying that the pretense that 1 MBers are playing central bankers seems funny in the light considering most block increase proponents are the ones arguing for arbitrary control of supply.

You must not understand what proof means.

The problem with your statement is that you've expressed it in terms of an unsolvable problem, which is begging the question.

Processing 24 GB of data in a 10 minute period is possible with technology that exists today. It does not require faster-than-light communication, or violating mass/energy conservation, or solving the halting problem, or anything else that's actually impossible.

Perhaps what you actually mean is that handing a 24 GB every 10 minutes would be expensive using existing technology. Perhaps even so expensive as to cost more than Bitcoin users would be willing to pay.

Expressed in those terms, you have a statement that can actually be rationally evaluated.

You'd need to establish how much it would cost to pay for the hardware and operating expenses to operate a 24 GB/10 minute network, and then estimate how much the users would be willing to pay per-transaction. If the estimated costs exceed the estimated budged, then you'd be correct to say that the network would probably be too expensive to operate.

Of course, once you've phrased the problem in a manner that allows for potential solutions, then it becomes possible to talk about productive things like, "what steps could we take to reduce the cost of operating the network?"

On the other hand, if you phrased your "obvious truth" in a form of an unsolvable problem deliberately because you have a preference for the problem remaining unsolved, then keep doing what you're doing.

...
you do know that real ppl actually hurt themselves from severe myopia?  i can fix that for you.

I'm not interested in reading your usual drivel.

What has happened since that confirmed your assumptions & previous conjectures?

Seems to me you are still very much coming up with your own delusions of what Blockstream "are trying to do" without any valid information to support your position.

Are you gonna hold the fact that they are cautious about block size increase against everything they try to do? Again, I'm gonna need some more convincing that you are actually an adult person.

sometimes little dogs just like to bark: