The LTB Network Forum


Upcoming Bitcoin Hard Fork & /r/bitcoin censorship

Back to Bitcoin & Beyond

Jump to bottom

Comments

  • adam

    @shmadz @Adam afaik they intend to increase blocksize using BIP 101

    "Proposal to increase maximum possible block size, starting at 8MB in January 2016 and increasing on-pace with technological growth to 8,192MB in twenty years."

    This is the part that scares me. Increasing block size is not a solution to scaling, it is a stopgap.

    While I agree that 1MB is too restrictive, there must remain some kind of scarcity in the blockchain, otherwise you are opening up an entire new vector of attack. (Likely the kinds of spam attacks that the limit was implemented to mitigate in the first place) (Not even gonna get into miner rewards and how do you run a fee market if there is no scarcity)

    The initial spam attacks that necessitated the 1mb limit seemed to have more to do with the incredibly low value of btc and no dust limit thus making it really easy to do those fill-up-blocks spam attacks. I don't think that would come back just by adding more capacity

    If everyone agrees raising the block size isn't a final solution, it actually makes sense to codify something like BIP101 so that you dont have to have this argument every two years.

    As far as the economics of miner fees are concerned, I find myself thinking we've got a long way yet to go in terms of adoption and real use before I think fees can reasonably go up from where they are now. Even right now without full blocks the cost is about 2 and a half cents per tx which is not nothing and certainly not as cheap as it used to be. The next few years should be major ones for adoption, predictable low costs are important to that.

    Permalink
    1 like
  • dpc

    Two things pop out.

    1. Bitcoin is not a place for those who fear change. It is still a beta product, no matter how amazing or world changing we think it is. Many changes are yet to come if bitcoin is going to thrive.
    2. Large mining operations already make small miners irrelevant when it comes to hashing-power/voting/etc... This change would make that fact more obvious, but it doesn't change the nature of the current landscape.

    Stopgap solutions are the way things evolve. It's not always a bad thing. Sometimes evolution is best, other times revolution is necessary. Status quo is rarely a good survival strategy.

    Permalink
    3 likes
  • adam

    @maxentropy Anyone who is working in software development will understand that Hearn and Andresen are hi-jacking the Bitcoin project. Hearn's argument in Medium today, is not believeable and not relevant, as he does not discuss the complete set of code changes in his XT version.

    These are my thoughts:

    1: Given that Andresen is currently a salaried employee of MIT and that he is presumably responsible for the other developers of the Bitcoin Core software - it is bizarre that MIT would let this employee function in the manner that Andresen does.

    What do I mean:

    A: Andresen literally throws his project and the development group under the bus, in order to switch to the Bitcoin XT version which is run out of London by Hearn.

    B: Andresen opens the Bitcoin network up to code changes that are way beyond that of the Block Size feature, as Hearn has made 100+ code changes to Bitcoin fork since 2014 December.

    C: Andresen os offshoring the Bitcoin development to London, England. Sure, you can say that the developers are global, but what is clear is that Bitcoin product control (arguably) has moved from the Bitcoin Foundation (California), to MIT (US East coast) to Lomdon, if Bitcoin XT is adopted.

    I don't really think Gavin or MIT view him as an employee under their control, when I've spoken with Gavin about the relationship it seems like its the equivilent of "how gavin gets paid to do bitcoin" and the specific institution is largely irrelevent, he didnt even remember his official job title - I really doubt they have much control over him at all

    2: Andresen appears to have lost control of the Bitcoin Core developers at MIT, and has thus jumped to the only other implementation of significance. If this is true, then we should dig into the issues at MIT.

    Is there any possibility Gavin is pushing for the correct solution and in reality the developers you define as no longer being under Gavins control are just wrong in their opposition for whatever reason?

    3: Andresen has shown that he is not capable of leading developers, projects, or holding the respect of the community. If Andresen had access to a compiler he could have taken the initiative and developed specific Block Size features himself. This did not happen. If there is a move to Bitcoin XT, then Andresen will be a poster child for the new XT software in the U.S., while the real control will be in London. Again, sure the developers can be global but the control will reside in London.

    How has he shown this? Can you link to anything? - Why is development any less centralized with two voting developers compared to five? are they both really centralized by any standard? Why does "Andresen being a poster child for XT but control lies in London" matter?

    4: Who is funding Hearn? It is time to look into who Hearn's group of developers and advisors are.

    Do you also have this curiousity for who is funding developers supporitve of the no-block-increase school of thought? Seems like everybody is obviously operating in what they perceive to be their own best interest in both camps.

    Hearn's Medium letter of 2015 August lacks merit.

    I thought he made a pretty compelling case, what specifically did you find lacking in merit?

    Permalink
    0 likes
  • ademczuk

    You would know @adam as you have been the first to see layer 2 transaction costs. Comparitively Ethereum has yet to solve the greedy market btc overcame a few years ago. If that helps your resolve. Personally if I can survive a game of "the floor is lava" like you are currently up against i am envious.

    Permalink
    0 likes
  • cmason

    @maxentropy Anyone who is working in software development will understand that Hearn and Andresen are hi-jacking the Bitcoin project. Hearn's argument in Medium today, is not believeable and not relevant, as he does not discuss the complete set of code changes in his XT version.

    I have a feeling that I don't like.

    These are my thoughts:

    1: Given that Andresen is currently a salaried employee of MIT and that he is presumably responsible for the other developers of the Bitcoin Core software - it is bizarre that MIT would let this employee function in the manner that Andresen does.

    Linux has been funded by various companies over the years, some don't even exist anymore. Was this a conspiracy, or was he just trying to do the job while being paid enough to support his family?

    Everyone hated the Bitcoin Foundation, so it died and other funding was established. Why is this bad?

    What do I mean:

    A: Andresen literally throws his project and the development group under the bus, in order to switch to the Bitcoin XT version which is run out of London by Hearn.

    Where and how did this happen?

    B: Andresen opens the Bitcoin network up to code changes that are way beyond that of the Block Size feature, as Hearn has made 100+ code changes to Bitcoin fork since 2014 December.

    Someone with orignially unique commit access made changes to the code. Isn't that his job? If you are criticizing his opening up of committ access, I agree that this was premature.

    C: Andresen os offshoring the Bitcoin development to London, England. Sure, you can say that the developers are global, but what is clear is that Bitcoin product control (arguably) has moved from the Bitcoin Foundation (California), to MIT (US East coast) to Lomdon, if Bitcoin XT is adopted.

    As a Canadian, I'm not too invested in this, but I don't understand the concern with global collaboration. I think this is a good thing. Are you offended if Bitcoin development were to move "offshore"? Why?

    2: Andresen appears to have lost control of the Bitcoin Core developers at MIT, and has thus jumped to the only other implementation of significance. If this is true, then we should dig into the issues at MIT.

    Who gives a shit?

    3: Andresen has shown that he is not capable of leading developers, projects, or holding the respect of the community. If Andresen had access to a compiler he could have taken the initiative and developed specific Block Size features himself. This did not happen. If there is a move to Bitcoin XT, then Andresen will be a poster child for the new XT software in the U.S., while the real control will be in London. Again, sure the developers can be global but the control will reside in London.

    Um, he just produced a new version, your statements contradict themselves. This is not a popularity vote, just pick the software you want and stop grandstanding.

    4: Who is funding Hearn? It is time to look into who Hearn's group of developers and advisors are.

    Doesn't matter. Even if the Koch Brothers were funding him. You seem to have a problem making a rational decision.

    Permalink
    0 likes
  • adam

    Thanks to @bcohen for pointing me to twitter where much of the anti-xteffort seems to be focused.

    I have followed this from the beginning & I agree that it is an attempted governance coup. #NoPropagationWars https://t.co/Qs43Ho50IX— Jon Matonis (@jonmatonis) August 16, 2015

    @iang_fc @adam3us That's why I said "attempted" governance coup.— Jon Matonis (@jonmatonis) August 16, 2015

    @mola_io @pierre_rochard However, it won't get adopted...at least not via that channel. In the meantime, s/w propagation war is dangerous.— Jon Matonis (@jonmatonis) August 16, 2015

    @mola_io @pierre_rochard Bitcoin is anti-fragile, but "suggested" changes fought via propagation degrade confidence and cause uncertainty.— Jon Matonis (@jonmatonis) August 16, 2015

    @mola_io @jonmatonis the open source metaphor breaks down quickly. A better example of "open source forking" is litecoin— Pierre Rochard (@pierre_rochard) August 16, 2015

    @mola_io @jonmatonis because it is de facto winner-take-all, like if everyone was forced to upgrade to python3— Pierre Rochard (@pierre_rochard) August 16, 2015

    @jonmatonis @pierre_rochard And I say "Yay! If it can be broken, break it now" Bitcoin ought not be treated gingerly like a feeble old woman— DI$RUPTIV3 (@BitcoinBelle) August 16, 2015

    @jonmatonis imo it's sabotaging. If they want an alt they can make their alt. Instead they want to rape btc.— bitcoinaire (@bitcoinaire) August 16, 2015

    Permalink
    1 like
  • peasant-wizard

    Like others, I look forward to Andreas' opinion.

    I get the feeling this is being dramatized for all sorts of ridiculous reasons. There seem to be a suspiciously disproportionate amount of non-technical people upset right now.

    Bottom line for me is: crypto is here and I'm all in, financially and emotionally. BTC is my first love but that's a classic story that can have a sad ending. Nothing wrong with having an escape plan, and we are fortunate that right now there are real alternatives.

    Life's greatest recurring challenge for me has been adaptability. Stay alert and equanimous, find where you fit into this and don't force yourself into a role or opinion your not suited.

    Whatever happens, I'm participating, and I'm increasing my holdings in BTC or another crypto. Anything is better than CAD!

    Permalink
    1 like
  • MaxEntropy

    Adam raises valid objective questions... Adam says:

    Is there any possibility Gavin is pushing for the correct solution and in reality the developers you define as no longer being under Gavins control are just wrong in their opposition for whatever reason?

    --

    A software development group, developers, and management would never throw their code base over for a competing system. They would seek an incremental solution to problem with a code base that introduces the LEAST amount of risk, to the solution to the problem - Block Size; and to the overall system.

    Developers always introduce bugs with code changes.

    --

    So while your question, Adam, is constructive, it remains bizarre to the observer that Bitcoin Core guys would drop their work and jump on board for another system - just to fix a narrow Block Size issue.

    Bumping the Block Size can not be that difficult.

    --

    Something much larger is at play.

    Permalink
    1 like
  • astantoid

    i am update.. now, active on forum

    Permalink
    1 like
  • Cryptonaut

    @ademczuk I appreciate the alert but as a casual user I can see that Mike hearn (or whomever he represents) has created a problem to solve. @adam If XT cannot solve scaling then this fork is an attack.

    The apache tribe was defeated by admiting that they could only survive by centralising their livestock. You tought me this in your first 20 episodes.

    There is no such thing as "solving" scaling - it's a sliding scale, hence the name. We can't expect to just wait around until we figure out a solution that will let us go from the current 100,000 transactions a day to 7,000,000,000,000+ transactions per day instantly. We still have to get to the 1,000,000 and 10,000,000 per day mark, and the easiest and most obvious way to do that right now is to increase the block size limit, which has already previously been raised (everyone was using lower soft limits before) in similar situations of increasing TX volume.. So what we are talking about is keeping things business as usual for the next several years, and then we can work on figuring out how to get to a hundred million or a billion+ transactions per day. Additional nodes on the network come naturally with the adoption (main reason nodes have been going down up till now is actually the transition from hosting the blockchain yourself to just using SPV wallets like Mycelium)

    @shmadz

    Welcome Mike as our new bitcoin overlord? This feels wrong.

    Wrong? Mike (and Gavin, apparently) just wants to get more than 75% of nodes to all use the same client. A client that he has complete control over.

    Once the switch is made, it will make it easier for Mike to roll out some of his other pet projects. Perhaps we get redlists with v11.1?

    And I haven't heard anyone mention the second part of the protocol change, the doubling every 2 years...

    What could possibly go wrong?

    Edit @Adam - re: "benevolent dictator or deadlock" .. how can you be sure that Mike Hearn is benevolent? Or that once he is given the keys to the kingdom he will stay that way?

    That's true, but you can say that about anyone. I can sit here and pick apart 10 ideas from Greg Maxwell that I don't like, so why should I trust Core? Anyways I'm pretty sure Mike knows by now if he actually tried implementing stuff like that, people would lose their shit, plus a lot of his other ideas seem to just be him thinking out loud, rather than seriously "I'm going to do this". Either way, it doesn't matter because if BitcoinXT turns into the same sort of deadlock, or goes rouge and actively includes tools for censorship or w/e, then today's story will just repeat itself and you will see a movement to BitcoinZY or whatever else. Maybe that's inevitable, it only took about 5 or 6 years for it to happen to the Core project, so it could be a cycle :p

    @adam

    And I haven't heard anyone mention the second part of the protocol change, the doubling every 2 years...

    I don't know anything about this, link or any light you can shed?

    Yeah, every 2 years the cap doubles, for 20 years until it reaches 8GB IIRC. So in 2018 the cap will be 16MB, 2020 it will be 32MB and so on. Miners still have their soft limits though, so realistically no one is going to be mining blocks that don't make sense to mine. There is also another catch there though... the legacy network protocol has a fundamental limit of 32MB, so eventually it is going to need to be rewritten and there will need to be a hard fork. Gavin mentions this briefly in his scalability roadmap he posted last year http://blog.bitcoinfoundation.org/a-scalability-roadmap/

    @twebit What ever happened to the hard fork policy at bitcoin.org? https://bitcoin.org/en/posts/hard-fork-policy Does the XT violate this policy? Always wondered?

    Yeah, XT is actually precisely what they are referring to in that post, they just don't outright say it. There is a big argument about it on github.. Pretty much same day that Gavin had originally said he would move over and post the patches to XT if no consensus could be made, they posted that as a pre-emptive move.

    @adam

    @twebit What ever happened to the hard fork policy at bitcoin.org? https://bitcoin.org/en/posts/hard-fork-policy Does the XT violate this policy? Always wondered?

    I emailed Gavin for comment on this - One important question is who actually does this apply to? Bitcoin.org isn't an "official" anything, just another site on the internet that can pick what info it displays

    So the 'official" policy might just mean it won't be linked from bitcoin.org

    Also worthy to note that the same people that run bitcoin.org are the ones that run /r/bitcoin, bitcointalk.org and the "official" bitcoin wiki. Good ole Theymos and friends..

    Permalink
    1 like
Jump to top

Post Reply

Please Login to post a reply to this thread.

© Copyright 2013–2016 The LTB Network. All rights reserved .