sequences. And we're going to make sure that these consequences are going to hit these people hard. [Side, SegWit is NOT scale. Line chart allegedly comparing "Bitcoin vs SegWit"] Segwit is not scale. That [points to one line] is what get with a block size increase; that [points to other line] is what we get with segwit. If you have a 4 meg block; if you have a 16 meg block; you multiply it by 4. That is not scale. What you do to scale is increase the throughput, and you get more for a 4 meg block than you do any time that you have this split system that needs to be run that you can't really delete if you're a merchant or a financial organization. Saying "oh, well, you can keep it," where the hell is the actual benefit of deleting that you can't delete? Each transaction requires more bandwidth. It's very simple: it takes more. The answers you've been given about how terrible all this is: run multi-threaded systems; stop arguing that it needs to be put on Raspberry Pis so that they can lie to you and tell that it needs to be moved off to other systems. It doesn't. One of the things we, yes, we patent---I'm not afraid to say that. Unlike Greg [Maxwell?] and whatever else, we will choose what we do with our technology. That's not bad. I created things, I get to choose. My choice. I will put some out free. We will put some out otherwise. Our choice. But, at the end of the day, scale needs to happen---and it needs to happen now. And it's not quadratic due to these other problems they're saying. [New slide, looks like screencap of GitHub showing a some lines of code in Bitcoin Core.] Here's a thing no one's talking about: this quadratic scaling issue. It's added to Bitcoin. It is added. Follow the codebase. It is easy to fix. I know several, [such as] Bitcrust, Bitcoin Unlimited, and our team independently picked this out and fixed it. Our team did it in about three hours. That's sure scalability. Doing multithreading about putting things off to [unknown term; sounds like "Xeon fi cards"]... any idea how many sigops we can achieve now? Anyone? Five hundred thousand per second. That's scale. And yes, that's a $20,000 machine. Quite frankly, I don't care about Raspberry Pis. If you have been in Bitcoin since 2009 and you can't afford a $20,000 node to help this network, piss off. [Audience applause.] And I will say that one again, if you will not do this; if you will not help this network; and if you will not take this thing that has given you financial sovereignty, you financial freedom, you financial independence, and help other people by spending a little bit of money on a decent network, fuck off! [More audience applause.] [New slide, Scale is quadratic due to code flaws. Shows a diff with two added lines, one removed line in mempool management.] That's it: O-2 [sic; slide says O(n^2)]. Poor code. Shit code. That's why we need competition. That's why, not just Core, anyone should be release their own and compete fairly. If you make a better solution and you put it out to market, you compete fairly. Through competition, because people use your product. Not because you're cowed into... DDoS attacks or anything like that. Not because of all of that. Bitcoin Unlimited found the flaw as well. Some of these thing that Unlimited have been doing [are] very innovated. [New slide, Moore's Law is our friend] At the end of the day, Moore's Law [is] our friend. The smallest transistor---well, I'm probably being superseded already, but I've got a paper coming out on this, and the editors picked out a mistake because I said a 2 nanometer transistor and it turns out there's now a 1 nanometer transistor. When all this happened, people were arguing that because of quantum tunneling, this is impossible. "At six nanometers, it will never be done." Guess what? It's been done. So stop this, "oh, we can't do it" and "oh, everything's bad" idea. The reality is we need to start being optimistic, positive, and build. Allow competition. Allow free access to code. Allow people to actually start competing. No building little walled bloody gardens. [New