[00:00.000 --> 00:01.960] Get to suffer as I go through them. [00:02.420 --> 00:05.560] Okay, let me start. Get ready. [00:06.960 --> 00:07.840] Kahoot. [00:10.180 --> 00:11.500] Two, one. [00:11.500 --> 00:12.300] Question one. [00:12.300 --> 00:16.920] For the Monero E-A-E attack, what do the letter E's stand for? [00:16.920 --> 00:20.600] Is it epidemic, exchange, elliptic curve, or environment? [00:20.600 --> 00:24.900] Of course, in all of these cases, you should select the best answer. [00:26.260 --> 00:28.780] On your phone, you just have the colors and... [00:28.780 --> 00:31.940] an icon, so you will need to look at the screen. [00:31.940 --> 00:37.080] There is about a five-second delay, so get those answers in as quick as possible. [00:37.080 --> 00:39.500] I'm actually seeing more like a six-second delay. [00:40.740 --> 00:42.360] You're almost out of time. [00:47.680 --> 00:49.200] Wow, okay, yeah. [00:49.200 --> 00:54.160] For the Monero E-A-E attack, the correct answer is the exchange. [00:55.180 --> 01:01.100] E-A-E typically refers to a single user, at least in the case of E-A-E, with just one letter A in the middle, [01:01.100 --> 01:06.380] where a user will take funds from one exchange and send it to another colluding exchange. [01:06.380 --> 01:12.560] It does not have to be an exchange, but however, that's what the general name comes from. [01:12.560 --> 01:19.320] The idea that you are KYC'd on two exchanges that would collude to potentially understand [01:19.320 --> 01:25.620] that the Monero originated from the original exchange and ended up in the second exchange entity. [01:25.620 --> 01:27.780] So exchange is the best answer there. [01:27.780 --> 01:32.740] Elliptic curve is a cryptography term, and all the fancy-schmancy people chose that one, [01:32.740 --> 01:38.120] but I think that, yeah, the E-A-E does not refer to cryptography. [01:38.120 --> 01:42.860] It just refers to a limitation in targeted surveillance in Monero. [01:42.860 --> 01:51.860] If you are interested in learning more, there is a Breaking Monero episode on E-A-E or the Poisoned Output attack. [01:51.860 --> 01:55.980] A lot of these attacks are very similar. They're all derived from the same type of idea, [01:55.980 --> 02:01.480] where you are engaging with colluding entities, so you should be a little bit careful there. [02:02.000 --> 02:04.480] And yes, as NeedMoney90 says, please like and subscribe. [02:04.480 --> 02:07.740] This is a typical S.H.I.E.L.D. channel. Let me insert an ad break here. [02:07.740 --> 02:09.140] Just kidding, we're not affiliated. [02:09.140 --> 02:16.100] I even turned off the setting where users on this channel, if... [02:16.100 --> 02:19.400] I mean, I don't think people see ads. I'm not getting any money from Google. [02:19.400 --> 02:23.060] But even if they did, they would not also see personalized ads. [02:23.060 --> 02:28.740] I am getting less money than I already am not getting, so you're welcome. [02:29.300 --> 02:32.880] Any case, let's see who scored well in these. [02:33.960 --> 02:38.300] Knack answered the fastest, so they are on the top of the leaderboard. [02:38.300 --> 02:42.460] They have 909 points, so congratulations, Knack. [02:42.460 --> 02:44.720] Censored got that correct. JW got it correct. [02:44.720 --> 02:49.380] J-T-B-V, which is really hard for me to say, because these letters are way too similar. [02:51.200 --> 02:53.360] But yeah, four on the top of the leaderboard. [02:53.360 --> 02:55.560] Scott, for some reason, is still on the leaderboard. [02:55.560 --> 02:58.480] Scott, how did you not get that one? Come on, Scott, you should have known. [02:58.480 --> 03:00.240] Scott, I'm disappointed in you. [03:01.120 --> 03:06.060] All right. Also note, you get extra points, not just for answering quickly and correctly, [03:06.060 --> 03:08.240] but by answering several correct in a row. [03:08.240 --> 03:13.060] So you've got to get these long, correct answers in a row here. [03:13.060 --> 03:17.680] Vic clearly is not as good at trivia as he is at making memes. [03:17.680 --> 03:22.160] So, Vic, I'm watching out for you. You better get a few of these in. [03:22.760 --> 03:25.100] Scott is now banned from DEF CON. Honestly, yes. [03:25.100 --> 03:26.720] Scott, come on. Come on, Scott. [03:27.460 --> 03:29.820] All right, question two. Maybe you'll do better on this one. [03:29.880 --> 03:32.580] What does Monero most closely mean in Esperanto? [03:33.640 --> 03:36.200] Money, cash, coin, or private? [03:40.450 --> 03:41.150] Roasted, yeah. [03:41.150 --> 03:45.630] The whole point of this is basically just to adjust and free-for-all roasting people. [03:46.530 --> 03:49.490] Ultimately, the entire motivation I have behind this. [03:49.490 --> 03:53.270] And no one else is in Jitsi with me to complain. [03:54.310 --> 03:57.290] All right, we got a nice split here. [03:57.290 --> 04:02.950] So, I was playing the long con here, actually, for a few reasons. [04:02.950 --> 04:08.130] One, I gave this same question during the Moneroversary. [04:08.130 --> 04:11.470] At least, if I have good memory, I guess you can check me on that. [04:11.810 --> 04:16.010] But, yeah, most people got it wrong then, so I reuse the same question now. [04:16.010 --> 04:20.870] And I also released a movie called Monero Means Money. [04:20.870 --> 04:24.190] And it does not actually translate to money. [04:24.190 --> 04:27.770] It does instead translate to coin in Esperanto. [04:27.770 --> 04:30.770] That is when Monero first launched. [04:30.770 --> 04:35.130] It did not launch as the name Monero. It launched as the name Bit Monero. [04:35.130 --> 04:39.650] So, translated, basically, it was meant to mean Bit Coin. [04:39.650 --> 04:42.470] You know, Esperanto, for some reason. [04:43.730 --> 04:47.510] Esperanto, of course, is the world's most spoken constructed language. [04:47.510 --> 04:51.610] It is not one that was just spoken by people for a long time. [04:51.610 --> 04:53.530] It's a relatively recent language. [04:53.570 --> 04:58.490] And it's meant to be one that everyone could use as a neutral constructed language. [04:58.910 --> 05:01.970] But coin is the best answer here. [05:02.150 --> 05:04.150] So, let's see who got this one correct. [05:04.710 --> 05:06.810] Looks like someone else said that they got rekt. [05:06.810 --> 05:09.170] X, X, sorry, X, X, X, X. [05:09.170 --> 05:13.830] But, first place, still knack, got that one correct. [05:13.830 --> 05:15.510] Censored, Need Money 90, still on there. [05:15.510 --> 05:17.030] JW killing it. [05:17.370 --> 05:18.850] Scott got that one correct. [05:18.850 --> 05:23.790] And they moved up from their undeserved fifth place to fourth place. [05:23.790 --> 05:27.150] And then JTBV on the board now. [05:27.310 --> 05:29.210] Looks like they did not get that one correct, though. [05:29.210 --> 05:31.110] Because they got the previous one correct. [05:31.110 --> 05:33.590] So, really, Scott was the one who answered that one correctly. [05:34.490 --> 05:38.110] All right, let's see how people do in the next question here. [05:38.670 --> 05:43.070] Question three, what does the C in CLSAG stand for? [05:43.170 --> 05:47.010] Is it circular, compact, concise, or cooperative? [05:55.730 --> 06:01.830] People who were on for the MRL hour, office hours, earlier, hopefully know the answer to this one. [06:12.660 --> 06:14.740] I always like watching these because... [06:14.740 --> 06:22.540] All right, I just want to point out that for my quiz so far, the majority of people have answered incorrectly to every single one of these. [06:23.200 --> 06:25.400] So clearly I'm doing something right. [06:26.420 --> 06:29.240] But in no case has no one got it correct. [06:29.460 --> 06:33.920] Actually, if you chose compact, you shouldn't feel too bad. [06:33.920 --> 06:37.020] Because originally in MRL, they wanted to call it compact. [06:37.020 --> 06:38.360] But they got some pushback. [06:38.360 --> 06:41.720] They got a lot of saying, well, it's not compact technically. [06:41.720 --> 06:47.080] Because compact technically is supposed to have these guidelines if you're following other papers, yada, yada, yada, yada. [06:47.080 --> 06:52.700] And you're right, in a general use term, no one actually cares. [06:52.700 --> 06:55.520] But cryptographers are a bunch of picky bunch. [06:55.520 --> 06:58.640] And therefore, they decided to name it concise. [06:58.740 --> 07:02.480] Because it met the other cryptography definitions. [07:02.480 --> 07:05.040] Concise is what it actually is called. [07:05.220 --> 07:07.280] So it's not cooperative. It's not circular. [07:07.280 --> 07:11.540] I did throw that one in there in case someone thought it would be related to the circular ring. [07:11.540 --> 07:15.700] But in fact, ring signatures are not actually the form of a circle. [07:15.700 --> 07:19.320] They don't store actual pictures of blockchains in here. [07:19.480 --> 07:21.520] Yeah, you're right. Knack probably got this one correct. [07:21.520 --> 07:26.880] If Knack did not get this one correct, I think we can make fun of him more than anyone else that doesn't get these correct. [07:28.200 --> 07:28.920] What? [07:31.040 --> 07:33.940] Doug had defied your expectations there. [07:33.940 --> 07:35.860] I would have bet money. [07:36.400 --> 07:42.780] Maybe they went to the bathroom or something and weren't looking at the screen at the time. [07:42.780 --> 07:45.820] Or misclicked as a result of you allegedly misclicking, Doug. [07:45.820 --> 07:48.700] But Andres got that one correct. Meow got that one correct. [07:48.700 --> 07:52.020] And Rottenkwinkus got that one correct, too. [07:55.140 --> 07:57.720] JW censored Knack. Still remained at the top, though. [07:57.720 --> 08:00.820] But Scott was punched off the leaderboard. [08:00.820 --> 08:03.500] And yet, Knack is a researcher. So maybe they would know. [08:04.940 --> 08:08.900] Alright, so this is pretty fun. It's still anyone's game at this point. [08:08.900 --> 08:12.520] Of course, remember the last question alone is worth 2,000 points. [08:12.520 --> 08:14.240] So, you never know. [08:14.240 --> 08:20.560] Question 4. In its entire history, how many Monero transactions have hit the sender, receiver, and amount? [08:20.560 --> 08:26.880] Is it about 6,500, 65,000, 650,000, or 6,500,000? [08:27.360 --> 08:30.400] What is the closest answer here? [08:31.640 --> 08:34.360] Not all Monero transactions in all of history. [08:34.360 --> 08:37.060] Just ones that have hit the sender, receiver, and amount. [08:37.060 --> 08:42.040] Noting that in the past, when Monero first launched, up until RingCT was a thing, [08:42.040 --> 08:45.260] Monero did not hide the transaction amount. [08:45.780 --> 08:47.880] Because it was just denominated. [08:47.880 --> 08:49.640] Pretty poorly, honestly. [08:50.060 --> 08:53.500] I don't know if everyone got the question in time there. [08:53.500 --> 08:57.020] Make sure you are keeping track of the timer on the left [08:57.020 --> 08:59.300] and note that there is at least a 5 second delay. [08:59.300 --> 09:02.880] So get those answers in as quick as you can. [09:02.980 --> 09:05.900] Yes, the answer is 6.5 million. [09:05.900 --> 09:09.240] Which again, the majority of people did not get correct. [09:09.320 --> 09:11.900] Maybe they just saw the highest number and were like, [09:11.900 --> 09:13.540] Nah, that can't be true. [09:13.540 --> 09:17.560] But yes, almost, at least as of last month, [09:17.560 --> 09:19.920] it was over 6.2 million. [09:19.980 --> 09:23.820] So yeah, about 6.5 million transactions in Monero [09:23.820 --> 09:26.060] have hit the sender, receiver, and amount. [09:26.060 --> 09:28.280] These are all RingCT transactions. [09:28.400 --> 09:29.960] So that is pretty cool. [09:31.080 --> 09:36.760] Well, if you did in fact have 2 million transactions alone, [09:36.760 --> 09:39.520] that would not bode especially well [09:39.520 --> 09:42.180] for traceability with low ring sizes. [09:42.180 --> 09:43.740] With 11, we are probably fine. [09:43.740 --> 09:45.380] But I would be pretty suspicious. [09:45.380 --> 09:47.280] That is pretty much attack level there. [09:47.320 --> 09:50.060] Maybe certain mining pools collectively have those. [09:51.280 --> 09:53.280] Oh, let's see what other comments are coming in. [09:53.280 --> 09:55.100] Anyone who has synced the blockchain on the terminal [09:55.100 --> 09:57.480] will know how slow the later blocks are to sync. [09:57.480 --> 09:58.880] Yeah, that is mostly a RingCT thing. [09:58.880 --> 10:02.040] But luckily, CLSAG will definitely speed that up [10:02.040 --> 10:04.220] for future transactions going forward. [10:04.220 --> 10:06.660] And even so, Bulletproofs are much faster to verify. [10:07.240 --> 10:09.880] Serang did this really awesome thing where he was just [10:09.880 --> 10:11.000] looking at code and was like, [10:11.000 --> 10:14.100] Wow, I found a way to make all Bulletproof transactions [10:14.100 --> 10:16.920] much faster to verify even retroactively [10:16.920 --> 10:18.840] by just being more efficient. [10:18.840 --> 10:22.000] Because people just pull these optimizations out of nowhere [10:22.000 --> 10:24.200] when you are a genius like they are. [10:24.420 --> 10:27.140] Obviously, I am not a genius. I just make quizzes for people [10:27.140 --> 10:29.240] and get them wrong half the time. [10:29.260 --> 10:32.200] So yes, 6.5 million is the correct answer. [10:32.200 --> 10:35.580] If you were watching some of my talks in the past, [10:35.580 --> 10:37.200] one of which is on this channel, [10:37.200 --> 10:40.060] I did reference over 6 million transactions. [10:40.160 --> 10:43.040] So that is where I got the inspiration for this question. [10:45.040 --> 10:46.300] Yeah, but it should be efficient. [10:46.300 --> 10:49.640] We are doing our damn best to make sure it is as efficient as possible. [10:51.200 --> 10:53.840] Oh, JW got that one correct. [10:53.840 --> 10:55.620] Nat got that one incorrect. [10:57.000 --> 10:59.520] I don't think Doug got this one correct either. [10:59.800 --> 11:03.040] NeedMoney90 censored. Totally not the same set of people. [11:03.040 --> 11:08.020] JW, I know that your life is basically just knowing crypto trivia. [11:08.020 --> 11:09.540] It is basically your full-time job. [11:09.540 --> 11:11.160] You don't need to convince me otherwise. [11:11.160 --> 11:14.360] I know. But Andres, you got the last three correct. [11:14.360 --> 11:16.740] So look at you. You are killing it too. [11:17.020 --> 11:19.480] Still anybody's game here, really. [11:19.480 --> 11:21.580] We have a ton of questions left. [11:22.800 --> 11:26.700] Basically, yes. It basically is. Do not deny it. [11:26.800 --> 11:28.140] Question 5. [11:32.340 --> 11:33.480] Not how. [11:36.860 --> 11:39.820] Okay, that is the freebie. I have to throw these in here. [11:39.820 --> 11:41.760] What is the best answer here? [11:43.920 --> 11:45.060] Not how. [11:45.300 --> 11:46.980] See, I am making mistakes all the time. [11:46.980 --> 11:47.940] It should be which. [11:51.440 --> 11:53.380] Come on. Get those answers in. [11:53.380 --> 11:55.680] Whose channel? Get it in. [11:56.860 --> 11:59.600] And if you are watching now and want to join in this... [11:59.600 --> 12:01.140] I mean, I was going to call it fun. [12:01.140 --> 12:04.280] But I was instead going to call it rant slash chaos. [12:04.280 --> 12:08.060] You can join going to Kahoot.it, game pin 354661. [12:08.400 --> 12:11.980] People are doing so poorly that you can probably still beat a lot of them. [12:12.060 --> 12:14.700] Manero says no is the best answer here. [12:14.740 --> 12:17.940] You know what? NeedMoney90, that is not verifiable. [12:17.940 --> 12:20.180] So I am going to call BS on that one. [12:20.180 --> 12:24.840] And I am going to think that Manero says no is still probably the best answer here. [12:25.440 --> 12:28.640] This is just basically my low-effort chill here. [12:28.640 --> 12:31.400] Just to give people some chance of getting on the leaderboard. [12:31.400 --> 12:33.820] And one person apparently threw that one away anyway. [12:34.180 --> 12:37.120] So a lot of people are getting free points here. Thank goodness. [12:37.180 --> 12:38.520] Bitconnect is the highest climb. [12:38.520 --> 12:40.940] We are making our way up five places. [12:40.940 --> 12:45.300] That means we are going to explode over the next few rounds. [12:45.300 --> 12:46.100] And then die. [12:46.100 --> 12:48.320] I am not getting anything correct. [12:48.600 --> 12:50.960] So there is that going for it. [12:52.080 --> 12:54.020] We are still on the top of the leaderboard. [12:54.020 --> 12:57.620] Still only within three questions. [12:59.940 --> 13:03.280] So let us see what the next question is. [13:03.280 --> 13:04.440] Question six. [13:04.640 --> 13:07.920] What is the name of Manero's current mining algorithm? [13:08.200 --> 13:09.400] His name is Bitconnect. [13:57.370 --> 13:58.950] Okay, whole fan back. [13:58.950 --> 14:00.550] I do not know what happened there. [14:00.550 --> 14:02.250] But luckily no one got it correct. [14:02.290 --> 14:03.970] We are fine. [14:06.230 --> 14:07.550] Screw you. [14:10.170 --> 14:12.250] Okay, so we had a question that came in. [14:12.250 --> 14:14.970] What was the name of Manero's current mining algorithm? [14:15.330 --> 14:18.610] One person guessed by just clicking a random button. [14:18.610 --> 14:20.450] And they did not get it correct. [14:21.270 --> 14:23.090] I genuinely do not know what happened. [14:23.090 --> 14:24.830] My internet just totally dropped out. [14:24.830 --> 14:26.610] I think the stream was out too. [14:26.770 --> 14:28.950] So very odd stuff. [14:29.870 --> 14:31.130] Gotta love Comcast. [14:31.130 --> 14:33.430] I had to switch to Comcast after I moved. [14:33.570 --> 14:37.630] I know a lot of people probably would have gotten this one correct. [14:37.630 --> 14:38.890] But no one did. [14:38.890 --> 14:41.670] So it did break everyone's streaks I guess. [14:41.670 --> 14:46.530] So if you did have a streak, perhaps Andreas, you are most negatively impacted. [14:46.530 --> 14:49.730] Yeah, see Vic, the reason it crashed was because I knew you would get it right. [14:49.730 --> 14:50.790] And I just could not let you. [14:53.090 --> 14:54.730] Sorry about that everybody. [14:54.730 --> 14:57.090] Luckily that does not change the scoreboard at all. [14:57.090 --> 15:00.150] It resets your streaks, but I guess that is more fair anyway. [15:02.530 --> 15:06.050] But I am just glad that one random person did not select the first option. [15:06.450 --> 15:07.830] We have to decentralize Kahoot! [15:07.830 --> 15:10.610] Yes, I need to have a Kahoot satellite. [15:10.610 --> 15:12.370] A satellite internet connection. [15:12.370 --> 15:14.990] And we all need to be connected to each other of course. [15:15.090 --> 15:19.890] Otherwise we are just going to have to be dealing with this BS that is going on. [15:21.950 --> 15:24.130] I don't know what happened to my internet connection there. [15:24.130 --> 15:27.350] But good thing it happened to me now while playing Kahoot! [15:27.410 --> 15:29.050] Instead of when it actually mattered. [15:29.050 --> 15:31.050] When someone else's talk was on. [15:31.330 --> 15:33.650] Okay, looks like we are back to normal though. [15:33.650 --> 15:35.890] I am going to move on to the next question. [15:35.890 --> 15:40.230] On what day will the next Monero network upgrade occur? [15:40.230 --> 15:53.420] October 1st, October 17th, October 31st, or November 1st? [15:53.840 --> 15:55.740] People are getting their responses in pretty quickly. [15:55.740 --> 15:56.560] That is good. [16:00.570 --> 16:02.970] Remember, there is a stream delay. [16:11.180 --> 16:14.720] Okay, October 17th is the correct answer. [16:14.720 --> 16:16.300] It is not the 31st, it is not the 1st. [16:16.300 --> 16:18.060] It is not the 1st of November either. [16:18.220 --> 16:20.700] That was a tough one, Monero. [16:20.700 --> 16:24.300] You need to pay attention to what is going on in the Monero community sometimes. [16:25.660 --> 16:28.760] We are fun sometimes too. [16:29.040 --> 16:30.080] Hopefully. [16:30.080 --> 16:31.880] We aspire to be fun sometimes. [16:32.400 --> 16:35.720] Congratulations on guessing correctly. [16:37.960 --> 16:40.660] Redacted made its way up six places. [16:40.660 --> 16:45.060] They are trying to eventually compete with Censored. [16:45.440 --> 16:47.100] JW is still in first place. [16:47.100 --> 16:48.420] But Censored moved up. [16:48.420 --> 16:50.340] They are beating Knack right now. [16:50.340 --> 16:52.440] Just because you are a smart researcher, [16:52.440 --> 16:55.280] does not mean you waste all your time on Reddit all the time. [16:56.400 --> 16:58.420] Maybe they are not all the same. [16:59.000 --> 16:59.860] I got a message. [16:59.860 --> 17:01.300] It is probably someone complaining. [17:03.140 --> 17:05.360] Knack was answering how to answer trivia. [17:05.360 --> 17:07.200] It looks like they figured it out. [17:10.060 --> 17:11.860] Someone said they misclicked. [17:13.420 --> 17:17.260] You will have to fight your way back up to the top here. [17:19.080 --> 17:20.880] Next question. [17:22.100 --> 17:26.200] Which of the following was implemented in Monero most recently? [17:26.720 --> 17:30.600] Dandelion++, RingCT, Pruning, or LMDB? [17:34.410 --> 17:37.270] I think you will notice that one of these future questions [17:37.270 --> 17:41.230] absolutely gives a little bit of extra [17:42.330 --> 17:43.930] advantage to others. [17:44.050 --> 17:46.970] To a certain user compared to others. [17:46.970 --> 17:49.470] I will leave it to figure out who it is. [17:49.470 --> 17:51.210] Most people got this one correct. [17:51.610 --> 17:53.530] RingCT is definitely not the right answer. [17:53.530 --> 17:56.650] That was implemented in very early 2017. [17:56.650 --> 17:59.070] Pruning is more recent than RingCT. [17:59.730 --> 18:02.390] Dandelion++ is the most recent. [18:02.390 --> 18:05.310] That was implemented earlier this year. [18:05.750 --> 18:09.790] It was a network upgrade in the sense that [18:09.790 --> 18:10.850] there was a major release. [18:10.850 --> 18:15.450] It was Monero's first major release [18:15.450 --> 18:17.870] that did not require a network upgrade. [18:17.870 --> 18:20.710] That's pretty exciting history for everyone there. [18:21.890 --> 18:23.190] Pretty cool stuff. [18:23.190 --> 18:25.590] Monero is stabilizing as an ecosystem. [18:28.570 --> 18:30.090] Alright, let's see. [18:30.090 --> 18:31.470] Most people got that one correct. [18:31.470 --> 18:34.270] Looks like no one on the top leaderboard did not get that one correct [18:34.270 --> 18:37.150] or answer slower than someone who was not there. [18:37.390 --> 18:41.610] We will have to take this leaderboard into the next round. [18:41.610 --> 18:43.510] JW is still on top. [18:58.490 --> 19:01.490] Now granted, I will admit that I did not know [19:01.490 --> 19:03.930] that Nack would play this game. [19:06.330 --> 19:08.550] Some people who want to point fingers [19:08.550 --> 19:11.730] might try and claim that I'm biased [19:11.730 --> 19:14.670] towards helping them out. I don't know where they're getting that from. [19:14.670 --> 19:16.530] I don't think that's a fair assessment. [19:22.100 --> 19:26.000] But yes, the correct answer is tagging outputs with a sub-address hash. [19:26.000 --> 19:28.180] This was meant to be the hardest question in the quiz. [19:28.960 --> 19:31.200] Nice even split there, but no one thought [19:31.200 --> 19:34.260] that they would bin decoy outputs by block, which I'm a little surprised [19:34.260 --> 19:37.140] because that's something people have proposed at certain times. [19:37.140 --> 19:40.520] Maybe people acknowledge that that is not a potentially radical idea. [19:40.520 --> 19:42.540] That's one that's been proposed a few times. [19:42.540 --> 19:46.940] In fact, in many external research papers in Monero, they do talk about binning, [19:46.940 --> 19:50.040] which basically says when you choose a decoy, [19:50.040 --> 19:52.020] choose it in relation to your actual spend [19:52.020 --> 19:55.560] in a way to conceivably choose decoys [19:55.560 --> 19:56.880] under certain scenarios. [19:57.620 --> 19:59.940] But yes, this is purposely meant to be a tough one. [19:59.960 --> 20:03.940] Tagging outputs with a sub-address hash is the actual answer. [20:03.940 --> 20:08.280] Again, this is a very controversial idea. It will not necessarily be implemented. [20:08.320 --> 20:11.500] There's a bunch of potential advantages and disadvantages. [20:11.560 --> 20:14.220] So this one will go through a ton of discussion [20:14.220 --> 20:16.260] before anyone even moves on it. [20:16.940 --> 20:19.600] So this may have changed up the leaderboard. [20:19.600 --> 20:23.580] Let's see how much people are paying attention in MRL meetings. [20:24.620 --> 20:26.300] Of course JW got that one correct. [20:26.300 --> 20:28.220] In fact, it did not change the leaderboard at all. [20:28.220 --> 20:29.980] And of course, Knack got that one correct. [20:29.980 --> 20:33.320] You're welcome for the free points, Knack, to get you in closer striking distance [20:33.320 --> 20:35.440] of censored and non-various. [20:36.300 --> 20:38.600] But people further down must have gotten that one correct, [20:38.600 --> 20:41.860] which means Meow, especially, [20:41.860 --> 20:44.860] is at higher risk of being overrun. [20:44.860 --> 20:47.320] So we'll see what happens there. [20:51.280 --> 20:53.140] Yeah, someone's sending me questions on [20:54.220 --> 20:57.720] Defcon, but it's not relevant to trivia and that's all I care about at the moment. [20:57.720 --> 21:00.880] So, JW also has a streak [21:00.880 --> 21:03.320] of the last three in a row. Let's see what the next question is. [21:03.320 --> 21:06.760] Question 10. What was the original name for the Monero Community [21:07.220 --> 21:09.480] Workgroup? Was it the Marketing Workgroup, [21:09.480 --> 21:12.660] the Outreach Workgroup, the Developer Workgroup, or the Website [21:12.660 --> 21:13.580] Workgroup? [21:15.620 --> 21:19.000] Keeping in mind that the person who started this initiative was not me. [21:19.000 --> 21:21.260] I cannot take credit for this. It was Diego. [21:28.400 --> 21:30.100] Okay, at least half the people [21:30.100 --> 21:32.920] got this one correct. It was originally the Marketing [21:32.920 --> 21:36.420] Workgroup. The Outreach Workgroup is the name [21:36.420 --> 21:39.060] for a later formed and currently [21:39.060 --> 21:42.300] existing workgroup that took off [21:42.720 --> 21:45.120] a bunch of the initial ambitions [21:46.220 --> 21:46.880] of... [21:47.660 --> 21:51.200] Yeah, it took up a lot of the initial ambitions of the Marketing Workgroup. [21:51.200 --> 21:54.420] Now, at the time when this workgroup was started, [21:54.420 --> 21:57.080] the idea of marketing in Monero in [21:57.080 --> 22:00.380] general was very [22:00.380 --> 22:03.500] controversial. A lot of people hated the idea [22:03.500 --> 22:06.320] of talking about Monero in anything other [22:06.320 --> 22:09.340] than an academic or developer [22:09.340 --> 22:12.160] sense because they felt that anything else would diminish Monero compared [22:12.160 --> 22:15.140] to all the other, you know, shit [22:15.140 --> 22:18.120] coins, so-called, or scams [22:18.120 --> 22:20.340] that were out there, perhaps. And so [22:23.020 --> 22:23.700] the [22:24.160 --> 22:26.400] Marketing Workgroup initiative at the time was very [22:26.400 --> 22:29.740] controversial. And so we made very clear that the main focus [22:29.740 --> 22:32.860] was education to begin with, but even so, a lot of people did not [22:32.860 --> 22:36.000] like it. And after we started, it wasn't [22:36.000 --> 22:38.860] that we purposely wanted to drop these initiatives. [22:38.860 --> 22:41.900] That was not the case. But we felt that there wasn't [22:42.080 --> 22:44.800] a group that actually just brought people together and talked about stuff [22:44.800 --> 22:48.100] as a community. And so we renamed the Community [22:48.100 --> 22:51.280] Workgroup in order to best fit what we actually do. [22:51.280 --> 22:53.600] And then later down the line, the Outreach [22:54.080 --> 22:56.740] Workgroup came up and took the torch for some of those [22:57.240 --> 22:58.920] initial ambitions. [22:59.940 --> 23:03.000] Deafling was not the Developer Workgroup. Website Workgroup, I threw that in there [23:03.000 --> 23:05.480] just because someone may have known that Diego [23:06.040 --> 23:08.900] joined the community based off their desire to improve the website [23:08.900 --> 23:11.780] to begin with. And as Andres says [23:11.780 --> 23:14.780] in chat, the Monero Enterprise Alliance Working Group, you know [23:14.780 --> 23:17.880] that the Monero Enterprise Alliance was not a thing until [23:17.880 --> 23:20.700] what is it? Early [23:21.420 --> 23:24.120] 2017 it must have been. Yeah, it was during ConsenSys [23:24.800 --> 23:27.320] in... no, ConsenSys 2018. Sorry. [23:27.320 --> 23:30.280] It was ConsenSys 2018. So early 2018. [23:33.440 --> 23:35.620] There was an initial [23:35.620 --> 23:38.820] working group. It was like some investment [23:38.820 --> 23:42.200] focused Monero Workgroup that charged dues [23:42.200 --> 23:45.080] and things. That was really the first of its [23:45.080 --> 23:47.800] type. But they dissolved very early on. [23:48.220 --> 23:51.320] And certainly did not ever call themselves the Marketing [23:51.320 --> 23:53.420] or Monero Community Workgroup. [23:53.800 --> 23:55.960] So definitely very unrelated. [23:56.440 --> 24:00.000] Okay, let's see who got this one correct. Let's see if the top leaderboard [24:00.000 --> 24:02.760] changes. It does! Quite a bit. [24:02.760 --> 24:05.700] Knack is on fire. Looks like JW [24:05.700 --> 24:08.840] got that one incorrect. So Andres is within [24:08.840 --> 24:12.840] striking distance. So is Knack. They're all within one question of each other. [24:12.840 --> 24:15.900] And then within second place, within striking distance of one question, [24:15.900 --> 24:18.520] you have Censored and JTBB. So [24:18.520 --> 24:21.580] definitely fun competition going on here. [24:22.280 --> 24:24.640] And not too many questions left either. [24:25.180 --> 24:27.820] Question 11. What year did Monero first have [24:27.980 --> 24:30.940] a DEFCON Village? Because of course, this is Monero DEFCON Village. [24:30.940 --> 24:33.680] Is it 2017, 2018, 2019, or 2020? [24:33.680 --> 24:36.940] Note that I am not interpreting this strictly. I am not [24:36.940 --> 24:38.800] saying that like... [24:38.800 --> 24:41.860] It was the Monero and the Because Village. [24:41.860 --> 24:44.720] No, it's... I am counting Monero [24:44.720 --> 24:47.620] in that. I'm not saying Monero sole village. [24:53.190 --> 24:55.550] So hopefully someone was not trying to be [24:55.550 --> 24:58.230] like, eww, well, actually this... [24:58.230 --> 25:01.610] Nope, nope. I am being honest here. [25:01.630 --> 25:04.430] 2018 is the correct answer here. [25:04.430 --> 25:07.430] Yes, in 2017, it was very unofficial. [25:07.430 --> 25:10.390] There was not an official Monero DEFCON Village. In fact, [25:10.390 --> 25:13.230] you just had a number of individuals who were [25:13.230 --> 25:16.250] interested in Monero that attended DEFCON. Because, as you [25:16.250 --> 25:18.830] can imagine... [25:18.830 --> 25:22.790] Well, if you answered before the caveat, 2019 would have been your choice. [25:23.150 --> 25:25.150] Wow, Nero. So, no. [25:25.310 --> 25:28.750] No, he could not. 2019, it was the Monero Village. [25:28.750 --> 25:30.670] 2020 was the Monero Village. [25:32.110 --> 25:35.210] 2018, it was the Monero slash Because Village. [25:36.070 --> 25:36.930] Which is the [25:38.570 --> 25:38.930] blockchain... [25:38.930 --> 25:41.130] I actually don't remember what it stands for. [25:42.750 --> 25:45.610] Yeah, it's on me for not remembering what it stands for. [25:46.450 --> 25:47.850] 2017, a lot of Monero [25:49.270 --> 25:51.790] community members were at DEFCON. I was not one of them [25:51.790 --> 25:54.610] because I was not in that hemisphere. [25:55.170 --> 25:57.570] But, um... [25:57.570 --> 26:00.070] It, uh... [26:00.070 --> 26:03.510] Yeah, prompted people to be like, hey, wish we could have a Monero Village. And at the time, DEFCON [26:03.510 --> 26:06.350] seemed very uninterested in having a cryptocurrency village. [26:06.350 --> 26:10.530] But, in 2017, for that latter half, it exploded, of course. [26:10.670 --> 26:12.850] And Monero had a very large representation [26:12.850 --> 26:15.730] at DEFCON, and therefore were able to make this wonderful [26:15.730 --> 26:18.650] thing that we have right now out of it. So, that's really cool. [26:18.890 --> 26:21.690] So, let's see what five people got that one correct. [26:24.110 --> 26:27.610] Cake is the highest climber. You made your way up three places. [26:27.610 --> 26:29.450] So, you're doing something right there. [26:30.690 --> 26:33.110] Censored moved their way up into third place. [26:33.110 --> 26:35.470] They must have answered quicker than Mac. [26:35.470 --> 26:38.350] Remember, you do get extra points by answering quicker. [26:38.350 --> 26:41.690] So, if you know the answer, get that in as soon as possible. [26:41.690 --> 26:45.730] Otherwise, you are giving up three points, and you don't want to lose. [26:46.650 --> 26:47.130] So... [26:47.130 --> 26:51.350] But, it's certainly still anyone's game to see who will win this. [26:51.810 --> 26:53.230] Question 12. [26:53.230 --> 26:57.430] Which of the following was never a Monero minimum or mandatory ring size? [26:57.430 --> 27:00.110] Was it 3, 5, 8, or 11? [27:22.600 --> 27:23.600] Okay. [27:24.840 --> 27:29.040] The majority of people got this incorrect, but the most chosen answer was the correct one. [27:29.040 --> 27:30.320] Yes, it is 8. [27:30.500 --> 27:34.940] For some reason, the Monero community is allergic to even numbers. [27:34.940 --> 27:38.140] We only choose odd numbers, and we only choose prime numbers. [27:38.140 --> 27:40.900] The minimum slash mandatory ring sizes [27:40.900 --> 27:42.760] have only ever been [27:42.760 --> 27:46.400] 3, 5, 7, and 11. [27:47.500 --> 27:49.360] It's just the way it works out. [27:50.840 --> 27:52.020] So, uh... [27:52.560 --> 27:56.300] I mean, you may argue that 0 was the initial one. [27:56.300 --> 27:58.400] It was the original minimum ring size. [27:58.400 --> 28:02.500] Actually, no. 1. 1, actually. 0 doesn't make any sense. It would have been 1. [28:03.880 --> 28:05.120] So, uh... [28:05.120 --> 28:08.900] Unless you're talking about coin-based outputs, and they're treated kind of technically differently. [28:08.900 --> 28:11.520] And then, if you want to get all super, super technical about it. [28:11.520 --> 28:14.300] But, really, the best answer here is 8. [28:14.920 --> 28:16.820] Which 6 people got correct. [28:17.880 --> 28:19.200] It was good while it lasted. [28:19.200 --> 28:21.300] Oh, Andres, what are you going to do? [28:22.360 --> 28:25.300] I have to say, 8 was one of the numbers I recommended. [28:25.300 --> 28:29.600] When we learned about the possible impact of chain-split attacks [28:29.600 --> 28:32.920] in Monero, when splitting coins is a really popular way [28:32.920 --> 28:34.660] to pump and dump something. [28:37.040 --> 28:38.840] I recommended a move to [28:38.840 --> 28:40.800] ring size 7 or 8. [28:40.800 --> 28:42.720] And we ultimately chose 7 [28:42.720 --> 28:45.320] for the additional efficiency. [28:45.320 --> 28:48.400] And also because we have a rule of prime numbers, allegedly. [28:48.700 --> 28:51.500] But, you know, when Monero goes to trip-tick [28:51.500 --> 28:55.260] or Arcturus, we might not actually go with the prime number. [28:55.260 --> 28:57.360] We might go with, like, 128. [28:57.360 --> 28:59.700] Which, you know, is divisible by 2. [28:59.700 --> 29:01.180] And, of course, other numbers. [29:02.160 --> 29:06.280] We may be shortly dropping this, depending on [29:06.280 --> 29:10.160] how quickly certain improvements are made in the Monero protocol. [29:10.320 --> 29:12.260] We may no longer be able to say this. [29:12.920 --> 29:14.700] But, in any case, [29:15.920 --> 29:18.720] Andres still stays in first place. [29:18.920 --> 29:21.260] Scott makes their way to fifth. [29:21.560 --> 29:22.920] So that's pretty cool. [29:24.400 --> 29:25.460] So, yeah. [29:27.240 --> 29:30.280] Is it a ring if it is just one? It's more like a point? [29:30.280 --> 29:33.700] Yeah, that's a good question. I don't know if you can actually really call [29:35.340 --> 29:37.100] a transaction with only one input [29:37.820 --> 29:40.060] a ring, really. It's like a [29:40.060 --> 29:43.760] very sad ring. [29:43.760 --> 29:45.900] JW is still on top here, but you have to remember [29:46.580 --> 29:48.520] and Cake has the longest streak with three in a row. [29:48.520 --> 29:51.580] So they might be making their way up. They're going to get the most bonus points [29:51.580 --> 29:54.820] if they get the next one correct for the longest streak. [29:55.380 --> 29:58.020] But, the next question [29:58.020 --> 30:00.100] is worth twice as many points. [30:00.100 --> 30:03.480] It is the last question. Winner takes all. [30:03.480 --> 30:05.140] You all best be prepared. [30:06.780 --> 30:09.040] Be ready. Be ready to click that button [30:09.040 --> 30:10.760] once you know the right answer. [30:11.920 --> 30:15.120] I don't know if it'll be easy or hard. I mean, I do know, but I'm just going to make it [30:15.120 --> 30:18.020] stressful as a result because it's fun for me to [30:18.020 --> 30:20.680] draw this out. But let's see what it is. [30:20.980 --> 30:24.040] Last question for all of the bragging rights. [30:24.300 --> 30:25.420] What is it? [30:25.420 --> 30:28.260] True or false? [30:28.260 --> 30:32.080] Double points. Monero offers ubiquitous privacy. [30:32.080 --> 30:34.560] True or false? True on the left, [30:34.560 --> 30:36.960] false on the right. What is it? [30:39.850 --> 30:42.070] For double points. [30:42.970 --> 30:47.660] If someone answers one way, [30:47.660 --> 30:50.640] I'm just going to like, you deserve not to get these points, [30:50.640 --> 30:51.640] I guess. [30:55.220 --> 30:56.500] Like, [30:56.500 --> 30:58.580] just for all intents and purposes, mandatory. [31:00.740 --> 31:02.740] Used in all transactions. [31:03.580 --> 31:04.920] Oh, goodness. [31:07.660 --> 31:08.680] Maybe I chose [31:08.920 --> 31:11.180] a word that... [31:13.260 --> 31:15.060] Vic read it wrong. [31:18.280 --> 31:19.400] We actually... [31:19.400 --> 31:20.620] This is actually the reading [31:20.620 --> 31:22.280] comprehension quiz. [31:29.400 --> 31:31.120] Oh, wow. [31:31.140 --> 31:32.560] Okay, well, [31:32.560 --> 31:35.420] apparently this is more of a trick question than I thought. [31:36.480 --> 31:38.120] Ubiquitous means like common [31:38.120 --> 31:40.720] or implemented widely [31:40.720 --> 31:44.120] or every transaction would have [31:44.120 --> 31:45.820] this type of privacy. [31:47.600 --> 31:50.040] It's meant to say that every transaction has [31:51.120 --> 31:53.580] privacy. I actually like you calling it ubiquitous [31:53.580 --> 31:56.600] rather than mandatory because, I mean, [31:56.600 --> 31:59.860] Monero has mandatory network privacy, but you can still opt out. [31:59.860 --> 32:02.440] So I usually try to refer to it as ubiquitous because [32:02.440 --> 32:05.560] it's, you know, every transaction has this feature. [32:06.620 --> 32:08.220] Breaking Monero. [32:08.540 --> 32:11.200] I'm going to break down this community by just using [32:11.200 --> 32:13.620] apparently fancy words here. [32:15.000 --> 32:16.040] But it is... [32:17.360 --> 32:19.680] True is the correct answer. [32:19.680 --> 32:22.260] Apparently I'm an English teacher [32:22.260 --> 32:24.280] that just likes to annoy people. [32:24.960 --> 32:28.700] Google Trends for Ubiquitous Spikes. [32:28.700 --> 32:30.920] The like... [32:31.680 --> 32:34.320] 14 people that participated in this game are going to [32:34.320 --> 32:36.520] send off the ubiquitous... [32:38.160 --> 32:38.880] Um... [32:42.200 --> 32:43.640] Yeah. [32:44.380 --> 32:46.100] That's funny. [32:47.180 --> 32:50.540] All right. Well, we get to see who finishes in the podium [32:50.540 --> 32:53.240] here, which apparently ended up just being an [32:53.240 --> 32:54.760] English test. [32:56.620 --> 32:59.340] Let's see who finishes on the podium. In third place [32:59.340 --> 33:02.260] with 8 out of 13 correct, Nack. [33:02.600 --> 33:05.440] Second place, also 8 out of 13, but with more [33:05.440 --> 33:08.480] points. Definitely not NeedMoney90. And in first [33:08.480 --> 33:11.940] place with 9 out of 13, Andres. [33:11.960 --> 33:14.000] So, wow, JW [33:14.000 --> 33:18.720] must not have gotten it correct. They were a runner-up. [33:18.840 --> 33:21.280] Wow, after all that time, I'm [33:21.280 --> 33:23.840] the top of the podium. [33:24.460 --> 33:27.420] They just... they didn't know a word. [33:27.800 --> 33:29.660] So, darn. Wow. [33:29.660 --> 33:33.100] It really did shake things up there at the end more than I was [33:33.100 --> 33:36.080] expecting. Y'all are going to be [33:36.080 --> 33:39.480] so angry with me as a result of this. [33:40.120 --> 33:41.680] Oh, goodness. [33:42.380 --> 33:44.820] That is hilarious. [33:44.860 --> 33:47.300] That was a lot of fun. [33:51.060 --> 33:53.560] Okay, yeah. So, Andres, you [33:55.180 --> 33:57.040] you offered some great advice [33:57.040 --> 34:00.040] during the meme competition, and you, as a result [34:00.040 --> 34:03.140] of helping us out then, you deserve first place. [34:03.140 --> 34:05.680] Everyone's saying I have a trick question. You know what? [34:05.940 --> 34:08.700] Ironically, the intent of the last question [34:08.700 --> 34:11.440] was actually to get one that everyone would get correct [34:11.440 --> 34:14.540] so they would feel good about themselves. But I think here [34:14.540 --> 34:17.240] it just gives people a rant, you know? [34:22.160 --> 34:24.580] I am utterly shocked [34:24.580 --> 34:27.780] that JW did not finish in the top [34:27.780 --> 34:30.060] three. That is awesome. [34:32.700 --> 34:36.380] Well, now you learned a word about that. [34:37.720 --> 34:40.360] Well, the whole point of this is to have fun. [34:40.360 --> 34:42.680] We've actually increased the number of people that have watched the stream [34:42.680 --> 34:45.960] as we've continued, at least on YouTube. [34:45.960 --> 34:47.940] So, thank you, everyone, for participating. [34:48.320 --> 34:51.340] Please, please, please tell everyone that you had fun with Monero [34:51.340 --> 34:53.500] because you've got to [34:54.280 --> 34:57.240] find your prize in WoW. [34:57.240 --> 34:59.520] Okay, I see. Persistent. [35:00.840 --> 35:02.280] I don't know. Persistent. [35:03.560 --> 35:05.280] What if you have [35:06.440 --> 35:09.660] quantum computing that comes out? It might not be permanently persistent [35:09.660 --> 35:12.280] if you want to be all technical, technical about it. [35:12.460 --> 35:15.740] Or what if all of the ring members that you participate in [35:15.740 --> 35:19.040] just happen to all disclose information and then do you really have [35:19.040 --> 35:20.380] persistent privacy? [35:21.040 --> 35:24.500] I don't know. I think ubiquitous is a better term. [35:26.420 --> 35:29.700] Maybe standardized is a different word. [35:30.160 --> 35:32.300] Pervasive, I think, is a good way to put it. [35:32.300 --> 35:36.320] I'll think about using pervasive, but you better all know for next time. [35:36.700 --> 35:39.280] In any case, thank you, everyone, for participating. [35:39.280 --> 35:41.900] This was a ton of fun for me. You all made it really fun. [35:41.900 --> 35:44.900] Thank you so much for yelling at me, commenting. [35:45.120 --> 35:47.780] The whole, like, it is a blast. [35:48.200 --> 35:50.520] DEF CON is fun when it's fun for everybody. [35:50.920 --> 35:53.160] So, widespread. [35:53.840 --> 35:56.460] That doesn't imply 100% honorees. [35:56.460 --> 36:00.540] I have to really point out that everybody does it. [36:00.540 --> 36:02.120] Which maybe ubiquitous doesn't either. [36:02.120 --> 36:06.080] In any case, I had a ton of fun. Thank you, everyone, for joining. [36:06.080 --> 36:08.400] It was great. I will see you [36:09.180 --> 36:12.560] tomorrow, hopefully, starting at 10 a.m. Pacific. [36:12.560 --> 36:14.540] Be there or be square. [36:15.000 --> 36:16.940] Bye, everybody.