r/btc • u/SwedishSalsa • Feb 10 '19
MFW i read Luke Jr wants to limit BTC blocks to 300k.
33
u/homopit Feb 10 '19
He also believes that actual BTC chain usage is below 10KB per block, and all the rest is spam. There was a quote of him saying that.
11
Feb 10 '19
The return of the central planner..
How low the onchain capacity has to be to satisfy Cored dev vision of bitcoin?
4
u/loomenaughty Feb 10 '19
The vision isn't complete until all transfers of value occur either on a KYC exchange or through a KYC Lightning hub.
4
5
u/mcmuncaster Feb 10 '19
he has also released sw to attack SW to artificially inflate blocks (to make smaller blocks)
i like luke - even though i disagree with most of what he says, he's smart, knows what he believes and is consistent. he genuinely feels bitcoin is not sustainable at 1M blocks. .
9
25
u/michalpk Feb 10 '19
Fortunately for bitcoin he has no power to push it through
5
u/ShadowOfHarbringer Feb 10 '19
Fortunately for bitcoin he has no power to push it through
Oh really ?
LN will also obviously never work as advertised, and they are still pushing it through as "custodial accounts"(== bank).
So I wouldn't be so sure if they won't push it through.
At least they may try.
11
u/michalpk Feb 10 '19
I thought we talked about Luke and not "them". He never got wide support for mining algo change and he doesn't have support for 300kB blocks either...
2
u/Thanathosza Feb 10 '19
Wait till they start censoring anyone who objects. See how quickly he gets support.
5
u/michalpk Feb 10 '19
He has as much chance as convincing everybody the Earth is flat
6
u/Thanathosza Feb 10 '19
I remember a time when saying the blocks should be kept 1MB was dumber than saying the earth was flat. Never underestimate the power of censorship.
0
u/michalpk Feb 10 '19
Bitcoin dot com is probably most visited bitcoin related site r/btc is second biggest subreddit. BTC doesn't have anybody like Bitcoin jesus to push acceptance tirelessly day and night for almost 2 years now, and still only 3% users moved away from btc to bch. Stop blaming censorship for everything and look around. Majority of users are happy with BTC
2
u/Thanathosza Feb 10 '19
When last have you used it as cash?
3
u/michalpk Feb 10 '19
probably 2 months ago Why is it important? Taking my savings out of inflationary fiat currency to BTC is valuable use case for me. I prefer to get rid of my EURos unless merchant pushes me to spend my BTC.
1
u/Thanathosza Feb 10 '19
If you want a store of value gold is your best bet. Look at mene.com for instance. I use bch daily so I need something that works as cash. But your idea may end up paying off. To each his own, at least we can agree that fiat and banks suck.
1
u/lubokkanev Feb 10 '19
That's pretty delusional.
2
u/michalpk Feb 10 '19
Hmm if you think so ... https://bitinfocharts.com/comparison/transactions-btc-bch.html#log&1y
0
u/loomenaughty Feb 10 '19
You really can't judge Bitcoin Cash adoption by comparing market caps. 90% of users could move to BCH, but as long as the richest users stick with BTC it would remain higher.
5
u/michalpk Feb 10 '19
BCH which supposed to be used as cash has 3% of BTC (SoV coin) daily transaction count.
1
u/dominipater Feb 10 '19
one thing's for sure...there's an infinite reservoir of patience here for talk about what could be
0
3
u/Pretagonist Feb 10 '19
Who the hell are "they" and why do you believe they have any influence over bitcoin? No one is forcing LN on you, no one has the power to lower blocksize. LN is the least custodial blockchain layer 2 system ever invented. Most of it's actual problems stems from its decentralized nature.
-9
1
u/stale2000 Feb 10 '19
Actually, that is a softfork, not a hard fork. And as the Core Developers say, consensus doesn't matter for soft forks. So they absolutely *can* push it through.
2
u/michalpk Feb 10 '19
Not sure you can implement it as a soft fork, but I didn't read the proposal not even sure it exists. In my opinion it has 0 chance to succeed anyway. This will be another Luke's panic attack trying to solve a problem, which actually solves on its own. First was mining algo change to prevent mining centralisation.
1
u/stale2000 Feb 10 '19
Not sure you can implement it as a soft fork
It is trivial to implement a blocksize decrease as a soft fork. You literally just reduce a number. Thats it. 1 line of code.
2
u/michalpk Feb 10 '19
So you as a miner would just produce 300kB blocks but still accept 4MB blockweight? That desn't make much sense to me . And if you refuse blocks bigger than 300kB you fork yourself off from old nodes and it isn't softfork anymore
0
u/stale2000 Feb 10 '19
So you as a miner would just produce 300kB blocks but still accept 4MB blockweight?
Do you understand what a softfork is?
No, the way that it would work is that you would not accept blocks larget than 300KB.
This is backwards compatible with the old network. A soft fork is when you make the rules more strick. IE, you make old stuff invalid. The old stuff that would now be invalid is blocks bigger than 300kB.
A soft fork just means that you make the rules more strict. Old nodes would follow you, as it is backwards compatible.
2
u/michalpk Feb 10 '19
Correct Softfork is more restrictive, but it must accept old TXs and blocks. Current mining node can produce up to 4MB weight block which must be accepted by new nodes if you want to have consensus across old and new.
Same as Segwit nodes accept non-segwit transactions.
0
u/stale2000 Feb 10 '19
No, if you do a softfork you do not have to accept old blocks. That's the point. Old behavior (4MB weight blocks) would now be invalid.
You don't even need to accept old transactions, actually. If you only allowed empty blocks to be mined, this would be a soft fork, for example.
3
u/michalpk Feb 10 '19
What would happen to big blocks created by the old nodes?
They would be rejected by the new (300kB version) nodes, but perfectly acceptable for old-non ugraded nodes => so you have 2 chains / hard fork
0
u/stale2000 Feb 10 '19
The old blocks would be temporarily accepted by old nodes, and then they would be orphaned by the majority of the hashpower.
This would cause old nodes to then follow the new, majority chain.
Also, having 2 chains has nothing to do with hardforks. They are completely unrelated concepts. Go look up the definition of a soft fork and hard fork.
The only thing that a soft fork is is that you make the rules more restrictive. That's it. It has nothing to do with chain splits.
It is possible for soft forks to sometimes cause a chain split and other times to not. Either can happen.
1
u/Thanathosza Feb 10 '19
Isn't it just a setting in the client? As long as they control the client there isn't much anyone can do.
2
u/CatatonicMan Feb 10 '19
Miners can choose to put fewer transactions in blocks if they want, though they'd be leaving money on the table if they did, so they probably won't.
Alternatively, it could be done via soft fork, assuming they could manage to find enough support to get it through.
-1
u/michalpk Feb 10 '19
Everybody can run any client he wants. Old one or from different team. Everybody can choose to follow the fork he likes Only If ALL miners decide to follow new rules, you would have to start mining by the old rules yourself.
2
u/hibuddha Feb 10 '19
There aren't really any "other teams" in BTC development, at least teams that matter/make a difference.
2
u/michalpk Feb 10 '19
There are many
https://en.bitcoin.it/wiki/Clients
If users disagree with core team's implementation the other teams will grow....
0
u/hibuddha Feb 10 '19
https://coin.dance/nodes/share
Doesn't look that diverse when you view it by percentage. History indicates that it's more likely they'll just fork off if they disagree, too.
0
Feb 10 '19
[deleted]
3
u/michalpk Feb 10 '19
Just one example. Btcd is full re-write of full bitcoin node in Go. It has full feature parity with bitcoi core. Lnd (lightning network client) is using Btcd as default bitcoin client.
Bitcoin core is open source implementation of bitcoin rules Bitcoin cash like many other altcoins is clone of that repository with few changes implemented within one month. This can very easily happen again. And when majority of users will support the new fork, bitcoin core team will have no tools to stop them. BCH just doesn't have that user support. The laud and vocal "majority" turned up to be something like 3% of bitcoin user base.
0
Feb 10 '19
[deleted]
3
u/michalpk Feb 10 '19
btcd was intentionally developed without an integrated wallet for security reasons. Please see btcwallet for more information.
Interestingly btcd has been forked to support bitcoin cash rules
My point is that with real majority of users support it is trivial to fork bitcoin Amaury Séchet proved it when he created Bitcoin Cash. Nobody could stop him or whomever forked btcd. The problem is that almost nobody cares. When bitcoin core does something stupid with which the majority of user will disagree they will fork it the same way Amaury did, and if 90% of users install the forked version it will keep the Bitcoin name.
1
u/Capt_Roger_Murdock Feb 10 '19
Fortunately for bitcoin he has now power to push it through
Unfortunately for bitcoin, he doesn’t need to. Moving to a 300kb limit would simply represent an acceleration of the ongoing “nearly-empty block attack” BTC is being subjected to (described below).
I doubt a well-funded and sophisticated attacker would be that unsubtle. I think a more realistic threat than the “empty block attack” you’re describing is the far more insidious “nearly empty block attack.” This is where a hostile entity takes over (and/or bamboozles) a majority of the hash power in order to ensure that only blocks that are nearly empty are mined and accepted. (“Nearly empty” being defined here relative to transactional demand and the network’s actual technological capacity.) Ideally (from an attacker’s perspective) this attack would take the form of keeping in place an arbitrary and always-intended-as-temporary capacity limit as it became increasingly inadequate in the face of rising transactional demand. This would allow the attacker to leverage the power of the status quo while also ensuring a relatively slow (and thus less likely to be effectively resisted), “boiling frog”-type degradation of the network’s performance. A successful attack would likely necessitate the co-opting of key developers and forum operators as well as a sustained campaign of social media debate manipulation and propaganda. Hell, as ridiculous as it might sound, I can even imagine the attacker pushing propaganda painting their attack as a defense of the network (against “centralization” or the “danger” of “contentious hard forks” or some other such nonsense).
-1
u/frappuccinoCoin Feb 10 '19
Didn't he single-handedly add RBF?
7
-3
u/michalpk Feb 10 '19
Any developer can add whatever he/she wants. RBF was accepted by wast majority. Same with segwit. BCH fork is supported maybe by 5% of community.... Whatever measurement you use transaction count, node count, development activity, price.
3
u/frozengrandmatetris Feb 10 '19
they were going to implement opt-out RBF. and there was screaming and gnashing of teeth, and they capitulated and did opt-in RBF instead. it's not as simple as everyone just accepting RBF.
I do this all the time at work. When I need to force a change on my users I make two possible implementations that both have the change. Then I let them choose which one they want. I'm using deception to manipulate them into accepting my change and it works most of the time.
need I remind you that segwit was accepted only after a blocksize increase was promised to go along side it? and that it was just a lie?
2
u/phro Feb 10 '19
Yea, well emergent consensus was more popular than segwit for a long time. Segwit only reached activation threshold when packaged with 2x. Even then they added bip91 which orphaned any blocks not signaling for segwit. It took censorship, a bait and switch, and bullying to get segwit activated.
11
u/unitedstatian Feb 10 '19
Measuring the success of BTC in the number of full nodes is like measuring the economy by the miles goods travel (Soviet Russia reference).
10
9
u/Dixnorkel Feb 10 '19
He's a complete nut, he also once made the assertion that he wants to change the BTC algorithm to HalongSHA256 in order to make the market less centralized (i.e. since Bitmain is mining on the network) lol.
3
u/Makylias Feb 10 '19
Sometimes I have the feeling that he is deliberately proposing solutions that are the complete opposite of BCH or even attacking it like the algorithm change. Solutions that only worsen Bitcoin but are made out of his hate towards BCH, if that is the truth he should be fired instantly.
9
u/Dixnorkel Feb 10 '19
For a while, I thought he was trying to discredit BTC because he actually supported BCH. I've come to the conclusion that he's just completely insane though, his interviews make him come off as not even human lol.
2
u/TheGreatMuffin Feb 10 '19
What's "HalongSHA256" algorithm? I'm aware of the Halong miners, but it's the same SHA256 algorithm
7
u/Dixnorkel Feb 10 '19
He suggested switching to a modified version of SHA256, specifically designed for Halong miners. It doesn't exist, he just proposed it "to promote decentralization". Lol
5
9
u/where-is-satoshi Feb 10 '19
I say core should get right to it. Bring on the smaller blocks and the fee market. "Champaign" I say!
What better way to expose BTC for what it is - a dead coin walking.
It will also force coreons to move to LN and similarly expose its failure to scale.
Bitcoin BCH will begin its reign sooner.
2
16
u/daken15 Feb 10 '19 edited Feb 10 '19
Bitcoin values decentralization over all. And having more nodes and transactions being send from those nodes is the goal. If we allow 3-4 companies to be the only ones running nodes, they will have all the power to make any decision they want.
Luke with this proposal wants to increase the number of nodes. The initial blockchain download is already over 250GB and growing.
His opinion is not to limit the blocksize to 300k but to start with 300k and do a dynamic block size like Monero (not exactly like Monero but something to increase the size over time)
Nobody in Bitcoin is opposed to increase the blocksize. They believe that this should be done in a responsible manner, only when the tech allows it and doesn't prevent anybody to run their nodes.
16
u/caveden Feb 10 '19
Nobody in Bitcoin is opposed to increase the blocksize. They believe that this should be done in a responsible manner
This is an obvious lie. A "responsible manner" would have been before 2017. Before the system hit max capacity. You never let the system hit max capacity, that's basics.
-3
15
u/jessquit Feb 10 '19
Nobody in Bitcoin is opposed to increase the blocksize.
Nobody in China is opposed to democracy. They believe that this should be done in a responsible manner, only when the people are ready for it.
15
u/TetheralReserve Feb 10 '19
So why exactly it was notincreased by atleast 20% when blocks became full?
-2
u/daken15 Feb 10 '19
It doesn't matter how full the blocks are. The tech is not ready yet. Downloading the blockchain take 4 days already on an average computer.
10
2
u/pelasgian Feb 10 '19
So your measure of when to increase the block size is what? When storage costs drop? Aren’t they always dropping? Or is it when bandwidth costs drop? Or is it when the internet reaches undeveloped regions in the world? There needs to be an actual metric otherwise we’re at the whim of some nebulous idea.
-1
u/Onecoinbob Feb 10 '19
Another factor was that many economic nodes weren't using the blockchains very efficient.
Exchanges were able to improve the throughput by a lot by introducing batching for example.0
u/Capt_Roger_Murdock Feb 10 '19
Another factor was that many economic nodes weren't using the blockchains very efficient. Exchanges were able to improve the throughput by a lot by introducing batching for example.
What you're describing is one form of demand destruction and yes, it does partly explain why transaction numbers and average transaction fees fell in 2018. I give a more complete explanation here.
-1
u/Bag_Holding_Infidel Feb 10 '19
Consensus was it was not the correct time. Every other scaling option should be explored before a block size increase.
0
u/nevermark Feb 10 '19
I don’t even know what to say to comments like this. Bitcoin adoption by vendors rose, stalled and collapsed.
So BTC was exploring the failure option first, before considering the maintaining successful adoption option?
All to save a few bytes of almost costless storage in a world of cheap petabytes?
The whole block limit “debate” is so surreal.
2
u/Bag_Holding_Infidel Feb 10 '19
So BTC was exploring the failure option first
You are assumimg adoption by vendors in 2017 is the metric of success to be used to cover both the SoV element of bitcoin and the MoE element. It is not, the two different ideologies are the reason for the split.
1
u/nevermark Feb 11 '19 edited Feb 11 '19
two different ideologies
You are correct that the SoV vs. MoE false dichotomy is an ideology. There is no good economic theory suggesting that MoE hurts SoV, wh
You are also right to bring up alternate metrics. If the metric is store-of-value, then the lack of anything that can stabilize prices is a problem. If there is another mechanism besides transactions to create stickiness and stability to BTC value, what is it? (Genuinely asking.)
For instance, gold is also not transaction-friendly, but has practical uses relative to other materials. Drops in store-of-value demand don't collapse gold prices because lower prices create increased practical demand. Even if most available gold is used as "store of value", its usefulness and stability are held up by having a firm value bottom that does not involve speculation.
Edit: Clarity (I hope)
1
u/Bag_Holding_Infidel Feb 12 '19
If there is another mechanism besides transactions to create stickiness and stability to BTC value, what is it?
This is the part where we disagree on L2 solutions. I see a future where on-chain transactions are very expensive to pay the miners and L2 transactions support effectively infinite transactions. Whereas you see a future where its mostly on chain.
MimbleWimble isn't mentioned much but it reduced transaction size by 98%, effectively giving us an order of magnitude throughput to what we have now.
1
u/nevermark Feb 12 '19
Any scenario where on-chains end up expensive isn't realistic. Digital payments are going to be crazy cheap.
The only reason they are not now is this tech is relatively new and in-progress and there has not yet been a single must-have use case driving adoption (which would pull in greater scales of research). Also, the level of unprofessionalism (i.e. tribalism over pragmatism even by developers) is pretty astounding now. That will change too.
MimbleWimble is a great example of a huge improvement available now. Sharding also offers advantages. There will be more insights.
7
u/fapthepolice Feb 10 '19
They believe that this should be done in a responsible manner
There is nothing responsible about not doubling the block size before mid 2017. I don't necessarily disagree about the rest.
7
Feb 10 '19
Nobody in Bitcoin is opposed to increase the blocksize.
lol BULLSHIT, this issue is the entire reason BCH exists at all after fighting Core dev clowns on it for years
5
Feb 10 '19
Luke with this proposal wants to increase the number of nodes. The initial blockchain download is already over 250GB and growing.
How come lowering the blocksize limit will increase the total number of nodes?
Lowering the capacity will increase the cost of transactions, that will reduce the total number of nodes (who will run those cheap nodes for a network too expensive to use??)
3
u/phro Feb 10 '19
As bitcoin grew from 0 to 1MB node count and decentralization improved. No math proving 1.1MB would reverse that trend was ever provided.
2
u/pelasgian Feb 10 '19
If people aren’t transacting on the main chain because block size is small and transaction fees are high, what incentive do people have to run a node for a service they’re not even using?
1
u/daken15 Feb 10 '19
Bitcoin is the most used coin. People are using it.
1
u/pelasgian Feb 10 '19
I meant from an individual perspective. If you as a user do not transact on the main chain because of high fees, what incentive do you have to run a full node?
1
1
u/lubokkanev Feb 10 '19
And the only reason for that is that Blockstream stole the BTC network effect for their science project - restrained blockchain with unfinished layer on top.
2
u/SlingDNM Feb 10 '19
A 1TB harddrive is under 80$
4
u/daken15 Feb 10 '19
OMG. It's not about storage... it's about initial blockchain download and bandwidth
8
u/SlingDNM Feb 10 '19
Why would You Care about Initial Blockchain Download? A full node is supposed to be online 24/7, its a one time wait... Bandwith isnt really an Argument, You have unlimited bandwith in Most places in the First world (at least in Europe No Idea about the US) and Internet Connections are only going to become faster and cheaper (can't You get 50k Google Fiber for free in some places), I pay 15€ for half a Gigabit of limit-free Internet
Imo Bitcoin as a Project is dead, I'm still holding both Cash and Core because There will be fomo again coming years, but TBH Bitcoin was Just a nice First try, but Other cryptos are Just flat Out better sadly, especially the Point that You can't make Anonymous transactions
2
u/hibuddha Feb 10 '19
Why is that even an argument when fast-sync and pruning are now commonplace?
4
u/daken15 Feb 10 '19
Pruning? So you will never have the full blockchain? Who will have it? Who is going to send you the data?
2
u/hibuddha Feb 10 '19
Plenty of people will store the full blockchain, it just enables people to run a node on pretty much anything. It also blows a Core argument to smithereens.
1
u/frozengrandmatetris Feb 10 '19
I get really excited about blockchain projects that allow you to start a full node from a pruned node. You literally wouldn't have to care about coffee transactions from a decade ago and that's a massive benefit for scaling. There was discussion about heavy pruning on BTC until the censorship was in full swing. Now nobody talks about it in the BTC world anymore.
0
1
Feb 10 '19
Nodes are enterprise software, if you cannot handle a measly 250gb or have a network capable of downloading that much in a timely manor, you have no business running one then
0
u/roveridcoffee Feb 10 '19
Thanks for the explanation. Dynamic block size makes perfect sense, if safe to implement, since most blocks are underutilized at this stage anyway.
0
3
u/Hernzzzz Feb 10 '19
That would be 10 times bigger than BCH blocks, maybe BCH should implement it first to see if it helps with its centralization problem. https://fork.lol/blocks/size
6
Feb 10 '19
That would be 10 times bigger than BCH blocks,
One chain has potential, one chain is maxed out.
1
u/Hernzzzz Feb 10 '19
Choose wisely.
1
Feb 10 '19
We chose the version of Bitcoin that doesn't shit itself when traffic gets high
1
u/Hernzzzz Feb 10 '19
This chart clearly shows which coin shits the bed when traffic gets high https://coinmetrics.io/charts/#assets=btc,bch_roll=30_left=priceBtc_right=txCount_zoom=1498817322171.3018,1549670400000
0
1
u/Bag_Holding_Infidel Feb 10 '19
maxed out
Used most efficiently is another way of putting it.
1
Feb 10 '19
Used most efficiently is another way of putting it.
It is not accurate.
Segwit take more data for the same TPS and give a discount to large transactions (See weight calculation).
So no, segwit is not more efficient not that really matters for settlement network.
1
1
1
1
u/CatatonicAdenosine Feb 11 '19
Yes. There are now at least two Bitcoin experiments. Let them take theirs where they wish.
-2
u/foox404 Feb 10 '19
I can't belive that so much debate is going in to block size.. I wonder if in a parallel universe there's a war over the time to find blocks. I mean 10 minutes?! Seriously?
0
0
12
u/DaSpawn Feb 10 '19
this is because he completely ignores the reality that most users would be running lite clients in the future and not everyone needs to run a full node and so there is no need to obsess over the overall chain size (within reason)
what really baffles me is how someone so smart would ignore fixing the lite client risks instead of creating the SW/LN crazy contraption