Pages:
Author

Topic: it is Core, not Bitman blocking segwit - page 4. (Read 5420 times)

legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
April 07, 2017, 03:10:23 PM
#68
Ext Blocks only recently patched it to prevent ASICBoost use, and since then, Jihan will
no longer support that Ext Block proposal.

  Very interesting...  do you have a source?
legendary
Activity: 1092
Merit: 1001
April 07, 2017, 02:59:37 PM
#67
1. Jihan supported before understanding the final SegWit Implementation code. After learning the Coinbase references are used, he would obviously retract that support.
This is the same kind of idiotic argument I keep seeing around here.
The problem with your story is that you simply don't know what Jihan knew, and it was Greg who broke the HK agreement, not Jihan.
I know you tried your best to pretend to be logical, but in the end you just failed the simple common sense test. This is what happens when you have to make something sound 10 times more complex than it actually is.

First off, the fact that Jihan signed the HK Agreement doesn't mean anything of any value
in relation to this current ASICBoost issue. Second, Maxwell never signed the HK agreement,
so he could not have broken the agreement that he was not a party to. So, part of your "fact #1"
is not actually factual.

So, I'll give you 0.5 points for your first "fact". (0.5 out of 1.0)
Half a point because Jihan signed it, but that doesn't prove anything at issue.


2. Extension blocks do not change the Coinbase references, only add new anchor txs.
Those anchor txs should not effect the way ASICBoost works, the way new Coinbase refs do.
You're just trying to misdirect people without technical background here, the key to ASICBoost is the rearrangement of tx in a block, SegWit makes it costly to rearrange tx, so does Ext Block.
Granted there was still a little loop hole remaining in the tx in the canonical block, but it's so easy to fix, after Greg's crying, the Ext Block devs just eliminated the entire ASICBoost issue by adding 2 words in the Ext Block spec.
Just add a little extra crap to the merkle root calculation step, and ASICBoost instantly becomes a total non-issue, that is how small an issue this is, this is how weak your speculation is.

Sadly, you are the one misdirecting people.

You stated that your "Fact #2" was that Ext Blocks also blocked covert ASICBoost and
Jihan supports that, so you imply Jihan's innocence, since he would never accept the
Ext Block proposal if it also hurt the purported covert ASICBoost advantage and patents.
This is not a correct record of the events.
Ext Blocks only recently patched it to prevent ASICBoost use, and since then, Jihan will
no longer support that Ext Block proposal. Jihan only supported the Ext Block version that
allowed Covert ASICBoosting to remain intact.

So, I'll give you 0.0 points for your second "fact". (0.5 out of 2.0)
Due to being totally wrong.


3. This comment is jumping the gun. In depth investigations begin now.
And yours is a year late. The ASICBoost issue is over 2 years old, Core/Blockstream already cried about it a year ago, nobody gave a fuck. Stop pretending ASICBoost is some newly discovered game changing trick only Bitmain knew about until today.
30 Apr 2016 Luke Parker: AsicBoost claims 20% efficiency improvement in Bitcoin mining
13 May 2016 - ‏@olivierjanss: Note to miners: We, the core devs, discovered a patented optimization in your ASIC. We will make it obsolete in the next update.

Again, you are the one misdirecting people.

The issue of ASICBoost a few years ago, which I was around for, centered around the
community acknowledgment that Miners should not use it. In addition, Miners agreed
not to use it. The CURRENT ISSUE is that ASICBoost has been purportedly redesigned
to allow for covert ways to ASICBoost, which would be in violation of the community
and miner verbal agreements. I never claimed ASICBoost was newly discovered and
no one in the community is.

So, I'll give you 0.0 points for your third "fact". (0.5 out of 3.0)
Due to trying to arguing that no obvious evidence now, it proof of no wrongdoing.
That is equivalent to saying "there is no body now, so there was no murder ever".


4. This data set should be larger and go farther back in time. Likely prior to the patent dates.
The ASICBoost could be throttled from time to time to prevent obvious indicators.
So go ahead and gather older data then, you're the accuser here, the burden of proof is on you, so back up your accusations with facts instead of pure speculations, prophecies and red herrings.

Of course, the burden in on the community to determine if there is any evidence.

Your "fact #4" relied on faulty data and an incomplete examination of all the
data we could be analyzed. When you dismiss the current accusations outright
and cite a Twitter guy that only went back 3 months, that is disingenuous and
misdirection. We still need time to look over everything. It is likely, based upon
past Bitcoin events, within the next two months or less, someone will publish a
full scientific report either confirming, denying, or concluding that it is
indeterminable. As a Bitcoin supporter you should be interested in those results,
regardless of who is right. You shouldn't be prejudging.

Ultimately, you declaration that there is no evidence is very premature.
You may be correct in the end, but your "Fact #4" is not an actual fact yet.

So, I'll give you 0.0 points for your fourth "fact". (0.5 out of 4.0)
Due to it being not a "fact" and we will have actual "facts" in time.


5. Fees are irrelevant here. The exploit centers around gaining more block rewards.
In a future with less block reward and more fees, this exploit is worthless.
That fact was for the idiots who keep regurgitating the 'AntPool is using ASICBoost to mine empty blocks' bullshit script.

Again, you are the one misdirecting people.

Your "fact" implies that AntPool is innocent since they only profited 14% fees.
Ultimately, that statement is irrelevant entirely. ASICBoost is about cutting the
time down on finding blocks to gain the blockreward, not to gather as many fees
as possible. In addition, it may be possible with this new proposed covert ASICBoost
design, it could account for AntPools high empty block count. This may or may not
be correct, we still don't know. The community is still looking into this.

So, I'll give you 0.5 points for your fifth "fact". (1.0 out of 5.0)
Due to it being partial correct, but wrong as a "fact" to disprove the current accusations.


6. We need independent verification, which will begin now.
Blockstream already spent a year digging and got nothing solid on Bitmain. All Blockstream got is 'ASICBoost maybe used in the future', but it's obvious Bitmain/AntPool will be instantly caught if they actually use ASICBoost in any meaningful way that affect results.

Again, you are the one misdirecting people.

Your "fact #6", you stated that "Greg's math is wrong" which can not be a "fact"
and then you cited Bitman's public response to the current issue, which does not
cite any math or proofs as to why "Greg's math is wrong" or what is the math
determinations in general. I only stated that the community needs to begin
independent investigation. So this "fact #6" can't be a fact as well.

So, I'll give you 0.0 points for your sixth "fact". (1.0 out of 6.0)
Due to citing something that doesn't prove your asserted "Fact #6".


It would likely be best for you to stop quoting Alex.BTC since it is obvious that he
is not interested in learning anything, but perpetuating the obfuscations.
In time, all will be revealed. This is a new development and nicely explains many
previously unknown factors. If motive needed to be determined, this would be a
reasonable assumption to investigate further, and so the community will.
Your adherents to your viewpoints in light of new information still being gathered, is telling.
This is hilarious, all I did was post facts, and all you did was make speculations and then justify them by acting like some cult prophet talking bullshit prophecies  (read: Charles Manson/Heaven's Gate).
ASICBoost is an old issue, Greg is using it again as a distraction, get that through your head.

Here you go on to state that you provided "facts", yet as I have outlined above, your
"fact" score is around 1.0 out of a possible 6.0 facts. That is a lousy fact ratio.

Maybe the community should also investigate why your facts seem not to add up to what
the current evidence is and what it is currently pointing to. I would assume your high error
ratio has to do with being heavily biased in general and not having a problem with it, since you
are pushing an agenda that doesn't care about anything other than your own personal ego
and financial satisfaction. If you cared about Bitcoin and the community, you wouldn't post
those "facts" because they are self serving and a true distraction. "Nothing to see here guys".
"Don't try to look into any of the accusations, because there is no evidence. Case closed."

Talking about me acting like a cult prophet is laughable. Anyone can go back through my
post history and take a look if I have spoken like a prophet, alluding to communication with
God (or Satoshi, in this case), used people, attacked people, purposefully misconstrued info,
shilled positions that are unreasonable, fallen in line with "party" positions, or whatever. My
only allegiance is to the Bitcoin network and it's unencumbered unrestricted unregulated
future. The community can decide between both of us, who seems more reasonable and
genuine, and who is the bullshit artist.

The truth is that everything you are accusing me of is likely what you yourself is doing. I
haven't called you names, but if we are doing that now, I would advise you to read about
Jim Jones and The People's Temple. Since you think I'm acting like a false prophet or whatever,
I will prophesize that your future in the Bitcoin community and your false arguments will fall
along the same lines as what occurred with them. I see great disillusion in your future.
legendary
Activity: 4424
Merit: 4794
April 07, 2017, 01:40:15 PM
#66
But it sounds like you're saying Segwit might not have a chance, but support from miners is steadily rising, consistently above 30% for nearly a week now.

sorry to burst your bubble

 f2pool was good enough to have morals to admit something
meanwhile bitcoins segwit 31% block flagging is only temporary due to a hack expect it to drop back down below 30% in the next fortnight

https://twitter.com/f2pool_wangchun/status/848582740798611456
Quote
Wang Chun‏ @f2pool_wangchun

Someone hacked major mining operations and their stratum had been changed from antpool, viabtc, btctop to us. Our hashrate doubled instantly

10:07 am - 2 Apr 2017



legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
April 07, 2017, 01:29:17 PM
#65
Im tired of all of this talking, we need action now. We need to take out Jihan Wu, then we need segwit so we can enjoy lightning networks and sidechains, all other positions are incorrect.

i read this as:   I am a shill for Core/Blockstream.  Their scaling roadmap is the one true God.
legendary
Activity: 3430
Merit: 3080
April 07, 2017, 12:56:38 PM
#64
2m+segwit, why not?

Because it involves doubling MAX_BLOCK_WEIGHT as well as MAX_BLOCK_SIZE.

In practice, that means 2MB + 6MB, not 1MB + 3MB (Segwit BIP 141 as proposed).
What i meant in my whole post is that asicboost looks like an important issue to resolve.
Of course segwit would solve it, but it doesn't make consensus now and it can't be activated now.
So it is probably better to just stop asicboost from working and then go back to this old debate.

After asicboost has been stop working, jihan and other won't have any mean to activate it again and they might simply go on for segwit.

Yes, I broadly agree.

But it sounds like you're saying Segwit might not have a chance, but support from miners is steadily rising, consistently above 30% for nearly a week now.

Also, stopping ASIC Boost might cut Bitmain's hashrate share significantly (assuming they're actually using it, which is not an unfair assumption). Fear of getting their blocks orphaned by >51% of miners signalling Segwit might indeed change Bitmain's mind, they'd have little choice but to start signalling Segwit too, or they'd risk losing blocks and revenue.
the

I am really preaching against myself here because i am in favor of bigger block but i do not want to arguement that here because i already done that and it gives no result...

I'm not in favour of bigger blocks, but you will have your wish, when Segwit activates. I think 4MB blocks are a danger, especially since geopolitical tensions seem to increase every day (and more and more governments are using the tension to advocate putting more controls on the internet).

But I'm willing to compromise with Segwit. If you don't think 4MB blocks will be enough today, I don't know what compromise any of us could agree to.
legendary
Activity: 1204
Merit: 1028
April 07, 2017, 12:52:24 PM
#63
Im tired of all of this talking, we need action now. We need to take out Jihan Wu, then we need segwit so we can enjoy lightning networks and sidechains, all other positions are incorrect.
legendary
Activity: 892
Merit: 1013
April 07, 2017, 11:59:06 AM
#62
2m+segwit, why not?

Because it involves doubling MAX_BLOCK_WEIGHT as well as MAX_BLOCK_SIZE.

In practice, that means 2MB + 6MB, not 1MB + 3MB (Segwit BIP 141 as proposed).
What i meant in my whole post is that asicboost looks like an important issue to resolve.
Of course segwit would solve it, but it doesn't make consensus now and it can't be activated now.
So it is probably better to just stop asicboost from working and then go back to this old debate.
After asicboost has been stop working, jihan and other won't have any mean to activate it again and they might simply go on for segwit.


I am really preaching against myself here because i am in favor of bigger block but i do not want to arguement that here because i already done that and it gives no result...
legendary
Activity: 924
Merit: 1000
April 07, 2017, 11:58:35 AM
#61
2m+segwit, why not?

Because it involves doubling MAX_BLOCK_WEIGHT as well as MAX_BLOCK_SIZE.

In practice, that means 2MB + 6MB, not 1MB + 3MB (Segwit BIP 141 as proposed).

But what i understood is that it would not stop asicboost to work...

No, that's the whole point behind Antpool/Bitmain blocking Segwit (apparently). Segwit activation would stop ASIC Boost working, because of the way Segwit changes the coinbase structure in blocks. Blocking Segwit would allow Bitmain to continue covert ASIC Boosting, although we haven't got direct evidence that Bitmain are using it (but a range of highly suspicious indirect evidence, of course, exists)

I haven't seen any direct evidences from anyone so far about anything. All i see is opinions, accusations, etc. Hence this debate rolls on and on and on boring me to near death.
legendary
Activity: 924
Merit: 1000
April 07, 2017, 11:56:00 AM
#60
Quote
some devs have found a clever hack which they can use to make BTC TX and NOT pay miners a TX fee
we should enact a USHF to prevent this hack from being exploited, the security model of bitcoin itself is in jeopardy!!

Sources?
legendary
Activity: 3430
Merit: 3080
April 07, 2017, 10:04:34 AM
#59
They secured a patent and wrote functions to use it, but there is no actual proof (such as transaction re-ordering) that they have been using it. 
Why would they spend money building compatible hardware only to *not* use it? Anyone can see that this logic makes no sense.

Even so, there still isn't any proof. But I agree, it's highly likely Bitmain are mining empty blocks to make use of ASIC Boost. They've admitted it's there in the ASICs, but deny using it. The BIP to remove covert ASIC Boosting should still happen of course, but there genuinely is no proof it's being used, just some highly suspicious circumstantial evidence, it's not called covert ASIC Boosting for nothing.
legendary
Activity: 2674
Merit: 2970
Terminated.
April 07, 2017, 09:45:17 AM
#58
Is he really not open to others opinion? his vision seems to be the only one and nothing else Undecided
Unfortunately this is the case for the supermajority of the population as well as as good portion of the Bitcoin users ("even those thinking they are *awake*").

IF it can be proven they have been using it while claiming they weren't, I would say that is dishonest and deceitful and harmful to Bitcoin, absolutely.   
I'm pretty sure that it is extremely hard/possibly impossible to detect covert usage (which Segwit would prevent).

They secured a patent and wrote functions to use it, but there is no actual proof (such as transaction re-ordering) that they have been using it. 
Why would they spend money building compatible hardware only to *not* use it? Anyone can see that this logic makes no sense.

The fact that they did agree in the HK to segwit+8mb or segwit+4b whatever it was plus the fact that Jihan said (before this 'scandal') that he supports extension blocks (also incompatible with asicboost) supports the idea that they indeed haven't been using it. 
HK was neither +8 MB nor + 4MB. There was never an exact number specified.
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
April 07, 2017, 09:41:05 AM
#57


Mining pool operators clearly have no interest in scaling Bitcoin at this juncture.

Miners have all the interest in scaling Bitcoin. If Bitcoin does not scale it will not survive and miners have vested interest in Bitcoin.
 

Holliday has made his position clear to me:  He thinks Bitcoin will be fine with low TPS and it will still be valuable as a kind of digital gold.
legendary
Activity: 1512
Merit: 1012
April 07, 2017, 09:35:01 AM
#56
THey were codding and making analysis that 1MB segwit will make effective 2MB increase.
simple 2MB just increase is damaging for network and would lead to decreasing number of nodes.
Also 2mb block would lead to hardfork and when you have tons of apps stop working.
1MB segwit is solving problems with old soft compatibility.

SegWit will make an effective increase if/when someone jumps on board.

And what "old soft compatibility" issues does SegWit solve? If you're referring to what's described here, that's not really solving anything.

To get VISA transfers you need about 1000MB blocks , you can do it in paypal mysql database but not in decentralized network.

Of course one can't. At least for now.

And you won't care when Jihad will lift limit of 21m

I guess nobody will care, they can go on with their own altcoin if they so desire, but that's not really on the scope of this subsection of the forum.

Here is a life lesson for you: Ignore what people say and watch what they do.

Good lesson.

Mining pool operators clearly have no interest in scaling Bitcoin at this juncture.

Miners have all the interest in scaling Bitcoin. If Bitcoin does not scale it will not survive and miners have vested interest in Bitcoin.

If Miners are allowed to continue with ASICBoost, Bitcoin
development ends in many fundamental ways.

Well then, it's not hard to figure out what miners will opt for Smiley
legendary
Activity: 3430
Merit: 3080
April 07, 2017, 09:33:18 AM
#55
2m+segwit, why not?

Because it involves doubling MAX_BLOCK_WEIGHT as well as MAX_BLOCK_SIZE.

In practice, that means 2MB + 6MB, not 1MB + 3MB (Segwit BIP 141 as proposed).

But what i understood is that it would not stop asicboost to work...

No, that's the whole point behind Antpool/Bitmain blocking Segwit (apparently). Segwit activation would stop ASIC Boost working, because of the way Segwit changes the coinbase structure in blocks. Blocking Segwit would allow Bitmain to continue covert ASIC Boosting, although we haven't got direct evidence that Bitmain are using it (but a range of highly suspicious indirect evidence, of course, exists)
sr. member
Activity: 812
Merit: 250
A Blockchain Mobile Operator With Token Rewards
April 07, 2017, 08:57:07 AM
#54
some devs have found a clever hack which they can use to make BTC TX and NOT pay miners a TX fee
we should enact a USHF to prevent this hack from being exploited, the security model of bitcoin itself is in jeopardy!!
full member
Activity: 1414
Merit: 129
The first decentralized crypto betting platform
April 07, 2017, 08:48:40 AM
#53
Core won't even compromise to 2mb/segwit, which
probably could get consensus.  
You're right, they won't, which is why it's an interesting coincidence that Bitmain would support SegWit only in the circumstances which you believe won't happen.  They're taking advantage of Core's unwillingness to compromise by implying that they would support SegWit in other situations.
legendary
Activity: 892
Merit: 1013
April 07, 2017, 08:47:45 AM
#52
If we stop them using asicboost, they still have some substantial money invested in bitcoin mining.
So the second after asicboost is rendered useless, they might change their opinion and seek diferent consensus. This is very relevent.

2m+segwit, why not? But what i understood is that it would not stop asicboost to work...
So why not bip anti asicboost and then see if 2mb + segwit get traction ?
legendary
Activity: 3430
Merit: 3080
April 07, 2017, 08:42:46 AM
#51
Wauw, all kinds of people are trolling and shilling....

Fact is, I'm open to many scaling proposals:

Bitcoin Original
Bitcoin Classic
Bitcoin Unlimited
Lightening Network
Bitcoin CoreEC
Flexcap
Extension Blocks



hmmmm..... except those are all capacity change proposals, not scaling proposals. Who's the sh(r)ill troll, jonald fyookball?
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
April 07, 2017, 08:36:15 AM
#50
Wauw, so many people tried explaining all kind off things but Jonald keeps putting his fingers in his ears..

Is he really not open to others opinion? his vision seems to be the only one and nothing else Undecided

Wauw, all kinds of people are trolling and shilling....

Fact is, I'm open to many scaling proposals:

Bitcoin Original
Bitcoin Classic
Bitcoin Unlimited
Lightening Network
Bitcoin CoreEC
Flexcap
Extension Blocks

I would even compromise with Segwit-HF + bigger blocks.

Core Devs and their supporters seem to be the ones unwilling to be open to others opinion and unwilling to compromise.
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
April 07, 2017, 08:30:13 AM
#49
You didn't answer my question at all... I'll restate it another way: Regardless of whether you think its related, or what they support, or whether anything was deflected,
how would anything change in the scaling debate even if they did admit they were using asicboost?
It doesn't change much

Glad we agree on that.

Quote
 Therefore, you as a rational (assumption) individual along with other rational individuals would condemn their behavior.
 

IF it can be proven they have been using it while claiming they weren't, I would say that is dishonest and deceitful and harmful to Bitcoin, absolutely.   They secured a patent and wrote functions to use it, but there is no actual proof (such as transaction re-ordering) that they have been using it.  They may have merely prepared to use defensively if other miners started using it.  The fact that they did agree in the HK to segwit+8mb or segwit+4b whatever it was plus the fact that Jihan said (before this 'scandal') that he supports extension blocks (also incompatible with asicboost) supports the idea that they indeed haven't been using it.  Also my understanding from reading a r/bitcoin thread is that it requires a pool to allow and there's no evidence of antpool or any other pool allowing it.

Anyway , I would support a BIP to block asicboost generally speaking.  Not really that interested in further debate on it.   Have a good weekend.

 
Pages:
Jump to: