WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:11.150 align:start position:0% oh<00:00:00.060> thank<00:00:00.989> you<00:00:01.110> all<00:00:01.290> for<00:00:01.530> attending<00:00:09.920> yes<00:00:10.920> oh 00:00:11.150 --> 00:00:11.160 align:start position:0% oh thank you all for attending yes oh 00:00:11.160 --> 00:00:14.900 align:start position:0% oh thank you all for attending yes oh maybe<00:00:11.340> we<00:00:11.580> start<00:00:11.910> off<00:00:12.059> with<00:00:12.950> what<00:00:13.950> you<00:00:14.820> know 00:00:14.900 --> 00:00:14.910 align:start position:0% maybe we start off with what you know 00:00:14.910 --> 00:00:17.870 align:start position:0% maybe we start off with what you know what<00:00:15.150> were<00:00:15.770> introduction<00:00:16.770> on<00:00:17.039> what<00:00:17.730> we're 00:00:17.870 --> 00:00:17.880 align:start position:0% what were introduction on what we're 00:00:17.880 --> 00:00:20.529 align:start position:0% what were introduction on what we're researching<00:00:18.770> what<00:00:19.770> were<00:00:20.010> you<00:00:20.369> know 00:00:20.529 --> 00:00:20.539 align:start position:0% researching what were you know 00:00:20.539 --> 00:00:22.700 align:start position:0% researching what were you know enthusiastic<00:00:21.539> with<00:00:21.689> plasma<00:00:21.869> and<00:00:22.320> then<00:00:22.470> maybe 00:00:22.700 --> 00:00:22.710 align:start position:0% enthusiastic with plasma and then maybe 00:00:22.710 --> 00:00:25.720 align:start position:0% enthusiastic with plasma and then maybe we<00:00:22.890> could<00:00:23.039> do<00:00:23.130> another<00:00:23.250> round<00:00:23.640> on<00:00:24.000> like 00:00:25.720 --> 00:00:25.730 align:start position:0% we could do another round on like 00:00:25.730 --> 00:00:28.480 align:start position:0% we could do another round on like actually<00:00:26.730> before<00:00:27.090> that<00:00:27.300> we<00:00:27.480> can<00:00:27.570> maybe<00:00:27.779> like 00:00:28.480 --> 00:00:28.490 align:start position:0% actually before that we can maybe like 00:00:28.490 --> 00:00:32.720 align:start position:0% actually before that we can maybe like give<00:00:29.490> a<00:00:30.240> I<00:00:31.109> think<00:00:31.890> it<00:00:31.949> would<00:00:32.040> be<00:00:32.130> fun<00:00:32.489> actually 00:00:32.720 --> 00:00:32.730 align:start position:0% give a I think it would be fun actually 00:00:32.730 --> 00:00:35.420 align:start position:0% give a I think it would be fun actually to<00:00:32.969> start<00:00:33.420> off<00:00:33.570> with<00:00:33.870> maybe<00:00:34.230> talking<00:00:35.130> about 00:00:35.420 --> 00:00:35.430 align:start position:0% to start off with maybe talking about 00:00:35.430 --> 00:00:38.959 align:start position:0% to start off with maybe talking about what<00:00:36.140> one<00:00:37.219> thinks<00:00:38.219> are<00:00:38.399> good 00:00:38.959 --> 00:00:38.969 align:start position:0% what one thinks are good 00:00:38.969 --> 00:00:42.709 align:start position:0% what one thinks are good e<00:00:39.770> applications<00:00:40.770> of<00:00:40.950> plasma<00:00:41.340> and<00:00:41.579> what<00:00:42.360> it's 00:00:42.709 --> 00:00:42.719 align:start position:0% e applications of plasma and what it's 00:00:42.719 --> 00:00:44.569 align:start position:0% e applications of plasma and what it's good<00:00:42.960> like<00:00:43.320> what<00:00:43.800> what<00:00:44.010> it<00:00:44.129> could<00:00:44.250> be<00:00:44.370> good<00:00:44.520> for 00:00:44.569 --> 00:00:44.579 align:start position:0% good like what what it could be good for 00:00:44.579 --> 00:00:46.639 align:start position:0% good like what what it could be good for what<00:00:45.239> it<00:00:45.329> could<00:00:45.420> maybe<00:00:45.629> not<00:00:45.809> be<00:00:45.960> good<00:00:46.079> for<00:00:46.140> and 00:00:46.639 --> 00:00:46.649 align:start position:0% what it could maybe not be good for and 00:00:46.649 --> 00:00:49.240 align:start position:0% what it could maybe not be good for and what<00:00:47.250> one<00:00:47.610> is<00:00:47.730> working<00:00:47.969> on<00:00:48.210> when<00:00:48.420> it<00:00:48.539> comes<00:00:48.570> to 00:00:49.240 --> 00:00:49.250 align:start position:0% what one is working on when it comes to 00:00:49.250 --> 00:00:52.010 align:start position:0% what one is working on when it comes to specifically<00:00:50.250> applications<00:00:51.180> and<00:00:51.420> that<00:00:51.899> way 00:00:52.010 --> 00:00:52.020 align:start position:0% specifically applications and that way 00:00:52.020 --> 00:01:08.350 align:start position:0% specifically applications and that way there's<00:00:52.230> some<00:00:52.379> context<00:01:06.200> mentioned<00:01:07.200> there 00:01:08.350 --> 00:01:08.360 align:start position:0% there's some context mentioned there 00:01:08.360 --> 00:01:10.850 align:start position:0% there's some context mentioned there okay<00:01:09.360> well<00:01:09.540> I'll<00:01:10.110> just<00:01:10.140> first<00:01:10.500> say<00:01:10.619> what<00:01:10.650> I 00:01:10.850 --> 00:01:10.860 align:start position:0% okay well I'll just first say what I 00:01:10.860 --> 00:01:13.160 align:start position:0% okay well I'll just first say what I think<00:01:11.369> are<00:01:11.549> good<00:01:12.090> applications<00:01:12.630> of<00:01:12.750> plasma 00:01:13.160 --> 00:01:13.170 align:start position:0% think are good applications of plasma 00:01:13.170 --> 00:01:14.210 align:start position:0% think are good applications of plasma because<00:01:13.350> I<00:01:13.409> think<00:01:13.470> that's<00:01:13.710> sort<00:01:14.010> of<00:01:14.130> the 00:01:14.210 --> 00:01:14.220 align:start position:0% because I think that's sort of the 00:01:14.220 --> 00:01:17.210 align:start position:0% because I think that's sort of the interesting<00:01:14.640> thing<00:01:14.790> here<00:01:16.220> obviously 00:01:17.210 --> 00:01:17.220 align:start position:0% interesting thing here obviously 00:01:17.220 --> 00:01:20.390 align:start position:0% interesting thing here obviously payments<00:01:17.700> in<00:01:17.759> exchange<00:01:18.119> or<00:01:18.390> like<00:01:18.630> the<00:01:19.400> plasma 00:01:20.390 --> 00:01:20.400 align:start position:0% payments in exchange or like the plasma 00:01:20.400 --> 00:01:22.070 align:start position:0% payments in exchange or like the plasma application<00:01:21.060> at<00:01:21.150> least<00:01:21.180> right<00:01:21.540> now<00:01:21.570> it's<00:01:21.960> sort 00:01:22.070 --> 00:01:22.080 align:start position:0% application at least right now it's sort 00:01:22.080 --> 00:01:25.789 align:start position:0% application at least right now it's sort of<00:01:22.229> the<00:01:22.979> the<00:01:23.250> thing<00:01:23.460> that's<00:01:23.670> most<00:01:24.710> you<00:01:25.710> know 00:01:25.789 --> 00:01:25.799 align:start position:0% of the the thing that's most you know 00:01:25.799 --> 00:01:30.560 align:start position:0% of the the thing that's most you know useful<00:01:26.790> or<00:01:27.030> novel<00:01:28.310> but<00:01:29.310> and<00:01:29.579> and<00:01:30.180> kind<00:01:30.509> of 00:01:30.560 --> 00:01:30.570 align:start position:0% useful or novel but and and kind of 00:01:30.570 --> 00:01:33.950 align:start position:0% useful or novel but and and kind of makes<00:01:31.470> use<00:01:31.710> of<00:01:31.740> this<00:01:32.009> blockchain<00:01:32.850> as<00:01:33.000> a<00:01:33.299> value 00:01:33.950 --> 00:01:33.960 align:start position:0% makes use of this blockchain as a value 00:01:33.960 --> 00:01:36.649 align:start position:0% makes use of this blockchain as a value store<00:01:34.350> slash<00:01:34.619> exchange<00:01:35.040> thing<00:01:35.520> but<00:01:36.180> it's 00:01:36.649 --> 00:01:36.659 align:start position:0% store slash exchange thing but it's 00:01:36.659 --> 00:01:37.789 align:start position:0% store slash exchange thing but it's other<00:01:36.990> stuff<00:01:37.079> that<00:01:37.290> I'm<00:01:37.470> really<00:01:37.619> excited 00:01:37.789 --> 00:01:37.799 align:start position:0% other stuff that I'm really excited 00:01:37.799 --> 00:01:40.580 align:start position:0% other stuff that I'm really excited about<00:01:37.950> is<00:01:38.250> gaming<00:01:39.119> in<00:01:39.240> general<00:01:39.600> it's<00:01:40.200> it's<00:01:40.439> one 00:01:40.580 --> 00:01:40.590 align:start position:0% about is gaming in general it's it's one 00:01:40.590 --> 00:01:42.170 align:start position:0% about is gaming in general it's it's one of<00:01:40.650> these<00:01:40.710> things<00:01:40.979> that<00:01:41.130> brings<00:01:41.430> people<00:01:41.729> in 00:01:42.170 --> 00:01:42.180 align:start position:0% of these things that brings people in 00:01:42.180 --> 00:01:45.230 align:start position:0% of these things that brings people in and<00:01:42.600> it's<00:01:42.840> simple<00:01:43.500> it's<00:01:43.799> not<00:01:43.979> threatening<00:01:44.340> you 00:01:45.230 --> 00:01:45.240 align:start position:0% and it's simple it's not threatening you 00:01:45.240 --> 00:01:48.499 align:start position:0% and it's simple it's not threatening you know<00:01:45.659> I'm<00:01:46.020> willing<00:01:46.500> to<00:01:46.530> put<00:01:47.130> $10<00:01:47.939> into<00:01:48.240> a<00:01:48.270> video 00:01:48.499 --> 00:01:48.509 align:start position:0% know I'm willing to put $10 into a video 00:01:48.509 --> 00:01:49.880 align:start position:0% know I'm willing to put $10 into a video game<00:01:48.689> and<00:01:48.869> I<00:01:48.930> don't<00:01:48.990> really<00:01:49.170> care<00:01:49.290> if<00:01:49.649> I<00:01:49.710> never 00:01:49.880 --> 00:01:49.890 align:start position:0% game and I don't really care if I never 00:01:49.890 --> 00:01:52.370 align:start position:0% game and I don't really care if I never play<00:01:50.100> that<00:01:50.250> video<00:01:50.340> game<00:01:50.520> again<00:01:50.939> and<00:01:51.240> and<00:01:51.960> you 00:01:52.370 --> 00:01:52.380 align:start position:0% play that video game again and and you 00:01:52.380 --> 00:01:55.460 align:start position:0% play that video game again and and you know<00:01:52.470> I<00:01:52.970> that<00:01:53.970> $10<00:01:54.600> is<00:01:54.780> just<00:01:55.020> gone<00:01:55.200> that's 00:01:55.460 --> 00:01:55.470 align:start position:0% know I that $10 is just gone that's 00:01:55.470 --> 00:01:58.310 align:start position:0% know I that $10 is just gone that's that's<00:01:55.770> fine<00:01:56.009> and<00:01:56.280> so<00:01:56.689> the<00:01:57.689> same<00:01:58.020> doesn't 00:01:58.310 --> 00:01:58.320 align:start position:0% that's fine and so the same doesn't 00:01:58.320 --> 00:02:00.740 align:start position:0% that's fine and so the same doesn't apply<00:01:58.469> if<00:01:59.009> we're<00:01:59.189> talking<00:01:59.460> about<00:01:59.610> payments<00:02:00.540> I 00:02:00.740 --> 00:02:00.750 align:start position:0% apply if we're talking about payments I 00:02:00.750 --> 00:02:03.469 align:start position:0% apply if we're talking about payments I expect<00:02:01.530> that<00:02:01.770> my<00:02:01.799> bank<00:02:02.219> app<00:02:02.520> doesn't<00:02:02.909> lose<00:02:03.240> my 00:02:03.469 --> 00:02:03.479 align:start position:0% expect that my bank app doesn't lose my 00:02:03.479 --> 00:02:06.350 align:start position:0% expect that my bank app doesn't lose my money<00:02:04.159> but<00:02:05.159> I<00:02:05.219> have<00:02:05.460> different<00:02:05.640> expectations 00:02:06.350 --> 00:02:06.360 align:start position:0% money but I have different expectations 00:02:06.360 --> 00:02:09.949 align:start position:0% money but I have different expectations on<00:02:06.689> games<00:02:07.290> and<00:02:07.560> so<00:02:07.680> I<00:02:08.209> think<00:02:09.209> I<00:02:09.390> think<00:02:09.690> games 00:02:09.949 --> 00:02:09.959 align:start position:0% on games and so I think I think games 00:02:09.959 --> 00:02:11.930 align:start position:0% on games and so I think I think games are<00:02:10.140> actually<00:02:10.289> quite<00:02:10.800> feasible<00:02:11.310> today<00:02:11.790> with 00:02:11.930 --> 00:02:11.940 align:start position:0% are actually quite feasible today with 00:02:11.940 --> 00:02:12.830 align:start position:0% are actually quite feasible today with plasma<00:02:12.270> as 00:02:12.830 --> 00:02:12.840 align:start position:0% plasma as 00:02:12.840 --> 00:02:15.710 align:start position:0% plasma as lume<00:02:13.410> has<00:02:13.650> just<00:02:13.890> made<00:02:14.069> very<00:02:14.099> clear<00:02:14.819> and<00:02:15.000> I 00:02:15.710 --> 00:02:15.720 align:start position:0% lume has just made very clear and I 00:02:15.720 --> 00:02:17.360 align:start position:0% lume has just made very clear and I think<00:02:15.930> that<00:02:16.019> people<00:02:16.140> should<00:02:16.260> start<00:02:16.739> looking 00:02:17.360 --> 00:02:17.370 align:start position:0% think that people should start looking 00:02:17.370 --> 00:02:19.220 align:start position:0% think that people should start looking at<00:02:17.610> that<00:02:17.760> right<00:02:17.910> now<00:02:18.060> I'm<00:02:18.300> highly<00:02:18.840> interested 00:02:19.220 --> 00:02:19.230 align:start position:0% at that right now I'm highly interested 00:02:19.230 --> 00:02:24.589 align:start position:0% at that right now I'm highly interested in<00:02:19.440> getting<00:02:19.769> a<00:02:19.980> sort<00:02:20.730> of<00:02:21.709> plasma<00:02:23.390> kind<00:02:24.390> of<00:02:24.480> like 00:02:24.589 --> 00:02:24.599 align:start position:0% in getting a sort of plasma kind of like 00:02:24.599 --> 00:02:26.420 align:start position:0% in getting a sort of plasma kind of like an<00:02:24.720> SDK<00:02:25.140> setup<00:02:25.620> so<00:02:25.800> that<00:02:25.830> people<00:02:26.190> can<00:02:26.400> just 00:02:26.420 --> 00:02:26.430 align:start position:0% an SDK setup so that people can just 00:02:26.430 --> 00:02:28.309 align:start position:0% an SDK setup so that people can just build<00:02:26.790> these<00:02:27.060> games<00:02:27.390> without<00:02:28.140> really 00:02:28.309 --> 00:02:28.319 align:start position:0% build these games without really 00:02:28.319 --> 00:02:30.940 align:start position:0% build these games without really understanding<00:02:28.379> what<00:02:29.010> the<00:02:29.040> underlying<00:02:29.900> plasma 00:02:30.940 --> 00:02:30.950 align:start position:0% understanding what the underlying plasma 00:02:30.950 --> 00:02:43.250 align:start position:0% understanding what the underlying plasma does<00:02:39.110> sure<00:02:40.110> I'm<00:02:41.010> David<00:02:41.459> I<00:02:41.610> feel<00:02:41.849> like<00:02:42.260> with 00:02:43.250 --> 00:02:43.260 align:start position:0% does sure I'm David I feel like with 00:02:43.260 --> 00:02:44.809 align:start position:0% does sure I'm David I feel like with plasma<00:02:43.709> in<00:02:44.040> its<00:02:44.190> current<00:02:44.340> state<00:02:44.459> it's 00:02:44.809 --> 00:02:44.819 align:start position:0% plasma in its current state it's 00:02:44.819 --> 00:02:47.390 align:start position:0% plasma in its current state it's excellent<00:02:45.360> for<00:02:46.130> supporting<00:02:47.130> applications 00:02:47.390 --> 00:02:47.400 align:start position:0% excellent for supporting applications 00:02:47.400 --> 00:02:50.240 align:start position:0% excellent for supporting applications that<00:02:48.360> don't<00:02:48.540> require<00:02:48.989> an<00:02:49.410> incredible<00:02:50.010> amount 00:02:50.240 --> 00:02:50.250 align:start position:0% that don't require an incredible amount 00:02:50.250 --> 00:02:54.199 align:start position:0% that don't require an incredible amount of<00:02:50.489> interaction<00:02:51.260> with<00:02:52.260> like<00:02:52.470> the<00:02:52.799> rest<00:02:53.040> of<00:02:53.370> the 00:02:54.199 --> 00:02:54.209 align:start position:0% of interaction with like the rest of the 00:02:54.209 --> 00:02:57.830 align:start position:0% of interaction with like the rest of the like<00:02:54.750> the<00:02:55.380> loop<00:02:55.560> chain<00:02:55.590> ecosystem<00:02:56.840> just 00:02:57.830 --> 00:02:57.840 align:start position:0% like the loop chain ecosystem just 00:02:57.840 --> 00:02:59.600 align:start position:0% like the loop chain ecosystem just because<00:02:58.230> of<00:02:58.680> the<00:02:58.890> way<00:02:59.010> things<00:02:59.069> are<00:02:59.430> right<00:02:59.549> now 00:02:59.600 --> 00:02:59.610 align:start position:0% because of the way things are right now 00:02:59.610 --> 00:03:02.750 align:start position:0% because of the way things are right now with<00:03:00.000> the<00:03:00.030> food<00:03:00.269> chain<00:03:00.510> having<00:03:00.870> custody<00:03:01.760> it's 00:03:02.750 --> 00:03:02.760 align:start position:0% with the food chain having custody it's 00:03:02.760 --> 00:03:06.170 align:start position:0% with the food chain having custody it's super<00:03:03.480> great<00:03:03.690> for<00:03:03.750> modular<00:03:04.760> modular<00:03:05.760> systems 00:03:06.170 --> 00:03:06.180 align:start position:0% super great for modular modular systems 00:03:06.180 --> 00:03:09.500 align:start position:0% super great for modular modular systems and<00:03:07.019> then<00:03:07.319> also<00:03:07.980> I<00:03:08.400> would<00:03:08.640> say<00:03:08.910> I'm<00:03:09.209> very 00:03:09.500 --> 00:03:09.510 align:start position:0% and then also I would say I'm very 00:03:09.510 --> 00:03:12.170 align:start position:0% and then also I would say I'm very excited<00:03:10.019> about<00:03:10.140> the<00:03:10.769> potential<00:03:11.370> for<00:03:11.730> plasma 00:03:12.170 --> 00:03:12.180 align:start position:0% excited about the potential for plasma 00:03:12.180 --> 00:03:17.449 align:start position:0% excited about the potential for plasma chains<00:03:12.680> to<00:03:13.680> kind<00:03:13.980> of<00:03:14.810> work<00:03:16.100> like<00:03:17.100> down<00:03:17.280> the 00:03:17.449 --> 00:03:17.459 align:start position:0% chains to kind of work like down the 00:03:17.459 --> 00:03:19.940 align:start position:0% chains to kind of work like down the road<00:03:17.609> they<00:03:18.540> can<00:03:18.600> be<00:03:18.870> more<00:03:19.139> private<00:03:19.560> than 00:03:19.940 --> 00:03:19.950 align:start position:0% road they can be more private than 00:03:19.950 --> 00:03:22.610 align:start position:0% road they can be more private than public<00:03:20.730> chains<00:03:20.970> and<00:03:21.600> so<00:03:21.780> excited<00:03:22.319> to<00:03:22.380> see<00:03:22.470> that 00:03:22.610 --> 00:03:22.620 align:start position:0% public chains and so excited to see that 00:03:22.620 --> 00:03:24.500 align:start position:0% public chains and so excited to see that explored<00:03:23.040> more<00:03:23.280> especially<00:03:23.850> with<00:03:24.180> the<00:03:24.359> plasma 00:03:24.500 --> 00:03:24.510 align:start position:0% explored more especially with the plasma 00:03:24.510 --> 00:03:27.229 align:start position:0% explored more especially with the plasma cash<00:03:24.900> architecture<00:03:25.590> where<00:03:26.549> users<00:03:27.030> don't 00:03:27.229 --> 00:03:27.239 align:start position:0% cash architecture where users don't 00:03:27.239 --> 00:03:30.229 align:start position:0% cash architecture where users don't actually<00:03:27.510> have<00:03:27.780> to<00:03:27.840> know<00:03:28.109> about<00:03:28.920> the<00:03:29.910> entire 00:03:30.229 --> 00:03:30.239 align:start position:0% actually have to know about the entire 00:03:30.239 --> 00:03:35.539 align:start position:0% actually have to know about the entire information<00:03:31.200> on<00:03:31.769> our<00:03:32.250> Jane<00:03:34.010> the<00:03:35.010> only<00:03:35.400> thing 00:03:35.539 --> 00:03:35.549 align:start position:0% information on our Jane the only thing 00:03:35.549 --> 00:03:37.849 align:start position:0% information on our Jane the only thing that<00:03:35.730> I<00:03:36.239> believe<00:03:36.420> what<00:03:37.200> makes<00:03:37.410> me<00:03:37.560> interested 00:03:37.849 --> 00:03:37.859 align:start position:0% that I believe what makes me interested 00:03:37.859 --> 00:03:39.890 align:start position:0% that I believe what makes me interested in<00:03:37.950> plasma<00:03:38.280> as<00:03:38.730> a<00:03:38.880> technique<00:03:39.239> is<00:03:39.450> the<00:03:39.690> fact 00:03:39.890 --> 00:03:39.900 align:start position:0% in plasma as a technique is the fact 00:03:39.900 --> 00:03:41.659 align:start position:0% in plasma as a technique is the fact that<00:03:40.079> you<00:03:40.200> can<00:03:40.349> settle<00:03:40.590> many<00:03:41.040> transactions 00:03:41.659 --> 00:03:41.669 align:start position:0% that you can settle many transactions 00:03:41.669 --> 00:03:43.400 align:start position:0% that you can settle many transactions whatever<00:03:42.569> they<00:03:42.750> may<00:03:42.930> be<00:03:42.989> whatever 00:03:43.400 --> 00:03:43.410 align:start position:0% whatever they may be whatever 00:03:43.410 --> 00:03:45.470 align:start position:0% whatever they may be whatever information<00:03:43.739> it<00:03:44.099> is<00:03:44.250> without<00:03:44.700> bloating<00:03:45.269> the 00:03:45.470 --> 00:03:45.480 align:start position:0% information it is without bloating the 00:03:45.480 --> 00:03:48.830 align:start position:0% information it is without bloating the chain<00:03:45.690> so<00:03:45.930> you<00:03:45.989> know<00:03:46.169> like<00:03:46.349> the<00:03:47.280> casual<00:03:47.940> let's 00:03:48.830 --> 00:03:48.840 align:start position:0% chain so you know like the casual let's 00:03:48.840 --> 00:03:51.440 align:start position:0% chain so you know like the casual let's say<00:03:49.280> Bitcoin<00:03:50.280> logic<00:03:50.669> that<00:03:50.880> you<00:03:51.000> don't<00:03:51.209> want<00:03:51.359> to 00:03:51.440 --> 00:03:51.450 align:start position:0% say Bitcoin logic that you don't want to 00:03:51.450 --> 00:03:53.569 align:start position:0% say Bitcoin logic that you don't want to put<00:03:51.599> any<00:03:51.870> data<00:03:52.230> more<00:03:52.650> than<00:03:52.709> what's<00:03:53.069> necessary 00:03:53.569 --> 00:03:53.579 align:start position:0% put any data more than what's necessary 00:03:53.579 --> 00:03:55.159 align:start position:0% put any data more than what's necessary and<00:03:53.700> I<00:03:53.940> believe<00:03:54.209> that's<00:03:54.389> the<00:03:54.450> general<00:03:54.750> problem 00:03:55.159 --> 00:03:55.169 align:start position:0% and I believe that's the general problem 00:03:55.169 --> 00:03:58.640 align:start position:0% and I believe that's the general problem good<00:03:55.290> apps<00:03:55.530> that<00:03:57.049> smart<00:03:58.049> contracts<00:03:58.500> they 00:03:58.640 --> 00:03:58.650 align:start position:0% good apps that smart contracts they 00:03:58.650 --> 00:04:01.879 align:start position:0% good apps that smart contracts they store<00:03:58.919> too<00:03:59.069> much<00:03:59.250> whatever<00:04:00.000> on<00:04:00.359> chain<00:04:00.599> so<00:04:01.290> you 00:04:01.879 --> 00:04:01.889 align:start position:0% store too much whatever on chain so you 00:04:01.889 --> 00:04:03.770 align:start position:0% store too much whatever on chain so you know<00:04:01.950> let's<00:04:02.190> put<00:04:02.370> just<00:04:02.940> 32<00:04:03.329> bytes<00:04:03.540> per 00:04:03.770 --> 00:04:03.780 align:start position:0% know let's put just 32 bytes per 00:04:03.780 --> 00:04:05.270 align:start position:0% know let's put just 32 bytes per whatever<00:04:04.109> amount<00:04:04.470> of<00:04:04.560> time<00:04:04.620> and<00:04:04.980> it's<00:04:05.069> better 00:04:05.270 --> 00:04:05.280 align:start position:0% whatever amount of time and it's better 00:04:05.280 --> 00:04:12.710 align:start position:0% whatever amount of time and it's better and<00:04:06.150> yeah<00:04:06.480> payments<00:04:10.669> well<00:04:11.669> it's<00:04:12.120> difficult<00:04:12.450> to 00:04:12.710 --> 00:04:12.720 align:start position:0% and yeah payments well it's difficult to 00:04:12.720 --> 00:04:15.890 align:start position:0% and yeah payments well it's difficult to get<00:04:12.780> you<00:04:12.959> every<00:04:13.109> single<00:04:13.260> said<00:04:13.530> before<00:04:13.950> I<00:04:14.900> think 00:04:15.890 --> 00:04:15.900 align:start position:0% get you every single said before I think 00:04:15.900 --> 00:04:17.839 align:start position:0% get you every single said before I think you<00:04:15.959> should<00:04:16.109> at<00:04:16.229> two<00:04:16.470> parts<00:04:16.859> first<00:04:17.039> as<00:04:17.310> the<00:04:17.609> Z 00:04:17.839 --> 00:04:17.849 align:start position:0% you should at two parts first as the Z 00:04:17.849 --> 00:04:20.750 align:start position:0% you should at two parts first as the Z key<00:04:18.060> based<00:04:18.440> plasmas<00:04:19.440> or<00:04:19.709> other<00:04:20.160> constructions 00:04:20.750 --> 00:04:20.760 align:start position:0% key based plasmas or other constructions 00:04:20.760 --> 00:04:22.610 align:start position:0% key based plasmas or other constructions like<00:04:21.000> the<00:04:21.299> metallic<00:04:21.539> propose<00:04:22.019> with<00:04:22.260> post<00:04:22.469> and 00:04:22.610 --> 00:04:22.620 align:start position:0% like the metallic propose with post and 00:04:22.620 --> 00:04:25.200 align:start position:0% like the metallic propose with post and also<00:04:22.800> data<00:04:23.370> on<00:04:23.669> chain 00:04:25.200 --> 00:04:25.210 align:start position:0% also data on chain 00:04:25.210 --> 00:04:29.680 align:start position:0% also data on chain okay<00:04:26.470> the<00:04:27.470> Z<00:04:28.130> key<00:04:28.280> based<00:04:28.850> plasmus<00:04:29.540> is<00:04:29.660> a 00:04:29.680 --> 00:04:29.690 align:start position:0% okay the Z key based plasmus is a 00:04:29.690 --> 00:04:31.420 align:start position:0% okay the Z key based plasmus is a plasmus<00:04:30.320> whereas<00:04:30.620> the<00:04:30.710> state-transition<00:04:30.920> is 00:04:31.420 --> 00:04:31.430 align:start position:0% plasmus whereas the state-transition is 00:04:31.430 --> 00:04:33.610 align:start position:0% plasmus whereas the state-transition is governed<00:04:31.790> by<00:04:31.880> snark<00:04:32.330> or<00:04:32.540> Stark<00:04:32.870> or<00:04:33.139> maybe 00:04:33.610 --> 00:04:33.620 align:start position:0% governed by snark or Stark or maybe 00:04:33.620 --> 00:04:35.230 align:start position:0% governed by snark or Stark or maybe other<00:04:33.860> features<00:04:34.310> you<00:04:34.430> keep<00:04:34.580> it<00:04:34.730> Ziqi 00:04:35.230 --> 00:04:35.240 align:start position:0% other features you keep it Ziqi 00:04:35.240 --> 00:04:38.950 align:start position:0% other features you keep it Ziqi construction<00:04:35.690> in<00:04:36.320> principle<00:04:36.980> it<00:04:37.340> is<00:04:37.960> mainly 00:04:38.950 --> 00:04:38.960 align:start position:0% construction in principle it is mainly 00:04:38.960 --> 00:04:40.840 align:start position:0% construction in principle it is mainly an<00:04:39.139> ultimate<00:04:39.530> goal<00:04:39.710> you<00:04:39.830> can<00:04:39.950> make<00:04:40.130> an<00:04:40.250> invalid 00:04:40.840 --> 00:04:40.850 align:start position:0% an ultimate goal you can make an invalid 00:04:40.850 --> 00:04:42.190 align:start position:0% an ultimate goal you can make an invalid state<00:04:41.030> transition<00:04:41.450> but<00:04:41.630> you<00:04:41.720> still<00:04:41.930> have<00:04:42.080> the 00:04:42.190 --> 00:04:42.200 align:start position:0% state transition but you still have the 00:04:42.200 --> 00:04:44.379 align:start position:0% state transition but you still have the data<00:04:42.380> availability<00:04:42.790> an<00:04:43.790> intermediate 00:04:44.379 --> 00:04:44.389 align:start position:0% data availability an intermediate 00:04:44.389 --> 00:04:46.030 align:start position:0% data availability an intermediate solution<00:04:44.540> was<00:04:44.960> introduced<00:04:45.380> by<00:04:45.500> vitalik<00:04:45.889> in<00:04:45.980> a 00:04:46.030 --> 00:04:46.040 align:start position:0% solution was introduced by vitalik in a 00:04:46.040 --> 00:04:48.250 align:start position:0% solution was introduced by vitalik in a recent<00:04:46.340> post<00:04:46.550> I<00:04:47.000> think<00:04:47.240> two<00:04:47.510> weeks<00:04:47.600> ago<00:04:47.960> and 00:04:48.250 --> 00:04:48.260 align:start position:0% recent post I think two weeks ago and 00:04:48.260 --> 00:04:50.800 align:start position:0% recent post I think two weeks ago and his<00:04:48.470> research<00:04:48.800> where<00:04:49.490> it<00:04:49.669> says<00:04:49.880> well<00:04:50.120> post 00:04:50.800 --> 00:04:50.810 align:start position:0% his research where it says well post 00:04:50.810 --> 00:04:52.780 align:start position:0% his research where it says well post also<00:04:51.169> data<00:04:51.320> on<00:04:51.620> chain<00:04:51.980> and<00:04:52.250> make<00:04:52.460> it<00:04:52.639> as<00:04:52.760> a 00:04:52.780 --> 00:04:52.790 align:start position:0% also data on chain and make it as a 00:04:52.790 --> 00:04:55.480 align:start position:0% also data on chain and make it as a public<00:04:53.150> input<00:04:53.270> to<00:04:53.480> your<00:04:53.570> snark<00:04:53.810> and<00:04:54.050> here<00:04:55.010> good 00:04:55.480 --> 00:04:55.490 align:start position:0% public input to your snark and here good 00:04:55.490 --> 00:04:57.400 align:start position:0% public input to your snark and here good well<00:04:55.669> you<00:04:55.850> blowed<00:04:56.210> the<00:04:56.510> transaction<00:04:56.990> data<00:04:57.110> you 00:04:57.400 --> 00:04:57.410 align:start position:0% well you blowed the transaction data you 00:04:57.410 --> 00:04:59.409 align:start position:0% well you blowed the transaction data you pay<00:04:57.620> an<00:04:57.740> extra<00:04:57.980> guest<00:04:58.220> cast<00:04:58.460> but<00:04:59.030> still<00:04:59.300> you 00:04:59.409 --> 00:04:59.419 align:start position:0% pay an extra guest cast but still you 00:04:59.419 --> 00:05:01.090 align:start position:0% pay an extra guest cast but still you can<00:04:59.570> aggregate<00:04:59.870> a<00:05:00.110> lot<00:05:00.380> this<00:05:00.620> is<00:05:00.680> a<00:05:00.830> great 00:05:01.090 --> 00:05:01.100 align:start position:0% can aggregate a lot this is a great 00:05:01.100 --> 00:05:02.650 align:start position:0% can aggregate a lot this is a great approach<00:05:01.340> and<00:05:01.640> six<00:05:01.790> the<00:05:01.880> ultimate<00:05:02.330> plasma 00:05:02.650 --> 00:05:02.660 align:start position:0% approach and six the ultimate plasma 00:05:02.660 --> 00:05:04.330 align:start position:0% approach and six the ultimate plasma will<00:05:02.780> still<00:05:02.960> be<00:05:03.080> somehow<00:05:03.560> based<00:05:03.770> on<00:05:03.890> ZK<00:05:04.130> piece 00:05:04.330 --> 00:05:04.340 align:start position:0% will still be somehow based on ZK piece 00:05:04.340 --> 00:05:06.850 align:start position:0% will still be somehow based on ZK piece another<00:05:05.240> part<00:05:05.570> is<00:05:05.750> people<00:05:05.930> forget<00:05:06.440> and<00:05:06.620> we<00:05:06.710> had 00:05:06.850 --> 00:05:06.860 align:start position:0% another part is people forget and we had 00:05:06.860 --> 00:05:09.220 align:start position:0% another part is people forget and we had this<00:05:06.980> discussion<00:05:07.040> earlier<00:05:07.610> before<00:05:08.230> original 00:05:09.220 --> 00:05:09.230 align:start position:0% this discussion earlier before original 00:05:09.230 --> 00:05:11.050 align:start position:0% this discussion earlier before original plasma<00:05:09.500> paper<00:05:09.740> had<00:05:10.160> a<00:05:10.460> part<00:05:10.760> about<00:05:11.000> a 00:05:11.050 --> 00:05:11.060 align:start position:0% plasma paper had a part about a 00:05:11.060 --> 00:05:13.659 align:start position:0% plasma paper had a part about a MapReduce<00:05:11.419> functionality<00:05:12.310> there<00:05:13.310> aware<00:05:13.640> a 00:05:13.659 --> 00:05:13.669 align:start position:0% MapReduce functionality there aware a 00:05:13.669 --> 00:05:15.190 align:start position:0% MapReduce functionality there aware a limited<00:05:14.120> sets<00:05:14.300> of<00:05:14.419> computation<00:05:14.810> which<00:05:15.080> are 00:05:15.190 --> 00:05:15.200 align:start position:0% limited sets of computation which are 00:05:15.200 --> 00:05:16.690 align:start position:0% limited sets of computation which are still<00:05:15.380> viable<00:05:15.590> this<00:05:15.860> way<00:05:16.010> for<00:05:16.190> example<00:05:16.280> what 00:05:16.690 --> 00:05:16.700 align:start position:0% still viable this way for example what 00:05:16.700 --> 00:05:18.969 align:start position:0% still viable this way for example what you<00:05:16.790> can<00:05:16.970> do<00:05:17.120> right<00:05:17.300> now<00:05:17.479> is<00:05:17.900> you<00:05:18.440> can<00:05:18.470> offload 00:05:18.969 --> 00:05:18.979 align:start position:0% you can do right now is you can offload 00:05:18.979 --> 00:05:20.800 align:start position:0% you can do right now is you can offload for<00:05:19.400> example<00:05:19.760> there's<00:05:19.940> no<00:05:20.060> qualification<00:05:20.690> of 00:05:20.800 --> 00:05:20.810 align:start position:0% for example there's no qualification of 00:05:20.810 --> 00:05:22.270 align:start position:0% for example there's no qualification of change<00:05:21.110> for<00:05:21.290> examples<00:05:21.590> a<00:05:21.620> recent<00:05:21.950> game<00:05:22.070> which 00:05:22.270 --> 00:05:22.280 align:start position:0% change for examples a recent game which 00:05:22.280 --> 00:05:24.040 align:start position:0% change for examples a recent game which is<00:05:22.400> governed<00:05:22.729> by<00:05:22.760> a<00:05:22.880> state<00:05:23.000> which<00:05:23.450> the<00:05:23.690> state 00:05:24.040 --> 00:05:24.050 align:start position:0% is governed by a state which the state 00:05:24.050 --> 00:05:26.590 align:start position:0% is governed by a state which the state is<00:05:24.169> governed<00:05:24.320> by<00:05:24.530> a<00:05:24.590> snark<00:05:24.889> in<00:05:25.160> the<00:05:26.000> principle 00:05:26.590 --> 00:05:26.600 align:start position:0% is governed by a snark in the principle 00:05:26.600 --> 00:05:28.900 align:start position:0% is governed by a snark in the principle the<00:05:26.900> only<00:05:27.110> part<00:05:27.350> you<00:05:27.410> actually<00:05:28.040> care<00:05:28.370> as<00:05:28.610> as 00:05:28.900 --> 00:05:28.910 align:start position:0% the only part you actually care as as 00:05:28.910 --> 00:05:30.550 align:start position:0% the only part you actually care as as the<00:05:29.000> state<00:05:29.210> transition<00:05:29.630> as<00:05:29.750> well<00:05:29.870> it<00:05:30.050> and<00:05:30.200> you 00:05:30.550 --> 00:05:30.560 align:start position:0% the state transition as well it and you 00:05:30.560 --> 00:05:32.290 align:start position:0% the state transition as well it and you can<00:05:30.710> applause<00:05:30.979> a<00:05:31.010> snark<00:05:31.430> verification<00:05:31.970> of 00:05:32.290 --> 00:05:32.300 align:start position:0% can applause a snark verification of 00:05:32.300 --> 00:05:34.450 align:start position:0% can applause a snark verification of change<00:05:32.750> to<00:05:32.960> some<00:05:33.140> operator<00:05:33.560> which<00:05:34.190> you<00:05:34.310> can 00:05:34.450 --> 00:05:34.460 align:start position:0% change to some operator which you can 00:05:34.460 --> 00:05:36.190 align:start position:0% change to some operator which you can easily<00:05:34.760> monitor<00:05:34.940> begets<00:05:35.540> nor<00:05:35.690> if<00:05:35.960> you<00:05:36.050> get 00:05:36.190 --> 00:05:36.200 align:start position:0% easily monitor begets nor if you get 00:05:36.200 --> 00:05:38.710 align:start position:0% easily monitor begets nor if you get snarky<00:05:36.350> vacations<00:05:36.950> to<00:05:37.100> milliseconds<00:05:37.640> so<00:05:38.090> is 00:05:38.710 --> 00:05:38.720 align:start position:0% snarky vacations to milliseconds so is 00:05:38.720 --> 00:05:40.930 align:start position:0% snarky vacations to milliseconds so is the<00:05:39.080> verification<00:05:39.290> and<00:05:39.830> it's<00:05:40.070> stateless<00:05:40.490> so 00:05:40.930 --> 00:05:40.940 align:start position:0% the verification and it's stateless so 00:05:40.940 --> 00:05:43.120 align:start position:0% the verification and it's stateless so this<00:05:41.270> approach<00:05:41.539> may<00:05:42.020> work<00:05:42.320> but<00:05:42.770> we<00:05:42.950> should 00:05:43.120 --> 00:05:43.130 align:start position:0% this approach may work but we should 00:05:43.130 --> 00:05:45.820 align:start position:0% this approach may work but we should maybe<00:05:43.700> focus<00:05:44.120> more<00:05:44.750> on<00:05:44.780> it<00:05:45.080> after<00:05:45.500> we<00:05:45.620> solve 00:05:45.820 --> 00:05:45.830 align:start position:0% maybe focus more on it after we solve 00:05:45.830 --> 00:05:50.140 align:start position:0% maybe focus more on it after we solve the<00:05:45.979> payments<00:05:46.340> and<00:05:46.460> exit<00:05:46.700> problem<00:05:48.850> yeah<00:05:49.850> just 00:05:50.140 --> 00:05:50.150 align:start position:0% the payments and exit problem yeah just 00:05:50.150 --> 00:05:51.550 align:start position:0% the payments and exit problem yeah just to<00:05:50.240> add<00:05:50.360> to<00:05:50.750> that<00:05:50.780> I<00:05:50.930> guess<00:05:51.200> a<00:05:51.229> lot<00:05:51.410> of<00:05:51.470> people 00:05:51.550 --> 00:05:51.560 align:start position:0% to add to that I guess a lot of people 00:05:51.560 --> 00:05:52.840 align:start position:0% to add to that I guess a lot of people ask<00:05:51.950> me<00:05:52.130> what's<00:05:52.310> the<00:05:52.370> difference<00:05:52.460> between 00:05:52.840 --> 00:05:52.850 align:start position:0% ask me what's the difference between 00:05:52.850 --> 00:05:55.300 align:start position:0% ask me what's the difference between plasma<00:05:53.360> and<00:05:53.690> sidechains<00:05:54.200> and<00:05:54.470> that<00:05:55.160> also 00:05:55.300 --> 00:05:55.310 align:start position:0% plasma and sidechains and that also 00:05:55.310 --> 00:05:59.320 align:start position:0% plasma and sidechains and that also plays<00:05:55.669> into<00:05:55.910> the<00:05:56.300> use<00:05:57.200> cases<00:05:57.470> so<00:05:58.060> in<00:05:59.060> general 00:05:59.320 --> 00:05:59.330 align:start position:0% plays into the use cases so in general 00:05:59.330 --> 00:06:01.600 align:start position:0% plays into the use cases so in general the<00:05:59.960> site<00:06:00.169> owners<00:06:00.560> if<00:06:00.740> you<00:06:00.890> have<00:06:01.070> transactions 00:06:01.600 --> 00:06:01.610 align:start position:0% the site owners if you have transactions 00:06:01.610 --> 00:06:03.820 align:start position:0% the site owners if you have transactions on<00:06:01.760> a<00:06:01.789> side<00:06:02.030> chain<00:06:02.270> you<00:06:02.570> basically<00:06:03.500> just<00:06:03.620> need 00:06:03.820 --> 00:06:03.830 align:start position:0% on a side chain you basically just need 00:06:03.830 --> 00:06:05.680 align:start position:0% on a side chain you basically just need to<00:06:03.950> calculate<00:06:04.220> the<00:06:04.729> amount<00:06:05.000> that<00:06:05.120> you<00:06:05.330> need<00:06:05.539> to 00:06:05.680 --> 00:06:05.690 align:start position:0% to calculate the amount that you need to 00:06:05.690 --> 00:06:07.680 align:start position:0% to calculate the amount that you need to bribe<00:06:06.169> the<00:06:06.440> validator<00:06:06.919> so<00:06:07.220> proof-of-work 00:06:07.680 --> 00:06:07.690 align:start position:0% bribe the validator so proof-of-work 00:06:07.690 --> 00:06:10.360 align:start position:0% bribe the validator so proof-of-work operators<00:06:08.690> with<00:06:08.870> and<00:06:09.080> you<00:06:09.620> know<00:06:09.770> how<00:06:09.919> secure 00:06:10.360 --> 00:06:10.370 align:start position:0% operators with and you know how secure 00:06:10.370 --> 00:06:12.400 align:start position:0% operators with and you know how secure your<00:06:10.490> transaction<00:06:11.000> is<00:06:11.150> the<00:06:11.330> main<00:06:12.229> difference 00:06:12.400 --> 00:06:12.410 align:start position:0% your transaction is the main difference 00:06:12.410 --> 00:06:14.620 align:start position:0% your transaction is the main difference I<00:06:12.770> think<00:06:12.800> the<00:06:13.039> plasma<00:06:13.490> is<00:06:13.610> that<00:06:13.789> on<00:06:13.910> plasma<00:06:14.300> you 00:06:14.620 --> 00:06:14.630 align:start position:0% I think the plasma is that on plasma you 00:06:14.630 --> 00:06:16.510 align:start position:0% I think the plasma is that on plasma you don't<00:06:14.870> do<00:06:15.050> that<00:06:15.229> calculation<00:06:15.740> the<00:06:16.070> answer<00:06:16.370> is 00:06:16.510 --> 00:06:16.520 align:start position:0% don't do that calculation the answer is 00:06:16.520 --> 00:06:19.480 align:start position:0% don't do that calculation the answer is you<00:06:16.970> need<00:06:17.120> to<00:06:17.300> bribe<00:06:17.539> the<00:06:17.840> theorem<00:06:18.470> proof<00:06:19.400> of 00:06:19.480 --> 00:06:19.490 align:start position:0% you need to bribe the theorem proof of 00:06:19.490 --> 00:06:23.590 align:start position:0% you need to bribe the theorem proof of work<00:06:20.169> so<00:06:21.169> we<00:06:21.500> kind<00:06:22.340> of<00:06:22.400> extend<00:06:22.880> the<00:06:23.060> security 00:06:23.590 --> 00:06:23.600 align:start position:0% work so we kind of extend the security 00:06:23.600 --> 00:06:25.840 align:start position:0% work so we kind of extend the security of<00:06:23.630> the<00:06:23.810> plasma<00:06:23.990> of<00:06:24.740> the<00:06:24.979> main<00:06:25.130> net<00:06:25.310> onto<00:06:25.580> the 00:06:25.840 --> 00:06:25.850 align:start position:0% of the plasma of the main net onto the 00:06:25.850 --> 00:06:27.700 align:start position:0% of the plasma of the main net onto the plasma<00:06:26.240> chain<00:06:26.450> that<00:06:26.930> is<00:06:27.050> not<00:06:27.229> done<00:06:27.440> with<00:06:27.620> the 00:06:27.700 --> 00:06:27.710 align:start position:0% plasma chain that is not done with the 00:06:27.710 --> 00:06:29.469 align:start position:0% plasma chain that is not done with the side<00:06:27.890> chains<00:06:28.130> and<00:06:28.370> I<00:06:28.490> think<00:06:28.700> that<00:06:29.210> works 00:06:29.469 --> 00:06:29.479 align:start position:0% side chains and I think that works 00:06:29.479 --> 00:06:32.860 align:start position:0% side chains and I think that works specifically<00:06:30.140> for<00:06:30.500> exchanges<00:06:31.430> and<00:06:31.640> all<00:06:32.150> apps 00:06:32.860 --> 00:06:32.870 align:start position:0% specifically for exchanges and all apps 00:06:32.870 --> 00:06:35.770 align:start position:0% specifically for exchanges and all apps and<00:06:33.140> have<00:06:33.380> high<00:06:34.039> deposits<00:06:34.640> so<00:06:35.030> at<00:06:35.479> the<00:06:35.630> moment 00:06:35.770 --> 00:06:35.780 align:start position:0% and have high deposits so at the moment 00:06:35.780 --> 00:06:36.820 align:start position:0% and have high deposits so at the moment we're<00:06:36.110> in<00:06:36.200> exchange 00:06:36.820 --> 00:06:36.830 align:start position:0% we're in exchange 00:06:36.830 --> 00:06:41.710 align:start position:0% we're in exchange deposit<00:06:37.820> size<00:06:38.000> exceeds<00:06:38.659> the<00:06:40.240> stake<00:06:41.240> size<00:06:41.479> of 00:06:41.710 --> 00:06:41.720 align:start position:0% deposit size exceeds the stake size of 00:06:41.720 --> 00:06:43.740 align:start position:0% deposit size exceeds the stake size of the<00:06:41.870> validators<00:06:42.440> it<00:06:42.590> rationally<00:06:43.159> makes<00:06:43.400> sense 00:06:43.740 --> 00:06:43.750 align:start position:0% the validators it rationally makes sense 00:06:43.750 --> 00:06:46.690 align:start position:0% the validators it rationally makes sense to<00:06:44.750> steal<00:06:45.020> and<00:06:45.260> that<00:06:45.830> is<00:06:45.950> not<00:06:46.130> true<00:06:46.340> for<00:06:46.370> plasma 00:06:46.690 --> 00:06:46.700 align:start position:0% to steal and that is not true for plasma 00:06:46.700 --> 00:06:48.580 align:start position:0% to steal and that is not true for plasma chains<00:06:47.090> so<00:06:47.360> that's<00:06:47.960> where<00:06:48.169> these<00:06:48.289> use<00:06:48.500> cases 00:06:48.580 --> 00:06:48.590 align:start position:0% chains so that's where these use cases 00:06:48.590 --> 00:06:52.180 align:start position:0% chains so that's where these use cases could<00:06:49.070> live<00:06:50.440> I'm<00:06:51.440> super<00:06:51.770> excited<00:06:51.860> about 00:06:52.180 --> 00:06:52.190 align:start position:0% could live I'm super excited about 00:06:52.190 --> 00:06:54.550 align:start position:0% could live I'm super excited about plasma<00:06:52.490> because<00:06:53.000> of<00:06:53.150> the<00:06:53.330> at<00:06:53.599> least<00:06:53.780> for<00:06:54.530> now 00:06:54.550 --> 00:06:54.560 align:start position:0% plasma because of the at least for now 00:06:54.560 --> 00:06:56.950 align:start position:0% plasma because of the at least for now the<00:06:54.800> you<00:06:55.580> know<00:06:55.669> scalable<00:06:56.240> payments<00:06:56.750> and 00:06:56.950 --> 00:06:56.960 align:start position:0% the you know scalable payments and 00:06:56.960 --> 00:06:59.409 align:start position:0% the you know scalable payments and exchange<00:06:57.530> type<00:06:57.979> stuff<00:06:58.310> because<00:06:58.760> we<00:06:58.970> are<00:06:59.090> close 00:06:59.409 --> 00:06:59.419 align:start position:0% exchange type stuff because we are close 00:06:59.419 --> 00:07:01.570 align:start position:0% exchange type stuff because we are close and<00:06:59.750> I<00:07:00.020> think<00:07:00.260> it's<00:07:00.349> really<00:07:00.680> important<00:07:01.130> for 00:07:01.570 --> 00:07:01.580 align:start position:0% and I think it's really important for 00:07:01.580 --> 00:07:03.940 align:start position:0% and I think it's really important for just<00:07:01.820> crypto<00:07:02.450> as<00:07:02.720> a<00:07:02.780> whole<00:07:03.200> to<00:07:03.440> like<00:07:03.650> one 00:07:03.940 --> 00:07:03.950 align:start position:0% just crypto as a whole to like one 00:07:03.950 --> 00:07:06.850 align:start position:0% just crypto as a whole to like one generate<00:07:04.580> a<00:07:04.610> lot<00:07:04.940> more<00:07:04.970> assets<00:07:05.840> and<00:07:06.020> to<00:07:06.530> make 00:07:06.850 --> 00:07:06.860 align:start position:0% generate a lot more assets and to make 00:07:06.860 --> 00:07:08.469 align:start position:0% generate a lot more assets and to make sure<00:07:06.890> that<00:07:07.039> those<00:07:07.340> assets<00:07:07.520> are<00:07:07.820> very<00:07:08.000> easy<00:07:08.210> to 00:07:08.469 --> 00:07:08.479 align:start position:0% sure that those assets are very easy to 00:07:08.479 --> 00:07:10.029 align:start position:0% sure that those assets are very easy to exchange<00:07:08.690> and<00:07:09.140> I<00:07:09.169> think<00:07:09.380> that<00:07:09.500> that<00:07:09.650> will<00:07:09.800> like 00:07:10.029 --> 00:07:10.039 align:start position:0% exchange and I think that that will like 00:07:10.039 --> 00:07:12.460 align:start position:0% exchange and I think that that will like facilitate<00:07:10.909> the<00:07:11.150> generation<00:07:11.870> of<00:07:12.020> value<00:07:12.140> in 00:07:12.460 --> 00:07:12.470 align:start position:0% facilitate the generation of value in 00:07:12.470 --> 00:07:15.370 align:start position:0% facilitate the generation of value in our<00:07:12.620> kind<00:07:13.039> of<00:07:13.130> like<00:07:13.520> weird<00:07:13.909> economy<00:07:14.570> and<00:07:14.750> so 00:07:15.370 --> 00:07:15.380 align:start position:0% our kind of like weird economy and so 00:07:15.380 --> 00:07:17.980 align:start position:0% our kind of like weird economy and so yeah<00:07:16.070> I'm<00:07:16.280> hopefully<00:07:16.880> plasma<00:07:17.330> can<00:07:17.510> can<00:07:17.810> play<00:07:17.960> a 00:07:17.980 --> 00:07:17.990 align:start position:0% yeah I'm hopefully plasma can can play a 00:07:17.990 --> 00:07:20.320 align:start position:0% yeah I'm hopefully plasma can can play a part<00:07:18.229> in<00:07:18.260> that<00:07:18.320> story<00:07:18.680> so<00:07:19.310> I<00:07:19.700> believe<00:07:20.240> we 00:07:20.320 --> 00:07:20.330 align:start position:0% part in that story so I believe we 00:07:20.330 --> 00:07:21.730 align:start position:0% part in that story so I believe we should<00:07:20.479> take<00:07:20.510> a<00:07:20.659> more<00:07:20.840> structured<00:07:21.140> format 00:07:21.730 --> 00:07:21.740 align:start position:0% should take a more structured format 00:07:21.740 --> 00:07:24.130 align:start position:0% should take a more structured format because<00:07:21.979> we're<00:07:22.159> just<00:07:22.190> like<00:07:22.930> talking<00:07:23.930> about 00:07:24.130 --> 00:07:24.140 align:start position:0% because we're just like talking about 00:07:24.140 --> 00:07:24.700 align:start position:0% because we're just like talking about the<00:07:24.260> vision 00:07:24.700 --> 00:07:24.710 align:start position:0% the vision 00:07:24.710 --> 00:07:27.790 align:start position:0% the vision let's<00:07:25.640> set<00:07:26.150> some<00:07:26.390> like<00:07:26.840> questions<00:07:27.320> like 00:07:27.790 --> 00:07:27.800 align:start position:0% let's set some like questions like 00:07:27.800 --> 00:07:38.380 align:start position:0% let's set some like questions like between<00:07:28.190> us<00:07:36.370> yeah<00:07:37.370> I<00:07:37.400> think<00:07:37.640> it'd<00:07:37.729> be<00:07:38.090> good<00:07:38.330> to 00:07:38.380 --> 00:07:38.390 align:start position:0% between us yeah I think it'd be good to 00:07:38.390 --> 00:07:40.149 align:start position:0% between us yeah I think it'd be good to definitely<00:07:38.870> get<00:07:39.050> into<00:07:39.229> that<00:07:39.470> because<00:07:39.800> we<00:07:40.039> have 00:07:40.149 --> 00:07:40.159 align:start position:0% definitely get into that because we have 00:07:40.159 --> 00:07:42.790 align:start position:0% definitely get into that because we have a<00:07:40.190> limited<00:07:40.370> time<00:07:40.580> I<00:07:41.240> think<00:07:41.900> as<00:07:42.110> long<00:07:42.680> as 00:07:42.790 --> 00:07:42.800 align:start position:0% a limited time I think as long as 00:07:42.800 --> 00:07:44.170 align:start position:0% a limited time I think as long as everyone<00:07:43.130> like<00:07:43.310> went<00:07:43.610> through<00:07:43.849> the 00:07:44.170 --> 00:07:44.180 align:start position:0% everyone like went through the 00:07:44.180 --> 00:07:46.469 align:start position:0% everyone like went through the introductions<00:07:44.690> and<00:07:44.840> they<00:07:44.900> wanted<00:07:45.140> to<00:07:45.200> make 00:07:46.469 --> 00:07:46.479 align:start position:0% introductions and they wanted to make 00:07:46.479 --> 00:07:50.170 align:start position:0% introductions and they wanted to make okay<00:07:47.479> for<00:07:48.260> me<00:07:48.380> like<00:07:48.740> right<00:07:49.250> now<00:07:49.490> my<00:07:49.760> principle 00:07:50.170 --> 00:07:50.180 align:start position:0% okay for me like right now my principle 00:07:50.180 --> 00:07:53.020 align:start position:0% okay for me like right now my principle area<00:07:50.479> is<00:07:50.900> that<00:07:51.409> you<00:07:52.340> know<00:07:52.430> beyond<00:07:52.880> what 00:07:53.020 --> 00:07:53.030 align:start position:0% area is that you know beyond what 00:07:53.030 --> 00:07:55.930 align:start position:0% area is that you know beyond what everyone<00:07:53.360> said<00:07:53.599> which<00:07:53.750> I<00:07:53.990> do<00:07:54.110> agree<00:07:54.470> with<00:07:54.940> like 00:07:55.930 --> 00:07:55.940 align:start position:0% everyone said which I do agree with like 00:07:55.940 --> 00:07:57.310 align:start position:0% everyone said which I do agree with like 100<00:07:56.419> percent<00:07:56.690> I<00:07:56.750> think<00:07:56.780> payments<00:07:57.260> are 00:07:57.310 --> 00:07:57.320 align:start position:0% 100 percent I think payments are 00:07:57.320 --> 00:07:59.760 align:start position:0% 100 percent I think payments are important<00:07:57.710> and<00:07:57.979> like<00:07:58.370> definitely<00:07:59.060> a<00:07:59.090> lot<00:07:59.300> of 00:07:59.760 --> 00:07:59.770 align:start position:0% important and like definitely a lot of 00:07:59.770 --> 00:08:02.170 align:start position:0% important and like definitely a lot of advantages<00:08:00.770> over<00:08:01.070> you<00:08:01.610> know<00:08:01.700> at<00:08:01.820> least<00:08:01.940> the 00:08:02.170 --> 00:08:02.180 align:start position:0% advantages over you know at least the 00:08:02.180 --> 00:08:05.710 align:start position:0% advantages over you know at least the federated<00:08:02.780> sidechain<00:08:03.140> models<00:08:04.090> another<00:08:05.090> major 00:08:05.710 --> 00:08:05.720 align:start position:0% federated sidechain models another major 00:08:05.720 --> 00:08:07.420 align:start position:0% federated sidechain models another major thing<00:08:06.080> that<00:08:06.380> I<00:08:06.409> think<00:08:06.650> could<00:08:06.740> be<00:08:06.770> very<00:08:07.280> helpful 00:08:07.420 --> 00:08:07.430 align:start position:0% thing that I think could be very helpful 00:08:07.430 --> 00:08:10.960 align:start position:0% thing that I think could be very helpful for<00:08:07.669> at<00:08:08.630> least<00:08:08.780> this<00:08:08.990> ecosystem<00:08:09.289> is<00:08:09.890> that<00:08:10.340> you 00:08:10.960 --> 00:08:10.970 align:start position:0% for at least this ecosystem is that you 00:08:10.970 --> 00:08:12.730 align:start position:0% for at least this ecosystem is that you know<00:08:11.060> you're<00:08:11.210> seeing<00:08:11.450> a<00:08:11.780> lot<00:08:12.110> of<00:08:12.349> you<00:08:12.710> know 00:08:12.730 --> 00:08:12.740 align:start position:0% know you're seeing a lot of you know 00:08:12.740 --> 00:08:14.770 align:start position:0% know you're seeing a lot of you know aetherium<00:08:13.550> me<00:08:13.700> toos<00:08:13.940> and<00:08:14.270> a<00:08:14.300> lot<00:08:14.450> of<00:08:14.479> people 00:08:14.770 --> 00:08:14.780 align:start position:0% aetherium me toos and a lot of people 00:08:14.780 --> 00:08:17.290 align:start position:0% aetherium me toos and a lot of people that<00:08:14.900> want<00:08:15.080> a<00:08:15.140> copy<00:08:15.320> aetherium<00:08:15.860> and<00:08:16.300> what's 00:08:17.290 --> 00:08:17.300 align:start position:0% that want a copy aetherium and what's 00:08:17.300 --> 00:08:20.709 align:start position:0% that want a copy aetherium and what's interesting<00:08:17.599> is<00:08:18.200> that<00:08:18.229> is<00:08:18.909> that<00:08:19.909> aetherium 00:08:20.709 --> 00:08:20.719 align:start position:0% interesting is that is that aetherium 00:08:20.719 --> 00:08:22.750 align:start position:0% interesting is that is that aetherium can<00:08:21.080> end<00:08:21.320> up<00:08:21.469> being<00:08:21.740> you<00:08:22.070> know<00:08:22.099> a<00:08:22.219> central 00:08:22.750 --> 00:08:22.760 align:start position:0% can end up being you know a central 00:08:22.760 --> 00:08:24.790 align:start position:0% can end up being you know a central point<00:08:22.880> between<00:08:23.479> a<00:08:23.750> lot<00:08:24.020> of<00:08:24.169> different<00:08:24.560> you 00:08:24.790 --> 00:08:24.800 align:start position:0% point between a lot of different you 00:08:24.800 --> 00:08:27.010 align:start position:0% point between a lot of different you know<00:08:24.919> block<00:08:25.130> chains<00:08:25.370> even<00:08:25.669> even<00:08:26.330> if<00:08:26.599> you<00:08:26.900> know 00:08:27.010 --> 00:08:27.020 align:start position:0% know block chains even even if you know 00:08:27.020 --> 00:08:28.540 align:start position:0% know block chains even even if you know let's<00:08:27.380> say<00:08:27.560> you<00:08:27.590> want<00:08:28.010> to<00:08:28.130> build<00:08:28.250> a<00:08:28.400> top 00:08:28.540 --> 00:08:28.550 align:start position:0% let's say you want to build a top 00:08:28.550 --> 00:08:30.909 align:start position:0% let's say you want to build a top ecosystem<00:08:29.240> inside<00:08:29.539> ethereum<00:08:30.020> I<00:08:30.169> think<00:08:30.680> you 00:08:30.909 --> 00:08:30.919 align:start position:0% ecosystem inside ethereum I think you 00:08:30.919 --> 00:08:33.159 align:start position:0% ecosystem inside ethereum I think you know<00:08:31.039> obviously<00:08:31.640> this<00:08:31.880> is<00:08:32.089> that<00:08:32.419> is<00:08:32.539> much<00:08:32.959> more 00:08:33.159 --> 00:08:33.169 align:start position:0% know obviously this is that is much more 00:08:33.169 --> 00:08:34.810 align:start position:0% know obviously this is that is much more advantage<00:08:33.500> advantageous<00:08:34.070> because<00:08:34.400> you<00:08:34.669> do 00:08:34.810 --> 00:08:34.820 align:start position:0% advantage advantageous because you do 00:08:34.820 --> 00:08:36.850 align:start position:0% advantage advantageous because you do have<00:08:35.030> you<00:08:35.570> know<00:08:35.599> people<00:08:35.959> that<00:08:36.169> you<00:08:36.469> know<00:08:36.589> the 00:08:36.850 --> 00:08:36.860 align:start position:0% have you know people that you know the 00:08:36.860 --> 00:08:38.920 align:start position:0% have you know people that you know the stock<00:08:37.579> is<00:08:37.729> there<00:08:37.940> the<00:08:38.180> community<00:08:38.570> is<00:08:38.719> there 00:08:38.920 --> 00:08:38.930 align:start position:0% stock is there the community is there 00:08:38.930 --> 00:08:41.199 align:start position:0% stock is there the community is there the<00:08:39.169> developers<00:08:39.620> are<00:08:39.800> there<00:08:39.979> but<00:08:40.520> even<00:08:40.699> with 00:08:41.199 --> 00:08:41.209 align:start position:0% the developers are there but even with 00:08:41.209 --> 00:08:43.000 align:start position:0% the developers are there but even with you<00:08:41.510> know<00:08:41.539> aetherium<00:08:41.959> e2s<00:08:42.500> they're<00:08:42.770> probably 00:08:43.000 --> 00:08:43.010 align:start position:0% you know aetherium e2s they're probably 00:08:43.010 --> 00:08:44.620 align:start position:0% you know aetherium e2s they're probably going<00:08:43.370> to<00:08:43.459> have<00:08:43.550> to<00:08:43.579> cross<00:08:43.910> through<00:08:44.150> aetherium 00:08:44.620 --> 00:08:44.630 align:start position:0% going to have to cross through aetherium 00:08:44.630 --> 00:08:45.970 align:start position:0% going to have to cross through aetherium and 00:08:45.970 --> 00:08:45.980 align:start position:0% and 00:08:45.980 --> 00:08:47.890 align:start position:0% and etherium<00:08:46.459> can<00:08:46.699> end<00:08:46.880> up<00:08:46.970> being<00:08:47.209> like<00:08:47.360> a<00:08:47.420> central 00:08:47.890 --> 00:08:47.900 align:start position:0% etherium can end up being like a central 00:08:47.900 --> 00:08:52.500 align:start position:0% etherium can end up being like a central trading<00:08:48.470> point<00:08:48.620> for<00:08:48.949> that<00:08:49.160> as<00:08:49.310> well 00:08:52.500 --> 00:08:52.510 align:start position:0% 00:08:52.510 --> 00:08:56.890 align:start position:0% all<00:08:53.510> right<00:08:53.690> I<00:08:53.750> have<00:08:53.930> a<00:08:53.960> question<00:08:54.080> so<00:08:55.900> with 00:08:56.890 --> 00:08:56.900 align:start position:0% all right I have a question so with 00:08:56.900 --> 00:08:59.500 align:start position:0% all right I have a question so with respect<00:08:57.080> to<00:08:57.320> Charlene<00:08:58.040> it<00:08:58.760> is<00:08:58.910> considered<00:08:59.330> a 00:08:59.500 --> 00:08:59.510 align:start position:0% respect to Charlene it is considered a 00:08:59.510 --> 00:09:00.790 align:start position:0% respect to Charlene it is considered a layer<00:08:59.750> 1<00:08:59.960> solution 00:09:00.790 --> 00:09:00.800 align:start position:0% layer 1 solution 00:09:00.800 --> 00:09:04.210 align:start position:0% layer 1 solution like<00:09:01.640> maybe<00:09:02.030> mechanism<00:09:02.630> because<00:09:03.110> they<00:09:03.500> actual 00:09:04.210 --> 00:09:04.220 align:start position:0% like maybe mechanism because they actual 00:09:04.220 --> 00:09:05.770 align:start position:0% like maybe mechanism because they actual the<00:09:04.400> whole<00:09:04.580> connection<00:09:04.910> between<00:09:05.240> the<00:09:05.510> beacon 00:09:05.770 --> 00:09:05.780 align:start position:0% the whole connection between the beacon 00:09:05.780 --> 00:09:09.100 align:start position:0% the whole connection between the beacon chain<00:09:05.990> and<00:09:06.200> the<00:09:06.350> short<00:09:06.770> chain<00:09:06.980> it<00:09:07.490> is<00:09:07.990> built<00:09:08.990> in 00:09:09.100 --> 00:09:09.110 align:start position:0% chain and the short chain it is built in 00:09:09.110 --> 00:09:11.080 align:start position:0% chain and the short chain it is built in the<00:09:09.200> protocol<00:09:09.500> and<00:09:09.740> there<00:09:10.190> are<00:09:10.280> no<00:09:10.430> gas<00:09:10.730> costs 00:09:11.080 --> 00:09:11.090 align:start position:0% the protocol and there are no gas costs 00:09:11.090 --> 00:09:13.990 align:start position:0% the protocol and there are no gas costs for<00:09:11.390> doing<00:09:11.420> that<00:09:11.750> so<00:09:12.350> I<00:09:12.380> was<00:09:12.770> I<00:09:13.040> kind<00:09:13.730> of<00:09:13.850> play 00:09:13.990 --> 00:09:14.000 align:start position:0% for doing that so I was I kind of play 00:09:14.000 --> 00:09:16.270 align:start position:0% for doing that so I was I kind of play around<00:09:14.120> with<00:09:14.390> the<00:09:14.540> idea<00:09:14.570> of<00:09:14.900> like<00:09:15.200> for<00:09:15.890> Kingo 00:09:16.270 --> 00:09:16.280 align:start position:0% around with the idea of like for Kingo 00:09:16.280 --> 00:09:19.690 align:start position:0% around with the idea of like for Kingo ethereum<00:09:16.790> or<00:09:17.000> parity<00:09:17.840> and<00:09:18.160> make<00:09:19.160> it<00:09:19.310> so<00:09:19.520> that 00:09:19.690 --> 00:09:19.700 align:start position:0% ethereum or parity and make it so that 00:09:19.700 --> 00:09:22.450 align:start position:0% ethereum or parity and make it so that there<00:09:19.880> is<00:09:19.970> a<00:09:21.010> basically<00:09:22.010> all<00:09:22.220> plasma 00:09:22.450 --> 00:09:22.460 align:start position:0% there is a basically all plasma 00:09:22.460 --> 00:09:24.880 align:start position:0% there is a basically all plasma operations<00:09:23.030> free<00:09:23.240> ok<00:09:24.230> but<00:09:24.440> in<00:09:24.530> a<00:09:24.590> way<00:09:24.710> that 00:09:24.880 --> 00:09:24.890 align:start position:0% operations free ok but in a way that 00:09:24.890 --> 00:09:26.290 align:start position:0% operations free ok but in a way that it's<00:09:25.010> not<00:09:25.160> possible<00:09:25.430> in<00:09:25.850> the<00:09:25.940> same<00:09:26.120> way<00:09:26.240> that 00:09:26.290 --> 00:09:26.300 align:start position:0% it's not possible in the same way that 00:09:26.300 --> 00:09:28.870 align:start position:0% it's not possible in the same way that how<00:09:26.570> like<00:09:26.840> the<00:09:27.050> proof<00:09:27.680> of<00:09:27.830> stake<00:09:27.980> as<00:09:28.700> per 00:09:28.870 --> 00:09:28.880 align:start position:0% how like the proof of stake as per 00:09:28.880 --> 00:09:30.820 align:start position:0% how like the proof of stake as per design<00:09:29.150> would<00:09:29.390> work<00:09:29.570> and<00:09:29.930> so<00:09:30.380> would<00:09:30.530> that<00:09:30.680> make 00:09:30.820 --> 00:09:30.830 align:start position:0% design would work and so would that make 00:09:30.830 --> 00:09:35.170 align:start position:0% design would work and so would that make plasma<00:09:31.160> later<00:09:31.370> on<00:09:31.550> discuss<00:09:34.060> doesn't<00:09:35.060> make 00:09:35.170 --> 00:09:35.180 align:start position:0% plasma later on discuss doesn't make 00:09:35.180 --> 00:09:39.910 align:start position:0% plasma later on discuss doesn't make sense<00:09:37.510> well<00:09:38.510> first<00:09:38.840> of<00:09:38.990> all<00:09:39.020> we<00:09:39.170> all<00:09:39.740> the 00:09:39.910 --> 00:09:39.920 align:start position:0% sense well first of all we all the 00:09:39.920 --> 00:09:41.980 align:start position:0% sense well first of all we all the possible<00:09:40.400> implementers<00:09:41.150> of<00:09:41.300> different<00:09:41.780> kind 00:09:41.980 --> 00:09:41.990 align:start position:0% possible implementers of different kind 00:09:41.990 --> 00:09:44.170 align:start position:0% possible implementers of different kind of<00:09:42.050> flavors<00:09:42.470> of<00:09:42.620> plasma<00:09:43.040> in<00:09:43.190> a<00:09:43.640> menu<00:09:43.850> of<00:09:43.970> those 00:09:44.170 --> 00:09:44.180 align:start position:0% of flavors of plasma in a menu of those 00:09:44.180 --> 00:09:47.920 align:start position:0% of flavors of plasma in a menu of those we<00:09:45.080> have<00:09:45.290> the<00:09:45.440> bonds<00:09:45.680> on<00:09:45.920> exits<00:09:46.780> first<00:09:47.780> you 00:09:47.920 --> 00:09:47.930 align:start position:0% we have the bonds on exits first you 00:09:47.930 --> 00:09:49.120 align:start position:0% we have the bonds on exits first you should<00:09:48.110> define<00:09:48.230> what<00:09:48.710> is<00:09:48.830> the<00:09:48.920> plasma 00:09:49.120 --> 00:09:49.130 align:start position:0% should define what is the plasma 00:09:49.130 --> 00:09:50.770 align:start position:0% should define what is the plasma operation<00:09:49.730> which<00:09:49.850> should<00:09:49.970> be<00:09:50.090> made<00:09:50.270> free<00:09:50.540> and 00:09:50.770 --> 00:09:50.780 align:start position:0% operation which should be made free and 00:09:50.780 --> 00:09:52.960 align:start position:0% operation which should be made free and in<00:09:51.680> principle<00:09:51.920> what<00:09:52.310> you're<00:09:52.430> proposing<00:09:52.700> more 00:09:52.960 --> 00:09:52.970 align:start position:0% in principle what you're proposing more 00:09:52.970 --> 00:09:55.360 align:start position:0% in principle what you're proposing more like<00:09:53.120> a<00:09:53.150> polka<00:09:53.600> dot<00:09:53.800> if<00:09:54.800> there<00:09:55.070> are<00:09:55.160> some 00:09:55.360 --> 00:09:55.370 align:start position:0% like a polka dot if there are some 00:09:55.370 --> 00:09:57.490 align:start position:0% like a polka dot if there are some special<00:09:56.000> smart<00:09:56.270> contracts<00:09:56.630> which<00:09:56.810> are<00:09:56.960> free<00:09:57.290> I 00:09:57.490 --> 00:09:57.500 align:start position:0% special smart contracts which are free I 00:09:57.500 --> 00:09:59.800 align:start position:0% special smart contracts which are free I think<00:09:57.980> it's<00:09:58.100> basic<00:09:58.460> philosophy<00:09:58.940> of<00:09:58.970> the<00:09:59.240> kiss 00:09:59.800 --> 00:09:59.810 align:start position:0% think it's basic philosophy of the kiss 00:09:59.810 --> 00:10:01.360 align:start position:0% think it's basic philosophy of the kiss system<00:10:00.140> I<00:10:00.350> mean<00:10:00.650> you<00:10:00.770> can<00:10:00.890> make<00:10:01.010> the<00:10:01.160> block 00:10:01.360 --> 00:10:01.370 align:start position:0% system I mean you can make the block 00:10:01.370 --> 00:10:03.820 align:start position:0% system I mean you can make the block spam<00:10:01.670> as<00:10:01.940> an<00:10:02.390> operator<00:10:02.810> as<00:10:03.020> a<00:10:03.050> central<00:10:03.470> party 00:10:03.820 --> 00:10:03.830 align:start position:0% spam as an operator as a central party 00:10:03.830 --> 00:10:06.580 align:start position:0% spam as an operator as a central party what<00:10:04.550> maybe<00:10:05.060> you<00:10:05.300> can<00:10:05.480> make<00:10:05.630> some<00:10:05.870> other<00:10:06.110> fancy 00:10:06.580 --> 00:10:06.590 align:start position:0% what maybe you can make some other fancy 00:10:06.590 --> 00:10:08.500 align:start position:0% what maybe you can make some other fancy stuff<00:10:06.740> which<00:10:07.040> you<00:10:07.070> name<00:10:07.340> they<00:10:07.820> make<00:10:08.270> out<00:10:08.480> right 00:10:08.500 --> 00:10:08.510 align:start position:0% stuff which you name they make out right 00:10:08.510 --> 00:10:11.530 align:start position:0% stuff which you name they make out right now<00:10:08.930> but<00:10:09.130> let's<00:10:10.130> start<00:10:10.430> with<00:10:10.520> without<00:10:11.330> this 00:10:11.530 --> 00:10:11.540 align:start position:0% now but let's start with without this 00:10:11.540 --> 00:10:16.390 align:start position:0% now but let's start with without this proposal<00:10:11.870> at<00:10:12.080> least<00:10:13.000> yeah<00:10:14.770> yeah<00:10:15.770> it's<00:10:16.100> kind<00:10:16.340> of 00:10:16.390 --> 00:10:16.400 align:start position:0% proposal at least yeah yeah it's kind of 00:10:16.400 --> 00:10:18.100 align:start position:0% proposal at least yeah yeah it's kind of like<00:10:16.460> the<00:10:16.760> whole<00:10:16.910> like<00:10:17.120> shelling<00:10:17.660> Fanta<00:10:17.960> type 00:10:18.100 --> 00:10:18.110 align:start position:0% like the whole like shelling Fanta type 00:10:18.110 --> 00:10:20.140 align:start position:0% like the whole like shelling Fanta type thing<00:10:18.350> where<00:10:18.560> once<00:10:18.860> you<00:10:18.980> start<00:10:19.280> making<00:10:19.850> in 00:10:20.140 --> 00:10:20.150 align:start position:0% thing where once you start making in 00:10:20.150 --> 00:10:22.150 align:start position:0% thing where once you start making in protocol<00:10:20.570> changes<00:10:21.200> or<00:10:21.530> like<00:10:21.770> layer<00:10:21.980> 1 00:10:22.150 --> 00:10:22.160 align:start position:0% protocol changes or like layer 1 00:10:22.160 --> 00:10:24.070 align:start position:0% protocol changes or like layer 1 protocol<00:10:22.580> changes<00:10:22.910> where<00:10:23.690> do<00:10:23.780> you<00:10:23.870> draw<00:10:23.990> the 00:10:24.070 --> 00:10:24.080 align:start position:0% protocol changes where do you draw the 00:10:24.080 --> 00:10:26.440 align:start position:0% protocol changes where do you draw the line<00:10:24.260> I'd<00:10:24.770> be<00:10:25.010> really<00:10:25.190> interested<00:10:25.400> in<00:10:26.000> seeing 00:10:26.440 --> 00:10:26.450 align:start position:0% line I'd be really interested in seeing 00:10:26.450 --> 00:10:29.590 align:start position:0% line I'd be really interested in seeing more<00:10:26.690> like<00:10:27.140> discussion<00:10:27.830> about<00:10:28.600> essentially 00:10:29.590 --> 00:10:29.600 align:start position:0% more like discussion about essentially 00:10:29.600 --> 00:10:32.800 align:start position:0% more like discussion about essentially coupling<00:10:30.500> are<00:10:30.830> like<00:10:31.160> combining<00:10:31.730> who<00:10:32.540> trained 00:10:32.800 --> 00:10:32.810 align:start position:0% coupling are like combining who trained 00:10:32.810 --> 00:10:34.540 align:start position:0% coupling are like combining who trained block<00:10:33.050> submission<00:10:33.530> between<00:10:33.920> plasma<00:10:34.160> chains 00:10:34.540 --> 00:10:34.550 align:start position:0% block submission between plasma chains 00:10:34.550 --> 00:10:37.240 align:start position:0% block submission between plasma chains because<00:10:35.450> that's<00:10:35.660> a<00:10:35.870> way<00:10:35.900> to<00:10:36.260> essentially 00:10:37.240 --> 00:10:37.250 align:start position:0% because that's a way to essentially 00:10:37.250 --> 00:10:39.700 align:start position:0% because that's a way to essentially reduce<00:10:37.880> the<00:10:38.090> cost<00:10:38.300> of<00:10:38.540> running<00:10:38.690> plasma<00:10:39.470> chains 00:10:39.700 --> 00:10:39.710 align:start position:0% reduce the cost of running plasma chains 00:10:39.710 --> 00:10:42.100 align:start position:0% reduce the cost of running plasma chains without<00:10:40.580> making<00:10:41.060> base<00:10:41.480> layer<00:10:41.660> protocol 00:10:42.100 --> 00:10:42.110 align:start position:0% without making base layer protocol 00:10:42.110 --> 00:10:46.300 align:start position:0% without making base layer protocol changes<00:10:44.020> so<00:10:45.020> I<00:10:45.050> think<00:10:45.170> some<00:10:45.770> of<00:10:45.860> my<00:10:45.950> concerns 00:10:46.300 --> 00:10:46.310 align:start position:0% changes so I think some of my concerns 00:10:46.310 --> 00:10:48.460 align:start position:0% changes so I think some of my concerns about<00:10:46.490> like<00:10:46.790> enshrining<00:10:47.750> anything<00:10:48.140> plasma 00:10:48.460 --> 00:10:48.470 align:start position:0% about like enshrining anything plasma 00:10:48.470 --> 00:10:51.010 align:start position:0% about like enshrining anything plasma related<00:10:48.860> in<00:10:49.010> layer<00:10:49.160> one<00:10:49.400> is<00:10:49.430> that<00:10:49.760> like<00:10:50.020> that's 00:10:51.010 --> 00:10:51.020 align:start position:0% related in layer one is that like that's 00:10:51.020 --> 00:10:53.320 align:start position:0% related in layer one is that like that's a<00:10:51.140> new<00:10:51.260> like<00:10:51.440> liveness<00:10:51.650> assumption<00:10:52.280> to<00:10:52.460> to 00:10:53.320 --> 00:10:53.330 align:start position:0% a new like liveness assumption to to 00:10:53.330 --> 00:10:54.820 align:start position:0% a new like liveness assumption to to aterial<00:10:53.630> validators<00:10:54.200> or<00:10:54.320> people<00:10:54.560> who<00:10:54.650> hold 00:10:54.820 --> 00:10:54.830 align:start position:0% aterial validators or people who hold 00:10:54.830 --> 00:10:57.030 align:start position:0% aterial validators or people who hold value<00:10:55.730> on<00:10:55.820> the<00:10:55.910> theorem<00:10:56.180> like<00:10:56.300> you<00:10:56.540> have<00:10:56.660> to 00:10:57.030 --> 00:10:57.040 align:start position:0% value on the theorem like you have to 00:10:57.040 --> 00:10:59.260 align:start position:0% value on the theorem like you have to like<00:10:58.040> the<00:10:58.220> protocol<00:10:58.610> says<00:10:58.790> you<00:10:58.880> have<00:10:59.030> to<00:10:59.120> log 00:10:59.260 --> 00:10:59.270 align:start position:0% like the protocol says you have to log 00:10:59.270 --> 00:11:01.000 align:start position:0% like the protocol says you have to log in<00:10:59.420> once<00:10:59.570> every<00:10:59.690> certain<00:11:00.380> amount<00:11:00.560> of<00:11:00.590> time<00:11:00.800> and 00:11:01.000 --> 00:11:01.010 align:start position:0% in once every certain amount of time and 00:11:01.010 --> 00:11:02.800 align:start position:0% in once every certain amount of time and like<00:11:01.610> that's<00:11:01.910> not<00:11:02.030> there's<00:11:02.480> no<00:11:02.570> trade-off 00:11:02.800 --> 00:11:02.810 align:start position:0% like that's not there's no trade-off 00:11:02.810 --> 00:11:04.009 align:start position:0% like that's not there's no trade-off everyone<00:11:03.290> wants<00:11:03.830> to 00:11:04.009 --> 00:11:04.019 align:start position:0% everyone wants to 00:11:04.019 --> 00:11:06.769 align:start position:0% everyone wants to like<00:11:04.319> some<00:11:05.220> people<00:11:05.339> are<00:11:05.489> even<00:11:05.699> unhappy<00:11:06.089> about 00:11:06.769 --> 00:11:06.779 align:start position:0% like some people are even unhappy about 00:11:06.779 --> 00:11:08.780 align:start position:0% like some people are even unhappy about that<00:11:07.319> like<00:11:07.679> proof<00:11:07.920> of<00:11:08.009> steak<00:11:08.220> that's<00:11:08.369> a<00:11:08.550> weak 00:11:08.780 --> 00:11:08.790 align:start position:0% that like proof of steak that's a weak 00:11:08.790 --> 00:11:12.290 align:start position:0% that like proof of steak that's a weak subjectivity<00:11:09.179> kind<00:11:09.629> of<00:11:09.720> yeah<00:11:11.269> yeah<00:11:12.269> I 00:11:12.290 --> 00:11:12.300 align:start position:0% subjectivity kind of yeah yeah I 00:11:12.300 --> 00:11:13.999 align:start position:0% subjectivity kind of yeah yeah I definitely<00:11:12.509> agree<00:11:12.899> with<00:11:13.050> Sean<00:11:13.499> G<00:11:13.679> right<00:11:13.829> there 00:11:13.999 --> 00:11:14.009 align:start position:0% definitely agree with Sean G right there 00:11:14.009 --> 00:11:16.220 align:start position:0% definitely agree with Sean G right there I<00:11:14.579> think<00:11:15.300> when<00:11:15.420> it<00:11:15.509> comes<00:11:15.689> to<00:11:15.779> changes<00:11:16.110> on 00:11:16.220 --> 00:11:16.230 align:start position:0% I think when it comes to changes on 00:11:16.230 --> 00:11:19.129 align:start position:0% I think when it comes to changes on layer<00:11:16.410> one<00:11:16.939> I<00:11:17.939> mean<00:11:18.300> this<00:11:18.569> is<00:11:18.720> a<00:11:18.749> little<00:11:19.019> bit 00:11:19.129 --> 00:11:19.139 align:start position:0% layer one I mean this is a little bit 00:11:19.139 --> 00:11:20.689 align:start position:0% layer one I mean this is a little bit tangential<00:11:19.589> but<00:11:19.619> gets<00:11:20.100> to<00:11:20.189> the<00:11:20.279> point<00:11:20.459> as<00:11:20.549> well 00:11:20.689 --> 00:11:20.699 align:start position:0% tangential but gets to the point as well 00:11:20.699 --> 00:11:22.489 align:start position:0% tangential but gets to the point as well I<00:11:20.730> think<00:11:20.910> when<00:11:21.209> it<00:11:21.299> comes<00:11:21.480> to<00:11:21.629> layer<00:11:21.809> one<00:11:22.110> and 00:11:22.489 --> 00:11:22.499 align:start position:0% I think when it comes to layer one and 00:11:22.499 --> 00:11:25.910 align:start position:0% I think when it comes to layer one and how<00:11:22.619> it<00:11:23.069> can<00:11:23.160> help<00:11:23.220> plasma<00:11:23.759> I<00:11:24.749> think<00:11:25.470> you<00:11:25.799> know 00:11:25.910 --> 00:11:25.920 align:start position:0% how it can help plasma I think you know 00:11:25.920 --> 00:11:28.489 align:start position:0% how it can help plasma I think you know there's<00:11:26.489> there's<00:11:27.029> a<00:11:27.089> dynamic<00:11:27.600> where<00:11:27.839> you<00:11:28.379> know 00:11:28.489 --> 00:11:28.499 align:start position:0% there's there's a dynamic where you know 00:11:28.499 --> 00:11:29.809 align:start position:0% there's there's a dynamic where you know we're<00:11:28.649> dealing<00:11:29.129> with<00:11:29.309> different<00:11:29.639> layers 00:11:29.809 --> 00:11:29.819 align:start position:0% we're dealing with different layers 00:11:29.819 --> 00:11:31.519 align:start position:0% we're dealing with different layers there<00:11:30.089> and<00:11:30.209> communications<00:11:30.929> between<00:11:31.259> them<00:11:31.410> is 00:11:31.519 --> 00:11:31.529 align:start position:0% there and communications between them is 00:11:31.529 --> 00:11:34.729 align:start position:0% there and communications between them is pretty<00:11:31.709> important<00:11:32.129> so<00:11:32.869> you<00:11:33.869> know<00:11:33.959> that<00:11:34.559> may 00:11:34.729 --> 00:11:34.739 align:start position:0% pretty important so you know that may 00:11:34.739 --> 00:11:36.799 align:start position:0% pretty important so you know that may require<00:11:34.949> coordinating<00:11:35.850> coordinating<00:11:36.629> with 00:11:36.799 --> 00:11:36.809 align:start position:0% require coordinating coordinating with 00:11:36.809 --> 00:11:38.749 align:start position:0% require coordinating coordinating with you<00:11:36.989> know<00:11:37.110> a<00:11:37.139> lot<00:11:37.379> of<00:11:37.410> the<00:11:37.679> core<00:11:38.279> atheneum 00:11:38.749 --> 00:11:38.759 align:start position:0% you know a lot of the core atheneum 00:11:38.759 --> 00:11:40.970 align:start position:0% you know a lot of the core atheneum research<00:11:39.119> one<00:11:39.869> topic<00:11:40.259> that<00:11:40.470> I<00:11:40.499> do<00:11:40.619> care<00:11:40.920> about 00:11:40.970 --> 00:11:40.980 align:start position:0% research one topic that I do care about 00:11:40.980 --> 00:11:43.100 align:start position:0% research one topic that I do care about and<00:11:41.489> I<00:11:41.730> actually<00:11:41.999> don't<00:11:42.389> know<00:11:42.629> if<00:11:42.779> it's<00:11:42.899> on<00:11:42.959> the 00:11:43.100 --> 00:11:43.110 align:start position:0% and I actually don't know if it's on the 00:11:43.110 --> 00:11:44.929 align:start position:0% and I actually don't know if it's on the roadmap<00:11:43.290> so<00:11:43.649> maybe<00:11:43.829> tell<00:11:44.610> me<00:11:44.699> if<00:11:44.790> this<00:11:44.879> is 00:11:44.929 --> 00:11:44.939 align:start position:0% roadmap so maybe tell me if this is 00:11:44.939 --> 00:11:47.809 align:start position:0% roadmap so maybe tell me if this is there<00:11:45.239> isn't<00:11:45.389> Karl<00:11:46.290> is<00:11:46.529> some<00:11:47.339> type<00:11:47.639> of 00:11:47.809 --> 00:11:47.819 align:start position:0% there isn't Karl is some type of 00:11:47.819 --> 00:11:51.650 align:start position:0% there isn't Karl is some type of calculation<00:11:48.540> for<00:11:49.009> basically<00:11:50.009> the<00:11:50.339> gas<00:11:51.119> costs 00:11:51.650 --> 00:11:51.660 align:start position:0% calculation for basically the gas costs 00:11:51.660 --> 00:11:54.289 align:start position:0% calculation for basically the gas costs per<00:11:52.649> block<00:11:52.860> and<00:11:53.429> I<00:11:53.699> think<00:11:53.879> some<00:11:54.029> type<00:11:54.209> of 00:11:54.289 --> 00:11:54.299 align:start position:0% per block and I think some type of 00:11:54.299 --> 00:11:56.960 align:start position:0% per block and I think some type of metric<00:11:54.629> for<00:11:54.779> that<00:11:54.959> can<00:11:55.829> be<00:11:55.949> really<00:11:56.309> helpful<00:11:56.429> on 00:11:56.960 --> 00:11:56.970 align:start position:0% metric for that can be really helpful on 00:11:56.970 --> 00:11:59.869 align:start position:0% metric for that can be really helpful on the<00:11:57.179> plasma<00:11:57.360> side<00:11:57.720> because<00:11:58.049> it<00:11:58.139> makes<00:11:58.319> the<00:11:58.879> you 00:11:59.869 --> 00:11:59.879 align:start position:0% the plasma side because it makes the you 00:11:59.879 --> 00:12:02.090 align:start position:0% the plasma side because it makes the you know<00:11:59.999> more<00:12:00.839> robust<00:12:01.170> exiting<00:12:01.619> games<00:12:01.829> and 00:12:02.090 --> 00:12:02.100 align:start position:0% know more robust exiting games and 00:12:02.100 --> 00:12:04.039 align:start position:0% know more robust exiting games and reliability<00:12:03.029> on<00:12:03.329> that<00:12:03.569> can<00:12:03.779> be<00:12:03.869> pretty 00:12:04.039 --> 00:12:04.049 align:start position:0% reliability on that can be pretty 00:12:04.049 --> 00:12:07.100 align:start position:0% reliability on that can be pretty helpful<00:12:04.259> but<00:12:04.709> is<00:12:05.610> not<00:12:05.999> necessary<00:12:06.509> for<00:12:06.600> plasma 00:12:07.100 --> 00:12:07.110 align:start position:0% helpful but is not necessary for plasma 00:12:07.110 --> 00:12:09.199 align:start position:0% helpful but is not necessary for plasma but<00:12:07.649> you<00:12:07.829> know<00:12:07.920> you<00:12:07.980> may<00:12:08.220> you<00:12:08.490> may<00:12:08.519> see<00:12:08.699> these 00:12:09.199 --> 00:12:09.209 align:start position:0% but you know you may you may see these 00:12:09.209 --> 00:12:10.850 align:start position:0% but you know you may you may see these dynamics<00:12:09.720> where<00:12:09.899> like<00:12:10.110> you<00:12:10.319> know<00:12:10.350> whether<00:12:10.709> it 00:12:10.850 --> 00:12:10.860 align:start position:0% dynamics where like you know whether it 00:12:10.860 --> 00:12:12.379 align:start position:0% dynamics where like you know whether it be<00:12:10.889> contracts<00:12:11.399> really<00:12:11.579> are<00:12:11.759> two<00:12:11.939> type<00:12:12.119> things 00:12:12.379 --> 00:12:12.389 align:start position:0% be contracts really are two type things 00:12:12.389 --> 00:12:14.749 align:start position:0% be contracts really are two type things you<00:12:12.899> know<00:12:13.019> can<00:12:13.350> be<00:12:13.379> helpful<00:12:13.709> for<00:12:13.920> layer<00:12:14.100> one<00:12:14.369> in 00:12:14.749 --> 00:12:14.759 align:start position:0% you know can be helpful for layer one in 00:12:14.759 --> 00:12:18.350 align:start position:0% you know can be helpful for layer one in the<00:12:14.879> opposite<00:12:15.240> perspective<00:12:17.119> yeah<00:12:18.119> that's 00:12:18.350 --> 00:12:18.360 align:start position:0% the opposite perspective yeah that's 00:12:18.360 --> 00:12:20.179 align:start position:0% the opposite perspective yeah that's actually<00:12:18.509> a<00:12:18.720> good<00:12:18.809> point<00:12:19.019> I<00:12:19.230> mean<00:12:19.619> the<00:12:19.889> the 00:12:20.179 --> 00:12:20.189 align:start position:0% actually a good point I mean the the 00:12:20.189 --> 00:12:22.759 align:start position:0% actually a good point I mean the the whole<00:12:20.339> gas<00:12:20.959> market<00:12:21.959> is<00:12:22.079> actually<00:12:22.230> going<00:12:22.559> to 00:12:22.759 --> 00:12:22.769 align:start position:0% whole gas market is actually going to 00:12:22.769 --> 00:12:24.829 align:start position:0% whole gas market is actually going to get<00:12:22.889> revamped<00:12:23.309> with<00:12:23.579> the<00:12:23.879> the<00:12:24.240> if<00:12:24.629> they're 00:12:24.829 --> 00:12:24.839 align:start position:0% get revamped with the the if they're 00:12:24.839 --> 00:12:26.239 align:start position:0% get revamped with the the if they're named<00:12:24.929> 2.0<00:12:25.319> and<00:12:25.439> you<00:12:25.499> can<00:12:25.649> kind<00:12:25.799> of<00:12:25.829> like<00:12:25.980> read 00:12:26.239 --> 00:12:26.249 align:start position:0% named 2.0 and you can kind of like read 00:12:26.249 --> 00:12:28.730 align:start position:0% named 2.0 and you can kind of like read about<00:12:26.459> that<00:12:26.639> in<00:12:26.699> fatale<00:12:27.240> --ax<00:12:27.389> like<00:12:28.290> he<00:12:28.439> has<00:12:28.709> a 00:12:28.730 --> 00:12:28.740 align:start position:0% about that in fatale --ax like he has a 00:12:28.740 --> 00:12:31.999 align:start position:0% about that in fatale --ax like he has a paper<00:12:29.009> out<00:12:29.220> there<00:12:29.299> and<00:12:30.299> so<00:12:30.869> yeah<00:12:31.139> I<00:12:31.170> think<00:12:31.379> it 00:12:31.999 --> 00:12:32.009 align:start position:0% paper out there and so yeah I think it 00:12:32.009 --> 00:12:34.549 align:start position:0% paper out there and so yeah I think it should<00:12:32.279> be<00:12:32.339> more<00:12:32.699> viable<00:12:33.230> it's<00:12:34.230> definitely 00:12:34.549 --> 00:12:34.559 align:start position:0% should be more viable it's definitely 00:12:34.559 --> 00:12:36.199 align:start position:0% should be more viable it's definitely more<00:12:34.740> consistent<00:12:35.399> right<00:12:35.610> just<00:12:35.819> push<00:12:35.970> it<00:12:36.119> to 00:12:36.199 --> 00:12:36.209 align:start position:0% more consistent right just push it to 00:12:36.209 --> 00:12:37.939 align:start position:0% more consistent right just push it to stack<00:12:36.420> like<00:12:36.660> so<00:12:36.779> yeah<00:12:36.990> an<00:12:37.199> opcode<00:12:37.350> word<00:12:37.709> like 00:12:37.939 --> 00:12:37.949 align:start position:0% stack like so yeah an opcode word like 00:12:37.949 --> 00:12:40.699 align:start position:0% stack like so yeah an opcode word like pushes<00:12:38.610> let's<00:12:38.850> say<00:12:39.029> not<00:12:39.660> even<00:12:39.929> like<00:12:40.110> all<00:12:40.319> the 00:12:40.699 --> 00:12:40.709 align:start position:0% pushes let's say not even like all the 00:12:40.709 --> 00:12:42.109 align:start position:0% pushes let's say not even like all the blocks<00:12:40.920> like<00:12:41.160> not<00:12:41.339> storing<00:12:41.699> all<00:12:41.819> the<00:12:41.910> blocks 00:12:42.109 --> 00:12:42.119 align:start position:0% blocks like not storing all the blocks 00:12:42.119 --> 00:12:44.720 align:start position:0% blocks like not storing all the blocks like<00:12:42.569> gas<00:12:42.839> costs<00:12:43.110> but<00:12:43.199> maybe<00:12:43.410> like<00:12:43.649> maybe<00:12:44.459> the 00:12:44.720 --> 00:12:44.730 align:start position:0% like gas costs but maybe like maybe the 00:12:44.730 --> 00:12:46.429 align:start position:0% like gas costs but maybe like maybe the previous<00:12:45.179> ones<00:12:45.389> with<00:12:45.540> the<00:12:45.629> current<00:12:45.959> one<00:12:46.139> why 00:12:46.429 --> 00:12:46.439 align:start position:0% previous ones with the current one why 00:12:46.439 --> 00:12:48.259 align:start position:0% previous ones with the current one why not<00:12:46.679> that's<00:12:47.220> very<00:12:47.730> reasonable 00:12:48.259 --> 00:12:48.269 align:start position:0% not that's very reasonable 00:12:48.269 --> 00:12:51.350 align:start position:0% not that's very reasonable yeah<00:12:48.689> what<00:12:49.559> is<00:12:49.649> the<00:12:49.799> change<00:12:50.240> basically<00:12:51.240> you 00:12:51.350 --> 00:12:51.360 align:start position:0% yeah what is the change basically you 00:12:51.360 --> 00:12:53.119 align:start position:0% yeah what is the change basically you push<00:12:51.569> on<00:12:51.720> to<00:12:51.839> stack<00:12:52.110> maybe<00:12:52.439> a<00:12:52.529> some<00:12:52.740> cop<00:12:52.919> code 00:12:53.119 --> 00:12:53.129 align:start position:0% push on to stack maybe a some cop code 00:12:53.129 --> 00:12:55.480 align:start position:0% push on to stack maybe a some cop code where<00:12:53.279> you<00:12:53.339> push<00:12:53.490> on<00:12:53.639> to<00:12:53.730> the<00:12:53.850> stack<00:12:54.059> the<00:12:54.439> the 00:12:55.480 --> 00:12:55.490 align:start position:0% where you push on to the stack the the 00:12:55.490 --> 00:12:57.769 align:start position:0% where you push on to the stack the the maybe<00:12:56.490> you<00:12:56.759> have<00:12:56.879> some<00:12:57.059> very<00:12:57.240> assign<00:12:57.749> a 00:12:57.769 --> 00:12:57.779 align:start position:0% maybe you have some very assign a 00:12:57.779 --> 00:13:02.989 align:start position:0% maybe you have some very assign a variable<00:12:58.610> basically<00:12:59.610> some<00:13:01.129> what<00:13:02.129> the<00:13:02.639> gas 00:13:02.989 --> 00:13:02.999 align:start position:0% variable basically some what the gas 00:13:02.999 --> 00:13:07.489 align:start position:0% variable basically some what the gas costs<00:13:03.660> on<00:13:04.220> that<00:13:05.220> block<00:13:05.699> was<00:13:05.999> Oh<00:13:06.269> like<00:13:06.540> to<00:13:06.989> see 00:13:07.489 --> 00:13:07.499 align:start position:0% costs on that block was Oh like to see 00:13:07.499 --> 00:13:09.829 align:start position:0% costs on that block was Oh like to see to<00:13:07.739> to<00:13:08.100> read<00:13:08.279> what<00:13:08.429> the<00:13:08.519> guess<00:13:08.730> oh<00:13:09.360> yeah<00:13:09.689> yeah 00:13:09.829 --> 00:13:09.839 align:start position:0% to to read what the guess oh yeah yeah 00:13:09.839 --> 00:13:11.840 align:start position:0% to to read what the guess oh yeah yeah sorry<00:13:09.989> for<00:13:10.259> context<00:13:10.799> in<00:13:10.889> the<00:13:10.980> audience<00:13:11.279> right 00:13:11.840 --> 00:13:11.850 align:start position:0% sorry for context in the audience right 00:13:11.850 --> 00:13:14.569 align:start position:0% sorry for context in the audience right now<00:13:12.360> doing<00:13:13.049> gas<00:13:13.379> cost<00:13:13.709> estimation<00:13:14.399> in 00:13:14.569 --> 00:13:14.579 align:start position:0% now doing gas cost estimation in 00:13:14.579 --> 00:13:17.810 align:start position:0% now doing gas cost estimation in contracts<00:13:15.360> on<00:13:15.569> recent<00:13:16.169> blocks<00:13:16.410> is 00:13:17.810 --> 00:13:17.820 align:start position:0% contracts on recent blocks is 00:13:17.820 --> 00:13:20.450 align:start position:0% contracts on recent blocks is difficult<00:13:18.120> um<00:13:18.620> we<00:13:19.620> have<00:13:19.830> something<00:13:20.160> like<00:13:20.310> that 00:13:20.450 --> 00:13:20.460 align:start position:0% difficult um we have something like that 00:13:20.460 --> 00:13:22.940 align:start position:0% difficult um we have something like that where<00:13:20.790> we<00:13:21.390> assume<00:13:21.750> that<00:13:21.780> if<00:13:22.380> there<00:13:22.680> is<00:13:22.770> more 00:13:22.940 --> 00:13:22.950 align:start position:0% where we assume that if there is more 00:13:22.950 --> 00:13:24.890 align:start position:0% where we assume that if there is more than<00:13:23.010> one<00:13:23.280> Operator<00:13:23.730> they<00:13:24.180> compete<00:13:24.660> for<00:13:24.690> the 00:13:24.890 --> 00:13:24.900 align:start position:0% than one Operator they compete for the 00:13:24.900 --> 00:13:27.860 align:start position:0% than one Operator they compete for the next<00:13:25.200> block<00:13:25.760> just<00:13:26.760> think<00:13:27.000> along<00:13:27.240> this<00:13:27.390> way<00:13:27.630> and 00:13:27.860 --> 00:13:27.870 align:start position:0% next block just think along this way and 00:13:27.870 --> 00:13:31.130 align:start position:0% next block just think along this way and then<00:13:28.500> you<00:13:29.100> know<00:13:29.250> when<00:13:29.490> when<00:13:29.940> the<00:13:30.060> the<00:13:30.960> header 00:13:31.130 --> 00:13:31.140 align:start position:0% then you know when when the the header 00:13:31.140 --> 00:13:33.740 align:start position:0% then you know when when the the header is<00:13:31.350> submitted<00:13:31.860> we<00:13:32.070> can<00:13:32.250> just<00:13:32.460> do<00:13:32.910> message<00:13:33.510> gas 00:13:33.740 --> 00:13:33.750 align:start position:0% is submitted we can just do message gas 00:13:33.750 --> 00:13:35.660 align:start position:0% is submitted we can just do message gas and<00:13:34.050> then<00:13:34.560> we<00:13:34.680> save<00:13:34.920> that<00:13:34.950> and<00:13:35.400> take<00:13:35.550> the 00:13:35.660 --> 00:13:35.670 align:start position:0% and then we save that and take the 00:13:35.670 --> 00:13:37.990 align:start position:0% and then we save that and take the average<00:13:35.790> over<00:13:36.120> the<00:13:36.270> last<00:13:36.330> exploits 00:13:37.990 --> 00:13:38.000 align:start position:0% average over the last exploits 00:13:38.000 --> 00:13:40.720 align:start position:0% average over the last exploits specifically<00:13:39.000> an<00:13:39.120> example<00:13:39.630> where<00:13:39.840> that 00:13:40.720 --> 00:13:40.730 align:start position:0% specifically an example where that 00:13:40.730 --> 00:13:43.820 align:start position:0% specifically an example where that definitely<00:13:41.730> is<00:13:41.820> a<00:13:41.850> good<00:13:42.060> idea<00:13:42.260> but<00:13:43.260> for<00:13:43.470> exits 00:13:43.820 --> 00:13:43.830 align:start position:0% definitely is a good idea but for exits 00:13:43.830 --> 00:13:46.280 align:start position:0% definitely is a good idea but for exits this<00:13:44.760> this<00:13:45.060> this<00:13:45.360> can<00:13:45.540> be<00:13:45.660> beneficial<00:13:46.050> as<00:13:46.260> well 00:13:46.280 --> 00:13:46.290 align:start position:0% this this this can be beneficial as well 00:13:46.290 --> 00:13:48.380 align:start position:0% this this this can be beneficial as well because<00:13:46.770> that<00:13:46.800> way<00:13:47.100> you<00:13:47.160> can<00:13:47.370> you<00:13:47.760> can<00:13:47.940> have 00:13:48.380 --> 00:13:48.390 align:start position:0% because that way you can you can have 00:13:48.390 --> 00:13:51.440 align:start position:0% because that way you can you can have maybe<00:13:48.630> relative<00:13:49.200> bond<00:13:49.380> sizes<00:13:50.270> relative<00:13:51.270> to 00:13:51.440 --> 00:13:51.450 align:start position:0% maybe relative bond sizes relative to 00:13:51.450 --> 00:13:53.990 align:start position:0% maybe relative bond sizes relative to the<00:13:51.600> cost<00:13:51.810> of<00:13:52.020> exiting<00:13:52.460> when<00:13:53.460> you<00:13:53.580> when<00:13:53.880> you 00:13:53.990 --> 00:13:54.000 align:start position:0% the cost of exiting when you when you 00:13:54.000 --> 00:13:55.910 align:start position:0% the cost of exiting when you when you exit<00:13:54.420> right<00:13:54.630> you<00:13:54.780> want<00:13:55.050> to<00:13:55.110> be<00:13:55.200> able<00:13:55.470> to<00:13:55.560> pay 00:13:55.910 --> 00:13:55.920 align:start position:0% exit right you want to be able to pay 00:13:55.920 --> 00:13:58.070 align:start position:0% exit right you want to be able to pay for<00:13:56.250> whoever<00:13:56.940> is<00:13:57.060> going<00:13:57.240> to<00:13:57.330> challenge<00:13:57.660> you 00:13:58.070 --> 00:13:58.080 align:start position:0% for whoever is going to challenge you 00:13:58.080 --> 00:13:59.390 align:start position:0% for whoever is going to challenge you you<00:13:58.110> want<00:13:58.470> to<00:13:58.530> be<00:13:58.590> able<00:13:58.680> to<00:13:58.860> pay<00:13:58.980> for<00:13:59.010> the<00:13:59.250> gas 00:13:59.390 --> 00:13:59.400 align:start position:0% you want to be able to pay for the gas 00:13:59.400 --> 00:14:01.700 align:start position:0% you want to be able to pay for the gas cost<00:13:59.730> and<00:14:00.060> so<00:14:00.390> doing<00:14:00.600> that<00:14:00.900> is<00:14:01.140> a<00:14:01.170> little<00:14:01.500> bit 00:14:01.700 --> 00:14:01.710 align:start position:0% cost and so doing that is a little bit 00:14:01.710 --> 00:14:03.320 align:start position:0% cost and so doing that is a little bit tricky<00:14:02.070> and<00:14:02.280> you<00:14:02.550> probably<00:14:02.880> have<00:14:03.180> to 00:14:03.320 --> 00:14:03.330 align:start position:0% tricky and you probably have to 00:14:03.330 --> 00:14:05.270 align:start position:0% tricky and you probably have to overestimate<00:14:03.660> and<00:14:04.200> it<00:14:04.740> would<00:14:04.830> be<00:14:04.920> helpful<00:14:05.160> to 00:14:05.270 --> 00:14:05.280 align:start position:0% overestimate and it would be helpful to 00:14:05.280 --> 00:14:10.060 align:start position:0% overestimate and it would be helpful to have<00:14:05.550> this<00:14:05.700> kind<00:14:05.970> of<00:14:06.000> in<00:14:06.360> protocol<00:14:06.840> be<00:14:07.260> nice 00:14:10.060 --> 00:14:10.070 align:start position:0% 00:14:10.070 --> 00:14:12.020 align:start position:0% uncommon<00:14:11.070> I<00:14:11.250> have<00:14:11.370> to<00:14:11.490> make<00:14:11.610> about<00:14:11.820> that<00:14:11.970> is 00:14:12.020 --> 00:14:12.030 align:start position:0% uncommon I have to make about that is 00:14:12.030 --> 00:14:14.870 align:start position:0% uncommon I have to make about that is like<00:14:12.300> the<00:14:12.450> current<00:14:12.780> gas<00:14:13.430> the<00:14:14.430> current<00:14:14.730> gas 00:14:14.870 --> 00:14:14.880 align:start position:0% like the current gas the current gas 00:14:14.880 --> 00:14:17.030 align:start position:0% like the current gas the current gas market<00:14:15.390> is<00:14:15.540> not<00:14:15.690> designed<00:14:16.080> to<00:14:16.170> be<00:14:16.230> like 00:14:17.030 --> 00:14:17.040 align:start position:0% market is not designed to be like 00:14:17.040 --> 00:14:18.620 align:start position:0% market is not designed to be like resistant<00:14:17.520> to<00:14:17.610> manipulation<00:14:18.180> if<00:14:18.300> people<00:14:18.540> are 00:14:18.620 --> 00:14:18.630 align:start position:0% resistant to manipulation if people are 00:14:18.630 --> 00:14:20.990 align:start position:0% resistant to manipulation if people are relying<00:14:18.900> on<00:14:19.140> on<00:14:19.440> if<00:14:20.280> people<00:14:20.550> are<00:14:20.640> relying<00:14:20.850> on 00:14:20.990 --> 00:14:21.000 align:start position:0% relying on on if people are relying on 00:14:21.000 --> 00:14:26.840 align:start position:0% relying on on if people are relying on it<00:14:21.060> for<00:14:24.860> to<00:14:25.860> have<00:14:25.980> an<00:14:26.070> accurate<00:14:26.220> metric<00:14:26.730> off 00:14:26.840 --> 00:14:26.850 align:start position:0% it for to have an accurate metric off 00:14:26.850 --> 00:14:28.940 align:start position:0% it for to have an accurate metric off this<00:14:27.030> is<00:14:27.180> how<00:14:27.300> much<00:14:27.450> you<00:14:27.660> you<00:14:28.230> have<00:14:28.380> to<00:14:28.530> pay<00:14:28.680> in 00:14:28.940 --> 00:14:28.950 align:start position:0% this is how much you you have to pay in 00:14:28.950 --> 00:14:30.260 align:start position:0% this is how much you you have to pay in order<00:14:29.160> to<00:14:29.280> guarantee<00:14:29.430> inclusion<00:14:30.090> in<00:14:30.180> the 00:14:30.260 --> 00:14:30.270 align:start position:0% order to guarantee inclusion in the 00:14:30.270 --> 00:14:35.540 align:start position:0% order to guarantee inclusion in the block<00:14:33.020> it's<00:14:34.020> very<00:14:34.260> hard<00:14:34.590> to<00:14:34.710> predict<00:14:35.190> gas 00:14:35.540 --> 00:14:35.550 align:start position:0% block it's very hard to predict gas 00:14:35.550 --> 00:14:37.550 align:start position:0% block it's very hard to predict gas prices<00:14:36.090> in<00:14:36.300> the<00:14:36.360> future<00:14:36.510> as<00:14:36.990> one<00:14:37.380> might 00:14:37.550 --> 00:14:37.560 align:start position:0% prices in the future as one might 00:14:37.560 --> 00:14:38.810 align:start position:0% prices in the future as one might imagine<00:14:37.680> because<00:14:38.310> we<00:14:38.490> don't<00:14:38.670> necessarily 00:14:38.810 --> 00:14:38.820 align:start position:0% imagine because we don't necessarily 00:14:38.820 --> 00:14:40.910 align:start position:0% imagine because we don't necessarily know<00:14:39.300> like<00:14:39.480> there<00:14:39.660> was<00:14:39.780> say<00:14:39.900> we've<00:14:40.650> thought<00:14:40.860> a 00:14:40.910 --> 00:14:40.920 align:start position:0% know like there was say we've thought a 00:14:40.920 --> 00:14:43.130 align:start position:0% know like there was say we've thought a lot<00:14:41.040> about<00:14:41.520> like<00:14:42.000> let's<00:14:42.450> make<00:14:42.630> it<00:14:42.660> so<00:14:42.930> that<00:14:42.960> you 00:14:43.130 --> 00:14:43.140 align:start position:0% lot about like let's make it so that you 00:14:43.140 --> 00:14:44.510 align:start position:0% lot about like let's make it so that you can<00:14:43.290> send<00:14:43.470> a<00:14:43.560> transaction<00:14:43.890> that's<00:14:44.250> guaranteed 00:14:44.510 --> 00:14:44.520 align:start position:0% can send a transaction that's guaranteed 00:14:44.520 --> 00:14:46.670 align:start position:0% can send a transaction that's guaranteed to<00:14:44.820> be<00:14:45.120> included<00:14:45.540> in<00:14:45.720> a<00:14:45.840> block<00:14:46.110> in<00:14:46.320> the<00:14:46.410> future 00:14:46.670 --> 00:14:46.680 align:start position:0% to be included in a block in the future 00:14:46.680 --> 00:14:48.500 align:start position:0% to be included in a block in the future but<00:14:47.100> that<00:14:47.160> gets<00:14:47.430> so<00:14:47.580> funky<00:14:48.060> because<00:14:48.240> then 00:14:48.500 --> 00:14:48.510 align:start position:0% but that gets so funky because then 00:14:48.510 --> 00:14:50.030 align:start position:0% but that gets so funky because then you're<00:14:48.630> like<00:14:48.780> okay<00:14:49.080> what<00:14:49.290> are<00:14:49.410> the<00:14:49.440> actual<00:14:49.890> gas 00:14:50.030 --> 00:14:50.040 align:start position:0% you're like okay what are the actual gas 00:14:50.040 --> 00:14:51.530 align:start position:0% you're like okay what are the actual gas price<00:14:50.310> like<00:14:50.520> they're<00:14:50.670> weird<00:14:50.820> manipulations 00:14:51.530 --> 00:14:51.540 align:start position:0% price like they're weird manipulations 00:14:51.540 --> 00:14:52.910 align:start position:0% price like they're weird manipulations that<00:14:51.660> you<00:14:51.720> can<00:14:51.870> do<00:14:51.930> if<00:14:52.020> you<00:14:52.110> thought<00:14:52.260> gas<00:14:52.500> token 00:14:52.910 --> 00:14:52.920 align:start position:0% that you can do if you thought gas token 00:14:52.920 --> 00:14:54.860 align:start position:0% that you can do if you thought gas token was<00:14:53.040> weird<00:14:53.280> this<00:14:53.790> just<00:14:54.060> gets<00:14:54.240> very<00:14:54.450> confusing 00:14:54.860 --> 00:14:54.870 align:start position:0% was weird this just gets very confusing 00:14:54.870 --> 00:14:57.290 align:start position:0% was weird this just gets very confusing so<00:14:55.200> I<00:14:55.440> was<00:14:55.770> about<00:14:55.860> to<00:14:56.100> say<00:14:56.220> that<00:14:56.250> that<00:14:56.670> in<00:14:57.000> my 00:14:57.290 --> 00:14:57.300 align:start position:0% so I was about to say that that in my 00:14:57.300 --> 00:14:59.770 align:start position:0% so I was about to say that that in my opinion<00:14:57.660> I<00:14:57.780> I'm<00:14:57.990> considering<00:14:58.740> implementing 00:14:59.770 --> 00:14:59.780 align:start position:0% opinion I I'm considering implementing 00:14:59.780 --> 00:15:02.930 align:start position:0% opinion I I'm considering implementing basically<00:15:00.780> gas<00:15:00.960> token<00:15:01.410> so<00:15:02.190> the<00:15:02.520> gas<00:15:02.670> token 00:15:02.930 --> 00:15:02.940 align:start position:0% basically gas token so the gas token 00:15:02.940 --> 00:15:04.760 align:start position:0% basically gas token so the gas token comes<00:15:03.120> to<00:15:03.210> action<00:15:03.450> is<00:15:03.600> it<00:15:03.900> exploits<00:15:04.290> a<00:15:04.440> market 00:15:04.760 --> 00:15:04.770 align:start position:0% comes to action is it exploits a market 00:15:04.770 --> 00:15:06.770 align:start position:0% comes to action is it exploits a market inefficiency<00:15:04.950> where<00:15:05.580> you<00:15:05.670> can<00:15:05.820> just<00:15:06.000> buy<00:15:06.480> gas 00:15:06.770 --> 00:15:06.780 align:start position:0% inefficiency where you can just buy gas 00:15:06.780 --> 00:15:08.600 align:start position:0% inefficiency where you can just buy gas at<00:15:06.930> the<00:15:06.990> very<00:15:07.140> low<00:15:07.260> low<00:15:07.620> price<00:15:07.860> and<00:15:08.100> you<00:15:08.460> can 00:15:08.600 --> 00:15:08.610 align:start position:0% at the very low low price and you can 00:15:08.610 --> 00:15:11.420 align:start position:0% at the very low low price and you can reuse<00:15:08.820> it<00:15:09.180> at<00:15:09.300> some<00:15:09.480> later<00:15:09.690> point<00:15:09.840> and<00:15:10.260> so<00:15:11.070> I 00:15:11.420 --> 00:15:11.430 align:start position:0% reuse it at some later point and so I 00:15:11.430 --> 00:15:14.180 align:start position:0% reuse it at some later point and so I was<00:15:11.820> thinking<00:15:12.450> that<00:15:12.480> maybe<00:15:12.870> like<00:15:13.350> you<00:15:14.040> can 00:15:14.180 --> 00:15:14.190 align:start position:0% was thinking that maybe like you can 00:15:14.190 --> 00:15:16.580 align:start position:0% was thinking that maybe like you can have<00:15:14.370> like<00:15:14.580> a<00:15:14.760> minor<00:15:15.090> inside<00:15:15.960> the<00:15:16.290> plasma 00:15:16.580 --> 00:15:16.590 align:start position:0% have like a minor inside the plasma 00:15:16.590 --> 00:15:18.590 align:start position:0% have like a minor inside the plasma contract<00:15:17.100> we<00:15:17.220> just<00:15:17.490> like<00:15:17.880> it<00:15:18.000> makes<00:15:18.210> useless 00:15:18.590 --> 00:15:18.600 align:start position:0% contract we just like it makes useless 00:15:18.600 --> 00:15:20.060 align:start position:0% contract we just like it makes useless operations<00:15:19.080> during<00:15:19.440> the<00:15:19.530> night<00:15:19.650> or<00:15:19.680> wherever 00:15:20.060 --> 00:15:20.070 align:start position:0% operations during the night or wherever 00:15:20.070 --> 00:15:23.840 align:start position:0% operations during the night or wherever like<00:15:20.820> the<00:15:20.970> gas<00:15:21.780> price<00:15:22.050> is<00:15:22.080> low<00:15:22.350> and<00:15:22.590> so<00:15:23.250> like<00:15:23.610> if 00:15:23.840 --> 00:15:23.850 align:start position:0% like the gas price is low and so like if 00:15:23.850 --> 00:15:26.660 align:start position:0% like the gas price is low and so like if currently<00:15:24.690> if<00:15:24.870> I<00:15:25.020> buy<00:15:25.380> gas<00:15:25.650> at<00:15:25.830> like<00:15:26.010> two<00:15:26.370> QA 00:15:26.660 --> 00:15:26.670 align:start position:0% currently if I buy gas at like two QA 00:15:26.670 --> 00:15:28.430 align:start position:0% currently if I buy gas at like two QA like<00:15:27.000> an<00:15:27.180> estimate<00:15:27.570> one<00:15:27.720> block<00:15:27.960> period<00:15:28.140> like 00:15:28.430 --> 00:15:28.440 align:start position:0% like an estimate one block period like 00:15:28.440 --> 00:15:30.710 align:start position:0% like an estimate one block period like 15<00:15:29.010> seconds<00:15:29.400> maybe<00:15:29.970> it<00:15:30.120> cost<00:15:30.330> hundred 00:15:30.710 --> 00:15:30.720 align:start position:0% 15 seconds maybe it cost hundred 00:15:30.720 --> 00:15:31.640 align:start position:0% 15 seconds maybe it cost hundred thousand 00:15:31.640 --> 00:15:31.650 align:start position:0% thousand 00:15:31.650 --> 00:15:35.000 align:start position:0% thousand it<00:15:31.920> sucks<00:15:32.220> but<00:15:32.940> if<00:15:33.180> you<00:15:33.330> bought<00:15:33.480> at<00:15:33.680> 0.1<00:15:34.680> UA 00:15:35.000 --> 00:15:35.010 align:start position:0% it sucks but if you bought at 0.1 UA 00:15:35.010 --> 00:15:37.310 align:start position:0% it sucks but if you bought at 0.1 UA which<00:15:35.339> is<00:15:35.400> totally<00:15:35.940> feasible<00:15:36.089> like<00:15:36.540> with<00:15:36.900> this 00:15:37.310 --> 00:15:37.320 align:start position:0% which is totally feasible like with this 00:15:37.320 --> 00:15:41.180 align:start position:0% which is totally feasible like with this inefficiency<00:15:39.440> basically<00:15:40.440> the<00:15:40.560> cast<00:15:40.740> cost<00:15:40.980> is 00:15:41.180 --> 00:15:41.190 align:start position:0% inefficiency basically the cast cost is 00:15:41.190 --> 00:15:43.940 align:start position:0% inefficiency basically the cast cost is totally<00:15:41.520> manageable<00:15:41.790> however<00:15:42.950> you're 00:15:43.940 --> 00:15:43.950 align:start position:0% totally manageable however you're 00:15:43.950 --> 00:15:45.590 align:start position:0% totally manageable however you're exploiting<00:15:44.279> an<00:15:44.580> inefficiency<00:15:45.150> and<00:15:45.450> the 00:15:45.590 --> 00:15:45.600 align:start position:0% exploiting an inefficiency and the 00:15:45.600 --> 00:15:47.480 align:start position:0% exploiting an inefficiency and the moment<00:15:45.900> that<00:15:46.260> people<00:15:46.410> other<00:15:47.010> people<00:15:47.370> also 00:15:47.480 --> 00:15:47.490 align:start position:0% moment that people other people also 00:15:47.490 --> 00:15:49.550 align:start position:0% moment that people other people also start<00:15:47.850> using<00:15:48.060> it<00:15:48.300> this<00:15:48.750> inefficiency<00:15:49.110> goes 00:15:49.550 --> 00:15:49.560 align:start position:0% start using it this inefficiency goes 00:15:49.560 --> 00:15:52.280 align:start position:0% start using it this inefficiency goes away<00:15:49.770> so<00:15:50.400> it<00:15:50.550> is<00:15:50.670> not<00:15:50.970> it<00:15:51.330> is<00:15:51.360> totally<00:15:52.050> hack 00:15:52.280 --> 00:15:52.290 align:start position:0% away so it is not it is totally hack 00:15:52.290 --> 00:15:54.769 align:start position:0% away so it is not it is totally hack that<00:15:52.589> is<00:15:52.800> temporarily<00:15:53.700> that's<00:15:54.480> only<00:15:54.660> a 00:15:54.769 --> 00:15:54.779 align:start position:0% that is temporarily that's only a 00:15:54.779 --> 00:15:56.780 align:start position:0% that is temporarily that's only a temporary<00:15:54.930> solution<00:15:55.290> and<00:15:56.220> to<00:15:56.370> be<00:15:56.460> clear<00:15:56.670> these 00:15:56.780 --> 00:15:56.790 align:start position:0% temporary solution and to be clear these 00:15:56.790 --> 00:16:00.860 align:start position:0% temporary solution and to be clear these are<00:15:56.850> all<00:15:57.089> optimizations<00:15:57.930> it's<00:15:59.089> tough<00:16:00.089> yeah 00:16:00.860 --> 00:16:00.870 align:start position:0% are all optimizations it's tough yeah 00:16:00.870 --> 00:16:03.350 align:start position:0% are all optimizations it's tough yeah but<00:16:01.050> still<00:16:01.200> up<00:16:01.350> to<00:16:01.470> any<00:16:01.740> optimization<00:16:02.430> or<00:16:02.670> just 00:16:03.350 --> 00:16:03.360 align:start position:0% but still up to any optimization or just 00:16:03.360 --> 00:16:05.450 align:start position:0% but still up to any optimization or just anything<00:16:04.020> which<00:16:04.230> reduces<00:16:04.680> the<00:16:04.950> inefficiency 00:16:05.450 --> 00:16:05.460 align:start position:0% anything which reduces the inefficiency 00:16:05.460 --> 00:16:07.790 align:start position:0% anything which reduces the inefficiency of<00:16:05.640> any<00:16:05.850> market<00:16:06.300> and<00:16:06.420> the<00:16:07.350> three-room<00:16:07.680> is 00:16:07.790 --> 00:16:07.800 align:start position:0% of any market and the three-room is 00:16:07.800 --> 00:16:10.160 align:start position:0% of any market and the three-room is large<00:16:08.010> so<00:16:08.339> a<00:16:08.490> huge<00:16:08.760> market<00:16:09.089> is<00:16:09.270> still<00:16:09.870> great 00:16:10.160 --> 00:16:10.170 align:start position:0% large so a huge market is still great 00:16:10.170 --> 00:16:12.860 align:start position:0% large so a huge market is still great because<00:16:10.620> we<00:16:11.220> do<00:16:11.670> the<00:16:11.850> same<00:16:12.029> is<00:16:12.240> not<00:16:12.390> the<00:16:12.510> area's 00:16:12.860 --> 00:16:12.870 align:start position:0% because we do the same is not the area's 00:16:12.870 --> 00:16:14.840 align:start position:0% because we do the same is not the area's and<00:16:13.650> you<00:16:13.770> need<00:16:13.920> to<00:16:14.040> do<00:16:14.160> this<00:16:14.339> it<00:16:14.550> could<00:16:14.730> be 00:16:14.840 --> 00:16:14.850 align:start position:0% and you need to do this it could be 00:16:14.850 --> 00:16:16.430 align:start position:0% and you need to do this it could be helpful<00:16:15.060> for<00:16:15.270> many<00:16:15.450> other<00:16:15.660> smart<00:16:15.990> contracts 00:16:16.430 --> 00:16:16.440 align:start position:0% helpful for many other smart contracts 00:16:16.440 --> 00:16:19.010 align:start position:0% helpful for many other smart contracts is<00:16:16.620> basically<00:16:17.010> this<00:16:17.310> dynamic<00:16:18.060> regarding<00:16:18.870> the 00:16:19.010 --> 00:16:19.020 align:start position:0% is basically this dynamic regarding the 00:16:19.020 --> 00:16:21.710 align:start position:0% is basically this dynamic regarding the free<00:16:19.200> market<00:16:19.500> gap<00:16:20.339> so<00:16:20.880> actually<00:16:21.270> there<00:16:21.450> is<00:16:21.540> the 00:16:21.710 --> 00:16:21.720 align:start position:0% free market gap so actually there is the 00:16:21.720 --> 00:16:24.200 align:start position:0% free market gap so actually there is the market<00:16:22.080> for<00:16:22.140> gas<00:16:22.620> for<00:16:23.220> the<00:16:23.370> bonds<00:16:23.580> that<00:16:23.850> you 00:16:24.200 --> 00:16:24.210 align:start position:0% market for gas for the bonds that you 00:16:24.210 --> 00:16:25.640 align:start position:0% market for gas for the bonds that you put<00:16:24.360> up<00:16:24.480> also<00:16:24.870> like<00:16:25.020> when<00:16:25.140> you're<00:16:25.290> making<00:16:25.440> a 00:16:25.640 --> 00:16:25.650 align:start position:0% put up also like when you're making a 00:16:25.650 --> 00:16:27.230 align:start position:0% put up also like when you're making a exit<00:16:25.890> so<00:16:26.430> I'd<00:16:26.490> like<00:16:26.670> to<00:16:26.730> initiate<00:16:27.150> the 00:16:27.230 --> 00:16:27.240 align:start position:0% exit so I'd like to initiate the 00:16:27.240 --> 00:16:28.970 align:start position:0% exit so I'd like to initiate the discussion<00:16:27.720> the<00:16:28.050> incentives<00:16:28.500> of<00:16:28.650> miners 00:16:28.970 --> 00:16:28.980 align:start position:0% discussion the incentives of miners 00:16:28.980 --> 00:16:31.850 align:start position:0% discussion the incentives of miners front-running<00:16:29.730> challenge<00:16:30.330> transactions<00:16:30.990> and 00:16:31.850 --> 00:16:31.860 align:start position:0% front-running challenge transactions and 00:16:31.860 --> 00:16:33.950 align:start position:0% front-running challenge transactions and like<00:16:32.700> how<00:16:32.880> would<00:16:32.940> you<00:16:33.150> approach<00:16:33.330> it<00:16:33.450> my 00:16:33.950 --> 00:16:33.960 align:start position:0% like how would you approach it my 00:16:33.960 --> 00:16:35.600 align:start position:0% like how would you approach it my current<00:16:34.260> understanding<00:16:34.320> is<00:16:34.890> that<00:16:34.920> you<00:16:35.400> can<00:16:35.520> do 00:16:35.600 --> 00:16:35.610 align:start position:0% current understanding is that you can do 00:16:35.610 --> 00:16:37.340 align:start position:0% current understanding is that you can do it<00:16:35.700> with<00:16:35.790> a<00:16:35.820> commitment<00:16:36.300> but<00:16:36.750> still<00:16:37.140> that 00:16:37.340 --> 00:16:37.350 align:start position:0% it with a commitment but still that 00:16:37.350 --> 00:16:40.040 align:start position:0% it with a commitment but still that commitment<00:16:37.830> also<00:16:38.040> leaks<00:16:38.370> information<00:16:39.050> there 00:16:40.040 --> 00:16:40.050 align:start position:0% commitment also leaks information there 00:16:40.050 --> 00:16:41.570 align:start position:0% commitment also leaks information there is<00:16:40.110> a<00:16:40.140> current<00:16:40.380> effort<00:16:40.740> on<00:16:41.010> somewhere 00:16:41.570 --> 00:16:41.580 align:start position:0% is a current effort on somewhere 00:16:41.580 --> 00:16:43.220 align:start position:0% is a current effort on somewhere somewhere<00:16:41.970> in<00:16:42.089> sense<00:16:42.390> that<00:16:42.660> essentially<00:16:43.140> you 00:16:43.220 --> 00:16:43.230 align:start position:0% somewhere in sense that essentially you 00:16:43.230 --> 00:16:45.260 align:start position:0% somewhere in sense that essentially you you<00:16:43.709> make<00:16:43.890> a<00:16:43.920> commitment<00:16:44.310> that<00:16:44.640> is<00:16:44.790> more 00:16:45.260 --> 00:16:45.270 align:start position:0% you make a commitment that is more 00:16:45.270 --> 00:16:47.930 align:start position:0% you make a commitment that is more stealthy<00:16:46.130> yeah<00:16:47.130> I<00:16:47.160> would<00:16:47.310> be<00:16:47.459> interested<00:16:47.820> if 00:16:47.930 --> 00:16:47.940 align:start position:0% stealthy yeah I would be interested if 00:16:47.940 --> 00:16:50.930 align:start position:0% stealthy yeah I would be interested if you<00:16:47.970> have<00:16:48.089> an<00:16:48.360> opinion<00:16:48.660> on<00:16:48.870> that<00:16:49.940> specifically 00:16:50.930 --> 00:16:50.940 align:start position:0% you have an opinion on that specifically 00:16:50.940 --> 00:16:57.829 align:start position:0% you have an opinion on that specifically the<00:16:51.650> commitments<00:16:52.650> for<00:16:56.029> the<00:16:57.029> question<00:16:57.330> is<00:16:57.450> how 00:16:57.829 --> 00:16:57.839 align:start position:0% the commitments for the question is how 00:16:57.839 --> 00:17:00.610 align:start position:0% the commitments for the question is how to<00:16:57.870> avoid<00:16:58.290> the<00:16:58.560> challenge<00:16:59.010> from<00:16:59.279> running 00:17:00.610 --> 00:17:00.620 align:start position:0% to avoid the challenge from running 00:17:00.620 --> 00:17:03.699 align:start position:0% to avoid the challenge from running challenge<00:17:01.620> front<00:17:01.860> lining<00:17:02.040> with<00:17:02.520> regards<00:17:03.029> to 00:17:03.699 --> 00:17:03.709 align:start position:0% challenge front lining with regards to 00:17:03.709 --> 00:17:06.260 align:start position:0% challenge front lining with regards to exiting<00:17:04.709> on<00:17:04.860> the<00:17:05.040> main<00:17:05.189> chain<00:17:05.400> or<00:17:05.579> for<00:17:06.000> always 00:17:06.260 --> 00:17:06.270 align:start position:0% exiting on the main chain or for always 00:17:06.270 --> 00:17:14.090 align:start position:0% exiting on the main chain or for always the<00:17:06.390> dimension<00:17:06.839> okay<00:17:11.959> I<00:17:12.959> make<00:17:13.350> an<00:17:13.470> exit<00:17:13.829> and 00:17:14.090 --> 00:17:14.100 align:start position:0% the dimension okay I make an exit and 00:17:14.100 --> 00:17:16.370 align:start position:0% the dimension okay I make an exit and somebody<00:17:14.550> must<00:17:14.699> challenge<00:17:15.120> me<00:17:15.270> I<00:17:15.420> put<00:17:15.720> the<00:17:15.839> 0.1 00:17:16.370 --> 00:17:16.380 align:start position:0% somebody must challenge me I put the 0.1 00:17:16.380 --> 00:17:18.199 align:start position:0% somebody must challenge me I put the 0.1 ether<00:17:16.559> boom<00:17:16.770> somebody<00:17:17.429> goes<00:17:17.610> to<00:17:17.640> challenge<00:17:18.059> me 00:17:18.199 --> 00:17:18.209 align:start position:0% ether boom somebody goes to challenge me 00:17:18.209 --> 00:17:20.299 align:start position:0% ether boom somebody goes to challenge me they<00:17:18.900> put<00:17:19.079> up<00:17:19.260> they<00:17:19.530> go<00:17:19.709> they<00:17:19.980> make<00:17:20.189> the 00:17:20.299 --> 00:17:20.309 align:start position:0% they put up they go they make the 00:17:20.309 --> 00:17:21.949 align:start position:0% they put up they go they make the transaction<00:17:20.819> the<00:17:20.970> miners<00:17:21.300> is<00:17:21.480> it<00:17:21.630> they<00:17:21.780> make 00:17:21.949 --> 00:17:21.959 align:start position:0% transaction the miners is it they make 00:17:21.959 --> 00:17:23.569 align:start position:0% transaction the miners is it they make the<00:17:21.990> transaction<00:17:22.410> before<00:17:22.949> the<00:17:23.130> Challenger 00:17:23.569 --> 00:17:23.579 align:start position:0% the transaction before the Challenger 00:17:23.579 --> 00:17:25.579 align:start position:0% the transaction before the Challenger okay<00:17:24.329> and<00:17:24.480> it<00:17:24.630> that<00:17:24.900> means<00:17:25.079> that<00:17:25.230> they<00:17:25.350> sweep 00:17:25.579 --> 00:17:25.589 align:start position:0% okay and it that means that they sweep 00:17:25.589 --> 00:17:28.220 align:start position:0% okay and it that means that they sweep they<00:17:26.040> get<00:17:26.280> the<00:17:26.370> bond<00:17:26.579> right<00:17:27.420> the<00:17:27.689> miner<00:17:27.929> get 00:17:28.220 --> 00:17:28.230 align:start position:0% they get the bond right the miner get 00:17:28.230 --> 00:17:32.030 align:start position:0% they get the bond right the miner get this<00:17:29.070> is<00:17:29.220> an<00:17:29.400> implicit<00:17:29.790> like<00:17:30.240> this<00:17:31.170> is<00:17:31.290> a<00:17:31.320> fee 00:17:32.030 --> 00:17:32.040 align:start position:0% this is an implicit like this is a fee 00:17:32.040 --> 00:17:34.400 align:start position:0% this is an implicit like this is a fee on<00:17:32.309> top<00:17:32.610> of<00:17:32.790> this<00:17:33.300> creates<00:17:33.960> a<00:17:34.020> secondary 00:17:34.400 --> 00:17:34.410 align:start position:0% on top of this creates a secondary 00:17:34.410 --> 00:17:37.430 align:start position:0% on top of this creates a secondary market<00:17:34.670> which<00:17:35.670> it<00:17:36.030> complicates<00:17:36.720> how<00:17:36.960> like<00:17:37.230> the 00:17:37.430 --> 00:17:37.440 align:start position:0% market which it complicates how like the 00:17:37.440 --> 00:17:40.130 align:start position:0% market which it complicates how like the miners<00:17:37.800> can<00:17:37.980> calculate<00:17:38.400> their<00:17:38.580> profits<00:17:39.140> do 00:17:40.130 --> 00:17:40.140 align:start position:0% miners can calculate their profits do 00:17:40.140 --> 00:17:41.419 align:start position:0% miners can calculate their profits do you<00:17:40.230> do<00:17:40.350> how<00:17:40.470> like<00:17:40.679> you're<00:17:40.830> no<00:17:40.950> longer<00:17:41.280> based 00:17:41.419 --> 00:17:41.429 align:start position:0% you do how like you're no longer based 00:17:41.429 --> 00:17:43.850 align:start position:0% you do how like you're no longer based on<00:17:41.670> this<00:17:41.760> like<00:17:42.000> gas<00:17:42.240> model<00:17:42.780> and<00:17:42.960> essentially 00:17:43.850 --> 00:17:43.860 align:start position:0% on this like gas model and essentially 00:17:43.860 --> 00:17:45.540 align:start position:0% on this like gas model and essentially it's<00:17:44.550> based<00:17:44.880> like<00:17:45.150> it 00:17:45.540 --> 00:17:45.550 align:start position:0% it's based like it 00:17:45.550 --> 00:17:47.760 align:start position:0% it's based like it incentive<00:17:46.090> to<00:17:46.270> censor<00:17:46.630> transactions<00:17:47.200> so<00:17:47.710> you 00:17:47.760 --> 00:17:47.770 align:start position:0% incentive to censor transactions so you 00:17:47.770 --> 00:17:49.950 align:start position:0% incentive to censor transactions so you lose<00:17:48.040> fees<00:17:48.310> but<00:17:48.730> I<00:17:48.790> don't<00:17:48.970> layer<00:17:49.150> one<00:17:49.390> but<00:17:49.870> you 00:17:49.950 --> 00:17:49.960 align:start position:0% lose fees but I don't layer one but you 00:17:49.960 --> 00:17:52.560 align:start position:0% lose fees but I don't layer one but you gain<00:17:50.140> on<00:17:50.320> fees<00:17:50.470> that<00:17:50.620> are<00:17:50.680> on<00:17:50.980> layer<00:17:51.250> 2<00:17:51.570> how 00:17:52.560 --> 00:17:52.570 align:start position:0% gain on fees that are on layer 2 how 00:17:52.570 --> 00:17:54.770 align:start position:0% gain on fees that are on layer 2 how would<00:17:52.990> you<00:17:53.110> model<00:17:53.410> this<00:17:53.560> approach<00:17:53.890> because 00:17:54.770 --> 00:17:54.780 align:start position:0% would you model this approach because 00:17:54.780 --> 00:17:57.900 align:start position:0% would you model this approach because basically<00:17:55.780> what<00:17:56.560> you<00:17:56.680> mean<00:17:56.860> I<00:17:56.890> think<00:17:57.310> correct 00:17:57.900 --> 00:17:57.910 align:start position:0% basically what you mean I think correct 00:17:57.910 --> 00:17:59.520 align:start position:0% basically what you mean I think correct me<00:17:58.030> if<00:17:58.090> I'm<00:17:58.240> wrong<00:17:58.270> so<00:17:58.570> I<00:17:58.600> can<00:17:58.660> describe<00:17:59.260> it<00:17:59.410> to 00:17:59.520 --> 00:17:59.530 align:start position:0% me if I'm wrong so I can describe it to 00:17:59.530 --> 00:18:04.080 align:start position:0% me if I'm wrong so I can describe it to audience<00:17:59.830> is<00:18:00.270> this<00:18:01.270> dynamic<00:18:01.540> whereby<00:18:02.230> a<00:18:03.220> proof 00:18:04.080 --> 00:18:04.090 align:start position:0% audience is this dynamic whereby a proof 00:18:04.090 --> 00:18:06.780 align:start position:0% audience is this dynamic whereby a proof of<00:18:04.620> invalidity<00:18:05.620> or<00:18:06.040> some<00:18:06.220> type<00:18:06.400> of<00:18:06.520> proof 00:18:06.780 --> 00:18:06.790 align:start position:0% of invalidity or some type of proof 00:18:06.790 --> 00:18:08.520 align:start position:0% of invalidity or some type of proof basically<00:18:07.390> doesn't<00:18:07.660> have<00:18:07.990> a<00:18:08.020> signature 00:18:08.520 --> 00:18:08.530 align:start position:0% basically doesn't have a signature 00:18:08.530 --> 00:18:11.610 align:start position:0% basically doesn't have a signature attached<00:18:08.950> to<00:18:09.160> it<00:18:09.250> necessarily<00:18:09.780> whereby<00:18:10.780> the 00:18:11.610 --> 00:18:11.620 align:start position:0% attached to it necessarily whereby the 00:18:11.620 --> 00:18:13.290 align:start position:0% attached to it necessarily whereby the solution<00:18:12.100> about<00:18:12.250> that<00:18:12.400> I'm<00:18:12.880> talking<00:18:13.270> about 00:18:13.290 --> 00:18:13.300 align:start position:0% solution about that I'm talking about 00:18:13.300 --> 00:18:15.240 align:start position:0% solution about that I'm talking about the<00:18:13.750> simple<00:18:14.080> fact<00:18:14.290> that<00:18:14.350> the<00:18:14.530> minor<00:18:14.800> can 00:18:15.240 --> 00:18:15.250 align:start position:0% the simple fact that the minor can 00:18:15.250 --> 00:18:17.460 align:start position:0% the simple fact that the minor can simply<00:18:15.640> or<00:18:15.820> another<00:18:16.330> user<00:18:16.600> can<00:18:16.930> monitor<00:18:17.320> the 00:18:17.460 --> 00:18:17.470 align:start position:0% simply or another user can monitor the 00:18:17.470 --> 00:18:19.380 align:start position:0% simply or another user can monitor the change<00:18:17.710> similar<00:18:18.250> to<00:18:18.430> the<00:18:18.520> math<00:18:18.700> to<00:18:19.090> the<00:18:19.180> bank 00:18:19.380 --> 00:18:19.390 align:start position:0% change similar to the math to the bank 00:18:19.390 --> 00:18:21.390 align:start position:0% change similar to the math to the bank or<00:18:19.600> inefficiency<00:18:20.410> if<00:18:20.620> anybody<00:18:21.040> else<00:18:21.190> is 00:18:21.390 --> 00:18:21.400 align:start position:0% or inefficiency if anybody else is 00:18:21.400 --> 00:18:23.790 align:start position:0% or inefficiency if anybody else is familiar<00:18:21.850> with<00:18:21.880> that<00:18:22.030> that<00:18:22.750> essentially<00:18:23.590> you 00:18:23.790 --> 00:18:23.800 align:start position:0% familiar with that that essentially you 00:18:23.800 --> 00:18:27.210 align:start position:0% familiar with that that essentially you front-run<00:18:24.280> in<00:18:24.430> transaction<00:18:24.970> and<00:18:25.120> if<00:18:26.220> the 00:18:27.210 --> 00:18:27.220 align:start position:0% front-run in transaction and if the 00:18:27.220 --> 00:18:29.910 align:start position:0% front-run in transaction and if the penalty<00:18:27.430> no<00:18:28.270> no<00:18:28.540> no<00:18:28.690> no<00:18:28.810> no<00:18:28.960> no<00:18:29.080> it's<00:18:29.230> oh<00:18:29.350> I<00:18:29.620> make 00:18:29.910 --> 00:18:29.920 align:start position:0% penalty no no no no no no it's oh I make 00:18:29.920 --> 00:18:32.010 align:start position:0% penalty no no no no no no it's oh I make an<00:18:30.010> exit<00:18:30.280> on<00:18:30.400> checking<00:18:30.820> yeah<00:18:31.090> okay<00:18:31.390> I<00:18:31.570> make<00:18:31.870> I 00:18:32.010 --> 00:18:32.020 align:start position:0% an exit on checking yeah okay I make I 00:18:32.020 --> 00:18:34.800 align:start position:0% an exit on checking yeah okay I make I put<00:18:32.290> up<00:18:32.410> a<00:18:32.470> bond<00:18:32.680> it<00:18:33.550> is<00:18:33.730> an<00:18:33.820> invalid<00:18:34.120> exit<00:18:34.480> we 00:18:34.800 --> 00:18:34.810 align:start position:0% put up a bond it is an invalid exit we 00:18:34.810 --> 00:18:36.120 align:start position:0% put up a bond it is an invalid exit we don't<00:18:34.990> care<00:18:35.110> about<00:18:35.140> that<00:18:35.320> we<00:18:35.560> care<00:18:35.770> about<00:18:35.860> the 00:18:36.120 --> 00:18:36.130 align:start position:0% don't care about that we care about the 00:18:36.130 --> 00:18:38.490 align:start position:0% don't care about that we care about the economics<00:18:37.120> regarding<00:18:37.540> the<00:18:37.690> challenger's<00:18:38.290> and 00:18:38.490 --> 00:18:38.500 align:start position:0% economics regarding the challenger's and 00:18:38.500 --> 00:18:40.530 align:start position:0% economics regarding the challenger's and then<00:18:38.680> the<00:18:38.770> minor<00:18:39.040> basically<00:18:39.940> publishes<00:18:40.390> the 00:18:40.530 --> 00:18:40.540 align:start position:0% then the minor basically publishes the 00:18:40.540 --> 00:18:43.200 align:start position:0% then the minor basically publishes the exit<00:18:40.780> no<00:18:41.560> no<00:18:41.800> the<00:18:42.010> exit<00:18:42.430> has<00:18:42.610> happened<00:18:42.970> it's 00:18:43.200 --> 00:18:43.210 align:start position:0% exit no no the exit has happened it's 00:18:43.210 --> 00:18:46.230 align:start position:0% exit no no the exit has happened it's okay<00:18:43.360> they<00:18:43.920> okay<00:18:44.950> and<00:18:45.100> now<00:18:45.460> somebody<00:18:45.910> wants<00:18:46.180> to 00:18:46.230 --> 00:18:46.240 align:start position:0% okay they okay and now somebody wants to 00:18:46.240 --> 00:18:48.390 align:start position:0% okay they okay and now somebody wants to challenge<00:18:46.630> the<00:18:46.900> exit<00:18:47.170> they<00:18:47.740> challenge 00:18:48.390 --> 00:18:48.400 align:start position:0% challenge the exit they challenge 00:18:48.400 --> 00:18:50.340 align:start position:0% challenge the exit they challenge they<00:18:48.700> the<00:18:48.970> challenge<00:18:49.360> is<00:18:49.510> a<00:18:49.570> valid<00:18:50.020> Channel 00:18:50.340 --> 00:18:50.350 align:start position:0% they the challenge is a valid Channel 00:18:50.350 --> 00:18:52.650 align:start position:0% they the challenge is a valid Channel yeah<00:18:50.470> okay<00:18:51.100> but<00:18:51.370> somebody<00:18:51.670> else<00:18:52.000> comes<00:18:52.330> in<00:18:52.450> for 00:18:52.650 --> 00:18:52.660 align:start position:0% yeah okay but somebody else comes in for 00:18:52.660 --> 00:18:55.440 align:start position:0% yeah okay but somebody else comes in for trans<00:18:52.900> challenge<00:18:53.650> this<00:18:54.130> means<00:18:54.430> that<00:18:54.850> if<00:18:55.120> there 00:18:55.440 --> 00:18:55.450 align:start position:0% trans challenge this means that if there 00:18:55.450 --> 00:18:56.880 align:start position:0% trans challenge this means that if there is<00:18:55.540> a<00:18:55.570> way<00:18:55.840> for<00:18:56.110> people<00:18:56.140> to<00:18:56.410> front<00:18:56.710> on<00:18:56.860> your 00:18:56.880 --> 00:18:56.890 align:start position:0% is a way for people to front on your 00:18:56.890 --> 00:18:59.400 align:start position:0% is a way for people to front on your transactions<00:18:57.580> yep<00:18:57.910> you<00:18:58.450> no<00:18:58.720> longer<00:18:58.960> are 00:18:59.400 --> 00:18:59.410 align:start position:0% transactions yep you no longer are 00:18:59.410 --> 00:19:01.410 align:start position:0% transactions yep you no longer are guaranteed<00:19:00.040> to<00:19:00.280> profit<00:19:00.820> from<00:19:01.240> the 00:19:01.410 --> 00:19:01.420 align:start position:0% guaranteed to profit from the 00:19:01.420 --> 00:19:10.440 align:start position:0% guaranteed to profit from the transaction<00:19:03.420> is<00:19:04.420> to<00:19:04.630> stop<00:19:04.870> challenging<00:19:09.450> cast 00:19:10.440 --> 00:19:10.450 align:start position:0% transaction is to stop challenging cast 00:19:10.450 --> 00:19:12.480 align:start position:0% transaction is to stop challenging cast it<00:19:10.630> the<00:19:11.140> person<00:19:11.590> that's<00:19:11.740> going<00:19:12.010> to<00:19:12.130> front<00:19:12.430> run 00:19:12.480 --> 00:19:12.490 align:start position:0% it the person that's going to front run 00:19:12.490 --> 00:19:16.110 align:start position:0% it the person that's going to front run most<00:19:12.790> likely<00:19:13.150> is<00:19:13.300> the<00:19:13.510> miner<00:19:13.720> oh<00:19:13.960> yeah<00:19:15.120> point 00:19:16.110 --> 00:19:16.120 align:start position:0% most likely is the miner oh yeah point 00:19:16.120 --> 00:19:18.270 align:start position:0% most likely is the miner oh yeah point being<00:19:16.300> that<00:19:16.330> front<00:19:16.750> running<00:19:16.960> it<00:19:17.560> directly 00:19:18.270 --> 00:19:18.280 align:start position:0% being that front running it directly 00:19:18.280 --> 00:19:21.240 align:start position:0% being that front running it directly impacts<00:19:18.820> the<00:19:18.850> security<00:19:19.600> of<00:19:19.780> the<00:19:20.050> chain<00:19:20.290> yeah 00:19:21.240 --> 00:19:21.250 align:start position:0% impacts the security of the chain yeah 00:19:21.250 --> 00:19:22.830 align:start position:0% impacts the security of the chain yeah very<00:19:21.580> likely<00:19:21.820> does<00:19:21.970> because<00:19:22.450> people<00:19:22.720> will 00:19:22.830 --> 00:19:22.840 align:start position:0% very likely does because people will 00:19:22.840 --> 00:19:24.750 align:start position:0% very likely does because people will stop<00:19:23.080> challenging<00:19:23.560> if<00:19:23.800> you<00:19:24.010> get<00:19:24.370> from<00:19:24.550> drawn 00:19:24.750 --> 00:19:24.760 align:start position:0% stop challenging if you get from drawn 00:19:24.760 --> 00:19:27.120 align:start position:0% stop challenging if you get from drawn by<00:19:24.910> the<00:19:24.970> miners<00:19:25.330> and<00:19:25.840> then<00:19:26.140> the<00:19:26.320> miners<00:19:26.710> are<00:19:26.950> in 00:19:27.120 --> 00:19:27.130 align:start position:0% by the miners and then the miners are in 00:19:27.130 --> 00:19:28.560 align:start position:0% by the miners and then the miners are in the<00:19:27.220> perfect<00:19:27.580> position<00:19:27.700> where<00:19:28.180> they<00:19:28.300> control 00:19:28.560 --> 00:19:28.570 align:start position:0% the perfect position where they control 00:19:28.570 --> 00:19:29.580 align:start position:0% the perfect position where they control both<00:19:28.660> in<00:19:29.050> layer<00:19:29.200> two 00:19:29.580 --> 00:19:29.590 align:start position:0% both in layer two 00:19:29.590 --> 00:19:31.650 align:start position:0% both in layer two simply<00:19:30.040> by<00:19:30.160> playing<00:19:30.700> this<00:19:30.850> game<00:19:31.060> where<00:19:31.330> they 00:19:31.650 --> 00:19:31.660 align:start position:0% simply by playing this game where they 00:19:31.660 --> 00:19:33.480 align:start position:0% simply by playing this game where they simply<00:19:32.110> bullied<00:19:32.470> people<00:19:32.620> lot<00:19:32.890> of<00:19:33.040> challenging 00:19:33.480 --> 00:19:33.490 align:start position:0% simply bullied people lot of challenging 00:19:33.490 --> 00:19:35.370 align:start position:0% simply bullied people lot of challenging yeah<00:19:33.910> yeah<00:19:34.180> that's<00:19:34.420> definitely<00:19:34.960> a<00:19:34.990> risk<00:19:35.230> with 00:19:35.370 --> 00:19:35.380 align:start position:0% yeah yeah that's definitely a risk with 00:19:35.380 --> 00:19:36.870 align:start position:0% yeah yeah that's definitely a risk with a<00:19:35.410> lot<00:19:35.620> of<00:19:35.740> these<00:19:35.830> things<00:19:36.040> there's<00:19:36.340> multiple 00:19:36.870 --> 00:19:36.880 align:start position:0% a lot of these things there's multiple 00:19:36.880 --> 00:19:38.340 align:start position:0% a lot of these things there's multiple there's<00:19:37.120> multiple<00:19:37.450> mitigations<00:19:37.960> you<00:19:38.110> can<00:19:38.230> do 00:19:38.340 --> 00:19:38.350 align:start position:0% there's multiple mitigations you can do 00:19:38.350 --> 00:19:41.430 align:start position:0% there's multiple mitigations you can do basically<00:19:38.740> I<00:19:39.100> don't<00:19:39.760> like<00:19:40.060> this<00:19:40.240> but<00:19:40.960> you<00:19:41.350> know 00:19:41.430 --> 00:19:41.440 align:start position:0% basically I don't like this but you know 00:19:41.440 --> 00:19:43.710 align:start position:0% basically I don't like this but you know a<00:19:41.470> naive<00:19:41.860> solution<00:19:42.280> would<00:19:42.370> be<00:19:42.430> to<00:19:42.550> you<00:19:43.450> know<00:19:43.480> do 00:19:43.710 --> 00:19:43.720 align:start position:0% a naive solution would be to you know do 00:19:43.720 --> 00:19:46.170 align:start position:0% a naive solution would be to you know do some<00:19:43.900> commit<00:19:44.170> reveal<00:19:44.410> whereby<00:19:45.310> basically<00:19:45.850> you 00:19:46.170 --> 00:19:46.180 align:start position:0% some commit reveal whereby basically you 00:19:46.180 --> 00:19:48.600 align:start position:0% some commit reveal whereby basically you submit<00:19:46.870> to<00:19:46.960> a<00:19:46.990> hash<00:19:47.200> similar<00:19:47.980> to<00:19:48.100> a<00:19:48.130> Fox<00:19:48.370> coin 00:19:48.600 --> 00:19:48.610 align:start position:0% submit to a hash similar to a Fox coin 00:19:48.610 --> 00:19:50.490 align:start position:0% submit to a hash similar to a Fox coin construction<00:19:49.210> you<00:19:49.450> know<00:19:49.540> Joe<00:19:49.690> Bono<00:19:49.900> and<00:19:49.930> 2014 00:19:50.490 --> 00:19:50.500 align:start position:0% construction you know Joe Bono and 2014 00:19:50.500 --> 00:19:52.440 align:start position:0% construction you know Joe Bono and 2014 Road<00:19:50.710> you<00:19:50.950> know<00:19:51.070> Fox<00:19:51.790> when<00:19:52.030> you<00:19:52.150> do<00:19:52.240> something 00:19:52.440 --> 00:19:52.450 align:start position:0% Road you know Fox when you do something 00:19:52.450 --> 00:19:53.640 align:start position:0% Road you know Fox when you do something like<00:19:52.570> that<00:19:52.690> where<00:19:52.960> you<00:19:52.990> commit<00:19:53.290> to<00:19:53.380> the<00:19:53.470> hash 00:19:53.640 --> 00:19:53.650 align:start position:0% like that where you commit to the hash 00:19:53.650 --> 00:19:55.470 align:start position:0% like that where you commit to the hash of<00:19:53.890> whatever<00:19:54.100> it<00:19:54.520> is<00:19:54.640> that<00:19:54.910> you're<00:19:55.060> going<00:19:55.330> to 00:19:55.470 --> 00:19:55.480 align:start position:0% of whatever it is that you're going to 00:19:55.480 --> 00:19:58.920 align:start position:0% of whatever it is that you're going to do<00:19:55.660> namecoin<00:19:56.560> does<00:19:56.740> something<00:19:57.010> similar<00:19:57.690> the 00:19:58.920 --> 00:19:58.930 align:start position:0% do namecoin does something similar the 00:19:58.930 --> 00:20:00.870 align:start position:0% do namecoin does something similar the there<00:19:59.050> are<00:19:59.290> significant<00:20:00.160> issues<00:20:00.580> with<00:20:00.610> this 00:20:00.870 --> 00:20:00.880 align:start position:0% there are significant issues with this 00:20:00.880 --> 00:20:02.850 align:start position:0% there are significant issues with this to<00:20:01.210> be<00:20:01.330> able<00:20:01.420> in<00:20:01.780> in<00:20:02.110> terms<00:20:02.230> of<00:20:02.410> complexity 00:20:02.850 --> 00:20:02.860 align:start position:0% to be able in in terms of complexity 00:20:02.860 --> 00:20:06.030 align:start position:0% to be able in in terms of complexity with<00:20:03.130> a<00:20:03.160> smart<00:20:03.430> contract<00:20:03.550> code<00:20:04.080> I<00:20:05.080> think<00:20:05.320> some 00:20:06.030 --> 00:20:06.040 align:start position:0% with a smart contract code I think some 00:20:06.040 --> 00:20:07.560 align:start position:0% with a smart contract code I think some type<00:20:06.220> of<00:20:06.250> model<00:20:06.670> where<00:20:06.820> you're<00:20:07.000> splitting<00:20:07.330> up 00:20:07.560 --> 00:20:07.570 align:start position:0% type of model where you're splitting up 00:20:07.570 --> 00:20:09.120 align:start position:0% type of model where you're splitting up the<00:20:07.600> penalty<00:20:08.020> or<00:20:08.200> maybe<00:20:08.380> pre<00:20:08.710> committing 00:20:09.120 --> 00:20:09.130 align:start position:0% the penalty or maybe pre committing 00:20:09.130 --> 00:20:12.120 align:start position:0% the penalty or maybe pre committing where<00:20:09.730> penalties<00:20:10.270> go<00:20:10.480> to<00:20:10.560> is<00:20:11.560> probably 00:20:12.120 --> 00:20:12.130 align:start position:0% where penalties go to is probably 00:20:12.130 --> 00:20:14.730 align:start position:0% where penalties go to is probably shorter<00:20:12.610> in<00:20:12.790> terms<00:20:13.060> of<00:20:13.330> lines<00:20:13.630> of<00:20:13.810> code<00:20:13.990> so<00:20:14.560> for 00:20:14.730 --> 00:20:14.740 align:start position:0% shorter in terms of lines of code so for 00:20:14.740 --> 00:20:16.950 align:start position:0% shorter in terms of lines of code so for example<00:20:15.160> you<00:20:15.400> can<00:20:15.550> assign<00:20:15.850> let's<00:20:16.120> say<00:20:16.240> 50%<00:20:16.570> of 00:20:16.950 --> 00:20:16.960 align:start position:0% example you can assign let's say 50% of 00:20:16.960 --> 00:20:18.870 align:start position:0% example you can assign let's say 50% of the<00:20:17.020> penalty<00:20:17.410> as<00:20:17.620> part<00:20:18.250> of<00:20:18.370> this<00:20:18.580> specific 00:20:18.870 --> 00:20:18.880 align:start position:0% the penalty as part of this specific 00:20:18.880 --> 00:20:22.530 align:start position:0% the penalty as part of this specific output<00:20:19.540> goes<00:20:20.350> to<00:20:20.770> these<00:20:21.340> sets<00:20:21.790> of<00:20:21.940> people<00:20:22.150> and 00:20:22.530 --> 00:20:22.540 align:start position:0% output goes to these sets of people and 00:20:22.540 --> 00:20:24.390 align:start position:0% output goes to these sets of people and those<00:20:22.930> are<00:20:23.140> the<00:20:23.230> sets<00:20:23.440> of<00:20:23.530> people<00:20:23.680> responsible 00:20:24.390 --> 00:20:24.400 align:start position:0% those are the sets of people responsible 00:20:24.400 --> 00:20:26.160 align:start position:0% those are the sets of people responsible for<00:20:24.460> publishing<00:20:24.940> but<00:20:25.300> then<00:20:25.450> you<00:20:25.630> made<00:20:25.840> you 00:20:26.160 --> 00:20:26.170 align:start position:0% for publishing but then you made you 00:20:26.170 --> 00:20:28.080 align:start position:0% for publishing but then you made you just<00:20:26.410> made<00:20:26.590> the<00:20:26.770> challenge<00:20:27.010> mechanism<00:20:27.820> not 00:20:28.080 --> 00:20:28.090 align:start position:0% just made the challenge mechanism not 00:20:28.090 --> 00:20:30.810 align:start position:0% just made the challenge mechanism not trustless<00:20:28.830> yeah<00:20:29.830> yeah<00:20:30.010> I'm<00:20:30.190> just<00:20:30.220> saying<00:20:30.580> that 00:20:30.810 --> 00:20:30.820 align:start position:0% trustless yeah yeah I'm just saying that 00:20:30.820 --> 00:20:32.580 align:start position:0% trustless yeah yeah I'm just saying that is<00:20:31.180> a<00:20:31.210> possibility<00:20:31.690> if<00:20:32.020> you<00:20:32.170> already<00:20:32.350> have 00:20:32.580 --> 00:20:32.590 align:start position:0% is a possibility if you already have 00:20:32.590 --> 00:20:34.160 align:start position:0% is a possibility if you already have someone<00:20:32.860> watching<00:20:33.070> on<00:20:33.310> your<00:20:33.370> behalf<00:20:33.670> I<00:20:33.760> mean 00:20:34.160 --> 00:20:34.170 align:start position:0% someone watching on your behalf I mean 00:20:34.170 --> 00:20:36.090 align:start position:0% someone watching on your behalf I mean okay<00:20:35.170> but<00:20:35.440> they're<00:20:35.680> after<00:20:35.770> let's<00:20:35.980> watch 00:20:36.090 --> 00:20:36.100 align:start position:0% okay but they're after let's watch 00:20:36.100 --> 00:20:38.580 align:start position:0% okay but they're after let's watch towers<00:20:36.460> aren't<00:20:36.760> real<00:20:37.060> hardly 00:20:38.580 --> 00:20:38.590 align:start position:0% towers aren't real hardly 00:20:38.590 --> 00:20:40.230 align:start position:0% towers aren't real hardly what<00:20:39.160> do<00:20:39.220> you<00:20:39.310> it<00:20:39.430> depends<00:20:39.790> what<00:20:39.910> you<00:20:39.940> mean<00:20:40.000> by 00:20:40.230 --> 00:20:40.240 align:start position:0% what do you it depends what you mean by 00:20:40.240 --> 00:20:43.020 align:start position:0% what do you it depends what you mean by trustless<00:20:40.630> watchtowers<00:20:41.140> but<00:20:41.290> basically<00:20:42.030> yeah 00:20:43.020 --> 00:20:43.030 align:start position:0% trustless watchtowers but basically yeah 00:20:43.030 --> 00:20:44.340 align:start position:0% trustless watchtowers but basically yeah I<00:20:43.060> mean<00:20:43.270> basically<00:20:43.450> you<00:20:43.900> would<00:20:44.020> have<00:20:44.140> to<00:20:44.260> do 00:20:44.340 --> 00:20:44.350 align:start position:0% I mean basically you would have to do 00:20:44.350 --> 00:20:46.110 align:start position:0% I mean basically you would have to do some<00:20:44.530> type<00:20:44.680> of<00:20:44.710> commit<00:20:45.040> reveal<00:20:45.310> then<00:20:45.550> as<00:20:46.060> a 00:20:46.110 --> 00:20:46.120 align:start position:0% some type of commit reveal then as a 00:20:46.120 --> 00:20:48.600 align:start position:0% some type of commit reveal then as a consequence<00:20:46.690> and<00:20:46.960> that<00:20:47.230> does<00:20:47.470> extend<00:20:48.370> out<00:20:48.490> the 00:20:48.600 --> 00:20:48.610 align:start position:0% consequence and that does extend out the 00:20:48.610 --> 00:20:50.160 align:start position:0% consequence and that does extend out the challenge<00:20:48.970> appeared<00:20:49.210> it<00:20:49.330> probably<00:20:49.720> increases 00:20:50.160 --> 00:20:50.170 align:start position:0% challenge appeared it probably increases 00:20:50.170 --> 00:20:53.310 align:start position:0% challenge appeared it probably increases the<00:20:50.320> exit<00:20:50.560> code<00:20:50.710> by<00:20:50.890> like<00:20:51.070> you<00:20:51.220> know<00:20:52.320> the 00:20:53.310 --> 00:20:53.320 align:start position:0% the exit code by like you know the 00:20:53.320 --> 00:20:55.920 align:start position:0% the exit code by like you know the Kelvin<00:20:53.680> had<00:20:53.920> and<00:20:54.070> I<00:20:54.130> had<00:20:54.190> a<00:20:54.700> point<00:20:55.450> in<00:20:55.630> a<00:20:55.690> chant 00:20:55.920 --> 00:20:55.930 align:start position:0% Kelvin had and I had a point in a chant 00:20:55.930 --> 00:20:59.190 align:start position:0% Kelvin had and I had a point in a chant about<00:20:56.200> the<00:20:56.410> submarine<00:20:56.800> commitments<00:20:58.200> Kelvin 00:20:59.190 --> 00:20:59.200 align:start position:0% about the submarine commitments Kelvin 00:20:59.200 --> 00:21:01.050 align:start position:0% about the submarine commitments Kelvin can<00:20:59.320> you<00:20:59.440> explain<00:20:59.680> it<00:20:59.830> ensured<00:21:00.340> I<00:21:00.550> read<00:21:00.820> the 00:21:01.050 --> 00:21:01.060 align:start position:0% can you explain it ensured I read the 00:21:01.060 --> 00:21:04.230 align:start position:0% can you explain it ensured I read the documents<00:21:01.750> and<00:21:01.960> well<00:21:02.620> more<00:21:03.220> or<00:21:03.370> less<00:21:03.430> just<00:21:03.580> get 00:21:04.230 --> 00:21:04.240 align:start position:0% documents and well more or less just get 00:21:04.240 --> 00:21:07.290 align:start position:0% documents and well more or less just get and<00:21:04.960> I<00:21:05.140> have<00:21:05.590> one<00:21:05.770> question<00:21:06.130> which<00:21:06.310> will<00:21:06.490> need 00:21:07.290 --> 00:21:07.300 align:start position:0% and I have one question which will need 00:21:07.300 --> 00:21:11.940 align:start position:0% and I have one question which will need to<00:21:07.690> be<00:21:07.990> answered<00:21:08.110> later<00:21:08.880> sure<00:21:09.880> so<00:21:10.590> the<00:21:11.590> problem 00:21:11.940 --> 00:21:11.950 align:start position:0% to be answered later sure so the problem 00:21:11.950 --> 00:21:14.850 align:start position:0% to be answered later sure so the problem with<00:21:12.070> just<00:21:12.310> just<00:21:13.300> standard<00:21:13.780> commit<00:21:14.320> reveal<00:21:14.620> is 00:21:14.850 --> 00:21:14.860 align:start position:0% with just just standard commit reveal is 00:21:14.860 --> 00:21:18.510 align:start position:0% with just just standard commit reveal is that<00:21:15.960> usually<00:21:16.960> well<00:21:17.320> the<00:21:18.070> fact<00:21:18.280> that<00:21:18.340> I'm 00:21:18.510 --> 00:21:18.520 align:start position:0% that usually well the fact that I'm 00:21:18.520 --> 00:21:20.430 align:start position:0% that usually well the fact that I'm committing<00:21:19.000> is<00:21:19.150> leaking<00:21:19.630> information<00:21:19.840> about 00:21:20.430 --> 00:21:20.440 align:start position:0% committing is leaking information about 00:21:20.440 --> 00:21:22.710 align:start position:0% committing is leaking information about the<00:21:20.620> fact<00:21:20.830> that<00:21:20.920> I<00:21:21.160> am<00:21:21.610> going<00:21:22.150> to<00:21:22.300> make<00:21:22.570> an 00:21:22.710 --> 00:21:22.720 align:start position:0% the fact that I am going to make an 00:21:22.720 --> 00:21:23.970 align:start position:0% the fact that I am going to make an action<00:21:23.050> I'm<00:21:23.230> not<00:21:23.350> telling<00:21:23.620> you<00:21:23.680> what<00:21:23.860> the 00:21:23.970 --> 00:21:23.980 align:start position:0% action I'm not telling you what the 00:21:23.980 --> 00:21:29.340 align:start position:0% action I'm not telling you what the action<00:21:24.310> is<00:21:27.570> you<00:21:28.570> confront<00:21:28.990> transit 00:21:29.340 --> 00:21:29.350 align:start position:0% action is you confront transit 00:21:29.350 --> 00:21:32.160 align:start position:0% action is you confront transit commitment<00:21:29.740> you<00:21:29.830> can<00:21:29.890> recommit<00:21:30.430> right<00:21:31.390> or<00:21:31.990> if 00:21:32.160 --> 00:21:32.170 align:start position:0% commitment you can recommit right or if 00:21:32.170 --> 00:21:33.990 align:start position:0% commitment you can recommit right or if you<00:21:32.320> cannot<00:21:32.920> be<00:21:33.160> allowed<00:21:33.340> to<00:21:33.400> reconvene 00:21:33.990 --> 00:21:34.000 align:start position:0% you cannot be allowed to reconvene 00:21:34.000 --> 00:21:37.740 align:start position:0% you cannot be allowed to reconvene that's<00:21:35.100> I<00:21:36.100> think<00:21:36.490> the<00:21:36.670> strongest<00:21:36.910> attack<00:21:37.420> is 00:21:37.740 --> 00:21:37.750 align:start position:0% that's I think the strongest attack is 00:21:37.750 --> 00:21:39.810 align:start position:0% that's I think the strongest attack is is<00:21:38.170> not<00:21:38.410> too<00:21:38.530> far<00:21:38.740> under<00:21:39.040> commitment<00:21:39.460> it's<00:21:39.610> to 00:21:39.810 --> 00:21:39.820 align:start position:0% is not too far under commitment it's to 00:21:39.820 --> 00:21:45.120 align:start position:0% is not too far under commitment it's to notice<00:21:40.570> that<00:21:43.500> absolutely<00:21:44.500> that's<00:21:44.830> the<00:21:44.920> point 00:21:45.120 --> 00:21:45.130 align:start position:0% notice that absolutely that's the point 00:21:45.130 --> 00:21:48.870 align:start position:0% notice that absolutely that's the point right<00:21:45.250> so<00:21:45.370> that<00:21:45.670> I<00:21:45.790> if<00:21:46.540> I'm<00:21:46.720> a<00:21:46.750> minor<00:21:47.880> the 00:21:48.870 --> 00:21:48.880 align:start position:0% right so that I if I'm a minor the 00:21:48.880 --> 00:21:51.480 align:start position:0% right so that I if I'm a minor the original<00:21:49.240> problem<00:21:49.570> is<00:21:49.690> that<00:21:49.870> if<00:21:50.500> if<00:21:50.800> I<00:21:51.010> see<00:21:51.280> a 00:21:51.480 --> 00:21:51.490 align:start position:0% original problem is that if if I see a 00:21:51.490 --> 00:21:53.820 align:start position:0% original problem is that if if I see a challenge<00:21:51.820> I<00:21:52.270> can<00:21:52.840> just<00:21:53.230> execute<00:21:53.710> the 00:21:53.820 --> 00:21:53.830 align:start position:0% challenge I can just execute the 00:21:53.830 --> 00:21:56.430 align:start position:0% challenge I can just execute the challenge<00:21:54.190> and<00:21:54.430> boom<00:21:55.210> I'll<00:21:55.570> see<00:21:56.110> that<00:21:56.140> it's<00:21:56.380> a 00:21:56.430 --> 00:21:56.440 align:start position:0% challenge and boom I'll see that it's a 00:21:56.440 --> 00:21:58.320 align:start position:0% challenge and boom I'll see that it's a valid<00:21:56.650> challenge<00:21:57.130> so<00:21:57.610> I'll<00:21:57.730> front<00:21:57.940> and<00:21:58.120> run<00:21:58.210> it 00:21:58.320 --> 00:21:58.330 align:start position:0% valid challenge so I'll front and run it 00:21:58.330 --> 00:21:59.760 align:start position:0% valid challenge so I'll front and run it and<00:21:58.450> I'll<00:21:58.570> take<00:21:58.780> the<00:21:58.930> fee<00:21:59.080> instead<00:21:59.500> of<00:21:59.620> the 00:21:59.760 --> 00:21:59.770 align:start position:0% and I'll take the fee instead of the 00:21:59.770 --> 00:22:01.530 align:start position:0% and I'll take the fee instead of the person<00:22:00.070> who<00:22:00.160> actually<00:22:00.340> did<00:22:00.700> the<00:22:00.820> work<00:22:01.000> to<00:22:01.030> spot 00:22:01.530 --> 00:22:01.540 align:start position:0% person who actually did the work to spot 00:22:01.540 --> 00:22:03.720 align:start position:0% person who actually did the work to spot the<00:22:01.720> error<00:22:01.870> and<00:22:02.200> and<00:22:02.740> throw<00:22:03.100> the<00:22:03.220> challenge<00:22:03.370> so 00:22:03.720 --> 00:22:03.730 align:start position:0% the error and and throw the challenge so 00:22:03.730 --> 00:22:05.610 align:start position:0% the error and and throw the challenge so the<00:22:03.970> the<00:22:04.180> first<00:22:04.210> solution<00:22:04.750> that<00:22:05.200> you<00:22:05.290> could<00:22:05.500> do 00:22:05.610 --> 00:22:05.620 align:start position:0% the the first solution that you could do 00:22:05.620 --> 00:22:08.660 align:start position:0% the the first solution that you could do is<00:22:05.800> make<00:22:06.190> a<00:22:06.220> commitment<00:22:06.460> so<00:22:06.910> somebody<00:22:07.840> is<00:22:08.020> is 00:22:08.660 --> 00:22:08.670 align:start position:0% is make a commitment so somebody is is 00:22:08.670 --> 00:22:12.300 align:start position:0% is make a commitment so somebody is is asked<00:22:09.670> to<00:22:09.940> commit<00:22:10.420> to<00:22:11.230> making<00:22:11.680> a<00:22:11.920> challenge 00:22:12.300 --> 00:22:12.310 align:start position:0% asked to commit to making a challenge 00:22:12.310 --> 00:22:12.780 align:start position:0% asked to commit to making a challenge before 00:22:12.780 --> 00:22:12.790 align:start position:0% before 00:22:12.790 --> 00:22:13.980 align:start position:0% before actually<00:22:13.060> revealing<00:22:13.420> the<00:22:13.630> challenged 00:22:13.980 --> 00:22:13.990 align:start position:0% actually revealing the challenged 00:22:13.990 --> 00:22:16.650 align:start position:0% actually revealing the challenged information<00:22:15.000> the<00:22:16.000> problem<00:22:16.300> with<00:22:16.390> this<00:22:16.480> is 00:22:16.650 --> 00:22:16.660 align:start position:0% information the problem with this is 00:22:16.660 --> 00:22:18.240 align:start position:0% information the problem with this is that<00:22:16.720> it<00:22:16.840> leaks<00:22:17.110> the<00:22:17.380> information<00:22:17.980> that 00:22:18.240 --> 00:22:18.250 align:start position:0% that it leaks the information that 00:22:18.250 --> 00:22:20.430 align:start position:0% that it leaks the information that somebody<00:22:18.610> is<00:22:18.760> going<00:22:19.060> to<00:22:19.210> challenge<00:22:19.720> later<00:22:20.170> and 00:22:20.430 --> 00:22:20.440 align:start position:0% somebody is going to challenge later and 00:22:20.440 --> 00:22:27.600 align:start position:0% somebody is going to challenge later and so<00:22:20.890> what<00:22:21.220> they<00:22:21.340> do<00:22:21.400> is<00:22:26.130> it<00:22:27.130> doesn't<00:22:27.340> look<00:22:27.550> that 00:22:27.600 --> 00:22:27.610 align:start position:0% so what they do is it doesn't look that 00:22:27.610 --> 00:22:29.070 align:start position:0% so what they do is it doesn't look that somebody<00:22:28.030> will<00:22:28.180> turn<00:22:28.360> it<00:22:28.720> looks<00:22:28.900> that 00:22:29.070 --> 00:22:29.080 align:start position:0% somebody will turn it looks that 00:22:29.080 --> 00:22:33.720 align:start position:0% somebody will turn it looks that somebody<00:22:29.470> made<00:22:30.100> an<00:22:30.250> action<00:22:32.400> at<00:22:33.400> least<00:22:33.610> that 00:22:33.720 --> 00:22:33.730 align:start position:0% somebody made an action at least that 00:22:33.730 --> 00:22:35.580 align:start position:0% somebody made an action at least that somebody<00:22:34.000> somebody<00:22:34.360> made<00:22:34.600> an<00:22:34.720> action<00:22:35.050> and<00:22:35.290> and 00:22:35.580 --> 00:22:35.590 align:start position:0% somebody somebody made an action and and 00:22:35.590 --> 00:22:37.200 align:start position:0% somebody somebody made an action and and because<00:22:35.980> somebody<00:22:36.310> is<00:22:36.460> forced<00:22:36.850> to<00:22:36.940> make<00:22:37.060> an 00:22:37.200 --> 00:22:37.210 align:start position:0% because somebody is forced to make an 00:22:37.210 --> 00:22:39.630 align:start position:0% because somebody is forced to make an action<00:22:37.540> before<00:22:38.350> challenging<00:22:38.890> later<00:22:39.370> right 00:22:39.630 --> 00:22:39.640 align:start position:0% action before challenging later right 00:22:39.640 --> 00:22:41.250 align:start position:0% action before challenging later right we've<00:22:39.790> we've<00:22:40.120> asked<00:22:40.420> people<00:22:40.540> to<00:22:40.660> commit<00:22:41.080> then 00:22:41.250 --> 00:22:41.260 align:start position:0% we've we've asked people to commit then 00:22:41.260 --> 00:22:44.430 align:start position:0% we've we've asked people to commit then reveal<00:22:41.850> a<00:22:42.850> minor<00:22:43.330> can<00:22:43.600> say<00:22:43.780> ok<00:22:44.080> I<00:22:44.110> saw<00:22:44.410> a 00:22:44.430 --> 00:22:44.440 align:start position:0% reveal a minor can say ok I saw a 00:22:44.440 --> 00:22:46.320 align:start position:0% reveal a minor can say ok I saw a commitment<00:22:44.980> so<00:22:45.160> now<00:22:45.370> I'm<00:22:45.520> going<00:22:45.790> to<00:22:45.910> check<00:22:46.120> it 00:22:46.320 --> 00:22:46.330 align:start position:0% commitment so now I'm going to check it 00:22:46.330 --> 00:22:48.150 align:start position:0% commitment so now I'm going to check it and<00:22:46.510> then<00:22:46.900> I'm<00:22:47.020> gonna<00:22:47.170> front<00:22:47.470> run<00:22:47.680> and<00:22:47.890> I'm 00:22:48.150 --> 00:22:48.160 align:start position:0% and then I'm gonna front run and I'm 00:22:48.160 --> 00:22:49.650 align:start position:0% and then I'm gonna front run and I'm gonna<00:22:48.370> I'm<00:22:48.610> gonna<00:22:48.790> get<00:22:48.970> my<00:22:49.090> commitment<00:22:49.570> in 00:22:49.650 --> 00:22:49.660 align:start position:0% gonna I'm gonna get my commitment in 00:22:49.660 --> 00:22:51.840 align:start position:0% gonna I'm gonna get my commitment in first<00:22:49.930> and<00:22:50.140> so<00:22:50.680> the<00:22:51.190> problem<00:22:51.460> with<00:22:51.550> this<00:22:51.670> is 00:22:51.840 --> 00:22:51.850 align:start position:0% first and so the problem with this is 00:22:51.850 --> 00:22:53.910 align:start position:0% first and so the problem with this is that<00:22:51.880> it's<00:22:52.420> the<00:22:52.570> same<00:22:52.750> exact<00:22:53.140> same<00:22:53.560> exact 00:22:53.910 --> 00:22:53.920 align:start position:0% that it's the same exact same exact 00:22:53.920 --> 00:22:56.160 align:start position:0% that it's the same exact same exact issue<00:22:54.100> the<00:22:54.730> a<00:22:54.970> minor<00:22:55.180> they<00:22:55.690> don't<00:22:55.840> have<00:22:55.960> to<00:22:56.050> do 00:22:56.160 --> 00:22:56.170 align:start position:0% issue the a minor they don't have to do 00:22:56.170 --> 00:22:58.200 align:start position:0% issue the a minor they don't have to do any<00:22:56.380> work<00:22:56.470> until<00:22:57.430> somebody<00:22:57.730> else<00:22:57.880> does<00:22:58.090> the 00:22:58.200 --> 00:22:58.210 align:start position:0% any work until somebody else does the 00:22:58.210 --> 00:22:59.910 align:start position:0% any work until somebody else does the work<00:22:58.390> then<00:22:59.080> they<00:22:59.230> can<00:22:59.440> do<00:22:59.560> it 00:22:59.910 --> 00:22:59.920 align:start position:0% work then they can do it 00:22:59.920 --> 00:23:01.890 align:start position:0% work then they can do it they<00:23:00.250> can<00:23:00.430> spot<00:23:00.640> the<00:23:00.790> problem<00:23:00.910> front<00:23:01.600> run<00:23:01.750> it 00:23:01.890 --> 00:23:01.900 align:start position:0% they can spot the problem front run it 00:23:01.900 --> 00:23:03.600 align:start position:0% they can spot the problem front run it and<00:23:02.020> take<00:23:02.410> the<00:23:02.590> fee<00:23:02.800> and<00:23:03.100> which<00:23:03.250> kind<00:23:03.520> of 00:23:03.600 --> 00:23:03.610 align:start position:0% and take the fee and which kind of 00:23:03.610 --> 00:23:06.210 align:start position:0% and take the fee and which kind of destroys<00:23:04.360> the<00:23:04.600> whole<00:23:04.630> thing<00:23:04.900> so<00:23:05.110> so<00:23:05.620> generally 00:23:06.210 --> 00:23:06.220 align:start position:0% destroys the whole thing so so generally 00:23:06.220 --> 00:23:08.100 align:start position:0% destroys the whole thing so so generally the<00:23:06.580> idea<00:23:06.910> of<00:23:06.970> these<00:23:07.150> submarine<00:23:07.570> commitments 00:23:08.100 --> 00:23:08.110 align:start position:0% the idea of these submarine commitments 00:23:08.110 --> 00:23:09.660 align:start position:0% the idea of these submarine commitments is<00:23:08.260> that<00:23:08.440> you<00:23:08.530> make<00:23:08.710> a<00:23:08.740> commitment<00:23:09.130> in<00:23:09.400> a<00:23:09.490> way 00:23:09.660 --> 00:23:09.670 align:start position:0% is that you make a commitment in a way 00:23:09.670 --> 00:23:12.690 align:start position:0% is that you make a commitment in a way that<00:23:10.230> you're<00:23:11.230> not<00:23:11.520> leaking<00:23:12.520> the<00:23:12.670> information 00:23:12.690 --> 00:23:12.700 align:start position:0% that you're not leaking the information 00:23:12.700 --> 00:23:15.600 align:start position:0% that you're not leaking the information that<00:23:13.390> you<00:23:13.480> have<00:23:13.660> made<00:23:13.930> a<00:23:14.140> commitment<00:23:14.530> right<00:23:15.040> so 00:23:15.600 --> 00:23:15.610 align:start position:0% that you have made a commitment right so 00:23:15.610 --> 00:23:18.000 align:start position:0% that you have made a commitment right so you<00:23:15.910> basically<00:23:16.090> send<00:23:16.720> a<00:23:16.870> transaction<00:23:17.500> to<00:23:17.530> some 00:23:18.000 --> 00:23:18.010 align:start position:0% you basically send a transaction to some 00:23:18.010 --> 00:23:20.730 align:start position:0% you basically send a transaction to some random<00:23:18.640> address<00:23:19.300> and<00:23:19.540> then<00:23:19.960> you<00:23:20.080> later<00:23:20.290> prove 00:23:20.730 --> 00:23:20.740 align:start position:0% random address and then you later prove 00:23:20.740 --> 00:23:22.260 align:start position:0% random address and then you later prove that<00:23:21.070> you<00:23:21.190> made<00:23:21.340> a<00:23:21.370> transaction<00:23:21.820> to<00:23:22.150> that 00:23:22.260 --> 00:23:22.270 align:start position:0% that you made a transaction to that 00:23:22.270 --> 00:23:24.990 align:start position:0% that you made a transaction to that random<00:23:22.480> address<00:23:22.930> and<00:23:23.220> nobody<00:23:24.220> can<00:23:24.430> tell<00:23:24.700> that 00:23:24.990 --> 00:23:25.000 align:start position:0% random address and nobody can tell that 00:23:25.000 --> 00:23:27.660 align:start position:0% random address and nobody can tell that you<00:23:25.090> made<00:23:25.330> a<00:23:25.360> commitment<00:23:26.050> in<00:23:26.200> advance<00:23:26.890> and<00:23:27.130> and 00:23:27.660 --> 00:23:27.670 align:start position:0% you made a commitment in advance and and 00:23:27.670 --> 00:23:29.040 align:start position:0% you made a commitment in advance and and so<00:23:28.120> the<00:23:28.240> benefit<00:23:28.540> of<00:23:28.630> this<00:23:28.690> is<00:23:28.750> that<00:23:28.960> you're 00:23:29.040 --> 00:23:29.050 align:start position:0% so the benefit of this is that you're 00:23:29.050 --> 00:23:31.590 align:start position:0% so the benefit of this is that you're not<00:23:29.200> leaking<00:23:29.560> the<00:23:29.710> information<00:23:30.700> that<00:23:30.970> you<00:23:31.150> you 00:23:31.590 --> 00:23:31.600 align:start position:0% not leaking the information that you you 00:23:31.600 --> 00:23:33.510 align:start position:0% not leaking the information that you you make<00:23:31.840> you<00:23:32.140> might<00:23:32.350> be<00:23:32.500> planning<00:23:32.920> to<00:23:32.950> act<00:23:33.190> later 00:23:33.510 --> 00:23:33.520 align:start position:0% make you might be planning to act later 00:23:33.520 --> 00:23:35.940 align:start position:0% make you might be planning to act later on<00:23:33.730> and<00:23:34.120> so<00:23:34.570> you<00:23:35.200> don't<00:23:35.650> have<00:23:35.830> this 00:23:35.940 --> 00:23:35.950 align:start position:0% on and so you don't have this 00:23:35.950 --> 00:23:37.020 align:start position:0% on and so you don't have this front-running<00:23:36.310> problem<00:23:36.670> but<00:23:36.820> it<00:23:36.910> is 00:23:37.020 --> 00:23:37.030 align:start position:0% front-running problem but it is 00:23:37.030 --> 00:23:40.620 align:start position:0% front-running problem but it is significantly<00:23:37.990> more<00:23:38.200> complex<00:23:38.650> than<00:23:39.280> then<00:23:39.850> not 00:23:40.620 --> 00:23:40.630 align:start position:0% significantly more complex than then not 00:23:40.630 --> 00:23:43.860 align:start position:0% significantly more complex than then not having<00:23:41.050> this<00:23:41.230> right<00:23:41.740> I<00:23:42.010> think<00:23:42.550> from<00:23:42.970> my 00:23:43.860 --> 00:23:43.870 align:start position:0% having this right I think from my 00:23:43.870 --> 00:23:46.260 align:start position:0% having this right I think from my perspective<00:23:44.260> is<00:23:44.770> I<00:23:44.800> think<00:23:45.100> you<00:23:45.490> know<00:23:45.520> given 00:23:46.260 --> 00:23:46.270 align:start position:0% perspective is I think you know given 00:23:46.270 --> 00:23:47.820 align:start position:0% perspective is I think you know given given<00:23:46.780> your<00:23:46.900> worst<00:23:47.110> case<00:23:47.290> searches<00:23:47.650> I 00:23:47.820 --> 00:23:47.830 align:start position:0% given your worst case searches I 00:23:47.830 --> 00:23:49.350 align:start position:0% given your worst case searches I actually<00:23:47.980> don't<00:23:48.280> think<00:23:48.340> it's<00:23:48.520> that<00:23:48.700> bad<00:23:48.880> you 00:23:49.350 --> 00:23:49.360 align:start position:0% actually don't think it's that bad you 00:23:49.360 --> 00:23:50.970 align:start position:0% actually don't think it's that bad you know<00:23:49.480> like<00:23:49.660> if<00:23:49.900> it<00:23:50.050> ends<00:23:50.260> up<00:23:50.350> being<00:23:50.590> the<00:23:50.800> minor 00:23:50.970 --> 00:23:50.980 align:start position:0% know like if it ends up being the minor 00:23:50.980 --> 00:23:52.590 align:start position:0% know like if it ends up being the minor just<00:23:51.310> ends<00:23:51.550> up<00:23:51.640> collecting<00:23:51.940> the<00:23:52.150> fees<00:23:52.330> that 00:23:52.590 --> 00:23:52.600 align:start position:0% just ends up collecting the fees that 00:23:52.600 --> 00:23:54.900 align:start position:0% just ends up collecting the fees that amounts<00:23:53.470> to<00:23:53.530> being<00:23:53.770> burning<00:23:54.070> the<00:23:54.190> coins<00:23:54.400> right 00:23:54.900 --> 00:23:54.910 align:start position:0% amounts to being burning the coins right 00:23:54.910 --> 00:23:56.340 align:start position:0% amounts to being burning the coins right from<00:23:55.150> from<00:23:55.510> an<00:23:55.630> individual's<00:23:56.110> perspective 00:23:56.340 --> 00:23:56.350 align:start position:0% from from an individual's perspective 00:23:56.350 --> 00:23:59.720 align:start position:0% from from an individual's perspective and<00:23:56.970> I<00:23:57.970> think<00:23:58.570> that's<00:23:58.720> acceptable<00:23:59.050> because 00:23:59.720 --> 00:23:59.730 align:start position:0% and I think that's acceptable because 00:23:59.730 --> 00:24:05.160 align:start position:0% and I think that's acceptable because because<00:24:02.820> there<00:24:03.820> is<00:24:03.940> no<00:24:04.090> equilibrium<00:24:04.660> in<00:24:05.050> that 00:24:05.160 --> 00:24:05.170 align:start position:0% because there is no equilibrium in that 00:24:05.170 --> 00:24:07.860 align:start position:0% because there is no equilibrium in that situation<00:24:05.740> because<00:24:05.860> you<00:24:06.690> challenges<00:24:07.690> will 00:24:07.860 --> 00:24:07.870 align:start position:0% situation because you challenges will 00:24:07.870 --> 00:24:09.720 align:start position:0% situation because you challenges will stop<00:24:08.170> even<00:24:08.680> though<00:24:08.800> there<00:24:08.980> are<00:24:09.010> invalid<00:24:09.550> oh<00:24:09.700> I 00:24:09.720 --> 00:24:09.730 align:start position:0% stop even though there are invalid oh I 00:24:09.730 --> 00:24:11.280 align:start position:0% stop even though there are invalid oh I think<00:24:09.910> there's<00:24:10.180> sufficient<00:24:10.630> incentive<00:24:10.870> to<00:24:11.140> do 00:24:11.280 --> 00:24:11.290 align:start position:0% think there's sufficient incentive to do 00:24:11.290 --> 00:24:13.500 align:start position:0% think there's sufficient incentive to do challenges<00:24:11.740> anyway<00:24:12.130> yeah<00:24:12.430> like<00:24:12.970> I'm<00:24:13.120> not<00:24:13.150> I'm 00:24:13.500 --> 00:24:13.510 align:start position:0% challenges anyway yeah like I'm not I'm 00:24:13.510 --> 00:24:15.150 align:start position:0% challenges anyway yeah like I'm not I'm not<00:24:13.570> totally<00:24:13.900> concerned<00:24:14.440> with<00:24:14.590> that<00:24:14.710> yeah<00:24:15.130> I 00:24:15.150 --> 00:24:15.160 align:start position:0% not totally concerned with that yeah I 00:24:15.160 --> 00:24:16.950 align:start position:0% not totally concerned with that yeah I agree<00:24:15.430> I<00:24:15.610> mean<00:24:15.850> the<00:24:16.060> the<00:24:16.330> cool<00:24:16.570> thing<00:24:16.780> about 00:24:16.950 --> 00:24:16.960 align:start position:0% agree I mean the the cool thing about 00:24:16.960 --> 00:24:19.050 align:start position:0% agree I mean the the cool thing about like<00:24:17.230> plasma<00:24:17.500> cash<00:24:17.860> and<00:24:18.250> plasma<00:24:18.760> from<00:24:18.850> these 00:24:19.050 --> 00:24:19.060 align:start position:0% like plasma cash and plasma from these 00:24:19.060 --> 00:24:21.270 align:start position:0% like plasma cash and plasma from these kinds<00:24:19.360> of<00:24:19.450> Merkle<00:24:20.260> tree<00:24:20.530> where<00:24:20.800> you<00:24:20.830> own<00:24:21.250> a 00:24:21.270 --> 00:24:21.280 align:start position:0% kinds of Merkle tree where you own a 00:24:21.280 --> 00:24:24.630 align:start position:0% kinds of Merkle tree where you own a particular<00:24:21.640> subtree<00:24:23.040> the<00:24:24.040> cool<00:24:24.250> thing<00:24:24.460> is 00:24:24.630 --> 00:24:24.640 align:start position:0% particular subtree the cool thing is 00:24:24.640 --> 00:24:26.680 align:start position:0% particular subtree the cool thing is that<00:24:24.670> you<00:24:25.240> have<00:24:25.270> a<00:24:25.480> very<00:24:25.810> strong<00:24:26.170> incentive 00:24:26.680 --> 00:24:26.690 align:start position:0% that you have a very strong incentive 00:24:26.690 --> 00:24:28.360 align:start position:0% that you have a very strong incentive to<00:24:26.870> challenge<00:24:27.290> no<00:24:27.470> matter<00:24:27.500> what<00:24:27.920> even<00:24:28.130> if 00:24:28.360 --> 00:24:28.370 align:start position:0% to challenge no matter what even if 00:24:28.370 --> 00:24:29.800 align:start position:0% to challenge no matter what even if you're<00:24:28.520> not<00:24:28.700> gonna<00:24:28.820> even<00:24:29.270> if<00:24:29.480> you're<00:24:29.600> gonna 00:24:29.800 --> 00:24:29.810 align:start position:0% you're not gonna even if you're gonna 00:24:29.810 --> 00:24:32.110 align:start position:0% you're not gonna even if you're gonna not<00:24:30.230> make<00:24:30.260> any<00:24:30.560> money<00:24:30.710> from<00:24:30.920> this<00:24:31.160> like<00:24:31.640> your 00:24:32.110 --> 00:24:32.120 align:start position:0% not make any money from this like your 00:24:32.120 --> 00:24:35.320 align:start position:0% not make any money from this like your coins<00:24:32.390> are<00:24:32.630> at<00:24:32.750> risk<00:24:33.190> basically<00:24:34.190> I<00:24:34.220> think<00:24:34.430> what 00:24:35.320 --> 00:24:35.330 align:start position:0% coins are at risk basically I think what 00:24:35.330 --> 00:24:37.690 align:start position:0% coins are at risk basically I think what we're<00:24:35.510> talking<00:24:35.840> about<00:24:35.900> is<00:24:36.410> what<00:24:36.980> what<00:24:37.190> I<00:24:37.400> think 00:24:37.690 --> 00:24:37.700 align:start position:0% we're talking about is what what I think 00:24:37.700 --> 00:24:39.220 align:start position:0% we're talking about is what what I think the<00:24:37.790> implication<00:24:38.360> if<00:24:38.480> we<00:24:38.570> wanted<00:24:38.840> to<00:24:38.900> hone 00:24:39.220 --> 00:24:39.230 align:start position:0% the implication if we wanted to hone 00:24:39.230 --> 00:24:41.050 align:start position:0% the implication if we wanted to hone down<00:24:39.260> and<00:24:39.620> on<00:24:39.980> your<00:24:40.190> concern<00:24:40.490> George's<00:24:40.880> is 00:24:41.050 --> 00:24:41.060 align:start position:0% down and on your concern George's is 00:24:41.060 --> 00:24:44.050 align:start position:0% down and on your concern George's is that<00:24:41.270> if<00:24:42.230> you<00:24:42.560> can<00:24:42.740> get<00:24:42.950> what<00:24:43.130> you<00:24:43.160> want<00:24:43.520> in 00:24:44.050 --> 00:24:44.060 align:start position:0% that if you can get what you want in 00:24:44.060 --> 00:24:46.510 align:start position:0% that if you can get what you want in terms<00:24:44.150> of<00:24:44.510> your<00:24:44.630> goals<00:24:44.660> um<00:24:45.260> bond<00:24:45.950> sizes<00:24:46.370> to 00:24:46.510 --> 00:24:46.520 align:start position:0% terms of your goals um bond sizes to 00:24:46.520 --> 00:24:48.760 align:start position:0% terms of your goals um bond sizes to decrease<00:24:46.910> dramatically<00:24:47.390> I<00:24:47.660> think<00:24:48.410> that's<00:24:48.560> the 00:24:48.760 --> 00:24:48.770 align:start position:0% decrease dramatically I think that's the 00:24:48.770 --> 00:24:50.680 align:start position:0% decrease dramatically I think that's the end<00:24:48.860> result<00:24:49.040> because<00:24:49.550> I<00:24:49.580> think<00:24:49.700> effectively 00:24:50.680 --> 00:24:50.690 align:start position:0% end result because I think effectively 00:24:50.690 --> 00:24:52.360 align:start position:0% end result because I think effectively if<00:24:50.960> you're<00:24:51.260> talking<00:24:51.440> about<00:24:51.650> your<00:24:51.890> worst<00:24:52.100> case 00:24:52.360 --> 00:24:52.370 align:start position:0% if you're talking about your worst case 00:24:52.370 --> 00:24:54.370 align:start position:0% if you're talking about your worst case it's<00:24:52.610> possible<00:24:52.790> that<00:24:53.180> the<00:24:53.300> bond<00:24:53.480> size<00:24:53.750> we'll 00:24:54.370 --> 00:24:54.380 align:start position:0% it's possible that the bond size we'll 00:24:54.380 --> 00:24:56.650 align:start position:0% it's possible that the bond size we'll get<00:24:54.560> fairly<00:24:55.250> large<00:24:55.490> and<00:24:55.640> maybe<00:24:55.850> maybe<00:24:56.300> you 00:24:56.650 --> 00:24:56.660 align:start position:0% get fairly large and maybe maybe you 00:24:56.660 --> 00:24:58.030 align:start position:0% get fairly large and maybe maybe you know<00:24:56.750> large<00:24:57.050> enough<00:24:57.350> that<00:24:57.380> you<00:24:57.680> have<00:24:57.830> to<00:24:57.860> be 00:24:58.030 --> 00:24:58.040 align:start position:0% know large enough that you have to be 00:24:58.040 --> 00:24:59.680 align:start position:0% know large enough that you have to be fairly<00:24:58.280> capitalized<00:24:58.850> in<00:24:59.000> order<00:24:59.180> to<00:24:59.270> do<00:24:59.390> it<00:24:59.510> and 00:24:59.680 --> 00:24:59.690 align:start position:0% fairly capitalized in order to do it and 00:24:59.690 --> 00:25:01.780 align:start position:0% fairly capitalized in order to do it and definitely<00:25:00.350> it's<00:25:00.800> a<00:25:00.860> it's<00:25:01.400> a<00:25:01.490> research 00:25:01.780 --> 00:25:01.790 align:start position:0% definitely it's a it's a research 00:25:01.790 --> 00:25:04.150 align:start position:0% definitely it's a it's a research opportunity<00:25:02.540> that<00:25:02.840> I<00:25:03.050> think<00:25:03.290> will<00:25:03.980> make<00:25:04.010> a 00:25:04.150 --> 00:25:04.160 align:start position:0% opportunity that I think will make a 00:25:04.160 --> 00:25:06.040 align:start position:0% opportunity that I think will make a pretty<00:25:05.090> big<00:25:05.240> difference<00:25:05.570> in<00:25:05.690> terms<00:25:05.720> of<00:25:05.960> the 00:25:06.040 --> 00:25:06.050 align:start position:0% pretty big difference in terms of the 00:25:06.050 --> 00:25:09.310 align:start position:0% pretty big difference in terms of the end<00:25:06.200> usability<00:25:06.890> in<00:25:07.730> terms<00:25:08.000> of<00:25:08.270> whether<00:25:08.840> one 00:25:09.310 --> 00:25:09.320 align:start position:0% end usability in terms of whether one 00:25:09.320 --> 00:25:11.620 align:start position:0% end usability in terms of whether one outsources<00:25:10.100> once<00:25:10.310> exits<00:25:10.700> in<00:25:10.850> terms<00:25:11.030> of<00:25:11.210> the<00:25:11.330> in 00:25:11.620 --> 00:25:11.630 align:start position:0% outsources once exits in terms of the in 00:25:11.630 --> 00:25:13.120 align:start position:0% outsources once exits in terms of the in sort<00:25:11.870> of<00:25:11.930> you<00:25:12.200> know<00:25:12.290> like<00:25:12.500> trading<00:25:12.770> the<00:25:12.950> coins 00:25:13.120 --> 00:25:13.130 align:start position:0% sort of you know like trading the coins 00:25:13.130 --> 00:25:17.530 align:start position:0% sort of you know like trading the coins trading<00:25:13.880> the<00:25:14.170> the<00:25:15.170> actual<00:25:15.560> value<00:25:16.390> so<00:25:17.390> I<00:25:17.420> think 00:25:17.530 --> 00:25:17.540 align:start position:0% trading the the actual value so I think 00:25:17.540 --> 00:25:19.300 align:start position:0% trading the the actual value so I think it<00:25:17.840> is<00:25:17.870> a<00:25:17.990> really<00:25:18.440> really<00:25:18.680> important<00:25:19.070> thing<00:25:19.220> to 00:25:19.300 --> 00:25:19.310 align:start position:0% it is a really really important thing to 00:25:19.310 --> 00:25:21.430 align:start position:0% it is a really really important thing to do<00:25:19.460> but<00:25:19.910> given<00:25:20.210> the<00:25:20.330> worst<00:25:20.510> case<00:25:20.810> I<00:25:21.050> think<00:25:21.170> you 00:25:21.430 --> 00:25:21.440 align:start position:0% do but given the worst case I think you 00:25:21.440 --> 00:25:23.020 align:start position:0% do but given the worst case I think you know<00:25:21.650> effectively<00:25:22.220> the<00:25:22.340> bond<00:25:22.490> sizes<00:25:22.880> if<00:25:23.000> you 00:25:23.020 --> 00:25:23.030 align:start position:0% know effectively the bond sizes if you 00:25:23.030 --> 00:25:26.110 align:start position:0% know effectively the bond sizes if you increase<00:25:23.390> it<00:25:23.540> enough<00:25:23.810> then<00:25:24.590> the<00:25:25.430> probability 00:25:26.110 --> 00:25:26.120 align:start position:0% increase it enough then the probability 00:25:26.120 --> 00:25:27.910 align:start position:0% increase it enough then the probability of<00:25:26.150> you<00:25:26.330> personally<00:25:26.630> watching<00:25:27.320> it<00:25:27.440> should<00:25:27.770> be 00:25:27.910 --> 00:25:27.920 align:start position:0% of you personally watching it should be 00:25:27.920 --> 00:25:30.220 align:start position:0% of you personally watching it should be sufficient<00:25:28.430> so<00:25:29.150> then<00:25:29.390> the<00:25:29.630> problem<00:25:29.780> reduces 00:25:30.220 --> 00:25:30.230 align:start position:0% sufficient so then the problem reduces 00:25:30.230 --> 00:25:32.920 align:start position:0% sufficient so then the problem reduces to<00:25:30.440> parameterizing<00:25:31.310> probably<00:25:31.880> and<00:25:32.060> so<00:25:32.630> I'm 00:25:32.920 --> 00:25:32.930 align:start position:0% to parameterizing probably and so I'm 00:25:32.930 --> 00:25:35.170 align:start position:0% to parameterizing probably and so I'm curious<00:25:33.260> from<00:25:33.380> the<00:25:33.650> how<00:25:34.580> would<00:25:34.760> you<00:25:34.880> properly 00:25:35.170 --> 00:25:35.180 align:start position:0% curious from the how would you properly 00:25:35.180 --> 00:25:37.660 align:start position:0% curious from the how would you properly parameterize<00:25:35.690> both<00:25:36.440> the<00:25:36.620> bonds<00:25:36.830> and<00:25:37.100> the 00:25:37.660 --> 00:25:37.670 align:start position:0% parameterize both the bonds and the 00:25:37.670 --> 00:25:41.110 align:start position:0% parameterize both the bonds and the duration<00:25:38.150> of<00:25:38.480> a<00:25:38.840> dispute<00:25:39.140> period<00:25:39.970> that's<00:25:40.970> a 00:25:41.110 --> 00:25:41.120 align:start position:0% duration of a dispute period that's a 00:25:41.120 --> 00:25:43.960 align:start position:0% duration of a dispute period that's a really<00:25:41.390> good<00:25:41.510> question<00:25:41.570> I<00:25:42.140> thought<00:25:42.860> and<00:25:43.760> I 00:25:43.960 --> 00:25:43.970 align:start position:0% really good question I thought and I 00:25:43.970 --> 00:25:45.280 align:start position:0% really good question I thought and I would<00:25:44.090> be<00:25:44.210> interested<00:25:44.330> in<00:25:44.630> a<00:25:44.720> good<00:25:45.050> like 00:25:45.280 --> 00:25:45.290 align:start position:0% would be interested in a good like 00:25:45.290 --> 00:25:48.880 align:start position:0% would be interested in a good like market<00:25:45.860> analysis<00:25:46.310> of<00:25:46.430> how<00:25:46.580> that<00:25:46.640> would<00:25:46.970> be<00:25:47.890> so 00:25:48.880 --> 00:25:48.890 align:start position:0% market analysis of how that would be so 00:25:48.890 --> 00:25:50.770 align:start position:0% market analysis of how that would be so the<00:25:48.980> other<00:25:49.100> thing<00:25:49.310> is<00:25:49.460> the<00:25:49.670> there<00:25:50.180> was<00:25:50.300> sort<00:25:50.720> of 00:25:50.770 --> 00:25:50.780 align:start position:0% the other thing is the there was sort of 00:25:50.780 --> 00:25:52.630 align:start position:0% the other thing is the there was sort of the<00:25:50.960> scorched<00:25:51.350> earth<00:25:51.440> version<00:25:52.160> of<00:25:52.280> this<00:25:52.400> which 00:25:52.630 --> 00:25:52.640 align:start position:0% the scorched earth version of this which 00:25:52.640 --> 00:25:55.450 align:start position:0% the scorched earth version of this which was<00:25:52.820> if<00:25:53.300> you<00:25:53.600> can<00:25:53.870> prove<00:25:54.320> that<00:25:54.620> an<00:25:54.890> invalid 00:25:55.450 --> 00:25:55.460 align:start position:0% was if you can prove that an invalid 00:25:55.460 --> 00:25:57.580 align:start position:0% was if you can prove that an invalid exit<00:25:55.910> went<00:25:56.180> through<00:25:56.450> you<00:25:57.020> burn<00:25:57.290> the<00:25:57.500> entire 00:25:57.580 --> 00:25:57.590 align:start position:0% exit went through you burn the entire 00:25:57.590 --> 00:26:00.400 align:start position:0% exit went through you burn the entire contract<00:25:58.340> down<00:25:58.640> and<00:25:58.910> so<00:25:59.480> it<00:25:59.840> creates<00:26:00.200> like<00:26:00.380> a 00:26:00.400 --> 00:26:00.410 align:start position:0% contract down and so it creates like a 00:26:00.410 --> 00:26:02.560 align:start position:0% contract down and so it creates like a massive<00:26:01.130> negative<00:26:01.610> incentive<00:26:02.120> for<00:26:02.330> you<00:26:02.450> to 00:26:02.560 --> 00:26:02.570 align:start position:0% massive negative incentive for you to 00:26:02.570 --> 00:26:05.440 align:start position:0% massive negative incentive for you to not<00:26:03.140> challenge<00:26:03.680> right<00:26:04.160> and<00:26:04.340> so<00:26:04.790> we<00:26:05.180> have<00:26:05.330> this 00:26:05.440 --> 00:26:05.450 align:start position:0% not challenge right and so we have this 00:26:05.450 --> 00:26:09.040 align:start position:0% not challenge right and so we have this problem<00:26:05.660> in<00:26:05.930> plasma<00:26:06.650> maybe<00:26:06.830> you<00:26:07.130> wear<00:26:08.050> this 00:26:09.040 --> 00:26:09.050 align:start position:0% problem in plasma maybe you wear this 00:26:09.050 --> 00:26:10.510 align:start position:0% problem in plasma maybe you wear this wouldn't<00:26:09.380> happen<00:26:09.500> in<00:26:09.740> plasma<00:26:10.040> cash<00:26:10.220> you<00:26:10.370> don't 00:26:10.510 --> 00:26:10.520 align:start position:0% wouldn't happen in plasma cash you don't 00:26:10.520 --> 00:26:11.710 align:start position:0% wouldn't happen in plasma cash you don't need<00:26:10.670> this<00:26:10.790> in<00:26:10.910> plasma<00:26:11.150> cash<00:26:11.270> but<00:26:11.480> impossible 00:26:11.710 --> 00:26:11.720 align:start position:0% need this in plasma cash but impossible 00:26:11.720 --> 00:26:14.050 align:start position:0% need this in plasma cash but impossible VP<00:26:12.200> of<00:26:12.350> this<00:26:12.500> problem<00:26:12.770> where<00:26:12.950> you<00:26:13.490> know<00:26:13.580> if<00:26:13.730> I 00:26:14.050 --> 00:26:14.060 align:start position:0% VP of this problem where you know if I 00:26:14.060 --> 00:26:16.840 align:start position:0% VP of this problem where you know if I make<00:26:14.450> an<00:26:14.570> invalid<00:26:14.960> exit<00:26:15.260> for<00:26:15.740> five<00:26:15.980> dollars<00:26:16.520> or 00:26:16.840 --> 00:26:16.850 align:start position:0% make an invalid exit for five dollars or 00:26:16.850 --> 00:26:18.490 align:start position:0% make an invalid exit for five dollars or whatever<00:26:17.000> you<00:26:17.270> know<00:26:17.360> points<00:26:17.750> zero<00:26:18.200> whatever 00:26:18.490 --> 00:26:18.500 align:start position:0% whatever you know points zero whatever 00:26:18.500 --> 00:26:23.920 align:start position:0% whatever you know points zero whatever eath<00:26:19.600> then<00:26:20.600> if<00:26:21.590> it<00:26:22.100> goes<00:26:22.280> through<00:26:22.610> the<00:26:23.600> people 00:26:23.920 --> 00:26:23.930 align:start position:0% eath then if it goes through the people 00:26:23.930 --> 00:26:26.680 align:start position:0% eath then if it goes through the people who<00:26:24.370> take<00:26:25.370> the<00:26:25.580> loss<00:26:25.790> or<00:26:26.120> the<00:26:26.210> people<00:26:26.480> at<00:26:26.570> the 00:26:26.680 --> 00:26:26.690 align:start position:0% who take the loss or the people at the 00:26:26.690 --> 00:26:28.480 align:start position:0% who take the loss or the people at the end<00:26:26.900> of<00:26:27.320> the<00:26:27.470> priority<00:26:27.950> queue<00:26:28.190> it's<00:26:28.400> the 00:26:28.480 --> 00:26:28.490 align:start position:0% end of the priority queue it's the 00:26:28.490 --> 00:26:31.300 align:start position:0% end of the priority queue it's the people<00:26:28.760> it's<00:26:29.060> it's<00:26:29.480> not<00:26:30.010> necessarily<00:26:31.010> me 00:26:31.300 --> 00:26:31.310 align:start position:0% people it's it's not necessarily me 00:26:31.310 --> 00:26:33.340 align:start position:0% people it's it's not necessarily me right<00:26:31.670> so<00:26:31.880> it<00:26:32.000> could<00:26:32.150> be<00:26:32.240> you<00:26:32.810> know<00:26:32.870> it's<00:26:33.110> just 00:26:33.340 --> 00:26:33.350 align:start position:0% right so it could be you know it's just 00:26:33.350 --> 00:26:36.160 align:start position:0% right so it could be you know it's just some<00:26:33.560> random<00:26:33.770> person<00:26:34.040> and<00:26:34.550> so<00:26:34.640> you<00:26:35.240> that<00:26:35.750> that 00:26:36.160 --> 00:26:36.170 align:start position:0% some random person and so you that that 00:26:36.170 --> 00:26:38.680 align:start position:0% some random person and so you that that person<00:26:36.650> would<00:26:37.120> they're<00:26:38.120> the<00:26:38.270> only<00:26:38.420> person 00:26:38.680 --> 00:26:38.690 align:start position:0% person would they're the only person 00:26:38.690 --> 00:26:40.150 align:start position:0% person would they're the only person who's<00:26:38.810> going<00:26:38.900> to<00:26:38.960> experience<00:26:39.410> the<00:26:39.500> negative 00:26:40.150 --> 00:26:40.160 align:start position:0% who's going to experience the negative 00:26:40.160 --> 00:26:42.370 align:start position:0% who's going to experience the negative of<00:26:40.190> impact<00:26:40.760> of<00:26:40.880> this<00:26:41.060> and<00:26:41.300> so<00:26:41.390> we<00:26:41.420> can<00:26:41.720> make 00:26:42.370 --> 00:26:42.380 align:start position:0% of impact of this and so we can make 00:26:42.380 --> 00:26:43.840 align:start position:0% of impact of this and so we can make other<00:26:42.650> people<00:26:43.070> experience<00:26:43.610> the<00:26:43.730> negative 00:26:43.840 --> 00:26:43.850 align:start position:0% other people experience the negative 00:26:43.850 --> 00:26:46.600 align:start position:0% other people experience the negative impact<00:26:44.330> of<00:26:44.450> this<00:26:44.630> if<00:26:44.840> we<00:26:45.080> basically<00:26:45.770> say<00:26:46.100> we 00:26:46.600 --> 00:26:46.610 align:start position:0% impact of this if we basically say we 00:26:46.610 --> 00:26:48.580 align:start position:0% impact of this if we basically say we will<00:26:46.820> burn<00:26:47.030> down<00:26:47.240> the<00:26:47.420> entire<00:26:47.690> contract<00:26:48.050> throw 00:26:48.580 --> 00:26:48.590 align:start position:0% will burn down the entire contract throw 00:26:48.590 --> 00:26:50.440 align:start position:0% will burn down the entire contract throw away<00:26:48.800> all<00:26:49.010> the<00:26:49.190> money<00:26:49.400> if<00:26:49.670> you<00:26:49.820> ever<00:26:50.030> let<00:26:50.300> this 00:26:50.440 --> 00:26:50.450 align:start position:0% away all the money if you ever let this 00:26:50.450 --> 00:26:53.110 align:start position:0% away all the money if you ever let this happen<00:26:50.660> which<00:26:51.260> is<00:26:51.290> like<00:26:51.770> you<00:26:52.280> know<00:26:52.400> probably 00:26:53.110 --> 00:26:53.120 align:start position:0% happen which is like you know probably 00:26:53.120 --> 00:26:55.000 align:start position:0% happen which is like you know probably not<00:26:53.480> a<00:26:53.540> great<00:26:53.840> solution<00:26:54.050> but<00:26:54.530> I<00:26:54.560> thought<00:26:54.860> it 00:26:55.000 --> 00:26:55.010 align:start position:0% not a great solution but I thought it 00:26:55.010 --> 00:26:56.770 align:start position:0% not a great solution but I thought it was<00:26:55.070> fun<00:26:55.340> and<00:26:55.640> it's<00:26:55.880> a<00:26:55.940> good<00:26:56.060> thing<00:26:56.120> I<00:26:56.600> think 00:26:56.770 --> 00:26:56.780 align:start position:0% was fun and it's a good thing I think 00:26:56.780 --> 00:26:58.300 align:start position:0% was fun and it's a good thing I think it's<00:26:56.900> great<00:26:57.020> I<00:26:57.110> think<00:26:57.230> that<00:26:57.530> there's<00:26:57.770> like<00:26:58.130> a 00:26:58.300 --> 00:26:58.310 align:start position:0% it's great I think that there's like a 00:26:58.310 --> 00:27:00.700 align:start position:0% it's great I think that there's like a general<00:26:58.820> rule<00:26:59.090> here<00:26:59.510> where<00:27:00.080> when<00:27:00.590> you're 00:27:00.700 --> 00:27:00.710 align:start position:0% general rule here where when you're 00:27:00.710 --> 00:27:02.230 align:start position:0% general rule here where when you're designing<00:27:01.100> these<00:27:01.340> like<00:27:01.580> economic<00:27:02.030> crypto 00:27:02.230 --> 00:27:02.240 align:start position:0% designing these like economic crypto 00:27:02.240 --> 00:27:04.510 align:start position:0% designing these like economic crypto anomic<00:27:02.570> mechanisms<00:27:03.080> you<00:27:03.650> don't<00:27:03.950> socialize 00:27:04.510 --> 00:27:04.520 align:start position:0% anomic mechanisms you don't socialize 00:27:04.520 --> 00:27:07.180 align:start position:0% anomic mechanisms you don't socialize losses<00:27:05.480> are<00:27:05.720> generally<00:27:06.380> scary<00:27:06.710> because<00:27:06.950> it's 00:27:07.180 --> 00:27:07.190 align:start position:0% losses are generally scary because it's 00:27:07.190 --> 00:27:08.980 align:start position:0% losses are generally scary because it's this<00:27:07.430> kind<00:27:07.580> of<00:27:07.700> common<00:27:08.090> goods<00:27:08.300> problem<00:27:08.600> right 00:27:08.980 --> 00:27:08.990 align:start position:0% this kind of common goods problem right 00:27:08.990 --> 00:27:10.780 align:start position:0% this kind of common goods problem right with<00:27:09.170> this<00:27:09.260> prisoner's<00:27:09.740> dilemma<00:27:09.890> we<00:27:10.220> you<00:27:10.700> know 00:27:10.780 --> 00:27:10.790 align:start position:0% with this prisoner's dilemma we you know 00:27:10.790 --> 00:27:12.280 align:start position:0% with this prisoner's dilemma we you know it's<00:27:11.060> not<00:27:11.180> really<00:27:11.330> gonna<00:27:11.510> affect<00:27:11.660> me<00:27:12.020> I'm 00:27:12.280 --> 00:27:12.290 align:start position:0% it's not really gonna affect me I'm 00:27:12.290 --> 00:27:14.020 align:start position:0% it's not really gonna affect me I'm gonna<00:27:12.440> exit<00:27:12.860> before<00:27:13.010> them<00:27:13.370> so<00:27:13.610> why<00:27:13.760> do<00:27:13.820> I<00:27:14.000> even 00:27:14.020 --> 00:27:14.030 align:start position:0% gonna exit before them so why do I even 00:27:14.030 --> 00:27:15.640 align:start position:0% gonna exit before them so why do I even care<00:27:14.240> about<00:27:14.480> this<00:27:14.690> five<00:27:14.960> dollars<00:27:15.410> it's<00:27:15.590> going 00:27:15.640 --> 00:27:15.650 align:start position:0% care about this five dollars it's going 00:27:15.650 --> 00:27:17.980 align:start position:0% care about this five dollars it's going to<00:27:15.890> be<00:27:15.980> stolen<00:27:16.400> I<00:27:16.580> can<00:27:17.000> exist<00:27:17.270> on<00:27:17.450> a<00:27:17.510> fractional 00:27:17.980 --> 00:27:17.990 align:start position:0% to be stolen I can exist on a fractional 00:27:17.990 --> 00:27:19.600 align:start position:0% to be stolen I can exist on a fractional reserve<00:27:18.260> as<00:27:18.440> long<00:27:18.620> as<00:27:18.740> I<00:27:18.830> get<00:27:18.890> out<00:27:19.010> first<00:27:19.310> right 00:27:19.600 --> 00:27:19.610 align:start position:0% reserve as long as I get out first right 00:27:19.610 --> 00:27:21.820 align:start position:0% reserve as long as I get out first right that's<00:27:19.910> those<00:27:20.480> kinds<00:27:20.930> of<00:27:20.990> weird<00:27:21.260> incentives 00:27:21.820 --> 00:27:21.830 align:start position:0% that's those kinds of weird incentives 00:27:21.830 --> 00:27:23.830 align:start position:0% that's those kinds of weird incentives where<00:27:21.980> you<00:27:22.160> you<00:27:22.460> share<00:27:22.790> the<00:27:23.120> burden<00:27:23.420> of<00:27:23.600> you 00:27:23.830 --> 00:27:23.840 align:start position:0% where you you share the burden of you 00:27:23.840 --> 00:27:27.430 align:start position:0% where you you share the burden of you know<00:27:24.040> a<00:27:25.040> you<00:27:25.910> know<00:27:26.000> challenging<00:27:26.840> or<00:27:27.110> whatever 00:27:27.430 --> 00:27:27.440 align:start position:0% know a you know challenging or whatever 00:27:27.440 --> 00:27:30.010 align:start position:0% know a you know challenging or whatever it<00:27:27.620> is<00:27:27.770> pretty<00:27:28.370> bad<00:27:28.610> the<00:27:29.120> better<00:27:29.360> incentives 00:27:30.010 --> 00:27:30.020 align:start position:0% it is pretty bad the better incentives 00:27:30.020 --> 00:27:32.020 align:start position:0% it is pretty bad the better incentives are<00:27:30.140> when<00:27:30.440> you<00:27:30.770> are<00:27:31.040> directly<00:27:31.430> affected<00:27:31.580> and 00:27:32.020 --> 00:27:32.030 align:start position:0% are when you are directly affected and 00:27:32.030 --> 00:27:34.000 align:start position:0% are when you are directly affected and only<00:27:32.450> you<00:27:32.600> are<00:27:32.630> directly<00:27:33.200> affected<00:27:33.350> and<00:27:33.830> so 00:27:34.000 --> 00:27:34.010 align:start position:0% only you are directly affected and so 00:27:34.010 --> 00:27:35.860 align:start position:0% only you are directly affected and so you<00:27:34.100> have<00:27:34.220> a<00:27:34.250> the<00:27:34.850> the<00:27:35.180> person<00:27:35.540> who<00:27:35.690> is 00:27:35.860 --> 00:27:35.870 align:start position:0% you have a the the person who is 00:27:35.870 --> 00:27:38.260 align:start position:0% you have a the the person who is supposed<00:27:36.110> to<00:27:36.350> act<00:27:36.680> in<00:27:37.070> response<00:27:37.220> to<00:27:37.700> this<00:27:37.850> is 00:27:38.260 --> 00:27:38.270 align:start position:0% supposed to act in response to this is 00:27:38.270 --> 00:27:41.110 align:start position:0% supposed to act in response to this is like<00:27:38.540> very<00:27:38.960> very<00:27:39.080> clear<00:27:39.650> and<00:27:40.520> I<00:27:40.640> think<00:27:40.850> bond 00:27:41.110 --> 00:27:41.120 align:start position:0% like very very clear and I think bond 00:27:41.120 --> 00:27:43.660 align:start position:0% like very very clear and I think bond sizing<00:27:41.630> is<00:27:41.780> is<00:27:42.620> a<00:27:42.680> really<00:27:43.130> important<00:27:43.550> topic 00:27:43.660 --> 00:27:43.670 align:start position:0% sizing is is a really important topic 00:27:43.670 --> 00:27:46.690 align:start position:0% sizing is is a really important topic that<00:27:43.910> I<00:27:44.360> think<00:27:44.450> even<00:27:45.320> even<00:27:45.740> us<00:27:45.950> are<00:27:46.340> not 00:27:46.690 --> 00:27:46.700 align:start position:0% that I think even even us are not 00:27:46.700 --> 00:27:48.940 align:start position:0% that I think even even us are not necessarily<00:27:47.420> experts<00:27:47.840> in<00:27:48.050> I<00:27:48.290> think<00:27:48.680> it's 00:27:48.940 --> 00:27:48.950 align:start position:0% necessarily experts in I think it's 00:27:48.950 --> 00:27:51.010 align:start position:0% necessarily experts in I think it's something<00:27:49.160> where<00:27:49.580> you<00:27:49.610> know<00:27:50.150> it<00:27:50.360> applies<00:27:50.720> to<00:27:50.750> a 00:27:51.010 --> 00:27:51.020 align:start position:0% something where you know it applies to a 00:27:51.020 --> 00:27:52.870 align:start position:0% something where you know it applies to a lot<00:27:51.320> of<00:27:51.350> smart<00:27:51.920> contracts<00:27:52.400> in<00:27:52.550> this<00:27:52.670> space<00:27:52.850> you 00:27:52.870 --> 00:27:52.880 align:start position:0% lot of smart contracts in this space you 00:27:52.880 --> 00:27:54.670 align:start position:0% lot of smart contracts in this space you know<00:27:53.180> state<00:27:53.780> channels<00:27:54.110> are<00:27:54.260> another<00:27:54.470> example 00:27:54.670 --> 00:27:54.680 align:start position:0% know state channels are another example 00:27:54.680 --> 00:27:58.000 align:start position:0% know state channels are another example of<00:27:55.100> this<00:27:55.280> where<00:27:55.730> you<00:27:56.000> know<00:27:56.090> bond<00:27:56.330> sizing<00:27:57.010> in 00:27:58.000 --> 00:27:58.010 align:start position:0% of this where you know bond sizing in 00:27:58.010 --> 00:27:59.890 align:start position:0% of this where you know bond sizing in relation<00:27:58.490> to<00:27:58.520> gas<00:27:58.700> fees<00:27:58.940> are<00:27:59.150> an<00:27:59.510> important 00:27:59.890 --> 00:27:59.900 align:start position:0% relation to gas fees are an important 00:27:59.900 --> 00:28:02.590 align:start position:0% relation to gas fees are an important topic<00:28:00.280> and<00:28:01.280> you<00:28:01.700> know<00:28:01.790> it<00:28:01.910> affects<00:28:02.270> a<00:28:02.570> whole 00:28:02.590 --> 00:28:02.600 align:start position:0% topic and you know it affects a whole 00:28:02.600 --> 00:28:03.850 align:start position:0% topic and you know it affects a whole host<00:28:02.930> of<00:28:03.050> contracts<00:28:03.500> so<00:28:03.650> if<00:28:03.710> you're 00:28:03.850 --> 00:28:03.860 align:start position:0% host of contracts so if you're 00:28:03.860 --> 00:28:06.010 align:start position:0% host of contracts so if you're interested<00:28:04.160> and/or<00:28:05.060> have<00:28:05.360> an<00:28:05.510> economics 00:28:06.010 --> 00:28:06.020 align:start position:0% interested and/or have an economics 00:28:06.020 --> 00:28:07.660 align:start position:0% interested and/or have an economics background<00:28:06.140> or<00:28:06.680> interested<00:28:07.310> in<00:28:07.370> this<00:28:07.490> topic 00:28:07.660 --> 00:28:07.670 align:start position:0% background or interested in this topic 00:28:07.670 --> 00:28:09.910 align:start position:0% background or interested in this topic it's<00:28:08.300> something<00:28:08.750> which<00:28:08.960> you<00:28:09.260> know<00:28:09.290> everybody 00:28:09.910 --> 00:28:09.920 align:start position:0% it's something which you know everybody 00:28:09.920 --> 00:28:11.500 align:start position:0% it's something which you know everybody in<00:28:10.040> the<00:28:10.130> space<00:28:10.340> would<00:28:10.520> be<00:28:10.580> very<00:28:10.910> appreciative 00:28:11.500 --> 00:28:11.510 align:start position:0% in the space would be very appreciative 00:28:11.510 --> 00:28:12.940 align:start position:0% in the space would be very appreciative if<00:28:11.690> you<00:28:11.720> know<00:28:12.110> you're<00:28:12.350> interested<00:28:12.590> in<00:28:12.860> doing 00:28:12.940 --> 00:28:12.950 align:start position:0% if you know you're interested in doing 00:28:12.950 --> 00:28:15.250 align:start position:0% if you know you're interested in doing research<00:28:13.070> in<00:28:13.580> this<00:28:13.700> yeah<00:28:14.390> the<00:28:14.900> Cohens<00:28:15.200> the 00:28:15.250 --> 00:28:15.260 align:start position:0% research in this yeah the Cohens the 00:28:15.260 --> 00:28:16.930 align:start position:0% research in this yeah the Cohens the question<00:28:15.500> I<00:28:15.590> had<00:28:15.800> is<00:28:15.980> there<00:28:16.400> is<00:28:16.550> still 00:28:16.930 --> 00:28:16.940 align:start position:0% question I had is there is still 00:28:16.940 --> 00:28:19.810 align:start position:0% question I had is there is still indirect<00:28:17.690> all<00:28:18.200> leaking<00:28:18.710> of<00:28:18.920> information<00:28:19.040> in<00:28:19.670> a 00:28:19.810 --> 00:28:19.820 align:start position:0% indirect all leaking of information in a 00:28:19.820 --> 00:28:21.840 align:start position:0% indirect all leaking of information in a submarine<00:28:20.120> case<00:28:20.360> because<00:28:21.170> it's 00:28:21.840 --> 00:28:21.850 align:start position:0% submarine case because it's 00:28:21.850 --> 00:28:23.650 align:start position:0% submarine case because it's unfortunately<00:28:22.850> due<00:28:23.090> to<00:28:23.120> the<00:28:23.360> technical 00:28:23.650 --> 00:28:23.660 align:start position:0% unfortunately due to the technical 00:28:23.660 --> 00:28:25.840 align:start position:0% unfortunately due to the technical perspective<00:28:23.960> how<00:28:24.380> its<00:28:24.560> implemented<00:28:24.920> reduce<00:28:25.730> a 00:28:25.840 --> 00:28:25.850 align:start position:0% perspective how its implemented reduce a 00:28:25.850 --> 00:28:27.250 align:start position:0% perspective how its implemented reduce a transaction<00:28:26.360> to<00:28:26.390> some<00:28:26.630> external<00:28:26.870> smart 00:28:27.250 --> 00:28:27.260 align:start position:0% transaction to some external smart 00:28:27.260 --> 00:28:28.570 align:start position:0% transaction to some external smart contract<00:28:27.590> address<00:28:27.980> of<00:28:28.070> which<00:28:28.250> you<00:28:28.400> know 00:28:28.570 --> 00:28:28.580 align:start position:0% contract address of which you know 00:28:28.580 --> 00:28:29.920 align:start position:0% contract address of which you know because<00:28:28.850> you<00:28:29.120> know<00:28:29.240> some<00:28:29.450> data<00:28:29.630> which<00:28:29.840> you 00:28:29.920 --> 00:28:29.930 align:start position:0% because you know some data which you 00:28:29.930 --> 00:28:32.190 align:start position:0% because you know some data which you need<00:28:30.050> to<00:28:30.200> publish<00:28:30.530> so<00:28:30.770> it<00:28:31.070> will<00:28:31.250> be<00:28:31.340> cheap<00:28:31.580> this 00:28:32.190 --> 00:28:32.200 align:start position:0% need to publish so it will be cheap this 00:28:32.200 --> 00:28:33.970 align:start position:0% need to publish so it will be cheap this address<00:28:33.200> what<00:28:33.380> the<00:28:33.410> contract<00:28:33.740> will<00:28:33.860> be 00:28:33.970 --> 00:28:33.980 align:start position:0% address what the contract will be 00:28:33.980 --> 00:28:35.920 align:start position:0% address what the contract will be recalculated<00:28:34.250> its<00:28:35.030> guessed<00:28:35.270> as<00:28:35.390> a<00:28:35.420> problem<00:28:35.780> if 00:28:35.920 --> 00:28:35.930 align:start position:0% recalculated its guessed as a problem if 00:28:35.930 --> 00:28:37.930 align:start position:0% recalculated its guessed as a problem if your<00:28:36.380> transaction<00:28:37.160> to<00:28:37.310> this<00:28:37.430> contract<00:28:37.760> is 00:28:37.930 --> 00:28:37.940 align:start position:0% your transaction to this contract is 00:28:37.940 --> 00:28:41.680 align:start position:0% your transaction to this contract is somewhere<00:28:38.510> some<00:28:39.160> fancy<00:28:40.160> amount<00:28:40.430> a<00:28:40.730> very<00:28:41.330> small 00:28:41.680 --> 00:28:41.690 align:start position:0% somewhere some fancy amount a very small 00:28:41.690 --> 00:28:44.650 align:start position:0% somewhere some fancy amount a very small for<00:28:41.930> example<00:28:42.380> it's<00:28:42.980> leaking<00:28:43.820> information<00:28:44.090> if 00:28:44.650 --> 00:28:44.660 align:start position:0% for example it's leaking information if 00:28:44.660 --> 00:28:49.210 align:start position:0% for example it's leaking information if it's<00:28:45.140> an<00:28:45.350> average<00:28:46.600> it<00:28:47.600> basically<00:28:48.260> just<00:28:48.410> well 00:28:49.210 --> 00:28:49.220 align:start position:0% it's an average it basically just well 00:28:49.220 --> 00:28:50.220 align:start position:0% it's an average it basically just well Rick 00:28:50.220 --> 00:28:50.230 align:start position:0% Rick 00:28:50.230 --> 00:28:52.859 align:start position:0% Rick if<00:28:50.559> it's<00:28:50.859> if<00:28:51.249> it's<00:28:51.489> more<00:28:52.269> or<00:28:52.359> less<00:28:52.419> like<00:28:52.720> an 00:28:52.859 --> 00:28:52.869 align:start position:0% if it's if it's more or less like an 00:28:52.869 --> 00:28:54.690 align:start position:0% if it's if it's more or less like an ordering<00:28:53.200> transaction<00:28:53.980> especially<00:28:54.399> in<00:28:54.460> high 00:28:54.690 --> 00:28:54.700 align:start position:0% ordering transaction especially in high 00:28:54.700 --> 00:28:56.129 align:start position:0% ordering transaction especially in high season<00:28:54.999> three<00:28:55.299> years<00:28:55.539> from<00:28:55.600> transaction 00:28:56.129 --> 00:28:56.139 align:start position:0% season three years from transaction 00:28:56.139 --> 00:28:58.789 align:start position:0% season three years from transaction amount<00:28:56.350> for<00:28:56.559> example<00:28:56.889> hi<00:28:57.100> it<00:28:57.639> most<00:28:58.059> likely 00:28:58.789 --> 00:28:58.799 align:start position:0% amount for example hi it most likely 00:28:58.799 --> 00:29:01.529 align:start position:0% amount for example hi it most likely means<00:28:59.799> you<00:29:00.129> need<00:29:00.249> to<00:29:00.489> have<00:29:00.700> the<00:29:00.879> higher<00:29:01.179> amount 00:29:01.529 --> 00:29:01.539 align:start position:0% means you need to have the higher amount 00:29:01.539 --> 00:29:03.779 align:start position:0% means you need to have the higher amount even<00:29:01.869> starts<00:29:02.139> a<00:29:02.230> challenge<00:29:02.590> and<00:29:02.799> it's<00:29:03.009> begins 00:29:03.779 --> 00:29:03.789 align:start position:0% even starts a challenge and it's begins 00:29:03.789 --> 00:29:05.009 align:start position:0% even starts a challenge and it's begins like<00:29:03.970> another<00:29:04.269> probability<00:29:04.690> challenger 00:29:05.009 --> 00:29:05.019 align:start position:0% like another probability challenger 00:29:05.019 --> 00:29:07.289 align:start position:0% like another probability challenger should<00:29:05.200> have<00:29:05.409> at<00:29:06.220> the<00:29:06.340> worst<00:29:06.519> case<00:29:06.609> more 00:29:07.289 --> 00:29:07.299 align:start position:0% should have at the worst case more 00:29:07.299 --> 00:29:09.419 align:start position:0% should have at the worst case more suddenly<00:29:07.929> it<00:29:07.989> would<00:29:08.049> be<00:29:08.200> just<00:29:08.470> necessary<00:29:09.009> to 00:29:09.419 --> 00:29:09.429 align:start position:0% suddenly it would be just necessary to 00:29:09.429 --> 00:29:12.450 align:start position:0% suddenly it would be just necessary to just<00:29:09.639> may<00:29:10.570> be<00:29:10.629> allowed<00:29:10.899> to<00:29:10.960> front<00:29:11.289> run<00:29:11.379> you<00:29:11.649> and 00:29:12.450 --> 00:29:12.460 align:start position:0% just may be allowed to front run you and 00:29:12.460 --> 00:29:14.789 align:start position:0% just may be allowed to front run you and and<00:29:12.850> just<00:29:13.179> indirect<00:29:13.659> kind<00:29:14.080> of<00:29:14.169> indirect<00:29:14.559> loss 00:29:14.789 --> 00:29:14.799 align:start position:0% and just indirect kind of indirect loss 00:29:14.799 --> 00:29:16.769 align:start position:0% and just indirect kind of indirect loss and<00:29:15.070> as<00:29:15.460> a<00:29:15.489> side<00:29:15.759> comment<00:29:15.999> I<00:29:16.269> think<00:29:16.570> you<00:29:16.690> know 00:29:16.769 --> 00:29:16.779 align:start position:0% and as a side comment I think you know 00:29:16.779 --> 00:29:18.989 align:start position:0% and as a side comment I think you know the<00:29:17.109> the<00:29:17.320> reason<00:29:17.710> why<00:29:17.919> you<00:29:17.980> know<00:29:18.429> we<00:29:18.609> do<00:29:18.789> need<00:29:18.940> a 00:29:18.989 --> 00:29:18.999 align:start position:0% the the reason why you know we do need a 00:29:18.999 --> 00:29:21.389 align:start position:0% the the reason why you know we do need a lot<00:29:19.179> of<00:29:19.239> people<00:29:19.570> researching<00:29:20.559> plasma<00:29:21.009> and<00:29:21.220> why 00:29:21.389 --> 00:29:21.399 align:start position:0% lot of people researching plasma and why 00:29:21.399 --> 00:29:23.399 align:start position:0% lot of people researching plasma and why you<00:29:21.460> know<00:29:21.789> a<00:29:21.970> lot<00:29:22.359> of<00:29:22.450> people<00:29:22.749> are<00:29:22.869> making 00:29:23.399 --> 00:29:23.409 align:start position:0% you know a lot of people are making 00:29:23.409 --> 00:29:25.109 align:start position:0% you know a lot of people are making significant<00:29:24.100> contributions<00:29:24.669> is<00:29:24.820> you<00:29:24.909> need<00:29:25.090> a 00:29:25.109 --> 00:29:25.119 align:start position:0% significant contributions is you need a 00:29:25.119 --> 00:29:27.359 align:start position:0% significant contributions is you need a lot<00:29:25.299> of<00:29:25.359> ice<00:29:25.600> on<00:29:25.840> this<00:29:25.989> for<00:29:26.799> example<00:29:27.009> one<00:29:27.340> thing 00:29:27.359 --> 00:29:27.369 align:start position:0% lot of ice on this for example one thing 00:29:27.369 --> 00:29:29.159 align:start position:0% lot of ice on this for example one thing like<00:29:27.700> I<00:29:27.879> just<00:29:28.119> realized<00:29:28.720> it's<00:29:28.869> just<00:29:28.929> now 00:29:29.159 --> 00:29:29.169 align:start position:0% like I just realized it's just now 00:29:29.169 --> 00:29:30.899 align:start position:0% like I just realized it's just now sitting<00:29:29.470> here<00:29:29.499> is<00:29:29.710> you<00:29:30.159> know<00:29:30.249> attack<00:29:30.549> vector 00:29:30.899 --> 00:29:30.909 align:start position:0% sitting here is you know attack vector 00:29:30.909 --> 00:29:32.310 align:start position:0% sitting here is you know attack vector because<00:29:31.450> like<00:29:31.629> when<00:29:31.899> you're<00:29:32.019> talking<00:29:32.289> about 00:29:32.310 --> 00:29:32.320 align:start position:0% because like when you're talking about 00:29:32.320 --> 00:29:34.109 align:start position:0% because like when you're talking about game<00:29:32.590> theory<00:29:32.919> you<00:29:33.070> need<00:29:33.190> you<00:29:33.460> need<00:29:33.609> a<00:29:33.759> lot<00:29:33.999> of 00:29:34.109 --> 00:29:34.119 align:start position:0% game theory you need you need a lot of 00:29:34.119 --> 00:29:35.279 align:start position:0% game theory you need you need a lot of eyes<00:29:34.239> on<00:29:34.450> this<00:29:34.539> to<00:29:34.690> understand<00:29:35.109> the<00:29:35.169> game 00:29:35.279 --> 00:29:35.289 align:start position:0% eyes on this to understand the game 00:29:35.289 --> 00:29:36.989 align:start position:0% eyes on this to understand the game theory<00:29:35.529> an<00:29:35.739> attack<00:29:36.190> vector<00:29:36.220> on<00:29:36.580> the<00:29:36.669> submarine 00:29:36.989 --> 00:29:36.999 align:start position:0% theory an attack vector on the submarine 00:29:36.999 --> 00:29:39.779 align:start position:0% theory an attack vector on the submarine is<00:29:37.590> construction<00:29:38.590> that<00:29:38.980> I<00:29:39.009> was<00:29:39.369> just<00:29:39.519> thinking 00:29:39.779 --> 00:29:39.789 align:start position:0% is construction that I was just thinking 00:29:39.789 --> 00:29:41.340 align:start position:0% is construction that I was just thinking of<00:29:39.940> and<00:29:40.119> correct<00:29:40.419> me<00:29:40.509> if<00:29:40.600> I'm<00:29:40.690> wrong<00:29:40.720> this<00:29:41.019> is 00:29:41.340 --> 00:29:41.350 align:start position:0% of and correct me if I'm wrong this is 00:29:41.350 --> 00:29:44.190 align:start position:0% of and correct me if I'm wrong this is viable<00:29:41.739> is<00:29:42.070> you<00:29:42.549> know<00:29:42.669> I<00:29:42.879> always<00:29:43.359> if<00:29:43.899> I'm<00:29:44.049> an 00:29:44.190 --> 00:29:44.200 align:start position:0% viable is you know I always if I'm an 00:29:44.200 --> 00:29:45.629 align:start position:0% viable is you know I always if I'm an attacker<00:29:44.289> I'm<00:29:44.679> always<00:29:44.950> going<00:29:45.190> to<00:29:45.249> publish<00:29:45.609> a 00:29:45.629 --> 00:29:45.639 align:start position:0% attacker I'm always going to publish a 00:29:45.639 --> 00:29:52.220 align:start position:0% attacker I'm always going to publish a submarine<00:29:46.379> proof<00:29:48.989> yeah<00:29:49.989> it<00:29:50.230> would<00:29:50.669> like<00:29:51.669> you 00:29:52.220 --> 00:29:52.230 align:start position:0% submarine proof yeah it would like you 00:29:52.230 --> 00:29:55.289 align:start position:0% submarine proof yeah it would like you steal<00:29:53.230> the<00:29:53.470> submarine<00:29:53.889> proofs<00:29:54.220> as<00:29:54.879> you 00:29:55.289 --> 00:29:55.299 align:start position:0% steal the submarine proofs as you 00:29:55.299 --> 00:29:57.210 align:start position:0% steal the submarine proofs as you attempt<00:29:55.570> to<00:29:55.629> steal<00:29:55.869> the<00:29:55.929> penalty<00:29:56.440> by<00:29:56.830> always 00:29:57.210 --> 00:29:57.220 align:start position:0% attempt to steal the penalty by always 00:29:57.220 --> 00:29:58.499 align:start position:0% attempt to steal the penalty by always publishing<00:29:57.669> a<00:29:57.730> submarine<00:29:58.090> proof 00:29:58.499 --> 00:29:58.509 align:start position:0% publishing a submarine proof 00:29:58.509 --> 00:30:00.509 align:start position:0% publishing a submarine proof I<00:29:58.539> don't<00:29:59.049> reveal<00:29:59.350> it<00:29:59.559> but<00:29:59.919> when<00:30:00.070> someone<00:30:00.369> else 00:30:00.509 --> 00:30:00.519 align:start position:0% I don't reveal it but when someone else 00:30:00.519 --> 00:30:02.279 align:start position:0% I don't reveal it but when someone else reveals<00:30:00.850> it<00:30:01.059> I<00:30:01.179> also<00:30:01.450> reveal<00:30:01.929> my<00:30:02.080> submarine 00:30:02.279 --> 00:30:02.289 align:start position:0% reveals it I also reveal my submarine 00:30:02.289 --> 00:30:04.979 align:start position:0% reveals it I also reveal my submarine proof<00:30:02.710> the<00:30:03.340> submarine<00:30:03.759> proof<00:30:03.999> has<00:30:04.239> to<00:30:04.419> commit 00:30:04.979 --> 00:30:04.989 align:start position:0% proof the submarine proof has to commit 00:30:04.989 --> 00:30:07.229 align:start position:0% proof the submarine proof has to commit to<00:30:05.320> the<00:30:05.559> challenge<00:30:05.950> of<00:30:06.039> yeah<00:30:06.220> yeah<00:30:06.369> yeah<00:30:06.759> so 00:30:07.229 --> 00:30:07.239 align:start position:0% to the challenge of yeah yeah yeah so 00:30:07.239 --> 00:30:10.229 align:start position:0% to the challenge of yeah yeah yeah so I'm<00:30:07.450> committing<00:30:07.989> to<00:30:08.499> my<00:30:09.039> own<00:30:09.249> my<00:30:09.700> own<00:30:09.850> my<00:30:10.210> own 00:30:10.229 --> 00:30:10.239 align:start position:0% I'm committing to my own my own my own 00:30:10.239 --> 00:30:17.159 align:start position:0% I'm committing to my own my own my own invalid<00:30:11.019> exit<00:30:11.320> I<00:30:15.629> mean<00:30:16.629> you<00:30:16.809> start<00:30:17.049> an 00:30:17.159 --> 00:30:17.169 align:start position:0% invalid exit I mean you start an 00:30:17.169 --> 00:30:19.169 align:start position:0% invalid exit I mean you start an involute<00:30:17.529> exit<00:30:17.859> and<00:30:18.009> yourself<00:30:18.609> prevented 00:30:19.169 --> 00:30:19.179 align:start position:0% involute exit and yourself prevented 00:30:19.179 --> 00:30:22.619 align:start position:0% involute exit and yourself prevented yeah<00:30:19.960> so<00:30:20.499> basically<00:30:20.649> like<00:30:21.220> I<00:30:21.460> I<00:30:21.639> must<00:30:22.210> publish 00:30:22.619 --> 00:30:22.629 align:start position:0% yeah so basically like I I must publish 00:30:22.629 --> 00:30:25.859 align:start position:0% yeah so basically like I I must publish an<00:30:22.779> invalid<00:30:23.230> exit<00:30:23.559> I<00:30:23.850> also<00:30:24.850> publish<00:30:25.179> a<00:30:25.330> hash<00:30:25.629> of 00:30:25.859 --> 00:30:25.869 align:start position:0% an invalid exit I also publish a hash of 00:30:25.869 --> 00:30:30.210 align:start position:0% an invalid exit I also publish a hash of the<00:30:25.960> proof<00:30:26.259> of<00:30:26.409> the<00:30:26.529> dispute<00:30:28.919> that's<00:30:29.919> useful 00:30:30.210 --> 00:30:30.220 align:start position:0% the proof of the dispute that's useful 00:30:30.220 --> 00:30:31.889 align:start position:0% the proof of the dispute that's useful because<00:30:30.489> when<00:30:30.820> someone<00:30:31.239> else<00:30:31.359> publishes<00:30:31.869> a 00:30:31.889 --> 00:30:31.899 align:start position:0% because when someone else publishes a 00:30:31.899 --> 00:30:34.379 align:start position:0% because when someone else publishes a penalty<00:30:32.320> I<00:30:32.529> can<00:30:33.369> claim<00:30:33.580> that<00:30:33.759> I<00:30:33.820> did<00:30:34.029> it<00:30:34.119> before 00:30:34.379 --> 00:30:34.389 align:start position:0% penalty I can claim that I did it before 00:30:34.389 --> 00:30:37.919 align:start position:0% penalty I can claim that I did it before them<00:30:34.919> the<00:30:35.919> submarine<00:30:36.309> proof<00:30:36.549> it<00:30:36.669> is<00:30:36.820> it<00:30:37.720> is 00:30:37.919 --> 00:30:37.929 align:start position:0% them the submarine proof it is it is 00:30:37.929 --> 00:30:41.549 align:start position:0% them the submarine proof it is it is very<00:30:38.259> well<00:30:38.470> linked<00:30:38.769> to<00:30:39.039> you<00:30:39.190> I<00:30:39.460> think<00:30:40.169> yeah<00:30:41.169> so 00:30:41.549 --> 00:30:41.559 align:start position:0% very well linked to you I think yeah so 00:30:41.559 --> 00:30:44.430 align:start position:0% very well linked to you I think yeah so so<00:30:42.129> what<00:30:42.759> I'm<00:30:42.850> saying<00:30:43.119> is<00:30:43.269> that<00:30:43.299> like<00:30:43.720> anyone 00:30:44.430 --> 00:30:44.440 align:start position:0% so what I'm saying is that like anyone 00:30:44.440 --> 00:30:45.690 align:start position:0% so what I'm saying is that like anyone in<00:30:44.559> the<00:30:44.649> audience<00:30:44.769> can<00:30:45.129> come<00:30:45.369> up<00:30:45.519> with 00:30:45.690 --> 00:30:45.700 align:start position:0% in the audience can come up with 00:30:45.700 --> 00:30:47.310 align:start position:0% in the audience can come up with interesting<00:30:45.940> constructions<00:30:46.779> and<00:30:46.929> disputes 00:30:47.310 --> 00:30:47.320 align:start position:0% interesting constructions and disputes 00:30:47.320 --> 00:30:49.799 align:start position:0% interesting constructions and disputes on<00:30:47.639> whatever<00:30:48.639> mechanism<00:30:49.389> that<00:30:49.539> we're<00:30:49.720> all 00:30:49.799 --> 00:30:49.809 align:start position:0% on whatever mechanism that we're all 00:30:49.809 --> 00:30:52.080 align:start position:0% on whatever mechanism that we're all coming<00:30:50.139> up<00:30:50.230> with<00:30:50.470> and<00:30:50.769> it's<00:30:51.549> something<00:30:51.820> that's 00:30:52.080 --> 00:30:52.090 align:start position:0% coming up with and it's something that's 00:30:52.090 --> 00:30:53.879 align:start position:0% coming up with and it's something that's very<00:30:52.149> very<00:30:52.570> important<00:30:53.049> to<00:30:53.169> do<00:30:53.320> and<00:30:53.499> I'm<00:30:53.710> not 00:30:53.879 --> 00:30:53.889 align:start position:0% very very important to do and I'm not 00:30:53.889 --> 00:30:56.009 align:start position:0% very very important to do and I'm not sure<00:30:54.129> that<00:30:54.249> this<00:30:54.369> actually<00:30:54.820> works<00:30:55.029> but<00:30:55.840> you 00:30:56.009 --> 00:30:56.019 align:start position:0% sure that this actually works but you 00:30:56.019 --> 00:30:57.779 align:start position:0% sure that this actually works but you know<00:30:56.109> is<00:30:56.230> an<00:30:56.350> example<00:30:56.679> of<00:30:57.039> you<00:30:57.399> know<00:30:57.489> something 00:30:57.779 --> 00:30:57.789 align:start position:0% know is an example of you know something 00:30:57.789 --> 00:31:00.839 align:start position:0% know is an example of you know something which<00:30:58.119> you<00:30:58.330> know<00:30:58.619> why<00:30:59.619> why<00:31:00.129> the<00:31:00.190> community 00:31:00.839 --> 00:31:00.849 align:start position:0% which you know why why the community 00:31:00.849 --> 00:31:02.279 align:start position:0% which you know why why the community when<00:31:01.330> it<00:31:01.359> comes<00:31:01.570> to<00:31:01.690> smart<00:31:01.899> contract 00:31:02.279 --> 00:31:02.289 align:start position:0% when it comes to smart contract 00:31:02.289 --> 00:31:03.389 align:start position:0% when it comes to smart contract development<00:31:02.799> is 00:31:03.389 --> 00:31:03.399 align:start position:0% development is 00:31:03.399 --> 00:31:05.009 align:start position:0% development is really<00:31:03.639> really<00:31:03.849> important<00:31:04.389> to<00:31:04.479> you<00:31:04.719> know<00:31:04.839> get 00:31:05.009 --> 00:31:05.019 align:start position:0% really really important to you know get 00:31:05.019 --> 00:31:06.539 align:start position:0% really really important to you know get everyone<00:31:05.379> involved<00:31:05.649> and<00:31:05.950> have<00:31:06.070> a<00:31:06.099> lot<00:31:06.309> of<00:31:06.339> ice 00:31:06.539 --> 00:31:06.549 align:start position:0% everyone involved and have a lot of ice 00:31:06.549 --> 00:31:15.379 align:start position:0% everyone involved and have a lot of ice look<00:31:06.759> at<00:31:06.879> this<00:31:07.089> oh<00:31:09.809> yeah<00:31:10.839> QA<00:31:11.109> would<00:31:11.379> be<00:31:11.469> fun 00:31:15.379 --> 00:31:15.389 align:start position:0% 00:31:15.389 --> 00:31:26.129 align:start position:0% Kunis<00:31:23.879> our<00:31:24.879> guys<00:31:25.089> skill<00:31:25.509> Beauty<00:31:25.809> love<00:31:25.960> hearing 00:31:26.129 --> 00:31:26.139 align:start position:0% Kunis our guys skill Beauty love hearing 00:31:26.139 --> 00:31:27.749 align:start position:0% Kunis our guys skill Beauty love hearing with<00:31:26.379> thousand<00:31:26.889> TPS<00:31:27.249> how<00:31:27.429> will<00:31:27.580> it<00:31:27.639> affect 00:31:27.749 --> 00:31:27.759 align:start position:0% with thousand TPS how will it affect 00:31:27.759 --> 00:31:35.099 align:start position:0% with thousand TPS how will it affect plasma<00:31:28.419> negatively<00:31:28.960> positively<00:31:33.839> if<00:31:34.839> layer 00:31:35.099 --> 00:31:35.109 align:start position:0% plasma negatively positively if layer 00:31:35.109 --> 00:31:36.719 align:start position:0% plasma negatively positively if layer one<00:31:35.320> scales<00:31:35.679> will<00:31:36.009> it<00:31:36.159> make<00:31:36.309> layer<00:31:36.519> two 00:31:36.719 --> 00:31:36.729 align:start position:0% one scales will it make layer two 00:31:36.729 --> 00:31:42.719 align:start position:0% one scales will it make layer two obsolete<00:31:37.179> is<00:31:37.509> the<00:31:37.869> question<00:31:41.460> so<00:31:42.460> my 00:31:42.719 --> 00:31:42.729 align:start position:0% obsolete is the question so my 00:31:42.729 --> 00:31:44.639 align:start position:0% obsolete is the question so my understanding<00:31:42.879> is<00:31:43.419> that<00:31:43.599> anytime<00:31:44.229> that<00:31:44.409> you 00:31:44.639 --> 00:31:44.649 align:start position:0% understanding is that anytime that you 00:31:44.649 --> 00:31:46.049 align:start position:0% understanding is that anytime that you gain<00:31:44.799> committee<00:31:45.129> placed<00:31:45.399> data<00:31:45.609> to<00:31:45.789> the<00:31:45.879> chain 00:31:46.049 --> 00:31:46.059 align:start position:0% gain committee placed data to the chain 00:31:46.059 --> 00:31:48.419 align:start position:0% gain committee placed data to the chain you<00:31:46.210> do<00:31:46.330> it<00:31:46.450> if<00:31:46.749> you<00:31:47.139> can<00:31:47.289> do<00:31:47.379> it<00:31:47.409> that's<00:31:47.950> like 00:31:48.419 --> 00:31:48.429 align:start position:0% you do it if you can do it that's like 00:31:48.429 --> 00:31:50.789 align:start position:0% you do it if you can do it that's like pretty<00:31:48.789> obvious<00:31:49.210> so<00:31:49.289> there<00:31:50.289> is<00:31:50.379> always<00:31:50.679> the 00:31:50.789 --> 00:31:50.799 align:start position:0% pretty obvious so there is always the 00:31:50.799 --> 00:31:54.119 align:start position:0% pretty obvious so there is always the need<00:31:50.919> for<00:31:50.979> layer<00:31:51.279> two<00:31:51.519> yeah<00:31:52.419> I<00:31:52.889> think<00:31:53.889> that 00:31:54.119 --> 00:31:54.129 align:start position:0% need for layer two yeah I think that 00:31:54.129 --> 00:31:55.469 align:start position:0% need for layer two yeah I think that they're<00:31:54.249> going<00:31:54.489> to<00:31:54.609> be<00:31:54.700> different<00:31:54.999> properties 00:31:55.469 --> 00:31:55.479 align:start position:0% they're going to be different properties 00:31:55.479 --> 00:31:57.719 align:start position:0% they're going to be different properties of<00:31:55.749> the<00:31:56.080> main<00:31:56.259> chain<00:31:56.559> and<00:31:56.889> of<00:31:57.099> plasma<00:31:57.489> chains 00:31:57.719 --> 00:31:57.729 align:start position:0% of the main chain and of plasma chains 00:31:57.729 --> 00:31:59.039 align:start position:0% of the main chain and of plasma chains plasma<00:31:58.089> chains<00:31:58.269> are<00:31:58.419> just<00:31:58.570> going<00:31:58.690> to<00:31:58.779> have 00:31:59.039 --> 00:31:59.049 align:start position:0% plasma chains are just going to have 00:31:59.049 --> 00:32:02.039 align:start position:0% plasma chains are just going to have like<00:31:59.349> you<00:31:59.889> know<00:31:59.919> maybe<00:32:00.759> it's<00:32:00.999> tons<00:32:01.659> of 00:32:02.039 --> 00:32:02.049 align:start position:0% like you know maybe it's tons of 00:32:02.049 --> 00:32:04.259 align:start position:0% like you know maybe it's tons of scalability<00:32:02.799> and<00:32:03.009> you<00:32:03.369> know<00:32:03.489> exchange<00:32:03.999> kind 00:32:04.259 --> 00:32:04.269 align:start position:0% scalability and you know exchange kind 00:32:04.269 --> 00:32:07.109 align:start position:0% scalability and you know exchange kind of<00:32:04.330> built<00:32:04.539> in<00:32:04.719> and<00:32:04.960> maybe<00:32:05.109> fast<00:32:06.029> finality<00:32:07.029> or 00:32:07.109 --> 00:32:07.119 align:start position:0% of built in and maybe fast finality or 00:32:07.119 --> 00:32:09.299 align:start position:0% of built in and maybe fast finality or something<00:32:07.450> like<00:32:07.599> this<00:32:07.749> and<00:32:08.589> something<00:32:09.159> that<00:32:09.279> I 00:32:09.299 --> 00:32:09.309 align:start position:0% something like this and something that I 00:32:09.309 --> 00:32:10.859 align:start position:0% something like this and something that I was<00:32:09.429> thinking<00:32:09.549> about<00:32:09.700> it's<00:32:10.210> like<00:32:10.330> okay<00:32:10.629> does 00:32:10.859 --> 00:32:10.869 align:start position:0% was thinking about it's like okay does 00:32:10.869 --> 00:32:14.009 align:start position:0% was thinking about it's like okay does does<00:32:11.349> plasma<00:32:11.619> work<00:32:12.429> in<00:32:12.639> a<00:32:12.759> sharded<00:32:13.330> context<00:32:13.869> I 00:32:14.009 --> 00:32:14.019 align:start position:0% does plasma work in a sharded context I 00:32:14.019 --> 00:32:15.450 align:start position:0% does plasma work in a sharded context I was<00:32:14.259> like<00:32:14.379> oh<00:32:14.499> well<00:32:14.830> there's<00:32:15.099> actually<00:32:15.429> a 00:32:15.450 --> 00:32:15.460 align:start position:0% was like oh well there's actually a 00:32:15.460 --> 00:32:18.329 align:start position:0% was like oh well there's actually a really<00:32:15.879> simple<00:32:16.589> construction<00:32:17.589> which<00:32:18.009> allows 00:32:18.329 --> 00:32:18.339 align:start position:0% really simple construction which allows 00:32:18.339 --> 00:32:20.190 align:start position:0% really simple construction which allows you<00:32:18.549> to<00:32:18.669> say<00:32:18.849> okay<00:32:19.210> I'm<00:32:19.359> going<00:32:19.629> to<00:32:19.749> take<00:32:20.019> one 00:32:20.190 --> 00:32:20.200 align:start position:0% you to say okay I'm going to take one 00:32:20.200 --> 00:32:22.049 align:start position:0% you to say okay I'm going to take one plasma<00:32:20.619> chain<00:32:20.830> and<00:32:21.070> I'm<00:32:21.309> gonna<00:32:21.489> hook<00:32:21.669> it<00:32:21.789> up<00:32:21.879> to 00:32:22.049 --> 00:32:22.059 align:start position:0% plasma chain and I'm gonna hook it up to 00:32:22.059 --> 00:32:25.109 align:start position:0% plasma chain and I'm gonna hook it up to ten<00:32:22.359> shard<00:32:23.080> chains<00:32:23.409> and<00:32:23.710> then<00:32:24.099> all<00:32:24.399> ten<00:32:24.759> shard 00:32:25.109 --> 00:32:25.119 align:start position:0% ten shard chains and then all ten shard 00:32:25.119 --> 00:32:28.529 align:start position:0% ten shard chains and then all ten shard chains<00:32:25.419> will<00:32:25.989> be<00:32:26.109> able<00:32:26.289> to<00:32:26.529> deposit<00:32:27.539> transit 00:32:28.529 --> 00:32:28.539 align:start position:0% chains will be able to deposit transit 00:32:28.539 --> 00:32:31.109 align:start position:0% chains will be able to deposit transit assets<00:32:28.960> into<00:32:29.529> the<00:32:29.739> single<00:32:30.190> massive<00:32:30.489> plasma 00:32:31.109 --> 00:32:31.119 align:start position:0% assets into the single massive plasma 00:32:31.119 --> 00:32:32.909 align:start position:0% assets into the single massive plasma chain<00:32:31.330> and<00:32:31.539> so<00:32:31.809> then<00:32:31.960> everyone's<00:32:32.379> able<00:32:32.529> to<00:32:32.799> do 00:32:32.909 --> 00:32:32.919 align:start position:0% chain and so then everyone's able to do 00:32:32.919 --> 00:32:35.789 align:start position:0% chain and so then everyone's able to do kind<00:32:33.099> of<00:32:33.219> like<00:32:33.279> native<00:32:33.820> atomic<00:32:34.239> swaps<00:32:34.799> across 00:32:35.789 --> 00:32:35.799 align:start position:0% kind of like native atomic swaps across 00:32:35.799 --> 00:32:37.859 align:start position:0% kind of like native atomic swaps across these<00:32:36.099> different<00:32:36.309> charts<00:32:36.879> so<00:32:37.330> like<00:32:37.539> like<00:32:37.659> how 00:32:37.859 --> 00:32:37.869 align:start position:0% these different charts so like like how 00:32:37.869 --> 00:32:39.690 align:start position:0% these different charts so like like how does<00:32:37.929> it<00:32:38.109> work<00:32:38.409> it's<00:32:38.830> very<00:32:39.190> simple<00:32:39.489> it's<00:32:39.669> very 00:32:39.690 --> 00:32:39.700 align:start position:0% does it work it's very simple it's very 00:32:39.700 --> 00:32:42.060 align:start position:0% does it work it's very simple it's very simple<00:32:40.089> I<00:32:40.239> promise<00:32:40.659> it's<00:32:41.320> it<00:32:41.679> sounds<00:32:41.979> like 00:32:42.060 --> 00:32:42.070 align:start position:0% simple I promise it's it sounds like 00:32:42.070 --> 00:32:46.950 align:start position:0% simple I promise it's it sounds like dream<00:32:43.029> but<00:32:43.210> I'm<00:32:43.419> not<00:32:43.570> sure<00:32:43.749> how<00:32:45.359> one<00:32:46.359> contract 00:32:46.950 --> 00:32:46.960 align:start position:0% dream but I'm not sure how one contract 00:32:46.960 --> 00:32:51.029 align:start position:0% dream but I'm not sure how one contract in<00:32:47.169> each<00:32:47.289> shard<00:32:49.080> scene<00:32:50.080> watches<00:32:50.499> multiple 00:32:51.029 --> 00:32:51.039 align:start position:0% in each shard scene watches multiple 00:32:51.039 --> 00:32:53.299 align:start position:0% in each shard scene watches multiple shots<00:32:51.279> boom<00:32:51.789> I'm<00:32:52.239> blamed<00:32:52.450> for<00:32:52.599> this<00:32:52.809> it<00:32:52.960> sounds 00:32:53.299 --> 00:32:53.309 align:start position:0% shots boom I'm blamed for this it sounds 00:32:53.309 --> 00:33:00.589 align:start position:0% shots boom I'm blamed for this it sounds I<00:32:54.309> mean<00:32:55.239> well<00:32:55.419> first<00:32:55.450> we<00:32:55.779> need<00:32:55.809> a<00:32:55.960> 32-point<00:32:56.649> oh 00:33:00.589 --> 00:33:00.599 align:start position:0% 00:33:00.599 --> 00:33:04.279 align:start position:0% yeah<00:33:01.599> you<00:33:01.809> know<00:33:02.070> right<00:33:03.070> well<00:33:03.700> the<00:33:03.909> thing<00:33:04.119> is 00:33:04.279 --> 00:33:04.289 align:start position:0% yeah you know right well the thing is 00:33:04.289 --> 00:33:06.959 align:start position:0% yeah you know right well the thing is it's<00:33:05.289> scary<00:33:05.649> to<00:33:05.950> research<00:33:06.279> something<00:33:06.549> and 00:33:06.959 --> 00:33:06.969 align:start position:0% it's scary to research something and 00:33:06.969 --> 00:33:09.479 align:start position:0% it's scary to research something and then<00:33:07.539> be<00:33:07.659> like<00:33:07.839> oh<00:33:08.049> this<00:33:08.379> new<00:33:08.589> technology<00:33:09.399> is 00:33:09.479 --> 00:33:09.489 align:start position:0% then be like oh this new technology is 00:33:09.489 --> 00:33:11.249 align:start position:0% then be like oh this new technology is coming<00:33:09.639> out<00:33:09.879> does<00:33:10.659> that<00:33:10.839> just<00:33:11.049> totally 00:33:11.249 --> 00:33:11.259 align:start position:0% coming out does that just totally 00:33:11.259 --> 00:33:13.829 align:start position:0% coming out does that just totally obsolete<00:33:11.559> all<00:33:12.070> of<00:33:12.249> what<00:33:12.369> I'm<00:33:12.460> doing<00:33:12.489> Jeff<00:33:13.509> I'm 00:33:13.829 --> 00:33:13.839 align:start position:0% obsolete all of what I'm doing Jeff I'm 00:33:13.839 --> 00:33:19.930 align:start position:0% obsolete all of what I'm doing Jeff I'm so<00:33:14.079> curious 00:33:19.930 --> 00:33:19.940 align:start position:0% 00:33:19.940 --> 00:33:22.460 align:start position:0% it<00:33:20.940> doesn't<00:33:21.240> matter<00:33:21.330> so<00:33:21.540> much<00:33:21.570> about<00:33:21.930> access 00:33:22.460 --> 00:33:22.470 align:start position:0% it doesn't matter so much about access 00:33:22.470 --> 00:33:24.680 align:start position:0% it doesn't matter so much about access to<00:33:22.710> plasma<00:33:23.250> from<00:33:23.430> chars<00:33:23.700> because<00:33:24.030> for<00:33:24.510> at 00:33:24.680 --> 00:33:24.690 align:start position:0% to plasma from chars because for at 00:33:24.690 --> 00:33:26.210 align:start position:0% to plasma from chars because for at least<00:33:24.870> four<00:33:25.020> fungible<00:33:25.320> token<00:33:25.650> flows<00:33:25.860> because 00:33:26.210 --> 00:33:26.220 align:start position:0% least four fungible token flows because 00:33:26.220 --> 00:33:28.730 align:start position:0% least four fungible token flows because you<00:33:26.430> can<00:33:26.550> just<00:33:26.730> instant<00:33:27.210> swap<00:33:27.480> in<00:33:28.350> channels 00:33:28.730 --> 00:33:28.740 align:start position:0% you can just instant swap in channels 00:33:28.740 --> 00:33:31.070 align:start position:0% you can just instant swap in channels between<00:33:29.010> a<00:33:29.760> channel<00:33:30.360> literally<00:33:30.750> anywhere<00:33:30.990> in 00:33:31.070 --> 00:33:31.080 align:start position:0% between a channel literally anywhere in 00:33:31.080 --> 00:33:32.390 align:start position:0% between a channel literally anywhere in the<00:33:31.140> ecosystem<00:33:31.650> and<00:33:31.710> a<00:33:31.770> channel<00:33:32.040> and<00:33:32.130> plasma 00:33:32.390 --> 00:33:32.400 align:start position:0% the ecosystem and a channel and plasma 00:33:32.400 --> 00:33:34.400 align:start position:0% the ecosystem and a channel and plasma anyways<00:33:32.670> so<00:33:33.120> the<00:33:33.450> only<00:33:33.630> thing<00:33:33.990> you<00:33:34.110> need<00:33:34.260> the 00:33:34.400 --> 00:33:34.410 align:start position:0% anyways so the only thing you need the 00:33:34.410 --> 00:33:35.900 align:start position:0% anyways so the only thing you need the connection<00:33:34.830> between<00:33:35.010> plasma<00:33:35.490> and<00:33:35.700> the<00:33:35.760> main 00:33:35.900 --> 00:33:35.910 align:start position:0% connection between plasma and the main 00:33:35.910 --> 00:33:38.050 align:start position:0% connection between plasma and the main chain<00:33:36.150> for<00:33:36.420> in<00:33:36.570> terms<00:33:36.690> of<00:33:36.900> fungible<00:33:37.350> tokens<00:33:37.740> is 00:33:38.050 --> 00:33:38.060 align:start position:0% chain for in terms of fungible tokens is 00:33:38.060 --> 00:33:40.430 align:start position:0% chain for in terms of fungible tokens is managing<00:33:39.060> net<00:33:39.240> capital<00:33:39.450> flows<00:33:39.840> in<00:33:40.050> arbitrage 00:33:40.430 --> 00:33:40.440 align:start position:0% managing net capital flows in arbitrage 00:33:40.440 --> 00:33:42.380 align:start position:0% managing net capital flows in arbitrage we<00:33:40.740> should<00:33:40.920> happen<00:33:41.190> like<00:33:41.340> just<00:33:41.550> every<00:33:42.120> once<00:33:42.300> in 00:33:42.380 --> 00:33:42.390 align:start position:0% we should happen like just every once in 00:33:42.390 --> 00:33:43.610 align:start position:0% we should happen like just every once in a<00:33:42.450> while<00:33:42.570> it<00:33:42.780> doesn't<00:33:43.020> even<00:33:43.170> matter<00:33:43.380> like 00:33:43.610 --> 00:33:43.620 align:start position:0% a while it doesn't even matter like 00:33:43.620 --> 00:33:45.950 align:start position:0% a while it doesn't even matter like people<00:33:43.920> people<00:33:44.280> don't<00:33:44.340> even<00:33:44.460> care<00:33:44.700> yes<00:33:45.690> and<00:33:45.930> a 00:33:45.950 --> 00:33:45.960 align:start position:0% people people don't even care yes and a 00:33:45.960 --> 00:33:47.630 align:start position:0% people people don't even care yes and a couple<00:33:46.170> of<00:33:46.320> something<00:33:46.650> similar<00:33:47.070> was<00:33:47.340> that<00:33:47.520> you 00:33:47.630 --> 00:33:47.640 align:start position:0% couple of something similar was that you 00:33:47.640 --> 00:33:49.160 align:start position:0% couple of something similar was that you can<00:33:47.790> hook<00:33:47.970> the<00:33:48.090> plasma<00:33:48.390> more<00:33:48.570> to<00:33:48.810> more<00:33:49.050> than 00:33:49.160 --> 00:33:49.170 align:start position:0% can hook the plasma more to more than 00:33:49.170 --> 00:33:52.040 align:start position:0% can hook the plasma more to more than they're<00:33:49.320> just<00:33:49.590> issuing<00:33:50.010> flavor<00:33:50.400> and<00:33:51.050> well 00:33:52.040 --> 00:33:52.050 align:start position:0% they're just issuing flavor and well 00:33:52.050 --> 00:33:54.020 align:start position:0% they're just issuing flavor and well with<00:33:52.320> some<00:33:52.890> problems<00:33:53.310> which<00:33:53.520> arise<00:33:53.670> because 00:33:54.020 --> 00:33:54.030 align:start position:0% with some problems which arise because 00:33:54.030 --> 00:33:55.220 align:start position:0% with some problems which arise because you<00:33:54.300> can<00:33:54.450> commit<00:33:54.690> different<00:33:54.990> blocks 00:33:55.220 --> 00:33:55.230 align:start position:0% you can commit different blocks 00:33:55.230 --> 00:33:56.960 align:start position:0% you can commit different blocks different<00:33:55.950> headers<00:33:56.250> and<00:33:56.490> everything<00:33:56.850> that 00:33:56.960 --> 00:33:56.970 align:start position:0% different headers and everything that 00:33:56.970 --> 00:33:59.540 align:start position:0% different headers and everything that should<00:33:57.090> be<00:33:57.240> in<00:33:57.330> time<00:33:57.690> and<00:33:57.960> available<00:33:58.440> but<00:33:59.010> this 00:33:59.540 --> 00:33:59.550 align:start position:0% should be in time and available but this 00:33:59.550 --> 00:34:01.550 align:start position:0% should be in time and available but this is<00:33:59.730> quite<00:34:00.420> similar<00:34:00.630> so<00:34:00.810> we<00:34:01.170> can<00:34:01.290> try<00:34:01.500> this 00:34:01.550 --> 00:34:01.560 align:start position:0% is quite similar so we can try this 00:34:01.560 --> 00:34:04.250 align:start position:0% is quite similar so we can try this first<00:34:02.010> and<00:34:02.820> then<00:34:02.850> we'll<00:34:03.540> see<00:34:03.750> how<00:34:03.900> it<00:34:04.110> goes 00:34:04.250 --> 00:34:04.260 align:start position:0% first and then we'll see how it goes 00:34:04.260 --> 00:34:06.590 align:start position:0% first and then we'll see how it goes maybe<00:34:04.500> some<00:34:04.950> fancy<00:34:05.910> market<00:34:06.210> between<00:34:06.330> the 00:34:06.590 --> 00:34:06.600 align:start position:0% maybe some fancy market between the 00:34:06.600 --> 00:34:09.920 align:start position:0% maybe some fancy market between the chains<00:34:06.900> we'll<00:34:07.800> see<00:34:07.950> maybe<00:34:08.250> between<00:34:08.700> this<00:34:08.930> eggs 00:34:09.920 --> 00:34:09.930 align:start position:0% chains we'll see maybe between this eggs 00:34:09.930 --> 00:34:13.220 align:start position:0% chains we'll see maybe between this eggs dye<00:34:10.320> chain<00:34:11.160> with<00:34:11.520> this<00:34:11.670> Authority<00:34:12.600> but<00:34:12.780> stable 00:34:13.220 --> 00:34:13.230 align:start position:0% dye chain with this Authority but stable 00:34:13.230 --> 00:34:15.890 align:start position:0% dye chain with this Authority but stable coin<00:34:13.530> inside<00:34:14.010> of<00:34:14.220> it's<00:34:14.520> what<00:34:14.820> you<00:34:15.090> see<00:34:15.270> inside 00:34:15.890 --> 00:34:15.900 align:start position:0% coin inside of it's what you see inside 00:34:15.900 --> 00:34:16.520 align:start position:0% coin inside of it's what you see inside the<00:34:16.080> plasma 00:34:16.520 --> 00:34:16.530 align:start position:0% the plasma 00:34:16.530 --> 00:34:19.400 align:start position:0% the plasma let's<00:34:16.860> make<00:34:17.010> as<00:34:17.160> a<00:34:17.190> fan<00:34:17.430> CDs<00:34:17.760> I<00:34:18.170> was<00:34:19.170> under<00:34:19.380> the 00:34:19.400 --> 00:34:19.410 align:start position:0% let's make as a fan CDs I was under the 00:34:19.410 --> 00:34:21.170 align:start position:0% let's make as a fan CDs I was under the assumption<00:34:19.860> that<00:34:20.010> they<00:34:20.280> each<00:34:20.460> dye<00:34:20.700> chain<00:34:20.970> is<00:34:21.150> a 00:34:21.170 --> 00:34:21.180 align:start position:0% assumption that they each dye chain is a 00:34:21.180 --> 00:34:27.050 align:start position:0% assumption that they each dye chain is a trusted<00:34:22.080> environment<00:34:24.590> but<00:34:25.590> to<00:34:25.920> also<00:34:26.850> extend 00:34:27.050 --> 00:34:27.060 align:start position:0% trusted environment but to also extend 00:34:27.060 --> 00:34:28.970 align:start position:0% trusted environment but to also extend your<00:34:27.270> point<00:34:27.480> from<00:34:27.570> a<00:34:27.690> different<00:34:27.840> facet<00:34:28.110> you 00:34:28.970 --> 00:34:28.980 align:start position:0% your point from a different facet you 00:34:28.980 --> 00:34:31.670 align:start position:0% your point from a different facet you know<00:34:29.100> state<00:34:29.370> channels<00:34:29.730> are<00:34:30.570> also<00:34:30.840> relevant<00:34:31.320> in 00:34:31.670 --> 00:34:31.680 align:start position:0% know state channels are also relevant in 00:34:31.680 --> 00:34:34.190 align:start position:0% know state channels are also relevant in relation<00:34:32.190> to<00:34:32.220> plasma<00:34:32.730> and<00:34:33.570> will<00:34:33.750> continue<00:34:34.050> to 00:34:34.190 --> 00:34:34.200 align:start position:0% relation to plasma and will continue to 00:34:34.200 --> 00:34:35.690 align:start position:0% relation to plasma and will continue to be<00:34:34.380> if<00:34:34.530> you<00:34:34.650> want<00:34:34.890> things<00:34:35.100> like<00:34:35.220> instant 00:34:35.690 --> 00:34:35.700 align:start position:0% be if you want things like instant 00:34:35.700 --> 00:34:37.820 align:start position:0% be if you want things like instant finality<00:34:36.030> and<00:34:36.540> can<00:34:36.900> be<00:34:37.050> it<00:34:37.200> probably<00:34:37.380> likely 00:34:37.820 --> 00:34:37.830 align:start position:0% finality and can be it probably likely 00:34:37.830 --> 00:34:40.310 align:start position:0% finality and can be it probably likely be<00:34:38.100> the<00:34:38.400> you<00:34:38.820> know<00:34:38.940> front-end<00:34:39.390> interface<00:34:39.600> at 00:34:40.310 --> 00:34:40.320 align:start position:0% be the you know front-end interface at 00:34:40.320 --> 00:34:43.310 align:start position:0% be the you know front-end interface at least<00:34:40.530> for<00:34:40.710> most<00:34:40.830> people<00:34:41.600> so<00:34:42.600> I<00:34:42.810> also<00:34:43.050> have<00:34:43.230> a 00:34:43.310 --> 00:34:43.320 align:start position:0% least for most people so I also have a 00:34:43.320 --> 00:34:45.830 align:start position:0% least for most people so I also have a completely<00:34:43.860> unrelated<00:34:44.190> question<00:34:44.700> which<00:34:45.690> is 00:34:45.830 --> 00:34:45.840 align:start position:0% completely unrelated question which is 00:34:45.840 --> 00:34:47.000 align:start position:0% completely unrelated question which is why<00:34:46.170> are<00:34:46.230> you<00:34:46.320> guys<00:34:46.410> spending<00:34:46.530> time<00:34:46.800> and<00:34:46.950> on 00:34:47.000 --> 00:34:47.010 align:start position:0% why are you guys spending time and on 00:34:47.010 --> 00:34:48.320 align:start position:0% why are you guys spending time and on this<00:34:47.100> piracy<00:34:47.460> accumulator<00:34:47.940> stuff<00:34:48.120> when<00:34:48.240> you 00:34:48.320 --> 00:34:48.330 align:start position:0% this piracy accumulator stuff when you 00:34:48.330 --> 00:34:49.280 align:start position:0% this piracy accumulator stuff when you should<00:34:48.510> just<00:34:48.630> verify<00:34:48.990> your<00:34:49.140> state 00:34:49.280 --> 00:34:49.290 align:start position:0% should just verify your state 00:34:49.290 --> 00:34:54.820 align:start position:0% should just verify your state transitions<00:34:49.770> I<00:34:50.750> totally<00:34:51.750> agree<00:34:51.900> with<00:34:51.930> you 00:34:54.820 --> 00:34:54.830 align:start position:0% 00:34:54.830 --> 00:34:58.250 align:start position:0% there<00:34:55.830> is<00:34:55.920> conflicting<00:34:56.400> with<00:34:56.760> curls<00:34:57.260> there's 00:34:58.250 --> 00:34:58.260 align:start position:0% there is conflicting with curls there's 00:34:58.260 --> 00:35:00.380 align:start position:0% there is conflicting with curls there's different<00:34:58.560> perspectives<00:34:58.650> on<00:34:59.190> this<00:34:59.400> so<00:35:00.240> maybe 00:35:00.380 --> 00:35:00.390 align:start position:0% different perspectives on this so maybe 00:35:00.390 --> 00:35:01.640 align:start position:0% different perspectives on this so maybe we<00:35:00.570> can<00:35:00.690> I'm<00:35:00.870> not<00:35:00.900> aware<00:35:01.230> that<00:35:01.290> I'm<00:35:01.500> being 00:35:01.640 --> 00:35:01.650 align:start position:0% we can I'm not aware that I'm being 00:35:01.650 --> 00:35:10.520 align:start position:0% we can I'm not aware that I'm being contentious<00:35:07.820> like<00:35:08.820> very<00:35:09.270> finest<00:35:09.600> verifying 00:35:10.520 --> 00:35:10.530 align:start position:0% contentious like very finest verifying 00:35:10.530 --> 00:35:14.060 align:start position:0% contentious like very finest verifying state<00:35:10.770> transitions<00:35:11.220> has<00:35:11.430> like<00:35:11.810> like<00:35:13.070> you 00:35:14.060 --> 00:35:14.070 align:start position:0% state transitions has like like you 00:35:14.070 --> 00:35:15.770 align:start position:0% state transitions has like like you might<00:35:14.250> get<00:35:14.340> a<00:35:14.400> low<00:35:14.610> marginal<00:35:15.000> cost<00:35:15.240> eventually 00:35:15.770 --> 00:35:15.780 align:start position:0% might get a low marginal cost eventually 00:35:15.780 --> 00:35:17.330 align:start position:0% might get a low marginal cost eventually but<00:35:15.930> usually<00:35:16.440> you<00:35:16.500> always<00:35:16.680> pay<00:35:16.830> the<00:35:16.890> base<00:35:17.100> cost 00:35:17.330 --> 00:35:17.340 align:start position:0% but usually you always pay the base cost 00:35:17.340 --> 00:35:19.400 align:start position:0% but usually you always pay the base cost but<00:35:18.270> with<00:35:18.480> something<00:35:18.780> like<00:35:18.930> last<00:35:19.110> Mike<00:35:19.260> hash 00:35:19.400 --> 00:35:19.410 align:start position:0% but with something like last Mike hash 00:35:19.410 --> 00:35:23.080 align:start position:0% but with something like last Mike hash you<00:35:19.530> can<00:35:19.650> get<00:35:19.800> down<00:35:19.920> to<00:35:20.100> like<00:35:20.870> 1s<00:35:21.870> torpor<00:35:22.350> like 00:35:23.080 --> 00:35:23.090 align:start position:0% you can get down to like 1s torpor like 00:35:23.090 --> 00:35:26.700 align:start position:0% you can get down to like 1s torpor like like<00:35:24.530> 20,000<00:35:25.530> guests<00:35:25.860> per 00:35:26.700 --> 00:35:26.710 align:start position:0% like 20,000 guests per 00:35:26.710 --> 00:35:29.100 align:start position:0% like 20,000 guests per per<00:35:27.250> transaction<00:35:27.730> without<00:35:28.330> without<00:35:28.690> any<00:35:28.750> like 00:35:29.100 --> 00:35:29.110 align:start position:0% per transaction without without any like 00:35:29.110 --> 00:35:38.130 align:start position:0% per transaction without without any like kind<00:35:29.470> of<00:35:29.530> batching<00:35:29.830> thing<00:35:36.900> one<00:35:37.900> advantage 00:35:38.130 --> 00:35:38.140 align:start position:0% kind of batching thing one advantage 00:35:38.140 --> 00:35:42.570 align:start position:0% kind of batching thing one advantage that<00:35:38.500> you<00:35:38.530> can't<00:35:38.830> get<00:35:38.920> with<00:35:40.890> the<00:35:41.890> problem<00:35:42.430> with 00:35:42.570 --> 00:35:42.580 align:start position:0% that you can't get with the problem with 00:35:42.580 --> 00:35:44.460 align:start position:0% that you can't get with the problem with this<00:35:42.760> DK<00:35:43.360> based<00:35:43.630> constructions<00:35:44.230> they<00:35:44.320> should 00:35:44.460 --> 00:35:44.470 align:start position:0% this DK based constructions they should 00:35:44.470 --> 00:35:46.290 align:start position:0% this DK based constructions they should encounter<00:35:44.890> for<00:35:45.160> more<00:35:45.610> than<00:35:45.820> just<00:35:45.850> cast<00:35:46.180> of 00:35:46.290 --> 00:35:46.300 align:start position:0% encounter for more than just cast of 00:35:46.300 --> 00:35:48.660 align:start position:0% encounter for more than just cast of postings<00:35:46.690> of<00:35:46.780> snark<00:35:47.080> but<00:35:47.710> well<00:35:47.980> state 00:35:48.660 --> 00:35:48.670 align:start position:0% postings of snark but well state 00:35:48.670 --> 00:35:50.190 align:start position:0% postings of snark but well state transition<00:35:49.150> or<00:35:49.330> something<00:35:49.660> like<00:35:49.780> this<00:35:49.930> any 00:35:50.190 --> 00:35:50.200 align:start position:0% transition or something like this any 00:35:50.200 --> 00:35:52.200 align:start position:0% transition or something like this any other<00:35:50.380> construction<00:35:50.620> it<00:35:51.340> also<00:35:51.640> boys<00:35:51.790> out<00:35:51.940> if 00:35:52.200 --> 00:35:52.210 align:start position:0% other construction it also boys out if 00:35:52.210 --> 00:35:54.690 align:start position:0% other construction it also boys out if you<00:35:52.300> want<00:35:52.480> like<00:35:53.410> one<00:35:53.800> proverb<00:35:54.340> which<00:35:54.520> should 00:35:54.690 --> 00:35:54.700 align:start position:0% you want like one proverb which should 00:35:54.700 --> 00:35:56.880 align:start position:0% you want like one proverb which should make<00:35:54.820> your<00:35:55.030> blocks<00:35:55.410> you<00:35:56.410> should<00:35:56.590> have<00:35:56.770> the 00:35:56.880 --> 00:35:56.890 align:start position:0% make your blocks you should have the 00:35:56.890 --> 00:35:58.800 align:start position:0% make your blocks you should have the mechanism<00:35:57.340> in<00:35:57.820> the<00:35:58.000> case<00:35:58.210> you<00:35:58.240> don't<00:35:58.510> publish 00:35:58.800 --> 00:35:58.810 align:start position:0% mechanism in the case you don't publish 00:35:58.810 --> 00:36:00.180 align:start position:0% mechanism in the case you don't publish the<00:35:58.930> call<00:35:59.080> data<00:35:59.260> to<00:35:59.470> the<00:35:59.590> contract<00:35:59.980> you 00:36:00.180 --> 00:36:00.190 align:start position:0% the call data to the contract you 00:36:00.190 --> 00:36:02.070 align:start position:0% the call data to the contract you publish<00:36:00.610> the<00:36:00.760> block<00:36:00.970> separately<00:36:01.420> you<00:36:01.900> should 00:36:02.070 --> 00:36:02.080 align:start position:0% publish the block separately you should 00:36:02.080 --> 00:36:03.210 align:start position:0% publish the block separately you should have<00:36:02.260> the<00:36:02.380> mechanism<00:36:02.770> to<00:36:02.890> solve<00:36:03.040> date 00:36:03.210 --> 00:36:03.220 align:start position:0% have the mechanism to solve date 00:36:03.220 --> 00:36:05.220 align:start position:0% have the mechanism to solve date availability<00:36:03.790> if<00:36:04.270> you<00:36:04.390> have<00:36:04.630> competing 00:36:05.220 --> 00:36:05.230 align:start position:0% availability if you have competing 00:36:05.230 --> 00:36:08.400 align:start position:0% availability if you have competing operators<00:36:05.770> your<00:36:06.760> cost<00:36:07.270> increases<00:36:07.840> because<00:36:08.170> to 00:36:08.400 --> 00:36:08.410 align:start position:0% operators your cost increases because to 00:36:08.410 --> 00:36:09.810 align:start position:0% operators your cost increases because to calculate<00:36:08.770> this<00:36:08.920> knife<00:36:09.070> is<00:36:09.220> not<00:36:09.340> easy<00:36:09.610> it's 00:36:09.810 --> 00:36:09.820 align:start position:0% calculate this knife is not easy it's 00:36:09.820 --> 00:36:11.820 align:start position:0% calculate this knife is not easy it's not<00:36:09.850> cheap<00:36:10.210> and<00:36:10.450> now<00:36:11.020> you<00:36:11.080> have<00:36:11.350> to<00:36:11.440> multiply 00:36:11.820 --> 00:36:11.830 align:start position:0% not cheap and now you have to multiply 00:36:11.830 --> 00:36:14.280 align:start position:0% not cheap and now you have to multiply by<00:36:12.220> the<00:36:12.250> number<00:36:12.400> of<00:36:12.610> competing<00:36:13.090> operators<00:36:13.780> who 00:36:14.280 --> 00:36:14.290 align:start position:0% by the number of competing operators who 00:36:14.290 --> 00:36:16.890 align:start position:0% by the number of competing operators who should<00:36:14.470> get<00:36:14.670> well<00:36:15.670> for<00:36:16.060> those<00:36:16.300> it<00:36:16.600> should<00:36:16.780> be 00:36:16.890 --> 00:36:16.900 align:start position:0% should get well for those it should be 00:36:16.900 --> 00:36:18.510 align:start position:0% should get well for those it should be reasonable<00:36:17.320> to<00:36:17.560> get<00:36:17.680> the<00:36:17.800> profits<00:36:18.100> from<00:36:18.250> it<00:36:18.400> so 00:36:18.510 --> 00:36:18.520 align:start position:0% reasonable to get the profits from it so 00:36:18.520 --> 00:36:20.220 align:start position:0% reasonable to get the profits from it so basically<00:36:19.030> transaction<00:36:19.510> cost<00:36:19.720> increases 00:36:20.220 --> 00:36:20.230 align:start position:0% basically transaction cost increases 00:36:20.230 --> 00:36:23.610 align:start position:0% basically transaction cost increases this<00:36:20.980> is<00:36:21.160> also<00:36:21.340> an<00:36:21.700> area<00:36:21.910> of<00:36:22.060> research<00:36:22.620> I'll 00:36:23.610 --> 00:36:23.620 align:start position:0% this is also an area of research I'll 00:36:23.620 --> 00:36:25.650 align:start position:0% this is also an area of research I'll sent<00:36:23.890> as<00:36:24.040> a<00:36:24.100> researcher<00:36:24.730> which<00:36:25.000> didn't<00:36:25.510> talk 00:36:25.650 --> 00:36:25.660 align:start position:0% sent as a researcher which didn't talk 00:36:25.660 --> 00:36:26.910 align:start position:0% sent as a researcher which didn't talk today<00:36:25.900> we<00:36:26.050> had<00:36:26.260> a<00:36:26.290> some<00:36:26.530> discussion 00:36:26.910 --> 00:36:26.920 align:start position:0% today we had a some discussion 00:36:26.920 --> 00:36:28.590 align:start position:0% today we had a some discussion accreditor<00:36:27.400> it's<00:36:27.880> how<00:36:28.060> you<00:36:28.120> can<00:36:28.330> make<00:36:28.480> the 00:36:28.590 --> 00:36:28.600 align:start position:0% accreditor it's how you can make the 00:36:28.600 --> 00:36:31.560 align:start position:0% accreditor it's how you can make the stateless<00:36:29.050> block<00:36:29.940> validation<00:36:30.940> which<00:36:31.270> was<00:36:31.450> the 00:36:31.560 --> 00:36:31.570 align:start position:0% stateless block validation which was the 00:36:31.570 --> 00:36:33.270 align:start position:0% stateless block validation which was the recent<00:36:31.840> paper<00:36:31.990> published<00:36:32.110> I<00:36:32.560> think<00:36:32.740> a<00:36:32.860> thank 00:36:33.270 --> 00:36:33.280 align:start position:0% recent paper published I think a thank 00:36:33.280 --> 00:36:35.160 align:start position:0% recent paper published I think a thank you<00:36:33.340> for<00:36:33.520> charges<00:36:33.910> for<00:36:34.090> link<00:36:34.300> as<00:36:34.750> a<00:36:34.810> research 00:36:35.160 --> 00:36:35.170 align:start position:0% you for charges for link as a research 00:36:35.170 --> 00:36:37.800 align:start position:0% you for charges for link as a research ed<00:36:35.350> works<00:36:35.560> yeah<00:36:35.880> you<00:36:36.880> can<00:36:37.030> make<00:36:37.150> a<00:36:37.300> block 00:36:37.800 --> 00:36:37.810 align:start position:0% ed works yeah you can make a block 00:36:37.810 --> 00:36:39.480 align:start position:0% ed works yeah you can make a block validator<00:36:38.230> completely<00:36:38.890> status<00:36:39.250> you<00:36:39.370> can 00:36:39.480 --> 00:36:39.490 align:start position:0% validator completely status you can 00:36:39.490 --> 00:36:40.860 align:start position:0% validator completely status you can write<00:36:39.640> it<00:36:39.790> on<00:36:39.940> mobile<00:36:40.120> devices<00:36:40.510> you<00:36:40.690> can<00:36:40.840> have 00:36:40.860 --> 00:36:40.870 align:start position:0% write it on mobile devices you can have 00:36:40.870 --> 00:36:44.310 align:start position:0% write it on mobile devices you can have like<00:36:41.290> almost<00:36:42.190> absolute<00:36:43.090> liveness<00:36:43.360> hundred 00:36:44.310 --> 00:36:44.320 align:start position:0% like almost absolute liveness hundred 00:36:44.320 --> 00:36:50.310 align:start position:0% like almost absolute liveness hundred minutes<00:36:44.560> of<00:36:45.690> thousands<00:36:46.690> of<00:36:46.750> users<00:36:47.880> no<00:36:49.170> not<00:36:50.170> the 00:36:50.310 --> 00:36:50.320 align:start position:0% minutes of thousands of users no not the 00:36:50.320 --> 00:36:51.930 align:start position:0% minutes of thousands of users no not the balanced<00:36:50.680> one<00:36:50.830> for<00:36:51.220> now<00:36:51.340> we<00:36:51.400> take<00:36:51.610> some<00:36:51.820> other 00:36:51.930 --> 00:36:51.940 align:start position:0% balanced one for now we take some other 00:36:51.940 --> 00:36:53.640 align:start position:0% balanced one for now we take some other vector<00:36:52.240> commits<00:36:52.630> and<00:36:52.750> we<00:36:52.840> can<00:36:52.960> discuss<00:36:53.590> later 00:36:53.640 --> 00:36:53.650 align:start position:0% vector commits and we can discuss later 00:36:53.650 --> 00:36:56.760 align:start position:0% vector commits and we can discuss later was<00:36:54.040> there<00:36:54.220> not<00:36:54.310> usable<00:36:54.730> right<00:36:54.880> now<00:36:55.000> so<00:36:55.900> there 00:36:56.760 --> 00:36:56.770 align:start position:0% was there not usable right now so there 00:36:56.770 --> 00:36:58.380 align:start position:0% was there not usable right now so there are<00:36:56.890> various<00:36:57.220> areas<00:36:57.580> of<00:36:57.700> research<00:36:58.060> this 00:36:58.380 --> 00:36:58.390 align:start position:0% are various areas of research this 00:36:58.390 --> 00:37:00.090 align:start position:0% are various areas of research this stateless<00:36:58.810> validation<00:36:59.350> is<00:36:59.530> great<00:36:59.830> just 00:37:00.090 --> 00:37:00.100 align:start position:0% stateless validation is great just 00:37:00.100 --> 00:37:02.280 align:start position:0% stateless validation is great just because<00:37:00.340> we<00:37:01.000> want<00:37:01.210> live<00:37:01.390> news<00:37:01.600> we<00:37:01.900> want 00:37:02.280 --> 00:37:02.290 align:start position:0% because we want live news we want 00:37:02.290 --> 00:37:04.050 align:start position:0% because we want live news we want someone<00:37:02.890> watching<00:37:03.280> at<00:37:03.400> least<00:37:03.580> someone's<00:37:03.970> the 00:37:04.050 --> 00:37:04.060 align:start position:0% someone watching at least someone's the 00:37:04.060 --> 00:37:05.670 align:start position:0% someone watching at least someone's the same<00:37:04.210> way<00:37:04.360> as<00:37:04.420> for<00:37:04.930> assuming<00:37:05.170> to<00:37:05.410> poundtown 00:37:05.670 --> 00:37:05.680 align:start position:0% same way as for assuming to poundtown 00:37:05.680 --> 00:37:07.680 align:start position:0% same way as for assuming to poundtown you<00:37:06.220> want<00:37:06.370> someone<00:37:06.730> to<00:37:06.880> run<00:37:07.180> this<00:37:07.330> fancy 00:37:07.680 --> 00:37:07.690 align:start position:0% you want someone to run this fancy 00:37:07.690 --> 00:37:10.170 align:start position:0% you want someone to run this fancy hardware<00:37:08.080> with<00:37:08.320> vdf<00:37:08.740> you<00:37:09.370> want<00:37:09.550> someone<00:37:09.880> to 00:37:10.170 --> 00:37:10.180 align:start position:0% hardware with vdf you want someone to 00:37:10.180 --> 00:37:13.080 align:start position:0% hardware with vdf you want someone to monitor<00:37:10.360> the<00:37:10.780> plasma<00:37:11.080> just<00:37:11.260> someone<00:37:11.860> and<00:37:12.130> then 00:37:13.080 --> 00:37:13.090 align:start position:0% monitor the plasma just someone and then 00:37:13.090 --> 00:37:15.120 align:start position:0% monitor the plasma just someone and then it<00:37:13.120> will<00:37:13.420> work<00:37:13.450> otherwise<00:37:14.200> well<00:37:14.710> we<00:37:14.860> need<00:37:14.980> to 00:37:15.120 --> 00:37:15.130 align:start position:0% it will work otherwise well we need to 00:37:15.130 --> 00:37:16.650 align:start position:0% it will work otherwise well we need to work<00:37:15.160> in<00:37:15.400> user<00:37:15.610> experience<00:37:15.700> validation<00:37:16.600> and 00:37:16.650 --> 00:37:16.660 align:start position:0% work in user experience validation and 00:37:16.660 --> 00:37:18.870 align:start position:0% work in user experience validation and everything<00:37:17.020> so<00:37:17.140> yeah<00:37:17.530> more<00:37:18.490> people<00:37:18.760> can 00:37:18.870 --> 00:37:18.880 align:start position:0% everything so yeah more people can 00:37:18.880 --> 00:37:20.730 align:start position:0% everything so yeah more people can change<00:37:19.090> the<00:37:19.210> research<00:37:19.510> is<00:37:19.690> better<00:37:19.900> as<00:37:20.110> well<00:37:20.470> in 00:37:20.730 --> 00:37:20.740 align:start position:0% change the research is better as well in 00:37:20.740 --> 00:37:22.560 align:start position:0% change the research is better as well in research<00:37:21.310> may<00:37:21.520> be<00:37:21.550> difficult<00:37:22.000> implementation 00:37:22.560 --> 00:37:22.570 align:start position:0% research may be difficult implementation 00:37:22.570 --> 00:37:24.210 align:start position:0% research may be difficult implementation is<00:37:22.690> still<00:37:23.110> great<00:37:23.350> because<00:37:23.650> you<00:37:23.740> need<00:37:23.890> to<00:37:24.040> test 00:37:24.210 --> 00:37:24.220 align:start position:0% is still great because you need to test 00:37:24.220 --> 00:37:25.560 align:start position:0% is still great because you need to test so<00:37:24.310> many<00:37:24.490> things<00:37:24.730> how<00:37:24.880> is<00:37:24.970> it<00:37:25.090> work<00:37:25.270> how<00:37:25.450> it 00:37:25.560 --> 00:37:25.570 align:start position:0% so many things how is it work how it 00:37:25.570 --> 00:37:27.870 align:start position:0% so many things how is it work how it makes<00:37:25.750> the<00:37:25.840> user<00:37:25.990> experience<00:37:26.320> so<00:37:27.010> just<00:37:27.220> please 00:37:27.870 --> 00:37:27.880 align:start position:0% makes the user experience so just please 00:37:27.880 --> 00:37:29.640 align:start position:0% makes the user experience so just please join<00:37:28.360> Evan<00:37:28.630> if<00:37:28.750> you<00:37:28.840> don't<00:37:29.020> want<00:37:29.230> to<00:37:29.350> research 00:37:29.640 --> 00:37:29.650 align:start position:0% join Evan if you don't want to research 00:37:29.650 --> 00:37:32.370 align:start position:0% join Evan if you don't want to research you<00:37:29.800> won't<00:37:29.950> just<00:37:30.130> write<00:37:30.400> a<00:37:30.430> code<00:37:31.230> yeah<00:37:32.230> I<00:37:32.260> think 00:37:32.370 --> 00:37:32.380 align:start position:0% you won't just write a code yeah I think 00:37:32.380 --> 00:37:34.620 align:start position:0% you won't just write a code yeah I think we<00:37:32.620> you<00:37:32.890> know<00:37:33.010> we<00:37:33.250> are<00:37:33.370> always<00:37:33.940> you<00:37:34.300> know<00:37:34.330> the 00:37:34.620 --> 00:37:34.630 align:start position:0% we you know we are always you know the 00:37:34.630 --> 00:37:36.120 align:start position:0% we you know we are always you know the space<00:37:35.020> always<00:37:35.230> needs<00:37:35.500> better<00:37:35.710> systems 00:37:36.120 --> 00:37:36.130 align:start position:0% space always needs better systems 00:37:36.130 --> 00:37:38.250 align:start position:0% space always needs better systems engineers<00:37:36.550> and<00:37:36.820> more<00:37:36.970> systems<00:37:37.300> engineers<00:37:37.750> I 00:37:38.250 --> 00:37:38.260 align:start position:0% engineers and more systems engineers I 00:37:38.260 --> 00:37:40.259 align:start position:0% engineers and more systems engineers I think 00:37:40.259 --> 00:37:40.269 align:start position:0% think 00:37:40.269 --> 00:37:41.969 align:start position:0% think yeah<00:37:40.479> in<00:37:40.659> addition<00:37:41.439> to<00:37:41.499> your<00:37:41.559> question<00:37:41.859> I 00:37:41.969 --> 00:37:41.979 align:start position:0% yeah in addition to your question I 00:37:41.979 --> 00:37:44.909 align:start position:0% yeah in addition to your question I think<00:37:42.029> you<00:37:43.029> know<00:37:43.119> having<00:37:43.359> having<00:37:44.259> a<00:37:44.439> baseline 00:37:44.909 --> 00:37:44.919 align:start position:0% think you know having having a baseline 00:37:44.919 --> 00:37:47.189 align:start position:0% think you know having having a baseline using<00:37:45.519> minimal<00:37:45.939> fancy<00:37:46.329> cryptography<00:37:46.869> is<00:37:47.019> good 00:37:47.189 --> 00:37:47.199 align:start position:0% using minimal fancy cryptography is good 00:37:47.199 --> 00:37:49.529 align:start position:0% using minimal fancy cryptography is good and<00:37:47.379> then<00:37:47.649> having<00:37:48.159> fancy<00:37:48.789> cryptography<00:37:49.359> used 00:37:49.529 --> 00:37:49.539 align:start position:0% and then having fancy cryptography used 00:37:49.539 --> 00:37:51.479 align:start position:0% and then having fancy cryptography used to<00:37:49.659> makes<00:37:49.809> everything<00:37:50.079> better<00:37:50.379> easier<00:37:50.979> faster 00:37:51.479 --> 00:37:51.489 align:start position:0% to makes everything better easier faster 00:37:51.489 --> 00:37:53.279 align:start position:0% to makes everything better easier faster I<00:37:51.669> think<00:37:51.939> it's<00:37:52.239> a<00:37:52.299> good<00:37:52.479> rule<00:37:52.719> of<00:37:52.749> thumb<00:37:52.869> in<00:37:53.199> the 00:37:53.279 --> 00:37:53.289 align:start position:0% I think it's a good rule of thumb in the 00:37:53.289 --> 00:37:55.049 align:start position:0% I think it's a good rule of thumb in the space<00:37:53.529> and<00:37:53.769> you<00:37:54.249> know<00:37:54.339> that<00:37:54.579> that<00:37:54.759> makes<00:37:54.969> them 00:37:55.049 --> 00:37:55.059 align:start position:0% space and you know that that makes them 00:37:55.059 --> 00:37:57.619 align:start position:0% space and you know that that makes them very<00:37:55.389> strong<00:37:55.749> measurable<00:37:56.259> improvement 00:37:57.619 --> 00:37:57.629 align:start position:0% very strong measurable improvement 00:37:57.629 --> 00:38:01.079 align:start position:0% very strong measurable improvement maybe<00:37:58.629> a<00:37:58.719> personal<00:37:59.499> story<00:37:59.739> so<00:38:00.129> I<00:38:00.429> got<00:38:00.849> into 00:38:01.079 --> 00:38:01.089 align:start position:0% maybe a personal story so I got into 00:38:01.089 --> 00:38:03.119 align:start position:0% maybe a personal story so I got into this<00:38:01.209> plasma<00:38:01.659> research<00:38:01.839> as<00:38:02.229> well<00:38:02.409> and<00:38:02.649> I<00:38:02.859> was 00:38:03.119 --> 00:38:03.129 align:start position:0% this plasma research as well and I was 00:38:03.129 --> 00:38:06.059 align:start position:0% this plasma research as well and I was kind<00:38:03.399> of<00:38:03.519> like<00:38:03.999> going<00:38:04.929> strong<00:38:05.289> on<00:38:05.499> aetherium 00:38:06.059 --> 00:38:06.069 align:start position:0% kind of like going strong on aetherium 00:38:06.069 --> 00:38:07.529 align:start position:0% kind of like going strong on aetherium style<00:38:06.399> contracts<00:38:06.909> and<00:38:07.089> I<00:38:07.149> thought<00:38:07.329> there's 00:38:07.529 --> 00:38:07.539 align:start position:0% style contracts and I thought there's 00:38:07.539 --> 00:38:09.209 align:start position:0% style contracts and I thought there's nothing<00:38:07.869> wrong<00:38:08.019> with<00:38:08.229> them<00:38:08.379> and<00:38:08.499> then<00:38:08.739> Kelvin 00:38:09.209 --> 00:38:09.219 align:start position:0% nothing wrong with them and then Kelvin 00:38:09.219 --> 00:38:11.039 align:start position:0% nothing wrong with them and then Kelvin wrote<00:38:09.579> a<00:38:09.609> bunch<00:38:10.089> of<00:38:10.269> interesting<00:38:10.569> blog 00:38:11.039 --> 00:38:11.049 align:start position:0% wrote a bunch of interesting blog 00:38:11.049 --> 00:38:14.939 align:start position:0% wrote a bunch of interesting blog articles<00:38:11.559> talking<00:38:11.919> about<00:38:12.159> how<00:38:12.969> actually<00:38:13.949> a 00:38:14.939 --> 00:38:14.949 align:start position:0% articles talking about how actually a 00:38:14.949 --> 00:38:15.629 align:start position:0% articles talking about how actually a ledger 00:38:15.629 --> 00:38:15.639 align:start position:0% ledger 00:38:15.639 --> 00:38:18.149 align:start position:0% ledger you<00:38:15.879> know<00:38:16.049> attracts<00:38:17.049> assets<00:38:17.619> it<00:38:17.799> doesn't 00:38:18.149 --> 00:38:18.159 align:start position:0% you know attracts assets it doesn't 00:38:18.159 --> 00:38:20.309 align:start position:0% you know attracts assets it doesn't necessarily<00:38:18.729> contracts<00:38:19.599> should<00:38:19.749> maybe<00:38:20.169> not 00:38:20.309 --> 00:38:20.319 align:start position:0% necessarily contracts should maybe not 00:38:20.319 --> 00:38:23.459 align:start position:0% necessarily contracts should maybe not be<00:38:20.739> first-class<00:38:21.219> citizens<00:38:21.699> on<00:38:21.879> on<00:38:22.719> assets<00:38:23.139> on 00:38:23.459 --> 00:38:23.469 align:start position:0% be first-class citizens on on assets on 00:38:23.469 --> 00:38:26.009 align:start position:0% be first-class citizens on on assets on Ledger's<00:38:24.249> and<00:38:24.369> the<00:38:25.209> whole<00:38:25.359> plasma<00:38:25.689> research 00:38:26.009 --> 00:38:26.019 align:start position:0% Ledger's and the whole plasma research 00:38:26.019 --> 00:38:28.459 align:start position:0% Ledger's and the whole plasma research has<00:38:26.259> kind<00:38:26.469> of<00:38:26.589> led<00:38:26.799> me<00:38:26.829> to<00:38:27.099> kind<00:38:27.339> of<00:38:27.429> rethink 00:38:28.459 --> 00:38:28.469 align:start position:0% has kind of led me to kind of rethink 00:38:28.469 --> 00:38:31.019 align:start position:0% has kind of led me to kind of rethink the<00:38:29.469> architecture<00:38:30.069> of<00:38:30.129> a<00:38:30.249> theorem<00:38:30.579> and<00:38:30.789> kind 00:38:31.019 --> 00:38:31.029 align:start position:0% the architecture of a theorem and kind 00:38:31.029 --> 00:38:33.059 align:start position:0% the architecture of a theorem and kind of<00:38:31.089> find<00:38:31.359> that<00:38:31.539> there<00:38:31.689> could<00:38:31.839> be<00:38:31.869> a<00:38:32.229> way<00:38:32.829> more 00:38:33.059 --> 00:38:33.069 align:start position:0% of find that there could be a way more 00:38:33.069 --> 00:38:35.939 align:start position:0% of find that there could be a way more efficient<00:38:33.609> set<00:38:34.149> up<00:38:34.329> where<00:38:34.569> in<00:38:34.839> Bitcoin<00:38:35.799> you 00:38:35.939 --> 00:38:35.949 align:start position:0% efficient set up where in Bitcoin you 00:38:35.949 --> 00:38:38.009 align:start position:0% efficient set up where in Bitcoin you kind<00:38:36.129> of<00:38:36.189> have<00:38:36.369> fat<00:38:36.639> blocks<00:38:36.969> but<00:38:37.329> a<00:38:37.359> thin<00:38:37.659> stage 00:38:38.009 --> 00:38:38.019 align:start position:0% kind of have fat blocks but a thin stage 00:38:38.019 --> 00:38:40.109 align:start position:0% kind of have fat blocks but a thin stage any<00:38:38.499> theorem<00:38:38.829> you<00:38:38.949> have<00:38:39.099> thin<00:38:39.399> blocks<00:38:39.699> of<00:38:39.909> fat 00:38:40.109 --> 00:38:40.119 align:start position:0% any theorem you have thin blocks of fat 00:38:40.119 --> 00:38:42.659 align:start position:0% any theorem you have thin blocks of fat state<00:38:40.509> but<00:38:40.839> we<00:38:40.989> could<00:38:41.139> go<00:38:41.319> with<00:38:41.589> thin<00:38:42.339> blocks 00:38:42.659 --> 00:38:42.669 align:start position:0% state but we could go with thin blocks 00:38:42.669 --> 00:38:50.909 align:start position:0% state but we could go with thin blocks and<00:38:42.939> thin<00:38:43.179> state<00:38:44.759> I<00:38:49.319> think<00:38:50.319> it<00:38:50.409> was<00:38:50.499> low<00:38:50.649> then<00:38:50.859> I 00:38:50.909 --> 00:38:50.919 align:start position:0% and thin state I think it was low then I 00:38:50.919 --> 00:38:53.039 align:start position:0% and thin state I think it was low then I was<00:38:51.069> still<00:38:51.279> it<00:38:51.459> says<00:38:51.579> the<00:38:51.699> trader<00:38:51.939> was<00:38:52.149> Kelvin 00:38:53.039 --> 00:38:53.049 align:start position:0% was still it says the trader was Kelvin 00:38:53.049 --> 00:38:54.749 align:start position:0% was still it says the trader was Kelvin was<00:38:53.169> talking<00:38:53.439> about<00:38:53.499> until<00:38:53.859> it's<00:38:54.099> formalized 00:38:54.749 --> 00:38:54.759 align:start position:0% was talking about until it's formalized 00:38:54.759 --> 00:38:57.389 align:start position:0% was talking about until it's formalized well<00:38:55.359> light<00:38:56.139> client<00:38:56.529> and<00:38:56.679> light<00:38:56.859> blocks<00:38:57.159> like 00:38:57.389 --> 00:38:57.399 align:start position:0% well light client and light blocks like 00:38:57.399 --> 00:38:59.969 align:start position:0% well light client and light blocks like ideal<00:38:57.999> scenario<00:38:58.359> but<00:38:58.989> still<00:38:59.319> most<00:38:59.619> like<00:38:59.799> is 00:38:59.969 --> 00:38:59.979 align:start position:0% ideal scenario but still most like is 00:38:59.979 --> 00:39:01.859 align:start position:0% ideal scenario but still most like is there<00:39:00.549> a<00:39:00.579> trade<00:39:01.029> offs<00:39:01.239> maybe<00:39:01.509> there<00:39:01.749> is 00:39:01.859 --> 00:39:01.869 align:start position:0% there a trade offs maybe there is 00:39:01.869 --> 00:39:03.809 align:start position:0% there a trade offs maybe there is nothing<00:39:02.169> like<00:39:02.349> a<00:39:02.589> external<00:39:03.459> computation 00:39:03.809 --> 00:39:03.819 align:start position:0% nothing like a external computation 00:39:03.819 --> 00:39:05.729 align:start position:0% nothing like a external computation powers<00:39:04.209> it<00:39:04.329> should<00:39:04.509> be<00:39:04.599> made<00:39:04.779> to<00:39:04.809> make<00:39:05.529> some 00:39:05.729 --> 00:39:05.739 align:start position:0% powers it should be made to make some 00:39:05.739 --> 00:39:08.879 align:start position:0% powers it should be made to make some blocks<00:39:05.949> and<00:39:06.939> one<00:39:07.239> fun<00:39:07.569> a<00:39:07.599> theorem<00:39:07.959> 2.0<00:39:08.409> note<00:39:08.649> is 00:39:08.879 --> 00:39:08.889 align:start position:0% blocks and one fun a theorem 2.0 note is 00:39:08.889 --> 00:39:12.029 align:start position:0% blocks and one fun a theorem 2.0 note is that<00:39:09.579> the<00:39:10.119> first<00:39:10.599> focus<00:39:11.109> in<00:39:11.289> the<00:39:11.379> main<00:39:11.589> focus 00:39:12.029 --> 00:39:12.039 align:start position:0% that the first focus in the main focus 00:39:12.039 --> 00:39:15.029 align:start position:0% that the first focus in the main focus is<00:39:12.309> providing<00:39:12.999> a<00:39:13.439> massive<00:39:14.439> stream<00:39:14.799> of 00:39:15.029 --> 00:39:15.039 align:start position:0% is providing a massive stream of 00:39:15.039 --> 00:39:17.309 align:start position:0% is providing a massive stream of available<00:39:15.699> ordered<00:39:16.179> data<00:39:16.419> that<00:39:16.719> you<00:39:16.809> can<00:39:16.989> rely 00:39:17.309 --> 00:39:17.319 align:start position:0% available ordered data that you can rely 00:39:17.319 --> 00:39:20.429 align:start position:0% available ordered data that you can rely on<00:39:17.349> and<00:39:17.589> Trust<00:39:17.889> right<00:39:18.699> this<00:39:18.999> is<00:39:19.269> in<00:39:19.659> fact<00:39:20.019> the 00:39:20.429 --> 00:39:20.439 align:start position:0% on and Trust right this is in fact the 00:39:20.439 --> 00:39:22.079 align:start position:0% on and Trust right this is in fact the most<00:39:20.649> primitive<00:39:21.009> in<00:39:21.339> my<00:39:21.459> opinion<00:39:21.789> because<00:39:22.059> it 00:39:22.079 --> 00:39:22.089 align:start position:0% most primitive in my opinion because it 00:39:22.089 --> 00:39:23.819 align:start position:0% most primitive in my opinion because it is<00:39:22.299> literally<00:39:22.629> just<00:39:22.839> information<00:39:23.589> that<00:39:23.619> we 00:39:23.819 --> 00:39:23.829 align:start position:0% is literally just information that we 00:39:23.829 --> 00:39:25.799 align:start position:0% is literally just information that we have<00:39:23.919> consensus<00:39:24.399> on<00:39:24.579> and<00:39:24.819> information<00:39:25.509> can<00:39:25.659> be 00:39:25.799 --> 00:39:25.809 align:start position:0% have consensus on and information can be 00:39:25.809 --> 00:39:27.869 align:start position:0% have consensus on and information can be interpreted<00:39:26.559> in<00:39:26.859> whatever<00:39:27.039> way<00:39:27.309> you<00:39:27.369> want<00:39:27.669> so 00:39:27.869 --> 00:39:27.879 align:start position:0% interpreted in whatever way you want so 00:39:27.879 --> 00:39:30.119 align:start position:0% interpreted in whatever way you want so if<00:39:28.299> you<00:39:28.749> want<00:39:29.079> a<00:39:29.319> different<00:39:29.589> kind<00:39:30.009> of 00:39:30.119 --> 00:39:30.129 align:start position:0% if you want a different kind of 00:39:30.129 --> 00:39:33.659 align:start position:0% if you want a different kind of aetherium<00:39:30.609> you<00:39:30.879> know<00:39:31.619> EVM<00:39:32.619> or<00:39:33.099> if<00:39:33.189> you<00:39:33.339> want<00:39:33.549> to 00:39:33.659 --> 00:39:33.669 align:start position:0% aetherium you know EVM or if you want to 00:39:33.669 --> 00:39:35.789 align:start position:0% aetherium you know EVM or if you want to you<00:39:33.759> know<00:39:33.879> put<00:39:34.059> Bitcoin<00:39:34.539> or<00:39:34.569> Z<00:39:34.959> cash<00:39:35.199> directly 00:39:35.789 --> 00:39:35.799 align:start position:0% you know put Bitcoin or Z cash directly 00:39:35.799 --> 00:39:37.679 align:start position:0% you know put Bitcoin or Z cash directly on<00:39:35.949> aetherium<00:39:36.309> and<00:39:36.609> use<00:39:36.819> that<00:39:37.089> kind<00:39:37.389> of<00:39:37.509> data 00:39:37.679 --> 00:39:37.689 align:start position:0% on aetherium and use that kind of data 00:39:37.689 --> 00:39:40.349 align:start position:0% on aetherium and use that kind of data stream<00:39:38.049> that's<00:39:38.619> super<00:39:39.189> cool<00:39:39.399> and<00:39:39.459> in<00:39:39.849> fact<00:39:40.029> it 00:39:40.349 --> 00:39:40.359 align:start position:0% stream that's super cool and in fact it 00:39:40.359 --> 00:39:42.779 align:start position:0% stream that's super cool and in fact it needs<00:39:40.629> to<00:39:40.929> happen<00:39:41.109> please<00:39:41.619> do<00:39:41.889> and<00:39:42.189> we're 00:39:42.779 --> 00:39:42.789 align:start position:0% needs to happen please do and we're 00:39:42.789 --> 00:39:44.459 align:start position:0% needs to happen please do and we're gonna<00:39:42.849> see<00:39:43.149> all<00:39:43.539> of<00:39:43.569> these<00:39:43.809> alternative 00:39:44.459 --> 00:39:44.469 align:start position:0% gonna see all of these alternative 00:39:44.469 --> 00:39:46.829 align:start position:0% gonna see all of these alternative execution<00:39:45.099> engine<00:39:45.429> constructions<00:39:46.329> probably 00:39:46.829 --> 00:39:46.839 align:start position:0% execution engine constructions probably 00:39:46.839 --> 00:39:48.989 align:start position:0% execution engine constructions probably pop<00:39:47.049> up<00:39:47.229> very<00:39:47.409> soon<00:39:47.619> but<00:39:48.009> we're<00:39:48.159> like<00:39:48.339> getting 00:39:48.989 --> 00:39:48.999 align:start position:0% pop up very soon but we're like getting 00:39:48.999 --> 00:39:50.639 align:start position:0% pop up very soon but we're like getting a<00:39:49.089> theorem<00:39:49.359> down<00:39:49.569> to<00:39:49.779> its<00:39:49.899> essence<00:39:50.259> which<00:39:50.559> is 00:39:50.639 --> 00:39:50.649 align:start position:0% a theorem down to its essence which is 00:39:50.649 --> 00:39:52.739 align:start position:0% a theorem down to its essence which is very<00:39:50.829> exciting<00:39:51.189> so<00:39:51.369> you're<00:39:52.299> basically<00:39:52.599> saying 00:39:52.739 --> 00:39:52.749 align:start position:0% very exciting so you're basically saying 00:39:52.749 --> 00:39:53.580 align:start position:0% very exciting so you're basically saying when<00:39:53.259> the<00:39:53.379> bay 00:39:53.580 --> 00:39:53.590 align:start position:0% when the bay 00:39:53.590 --> 00:39:55.470 align:start position:0% when the bay becomes<00:39:54.130> cheap<00:39:54.430> enough<00:39:54.670> we<00:39:54.850> can<00:39:55.030> use<00:39:55.180> plasma 00:39:55.470 --> 00:39:55.480 align:start position:0% becomes cheap enough we can use plasma 00:39:55.480 --> 00:39:59.730 align:start position:0% becomes cheap enough we can use plasma to<00:39:55.840> absorb<00:39:56.230> other<00:39:56.440> chains<00:39:58.140> no<00:39:59.140> you<00:39:59.290> can<00:39:59.560> just 00:39:59.730 --> 00:39:59.740 align:start position:0% to absorb other chains no you can just 00:39:59.740 --> 00:40:01.860 align:start position:0% to absorb other chains no you can just make<00:39:59.890> fancy<00:40:00.400> constructions<00:40:00.910> with<00:40:01.060> plasma<00:40:01.330> VM 00:40:01.860 --> 00:40:01.870 align:start position:0% make fancy constructions with plasma VM 00:40:01.870 --> 00:40:04.170 align:start position:0% make fancy constructions with plasma VM yeah<00:40:02.320> something<00:40:02.800> like<00:40:02.830> this<00:40:03.130> Justin<00:40:03.910> needs<00:40:04.060> a 00:40:04.170 --> 00:40:04.180 align:start position:0% yeah something like this Justin needs a 00:40:04.180 --> 00:40:05.700 align:start position:0% yeah something like this Justin needs a data<00:40:04.390> stream<00:40:04.690> and<00:40:04.930> publish<00:40:05.200> everything<00:40:05.500> on 00:40:05.700 --> 00:40:05.710 align:start position:0% data stream and publish everything on 00:40:05.710 --> 00:40:07.200 align:start position:0% data stream and publish everything on the<00:40:05.770> chain<00:40:05.980> no<00:40:06.130> data<00:40:06.370> availability<00:40:06.730> problem 00:40:07.200 --> 00:40:07.210 align:start position:0% the chain no data availability problem 00:40:07.210 --> 00:40:10.440 align:start position:0% the chain no data availability problem whatsoever<00:40:07.890> actually<00:40:08.890> actually<00:40:09.070> I<00:40:09.270> like<00:40:10.270> I'm 00:40:10.440 --> 00:40:10.450 align:start position:0% whatsoever actually actually I like I'm 00:40:10.450 --> 00:40:12.210 align:start position:0% whatsoever actually actually I like I'm really<00:40:10.570> excited<00:40:10.660> about<00:40:11.050> the<00:40:11.350> data 00:40:12.210 --> 00:40:12.220 align:start position:0% really excited about the data 00:40:12.220 --> 00:40:14.790 align:start position:0% really excited about the data availability<00:40:12.580> thing<00:40:13.060> but<00:40:13.270> like<00:40:13.440> from<00:40:14.440> a<00:40:14.530> text 00:40:14.790 --> 00:40:14.800 align:start position:0% availability thing but like from a text 00:40:14.800 --> 00:40:16.200 align:start position:0% availability thing but like from a text on<00:40:14.920> in<00:40:15.040> front<00:40:15.130> of<00:40:15.250> you<00:40:15.370> like<00:40:15.430> like<00:40:15.820> they've 00:40:16.200 --> 00:40:16.210 align:start position:0% on in front of you like like they've 00:40:16.210 --> 00:40:18.150 align:start position:0% on in front of you like like they've been<00:40:16.240> called<00:40:16.540> data<00:40:16.720> layer<00:40:17.470> to<00:40:17.650> execution 00:40:18.150 --> 00:40:18.160 align:start position:0% been called data layer to execution 00:40:18.160 --> 00:40:20.400 align:start position:0% been called data layer to execution engines<00:40:18.460> before<00:40:18.760> and<00:40:19.060> it's<00:40:19.810> basically<00:40:20.200> like<00:40:20.350> a 00:40:20.400 --> 00:40:20.410 align:start position:0% engines before and it's basically like a 00:40:20.410 --> 00:40:22.950 align:start position:0% engines before and it's basically like a mechanism<00:40:20.800> which<00:40:21.130> relies<00:40:21.580> on<00:40:21.660> are<00:40:22.660> at<00:40:22.810> the 00:40:22.950 --> 00:40:22.960 align:start position:0% mechanism which relies on are at the 00:40:22.960 --> 00:40:30.260 align:start position:0% mechanism which relies on are at the root<00:40:23.140> chain<00:40:23.350> for<00:40:24.090> for<00:40:25.090> for<00:40:25.660> data<00:40:25.840> availability 00:40:30.260 --> 00:40:30.270 align:start position:0% 00:40:30.270 --> 00:40:32.670 align:start position:0% yeah<00:40:31.270> so<00:40:31.480> like<00:40:31.630> we<00:40:32.140> could<00:40:32.320> call<00:40:32.440> it<00:40:32.530> plasma 00:40:32.670 --> 00:40:32.680 align:start position:0% yeah so like we could call it plasma 00:40:32.680 --> 00:40:34.530 align:start position:0% yeah so like we could call it plasma everyone<00:40:33.130> but<00:40:33.340> like<00:40:33.460> it's<00:40:33.640> it<00:40:33.880> is<00:40:34.030> it<00:40:34.240> is<00:40:34.330> used 00:40:34.530 --> 00:40:34.540 align:start position:0% everyone but like it's it is it is used 00:40:34.540 --> 00:40:35.970 align:start position:0% everyone but like it's it is it is used to<00:40:34.630> do<00:40:34.750> I<00:40:34.780> think<00:40:35.170> keep<00:40:35.320> a<00:40:35.410> distinction<00:40:35.740> between 00:40:35.970 --> 00:40:35.980 align:start position:0% to do I think keep a distinction between 00:40:35.980 --> 00:40:38.040 align:start position:0% to do I think keep a distinction between things<00:40:36.460> like<00:40:36.520> plasma<00:40:36.760> cache<00:40:37.090> which<00:40:37.330> which 00:40:38.040 --> 00:40:38.050 align:start position:0% things like plasma cache which which 00:40:38.050 --> 00:40:40.520 align:start position:0% things like plasma cache which which don't<00:40:38.260> rely<00:40:38.500> which<00:40:38.890> don't<00:40:39.070> rely<00:40:39.250> on<00:40:39.280> that<00:40:39.400> and 00:40:40.520 --> 00:40:40.530 align:start position:0% don't rely which don't rely on that and 00:40:40.530 --> 00:40:46.260 align:start position:0% don't rely which don't rely on that and and<00:40:41.530> things<00:40:41.770> which<00:40:41.920> do<00:40:42.330> yeah<00:40:44.940> yeah<00:40:45.940> roll<00:40:46.120> up 00:40:46.260 --> 00:40:46.270 align:start position:0% and things which do yeah yeah roll up 00:40:46.270 --> 00:40:47.760 align:start position:0% and things which do yeah yeah roll up would<00:40:46.450> be<00:40:46.600> an<00:40:46.780> example<00:40:47.170> of<00:40:47.410> something<00:40:47.650> that 00:40:47.760 --> 00:40:47.770 align:start position:0% would be an example of something that 00:40:47.770 --> 00:40:50.760 align:start position:0% would be an example of something that relies<00:40:48.190> on<00:40:48.540> the<00:40:49.540> theorem<00:40:50.440> for<00:40:50.590> data 00:40:50.760 --> 00:40:50.770 align:start position:0% relies on the theorem for data 00:40:50.770 --> 00:40:54.960 align:start position:0% relies on the theorem for data availability<00:40:53.160> all<00:40:54.160> right<00:40:54.310> so<00:40:54.670> I<00:40:54.700> want<00:40:54.940> to 00:40:54.960 --> 00:40:54.970 align:start position:0% availability all right so I want to 00:40:54.970 --> 00:41:01.340 align:start position:0% availability all right so I want to start<00:40:55.180> an<00:40:55.330> argument 00:41:01.340 --> 00:41:01.350 align:start position:0% 00:41:01.350 --> 00:41:04.980 align:start position:0% Thanks<00:41:02.380> so<00:41:03.250> my<00:41:03.370> question<00:41:03.700> is<00:41:03.790> you<00:41:04.450> mentioned<00:41:04.480> a 00:41:04.980 --> 00:41:04.990 align:start position:0% Thanks so my question is you mentioned a 00:41:04.990 --> 00:41:06.360 align:start position:0% Thanks so my question is you mentioned a little<00:41:05.140> bit<00:41:05.260> earlier<00:41:05.410> about<00:41:05.680> the<00:41:05.860> original 00:41:06.360 --> 00:41:06.370 align:start position:0% little bit earlier about the original 00:41:06.370 --> 00:41:09.000 align:start position:0% little bit earlier about the original plasma<00:41:06.700> paper<00:41:06.910> and<00:41:07.900> how<00:41:08.170> you<00:41:08.770> use<00:41:08.890> the 00:41:09.000 --> 00:41:09.010 align:start position:0% plasma paper and how you use the 00:41:09.010 --> 00:41:11.610 align:start position:0% plasma paper and how you use the MapReduce<00:41:09.780> mechanism<00:41:10.780> and<00:41:10.930> how<00:41:11.020> that<00:41:11.320> doesn't 00:41:11.610 --> 00:41:11.620 align:start position:0% MapReduce mechanism and how that doesn't 00:41:11.620 --> 00:41:13.740 align:start position:0% MapReduce mechanism and how that doesn't necessarily<00:41:11.830> fit<00:41:12.340> into<00:41:12.640> most<00:41:12.910> use<00:41:13.120> case<00:41:13.360> I'm 00:41:13.740 --> 00:41:13.750 align:start position:0% necessarily fit into most use case I'm 00:41:13.750 --> 00:41:15.150 align:start position:0% necessarily fit into most use case I'm kind<00:41:13.960> of<00:41:13.990> curious<00:41:14.200> like<00:41:14.410> what<00:41:14.770> kind<00:41:14.950> of<00:41:15.040> use 00:41:15.150 --> 00:41:15.160 align:start position:0% kind of curious like what kind of use 00:41:15.160 --> 00:41:17.670 align:start position:0% kind of curious like what kind of use case<00:41:15.370> will<00:41:15.790> fit<00:41:16.150> into<00:41:16.300> it's<00:41:17.290> still<00:41:17.530> like 00:41:17.670 --> 00:41:17.680 align:start position:0% case will fit into it's still like 00:41:17.680 --> 00:41:18.990 align:start position:0% case will fit into it's still like necessary<00:41:18.100> like<00:41:18.340> for<00:41:18.460> example<00:41:18.790> we<00:41:18.850> deal<00:41:18.970> with 00:41:18.990 --> 00:41:19.000 align:start position:0% necessary like for example we deal with 00:41:19.000 --> 00:41:20.880 align:start position:0% necessary like for example we deal with time<00:41:19.330> series<00:41:19.600> data<00:41:19.750> would<00:41:20.140> that<00:41:20.290> you<00:41:20.800> know 00:41:20.880 --> 00:41:20.890 align:start position:0% time series data would that you know 00:41:20.890 --> 00:41:23.280 align:start position:0% time series data would that you know it's<00:41:21.070> that<00:41:21.190> kind<00:41:21.460> of<00:41:21.520> that<00:41:21.640> a<00:41:21.700> use<00:41:21.910> case<00:41:22.140> in<00:41:23.140> a 00:41:23.280 --> 00:41:23.290 align:start position:0% it's that kind of that a use case in a 00:41:23.290 --> 00:41:25.920 align:start position:0% it's that kind of that a use case in a secondary<00:41:24.010> question<00:41:24.460> the<00:41:25.420> original<00:41:25.750> paper 00:41:25.920 --> 00:41:25.930 align:start position:0% secondary question the original paper 00:41:25.930 --> 00:41:28.500 align:start position:0% secondary question the original paper has<00:41:26.200> like<00:41:26.380> multiple<00:41:26.770> layers<00:41:26.980> and<00:41:27.310> is<00:41:28.270> that 00:41:28.500 --> 00:41:28.510 align:start position:0% has like multiple layers and is that 00:41:28.510 --> 00:41:30.600 align:start position:0% has like multiple layers and is that layering<00:41:28.720> just<00:41:29.350> for<00:41:29.830> the<00:41:29.950> mass<00:41:30.160> exit 00:41:30.600 --> 00:41:30.610 align:start position:0% layering just for the mass exit 00:41:30.610 --> 00:41:32.250 align:start position:0% layering just for the mass exit mechanism<00:41:31.120> is<00:41:31.240> that<00:41:31.270> is<00:41:31.540> that<00:41:31.690> layering<00:41:31.840> even 00:41:32.250 --> 00:41:32.260 align:start position:0% mechanism is that is that layering even 00:41:32.260 --> 00:41:35.100 align:start position:0% mechanism is that is that layering even necessary<00:41:32.680> anymore<00:41:32.890> so<00:41:33.850> basically<00:41:34.570> right<00:41:34.810> now 00:41:35.100 --> 00:41:35.110 align:start position:0% necessary anymore so basically right now 00:41:35.110 --> 00:41:37.020 align:start position:0% necessary anymore so basically right now we're<00:41:35.440> not<00:41:35.680> even<00:41:36.160> at<00:41:36.310> that<00:41:36.550> stage<00:41:36.730> the 00:41:37.020 --> 00:41:37.030 align:start position:0% we're not even at that stage the 00:41:37.030 --> 00:41:38.670 align:start position:0% we're not even at that stage the presumption<00:41:37.390> is<00:41:37.660> I<00:41:37.870> think<00:41:37.930> what<00:41:38.530> we're 00:41:38.670 --> 00:41:38.680 align:start position:0% presumption is I think what we're 00:41:38.680 --> 00:41:40.950 align:start position:0% presumption is I think what we're realizing<00:41:39.070> is<00:41:39.550> the<00:41:39.850> scalability<00:41:40.480> benefits 00:41:40.950 --> 00:41:40.960 align:start position:0% realizing is the scalability benefits 00:41:40.960 --> 00:41:43.230 align:start position:0% realizing is the scalability benefits that<00:41:41.920> you<00:41:42.070> can<00:41:42.100> get<00:41:42.340> simply<00:41:42.700> by<00:41:42.790> having<00:41:42.940> one 00:41:43.230 --> 00:41:43.240 align:start position:0% that you can get simply by having one 00:41:43.240 --> 00:41:45.240 align:start position:0% that you can get simply by having one plasma<00:41:43.630> chain<00:41:43.810> is<00:41:44.020> probably<00:41:44.860> going<00:41:45.100> to<00:41:45.160> be 00:41:45.240 --> 00:41:45.250 align:start position:0% plasma chain is probably going to be 00:41:45.250 --> 00:41:46.650 align:start position:0% plasma chain is probably going to be sufficient<00:41:45.700> for<00:41:45.760> the<00:41:46.150> overwhelming<00:41:46.630> use 00:41:46.650 --> 00:41:46.660 align:start position:0% sufficient for the overwhelming use 00:41:46.660 --> 00:41:50.340 align:start position:0% sufficient for the overwhelming use cases<00:41:47.460> the<00:41:48.460> the<00:41:48.880> notion<00:41:49.480> of<00:41:49.570> nesting<00:41:49.990> gives 00:41:50.340 --> 00:41:50.350 align:start position:0% cases the the notion of nesting gives 00:41:50.350 --> 00:41:52.770 align:start position:0% cases the the notion of nesting gives you<00:41:50.560> the<00:41:50.740> benefit<00:41:51.130> of<00:41:51.160> you<00:41:51.580> know<00:41:51.780> scalability 00:41:52.770 --> 00:41:52.780 align:start position:0% you the benefit of you know scalability 00:41:52.780 --> 00:41:54.360 align:start position:0% you the benefit of you know scalability within<00:41:53.170> the<00:41:53.260> context<00:41:53.770> of<00:41:53.890> you<00:41:54.070> know<00:41:54.190> perhaps 00:41:54.360 --> 00:41:54.370 align:start position:0% within the context of you know perhaps 00:41:54.370 --> 00:41:56.240 align:start position:0% within the context of you know perhaps you<00:41:54.700> know<00:41:54.820> you<00:41:54.880> don't<00:41:55.090> want<00:41:55.360> a<00:41:55.450> district 00:41:56.240 --> 00:41:56.250 align:start position:0% you know you don't want a district 00:41:56.250 --> 00:41:58.860 align:start position:0% you know you don't want a district engineering-wise<00:41:57.250> it's<00:41:57.610> a<00:41:57.670> lot<00:41:57.850> easier<00:41:58.090> to 00:41:58.860 --> 00:41:58.870 align:start position:0% engineering-wise it's a lot easier to 00:41:58.870 --> 00:42:00.780 align:start position:0% engineering-wise it's a lot easier to have<00:41:59.200> computation<00:41:59.950> that<00:41:59.980> can<00:42:00.220> fit<00:42:00.400> on<00:42:00.550> one 00:42:00.780 --> 00:42:00.790 align:start position:0% have computation that can fit on one 00:42:00.790 --> 00:42:02.940 align:start position:0% have computation that can fit on one server<00:42:01.090> right<00:42:01.870> that's<00:42:02.050> that's<00:42:02.260> simply<00:42:02.710> like 00:42:02.940 --> 00:42:02.950 align:start position:0% server right that's that's simply like 00:42:02.950 --> 00:42:04.560 align:start position:0% server right that's that's simply like if<00:42:03.190> you<00:42:03.400> ask<00:42:03.550> any<00:42:03.790> distributed<00:42:04.090> systems 00:42:04.560 --> 00:42:04.570 align:start position:0% if you ask any distributed systems 00:42:04.570 --> 00:42:05.910 align:start position:0% if you ask any distributed systems engineer<00:42:04.960> like<00:42:05.140> once 00:42:05.910 --> 00:42:05.920 align:start position:0% engineer like once 00:42:05.920 --> 00:42:07.620 align:start position:0% engineer like once you<00:42:05.980> have<00:42:06.220> you<00:42:06.549> know<00:42:06.579> some<00:42:06.910> state<00:42:07.210> across 00:42:07.620 --> 00:42:07.630 align:start position:0% you have you know some state across 00:42:07.630 --> 00:42:09.150 align:start position:0% you have you know some state across multiple<00:42:07.930> servers<00:42:08.200> the<00:42:08.770> engineering 00:42:09.150 --> 00:42:09.160 align:start position:0% multiple servers the engineering 00:42:09.160 --> 00:42:10.650 align:start position:0% multiple servers the engineering challenge<00:42:09.430> just<00:42:09.579> blows<00:42:09.790> up<00:42:09.819> and<00:42:10.119> that's<00:42:10.329> fine 00:42:10.650 --> 00:42:10.660 align:start position:0% challenge just blows up and that's fine 00:42:10.660 --> 00:42:13.109 align:start position:0% challenge just blows up and that's fine to<00:42:10.869> do<00:42:11.020> if<00:42:11.260> you<00:42:11.589> have<00:42:11.680> no<00:42:11.799> other<00:42:11.920> choice<00:42:12.119> and 00:42:13.109 --> 00:42:13.119 align:start position:0% to do if you have no other choice and 00:42:13.119 --> 00:42:14.970 align:start position:0% to do if you have no other choice and it's<00:42:13.329> sort<00:42:13.510> of<00:42:13.569> a<00:42:13.690> model<00:42:14.079> of<00:42:14.200> how<00:42:14.380> you<00:42:14.440> can<00:42:14.770> do 00:42:14.970 --> 00:42:14.980 align:start position:0% it's sort of a model of how you can do 00:42:14.980 --> 00:42:17.819 align:start position:0% it's sort of a model of how you can do that<00:42:15.359> for<00:42:16.359> a<00:42:16.390> lot<00:42:16.720> of<00:42:16.750> state<00:42:17.020> across<00:42:17.410> different 00:42:17.819 --> 00:42:17.829 align:start position:0% that for a lot of state across different 00:42:17.829 --> 00:42:20.299 align:start position:0% that for a lot of state across different you<00:42:18.099> know<00:42:18.220> uh<00:42:18.420> that<00:42:19.420> that<00:42:19.660> goes<00:42:19.780> beyond<00:42:20.079> that 00:42:20.299 --> 00:42:20.309 align:start position:0% you know uh that that goes beyond that 00:42:20.309 --> 00:42:22.470 align:start position:0% you know uh that that goes beyond that right<00:42:21.309> now<00:42:21.490> the<00:42:21.549> problem<00:42:21.819> sets<00:42:22.180> that<00:42:22.240> we're 00:42:22.470 --> 00:42:22.480 align:start position:0% right now the problem sets that we're 00:42:22.480 --> 00:42:24.780 align:start position:0% right now the problem sets that we're dealing<00:42:22.630> with<00:42:22.869> probably<00:42:23.740> can<00:42:23.890> be<00:42:24.010> done<00:42:24.190> on<00:42:24.460> one 00:42:24.780 --> 00:42:24.790 align:start position:0% dealing with probably can be done on one 00:42:24.790 --> 00:42:26.670 align:start position:0% dealing with probably can be done on one you<00:42:25.210> know<00:42:25.329> high<00:42:25.450> powered<00:42:25.750> server<00:42:25.990> or<00:42:26.319> a<00:42:26.380> set<00:42:26.589> of 00:42:26.670 --> 00:42:26.680 align:start position:0% you know high powered server or a set of 00:42:26.680 --> 00:42:29.339 align:start position:0% you know high powered server or a set of five<00:42:26.799> powered<00:42:27.069> servers<00:42:27.450> or<00:42:28.450> so<00:42:28.900> specifically 00:42:29.339 --> 00:42:29.349 align:start position:0% five powered servers or so specifically 00:42:29.349 --> 00:42:30.809 align:start position:0% five powered servers or so specifically once<00:42:29.650> a<00:42:29.770> high<00:42:29.890> power<00:42:30.099> servers<00:42:30.430> and<00:42:30.579> you<00:42:30.670> can 00:42:30.809 --> 00:42:30.819 align:start position:0% once a high power servers and you can 00:42:30.819 --> 00:42:32.370 align:start position:0% once a high power servers and you can eventually<00:42:30.970> go<00:42:31.420> into<00:42:31.660> a<00:42:31.690> set<00:42:31.930> of<00:42:32.049> high<00:42:32.170> power 00:42:32.370 --> 00:42:32.380 align:start position:0% eventually go into a set of high power 00:42:32.380 --> 00:42:33.900 align:start position:0% eventually go into a set of high power servers<00:42:32.710> by<00:42:32.859> making<00:42:33.130> nested<00:42:33.460> commitments 00:42:33.900 --> 00:42:33.910 align:start position:0% servers by making nested commitments 00:42:33.910 --> 00:42:35.490 align:start position:0% servers by making nested commitments we're<00:42:34.420> not<00:42:34.569> writing<00:42:34.780> another<00:42:35.140> code<00:42:35.290> for<00:42:35.470> that 00:42:35.490 --> 00:42:35.500 align:start position:0% we're not writing another code for that 00:42:35.500 --> 00:42:37.230 align:start position:0% we're not writing another code for that right<00:42:35.770> now<00:42:35.890> simply<00:42:36.130> because<00:42:36.549> or<00:42:36.790> doing<00:42:37.119> any 00:42:37.230 --> 00:42:37.240 align:start position:0% right now simply because or doing any 00:42:37.240 --> 00:42:38.430 align:start position:0% right now simply because or doing any designs<00:42:37.569> for<00:42:37.720> that<00:42:37.780> right<00:42:38.049> now<00:42:38.200> simply 00:42:38.430 --> 00:42:38.440 align:start position:0% designs for that right now simply 00:42:38.440 --> 00:42:41.130 align:start position:0% designs for that right now simply because<00:42:38.890> it's<00:42:39.430> not<00:42:39.760> we're<00:42:40.359> not<00:42:40.480> even<00:42:40.660> seeing<00:42:40.900> a 00:42:41.130 --> 00:42:41.140 align:start position:0% because it's not we're not even seeing a 00:42:41.140 --> 00:42:44.339 align:start position:0% because it's not we're not even seeing a need<00:42:41.380> for<00:42:41.619> that<00:42:41.799> necessarily<00:42:42.930> the<00:42:43.930> the 00:42:44.339 --> 00:42:44.349 align:start position:0% need for that necessarily the the 00:42:44.349 --> 00:42:46.079 align:start position:0% need for that necessarily the the context<00:42:44.920> for<00:42:45.040> the<00:42:45.160> MapReduce<00:42:45.430> construction 00:42:46.079 --> 00:42:46.089 align:start position:0% context for the MapReduce construction 00:42:46.089 --> 00:42:49.049 align:start position:0% context for the MapReduce construction within<00:42:46.299> within<00:42:46.900> that<00:42:47.170> need<00:42:47.470> is<00:42:47.849> within<00:42:48.849> that 00:42:49.049 --> 00:42:49.059 align:start position:0% within within that need is within that 00:42:49.059 --> 00:42:51.589 align:start position:0% within within that need is within that within<00:42:49.299> that<00:42:49.569> within<00:42:49.869> that<00:42:50.049> process<00:42:50.319> is<00:42:50.829> that 00:42:51.589 --> 00:42:51.599 align:start position:0% within that within that process is that 00:42:51.599 --> 00:42:54.569 align:start position:0% within that within that process is that essentially<00:42:52.829> there's<00:42:53.829> a<00:42:53.890> problem<00:42:54.309> in 00:42:54.569 --> 00:42:54.579 align:start position:0% essentially there's a problem in 00:42:54.579 --> 00:42:56.670 align:start position:0% essentially there's a problem in relation<00:42:55.059> to<00:42:55.089> a<00:42:55.660> lot<00:42:55.900> of<00:42:56.020> you<00:42:56.109> TXO<00:42:56.530> like 00:42:56.670 --> 00:42:56.680 align:start position:0% relation to a lot of you TXO like 00:42:56.680 --> 00:42:58.770 align:start position:0% relation to a lot of you TXO like instructions<00:42:57.040> whereby<00:42:58.030> you<00:42:58.089> txl<00:42:58.630> like 00:42:58.770 --> 00:42:58.780 align:start position:0% instructions whereby you txl like 00:42:58.780 --> 00:43:01.020 align:start position:0% instructions whereby you txl like instructions<00:42:59.109> don't<00:43:00.069> do<00:43:00.250> global<00:43:00.640> state<00:43:00.819> that 00:43:01.020 --> 00:43:01.030 align:start position:0% instructions don't do global state that 00:43:01.030 --> 00:43:03.599 align:start position:0% instructions don't do global state that well<00:43:01.240> it's<00:43:01.750> sort<00:43:01.900> of<00:43:02.049> like<00:43:02.230> in<00:43:03.160> terms<00:43:03.369> of<00:43:03.490> data 00:43:03.599 --> 00:43:03.609 align:start position:0% well it's sort of like in terms of data 00:43:03.609 --> 00:43:04.950 align:start position:0% well it's sort of like in terms of data structures<00:43:04.030> if<00:43:04.180> you<00:43:04.270> can<00:43:04.390> only<00:43:04.480> do<00:43:04.690> linked 00:43:04.950 --> 00:43:04.960 align:start position:0% structures if you can only do linked 00:43:04.960 --> 00:43:06.839 align:start position:0% structures if you can only do linked lists<00:43:05.260> and<00:43:05.440> you<00:43:05.829> can't<00:43:06.069> do<00:43:06.220> maps<00:43:06.430> or<00:43:06.609> a<00:43:06.640> race 00:43:06.839 --> 00:43:06.849 align:start position:0% lists and you can't do maps or a race 00:43:06.849 --> 00:43:09.059 align:start position:0% lists and you can't do maps or a race right<00:43:07.150> like<00:43:07.329> it's<00:43:07.510> sort<00:43:07.690> of<00:43:07.750> like<00:43:07.960> well<00:43:08.260> what 00:43:09.059 --> 00:43:09.069 align:start position:0% right like it's sort of like well what 00:43:09.069 --> 00:43:10.950 align:start position:0% right like it's sort of like well what can<00:43:09.220> you<00:43:09.280> really<00:43:09.549> do<00:43:09.819> with<00:43:10.030> this<00:43:10.180> right<00:43:10.450> when 00:43:10.950 --> 00:43:10.960 align:start position:0% can you really do with this right when 00:43:10.960 --> 00:43:12.150 align:start position:0% can you really do with this right when you're<00:43:11.079> dealing<00:43:11.319> with<00:43:11.500> global<00:43:11.740> State 00:43:12.150 --> 00:43:12.160 align:start position:0% you're dealing with global State 00:43:12.160 --> 00:43:13.470 align:start position:0% you're dealing with global State essentially<00:43:12.730> you<00:43:12.819> need<00:43:12.970> to<00:43:13.059> have<00:43:13.180> some<00:43:13.329> type 00:43:13.470 --> 00:43:13.480 align:start position:0% essentially you need to have some type 00:43:13.480 --> 00:43:14.940 align:start position:0% essentially you need to have some type of<00:43:13.510> you<00:43:13.809> know<00:43:13.839> global<00:43:14.380> agreement<00:43:14.890> or 00:43:14.940 --> 00:43:14.950 align:start position:0% of you know global agreement or 00:43:14.950 --> 00:43:16.920 align:start position:0% of you know global agreement or consensus<00:43:15.490> so<00:43:16.000> it's<00:43:16.119> a<00:43:16.240> statement<00:43:16.630> that<00:43:16.809> you 00:43:16.920 --> 00:43:16.930 align:start position:0% consensus so it's a statement that you 00:43:16.930 --> 00:43:19.500 align:start position:0% consensus so it's a statement that you basically<00:43:17.470> have<00:43:17.799> the<00:43:18.339> plasma<00:43:18.549> chain<00:43:19.000> be 00:43:19.500 --> 00:43:19.510 align:start position:0% basically have the plasma chain be 00:43:19.510 --> 00:43:21.510 align:start position:0% basically have the plasma chain be processing<00:43:19.930> global<00:43:20.349> consensus<00:43:20.859> and<00:43:21.069> that's 00:43:21.510 --> 00:43:21.520 align:start position:0% processing global consensus and that's 00:43:21.520 --> 00:43:23.220 align:start position:0% processing global consensus and that's basically<00:43:21.910> what<00:43:22.270> what<00:43:22.630> we're<00:43:22.809> doing<00:43:23.109> right 00:43:23.220 --> 00:43:23.230 align:start position:0% basically what what we're doing right 00:43:23.230 --> 00:43:25.260 align:start position:0% basically what what we're doing right now<00:43:24.030> yeah 00:43:25.260 --> 00:43:25.270 align:start position:0% now yeah 00:43:25.270 --> 00:43:27.299 align:start position:0% now yeah regarding<00:43:25.690> the<00:43:25.839> mapreduces<00:43:26.470> i<00:43:26.680> well<00:43:27.010> maybe<00:43:27.220> I 00:43:27.299 --> 00:43:27.309 align:start position:0% regarding the mapreduces i well maybe I 00:43:27.309 --> 00:43:28.650 align:start position:0% regarding the mapreduces i well maybe I shouldn't<00:43:27.579> mention<00:43:27.790> this<00:43:28.030> construction<00:43:28.540> how 00:43:28.650 --> 00:43:28.660 align:start position:0% shouldn't mention this construction how 00:43:28.660 --> 00:43:30.180 align:start position:0% shouldn't mention this construction how we<00:43:28.720> can<00:43:28.900> offload<00:43:29.049> the<00:43:29.290> snarky<00:43:29.650> execution<00:43:30.099> of 00:43:30.180 --> 00:43:30.190 align:start position:0% we can offload the snarky execution of 00:43:30.190 --> 00:43:32.910 align:start position:0% we can offload the snarky execution of chain<00:43:30.400> but<00:43:31.030> in<00:43:31.299> principle<00:43:31.990> as<00:43:32.650> Kelvin 00:43:32.910 --> 00:43:32.920 align:start position:0% chain but in principle as Kelvin 00:43:32.920 --> 00:43:34.799 align:start position:0% chain but in principle as Kelvin mentions<00:43:33.400> there<00:43:33.549> should<00:43:33.790> be<00:43:33.940> either<00:43:34.210> clear 00:43:34.799 --> 00:43:34.809 align:start position:0% mentions there should be either clear 00:43:34.809 --> 00:43:37.680 align:start position:0% mentions there should be either clear ownership<00:43:35.650> of<00:43:35.770> state<00:43:36.010> which<00:43:36.880> you<00:43:37.000> can<00:43:37.150> exit<00:43:37.540> in 00:43:37.680 --> 00:43:37.690 align:start position:0% ownership of state which you can exit in 00:43:37.690 --> 00:43:40.380 align:start position:0% ownership of state which you can exit in in<00:43:38.079> most<00:43:38.530> of<00:43:38.740> our<00:43:38.829> cases<00:43:39.099> for<00:43:39.460> now<00:43:39.730> the<00:43:40.180> state 00:43:40.380 --> 00:43:40.390 align:start position:0% in most of our cases for now the state 00:43:40.390 --> 00:43:43.770 align:start position:0% in most of our cases for now the state is<00:43:40.420> a<00:43:40.599> value<00:43:40.900> if<00:43:41.680> you<00:43:41.890> don't<00:43:42.299> if<00:43:43.299> you<00:43:43.420> state<00:43:43.660> is 00:43:43.770 --> 00:43:43.780 align:start position:0% is a value if you don't if you state is 00:43:43.780 --> 00:43:46.380 align:start position:0% is a value if you don't if you state is something<00:43:44.109> abstract<00:43:44.500> which<00:43:45.010> you<00:43:45.640> can<00:43:45.819> live 00:43:46.380 --> 00:43:46.390 align:start position:0% something abstract which you can live 00:43:46.390 --> 00:43:49.289 align:start position:0% something abstract which you can live with<00:43:46.690> having<00:43:47.380> exiting<00:43:48.010> like<00:43:48.490> the<00:43:48.730> previous 00:43:49.289 --> 00:43:49.299 align:start position:0% with having exiting like the previous 00:43:49.299 --> 00:43:51.390 align:start position:0% with having exiting like the previous state<00:43:49.660> at<00:43:49.900> some<00:43:50.049> point<00:43:50.380> and<00:43:50.650> just<00:43:50.920> saying<00:43:51.130> well 00:43:51.390 --> 00:43:51.400 align:start position:0% state at some point and just saying well 00:43:51.400 --> 00:43:53.549 align:start position:0% state at some point and just saying well this<00:43:51.579> is<00:43:51.760> a<00:43:51.790> previous<00:43:52.240> one<00:43:52.630> which<00:43:53.200> is<00:43:53.349> the<00:43:53.440> last 00:43:53.549 --> 00:43:53.559 align:start position:0% this is a previous one which is the last 00:43:53.559 --> 00:43:55.260 align:start position:0% this is a previous one which is the last well<00:43:53.859> it<00:43:54.010> and<00:43:54.190> I<00:43:54.430> can<00:43:54.609> just<00:43:54.640> afloat<00:43:54.970> all<00:43:55.150> the 00:43:55.260 --> 00:43:55.270 align:start position:0% well it and I can just afloat all the 00:43:55.270 --> 00:43:57.390 align:start position:0% well it and I can just afloat all the computation<00:43:55.809> I'm<00:43:56.020> fine<00:43:56.380> with<00:43:56.589> exiting<00:43:57.220> like 00:43:57.390 --> 00:43:57.400 align:start position:0% computation I'm fine with exiting like 00:43:57.400 --> 00:43:59.220 align:start position:0% computation I'm fine with exiting like the<00:43:57.549> previous<00:43:57.819> like<00:43:58.420> the<00:43:58.540> last<00:43:58.750> valid<00:43:59.049> state 00:43:59.220 --> 00:43:59.230 align:start position:0% the previous like the last valid state 00:43:59.230 --> 00:44:00.690 align:start position:0% the previous like the last valid state on<00:43:59.380> chain<00:43:59.619> and<00:43:59.799> doing<00:43:59.950> something<00:44:00.160> with<00:44:00.309> it<00:44:00.430> in 00:44:00.690 --> 00:44:00.700 align:start position:0% on chain and doing something with it in 00:44:00.700 --> 00:44:02.400 align:start position:0% on chain and doing something with it in a<00:44:00.760> worst-case<00:44:01.000> scenario<00:44:01.119> then<00:44:01.869> you<00:44:01.990> can<00:44:02.140> put 00:44:02.400 --> 00:44:02.410 align:start position:0% a worst-case scenario then you can put 00:44:02.410 --> 00:44:04.200 align:start position:0% a worst-case scenario then you can put the<00:44:02.530> computation<00:44:03.040> inside<00:44:03.369> so<00:44:03.880> you<00:44:03.940> can<00:44:04.059> make 00:44:04.200 --> 00:44:04.210 align:start position:0% the computation inside so you can make 00:44:04.210 --> 00:44:05.970 align:start position:0% the computation inside so you can make it<00:44:04.329> like<00:44:04.480> offloading<00:44:05.170> computation<00:44:05.530> of<00:44:05.680> change 00:44:05.970 --> 00:44:05.980 align:start position:0% it like offloading computation of change 00:44:05.980 --> 00:44:08.130 align:start position:0% it like offloading computation of change the<00:44:06.160> same<00:44:06.369> ways<00:44:06.520> as<00:44:06.780> everyone<00:44:07.780> want<00:44:07.960> to<00:44:08.049> do 00:44:08.130 --> 00:44:08.140 align:start position:0% the same ways as everyone want to do 00:44:08.140 --> 00:44:10.950 align:start position:0% the same ways as everyone want to do with<00:44:08.290> the<00:44:08.410> snarks<00:44:09.000> verify<00:44:10.000> it<00:44:10.059> on<00:44:10.299> chain<00:44:10.660> with 00:44:10.950 --> 00:44:10.960 align:start position:0% with the snarks verify it on chain with 00:44:10.960 --> 00:44:12.990 align:start position:0% with the snarks verify it on chain with starts<00:44:11.349> verify<00:44:11.740> it<00:44:11.799> and<00:44:12.010> chain<00:44:12.250> you<00:44:12.730> can<00:44:12.880> do 00:44:12.990 --> 00:44:13.000 align:start position:0% starts verify it and chain you can do 00:44:13.000 --> 00:44:13.770 align:start position:0% starts verify it and chain you can do something<00:44:13.329> similar 00:44:13.770 --> 00:44:13.780 align:start position:0% something similar 00:44:13.780 --> 00:44:16.589 align:start position:0% something similar it's<00:44:14.170> the<00:44:14.680> idea<00:44:14.950> is<00:44:15.130> not<00:44:15.579> huge<00:44:15.910> and<00:44:16.180> you<00:44:16.450> can 00:44:16.589 --> 00:44:16.599 align:start position:0% it's the idea is not huge and you can 00:44:16.599 --> 00:44:19.349 align:start position:0% it's the idea is not huge and you can just<00:44:16.780> try<00:44:17.230> to<00:44:17.290> make<00:44:17.500> it<00:44:17.530> but<00:44:18.280> very<00:44:18.730> limited<00:44:18.940> set 00:44:19.349 --> 00:44:19.359 align:start position:0% just try to make it but very limited set 00:44:19.359 --> 00:44:19.710 align:start position:0% just try to make it but very limited set of<00:44:19.390> key 00:44:19.710 --> 00:44:19.720 align:start position:0% of key 00:44:19.720 --> 00:44:22.050 align:start position:0% of key patience<00:44:20.020> which<00:44:20.140> you<00:44:20.260> can<00:44:20.380> use<00:44:21.099> and<00:44:21.550> it's<00:44:21.940> like 00:44:22.050 --> 00:44:22.060 align:start position:0% patience which you can use and it's like 00:44:22.060 --> 00:44:25.190 align:start position:0% patience which you can use and it's like maybe<00:44:22.599> games<00:44:22.900> can<00:44:23.109> be<00:44:23.230> done<00:44:23.800> this<00:44:23.920> way<00:44:24.130> well 00:44:25.190 --> 00:44:25.200 align:start position:0% maybe games can be done this way well 00:44:25.200 --> 00:44:28.099 align:start position:0% maybe games can be done this way well games<00:44:26.200> can<00:44:26.410> be<00:44:26.500> done<00:44:26.650> or<00:44:26.770> sorry<00:44:26.980> at<00:44:27.130> least 00:44:28.099 --> 00:44:28.109 align:start position:0% games can be done or sorry at least 00:44:28.109 --> 00:44:31.470 align:start position:0% games can be done or sorry at least sorry<00:44:29.250> cool<00:44:30.250> all<00:44:30.760> right<00:44:30.910> five<00:44:31.150> second 00:44:31.470 --> 00:44:31.480 align:start position:0% sorry cool all right five second 00:44:31.480 --> 00:44:34.170 align:start position:0% sorry cool all right five second argument<00:44:31.599> plasma<00:44:32.470> naming<00:44:32.859> scheme<00:44:33.190> is<00:44:33.550> bad<00:44:33.849> and 00:44:34.170 --> 00:44:34.180 align:start position:0% argument plasma naming scheme is bad and 00:44:34.180 --> 00:44:39.809 align:start position:0% argument plasma naming scheme is bad and you<00:44:34.329> should<00:44:34.540> feel<00:44:34.750> bad<00:44:37.619> so<00:44:38.619> so<00:44:38.950> my<00:44:39.160> you<00:44:39.550> know<00:44:39.640> we 00:44:39.809 --> 00:44:39.819 align:start position:0% you should feel bad so so my you know we 00:44:39.819 --> 00:44:42.960 align:start position:0% you should feel bad so so my you know we had<00:44:40.150> this<00:44:40.300> kind<00:44:40.780> of<00:44:40.869> meme<00:44:41.700> naming<00:44:42.700> scheme 00:44:42.960 --> 00:44:42.970 align:start position:0% had this kind of meme naming scheme 00:44:42.970 --> 00:44:45.870 align:start position:0% had this kind of meme naming scheme right<00:44:43.210> where<00:44:43.450> we<00:44:43.599> went<00:44:43.990> off<00:44:44.130> Bitcoin<00:44:45.130> Forks<00:44:45.579> so 00:44:45.870 --> 00:44:45.880 align:start position:0% right where we went off Bitcoin Forks so 00:44:45.880 --> 00:44:49.109 align:start position:0% right where we went off Bitcoin Forks so we<00:44:45.970> had<00:44:46.089> plasma<00:44:46.630> cash<00:44:46.869> plasma<00:44:47.530> XT<00:44:47.970> what<00:44:48.970> else 00:44:49.109 --> 00:44:49.119 align:start position:0% we had plasma cash plasma XT what else 00:44:49.119 --> 00:44:51.990 align:start position:0% we had plasma cash plasma XT what else did<00:44:49.270> we<00:44:49.300> have<00:44:49.420> plasma<00:44:49.960> gold<00:44:50.609> plasma<00:44:51.609> and<00:44:51.790> G 00:44:51.990 --> 00:44:52.000 align:start position:0% did we have plasma gold plasma and G 00:44:52.000 --> 00:44:54.660 align:start position:0% did we have plasma gold plasma and G whatever<00:44:52.690> right<00:44:52.960> so<00:44:53.200> and<00:44:54.130> it's<00:44:54.430> totally 00:44:54.660 --> 00:44:54.670 align:start position:0% whatever right so and it's totally 00:44:54.670 --> 00:44:56.640 align:start position:0% whatever right so and it's totally involved<00:44:54.970> into<00:44:55.240> this<00:44:55.329> problem<00:44:55.599> where<00:44:56.109> in 00:44:56.640 --> 00:44:56.650 align:start position:0% involved into this problem where in 00:44:56.650 --> 00:44:59.069 align:start position:0% involved into this problem where in order<00:44:57.099> to<00:44:57.220> be<00:44:57.640> I<00:44:58.000> mean<00:44:58.240> the<00:44:58.690> idea<00:44:58.869> is<00:44:58.900> like 00:44:59.069 --> 00:44:59.079 align:start position:0% order to be I mean the idea is like 00:44:59.079 --> 00:45:02.250 align:start position:0% order to be I mean the idea is like capture<00:44:59.890> this<00:45:00.880> design<00:45:01.480> that<00:45:01.510> you've<00:45:01.900> created 00:45:02.250 --> 00:45:02.260 align:start position:0% capture this design that you've created 00:45:02.260 --> 00:45:04.980 align:start position:0% capture this design that you've created with<00:45:02.680> one<00:45:03.280> name<00:45:03.640> and<00:45:03.910> refer<00:45:04.510> to<00:45:04.630> the<00:45:04.720> design 00:45:04.980 --> 00:45:04.990 align:start position:0% with one name and refer to the design 00:45:04.990 --> 00:45:07.650 align:start position:0% with one name and refer to the design with<00:45:05.109> that<00:45:05.140> name<00:45:05.819> and<00:45:06.819> so<00:45:07.030> now<00:45:07.180> it's<00:45:07.390> been<00:45:07.510> this 00:45:07.650 --> 00:45:07.660 align:start position:0% with that name and so now it's been this 00:45:07.660 --> 00:45:10.050 align:start position:0% with that name and so now it's been this thing<00:45:07.900> where<00:45:08.079> like<00:45:08.369> incremental<00:45:09.369> benefits 00:45:10.050 --> 00:45:10.060 align:start position:0% thing where like incremental benefits 00:45:10.060 --> 00:45:12.089 align:start position:0% thing where like incremental benefits like<00:45:10.210> tiny<00:45:10.540> little<00:45:10.680> improvements<00:45:11.680> are 00:45:12.089 --> 00:45:12.099 align:start position:0% like tiny little improvements are 00:45:12.099 --> 00:45:14.099 align:start position:0% like tiny little improvements are allocated<00:45:12.730> their<00:45:12.849> own<00:45:13.000> entire<00:45:13.540> name<00:45:13.839> which 00:45:14.099 --> 00:45:14.109 align:start position:0% allocated their own entire name which 00:45:14.109 --> 00:45:16.740 align:start position:0% allocated their own entire name which makes<00:45:14.349> you<00:45:14.770> know<00:45:14.859> kind<00:45:15.280> of<00:45:15.339> no<00:45:15.460> sense<00:45:15.700> and<00:45:15.849> and 00:45:16.740 --> 00:45:16.750 align:start position:0% makes you know kind of no sense and and 00:45:16.750 --> 00:45:20.120 align:start position:0% makes you know kind of no sense and and and<00:45:17.230> then<00:45:17.349> also<00:45:17.560> like<00:45:17.980> people<00:45:18.790> have<00:45:19.150> been 00:45:20.120 --> 00:45:20.130 align:start position:0% and then also like people have been 00:45:20.130 --> 00:45:24.089 align:start position:0% and then also like people have been taking<00:45:21.130> this<00:45:21.339> as<00:45:21.609> I<00:45:22.109> in<00:45:23.109> order<00:45:23.319> for<00:45:23.470> my<00:45:23.589> design 00:45:24.089 --> 00:45:24.099 align:start position:0% taking this as I in order for my design 00:45:24.099 --> 00:45:25.920 align:start position:0% taking this as I in order for my design to<00:45:24.339> be<00:45:24.460> taken<00:45:24.760> seriously<00:45:25.150> I<00:45:25.270> need<00:45:25.450> to<00:45:25.690> assign 00:45:25.920 --> 00:45:25.930 align:start position:0% to be taken seriously I need to assign 00:45:25.930 --> 00:45:27.630 align:start position:0% to be taken seriously I need to assign it<00:45:26.140> a<00:45:26.230> name<00:45:26.470> and<00:45:26.710> so<00:45:27.069> you<00:45:27.130> have<00:45:27.220> this<00:45:27.339> massive 00:45:27.630 --> 00:45:27.640 align:start position:0% it a name and so you have this massive 00:45:27.640 --> 00:45:31.050 align:start position:0% it a name and so you have this massive bloat<00:45:28.329> of<00:45:28.599> the<00:45:28.780> plasma<00:45:29.680> and<00:45:30.010> name<00:45:30.310> space<00:45:30.670> and 00:45:31.050 --> 00:45:31.060 align:start position:0% bloat of the plasma and name space and 00:45:31.060 --> 00:45:33.630 align:start position:0% bloat of the plasma and name space and it's<00:45:31.720> super<00:45:32.079> confusing<00:45:32.290> I<00:45:32.770> think<00:45:32.980> it's<00:45:33.099> just<00:45:33.369> I 00:45:33.630 --> 00:45:33.640 align:start position:0% it's super confusing I think it's just I 00:45:33.640 --> 00:45:35.520 align:start position:0% it's super confusing I think it's just I get<00:45:34.240> it<00:45:34.420> makes<00:45:34.660> it<00:45:34.839> really<00:45:34.960> hard<00:45:35.200> for<00:45:35.319> me<00:45:35.500> to 00:45:35.520 --> 00:45:35.530 align:start position:0% get it makes it really hard for me to 00:45:35.530 --> 00:45:36.960 align:start position:0% get it makes it really hard for me to refer<00:45:35.859> to<00:45:35.980> what<00:45:36.099> I'm<00:45:36.190> actually<00:45:36.369> talking<00:45:36.730> about 00:45:36.960 --> 00:45:36.970 align:start position:0% refer to what I'm actually talking about 00:45:36.970 --> 00:45:38.819 align:start position:0% refer to what I'm actually talking about when<00:45:37.300> there's<00:45:37.480> like<00:45:37.630> 18<00:45:38.020> different<00:45:38.230> names<00:45:38.560> so 00:45:38.819 --> 00:45:38.829 align:start position:0% when there's like 18 different names so 00:45:38.829 --> 00:45:42.480 align:start position:0% when there's like 18 different names so I<00:45:39.069> think<00:45:39.460> it's<00:45:39.790> considered<00:45:40.210> harmful<00:45:40.780> I<00:45:41.410> mean<00:45:42.400> I 00:45:42.480 --> 00:45:42.490 align:start position:0% I think it's considered harmful I mean I 00:45:42.490 --> 00:45:44.430 align:start position:0% I think it's considered harmful I mean I I<00:45:42.700> like<00:45:43.119> the<00:45:43.270> idea<00:45:43.510> of<00:45:43.569> naming<00:45:43.810> things<00:45:43.960> I<00:45:44.380> think 00:45:44.430 --> 00:45:44.440 align:start position:0% I like the idea of naming things I think 00:45:44.440 --> 00:45:47.069 align:start position:0% I like the idea of naming things I think we<00:45:45.099> should<00:45:45.310> just<00:45:45.430> be<00:45:45.579> careful<00:45:45.940> about<00:45:46.089> you<00:45:46.990> know 00:45:47.069 --> 00:45:47.079 align:start position:0% we should just be careful about you know 00:45:47.079 --> 00:45:49.200 align:start position:0% we should just be careful about you know unless<00:45:47.680> it's<00:45:47.740> something<00:45:48.099> totally<00:45:48.520> novel<00:45:48.910> like 00:45:49.200 --> 00:45:49.210 align:start position:0% unless it's something totally novel like 00:45:49.210 --> 00:45:51.480 align:start position:0% unless it's something totally novel like I<00:45:49.329> like<00:45:49.569> plasma<00:45:50.109> prime<00:45:50.560> being<00:45:50.829> named<00:45:51.130> its<00:45:51.369> own 00:45:51.480 --> 00:45:51.490 align:start position:0% I like plasma prime being named its own 00:45:51.490 --> 00:45:53.790 align:start position:0% I like plasma prime being named its own thing<00:45:51.790> is<00:45:51.970> it's<00:45:52.150> just<00:45:52.359> it's<00:45:52.839> a<00:45:53.020> ton<00:45:53.380> of<00:45:53.410> work 00:45:53.790 --> 00:45:53.800 align:start position:0% thing is it's just it's a ton of work 00:45:53.800 --> 00:45:55.109 align:start position:0% thing is it's just it's a ton of work that's<00:45:54.040> been<00:45:54.220> done<00:45:54.280> over<00:45:54.609> the<00:45:54.760> last<00:45:54.880> few 00:45:55.109 --> 00:45:55.119 align:start position:0% that's been done over the last few 00:45:55.119 --> 00:45:57.089 align:start position:0% that's been done over the last few months<00:45:55.180> put<00:45:56.079> into<00:45:56.349> its<00:45:56.500> thing<00:45:56.710> and<00:45:56.829> it<00:45:56.950> really 00:45:57.089 --> 00:45:57.099 align:start position:0% months put into its thing and it really 00:45:57.099 --> 00:45:59.069 align:start position:0% months put into its thing and it really refers<00:45:57.490> to<00:45:57.520> a<00:45:57.970> large<00:45:58.240> improvement<00:45:58.960> over 00:45:59.069 --> 00:45:59.079 align:start position:0% refers to a large improvement over 00:45:59.079 --> 00:46:01.589 align:start position:0% refers to a large improvement over plasma<00:45:59.349> cash<00:45:59.500> but<00:45:59.770> like<00:46:00.250> micro<00:46:00.940> improvements 00:46:01.589 --> 00:46:01.599 align:start position:0% plasma cash but like micro improvements 00:46:01.599 --> 00:46:03.960 align:start position:0% plasma cash but like micro improvements right<00:46:01.750> it<00:46:01.960> just<00:46:02.130> designs<00:46:03.130> that<00:46:03.400> aren't<00:46:03.760> well 00:46:03.960 --> 00:46:03.970 align:start position:0% right it just designs that aren't well 00:46:03.970 --> 00:46:07.370 align:start position:0% right it just designs that aren't well fleshed<00:46:04.420> out<00:46:04.660> I<00:46:05.460> feel<00:46:06.460> like<00:46:06.609> we<00:46:06.940> should 00:46:07.370 --> 00:46:07.380 align:start position:0% fleshed out I feel like we should 00:46:07.380 --> 00:46:09.780 align:start position:0% fleshed out I feel like we should present<00:46:08.380> the<00:46:08.650> ideas<00:46:09.010> and<00:46:09.369> then<00:46:09.460> it's<00:46:09.609> only 00:46:09.780 --> 00:46:09.790 align:start position:0% present the ideas and then it's only 00:46:09.790 --> 00:46:11.609 align:start position:0% present the ideas and then it's only when<00:46:10.089> it's<00:46:10.240> really<00:46:10.480> solidified<00:46:11.230> into<00:46:11.470> a 00:46:11.609 --> 00:46:11.619 align:start position:0% when it's really solidified into a 00:46:11.619 --> 00:46:14.309 align:start position:0% when it's really solidified into a package<00:46:12.579> should<00:46:13.210> it<00:46:13.300> be<00:46:13.420> assigned<00:46:13.690> a<00:46:13.839> name<00:46:14.050> and 00:46:14.309 --> 00:46:14.319 align:start position:0% package should it be assigned a name and 00:46:14.319 --> 00:46:18.480 align:start position:0% package should it be assigned a name and I<00:46:15.220> would<00:46:15.550> my<00:46:16.150> vote<00:46:16.869> here<00:46:17.170> is<00:46:17.260> that<00:46:17.500> we<00:46:17.710> take 00:46:18.480 --> 00:46:18.490 align:start position:0% I would my vote here is that we take 00:46:18.490 --> 00:46:20.940 align:start position:0% I would my vote here is that we take that<00:46:18.730> naming<00:46:18.970> scheme<00:46:19.329> apart<00:46:19.630> but<00:46:20.140> I<00:46:20.410> am<00:46:20.770> open 00:46:20.940 --> 00:46:20.950 align:start position:0% that naming scheme apart but I am open 00:46:20.950 --> 00:46:23.520 align:start position:0% that naming scheme apart but I am open arguments<00:46:21.579> against<00:46:22.480> this 00:46:23.520 --> 00:46:23.530 align:start position:0% arguments against this 00:46:23.530 --> 00:46:26.099 align:start position:0% arguments against this I<00:46:23.560> think<00:46:24.069> we're<00:46:24.220> short<00:46:24.760> on<00:46:24.849> time<00:46:25.089> let<00:46:25.690> me<00:46:25.720> bring 00:46:26.099 --> 00:46:26.109 align:start position:0% I think we're short on time let me bring 00:46:26.109 --> 00:46:28.349 align:start position:0% I think we're short on time let me bring the<00:46:26.319> mic<00:46:26.470> to<00:46:26.680> this<00:46:26.800> guy<00:46:27.040> and<00:46:27.280> while<00:46:27.700> I<00:46:28.060> bring 00:46:28.349 --> 00:46:28.359 align:start position:0% the mic to this guy and while I bring 00:46:28.359 --> 00:46:31.470 align:start position:0% the mic to this guy and while I bring the<00:46:28.510> mic<00:46:28.690> oh<00:46:28.839> he<00:46:28.960> got<00:46:29.109> I<00:46:29.410> just<00:46:30.040> want<00:46:30.400> to<00:46:30.579> ask<00:46:30.790> in 00:46:31.470 --> 00:46:31.480 align:start position:0% the mic oh he got I just want to ask in 00:46:31.480 --> 00:46:32.950 align:start position:0% the mic oh he got I just want to ask in your<00:46:31.720> opinion<00:46:32.200> first 00:46:32.950 --> 00:46:32.960 align:start position:0% your opinion first 00:46:32.960 --> 00:46:35.620 align:start position:0% your opinion first what<00:46:33.260> was<00:46:33.500> the<00:46:33.710> best<00:46:33.950> challenge<00:46:34.400> time<00:46:34.940> for<00:46:35.450> the 00:46:35.620 --> 00:46:35.630 align:start position:0% what was the best challenge time for the 00:46:35.630 --> 00:46:38.320 align:start position:0% what was the best challenge time for the for<00:46:36.170> the<00:46:36.260> challenge<00:46:36.589> period<00:46:37.000> well<00:46:38.000> that's<00:46:38.180> the 00:46:38.320 --> 00:46:38.330 align:start position:0% for the challenge period well that's the 00:46:38.330 --> 00:46:40.089 align:start position:0% for the challenge period well that's the question<00:46:38.720> is<00:46:38.869> we<00:46:39.020> actually<00:46:39.230> don't<00:46:39.560> know<00:46:39.830> and 00:46:40.089 --> 00:46:40.099 align:start position:0% question is we actually don't know and 00:46:40.099 --> 00:46:43.030 align:start position:0% question is we actually don't know and that's<00:46:40.490> why<00:46:40.849> you<00:46:41.420> know<00:46:41.540> you<00:46:42.530> know<00:46:42.650> like<00:46:42.890> I 00:46:43.030 --> 00:46:43.040 align:start position:0% that's why you know you know like I 00:46:43.040 --> 00:46:45.579 align:start position:0% that's why you know you know like I think<00:46:43.099> we<00:46:43.339> can<00:46:43.660> take<00:46:44.660> a<00:46:44.720> lot<00:46:44.930> of<00:46:44.960> the<00:46:45.109> work<00:46:45.290> used 00:46:45.579 --> 00:46:45.589 align:start position:0% think we can take a lot of the work used 00:46:45.589 --> 00:46:48.550 align:start position:0% think we can take a lot of the work used for<00:46:45.920> state<00:46:46.250> channels<00:46:46.580> as<00:46:46.940> of<00:46:47.150> late<00:46:47.380> but<00:46:48.380> that 00:46:48.550 --> 00:46:48.560 align:start position:0% for state channels as of late but that 00:46:48.560 --> 00:46:50.500 align:start position:0% for state channels as of late but that is<00:46:48.710> something<00:46:48.920> which<00:46:49.369> is<00:46:49.609> ultimately<00:46:50.150> up<00:46:50.270> to 00:46:50.500 --> 00:46:50.510 align:start position:0% is something which is ultimately up to 00:46:50.510 --> 00:46:53.290 align:start position:0% is something which is ultimately up to you<00:46:51.140> know<00:46:51.320> the<00:46:51.470> user<00:46:51.650> the<00:46:52.160> plasma<00:46:52.520> chain<00:46:52.760> and 00:46:53.290 --> 00:46:53.300 align:start position:0% you know the user the plasma chain and 00:46:53.300 --> 00:46:56.140 align:start position:0% you know the user the plasma chain and you<00:46:53.750> know<00:46:53.869> what<00:46:54.260> type<00:46:54.410> of<00:46:54.440> risk<00:46:54.680> models<00:46:55.070> if<00:46:55.970> I 00:46:56.140 --> 00:46:56.150 align:start position:0% you know what type of risk models if I 00:46:56.150 --> 00:46:58.990 align:start position:0% you know what type of risk models if I may<00:46:56.540> very<00:46:56.839> quick<00:46:57.109> you<00:46:57.830> already<00:46:58.220> said<00:46:58.550> that<00:46:58.580> the 00:46:58.990 --> 00:46:59.000 align:start position:0% may very quick you already said that the 00:46:59.000 --> 00:47:01.329 align:start position:0% may very quick you already said that the in<00:46:59.869> European<00:47:00.320> but<00:47:00.530> the<00:47:00.650> best<00:47:00.800> solution<00:47:01.220> is<00:47:01.310> to 00:47:01.329 --> 00:47:01.339 align:start position:0% in European but the best solution is to 00:47:01.339 --> 00:47:03.520 align:start position:0% in European but the best solution is to put<00:47:01.820> this<00:47:02.089> plasma<00:47:02.450> cash<00:47:02.599> on<00:47:02.750> one<00:47:02.900> server<00:47:03.200> and 00:47:03.520 --> 00:47:03.530 align:start position:0% put this plasma cash on one server and 00:47:03.530 --> 00:47:06.820 align:start position:0% put this plasma cash on one server and separate<00:47:04.400> having<00:47:05.030> like<00:47:05.300> one<00:47:05.720> super<00:47:06.080> server<00:47:06.320> so 00:47:06.820 --> 00:47:06.830 align:start position:0% separate having like one super server so 00:47:06.830 --> 00:47:09.640 align:start position:0% separate having like one super server so you<00:47:06.859> have<00:47:07.310> like<00:47:07.490> one<00:47:07.700> Operator<00:47:08.060> right<00:47:08.359> and<00:47:08.930> in 00:47:09.640 --> 00:47:09.650 align:start position:0% you have like one Operator right and in 00:47:09.650 --> 00:47:12.490 align:start position:0% you have like one Operator right and in that<00:47:10.160> point<00:47:10.450> what's<00:47:11.450> not<00:47:11.599> necessarily<00:47:12.349> the 00:47:12.490 --> 00:47:12.500 align:start position:0% that point what's not necessarily the 00:47:12.500 --> 00:47:15.250 align:start position:0% that point what's not necessarily the case<00:47:12.650> it<00:47:12.890> could<00:47:13.010> be<00:47:13.040> a<00:47:13.130> set<00:47:13.400> of<00:47:13.550> validators<00:47:14.260> you 00:47:15.250 --> 00:47:15.260 align:start position:0% case it could be a set of validators you 00:47:15.260 --> 00:47:16.390 align:start position:0% case it could be a set of validators you know<00:47:15.349> like<00:47:15.560> for<00:47:15.740> example<00:47:15.770> the<00:47:16.099> most<00:47:16.280> naive 00:47:16.390 --> 00:47:16.400 align:start position:0% know like for example the most naive 00:47:16.400 --> 00:47:17.920 align:start position:0% know like for example the most naive construction<00:47:17.060> would<00:47:17.180> be<00:47:17.270> around<00:47:17.540> robbing<00:47:17.839> a 00:47:17.920 --> 00:47:17.930 align:start position:0% construction would be around robbing a 00:47:17.930 --> 00:47:19.990 align:start position:0% construction would be around robbing a validators<00:47:18.470> for<00:47:18.680> example<00:47:19.040> so<00:47:19.609> most<00:47:19.820> likely 00:47:19.990 --> 00:47:20.000 align:start position:0% validators for example so most likely 00:47:20.000 --> 00:47:22.480 align:start position:0% validators for example so most likely peer-to-peer<00:47:20.630> network<00:47:21.290> yeah<00:47:22.040> yeah<00:47:22.190> will<00:47:22.400> be 00:47:22.480 --> 00:47:22.490 align:start position:0% peer-to-peer network yeah yeah will be 00:47:22.490 --> 00:47:23.890 align:start position:0% peer-to-peer network yeah yeah will be done<00:47:22.640> across<00:47:22.849> you<00:47:23.119> know<00:47:23.240> some<00:47:23.420> propagated 00:47:23.890 --> 00:47:23.900 align:start position:0% done across you know some propagated 00:47:23.900 --> 00:47:25.780 align:start position:0% done across you know some propagated peer-to-peer<00:47:24.080> network<00:47:24.500> you<00:47:25.339> just<00:47:25.520> want<00:47:25.700> the 00:47:25.780 --> 00:47:25.790 align:start position:0% peer-to-peer network you just want the 00:47:25.790 --> 00:47:27.370 align:start position:0% peer-to-peer network you just want the entire<00:47:26.119> state<00:47:26.420> to<00:47:26.599> be<00:47:26.690> able<00:47:26.750> to<00:47:26.869> rep<00:47:27.050> you 00:47:27.370 --> 00:47:27.380 align:start position:0% entire state to be able to rep you 00:47:27.380 --> 00:47:28.690 align:start position:0% entire state to be able to rep you represented<00:47:27.980> on<00:47:28.070> a<00:47:28.099> single<00:47:28.430> machine 00:47:28.690 --> 00:47:28.700 align:start position:0% represented on a single machine 00:47:28.700 --> 00:47:31.510 align:start position:0% represented on a single machine listen<00:47:29.089> commotion<00:47:29.560> the<00:47:30.560> idea<00:47:30.980> is<00:47:31.160> sort<00:47:31.460> of 00:47:31.510 --> 00:47:31.520 align:start position:0% listen commotion the idea is sort of 00:47:31.520 --> 00:47:32.800 align:start position:0% listen commotion the idea is sort of like<00:47:31.670> on<00:47:31.849> ethereum<00:47:32.119> you<00:47:32.450> know<00:47:32.540> you<00:47:32.599> know<00:47:32.750> you 00:47:32.800 --> 00:47:32.810 align:start position:0% like on ethereum you know you know you 00:47:32.810 --> 00:47:34.540 align:start position:0% like on ethereum you know you know you don't<00:47:32.990> you<00:47:33.109> don't<00:47:33.230> have<00:47:33.470> one<00:47:33.710> single<00:47:33.920> server 00:47:34.540 --> 00:47:34.550 align:start position:0% don't you don't have one single server 00:47:34.550 --> 00:47:36.550 align:start position:0% don't you don't have one single server running<00:47:34.820> aetherium<00:47:35.300> everyone<00:47:35.930> replicates<00:47:36.380> it 00:47:36.550 --> 00:47:36.560 align:start position:0% running aetherium everyone replicates it 00:47:36.560 --> 00:47:38.770 align:start position:0% running aetherium everyone replicates it but<00:47:36.830> it<00:47:37.070> can<00:47:37.280> be<00:47:37.430> run<00:47:37.670> on<00:47:37.970> a<00:47:38.359> single<00:47:38.510> machine 00:47:38.770 --> 00:47:38.780 align:start position:0% but it can be run on a single machine 00:47:38.780 --> 00:47:40.599 align:start position:0% but it can be run on a single machine currently<00:47:39.320> with<00:47:39.740> sharding<00:47:40.099> of<00:47:40.190> course<00:47:40.400> you 00:47:40.599 --> 00:47:40.609 align:start position:0% currently with sharding of course you 00:47:40.609 --> 00:47:45.310 align:start position:0% currently with sharding of course you know<00:47:40.730> you<00:47:41.089> have<00:47:41.480> a<00:47:41.510> more<00:47:42.109> distributed<00:47:42.500> model<00:47:44.320> I 00:47:45.310 --> 00:47:45.320 align:start position:0% know you have a more distributed model I 00:47:45.320 --> 00:47:47.290 align:start position:0% know you have a more distributed model I like<00:47:46.099> to<00:47:46.160> just<00:47:46.280> answer<00:47:46.550> his<00:47:46.580> question<00:47:47.060> and<00:47:47.119> uh 00:47:47.290 --> 00:47:47.300 align:start position:0% like to just answer his question and uh 00:47:47.300 --> 00:47:50.380 align:start position:0% like to just answer his question and uh like<00:47:47.839> I<00:47:48.820> it's<00:47:49.820> like<00:47:49.880> a<00:47:49.970> slightly<00:47:50.210> more 00:47:50.380 --> 00:47:50.390 align:start position:0% like I it's like a slightly more 00:47:50.390 --> 00:47:51.730 align:start position:0% like I it's like a slightly more technical<00:47:50.570> thing<00:47:50.900> but<00:47:51.050> I<00:47:51.080> I<00:47:51.200> think<00:47:51.410> the<00:47:51.710> the 00:47:51.730 --> 00:47:51.740 align:start position:0% technical thing but I I think the the 00:47:51.740 --> 00:47:53.230 align:start position:0% technical thing but I I think the the biggest<00:47:52.190> challenge<00:47:52.460> like<00:47:52.580> we<00:47:52.880> haven't<00:47:53.180> quite 00:47:53.230 --> 00:47:53.240 align:start position:0% biggest challenge like we haven't quite 00:47:53.240 --> 00:47:55.120 align:start position:0% biggest challenge like we haven't quite figure<00:47:53.480> it<00:47:53.570> out<00:47:53.690> is<00:47:53.900> like<00:47:54.619> some<00:47:54.859> people<00:47:55.070> in 00:47:55.120 --> 00:47:55.130 align:start position:0% figure it out is like some people in 00:47:55.130 --> 00:47:56.829 align:start position:0% figure it out is like some people in disagree<00:47:55.430> with<00:47:55.520> me<00:47:55.580> is<00:47:55.760> like<00:47:55.839> proof 00:47:56.829 --> 00:47:56.839 align:start position:0% disagree with me is like proof 00:47:56.839 --> 00:47:58.359 align:start position:0% disagree with me is like proof compression<00:47:57.320> for<00:47:57.440> plasma<00:47:57.589> cash<00:47:57.920> so<00:47:58.099> like<00:47:58.250> I 00:47:58.359 --> 00:47:58.369 align:start position:0% compression for plasma cash so like I 00:47:58.369 --> 00:48:00.359 align:start position:0% compression for plasma cash so like I think<00:47:58.430> that<00:47:58.700> who<00:47:58.880> best<00:47:59.510> candidates<00:47:59.900> are<00:48:00.080> like 00:48:00.359 --> 00:48:00.369 align:start position:0% think that who best candidates are like 00:48:00.369 --> 00:48:03.190 align:start position:0% think that who best candidates are like on<00:48:01.369> the<00:48:01.609> one<00:48:01.730> hand<00:48:01.940> using<00:48:02.300> RSA<00:48:02.630> accumulators 00:48:03.190 --> 00:48:03.200 align:start position:0% on the one hand using RSA accumulators 00:48:03.200 --> 00:48:05.380 align:start position:0% on the one hand using RSA accumulators and<00:48:03.410> on<00:48:04.040> the<00:48:04.160> other<00:48:04.250> hand<00:48:04.490> like<00:48:04.730> proof 00:48:05.380 --> 00:48:05.390 align:start position:0% and on the other hand like proof 00:48:05.390 --> 00:48:08.140 align:start position:0% and on the other hand like proof compression<00:48:05.960> using<00:48:06.320> using<00:48:07.040> using<00:48:07.730> stocks<00:48:07.970> and 00:48:08.140 --> 00:48:08.150 align:start position:0% compression using using using stocks and 00:48:08.150 --> 00:48:09.520 align:start position:0% compression using using using stocks and like<00:48:08.300> I<00:48:08.450> think<00:48:08.480> both<00:48:08.780> have<00:48:08.930> both<00:48:09.260> after 00:48:09.520 --> 00:48:09.530 align:start position:0% like I think both have both after 00:48:09.530 --> 00:48:13.570 align:start position:0% like I think both have both after downsides<00:48:09.980> like<00:48:10.810> like<00:48:12.010> RSA<00:48:13.010> commuters<00:48:13.369> are 00:48:13.570 --> 00:48:13.580 align:start position:0% downsides like like RSA commuters are 00:48:13.580 --> 00:48:16.720 align:start position:0% downsides like like RSA commuters are not<00:48:13.730> quantum<00:48:14.060> secure<00:48:14.420> they're<00:48:14.630> not<00:48:15.609> they<00:48:16.609> have 00:48:16.720 --> 00:48:16.730 align:start position:0% not quantum secure they're not they have 00:48:16.730 --> 00:48:19.180 align:start position:0% not quantum secure they're not they have like<00:48:16.940> the<00:48:17.450> engineering<00:48:18.349> it<00:48:18.560> is<00:48:18.589> I<00:48:18.859> think 00:48:19.180 --> 00:48:19.190 align:start position:0% like the engineering it is I think 00:48:19.190 --> 00:48:22.660 align:start position:0% like the engineering it is I think pretty<00:48:19.310> complicated<00:48:19.640> and<00:48:20.089> whereas<00:48:20.599> for<00:48:21.670> for 00:48:22.660 --> 00:48:22.670 align:start position:0% pretty complicated and whereas for for 00:48:22.670 --> 00:48:26.050 align:start position:0% pretty complicated and whereas for for it<00:48:22.849> as<00:48:23.240> stock<00:48:23.690> compression<00:48:24.609> like<00:48:25.609> Shari 00:48:26.050 --> 00:48:26.060 align:start position:0% it as stock compression like Shari 00:48:26.060 --> 00:48:27.790 align:start position:0% it as stock compression like Shari doesn't<00:48:26.330> compress<00:48:26.690> doesn't<00:48:27.140> run<00:48:27.530> very<00:48:27.680> well 00:48:27.790 --> 00:48:27.800 align:start position:0% doesn't compress doesn't run very well 00:48:27.800 --> 00:48:30.550 align:start position:0% doesn't compress doesn't run very well in<00:48:28.280> in<00:48:28.820> a<00:48:28.970> stark<00:48:29.210> and<00:48:29.450> like<00:48:29.599> the<00:48:30.380> stock 00:48:30.550 --> 00:48:30.560 align:start position:0% in in a stark and like the stock 00:48:30.560 --> 00:48:31.930 align:start position:0% in in a stark and like the stock friendly<00:48:30.859> hash<00:48:31.190> functions<00:48:31.550> are<00:48:31.640> a<00:48:31.700> very 00:48:31.930 --> 00:48:31.940 align:start position:0% friendly hash functions are a very 00:48:31.940 --> 00:48:35.500 align:start position:0% friendly hash functions are a very expensive<00:48:32.240> one<00:48:32.540> watching<00:48:33.820> that's<00:48:34.820> mine<00:48:35.089> it's 00:48:35.500 --> 00:48:35.510 align:start position:0% expensive one watching that's mine it's 00:48:35.510 --> 00:48:36.700 align:start position:0% expensive one watching that's mine it's my<00:48:35.630> personal<00:48:35.900> view<00:48:36.080> but<00:48:36.200> like<00:48:36.320> I<00:48:36.349> think<00:48:36.619> if 00:48:36.700 --> 00:48:36.710 align:start position:0% my personal view but like I think if 00:48:36.710 --> 00:48:38.109 align:start position:0% my personal view but like I think if that<00:48:36.859> is<00:48:36.980> I<00:48:37.220> think<00:48:37.339> if<00:48:37.490> that<00:48:37.580> is<00:48:37.640> solved<00:48:38.030> like 00:48:38.109 --> 00:48:38.119 align:start position:0% that is I think if that is solved like 00:48:38.119 --> 00:48:40.660 align:start position:0% that is I think if that is solved like we<00:48:38.390> get<00:48:38.599> like<00:48:39.230> the<00:48:39.410> list<00:48:39.560> of<00:48:39.710> features<00:48:40.040> is<00:48:40.250> is 00:48:40.660 --> 00:48:40.670 align:start position:0% we get like the list of features is is 00:48:40.670 --> 00:48:43.839 align:start position:0% we get like the list of features is is pretty<00:48:41.060> nice<00:48:41.680> just<00:48:42.680> a<00:48:42.770> little<00:48:43.190> bit<00:48:43.430> emphasize 00:48:43.839 --> 00:48:43.849 align:start position:0% pretty nice just a little bit emphasize 00:48:43.849 --> 00:48:46.550 align:start position:0% pretty nice just a little bit emphasize what<00:48:44.089> Joseph<00:48:44.420> said<00:48:44.660> I<00:48:45.290> you<00:48:46.280> can 00:48:46.550 --> 00:48:46.560 align:start position:0% what Joseph said I you can 00:48:46.560 --> 00:48:48.200 align:start position:0% what Joseph said I you can have<00:48:46.620> any<00:48:46.740> set<00:48:46.980> of<00:48:47.010> validators<00:48:47.730> for<00:48:48.030> a<00:48:48.060> new 00:48:48.200 --> 00:48:48.210 align:start position:0% have any set of validators for a new 00:48:48.210 --> 00:48:50.870 align:start position:0% have any set of validators for a new plasma<00:48:48.450> block<00:48:48.840> but<00:48:49.380> ideally<00:48:49.770> two<00:48:50.100> just<00:48:50.730> to 00:48:50.870 --> 00:48:50.880 align:start position:0% plasma block but ideally two just to 00:48:50.880 --> 00:48:52.460 align:start position:0% plasma block but ideally two just to plainly<00:48:51.300> reduce<00:48:51.660> the<00:48:51.780> cost<00:48:52.020> you<00:48:52.170> want<00:48:52.320> your 00:48:52.460 --> 00:48:52.470 align:start position:0% plainly reduce the cost you want your 00:48:52.470 --> 00:48:55.070 align:start position:0% plainly reduce the cost you want your data<00:48:52.680> to<00:48:52.950> produce<00:48:53.160> a<00:48:53.430> block<00:48:53.670> and<00:48:53.880> the<00:48:54.240> place 00:48:55.070 --> 00:48:55.080 align:start position:0% data to produce a block and the place 00:48:55.080 --> 00:48:56.900 align:start position:0% data to produce a block and the place where<00:48:55.380> you<00:48:55.410> take<00:48:56.010> all<00:48:56.160> the<00:48:56.310> transactions<00:48:56.790> from 00:48:56.900 --> 00:48:56.910 align:start position:0% where you take all the transactions from 00:48:56.910 --> 00:48:59.120 align:start position:0% where you take all the transactions from users<00:48:57.330> you<00:48:57.540> wanted<00:48:57.810> as<00:48:58.350> central<00:48:58.770> as<00:48:58.830> possible 00:48:59.120 --> 00:48:59.130 align:start position:0% users you wanted as central as possible 00:48:59.130 --> 00:49:00.980 align:start position:0% users you wanted as central as possible just<00:48:59.340> to<00:48:59.370> reduce<00:48:59.670> the<00:48:59.790> costs<00:49:00.120> if<00:49:00.630> you<00:49:00.690> have 00:49:00.980 --> 00:49:00.990 align:start position:0% just to reduce the costs if you have 00:49:00.990 --> 00:49:03.890 align:start position:0% just to reduce the costs if you have competing<00:49:01.470> producers<00:49:02.340> just<00:49:03.000> multiply<00:49:03.690> by<00:49:03.840> the 00:49:03.890 --> 00:49:03.900 align:start position:0% competing producers just multiply by the 00:49:03.900 --> 00:49:05.300 align:start position:0% competing producers just multiply by the number<00:49:04.020> of<00:49:04.260> producers<00:49:04.380> the<00:49:04.830> amount<00:49:05.010> of<00:49:05.130> fees 00:49:05.300 --> 00:49:05.310 align:start position:0% number of producers the amount of fees 00:49:05.310 --> 00:49:06.740 align:start position:0% number of producers the amount of fees you<00:49:05.430> would<00:49:05.580> want<00:49:05.760> to<00:49:05.850> expect<00:49:06.240> from<00:49:06.360> the<00:49:06.570> block 00:49:06.740 --> 00:49:06.750 align:start position:0% you would want to expect from the block 00:49:06.750 --> 00:49:08.510 align:start position:0% you would want to expect from the block otherwise<00:49:07.320> it's<00:49:07.590> not<00:49:07.710> profitable<00:49:07.890> for<00:49:08.250> them 00:49:08.510 --> 00:49:08.520 align:start position:0% otherwise it's not profitable for them 00:49:08.520 --> 00:49:11.660 align:start position:0% otherwise it's not profitable for them to<00:49:08.640> run<00:49:08.760> the<00:49:08.940> hardware<00:49:09.330> so<00:49:10.320> it's<00:49:10.830> again<00:49:11.460> a 00:49:11.660 --> 00:49:11.670 align:start position:0% to run the hardware so it's again a 00:49:11.670 --> 00:49:14.480 align:start position:0% to run the hardware so it's again a trade-off<00:49:12.030> but<00:49:12.620> there<00:49:13.620> are<00:49:13.740> there<00:49:14.220> are<00:49:14.340> ways 00:49:14.480 --> 00:49:14.490 align:start position:0% trade-off but there are there are ways 00:49:14.490 --> 00:49:16.340 align:start position:0% trade-off but there are there are ways to<00:49:14.520> well<00:49:15.030> not<00:49:15.210> ways<00:49:15.420> to<00:49:15.570> solve<00:49:15.780> it<00:49:15.870> you 00:49:16.340 --> 00:49:16.350 align:start position:0% to well not ways to solve it you 00:49:16.350 --> 00:49:19.220 align:start position:0% to well not ways to solve it you understand<00:49:16.800> every<00:49:17.750> strategy<00:49:18.750> and<00:49:18.870> most<00:49:19.080> like 00:49:19.220 --> 00:49:19.230 align:start position:0% understand every strategy and most like 00:49:19.230 --> 00:49:20.900 align:start position:0% understand every strategy and most like we<00:49:19.380> just<00:49:19.530> need<00:49:19.710> to<00:49:19.800> stay<00:49:19.950> to<00:49:20.010> set<00:49:20.490> of<00:49:20.640> elevators 00:49:20.900 --> 00:49:20.910 align:start position:0% we just need to stay to set of elevators 00:49:20.910 --> 00:49:26.750 align:start position:0% we just need to stay to set of elevators and<00:49:21.360> build<00:49:21.930> a<00:49:22.020> signature<00:49:22.320> I<00:49:23.690> think<00:49:25.520> what<00:49:26.520> about 00:49:26.750 --> 00:49:26.760 align:start position:0% and build a signature I think what about 00:49:26.760 --> 00:49:29.030 align:start position:0% and build a signature I think what about censorship<00:49:27.570> resistance<00:49:28.290> like<00:49:28.650> if<00:49:28.800> you<00:49:28.950> have 00:49:29.030 --> 00:49:29.040 align:start position:0% censorship resistance like if you have 00:49:29.040 --> 00:49:31.520 align:start position:0% censorship resistance like if you have one<00:49:29.250> Operator<00:49:29.700> then<00:49:30.080> it's<00:49:31.080> not<00:49:31.200> a<00:49:31.260> feature 00:49:31.520 --> 00:49:31.530 align:start position:0% one Operator then it's not a feature 00:49:31.530 --> 00:49:37.580 align:start position:0% one Operator then it's not a feature okay<00:49:34.910> is<00:49:35.910> that<00:49:35.970> and<00:49:36.600> it<00:49:36.750> also<00:49:36.990> relates<00:49:37.380> with 00:49:37.580 --> 00:49:37.590 align:start position:0% okay is that and it also relates with 00:49:37.590 --> 00:49:39.410 align:start position:0% okay is that and it also relates with fees<00:49:37.860> in<00:49:38.070> plasma<00:49:38.400> I<00:49:38.580> believe<00:49:39.090> that<00:49:39.270> you<00:49:39.390> should 00:49:39.410 --> 00:49:39.420 align:start position:0% fees in plasma I believe that you should 00:49:39.420 --> 00:49:41.210 align:start position:0% fees in plasma I believe that you should consider<00:49:39.750> that<00:49:40.020> your<00:49:40.290> transaction<00:49:40.830> is<00:49:41.010> by 00:49:41.210 --> 00:49:41.220 align:start position:0% consider that your transaction is by 00:49:41.220 --> 00:49:42.980 align:start position:0% consider that your transaction is by default<00:49:41.550> censored<00:49:42.120> and<00:49:42.510> you<00:49:42.660> should<00:49:42.810> feel 00:49:42.980 --> 00:49:42.990 align:start position:0% default censored and you should feel 00:49:42.990 --> 00:49:47.150 align:start position:0% default censored and you should feel nice<00:49:43.290> when<00:49:43.680> it<00:49:43.860> gets<00:49:44.100> included<00:49:44.490> and<00:49:46.010> this<00:49:47.010> is 00:49:47.150 --> 00:49:47.160 align:start position:0% nice when it gets included and this is 00:49:47.160 --> 00:49:49.280 align:start position:0% nice when it gets included and this is this<00:49:47.670> is<00:49:47.820> what<00:49:47.970> allows<00:49:48.240> you<00:49:48.360> to<00:49:48.390> like<00:49:48.660> any<00:49:48.960> kind 00:49:49.280 --> 00:49:49.290 align:start position:0% this is what allows you to like any kind 00:49:49.290 --> 00:49:51.410 align:start position:0% this is what allows you to like any kind of<00:49:49.410> transaction<00:49:50.010> fees<00:49:50.400> they<00:49:50.940> don't<00:49:51.150> have<00:49:51.300> to 00:49:51.410 --> 00:49:51.420 align:start position:0% of transaction fees they don't have to 00:49:51.420 --> 00:49:53.270 align:start position:0% of transaction fees they don't have to be<00:49:51.540> in<00:49:51.750> the<00:49:51.900> protocol<00:49:52.260> because<00:49:52.980> I<00:49:53.100> can 00:49:53.270 --> 00:49:53.280 align:start position:0% be in the protocol because I can 00:49:53.280 --> 00:49:54.770 align:start position:0% be in the protocol because I can literally<00:49:53.520> go<00:49:53.760> to<00:49:53.790> Jonesy<00:49:54.270> I<00:49:54.330> can<00:49:54.510> tell<00:49:54.630> him 00:49:54.770 --> 00:49:54.780 align:start position:0% literally go to Jonesy I can tell him 00:49:54.780 --> 00:49:56.660 align:start position:0% literally go to Jonesy I can tell him you're<00:49:55.080> my<00:49:55.230> operator<00:49:55.620> by<00:49:56.100> default<00:49:56.460> he's 00:49:56.660 --> 00:49:56.670 align:start position:0% you're my operator by default he's 00:49:56.670 --> 00:49:59.330 align:start position:0% you're my operator by default he's censoring<00:49:57.150> me<00:49:57.500> that<00:49:58.500> is<00:49:58.620> the<00:49:58.710> default<00:49:58.980> and 00:49:59.330 --> 00:49:59.340 align:start position:0% censoring me that is the default and 00:49:59.340 --> 00:50:02.510 align:start position:0% censoring me that is the default and like<00:49:59.490> if<00:49:59.760> if<00:50:00.060> he<00:50:00.720> takes<00:50:00.960> have<00:50:01.590> I<00:50:01.710> because<00:50:02.400> he 00:50:02.510 --> 00:50:02.520 align:start position:0% like if if he takes have I because he 00:50:02.520 --> 00:50:05.090 align:start position:0% like if if he takes have I because he paid<00:50:02.700> me<00:50:02.850> my<00:50:03.270> five<00:50:03.540> PayPal<00:50:04.110> dollars<00:50:04.680> this<00:50:04.920> one 00:50:05.090 --> 00:50:05.100 align:start position:0% paid me my five PayPal dollars this one 00:50:05.100 --> 00:50:07.340 align:start position:0% paid me my five PayPal dollars this one yes<00:50:05.670> I<00:50:05.880> let<00:50:06.480> the<00:50:06.570> transaction<00:50:06.990> go<00:50:07.110> through 00:50:07.340 --> 00:50:07.350 align:start position:0% yes I let the transaction go through 00:50:07.350 --> 00:50:09.950 align:start position:0% yes I let the transaction go through yeah<00:50:08.220> and<00:50:08.370> it's<00:50:08.880> totally<00:50:09.120> like<00:50:09.450> good<00:50:09.660> for<00:50:09.810> like 00:50:09.950 --> 00:50:09.960 align:start position:0% yeah and it's totally like good for like 00:50:09.960 --> 00:50:11.480 align:start position:0% yeah and it's totally like good for like the<00:50:10.110> fig<00:50:10.320> model<00:50:10.740> because<00:50:10.980> it's<00:50:11.160> totally 00:50:11.480 --> 00:50:11.490 align:start position:0% the fig model because it's totally 00:50:11.490 --> 00:50:13.220 align:start position:0% the fig model because it's totally independent<00:50:12.270> it's<00:50:12.420> like<00:50:12.570> you<00:50:12.960> have<00:50:13.110> a 00:50:13.220 --> 00:50:13.230 align:start position:0% independent it's like you have a 00:50:13.230 --> 00:50:14.180 align:start position:0% independent it's like you have a whatever<00:50:13.410> service<00:50:13.920> that<00:50:14.070> you're<00:50:14.160> providing 00:50:14.180 --> 00:50:14.190 align:start position:0% whatever service that you're providing 00:50:14.190 --> 00:50:17.240 align:start position:0% whatever service that you're providing because<00:50:14.940> you're<00:50:15.150> the<00:50:15.330> operator<00:50:15.920> you<00:50:16.920> must<00:50:17.100> be 00:50:17.240 --> 00:50:17.250 align:start position:0% because you're the operator you must be 00:50:17.250 --> 00:50:18.920 align:start position:0% because you're the operator you must be operating<00:50:17.640> something<00:50:17.970> you<00:50:18.150> have<00:50:18.300> some<00:50:18.480> for 00:50:18.920 --> 00:50:18.930 align:start position:0% operating something you have some for 00:50:18.930 --> 00:50:21.710 align:start position:0% operating something you have some for profit<00:50:19.290> and<00:50:19.530> yeah<00:50:20.340> I<00:50:20.610> believe<00:50:20.850> that<00:50:21.270> the<00:50:21.450> value 00:50:21.710 --> 00:50:21.720 align:start position:0% profit and yeah I believe that the value 00:50:21.720 --> 00:50:23.840 align:start position:0% profit and yeah I believe that the value that's<00:50:22.320> the<00:50:22.440> proper<00:50:22.740> way<00:50:22.860> to<00:50:22.920> think<00:50:23.130> if<00:50:23.670> you 00:50:23.840 --> 00:50:23.850 align:start position:0% that's the proper way to think if you 00:50:23.850 --> 00:50:25.490 align:start position:0% that's the proper way to think if you want<00:50:24.000> stronger<00:50:24.270> guarantees<00:50:24.810> change<00:50:25.320> your 00:50:25.490 --> 00:50:25.500 align:start position:0% want stronger guarantees change your 00:50:25.500 --> 00:50:27.020 align:start position:0% want stronger guarantees change your route<00:50:25.710> chain<00:50:25.920> smart<00:50:26.190> contract<00:50:26.640> to<00:50:26.730> be<00:50:26.790> able<00:50:26.850> to 00:50:27.020 --> 00:50:27.030 align:start position:0% route chain smart contract to be able to 00:50:27.030 --> 00:50:28.310 align:start position:0% route chain smart contract to be able to process<00:50:27.240> it<00:50:27.450> on<00:50:27.630> the<00:50:27.720> route<00:50:27.870> chain<00:50:28.050> as<00:50:28.170> well 00:50:28.310 --> 00:50:28.320 align:start position:0% process it on the route chain as well 00:50:28.320 --> 00:50:30.220 align:start position:0% process it on the route chain as well tit<00:50:28.620> would<00:50:28.740> be<00:50:28.830> reflected<00:50:29.310> in<00:50:29.430> the<00:50:29.490> clasp<00:50:29.700> yeah 00:50:30.220 --> 00:50:30.230 align:start position:0% tit would be reflected in the clasp yeah 00:50:30.230 --> 00:50:37.550 align:start position:0% tit would be reflected in the clasp yeah I<00:50:31.230> think<00:50:31.590> we're<00:50:31.710> running<00:50:31.800> a<00:50:31.950> long<00:50:32.130> time<00:50:36.560> just 00:50:37.550 --> 00:50:37.560 align:start position:0% I think we're running a long time just 00:50:37.560 --> 00:50:40.010 align:start position:0% I think we're running a long time just this<00:50:38.340> is<00:50:38.490> just<00:50:38.700> purely<00:50:39.300> for<00:50:39.600> redundancy 00:50:40.010 --> 00:50:40.020 align:start position:0% this is just purely for redundancy 00:50:40.020 --> 00:50:41.990 align:start position:0% this is just purely for redundancy purposes<00:50:40.740> too<00:50:40.920> I<00:50:40.950> think<00:50:41.160> like<00:50:41.460> you<00:50:41.670> all<00:50:41.790> made<00:50:41.970> a 00:50:41.990 --> 00:50:42.000 align:start position:0% purposes too I think like you all made a 00:50:42.000 --> 00:50:43.520 align:start position:0% purposes too I think like you all made a lot<00:50:42.180> of<00:50:42.210> good<00:50:42.420> points<00:50:42.630> and<00:50:42.990> like<00:50:43.140> all<00:50:43.320> of<00:50:43.350> us 00:50:43.520 --> 00:50:43.530 align:start position:0% lot of good points and like all of us 00:50:43.530 --> 00:50:45.200 align:start position:0% lot of good points and like all of us would<00:50:43.740> love<00:50:43.890> to<00:50:44.100> go<00:50:44.250> do<00:50:44.490> more<00:50:44.640> research<00:50:44.850> on 00:50:45.200 --> 00:50:45.210 align:start position:0% would love to go do more research on 00:50:45.210 --> 00:50:46.760 align:start position:0% would love to go do more research on some<00:50:45.420> of<00:50:45.510> the<00:50:45.600> points<00:50:45.750> that<00:50:45.930> you<00:50:46.080> made<00:50:46.140> but<00:50:46.680> we 00:50:46.760 --> 00:50:46.770 align:start position:0% some of the points that you made but we 00:50:46.770 --> 00:50:49.130 align:start position:0% some of the points that you made but we never<00:50:47.010> got<00:50:47.370> through<00:50:47.790> introductions<00:50:48.300> so<00:50:48.660> we 00:50:49.130 --> 00:50:49.140 align:start position:0% never got through introductions so we 00:50:49.140 --> 00:50:51.170 align:start position:0% never got through introductions so we only<00:50:49.290> got<00:50:49.470> half<00:50:49.770> of<00:50:49.920> your<00:50:50.070> names<00:50:50.310> to<00:50:50.700> do<00:50:50.910> for 00:50:51.170 --> 00:50:51.180 align:start position:0% only got half of your names to do for 00:50:51.180 --> 00:50:53.150 align:start position:0% only got half of your names to do for the<00:50:51.270> research<00:50:51.600> so<00:50:52.050> can<00:50:52.230> we<00:50:52.290> just<00:50:52.320> go<00:50:52.710> back<00:50:52.740> and 00:50:53.150 --> 00:50:53.160 align:start position:0% the research so can we just go back and 00:50:53.160 --> 00:50:54.770 align:start position:0% the research so can we just go back and get<00:50:53.280> everybody's<00:50:53.730> names<00:50:54.000> so<00:50:54.240> that<00:50:54.390> we<00:50:54.480> can<00:50:54.660> go 00:50:54.770 --> 00:50:54.780 align:start position:0% get everybody's names so that we can go 00:50:54.780 --> 00:50:56.210 align:start position:0% get everybody's names so that we can go research<00:50:55.200> some<00:50:55.260> of<00:50:55.530> the<00:50:55.680> points<00:50:55.950> that<00:50:56.010> you<00:50:56.100> all 00:50:56.210 --> 00:50:56.220 align:start position:0% research some of the points that you all 00:50:56.220 --> 00:50:58.800 align:start position:0% research some of the points that you all made<00:50:56.430> on<00:50:56.580> our<00:50:56.730> own<00:50:56.880> did<00:50:57.690> some<00:50:57.900> of<00:50:57.990> you<00:50:58.110> not 00:50:58.800 --> 00:50:58.810 align:start position:0% made on our own did some of you not 00:50:58.810 --> 00:51:00.300 align:start position:0% made on our own did some of you not on<00:50:58.870> the<00:50:59.020> walking<00:50:59.230> up<00:50:59.470> to<00:50:59.680> the<00:50:59.800> introduction 00:51:00.300 --> 00:51:00.310 align:start position:0% on the walking up to the introduction 00:51:00.310 --> 00:51:01.530 align:start position:0% on the walking up to the introduction we'll<00:51:00.430> just<00:51:00.580> we'll<00:51:00.760> just<00:51:00.820> do<00:51:01.030> it<00:51:01.060> really<00:51:01.330> quick 00:51:01.530 --> 00:51:01.540 align:start position:0% we'll just we'll just do it really quick 00:51:01.540 --> 00:51:06.530 align:start position:0% we'll just we'll just do it really quick hi<00:51:01.780> Calvin<00:51:02.260> fish<00:51:02.680> Sir<00:51:02.890> Joseph<00:51:03.580> own<00:51:04.440> shrine<00:51:05.440> see 00:51:06.530 --> 00:51:06.540 align:start position:0% hi Calvin fish Sir Joseph own shrine see 00:51:06.540 --> 00:51:09.990 align:start position:0% hi Calvin fish Sir Joseph own shrine see David<00:51:07.540> not<00:51:07.980> George's<00:51:08.980> constant<00:51:09.340> Ovilus<00:51:09.730> it's 00:51:09.990 --> 00:51:10.000 align:start position:0% David not George's constant Ovilus it's 00:51:10.000 --> 00:51:11.900 align:start position:0% David not George's constant Ovilus it's longer 00:51:11.900 --> 00:51:11.910 align:start position:0% longer 00:51:11.910 --> 00:51:15.780 align:start position:0% longer riverkeeper<00:51:13.740> Alex<00:51:14.740> philosophy<00:51:15.220> Alexander 00:51:15.780 --> 00:51:15.790 align:start position:0% riverkeeper Alex philosophy Alexander 00:51:15.790 --> 00:51:20.340 align:start position:0% riverkeeper Alex philosophy Alexander for<00:51:16.120> a<00:51:16.150> full<00:51:16.330> name<00:51:17.160> johann<00:51:18.160> Barbie<00:51:19.350> Karl 00:51:20.340 --> 00:51:20.350 align:start position:0% for a full name johann Barbie Karl 00:51:20.350 --> 00:51:22.710 align:start position:0% for a full name johann Barbie Karl flourish<00:51:21.010> and<00:51:21.670> and<00:51:22.090> I<00:51:22.150> think<00:51:22.210> there's<00:51:22.480> a<00:51:22.540> bunch 00:51:22.710 --> 00:51:22.720 align:start position:0% flourish and and I think there's a bunch 00:51:22.720 --> 00:51:24.390 align:start position:0% flourish and and I think there's a bunch of<00:51:22.930> you<00:51:23.440> know<00:51:23.530> I<00:51:23.560> don't<00:51:23.860> I<00:51:24.040> don't<00:51:24.100> want<00:51:24.310> to 00:51:24.390 --> 00:51:24.400 align:start position:0% of you know I don't I don't want to 00:51:24.400 --> 00:51:25.620 align:start position:0% of you know I don't I don't want to discount<00:51:24.670> all<00:51:24.850> the<00:51:24.970> all<00:51:25.090> the<00:51:25.210> other<00:51:25.330> people 00:51:25.620 --> 00:51:25.630 align:start position:0% discount all the all the other people 00:51:25.630 --> 00:51:26.940 align:start position:0% discount all the all the other people working<00:51:25.750> on<00:51:25.990> plasma<00:51:26.380> I<00:51:26.410> think<00:51:26.650> you<00:51:26.770> know<00:51:26.890> you 00:51:26.940 --> 00:51:26.950 align:start position:0% working on plasma I think you know you 00:51:26.950 --> 00:51:28.650 align:start position:0% working on plasma I think you know you know<00:51:27.220> people<00:51:27.490> like<00:51:27.640> dan<00:51:27.820> dan<00:51:28.210> Robinson 00:51:28.650 --> 00:51:28.660 align:start position:0% know people like dan dan Robinson 00:51:28.660 --> 00:51:30.360 align:start position:0% know people like dan dan Robinson couldn't<00:51:28.900> make<00:51:29.020> it<00:51:29.050> there's<00:51:29.890> a<00:51:29.950> lot<00:51:30.100> of<00:51:30.250> people 00:51:30.360 --> 00:51:30.370 align:start position:0% couldn't make it there's a lot of people 00:51:30.370 --> 00:51:31.830 align:start position:0% couldn't make it there's a lot of people writing<00:51:30.670> excellent<00:51:31.150> implementation<00:51:31.750> a<00:51:31.810> lot 00:51:31.830 --> 00:51:31.840 align:start position:0% writing excellent implementation a lot 00:51:31.840 --> 00:51:33.450 align:start position:0% writing excellent implementation a lot of<00:51:32.050> people<00:51:32.290> you<00:51:32.500> know<00:51:32.590> like<00:51:32.800> people<00:51:32.950> like<00:51:33.250> you 00:51:33.450 --> 00:51:33.460 align:start position:0% of people you know like people like you 00:51:33.460 --> 00:51:36.030 align:start position:0% of people you know like people like you know<00:51:33.550> or<00:51:33.820> state<00:51:34.150> walk<00:51:34.750> they're<00:51:35.200> not<00:51:35.380> they're 00:51:36.030 --> 00:51:36.040 align:start position:0% know or state walk they're not they're 00:51:36.040 --> 00:51:37.200 align:start position:0% know or state walk they're not they're not<00:51:36.160> represented<00:51:36.670> up<00:51:36.760> here<00:51:36.790> but<00:51:37.120> definitely 00:51:37.200 --> 00:51:37.210 align:start position:0% not represented up here but definitely 00:51:37.210 --> 00:51:39.270 align:start position:0% not represented up here but definitely have<00:51:37.660> been<00:51:37.780> doing<00:51:38.470> a<00:51:38.560> lot<00:51:38.710> of<00:51:38.740> excellent<00:51:39.250> work 00:51:39.270 --> 00:51:39.280 align:start position:0% have been doing a lot of excellent work 00:51:39.280 --> 00:51:41.550 align:start position:0% have been doing a lot of excellent work a<00:51:40.120> lot<00:51:40.480> of<00:51:40.600> other<00:51:40.750> other<00:51:41.050> other<00:51:41.380> people 00:51:41.550 --> 00:51:41.560 align:start position:0% a lot of other other other people 00:51:41.560 --> 00:51:43.620 align:start position:0% a lot of other other other people projects<00:51:42.310> and<00:51:42.550> I<00:51:42.760> think<00:51:42.880> you<00:51:43.210> know<00:51:43.300> a<00:51:43.330> lot<00:51:43.510> of 00:51:43.620 --> 00:51:43.630 align:start position:0% projects and I think you know a lot of 00:51:43.630 --> 00:51:45.810 align:start position:0% projects and I think you know a lot of people<00:51:43.840> making<00:51:44.020> comments<00:51:44.290> on<00:51:44.530> III<00:51:44.800> search<00:51:45.100> and 00:51:45.810 --> 00:51:45.820 align:start position:0% people making comments on III search and 00:51:45.820 --> 00:51:47.970 align:start position:0% people making comments on III search and you<00:51:46.210> know<00:51:46.300> this<00:51:46.540> is<00:51:46.660> a<00:51:46.690> very<00:51:46.960> you<00:51:47.320> know<00:51:47.380> the<00:51:47.740> the 00:51:47.970 --> 00:51:47.980 align:start position:0% you know this is a very you know the the 00:51:47.980 --> 00:51:48.900 align:start position:0% you know this is a very you know the the communities<00:51:48.340> designed<00:51:48.610> to<00:51:48.670> be<00:51:48.730> very 00:51:48.900 --> 00:51:48.910 align:start position:0% communities designed to be very 00:51:48.910 --> 00:51:50.610 align:start position:0% communities designed to be very inclusive<00:51:49.030> I<00:51:49.630> think<00:51:50.050> you<00:51:50.140> know<00:51:50.200> it's<00:51:50.350> called 00:51:50.610 --> 00:51:50.620 align:start position:0% inclusive I think you know it's called 00:51:50.620 --> 00:51:52.800 align:start position:0% inclusive I think you know it's called the<00:51:50.800> plasma<00:51:51.160> you<00:51:51.790> know<00:51:51.940> implementers<00:51:52.540> group 00:51:52.800 --> 00:51:52.810 align:start position:0% the plasma you know implementers group 00:51:52.810 --> 00:51:54.300 align:start position:0% the plasma you know implementers group but<00:51:53.050> it<00:51:53.230> seems<00:51:53.440> to<00:51:53.530> be<00:51:53.620> plasma<00:51:53.920> smacking<00:51:54.220> them 00:51:54.300 --> 00:51:54.310 align:start position:0% but it seems to be plasma smacking them 00:51:54.310 --> 00:51:55.470 align:start position:0% but it seems to be plasma smacking them some<00:51:54.490> designers<00:51:54.910> group<00:51:55.060> and<00:51:55.180> there's<00:51:55.300> a<00:51:55.360> lot 00:51:55.470 --> 00:51:55.480 align:start position:0% some designers group and there's a lot 00:51:55.480 --> 00:51:58.530 align:start position:0% some designers group and there's a lot of<00:51:55.600> implementations<00:51:56.410> as<00:51:56.560> well<00:51:57.390> and<00:51:58.390> they 00:51:58.530 --> 00:51:58.540 align:start position:0% of implementations as well and they 00:51:58.540 --> 00:52:00.420 align:start position:0% of implementations as well and they definitely<00:51:59.440> you<00:51:59.620> know<00:51:59.710> if<00:51:59.830> you<00:51:59.950> do<00:52:00.100> want<00:52:00.340> to 00:52:00.420 --> 00:52:00.430 align:start position:0% definitely you know if you do want to 00:52:00.430 --> 00:52:02.190 align:start position:0% definitely you know if you do want to contribute<00:52:00.730> you<00:52:01.090> know<00:52:01.180> I<00:52:01.210> think<00:52:01.360> there's<00:52:02.080> an 00:52:02.190 --> 00:52:02.200 align:start position:0% contribute you know I think there's an 00:52:02.200 --> 00:52:03.450 align:start position:0% contribute you know I think there's an opportunity<00:52:02.290> to<00:52:02.680> be<00:52:02.770> making<00:52:03.100> measurable 00:52:03.450 --> 00:52:03.460 align:start position:0% opportunity to be making measurable 00:52:03.460 --> 00:52:06.030 align:start position:0% opportunity to be making measurable differences<00:52:04.000> and<00:52:04.210> positive<00:52:04.600> differences<00:52:05.040> III 00:52:06.030 --> 00:52:06.040 align:start position:0% differences and positive differences III 00:52:06.040 --> 00:52:09.060 align:start position:0% differences and positive differences III search<00:52:06.280> and<00:52:06.640> learn<00:52:07.240> plasma<00:52:07.840> org<00:52:08.230> but<00:52:08.530> if<00:52:08.770> I<00:52:08.950> may 00:52:09.060 --> 00:52:09.070 align:start position:0% search and learn plasma org but if I may 00:52:09.070 --> 00:52:11.010 align:start position:0% search and learn plasma org but if I may say<00:52:09.250> one<00:52:09.430> thing<00:52:09.580> like<00:52:09.790> lately<00:52:10.330> I<00:52:10.480> noticed<00:52:10.930> that 00:52:11.010 --> 00:52:11.020 align:start position:0% say one thing like lately I noticed that 00:52:11.020 --> 00:52:12.930 align:start position:0% say one thing like lately I noticed that in<00:52:11.140> III<00:52:11.380> search<00:52:11.650> some<00:52:12.040> posts<00:52:12.370> like<00:52:12.490> you<00:52:12.670> open<00:52:12.880> a 00:52:12.930 --> 00:52:12.940 align:start position:0% in III search some posts like you open a 00:52:12.940 --> 00:52:15.030 align:start position:0% in III search some posts like you open a new<00:52:13.060> thread<00:52:13.330> just<00:52:13.570> ask<00:52:13.840> a<00:52:13.990> question<00:52:14.170> then<00:52:14.920> do 00:52:15.030 --> 00:52:15.040 align:start position:0% new thread just ask a question then do 00:52:15.040 --> 00:52:17.700 align:start position:0% new thread just ask a question then do that<00:52:15.220> just<00:52:15.910> post<00:52:16.210> a<00:52:16.510> reply<00:52:16.780> on<00:52:17.230> the<00:52:17.260> existing 00:52:17.700 --> 00:52:17.710 align:start position:0% that just post a reply on the existing 00:52:17.710 --> 00:52:18.900 align:start position:0% that just post a reply on the existing threads<00:52:17.980> because<00:52:18.280> it's<00:52:18.400> impossible<00:52:18.610> to 00:52:18.900 --> 00:52:18.910 align:start position:0% threads because it's impossible to 00:52:18.910 --> 00:52:22.170 align:start position:0% threads because it's impossible to follow<00:52:19.030> they<00:52:20.370> there's<00:52:21.370> that<00:52:21.550> and<00:52:21.760> secondly<00:52:22.150> I 00:52:22.170 --> 00:52:22.180 align:start position:0% follow they there's that and secondly I 00:52:22.180 --> 00:52:24.090 align:start position:0% follow they there's that and secondly I believe<00:52:22.480> that<00:52:22.630> the<00:52:22.840> actual<00:52:23.260> contributions<00:52:23.920> to 00:52:24.090 --> 00:52:24.100 align:start position:0% believe that the actual contributions to 00:52:24.100 --> 00:52:25.380 align:start position:0% believe that the actual contributions to this<00:52:24.190> like<00:52:24.400> not<00:52:24.580> to<00:52:24.700> sound<00:52:24.820> hostile<00:52:25.330> or 00:52:25.380 --> 00:52:25.390 align:start position:0% this like not to sound hostile or 00:52:25.390 --> 00:52:25.830 align:start position:0% this like not to sound hostile or anything 00:52:25.830 --> 00:52:25.840 align:start position:0% anything 00:52:25.840 --> 00:52:28.560 align:start position:0% anything it<00:52:26.020> must<00:52:26.290> be<00:52:26.440> technical<00:52:26.860> like<00:52:27.400> try<00:52:27.880> to<00:52:27.940> search 00:52:28.560 --> 00:52:28.570 align:start position:0% it must be technical like try to search 00:52:28.570 --> 00:52:30.660 align:start position:0% it must be technical like try to search what<00:52:29.050> has<00:52:29.260> been<00:52:29.410> answered<00:52:29.770> already<00:52:30.040> because 00:52:30.660 --> 00:52:30.670 align:start position:0% what has been answered already because 00:52:30.670 --> 00:52:33.060 align:start position:0% what has been answered already because like<00:52:31.390> there<00:52:31.600> are<00:52:31.750> a<00:52:31.780> few<00:52:32.140> good<00:52:32.320> resources<00:52:32.740> and 00:52:33.060 --> 00:52:33.070 align:start position:0% like there are a few good resources and 00:52:33.070 --> 00:52:34.800 align:start position:0% like there are a few good resources and if<00:52:33.190> they<00:52:33.340> are<00:52:33.400> not<00:52:33.610> like<00:52:33.790> we're<00:52:34.480> compiling 00:52:34.800 --> 00:52:34.810 align:start position:0% if they are not like we're compiling 00:52:34.810 --> 00:52:37.500 align:start position:0% if they are not like we're compiling some<00:52:35.290> which<00:52:35.530> are<00:52:35.650> pretty<00:52:36.040> like<00:52:36.280> all<00:52:37.150> in<00:52:37.330> one 00:52:37.500 --> 00:52:37.510 align:start position:0% some which are pretty like all in one 00:52:37.510 --> 00:52:39.780 align:start position:0% some which are pretty like all in one but<00:52:38.260> generally<00:52:38.590> like<00:52:38.740> in<00:52:39.040> the<00:52:39.130> classic<00:52:39.370> forum 00:52:39.780 --> 00:52:39.790 align:start position:0% but generally like in the classic forum 00:52:39.790 --> 00:52:41.880 align:start position:0% but generally like in the classic forum mentality<00:52:40.720> like<00:52:40.810> don't<00:52:41.290> ask<00:52:41.410> the<00:52:41.530> same<00:52:41.680> things 00:52:41.880 --> 00:52:41.890 align:start position:0% mentality like don't ask the same things 00:52:41.890 --> 00:52:48.000 align:start position:0% mentality like don't ask the same things maybe<00:52:42.400> add<00:52:42.700> issues<00:52:43.180> to<00:52:45.180> but<00:52:46.180> like<00:52:46.330> it<00:52:46.480> is<00:52:46.890> and<00:52:47.890> I 00:52:48.000 --> 00:52:48.010 align:start position:0% maybe add issues to but like it is and I 00:52:48.010 --> 00:52:50.400 align:start position:0% maybe add issues to but like it is and I say<00:52:48.160> I<00:52:48.280> think<00:52:48.370> you<00:52:48.610> know<00:52:48.700> the<00:52:48.910> the<00:52:49.180> the<00:52:49.260> this<00:52:50.260> is 00:52:50.400 --> 00:52:50.410 align:start position:0% say I think you know the the the this is 00:52:50.410 --> 00:52:52.020 align:start position:0% say I think you know the the the this is an<00:52:50.500> open<00:52:50.830> community<00:52:51.190> as<00:52:51.340> well<00:52:51.550> but<00:52:51.850> definitely 00:52:52.020 --> 00:52:52.030 align:start position:0% an open community as well but definitely 00:52:52.030 --> 00:52:55.020 align:start position:0% an open community as well but definitely keep<00:52:52.480> it<00:52:52.600> as<00:52:52.690> technical<00:52:53.050> as<00:52:53.140> possible<00:52:53.530> I<00:52:54.130> would 00:52:55.020 --> 00:52:55.030 align:start position:0% keep it as technical as possible I would 00:52:55.030 --> 00:52:57.150 align:start position:0% keep it as technical as possible I would agree<00:52:55.180> with<00:52:55.270> that<00:52:55.420> and<00:52:55.840> but<00:52:56.320> you<00:52:56.560> know<00:52:56.680> this<00:52:56.950> is 00:52:57.150 --> 00:52:57.160 align:start position:0% agree with that and but you know this is 00:52:57.160 --> 00:52:59.040 align:start position:0% agree with that and but you know this is a<00:52:57.370> you<00:52:57.940> know<00:52:58.030> inclusive<00:52:58.600> community 00:52:59.040 --> 00:52:59.050 align:start position:0% a you know inclusive community 00:52:59.050 --> 00:53:01.310 align:start position:0% a you know inclusive community definitely<00:52:59.800> you<00:53:00.250> know<00:53:00.370> look<00:53:00.580> at<00:53:00.700> e3<00:53:00.880> search 00:53:01.310 --> 00:53:01.320 align:start position:0% definitely you know look at e3 search 00:53:01.320 --> 00:53:03.570 align:start position:0% definitely you know look at e3 search going<00:53:02.320> through<00:53:02.440> the<00:53:02.500> scientific<00:53:02.770> process<00:53:03.100> of 00:53:03.570 --> 00:53:03.580 align:start position:0% going through the scientific process of 00:53:03.580 --> 00:53:05.010 align:start position:0% going through the scientific process of learning<00:53:03.730> how<00:53:03.910> to<00:53:04.030> you<00:53:04.390> know<00:53:04.420> do<00:53:04.750> all<00:53:04.810> this 00:53:05.010 --> 00:53:05.020 align:start position:0% learning how to you know do all this 00:53:05.020 --> 00:53:09.230 align:start position:0% learning how to you know do all this stuff<00:53:05.140> thank<00:53:05.470> you<00:53:05.590> thank<00:53:06.580> you 00:53:09.230 --> 00:53:09.240 align:start position:0% 00:53:09.240 --> 00:53:18.030 align:start position:0% you 00:53:18.030 --> 00:53:18.040 align:start position:0% 00:53:18.040 --> 00:53:20.100 align:start position:0% you