Bitcoin Forum
May 25, 2024, 10:53:01 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 ... 76 »
121  Economy / Scam Accusations / Re: Devianttwo is a Pedophile AKA Robert Christopher on: September 02, 2015, 11:52:39 PM
Filthy scumbag. Hope he gets tortured in prison and goes to hell and rots.

Really?  Just for:
  • 23 counts of Transmission of Pornography by Electronic Device or Equipment.
  • 23 counts of Possession of Child Pornography.

Did he scam you or something?

Edit: Transmission charges were dropped.
122  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: September 02, 2015, 11:05:08 PM
Another difference to bear in mind: block space is not treated as a fungible commodity the way oil, iron, gold, and copper are.  Many people are willing to pay more for a faster first confirmation.

I am not sure about this.  With no economic blocksize limit, every miner will include as many transactions in the block as possible.  The mempool will be empty and you will not need to outbid anyone to get a fast confirmation.

Honestly, I'm not sure either.  I'm applying the same elasticity of demand thinking you described above but to a single miner.

Imagine a world where basically all fees are <= 1 satoshi.  Suppose Alice is a miner with 5% of the network's total hashrate.  Alice could advertise that she will no longer be processing all transactions but only those that pay at least 10 satoshis.  Each bitcoin user now has the option of paying 9 extra satoshi to reduce the expected first transaction waiting time by about 30 seconds.  Supposing this extra utility is worth the 9 satoshi in enough cases, Alice would increase her revenue.

I also wonder about store of value.  The commodities you listed can all store value but I don't think this can be done with block space.  Supposing commodity super cycles are driven by speculation, what is the equivalent mechanic in Bitcoin?
123  Bitcoin / Bitcoin Discussion / Re: BIP1xx DynamicMaxBlockSize on: September 02, 2015, 12:26:42 PM
One idea: Is it possible to set up (or does there exist) a platform allowing people to bet on the state of technology 20 years from now?  If there were a lot of money in the pot predicting slower growth than BIP101 needs then you could make a strong case for a more conservative proposal.

Why not adjust to demand algorithmically at any given time? Trying to predict demand or supply of network resources, decades into the future, is not a sensible approach at all.

I'd very much prefer to determine an appropriate block size limit algorithmically.  Unfortunately, I cannot think of a way of doing this.  There do exist several dynamic limit proposals but none of them do the work of tracking technological progress.

If at any stage the blocksize is too much, the fee market is dead, and mining begins to looks unviable without an effective subsidy. Another blocksize change fork (+ debate)? Great.

Block subsidies are not necessary to make mining viable.  Even with no subsidy and no limits, transactions would be processed.  It is true that this situation could well lead to extremely low difficulty but this is a different matter.  It is far from clear that this calamity can only be solved by a blocksize limit or that such an approach would even work.

The real problem to an overestimation is that full nodes could well become progressively more expensive to maintain.  This would reduce the number of nodes (including mining nodes) and drive us towards centralisation.  This would require intervention and is a major strike against the proposal.  Fortunately, the growth rate of the BIP101 is rather conservative (not compared to other proposals, but compared with projections of technological growth).

If at any stage the blocksize is too little, the fee market could becomes so expensive that everyday transactions are priced out. Another blocksize change fork (+ debate)? Great.

If the blocksize limit is far below what humanity is capable of accommodating with a highly decentralised network then yes, we'd be in a situation similar to the one we have today (hopefully without the node crashing concerns).  This problem applies to all of the proposals.

I don't support any of the other static limits for the same broad reasons, it's just that under BIP101, "too big for viable mining" is eminently more likely than under any other proposal. It just cannot be portrayed as the "conservative" solution, it's radical, and in completely the wrong way.

It's not the conservative solution, it's a solution which follows a conservative estimate of future technological growth.
124  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: September 02, 2015, 09:06:04 AM
As a result, we see a global commodity super cycle, we see periods where prices fall and industry players fail, capacity then falls and the commodity prices increase again.  Producers then over invest in capacity and the cycle repeats.  This may be a reasonably healthy cycle.

You've lost me here.  You explained that prices were artificially high due to cartels.  However, you then say that a cycle is complete when "producers over invest".  How does over investment necessarily lead back to cartels?

However, Bitcoin mining is different in two respects, first we need a healthy and viable mining industry at all times and secondly, the above cycle cannot occur, because when transaction fees start to fall and miners begin to fail, this will not reduce capacity.  Any one miner can provide all the capacity we need.

Another difference to bear in mind: block space is not treated as a fungible commodity the way oil, iron, gold, and copper are.  Many people are willing to pay more for a faster first confirmation.
125  Bitcoin / Development & Technical Discussion / Re: Voting for block size increase proposals on: September 02, 2015, 03:24:46 AM
BIP101 - Increase to 8 MB on January 11, 2016, and double the limit every two years (Bitcoin XT)

Might I suggest:
BIP101 - Continuously raise the limit from 8MB on January 11, 2016 so that the limit is doubled every two years (Bitcoin XT).

"double the limit every two years" makes it sound like the limit will stay at 8MB for two years and then jump suddenly to 16MB.
126  Bitcoin / Bitcoin Discussion / Re: BIP1xx DynamicMaxBlockSize on: September 02, 2015, 03:13:56 AM
Ugly though it may seem, I currently believe the can-kicking BIP101 proposal is the best under consideration.

The reason why it seems ugly is because it involves kicking the metaphorical can into the upper atmosphere, not simply kicking it out of sight.

BIP101 is the most aggressive expansion schedule (well, except for the previous revision of BIP101 that advocated 20 MB + 2 yearly doublings). Not my definition of kicking the can, you need to be able to find the can when it's the right time to pick it up again....

Earlier in draft (before becoming a BIP) it was 20 MB + 50%/year (125% per two years).

I would happily support a similar proposal with different parameters if the parameters were well-justified and it grew to have more support than BIP101.

One idea: Is it possible to set up (or does there exist) a platform allowing people to bet on the state of technology 20 years from now?  If there were a lot of money in the pot predicting slower growth than BIP101 needs then you could make a strong case for a more conservative proposal.
127  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: September 01, 2015, 12:32:29 AM
The above describes why BIP100 so brilliant.  Miners consider the economic utility of the transactions, to the user, by considering the fee the user will pay.  BIP100 may restrict the volume to a lower level than could technically be achieved, however this is done in a balanced way reflecting the impact on the bitcoin price and the utility users would get from these extra transactions.

I don't think this takes into consideration competition.  Transactors will simply move more and more off chain, even to altcoins, if fees are kept relatively high by low block size limits.  Because of this, tx fees alone will not provide enough security for the network.

Miners are driven to maximise the purchasing power of their income, not simply their nominal bitcoin income.  If most miners felt that a larger block size would yield greater real value then I don't see why they wouldn't vote for it.

Or, as jonny1000 noted:
Remember more economic utility for users means the Bitcoin exchange rate may be higher, which would drive up mining revenue.  This would also be considered by miners when voting.
128  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: September 01, 2015, 12:25:26 AM
In this scenario, without the 2GB limit, blocks would not generally fill up.  This is not necessarily because no-one can think of any more uses for the space, but because the costs of relaying, processing, and storing any further transactions outweigh the benefits of using the space.  (I'll note that if this is true, we're probably operating under a different idea of "technical limitation").

This is not true no.  In my hypothetical scenario the costs of relaying, processing, and storing any further transactions are very low.  "Technically" the limit could be increased to 5TB and there would be no propagation or storage issues.  Because by 2035 my smart watch has a 5TB/s connection or whatever.  The 2GB limit is imposed by a miner vote under BIP100 to maximize mining revenue.

Ok, my misunderstanding.

Question: Why not remove both the 2GB limit and the 8GB limit?  With both limits gone, mankind will enjoy more transactions and lower fees.  Why should we prefer fewer transactions, higher fees, and a more complex protocol?

I think we may not need the 8GB limit in this scenario, but we still need the 2GB limit.  The 2GB is imposed by miners to ensure fees are higher enough.  Mankind will not get more utility from more transactions than 2GB per second.  

Extend Example
  • 2GB BIP100 block limit
  • All blocks are full
  • $0.01 average fee

Miners then vote under BIP100 to increase the limit to 8GB, the situation changes to the following:
  • 8GB BIP100 block limit
  • All blocks are full
  • $0.0001 average fee

Transaction volume is up, and users have more utility, but users are only prepared to pay $0.0001 per transaction, so the economic utility of these extra transactions for the users are low.  Mining revenue and therefore security has fallen by 25x.  This is why we prefer fewer transactions and lower fees despite the fact "technically" the network could handle more.  Under BIP100 it is up to the miners to decide.  Remember more economic utility for users means the Bitcoin exchange rate may be higher, which would drive up mining revenue.  This would also be considered by miners when voting.
(emphasis mine)

Nice clear example.  I agree.  A fee market may cause profit-seeking miners to increase network security.

That said, I don't find network security to be a particularly compelling reason for having a fee market.  There seems to be practically no connection between a miner's incentives regarding voting and true demand for network security.  I could easily imagine this method yielding far too little security or far too much.  I believe there are better solutions to the large-block low-fee tragedy of the commons problem.

If each of the variables:
  • The optimal level of network security;
  • The point of unit elasticity (where S * P is maximal);
  • The artificial limit derived by BIP100, driven by all of a miner's incentives;
  • The limit of what a well-decentralised network can supply,
happen to have a particular relationship with one another then I'm sure BIP100 will behave superbly (even in the long term and without limits).  It wouldn't surprise me to learn that there is some subtle robustness (mechanisms naturally drawing these quantities into a healthy relationship) given the technical brilliance of the people that helped created the proposal but it's also possible that BIP100 is built upon a certain amount of wishful thinking.  I've warmed to it slightly thanks to your efforts but I remain cautious.
129  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 09:04:43 PM
My intuition is the other way around.  I expect humanity will demonstrate an apparently insatiable appetite for blockspace, just as it has for storage and bandwidth.  I myself could use 50 GB of blockspace were the price low enough.

This is a good point and I kind of agree with you, although supporters of BIP101 seem to disagree with this.  BIP101 supportrs typically think blocks may not be full.  This is why I advocate a lower and upper bound in BIP100 for now.  My point is that what if there is a stable optimal economic limit under BIP100, based on miner expectations of demand curves, that is much lower than the limit when bandwidth and other constraints begin to come into play?  This could happen, as although there could be an "insatiable appetite for blockspace", users may not be willing to bid a high enough fee.  Therefore miners vote for a lower limit than the elastic demand not supported by strong fee bids.

Lets consider a hypothetical scenario in 2035:
Size limit based on BIP100 voting: 2GB
Upper bound in the protocol: 8GB
Technical limitations, based on broadband speed and storage costs, ect, in 2035: 5TB

If we experience the above scenario for many years, we may decide we no longer need the upper and lower bounds, as we have high confidence in the voting process and high confidence the optimal miner voting strategy will not bring the limit near what can safely technically be done.

Ok, let's see if I understand.

In this scenario, without the 2GB limit, blocks would not generally fill up.  This is not necessarily because no-one can think of any more uses for the space, but because the costs of relaying, processing, and storing any further transactions outweigh the benefits of using the space.  (I'll note that if this is true, we're probably operating under a different idea of "technical limitation").

With the 2GB limit in place, the total transaction volume is reduced but the total value of all transactions actually increases (following the S * P logic from earlier).

If this persisted for decades (as you suggest above 2 decades to 2035 + still more years of the same) I agree that it begins to look pretty safe to remove the 8GB limit.  In this case, I will have been practically proven wrong about my concerns.

Question: Why not remove both the 2GB limit and the 8GB limit?  With both limits gone, mankind will enjoy more transactions and lower fees.  Why should we prefer fewer transactions, higher fees, and a more complex protocol?
130  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 04:38:30 PM
What if the price elasticity of demand asks for a very high supply (i.e. Bitcoin takes off in a big way).  Will a miner vote for a block size limit that he himself does not have the resources to handle?

Yes, under BIP100 the blocksize limit could be very large if demand is large.  With respect to resources an upper bound could be in place for technical reasons.

Yes, this is roughly what I'm arguing.  Growth is great but if we run into a problem with real resources then we'll need some kind of upper bound (or else mining centralisation).  So long as real supply is much larger than the "ideal supply" being calculated by BIP100 then things should work just fine.

Many BIP101 proponents make comments like "In 20 years your watch will be able to download the whole blockchain in seconds".  I have no idea if this is correct, if it is then maybe the technical limitations may become insifgnificant in relation to the market driven blocksize under BIP100.  This is why I think the stabilizers (on both sides) could be removed in the future.

Wow, sounds pretty wild.

My intuition is the other way around.  I expect humanity will demonstrate an apparently insatiable appetite for blockspace, just as it has for storage and bandwidth.  I myself could use 50 GB of blockspace were the price low enough.

I could be wrong.  It might be that block space becomes so vast and cheap that human desire simply can't keep up.  Block space would be as plentiful as air.  In this world, BIP100 would work fine but I'd still question the point of it.  Why, for example, would we want to artificially restrict the atmosphere to create an air market?  All I can think of is that without a fee market, transaction fees would tend to the largest miner's transaction-processing costs and the network security afforded by the fees would tend to zero.
131  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 03:48:54 PM
The only valable argument I think of for BIP101 is about short term peak demand that BIP100 can't adapt for quickly. But this is an exceptional case.

BIP100 is likely to result in blocksize increases quite quickly at first, because when the block reward is high as there is little reason to vote for a lower limit, this should make it similar to BIP101 in the early years.

As time progresses and the block reward falls, if the network is fee driven it is likely to be able to handle short term demand variations much better, for various market driven reasons.  BIP100 can handle longer term variations.

For example if demand is high during peak shopping hours in the US, or at Christmas, the mining industry can allocate more power to mining and find blocks faster.  This is similar to how the national grid operates at the moment.  In the UK, when the national football team play an important match, at half time millions of national grid users make tea.  This causes a surge in power demand, however electricity producers predicted this in advance and respond by producing more energy.  Large amount of potential energy stored up in hydro facilities can be realized in one go, so the UK population can make their tea (http://news.bbc.co.uk/1/hi/uk/5059904.stm).  Bitcoin miners could also respond to demand surges and release large amounts of energy to increase their hash-power, temporarily producing faster blocks.

Exactly.  BIP100 can handle demand spikes as well as any other block size limit method (except arguably Meni's).  BIP101 has no principle advantage here.

If we do not allow a fee market to exist, amazing features like this may not occur.

While a fee-market focused limit might make reserve hashing power more commonplace, I fail to see why this in itself is a good thing.  Certainly, it is better to counter a surge with fast blocks than to not counter it at all.  Better still though would be to mitigate the surge by just having bigger blocks to begin with.  This way, people get their transactions confirmed even more quickly, and for a lower fee!

In a BIP101 universe, surges could be handled in the same way.
132  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 01:47:33 PM
The way I see it:
  • BIP100 measures demand
  • BIP101 speculates supply
I believe both have problems and that we'd ideally like something which measures supply.

We are talking about how miners should set supply, we do not need to measure supply to do this.  What we need to measure is the price elasticity of demand and then set supply accordingly.  BIP100 encourages miners to do this, at first they may be poor at doing so, but over time miners will improve.

What if the price elasticity of demand asks for a very high supply (i.e. Bitcoin takes off in a big way).  Will a miner vote for a block size limit that he himself does not have the resources to handle?

It seems like the BIP100 algorithm is trying to set a kind of "ideal supply" that would work well for the current demand.  What if we don't have enough resources to supply the "ideal supply"?

In the long run I don't think the upper bound can be safely removed without significantly changing the algorithm.

As demand increases, there will be pressure to increase the limit (to increase supply).  So long as miners can cope with the increased demand they have an incentive to vote to raise the limit for greater profits.  This is all well and good; we want these free-market efficiencies.

Miners may also have an incentive to vote for a lower limit, probably not in the first few years, but once the block reward is low they may vote to maximize revenue.  This would happen depending on what miners think about the price elasticity of demand.  Basically it depends on the demand curve, if reducing supply from S1 to S2 increases the price from P1 to P2, such that S1 * P1 < S2 * P2, miners should vote for a lower limit.

I agree (and this is a cool corollary of BIP100).  But notice that miner's are voting for lower block limits because demand is low.  What happens when these entrepreneurial miners correctly estimate that S * P is maximised at a point where S is very large?
133  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 06:46:49 AM
Lots of crosstalk then in this discussion, but I'd be very happy if bitcoin became so popular that we had 1GB of transactions regularly... Not sure where we'd find 1TB of transactions in a year let alone every 10 minutes, real or spammed.

Yeah, I feel I could have been clearer.  Sorry if I mislead anyone.

I can't imagine demand for 1TBs worth of block space every 10 minutes but I believe that if we had the resources to provide this at very low prices that people will find a use for the space.
134  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 06:32:51 AM
1MB blocks may be trivial, but 1GB blocks wouldn't be, and 1TB blocks would be out of the question today even the largest miner.
So there is not problem to take away any kind of limit Smiley
None is going to use 1TB blocks (and not even 1GB now)

Not now.  Of course BIP100 won't lead to instant disaster.  Even with no block size limit we'll not see a 1GB block anytime soon.  I argue simply that without a ceiling BIP100 will tend to miner centralisation in the long-term.

Without the 32MiB limit, I would expect a BIP100 limit to grow more quickly than a BIP101 limit (even were they both set to start at 8MB).
135  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 05:59:39 AM
So if 80% of the mining network wants to meet increased demand by supplying larger blocks and 20% of the mining network wouldn't be able to cope with the increased demand then this 20% will be driven out of mining.
There is no such problem. Miners voting at the bottom end will simply have their votes ignored. It has zero effect on their ability to keep mining.

Part of a miner's costs is in maintaining a full node.  With more transactions, these costs increase.  If a miner cannot make enough profit to cover its costs it must go out of business.

It is very possible for a block size limit increase under this scheme to push miners at the bottom end out of business.

Again there is no such problem. I suspect you're unaware of what the mining scene is today. Virtually no miner mines for himself with his own node any more. All the mining nodes are at the pool end and pools will in no way have any difficulty storing large block sizes.

Local node sizes will only affect regular node users who choose to stick with bitcoin core or a full blockchain application as their wallet - miners will be unaffected.

I'm aware of pools.  I've had plenty of experience both mining solo and mining as part of a pool.

Perhaps you missed that I was responding to jonny1000's notion of eventually removing BIP100s stabilizers (the 1MB and 32MiB limits).  No matter how big the pool, there is a limit to its resources.  1MB blocks may be trivial, but 1GB blocks wouldn't be, and 1TB blocks would be out of the question today even the largest miner.
136  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 31, 2015, 04:14:16 AM
So if 80% of the mining network wants to meet increased demand by supplying larger blocks and 20% of the mining network wouldn't be able to cope with the increased demand then this 20% will be driven out of mining.
There is no such problem. Miners voting at the bottom end will simply have their votes ignored. It has zero effect on their ability to keep mining.

Part of a miner's costs is in maintaining a full node.  With more transactions, these costs increase.  If a miner cannot make enough profit to cover its costs it must go out of business.

It is very possible for a block size limit increase under this scheme to push miners at the bottom end out of business.
137  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 30, 2015, 11:00:48 PM
Interesting.  So it seems that you're particularly wary of the proposals which speculate long-term exponential growth of resources like bandwidth.  I certainly understand that, it's a huge drawback to BIP 101 no question.

Yes, in particular I don't like speculating about demand for the next 20 years (as well as bandwidth).

The way I see it:
  • BIP100 measures demand
  • BIP101 speculates supply

I believe both have problems and that we'd ideally like something which measures supply.

The political philosopher in me doubts that Bitcoin will remain sound in the long term if it regularly requires protocol updates to correct past speculation (Official Bitcoin protocol organisation).  The economist in me doubts that Bitcoin will remain sound if the artificial capacity limits are driven by demand (miner centralisation).

Just out of curiosity, how would you feel about BIP100 + Sipa's proposal?

I would be happy to support BIP100 with Sipa's proposal as a lower bound and BIP101 as the upper bound.  In the long run it could be better if we remove the BIP100 "stabilizers", of both the upper and lower bound, once we can rely more on the voting mechanism.

Interesting idea to grow both bounds.  I must admit I've not been paying much attention to the lower 1MB bound.  I guess there's a potential 21% attack that a growing lower bound could help mitigate.

In the long run I don't think the upper bound can be safely removed without significantly changing the algorithm.

As demand increases, there will be pressure to increase the limit (to increase supply).  So long as miners can cope with the increased demand they have an incentive to vote to raise the limit for greater profits.  This is all well and good; we want these free-market efficiencies.

However, the algorithm itself pays no attention to the level of decentralisation.  From BIP100:
Quote from: Jeff Garzik
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.

This creates a framework whereby the network may increase the block size by consensus, a lower and less politically risky hurdle than hard fork.
So if 80% of the mining network wants to meet increased demand by supplying larger blocks and 20% of the mining network wouldn't be able to cope with the increased demand then this 20% will be driven out of mining.  We'd be slowly boiling a frog.
138  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 30, 2015, 11:33:23 AM
Is there some mechanism in BIP 100 that prevents us from reaching a block size limit of 32 MiB within a few years?  I don't see why miners voting to maximise their profits would keep growth slow, especially not if there is a large uptick in adoption.

This is a good point, the reason to vote for a lower limit in BIP100 only really comes into play once the block reward is low.  Therefore we need to be careful in the early years that the size limit does not get too large.  Therefore I agree BIP100 with BIP101 as an upper bound may be a better idea than allowing 32MB too quickly.

For what it is worth, here are my order preferences:

BIP100 with BIP101 as the upper bound > BIP100 > Sipa proposal > One off shift to 8MB > Do Nothing > BIP101

Interesting.  So it seems that you're particularly wary of the proposals which speculate long-term exponential growth of resources like bandwidth.  I certainly understand that, it's a huge drawback to BIP 101 no question.

For myself, as much as I am uncertain about future bandwidth growth, I am fairly certain that the bitcoiners of 2025 (if there are any) will be less interested in decentralisation than we are today and far more amenable to the formation of a special organisation to manage the protocol.

Just out of curiosity, how would you feel about BIP100 + Sipa's proposal?
139  Bitcoin / Development & Technical Discussion / Re: Measuring the cost of running a full node. on: August 30, 2015, 09:20:19 AM
Is it possible to measure the cost of running a full node?
You could put an electric meter on the plug of your node and measure it's consumption I guess.


I get that.  I meant is it possible to create a trustless measure, something that Bitcoin itself could refer to for example in calculating an appropriate block size limit.

I vaguely recall Gavin was toying with the idea of trying to measure technological development trustlessly by, for example, having full nodes report how long it takes them to verify a block.  Unfortunately, this system was open to abuse.

I didn't keep up with this line of inquiry and learned that eventually Gavin turned to simply estimating future technology trends (e.g. BIP 101).  I can't prove to myself that a dynamic approach is impossible so I decided to think out loud here.  I guess what I'm looking for is for someone to show me how to abuse the idea above; this would definitely help me hone in on the problem.  If no-one breaks it then I'll expand the idea and flesh out a draft proposal to catch more eyeballs.
140  Bitcoin / Development & Technical Discussion / Re: Why I support Jeff's BIP100 on: August 30, 2015, 05:33:32 AM

With a more thoughtfully set ceiling, I see no clear reason to reject BIP 100.

What is a more thoughtfully set ceiling to the proposed one of 32MB?

BIP 101, Block size following technological growth, and arguably 8MB.  Far from being thoughtfully set, the 32 MiB ceiling of BIP 100 is just an old limit revealed.

I should say that even with such a change I wouldn't be a supporter of BIP 100.  It's just that my main concern with BIP 100 evaporates if the limit is confined to a safe range.

You just said you're for BIP 100. With that comment I can't tell if you're for BIP 100 or 101.

I said I could see no clear reason to reject BIP 100.  I've never claimed to support it.  I realised my earlier comment might be misleading (I meant it literally) so I thought I'd clarify my position.  I found jonny1000's comments interesting because it highlighted that perhaps BIP 100 and BIP 101 were really doing different things.

What do you mean a safe range? BIP 100 with an 8GB limit in 2016 is open to abuse immediately, yet 101 eventually goes up to 101 in decades only.

Is there some mechanism in BIP 100 that prevents us from reaching a block size limit of 32 MiB within a few years?  I don't see why miners voting to maximise their profits would keep growth slow, especially not if there is a large uptick in adoption.

32MB is what I would call "confined to a safe range". Your comment says "no clear reason to reject BIP 100", but I really don't know what you're supporting with your follow up comment.

Right now I support BIP 101 (and have done since it was drafted).  My preferences at the moment (not that they matter much):
BIP 101 > sipa's proposal > Straight jump to 8MB > BIP 100 + BIP 101 > Straight jump to 32 MiB > BIP 100 > Do nothing.

I consider BIP 100 better than doing nothing (don't see how it hurts Bitcoin).  I do not support it because I think there are many better alternatives.
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 ... 76 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!