Then wtf was the point of the meeting? Just a few dev hanging around stroking each other's dicks?

There was a huge blocksize debate at the time, pressure was on Core to increase the blocksize limit, Blockstream/Core fucked everyone over by pretending to support 2MB block increase.
 
If nothing was agreed upon, then there would have been another meeting for the blocksize issue, but nope, Blockstream/Core played everyone, now nobody trust anything they say.


Now you're just shilling for Blockstream/Core.
The fact is the exact opposite. Blockstream/Core is still fucking everyone over by keeping blocksize at 1MB.

SegWit gets merged by Core without a word (and still have less support than BU).
Blocksize increase pull request instantly get closed by Blockstream co-founder on Github.


That's the problem with you trolls, you spending too much time on personal attacks and too little on facts.

I just don't like watching people going around making idiotic statements with zero proof then act like they are some kind of know-it-all authority on the future. If you have a theory, post it as a theory, don't state it as a matter of fact, then go for bullshit gymnastics and personal attacks when someone ask you for proof.


If you play with timezones I am sure you can pull out different numbers.

But that is just more of the same nitpicking on trivial bullshit.

At the end of the day you just don't know what the exact time was when Jihan learned about Extension Block, and the exact time when he decided to support it, it could have been hours it could have been days.

The history of Extension Block is here:
https://medium.com/purse-essays/extension-block-story-619a46b58c24

The first commit of Extension Block was on Mar 23, 2017, it was a small commit, just a few lines, and it reads:
"This repository contains the specification for extension blocks with a BIP141 ruleset"

This proves Extension Block is base on BIP-141 right from the get go, so it was immune to ASICBoost right from the start, not hours or minutes ago.

I actually asked Christopher wtf was he doing on that botched edit, he said the edit was strictly within the context of the new stuff in extension block only, not the regular stuff, and he said he removed that line because it was redundant and overall the edit changed nothing.

Christopher wasn't aware of ASICBoost until Greg's proposal, he simply didn't know how it works, so he didn't know BIP-141 already implied ASICBoost immunity. His knee jerk reactionary edit later changed nothing, Extension Block was already immune to ASICBoost right from the start.

And it didn't matter what Chris knew, Jihan would know what BIP-141 means for ASICBoost.

This ASICBoost distraction is just a total bullshit, regardless of what Jihan did, if the code allow this shortcut, then any miners can build their own ASIC to use that shortcut, Jihan's patent only forbids others from selling it in China, not forbidding miners from building their own, so fix the damn code instead of blaming other people.


The blocksize increase is the true issue, it has been for over a year, because it affects everyone's bottom line. It is ignorant for you to use tunnel vision and pin everything on ASICBoost when Jihan will also profit from a blocksize increase, there are many things in play here.

It doesn't matter who Jihan is, I expect him to do everything he can for his business, and right now he's speaking the truth and he's openly opposing BlockStream, and his words make sense, that's good enough for me.

That's what I don't like about you trolls, the blocksize limit is fucking up the network right now, it's already happening, and instead just acknowledging it, you idiots circle jerk around the issue then keep pointing fingers at someone else. Blockstream/Core is clearly the culprit here.



You said Jihan have already used ASICBoost in production.
I asked you for proof.
You went for personal attack.
I out trolled you back.
Now you want a report?
What are you even on about?

You made the accusation.
I haven't seen any evidence.
So I asked you for them.
You talked shit.
So I dug a little, I found data that went against your claim.
So I showed that data to you, and asked you for evidence for your accusations again.
You tried to act like a smart ass, knowing full well you had nothing.
And instead of just man up and admit that.
You started 'lol'ing at the data I found.

It's like you have no idea how stupid you actually look.
And the funny part is you actually think people can't see through this shit.
Like at this point any of your insults actually do anything.

What's with the smartass teenager act anyway? Obviously you're not a teenager, who the fuck is going to respect some loud mouth finger pointing dumb fuck who can only ever talk shit.

Yeah Extension Block being based on SegWit doesn't sit well with me either. Who knows if it's just some kind of good cop bad cop routine.

But the Bitcoin well has been poisoned by BlockStream/Core so badly, anything that can immediately get the blockchain out of their death grip is a plus, hopefully after the great escape, there will be big diversity on implementations, then someone come up with a truly great and open solution from scratch.

This whole ASICBoost bullshit is yet another distraction from Blockstream/Core keeping the blocksize at 1M and screwing everyone else over.

ASICBoost was out of the bag ages ago, patents don't stop any nameless mining farm from building their own ASICBoost rigs. If Core don't like ASICBoost, they should just fix the damn code instead of crying about it every year.

The ASICBoost write paper used way too much tech jargon, and when it comes to implementations all you get is "We will not discuss the optimal solution in this paper, but further information can be provided by the author on request."

So a year later half the devs still don't know how it works, if the devs can't even figure it out, it'll be even worse for users, so you end up with all these trolls trying to get away with making the most ridiculous statements, creating new enemy-of-the-week trying to distract people from Blockstream/Core's own fuck ups.

ASICBoost is:
1. A programming short cut of using 3 sha256 operations instead of 4 when mining a block hash.

2. It is possible because sha256 processes data in 64 bytes chunks, but the header is 80 bytes long.

3. So the block header is split into 2 chunks when sha256 computes its hash.

4. The merkle root inside the block header, spans over the position that sha256 split the chunks.

5. The merkle root is 32 bytes, 28 bytes of it (head) ended up in the first chunk, 4 bytes of it (tail) ended up in the 2nd chunk.

6. The second chunk has 16 bytes of data and 48 bytes of padding.

7. Of the 16 bytes of the data in the second chunk, 4bytes is the merkle root tail, the other 12 bytes are  time/difficulty/nonce, all known values by the miner.

8. That means if a miner can generate a bunch of hash with the same last 4 bytes, then the entire 2nd chunk, all 16+48 bytes of it becomes a fixed known value.

9. A fixed value means it can be reused, this allows miners to simplify the sha256 mining loop, so that it only uses 3 sha256 operations instead of 4 and increase efficiency.

10. The more 'hash with the same last 4 bytes' a miner can generate, the more times they can use the short cut, the more performance gain, this process is called 'finding partial hash collision'.

11. To generate these partial hash collisions, miners have to keep changing the data on the block then get a new hash at high speed, but different ways have different costs, only a few of them is worth while.

12. One of the fastest way to find hash collisions is to keep changing the extranonce in the coinbase, at the same time keep reordering tx in the block. This modifies both side of the merkle tree parallelly and allow further math shortcuts to take place.

13. Changing the coinbase and reordering tx is computationally costly, it is only worthwhile if you can do both at the same time without affecting each other.

14. In regular Bitcoin, modifying tx changes the right side of the merkle tree, and modifying the coinbase changes the left side of the merkle tree, the coinbase on the left doesn't care what happens to the tx on the right, and vice versa. There are no double overhead modifying data on any side, so in the end you can gain a 20% advantage with ASICBoost.

15. But if the coinbase merkle root includes the hash of all the tx, then ASICBoost is no longer worth the effort, in fact it'd make mining slower, because now every time you reorder the tx, the coinbase also changes, and you have to use an extra 10 or so operations to update the left side of the merkle tree. That 20% advantage is gone.

16. This is what happens in BIP-141 SegWit, the coinbase has a new merkle root call the 'witness root hash', that includes all regular and side tx. This makes the reordering tx also updates the coinbase, miners have to run extra operations for each reordering, this double overhead makes it too costly to use ASICBoost.

17. Extension Block is base on BIP-141, they have the same commitment structure, so Extension Block is immune to ASICBoost.

18. If anyone is using ASICBoost, the 'overt' method involves modifying block header data directly, so you'll see strange version numbers and other weird data, the 'covert' method involves reordering of tx, or empty blocks, these are also obvious.

19. If there is a new way to use ASICBoost without obvious side effects, then it's just another valid optimization on generating hash, optimization happens all the time.

20. The excuse of ASICBoost patent may lead to centralization is also silly, there are so many patent involved with mining already, from chip to connectors to cooling, everywhere you look there is a patent. Mining is so competitive, every year there are a bunch of new optimizations with a new bunch of patents. The biggest problem with ASICBoost is once it's used, it'll leave obvious patterns in the blockchain, the anomalies will be spotted very quickly.

coindesk is a well known Blockstream mouthpiece.

He can't answer you, AgentofCoin likes to use his secret crystal ball instead of facts.

He does, it's a sphere, it's made of glass, it's on the floor of his toilet and it has wet brown stains on it.

Not when someone with tunnel vision keep accusing Jihan of stop supporting SegWit once he realized he can't use ASICBoost on it.

The SegWit agreement was already derailed by Greg's 'dipshits' comment right after the agreement was signed, it was later furter derailed by Greg+gang changing the story to 'SegWit was the blocksize increase'.

The key here is Jihan was not the only miner who was pissed at Blockstream/Core and switched to BU. Pinning the entire mass exodus from Core on ASICBoost is just another distraction from the real issue: The 1M blocksize limit.


Irrelevant word play, when you resort to nitpick on a micro level, you should know the HK Agreement wasn't even a legally binding contract, but an acknowledgement of consensus between miners and Blockstream/Core.

Adam Back represented Blockstream when he signed the HK Agreement (he used a bait and switch at the last minute, but f2pool corrected him afterwards), Greg was part of Blockstream and Core, so everyone in Blockstream is in the same party that signed the agreement.

Greg actively and vocally went against the HK agreement right after it was signed, Greg's bullshit continued to this day. Greg wasn't the only one from Blockstream/Core working against the agreement, but he was the most vocal, that's why he's now called "One Meg Greg", miners switched to BU once it was clear that Blockstream/Core wasn't going to keep their promises and offer 2MB non witness blocks as promised.

This Blockstream circus has been going on for over a year, you have to be intentionally dishonest or grossly uninformed to claim Greg didn't break the HK Agreement.


I knew you'd fall for it. Ext Block had always been immune to ASICBoost, simply because its design is base on BIP-141 (SegWit), which hash all regular and side tx into the coinbase merkle root.

And now I know you really are a paid troll, only a paid troll would act stupid all the time then suddenly become smart enough to pick up on small details and try go for a kill. But you were lazy and didn't check commit history, so you didn't notice it was just a bait.

The funny thing is this time I'll use Greg's ASICBoost inhibiting proposal and BIP-141(SegWit) to prove you wrong, using one shill against another just for kicks.

Take a look at Greg's ASICBoost inhibiting proposal on 5 Apr 2017:

Notice the bold part, the key here is "BIP-141 commitment structure".

What this means is that if your proposal uses BIP-141(SegWit)'s commitment structure, then it is immune to ASICBoost. (BIP-141 is what Extension Block is base on, that's why Extension Block is immune to ASICBoost)

As to what the 'commitment structure' is, it is described in the spec of BIP-141 (haven't changed since 2016):


So, in BIP-141, you have a new commitment hash (a new markel root) in the coinbase called the 'witness root hash', this hash is base on all the 'wtxid' in the block, 'wtxid' is all the tx in the block, including both witness and non-witness tx.

That means, in plain english, in BIP-141 (aka SegWit, which Extension Block is also base on), every time you reorder/add/remove/replace a transaction from the block (to generate a new hash), the coinbase is changed.

By placing the hash of all the tx on the left side (witness root hash inside the coinbase), everytime you change the right side (reorder tx), you also change the left side at the same time.

This renders ASICBoost useless since one of the shortcut ASCIBoost relies on, is the fact that in Bitcoin when you change the tx order (right side of the Markel Tree), the coinbase (left side) doesn't change, which makes it much cheaper to generate and filter hash collisions (which will then be used for the sha256 msg expansion short cut in the mining outer loop).

Greg further explained BIP-141's ASICBoost immunity here:


Greg is a well-known for his lying, but he is also hell-bent on destroying Jihan and it took him a year to come up with this, so I might as well use it against another shill.

Now, about Extension Block, and why your accusations and prophecies don't stand up to facts.

On 3 Apr 2017, Jinhan posted this on twitter:" I love the extension block proposal. It is compitable with BU."

This was the spec of Extension Block on 1 Apr 2017 (2 days before Jihan's tweet, 5 days before the so-called ASICBoost patch):

This establishes three facts:
1. Extension Block uses the same commitment structure as BIP-141(SegWit), which is immune to ASICBoost.
2. In Extension Block, all txid, regular block or extension block, are all included in the Merkle Root. (Changing right side of the Merkle Tree = changing the left side = high tx reorder cost = immune to ASICBoost)
3. The Extension block spec Jihan supported on 3 Apr 2017, was immune to ASICBoost.

In 4 Apr 2017, 1 day after Jihan voiced his support for Extension block, chjj, an Ext Block dev, made the following changes in the Ext Block spec:

In this commit, chjj basically tried to remove the ASICBoost immunity from Extension Block.

What he did here was changed the spec to no longer include regular txid into the coinbase merkle root, this means miners can reorder regular txid (changing right side of the tree), without changing the coinbase (left side of the tree), this allow ASICBoost to efficiently generate and filter collision hashes for the mining loop short cut.

But he did a half ass job, because the line above still read:
"The commitment serialization and discovery rules follows the same rules defined in BIP141"

Following BIP-141 means all regular/extended tx is still in the new merkle root in the coinbase, still immune to ASICBoost.  

On the surface, it may look like chjj had no idea what he was doing.
(this is also the part where you got fucked over, thinking ASICBoost actually would work on Extension Block after chjj's botched edit)

This is evidenced by the issue he created the next day, 5 Apr 2017, soon after Greg posted the ASICBoost inhibiting proposal:

chjj's edit lasted only for one day, quickly fixed after some knee jerk reaction from the devs on Greg's ASICBoost inhibiting proposal.

A more experienced dev, indutny, made the following comment the next day:

indutny was correct, Extension Block has always been immune to ASICBoost, Ext Block's commitment structure was base on BIP-141/SegWit, so add/remove/reorder/replace any regular/extension tx has the same effect as SegWit - it changes the coinbase, making ASCBoost's collision filtering short cut no longer works, hash collision generation and filter too costly.

But one thing is curious tho, chjj removed 2 lines from the Ext Block spec to make it look like Extension Block wasn't immune to ASICBoost, at the same time Greg was posing the ASICBoost inhibiting proposal.

Right after he removed that line, he created an issue to ask for help on dealing with ASICBoost, then quickly accepted a PR to 'fix' the ASICBoost issue.

Delete ASICBoost immunity > Ask for Help on ASICBoost > Accept PR to deal with ASICBoost, all within 2 days. The delete commit was also burried under a bunch of other edits, with a disguised description.

What a series of strange coincident. It's as if chjj wanted to make a big deal out of ASICBoost in the Ext Block issue/pull request while Greg was also making a big deal out of ASICBoost at the same time.


I just established, using verifiable facts, that Jihan/Bitmain/AntPool supported Extension Block, which was and still is immune to ASICBoost.


Again, still no proof that ASICBoost was ever used in production.

With all these screaming you'd expect at least a little proof, but nope, just a bunch of idiots regurgitating the same script.

The real reason Jihan even put ASICBoost on the market but not enabled it was because 'first to market' is how you win patent wars. ASICBoost was being patened by other people in other countries, obviously the next move was to put ASICBoost on market to defend the patent.

That's also why Jihan Wu made the 'ASICBoost? Do you have any basic understanding of patent law' tweet then deleted it, him or his lawyer probably realized speaking that truth wasn't going to be helpful to future patent lawsuits.

And the real current issue here is a bunch of trolls are suffering from verbal diarrhea, trying to distract people from the real issue: the blocksize increase.


All the knee jerk responses, screaming and finger pointing, foaming at the mouth baseless accusations about ASICBoost suggest otherwise.


You made the accusations, the burden of proof is on you, back up your own words instead of cry wolf nonstop then looking around like a moron waiting for someone else to clean up your mess.


The blockchain (that immutable thing you call 'faulty data') has always been out there for everyone to see.
There are no long strings of empty blocks.
There are no pattern of funny version numbers.
There are no pattern of weird tx orders.

If there is some kind of secret way to use ASICBoost that can hide this well from everyone for this long, then ASICBoost automatically become yet another optimization. But then again, there aren't any abnormal hashrate:blockrate ratio.

You made accusations with absolutely nothing but bullshit prophecies, then you complain about people showing up with facts dating back months? Normal people just can't be that silly, trolling as a job is one thing, but this is just bad acting, very unprofessional.


Again, no long strings of empty blocks.
No abnormal hashrate/blockrate ratios.

It takes time to calculate the next block template, during which miners mine empty blocks, AntPool has the highest hash rate, naturally they'll have more empty blocks than others.
 
Empty blocks existed before ASIC was even in the picture.

Try look for some abnormal patterns from the blockchain, instead of keep pulling crystal balls out of your rear.


He did say why Greg was wrong.

Why are you even arguing for Greg. Greg doesn't even understand the difference between 1MB and 2MB.


Or they should investigate why there are so many unprofessional trolls posting similar bullshit narratives non stop.

No logic, no facts, wrong every time, yet keep repeating them like their jobs depend on it.

Sometimes they don't even remember what they posted a page ago, like they're working on multiple sites at the same time, or more than one PR worker is using the account.


1. You are laughable.
2. They can, I did, and you have.
3. Cult prophet wannabe proof:
AgentofCoin: In time, all will be revealed.
AgentofCoin: within the next two months or less, someone will publish a full scientific report
AgentofCoin: Jihan will no longer support that Ext Block proposal.

In time, you'll find a better job than acting like a robot online all the time.


You do realize you just got out trolled because you asked for it by name on page 1, right? Here:


And you do realize I was just using you to explain to people Extension Block is immune to ASICBoost, right?

This whole ASICBoost bullshit is just another distraction from Core keeping the blocksize at 1M slowing everything down.

The ASICBoost write paper used a lot of tech jargon, that's why after a year over half the devs still don't know how it works.

ASICBoost is:
1. A programming short cut of using 3 sha256 operations instead of 4 when mining a block hash.

2. It is possible because sha256 processes data in 64 bytes chunks, but the header is 80 bytes long.

3. So the block header is split into 2 chunks when sha256 computes its hash.

4. The merkle root inside the block header, spans over the position that sha256 split the chunks.

5. The merkle root is 32 bytes, 28 bytes of it (head) ends up in the first chunk, 4 bytes of it (tail) ends up in the 2nd chunk.

6. The second chunk has 16 bytes of data and 48 bytes of padding.

7. Of the 16 bytes of the data in the second chunk, 4bytes is the merkle root tail, the other 12 bytes are  time/difficulty/nonce, all known values by the miner.

8. That means if a miner can generate a bunch of hash with the same last 4 bytes, then the entire 2nd chunk, all 16+48 bytes of it becomes a fixed known value.

9. This allows miners to simplify the sha256 mining loop, so that it only uses 3 sha256 operations instead of 4, and increase performance.

10. The more hash with the same last 4 bytes a miner can generate, the more times they can use the short cut, the more performance gain, this process is called 'finding partial hash collision'.

11. To generate these partial hash collisions, miners have to keep changing the data on the block then get a new hash at high speed, but different ways have different costs, only a few of them is worth while.

12. One of the fastest way to find hash collisions is to keep changing the extranonce in the coinbase, at the same time keep reordering tx in the block. This modify both side of the merkle tree parallelly and allow further math shortcuts to take place.

13. Changing the coinbase and reordering tx is computationally costly, it is only worthwhile if you can do both at the same time without affecting each other.

14. In regular Bitcoin, modifying tx changes the right side of the merkle tree, and modifying the coinbase changes the left side of the merkle tree, the coinbase on the left doesn't care what happens to the tx on the right, and vice versa. There are no double overhead modifying data on any side, so in the end you can gain a 20% advantage with ASICBoost.

15. But if the coinbase merkle root includes the hash of all the tx, then ASICBoost is no longer worth the effort, in fact it'd make mining slower, because now every time you reorder the tx, the coinbase also changes, and you have to use an extra 10 or so operations to update the left side of the merkle tree. That 20% advantage is gone.

16. This is what happens in BIP-141 SegWit, the coinbase has a new merkle root call the 'witness root hash', that includes all regular and side tx. This makes reordering tx also updates the coinbase, miners have to spend 10 extra operations for each tx reordering, this double overhead makes it too costly to use ASICBoost.

17. Extension Block is base on BIP-141, they have the same commitment structure, so Extension Block is immune to ASICBoost.

18. If anyone is using ASICBoost, the 'overt' method involves modifying block header data directly, so you'll see strange version numbers and other weird data, the 'covert' method involve reordering of tx, or empty blocks, these are also obvious.

19. If there is a new way to use ASICBoost without obvious side effects, then it's just another valid optimization on generating hash, optimization happens all the time.

20. The excuse of ASICBoost patent may lead to centralization is just silly, there are so many patent involved with mining already, from chip to connectors to cooling, everywhere you look there is a patent. This field is so competitive, every year there are a bunch of new optimizations with a new bunch of patents.

So, ASICBoost doesn't work on Extension Block, and ASICBoost was never used in production.

Stop crying about it being used and just show us the proof for all your accusations.

Well said.

If they have the talent, they may afford this kind of arrogance.
But SegWit is such an overly complex bloated piece of shit, they clearly don't have it, or they're intentionally fucking up Bitcoin.

Nobody worth their salt will stay working with these arrogant but untalented kidults.
That's why people like Joseph Poon (first author of Lightning Network) is now going against Blockstream.

Here is the funny part, the Blockstream/Core walk around acting like they represent the 'Bitcoin Community', but Adam Back, the 'President' of Blockstream, never believed in Bitcoin and never even committed a single line of code to the Bitcoin Core code base.

This just in:

http://telegra.ph/Inside-the-Dragons-Den-Bitcoin-Cores-Troll-Army-04-07
Inside the Dragon's Den: Bitcoin Core's Troll Army
April 07, 2017

Here's what is known:

1. Poon alluded to "a secret channel where they organize their PR and trolling campaigns" which is "basically where a lot of decisions around PR happens."

2. There is a secret channel on the Bitcoin Core slack called #dragonsden

3. There are 21 members in this chat group, as of January 27th, 2017 (the date of Cohen's talk)

4. The known members of this channel, based on the information in the above glimpse of the channel are: BashCo (/r/bitcoin moderator), mrhodl (twitter troll), alp (twitter troll), moli (unknown), belcher (JoinMarket developer), BtcDrak (Bitcoin Core developer/activist) and Bram Cohen. These seven members represent 1/3rd of the total members in the channel.

5. BashCo is Theymos's second in command. Fellow /r/bitcoin moderator ThePiachu wrote in a blog post:
   
6. This establishes proof that there is collusion between Bitcoin Core and the moderation team of /r/Bitcoin.

7. At least one Bitcoin Core developer is present in this chat. There are 14 more chat members we cannot see.

This information provides further evidence of the Bitcoin Core propaganda machine and demonstrates the conclusive link between Bitcoin Core and the /r/Bitcoin moderation team. Everything written above is factual and verifiable.

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.


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.


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.


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.

That fact was for the idiots who keep regurgitating the 'AntPool is using ASICBoost to mine empty blocks' bullshit script.

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.


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.

Irrelevant, bullshit is still bullshit, 2011 is still 2011 and 2017 is still 2017, the internet has never stopped changing 'dramatically'. It doesn't take a genius to know things will only keep improving.

All you need to do is type 'average internet speed' in a search engine and you'll find similar facts. Instead you went out of your way to dig back 5 years and pull out bullshit links from fucking 2012 using data from 2011 just to support a bullshit statement, search engines don't even show results that old unless you really dig for it.

I am so fucking sick and tired of you shills/trolls/uninformed fucks making idiotic statements over and over base on either outdated data or just flat out bullshit, repeating the same FUD week after week.

What a load of bullshit.

Why the fuck are you quoting shits from 2011 when we're now in 2017 and FCC has stated that 'Average U.S. Internet speed has more than tripled since 2011', back in 2016?

What kind of dumb fuck use 2011 data in 2017 for something as fast growing as the internet, you're either yet another intentionally dishonest shill or yet another uninformed dumb fuck trolling over shit he doesn't understand.

Now this is just hilarious, you idiots were just proven wrong again by facts, and you just go ahead and repeat the same bullshit anyway? Did you even feel shame when you click the 'Post' button?

You know Blockstream is fucked when even the leading LN devs go against them in public, stating what everyone knew all along: Core runs PR and trolling campaigns:

We have our new "Blockstream's lie of the week", this time the enemy is the ASICs, again.

Looks like the block extension proposal really fucked Blockstream big time.
It is simple and it solves immediate blocksize problems.
 
What's even better is that the Block Extension is "party neutral" so Blockstream can't even go against it by bashing the BU straw man, so they needed to create another enemy to distract people for another week, Blockstream ran out of excuses so now they have to regurgitate bullshits from a year ago:


The bullshit didn't work then, it doesn't work now.

If you're a newbie all you need to know is every time people from Blockstream open their mouth, it's a lie. Blockstream spent millions on SegWit, they have a deadline coming, but their walls are crumbling and even LN devs are going against them now.

The good thing about this ASICboost bullshit is that it makes it so obvious who the paid shills are on this forum. These dumb fucks are paid to jump to conclusion with zero facts, all you need to do is ask them for proofs, then they break down and disappear (the stupid ones argue back and make their shilling look even more obvious).

Read the news before you troll you stupid lazy fuck, leading LN dev just public stated what everyone knew all along: Core runs PR and trolling campaigns:


According to your dumb fuck logic, LN dev must also be fighting on behalf for BU too then?

This kind if idiocracy is what I am talking about, there is a limit on how stupid you can be when you work as a shill for someone, when your logic degrade to this level the script just doesn't work anymore, why the fuck do you idiots even repeat them? It isn't working, does your PR handler even read what you're posting?
 
You know Blockstream is fucked when even the LN dev go against them in public, if I were you I'd start looking for a new PR job, at this rate Blockstream won't last long.

Here is another shining example of a shill, when the shill can't refute the facts you posted, they just quote you anyway and repeat the same bullshit.

Watch how he even began his reply by "Fucking yea" hoping people is so fucking stupid they'd actually think I was agreeing with the bullshit that follows.

Again, the shilling is too fucking stupid and too fucking obvious.

No, I was simply referring to your fucking idiotic 'summary'.


What side? What the fuck are you even on about? Have you even read my earlier posts?
Even if you haven't, I am just pointing out facts here, but you're against facts that's why you think I am on the other 'side'.

See, this is the kind of scripted shilling bullshit that are just too fucking obvious.

Let's look at your bullshit 'summary' again:


Tell me genius, if the ASICBoost is incompatible to both SegWit and Ext Block, and Bitmain supported SegWit and now supports Ext Block, then how the fuck could you possibly jump to that idiotic conclusion base on 'This exploit is incompatible with Segwit'?

How the fuck does your mind even work?

Let me rephrase:
Anyone who've followed Bitcoin news for longer than a week and still can't see this ASICBoost non-issue is just the same regurgitated half digested bullshit Blockstream pulled out off their collective ass, is either intentionally dishonest or just a complete dumb fuck.

I am describing what I am seeing, a bunch of stupid fucks agreeing to an obvious smear campaign base on something the other guy didn't even fucking do.

When people keep making idiotic statements where the stats don't check out, the facts don't check out, the historic facts are ignored, even fucking common sense is ignored, these people are by definition fucking morons.

You don't negotiate when the other idiot keep repeating 1+1=3, if he's simply uninformed, fine, learn the truth and move on, but when the same facts have already been explained over and over again, and they keep repeating the same bullshit, that is not a discussion, that is a shill operation, and shills deserve to be trashed for spreading bullshit nonstop.