r/btc • u/money78 • Apr 26 '19
Quote Jonathan Toomim: "BCH will not allow block sizes that are large enough to wreak havoc. We do our capacity engineering before lifting the capacity limits. BCH's limit is 32 MB, which the network can handle. BSV does not share this approach, and raises limits before improving actual capacity."
https://twitter.com/jtoomim/status/112173436727593370025
Apr 26 '19
Imagine engineering a system for usability while simultaneously mitigating technical risk - whodathunk that was a good way to do it?
1
u/fiah84 Apr 26 '19
that's all I ever wanted of bitcoin: focus on making electronic peer to peer cash work. Satoshi's decision to set the blocksize limit to 1MB was reasonable at the time, he just didn't foresee that it'd become the linchpin of an all out social war.
I'd argue that the 32MB limit is a bit high for BCH today, but it doesn't matter much. What matters is that the way forward is clear, and even today we have the tools to get there
0
u/Xangomott Redditor for less than 2 weeks Apr 26 '19
Imagine engineering a system for usability while simultaneously mitigating technical risk - whodathunk that was a good way to do it?
Someone should inform /u/timmy12688 of this fascinating thread and this fascinating concept.
0
Apr 26 '19
[deleted]
5
u/cryptocached Apr 26 '19
Yet some smaller, more insulated group of devs do?
10
Apr 26 '19
Yet some smaller, more insulated group of devs do?
Well they are not trying to change the project.
The core dev got a « bitcoin is fundamentally broken, we know how to fix it » god complex.
-5
u/cryptocached Apr 26 '19
So your tribe's god is better than their tribe's god?
9
Apr 26 '19
So your tribe’s god is better than their tribe’s god?
Yes.
One set of dev are trying to build a currency, allowing any scaling solution to be implemented (onchain/offchain), building on the project original goal and economics.
Another set dev decided to restrict the network capacity, deny the project should have currency characteristics, show lack of knowledge or even disregard for economic, impose unproven offchain scaling solution.. while being a startup whose business plan rely on sidechain products.
-2
u/cryptocached Apr 26 '19
It sounds like you're not really against the idea that a small group of insulated devs knows best. You just disagree on which small group of insulated devs knows best.
7
u/jessquit Apr 26 '19
Software is perforce created by small groups of devs. They do not have to be insulated perforce. But it's true that no team has a monopoly on good ideas.
1
Apr 26 '19
No single person or small group know better than the market, ever.
The superior approach is the one than allow the market to discover the best path forward.
Central planning always fails.
→ More replies (4)0
Apr 26 '19
[deleted]
4
u/tl121 Apr 26 '19
The original WP did not define a protocol, nor did the original implementation.
1
u/Adrian-X Apr 27 '19
Try to understand that the Bitcoin design incentivizes people (those negatively affected by problems) to fix the most pressing issues as they present.
No centralized authority is necessary.
0
Apr 26 '19
[deleted]
1
u/jessquit Apr 27 '19
Assuming this is true why is it even good?
Real Satoshi continuously improved the protocol and made all kinds of serious changes to it until he left the project around v0.3.x. He said in the white paper that we could enforce any needed changes to the rules or the incentives. It wasn't ever supposed to be some sort of museum piece. It's software, it has to evolve or die.
0
Apr 27 '19
[deleted]
1
u/jessquit Apr 27 '19
otoh, unlimited innovation should be the way forward on upper layers
Well well well. Where have we heard this message before, if not the Blockstream pitch deck?
4
u/cryptocached Apr 26 '19
No they're not. The implemented protocol never matched the white paper's description. If they intend to match the original implementation, they're going about it in a very round-about way considering the changes they've introduced.
0
Apr 26 '19
[deleted]
5
u/cryptocached Apr 26 '19
Adding new opcodes and altering functionality of old opcodes.
0
Apr 26 '19
[deleted]
2
u/cryptocached Apr 26 '19
which new opcodes
Do you not know already?
what alterations of significance?
If the goal is to restore the original protocol isn't any alteration significant?
→ More replies (13)3
Apr 26 '19
LOL your devs don't know what they're doing.
All the know how to do is uncomment code and do find and replace in documentation.
Don't believe me? Explain their GitHub: "Latest commit by Danconnolly 3 months ago"
0
Apr 26 '19
[deleted]
4
u/cryptocached Apr 26 '19
Not recognize Craig Wright as the transparent fraud he is.
→ More replies (7)-4
u/Vincents_keyboard Apr 26 '19
100%
Unfortunately many have drank too much of Greg Maxwell's koolaid, and now they've missed the last six months, not to mention the months before the November 2018 fork / "upgrade".
20
u/BitcoinIsTehFuture Moderator Apr 26 '19
Excellent and concise way of explaining why BCH's scaling method is the better choice. Anyone rooting for BSV's scaling method doesn't understand anything about actual technology and is fooled by big numbers because they are technically illiterate.
9
u/fiah84 Apr 26 '19
I see the BSV trolls are out in force today, desperate to prove to themselves that they haven't been fooled by the biggest fraud in crypto history
0
u/The_BCH_Boys Apr 26 '19
I have yet to have someone not behind a keyboard explain to me how I'm "technically illiterate" for siding with BSV.
Would you care to do a show and explain?
4
-2
Apr 26 '19
Riiiiiight. So sustained 128MB blocks are not possible?
3
u/BitcoinIsTehFuture Moderator Apr 26 '19
They are with proper optimizations, which SV has not done.
0
0
u/Vernon51 Redditor for less than 60 days Apr 27 '19
Exactly, they will never happen on BSV
1
Apr 27 '19
Ok, so the BSV test network is doing sustained 128MB blocks, but I guess that's nothing to worry about.
-1
u/lubokkanev Apr 26 '19
While I do agree, BTC-ers have been saying the exact same thing for BCH.
BSV was created to mock big blockers.
0
Apr 26 '19
[deleted]
17
u/LovelyDay Apr 26 '19
No, BSV has turned themselves into a laughing stock.
2
u/Vincents_keyboard Apr 26 '19
?
4
u/LovelyDay Apr 26 '19
Huge blocks that deep re-org their network ... not funny?
It's funny to me only because I don't need to use their network.
-2
Apr 26 '19
You are now afraid of a re-org which is a feature of Nakamoto consensus? If a miner loses a block reward, why do you care? Only the miner should care, and improve their operation, so it doesn't happen again.
4
u/LovelyDay Apr 26 '19
improve their operation, so it doesn't happen again.
I agree with you on that, but that's literally irreconcilable with a strategy of busting up their main network every so often in the process of testing their own software...
3
u/jessquit Apr 27 '19
You are now afraid of a re-org which is a feature of Nakamoto consensus?
A reorg is a feature of Nakamoto Consensus in the exact same way that a fever is a feature of the human immune system.
1
Apr 28 '19
Interesting analogy, but the immune system has more than fever in its locker. Nakamoto consensus is literally centred around the re-org mechanism. It makes no sense to eschew the one magical thing that makes Bitcoin, Bitcoin. When people do that I have to assume they don't understand it.
1
u/jessquit Apr 28 '19
I will tell you what I told your brain dead troll friend.
If you think reorgs are such a positive moment, then shut up and go cause more reorgs, so that all the good things that we don't understand about reorgs will happen to your chain, and you'll be vindicated.
Now stop arguing and pretending to know better and go reorg the fuck out of your chain. Because that's how Nakamoto Consensus works right? Please stop trying to convince us with your words, just prove it to us.
Ideally you'd have some nice 10+ block reorgs so that you can get all the benefits that we lost out on by implementing 10 block rolling checkpoints in ABC. You guys like to make fun of that one. Why not show us how useful a 13 block reorg can be? Do a few!
1
Apr 28 '19
The other guy is the troll. Why don’t you try reading instead of mouthing off? Much better use of your time. You may even learn something.
→ More replies (0)-5
u/Adrian-X Apr 26 '19
That's what this herd says. It sounds like the Bitcoin Core herd only they have switched BCH with BSV.
Same story different actors.
-14
u/Zarathustra_V Apr 26 '19
It's you and this sub, the Maxwell upvoters who are the laughing stock.
10
u/LovelyDay Apr 26 '19
I suggest you don't come here then.
You have your own cryptorebel sub now, where you can march on all fours to the tune of Craig's propaganda missives.
Orwell would be proud!
→ More replies (2)6
u/Richy_T Apr 26 '19
I'm no fan of BSV but some of the rhetoric and attitude coming from BCH definitely makes me uncomfortable.
3
u/mrreddit Apr 26 '19
What difference does it make if you are a small blocker or big as long as fee to get into the next block is $0.01? BTC could have raised blocksize to 2MB still call themselves tinyblockers but BTC would have been a viable currency TODAY.
-1
Apr 26 '19
We raised the block limit to 4000 weight, which has produced blocks greater than 2 MB. CHECKMATE
1
4
u/masterD3v Apr 26 '19
You've misinterpreted it. BU and Bitcoin (Cash) has always been about scaling on-chain safely. Only Core has been about a centralized, unfounded 1Mb artificial limit (everyone, including you, knows it can handle more without issue). BSV was an attack and is the opposite - scale as much as possible, making sure to not support that scaling technically in an attempt to disprove larger blocks.
-5
Apr 26 '19
BU and Bitcoin (Cash) has always been about scaling on-chain safely.
No, that's Bitcoin.
Only Core has been about a centralized, unfounded 1Mb artificial limit
See that's exactly the same thing BSV says about BCH. Thank you for proving my point.
5
u/masterD3v Apr 26 '19
If we can agree that 32Mb is small, then I think we can come to a compromise here!
Notice I said unfounded 1Mb limit. 32Mb is enough to allow scaling safely, while anything larger than that is also unfounded. The 32Mb limit is based on the Testnet Gigablock research. Research-based, fact-based and logic-based scaling solutions work.. your propaganda half-trolling doesn't.
You're an older user, I wonder when you switched and decided that peer-to-peer electronic cash didn't matter anymore? Maybe you decided to become a middleman?
-2
Apr 26 '19
Notice I said unfounded 1Mb limit
The limit isn't 1 MB and hasn't for the entirety of BCH's existence. Perhaps I could take you more seriously if you weren't working based on a years out of date model.
What you and I consider well-founded differ. We're making the same argument against unfounded block sizes, we are just considering different factors. You're considering purely the technical capacity of the system. I'm considering other effects, like socio-economic effects (things that aren't modeled by Testnet Gigablock) - increased cost to run a full node leading to fewer full nodes and increased trust required in miners, etc.
You're an older user, I wonder when you switched and decided that peer-to-peer electronic cash didn't matter anymore? Maybe you decided to become a middleman?
Ok now you can just go fuck yourself, newbie.
3
u/masterD3v Apr 26 '19 edited Apr 26 '19
I'm talking about BTC's 1Mb limit. Segwit doesn't count as it was a soft-fork and shouldn't be forced on anyone (that's the point of soft-fork's right?.. right?).
I guess having a large mempool and high unconfirmed transaction count is well-founded?
increased cost to run a full node leading to fewer full nodes and increased trust required in miners, etc
Chris, you know that full nodes are completely secondary unless they are mining nodes. Full nodes connect and get disconnected from the network - they don't make or signal changes on the network. If a non-mining full node disagrees with a mining full node, the non-mining full node gets kicked off of the network, not the mining one. This is also why SPV nodes are practical for most users.
Further, when you increase blocksizes and allow for more users, you will increase the number of full nodes. More businesses will be mining as the price rises. Allowing on-chain transactions helps mining full-nodes (the important ones) increase.
Ok now you can just go fuck yourself, newbie.
I'll just let that go.
0
Apr 26 '19 edited Apr 26 '19
Chris, you know that full nodes are completely secondary unless they are mining nodes.
False. Without a full node, you cannot ensure that miners are following consensus rules. Not understanding this, your position is entirely reasonable, though still absolutely wrong.
If you can't agree with this simple fact, there's no reason to discuss anything else.
1
u/masterD3v Apr 27 '19 edited Apr 27 '19
Full nodes don’t include transactions in the next block. Without miners, full nodes are useless. Full nodes receive and depend upon miners, miners only depend upon and receive blocks from other miners. Nodes mean nothing and dictate nothing.
Your factually 100% incorrect on a technical and fundamental level, to the point of being intellectually dishonest.
Just to make it entire clear: we have hashwars, not full-node wars. A single miner that is connected to other miners can disagree with 1000 or 10000 full nodes and those nodes are the ones that get kicked off of the network, as long as the other mining nodes validate that block.
Think about it: what you're saying is that a single person can spin up thousands of full nodes and somehow control the network because full nodes do something. Ras-pi full nodes don't control "the longest proof of work chain".
1
18
u/masterD3v Apr 26 '19
It never made sense that BSV would build fake 128Mb blocks just to show that their network couldn’t handle it yet. They reorg’d their own chain and proved the exact point that Jonathan Toomim just made: scale as much as possible when it’s shown to be possible, but not before.
18
u/Chris_Pacia OpenBazaar Apr 26 '19
You would think, but we've seen some incredibly dumb people in their community. Almost all are non-technical and shout down technical people and insist they are wrong. It's the flat earth club of crypto.
-3
u/5heikki Apr 26 '19
Says the computer illiterate who stated as a fact that blocks larger than 22MB were impossible
18
u/Chris_Pacia OpenBazaar Apr 26 '19
Say the guy which such a severe reading comprehension problem that he is STILL stating I said this despite numerous people linking to my actual words for months.
Allow me link to myself https://www.reddit.com/r/btc/comments/bemxay/the_bsv_chain_has_just_experienced_a_6block_reorg/el71fd4?utm_source=share&utm_medium=web2x
1
u/slbbb Apr 26 '19
1 reorg for 10 blocks. I am not an expert like you, but if what you say is right, the rate should be close to 100%, not 10%, yes?
6
u/Chris_Pacia OpenBazaar Apr 26 '19
Afaict BSV did not sustain 128mb blocks for any significant length of time.
0
Apr 26 '19
[deleted]
4
u/Chris_Pacia OpenBazaar Apr 26 '19
It's never been about one off blocks. This is why you guys drive me crazy. There's the old dictum from Murray Rothbard... it's no crime to be ignorant of something, but it's totally irresponsible to have a loud and vociferous opinion while remaining in a state of ignorance.
You guys should heed that advice. If you want people to value your opinion first inform yourself so you don't sound like an idiot to people who are informed.
0
Apr 26 '19
[deleted]
4
u/Chris_Pacia OpenBazaar Apr 26 '19
> weren't supposed to be even possible
You've seriously got some kind of mental handicap. I said repeatedly that the atmp bottleneck was a software problem that can be fixed. I even said there was code to fix it that had not yet been deployed.
I never once said the word "impossible".
→ More replies (0)0
u/tl121 Apr 26 '19
You take one 737 Max crash and blow it all out of proportion while ignoring all the other successful flights. Oops, another one...
-4
u/5heikki Apr 26 '19
https://twitter.com/ChrisPacia/status/1034556078032338945?s=19
Bitcoin network hasn't crashed. Re-orgs are part of the design. They happen with tiny BTC and BCH blocks as well. Anyway, I guess if people like you worked at e.g. Twitter then they would have limited people to one tweet per day until they were sure that they could handle whatever. I'm not interested in discussing this with you any further. All you do is spread FUD. You don't know anything about Bitcoin or software development but who cares when the fake accounts upvote you anyway, right? Social media manipulation is all that BCH is
17
u/Chris_Pacia OpenBazaar Apr 26 '19
Reorgs create uncertainty around whether your transaction should be considered final. Frequent reorgs means users have to wait substantially longer for the risk of losing the transaction to a double spend to drop to a low enough level.
This is a reduced level of service and seriously harms the cash use case.
If you persist in ramming through blocks of that size you'll have so many reorgs that the chain cannot converge and you've lost consensus.
I probably shouldn't be telling you this and just let you guys figure it out when it happens to you.
→ More replies (29)1
u/Vernon51 Redditor for less than 60 days Apr 27 '19
Reorgs create uncertainty around whether your transaction should be considered final. Frequent reorgs means users have to wait substantially longer for the risk of losing the transaction to a double spend
Yeah we have seen lots of double spends. Chris is right
2
u/500239 Apr 26 '19
6 re-orgs sure are possible. Neither Bitcoin or Bitcoin Cash were ever able to produce such an event until BSV's big block propagation issue forced it out.
-6
u/Adrian-X Apr 26 '19
You know I'm probably one of your incredibly dumb people.
I'm a generalize who probably knows more about your core business "OpenBzaar" than you do, but you'd never pay me to advise you so there that.
In fact, I probably have more influence over your business than you think. You'll probably avoid my suggestions just because you think I'm incredibly dumb.
3
u/blockspace_forsale Apr 26 '19
You know I'm probably one of your incredibly dumb people.
Proceeds to make 3 spelling mistakes in the next sentence.
Yeah I'd agree.
1
-3
u/Zarathustra_V Apr 26 '19
You would think, but we've seen some incredibly dumb people in their community
Yes, just some. But in your project it's a majority who is dumb enough to applaud and guild nullc.
4
u/-Dark-Phantom- Apr 26 '19
applaud and guild nullc
Even nullc can make comments that deserve that, for example, almost everything he wrote about Craig. All of you trolls still can not separate what he wrote in the comments of who wrote them. Why do not you try to prove that what he wrote is false for a change?
→ More replies (6)→ More replies (9)-8
u/Zarathustra_V Apr 26 '19
LOL. Who are you compared to unwriter?
18
u/Chris_Pacia OpenBazaar Apr 26 '19
I make shit with more than 2 users.
6
0
u/edoera Apr 27 '19
You're right. You build shit with 6 Users!!! How dare they compare 6 users with 2 users!! https://cash.coin.dance/nodes
As for OpenBazaar, I think OpenBazaar has more than 2 users. Probably your friends and family and investors, and yourself. That's already more than 2!
Good luck playing big influencer fish in a tiny pond that nobody cares.
-4
u/Adrian-X Apr 26 '19 edited Apr 27 '19
Still, shit is still shit. Now if you take that waste and make something with it that's something.
If you can afford my services, I can change that crap you make to something valuble for you.
→ More replies (6)-2
-4
-1
u/Der_Bergmann Apr 26 '19
It's very important. Either you have a blocksize limit bigger than the network can handle, so it must find an emergent consensus, or you have a developer set blocksize limit.
-3
u/TotesMessenger Apr 26 '19
I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:
[/r/bitcoincashsv] Now the world record 128MB blocks mined on BSV are "fake" according to troll sockpuppet /u/masterD3v, which is probably another account belonging to Greg Maxwell and the BlockStream troll team. The sheep /r/btc cult members are eating it up.
If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads. (Info / ^Contact)
0
Apr 26 '19
[deleted]
4
u/masterD3v Apr 26 '19
They were artificial.
0
Apr 26 '19
[deleted]
6
u/masterD3v Apr 26 '19
Which non-nChain or Coingeek user would use BSV for 128Mb of data? Nobody. They were artificially generated just like the paid trolls here make artificially generated comments. Nobody is using BSV. Nobody cares about BSV.
→ More replies (1)1
15
u/mrreddit Apr 26 '19
BCH is the only sane Bitcoin. BTC is fucking insane. BSV is fucking insane.
-1
u/Vincents_keyboard Apr 26 '19
Or is it?
Think about why Greg Maxwell would want to distance BSV from BCH. Why would he put the energy towards something like that, surely BCH could figure things out by themselves?
Why spin up and build a narrative against BSV? Odd to say the least.
2
u/500239 Apr 26 '19
Is this vincents brain talking or asshole?
I can't help but see anytime you post its dishonest or deceiving comments. Others have called you out for this as well. If anything you're the one stirring rumors and spinning a tall tale.
1
0
11
u/jonald_fyookball Electron Cash Wallet Developer Apr 26 '19
This thread absolutely infested with BSV sockpuppet minions. Probably half are the guy running the lonely sv sub. :(
1
0
Apr 27 '19
[deleted]
2
u/MarchewkaCzerwona Apr 27 '19
It was absolutely clear from very beginning, that block is supposed to be increased when needed and with technological advancement. If there is a problem with anything, it is logical to sort it first before going forward.
It is hilarious that you try to be sarcastic in here.
14
u/DaSpawn Apr 26 '19
the entire purpose of BSV is to confuse people by making it look like larger blocks "does not work" and/or Bitcoin "does not scale"
All the original attack/propaganda points for Bitcoin are just actually playing out now that Bitcoin has made it over 2 major hurdles, concerted well funded attacks and major expected/proper network upgrade
3
Apr 26 '19
the entire purpose of BSV is to confuse people by making it look like larger blocks "does not work"
Where did you pull that nonsense from?
2
u/anthonyoffire Apr 26 '19
I think "confuse" is putting it politely, as it leaves the most important bit out. They tried to take over BCH and force it to not scale. When they failed, the backup plan was to demonstrate how scaling by merely raising the block size doesn't work so that a strong narrative about on-chain scaling being nonviable could be spun.
-4
u/Vincents_keyboard Apr 26 '19
Wow, what?
I think you've got it wrong. Sorry.
The BCH community has just went through a good 6 to 9 months of Greg Maxwell stringing you along.
Think about that, many people here have been digesting his narratives day in day out.
3
u/BigBlockIfTrue Bitcoin Cash Developer Apr 26 '19
many people here have been digesting his narratives day in day out.
Unlike CSW's narrative w.r.t. bitcoin, I have no reason to believe Contrarian's narrative w.r.t. CSW is wrong.
2
u/DaSpawn Apr 26 '19
stringing you along
along with what? People seen through his BS long ago and is a large part of the reason BCH exists (we could see he was intentionally holding back Bitcoin)
-14
u/duggboy Apr 26 '19
Crikey, absolute quality example of Olympic standard mental gymnastics right here!
4
0
Apr 26 '19
[deleted]
6
u/mrreddit Apr 26 '19
BTC is claiming 1MB is too much. Noone is claiming BCHs 32 is enough or too high. Everyone on BCH is onboard with multi GB blocks someday.
0
Apr 26 '19
[deleted]
2
u/stale2000 Apr 26 '19
No, it instead depends on actually making sure the protocol scales, by deploying fixes.
We'll get to gigabyte blocks. Pretty soon. Once the protocol is made to work for it.
0
Apr 26 '19
[deleted]
3
u/stale2000 Apr 26 '19
Umm, the actual ability of the network decides?
Go try to create sustained 128 megabyte blocks right now. See what happens. (Hint, BSV isn't doing sustained blocks at that level).
What happens is that you start to see crazy high orphan rates. This was shown on the gigablock test initiative.
No amount of wishing changes the facts. And the facts are that at sustained levels of 128 blocks, the network starts to break down.
push the envelope of what's possible
Yeah, you say that, but everyone who is actually working to fix the problem, with things like CTOR and Graphene, get shit on.
We are working to fix this stuff.
0
Apr 26 '19
[deleted]
3
u/stale2000 Apr 26 '19
I used the specific word "sustained" for a reason. (Because I knew someone was going to bring up 1 or 2 blocks that were mined, but definitely were not "sustained")
Come back to me when the mainnet has a whole days worth of 128 MB blocks, all in a row, with a low orphan rate.
6
Apr 26 '19
BSV’s purpose is to continue demonstrating that a 32mb limit is way too low.
By loading video on the blockchain?
0
u/selectxxyba Apr 26 '19
If someone wants to pay to load data onto the blockchain and a miner is willing to accept it, that's a valid transaction.
1
Apr 27 '19
If someone wants to pay to load data onto the blockchain and a miner is willing to accept it, that’s a valid transaction.
Indeed,
The blockchain is incredibly poor fit for such usage tho.
Other project aim to do the same in much more efficient way.
Good the BSV chain seem to willing to take that usage..
13
u/LovelyDay Apr 26 '19
BSV's purpose is to continue demonstrating that a 32mb limit is way too low.
BSV's entire purpose is to demonstrate something the BCH community already takes for granted [1] and is engaged in doing?
Then BSV really doesn't have much going for it.
[1] https://www.reddit.com/r/btc/comments/b1bj4p/terabyte_blocks_for_bitcoin_cash_joannes_vermorel/
-10
u/Adrian-X Apr 26 '19
The Bitcoin community took for granted the 1MB would be lifted the same way the BCH community takes for granted the 32MB limit.
The BTC miners who didn't lift the limit will be moving to BCH if the price can accommodate them. When that happens, the same miners who failed to increase capacity will be mining BCH, and there will be more FUD than there was when the 1MB limit was enforced.
Expect another split. And like the last, this one won't be value creating.
The high capacity network will have establishes itself and miners can mine that if they want big blocks. Some call that network BCH SV.
8
Apr 26 '19
The Bitcoin community took for granted the 1MB would be lifted the same way the BCH community takes for granted the 32MB limit.
Well the BCH block limit is config file parameter.
There is no need for dev to lift it.
It is common knowledge.. have turned full troll?
15
u/Chris_Pacia OpenBazaar Apr 26 '19
32MB is enormous. It's likely more than all cryptocurrency volume combined. More than a payments company with a $127B market cap.
We are a long way from filling that capacity. Likely years if it's going to happen at all.
By the time we do fill that capacity we will have made it technically possible to raise the limit. Also remember all BCH nodes are designed to be able to lift the cap without the help of developers as it's just a command line option. So we are really of no risk the developers doing what the BTC devs did.
5
u/masterD3v Apr 26 '19
Just as a side note, I remember the old "there will be unlimited demand for blockspace" argument.
This is where the entire small-block argument originates from. BCH not having full blocks while also supporting them completely debases this argument.
9
u/Chris_Pacia OpenBazaar Apr 26 '19
That I never agreed with. There is a minimum relay fee (it's very low but it's still there) so transactions are not "free" thus there can't be unlimited demand.
-1
u/Vincents_keyboard Apr 26 '19
If you think 32MB is enormous you're a little girl.
You sound 100% like Adam Back, Jeff G, Greg Maxwell, et al. And by "et al" I mean BTC Core.
-2
u/Adrian-X Apr 26 '19
The size is irrelevant I thinkn1MB is too big I hate big blocks, but love what they alow.
What is important is understanding the incentives that balance, technical limitations, size utility cost and value?
What's as important is who decides! Is it the people who risk loss or a technocratic hegemonic authority who calls me incredibly dumb so as to dismiss my insights.
-7
u/Zarathustra_V Apr 26 '19
The same old ridiculous argumentation.
https://bitco.in/forum/threads/gold-collapsing-bitcoin-up.16/page-1429#post-92222
8
5
u/LovelyDay Apr 26 '19
Expect another split.
Calvinistas are gone now, if you wanna split, split BSV
Some call that network BCH SV
Only Core trolls and certain BSV morons who didn't get the memo about the ticker
0
Apr 26 '19
[deleted]
0
u/Vincents_keyboard Apr 26 '19
Don't you know, developers know best.
Can you believe that the guys over at SV want to lock in the protocol?! Gees! They won't have a job after they've locked it in!
/s
3
u/twilborn Apr 26 '19
I'm curious as to what is needed in terms of consensus changes to improve block propagation to comfortably handle 128mb + sizes.
I'm also curious as to whether avalanche would improve mempool synchronization and thus make even bigger blocks more feasible. (I've only heard it being talked about in the context of improving 0-conf reliability).
8
u/TypoNinja Apr 26 '19
From what I know the main bottleneck that was detected in the Gigablock Initiative was the mempool acceptance code, that was serialized. There have been efforts to parallelize it (BSV claims to have done and that it will go live in July, I'm skeptical), CTOR was supposed to make parallelization much easier and scalable. I'm looking forward to this bottleneck being lifted, with that and Graphene for efficient block propagation we should see blocks up to hundreds of MB.
1
u/throwawayo12345 Apr 26 '19
Flowee and BU have already tackled this.
1
u/TypoNinja Apr 26 '19
But I'm under the impression that they haven't released anything production ready, have they?
1
4
Apr 26 '19
I’m also curious as to whether avalanche would improve mempool synchronization and thus make even bigger blocks more feasible. (I’ve only heard it being talked about in the context of improving 0-conf reliability).
I have read some comment about that some time ago.
It curious too, avalanche can reliably keep large mempool in sync it immensely help graphen reliability.. that would be fantastic..
2
u/BigBlockIfTrue Bitcoin Cash Developer Apr 26 '19
In case of a set of unconfirmed, conflicting transactions:
Traditionally, you probably know only one of the transactions.
With double-spend relay, you know all of the transactions.
With Avalanche, you know all of the transactions, and you probably know which one will win too.
So both double-spend relay and Avalanche indeed speed up block propagation: when a block is found, you already know everything except the ids of the included transactions.
1
u/cryptocached Apr 27 '19
With Avalanche, you know all of the transactions, and you probably know which one will win too.
One of the unsolved problems for Avalanche preconsensus is how to securely disseminate the preconsensus state. Of course, even if you can know what the preconsensus state is, that doesn't ensure the PoW consensus will agree.
2
2
u/mrcrypto2 Apr 26 '19
To the trolls equating this to Blockstream blocking BTC size increase: Your argument would be more valid if current average blocksize was over 32MB and there is plenty of evidence that the network can handle blocks larger than 32MB, but the developers still said we need to "optimize" before adding size. Do you see the difference?
2
u/arbitrage10 Apr 26 '19
When 2 GB blocks are wreaking havoc on BSV, it’s good to know BCH will have reliable 300 kB blocks with the occasional 1-2 mb.
Then later when BSV is getting absolutely f’ed up with terabyte blocks, it will be comforting to know that BCH can safely handle 32 MB, when mass adoption inevitably happens.
1
1
u/cryptoplane Apr 26 '19
ah how refreshing , another post filled with angry people bickering until the end of time. This crap is the complete opposite of what you want to see for adoption and building respect and more investors. I get that we will see more of this with decentralized arch, but i can assure you the winners will not be dominated by what is found in this community. Non stop calling others out as incompetent and stupid, it only serves to make everyone look incompetent and stupid.
1
u/ngoaho Apr 26 '19
The narrative is pretty alike BS narrative huh?
3
u/mrcrypto2 Apr 26 '19
To the trolls equating this to Blockstream blocking BTC size increase: Your argument would be more valid if current average blocksize was over 32MB and there is plenty of evidence that the network can handle blocks larger than 32MB, but the developers still said we need to "optimize" before adding size. Do you see the difference?
0
u/HolyCrony Apr 26 '19
There are reasonably people on both sides, such as Jonathan Toomim for BCH and unwriter for BSV who would disagree on the approach to scaling. From my understanding the BCH side of the argument is that you should take a cautious approach and scale along with user adoption, while BSV side of the argument is that you have to scale now by learning through trial and error.
There are plenty of room for disagreement on this issue, but I personally agree with BSV's approach because it is much harder to scale an economic system if there are many vested interest at play. I mean, just look at the gridlock of BTC. Tackling a lot of the scaling pains now when there is little use and relatively low impact on the network seems like a good approach.
3
u/mrcrypto2 Apr 26 '19
If BCH can build the infrastructure to handle 50GB blocks while the ecosystem is small then that is a better approach than wait until we have 100MB blocks, then make a protocol breaking change that affects hundreds of billions of dollars of commerce.
2
u/Adrian-X Apr 26 '19
Hate can't stop progress so don't mind the downvotes.
I thought my comments were reasonable yet these received many downvotes.
0
-2
u/Adrian-X Apr 26 '19 edited Apr 26 '19
The "we" in that statement is not BCH. It's a central planning authority.
The engineering capacity testing they've done thus fare is a lie those are just words.
ABC lifted the limit from 8MB to 32MB without any testing the only implementation that did testing was BU and block sizes over 100MB were viable.
ABC had they done any "capacity engineering" would have found the bugs that Core introduced to limit transaction capacity to 7 tps. Before lifting the limit.
6
Apr 26 '19
The « w » » in that statement is not BCH. It’s a central planning authority.
Every implementation have some levels of centralization.
Not happy?
BCH is permissionless and ABC dev team HF every 6 months.
Easy, release a client that soft fork the 6 month HF schedule and cal for miner support ABC dev team is out.
2
u/SpiritofJames Apr 26 '19
It doesnt have to be. Why cant miners discover what the proper limit should be? Why do they need nannying?
2
u/edoera Apr 27 '19
BCH is permissionless
Do you even think about the words you speak? Please explain what "permissionless" means. Here are the facts:
At the end of the day ABC is defacto the dictator client.
All the rest need to "follow" ABC and even if they come up with some cool feature, they need to get "permission" from ABC to get them implemented into consensus. You've seen this in action with GROUP operator.
Bitcoin.com has shown it has enough connections with all the exchanges to coordinate an attack (which they call "defense") if there are issues. Now with Bitmain gone, this has become even more serious. Now everything can be vetoed by Bitcoin.com. Good luck
1
Apr 27 '19
Do you even think about the words you speak? Please explain what « permissionless » means. Here are the facts:
So far miner support the. ABC dev team.
Nothing prevents a new dev to attemps to soft fork the ABC implementation.
If miner support it, ABC is out.
In the same the Core used soft fork to quick competition out.
1
u/edoera Apr 27 '19
Sorry, wrong answer to the question "what permissionless means".
None of that has anything to do with "permissionless". Really, don't think superficially and think deep about what you're saying.
What you just listed is basically no different from "Nobody is forcing you to use the Lightning Network".
Moreover, it really has nothing to do with "permissionless", which literally means "doesn't require permission". You still need to get approval from ABC dev team to do anything meaningful on BCH chain, just like how you need to get approval from Blockstream and BTC Core dev team to do anything meaningful on BTC chain (Otherwise they throw stones at you), which is exactly what's happening on BCH chain with anyone who's thinking about heavily utilizing the ledger.
1
Apr 27 '19
Sorry, wrong answer to the question « what permissionless mean » ». None of that has anything to do wit« « permissionl »ss ». Really,’don’t think superficially and think deep about whatyou’re saying.
I am saying the BCH chain is permissionless not ABC.
ABC can authoritian as much as they want, they can be kicked out any time if miner feel so.
That just how blockchain cryptocurrency works.
What you just listed is basically no different from « Nobody is forcing you to use the Lightning Network ».
No.
Moreover, it really has nothing to do with « permissionles » », which literally mean« « do’sn’t require permission ». You still need to get approval from ABC dev team to do anything meaningful on BCH chain,
If you go by ABC rules, then it is permissioned yes.
Kicking ABC out requires no permission other than miner.
just like how you need to get approval from Blockstream and BTC Core dev team to do anything meaningful on BTC chain (Otherwise they throw stones at you), which is exactly what’s happening on BCH chain with anyone who’s thinking about heavily utilizing the ledger.
My point is valid for the Core dev team too.
They can kicked out of BTC and the way to do it it to release a implementation that fork them out and ask for miner support.
1
u/edoera Apr 27 '19
My point is valid for the Core dev team too.
They can kicked out of BTC and the way to do it it to release a implementation that fork them out and ask for miner support.
Sad, so THIS is what you're settling for? Same type of pathetic development as BTC? Good luck.
1
Apr 27 '19
Sad, so THIS is what you’re settling for? Same type of pathetic development as BTC? Good luck.
No.
If youread my comment you will see I showed how to get rid of such development team.
1
u/edoera Apr 27 '19
Yes I did. And your comment applies exactly the same for BTC. So what were you doing when BTC kicked out everyone who wanted to scale and people had to migrate to BCH?
Or do you actually think it is a "success" that the people who wanted to scale Bitcoin got kicked out of BTC and had to create a new coin?
1
Apr 27 '19
Yes I did. And your comment applies exactly the same for BTC. So what were you doing when BTC kicked out everyone who wanted to scale and people had to migrate to BCH?
I supported BCH, the soft fork activated HF was rather new and and never gain traction.
I don’t think anybody saw it as practical at the time.
Or do you actually think it is a « success » that the people who wanted to scale Bitcoin got kicked out of BTC and had to create a new coin?
No what I am saying is a soft fork is all that it takes for anyone that want to kick out any dev team.
ABC are the one taking the risk to HF every 6 months.
What I think personally is ABC dev are doing an outstanding job and the 6 months HF scheduled was a great idea. I doubt miner would support kicking them out.
-2
u/Evoff Apr 26 '19
Watching /r/btc having to pull arguments against bigger blocks is really fun. I guess we are "middle blockers" now
2
u/-Dark-Phantom- Apr 26 '19
Do you want to say that those are the same arguments that this community always had?
It was always said that you had to increase the size limit of the blocks so that they did not fill up and you also had to improve things in order to continue increasing them. Increasing them to an exaggerated size is imprudent, as demonstrated by BSV.
Maybe you were not paying attention.
2
u/BigBlockIfTrue Bitcoin Cash Developer Apr 26 '19
Bitcoin Cash has always avoided setting the limit too high. It launched with an 8 MB limit because of this.
-4
Apr 26 '19
"wreak havoc".... Good one!
2
u/Vincents_keyboard Apr 26 '19
Pretty hilarious right?
If anything it did "wreak havoc" on a few BCH developers credibility.
-1
Apr 26 '19
Yep. I guess /r/btc is now the "medium blocker" camp. They have no idea what's going on at BSV, yet assume they know everything. It's cute.
0
u/Vernon51 Redditor for less than 60 days Apr 26 '19
BCH is for peer to peer cash. We don't need huge blocks. 32 MB is more than we need.
10
u/TypoNinja Apr 26 '19
We don't need huge blocks yet. BCH will need larger blocks, just not right now. And the developers are working so the chain can keep scaling.
1
-1
Apr 27 '19
BchAbc sucks, Svbch does it better. Both still suck though. Both are still chinese copy coins.
-6
0
Apr 26 '19
[deleted]
10
Apr 26 '19
This is exactly the shit we heard years ago from another group.
ABC made the block limit a config file parameter.
They made that change so that the block can be changed without dev intervention.
We are not gonna have another block size crisis generated by crazy dev.
5
u/jessquit Apr 26 '19
This is exactly the shit we heard years ago from another group. Caveat emptor.
If Bitcoin Core had already hardforked to 8MB then 32MB before saying those things, we'd all still be singing kumbayah and signing up new users in rbitcoin.
2
u/mrcrypto2 Apr 26 '19
To all equating this to Blockstream blocking BTC size increase: Your argument would be more valid if current average blocksize was over 32MB and there is plenty of evidence that the network can handle blocks larger than 32MB, but the developers still said we need to "optimize" before adding size. Do you see the difference?
1
0
Apr 26 '19
[deleted]
5
u/mrcrypto2 Apr 26 '19
To the trolls equating this to Blockstream blocking BTC size increase: Your argument would be more valid if current average blocksize was over 32MB and there is plenty of evidence that the network can handle blocks larger than 32MB, but the developers still said we need to "optimize" before adding size. Do you see the difference?
17
u/tl121 Apr 26 '19
This is the correct technical approach. Networks with distributed control are subject to congestion collapse and with some designs even complete lockup. (Example, the Aloha experimental packet radio network.) To prevent this problem it is necessary to keep excessive traffic out of the critical portions of a network. However, this is only a partial solution, because if the users wish for more capacity than is available it will be necessary to expand the capacity or somehow discourage users from excessive usage. Given the goal of world-wide electronic cash, the only suitable option is to expand capacity.
Presently, the available hardware technology (processing, communications and storage) is more than sufficient for millions of transactions per second. The only limitation is the software which remains single threaded in many key places. This can be fixed, since most required computation is embarrassingly parallelizable.
The alternative approached, a layered approach, is unworkable as a method of increasing capacity. Layering was developed as a design approach to allow complex systems to be built that would otherwise exceed the mental capacity of a single human mind. They don't improve capacity: the base of a pyramid has to be broader than its top. In computer science and networking there have been many cases where layering has resulted in multiplicative inefficiencies. A simple flat one-layered approach avoids the pitfall of over enthusiasm, because most bottlenecks are relatively obvious and there are fewer edge case bottlenecks that can remain hidden for years, despite attempts at analytical modeling, simulation, and load testing.