link0 link1 link2 link3 link4 link5 link6 link7 link8 link9 link10 link11 link12 link13 link14 link15 link16 link17 link18 link19 link20 link21 link22 link23 link24 link25 link26 link27 link28 link29 link30 link31 link32 link33 link34 link35 link36 link37 link38 link39 link40 link41 link42 link43 link44 link45 link46 link47 link48 link49 link50 link51 link52 link53 link54 link55 link56 link57 link58 link59 link60 link61 link62 link63 link64 link65 link66 link67 link68 link69 link70 link71 link72 link73 link74 link75 link76 link77 link78 link79 link80 link81 link82 link83 link84 link85 link86 link87 link88 link89 link90 link91 link92 link93 link94 link95 link96 link97 link98 link99 link100 link101 link102 link103 link104 link105 link106 link107 link108 link109 link110 link111 link112 link113 link114 link115 link116 link117 link118 link119 link120 link121 link122 link123 link124 link125 link126 link127 link128 link129 link130 link131 link132 link133 link134 link135 link136 link137 link138 link139 link140 link141 link142 link143 link144 link145 link146

Bitcoin Scaling: Jeff Garzik AsicBoost Comments Lead to Frustration

Bitcoin Scaling:
Jeff Garzik AsicBoost Comments
Lead to Frustration

    

Bitcoin Core developer

Jeff Garzik has sparked contention with a post asking if further measures were needed to prevent covert AsicBoost. Addressing the work group (WG) on Github, Garzik put forward a selection of next steps aimed at “testing protocol/software changes that ban/disable/render ineffective this hardware optimization.” However, fellow contributor Greg Maxwell responded accusing Garzik of attempting to allow AsicBoost to, in fact, continue under his “modified version” of Segregated Witness with a hard fork.

Maxwell wrote:

“So to be clear about what you've written between the lines: you have decided that impeding covert asicboost would be a violation of the "SegWit2x charter" and so you will assure that covert asicboost continues to function in your modified version of segwit and HF as people have been alleging you would do? This will require further departure and incompatibility with the segwit proposal.”

Infighting among Core members has continued on the topic of Bitcoin’s future following Barry Silbert’s attempt to ratify an agreement which would see SegWit introduction in September followed by a cooling-off period for a block size increase to 2 MB. Reactions have been mixed, while practicality problems on the Bitcoin network are resulting in greater user calls than ever to initiate a binding solution. Garzik, meanwhile, faced pressure to state whether he intends to have AsicBoost disabled. “Anything that was not discussed is, by definition, A New Issue To Raise And Discuss. Which is what was done here,” he wrote.

Chuck Reynolds
Contributor
Please click either Link to Learn more about –
TCC-Bitcoin.

 

Alan Zibluk Markethive Founding Member