WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:16.590 align:start position:0% [Music] 00:00:16.590 --> 00:00:16.600 align:start position:0% [Music] 00:00:16.600 --> 00:00:22.420 align:start position:0% [Music] takes<00:00:17.600> everyone<00:00:19.870> so<00:00:20.870> I'm<00:00:21.170> tasting<00:00:21.740> toys 00:00:22.420 --> 00:00:22.430 align:start position:0% takes everyone so I'm tasting toys 00:00:22.430 --> 00:00:27.190 align:start position:0% takes everyone so I'm tasting toys can<00:00:22.580> we<00:00:22.670> talk<00:00:22.790> about<00:00:22.910> true--but<00:00:23.390> I<00:00:25.660> yeah<00:00:26.660> so<00:00:26.900> in 00:00:27.190 --> 00:00:27.200 align:start position:0% can we talk about true--but I yeah so in 00:00:27.200 --> 00:00:29.800 align:start position:0% can we talk about true--but I yeah so in what<00:00:27.350> in<00:00:27.530> what<00:00:27.680> sense<00:00:27.950> am<00:00:28.160> i<00:00:28.280> introducing<00:00:28.810> the 00:00:29.800 --> 00:00:29.810 align:start position:0% what in what sense am i introducing the 00:00:29.810 --> 00:00:32.069 align:start position:0% what in what sense am i introducing the troop<00:00:30.050> adverse<00:00:30.320> in<00:00:30.860> so<00:00:31.550> some<00:00:31.820> of<00:00:31.880> you<00:00:31.940> remember 00:00:32.069 --> 00:00:32.079 align:start position:0% troop adverse in so some of you remember 00:00:32.079 --> 00:00:36.160 align:start position:0% troop adverse in so some of you remember last<00:00:33.079> year<00:00:33.379> at<00:00:33.469> Def<00:00:33.620> Con<00:00:33.680> to<00:00:34.660> Christian<00:00:35.660> right 00:00:36.160 --> 00:00:36.170 align:start position:0% last year at Def Con to Christian right 00:00:36.170 --> 00:00:38.350 align:start position:0% last year at Def Con to Christian right best<00:00:36.380> nerve<00:00:36.620> also<00:00:37.220> gave<00:00:37.490> a<00:00:37.520> talk<00:00:37.760> on<00:00:37.910> true<00:00:38.150> bit 00:00:38.350 --> 00:00:38.360 align:start position:0% best nerve also gave a talk on true bit 00:00:38.360 --> 00:00:41.110 align:start position:0% best nerve also gave a talk on true bit so<00:00:38.810> I'm<00:00:39.200> pleased<00:00:39.620> to<00:00:39.800> announce<00:00:40.610> here<00:00:40.850> today 00:00:41.110 --> 00:00:41.120 align:start position:0% so I'm pleased to announce here today 00:00:41.120 --> 00:00:45.790 align:start position:0% so I'm pleased to announce here today that<00:00:43.239> troop<00:00:44.239> it<00:00:44.360> is<00:00:44.480> up<00:00:44.630> on<00:00:44.780> the<00:00:44.930> covent<00:00:45.290> test 00:00:45.790 --> 00:00:45.800 align:start position:0% that troop it is up on the covent test 00:00:45.800 --> 00:00:48.580 align:start position:0% that troop it is up on the covent test net<00:00:46.040> you<00:00:46.820> can<00:00:46.970> take<00:00:47.120> a<00:00:47.149> piece<00:00:47.870> of<00:00:47.899> C<00:00:48.230> or<00:00:48.410> C++ 00:00:48.580 --> 00:00:48.590 align:start position:0% net you can take a piece of C or C++ 00:00:48.590 --> 00:00:51.250 align:start position:0% net you can take a piece of C or C++ code<00:00:49.250> and<00:00:49.489> run<00:00:50.210> a<00:00:50.239> verification<00:00:50.600> game<00:00:51.079> up 00:00:51.250 --> 00:00:51.260 align:start position:0% code and run a verification game up 00:00:51.260 --> 00:00:54.130 align:start position:0% code and run a verification game up there<00:00:51.290> all<00:00:52.160> the<00:00:52.340> code<00:00:52.550> is<00:00:52.700> up<00:00:52.820> on<00:00:52.970> our<00:00:53.140> github 00:00:54.130 --> 00:00:54.140 align:start position:0% there all the code is up on our github 00:00:54.140 --> 00:00:58.560 align:start position:0% there all the code is up on our github it's<00:00:54.559> all<00:00:54.790> open<00:00:55.790> source<00:00:56.000> so<00:00:56.600> dig<00:00:57.290> right<00:00:57.470> in<00:00:57.649> and 00:00:58.560 --> 00:00:58.570 align:start position:0% it's all open source so dig right in and 00:00:58.570 --> 00:01:02.080 align:start position:0% it's all open source so dig right in and I'd<00:00:59.570> also<00:00:59.750> like<00:00:59.930> to<00:01:00.829> thank<00:01:01.010> all<00:01:01.280> of<00:01:01.309> our<00:01:01.579> in 00:01:02.080 --> 00:01:02.090 align:start position:0% I'd also like to thank all of our in 00:01:02.090 --> 00:01:03.310 align:start position:0% I'd also like to thank all of our in addition<00:01:02.390> to<00:01:02.480> our<00:01:02.570> core<00:01:02.780> team<00:01:02.930> all<00:01:03.170> of<00:01:03.200> our 00:01:03.310 --> 00:01:03.320 align:start position:0% addition to our core team all of our 00:01:03.320 --> 00:01:06.539 align:start position:0% addition to our core team all of our open<00:01:03.770> source<00:01:04.129> contributors<00:01:04.939> who<00:01:05.089> have<00:01:05.210> been 00:01:06.539 --> 00:01:06.549 align:start position:0% open source contributors who have been 00:01:06.549 --> 00:01:09.310 align:start position:0% open source contributors who have been making<00:01:07.549> that<00:01:07.820> into<00:01:08.120> a<00:01:08.630> reality<00:01:08.900> we<00:01:09.110> are 00:01:09.310 --> 00:01:09.320 align:start position:0% making that into a reality we are 00:01:09.320 --> 00:01:14.890 align:start position:0% making that into a reality we are especially<00:01:12.370> senior<00:01:13.370> Vivien<00:01:13.700> and<00:01:13.850> Harley<00:01:14.600> swig 00:01:14.890 --> 00:01:14.900 align:start position:0% especially senior Vivien and Harley swig 00:01:14.900 --> 00:01:19.390 align:start position:0% especially senior Vivien and Harley swig so<00:01:17.320> some<00:01:18.320> of<00:01:18.350> you<00:01:18.470> may<00:01:18.590> be<00:01:18.619> old<00:01:19.040> enough<00:01:19.340> to 00:01:19.390 --> 00:01:19.400 align:start position:0% so some of you may be old enough to 00:01:19.400 --> 00:01:22.690 align:start position:0% so some of you may be old enough to remember<00:01:20.560> before<00:01:21.560> Bitcoin<00:01:22.340> there<00:01:22.580> was<00:01:22.670> a 00:01:22.690 --> 00:01:22.700 align:start position:0% remember before Bitcoin there was a 00:01:22.700 --> 00:01:24.670 align:start position:0% remember before Bitcoin there was a thing<00:01:22.909> called<00:01:22.940> Big<00:01:23.299> Data<00:01:23.510> and<00:01:23.810> you<00:01:24.530> could 00:01:24.670 --> 00:01:24.680 align:start position:0% thing called Big Data and you could 00:01:24.680 --> 00:01:25.920 align:start position:0% thing called Big Data and you could actually<00:01:24.799> store<00:01:25.159> stuff<00:01:25.460> on<00:01:25.640> your<00:01:25.729> computer 00:01:25.920 --> 00:01:25.930 align:start position:0% actually store stuff on your computer 00:01:25.930 --> 00:01:28.180 align:start position:0% actually store stuff on your computer you<00:01:26.930> could<00:01:27.110> use<00:01:27.320> the<00:01:27.440> computer<00:01:27.770> to<00:01:27.799> compute 00:01:28.180 --> 00:01:28.190 align:start position:0% you could use the computer to compute 00:01:28.190 --> 00:01:30.580 align:start position:0% you could use the computer to compute stuff<00:01:28.460> and<00:01:29.060> there<00:01:29.810> was<00:01:29.900> even<00:01:30.020> some<00:01:30.229> privacy 00:01:30.580 --> 00:01:30.590 align:start position:0% stuff and there was even some privacy 00:01:30.590 --> 00:01:34.450 align:start position:0% stuff and there was even some privacy features<00:01:31.130> well<00:01:32.710> etherium<00:01:33.710> sacrificed<00:01:34.250> all 00:01:34.450 --> 00:01:34.460 align:start position:0% features well etherium sacrificed all 00:01:34.460 --> 00:01:35.580 align:start position:0% features well etherium sacrificed all these<00:01:34.640> for<00:01:34.820> a<00:01:34.850> property<00:01:35.150> we<00:01:35.330> called 00:01:35.580 --> 00:01:35.590 align:start position:0% these for a property we called 00:01:35.590 --> 00:01:39.490 align:start position:0% these for a property we called immutability<00:01:36.590> and<00:01:38.020> that's<00:01:39.020> what<00:01:39.320> makes 00:01:39.490 --> 00:01:39.500 align:start position:0% immutability and that's what makes 00:01:39.500 --> 00:01:42.100 align:start position:0% immutability and that's what makes blockchains<00:01:40.040> amazing<00:01:40.869> they're<00:01:41.869> immutable 00:01:42.100 --> 00:01:42.110 align:start position:0% blockchains amazing they're immutable 00:01:42.110 --> 00:01:44.200 align:start position:0% blockchains amazing they're immutable they<00:01:42.799> have<00:01:42.950> some<00:01:43.310> sort<00:01:43.549> of<00:01:43.580> democratic 00:01:44.200 --> 00:01:44.210 align:start position:0% they have some sort of democratic 00:01:44.210 --> 00:01:48.640 align:start position:0% they have some sort of democratic equality<00:01:44.960> properties<00:01:45.409> to<00:01:45.590> them<00:01:46.810> but<00:01:47.810> we<00:01:48.229> are 00:01:48.640 --> 00:01:48.650 align:start position:0% equality properties to them but we are 00:01:48.650 --> 00:01:51.999 align:start position:0% equality properties to them but we are so<00:01:49.490> it's<00:01:50.420> it's<00:01:50.930> time<00:01:51.170> to<00:01:51.320> bring<00:01:51.500> the<00:01:51.619> big<00:01:51.799> data 00:01:51.999 --> 00:01:52.009 align:start position:0% so it's it's time to bring the big data 00:01:52.009 --> 00:01:53.230 align:start position:0% so it's it's time to bring the big data back<00:01:52.340> on<00:01:52.549> to<00:01:52.640> the<00:01:52.729> blockchain 00:01:53.230 --> 00:01:53.240 align:start position:0% back on to the blockchain 00:01:53.240 --> 00:01:56.380 align:start position:0% back on to the blockchain so<00:01:53.810> that's<00:01:54.080> true--but<00:01:54.890> is<00:01:55.130> taking<00:01:55.520> this<00:01:56.119> piece 00:01:56.380 --> 00:01:56.390 align:start position:0% so that's true--but is taking this piece 00:01:56.390 --> 00:01:58.390 align:start position:0% so that's true--but is taking this piece right<00:01:56.600> here<00:01:56.659> computation<00:01:57.590> and<00:01:58.009> that's<00:01:58.280> what 00:01:58.390 --> 00:01:58.400 align:start position:0% right here computation and that's what 00:01:58.400 --> 00:02:02.069 align:start position:0% right here computation and that's what we're<00:01:58.520> bringing<00:01:58.670> onto<00:01:58.939> the<00:01:59.030> blockchain<00:01:59.240> so 00:02:02.069 --> 00:02:02.079 align:start position:0% we're bringing onto the blockchain so 00:02:02.079 --> 00:02:04.840 align:start position:0% we're bringing onto the blockchain so and<00:02:03.079> there's<00:02:03.530> also<00:02:03.680> a<00:02:03.850> communication 00:02:04.840 --> 00:02:04.850 align:start position:0% and there's also a communication 00:02:04.850 --> 00:02:08.679 align:start position:0% and there's also a communication component<00:02:05.360> to<00:02:05.479> it<00:02:05.630> the<00:02:07.179> just<00:02:08.179> like<00:02:08.329> you<00:02:08.539> have 00:02:08.679 --> 00:02:08.689 align:start position:0% component to it the just like you have 00:02:08.689 --> 00:02:10.389 align:start position:0% component to it the just like you have the<00:02:08.810> internet<00:02:09.170> for<00:02:09.409> big<00:02:09.590> data<00:02:09.739> where<00:02:10.099> we're 00:02:10.389 --> 00:02:10.399 align:start position:0% the internet for big data where we're 00:02:10.399 --> 00:02:12.550 align:start position:0% the internet for big data where we're looking<00:02:10.520> at<00:02:10.819> something<00:02:11.599> like<00:02:11.840> dojo<00:02:12.349> theory 00:02:12.550 --> 00:02:12.560 align:start position:0% looking at something like dojo theory 00:02:12.560 --> 00:02:14.440 align:start position:0% looking at something like dojo theory and<00:02:12.709> bridge<00:02:12.890> a<00:02:12.920> way<00:02:13.190> of<00:02:13.340> bringing 00:02:14.440 --> 00:02:14.450 align:start position:0% and bridge a way of bringing 00:02:14.450 --> 00:02:16.699 align:start position:0% and bridge a way of bringing existing<00:02:15.450> bridge<00:02:15.690> take<00:02:16.140> the<00:02:16.230> tokens<00:02:16.590> off 00:02:16.699 --> 00:02:16.709 align:start position:0% existing bridge take the tokens off 00:02:16.709 --> 00:02:18.350 align:start position:0% existing bridge take the tokens off dogecoin<00:02:17.220> and<00:02:17.400> put<00:02:17.550> them<00:02:17.670> on<00:02:17.760> aetherium<00:02:18.090> and 00:02:18.350 --> 00:02:18.360 align:start position:0% dogecoin and put them on aetherium and 00:02:18.360 --> 00:02:20.600 align:start position:0% dogecoin and put them on aetherium and back<00:02:18.510> so<00:02:19.290> that's<00:02:19.650> that's<00:02:19.950> the<00:02:20.220> the 00:02:20.600 --> 00:02:20.610 align:start position:0% back so that's that's the the 00:02:20.610 --> 00:02:22.160 align:start position:0% back so that's that's the the functionality<00:02:21.209> we're<00:02:21.360> talking<00:02:21.660> about<00:02:21.750> here 00:02:22.160 --> 00:02:22.170 align:start position:0% functionality we're talking about here 00:02:22.170 --> 00:02:24.290 align:start position:0% functionality we're talking about here so<00:02:22.620> true--but<00:02:23.010> is<00:02:23.130> a<00:02:23.160> scalability<00:02:23.640> solution 00:02:24.290 --> 00:02:24.300 align:start position:0% so true--but is a scalability solution 00:02:24.300 --> 00:02:27.559 align:start position:0% so true--but is a scalability solution and<00:02:25.130> in<00:02:26.130> terms<00:02:26.670> of<00:02:26.760> the<00:02:26.819> storage<00:02:27.120> piece<00:02:27.390> so<00:02:27.510> I'm 00:02:27.559 --> 00:02:27.569 align:start position:0% and in terms of the storage piece so I'm 00:02:27.569 --> 00:02:29.690 align:start position:0% and in terms of the storage piece so I'm talking<00:02:27.720> about<00:02:27.840> true<00:02:28.140> bit<00:02:28.290> as<00:02:28.380> a<00:02:28.700> scalability 00:02:29.690 --> 00:02:29.700 align:start position:0% talking about true bit as a scalability 00:02:29.700 --> 00:02:33.650 align:start position:0% talking about true bit as a scalability solution<00:02:30.150> for<00:02:30.300> computation<00:02:30.959> but<00:02:32.390> if<00:02:33.390> you<00:02:33.540> look 00:02:33.650 --> 00:02:33.660 align:start position:0% solution for computation but if you look 00:02:33.660 --> 00:02:36.050 align:start position:0% solution for computation but if you look at<00:02:33.750> the<00:02:34.170> storage<00:02:34.530> situation<00:02:34.739> there<00:02:35.370> are<00:02:35.400> a<00:02:35.550> lot 00:02:36.050 --> 00:02:36.060 align:start position:0% at the storage situation there are a lot 00:02:36.060 --> 00:02:38.479 align:start position:0% at the storage situation there are a lot of<00:02:36.290> projects<00:02:37.290> already<00:02:37.470> looking<00:02:38.280> in<00:02:38.370> that 00:02:38.479 --> 00:02:38.489 align:start position:0% of projects already looking in that 00:02:38.489 --> 00:02:43.070 align:start position:0% of projects already looking in that space<00:02:38.970> already<00:02:41.540> most<00:02:42.540> of<00:02:42.690> them<00:02:42.810> are<00:02:42.900> more 00:02:43.070 --> 00:02:43.080 align:start position:0% space already most of them are more 00:02:43.080 --> 00:02:46.880 align:start position:0% space already most of them are more focused<00:02:43.410> on<00:02:44.330> privacy<00:02:45.330> than<00:02:45.720> then<00:02:46.200> data 00:02:46.880 --> 00:02:46.890 align:start position:0% focused on privacy than then data 00:02:46.890 --> 00:02:50.330 align:start position:0% focused on privacy than then data availability<00:02:47.370> but<00:02:47.819> there<00:02:48.480> is<00:02:49.340> interesting 00:02:50.330 --> 00:02:50.340 align:start position:0% availability but there is interesting 00:02:50.340 --> 00:02:51.410 align:start position:0% availability but there is interesting things<00:02:50.519> going<00:02:50.640> on<00:02:50.940> in<00:02:51.090> the<00:02:51.180> storage 00:02:51.410 --> 00:02:51.420 align:start position:0% things going on in the storage 00:02:51.420 --> 00:02:53.449 align:start position:0% things going on in the storage department<00:02:52.019> fact<00:02:52.560> there's<00:02:52.769> interesting 00:02:53.449 --> 00:02:53.459 align:start position:0% department fact there's interesting 00:02:53.459 --> 00:02:54.920 align:start position:0% department fact there's interesting stuff<00:02:53.670> going<00:02:53.700> on<00:02:54.000> everywhere<00:02:54.420> I<00:02:54.480> guess<00:02:54.720> that's 00:02:54.920 --> 00:02:54.930 align:start position:0% stuff going on everywhere I guess that's 00:02:54.930 --> 00:02:57.949 align:start position:0% stuff going on everywhere I guess that's why<00:02:55.080> we're<00:02:55.260> here<00:02:55.790> but<00:02:56.790> what<00:02:57.090> what<00:02:57.480> what<00:02:57.810> is<00:02:57.930> it 00:02:57.949 --> 00:02:57.959 align:start position:0% why we're here but what what what is it 00:02:57.959 --> 00:02:59.900 align:start position:0% why we're here but what what what is it about<00:02:58.110> true<00:02:58.470> bit<00:02:58.680> what<00:02:58.950> are<00:02:58.980> we<00:02:59.130> here<00:02:59.730> to<00:02:59.880> talk 00:02:59.900 --> 00:02:59.910 align:start position:0% about true bit what are we here to talk 00:02:59.910 --> 00:03:02.000 align:start position:0% about true bit what are we here to talk about<00:03:00.090> today<00:03:00.510> is<00:03:00.660> a<00:03:00.690> process<00:03:01.440> which<00:03:01.560> we<00:03:01.769> called 00:03:02.000 --> 00:03:02.010 align:start position:0% about today is a process which we called 00:03:02.010 --> 00:03:05.449 align:start position:0% about today is a process which we called interactive<00:03:02.910> verification<00:03:03.799> okay<00:03:04.799> and<00:03:05.010> and 00:03:05.449 --> 00:03:05.459 align:start position:0% interactive verification okay and and 00:03:05.459 --> 00:03:09.500 align:start position:0% interactive verification okay and and what<00:03:05.760> is<00:03:05.850> it<00:03:06.030> this<00:03:06.480> is<00:03:07.970> what<00:03:08.970> are<00:03:09.030> we<00:03:09.120> focused 00:03:09.500 --> 00:03:09.510 align:start position:0% what is it this is what are we focused 00:03:09.510 --> 00:03:10.610 align:start position:0% what is it this is what are we focused on<00:03:09.630> true--but<00:03:09.930> is<00:03:10.049> focused<00:03:10.380> on<00:03:10.440> large 00:03:10.610 --> 00:03:10.620 align:start position:0% on true--but is focused on large 00:03:10.620 --> 00:03:12.559 align:start position:0% on true--but is focused on large transactions<00:03:11.459> so<00:03:11.610> if<00:03:11.700> you<00:03:11.819> we've<00:03:12.209> had<00:03:12.239> a<00:03:12.360> few 00:03:12.559 --> 00:03:12.569 align:start position:0% transactions so if you we've had a few 00:03:12.569 --> 00:03:15.199 align:start position:0% transactions so if you we've had a few talks<00:03:13.049> just<00:03:13.350> recently<00:03:13.769> about<00:03:13.950> sharding<00:03:14.910> so 00:03:15.199 --> 00:03:15.209 align:start position:0% talks just recently about sharding so 00:03:15.209 --> 00:03:16.729 align:start position:0% talks just recently about sharding so we're<00:03:15.480> true--but<00:03:16.019> is<00:03:16.170> not<00:03:16.290> going<00:03:16.470> to<00:03:16.530> assume 00:03:16.729 --> 00:03:16.739 align:start position:0% we're true--but is not going to assume 00:03:16.739 --> 00:03:19.280 align:start position:0% we're true--but is not going to assume that<00:03:16.860> you<00:03:16.950> can<00:03:17.100> take<00:03:17.700> your<00:03:17.880> transaction<00:03:18.690> set 00:03:19.280 --> 00:03:19.290 align:start position:0% that you can take your transaction set 00:03:19.290 --> 00:03:20.930 align:start position:0% that you can take your transaction set and<00:03:19.500> break<00:03:19.709> it<00:03:19.829> up<00:03:19.920> into<00:03:20.100> smaller<00:03:20.370> pieces<00:03:20.459> you 00:03:20.930 --> 00:03:20.940 align:start position:0% and break it up into smaller pieces you 00:03:20.940 --> 00:03:22.699 align:start position:0% and break it up into smaller pieces you have<00:03:20.970> a<00:03:21.090> massive<00:03:21.570> transaction<00:03:22.230> that's<00:03:22.380> coming 00:03:22.699 --> 00:03:22.709 align:start position:0% have a massive transaction that's coming 00:03:22.709 --> 00:03:24.620 align:start position:0% have a massive transaction that's coming in<00:03:22.859> and<00:03:22.980> you<00:03:23.400> have<00:03:23.430> to<00:03:23.670> process<00:03:23.910> it<00:03:24.150> so<00:03:24.450> that's 00:03:24.620 --> 00:03:24.630 align:start position:0% in and you have to process it so that's 00:03:24.630 --> 00:03:28.550 align:start position:0% in and you have to process it so that's that's<00:03:25.230> what<00:03:25.470> true<00:03:25.680> bid<00:03:25.829> is<00:03:25.950> all<00:03:26.070> about<00:03:27.109> ok<00:03:28.109> so 00:03:28.550 --> 00:03:28.560 align:start position:0% that's what true bid is all about ok so 00:03:28.560 --> 00:03:33.020 align:start position:0% that's what true bid is all about ok so what's<00:03:28.799> what's<00:03:29.310> the<00:03:29.430> problem<00:03:31.880> what<00:03:32.880> are<00:03:32.910> we 00:03:33.020 --> 00:03:33.030 align:start position:0% what's what's the problem what are we 00:03:33.030 --> 00:03:34.460 align:start position:0% what's what's the problem what are we trying<00:03:33.180> to<00:03:33.269> solve<00:03:33.450> here<00:03:33.660> I<00:03:33.870> guess<00:03:34.320> I<00:03:34.410> don't 00:03:34.460 --> 00:03:34.470 align:start position:0% trying to solve here I guess I don't 00:03:34.470 --> 00:03:35.930 align:start position:0% trying to solve here I guess I don't really<00:03:34.590> have<00:03:34.769> to<00:03:34.950> tell<00:03:35.130> this<00:03:35.280> audience<00:03:35.400> what<00:03:35.910> a 00:03:35.930 --> 00:03:35.940 align:start position:0% really have to tell this audience what a 00:03:35.940 --> 00:03:39.949 align:start position:0% really have to tell this audience what a smart<00:03:36.209> contract<00:03:36.720> is<00:03:36.930> but<00:03:37.920> I<00:03:38.190> do<00:03:38.400> want<00:03:38.760> to<00:03:38.959> point 00:03:39.949 --> 00:03:39.959 align:start position:0% smart contract is but I do want to point 00:03:39.959 --> 00:03:43.819 align:start position:0% smart contract is but I do want to point out<00:03:40.109> a<00:03:40.760> sort<00:03:41.760> of<00:03:42.109> critical<00:03:43.109> property<00:03:43.650> of<00:03:43.739> the 00:03:43.819 --> 00:03:43.829 align:start position:0% out a sort of critical property of the 00:03:43.829 --> 00:03:48.380 align:start position:0% out a sort of critical property of the smart<00:03:44.040> contract<00:03:44.220> is<00:03:44.609> that<00:03:44.760> they<00:03:44.910> only<00:03:47.390> this 00:03:48.380 --> 00:03:48.390 align:start position:0% smart contract is that they only this 00:03:48.390 --> 00:03:49.910 align:start position:0% smart contract is that they only this sign<00:03:48.930> at<00:03:49.049> the<00:03:49.140> bottom<00:03:49.350> which<00:03:49.470> you<00:03:49.590> can<00:03:49.709> see<00:03:49.890> now 00:03:49.910 --> 00:03:49.920 align:start position:0% sign at the bottom which you can see now 00:03:49.920 --> 00:03:52.699 align:start position:0% sign at the bottom which you can see now says<00:03:50.280> small<00:03:50.549> computations<00:03:51.239> only<00:03:51.600> you're<00:03:52.350> not 00:03:52.699 --> 00:03:52.709 align:start position:0% says small computations only you're not 00:03:52.709 --> 00:03:56.390 align:start position:0% says small computations only you're not running<00:03:53.400> computations<00:03:54.150> that<00:03:54.480> run<00:03:54.720> for<00:03:55.400> hours 00:03:56.390 --> 00:03:56.400 align:start position:0% running computations that run for hours 00:03:56.400 --> 00:03:57.740 align:start position:0% running computations that run for hours or<00:03:56.579> even<00:03:56.609> minutes<00:03:56.880> I<00:03:57.239> mean<00:03:57.359> they<00:03:57.480> don't<00:03:57.569> even 00:03:57.740 --> 00:03:57.750 align:start position:0% or even minutes I mean they don't even 00:03:57.750 --> 00:04:00.740 align:start position:0% or even minutes I mean they don't even run<00:03:58.019> for<00:03:58.500> for<00:03:58.890> a<00:03:58.920> second<00:03:59.340> so<00:03:59.579> that's<00:04:00.239> that's 00:04:00.740 --> 00:04:00.750 align:start position:0% run for for a second so that's that's 00:04:00.750 --> 00:04:02.710 align:start position:0% run for for a second so that's that's what<00:04:01.650> we<00:04:01.769> mean<00:04:01.859> about<00:04:02.010> scalability 00:04:02.710 --> 00:04:02.720 align:start position:0% what we mean about scalability 00:04:02.720 --> 00:04:06.289 align:start position:0% what we mean about scalability computations<00:04:03.720> actually<00:04:04.140> run<00:04:04.319> so<00:04:04.880> the<00:04:05.880> length 00:04:06.289 --> 00:04:06.299 align:start position:0% computations actually run so the length 00:04:06.299 --> 00:04:07.580 align:start position:0% computations actually run so the length of<00:04:06.450> the<00:04:06.510> computation<00:04:07.049> you<00:04:07.140> can<00:04:07.290> run<00:04:07.440> is 00:04:07.580 --> 00:04:07.590 align:start position:0% of the computation you can run is 00:04:07.590 --> 00:04:11.479 align:start position:0% of the computation you can run is bounded<00:04:07.950> by<00:04:08.100> aetherium<00:04:08.790> x'<00:04:08.819> gas<00:04:09.030> limit<00:04:09.480> so<00:04:10.489> the 00:04:11.479 --> 00:04:11.489 align:start position:0% bounded by aetherium x' gas limit so the 00:04:11.489 --> 00:04:13.550 align:start position:0% bounded by aetherium x' gas limit so the obvious<00:04:11.639> thing<00:04:11.910> let's<00:04:12.329> get<00:04:13.260> the<00:04:13.380> elephant 00:04:13.550 --> 00:04:13.560 align:start position:0% obvious thing let's get the elephant 00:04:13.560 --> 00:04:15.319 align:start position:0% obvious thing let's get the elephant other<00:04:13.829> room<00:04:13.950> why<00:04:14.040> don't<00:04:14.220> we<00:04:14.280> just<00:04:14.489> dump<00:04:15.150> the 00:04:15.319 --> 00:04:15.329 align:start position:0% other room why don't we just dump the 00:04:15.329 --> 00:04:20.870 align:start position:0% other room why don't we just dump the gas<00:04:15.510> limit<00:04:15.780> so<00:04:18.079> first<00:04:19.079> so<00:04:19.530> what<00:04:20.519> is<00:04:20.639> the<00:04:20.729> gas 00:04:20.870 --> 00:04:20.880 align:start position:0% gas limit so first so what is the gas 00:04:20.880 --> 00:04:22.820 align:start position:0% gas limit so first so what is the gas limit<00:04:21.060> a<00:04:21.329> theory<00:04:21.720> a<00:04:21.810> meter<00:04:22.049> smart<00:04:22.409> contract 00:04:22.820 --> 00:04:22.830 align:start position:0% limit a theory a meter smart contract 00:04:22.830 --> 00:04:25.310 align:start position:0% limit a theory a meter smart contract storage<00:04:23.159> and<00:04:23.310> compute<00:04:23.610> resources<00:04:23.990> with<00:04:24.990> a 00:04:25.310 --> 00:04:25.320 align:start position:0% storage and compute resources with a 00:04:25.320 --> 00:04:26.970 align:start position:0% storage and compute resources with a measurement<00:04:25.650> they<00:04:25.830> call<00:04:25.950> gas 00:04:26.970 --> 00:04:26.980 align:start position:0% measurement they call gas 00:04:26.980 --> 00:04:29.340 align:start position:0% measurement they call gas and<00:04:27.070> the<00:04:27.520> gas<00:04:27.700> limit<00:04:28.330> is<00:04:28.630> the<00:04:28.780> maximum<00:04:28.810> amount 00:04:29.340 --> 00:04:29.350 align:start position:0% and the gas limit is the maximum amount 00:04:29.350 --> 00:04:30.990 align:start position:0% and the gas limit is the maximum amount of<00:04:29.410> gas<00:04:29.590> that<00:04:29.770> you<00:04:29.860> could<00:04:30.040> allowed<00:04:30.220> per<00:04:30.730> block 00:04:30.990 --> 00:04:31.000 align:start position:0% of gas that you could allowed per block 00:04:31.000 --> 00:04:32.730 align:start position:0% of gas that you could allowed per block it's<00:04:31.450> not<00:04:31.570> per<00:04:31.720> student<00:04:31.990> transaction<00:04:32.590> it's 00:04:32.730 --> 00:04:32.740 align:start position:0% it's not per student transaction it's 00:04:32.740 --> 00:04:37.170 align:start position:0% it's not per student transaction it's it's<00:04:33.040> per<00:04:33.250> block<00:04:33.490> and<00:04:34.230> so<00:04:35.230> so<00:04:35.950> why<00:04:36.850> do<00:04:36.910> we<00:04:37.060> have 00:04:37.170 --> 00:04:37.180 align:start position:0% it's per block and so so why do we have 00:04:37.180 --> 00:04:39.030 align:start position:0% it's per block and so so why do we have the<00:04:37.330> gas<00:04:37.480> limit<00:04:37.780> that's<00:04:38.170> that's<00:04:38.590> that's<00:04:38.890> a 00:04:39.030 --> 00:04:39.040 align:start position:0% the gas limit that's that's that's a 00:04:39.040 --> 00:04:41.430 align:start position:0% the gas limit that's that's that's a question<00:04:39.220> so<00:04:39.640> reason<00:04:40.600> a<00:04:40.690> is<00:04:40.750> it<00:04:40.960> because<00:04:41.200> every 00:04:41.430 --> 00:04:41.440 align:start position:0% question so reason a is it because every 00:04:41.440 --> 00:04:43.050 align:start position:0% question so reason a is it because every miner<00:04:41.620> has<00:04:41.890> to<00:04:42.040> replicate<00:04:42.430> every<00:04:42.670> aetherium 00:04:43.050 --> 00:04:43.060 align:start position:0% miner has to replicate every aetherium 00:04:43.060 --> 00:04:46.110 align:start position:0% miner has to replicate every aetherium computation<00:04:43.780> B<00:04:44.740> it's<00:04:45.670> because<00:04:45.880> we're<00:04:46.060> moving 00:04:46.110 --> 00:04:46.120 align:start position:0% computation B it's because we're moving 00:04:46.120 --> 00:04:47.370 align:start position:0% computation B it's because we're moving the<00:04:46.330> gas<00:04:46.480> limit<00:04:46.720> would<00:04:46.930> leave<00:04:47.080> aetherium 00:04:47.370 --> 00:04:47.380 align:start position:0% the gas limit would leave aetherium 00:04:47.380 --> 00:04:49.730 align:start position:0% the gas limit would leave aetherium vulnerable<00:04:47.950> to<00:04:48.100> denial<00:04:48.430> of<00:04:48.610> service<00:04:48.940> attacks 00:04:49.730 --> 00:04:49.740 align:start position:0% vulnerable to denial of service attacks 00:04:49.740 --> 00:04:52.230 align:start position:0% vulnerable to denial of service attacks is<00:04:50.740> it<00:04:50.980> C<00:04:51.130> because<00:04:51.400> the<00:04:51.490> gas<00:04:51.640> limit<00:04:51.880> helps 00:04:52.230 --> 00:04:52.240 align:start position:0% is it C because the gas limit helps 00:04:52.240 --> 00:04:54.240 align:start position:0% is it C because the gas limit helps incentivize<00:04:52.930> verification<00:04:53.830> it<00:04:54.010> helps 00:04:54.240 --> 00:04:54.250 align:start position:0% incentivize verification it helps 00:04:54.250 --> 00:04:56.310 align:start position:0% incentivize verification it helps incentivize<00:04:54.790> transaction<00:04:55.450> verification<00:04:55.570> or 00:04:56.310 --> 00:04:56.320 align:start position:0% incentivize transaction verification or 00:04:56.320 --> 00:04:58.650 align:start position:0% incentivize transaction verification or is<00:04:57.130> it<00:04:57.250> just<00:04:57.460> the<00:04:57.640> metallic<00:04:58.390> you<00:04:58.450> trans 00:04:58.650 --> 00:04:58.660 align:start position:0% is it just the metallic you trans 00:04:58.660 --> 00:05:00.660 align:start position:0% is it just the metallic you trans secretly<00:04:58.990> doesn't<00:04:59.320> want<00:04:59.470> aetherium<00:05:00.040> to<00:05:00.430> scale 00:05:00.660 --> 00:05:00.670 align:start position:0% secretly doesn't want aetherium to scale 00:05:00.670 --> 00:05:03.960 align:start position:0% secretly doesn't want aetherium to scale well<00:05:01.360> I<00:05:01.690> think<00:05:02.200> we<00:05:02.500> can<00:05:02.680> quickly<00:05:03.310> cross<00:05:03.640> out<00:05:03.820> D 00:05:03.960 --> 00:05:03.970 align:start position:0% well I think we can quickly cross out D 00:05:03.970 --> 00:05:05.460 align:start position:0% well I think we can quickly cross out D because<00:05:04.150> it's<00:05:04.300> not<00:05:04.450> a<00:05:04.480> secret<00:05:04.780> anymore<00:05:05.050> I<00:05:05.170> told 00:05:05.460 --> 00:05:05.470 align:start position:0% because it's not a secret anymore I told 00:05:05.470 --> 00:05:07.770 align:start position:0% because it's not a secret anymore I told this<00:05:05.620> same<00:05:05.980> joke<00:05:06.250> a<00:05:06.520> few<00:05:06.760> weeks<00:05:06.910> ago<00:05:07.030> at<00:05:07.210> CES<00:05:07.570> C 00:05:07.770 --> 00:05:07.780 align:start position:0% this same joke a few weeks ago at CES C 00:05:07.780 --> 00:05:11.730 align:start position:0% this same joke a few weeks ago at CES C so<00:05:08.850> now<00:05:09.850> what<00:05:10.840> I<00:05:10.870> do<00:05:10.990> want<00:05:11.200> to<00:05:11.290> do<00:05:11.380> is<00:05:11.500> convince 00:05:11.730 --> 00:05:11.740 align:start position:0% so now what I do want to do is convince 00:05:11.740 --> 00:05:13.860 align:start position:0% so now what I do want to do is convince you<00:05:11.950> that<00:05:12.010> C<00:05:12.430> is<00:05:12.670> well<00:05:13.060> I<00:05:13.090> say<00:05:13.480> all<00:05:13.660> these 00:05:13.860 --> 00:05:13.870 align:start position:0% you that C is well I say all these 00:05:13.870 --> 00:05:16.320 align:start position:0% you that C is well I say all these answers<00:05:14.170> are<00:05:14.350> true<00:05:15.040> but<00:05:15.460> C<00:05:15.760> is<00:05:15.880> more<00:05:16.060> true<00:05:16.300> than 00:05:16.320 --> 00:05:16.330 align:start position:0% answers are true but C is more true than 00:05:16.330 --> 00:05:18.450 align:start position:0% answers are true but C is more true than all<00:05:16.600> the<00:05:16.750> others<00:05:16.990> so<00:05:17.230> this<00:05:17.470> is<00:05:17.680> this<00:05:18.100> is<00:05:18.160> what<00:05:18.430> I 00:05:18.450 --> 00:05:18.460 align:start position:0% all the others so this is this is what I 00:05:18.460 --> 00:05:20.160 align:start position:0% all the others so this is this is what I want<00:05:18.670> to<00:05:18.790> convince<00:05:19.030> you<00:05:19.240> in<00:05:19.360> the<00:05:19.450> next<00:05:19.660> three 00:05:20.160 --> 00:05:20.170 align:start position:0% want to convince you in the next three 00:05:20.170 --> 00:05:22.320 align:start position:0% want to convince you in the next three slides<00:05:20.320> that<00:05:21.160> C<00:05:21.580> is<00:05:21.700> actually<00:05:22.090> the<00:05:22.210> right 00:05:22.320 --> 00:05:22.330 align:start position:0% slides that C is actually the right 00:05:22.330 --> 00:05:24.900 align:start position:0% slides that C is actually the right answer<00:05:22.630> to<00:05:22.660> this<00:05:22.900> question<00:05:23.610> so<00:05:24.610> let's<00:05:24.790> see 00:05:24.900 --> 00:05:24.910 align:start position:0% answer to this question so let's see 00:05:24.910 --> 00:05:26.730 align:start position:0% answer to this question so let's see what<00:05:25.030> happens<00:05:25.360> without<00:05:25.480> the<00:05:25.750> gas<00:05:25.870> limit<00:05:26.290> okay 00:05:26.730 --> 00:05:26.740 align:start position:0% what happens without the gas limit okay 00:05:26.740 --> 00:05:30.390 align:start position:0% what happens without the gas limit okay so<00:05:26.950> no<00:05:27.700> gas<00:05:27.940> limit<00:05:28.330> you<00:05:28.450> have<00:05:28.480> a<00:05:29.260> guy<00:05:29.590> with<00:05:29.650> two 00:05:30.390 --> 00:05:30.400 align:start position:0% so no gas limit you have a guy with two 00:05:30.400 --> 00:05:32.310 align:start position:0% so no gas limit you have a guy with two pointy<00:05:30.790> horns<00:05:31.060> comes<00:05:31.390> in<00:05:31.570> with<00:05:31.690> a<00:05:31.720> heavy 00:05:32.310 --> 00:05:32.320 align:start position:0% pointy horns comes in with a heavy 00:05:32.320 --> 00:05:34.830 align:start position:0% pointy horns comes in with a heavy transaction<00:05:33.100> he<00:05:33.460> incentivizes<00:05:34.210> it<00:05:34.360> nicely<00:05:34.600> so 00:05:34.830 --> 00:05:34.840 align:start position:0% transaction he incentivizes it nicely so 00:05:34.840 --> 00:05:37.140 align:start position:0% transaction he incentivizes it nicely so someone<00:05:35.740> is<00:05:35.830> bound<00:05:36.040> to<00:05:36.310> pick<00:05:36.520> it<00:05:36.670> up<00:05:36.760> you<00:05:36.820> put<00:05:37.120> a 00:05:37.140 --> 00:05:37.150 align:start position:0% someone is bound to pick it up you put a 00:05:37.150 --> 00:05:40.560 align:start position:0% someone is bound to pick it up you put a big<00:05:37.390> nice<00:05:37.840> big<00:05:38.110> transaction<00:05:38.530> fee<00:05:39.300> so<00:05:40.300> a<00:05:40.330> miner 00:05:40.560 --> 00:05:40.570 align:start position:0% big nice big transaction fee so a miner 00:05:40.570 --> 00:05:42.270 align:start position:0% big nice big transaction fee so a miner comes<00:05:40.870> in<00:05:41.080> mines<00:05:41.500> the<00:05:41.650> block<00:05:41.860> he<00:05:41.980> says<00:05:42.130> sure 00:05:42.270 --> 00:05:42.280 align:start position:0% comes in mines the block he says sure 00:05:42.280 --> 00:05:44.340 align:start position:0% comes in mines the block he says sure I'll<00:05:42.310> I'll<00:05:42.550> include<00:05:42.850> that<00:05:42.880> because<00:05:43.390> he's<00:05:43.960> got 00:05:44.340 --> 00:05:44.350 align:start position:0% I'll I'll include that because he's got 00:05:44.350 --> 00:05:46.380 align:start position:0% I'll I'll include that because he's got an<00:05:44.800> incentive<00:05:45.250> for<00:05:45.280> it<00:05:45.550> and<00:05:45.730> one<00:05:46.060> of<00:05:46.090> the<00:05:46.240> rest 00:05:46.380 --> 00:05:46.390 align:start position:0% an incentive for it and one of the rest 00:05:46.390 --> 00:05:49.290 align:start position:0% an incentive for it and one of the rest of<00:05:46.510> the<00:05:46.570> miners<00:05:46.900> do<00:05:47.140> they<00:05:47.710> just<00:05:47.980> get<00:05:48.300> like 00:05:49.290 --> 00:05:49.300 align:start position:0% of the miners do they just get like 00:05:49.300 --> 00:05:51.480 align:start position:0% of the miners do they just get like completely<00:05:49.600> confused<00:05:50.530> right<00:05:50.770> because<00:05:51.220> they 00:05:51.480 --> 00:05:51.490 align:start position:0% completely confused right because they 00:05:51.490 --> 00:05:54.150 align:start position:0% completely confused right because they will<00:05:51.970> what<00:05:52.450> what<00:05:52.750> why<00:05:53.260> are<00:05:53.320> they<00:05:53.500> confused<00:05:53.920> so 00:05:54.150 --> 00:05:54.160 align:start position:0% will what what why are they confused so 00:05:54.160 --> 00:05:57.750 align:start position:0% will what what why are they confused so this<00:05:54.940> is<00:05:55.090> a<00:05:55.650> let's<00:05:56.650> look<00:05:57.190> it<00:05:57.340> a<00:05:57.370> little<00:05:57.580> bit 00:05:57.750 --> 00:05:57.760 align:start position:0% this is a let's look it a little bit 00:05:57.760 --> 00:06:00.150 align:start position:0% this is a let's look it a little bit into<00:05:58.060> their<00:05:58.210> confusion<00:05:58.660> so<00:05:58.980> what<00:05:59.980> are<00:06:00.070> they 00:06:00.150 --> 00:06:00.160 align:start position:0% into their confusion so what are they 00:06:00.160 --> 00:06:02.070 align:start position:0% into their confusion so what are they confused<00:06:00.340> about<00:06:00.700> so<00:06:01.270> this<00:06:01.360> is<00:06:01.510> this<00:06:01.960> is 00:06:02.070 --> 00:06:02.080 align:start position:0% confused about so this is this is 00:06:02.080 --> 00:06:06.960 align:start position:0% confused about so this is this is actually<00:06:02.230> a<00:06:02.470> principle<00:06:03.370> which<00:06:03.490> we<00:06:03.670> call<00:06:05.970> the 00:06:06.960 --> 00:06:06.970 align:start position:0% actually a principle which we call the 00:06:06.970 --> 00:06:08.040 align:start position:0% actually a principle which we call the verifiers<00:06:07.360> dilemma 00:06:08.040 --> 00:06:08.050 align:start position:0% verifiers dilemma 00:06:08.050 --> 00:06:11.010 align:start position:0% verifiers dilemma so<00:06:08.770> in<00:06:09.700> the<00:06:09.850> case<00:06:10.000> of<00:06:10.120> a<00:06:10.180> heavy<00:06:10.360> transaction 00:06:11.010 --> 00:06:11.020 align:start position:0% so in the case of a heavy transaction 00:06:11.020 --> 00:06:13.260 align:start position:0% so in the case of a heavy transaction what<00:06:11.200> should<00:06:11.350> a<00:06:11.380> rational<00:06:11.830> miner<00:06:12.040> do<00:06:12.340> rational 00:06:13.260 --> 00:06:13.270 align:start position:0% what should a rational miner do rational 00:06:13.270 --> 00:06:16.380 align:start position:0% what should a rational miner do rational miner<00:06:13.450> being<00:06:13.720> somebody<00:06:14.110> who<00:06:14.290> likes<00:06:15.040> to<00:06:15.400> earn 00:06:16.380 --> 00:06:16.390 align:start position:0% miner being somebody who likes to earn 00:06:16.390 --> 00:06:22.770 align:start position:0% miner being somebody who likes to earn more<00:06:16.690> ether<00:06:18.000> so<00:06:21.090> number<00:06:22.090> one<00:06:22.270> skipping 00:06:22.770 --> 00:06:22.780 align:start position:0% more ether so number one skipping 00:06:22.780 --> 00:06:24.720 align:start position:0% more ether so number one skipping verification<00:06:23.380> affords<00:06:23.710> an<00:06:23.830> advantage<00:06:24.250> in<00:06:24.550> the 00:06:24.720 --> 00:06:24.730 align:start position:0% verification affords an advantage in the 00:06:24.730 --> 00:06:26.970 align:start position:0% verification affords an advantage in the mining<00:06:25.030> race<00:06:25.180> so<00:06:25.630> therefore<00:06:26.020> he<00:06:26.140> has<00:06:26.650> a<00:06:26.710> reason 00:06:26.970 --> 00:06:26.980 align:start position:0% mining race so therefore he has a reason 00:06:26.980 --> 00:06:30.420 align:start position:0% mining race so therefore he has a reason to<00:06:27.010> skip<00:06:27.220> the<00:06:27.370> verification<00:06:29.100> mining<00:06:30.100> on<00:06:30.310> the 00:06:30.420 --> 00:06:30.430 align:start position:0% to skip the verification mining on the 00:06:30.430 --> 00:06:32.130 align:start position:0% to skip the verification mining on the wrong<00:06:30.550> chain<00:06:30.940> on<00:06:31.300> the<00:06:31.390> other<00:06:31.510> hand<00:06:31.720> means<00:06:31.930> that 00:06:32.130 --> 00:06:32.140 align:start position:0% wrong chain on the other hand means that 00:06:32.140 --> 00:06:34.110 align:start position:0% wrong chain on the other hand means that other<00:06:32.350> miners<00:06:32.740> will<00:06:33.070> ignore<00:06:33.370> the<00:06:33.670> found<00:06:33.880> block 00:06:34.110 --> 00:06:34.120 align:start position:0% other miners will ignore the found block 00:06:34.120 --> 00:06:35.880 align:start position:0% other miners will ignore the found block so<00:06:34.360> therefore<00:06:34.720> you<00:06:34.810> should<00:06:34.960> skip<00:06:35.500> the<00:06:35.680> very 00:06:35.880 --> 00:06:35.890 align:start position:0% so therefore you should skip the very 00:06:35.890 --> 00:06:37.700 align:start position:0% so therefore you should skip the very therefore<00:06:36.850> you<00:06:36.940> should<00:06:37.120> do<00:06:37.240> the<00:06:37.360> verification 00:06:37.700 --> 00:06:37.710 align:start position:0% therefore you should do the verification 00:06:37.710 --> 00:06:40.679 align:start position:0% therefore you should do the verification so<00:06:38.710> it<00:06:39.400> should<00:06:39.700> be<00:06:39.730> clear<00:06:39.970> from<00:06:40.090> looking 00:06:40.679 --> 00:06:40.689 align:start position:0% so it should be clear from looking 00:06:40.689 --> 00:06:42.149 align:start position:0% so it should be clear from looking these<00:06:40.839> two<00:06:41.080> statements<00:06:41.589> that<00:06:41.709> rationality 00:06:42.149 --> 00:06:42.159 align:start position:0% these two statements that rationality 00:06:42.159 --> 00:06:44.399 align:start position:0% these two statements that rationality doesn't<00:06:42.459> actually<00:06:42.580> help<00:06:43.119> you<00:06:43.330> decide<00:06:43.629> what<00:06:44.379> to 00:06:44.399 --> 00:06:44.409 align:start position:0% doesn't actually help you decide what to 00:06:44.409 --> 00:06:46.169 align:start position:0% doesn't actually help you decide what to do<00:06:44.679> so<00:06:44.979> the<00:06:45.099> miners<00:06:45.339> want<00:06:45.729> to<00:06:45.879> do<00:06:45.969> whatever 00:06:46.169 --> 00:06:46.179 align:start position:0% do so the miners want to do whatever 00:06:46.179 --> 00:06:48.989 align:start position:0% do so the miners want to do whatever other<00:06:46.749> miners<00:06:47.169> are<00:06:47.439> doing<00:06:47.860> so<00:06:48.159> so<00:06:48.879> that's 00:06:48.989 --> 00:06:48.999 align:start position:0% other miners are doing so so that's 00:06:48.999 --> 00:06:58.649 align:start position:0% other miners are doing so so that's that's<00:06:49.239> the<00:06:51.839> verifiers<00:06:52.839> dilemma<00:06:53.199> so<00:06:53.529> so<00:06:57.659> so 00:06:58.649 --> 00:06:58.659 align:start position:0% that's the verifiers dilemma so so so 00:06:58.659 --> 00:07:01.229 align:start position:0% that's the verifiers dilemma so so so what<00:06:58.869> is<00:06:58.989> true--but<00:06:59.319> true--but<00:06:59.649> is<00:06:59.769> a<00:06:59.849> is<00:07:00.849> is 00:07:01.229 --> 00:07:01.239 align:start position:0% what is true--but true--but is a is is 00:07:01.239 --> 00:07:04.019 align:start position:0% what is true--but true--but is a is is is<00:07:01.509> a<00:07:01.989> solution<00:07:02.409> to<00:07:02.589> this<00:07:02.829> verifiers<00:07:03.669> dilemma 00:07:04.019 --> 00:07:04.029 align:start position:0% is a solution to this verifiers dilemma 00:07:04.029 --> 00:07:08.159 align:start position:0% is a solution to this verifiers dilemma it's<00:07:04.329> it<00:07:04.719> sort<00:07:05.019> of<00:07:05.139> makes<00:07:05.949> it<00:07:06.129> so<00:07:06.309> we<00:07:06.989> we<00:07:07.989> put 00:07:08.159 --> 00:07:08.169 align:start position:0% it's it sort of makes it so we we put 00:07:08.169 --> 00:07:09.179 align:start position:0% it's it sort of makes it so we we put everything<00:07:08.379> off<00:07:08.559> chain<00:07:08.829> so<00:07:08.979> you<00:07:09.009> don't 00:07:09.179 --> 00:07:09.189 align:start position:0% everything off chain so you don't 00:07:09.189 --> 00:07:10.829 align:start position:0% everything off chain so you don't actually<00:07:09.309> have<00:07:09.459> to<00:07:09.579> deal<00:07:09.849> with<00:07:10.119> with<00:07:10.629> heavy 00:07:10.829 --> 00:07:10.839 align:start position:0% actually have to deal with with heavy 00:07:10.839 --> 00:07:12.809 align:start position:0% actually have to deal with with heavy transactions<00:07:11.529> on<00:07:11.649> chain<00:07:11.919> what<00:07:12.399> we've<00:07:12.549> sort<00:07:12.789> of 00:07:12.809 --> 00:07:12.819 align:start position:0% transactions on chain what we've sort of 00:07:12.819 --> 00:07:14.219 align:start position:0% transactions on chain what we've sort of observed<00:07:13.179> in<00:07:13.329> block<00:07:13.509> chains<00:07:13.809> and<00:07:14.019> this<00:07:14.110> is 00:07:14.219 --> 00:07:14.229 align:start position:0% observed in block chains and this is 00:07:14.229 --> 00:07:15.569 align:start position:0% observed in block chains and this is kind<00:07:14.409> of<00:07:14.499> the<00:07:14.739> miracle<00:07:15.129> of<00:07:15.159> the<00:07:15.249> whole<00:07:15.429> thing 00:07:15.569 --> 00:07:15.579 align:start position:0% kind of the miracle of the whole thing 00:07:15.579 --> 00:07:18.989 align:start position:0% kind of the miracle of the whole thing is<00:07:15.639> that<00:07:16.050> miners<00:07:17.050> are<00:07:17.229> willing<00:07:17.469> to<00:07:17.589> do<00:07:17.829> a<00:07:18.249> small 00:07:18.989 --> 00:07:18.999 align:start position:0% is that miners are willing to do a small 00:07:18.999 --> 00:07:20.729 align:start position:0% is that miners are willing to do a small amount<00:07:19.149> of<00:07:19.300> work<00:07:19.419> for<00:07:19.629> free<00:07:19.839> and<00:07:20.079> then<00:07:20.709> you 00:07:20.729 --> 00:07:20.739 align:start position:0% amount of work for free and then you 00:07:20.739 --> 00:07:23.309 align:start position:0% amount of work for free and then you don't<00:07:20.979> have<00:07:21.099> a<00:07:21.159> verifiers<00:07:21.669> dilemma<00:07:22.089> so<00:07:22.329> here 00:07:23.309 --> 00:07:23.319 align:start position:0% don't have a verifiers dilemma so here 00:07:23.319 --> 00:07:25.319 align:start position:0% don't have a verifiers dilemma so here with<00:07:23.529> with<00:07:23.800> true--but<00:07:24.159> we<00:07:24.550> are<00:07:24.669> going<00:07:25.029> to<00:07:25.179> give 00:07:25.319 --> 00:07:25.329 align:start position:0% with with true--but we are going to give 00:07:25.329 --> 00:07:26.819 align:start position:0% with with true--but we are going to give it<00:07:25.360> three<00:07:25.629> I'm<00:07:25.689> a<00:07:25.779> computational<00:07:26.019> boost<00:07:26.559> by 00:07:26.819 --> 00:07:26.829 align:start position:0% it three I'm a computational boost by 00:07:26.829 --> 00:07:29.279 align:start position:0% it three I'm a computational boost by doing<00:07:27.459> the<00:07:27.579> heavy<00:07:27.879> work<00:07:28.119> off<00:07:28.389> chain<00:07:28.749> so<00:07:29.169> the 00:07:29.279 --> 00:07:29.289 align:start position:0% doing the heavy work off chain so the 00:07:29.289 --> 00:07:30.869 align:start position:0% doing the heavy work off chain so the goals<00:07:29.559> of<00:07:29.679> the<00:07:29.769> protocol<00:07:30.219> is<00:07:30.339> that<00:07:30.369> anyone<00:07:30.819> can 00:07:30.869 --> 00:07:30.879 align:start position:0% goals of the protocol is that anyone can 00:07:30.879 --> 00:07:32.609 align:start position:0% goals of the protocol is that anyone can offer<00:07:31.300> a<00:07:31.539> reward<00:07:31.899> for<00:07:32.079> performing<00:07:32.559> a 00:07:32.609 --> 00:07:32.619 align:start position:0% offer a reward for performing a 00:07:32.619 --> 00:07:36.839 align:start position:0% offer a reward for performing a computational<00:07:33.339> task<00:07:34.379> anyone<00:07:35.379> can<00:07:35.829> solve<00:07:36.699> a 00:07:36.839 --> 00:07:36.849 align:start position:0% computational task anyone can solve a 00:07:36.849 --> 00:07:39.959 align:start position:0% computational task anyone can solve a task<00:07:36.999> in<00:07:37.239> exchange<00:07:37.599> for<00:07:37.659> a<00:07:37.809> ward<00:07:38.519> the<00:07:39.519> protocol 00:07:39.959 --> 00:07:39.969 align:start position:0% task in exchange for a ward the protocol 00:07:39.969 --> 00:07:42.029 align:start position:0% task in exchange for a ward the protocol most<00:07:40.479> importantly<00:07:40.989> guarantees<00:07:41.529> correctness 00:07:42.029 --> 00:07:42.039 align:start position:0% most importantly guarantees correctness 00:07:42.039 --> 00:07:45.479 align:start position:0% most importantly guarantees correctness of<00:07:42.279> solutions<00:07:42.759> and<00:07:42.999> here<00:07:43.989> by<00:07:44.139> anyone<00:07:44.589> I<00:07:44.860> mean 00:07:45.479 --> 00:07:45.489 align:start position:0% of solutions and here by anyone I mean 00:07:45.489 --> 00:07:47.699 align:start position:0% of solutions and here by anyone I mean anyone<00:07:45.909> that<00:07:46.089> means<00:07:46.360> a<00:07:46.449> smart<00:07:46.719> contract<00:07:46.869> soon 00:07:47.699 --> 00:07:47.709 align:start position:0% anyone that means a smart contract soon 00:07:47.709 --> 00:07:51.659 align:start position:0% anyone that means a smart contract soon anonymous<00:07:48.159> identity<00:07:48.959> or<00:07:49.959> the<00:07:50.259> bots<00:07:50.439> that<00:07:50.669> came 00:07:51.659 --> 00:07:51.669 align:start position:0% anonymous identity or the bots that came 00:07:51.669 --> 00:07:54.319 align:start position:0% anonymous identity or the bots that came up<00:07:51.819> in<00:07:51.999> the<00:07:52.649> earlier<00:07:53.649> talk<00:07:53.860> this<00:07:54.009> afternoon 00:07:54.319 --> 00:07:54.329 align:start position:0% up in the earlier talk this afternoon 00:07:54.329 --> 00:07:58.379 align:start position:0% up in the earlier talk this afternoon and<00:07:56.219> so<00:07:57.219> if<00:07:57.489> you<00:07:57.610> want<00:07:57.729> to<00:07:57.789> say<00:07:57.879> formally<00:07:58.239> what 00:07:58.379 --> 00:07:58.389 align:start position:0% and so if you want to say formally what 00:07:58.389 --> 00:08:00.239 align:start position:0% and so if you want to say formally what is<00:07:58.509> true--but<00:07:58.929> it's<00:07:59.379> an<00:07:59.589> aetherium<00:07:59.949> smart 00:08:00.239 --> 00:08:00.249 align:start position:0% is true--but it's an aetherium smart 00:08:00.249 --> 00:08:01.889 align:start position:0% is true--but it's an aetherium smart contract<00:08:00.729> that's<00:08:00.969> one<00:08:01.179> part<00:08:01.419> of<00:08:01.569> it<00:08:01.659> but<00:08:01.749> it's 00:08:01.889 --> 00:08:01.899 align:start position:0% contract that's one part of it but it's 00:08:01.899 --> 00:08:05.489 align:start position:0% contract that's one part of it but it's also<00:08:02.050> a<00:08:02.409> new<00:08:02.559> off<00:08:03.519> chain<00:08:04.209> architecture<00:08:04.959> so<00:08:05.349> I'm 00:08:05.489 --> 00:08:05.499 align:start position:0% also a new off chain architecture so I'm 00:08:05.499 --> 00:08:06.719 align:start position:0% also a new off chain architecture so I'm going<00:08:05.649> to<00:08:05.709> walk<00:08:05.979> us<00:08:06.189> through<00:08:06.219> these<00:08:06.550> two 00:08:06.719 --> 00:08:06.729 align:start position:0% going to walk us through these two 00:08:06.729 --> 00:08:09.269 align:start position:0% going to walk us through these two pieces<00:08:07.089> in<00:08:07.689> the<00:08:07.899> in<00:08:08.139> the<00:08:08.259> remaining<00:08:08.619> time<00:08:08.800> so 00:08:09.269 --> 00:08:09.279 align:start position:0% pieces in the in the remaining time so 00:08:09.279 --> 00:08:10.889 align:start position:0% pieces in the in the remaining time so let<00:08:09.519> me<00:08:09.639> try<00:08:09.759> to<00:08:09.849> explain<00:08:09.939> what<00:08:10.419> how<00:08:10.719> they 00:08:10.889 --> 00:08:10.899 align:start position:0% let me try to explain what how they 00:08:10.899 --> 00:08:12.059 align:start position:0% let me try to explain what how they let's<00:08:11.169> let's<00:08:11.409> look<00:08:11.559> at<00:08:11.679> the<00:08:11.769> architecture 00:08:12.059 --> 00:08:12.069 align:start position:0% let's let's look at the architecture 00:08:12.069 --> 00:08:14.989 align:start position:0% let's let's look at the architecture piece<00:08:12.610> first<00:08:12.879> just<00:08:13.479> as<00:08:13.599> an<00:08:13.719> overview<00:08:13.809> so 00:08:14.989 --> 00:08:14.999 align:start position:0% piece first just as an overview so 00:08:14.999 --> 00:08:17.219 align:start position:0% piece first just as an overview so trubin<00:08:15.999> is<00:08:16.119> a<00:08:16.149> unanimous<00:08:16.689> consensus 00:08:17.219 --> 00:08:17.229 align:start position:0% trubin is a unanimous consensus 00:08:17.229 --> 00:08:20.100 align:start position:0% trubin is a unanimous consensus algorithm<00:08:17.529> unlike<00:08:18.519> a<00:08:19.059> theory<00:08:19.659> in<00:08:19.749> which<00:08:19.779> you 00:08:20.100 --> 00:08:20.110 align:start position:0% algorithm unlike a theory in which you 00:08:20.110 --> 00:08:22.169 align:start position:0% algorithm unlike a theory in which you sort<00:08:20.349> of<00:08:20.409> have<00:08:20.559> majority<00:08:20.979> vote<00:08:21.369> on<00:08:21.579> the<00:08:21.849> on<00:08:22.059> the 00:08:22.169 --> 00:08:22.179 align:start position:0% sort of have majority vote on the on the 00:08:22.179 --> 00:08:24.299 align:start position:0% sort of have majority vote on the on the miners<00:08:22.449> people<00:08:22.749> to<00:08:22.869> say<00:08:23.110> like<00:08:23.259> this<00:08:23.409> anyone<00:08:24.249> a 00:08:24.299 --> 00:08:24.309 align:start position:0% miners people to say like this anyone a 00:08:24.309 --> 00:08:26.069 align:start position:0% miners people to say like this anyone a true<00:08:24.579> bit<00:08:24.729> can<00:08:24.879> challenge<00:08:25.239> a<00:08:25.300> computation<00:08:25.929> by 00:08:26.069 --> 00:08:26.079 align:start position:0% true bit can challenge a computation by 00:08:26.079 --> 00:08:29.369 align:start position:0% true bit can challenge a computation by taking<00:08:26.469> it<00:08:26.589> to<00:08:26.619> to<00:08:27.159> court<00:08:27.689> so<00:08:28.689> to<00:08:28.719> speak<00:08:29.019> and 00:08:29.369 --> 00:08:29.379 align:start position:0% taking it to to court so to speak and 00:08:29.379 --> 00:08:31.290 align:start position:0% taking it to to court so to speak and they<00:08:30.009> who<00:08:30.219> sits<00:08:30.489> in<00:08:30.579> the<00:08:30.699> court<00:08:30.939> while<00:08:31.149> it's 00:08:31.290 --> 00:08:31.300 align:start position:0% they who sits in the court while it's 00:08:31.300 --> 00:08:34.079 align:start position:0% they who sits in the court while it's your<00:08:31.539> your<00:08:31.809> your<00:08:32.139> miners<00:08:32.469> from<00:08:32.860> the<00:08:32.969> from<00:08:33.969> the 00:08:34.079 --> 00:08:34.089 align:start position:0% your your your miners from the from the 00:08:34.089 --> 00:08:35.639 align:start position:0% your your your miners from the from the etherium<00:08:34.449> network<00:08:34.719> are<00:08:34.899> sitting<00:08:35.199> sitting<00:08:35.559> in 00:08:35.639 --> 00:08:35.649 align:start position:0% etherium network are sitting sitting in 00:08:35.649 --> 00:08:37.799 align:start position:0% etherium network are sitting sitting in this<00:08:35.769> court<00:08:36.039> they're<00:08:36.729> always<00:08:36.969> right<00:08:37.360> but<00:08:37.689> they 00:08:37.799 --> 00:08:37.809 align:start position:0% this court they're always right but they 00:08:37.809 --> 00:08:39.929 align:start position:0% this court they're always right but they have<00:08:37.930> very<00:08:38.289> limited<00:08:38.559> banned<00:08:39.009> computational 00:08:39.929 --> 00:08:39.939 align:start position:0% have very limited banned computational 00:08:39.939 --> 00:08:42.089 align:start position:0% have very limited banned computational bandwidth<00:08:40.300> as<00:08:40.479> we<00:08:40.689> just<00:08:40.930> see<00:08:41.110> because<00:08:41.949> of<00:08:42.039> the 00:08:42.089 --> 00:08:42.099 align:start position:0% bandwidth as we just see because of the 00:08:42.099 --> 00:08:43.709 align:start position:0% bandwidth as we just see because of the gas<00:08:42.279> limit<00:08:42.550> because<00:08:43.149> of<00:08:43.269> the<00:08:43.360> verifiers 00:08:43.709 --> 00:08:43.719 align:start position:0% gas limit because of the verifiers 00:08:43.719 --> 00:08:45.869 align:start position:0% gas limit because of the verifiers dilemma<00:08:44.110> you're<00:08:44.529> stuck<00:08:44.800> with<00:08:44.920> that<00:08:44.980> so<00:08:45.670> what 00:08:45.869 --> 00:08:45.879 align:start position:0% dilemma you're stuck with that so what 00:08:45.879 --> 00:08:48.629 align:start position:0% dilemma you're stuck with that so what what<00:08:46.240> can<00:08:46.389> we<00:08:46.509> do<00:08:46.660> so<00:08:47.079> you<00:08:47.709> have<00:08:47.829> a<00:08:47.860> solver<00:08:48.370> you 00:08:48.629 --> 00:08:48.639 align:start position:0% what can we do so you have a solver you 00:08:48.639 --> 00:08:51.179 align:start position:0% what can we do so you have a solver you have<00:08:49.329> a<00:08:49.389> solver<00:08:49.689> who<00:08:49.870> comes<00:08:50.139> in<00:08:50.350> with<00:08:50.500> a<00:08:50.529> data 00:08:51.179 --> 00:08:51.189 align:start position:0% have a solver who comes in with a data 00:08:51.189 --> 00:08:52.570 align:start position:0% have a solver who comes in with a data computation 00:08:52.570 --> 00:08:52.580 align:start position:0% computation 00:08:52.580 --> 00:08:54.910 align:start position:0% computation a<00:08:52.640> challenger<00:08:53.510> who<00:08:53.630> comes<00:08:53.840> in<00:08:53.990> and<00:08:54.140> says<00:08:54.290> well 00:08:54.910 --> 00:08:54.920 align:start position:0% a challenger who comes in and says well 00:08:54.920 --> 00:08:57.430 align:start position:0% a challenger who comes in and says well you're<00:08:55.190> wrong<00:08:55.400> and<00:08:56.030> the<00:08:56.420> solver<00:08:56.780> doesn't 00:08:57.430 --> 00:08:57.440 align:start position:0% you're wrong and the solver doesn't 00:08:57.440 --> 00:08:58.630 align:start position:0% you're wrong and the solver doesn't actually<00:08:57.560> say<00:08:57.860> let's<00:08:58.070> play<00:08:58.250> a<00:08:58.280> verification 00:08:58.630 --> 00:08:58.640 align:start position:0% actually say let's play a verification 00:08:58.640 --> 00:09:00.190 align:start position:0% actually say let's play a verification game<00:08:59.180> he<00:08:59.330> gets<00:08:59.420> forced<00:08:59.870> to<00:08:59.990> play<00:09:00.170> a 00:09:00.190 --> 00:09:00.200 align:start position:0% game he gets forced to play a 00:09:00.200 --> 00:09:02.430 align:start position:0% game he gets forced to play a verification<00:09:00.560> game<00:09:01.040> he<00:09:01.370> gets<00:09:01.460> taken<00:09:01.760> to<00:09:01.970> court 00:09:02.430 --> 00:09:02.440 align:start position:0% verification game he gets taken to court 00:09:02.440 --> 00:09:05.560 align:start position:0% verification game he gets taken to court okay<00:09:03.440> so<00:09:04.130> what<00:09:04.310> does<00:09:04.370> the<00:09:04.520> court<00:09:04.760> do<00:09:04.970> it<00:09:05.300> tries 00:09:05.560 --> 00:09:05.570 align:start position:0% okay so what does the court do it tries 00:09:05.570 --> 00:09:06.850 align:start position:0% okay so what does the court do it tries to<00:09:05.600> pinpoint<00:09:05.960> the<00:09:06.320> place<00:09:06.530> where<00:09:06.740> they're 00:09:06.850 --> 00:09:06.860 align:start position:0% to pinpoint the place where they're 00:09:06.860 --> 00:09:09.580 align:start position:0% to pinpoint the place where they're disagreeing<00:09:07.340> so<00:09:08.150> you<00:09:08.210> have<00:09:08.330> a<00:09:08.390> solver<00:09:08.810> and<00:09:09.080> the 00:09:09.580 --> 00:09:09.590 align:start position:0% disagreeing so you have a solver and the 00:09:09.590 --> 00:09:10.150 align:start position:0% disagreeing so you have a solver and the Challenger 00:09:10.150 --> 00:09:10.160 align:start position:0% Challenger 00:09:10.160 --> 00:09:11.920 align:start position:0% Challenger they<00:09:10.400> enumerate<00:09:10.940> the<00:09:11.090> computation<00:09:11.660> states 00:09:11.920 --> 00:09:11.930 align:start position:0% they enumerate the computation states 00:09:11.930 --> 00:09:13.810 align:start position:0% they enumerate the computation states they<00:09:12.110> do<00:09:12.170> the<00:09:12.350> all<00:09:12.470> this<00:09:12.620> off<00:09:12.830> chain<00:09:13.280> and<00:09:13.490> then 00:09:13.810 --> 00:09:13.820 align:start position:0% they do the all this off chain and then 00:09:13.820 --> 00:09:15.460 align:start position:0% they do the all this off chain and then the<00:09:13.850> judges<00:09:14.180> are<00:09:14.450> going<00:09:14.570> to<00:09:14.630> enforce<00:09:14.930> a<00:09:15.080> binary 00:09:15.460 --> 00:09:15.470 align:start position:0% the judges are going to enforce a binary 00:09:15.470 --> 00:09:17.830 align:start position:0% the judges are going to enforce a binary search<00:09:15.680> to<00:09:16.130> find<00:09:16.310> the<00:09:16.490> first<00:09:16.730> step<00:09:17.600> in<00:09:17.780> the 00:09:17.830 --> 00:09:17.840 align:start position:0% search to find the first step in the 00:09:17.840 --> 00:09:22.420 align:start position:0% search to find the first step in the computation<00:09:18.500> where<00:09:19.430> they<00:09:19.580> disagree<00:09:20.710> so<00:09:21.710> solve 00:09:22.420 --> 00:09:22.430 align:start position:0% computation where they disagree so solve 00:09:22.430 --> 00:09:27.160 align:start position:0% computation where they disagree so solve assess<00:09:23.440> here<00:09:24.440> he<00:09:25.160> kicks<00:09:25.760> out<00:09:25.910> his<00:09:26.170> obviously 00:09:27.160 --> 00:09:27.170 align:start position:0% assess here he kicks out his obviously 00:09:27.170 --> 00:09:29.560 align:start position:0% assess here he kicks out his obviously they<00:09:27.320> agreed<00:09:27.560> on<00:09:27.650> the<00:09:27.770> the<00:09:28.250> green<00:09:29.150> means<00:09:29.420> they 00:09:29.560 --> 00:09:29.570 align:start position:0% they agreed on the the green means they 00:09:29.570 --> 00:09:31.210 align:start position:0% they agreed on the the green means they agreed<00:09:29.810> so<00:09:29.990> they<00:09:30.410> agreed<00:09:30.650> on<00:09:30.680> the<00:09:30.860> first<00:09:31.040> step 00:09:31.210 --> 00:09:31.220 align:start position:0% agreed so they agreed on the first step 00:09:31.220 --> 00:09:32.470 align:start position:0% agreed so they agreed on the first step because<00:09:31.370> it's<00:09:31.460> the<00:09:31.520> input<00:09:31.850> it's<00:09:32.000> it's<00:09:32.240> just 00:09:32.470 --> 00:09:32.480 align:start position:0% because it's the input it's it's just 00:09:32.480 --> 00:09:34.150 align:start position:0% because it's the input it's it's just given<00:09:32.810> and<00:09:32.960> they<00:09:33.350> didn't<00:09:33.590> agree<00:09:33.740> on<00:09:33.920> the<00:09:34.010> end 00:09:34.150 --> 00:09:34.160 align:start position:0% given and they didn't agree on the end 00:09:34.160 --> 00:09:35.380 align:start position:0% given and they didn't agree on the end or<00:09:34.460> they<00:09:34.550> wouldn't<00:09:34.790> have<00:09:34.850> been<00:09:35.000> in<00:09:35.120> the<00:09:35.180> court 00:09:35.380 --> 00:09:35.390 align:start position:0% or they wouldn't have been in the court 00:09:35.390 --> 00:09:36.790 align:start position:0% or they wouldn't have been in the court in<00:09:35.450> the<00:09:35.510> first<00:09:35.750> place<00:09:35.960> so<00:09:36.080> he<00:09:36.170> says<00:09:36.350> do<00:09:36.740> you 00:09:36.790 --> 00:09:36.800 align:start position:0% in the first place so he says do you 00:09:36.800 --> 00:09:39.220 align:start position:0% in the first place so he says do you agree<00:09:36.980> halfway<00:09:37.400> through<00:09:37.870> challenger<00:09:38.870> says<00:09:39.050> no 00:09:39.220 --> 00:09:39.230 align:start position:0% agree halfway through challenger says no 00:09:39.230 --> 00:09:40.660 align:start position:0% agree halfway through challenger says no I<00:09:39.260> don't<00:09:39.500> agree<00:09:39.590> on<00:09:39.770> that<00:09:40.010> so<00:09:40.220> we<00:09:40.310> marked<00:09:40.580> that 00:09:40.660 --> 00:09:40.670 align:start position:0% I don't agree on that so we marked that 00:09:40.670 --> 00:09:42.880 align:start position:0% I don't agree on that so we marked that as<00:09:40.880> as<00:09:41.120> red<00:09:41.450> do<00:09:41.900> you<00:09:41.990> agree<00:09:42.080> it's<00:09:42.320> step<00:09:42.530> at<00:09:42.680> over 00:09:42.880 --> 00:09:42.890 align:start position:0% as as red do you agree it's step at over 00:09:42.890 --> 00:09:46.840 align:start position:0% as as red do you agree it's step at over for<00:09:43.420> says<00:09:44.420> yeah<00:09:44.930> okay<00:09:45.560> great<00:09:46.040> step<00:09:46.340> no<00:09:46.640> for 00:09:46.840 --> 00:09:46.850 align:start position:0% for says yeah okay great step no for 00:09:46.850 --> 00:09:49.210 align:start position:0% for says yeah okay great step no for what<00:09:47.000> about<00:09:47.180> 3n<00:09:47.900> over<00:09:48.020> 8<00:09:48.320> so<00:09:48.860> we're<00:09:49.040> just 00:09:49.210 --> 00:09:49.220 align:start position:0% what about 3n over 8 so we're just 00:09:49.220 --> 00:09:51.670 align:start position:0% what about 3n over 8 so we're just getting<00:09:49.910> now<00:09:50.240> now<00:09:50.510> we're<00:09:50.990> there<00:09:51.350> these<00:09:51.620> are 00:09:51.670 --> 00:09:51.680 align:start position:0% getting now now we're there these are 00:09:51.680 --> 00:09:53.260 align:start position:0% getting now now we're there these are close<00:09:51.980> enough<00:09:52.010> you<00:09:52.340> can<00:09:52.370> actually<00:09:52.790> run<00:09:53.000> this 00:09:53.260 --> 00:09:53.270 align:start position:0% close enough you can actually run this 00:09:53.270 --> 00:09:55.240 align:start position:0% close enough you can actually run this one<00:09:53.510> step<00:09:53.840> of<00:09:53.990> the<00:09:54.050> computation<00:09:54.680> you<00:09:55.010> could<00:09:55.160> do 00:09:55.240 --> 00:09:55.250 align:start position:0% one step of the computation you could do 00:09:55.250 --> 00:09:58.060 align:start position:0% one step of the computation you could do it<00:09:55.340> on<00:09:55.400> chain<00:09:55.730> because<00:09:56.330> it's<00:09:56.480> small<00:09:56.750> and<00:09:57.070> it's 00:09:58.060 --> 00:09:58.070 align:start position:0% it on chain because it's small and it's 00:09:58.070 --> 00:09:59.020 align:start position:0% it on chain because it's small and it's important<00:09:58.400> to<00:09:58.430> note<00:09:58.610> here<00:09:58.790> that<00:09:58.850> the 00:09:59.020 --> 00:09:59.030 align:start position:0% important to note here that the 00:09:59.030 --> 00:10:00.520 align:start position:0% important to note here that the computational<00:09:59.600> steps<00:09:59.810> have<00:10:00.290> to<00:10:00.320> be 00:10:00.520 --> 00:10:00.530 align:start position:0% computational steps have to be 00:10:00.530 --> 00:10:02.950 align:start position:0% computational steps have to be absolutely<00:10:01.190> identical<00:10:01.250> across<00:10:02.210> all<00:10:02.330> the 00:10:02.950 --> 00:10:02.960 align:start position:0% absolutely identical across all the 00:10:02.960 --> 00:10:04.930 align:start position:0% absolutely identical across all the platforms<00:10:03.080> in<00:10:03.620> order<00:10:03.830> to<00:10:04.010> rule<00:10:04.220> fairly<00:10:04.790> on<00:10:04.880> the 00:10:04.930 --> 00:10:04.940 align:start position:0% platforms in order to rule fairly on the 00:10:04.940 --> 00:10:06.970 align:start position:0% platforms in order to rule fairly on the final<00:10:05.210> check<00:10:05.420> right<00:10:06.140> there's<00:10:06.320> no<00:10:06.470> notion<00:10:06.680> of 00:10:06.970 --> 00:10:06.980 align:start position:0% final check right there's no notion of 00:10:06.980 --> 00:10:08.830 align:start position:0% final check right there's no notion of one<00:10:07.520> step<00:10:07.790> if<00:10:08.000> everybody's<00:10:08.420> running<00:10:08.720> a 00:10:08.830 --> 00:10:08.840 align:start position:0% one step if everybody's running a 00:10:08.840 --> 00:10:10.690 align:start position:0% one step if everybody's running a different<00:10:09.110> set<00:10:09.410> of<00:10:09.440> steps<00:10:09.770> so<00:10:09.890> the<00:10:10.040> judges<00:10:10.280> we 00:10:10.690 --> 00:10:10.700 align:start position:0% different set of steps so the judges we 00:10:10.700 --> 00:10:12.730 align:start position:0% different set of steps so the judges we have<00:10:11.120> to<00:10:11.270> make<00:10:11.390> sure<00:10:11.420> that<00:10:11.570> that's<00:10:12.290> the<00:10:12.560> key 00:10:12.730 --> 00:10:12.740 align:start position:0% have to make sure that that's the key 00:10:12.740 --> 00:10:14.470 align:start position:0% have to make sure that that's the key property<00:10:13.220> of<00:10:13.310> our<00:10:13.400> architectures<00:10:14.060> that<00:10:14.270> all 00:10:14.470 --> 00:10:14.480 align:start position:0% property of our architectures that all 00:10:14.480 --> 00:10:17.290 align:start position:0% property of our architectures that all the<00:10:14.660> steps<00:10:14.840> are<00:10:15.080> exactly<00:10:15.170> the<00:10:15.620> same<00:10:16.150> okay<00:10:17.150> so 00:10:17.290 --> 00:10:17.300 align:start position:0% the steps are exactly the same okay so 00:10:17.300 --> 00:10:19.090 align:start position:0% the steps are exactly the same okay so what<00:10:17.540> happens<00:10:17.870> here<00:10:17.960> so<00:10:18.260> here<00:10:18.440> is<00:10:18.560> this<00:10:18.770> the 00:10:19.090 --> 00:10:19.100 align:start position:0% what happens here so here is this the 00:10:19.100 --> 00:10:21.190 align:start position:0% what happens here so here is this the last<00:10:19.250> step<00:10:19.550> where<00:10:19.730> they<00:10:19.820> they<00:10:20.270> agreed<00:10:20.990> and 00:10:21.190 --> 00:10:21.200 align:start position:0% last step where they they agreed and 00:10:21.200 --> 00:10:23.440 align:start position:0% last step where they they agreed and here's<00:10:21.680> the<00:10:21.860> step<00:10:22.100> or<00:10:22.490> they<00:10:22.580> disagreed<00:10:23.030> this 00:10:23.440 --> 00:10:23.450 align:start position:0% here's the step or they disagreed this 00:10:23.450 --> 00:10:25.870 align:start position:0% here's the step or they disagreed this is<00:10:23.600> what<00:10:23.780> the<00:10:23.950> this<00:10:24.950> is<00:10:25.100> this<00:10:25.310> step<00:10:25.580> was<00:10:25.760> of 00:10:25.870 --> 00:10:25.880 align:start position:0% is what the this is this step was of 00:10:25.880 --> 00:10:28.540 align:start position:0% is what the this is this step was of course<00:10:26.000> provided<00:10:26.480> by<00:10:26.600> the<00:10:26.660> solver<00:10:27.370> so<00:10:28.370> he's 00:10:28.540 --> 00:10:28.550 align:start position:0% course provided by the solver so he's 00:10:28.550 --> 00:10:30.010 align:start position:0% course provided by the solver so he's saying<00:10:28.790> so<00:10:29.030> I'm<00:10:29.090> talking<00:10:29.540> about<00:10:29.570> this<00:10:29.810> we 00:10:30.010 --> 00:10:30.020 align:start position:0% saying so I'm talking about this we 00:10:30.020 --> 00:10:31.360 align:start position:0% saying so I'm talking about this we there's<00:10:30.410> a<00:10:30.500> picture<00:10:30.680> of<00:10:30.800> a<00:10:30.920> Merkel<00:10:31.220> tree 00:10:31.360 --> 00:10:31.370 align:start position:0% there's a picture of a Merkel tree 00:10:31.370 --> 00:10:33.010 align:start position:0% there's a picture of a Merkel tree because<00:10:31.580> you<00:10:31.670> can<00:10:31.820> sort<00:10:32.030> of<00:10:32.150> to<00:10:32.600> optimize 00:10:33.010 --> 00:10:33.020 align:start position:0% because you can sort of to optimize 00:10:33.020 --> 00:10:35.560 align:start position:0% because you can sort of to optimize space<00:10:33.320> on<00:10:33.530> the<00:10:33.620> on<00:10:33.770> the<00:10:33.860> on<00:10:34.100> the<00:10:34.220> on<00:10:34.460> the<00:10:34.610> block 00:10:35.560 --> 00:10:35.570 align:start position:0% space on the on the on the on the block 00:10:35.570 --> 00:10:37.840 align:start position:0% space on the on the on the on the block chain<00:10:35.810> we<00:10:35.990> represent<00:10:36.710> these<00:10:36.920> states<00:10:37.700> and 00:10:37.840 --> 00:10:37.850 align:start position:0% chain we represent these states and 00:10:37.850 --> 00:10:39.070 align:start position:0% chain we represent these states and former<00:10:38.090> Merkel<00:10:38.390> tree<00:10:38.540> but<00:10:38.690> you<00:10:38.780> can<00:10:38.900> think<00:10:39.020> of 00:10:39.070 --> 00:10:39.080 align:start position:0% former Merkel tree but you can think of 00:10:39.080 --> 00:10:42.250 align:start position:0% former Merkel tree but you can think of it<00:10:39.170> as<00:10:39.230> a<00:10:39.530> Turing<00:10:39.860> machine<00:10:40.600> so<00:10:41.600> you<00:10:41.630> said<00:10:42.020> your 00:10:42.250 --> 00:10:42.260 align:start position:0% it as a Turing machine so you said your 00:10:42.260 --> 00:10:44.500 align:start position:0% it as a Turing machine so you said your give<00:10:42.440> a<00:10:42.470> machine<00:10:42.800> it's<00:10:43.220> in<00:10:43.400> state<00:10:43.550> q0<00:10:43.850> it<00:10:44.300> sees 00:10:44.500 --> 00:10:44.510 align:start position:0% give a machine it's in state q0 it sees 00:10:44.510 --> 00:10:48.250 align:start position:0% give a machine it's in state q0 it sees a<00:10:44.540> one<00:10:45.310> so<00:10:46.310> then<00:10:46.520> the<00:10:47.390> program<00:10:47.750> he's<00:10:47.990> claiming 00:10:48.250 --> 00:10:48.260 align:start position:0% a one so then the program he's claiming 00:10:48.260 --> 00:10:50.200 align:start position:0% a one so then the program he's claiming if<00:10:48.440> the<00:10:48.530> program<00:10:48.860> says<00:10:49.130> write<00:10:49.430> a<00:10:49.460> zero<00:10:49.790> change 00:10:50.200 --> 00:10:50.210 align:start position:0% if the program says write a zero change 00:10:50.210 --> 00:10:52.600 align:start position:0% if the program says write a zero change to<00:10:50.360> state<00:10:50.420> q1<00:10:50.810> and<00:10:51.110> move<00:10:51.200> to<00:10:51.350> the<00:10:51.440> left<00:10:51.590> if<00:10:52.010> you 00:10:52.600 --> 00:10:52.610 align:start position:0% to state q1 and move to the left if you 00:10:52.610 --> 00:10:53.440 align:start position:0% to state q1 and move to the left if you don't<00:10:52.760> know<00:10:52.820> what<00:10:52.910> a<00:10:52.970> Turing<00:10:53.180> machine<00:10:53.210> is 00:10:53.440 --> 00:10:53.450 align:start position:0% don't know what a Turing machine is 00:10:53.450 --> 00:10:55.600 align:start position:0% don't know what a Turing machine is that's<00:10:53.750> fine<00:10:54.020> just<00:10:54.470> note<00:10:54.710> that<00:10:54.740> whatever<00:10:55.340> the 00:10:55.600 --> 00:10:55.610 align:start position:0% that's fine just note that whatever the 00:10:55.610 --> 00:10:57.040 align:start position:0% that's fine just note that whatever the judge<00:10:55.850> said<00:10:56.120> he<00:10:56.150> noticed<00:10:56.600> that<00:10:56.690> it<00:10:56.780> did 00:10:57.040 --> 00:10:57.050 align:start position:0% judge said he noticed that it did 00:10:57.050 --> 00:10:58.750 align:start position:0% judge said he noticed that it did something<00:10:57.410> different<00:10:57.860> than<00:10:57.980> what<00:10:58.100> the<00:10:58.310> what 00:10:58.750 --> 00:10:58.760 align:start position:0% something different than what the what 00:10:58.760 --> 00:11:00.880 align:start position:0% something different than what the what the<00:10:58.940> solver<00:10:59.750> claimed<00:11:00.050> it<00:11:00.200> would<00:11:00.320> so<00:11:00.710> it's 00:11:00.880 --> 00:11:00.890 align:start position:0% the solver claimed it would so it's 00:11:00.890 --> 00:11:02.230 align:start position:0% the solver claimed it would so it's there<00:11:01.220> there<00:11:01.520> there 00:11:02.230 --> 00:11:02.240 align:start position:0% there there there 00:11:02.240 --> 00:11:04.419 align:start position:0% there there there the<00:11:02.869> solver<00:11:03.170> is<00:11:03.259> wrong<00:11:03.499> so<00:11:03.920> the<00:11:04.040> challenge<00:11:04.339> is 00:11:04.419 --> 00:11:04.429 align:start position:0% the solver is wrong so the challenge is 00:11:04.429 --> 00:11:06.549 align:start position:0% the solver is wrong so the challenge is justified<00:11:04.939> and<00:11:05.209> that<00:11:05.240> forfeit<00:11:05.809> is<00:11:05.929> now<00:11:06.079> the 00:11:06.549 --> 00:11:06.559 align:start position:0% justified and that forfeit is now the 00:11:06.559 --> 00:11:10.869 align:start position:0% justified and that forfeit is now the positive<00:11:06.790> and<00:11:07.790> it<00:11:08.920> forfeited<00:11:09.920> the<00:11:10.309> deposit<00:11:10.790> is 00:11:10.869 --> 00:11:10.879 align:start position:0% positive and it forfeited the deposit is 00:11:10.879 --> 00:11:13.749 align:start position:0% positive and it forfeited the deposit is forfeited<00:11:11.269> so<00:11:11.889> so<00:11:12.889> now<00:11:13.040> let's<00:11:13.309> look<00:11:13.490> at<00:11:13.610> the 00:11:13.749 --> 00:11:13.759 align:start position:0% forfeited so so now let's look at the 00:11:13.759 --> 00:11:15.309 align:start position:0% forfeited so so now let's look at the other<00:11:13.879> piece<00:11:14.179> the<00:11:14.420> smart<00:11:14.689> contract<00:11:14.869> piece 00:11:15.309 --> 00:11:15.319 align:start position:0% other piece the smart contract piece 00:11:15.319 --> 00:11:20.669 align:start position:0% other piece the smart contract piece which<00:11:15.529> is<00:11:16.600> sort<00:11:17.600> of<00:11:17.689> the<00:11:18.519> crept<00:11:19.519> economic 00:11:20.669 --> 00:11:20.679 align:start position:0% which is sort of the crept economic 00:11:20.679 --> 00:11:24.790 align:start position:0% which is sort of the crept economic innovation<00:11:21.679> part<00:11:22.249> of<00:11:22.339> this<00:11:22.459> project<00:11:22.730> so<00:11:23.800> how 00:11:24.790 --> 00:11:24.800 align:start position:0% innovation part of this project so how 00:11:24.800 --> 00:11:26.499 align:start position:0% innovation part of this project so how do<00:11:24.860> you<00:11:25.009> actually<00:11:25.610> ensure<00:11:26.209> that<00:11:26.240> this 00:11:26.499 --> 00:11:26.509 align:start position:0% do you actually ensure that this 00:11:26.509 --> 00:11:28.509 align:start position:0% do you actually ensure that this verification<00:11:26.839> actually<00:11:27.740> occurs<00:11:28.040> right<00:11:28.339> what 00:11:28.509 --> 00:11:28.519 align:start position:0% verification actually occurs right what 00:11:28.519 --> 00:11:30.910 align:start position:0% verification actually occurs right what if<00:11:28.639> nobody<00:11:29.029> shows<00:11:29.089> up<00:11:29.329> to<00:11:29.660> to<00:11:30.199> take<00:11:30.679> you<00:11:30.800> to 00:11:30.910 --> 00:11:30.920 align:start position:0% if nobody shows up to to take you to 00:11:30.920 --> 00:11:34.780 align:start position:0% if nobody shows up to to take you to court<00:11:31.129> then<00:11:31.339> it's<00:11:31.550> there's<00:11:31.999> no<00:11:33.309> it<00:11:34.309> doesn't 00:11:34.780 --> 00:11:34.790 align:start position:0% court then it's there's no it doesn't 00:11:34.790 --> 00:11:36.460 align:start position:0% court then it's there's no it doesn't really<00:11:34.850> work<00:11:35.119> so<00:11:35.360> so<00:11:35.899> how<00:11:36.110> do<00:11:36.170> you<00:11:36.290> make<00:11:36.439> sure 00:11:36.460 --> 00:11:36.470 align:start position:0% really work so so how do you make sure 00:11:36.470 --> 00:11:38.799 align:start position:0% really work so so how do you make sure that<00:11:36.589> people<00:11:36.889> actually<00:11:37.240> use<00:11:38.240> the<00:11:38.449> court<00:11:38.689> the 00:11:38.799 --> 00:11:38.809 align:start position:0% that people actually use the court the 00:11:38.809 --> 00:11:40.419 align:start position:0% that people actually use the court the way<00:11:38.899> it's<00:11:39.019> supposed<00:11:39.319> to<00:11:39.379> be<00:11:39.529> used<00:11:39.740> so<00:11:40.129> the 00:11:40.419 --> 00:11:40.429 align:start position:0% way it's supposed to be used so the 00:11:40.429 --> 00:11:42.519 align:start position:0% way it's supposed to be used so the second<00:11:40.970> idea<00:11:41.029> you<00:11:41.629> offer<00:11:41.809> awards<00:11:42.319> for 00:11:42.519 --> 00:11:42.529 align:start position:0% second idea you offer awards for 00:11:42.529 --> 00:11:44.439 align:start position:0% second idea you offer awards for checking<00:11:42.860> computations<00:11:43.550> just<00:11:43.850> pay<00:11:43.999> everybody 00:11:44.439 --> 00:11:44.449 align:start position:0% checking computations just pay everybody 00:11:44.449 --> 00:11:48.249 align:start position:0% checking computations just pay everybody for<00:11:45.079> who<00:11:45.259> checks<00:11:46.149> so<00:11:47.149> now<00:11:47.869> how<00:11:48.050> do<00:11:48.110> you<00:11:48.170> know 00:11:48.249 --> 00:11:48.259 align:start position:0% for who checks so now how do you know 00:11:48.259 --> 00:11:50.259 align:start position:0% for who checks so now how do you know what<00:11:48.379> they<00:11:48.470> checked<00:11:48.769> well<00:11:49.069> you<00:11:49.639> go<00:11:49.970> back<00:11:50.119> and 00:11:50.259 --> 00:11:50.269 align:start position:0% what they checked well you go back and 00:11:50.269 --> 00:11:51.819 align:start position:0% what they checked well you go back and run<00:11:50.360> the<00:11:50.449> computation<00:11:50.720> yourself<00:11:51.499> you<00:11:51.619> I<00:11:51.649> mean 00:11:51.819 --> 00:11:51.829 align:start position:0% run the computation yourself you I mean 00:11:51.829 --> 00:11:52.900 align:start position:0% run the computation yourself you I mean you<00:11:51.920> check<00:11:52.100> that<00:11:52.129> they<00:11:52.369> checked<00:11:52.639> well<00:11:52.819> you 00:11:52.900 --> 00:11:52.910 align:start position:0% you check that they checked well you 00:11:52.910 --> 00:11:54.129 align:start position:0% you check that they checked well you might<00:11:53.059> as<00:11:53.149> well<00:11:53.240> have<00:11:53.360> just<00:11:53.389> done<00:11:53.869> the<00:11:53.990> thing 00:11:54.129 --> 00:11:54.139 align:start position:0% might as well have just done the thing 00:11:54.139 --> 00:11:56.280 align:start position:0% might as well have just done the thing yourself<00:11:54.499> in<00:11:54.619> the<00:11:54.679> first<00:11:54.800> place<00:11:55.100> so<00:11:55.639> this<00:11:55.999> this 00:11:56.280 --> 00:11:56.290 align:start position:0% yourself in the first place so this this 00:11:56.290 --> 00:11:58.389 align:start position:0% yourself in the first place so this this incentivizes<00:11:57.290> participation<00:11:58.040> if<00:11:58.160> you<00:11:58.249> pay 00:11:58.389 --> 00:11:58.399 align:start position:0% incentivizes participation if you pay 00:11:58.399 --> 00:12:00.869 align:start position:0% incentivizes participation if you pay people<00:11:58.579> but<00:11:58.999> it<00:11:59.119> doesn't<00:11:59.149> incentivize 00:12:00.869 --> 00:12:00.879 align:start position:0% people but it doesn't incentivize 00:12:00.879 --> 00:12:04.569 align:start position:0% people but it doesn't incentivize correctness<00:12:01.990> so<00:12:02.990> I<00:12:03.019> I<00:12:03.319> didn't<00:12:03.889> three<00:12:04.249> would<00:12:04.550> be 00:12:04.569 --> 00:12:04.579 align:start position:0% correctness so I I didn't three would be 00:12:04.579 --> 00:12:06.129 align:start position:0% correctness so I I didn't three would be that<00:12:04.819> you<00:12:04.910> offer<00:12:05.059> rewards<00:12:05.269> for<00:12:05.660> finding<00:12:05.929> bugs 00:12:06.129 --> 00:12:06.139 align:start position:0% that you offer rewards for finding bugs 00:12:06.139 --> 00:12:08.319 align:start position:0% that you offer rewards for finding bugs so<00:12:07.040> this<00:12:07.189> gives<00:12:07.429> you<00:12:07.549> correctness<00:12:07.939> but<00:12:08.240> it 00:12:08.319 --> 00:12:08.329 align:start position:0% so this gives you correctness but it 00:12:08.329 --> 00:12:11.769 align:start position:0% so this gives you correctness but it doesn't<00:12:08.569> incentivize<00:12:08.889> participation<00:12:10.779> when 00:12:11.769 --> 00:12:11.779 align:start position:0% doesn't incentivize participation when 00:12:11.779 --> 00:12:13.869 align:start position:0% doesn't incentivize participation when there<00:12:11.929> are<00:12:11.990> no<00:12:12.049> bugs<00:12:12.259> so<00:12:13.069> it's<00:12:13.369> the<00:12:13.519> opposite 00:12:13.869 --> 00:12:13.879 align:start position:0% there are no bugs so it's the opposite 00:12:13.879 --> 00:12:17.410 align:start position:0% there are no bugs so it's the opposite problem<00:12:14.559> so<00:12:15.910> essentially<00:12:16.910> we<00:12:17.209> have<00:12:17.240> the 00:12:17.410 --> 00:12:17.420 align:start position:0% problem so essentially we have the 00:12:17.420 --> 00:12:18.850 align:start position:0% problem so essentially we have the problem<00:12:17.689> that<00:12:17.779> these<00:12:18.199> verifiers 00:12:18.850 --> 00:12:18.860 align:start position:0% problem that these verifiers 00:12:18.860 --> 00:12:20.530 align:start position:0% problem that these verifiers stop<00:12:19.399> paying<00:12:19.610> attention<00:12:20.149> if<00:12:20.240> they<00:12:20.269> don't 00:12:20.530 --> 00:12:20.540 align:start position:0% stop paying attention if they don't 00:12:20.540 --> 00:12:25.449 align:start position:0% stop paying attention if they don't expect<00:12:20.809> to<00:12:20.959> receive<00:12:21.079> any<00:12:21.350> rewards<00:12:23.980> okay<00:12:24.980> this 00:12:25.449 --> 00:12:25.459 align:start position:0% expect to receive any rewards okay this 00:12:25.459 --> 00:12:28.539 align:start position:0% expect to receive any rewards okay this brings<00:12:25.639> us<00:12:25.910> to<00:12:26.179> our<00:12:26.439> final<00:12:27.439> scalability<00:12:28.249> idea 00:12:28.539 --> 00:12:28.549 align:start position:0% brings us to our final scalability idea 00:12:28.549 --> 00:12:30.489 align:start position:0% brings us to our final scalability idea for<00:12:28.730> this<00:12:28.790> talk<00:12:28.850> which<00:12:29.329> we<00:12:29.869> call<00:12:30.110> forced 00:12:30.489 --> 00:12:30.499 align:start position:0% for this talk which we call forced 00:12:30.499 --> 00:12:32.980 align:start position:0% for this talk which we call forced errors<00:12:30.829> and<00:12:31.639> that<00:12:32.360> is<00:12:32.540> that<00:12:32.720> we're<00:12:32.839> going<00:12:32.929> to 00:12:32.980 --> 00:12:32.990 align:start position:0% errors and that is that we're going to 00:12:32.990 --> 00:12:35.230 align:start position:0% errors and that is that we're going to offer<00:12:33.049> a<00:12:33.319> bug<00:12:34.040> bounty<00:12:34.220> and<00:12:34.610> provide 00:12:35.230 --> 00:12:35.240 align:start position:0% offer a bug bounty and provide 00:12:35.240 --> 00:12:39.879 align:start position:0% offer a bug bounty and provide expectation<00:12:36.049> that<00:12:36.230> bugs<00:12:36.709> will<00:12:36.980> exist<00:12:37.369> and<00:12:38.889> so 00:12:39.879 --> 00:12:39.889 align:start position:0% expectation that bugs will exist and so 00:12:39.889 --> 00:12:42.129 align:start position:0% expectation that bugs will exist and so this<00:12:40.040> is<00:12:40.160> actually<00:12:40.279> what<00:12:40.549> true--but<00:12:40.850> does<00:12:41.139> we 00:12:42.129 --> 00:12:42.139 align:start position:0% this is actually what true--but does we 00:12:42.139 --> 00:12:44.829 align:start position:0% this is actually what true--but does we are<00:12:42.309> occasionally<00:12:43.309> the<00:12:44.119> protocol<00:12:44.569> pays 00:12:44.829 --> 00:12:44.839 align:start position:0% are occasionally the protocol pays 00:12:44.839 --> 00:12:46.689 align:start position:0% are occasionally the protocol pays solvers<00:12:45.439> for<00:12:45.709> submitting<00:12:46.160> incorrect 00:12:46.689 --> 00:12:46.699 align:start position:0% solvers for submitting incorrect 00:12:46.699 --> 00:12:52.590 align:start position:0% solvers for submitting incorrect solutions<00:12:47.179> you<00:12:47.449> have<00:12:47.480> to<00:12:47.779> get<00:12:47.899> it<00:12:48.019> wrong<00:12:49.149> so<00:12:50.589> so 00:12:52.590 --> 00:12:52.600 align:start position:0% solutions you have to get it wrong so so 00:12:52.600 --> 00:12:55.809 align:start position:0% solutions you have to get it wrong so so the<00:12:53.619> dispute<00:12:54.619> resolution<00:12:55.160> ensures 00:12:55.809 --> 00:12:55.819 align:start position:0% the dispute resolution ensures 00:12:55.819 --> 00:12:57.249 align:start position:0% the dispute resolution ensures correctness<00:12:56.179> whenever<00:12:56.540> forced<00:12:56.869> errors<00:12:57.139> are 00:12:57.249 --> 00:12:57.259 align:start position:0% correctness whenever forced errors are 00:12:57.259 --> 00:12:58.480 align:start position:0% correctness whenever forced errors are not<00:12:57.379> in<00:12:57.499> effect<00:12:57.589> what<00:12:57.980> do<00:12:58.040> I<00:12:58.129> mean<00:12:58.339> by<00:12:58.369> that 00:12:58.480 --> 00:12:58.490 align:start position:0% not in effect what do I mean by that 00:12:58.490 --> 00:13:00.369 align:start position:0% not in effect what do I mean by that since<00:12:59.240> you're<00:12:59.480> only<00:12:59.509> having<00:12:59.839> maybe<00:13:00.079> one<00:13:00.290> out 00:13:00.369 --> 00:13:00.379 align:start position:0% since you're only having maybe one out 00:13:00.379 --> 00:13:01.569 align:start position:0% since you're only having maybe one out of<00:13:00.410> a<00:13:00.559> thousand<00:13:00.920> times<00:13:01.100> you<00:13:01.249> might<00:13:01.369> have<00:13:01.549> a 00:13:01.569 --> 00:13:01.579 align:start position:0% of a thousand times you might have a 00:13:01.579 --> 00:13:03.879 align:start position:0% of a thousand times you might have a forced<00:13:01.939> error<00:13:02.149> but<00:13:02.540> the<00:13:02.660> idea<00:13:03.019> is<00:13:03.199> that<00:13:03.230> every 00:13:03.879 --> 00:13:03.889 align:start position:0% forced error but the idea is that every 00:13:03.889 --> 00:13:05.710 align:start position:0% forced error but the idea is that every verifier<00:13:04.279> doesn't<00:13:04.610> know<00:13:04.759> when<00:13:05.240> the<00:13:05.389> forced 00:13:05.710 --> 00:13:05.720 align:start position:0% verifier doesn't know when the forced 00:13:05.720 --> 00:13:06.850 align:start position:0% verifier doesn't know when the forced air<00:13:05.869> is<00:13:05.959> going<00:13:06.079> to<00:13:06.139> come<00:13:06.319> so<00:13:06.499> they're<00:13:06.649> just 00:13:06.850 --> 00:13:06.860 align:start position:0% air is going to come so they're just 00:13:06.860 --> 00:13:08.799 align:start position:0% air is going to come so they're just going<00:13:06.980> to<00:13:07.040> check<00:13:07.279> everything<00:13:07.939> so<00:13:08.299> most<00:13:08.540> of<00:13:08.720> the 00:13:08.799 --> 00:13:08.809 align:start position:0% going to check everything so most of the 00:13:08.809 --> 00:13:12.280 align:start position:0% going to check everything so most of the time<00:13:09.399> they're<00:13:10.399> the<00:13:10.699> the<00:13:10.999> the<00:13:11.540> verifiers<00:13:11.899> think 00:13:12.280 --> 00:13:12.290 align:start position:0% time they're the the the verifiers think 00:13:12.290 --> 00:13:13.569 align:start position:0% time they're the the the verifiers think they're<00:13:12.410> getting<00:13:12.649> paid<00:13:12.799> and<00:13:13.040> the<00:13:13.279> solver 00:13:13.569 --> 00:13:13.579 align:start position:0% they're getting paid and the solver 00:13:13.579 --> 00:13:14.919 align:start position:0% they're getting paid and the solver thinks<00:13:13.819> someone's<00:13:14.089> going<00:13:14.329> to<00:13:14.360> watch<00:13:14.600> and 00:13:14.919 --> 00:13:14.929 align:start position:0% thinks someone's going to watch and 00:13:14.929 --> 00:13:15.430 align:start position:0% thinks someone's going to watch and therefore 00:13:15.430 --> 00:13:15.440 align:start position:0% therefore 00:13:15.440 --> 00:13:19.150 align:start position:0% therefore he<00:13:15.590> gives<00:13:15.740> the<00:13:15.890> right<00:13:16.010> answer<00:13:17.140> so<00:13:18.140> an<00:13:18.440> ideally 00:13:19.150 --> 00:13:19.160 align:start position:0% he gives the right answer so an ideally 00:13:19.160 --> 00:13:21.520 align:start position:0% he gives the right answer so an ideally if<00:13:19.250> we<00:13:19.400> made<00:13:20.060> our<00:13:20.180> compiler<00:13:20.630> exactly<00:13:21.170> right<00:13:21.350> on 00:13:21.520 --> 00:13:21.530 align:start position:0% if we made our compiler exactly right on 00:13:21.530 --> 00:13:23.590 align:start position:0% if we made our compiler exactly right on this<00:13:21.770> architecture<00:13:22.370> no<00:13:23.090> one's<00:13:23.240> ever<00:13:23.390> going<00:13:23.510> to 00:13:23.590 --> 00:13:23.600 align:start position:0% this architecture no one's ever going to 00:13:23.600 --> 00:13:25.330 align:start position:0% this architecture no one's ever going to go<00:13:23.690> to<00:13:23.750> court<00:13:24.140> this<00:13:24.470> subroutine<00:13:24.770> is<00:13:25.130> never 00:13:25.330 --> 00:13:25.340 align:start position:0% go to court this subroutine is never 00:13:25.340 --> 00:13:27.850 align:start position:0% go to court this subroutine is never even<00:13:25.460> going<00:13:25.700> to<00:13:25.760> be<00:13:25.850> executed<00:13:26.570> so<00:13:26.870> that's<00:13:27.680> a 00:13:27.850 --> 00:13:27.860 align:start position:0% even going to be executed so that's a 00:13:27.860 --> 00:13:29.260 align:start position:0% even going to be executed so that's a lot<00:13:28.010> of<00:13:28.040> work<00:13:28.310> for<00:13:28.550> code<00:13:28.790> that<00:13:28.970> you're<00:13:29.120> never 00:13:29.260 --> 00:13:29.270 align:start position:0% lot of work for code that you're never 00:13:29.270 --> 00:13:31.630 align:start position:0% lot of work for code that you're never going<00:13:29.450> to<00:13:29.480> run<00:13:29.860> now<00:13:30.860> if<00:13:31.040> you<00:13:31.130> only<00:13:31.250> remember 00:13:31.630 --> 00:13:31.640 align:start position:0% going to run now if you only remember 00:13:31.640 --> 00:13:33.550 align:start position:0% going to run now if you only remember one<00:13:31.670> slide<00:13:32.030> from<00:13:32.240> my<00:13:32.360> talk<00:13:32.600> please<00:13:32.960> look<00:13:33.410> at 00:13:33.550 --> 00:13:33.560 align:start position:0% one slide from my talk please look at 00:13:33.560 --> 00:13:37.150 align:start position:0% one slide from my talk please look at this<00:13:33.710> one<00:13:33.890> this<00:13:34.400> is<00:13:34.640> a<00:13:34.670> picture<00:13:34.970> of<00:13:36.160> an 00:13:37.150 --> 00:13:37.160 align:start position:0% this one this is a picture of an 00:13:37.160 --> 00:13:39.340 align:start position:0% this one this is a picture of an illustration<00:13:37.640> of<00:13:37.910> Ruby<00:13:38.180> Ayers<00:13:38.330> Simon<00:13:39.140> deliver 00:13:39.340 --> 00:13:39.350 align:start position:0% illustration of Ruby Ayers Simon deliver 00:13:39.350 --> 00:13:43.810 align:start position:0% illustration of Ruby Ayers Simon deliver beers<00:13:39.590> panopticon<00:13:40.430> pewter<00:13:42.040> which<00:13:43.040> which<00:13:43.640> is 00:13:43.810 --> 00:13:43.820 align:start position:0% beers panopticon pewter which which is 00:13:43.820 --> 00:13:48.790 align:start position:0% beers panopticon pewter which which is based<00:13:44.030> on<00:13:45.340> Bentham's<00:13:46.340> panopticon<00:13:47.350> and<00:13:48.350> which 00:13:48.790 --> 00:13:48.800 align:start position:0% based on Bentham's panopticon and which 00:13:48.800 --> 00:13:51.250 align:start position:0% based on Bentham's panopticon and which has<00:13:49.100> physical<00:13:49.520> manifestations<00:13:50.240> in<00:13:50.480> the<00:13:50.930> State 00:13:51.250 --> 00:13:51.260 align:start position:0% has physical manifestations in the State 00:13:51.260 --> 00:13:53.080 align:start position:0% has physical manifestations in the State Penitentiary<00:13:51.410> in<00:13:52.040> Joliet<00:13:52.430> Illinois<00:13:52.460> the 00:13:53.080 --> 00:13:53.090 align:start position:0% Penitentiary in Joliet Illinois the 00:13:53.090 --> 00:13:54.730 align:start position:0% Penitentiary in Joliet Illinois the Presidium<00:13:53.600> Modelo<00:13:53.870> and<00:13:54.080> his<00:13:54.170> little<00:13:54.350> pedo 00:13:54.730 --> 00:13:54.740 align:start position:0% Presidium Modelo and his little pedo 00:13:54.740 --> 00:13:57.730 align:start position:0% Presidium Modelo and his little pedo sand<00:13:55.100> in<00:13:55.250> cuba<00:13:56.090> and<00:13:56.270> it's<00:13:56.450> it's<00:13:56.750> it's<00:13:57.200> a<00:13:57.410> prison 00:13:57.730 --> 00:13:57.740 align:start position:0% sand in cuba and it's it's it's a prison 00:13:57.740 --> 00:13:59.740 align:start position:0% sand in cuba and it's it's it's a prison okay<00:13:57.980> so<00:13:58.040> you<00:13:58.220> have<00:13:58.550> in<00:13:58.850> the<00:13:59.210> middle<00:13:59.480> there's<00:13:59.690> a 00:13:59.740 --> 00:13:59.750 align:start position:0% okay so you have in the middle there's a 00:13:59.750 --> 00:14:02.020 align:start position:0% okay so you have in the middle there's a watchtower<00:14:00.440> with<00:14:00.770> someone<00:14:01.100> who's<00:14:01.310> who's 00:14:02.020 --> 00:14:02.030 align:start position:0% watchtower with someone who's who's 00:14:02.030 --> 00:14:05.440 align:start position:0% watchtower with someone who's who's looking<00:14:02.600> around<00:14:03.050> into<00:14:04.000> all<00:14:05.000> of<00:14:05.030> these<00:14:05.210> cells 00:14:05.440 --> 00:14:05.450 align:start position:0% looking around into all of these cells 00:14:05.450 --> 00:14:07.540 align:start position:0% looking around into all of these cells there's<00:14:06.260> a<00:14:06.350> bright<00:14:06.530> light<00:14:06.560> so<00:14:07.010> they<00:14:07.130> can't<00:14:07.340> see 00:14:07.540 --> 00:14:07.550 align:start position:0% there's a bright light so they can't see 00:14:07.550 --> 00:14:09.280 align:start position:0% there's a bright light so they can't see what<00:14:07.730> he's<00:14:07.850> looking<00:14:08.180> at<00:14:08.300> but<00:14:08.810> out<00:14:08.930> of<00:14:08.960> fear 00:14:09.280 --> 00:14:09.290 align:start position:0% what he's looking at but out of fear 00:14:09.290 --> 00:14:13.150 align:start position:0% what he's looking at but out of fear that<00:14:09.470> the<00:14:09.800> the<00:14:11.590> guarding<00:14:12.590> of<00:14:12.650> the<00:14:12.710> watchtower 00:14:13.150 --> 00:14:13.160 align:start position:0% that the the guarding of the watchtower 00:14:13.160 --> 00:14:14.470 align:start position:0% that the the guarding of the watchtower is<00:14:13.310> actually<00:14:13.730> looking<00:14:13.970> at<00:14:14.090> them<00:14:14.240> they 00:14:14.470 --> 00:14:14.480 align:start position:0% is actually looking at them they 00:14:14.480 --> 00:14:16.210 align:start position:0% is actually looking at them they actually<00:14:14.840> behave<00:14:15.140> correctly<00:14:15.470> so<00:14:16.040> that's 00:14:16.210 --> 00:14:16.220 align:start position:0% actually behave correctly so that's 00:14:16.220 --> 00:14:18.100 align:start position:0% actually behave correctly so that's that's<00:14:16.820> the<00:14:17.120> principle<00:14:17.570> of<00:14:17.660> the<00:14:17.810> panopticon 00:14:18.100 --> 00:14:18.110 align:start position:0% that's the principle of the panopticon 00:14:18.110 --> 00:14:23.380 align:start position:0% that's the principle of the panopticon pewter<00:14:18.710> it's<00:14:18.860> all<00:14:19.040> about<00:14:21.820> you<00:14:22.820> imagine<00:14:23.270> that 00:14:23.380 --> 00:14:23.390 align:start position:0% pewter it's all about you imagine that 00:14:23.390 --> 00:14:24.490 align:start position:0% pewter it's all about you imagine that these<00:14:23.540> people<00:14:23.720> sitting<00:14:24.080> up<00:14:24.170> here<00:14:24.380> are<00:14:24.470> all 00:14:24.490 --> 00:14:24.500 align:start position:0% these people sitting up here are all 00:14:24.500 --> 00:14:27.880 align:start position:0% these people sitting up here are all performing<00:14:25.100> the<00:14:25.520> computations<00:14:26.480> and<00:14:26.890> this 00:14:27.880 --> 00:14:27.890 align:start position:0% performing the computations and this 00:14:27.890 --> 00:14:30.400 align:start position:0% performing the computations and this this<00:14:28.370> they're<00:14:29.090> there<00:14:29.480> they<00:14:29.750> do<00:14:29.990> it<00:14:30.110> correctly 00:14:30.400 --> 00:14:30.410 align:start position:0% this they're there they do it correctly 00:14:30.410 --> 00:14:31.570 align:start position:0% this they're there they do it correctly because<00:14:30.590> they<00:14:30.860> think<00:14:30.920> they're<00:14:31.160> being<00:14:31.310> watched 00:14:31.570 --> 00:14:31.580 align:start position:0% because they think they're being watched 00:14:31.580 --> 00:14:34.600 align:start position:0% because they think they're being watched so<00:14:31.910> and<00:14:32.840> and<00:14:33.320> I<00:14:33.500> just<00:14:33.740> quote<00:14:34.010> from<00:14:34.040> Michel 00:14:34.600 --> 00:14:34.610 align:start position:0% so and and I just quote from Michel 00:14:34.610 --> 00:14:36.640 align:start position:0% so and and I just quote from Michel Foucault<00:14:34.910> who<00:14:35.090> was<00:14:35.180> also<00:14:35.360> an<00:14:35.750> important 00:14:36.640 --> 00:14:36.650 align:start position:0% Foucault who was also an important 00:14:36.650 --> 00:14:38.980 align:start position:0% Foucault who was also an important figure<00:14:36.830> in<00:14:36.980> the<00:14:37.160> ninth<00:14:37.310> a<00:14:37.910> book<00:14:38.630> you<00:14:38.810> know<00:14:38.900> in 00:14:38.980 --> 00:14:38.990 align:start position:0% figure in the ninth a book you know in 00:14:38.990 --> 00:14:41.890 align:start position:0% figure in the ninth a book you know in the<00:14:39.050> 1970s<00:14:39.800> about<00:14:40.360> Panopto<00:14:41.360> system<00:14:41.660> we<00:14:41.780> have 00:14:41.890 --> 00:14:41.900 align:start position:0% the 1970s about Panopto system we have 00:14:41.900 --> 00:14:43.870 align:start position:0% the 1970s about Panopto system we have seen<00:14:41.930> that<00:14:42.350> anyone<00:14:42.680> may<00:14:42.830> come<00:14:42.860> an<00:14:43.130> exercise<00:14:43.580> in 00:14:43.870 --> 00:14:43.880 align:start position:0% seen that anyone may come an exercise in 00:14:43.880 --> 00:14:45.430 align:start position:0% seen that anyone may come an exercise in the<00:14:44.180> central<00:14:44.510> tower<00:14:44.690> the<00:14:44.930> functions<00:14:45.320> of 00:14:45.430 --> 00:14:45.440 align:start position:0% the central tower the functions of 00:14:45.440 --> 00:14:48.760 align:start position:0% the central tower the functions of surveillance<00:14:46.210> so<00:14:47.210> anybody<00:14:48.050> can<00:14:48.320> sit<00:14:48.500> in<00:14:48.620> there 00:14:48.760 --> 00:14:48.770 align:start position:0% surveillance so anybody can sit in there 00:14:48.770 --> 00:14:50.470 align:start position:0% surveillance so anybody can sit in there now<00:14:49.220> there's<00:14:49.430> no<00:14:49.520> reputation<00:14:50.000> this<00:14:50.360> is 00:14:50.470 --> 00:14:50.480 align:start position:0% now there's no reputation this is 00:14:50.480 --> 00:14:52.240 align:start position:0% now there's no reputation this is exactly<00:14:50.840> an<00:14:51.230> illustration<00:14:51.710> of<00:14:51.890> true--but 00:14:52.240 --> 00:14:52.250 align:start position:0% exactly an illustration of true--but 00:14:52.250 --> 00:14:53.560 align:start position:0% exactly an illustration of true--but because<00:14:52.490> there's<00:14:52.700> no<00:14:52.820> reputation<00:14:53.270> and 00:14:53.560 --> 00:14:53.570 align:start position:0% because there's no reputation and 00:14:53.570 --> 00:14:56.560 align:start position:0% because there's no reputation and true--but<00:14:54.350> anyone<00:14:55.070> can<00:14:55.370> can<00:14:55.700> come<00:14:55.940> in<00:14:56.060> and<00:14:56.240> and 00:14:56.560 --> 00:14:56.570 align:start position:0% true--but anyone can can come in and and 00:14:56.570 --> 00:14:59.260 align:start position:0% true--but anyone can can come in and and and<00:14:56.870> do<00:14:56.990> that<00:14:57.110> so<00:14:57.350> let<00:14:57.860> me<00:14:58.010> in<00:14:58.820> the<00:14:58.910> last<00:14:59.089> few 00:14:59.260 --> 00:14:59.270 align:start position:0% and do that so let me in the last few 00:14:59.270 --> 00:15:00.910 align:start position:0% and do that so let me in the last few minutes<00:14:59.510> talk<00:14:59.720> about<00:14:59.960> the<00:15:00.170> the<00:15:00.440> developments 00:15:00.910 --> 00:15:00.920 align:start position:0% minutes talk about the the developments 00:15:00.920 --> 00:15:02.890 align:start position:0% minutes talk about the the developments that<00:15:00.980> we're<00:15:01.190> going<00:15:01.339> on<00:15:01.520> with<00:15:01.760> with<00:15:02.390> with<00:15:02.750> true 00:15:02.890 --> 00:15:02.900 align:start position:0% that we're going on with with with true 00:15:02.900 --> 00:15:04.270 align:start position:0% that we're going on with with with true right<00:15:03.110> now<00:15:03.200> so<00:15:03.350> the<00:15:03.470> de<00:15:03.650> true--but<00:15:03.920> virtual 00:15:04.270 --> 00:15:04.280 align:start position:0% right now so the de true--but virtual 00:15:04.280 --> 00:15:05.530 align:start position:0% right now so the de true--but virtual machine<00:15:04.580> when<00:15:04.700> I<00:15:04.790> speak<00:15:05.000> of<00:15:05.150> the<00:15:05.240> virtual 00:15:05.530 --> 00:15:05.540 align:start position:0% machine when I speak of the virtual 00:15:05.540 --> 00:15:07.960 align:start position:0% machine when I speak of the virtual machine<00:15:05.780> I<00:15:05.810> mean<00:15:06.170> specifically<00:15:07.160> this<00:15:07.400> this 00:15:07.960 --> 00:15:07.970 align:start position:0% machine I mean specifically this this 00:15:07.970 --> 00:15:09.700 align:start position:0% machine I mean specifically this this new<00:15:08.210> architecture<00:15:08.450> that's<00:15:09.050> offset<00:15:09.350> not<00:15:09.530> the 00:15:09.700 --> 00:15:09.710 align:start position:0% new architecture that's offset not the 00:15:09.710 --> 00:15:12.160 align:start position:0% new architecture that's offset not the which<00:15:10.460> is<00:15:10.580> part<00:15:10.820> off<00:15:11.089> chain<00:15:11.600> but<00:15:11.720> also<00:15:11.870> you're 00:15:12.160 --> 00:15:12.170 align:start position:0% which is part off chain but also you're 00:15:12.170 --> 00:15:14.350 align:start position:0% which is part off chain but also you're on<00:15:12.500> chain<00:15:12.860> stepper<00:15:13.280> which<00:15:13.400> allows<00:15:13.700> judges<00:15:14.210> to 00:15:14.350 --> 00:15:14.360 align:start position:0% on chain stepper which allows judges to 00:15:14.360 --> 00:15:18.160 align:start position:0% on chain stepper which allows judges to participate<00:15:14.960> in<00:15:15.380> this<00:15:16.010> mechanism<00:15:16.339> so<00:15:17.150> as<00:15:17.540> I 00:15:18.160 --> 00:15:18.170 align:start position:0% participate in this mechanism so as I 00:15:18.170 --> 00:15:19.510 align:start position:0% participate in this mechanism so as I mentioned<00:15:18.470> before<00:15:18.530> the<00:15:18.860> tasks<00:15:19.190> have<00:15:19.370> to 00:15:19.510 --> 00:15:19.520 align:start position:0% mentioned before the tasks have to 00:15:19.520 --> 00:15:21.880 align:start position:0% mentioned before the tasks have to compile<00:15:19.880> and<00:15:20.210> execute<00:15:20.650> identically<00:15:21.650> on<00:15:21.680> all 00:15:21.880 --> 00:15:21.890 align:start position:0% compile and execute identically on all 00:15:21.890 --> 00:15:23.710 align:start position:0% compile and execute identically on all machines<00:15:22.010> otherwise<00:15:22.940> there's<00:15:23.210> no<00:15:23.330> notion<00:15:23.660> of 00:15:23.710 --> 00:15:23.720 align:start position:0% machines otherwise there's no notion of 00:15:23.720 --> 00:15:26.200 align:start position:0% machines otherwise there's no notion of step<00:15:24.020> and<00:15:24.200> the<00:15:24.710> judges<00:15:25.130> can't<00:15:25.640> really 00:15:26.200 --> 00:15:26.210 align:start position:0% step and the judges can't really 00:15:26.210 --> 00:15:27.970 align:start position:0% step and the judges can't really participate<00:15:26.660> so<00:15:27.320> they<00:15:27.440> all<00:15:27.560> have<00:15:27.680> to<00:15:27.710> be<00:15:27.800> the 00:15:27.970 --> 00:15:27.980 align:start position:0% participate so they all have to be the 00:15:27.980 --> 00:15:28.680 align:start position:0% participate so they all have to be the same<00:15:28.190> the 00:15:28.680 --> 00:15:28.690 align:start position:0% same the 00:15:28.690 --> 00:15:30.540 align:start position:0% same the thing<00:15:28.960> is<00:15:29.080> that<00:15:29.290> you're<00:15:29.590> single<00:15:29.800> computation 00:15:30.540 --> 00:15:30.550 align:start position:0% thing is that you're single computation 00:15:30.550 --> 00:15:33.150 align:start position:0% thing is that you're single computation step<00:15:30.820> on<00:15:31.000> the<00:15:31.090> TVM<00:15:31.420> has<00:15:31.720> to<00:15:31.900> be<00:15:32.080> running<00:15:32.710> within 00:15:33.150 --> 00:15:33.160 align:start position:0% step on the TVM has to be running within 00:15:33.160 --> 00:15:36.290 align:start position:0% step on the TVM has to be running within if<00:15:33.520> their<00:15:33.670> mas<00:15:34.030> limit<00:15:34.390> itself<00:15:34.750> so<00:15:35.470> into<00:15:35.800> this 00:15:36.290 --> 00:15:36.300 align:start position:0% if their mas limit itself so into this 00:15:36.300 --> 00:15:38.790 align:start position:0% if their mas limit itself so into this and<00:15:37.300> not<00:15:37.600> only<00:15:37.720> I<00:15:37.840> also<00:15:38.080> have<00:15:38.260> to<00:15:38.380> the<00:15:38.560> space 00:15:38.790 --> 00:15:38.800 align:start position:0% and not only I also have to the space 00:15:38.800 --> 00:15:40.800 align:start position:0% and not only I also have to the space required<00:15:39.220> to<00:15:39.430> describe<00:15:39.730> a<00:15:39.910> state<00:15:40.150> change<00:15:40.390> also 00:15:40.800 --> 00:15:40.810 align:start position:0% required to describe a state change also 00:15:40.810 --> 00:15:42.600 align:start position:0% required to describe a state change also has<00:15:40.900> to<00:15:41.050> fit<00:15:41.230> inside<00:15:41.440> a<00:15:41.560> theorem<00:15:41.950> transaction 00:15:42.600 --> 00:15:42.610 align:start position:0% has to fit inside a theorem transaction 00:15:42.610 --> 00:15:47.400 align:start position:0% has to fit inside a theorem transaction so<00:15:42.790> we<00:15:44.940> ideally<00:15:45.940> use<00:15:46.450> the<00:15:46.600> Turing<00:15:47.050> machine<00:15:47.260> as 00:15:47.400 --> 00:15:47.410 align:start position:0% so we ideally use the Turing machine as 00:15:47.410 --> 00:15:49.680 align:start position:0% so we ideally use the Turing machine as I<00:15:47.500> said<00:15:47.710> before<00:15:48.070> but<00:15:48.250> there's<00:15:48.460> no<00:15:48.640> at<00:15:49.390> least<00:15:49.570> I 00:15:49.680 --> 00:15:49.690 align:start position:0% I said before but there's no at least I 00:15:49.690 --> 00:15:51.930 align:start position:0% I said before but there's no at least I haven't<00:15:49.840> found<00:15:50.080> any<00:15:50.230> code<00:15:50.470> that<00:15:50.710> takes<00:15:51.070> a<00:15:51.340> bit 00:15:51.930 --> 00:15:51.940 align:start position:0% haven't found any code that takes a bit 00:15:51.940 --> 00:15:53.460 align:start position:0% haven't found any code that takes a bit of<00:15:51.970> C<00:15:52.210> code<00:15:52.390> and<00:15:52.450> turns<00:15:52.780> it<00:15:52.900> into<00:15:53.050> a<00:15:53.140> Turing 00:15:53.460 --> 00:15:53.470 align:start position:0% of C code and turns it into a Turing 00:15:53.470 --> 00:15:56.220 align:start position:0% of C code and turns it into a Turing machine<00:15:53.790> so<00:15:54.790> we<00:15:54.970> had<00:15:55.090> to<00:15:55.300> do<00:15:55.750> the<00:15:55.870> next<00:15:56.050> best 00:15:56.220 --> 00:15:56.230 align:start position:0% machine so we had to do the next best 00:15:56.230 --> 00:15:58.830 align:start position:0% machine so we had to do the next best thing<00:15:56.350> which<00:15:56.620> is<00:15:56.770> go<00:15:56.980> to<00:15:57.040> web<00:15:57.970> assembly<00:15:58.480> and<00:15:58.720> we 00:15:58.830 --> 00:15:58.840 align:start position:0% thing which is go to web assembly and we 00:15:58.840 --> 00:16:02.250 align:start position:0% thing which is go to web assembly and we even<00:15:59.800> broke<00:16:00.130> that<00:16:00.310> down<00:16:00.550> further<00:16:01.120> it's<00:16:01.510> we<00:16:01.930> we 00:16:02.250 --> 00:16:02.260 align:start position:0% even broke that down further it's we we 00:16:02.260 --> 00:16:05.100 align:start position:0% even broke that down further it's we we have<00:16:02.500> each<00:16:03.400> web<00:16:03.670> assembly<00:16:04.000> step<00:16:04.210> is<00:16:04.420> broken 00:16:05.100 --> 00:16:05.110 align:start position:0% have each web assembly step is broken 00:16:05.110 --> 00:16:08.700 align:start position:0% have each web assembly step is broken down<00:16:05.320> into<00:16:05.560> basically<00:16:06.600> sixteen<00:16:07.600> sub<00:16:08.410> steps 00:16:08.700 --> 00:16:08.710 align:start position:0% down into basically sixteen sub steps 00:16:08.710 --> 00:16:11.490 align:start position:0% down into basically sixteen sub steps sort<00:16:08.980> of<00:16:09.100> so<00:16:09.340> so<00:16:09.610> this<00:16:09.790> is<00:16:09.850> this<00:16:10.210> was<00:16:10.360> a<00:16:10.390> we<00:16:11.290> have 00:16:11.490 --> 00:16:11.500 align:start position:0% sort of so so this is this was a we have 00:16:11.500 --> 00:16:13.350 align:start position:0% sort of so so this is this was a we have these<00:16:11.650> properties<00:16:11.890> of<00:16:12.310> our<00:16:12.430> of<00:16:12.640> our<00:16:12.760> of<00:16:13.120> our 00:16:13.350 --> 00:16:13.360 align:start position:0% these properties of our of our of our 00:16:13.360 --> 00:16:14.640 align:start position:0% these properties of our of our of our architecture<00:16:13.630> so<00:16:14.050> if<00:16:14.140> you<00:16:14.200> look<00:16:14.350> at<00:16:14.470> what<00:16:14.590> does 00:16:14.640 --> 00:16:14.650 align:start position:0% architecture so if you look at what does 00:16:14.650 --> 00:16:16.590 align:start position:0% architecture so if you look at what does it<00:16:14.710> look<00:16:14.920> like<00:16:14.980> overall<00:16:15.910> the<00:16:16.120> picture<00:16:16.240> of<00:16:16.510> the 00:16:16.590 --> 00:16:16.600 align:start position:0% it look like overall the picture of the 00:16:16.600 --> 00:16:19.140 align:start position:0% it look like overall the picture of the TVM<00:16:16.960> so<00:16:17.440> you<00:16:17.500> have<00:16:17.620> as<00:16:17.710> your<00:16:17.890> c<00:16:18.130> and<00:16:18.310> c++<00:16:18.490> code 00:16:19.140 --> 00:16:19.150 align:start position:0% TVM so you have as your c and c++ code 00:16:19.150 --> 00:16:23.670 align:start position:0% TVM so you have as your c and c++ code and<00:16:19.570> it's<00:16:20.380> coming<00:16:20.680> in<00:16:20.800> to<00:16:22.290> you<00:16:23.290> want<00:16:23.440> to<00:16:23.530> run 00:16:23.670 --> 00:16:23.680 align:start position:0% and it's coming in to you want to run 00:16:23.680 --> 00:16:25.440 align:start position:0% and it's coming in to you want to run this<00:16:23.800> task<00:16:24.010> so<00:16:24.190> your<00:16:24.340> smart<00:16:24.640> contract<00:16:25.090> needs 00:16:25.440 --> 00:16:25.450 align:start position:0% this task so your smart contract needs 00:16:25.450 --> 00:16:27.450 align:start position:0% this task so your smart contract needs some<00:16:25.690> computational<00:16:26.350> boost<00:16:26.590> so<00:16:27.010> you<00:16:27.040> have<00:16:27.190> a<00:16:27.220> C 00:16:27.450 --> 00:16:27.460 align:start position:0% some computational boost so you have a C 00:16:27.460 --> 00:16:29.700 align:start position:0% some computational boost so you have a C or<00:16:27.580> C++<00:16:27.760> code<00:16:28.390> that<00:16:28.540> says<00:16:28.750> the<00:16:29.140> task<00:16:29.380> that<00:16:29.500> it 00:16:29.700 --> 00:16:29.710 align:start position:0% or C++ code that says the task that it 00:16:29.710 --> 00:16:31.140 align:start position:0% or C++ code that says the task that it wants<00:16:29.920> performed<00:16:30.370> and<00:16:30.490> it<00:16:30.550> wants<00:16:30.760> to<00:16:30.820> ensure 00:16:31.140 --> 00:16:31.150 align:start position:0% wants performed and it wants to ensure 00:16:31.150 --> 00:16:32.880 align:start position:0% wants performed and it wants to ensure that<00:16:31.180> it's<00:16:31.480> done<00:16:31.660> correctly<00:16:32.350> you<00:16:32.440> can<00:16:32.740> use 00:16:32.880 --> 00:16:32.890 align:start position:0% that it's done correctly you can use 00:16:32.890 --> 00:16:37.110 align:start position:0% that it's done correctly you can use this<00:16:33.600> property<00:16:34.600> called<00:16:34.900> in<00:16:35.430> unscripted<00:16:36.430> which 00:16:37.110 --> 00:16:37.120 align:start position:0% this property called in unscripted which 00:16:37.120 --> 00:16:39.630 align:start position:0% this property called in unscripted which which<00:16:37.480> we<00:16:37.660> use<00:16:37.870> to<00:16:38.050> transform<00:16:38.620> the<00:16:39.040> C++<00:16:39.610> code 00:16:39.630 --> 00:16:39.640 align:start position:0% which we use to transform the C++ code 00:16:39.640 --> 00:16:41.730 align:start position:0% which we use to transform the C++ code into<00:16:40.060> the<00:16:40.090> web<00:16:40.420> assembly<00:16:40.840> code<00:16:41.020> now<00:16:41.440> that<00:16:41.590> web 00:16:41.730 --> 00:16:41.740 align:start position:0% into the web assembly code now that web 00:16:41.740 --> 00:16:43.500 align:start position:0% into the web assembly code now that web assembly<00:16:42.130> code<00:16:42.280> is<00:16:42.430> used<00:16:42.610> in<00:16:42.760> two<00:16:42.880> places<00:16:43.150> it's 00:16:43.500 --> 00:16:43.510 align:start position:0% assembly code is used in two places it's 00:16:43.510 --> 00:16:46.500 align:start position:0% assembly code is used in two places it's used<00:16:43.690> both<00:16:43.930> off<00:16:44.290> chain<00:16:44.830> in<00:16:45.040> this<00:16:45.700> oft<00:16:46.030> we<00:16:46.390> use 00:16:46.500 --> 00:16:46.510 align:start position:0% used both off chain in this oft we use 00:16:46.510 --> 00:16:48.960 align:start position:0% used both off chain in this oft we use the<00:16:46.690> Oh<00:16:46.720> camel<00:16:47.110> reference<00:16:47.950> interpreter<00:16:48.490> to<00:16:48.700> to 00:16:48.960 --> 00:16:48.970 align:start position:0% the Oh camel reference interpreter to to 00:16:48.970 --> 00:16:51.810 align:start position:0% the Oh camel reference interpreter to to generate<00:16:49.690> the<00:16:50.380> states<00:16:50.950> you<00:16:51.430> list<00:16:51.670> of 00:16:51.810 --> 00:16:51.820 align:start position:0% generate the states you list of 00:16:51.820 --> 00:16:54.450 align:start position:0% generate the states you list of computation<00:16:52.800> steps<00:16:53.800> that<00:16:54.100> are<00:16:54.190> going<00:16:54.280> to<00:16:54.370> go 00:16:54.450 --> 00:16:54.460 align:start position:0% computation steps that are going to go 00:16:54.460 --> 00:16:55.680 align:start position:0% computation steps that are going to go through<00:16:54.610> on<00:16:54.700> the<00:16:54.790> computation<00:16:55.300> that's<00:16:55.450> used 00:16:55.680 --> 00:16:55.690 align:start position:0% through on the computation that's used 00:16:55.690 --> 00:16:56.820 align:start position:0% through on the computation that's used by<00:16:55.780> the<00:16:55.840> solvers<00:16:56.260> and<00:16:56.290> the<00:16:56.440> verifiers 00:16:56.820 --> 00:16:56.830 align:start position:0% by the solvers and the verifiers 00:16:56.830 --> 00:16:58.890 align:start position:0% by the solvers and the verifiers meanwhile<00:16:57.280> the<00:16:57.730> task<00:16:57.970> giver<00:16:58.270> pitches<00:16:58.750> this 00:16:58.890 --> 00:16:58.900 align:start position:0% meanwhile the task giver pitches this 00:16:58.900 --> 00:17:01.740 align:start position:0% meanwhile the task giver pitches this woz<00:16:59.530> and<00:16:59.560> tasks<00:16:59.950> actually<00:17:00.280> on<00:17:00.580> to<00:17:00.790> he<00:17:01.390> commits 00:17:01.740 --> 00:17:01.750 align:start position:0% woz and tasks actually on to he commits 00:17:01.750 --> 00:17:04.610 align:start position:0% woz and tasks actually on to he commits the<00:17:01.870> task<00:17:02.230> to<00:17:02.500> the<00:17:02.530> chain<00:17:02.860> itself<00:17:03.640> so<00:17:04.329> that 00:17:04.610 --> 00:17:04.620 align:start position:0% the task to the chain itself so that 00:17:04.620 --> 00:17:07.679 align:start position:0% the task to the chain itself so that it's<00:17:05.620> enforceable<00:17:06.069> so<00:17:06.670> the<00:17:06.790> judges<00:17:07.030> can<00:17:07.240> can 00:17:07.679 --> 00:17:07.689 align:start position:0% it's enforceable so the judges can can 00:17:07.689 --> 00:17:08.819 align:start position:0% it's enforceable so the judges can can can<00:17:07.959> do<00:17:08.050> their<00:17:08.260> and<00:17:08.350> then<00:17:08.439> all<00:17:08.589> this<00:17:08.770> stuff 00:17:08.819 --> 00:17:08.829 align:start position:0% can do their and then all this stuff 00:17:08.829 --> 00:17:10.949 align:start position:0% can do their and then all this stuff about<00:17:09.189> the<00:17:09.339> incentives<00:17:09.910> that<00:17:10.150> we<00:17:10.540> discussed 00:17:10.949 --> 00:17:10.959 align:start position:0% about the incentives that we discussed 00:17:10.959 --> 00:17:12.870 align:start position:0% about the incentives that we discussed before<00:17:11.350> and<00:17:11.680> the<00:17:11.740> four<00:17:11.920> stairs<00:17:12.189> are<00:17:12.430> monitored 00:17:12.870 --> 00:17:12.880 align:start position:0% before and the four stairs are monitored 00:17:12.880 --> 00:17:14.850 align:start position:0% before and the four stairs are monitored there<00:17:13.060> and<00:17:13.209> we<00:17:13.270> have<00:17:13.390> this<00:17:13.750> this<00:17:14.470> is<00:17:14.620> what 00:17:14.850 --> 00:17:14.860 align:start position:0% there and we have this this is what 00:17:14.860 --> 00:17:16.800 align:start position:0% there and we have this this is what holds<00:17:15.010> the<00:17:15.310> money<00:17:15.880> that<00:17:16.060> pays<00:17:16.270> out<00:17:16.420> some<00:17:16.720> of 00:17:16.800 --> 00:17:16.810 align:start position:0% holds the money that pays out some of 00:17:16.810 --> 00:17:19.290 align:start position:0% holds the money that pays out some of the<00:17:16.870> incentives<00:17:17.380> and<00:17:18.120> here's<00:17:19.120> where<00:17:19.270> the 00:17:19.290 --> 00:17:19.300 align:start position:0% the incentives and here's where the 00:17:19.300 --> 00:17:20.640 align:start position:0% the incentives and here's where the judges<00:17:19.600> live<00:17:19.900> they're<00:17:20.079> running<00:17:20.380> this<00:17:20.500> is 00:17:20.640 --> 00:17:20.650 align:start position:0% judges live they're running this is 00:17:20.650 --> 00:17:22.140 align:start position:0% judges live they're running this is where<00:17:20.800> you<00:17:20.890> that's<00:17:21.250> on<00:17:21.490> chain<00:17:21.760> and<00:17:21.939> it<00:17:22.000> runs 00:17:22.140 --> 00:17:22.150 align:start position:0% where you that's on chain and it runs 00:17:22.150 --> 00:17:23.520 align:start position:0% where you that's on chain and it runs one<00:17:22.390> step<00:17:22.630> now<00:17:22.780> I<00:17:22.810> want<00:17:22.990> to<00:17:23.050> point<00:17:23.170> out<00:17:23.290> that<00:17:23.410> we 00:17:23.520 --> 00:17:23.530 align:start position:0% one step now I want to point out that we 00:17:23.530 --> 00:17:26.640 align:start position:0% one step now I want to point out that we do<00:17:23.740> have<00:17:24.130> a<00:17:24.550> new<00:17:25.420> file<00:17:25.689> system<00:17:25.930> for<00:17:26.350> true--but 00:17:26.640 --> 00:17:26.650 align:start position:0% do have a new file system for true--but 00:17:26.650 --> 00:17:32.580 align:start position:0% do have a new file system for true--but which<00:17:27.520> is<00:17:28.110> basically<00:17:29.110> has<00:17:31.080> well<00:17:32.080> it<00:17:32.230> currently 00:17:32.580 --> 00:17:32.590 align:start position:0% which is basically has well it currently 00:17:32.590 --> 00:17:35.160 align:start position:0% which is basically has well it currently has<00:17:32.740> two<00:17:33.100> two<00:17:33.490> flavors<00:17:33.940> one<00:17:34.180> is<00:17:34.300> you<00:17:34.930> could<00:17:35.080> if 00:17:35.160 --> 00:17:35.170 align:start position:0% has two two flavors one is you could if 00:17:35.170 --> 00:17:36.960 align:start position:0% has two two flavors one is you could if you<00:17:35.260> store<00:17:35.560> the<00:17:35.710> data<00:17:36.460> on<00:17:36.580> the<00:17:36.670> chain<00:17:36.850> you 00:17:36.960 --> 00:17:36.970 align:start position:0% you store the data on the chain you 00:17:36.970 --> 00:17:38.880 align:start position:0% you store the data on the chain you still<00:17:37.210> need<00:17:37.360> a<00:17:37.390> file<00:17:37.810> system<00:17:38.020> to<00:17:38.350> access<00:17:38.500> it<00:17:38.800> on 00:17:38.880 --> 00:17:38.890 align:start position:0% still need a file system to access it on 00:17:38.890 --> 00:17:40.980 align:start position:0% still need a file system to access it on the<00:17:39.010> blockchain<00:17:39.220> so<00:17:39.550> you<00:17:39.640> can<00:17:39.790> you<00:17:40.240> can<00:17:40.270> put 00:17:40.980 --> 00:17:40.990 align:start position:0% the blockchain so you can you can put 00:17:40.990 --> 00:17:42.240 align:start position:0% the blockchain so you can you can put your<00:17:41.140> data<00:17:41.320> on<00:17:41.470> the<00:17:41.590> chain<00:17:41.830> and 00:17:42.240 --> 00:17:42.250 align:start position:0% your data on the chain and 00:17:42.250 --> 00:17:44.150 align:start position:0% your data on the chain and advantage<00:17:42.580> there's<00:17:42.820> that<00:17:43.120> it<00:17:43.420> stays<00:17:43.750> there 00:17:44.150 --> 00:17:44.160 align:start position:0% advantage there's that it stays there 00:17:44.160 --> 00:17:48.630 align:start position:0% advantage there's that it stays there but<00:17:45.160> you<00:17:47.010> disadvantages<00:17:48.010> you<00:17:48.130> can't<00:17:48.310> put<00:17:48.460> very 00:17:48.630 --> 00:17:48.640 align:start position:0% but you disadvantages you can't put very 00:17:48.640 --> 00:17:50.250 align:start position:0% but you disadvantages you can't put very much<00:17:48.700> ipfs<00:17:49.450> on<00:17:49.600> the<00:17:49.660> other<00:17:49.780> hand<00:17:49.990> you<00:17:50.110> can 00:17:50.250 --> 00:17:50.260 align:start position:0% much ipfs on the other hand you can 00:17:50.260 --> 00:17:54.090 align:start position:0% much ipfs on the other hand you can store<00:17:50.500> whatever<00:17:50.680> you<00:17:50.890> want<00:17:51.130> but<00:17:53.100> data 00:17:54.090 --> 00:17:54.100 align:start position:0% store whatever you want but data 00:17:54.100 --> 00:17:55.860 align:start position:0% store whatever you want but data availability<00:17:54.550> well<00:17:55.060> ideally<00:17:55.480> we<00:17:55.660> want<00:17:55.750> a 00:17:55.860 --> 00:17:55.870 align:start position:0% availability well ideally we want a 00:17:55.870 --> 00:17:59.340 align:start position:0% availability well ideally we want a system<00:17:56.020> that<00:17:56.710> that<00:17:57.870> has<00:17:58.870> both<00:17:59.140> of<00:17:59.170> these 00:17:59.340 --> 00:17:59.350 align:start position:0% system that that has both of these 00:17:59.350 --> 00:18:01.410 align:start position:0% system that that has both of these properties<00:17:59.680> the<00:17:59.950> data<00:18:00.130> is<00:18:00.250> available<00:18:00.760> and<00:18:01.360> you 00:18:01.410 --> 00:18:01.420 align:start position:0% properties the data is available and you 00:18:01.420 --> 00:18:05.360 align:start position:0% properties the data is available and you can<00:18:01.660> put<00:18:01.840> stuff<00:18:01.960> there<00:18:02.290> so<00:18:03.480> to<00:18:04.480> be<00:18:04.600> continued 00:18:05.360 --> 00:18:05.370 align:start position:0% can put stuff there so to be continued 00:18:05.370 --> 00:18:07.800 align:start position:0% can put stuff there so to be continued so<00:18:06.370> let<00:18:06.700> me<00:18:06.760> just<00:18:06.910> wrap<00:18:07.060> things<00:18:07.330> up<00:18:07.480> we<00:18:07.690> are 00:18:07.800 --> 00:18:07.810 align:start position:0% so let me just wrap things up we are 00:18:07.810 --> 00:18:12.420 align:start position:0% so let me just wrap things up we are we're<00:18:08.050> we're<00:18:08.410> in<00:18:08.530> the<00:18:08.650> in<00:18:09.070> the<00:18:09.220> process<00:18:09.850> of<00:18:11.430> one 00:18:12.420 --> 00:18:12.430 align:start position:0% we're we're in the in the process of one 00:18:12.430 --> 00:18:14.250 align:start position:0% we're we're in the in the process of one one<00:18:12.640> of<00:18:12.730> the<00:18:12.790> first<00:18:13.270> applications<00:18:14.170> of 00:18:14.250 --> 00:18:14.260 align:start position:0% one of the first applications of 00:18:14.260 --> 00:18:16.620 align:start position:0% one of the first applications of true--but<00:18:15.040> is<00:18:15.250> going<00:18:15.460> to<00:18:15.550> be<00:18:15.640> the<00:18:15.820> the<00:18:16.120> Doge 00:18:16.620 --> 00:18:16.630 align:start position:0% true--but is going to be the the Doge 00:18:16.630 --> 00:18:21.690 align:start position:0% true--but is going to be the the Doge aetherium<00:18:17.080> bridge<00:18:17.290> and<00:18:19.320> we've<00:18:20.320> got<00:18:20.620> the<00:18:20.980> code 00:18:21.690 --> 00:18:21.700 align:start position:0% aetherium bridge and we've got the code 00:18:21.700 --> 00:18:23.370 align:start position:0% aetherium bridge and we've got the code ready<00:18:22.000> on<00:18:22.120> the<00:18:22.210> etherium<00:18:22.720> side<00:18:22.900> but<00:18:23.110> we<00:18:23.230> need 00:18:23.370 --> 00:18:23.380 align:start position:0% ready on the etherium side but we need 00:18:23.380 --> 00:18:24.990 align:start position:0% ready on the etherium side but we need to<00:18:23.440> reach<00:18:23.590> out<00:18:23.770> to<00:18:23.980> the<00:18:24.070> dogecoin<00:18:24.250> community 00:18:24.990 --> 00:18:25.000 align:start position:0% to reach out to the dogecoin community 00:18:25.000 --> 00:18:27.240 align:start position:0% to reach out to the dogecoin community and<00:18:25.180> get<00:18:25.720> them<00:18:25.900> to<00:18:26.140> put<00:18:26.500> in<00:18:26.620> the<00:18:26.710> new<00:18:26.830> opcode 00:18:27.240 --> 00:18:27.250 align:start position:0% and get them to put in the new opcode 00:18:27.250 --> 00:18:28.560 align:start position:0% and get them to put in the new opcode that<00:18:27.400> we<00:18:27.490> need<00:18:27.670> which<00:18:28.120> is<00:18:28.150> going<00:18:28.420> to<00:18:28.480> be 00:18:28.560 --> 00:18:28.570 align:start position:0% that we need which is going to be 00:18:28.570 --> 00:18:29.990 align:start position:0% that we need which is going to be something<00:18:28.780> that<00:18:28.960> allows<00:18:29.170> people<00:18:29.440> to<00:18:29.590> take 00:18:29.990 --> 00:18:30.000 align:start position:0% something that allows people to take 00:18:30.000 --> 00:18:33.450 align:start position:0% something that allows people to take dogecoin<00:18:31.000> off<00:18:31.180> the<00:18:31.800> dogecoin<00:18:32.800> network<00:18:33.280> and 00:18:33.450 --> 00:18:33.460 align:start position:0% dogecoin off the dogecoin network and 00:18:33.460 --> 00:18:34.890 align:start position:0% dogecoin off the dogecoin network and put<00:18:33.580> it<00:18:33.670> on<00:18:33.760> to<00:18:33.940> like<00:18:34.180> lock<00:18:34.540> it<00:18:34.720> on<00:18:34.810> the 00:18:34.890 --> 00:18:34.900 align:start position:0% put it on to like lock it on the 00:18:34.900 --> 00:18:36.570 align:start position:0% put it on to like lock it on the dogecoin<00:18:35.110> side<00:18:35.500> unlock<00:18:35.830> it<00:18:35.980> on<00:18:36.070> a<00:18:36.160> theory<00:18:36.460> I'm 00:18:36.570 --> 00:18:36.580 align:start position:0% dogecoin side unlock it on a theory I'm 00:18:36.580 --> 00:18:38.430 align:start position:0% dogecoin side unlock it on a theory I'm use<00:18:36.730> it<00:18:36.880> in<00:18:36.970> a<00:18:37.000> smart<00:18:37.210> contract<00:18:37.480> whatever<00:18:38.050> and 00:18:38.430 --> 00:18:38.440 align:start position:0% use it in a smart contract whatever and 00:18:38.440 --> 00:18:41.400 align:start position:0% use it in a smart contract whatever and then<00:18:39.090> lock<00:18:40.090> and<00:18:40.300> unlock<00:18:40.360> send<00:18:40.840> it<00:18:40.960> back<00:18:41.110> it's<00:18:41.320> a 00:18:41.400 --> 00:18:41.410 align:start position:0% then lock and unlock send it back it's a 00:18:41.410 --> 00:18:44.250 align:start position:0% then lock and unlock send it back it's a Doge<00:18:41.590> again<00:18:41.970> and<00:18:42.970> in<00:18:43.600> order<00:18:43.810> to<00:18:43.930> reach<00:18:44.080> out<00:18:44.230> to 00:18:44.250 --> 00:18:44.260 align:start position:0% Doge again and in order to reach out to 00:18:44.260 --> 00:18:45.720 align:start position:0% Doge again and in order to reach out to people<00:18:44.470> we're<00:18:44.740> doing<00:18:45.100> where<00:18:45.340> we<00:18:45.640> are 00:18:45.720 --> 00:18:45.730 align:start position:0% people we're doing where we are 00:18:45.730 --> 00:18:48.570 align:start position:0% people we're doing where we are instituting<00:18:46.120> a<00:18:46.390> new<00:18:46.570> public<00:18:47.320> art<00:18:47.500> project<00:18:48.010> so 00:18:48.570 --> 00:18:48.580 align:start position:0% instituting a new public art project so 00:18:48.580 --> 00:18:51.000 align:start position:0% instituting a new public art project so I'm<00:18:49.480> calling<00:18:49.750> everyone<00:18:50.080> who's<00:18:50.380> interested<00:18:50.560> in 00:18:51.000 --> 00:18:51.010 align:start position:0% I'm calling everyone who's interested in 00:18:51.010 --> 00:18:54.000 align:start position:0% I'm calling everyone who's interested in being<00:18:51.760> part<00:18:51.820> of<00:18:52.150> this<00:18:52.470> amazing<00:18:53.470> movement<00:18:53.650> this 00:18:54.000 --> 00:18:54.010 align:start position:0% being part of this amazing movement this 00:18:54.010 --> 00:18:55.980 align:start position:0% being part of this amazing movement this is<00:18:54.070> a<00:18:54.220> once-in-a-lifetime<00:18:54.700> opportunity<00:18:55.060> come 00:18:55.980 --> 00:18:55.990 align:start position:0% is a once-in-a-lifetime opportunity come 00:18:55.990 --> 00:18:58.620 align:start position:0% is a once-in-a-lifetime opportunity come talk<00:18:56.230> to<00:18:56.260> me<00:18:56.500> after<00:18:57.130> this<00:18:57.250> talk<00:18:57.520> where<00:18:58.360> as<00:18:58.510> I 00:18:58.620 --> 00:18:58.630 align:start position:0% talk to me after this talk where as I 00:18:58.630 --> 00:19:00.090 align:start position:0% talk to me after this talk where as I mentioned<00:18:58.930> earlier<00:18:59.170> we're<00:18:59.350> live<00:18:59.500> on<00:18:59.530> Cove<00:18:59.980> on 00:19:00.090 --> 00:19:00.100 align:start position:0% mentioned earlier we're live on Cove on 00:19:00.100 --> 00:19:04.170 align:start position:0% mentioned earlier we're live on Cove on test<00:19:00.370> net<00:19:00.580> and<00:19:01.770> all<00:19:02.770> of<00:19:02.890> our<00:19:03.040> code<00:19:03.490> is<00:19:03.670> up<00:19:03.820> on 00:19:04.170 --> 00:19:04.180 align:start position:0% test net and all of our code is up on 00:19:04.180 --> 00:19:06.780 align:start position:0% test net and all of our code is up on github<00:19:04.780> check<00:19:05.350> us<00:19:05.470> out<00:19:05.620> on<00:19:05.740> true--but<00:19:06.490> follow 00:19:06.780 --> 00:19:06.790 align:start position:0% github check us out on true--but follow 00:19:06.790 --> 00:19:08.790 align:start position:0% github check us out on true--but follow us<00:19:07.000> on<00:19:07.120> reddit<00:19:07.450> medium<00:19:07.780> github<00:19:08.140> Twitter<00:19:08.470> and 00:19:08.790 --> 00:19:08.800 align:start position:0% us on reddit medium github Twitter and 00:19:08.800 --> 00:19:21.410 align:start position:0% us on reddit medium github Twitter and Facebook<00:19:09.430> and<00:19:10.710> thanks<00:19:11.710> everybody 00:19:21.410 --> 00:19:21.420 align:start position:0% 00:19:21.420 --> 00:19:29.009 align:start position:0% [Music]