WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:03.710 align:start position:0% okay<00:00:00.840> so<00:00:00.900> thanks<00:00:01.380> a<00:00:01.469> lot<00:00:01.680> and<00:00:02.580> I'm<00:00:03.389> also<00:00:03.570> very 00:00:03.710 --> 00:00:03.720 align:start position:0% okay so thanks a lot and I'm also very 00:00:03.720 --> 00:00:05.720 align:start position:0% okay so thanks a lot and I'm also very excited<00:00:04.140> to<00:00:04.230> be<00:00:04.350> here<00:00:04.529> at<00:00:04.740> Def<00:00:05.250> Con<00:00:05.279> I<00:00:05.520> never 00:00:05.720 --> 00:00:05.730 align:start position:0% excited to be here at Def Con I never 00:00:05.730 --> 00:00:07.579 align:start position:0% excited to be here at Def Con I never was<00:00:06.000> was<00:00:06.600> here<00:00:06.810> although<00:00:07.080> I<00:00:07.109> had<00:00:07.259> several 00:00:07.579 --> 00:00:07.589 align:start position:0% was was here although I had several 00:00:07.589 --> 00:00:10.430 align:start position:0% was was here although I had several times<00:00:07.770> watch<00:00:08.040> the<00:00:08.189> videos<00:00:08.550> off<00:00:09.000> of<00:00:09.389> James<00:00:09.900> Otis 00:00:10.430 --> 00:00:10.440 align:start position:0% times watch the videos off of James Otis 00:00:10.440 --> 00:00:14.780 align:start position:0% times watch the videos off of James Otis area<00:00:10.800> so<00:00:12.500> so<00:00:13.500> this<00:00:13.679> talk<00:00:13.889> will<00:00:14.040> be<00:00:14.070> about<00:00:14.429> Tarun 00:00:14.780 --> 00:00:14.790 align:start position:0% area so so this talk will be about Tarun 00:00:14.790 --> 00:00:16.910 align:start position:0% area so so this talk will be about Tarun our<00:00:15.030> work<00:00:15.420> it's<00:00:15.990> like<00:00:16.199> a<00:00:16.230> joint<00:00:16.680> research 00:00:16.910 --> 00:00:16.920 align:start position:0% our work it's like a joint research 00:00:16.920 --> 00:00:20.029 align:start position:0% our work it's like a joint research project<00:00:17.100> between<00:00:17.730> the<00:00:18.980> Technical<00:00:19.980> University 00:00:20.029 --> 00:00:20.039 align:start position:0% project between the Technical University 00:00:20.039 --> 00:00:23.740 align:start position:0% project between the Technical University of<00:00:20.580> Darmstadt<00:00:20.970> in<00:00:21.150> Germany<00:00:21.539> and<00:00:21.720> the 00:00:23.740 --> 00:00:23.750 align:start position:0% of Darmstadt in Germany and the 00:00:23.750 --> 00:00:26.870 align:start position:0% of Darmstadt in Germany and the University<00:00:24.750> of<00:00:24.779> Warsaw<00:00:25.400> in<00:00:26.400> Poland<00:00:26.460> in 00:00:26.870 --> 00:00:26.880 align:start position:0% University of Warsaw in Poland in 00:00:26.880 --> 00:00:28.820 align:start position:0% University of Warsaw in Poland in several<00:00:27.210> of<00:00:27.390> my<00:00:27.420> co-authors<00:00:28.320> so<00:00:28.470> this<00:00:28.590> is<00:00:28.680> some 00:00:28.820 --> 00:00:28.830 align:start position:0% several of my co-authors so this is some 00:00:28.830 --> 00:00:30.710 align:start position:0% several of my co-authors so this is some kind<00:00:29.010> of<00:00:29.099> academic<00:00:29.490> work<00:00:29.849> so<00:00:30.330> we<00:00:30.510> published 00:00:30.710 --> 00:00:30.720 align:start position:0% kind of academic work so we published 00:00:30.720 --> 00:00:32.720 align:start position:0% kind of academic work so we published some<00:00:31.050> papers<00:00:31.080> at<00:00:31.470> some<00:00:31.590> top<00:00:31.740> conferences<00:00:32.340> in 00:00:32.720 --> 00:00:32.730 align:start position:0% some papers at some top conferences in 00:00:32.730 --> 00:00:35.060 align:start position:0% some papers at some top conferences in security<00:00:33.480> and<00:00:33.750> several<00:00:33.989> of<00:00:34.140> them<00:00:34.320> also<00:00:34.829> here 00:00:35.060 --> 00:00:35.070 align:start position:0% security and several of them also here 00:00:35.070 --> 00:00:37.280 align:start position:0% security and several of them also here sitting<00:00:35.700> there<00:00:35.940> over<00:00:36.329> there<00:00:36.450> and<00:00:36.899> here<00:00:37.140> in<00:00:37.200> the 00:00:37.280 --> 00:00:37.290 align:start position:0% sitting there over there and here in the 00:00:37.290 --> 00:00:39.860 align:start position:0% sitting there over there and here in the front<00:00:37.559> row<00:00:38.340> so<00:00:38.670> we<00:00:38.969> are<00:00:39.149> very<00:00:39.239> happy<00:00:39.480> to<00:00:39.629> answer 00:00:39.860 --> 00:00:39.870 align:start position:0% front row so we are very happy to answer 00:00:39.870 --> 00:00:43.040 align:start position:0% front row so we are very happy to answer questions<00:00:40.469> later<00:00:40.649> also<00:00:41.090> okay<00:00:42.090> so<00:00:42.149> as<00:00:42.750> we<00:00:42.960> have 00:00:43.040 --> 00:00:43.050 align:start position:0% questions later also okay so as we have 00:00:43.050 --> 00:00:45.290 align:start position:0% questions later also okay so as we have seen<00:00:43.230> already<00:00:43.410> today<00:00:44.100> several<00:00:44.700> talks<00:00:45.059> there 00:00:45.290 --> 00:00:45.300 align:start position:0% seen already today several talks there 00:00:45.300 --> 00:00:47.779 align:start position:0% seen already today several talks there are<00:00:45.390> many<00:00:46.140> exciting<00:00:46.770> projects<00:00:47.430> currently 00:00:47.779 --> 00:00:47.789 align:start position:0% are many exciting projects currently 00:00:47.789 --> 00:00:50.569 align:start position:0% are many exciting projects currently going<00:00:48.480> on<00:00:48.780> people<00:00:49.440> like<00:00:50.160> do<00:00:50.340> a<00:00:50.370> lot<00:00:50.550> of 00:00:50.569 --> 00:00:50.579 align:start position:0% going on people like do a lot of 00:00:50.579 --> 00:00:52.790 align:start position:0% going on people like do a lot of research<00:00:51.120> and<00:00:51.360> also<00:00:51.809> development<00:00:52.199> in 00:00:52.790 --> 00:00:52.800 align:start position:0% research and also development in 00:00:52.800 --> 00:00:55.459 align:start position:0% research and also development in building<00:00:53.670> different<00:00:54.239> types<00:00:54.480> of<00:00:54.780> state 00:00:55.459 --> 00:00:55.469 align:start position:0% building different types of state 00:00:55.469 --> 00:00:58.430 align:start position:0% building different types of state channel<00:00:55.860> and<00:00:56.070> payment<00:00:56.539> channel<00:00:57.539> networks<00:00:57.899> so 00:00:58.430 --> 00:00:58.440 align:start position:0% channel and payment channel networks so 00:00:58.440 --> 00:01:00.590 align:start position:0% channel and payment channel networks so I<00:00:58.469> would<00:00:58.680> like<00:00:58.829> to<00:00:58.980> explain<00:00:59.340> to<00:00:59.399> you<00:00:59.609> basically 00:01:00.590 --> 00:01:00.600 align:start position:0% I would like to explain to you basically 00:01:00.600 --> 00:01:03.889 align:start position:0% I would like to explain to you basically at<00:01:00.719> a<00:01:00.809> high<00:01:00.930> level<00:01:00.960> what<00:01:01.739> we<00:01:01.920> do<00:01:02.129> in<00:01:02.430> karoon<00:01:03.090> so 00:01:03.889 --> 00:01:03.899 align:start position:0% at a high level what we do in karoon so 00:01:03.899 --> 00:01:06.620 align:start position:0% at a high level what we do in karoon so in<00:01:04.860> Peru<00:01:05.070> essentially<00:01:05.729> the<00:01:05.850> goal<00:01:06.000> is<00:01:06.210> similar 00:01:06.620 --> 00:01:06.630 align:start position:0% in Peru essentially the goal is similar 00:01:06.630 --> 00:01:10.370 align:start position:0% in Peru essentially the goal is similar to<00:01:06.750> the<00:01:06.840> previous<00:01:07.170> two<00:01:07.770> talks<00:01:08.810> of<00:01:09.810> Moore<00:01:10.170> and 00:01:10.370 --> 00:01:10.380 align:start position:0% to the previous two talks of Moore and 00:01:10.380 --> 00:01:13.010 align:start position:0% to the previous two talks of Moore and Liam<00:01:10.680> we<00:01:11.280> are<00:01:11.369> trying<00:01:11.580> to<00:01:11.670> build<00:01:12.020> generalized 00:01:13.010 --> 00:01:13.020 align:start position:0% Liam we are trying to build generalized 00:01:13.020 --> 00:01:16.160 align:start position:0% Liam we are trying to build generalized state<00:01:13.590> channel<00:01:13.920> networks<00:01:14.310> and<00:01:14.670> I<00:01:15.450> will<00:01:15.600> talk 00:01:16.160 --> 00:01:16.170 align:start position:0% state channel networks and I will talk 00:01:16.170 --> 00:01:18.440 align:start position:0% state channel networks and I will talk in<00:01:16.200> a<00:01:16.409> moment<00:01:16.770> a<00:01:16.860> bit<00:01:17.040> in<00:01:17.280> more<00:01:17.700> detail<00:01:18.060> what<00:01:18.330> we 00:01:18.440 --> 00:01:18.450 align:start position:0% in a moment a bit in more detail what we 00:01:18.450 --> 00:01:19.969 align:start position:0% in a moment a bit in more detail what we understand<00:01:18.900> about<00:01:19.020> general<00:01:19.530> state<00:01:19.740> channel 00:01:19.969 --> 00:01:19.979 align:start position:0% understand about general state channel 00:01:19.979 --> 00:01:22.490 align:start position:0% understand about general state channel networks<00:01:20.630> the<00:01:21.630> main<00:01:21.840> technique<00:01:22.229> that<00:01:22.380> we 00:01:22.490 --> 00:01:22.500 align:start position:0% networks the main technique that we 00:01:22.500 --> 00:01:25.280 align:start position:0% networks the main technique that we developed<00:01:22.619> in<00:01:23.130> our<00:01:23.369> work<00:01:24.180> and<00:01:24.450> I'm<00:01:24.689> kind<00:01:25.259> of 00:01:25.280 --> 00:01:25.290 align:start position:0% developed in our work and I'm kind of 00:01:25.290 --> 00:01:27.080 align:start position:0% developed in our work and I'm kind of happy<00:01:25.439> that<00:01:25.680> nobody<00:01:25.860> so<00:01:26.340> far<00:01:26.369> talked<00:01:26.850> so<00:01:27.030> much 00:01:27.080 --> 00:01:27.090 align:start position:0% happy that nobody so far talked so much 00:01:27.090 --> 00:01:30.039 align:start position:0% happy that nobody so far talked so much about<00:01:27.210> this<00:01:27.720> is<00:01:28.290> about<00:01:28.680> virtual<00:01:29.340> Channel<00:01:29.700> so 00:01:30.039 --> 00:01:30.049 align:start position:0% about this is about virtual Channel so 00:01:30.049 --> 00:01:32.420 align:start position:0% about this is about virtual Channel so some<00:01:31.049> people<00:01:31.200> also<00:01:31.439> call<00:01:31.680> it<00:01:31.710> meta<00:01:31.979> channels 00:01:32.420 --> 00:01:32.430 align:start position:0% some people also call it meta channels 00:01:32.430 --> 00:01:34.940 align:start position:0% some people also call it meta channels and<00:01:32.610> I<00:01:33.390> will<00:01:33.540> explain<00:01:34.140> in<00:01:34.350> more<00:01:34.470> detail<00:01:34.530> what 00:01:34.940 --> 00:01:34.950 align:start position:0% and I will explain in more detail what 00:01:34.950 --> 00:01:36.679 align:start position:0% and I will explain in more detail what actually<00:01:35.310> are<00:01:35.400> virtual<00:01:35.729> channels<00:01:36.090> and<00:01:36.570> what 00:01:36.679 --> 00:01:36.689 align:start position:0% actually are virtual channels and what 00:01:36.689 --> 00:01:38.030 align:start position:0% actually are virtual channels and what are<00:01:36.780> the<00:01:36.840> advantages<00:01:36.930> of<00:01:37.409> these<00:01:37.710> virtual 00:01:38.030 --> 00:01:38.040 align:start position:0% are the advantages of these virtual 00:01:38.040 --> 00:01:40.039 align:start position:0% are the advantages of these virtual channels<00:01:38.430> and<00:01:38.729> the<00:01:39.270> special<00:01:39.659> feature<00:01:39.840> and 00:01:40.039 --> 00:01:40.049 align:start position:0% channels and the special feature and 00:01:40.049 --> 00:01:41.719 align:start position:0% channels and the special feature and maybe<00:01:40.200> this<00:01:40.380> is<00:01:40.500> also<00:01:40.650> one<00:01:40.920> distinctive 00:01:41.719 --> 00:01:41.729 align:start position:0% maybe this is also one distinctive 00:01:41.729 --> 00:01:43.819 align:start position:0% maybe this is also one distinctive feature<00:01:41.790> of<00:01:42.060> our<00:01:42.240> project<00:01:42.780> because<00:01:43.259> we<00:01:43.590> have 00:01:43.819 --> 00:01:43.829 align:start position:0% feature of our project because we have 00:01:43.829 --> 00:01:45.410 align:start position:0% feature of our project because we have like<00:01:44.009> a<00:01:44.070> very<00:01:44.640> strong<00:01:44.880> background<00:01:45.329> in 00:01:45.410 --> 00:01:45.420 align:start position:0% like a very strong background in 00:01:45.420 --> 00:01:48.050 align:start position:0% like a very strong background in cryptographic<00:01:45.780> research<00:01:46.320> we<00:01:47.159> focus<00:01:47.579> a<00:01:47.759> lot 00:01:48.050 --> 00:01:48.060 align:start position:0% cryptographic research we focus a lot 00:01:48.060 --> 00:01:49.760 align:start position:0% cryptographic research we focus a lot also<00:01:48.479> on<00:01:48.720> not<00:01:48.899> only<00:01:48.930> designing<00:01:49.649> these 00:01:49.760 --> 00:01:49.770 align:start position:0% also on not only designing these 00:01:49.770 --> 00:01:52.039 align:start position:0% also on not only designing these protocols<00:01:50.100> at<00:01:50.490> an<00:01:50.579> abstract<00:01:50.850> level<00:01:51.270> but<00:01:51.869> also 00:01:52.039 --> 00:01:52.049 align:start position:0% protocols at an abstract level but also 00:01:52.049 --> 00:01:53.600 align:start position:0% protocols at an abstract level but also proving<00:01:52.500> the<00:01:52.590> security<00:01:53.070> of<00:01:53.189> these<00:01:53.340> protocols 00:01:53.600 --> 00:01:53.610 align:start position:0% proving the security of these protocols 00:01:53.610 --> 00:01:56.959 align:start position:0% proving the security of these protocols okay<00:01:54.299> so<00:01:54.360> we<00:01:55.200> usually<00:01:55.470> when<00:01:56.369> we<00:01:56.490> come<00:01:56.700> up<00:01:56.820> with 00:01:56.959 --> 00:01:56.969 align:start position:0% okay so we usually when we come up with 00:01:56.969 --> 00:01:58.819 align:start position:0% okay so we usually when we come up with a<00:01:57.000> design<00:01:57.509> of<00:01:57.810> what<00:01:58.290> the<00:01:58.439> protocol<00:01:58.619> is 00:01:58.819 --> 00:01:58.829 align:start position:0% a design of what the protocol is 00:01:58.829 --> 00:02:01.340 align:start position:0% a design of what the protocol is specification<00:01:59.549> of<00:01:59.670> the<00:01:59.820> protocol<00:02:00.229> what<00:02:01.229> it 00:02:01.340 --> 00:02:01.350 align:start position:0% specification of the protocol what it 00:02:01.350 --> 00:02:04.370 align:start position:0% specification of the protocol what it what<00:02:01.710> it<00:02:01.740> what<00:02:02.549> it<00:02:02.579> is<00:02:02.820> then<00:02:03.390> we<00:02:03.600> also<00:02:03.840> usually 00:02:04.370 --> 00:02:04.380 align:start position:0% what it what it is then we also usually 00:02:04.380 --> 00:02:06.830 align:start position:0% what it what it is then we also usually carry<00:02:05.070> out<00:02:05.310> a<00:02:05.340> formal<00:02:05.820> security<00:02:06.090> proof<00:02:06.570> that 00:02:06.830 --> 00:02:06.840 align:start position:0% carry out a formal security proof that 00:02:06.840 --> 00:02:10.540 align:start position:0% carry out a formal security proof that it<00:02:06.990> satisfies<00:02:07.530> certain<00:02:08.190> security<00:02:08.940> guarantees 00:02:10.540 --> 00:02:10.550 align:start position:0% it satisfies certain security guarantees 00:02:10.550 --> 00:02:13.790 align:start position:0% it satisfies certain security guarantees so<00:02:11.550> what<00:02:11.670> is<00:02:11.790> the<00:02:11.910> state<00:02:12.390> channel<00:02:12.690> network 00:02:13.790 --> 00:02:13.800 align:start position:0% so what is the state channel network 00:02:13.800 --> 00:02:16.970 align:start position:0% so what is the state channel network I<00:02:14.000> will<00:02:15.000> essentially<00:02:15.630> show<00:02:16.020> you<00:02:16.080> our<00:02:16.470> view<00:02:16.860> at 00:02:16.970 --> 00:02:16.980 align:start position:0% I will essentially show you our view at 00:02:16.980 --> 00:02:20.300 align:start position:0% I will essentially show you our view at the<00:02:17.160> rune<00:02:17.370> of<00:02:17.580> what<00:02:18.390> this<00:02:18.570> is<00:02:18.810> the<00:02:19.710> basic 00:02:20.300 --> 00:02:20.310 align:start position:0% the rune of what this is the basic 00:02:20.310 --> 00:02:22.000 align:start position:0% the rune of what this is the basic ingredient<00:02:20.880> and<00:02:21.060> you<00:02:21.090> have<00:02:21.330> already<00:02:21.480> seen 00:02:22.000 --> 00:02:22.010 align:start position:0% ingredient and you have already seen 00:02:22.010 --> 00:02:25.730 align:start position:0% ingredient and you have already seen this<00:02:23.010> in<00:02:23.280> several<00:02:24.210> other<00:02:24.330> talks<00:02:24.690> we<00:02:25.320> call<00:02:25.560> them 00:02:25.730 --> 00:02:25.740 align:start position:0% this in several other talks we call them 00:02:25.740 --> 00:02:28.310 align:start position:0% this in several other talks we call them legislators<00:02:26.640> and<00:02:26.970> let<00:02:27.510> us<00:02:27.660> state<00:02:27.870> channels 00:02:28.310 --> 00:02:28.320 align:start position:0% legislators and let us state channels 00:02:28.320 --> 00:02:30.770 align:start position:0% legislators and let us state channels they<00:02:28.800> are<00:02:28.830> built<00:02:29.130> directly<00:02:29.370> over<00:02:30.150> the<00:02:30.570> ledger 00:02:30.770 --> 00:02:30.780 align:start position:0% they are built directly over the ledger 00:02:30.780 --> 00:02:32.510 align:start position:0% they are built directly over the ledger okay<00:02:31.230> so<00:02:31.320> that's<00:02:31.560> why<00:02:31.680> they<00:02:31.830> call<00:02:31.860> legislate 00:02:32.510 --> 00:02:32.520 align:start position:0% okay so that's why they call legislate 00:02:32.520 --> 00:02:35.240 align:start position:0% okay so that's why they call legislate channels<00:02:33.320> so<00:02:34.320> we<00:02:34.350> have<00:02:34.680> these<00:02:34.830> two<00:02:34.980> parties 00:02:35.240 --> 00:02:35.250 align:start position:0% channels so we have these two parties 00:02:35.250 --> 00:02:36.950 align:start position:0% channels so we have these two parties Alice<00:02:35.520> and<00:02:35.640> Bob<00:02:35.760> and<00:02:35.940> they<00:02:36.420> want<00:02:36.720> for<00:02:36.930> example 00:02:36.950 --> 00:02:36.960 align:start position:0% Alice and Bob and they want for example 00:02:36.960 --> 00:02:40.190 align:start position:0% Alice and Bob and they want for example to<00:02:37.410> execute<00:02:38.040> some<00:02:38.880> contract<00:02:39.390> off<00:02:39.570> chain<00:02:39.900> for 00:02:40.190 --> 00:02:40.200 align:start position:0% to execute some contract off chain for 00:02:40.200 --> 00:02:42.650 align:start position:0% to execute some contract off chain for example<00:02:40.230> it<00:02:40.620> could<00:02:40.770> be<00:02:40.950> some<00:02:41.220> chess<00:02:41.940> game<00:02:42.300> or 00:02:42.650 --> 00:02:42.660 align:start position:0% example it could be some chess game or 00:02:42.660 --> 00:02:46.580 align:start position:0% example it could be some chess game or some<00:02:43.200> other<00:02:44.300> online<00:02:45.300> game<00:02:45.750> or<00:02:46.050> a<00:02:46.080> payment<00:02:46.500> or 00:02:46.580 --> 00:02:46.590 align:start position:0% some other online game or a payment or 00:02:46.590 --> 00:02:49.370 align:start position:0% some other online game or a payment or whatever<00:02:46.890> and<00:02:47.510> the<00:02:48.510> letter<00:02:48.690> state<00:02:49.020> channel 00:02:49.370 --> 00:02:49.380 align:start position:0% whatever and the letter state channel 00:02:49.380 --> 00:02:51.560 align:start position:0% whatever and the letter state channel then<00:02:50.040> works<00:02:50.430> in<00:02:50.610> three<00:02:50.790> phases<00:02:51.000> so<00:02:51.330> in<00:02:51.450> the 00:02:51.560 --> 00:02:51.570 align:start position:0% then works in three phases so in the 00:02:51.570 --> 00:02:54.830 align:start position:0% then works in three phases so in the first<00:02:51.810> phase<00:02:52.050> the<00:02:53.330> party's<00:02:54.330> Alice<00:02:54.570> and<00:02:54.690> Bob 00:02:54.830 --> 00:02:54.840 align:start position:0% first phase the party's Alice and Bob 00:02:54.840 --> 00:02:56.780 align:start position:0% first phase the party's Alice and Bob they<00:02:55.380> have<00:02:55.530> to<00:02:55.740> go<00:02:56.100> to<00:02:56.160> the<00:02:56.370> blockchain<00:02:56.580> and 00:02:56.780 --> 00:02:56.790 align:start position:0% they have to go to the blockchain and 00:02:56.790 --> 00:02:59.960 align:start position:0% they have to go to the blockchain and create<00:02:57.210> this<00:02:57.390> legislature<00:02:58.110> and<00:02:58.610> help<00:02:59.610> this<00:02:59.820> is 00:02:59.960 --> 00:02:59.970 align:start position:0% create this legislature and help this is 00:02:59.970 --> 00:03:01.100 align:start position:0% create this legislature and help this is happening<00:03:00.300> with<00:03:00.450> some<00:03:00.570> kind<00:03:00.750> of<00:03:00.810> cryptography 00:03:01.100 --> 00:03:01.110 align:start position:0% happening with some kind of cryptography 00:03:01.110 --> 00:03:03.110 align:start position:0% happening with some kind of cryptography like<00:03:01.620> signatures<00:03:02.070> are<00:03:02.250> exchanged<00:03:02.730> and<00:03:02.880> so<00:03:02.970> on 00:03:03.110 --> 00:03:03.120 align:start position:0% like signatures are exchanged and so on 00:03:03.120 --> 00:03:05.690 align:start position:0% like signatures are exchanged and so on and<00:03:03.300> then<00:03:03.660> at<00:03:03.780> the<00:03:03.900> end<00:03:04.310> parties<00:03:05.310> Alice<00:03:05.550> and 00:03:05.690 --> 00:03:05.700 align:start position:0% and then at the end parties Alice and 00:03:05.700 --> 00:03:07.760 align:start position:0% and then at the end parties Alice and Bob<00:03:05.850> don't<00:03:06.690> have<00:03:06.870> a<00:03:06.900> pointer<00:03:07.230> here<00:03:07.380> Alice<00:03:07.620> and 00:03:07.760 --> 00:03:07.770 align:start position:0% Bob don't have a pointer here Alice and 00:03:07.770 --> 00:03:10.460 align:start position:0% Bob don't have a pointer here Alice and Bob<00:03:07.890> they<00:03:08.370> can<00:03:08.610> like<00:03:08.880> go<00:03:09.090> to<00:03:09.150> the<00:03:09.540> send 00:03:10.460 --> 00:03:10.470 align:start position:0% Bob they can like go to the send 00:03:10.470 --> 00:03:12.170 align:start position:0% Bob they can like go to the send something<00:03:10.650> to<00:03:10.890> the<00:03:10.980> blockchain<00:03:11.190> and<00:03:11.460> deploy 00:03:12.170 --> 00:03:12.180 align:start position:0% something to the blockchain and deploy 00:03:12.180 --> 00:03:14.270 align:start position:0% something to the blockchain and deploy some<00:03:12.540> channel<00:03:12.900> contract<00:03:13.350> which<00:03:13.800> is<00:03:13.980> later<00:03:14.160> on 00:03:14.270 --> 00:03:14.280 align:start position:0% some channel contract which is later on 00:03:14.280 --> 00:03:16.340 align:start position:0% some channel contract which is later on going<00:03:14.640> to<00:03:14.820> be<00:03:14.940> used<00:03:15.150> potentially<00:03:15.780> if<00:03:16.020> there 00:03:16.340 --> 00:03:16.350 align:start position:0% going to be used potentially if there 00:03:16.350 --> 00:03:17.450 align:start position:0% going to be used potentially if there are<00:03:16.410> some<00:03:16.590> disagreements<00:03:17.160> between<00:03:17.280> the 00:03:17.450 --> 00:03:17.460 align:start position:0% are some disagreements between the 00:03:17.460 --> 00:03:18.020 align:start position:0% are some disagreements between the parties 00:03:18.020 --> 00:03:18.030 align:start position:0% parties 00:03:18.030 --> 00:03:21.980 align:start position:0% parties so<00:03:18.720> once<00:03:18.990> the<00:03:19.590> letter<00:03:20.460> state<00:03:20.850> channel<00:03:21.240> has 00:03:21.980 --> 00:03:21.990 align:start position:0% so once the letter state channel has 00:03:21.990 --> 00:03:24.080 align:start position:0% so once the letter state channel has been<00:03:22.020> deployed<00:03:22.650> so<00:03:22.890> it's<00:03:23.010> established<00:03:23.580> the 00:03:24.080 --> 00:03:24.090 align:start position:0% been deployed so it's established the 00:03:24.090 --> 00:03:26.600 align:start position:0% been deployed so it's established the parties<00:03:24.450> can<00:03:24.630> then<00:03:24.870> like<00:03:25.200> execute<00:03:26.130> contracts 00:03:26.600 --> 00:03:26.610 align:start position:0% parties can then like execute contracts 00:03:26.610 --> 00:03:28.040 align:start position:0% parties can then like execute contracts of<00:03:26.760> chain<00:03:27.030> so<00:03:27.180> this<00:03:27.300> is<00:03:27.390> the<00:03:27.480> whole<00:03:27.600> purpose<00:03:27.780> of 00:03:28.040 --> 00:03:28.050 align:start position:0% of chain so this is the whole purpose of 00:03:28.050 --> 00:03:30.800 align:start position:0% of chain so this is the whole purpose of course<00:03:28.260> so<00:03:28.470> they<00:03:28.920> can<00:03:29.130> like<00:03:29.340> for<00:03:29.610> example<00:03:30.060> run 00:03:30.800 --> 00:03:30.810 align:start position:0% course so they can like for example run 00:03:30.810 --> 00:03:33.050 align:start position:0% course so they can like for example run multiple<00:03:31.190> execution<00:03:32.190> of<00:03:32.400> a<00:03:32.520> chess<00:03:32.760> game 00:03:33.050 --> 00:03:33.060 align:start position:0% multiple execution of a chess game 00:03:33.060 --> 00:03:35.740 align:start position:0% multiple execution of a chess game without<00:03:33.840> ever<00:03:34.080> touching<00:03:34.290> the<00:03:34.590> blockchain<00:03:34.830> and 00:03:35.740 --> 00:03:35.750 align:start position:0% without ever touching the blockchain and 00:03:35.750 --> 00:03:38.570 align:start position:0% without ever touching the blockchain and s<00:03:36.750> like<00:03:37.140> Liam<00:03:37.530> mentioned<00:03:37.860> earlier<00:03:38.130> so<00:03:38.280> we<00:03:38.400> also 00:03:38.570 --> 00:03:38.580 align:start position:0% s like Liam mentioned earlier so we also 00:03:38.580 --> 00:03:41.330 align:start position:0% s like Liam mentioned earlier so we also support<00:03:39.540> like<00:03:39.780> this<00:03:39.990> generalized<00:03:40.590> state 00:03:41.330 --> 00:03:41.340 align:start position:0% support like this generalized state 00:03:41.340 --> 00:03:42.800 align:start position:0% support like this generalized state channels<00:03:41.700> where<00:03:41.910> you<00:03:41.940> can<00:03:42.150> not<00:03:42.270> only<00:03:42.420> run<00:03:42.780> a 00:03:42.800 --> 00:03:42.810 align:start position:0% channels where you can not only run a 00:03:42.810 --> 00:03:45.470 align:start position:0% channels where you can not only run a chess<00:03:43.200> contract<00:03:43.680> but<00:03:43.830> you<00:03:43.890> could<00:03:44.130> run<00:03:44.480> several 00:03:45.470 --> 00:03:45.480 align:start position:0% chess contract but you could run several 00:03:45.480 --> 00:03:47.210 align:start position:0% chess contract but you could run several chess<00:03:45.780> contracts<00:03:46.230> or<00:03:46.380> like<00:03:46.590> even<00:03:46.710> completely 00:03:47.210 --> 00:03:47.220 align:start position:0% chess contracts or like even completely 00:03:47.220 --> 00:03:50.570 align:start position:0% chess contracts or like even completely other<00:03:47.370> games<00:03:47.670> also<00:03:48.660> in<00:03:48.990> this<00:03:49.140> in<00:03:49.530> this<00:03:49.860> in<00:03:50.400> this 00:03:50.570 --> 00:03:50.580 align:start position:0% other games also in this in this in this 00:03:50.580 --> 00:03:53.690 align:start position:0% other games also in this in this in this legislature<00:03:51.450> and<00:03:51.920> the<00:03:52.920> main<00:03:53.100> point<00:03:53.340> here<00:03:53.550> is 00:03:53.690 --> 00:03:53.700 align:start position:0% legislature and the main point here is 00:03:53.700 --> 00:03:56.210 align:start position:0% legislature and the main point here is that<00:03:53.730> as<00:03:54.540> you<00:03:54.690> can<00:03:54.810> see<00:03:54.870> that<00:03:55.320> this<00:03:55.590> execution 00:03:56.210 --> 00:03:56.220 align:start position:0% that as you can see that this execution 00:03:56.220 --> 00:03:58.730 align:start position:0% that as you can see that this execution of<00:03:56.310> contracts<00:03:56.850> so<00:03:57.570> this<00:03:57.720> update<00:03:58.140> of<00:03:58.320> the<00:03:58.470> state 00:03:58.730 --> 00:03:58.740 align:start position:0% of contracts so this update of the state 00:03:58.740 --> 00:04:02.210 align:start position:0% of contracts so this update of the state this<00:03:59.990> is<00:04:00.990> carried<00:04:01.500> out<00:04:01.590> of<00:04:01.830> jail 00:04:02.210 --> 00:04:02.220 align:start position:0% this is carried out of jail 00:04:02.220 --> 00:04:05.060 align:start position:0% this is carried out of jail so<00:04:02.370> it's<00:04:02.580> carried<00:04:03.210> out<00:04:03.390> without<00:04:04.230> Alice<00:04:04.890> and 00:04:05.060 --> 00:04:05.070 align:start position:0% so it's carried out without Alice and 00:04:05.070 --> 00:04:06.710 align:start position:0% so it's carried out without Alice and Bob<00:04:05.250> needing<00:04:05.640> to<00:04:05.760> interact<00:04:06.210> with<00:04:06.570> the 00:04:06.710 --> 00:04:06.720 align:start position:0% Bob needing to interact with the 00:04:06.720 --> 00:04:09.590 align:start position:0% Bob needing to interact with the blockchain<00:04:07.640> so<00:04:08.640> then<00:04:08.880> at<00:04:09.000> some<00:04:09.150> point<00:04:09.180> when 00:04:09.590 --> 00:04:09.600 align:start position:0% blockchain so then at some point when 00:04:09.600 --> 00:04:11.240 align:start position:0% blockchain so then at some point when Alice<00:04:09.959> and<00:04:10.200> Bob<00:04:10.560> they<00:04:10.709> don't<00:04:10.890> want<00:04:11.040> to<00:04:11.100> use 00:04:11.240 --> 00:04:11.250 align:start position:0% Alice and Bob they don't want to use 00:04:11.250 --> 00:04:13.430 align:start position:0% Alice and Bob they don't want to use anymore<00:04:11.550> this<00:04:11.870> legislature<00:04:12.870> state<00:04:13.140> channel 00:04:13.430 --> 00:04:13.440 align:start position:0% anymore this legislature state channel 00:04:13.440 --> 00:04:16.220 align:start position:0% anymore this legislature state channel then<00:04:13.620> they<00:04:13.740> can<00:04:14.030> settle<00:04:15.030> this<00:04:15.209> channel<00:04:15.900> and<00:04:16.080> go 00:04:16.220 --> 00:04:16.230 align:start position:0% then they can settle this channel and go 00:04:16.230 --> 00:04:18.440 align:start position:0% then they can settle this channel and go to<00:04:16.290> the<00:04:16.560> blockchain<00:04:16.770> close<00:04:17.640> it<00:04:17.880> and<00:04:18.090> this 00:04:18.440 --> 00:04:18.450 align:start position:0% to the blockchain close it and this 00:04:18.450 --> 00:04:21.349 align:start position:0% to the blockchain close it and this again<00:04:18.720> requires<00:04:19.530> unchain<00:04:20.359> communication 00:04:21.349 --> 00:04:21.359 align:start position:0% again requires unchain communication 00:04:21.359 --> 00:04:23.810 align:start position:0% again requires unchain communication okay<00:04:21.960> so<00:04:22.020> this<00:04:22.770> is<00:04:22.950> essentially<00:04:23.490> the<00:04:23.610> three 00:04:23.810 --> 00:04:23.820 align:start position:0% okay so this is essentially the three 00:04:23.820 --> 00:04:26.990 align:start position:0% okay so this is essentially the three phases<00:04:24.240> of<00:04:24.390> a<00:04:24.780> basic<00:04:25.140> state 00:04:26.990 --> 00:04:27.000 align:start position:0% phases of a basic state 00:04:27.000 --> 00:04:29.340 align:start position:0% phases of a basic state now<00:04:28.000> we<00:04:28.060> would<00:04:28.240> like<00:04:28.360> to<00:04:28.419> extend<00:04:28.750> this<00:04:28.960> to 00:04:29.340 --> 00:04:29.350 align:start position:0% now we would like to extend this to 00:04:29.350 --> 00:04:32.100 align:start position:0% now we would like to extend this to forming<00:04:30.160> a<00:04:30.190> network<00:04:30.340> so<00:04:30.880> this<00:04:31.030> is<00:04:31.150> the<00:04:31.360> most 00:04:32.100 --> 00:04:32.110 align:start position:0% forming a network so this is the most 00:04:32.110 --> 00:04:34.379 align:start position:0% forming a network so this is the most simple<00:04:32.590> network<00:04:32.919> that<00:04:33.460> you<00:04:33.610> can<00:04:33.790> think<00:04:34.030> of<00:04:34.150> you 00:04:34.379 --> 00:04:34.389 align:start position:0% simple network that you can think of you 00:04:34.389 --> 00:04:36.270 align:start position:0% simple network that you can think of you have<00:04:34.540> like<00:04:34.750> LS<00:04:35.110> ingress<00:04:35.500> and<00:04:35.530> Bob<00:04:35.830> Ellis<00:04:36.160> is 00:04:36.270 --> 00:04:36.280 align:start position:0% have like LS ingress and Bob Ellis is 00:04:36.280 --> 00:04:38.460 align:start position:0% have like LS ingress and Bob Ellis is connected<00:04:36.729> to<00:04:36.940> Ingrid<00:04:37.570> by<00:04:37.810> a<00:04:37.840> letter<00:04:38.169> state 00:04:38.460 --> 00:04:38.470 align:start position:0% connected to Ingrid by a letter state 00:04:38.470 --> 00:04:40.920 align:start position:0% connected to Ingrid by a letter state channel<00:04:38.830> and<00:04:39.010> Ingrid<00:04:39.729> is<00:04:39.880> connected<00:04:40.389> to<00:04:40.750> both 00:04:40.920 --> 00:04:40.930 align:start position:0% channel and Ingrid is connected to both 00:04:40.930 --> 00:04:44.520 align:start position:0% channel and Ingrid is connected to both via<00:04:41.260> a<00:04:41.350> letter<00:04:41.500> State<00:04:41.889> Channel<00:04:42.190> and<00:04:42.370> now<00:04:43.530> what 00:04:44.520 --> 00:04:44.530 align:start position:0% via a letter State Channel and now what 00:04:44.530 --> 00:04:46.590 align:start position:0% via a letter State Channel and now what Ellis<00:04:45.070> wants<00:04:45.190> to<00:04:45.400> do<00:04:45.580> is<00:04:45.850> she<00:04:46.210> wants<00:04:46.479> to 00:04:46.590 --> 00:04:46.600 align:start position:0% Ellis wants to do is she wants to 00:04:46.600 --> 00:04:49.620 align:start position:0% Ellis wants to do is she wants to execute<00:04:46.960> off<00:04:47.410> chain<00:04:47.889> a<00:04:48.210> contract<00:04:49.210> with<00:04:49.419> Bob 00:04:49.620 --> 00:04:49.630 align:start position:0% execute off chain a contract with Bob 00:04:49.630 --> 00:04:53.340 align:start position:0% execute off chain a contract with Bob okay<00:04:50.530> so<00:04:50.590> how<00:04:51.100> can<00:04:51.340> she<00:04:51.370> do<00:04:51.699> this<00:04:52.290> there<00:04:53.290> are 00:04:53.340 --> 00:04:53.350 align:start position:0% okay so how can she do this there are 00:04:53.350 --> 00:04:55.860 align:start position:0% okay so how can she do this there are several<00:04:53.680> options<00:04:54.030> to<00:04:55.030> achieve<00:04:55.150> this<00:04:55.540> the 00:04:55.860 --> 00:04:55.870 align:start position:0% several options to achieve this the 00:04:55.870 --> 00:04:58.110 align:start position:0% several options to achieve this the first<00:04:56.139> option<00:04:56.560> would<00:04:56.680> be<00:04:56.889> of<00:04:57.070> course<00:04:57.250> we<00:04:58.090> just 00:04:58.110 --> 00:04:58.120 align:start position:0% first option would be of course we just 00:04:58.120 --> 00:05:00.120 align:start position:0% first option would be of course we just have<00:04:58.479> seen<00:04:58.720> like<00:04:59.050> legislate<00:04:59.650> channels<00:04:59.979> so<00:05:00.100> we 00:05:00.120 --> 00:05:00.130 align:start position:0% have seen like legislate channels so we 00:05:00.130 --> 00:05:01.830 align:start position:0% have seen like legislate channels so we could<00:05:00.400> just<00:05:00.610> use<00:05:00.880> this<00:05:01.060> okay<00:05:01.360> so<00:05:01.419> we<00:05:01.690> could 00:05:01.830 --> 00:05:01.840 align:start position:0% could just use this okay so we could 00:05:01.840 --> 00:05:04.500 align:start position:0% could just use this okay so we could just<00:05:02.280> create<00:05:03.280> a<00:05:03.310> new<00:05:03.610> letter<00:05:03.850> state<00:05:04.210> channel 00:05:04.500 --> 00:05:04.510 align:start position:0% just create a new letter state channel 00:05:04.510 --> 00:05:06.689 align:start position:0% just create a new letter state channel between<00:05:04.780> Alice<00:05:05.020> and<00:05:05.050> Bob<00:05:05.430> but<00:05:06.430> this<00:05:06.550> of<00:05:06.669> course 00:05:06.689 --> 00:05:06.699 align:start position:0% between Alice and Bob but this of course 00:05:06.699 --> 00:05:09.240 align:start position:0% between Alice and Bob but this of course has<00:05:06.940> some<00:05:07.060> disadvantages<00:05:07.270> because<00:05:08.080> as<00:05:08.860> you 00:05:09.240 --> 00:05:09.250 align:start position:0% has some disadvantages because as you 00:05:09.250 --> 00:05:11.969 align:start position:0% has some disadvantages because as you saw<00:05:09.460> like<00:05:09.729> creating<00:05:10.210> a<00:05:10.300> channel<00:05:10.740> let<00:05:11.740> us<00:05:11.889> say 00:05:11.969 --> 00:05:11.979 align:start position:0% saw like creating a channel let us say 00:05:11.979 --> 00:05:13.469 align:start position:0% saw like creating a channel let us say channel<00:05:12.280> this<00:05:12.400> requires<00:05:12.789> interaction<00:05:13.360> with 00:05:13.469 --> 00:05:13.479 align:start position:0% channel this requires interaction with 00:05:13.479 --> 00:05:15.300 align:start position:0% channel this requires interaction with the<00:05:13.570> blockchain<00:05:13.780> so<00:05:14.199> I<00:05:14.229> need<00:05:14.590> to<00:05:14.740> communicate 00:05:15.300 --> 00:05:15.310 align:start position:0% the blockchain so I need to communicate 00:05:15.310 --> 00:05:17.820 align:start position:0% the blockchain so I need to communicate to<00:05:15.910> the<00:05:16.030> ledger<00:05:16.240> deploy<00:05:17.050> it<00:05:17.169> as<00:05:17.260> contracts 00:05:17.820 --> 00:05:17.830 align:start position:0% to the ledger deploy it as contracts 00:05:17.830 --> 00:05:20.460 align:start position:0% to the ledger deploy it as contracts this<00:05:17.949> is<00:05:18.130> slow<00:05:18.370> so<00:05:19.330> it<00:05:19.419> takes<00:05:19.600> some<00:05:19.720> time<00:05:19.930> it<00:05:20.199> is 00:05:20.460 --> 00:05:20.470 align:start position:0% this is slow so it takes some time it is 00:05:20.470 --> 00:05:22.560 align:start position:0% this is slow so it takes some time it is also<00:05:20.680> expensive<00:05:21.100> because<00:05:21.760> like<00:05:22.000> deploying<00:05:22.479> a 00:05:22.560 --> 00:05:22.570 align:start position:0% also expensive because like deploying a 00:05:22.570 --> 00:05:24.810 align:start position:0% also expensive because like deploying a contract<00:05:22.960> takes<00:05:23.169> cost<00:05:23.710> a<00:05:23.800> lot<00:05:23.919> of<00:05:24.039> fees<00:05:24.220> so<00:05:24.729> you 00:05:24.810 --> 00:05:24.820 align:start position:0% contract takes cost a lot of fees so you 00:05:24.820 --> 00:05:27.210 align:start position:0% contract takes cost a lot of fees so you would<00:05:24.940> like<00:05:25.090> to<00:05:25.240> avoid<00:05:25.330> this<00:05:26.039> so<00:05:27.039> another 00:05:27.210 --> 00:05:27.220 align:start position:0% would like to avoid this so another 00:05:27.220 --> 00:05:29.010 align:start position:0% would like to avoid this so another option<00:05:27.280> is<00:05:27.639> because<00:05:27.970> we<00:05:28.300> have<00:05:28.479> these<00:05:28.690> two 00:05:29.010 --> 00:05:29.020 align:start position:0% option is because we have these two 00:05:29.020 --> 00:05:31.200 align:start position:0% option is because we have these two channels<00:05:29.320> between<00:05:29.650> LS<00:05:30.130> English<00:05:30.880> and<00:05:31.090> English 00:05:31.200 --> 00:05:31.210 align:start position:0% channels between LS English and English 00:05:31.210 --> 00:05:32.969 align:start position:0% channels between LS English and English and<00:05:31.479> Bob<00:05:31.599> we<00:05:31.870> could<00:05:32.020> use<00:05:32.229> this<00:05:32.470> existing 00:05:32.969 --> 00:05:32.979 align:start position:0% and Bob we could use this existing 00:05:32.979 --> 00:05:35.850 align:start position:0% and Bob we could use this existing infrastructure<00:05:33.599> to<00:05:34.599> let<00:05:35.020> Alice<00:05:35.500> and<00:05:35.680> Bob 00:05:35.850 --> 00:05:35.860 align:start position:0% infrastructure to let Alice and Bob 00:05:35.860 --> 00:05:38.580 align:start position:0% infrastructure to let Alice and Bob directly<00:05:36.430> execute<00:05:37.110> contracts<00:05:38.110> between<00:05:38.260> them 00:05:38.580 --> 00:05:38.590 align:start position:0% directly execute contracts between them 00:05:38.590 --> 00:05:40.409 align:start position:0% directly execute contracts between them by<00:05:38.919> using<00:05:39.099> these<00:05:39.550> two<00:05:39.849> underlying 00:05:40.409 --> 00:05:40.419 align:start position:0% by using these two underlying 00:05:40.419 --> 00:05:43.050 align:start position:0% by using these two underlying legislators<00:05:41.289> okay<00:05:41.979> so<00:05:42.039> and<00:05:42.460> this<00:05:42.820> is<00:05:42.940> of 00:05:43.050 --> 00:05:43.060 align:start position:0% legislators okay so and this is of 00:05:43.060 --> 00:05:44.550 align:start position:0% legislators okay so and this is of course<00:05:43.090> the<00:05:43.360> advantage<00:05:43.750> that<00:05:43.810> this<00:05:44.080> can<00:05:44.410> be 00:05:44.550 --> 00:05:44.560 align:start position:0% course the advantage that this can be 00:05:44.560 --> 00:05:46.320 align:start position:0% course the advantage that this can be fast<00:05:44.830> if<00:05:45.099> we<00:05:45.340> manage<00:05:45.639> to<00:05:45.669> design<00:05:46.030> such<00:05:46.240> a 00:05:46.320 --> 00:05:46.330 align:start position:0% fast if we manage to design such a 00:05:46.330 --> 00:05:48.270 align:start position:0% fast if we manage to design such a protocol<00:05:46.690> can<00:05:46.990> be<00:05:47.110> fast<00:05:47.349> it<00:05:47.740> can<00:05:47.919> also<00:05:48.070> be 00:05:48.270 --> 00:05:48.280 align:start position:0% protocol can be fast it can also be 00:05:48.280 --> 00:05:50.839 align:start position:0% protocol can be fast it can also be cheap<00:05:48.520> because<00:05:48.880> it<00:05:49.630> does<00:05:49.810> not<00:05:49.990> require<00:05:50.200> any 00:05:50.839 --> 00:05:50.849 align:start position:0% cheap because it does not require any 00:05:50.849 --> 00:05:53.510 align:start position:0% cheap because it does not require any communication<00:05:51.849> with<00:05:52.300> the<00:05:52.450> underlying<00:05:52.840> ledger 00:05:53.510 --> 00:05:53.520 align:start position:0% communication with the underlying ledger 00:05:53.520 --> 00:05:55.890 align:start position:0% communication with the underlying ledger and<00:05:54.520> this<00:05:54.700> is<00:05:54.820> essentially<00:05:55.240> what<00:05:55.360> we<00:05:55.419> do<00:05:55.660> in 00:05:55.890 --> 00:05:55.900 align:start position:0% and this is essentially what we do in 00:05:55.900 --> 00:05:56.640 align:start position:0% and this is essentially what we do in Peru 00:05:56.640 --> 00:05:56.650 align:start position:0% Peru 00:05:56.650 --> 00:05:58.890 align:start position:0% Peru so<00:05:56.979> we<00:05:57.490> developed<00:05:58.150> a<00:05:58.210> technique<00:05:58.449> that<00:05:58.510> we<00:05:58.750> call 00:05:58.890 --> 00:05:58.900 align:start position:0% so we developed a technique that we call 00:05:58.900 --> 00:06:02.120 align:start position:0% so we developed a technique that we call virtual<00:05:59.349> channels<00:06:00.130> and<00:06:00.849> the<00:06:01.000> main<00:06:01.210> idea<00:06:01.780> is 00:06:02.120 --> 00:06:02.130 align:start position:0% virtual channels and the main idea is 00:06:02.130 --> 00:06:05.189 align:start position:0% virtual channels and the main idea is you<00:06:03.130> can<00:06:03.310> think<00:06:03.520> of<00:06:03.669> these<00:06:03.880> underlying<00:06:04.780> let's 00:06:05.189 --> 00:06:05.199 align:start position:0% you can think of these underlying let's 00:06:05.199 --> 00:06:07.770 align:start position:0% you can think of these underlying let's just<00:06:05.349> state<00:06:05.500> channels<00:06:05.889> as<00:06:06.180> like<00:06:07.180> a<00:06:07.210> two-party 00:06:07.770 --> 00:06:07.780 align:start position:0% just state channels as like a two-party 00:06:07.780 --> 00:06:10.200 align:start position:0% just state channels as like a two-party blockchain<00:06:08.199> okay<00:06:08.889> so<00:06:08.949> let's<00:06:09.910> just<00:06:09.970> state 00:06:10.200 --> 00:06:10.210 align:start position:0% blockchain okay so let's just state 00:06:10.210 --> 00:06:11.879 align:start position:0% blockchain okay so let's just state channels<00:06:10.570> between<00:06:10.720> Alice<00:06:11.169> and<00:06:11.289> Ingrid<00:06:11.680> and 00:06:11.879 --> 00:06:11.889 align:start position:0% channels between Alice and Ingrid and 00:06:11.889 --> 00:06:14.189 align:start position:0% channels between Alice and Ingrid and the<00:06:12.729> letter<00:06:12.910> state<00:06:13.150> channel<00:06:13.419> between<00:06:13.539> Ingrid 00:06:14.189 --> 00:06:14.199 align:start position:0% the letter state channel between Ingrid 00:06:14.199 --> 00:06:17.939 align:start position:0% the letter state channel between Ingrid and<00:06:14.289> Bob<00:06:14.940> they<00:06:15.940> offer<00:06:16.150> you<00:06:16.419> something<00:06:17.349> similar 00:06:17.939 --> 00:06:17.949 align:start position:0% and Bob they offer you something similar 00:06:17.949 --> 00:06:21.150 align:start position:0% and Bob they offer you something similar to<00:06:18.190> what<00:06:18.220> the<00:06:18.760> blockchain<00:06:18.970> offers<00:06:19.419> you<00:06:19.740> so<00:06:20.740> how 00:06:21.150 --> 00:06:21.160 align:start position:0% to what the blockchain offers you so how 00:06:21.160 --> 00:06:24.029 align:start position:0% to what the blockchain offers you so how can<00:06:21.389> we<00:06:22.389> now<00:06:22.599> create<00:06:22.990> a<00:06:23.349> virtual<00:06:23.830> state 00:06:24.029 --> 00:06:24.039 align:start position:0% can we now create a virtual state 00:06:24.039 --> 00:06:26.100 align:start position:0% can we now create a virtual state Channel<00:06:24.400> so<00:06:24.610> essentially<00:06:25.210> also<00:06:25.449> this<00:06:25.780> works 00:06:26.100 --> 00:06:26.110 align:start position:0% Channel so essentially also this works 00:06:26.110 --> 00:06:28.740 align:start position:0% Channel so essentially also this works in<00:06:26.320> three<00:06:26.560> phases<00:06:26.820> in<00:06:27.820> the<00:06:27.940> first<00:06:28.210> phase<00:06:28.479> in 00:06:28.740 --> 00:06:28.750 align:start position:0% in three phases in the first phase in 00:06:28.750 --> 00:06:31.490 align:start position:0% in three phases in the first phase in the<00:06:29.050> creation<00:06:29.320> of<00:06:29.590> the<00:06:29.740> legislature<00:06:30.370> now<00:06:30.430> we 00:06:31.490 --> 00:06:31.500 align:start position:0% the creation of the legislature now we 00:06:31.500 --> 00:06:34.170 align:start position:0% the creation of the legislature now we run<00:06:32.500> a<00:06:32.530> protocol<00:06:32.830> between<00:06:33.010> Ellis<00:06:33.669> Ingrid<00:06:34.090> and 00:06:34.170 --> 00:06:34.180 align:start position:0% run a protocol between Ellis Ingrid and 00:06:34.180 --> 00:06:35.610 align:start position:0% run a protocol between Ellis Ingrid and Bob<00:06:34.389> now<00:06:34.810> there<00:06:35.020> are<00:06:35.080> three<00:06:35.229> parties<00:06:35.560> involved 00:06:35.610 --> 00:06:35.620 align:start position:0% Bob now there are three parties involved 00:06:35.620 --> 00:06:37.709 align:start position:0% Bob now there are three parties involved okay<00:06:36.190> Ingrid<00:06:36.550> kind<00:06:37.060> of<00:06:37.180> takes<00:06:37.390> the<00:06:37.539> role<00:06:37.690> of 00:06:37.709 --> 00:06:37.719 align:start position:0% okay Ingrid kind of takes the role of 00:06:37.719 --> 00:06:39.140 align:start position:0% okay Ingrid kind of takes the role of the<00:06:37.990> blockchain<00:06:38.380> to<00:06:38.500> some<00:06:38.650> extent 00:06:39.140 --> 00:06:39.150 align:start position:0% the blockchain to some extent 00:06:39.150 --> 00:06:42.710 align:start position:0% the blockchain to some extent and<00:06:39.800> this<00:06:40.800> is<00:06:41.040> object<00:06:41.669> so<00:06:41.940> the<00:06:42.270> communication 00:06:42.710 --> 00:06:42.720 align:start position:0% and this is object so the communication 00:06:42.720 --> 00:06:46.070 align:start position:0% and this is object so the communication between<00:06:43.169> the<00:06:43.650> the<00:06:44.610> parties<00:06:45.030> is<00:06:45.180> going<00:06:45.660> on<00:06:45.810> like 00:06:46.070 --> 00:06:46.080 align:start position:0% between the the parties is going on like 00:06:46.080 --> 00:06:47.240 align:start position:0% between the the parties is going on like off<00:06:46.229> chain<00:06:46.470> without<00:06:46.560> touching<00:06:47.010> the 00:06:47.240 --> 00:06:47.250 align:start position:0% off chain without touching the 00:06:47.250 --> 00:06:49.850 align:start position:0% off chain without touching the blockchain<00:06:47.720> so<00:06:48.720> it<00:06:48.840> can<00:06:48.960> also<00:06:49.199> be<00:06:49.410> very<00:06:49.560> fast 00:06:49.850 --> 00:06:49.860 align:start position:0% blockchain so it can also be very fast 00:06:49.860 --> 00:06:53.240 align:start position:0% blockchain so it can also be very fast of<00:06:50.040> course<00:06:50.389> and<00:06:51.389> then<00:06:51.900> you<00:06:52.680> can<00:06:52.830> compare<00:06:53.130> this 00:06:53.240 --> 00:06:53.250 align:start position:0% of course and then you can compare this 00:06:53.250 --> 00:06:54.650 align:start position:0% of course and then you can compare this to<00:06:53.430> let's<00:06:53.639> just<00:06:53.790> state<00:06:53.910> channels<00:06:54.240> they're<00:06:54.510> the 00:06:54.650 --> 00:06:54.660 align:start position:0% to let's just state channels they're the 00:06:54.660 --> 00:06:56.330 align:start position:0% to let's just state channels they're the creation<00:06:55.110> was<00:06:55.290> on<00:06:55.590> chain<00:06:55.860> so<00:06:56.070> it<00:06:56.100> took 00:06:56.330 --> 00:06:56.340 align:start position:0% creation was on chain so it took 00:06:56.340 --> 00:07:00.050 align:start position:0% creation was on chain so it took potentially<00:06:57.120> a<00:06:57.150> lot<00:06:57.240> of<00:06:57.330> time<00:06:57.800> now<00:06:59.060> executing 00:07:00.050 --> 00:07:00.060 align:start position:0% potentially a lot of time now executing 00:07:00.060 --> 00:07:01.670 align:start position:0% potentially a lot of time now executing executing<00:07:00.300> is<00:07:00.720> very<00:07:00.900> similar<00:07:01.080> to<00:07:01.229> let<00:07:01.440> us<00:07:01.560> say 00:07:01.670 --> 00:07:01.680 align:start position:0% executing is very similar to let us say 00:07:01.680 --> 00:07:03.409 align:start position:0% executing is very similar to let us say what<00:07:02.160> happens<00:07:02.460> in<00:07:02.550> letter<00:07:02.699> state<00:07:02.970> channel<00:07:03.270> so 00:07:03.409 --> 00:07:03.419 align:start position:0% what happens in letter state channel so 00:07:03.419 --> 00:07:04.939 align:start position:0% what happens in letter state channel so Alice<00:07:03.720> and<00:07:03.870> Bob<00:07:03.990> they<00:07:04.139> can<00:07:04.320> now<00:07:04.470> execute 00:07:04.939 --> 00:07:04.949 align:start position:0% Alice and Bob they can now execute 00:07:04.949 --> 00:07:08.300 align:start position:0% Alice and Bob they can now execute multiple<00:07:05.910> contracts<00:07:06.660> of<00:07:06.810> chain<00:07:07.110> so<00:07:07.650> also<00:07:07.949> here 00:07:08.300 --> 00:07:08.310 align:start position:0% multiple contracts of chain so also here 00:07:08.310 --> 00:07:10.640 align:start position:0% multiple contracts of chain so also here we<00:07:08.490> can<00:07:08.699> allow<00:07:08.970> contracts<00:07:09.690> several<00:07:10.229> contracts 00:07:10.640 --> 00:07:10.650 align:start position:0% we can allow contracts several contracts 00:07:10.650 --> 00:07:13.990 align:start position:0% we can allow contracts several contracts potentially<00:07:11.160> to<00:07:11.820> be<00:07:11.850> executed<00:07:12.479> off<00:07:12.600> chain<00:07:12.840> and 00:07:13.990 --> 00:07:14.000 align:start position:0% potentially to be executed off chain and 00:07:14.000 --> 00:07:16.310 align:start position:0% potentially to be executed off chain and finally<00:07:15.000> when<00:07:15.240> Alice<00:07:15.720> and<00:07:15.900> Bob<00:07:15.990> they<00:07:16.110> don't 00:07:16.310 --> 00:07:16.320 align:start position:0% finally when Alice and Bob they don't 00:07:16.320 --> 00:07:19.340 align:start position:0% finally when Alice and Bob they don't want<00:07:16.470> to<00:07:16.560> use<00:07:16.740> anymore<00:07:17.010> dead<00:07:17.310> Channel<00:07:18.350> then 00:07:19.340 --> 00:07:19.350 align:start position:0% want to use anymore dead Channel then 00:07:19.350 --> 00:07:23.180 align:start position:0% want to use anymore dead Channel then they<00:07:19.500> can<00:07:19.680> close<00:07:19.949> it<00:07:20.190> by<00:07:20.970> again<00:07:21.680> not<00:07:22.680> going<00:07:22.919> to 00:07:23.180 --> 00:07:23.190 align:start position:0% they can close it by again not going to 00:07:23.190 --> 00:07:25.279 align:start position:0% they can close it by again not going to the<00:07:23.340> to<00:07:23.639> the<00:07:23.729> blockchain<00:07:23.940> not<00:07:24.900> going<00:07:25.110> to<00:07:25.199> the 00:07:25.279 --> 00:07:25.289 align:start position:0% the to the blockchain not going to the 00:07:25.289 --> 00:07:26.840 align:start position:0% the to the blockchain not going to the ledger<00:07:25.470> but<00:07:25.919> going<00:07:26.130> to<00:07:26.280> the<00:07:26.460> underlying 00:07:26.840 --> 00:07:26.850 align:start position:0% ledger but going to the underlying 00:07:26.850 --> 00:07:29.629 align:start position:0% ledger but going to the underlying legislature<00:07:27.919> okay<00:07:28.919> again<00:07:29.220> this<00:07:29.400> has<00:07:29.550> the 00:07:29.629 --> 00:07:29.639 align:start position:0% legislature okay again this has the 00:07:29.639 --> 00:07:31.159 align:start position:0% legislature okay again this has the advantage<00:07:29.729> that<00:07:30.060> all<00:07:30.419> of<00:07:30.600> this<00:07:30.750> year<00:07:31.020> as<00:07:31.139> you 00:07:31.159 --> 00:07:31.169 align:start position:0% advantage that all of this year as you 00:07:31.169 --> 00:07:33.680 align:start position:0% advantage that all of this year as you can<00:07:31.410> see<00:07:31.590> all<00:07:32.039> of<00:07:32.130> this<00:07:32.370> create<00:07:32.760> execute<00:07:33.419> and 00:07:33.680 --> 00:07:33.690 align:start position:0% can see all of this create execute and 00:07:33.690 --> 00:07:36.490 align:start position:0% can see all of this create execute and close<00:07:34.620> all<00:07:35.100> of<00:07:35.340> this<00:07:35.460> happens<00:07:35.880> off<00:07:36.000> chain 00:07:36.490 --> 00:07:36.500 align:start position:0% close all of this happens off chain 00:07:36.500 --> 00:07:39.400 align:start position:0% close all of this happens off chain without<00:07:37.500> interaction<00:07:38.130> with<00:07:38.940> the<00:07:39.060> ledger 00:07:39.400 --> 00:07:39.410 align:start position:0% without interaction with the ledger 00:07:39.410 --> 00:07:41.600 align:start position:0% without interaction with the ledger which<00:07:40.410> is<00:07:40.530> in<00:07:40.620> contrast<00:07:40.979> to<00:07:41.010> the<00:07:41.160> legend<00:07:41.430> state 00:07:41.600 --> 00:07:41.610 align:start position:0% which is in contrast to the legend state 00:07:41.610 --> 00:07:45.409 align:start position:0% which is in contrast to the legend state channels<00:07:42.110> now<00:07:43.400> this<00:07:44.400> is<00:07:44.520> very<00:07:44.700> nice<00:07:44.910> but<00:07:45.180> we<00:07:45.330> of 00:07:45.409 --> 00:07:45.419 align:start position:0% channels now this is very nice but we of 00:07:45.419 --> 00:07:47.240 align:start position:0% channels now this is very nice but we of course<00:07:45.630> would<00:07:45.750> like<00:07:45.930> to<00:07:46.080> consider<00:07:46.530> to<00:07:46.860> also 00:07:47.240 --> 00:07:47.250 align:start position:0% course would like to consider to also 00:07:47.250 --> 00:07:48.830 align:start position:0% course would like to consider to also capture<00:07:47.460> exception<00:07:48.090> more<00:07:48.270> complicated 00:07:48.830 --> 00:07:48.840 align:start position:0% capture exception more complicated 00:07:48.840 --> 00:07:50.750 align:start position:0% capture exception more complicated networks<00:07:49.200> so<00:07:49.680> like<00:07:49.979> here<00:07:50.160> we<00:07:50.250> have<00:07:50.370> much<00:07:50.610> more 00:07:50.750 --> 00:07:50.760 align:start position:0% networks so like here we have much more 00:07:50.760 --> 00:07:53.330 align:start position:0% networks so like here we have much more complicated<00:07:51.000> network<00:07:51.630> like<00:07:52.500> little<00:07:53.220> more 00:07:53.330 --> 00:07:53.340 align:start position:0% complicated network like little more 00:07:53.340 --> 00:07:55.520 align:start position:0% complicated network like little more complicated<00:07:53.580> Network<00:07:54.330> and<00:07:54.539> we<00:07:54.720> want<00:07:55.349> for 00:07:55.520 --> 00:07:55.530 align:start position:0% complicated Network and we want for 00:07:55.530 --> 00:07:58.100 align:start position:0% complicated Network and we want for example<00:07:55.560> that<00:07:56.039> Ellis<00:07:56.340> wants<00:07:56.669> to<00:07:56.910> talk<00:07:57.720> to<00:07:57.900> Dave 00:07:58.100 --> 00:07:58.110 align:start position:0% example that Ellis wants to talk to Dave 00:07:58.110 --> 00:08:00.170 align:start position:0% example that Ellis wants to talk to Dave okay<00:07:58.590> so<00:07:58.650> how<00:07:58.830> can<00:07:59.039> they<00:07:59.160> do<00:07:59.310> this<00:07:59.490> you<00:08:00.000> can 00:08:00.170 --> 00:08:00.180 align:start position:0% okay so how can they do this you can 00:08:00.180 --> 00:08:02.930 align:start position:0% okay so how can they do this you can just<00:08:00.479> apply<00:08:00.750> this<00:08:01.080> technique<00:08:01.919> that<00:08:02.250> I<00:08:02.849> just 00:08:02.930 --> 00:08:02.940 align:start position:0% just apply this technique that I just 00:08:02.940 --> 00:08:04.750 align:start position:0% just apply this technique that I just thought<00:08:03.450> I<00:08:03.570> told<00:08:03.780> you<00:08:03.960> about 00:08:04.750 --> 00:08:04.760 align:start position:0% thought I told you about 00:08:04.760 --> 00:08:08.060 align:start position:0% thought I told you about recursively<00:08:05.760> so<00:08:06.150> we<00:08:06.330> could<00:08:06.570> let<00:08:07.500> Ellis<00:08:07.770> first 00:08:08.060 --> 00:08:08.070 align:start position:0% recursively so we could let Ellis first 00:08:08.070 --> 00:08:10.850 align:start position:0% recursively so we could let Ellis first create<00:08:08.460> a<00:08:08.490> virtual<00:08:09.360> state<00:08:09.570> channel<00:08:09.930> with<00:08:10.650> Bob 00:08:10.850 --> 00:08:10.860 align:start position:0% create a virtual state channel with Bob 00:08:10.860 --> 00:08:13.400 align:start position:0% create a virtual state channel with Bob then<00:08:11.460> over<00:08:12.360> the<00:08:12.479> virtual<00:08:12.780> state<00:08:13.020> channel 00:08:13.400 --> 00:08:13.410 align:start position:0% then over the virtual state channel 00:08:13.410 --> 00:08:16.010 align:start position:0% then over the virtual state channel between<00:08:14.340> Alice<00:08:14.669> and<00:08:14.789> Bob<00:08:14.880> Ellis<00:08:15.750> can<00:08:15.900> now 00:08:16.010 --> 00:08:16.020 align:start position:0% between Alice and Bob Ellis can now 00:08:16.020 --> 00:08:18.080 align:start position:0% between Alice and Bob Ellis can now create<00:08:16.320> another<00:08:16.410> virtual<00:08:16.949> state<00:08:17.190> channel<00:08:17.460> was 00:08:18.080 --> 00:08:18.090 align:start position:0% create another virtual state channel was 00:08:18.090 --> 00:08:20.089 align:start position:0% create another virtual state channel was clear<00:08:18.419> and<00:08:18.690> then<00:08:18.960> this<00:08:19.080> can<00:08:19.260> be<00:08:19.289> continuing 00:08:20.089 --> 00:08:20.099 align:start position:0% clear and then this can be continuing 00:08:20.099 --> 00:08:24.500 align:start position:0% clear and then this can be continuing like<00:08:20.760> this<00:08:20.789> until<00:08:21.360> finally<00:08:22.250> Ellis<00:08:23.250> has<00:08:23.639> it<00:08:24.330> has 00:08:24.500 --> 00:08:24.510 align:start position:0% like this until finally Ellis has it has 00:08:24.510 --> 00:08:26.870 align:start position:0% like this until finally Ellis has it has reached<00:08:24.750> Dave<00:08:25.440> and<00:08:25.949> then<00:08:26.130> they<00:08:26.220> can<00:08:26.400> execute 00:08:26.870 --> 00:08:26.880 align:start position:0% reached Dave and then they can execute 00:08:26.880 --> 00:08:29.170 align:start position:0% reached Dave and then they can execute in<00:08:27.300> this<00:08:27.539> final<00:08:27.870> channels<00:08:28.470> they<00:08:28.620> can<00:08:28.830> execute 00:08:29.170 --> 00:08:29.180 align:start position:0% in this final channels they can execute 00:08:29.180 --> 00:08:32.659 align:start position:0% in this final channels they can execute their<00:08:30.180> contracts<00:08:30.599> of<00:08:30.720> chain<00:08:31.370> so<00:08:32.370> what<00:08:32.490> are<00:08:32.580> the 00:08:32.659 --> 00:08:32.669 align:start position:0% their contracts of chain so what are the 00:08:32.669 --> 00:08:34.610 align:start position:0% their contracts of chain so what are the advantages<00:08:32.760> of<00:08:33.150> channel<00:08:34.110> visualizations 00:08:34.610 --> 00:08:34.620 align:start position:0% advantages of channel visualizations 00:08:34.620 --> 00:08:37.279 align:start position:0% advantages of channel visualizations there<00:08:35.610> are<00:08:35.729> several<00:08:36.060> of<00:08:36.599> them<00:08:36.900> that<00:08:36.930> I<00:08:37.140> would 00:08:37.279 --> 00:08:37.289 align:start position:0% there are several of them that I would 00:08:37.289 --> 00:08:39.170 align:start position:0% there are several of them that I would like<00:08:37.440> to<00:08:37.529> highlight<00:08:37.709> first<00:08:38.580> of<00:08:38.760> all<00:08:38.880> this<00:08:39.000> is 00:08:39.170 --> 00:08:39.180 align:start position:0% like to highlight first of all this is 00:08:39.180 --> 00:08:41.630 align:start position:0% like to highlight first of all this is low<00:08:39.900> costs<00:08:40.320> so<00:08:40.650> since<00:08:40.950> the<00:08:41.099> intermediary<00:08:41.610> is 00:08:41.630 --> 00:08:41.640 align:start position:0% low costs so since the intermediary is 00:08:41.640 --> 00:08:44.480 align:start position:0% low costs so since the intermediary is not<00:08:41.909> involved<00:08:42.330> anymore<00:08:42.750> in<00:08:43.289> the<00:08:43.740> execution<00:08:44.339> of 00:08:44.480 --> 00:08:44.490 align:start position:0% not involved anymore in the execution of 00:08:44.490 --> 00:08:47.810 align:start position:0% not involved anymore in the execution of the<00:08:45.529> the<00:08:46.529> contract<00:08:46.950> similar<00:08:47.459> to<00:08:47.610> the<00:08:47.670> later 00:08:47.810 --> 00:08:47.820 align:start position:0% the the contract similar to the later 00:08:47.820 --> 00:08:49.760 align:start position:0% the the contract similar to the later state<00:08:48.150> channel<00:08:48.540> where<00:08:48.930> the<00:08:49.110> blockchain<00:08:49.530> is 00:08:49.760 --> 00:08:49.770 align:start position:0% state channel where the blockchain is 00:08:49.770 --> 00:08:52.250 align:start position:0% state channel where the blockchain is not<00:08:49.950> involved<00:08:50.339> in<00:08:50.940> the<00:08:51.570> execution<00:08:51.810> of<00:08:52.140> the 00:08:52.250 --> 00:08:52.260 align:start position:0% not involved in the execution of the 00:08:52.260 --> 00:08:52.670 align:start position:0% not involved in the execution of the contract 00:08:52.670 --> 00:08:52.680 align:start position:0% contract 00:08:52.680 --> 00:08:55.010 align:start position:0% contract this<00:08:53.250> can<00:08:53.430> be<00:08:53.550> very<00:08:53.820> fast<00:08:54.120> and<00:08:54.390> it<00:08:54.480> can<00:08:54.660> also<00:08:54.870> be 00:08:55.010 --> 00:08:55.020 align:start position:0% this can be very fast and it can also be 00:08:55.020 --> 00:08:56.710 align:start position:0% this can be very fast and it can also be cheap<00:08:55.380> so<00:08:55.770> there<00:08:55.950> in<00:08:56.010> particular<00:08:56.490> the 00:08:56.710 --> 00:08:56.720 align:start position:0% cheap so there in particular the 00:08:56.720 --> 00:08:59.030 align:start position:0% cheap so there in particular the intermediary<00:08:57.720> does<00:08:58.080> not<00:08:58.290> necessarily<00:08:58.890> need 00:08:59.030 --> 00:08:59.040 align:start position:0% intermediary does not necessarily need 00:08:59.040 --> 00:09:02.630 align:start position:0% intermediary does not necessarily need to<00:08:59.820> ask<00:09:00.089> for<00:09:00.540> fees<00:09:01.220> we<00:09:02.220> also<00:09:02.339> have<00:09:02.520> better 00:09:02.630 --> 00:09:02.640 align:start position:0% to ask for fees we also have better 00:09:02.640 --> 00:09:05.870 align:start position:0% to ask for fees we also have better privacy<00:09:03.210> so<00:09:03.920> because<00:09:04.920> the<00:09:05.130> intermediary<00:09:05.700> does 00:09:05.870 --> 00:09:05.880 align:start position:0% privacy so because the intermediary does 00:09:05.880 --> 00:09:07.340 align:start position:0% privacy so because the intermediary does not<00:09:06.060> know<00:09:06.240> what<00:09:06.570> happens<00:09:06.899> in<00:09:07.050> the<00:09:07.170> letter 00:09:07.340 --> 00:09:07.350 align:start position:0% not know what happens in the letter 00:09:07.350 --> 00:09:11.210 align:start position:0% not know what happens in the letter individual<00:09:07.890> state<00:09:08.100> Channel<00:09:09.890> Alice<00:09:10.890> and<00:09:11.040> Bob 00:09:11.210 --> 00:09:11.220 align:start position:0% individual state Channel Alice and Bob 00:09:11.220 --> 00:09:14.810 align:start position:0% individual state Channel Alice and Bob can<00:09:11.580> keep<00:09:12.420> the<00:09:12.690> state<00:09:13.230> updates<00:09:13.680> private<00:09:14.100> and 00:09:14.810 --> 00:09:14.820 align:start position:0% can keep the state updates private and 00:09:14.820 --> 00:09:16.820 align:start position:0% can keep the state updates private and tears<00:09:15.209> of<00:09:15.390> course<00:09:15.600> the<00:09:16.260> other<00:09:16.440> advantage 00:09:16.820 --> 00:09:16.830 align:start position:0% tears of course the other advantage 00:09:16.830 --> 00:09:18.620 align:start position:0% tears of course the other advantage there<00:09:16.980> is<00:09:17.010> no<00:09:17.160> availability<00:09:17.790> required<00:09:18.360> so 00:09:18.620 --> 00:09:18.630 align:start position:0% there is no availability required so 00:09:18.630 --> 00:09:21.040 align:start position:0% there is no availability required so even<00:09:18.959> if<00:09:19.110> Ingrid<00:09:19.410> goes<00:09:19.649> offline<00:09:19.980> for<00:09:20.430> a<00:09:20.459> while 00:09:21.040 --> 00:09:21.050 align:start position:0% even if Ingrid goes offline for a while 00:09:21.050 --> 00:09:23.389 align:start position:0% even if Ingrid goes offline for a while then<00:09:22.050> Alice<00:09:22.440> and<00:09:22.620> Bob<00:09:22.740> can<00:09:22.770> still<00:09:23.100> continue 00:09:23.389 --> 00:09:23.399 align:start position:0% then Alice and Bob can still continue 00:09:23.399 --> 00:09:26.060 align:start position:0% then Alice and Bob can still continue playing<00:09:23.880> chess<00:09:24.180> which<00:09:24.810> is<00:09:24.930> of<00:09:25.110> course<00:09:25.350> a<00:09:25.529> nice 00:09:26.060 --> 00:09:26.070 align:start position:0% playing chess which is of course a nice 00:09:26.070 --> 00:09:29.180 align:start position:0% playing chess which is of course a nice feature<00:09:26.399> so<00:09:26.700> now<00:09:27.600> you<00:09:27.660> have<00:09:27.839> seen<00:09:27.990> a<00:09:28.190> basic 00:09:29.180 --> 00:09:29.190 align:start position:0% feature so now you have seen a basic 00:09:29.190 --> 00:09:32.060 align:start position:0% feature so now you have seen a basic idea<00:09:29.700> of<00:09:29.970> how<00:09:30.120> we<00:09:30.330> construct<00:09:31.070> generalized 00:09:32.060 --> 00:09:32.070 align:start position:0% idea of how we construct generalized 00:09:32.070 --> 00:09:34.820 align:start position:0% idea of how we construct generalized state<00:09:32.279> channels<00:09:32.610> now<00:09:33.020> or<00:09:34.020> like<00:09:34.380> what<00:09:34.680> are 00:09:34.820 --> 00:09:34.830 align:start position:0% state channels now or like what are 00:09:34.830 --> 00:09:36.320 align:start position:0% state channels now or like what are actually<00:09:35.100> general<00:09:35.399> stations<00:09:35.790> you<00:09:36.029> would<00:09:36.180> like 00:09:36.320 --> 00:09:36.330 align:start position:0% actually general stations you would like 00:09:36.330 --> 00:09:37.940 align:start position:0% actually general stations you would like of<00:09:36.480> course<00:09:36.690> to<00:09:36.810> know<00:09:36.930> how<00:09:37.110> you<00:09:37.529> can<00:09:37.680> construct 00:09:37.940 --> 00:09:37.950 align:start position:0% of course to know how you can construct 00:09:37.950 --> 00:09:40.550 align:start position:0% of course to know how you can construct them<00:09:38.270> unfortunately<00:09:39.270> I<00:09:39.510> cannot<00:09:40.080> explain<00:09:40.380> in 00:09:40.550 --> 00:09:40.560 align:start position:0% them unfortunately I cannot explain in 00:09:40.560 --> 00:09:42.829 align:start position:0% them unfortunately I cannot explain in detail<00:09:40.830> how<00:09:40.860> this<00:09:41.190> works<00:09:41.430> now<00:09:41.790> because<00:09:42.660> it 00:09:42.829 --> 00:09:42.839 align:start position:0% detail how this works now because it 00:09:42.839 --> 00:09:44.780 align:start position:0% detail how this works now because it will<00:09:42.930> take<00:09:43.140> quite<00:09:43.320> a<00:09:43.380> lot<00:09:43.589> of<00:09:43.649> time<00:09:43.860> and<00:09:44.070> we<00:09:44.760> can 00:09:44.780 --> 00:09:44.790 align:start position:0% will take quite a lot of time and we can 00:09:44.790 --> 00:09:46.730 align:start position:0% will take quite a lot of time and we can I<00:09:45.089> would<00:09:45.570> refer<00:09:45.870> liked<00:09:46.050> to<00:09:46.170> refer<00:09:46.290> you<00:09:46.529> to<00:09:46.560> our 00:09:46.730 --> 00:09:46.740 align:start position:0% I would refer liked to refer you to our 00:09:46.740 --> 00:09:49.310 align:start position:0% I would refer liked to refer you to our papers<00:09:47.370> which<00:09:47.640> are<00:09:47.790> on<00:09:47.910> the<00:09:48.029> webpage<00:09:48.180> it<00:09:49.080> was 00:09:49.310 --> 00:09:49.320 align:start position:0% papers which are on the webpage it was 00:09:49.320 --> 00:09:52.010 align:start position:0% papers which are on the webpage it was mentioned<00:09:49.649> on<00:09:49.740> the<00:09:49.830> first<00:09:49.980> slide<00:09:50.160> the<00:09:51.089> one 00:09:52.010 --> 00:09:52.020 align:start position:0% mentioned on the first slide the one 00:09:52.020 --> 00:09:54.699 align:start position:0% mentioned on the first slide the one thing<00:09:52.260> that<00:09:52.380> I<00:09:52.440> want<00:09:52.620> to<00:09:52.680> explain<00:09:53.130> to<00:09:53.430> you<00:09:53.610> is 00:09:54.699 --> 00:09:54.709 align:start position:0% thing that I want to explain to you is 00:09:54.709 --> 00:09:56.840 align:start position:0% thing that I want to explain to you is what<00:09:55.709> happens<00:09:56.070> in<00:09:56.220> the<00:09:56.310> case<00:09:56.430> of<00:09:56.490> corruption 00:09:56.840 --> 00:09:56.850 align:start position:0% what happens in the case of corruption 00:09:56.850 --> 00:09:58.880 align:start position:0% what happens in the case of corruption so<00:09:57.209> corruption<00:09:57.720> makes<00:09:57.990> as<00:09:58.260> we<00:09:58.470> all<00:09:58.589> know<00:09:58.709> our 00:09:58.880 --> 00:09:58.890 align:start position:0% so corruption makes as we all know our 00:09:58.890 --> 00:10:01.640 align:start position:0% so corruption makes as we all know our life<00:09:59.130> more<00:09:59.370> difficult<00:09:59.820> and<00:10:00.080> this<00:10:01.080> is<00:10:01.230> also<00:10:01.410> why 00:10:01.640 --> 00:10:01.650 align:start position:0% life more difficult and this is also why 00:10:01.650 --> 00:10:03.590 align:start position:0% life more difficult and this is also why designing<00:10:02.100> such<00:10:02.250> protocols<00:10:02.459> gets<00:10:03.300> quite 00:10:03.590 --> 00:10:03.600 align:start position:0% designing such protocols gets quite 00:10:03.600 --> 00:10:06.380 align:start position:0% designing such protocols gets quite complex<00:10:03.959> so<00:10:04.950> we<00:10:05.100> have<00:10:05.250> the<00:10:05.820> first<00:10:06.000> case<00:10:06.240> the 00:10:06.380 --> 00:10:06.390 align:start position:0% complex so we have the first case the 00:10:06.390 --> 00:10:07.640 align:start position:0% complex so we have the first case the first<00:10:06.420> example<00:10:06.990> that<00:10:07.020> I<00:10:07.140> would<00:10:07.260> like<00:10:07.410> to<00:10:07.529> look 00:10:07.640 --> 00:10:07.650 align:start position:0% first example that I would like to look 00:10:07.650 --> 00:10:10.550 align:start position:0% first example that I would like to look at<00:10:08.209> with<00:10:09.209> you<00:10:09.390> is<00:10:09.540> now<00:10:09.750> the<00:10:09.810> following<00:10:10.350> so<00:10:10.470> we 00:10:10.550 --> 00:10:10.560 align:start position:0% at with you is now the following so we 00:10:10.560 --> 00:10:12.190 align:start position:0% at with you is now the following so we have<00:10:10.680> Ellis<00:10:10.980> Ingrid<00:10:11.250> Bob<00:10:11.430> and<00:10:11.670> clear<00:10:11.880> and 00:10:12.190 --> 00:10:12.200 align:start position:0% have Ellis Ingrid Bob and clear and 00:10:12.200 --> 00:10:15.710 align:start position:0% have Ellis Ingrid Bob and clear and Ellis<00:10:13.200> wants<00:10:13.380> to<00:10:13.470> play<00:10:13.620> chess<00:10:13.860> was<00:10:14.040> clear<00:10:14.720> so 00:10:15.710 --> 00:10:15.720 align:start position:0% Ellis wants to play chess was clear so 00:10:15.720 --> 00:10:18.650 align:start position:0% Ellis wants to play chess was clear so Ellis<00:10:16.200> can<00:10:16.410> open<00:10:17.250> a<00:10:17.459> virtual<00:10:18.060> state<00:10:18.300> channel 00:10:18.650 --> 00:10:18.660 align:start position:0% Ellis can open a virtual state channel 00:10:18.660 --> 00:10:21.050 align:start position:0% Ellis can open a virtual state channel between<00:10:18.839> Ellis<00:10:19.709> and<00:10:19.830> clear<00:10:20.070> by<00:10:20.490> using<00:10:20.940> this 00:10:21.050 --> 00:10:21.060 align:start position:0% between Ellis and clear by using this 00:10:21.060 --> 00:10:22.870 align:start position:0% between Ellis and clear by using this recursive<00:10:21.240> approach<00:10:21.660> that<00:10:22.050> I<00:10:22.140> just<00:10:22.350> explained 00:10:22.870 --> 00:10:22.880 align:start position:0% recursive approach that I just explained 00:10:22.880 --> 00:10:25.430 align:start position:0% recursive approach that I just explained and<00:10:23.880> then<00:10:24.000> she<00:10:24.180> can<00:10:24.360> open<00:10:24.510> a<00:10:24.779> chess<00:10:24.990> contract 00:10:25.430 --> 00:10:25.440 align:start position:0% and then she can open a chess contract 00:10:25.440 --> 00:10:27.290 align:start position:0% and then she can open a chess contract and<00:10:25.589> maybe<00:10:25.770> in<00:10:25.920> this<00:10:26.040> chess<00:10:26.250> contract<00:10:26.670> she<00:10:26.940> did 00:10:27.290 --> 00:10:27.300 align:start position:0% and maybe in this chess contract she did 00:10:27.300 --> 00:10:29.449 align:start position:0% and maybe in this chess contract she did some<00:10:27.540> several<00:10:27.870> moves<00:10:28.230> okay<00:10:28.680> she<00:10:28.950> played<00:10:29.220> very 00:10:29.449 --> 00:10:29.459 align:start position:0% some several moves okay she played very 00:10:29.459 --> 00:10:32.840 align:start position:0% some several moves okay she played very smartly<00:10:29.850> and<00:10:30.660> at<00:10:31.050> the<00:10:31.200> end<00:10:31.380> she<00:10:31.770> is<00:10:32.279> in<00:10:32.490> state<00:10:32.700> n 00:10:32.840 --> 00:10:32.850 align:start position:0% smartly and at the end she is in state n 00:10:32.850 --> 00:10:34.340 align:start position:0% smartly and at the end she is in state n minus<00:10:33.180> one<00:10:33.390> and<00:10:33.570> there<00:10:33.690> is<00:10:33.750> only<00:10:33.839> one<00:10:34.200> state 00:10:34.340 --> 00:10:34.350 align:start position:0% minus one and there is only one state 00:10:34.350 --> 00:10:37.400 align:start position:0% minus one and there is only one state left<00:10:34.770> substitue<00:10:35.730> finally<00:10:36.120> wins<00:10:36.360> the<00:10:36.750> game<00:10:36.959> ok 00:10:37.400 --> 00:10:37.410 align:start position:0% left substitue finally wins the game ok 00:10:37.410 --> 00:10:40.610 align:start position:0% left substitue finally wins the game ok so<00:10:37.910> this<00:10:38.910> has<00:10:39.209> to<00:10:39.390> submit<00:10:39.570> to<00:10:39.959> execute<00:10:40.410> to<00:10:40.529> the 00:10:40.610 --> 00:10:40.620 align:start position:0% so this has to submit to execute to the 00:10:40.620 --> 00:10:43.130 align:start position:0% so this has to submit to execute to the next<00:10:40.829> state<00:10:41.010> and<00:10:41.220> then<00:10:41.310> she<00:10:41.490> will<00:10:41.670> win<00:10:41.990> but<00:10:42.990> now 00:10:43.130 --> 00:10:43.140 align:start position:0% next state and then she will win but now 00:10:43.140 --> 00:10:46.100 align:start position:0% next state and then she will win but now of<00:10:43.290> course<00:10:43.880> clear<00:10:44.880> and<00:10:45.300> potentially<00:10:45.990> all<00:10:46.079> the 00:10:46.100 --> 00:10:46.110 align:start position:0% of course clear and potentially all the 00:10:46.110 --> 00:10:47.420 align:start position:0% of course clear and potentially all the other<00:10:46.350> parties<00:10:46.680> they<00:10:46.829> don't<00:10:47.130> have<00:10:47.250> any 00:10:47.420 --> 00:10:47.430 align:start position:0% other parties they don't have any 00:10:47.430 --> 00:10:49.130 align:start position:0% other parties they don't have any interest<00:10:47.790> in<00:10:47.910> this<00:10:48.029> ok<00:10:48.360> so<00:10:48.420> they<00:10:48.630> tend<00:10:49.050> to 00:10:49.130 --> 00:10:49.140 align:start position:0% interest in this ok so they tend to 00:10:49.140 --> 00:10:52.310 align:start position:0% interest in this ok so they tend to interrupt<00:10:49.529> and<00:10:50.240> try<00:10:51.240> to<00:10:51.300> prevent<00:10:51.779> this<00:10:52.020> they 00:10:52.310 --> 00:10:52.320 align:start position:0% interrupt and try to prevent this they 00:10:52.320 --> 00:10:54.260 align:start position:0% interrupt and try to prevent this they disappear<00:10:52.740> like<00:10:53.070> just<00:10:53.520> in<00:10:53.670> this<00:10:53.760> example<00:10:54.120> that 00:10:54.260 --> 00:10:54.270 align:start position:0% disappear like just in this example that 00:10:54.270 --> 00:10:57.079 align:start position:0% disappear like just in this example that mu<00:10:54.510> short<00:10:55.170> on<00:10:55.350> this<00:10:55.470> slide<00:10:55.740> they<00:10:56.700> disappear 00:10:57.079 --> 00:10:57.089 align:start position:0% mu short on this slide they disappear 00:10:57.089 --> 00:10:59.210 align:start position:0% mu short on this slide they disappear and<00:10:57.360> then<00:10:57.600> we<00:10:58.589> still<00:10:58.800> have<00:10:58.829> to<00:10:59.040> finish 00:10:59.210 --> 00:10:59.220 align:start position:0% and then we still have to finish 00:10:59.220 --> 00:11:01.460 align:start position:0% and then we still have to finish finalize<00:10:59.790> this<00:11:00.060> execution<00:11:00.930> because<00:11:01.050> we<00:11:01.290> want 00:11:01.460 --> 00:11:01.470 align:start position:0% finalize this execution because we want 00:11:01.470 --> 00:11:03.500 align:start position:0% finalize this execution because we want to<00:11:01.500> have<00:11:01.680> a<00:11:01.709> secure<00:11:02.040> protocol<00:11:02.430> so<00:11:03.329> how<00:11:03.450> can 00:11:03.500 --> 00:11:03.510 align:start position:0% to have a secure protocol so how can 00:11:03.510 --> 00:11:05.390 align:start position:0% to have a secure protocol so how can this<00:11:03.720> work<00:11:03.930> at<00:11:04.470> the<00:11:04.620> very<00:11:04.800> high<00:11:04.950> level<00:11:05.010> of 00:11:05.390 --> 00:11:05.400 align:start position:0% this work at the very high level of 00:11:05.400 --> 00:11:06.770 align:start position:0% this work at the very high level of course<00:11:05.610> it<00:11:05.790> gets<00:11:06.209> very<00:11:06.270> technique 00:11:06.770 --> 00:11:06.780 align:start position:0% course it gets very technique 00:11:06.780 --> 00:11:08.330 align:start position:0% course it gets very technique because<00:11:07.080> of<00:11:07.200> their<00:11:07.320> many<00:11:07.530> Sitecore<00:11:08.070> aside 00:11:08.330 --> 00:11:08.340 align:start position:0% because of their many Sitecore aside 00:11:08.340 --> 00:11:10.700 align:start position:0% because of their many Sitecore aside cases<00:11:08.760> that<00:11:08.910> we<00:11:09.030> have<00:11:09.150> to<00:11:09.300> do<00:11:09.450> is<00:11:09.710> essentially 00:11:10.700 --> 00:11:10.710 align:start position:0% cases that we have to do is essentially 00:11:10.710 --> 00:11:13.940 align:start position:0% cases that we have to do is essentially Ellis<00:11:11.520> first<00:11:11.820> tries<00:11:12.120> to<00:11:12.570> execute<00:11:12.990> the 00:11:13.940 --> 00:11:13.950 align:start position:0% Ellis first tries to execute the 00:11:13.950 --> 00:11:15.770 align:start position:0% Ellis first tries to execute the contract<00:11:14.190> in<00:11:14.730> the<00:11:15.120> underlying<00:11:15.600> virtual 00:11:15.770 --> 00:11:15.780 align:start position:0% contract in the underlying virtual 00:11:15.780 --> 00:11:18.230 align:start position:0% contract in the underlying virtual channel<00:11:16.290> between<00:11:16.440> Bob<00:11:16.770> if<00:11:17.400> this<00:11:17.670> also<00:11:17.850> fails 00:11:18.230 --> 00:11:18.240 align:start position:0% channel between Bob if this also fails 00:11:18.240 --> 00:11:19.820 align:start position:0% channel between Bob if this also fails because<00:11:18.450> in<00:11:18.690> my<00:11:18.810> example<00:11:19.260> Bob<00:11:19.380> is<00:11:19.530> also 00:11:19.820 --> 00:11:19.830 align:start position:0% because in my example Bob is also 00:11:19.830 --> 00:11:21.980 align:start position:0% because in my example Bob is also corrupt<00:11:20.100> and<00:11:20.400> essentially<00:11:21.240> everybody<00:11:21.480> can<00:11:21.810> be 00:11:21.980 --> 00:11:21.990 align:start position:0% corrupt and essentially everybody can be 00:11:21.990 --> 00:11:24.230 align:start position:0% corrupt and essentially everybody can be the<00:11:22.350> protocols<00:11:22.770> have<00:11:22.890> to<00:11:22.950> work<00:11:23.250> even<00:11:23.700> if<00:11:24.030> all 00:11:24.230 --> 00:11:24.240 align:start position:0% the protocols have to work even if all 00:11:24.240 --> 00:11:25.910 align:start position:0% the protocols have to work even if all parties<00:11:24.450> are<00:11:24.780> corrupt<00:11:25.230> except<00:11:25.560> for<00:11:25.740> this 00:11:25.910 --> 00:11:25.920 align:start position:0% parties are corrupt except for this 00:11:25.920 --> 00:11:29.090 align:start position:0% parties are corrupt except for this single<00:11:26.310> party<00:11:27.170> and<00:11:28.170> if<00:11:28.320> this<00:11:28.470> also<00:11:28.620> fails<00:11:28.920> then 00:11:29.090 --> 00:11:29.100 align:start position:0% single party and if this also fails then 00:11:29.100 --> 00:11:30.320 align:start position:0% single party and if this also fails then she<00:11:29.250> goes<00:11:29.400> to<00:11:29.580> the<00:11:29.670> next<00:11:29.730> underlying 00:11:30.320 --> 00:11:30.330 align:start position:0% she goes to the next underlying 00:11:30.330 --> 00:11:32.780 align:start position:0% she goes to the next underlying legislation<00:11:30.630> on<00:11:31.230> here<00:11:31.530> she<00:11:31.950> tries<00:11:32.220> to<00:11:32.250> execute 00:11:32.780 --> 00:11:32.790 align:start position:0% legislation on here she tries to execute 00:11:32.790 --> 00:11:35.450 align:start position:0% legislation on here she tries to execute to<00:11:33.180> the<00:11:33.300> next<00:11:33.570> state<00:11:33.810> in<00:11:34.080> this<00:11:34.410> and<00:11:34.620> then 00:11:35.450 --> 00:11:35.460 align:start position:0% to the next state in this and then 00:11:35.460 --> 00:11:37.490 align:start position:0% to the next state in this and then finally<00:11:35.970> if<00:11:36.180> also<00:11:36.420> England<00:11:36.900> as<00:11:36.990> corrupt<00:11:37.320> she 00:11:37.490 --> 00:11:37.500 align:start position:0% finally if also England as corrupt she 00:11:37.500 --> 00:11:39.410 align:start position:0% finally if also England as corrupt she goes<00:11:37.680> to<00:11:37.890> the<00:11:38.040> to<00:11:38.700> the<00:11:38.790> underlying<00:11:39.150> ledger 00:11:39.410 --> 00:11:39.420 align:start position:0% goes to the to the underlying ledger 00:11:39.420 --> 00:11:42.890 align:start position:0% goes to the to the underlying ledger okay<00:11:39.810> and<00:11:39.930> of<00:11:40.050> course<00:11:40.320> we<00:11:41.130> trust<00:11:41.460> a<00:11:41.790> serum<00:11:42.510> we 00:11:42.890 --> 00:11:42.900 align:start position:0% okay and of course we trust a serum we 00:11:42.900 --> 00:11:46.190 align:start position:0% okay and of course we trust a serum we trust<00:11:43.140> vitalik<00:11:43.590> so<00:11:44.520> we<00:11:44.910> will<00:11:45.090> get<00:11:45.300> eventually 00:11:46.190 --> 00:11:46.200 align:start position:0% trust vitalik so we will get eventually 00:11:46.200 --> 00:11:49.520 align:start position:0% trust vitalik so we will get eventually we<00:11:47.070> get<00:11:47.430> eventually<00:11:47.850> the<00:11:48.690> execution<00:11:49.350> time 00:11:49.520 --> 00:11:49.530 align:start position:0% we get eventually the execution time 00:11:49.530 --> 00:11:53.930 align:start position:0% we get eventually the execution time okay<00:11:49.830> so<00:11:51.920> this<00:11:52.920> is<00:11:53.070> the<00:11:53.160> first<00:11:53.340> example<00:11:53.550> that<00:11:53.820> I 00:11:53.930 --> 00:11:53.940 align:start position:0% okay so this is the first example that I 00:11:53.940 --> 00:11:55.880 align:start position:0% okay so this is the first example that I would<00:11:54.060> like<00:11:54.180> to<00:11:54.210> look<00:11:54.390> in<00:11:54.540> so<00:11:55.350> now<00:11:55.560> let's<00:11:55.830> look 00:11:55.880 --> 00:11:55.890 align:start position:0% would like to look in so now let's look 00:11:55.890 --> 00:11:59.570 align:start position:0% would like to look in so now let's look into<00:11:56.070> the<00:11:56.190> next<00:11:56.370> example<00:11:58.160> how<00:11:59.160> can<00:11:59.310> we<00:11:59.400> deal 00:11:59.570 --> 00:11:59.580 align:start position:0% into the next example how can we deal 00:11:59.580 --> 00:12:01.280 align:start position:0% into the next example how can we deal with<00:11:59.640> the<00:11:59.910> corruption<00:12:00.240> case<00:12:00.420> when<00:12:00.660> Alice<00:12:01.080> and 00:12:01.280 --> 00:12:01.290 align:start position:0% with the corruption case when Alice and 00:12:01.290 --> 00:12:05.440 align:start position:0% with the corruption case when Alice and Bob<00:12:02.130> are<00:12:02.880> corrupted<00:12:03.630> and<00:12:03.810> they<00:12:04.200> try<00:12:04.380> to<00:12:04.410> cheat 00:12:05.440 --> 00:12:05.450 align:start position:0% Bob are corrupted and they try to cheat 00:12:05.450 --> 00:12:08.450 align:start position:0% Bob are corrupted and they try to cheat Ingrid<00:12:06.450> and<00:12:06.690> try<00:12:07.380> to<00:12:07.440> steal<00:12:07.890> her<00:12:08.040> money<00:12:08.250> so 00:12:08.450 --> 00:12:08.460 align:start position:0% Ingrid and try to steal her money so 00:12:08.460 --> 00:12:10.790 align:start position:0% Ingrid and try to steal her money so they<00:12:08.670> want<00:12:08.880> to<00:12:08.940> steal<00:12:09.270> some<00:12:09.540> is<00:12:09.750> from<00:12:10.170> from<00:12:10.590> her 00:12:10.790 --> 00:12:10.800 align:start position:0% they want to steal some is from from her 00:12:10.800 --> 00:12:13.070 align:start position:0% they want to steal some is from from her and<00:12:11.070> this<00:12:11.790> is<00:12:11.940> like<00:12:12.090> a<00:12:12.120> kind<00:12:12.660> of<00:12:12.720> can<00:12:12.930> be<00:12:13.050> a 00:12:13.070 --> 00:12:13.080 align:start position:0% and this is like a kind of can be a 00:12:13.080 --> 00:12:14.360 align:start position:0% and this is like a kind of can be a difficult<00:12:13.530> case<00:12:13.650> so<00:12:13.860> for<00:12:14.010> example<00:12:14.340> consider 00:12:14.360 --> 00:12:14.370 align:start position:0% difficult case so for example consider 00:12:14.370 --> 00:12:16.730 align:start position:0% difficult case so for example consider the<00:12:14.970> following<00:12:15.000> situation<00:12:15.420> we<00:12:15.930> have<00:12:16.050> a<00:12:16.080> again 00:12:16.730 --> 00:12:16.740 align:start position:0% the following situation we have a again 00:12:16.740 --> 00:12:19.190 align:start position:0% the following situation we have a again a<00:12:16.770> virtual<00:12:17.190> led<00:12:17.940> a<00:12:17.970> virtual<00:12:18.480> state<00:12:18.870> channel 00:12:19.190 --> 00:12:19.200 align:start position:0% a virtual led a virtual state channel 00:12:19.200 --> 00:12:22.940 align:start position:0% a virtual led a virtual state channel between<00:12:19.350> Alice<00:12:19.830> and<00:12:19.860> Bob<00:12:20.550> and<00:12:21.230> we<00:12:22.230> are<00:12:22.410> having 00:12:22.940 --> 00:12:22.950 align:start position:0% between Alice and Bob and we are having 00:12:22.950 --> 00:12:25.400 align:start position:0% between Alice and Bob and we are having a<00:12:23.070> rerun<00:12:23.580> a<00:12:23.640> contract<00:12:24.090> and<00:12:24.420> this<00:12:24.720> contract<00:12:25.140> has 00:12:25.400 --> 00:12:25.410 align:start position:0% a rerun a contract and this contract has 00:12:25.410 --> 00:12:27.740 align:start position:0% a rerun a contract and this contract has the<00:12:25.500> following<00:12:25.680> property<00:12:26.190> that<00:12:26.760> if<00:12:27.030> state<00:12:27.540> n 00:12:27.740 --> 00:12:27.750 align:start position:0% the following property that if state n 00:12:27.750 --> 00:12:30.410 align:start position:0% the following property that if state n minus<00:12:28.320> 1<00:12:28.500> is<00:12:28.680> set<00:12:28.860> by<00:12:28.980> n<00:12:29.130> minus<00:12:29.400> 1<00:12:29.430> it<00:12:29.700> pays<00:12:29.880> 5<00:12:30.150> is 00:12:30.410 --> 00:12:30.420 align:start position:0% minus 1 is set by n minus 1 it pays 5 is 00:12:30.420 --> 00:12:33.710 align:start position:0% minus 1 is set by n minus 1 it pays 5 is to<00:12:30.630> Bob<00:12:30.840> and<00:12:31.080> in<00:12:31.470> state<00:12:31.740> n<00:12:31.980> it<00:12:32.190> pays<00:12:32.370> 5<00:12:32.670> is<00:12:32.970> to 00:12:33.710 --> 00:12:33.720 align:start position:0% to Bob and in state n it pays 5 is to 00:12:33.720 --> 00:12:36.470 align:start position:0% to Bob and in state n it pays 5 is to Alice<00:12:34.410> ok<00:12:34.830> so<00:12:34.890> now<00:12:35.730> what<00:12:35.910> Alice<00:12:36.180> and<00:12:36.330> Bob<00:12:36.450> can 00:12:36.470 --> 00:12:36.480 align:start position:0% Alice ok so now what Alice and Bob can 00:12:36.480 --> 00:12:39.920 align:start position:0% Alice ok so now what Alice and Bob can do<00:12:36.900> to<00:12:37.140> try<00:12:37.380> to<00:12:37.410> cheat<00:12:38.510> Ingrid<00:12:39.510> for<00:12:39.690> her<00:12:39.780> money 00:12:39.920 --> 00:12:39.930 align:start position:0% do to try to cheat Ingrid for her money 00:12:39.930 --> 00:12:42.650 align:start position:0% do to try to cheat Ingrid for her money they<00:12:40.260> could<00:12:40.470> try<00:12:41.070> to<00:12:41.130> submit<00:12:41.970> in<00:12:42.390> the 00:12:42.650 --> 00:12:42.660 align:start position:0% they could try to submit in the 00:12:42.660 --> 00:12:44.540 align:start position:0% they could try to submit in the underlying<00:12:42.960> legislation<00:12:43.440> Al's<00:12:44.190> because<00:12:44.400> I 00:12:44.540 --> 00:12:44.550 align:start position:0% underlying legislation Al's because I 00:12:44.550 --> 00:12:46.310 align:start position:0% underlying legislation Al's because I said<00:12:44.850> this<00:12:45.000> underlying<00:12:45.510> legislation<00:12:45.690> else 00:12:46.310 --> 00:12:46.320 align:start position:0% said this underlying legislation else 00:12:46.320 --> 00:12:48.890 align:start position:0% said this underlying legislation else take<00:12:46.500> the<00:12:46.530> role<00:12:46.860> of<00:12:46.940> the<00:12:47.940> blockchain<00:12:48.210> the 00:12:48.890 --> 00:12:48.900 align:start position:0% take the role of the blockchain the 00:12:48.900 --> 00:12:50.750 align:start position:0% take the role of the blockchain the accept<00:12:49.170> MIT<00:12:49.350> in<00:12:49.530> these<00:12:49.740> underlying<00:12:50.190> lesson 00:12:50.750 --> 00:12:50.760 align:start position:0% accept MIT in these underlying lesson 00:12:50.760 --> 00:12:52.370 align:start position:0% accept MIT in these underlying lesson state<00:12:51.030> channels<00:12:51.390> these<00:12:51.540> conflicting<00:12:52.110> states 00:12:52.370 --> 00:12:52.380 align:start position:0% state channels these conflicting states 00:12:52.380 --> 00:12:54.590 align:start position:0% state channels these conflicting states and<00:12:52.700> this<00:12:53.700> would<00:12:53.880> result<00:12:54.060> in<00:12:54.360> the<00:12:54.480> following 00:12:54.590 --> 00:12:54.600 align:start position:0% and this would result in the following 00:12:54.600 --> 00:12:56.930 align:start position:0% and this would result in the following situation<00:12:55.380> if<00:12:55.560> you<00:12:55.680> don't<00:12:55.860> design<00:12:56.790> a 00:12:56.930 --> 00:12:56.940 align:start position:0% situation if you don't design a 00:12:56.940 --> 00:12:59.510 align:start position:0% situation if you don't design a carefully<00:12:57.600> develop<00:12:58.590> protocol<00:12:58.950> then<00:12:59.190> it<00:12:59.370> would 00:12:59.510 --> 00:12:59.520 align:start position:0% carefully develop protocol then it would 00:12:59.520 --> 00:13:02.210 align:start position:0% carefully develop protocol then it would result<00:12:59.820> in<00:13:00.030> the<00:13:00.120> situation<00:13:00.630> that<00:13:00.660> LS<00:13:01.470> the 00:13:02.210 --> 00:13:02.220 align:start position:0% result in the situation that LS the 00:13:02.220 --> 00:13:04.400 align:start position:0% result in the situation that LS the corrupted<00:13:02.790> LS<00:13:03.030> wins<00:13:03.240> five<00:13:03.450> coins<00:13:03.840> to<00:13:04.170> corrupt 00:13:04.400 --> 00:13:04.410 align:start position:0% corrupted LS wins five coins to corrupt 00:13:04.410 --> 00:13:06.740 align:start position:0% corrupted LS wins five coins to corrupt the<00:13:04.500> Bob<00:13:04.680> who<00:13:05.040> wins<00:13:05.220> five<00:13:05.400> coins<00:13:05.730> but<00:13:06.330> Ingrid 00:13:06.740 --> 00:13:06.750 align:start position:0% the Bob who wins five coins but Ingrid 00:13:06.750 --> 00:13:09.110 align:start position:0% the Bob who wins five coins but Ingrid who<00:13:06.900> just<00:13:07.340> who's<00:13:08.340> just<00:13:08.610> played<00:13:08.820> the<00:13:08.970> role<00:13:09.090> of 00:13:09.110 --> 00:13:09.120 align:start position:0% who just who's just played the role of 00:13:09.120 --> 00:13:10.520 align:start position:0% who just who's just played the role of the<00:13:09.210> intermediary<00:13:09.810> she<00:13:09.990> was<00:13:10.140> not<00:13:10.350> even 00:13:10.520 --> 00:13:10.530 align:start position:0% the intermediary she was not even 00:13:10.530 --> 00:13:11.660 align:start position:0% the intermediary she was not even involved<00:13:10.800> in<00:13:11.010> this<00:13:11.160> contract 00:13:11.660 --> 00:13:11.670 align:start position:0% involved in this contract 00:13:11.670 --> 00:13:13.910 align:start position:0% involved in this contract she<00:13:12.150> loses<00:13:12.330> 10<00:13:12.660> coins<00:13:12.870> okay<00:13:13.380> so<00:13:13.500> this<00:13:13.740> is 00:13:13.910 --> 00:13:13.920 align:start position:0% she loses 10 coins okay so this is 00:13:13.920 --> 00:13:16.160 align:start position:0% she loses 10 coins okay so this is something<00:13:14.670> that<00:13:14.790> we<00:13:14.880> want<00:13:15.090> to<00:13:15.120> prevent<00:13:15.450> and<00:13:15.750> we 00:13:16.160 --> 00:13:16.170 align:start position:0% something that we want to prevent and we 00:13:16.170 --> 00:13:19.010 align:start position:0% something that we want to prevent and we can<00:13:16.320> do<00:13:16.440> this<00:13:16.590> by<00:13:16.830> using<00:13:17.220> the<00:13:17.580> by<00:13:18.480> developing<00:13:18.930> a 00:13:19.010 --> 00:13:19.020 align:start position:0% can do this by using the by developing a 00:13:19.020 --> 00:13:20.269 align:start position:0% can do this by using the by developing a carefully<00:13:19.440> designed 00:13:20.269 --> 00:13:20.279 align:start position:0% carefully designed 00:13:20.279 --> 00:13:22.670 align:start position:0% carefully designed called<00:13:20.459> in<00:13:20.939> particular<00:13:21.240> using<00:13:22.050> timings<00:13:22.499> or 00:13:22.670 --> 00:13:22.680 align:start position:0% called in particular using timings or 00:13:22.680 --> 00:13:24.530 align:start position:0% called in particular using timings or carefully<00:13:23.009> chosen<00:13:23.220> timings<00:13:23.699> to<00:13:24.149> deal<00:13:24.360> with 00:13:24.530 --> 00:13:24.540 align:start position:0% carefully chosen timings to deal with 00:13:24.540 --> 00:13:27.949 align:start position:0% carefully chosen timings to deal with these<00:13:24.689> special<00:13:25.290> cases<00:13:26.449> unfortunately<00:13:27.449> this 00:13:27.949 --> 00:13:27.959 align:start position:0% these special cases unfortunately this 00:13:27.959 --> 00:13:29.420 align:start position:0% these special cases unfortunately this is<00:13:28.139> like<00:13:28.290> very<00:13:28.470> simple<00:13:28.740> cases<00:13:28.889> only<00:13:29.129> and<00:13:29.370> it 00:13:29.420 --> 00:13:29.430 align:start position:0% is like very simple cases only and it 00:13:29.430 --> 00:13:30.619 align:start position:0% is like very simple cases only and it gets<00:13:29.579> much<00:13:29.759> more<00:13:29.910> complicated<00:13:30.449> in<00:13:30.540> our 00:13:30.619 --> 00:13:30.629 align:start position:0% gets much more complicated in our 00:13:30.629 --> 00:13:32.210 align:start position:0% gets much more complicated in our situation<00:13:31.170> so<00:13:31.290> we<00:13:31.379> have<00:13:31.529> this<00:13:31.680> complicated 00:13:32.210 --> 00:13:32.220 align:start position:0% situation so we have this complicated 00:13:32.220 --> 00:13:34.100 align:start position:0% situation so we have this complicated Network<00:13:32.610> and<00:13:32.850> now<00:13:32.970> we<00:13:33.029> want<00:13:33.360> to<00:13:33.449> handle<00:13:33.959> also 00:13:34.100 --> 00:13:34.110 align:start position:0% Network and now we want to handle also 00:13:34.110 --> 00:13:36.319 align:start position:0% Network and now we want to handle also full<00:13:34.410> concurrent<00:13:34.860> protocol<00:13:35.220> execution<00:13:35.790> so 00:13:36.319 --> 00:13:36.329 align:start position:0% full concurrent protocol execution so 00:13:36.329 --> 00:13:37.610 align:start position:0% full concurrent protocol execution so many<00:13:36.509> things<00:13:36.749> can<00:13:36.959> happen<00:13:37.110> in<00:13:37.319> parallel 00:13:37.610 --> 00:13:37.620 align:start position:0% many things can happen in parallel 00:13:37.620 --> 00:13:40.160 align:start position:0% many things can happen in parallel packets<00:13:38.519> can<00:13:38.639> open<00:13:39.029> contracts<00:13:39.569> in<00:13:39.720> parallel 00:13:40.160 --> 00:13:40.170 align:start position:0% packets can open contracts in parallel 00:13:40.170 --> 00:13:42.230 align:start position:0% packets can open contracts in parallel for<00:13:40.709> example<00:13:41.069> here<00:13:41.189> this<00:13:41.399> middle<00:13:41.579> party<00:13:42.029> here 00:13:42.230 --> 00:13:42.240 align:start position:0% for example here this middle party here 00:13:42.240 --> 00:13:45.739 align:start position:0% for example here this middle party here she<00:13:42.480> is<00:13:42.509> involved<00:13:42.899> in<00:13:43.199> two<00:13:43.769> virtual<00:13:44.749> state 00:13:45.739 --> 00:13:45.749 align:start position:0% she is involved in two virtual state 00:13:45.749 --> 00:13:48.079 align:start position:0% she is involved in two virtual state channels<00:13:46.170> and<00:13:46.379> she<00:13:46.410> runs<00:13:46.709> possibly<00:13:47.579> several 00:13:48.079 --> 00:13:48.089 align:start position:0% channels and she runs possibly several 00:13:48.089 --> 00:13:50.449 align:start position:0% channels and she runs possibly several contracts<00:13:48.689> and<00:13:48.839> them<00:13:49.050> in<00:13:49.410> parallel<00:13:49.769> and<00:13:50.370> they 00:13:50.449 --> 00:13:50.459 align:start position:0% contracts and them in parallel and they 00:13:50.459 --> 00:13:53.299 align:start position:0% contracts and them in parallel and they can<00:13:50.579> also<00:13:50.699> be<00:13:50.790> many<00:13:51.740> corrupted<00:13:52.740> parties<00:13:53.069> and 00:13:53.299 --> 00:13:53.309 align:start position:0% can also be many corrupted parties and 00:13:53.309 --> 00:13:55.309 align:start position:0% can also be many corrupted parties and of<00:13:53.490> course<00:13:53.699> we<00:13:53.879> want<00:13:54.059> to<00:13:54.209> deal<00:13:54.420> with<00:13:55.170> this 00:13:55.309 --> 00:13:55.319 align:start position:0% of course we want to deal with this 00:13:55.319 --> 00:13:56.869 align:start position:0% of course we want to deal with this situation<00:13:55.499> okay<00:13:56.129> so<00:13:56.249> we<00:13:56.459> want<00:13:56.579> to<00:13:56.730> design 00:13:56.869 --> 00:13:56.879 align:start position:0% situation okay so we want to design 00:13:56.879 --> 00:14:01.160 align:start position:0% situation okay so we want to design protocol<00:13:57.540> that<00:13:57.720> even<00:13:58.050> is<00:13:58.199> secure<00:13:59.449> when<00:14:00.449> there 00:14:01.160 --> 00:14:01.170 align:start position:0% protocol that even is secure when there 00:14:01.170 --> 00:14:02.689 align:start position:0% protocol that even is secure when there are<00:14:01.230> so<00:14:01.379> many<00:14:01.499> corrupted<00:14:01.980> parties<00:14:02.309> when<00:14:02.519> so 00:14:02.689 --> 00:14:02.699 align:start position:0% are so many corrupted parties when so 00:14:02.699 --> 00:14:04.309 align:start position:0% are so many corrupted parties when so many<00:14:02.879> things<00:14:03.089> happen<00:14:03.360> in<00:14:03.449> parallel<00:14:03.779> when 00:14:04.309 --> 00:14:04.319 align:start position:0% many things happen in parallel when 00:14:04.319 --> 00:14:05.900 align:start position:0% many things happen in parallel when these<00:14:04.499> all<00:14:04.649> these<00:14:04.769> messages<00:14:05.100> are<00:14:05.370> exchanged 00:14:05.900 --> 00:14:05.910 align:start position:0% these all these messages are exchanged 00:14:05.910 --> 00:14:07.489 align:start position:0% these all these messages are exchanged and<00:14:05.970> the<00:14:06.569> protocol<00:14:06.930> should<00:14:06.959> guarantee 00:14:07.489 --> 00:14:07.499 align:start position:0% and the protocol should guarantee 00:14:07.499 --> 00:14:09.889 align:start position:0% and the protocol should guarantee security<00:14:08.490> the<00:14:08.670> security<00:14:09.180> requirements<00:14:09.449> that 00:14:09.889 --> 00:14:09.899 align:start position:0% security the security requirements that 00:14:09.899 --> 00:14:12.829 align:start position:0% security the security requirements that we<00:14:10.170> specified<00:14:10.970> so<00:14:11.970> how<00:14:12.059> can<00:14:12.120> we<00:14:12.329> design<00:14:12.449> such<00:14:12.809> a 00:14:12.829 --> 00:14:12.839 align:start position:0% we specified so how can we design such a 00:14:12.839 --> 00:14:15.739 align:start position:0% we specified so how can we design such a complex<00:14:13.230> protocol<00:14:13.680> and<00:14:13.920> for<00:14:14.610> this<00:14:14.759> we<00:14:15.029> rely<00:14:15.480> on 00:14:15.739 --> 00:14:15.749 align:start position:0% complex protocol and for this we rely on 00:14:15.749 --> 00:14:18.619 align:start position:0% complex protocol and for this we rely on what<00:14:16.470> is<00:14:17.040> essentially<00:14:17.879> the<00:14:17.910> approach<00:14:18.420> of 00:14:18.619 --> 00:14:18.629 align:start position:0% what is essentially the approach of 00:14:18.629 --> 00:14:20.629 align:start position:0% what is essentially the approach of modern<00:14:18.899> cryptography<00:14:19.170> which<00:14:19.680> uses<00:14:20.339> what<00:14:20.610> I 00:14:20.629 --> 00:14:20.639 align:start position:0% modern cryptography which uses what I 00:14:20.639 --> 00:14:22.660 align:start position:0% modern cryptography which uses what I mentioned<00:14:20.910> the<00:14:21.120> beginning<00:14:21.480> security<00:14:22.319> proves 00:14:22.660 --> 00:14:22.670 align:start position:0% mentioned the beginning security proves 00:14:22.670 --> 00:14:26.360 align:start position:0% mentioned the beginning security proves to<00:14:23.670> kind<00:14:23.970> of<00:14:24.059> design<00:14:24.449> the<00:14:24.990> protocol<00:14:25.470> using<00:14:26.309> a 00:14:26.360 --> 00:14:26.370 align:start position:0% to kind of design the protocol using a 00:14:26.370 --> 00:14:29.240 align:start position:0% to kind of design the protocol using a sound<00:14:26.519> methodology<00:14:26.970> so<00:14:27.750> this<00:14:28.019> approach<00:14:28.980> of 00:14:29.240 --> 00:14:29.250 align:start position:0% sound methodology so this approach of 00:14:29.250 --> 00:14:30.650 align:start position:0% sound methodology so this approach of modern<00:14:29.519> cryptography<00:14:29.730> which<00:14:30.209> we<00:14:30.509> use 00:14:30.650 --> 00:14:30.660 align:start position:0% modern cryptography which we use 00:14:30.660 --> 00:14:32.420 align:start position:0% modern cryptography which we use essentially<00:14:31.199> for<00:14:31.410> designing<00:14:31.709> cryptographic 00:14:32.420 --> 00:14:32.430 align:start position:0% essentially for designing cryptographic 00:14:32.430 --> 00:14:35.119 align:start position:0% essentially for designing cryptographic protocols<00:14:33.139> like<00:14:34.139> whatever<00:14:34.620> encryption 00:14:35.119 --> 00:14:35.129 align:start position:0% protocols like whatever encryption 00:14:35.129 --> 00:14:37.309 align:start position:0% protocols like whatever encryption schemes<00:14:35.370> are<00:14:35.519> more<00:14:35.639> complicated<00:14:35.850> schemes<00:14:36.329> it 00:14:37.309 --> 00:14:37.319 align:start position:0% schemes are more complicated schemes it 00:14:37.319 --> 00:14:39.769 align:start position:0% schemes are more complicated schemes it works<00:14:37.529> like<00:14:37.709> this<00:14:37.829> that<00:14:38.189> you<00:14:38.610> first<00:14:38.910> specify 00:14:39.769 --> 00:14:39.779 align:start position:0% works like this that you first specify 00:14:39.779 --> 00:14:42.530 align:start position:0% works like this that you first specify what<00:14:40.230> is<00:14:40.350> your<00:14:40.620> security<00:14:41.339> definition<00:14:42.000> so<00:14:42.509> you 00:14:42.530 --> 00:14:42.540 align:start position:0% what is your security definition so you 00:14:42.540 --> 00:14:44.780 align:start position:0% what is your security definition so you what<00:14:43.110> do<00:14:43.589> you<00:14:43.620> want<00:14:43.889> that<00:14:44.399> the<00:14:44.519> protocol 00:14:44.780 --> 00:14:44.790 align:start position:0% what do you want that the protocol 00:14:44.790 --> 00:14:47.179 align:start position:0% what do you want that the protocol actually<00:14:45.360> should<00:14:45.509> achieve<00:14:45.809> then<00:14:46.649> we<00:14:46.829> design 00:14:47.179 --> 00:14:47.189 align:start position:0% actually should achieve then we design 00:14:47.189 --> 00:14:49.939 align:start position:0% actually should achieve then we design the<00:14:47.639> protocol<00:14:48.089> so<00:14:48.600> we<00:14:48.709> come<00:14:49.709> up<00:14:49.800> with<00:14:49.920> a 00:14:49.939 --> 00:14:49.949 align:start position:0% the protocol so we come up with a 00:14:49.949 --> 00:14:52.129 align:start position:0% the protocol so we come up with a candidate<00:14:50.819> scheme<00:14:51.149> that<00:14:51.389> hopefully<00:14:51.839> achieves 00:14:52.129 --> 00:14:52.139 align:start position:0% candidate scheme that hopefully achieves 00:14:52.139 --> 00:14:55.220 align:start position:0% candidate scheme that hopefully achieves the<00:14:52.319> security<00:14:52.769> definition<00:14:53.220> and<00:14:53.610> once<00:14:54.389> we<00:14:54.600> have 00:14:55.220 --> 00:14:55.230 align:start position:0% the security definition and once we have 00:14:55.230 --> 00:14:58.369 align:start position:0% the security definition and once we have done<00:14:55.920> this<00:14:56.100> then<00:14:56.430> we<00:14:57.329> prove<00:14:57.629> its<00:14:57.839> security 00:14:58.369 --> 00:14:58.379 align:start position:0% done this then we prove its security 00:14:58.379 --> 00:15:02.329 align:start position:0% done this then we prove its security okay<00:14:58.860> so<00:14:59.329> at<00:15:00.329> the<00:15:00.420> point<00:15:00.600> so<00:15:01.439> okay<00:15:01.949> we<00:15:02.160> prove 00:15:02.329 --> 00:15:02.339 align:start position:0% okay so at the point so okay we prove 00:15:02.339 --> 00:15:04.790 align:start position:0% okay so at the point so okay we prove its<00:15:02.459> security<00:15:02.850> so<00:15:03.120> at<00:15:04.079> the<00:15:04.170> point<00:15:04.350> then<00:15:04.589> of 00:15:04.790 --> 00:15:04.800 align:start position:0% its security so at the point then of 00:15:04.800 --> 00:15:06.530 align:start position:0% its security so at the point then of course<00:15:05.040> this<00:15:05.189> process<00:15:05.370> is<00:15:05.759> not<00:15:05.939> like<00:15:06.089> so<00:15:06.269> nice 00:15:06.530 --> 00:15:06.540 align:start position:0% course this process is not like so nice 00:15:06.540 --> 00:15:09.079 align:start position:0% course this process is not like so nice as<00:15:06.750> I<00:15:06.870> showed<00:15:07.170> to<00:15:07.319> you<00:15:07.379> here<00:15:07.769> okay<00:15:08.189> it's<00:15:08.879> like 00:15:09.079 --> 00:15:09.089 align:start position:0% as I showed to you here okay it's like 00:15:09.089 --> 00:15:13.699 align:start position:0% as I showed to you here okay it's like iterative<00:15:09.660> way<00:15:09.959> so<00:15:11.509> we<00:15:12.509> sometimes<00:15:12.839> you<00:15:13.589> come 00:15:13.699 --> 00:15:13.709 align:start position:0% iterative way so we sometimes you come 00:15:13.709 --> 00:15:15.019 align:start position:0% iterative way so we sometimes you come up<00:15:13.800> with<00:15:13.829> the<00:15:13.980> candidate<00:15:14.309> scheme<00:15:14.579> we<00:15:14.790> find 00:15:15.019 --> 00:15:15.029 align:start position:0% up with the candidate scheme we find 00:15:15.029 --> 00:15:16.790 align:start position:0% up with the candidate scheme we find some<00:15:15.240> problem<00:15:15.660> in<00:15:15.720> this<00:15:15.839> candidate<00:15:16.199> scheme<00:15:16.499> so 00:15:16.790 --> 00:15:16.800 align:start position:0% some problem in this candidate scheme so 00:15:16.800 --> 00:15:18.650 align:start position:0% some problem in this candidate scheme so when<00:15:17.399> we<00:15:17.550> try<00:15:17.699> to<00:15:17.790> prove<00:15:18.029> it<00:15:18.209> so<00:15:18.389> the<00:15:18.480> proof 00:15:18.650 --> 00:15:18.660 align:start position:0% when we try to prove it so the proof 00:15:18.660 --> 00:15:20.989 align:start position:0% when we try to prove it so the proof course<00:15:18.929> fails<00:15:19.740> okay<00:15:20.399> so<00:15:20.459> that's<00:15:20.790> the<00:15:20.879> nice 00:15:20.989 --> 00:15:20.999 align:start position:0% course fails okay so that's the nice 00:15:20.999 --> 00:15:22.489 align:start position:0% course fails okay so that's the nice thing<00:15:21.059> about<00:15:21.300> it<00:15:21.600> it's<00:15:21.839> gives<00:15:22.139> you<00:15:22.259> a<00:15:22.290> sound 00:15:22.489 --> 00:15:22.499 align:start position:0% thing about it it's gives you a sound 00:15:22.499 --> 00:15:24.829 align:start position:0% thing about it it's gives you a sound methodology<00:15:23.189> so<00:15:23.610> to<00:15:23.670> say<00:15:23.879> so<00:15:24.059> the<00:15:24.420> proof<00:15:24.569> fails 00:15:24.829 --> 00:15:24.839 align:start position:0% methodology so to say so the proof fails 00:15:24.839 --> 00:15:27.230 align:start position:0% methodology so to say so the proof fails we<00:15:25.470> have<00:15:25.499> to<00:15:25.679> adjust<00:15:25.860> the<00:15:26.009> protocol<00:15:26.459> and<00:15:26.730> then 00:15:27.230 --> 00:15:27.240 align:start position:0% we have to adjust the protocol and then 00:15:27.240 --> 00:15:30.139 align:start position:0% we have to adjust the protocol and then we<00:15:28.199> try<00:15:28.379> to<00:15:28.410> again<00:15:28.649> prove<00:15:28.920> it<00:15:29.100> we<00:15:29.399> fail<00:15:29.639> we<00:15:29.970> try 00:15:30.139 --> 00:15:30.149 align:start position:0% we try to again prove it we fail we try 00:15:30.149 --> 00:15:32.030 align:start position:0% we try to again prove it we fail we try to<00:15:30.209> again<00:15:30.449> prove<00:15:30.660> so<00:15:31.199> we<00:15:31.319> could<00:15:31.439> try<00:15:31.559> to<00:15:31.620> adjust 00:15:32.030 --> 00:15:32.040 align:start position:0% to again prove so we could try to adjust 00:15:32.040 --> 00:15:33.470 align:start position:0% to again prove so we could try to adjust it<00:15:32.189> we<00:15:32.339> try<00:15:32.490> to<00:15:32.550> again<00:15:32.699> food<00:15:32.910> and<00:15:33.120> so<00:15:33.179> on<00:15:33.300> and<00:15:33.420> so 00:15:33.470 --> 00:15:33.480 align:start position:0% it we try to again food and so on and so 00:15:33.480 --> 00:15:33.950 align:start position:0% it we try to again food and so on and so forth 00:15:33.950 --> 00:15:33.960 align:start position:0% forth 00:15:33.960 --> 00:15:36.350 align:start position:0% forth at<00:15:34.170> some<00:15:34.320> point<00:15:34.529> hopefully<00:15:34.850> then<00:15:35.850> we<00:15:36.180> have<00:15:36.330> a 00:15:36.350 --> 00:15:36.360 align:start position:0% at some point hopefully then we have a 00:15:36.360 --> 00:15:38.720 align:start position:0% at some point hopefully then we have a security<00:15:36.750> proof<00:15:37.080> that<00:15:37.230> our<00:15:37.410> protocol<00:15:37.920> the<00:15:38.550> our 00:15:38.720 --> 00:15:38.730 align:start position:0% security proof that our protocol the our 00:15:38.730 --> 00:15:41.000 align:start position:0% security proof that our protocol the our protocol<00:15:39.149> specification<00:15:39.839> guarantees<00:15:40.710> the 00:15:41.000 --> 00:15:41.010 align:start position:0% protocol specification guarantees the 00:15:41.010 --> 00:15:43.040 align:start position:0% protocol specification guarantees the security<00:15:41.490> requirements<00:15:41.670> that<00:15:42.360> we<00:15:42.870> have 00:15:43.040 --> 00:15:43.050 align:start position:0% security requirements that we have 00:15:43.050 --> 00:15:45.110 align:start position:0% security requirements that we have specified<00:15:43.320> earlier<00:15:43.800> in<00:15:44.399> this<00:15:44.580> definition<00:15:44.760> but 00:15:45.110 --> 00:15:45.120 align:start position:0% specified earlier in this definition but 00:15:45.120 --> 00:15:47.750 align:start position:0% specified earlier in this definition but so<00:15:45.930> this<00:15:46.260> is<00:15:46.440> the<00:15:46.950> main<00:15:47.100> benefits<00:15:47.520> of<00:15:47.640> this 00:15:47.750 --> 00:15:47.760 align:start position:0% so this is the main benefits of this 00:15:47.760 --> 00:15:49.130 align:start position:0% so this is the main benefits of this approach<00:15:47.910> is<00:15:48.300> that<00:15:48.330> it<00:15:48.540> provides<00:15:48.810> a<00:15:49.020> sound 00:15:49.130 --> 00:15:49.140 align:start position:0% approach is that it provides a sound 00:15:49.140 --> 00:15:51.440 align:start position:0% approach is that it provides a sound methodology<00:15:49.790> for<00:15:50.790> designing<00:15:51.240> complex 00:15:51.440 --> 00:15:51.450 align:start position:0% methodology for designing complex 00:15:51.450 --> 00:15:54.050 align:start position:0% methodology for designing complex protocols<00:15:51.810> and<00:15:52.290> it<00:15:52.770> also<00:15:53.040> prevents<00:15:53.490> insecure 00:15:54.050 --> 00:15:54.060 align:start position:0% protocols and it also prevents insecure 00:15:54.060 --> 00:15:56.690 align:start position:0% protocols and it also prevents insecure Atok<00:15:54.330> design<00:15:54.660> so<00:15:54.839> there<00:15:54.990> is<00:15:55.080> like<00:15:55.290> maybe<00:15:56.130> some 00:15:56.690 --> 00:15:56.700 align:start position:0% Atok design so there is like maybe some 00:15:56.700 --> 00:15:58.070 align:start position:0% Atok design so there is like maybe some of<00:15:56.730> you<00:15:56.910> have<00:15:57.060> heard<00:15:57.180> about<00:15:57.240> it<00:15:57.600> there's<00:15:57.839> like 00:15:58.070 --> 00:15:58.080 align:start position:0% of you have heard about it there's like 00:15:58.080 --> 00:16:00.680 align:start position:0% of you have heard about it there's like this<00:15:58.860> protocol<00:15:59.160> of<00:15:59.760> this<00:16:00.029> probably<00:16:00.390> most<00:16:00.600> of 00:16:00.680 --> 00:16:00.690 align:start position:0% this protocol of this probably most of 00:16:00.690 --> 00:16:02.870 align:start position:0% this protocol of this probably most of you<00:16:00.810> have<00:16:00.930> heard<00:16:01.020> about<00:16:01.110> TLS<00:16:01.680> okay<00:16:02.070> and<00:16:02.580> it<00:16:02.730> was 00:16:02.870 --> 00:16:02.880 align:start position:0% you have heard about TLS okay and it was 00:16:02.880 --> 00:16:05.060 align:start position:0% you have heard about TLS okay and it was designed<00:16:03.089> in<00:16:03.390> a<00:16:03.510> talk<00:16:03.779> way<00:16:03.990> without<00:16:04.230> having<00:16:04.440> it 00:16:05.060 --> 00:16:05.070 align:start position:0% designed in a talk way without having it 00:16:05.070 --> 00:16:06.740 align:start position:0% designed in a talk way without having it without<00:16:05.310> using<00:16:05.700> this<00:16:05.820> kind<00:16:06.000> of<00:16:06.149> approach<00:16:06.300> of 00:16:06.740 --> 00:16:06.750 align:start position:0% without using this kind of approach of 00:16:06.750 --> 00:16:08.660 align:start position:0% without using this kind of approach of modern<00:16:07.050> cryptography<00:16:07.290> of<00:16:07.770> proofs<00:16:08.190> provable 00:16:08.660 --> 00:16:08.670 align:start position:0% modern cryptography of proofs provable 00:16:08.670 --> 00:16:10.730 align:start position:0% modern cryptography of proofs provable security<00:16:09.180> and<00:16:09.390> it<00:16:10.080> turned<00:16:10.260> out<00:16:10.380> that<00:16:10.589> there 00:16:10.730 --> 00:16:10.740 align:start position:0% security and it turned out that there 00:16:10.740 --> 00:16:12.139 align:start position:0% security and it turned out that there are<00:16:10.770> many<00:16:10.890> kind<00:16:11.220> of<00:16:11.310> bugs<00:16:11.580> in<00:16:11.790> this<00:16:11.880> protocol 00:16:12.139 --> 00:16:12.149 align:start position:0% are many kind of bugs in this protocol 00:16:12.149 --> 00:16:13.610 align:start position:0% are many kind of bugs in this protocol okay<00:16:12.480> so<00:16:12.540> there<00:16:12.839> are<00:16:12.870> many<00:16:13.020> people<00:16:13.230> found 00:16:13.610 --> 00:16:13.620 align:start position:0% okay so there are many people found 00:16:13.620 --> 00:16:15.860 align:start position:0% okay so there are many people found problems<00:16:14.339> and<00:16:14.820> now<00:16:15.270> they<00:16:15.420> are<00:16:15.480> trying<00:16:15.630> to<00:16:15.720> fix 00:16:15.860 --> 00:16:15.870 align:start position:0% problems and now they are trying to fix 00:16:15.870 --> 00:16:17.510 align:start position:0% problems and now they are trying to fix it<00:16:16.080> it's<00:16:16.350> a<00:16:16.470> kind<00:16:16.649> of<00:16:16.709> a<00:16:16.800> cat-and-mouse<00:16:17.010> game 00:16:17.510 --> 00:16:17.520 align:start position:0% it it's a kind of a cat-and-mouse game 00:16:17.520 --> 00:16:19.579 align:start position:0% it it's a kind of a cat-and-mouse game and<00:16:18.089> we<00:16:18.209> want<00:16:18.360> to<00:16:18.480> prevent<00:16:18.839> this<00:16:18.990> from<00:16:19.200> the 00:16:19.579 --> 00:16:19.589 align:start position:0% and we want to prevent this from the 00:16:19.589 --> 00:16:21.260 align:start position:0% and we want to prevent this from the start<00:16:19.770> and<00:16:20.190> actually<00:16:20.459> now<00:16:20.790> in<00:16:21.000> the<00:16:21.089> new 00:16:21.260 --> 00:16:21.270 align:start position:0% start and actually now in the new 00:16:21.270 --> 00:16:24.440 align:start position:0% start and actually now in the new version<00:16:21.690> of<00:16:21.810> TLS<00:16:22.320> people<00:16:23.250> decided<00:16:24.240> to<00:16:24.330> use 00:16:24.440 --> 00:16:24.450 align:start position:0% version of TLS people decided to use 00:16:24.450 --> 00:16:26.420 align:start position:0% version of TLS people decided to use security<00:16:24.959> proofs<00:16:25.170> to<00:16:25.440> develop<00:16:26.070> the<00:16:26.160> protocols 00:16:26.420 --> 00:16:26.430 align:start position:0% security proofs to develop the protocols 00:16:26.430 --> 00:16:28.550 align:start position:0% security proofs to develop the protocols so<00:16:27.240> we<00:16:27.330> believe<00:16:27.480> that<00:16:27.630> we<00:16:27.959> should<00:16:28.110> also<00:16:28.290> do 00:16:28.550 --> 00:16:28.560 align:start position:0% so we believe that we should also do 00:16:28.560 --> 00:16:30.590 align:start position:0% so we believe that we should also do this<00:16:28.680> from<00:16:28.950> this<00:16:29.100> from<00:16:29.610> the<00:16:29.700> start<00:16:29.910> with 00:16:30.590 --> 00:16:30.600 align:start position:0% this from this from the start with 00:16:30.600 --> 00:16:32.090 align:start position:0% this from this from the start with something<00:16:30.810> as<00:16:31.080> complicated<00:16:31.410> as<00:16:31.830> state 00:16:32.090 --> 00:16:32.100 align:start position:0% something as complicated as state 00:16:32.100 --> 00:16:35.540 align:start position:0% something as complicated as state channel<00:16:32.370> networks<00:16:33.350> so<00:16:34.350> what<00:16:34.470> is<00:16:34.560> our<00:16:34.680> basic 00:16:35.540 --> 00:16:35.550 align:start position:0% channel networks so what is our basic 00:16:35.550 --> 00:16:37.340 align:start position:0% channel networks so what is our basic framework<00:16:36.000> to<00:16:36.120> use<00:16:36.300> this<00:16:36.510> this<00:16:36.750> is<00:16:36.870> the 00:16:37.340 --> 00:16:37.350 align:start position:0% framework to use this this is the 00:16:37.350 --> 00:16:38.720 align:start position:0% framework to use this this is the quality<00:16:37.620> universal<00:16:38.070> comm<00:16:38.220> possibility 00:16:38.720 --> 00:16:38.730 align:start position:0% quality universal comm possibility 00:16:38.730 --> 00:16:41.180 align:start position:0% quality universal comm possibility framework<00:16:39.150> and<00:16:39.360> some<00:16:40.050> time<00:16:40.290> ago<00:16:40.320> we<00:16:40.980> gave<00:16:41.130> a 00:16:41.180 --> 00:16:41.190 align:start position:0% framework and some time ago we gave a 00:16:41.190 --> 00:16:42.890 align:start position:0% framework and some time ago we gave a talks<00:16:41.550> if<00:16:41.790> you<00:16:41.850> gave<00:16:42.000> some<00:16:42.180> talks<00:16:42.390> at<00:16:42.630> the 00:16:42.890 --> 00:16:42.900 align:start position:0% talks if you gave some talks at the 00:16:42.900 --> 00:16:45.500 align:start position:0% talks if you gave some talks at the workshop<00:16:43.740> in<00:16:44.160> Berlin<00:16:44.790> and<00:16:44.880> everybody<00:16:45.270> liked 00:16:45.500 --> 00:16:45.510 align:start position:0% workshop in Berlin and everybody liked 00:16:45.510 --> 00:16:47.150 align:start position:0% workshop in Berlin and everybody liked this<00:16:45.690> universal<00:16:46.140> compatibility<00:16:46.440> framework 00:16:47.150 --> 00:16:47.160 align:start position:0% this universal compatibility framework 00:16:47.160 --> 00:16:48.440 align:start position:0% this universal compatibility framework so<00:16:47.310> I<00:16:47.339> would<00:16:47.580> like<00:16:47.730> to<00:16:47.880> mention<00:16:48.000> it<00:16:48.240> here<00:16:48.390> as 00:16:48.440 --> 00:16:48.450 align:start position:0% so I would like to mention it here as 00:16:48.450 --> 00:16:50.930 align:start position:0% so I would like to mention it here as well<00:16:48.660> so<00:16:49.320> this<00:16:49.529> is<00:16:49.650> basically<00:16:50.040> how<00:16:50.279> we<00:16:50.339> kind<00:16:50.820> of 00:16:50.930 --> 00:16:50.940 align:start position:0% well so this is basically how we kind of 00:16:50.940 --> 00:16:53.210 align:start position:0% well so this is basically how we kind of define<00:16:51.270> security<00:16:51.570> what<00:16:52.290> actually<00:16:52.770> security 00:16:53.210 --> 00:16:53.220 align:start position:0% define security what actually security 00:16:53.220 --> 00:16:55.310 align:start position:0% define security what actually security means<00:16:53.400> okay<00:16:53.670> so<00:16:53.730> so<00:16:54.510> we<00:16:54.750> have<00:16:54.900> these<00:16:55.050> two 00:16:55.310 --> 00:16:55.320 align:start position:0% means okay so so we have these two 00:16:55.320 --> 00:16:57.550 align:start position:0% means okay so so we have these two worlds<00:16:55.770> ideal<00:16:56.490> world<00:16:56.820> and<00:16:57.029> the<00:16:57.150> real<00:16:57.330> world 00:16:57.550 --> 00:16:57.560 align:start position:0% worlds ideal world and the real world 00:16:57.560 --> 00:17:00.530 align:start position:0% worlds ideal world and the real world the<00:16:58.560> ideal<00:16:58.830> world<00:16:59.070> is<00:16:59.279> some<00:16:59.730> kind<00:16:59.910> of<00:16:59.970> abstract 00:17:00.530 --> 00:17:00.540 align:start position:0% the ideal world is some kind of abstract 00:17:00.540 --> 00:17:02.870 align:start position:0% the ideal world is some kind of abstract specification<00:17:00.930> of<00:17:01.680> what<00:17:01.980> kind<00:17:02.550> of<00:17:02.610> security 00:17:02.870 --> 00:17:02.880 align:start position:0% specification of what kind of security 00:17:02.880 --> 00:17:05.120 align:start position:0% specification of what kind of security properties<00:17:03.480> the<00:17:04.199> protocol<00:17:04.620> should<00:17:04.650> satisfy 00:17:05.120 --> 00:17:05.130 align:start position:0% properties the protocol should satisfy 00:17:05.130 --> 00:17:09.169 align:start position:0% properties the protocol should satisfy okay<00:17:05.850> so<00:17:05.929> it's<00:17:06.929> very<00:17:07.199> simple<00:17:07.559> it<00:17:08.220> just<00:17:08.459> can<00:17:09.030> be 00:17:09.169 --> 00:17:09.179 align:start position:0% okay so it's very simple it just can be 00:17:09.179 --> 00:17:11.090 align:start position:0% okay so it's very simple it just can be written<00:17:09.329> maybe<00:17:09.569> on<00:17:09.839> half<00:17:10.380> a<00:17:10.470> page<00:17:10.650> yeah<00:17:10.890> so 00:17:11.090 --> 00:17:11.100 align:start position:0% written maybe on half a page yeah so 00:17:11.100 --> 00:17:12.590 align:start position:0% written maybe on half a page yeah so it's<00:17:11.250> very<00:17:11.370> simple<00:17:11.640> specification<00:17:12.360> of<00:17:12.449> what 00:17:12.590 --> 00:17:12.600 align:start position:0% it's very simple specification of what 00:17:12.600 --> 00:17:15.980 align:start position:0% it's very simple specification of what this<00:17:12.689> protocol<00:17:13.170> it<00:17:13.439> is<00:17:13.500> and<00:17:14.569> then<00:17:15.569> the 00:17:15.980 --> 00:17:15.990 align:start position:0% this protocol it is and then the 00:17:15.990 --> 00:17:18.860 align:start position:0% this protocol it is and then the protocol<00:17:16.260> can<00:17:16.439> be<00:17:16.620> like<00:17:16.920> pages<00:17:17.400> long<00:17:17.579> maybe<00:17:17.880> in 00:17:18.860 --> 00:17:18.870 align:start position:0% protocol can be like pages long maybe in 00:17:18.870 --> 00:17:20.360 align:start position:0% protocol can be like pages long maybe in our<00:17:18.990> case<00:17:19.260> was<00:17:19.439> 2000<00:17:19.860> I<00:17:19.949> don't<00:17:20.130> know<00:17:20.189> whatever 00:17:20.360 --> 00:17:20.370 align:start position:0% our case was 2000 I don't know whatever 00:17:20.370 --> 00:17:23.179 align:start position:0% our case was 2000 I don't know whatever so<00:17:21.089> and<00:17:21.120> now<00:17:22.020> we<00:17:22.050> would<00:17:22.230> like<00:17:22.290> to<00:17:22.589> show<00:17:22.800> that 00:17:23.179 --> 00:17:23.189 align:start position:0% so and now we would like to show that 00:17:23.189 --> 00:17:26.090 align:start position:0% so and now we would like to show that actually<00:17:23.790> this<00:17:23.939> protocol<00:17:24.709> has<00:17:25.709> the<00:17:25.890> same 00:17:26.090 --> 00:17:26.100 align:start position:0% actually this protocol has the same 00:17:26.100 --> 00:17:28.280 align:start position:0% actually this protocol has the same security<00:17:26.760> features<00:17:27.150> then<00:17:27.390> this<00:17:27.600> very<00:17:27.839> compact 00:17:28.280 --> 00:17:28.290 align:start position:0% security features then this very compact 00:17:28.290 --> 00:17:30.080 align:start position:0% security features then this very compact description<00:17:28.860> this<00:17:29.220> very<00:17:29.429> compact<00:17:29.790> RP 00:17:30.080 --> 00:17:30.090 align:start position:0% description this very compact RP 00:17:30.090 --> 00:17:32.060 align:start position:0% description this very compact RP description<00:17:30.600> of<00:17:30.750> the<00:17:31.230> specification<00:17:31.890> and 00:17:32.060 --> 00:17:32.070 align:start position:0% description of the specification and 00:17:32.070 --> 00:17:34.520 align:start position:0% description of the specification and this<00:17:32.760> is<00:17:32.910> done<00:17:33.059> by<00:17:33.270> what<00:17:33.870> is<00:17:33.960> called<00:17:34.170> a<00:17:34.260> you<00:17:34.350> see 00:17:34.520 --> 00:17:34.530 align:start position:0% this is done by what is called a you see 00:17:34.530 --> 00:17:35.990 align:start position:0% this is done by what is called a you see proof<00:17:34.740> a<00:17:34.920> universal<00:17:35.400> comm<00:17:35.520> possibility 00:17:35.990 --> 00:17:36.000 align:start position:0% proof a universal comm possibility 00:17:36.000 --> 00:17:38.570 align:start position:0% proof a universal comm possibility security<00:17:36.960> proof<00:17:37.200> and<00:17:37.500> this<00:17:38.010> essentially 00:17:38.570 --> 00:17:38.580 align:start position:0% security proof and this essentially 00:17:38.580 --> 00:17:41.570 align:start position:0% security proof and this essentially reduces<00:17:39.330> complex<00:17:39.900> protocol<00:17:40.380> to<00:17:41.040> something<00:17:41.460> as 00:17:41.570 --> 00:17:41.580 align:start position:0% reduces complex protocol to something as 00:17:41.580 --> 00:17:44.750 align:start position:0% reduces complex protocol to something as simple<00:17:41.790> as<00:17:42.059> this<00:17:42.240> idea<00:17:42.419> of<00:17:42.660> functionality<00:17:43.760> so 00:17:44.750 --> 00:17:44.760 align:start position:0% simple as this idea of functionality so 00:17:44.760 --> 00:17:46.790 align:start position:0% simple as this idea of functionality so before<00:17:45.419> I<00:17:45.450> run<00:17:46.020> out<00:17:46.050> of<00:17:46.169> time<00:17:46.410> I<00:17:46.470> want<00:17:46.590> to 00:17:46.790 --> 00:17:46.800 align:start position:0% before I run out of time I want to 00:17:46.800 --> 00:17:47.630 align:start position:0% before I run out of time I want to quickly 00:17:47.630 --> 00:17:47.640 align:start position:0% quickly 00:17:47.640 --> 00:17:49.760 align:start position:0% quickly talk<00:17:47.940> about<00:17:48.060> some<00:17:48.420> extensions<00:17:49.080> and<00:17:49.260> implement 00:17:49.760 --> 00:17:49.770 align:start position:0% talk about some extensions and implement 00:17:49.770 --> 00:17:51.880 align:start position:0% talk about some extensions and implement it<00:17:49.890> and<00:17:50.220> also<00:17:50.340> briefly<00:17:50.910> about<00:17:51.060> implementation 00:17:51.880 --> 00:17:51.890 align:start position:0% it and also briefly about implementation 00:17:51.890 --> 00:17:56.270 align:start position:0% it and also briefly about implementation so<00:17:52.890> we<00:17:53.270> recently<00:17:54.410> worked<00:17:55.410> on<00:17:55.620> some<00:17:55.920> follow-up 00:17:56.270 --> 00:17:56.280 align:start position:0% so we recently worked on some follow-up 00:17:56.280 --> 00:18:00.620 align:start position:0% so we recently worked on some follow-up of<00:17:56.520> our<00:17:57.110> original<00:17:58.110> Peru<00:17:58.590> Network<00:17:59.010> paper<00:17:59.940> and 00:18:00.620 --> 00:18:00.630 align:start position:0% of our original Peru Network paper and 00:18:00.630 --> 00:18:03.920 align:start position:0% of our original Peru Network paper and we<00:18:01.380> extended<00:18:01.800> it<00:18:01.890> to<00:18:02.040> also<00:18:02.580> cover<00:18:03.090> or<00:18:03.480> to<00:18:03.660> also 00:18:03.920 --> 00:18:03.930 align:start position:0% we extended it to also cover or to also 00:18:03.930 --> 00:18:05.540 align:start position:0% we extended it to also cover or to also support<00:18:04.260> multi-party<00:18:04.890> state<00:18:05.070> channels<00:18:05.430> so 00:18:05.540 --> 00:18:05.550 align:start position:0% support multi-party state channels so 00:18:05.550 --> 00:18:07.520 align:start position:0% support multi-party state channels so what<00:18:05.730> is<00:18:05.850> a<00:18:05.880> multi-party<00:18:06.840> state<00:18:07.050> Channel 00:18:07.520 --> 00:18:07.530 align:start position:0% what is a multi-party state Channel 00:18:07.530 --> 00:18:09.110 align:start position:0% what is a multi-party state Channel we<00:18:07.890> have<00:18:08.010> now<00:18:08.130> a<00:18:08.160> situation<00:18:08.370> Alice<00:18:08.910> Bob<00:18:09.090> Carol 00:18:09.110 --> 00:18:09.120 align:start position:0% we have now a situation Alice Bob Carol 00:18:09.120 --> 00:18:12.830 align:start position:0% we have now a situation Alice Bob Carol David<00:18:09.780> and<00:18:10.040> Ellis<00:18:11.040> Bob<00:18:11.280> and<00:18:11.520> David<00:18:12.210> they<00:18:12.660> would 00:18:12.830 --> 00:18:12.840 align:start position:0% David and Ellis Bob and David they would 00:18:12.840 --> 00:18:15.110 align:start position:0% David and Ellis Bob and David they would like<00:18:13.020> to<00:18:13.410> execute<00:18:14.160> some<00:18:14.580> multi-party 00:18:15.110 --> 00:18:15.120 align:start position:0% like to execute some multi-party 00:18:15.120 --> 00:18:17.240 align:start position:0% like to execute some multi-party contract<00:18:15.480> like<00:18:16.140> maybe<00:18:16.410> a<00:18:16.500> game<00:18:16.800> that<00:18:17.010> involves 00:18:17.240 --> 00:18:17.250 align:start position:0% contract like maybe a game that involves 00:18:17.250 --> 00:18:18.830 align:start position:0% contract like maybe a game that involves poker<00:18:17.760> game<00:18:17.940> that<00:18:17.970> involves<00:18:18.420> three<00:18:18.570> players 00:18:18.830 --> 00:18:18.840 align:start position:0% poker game that involves three players 00:18:18.840 --> 00:18:20.810 align:start position:0% poker game that involves three players and<00:18:19.080> they<00:18:19.800> can<00:18:19.950> do<00:18:20.100> this<00:18:20.190> as<00:18:20.340> follows<00:18:20.490> they 00:18:20.810 --> 00:18:20.820 align:start position:0% and they can do this as follows they 00:18:20.820 --> 00:18:23.180 align:start position:0% and they can do this as follows they built<00:18:21.060> first<00:18:21.840> a<00:18:22.110> virtual<00:18:22.560> channel<00:18:22.920> between 00:18:23.180 --> 00:18:23.190 align:start position:0% built first a virtual channel between 00:18:23.190 --> 00:18:25.730 align:start position:0% built first a virtual channel between Bob<00:18:24.150> and<00:18:24.180> David<00:18:24.510> which<00:18:25.230> was<00:18:25.380> stationed 00:18:25.730 --> 00:18:25.740 align:start position:0% Bob and David which was stationed 00:18:25.740 --> 00:18:27.260 align:start position:0% Bob and David which was stationed between<00:18:26.010> Bob<00:18:26.190> and<00:18:26.340> David<00:18:26.490> that's<00:18:26.820> what<00:18:27.090> we 00:18:27.260 --> 00:18:27.270 align:start position:0% between Bob and David that's what we 00:18:27.270 --> 00:18:29.510 align:start position:0% between Bob and David that's what we already<00:18:27.420> have<00:18:27.900> seen<00:18:28.290> in<00:18:28.470> this<00:18:28.590> talk<00:18:28.770> and<00:18:28.980> then 00:18:29.510 --> 00:18:29.520 align:start position:0% already have seen in this talk and then 00:18:29.520 --> 00:18:32.270 align:start position:0% already have seen in this talk and then over<00:18:30.120> this<00:18:30.780> virtual<00:18:31.170> state<00:18:31.440> channel<00:18:31.740> and<00:18:31.920> the 00:18:32.270 --> 00:18:32.280 align:start position:0% over this virtual state channel and the 00:18:32.280 --> 00:18:34.670 align:start position:0% over this virtual state channel and the underlying<00:18:32.580> legislation<00:18:33.140> or<00:18:34.140> between<00:18:34.350> Alice 00:18:34.670 --> 00:18:34.680 align:start position:0% underlying legislation or between Alice 00:18:34.680 --> 00:18:36.920 align:start position:0% underlying legislation or between Alice and<00:18:34.710> Bob<00:18:34.860> they<00:18:35.700> can<00:18:35.940> create<00:18:36.240> a<00:18:36.270> multi-party 00:18:36.920 --> 00:18:36.930 align:start position:0% and Bob they can create a multi-party 00:18:36.930 --> 00:18:39.290 align:start position:0% and Bob they can create a multi-party state<00:18:37.530> channel<00:18:37.890> and<00:18:38.070> in<00:18:38.490> this<00:18:38.610> case<00:18:38.850> this<00:18:39.090> one 00:18:39.290 --> 00:18:39.300 align:start position:0% state channel and in this case this one 00:18:39.300 --> 00:18:42.980 align:start position:0% state channel and in this case this one then<00:18:39.540> they<00:18:40.080> can<00:18:40.820> deploy<00:18:41.820> a<00:18:42.120> gaming<00:18:42.510> contract<00:18:42.900> a 00:18:42.980 --> 00:18:42.990 align:start position:0% then they can deploy a gaming contract a 00:18:42.990 --> 00:18:47.000 align:start position:0% then they can deploy a gaming contract a multi-party<00:18:43.500> gaming<00:18:43.800> contract<00:18:45.560> so<00:18:46.560> about 00:18:47.000 --> 00:18:47.010 align:start position:0% multi-party gaming contract so about 00:18:47.010 --> 00:18:48.920 align:start position:0% multi-party gaming contract so about implementation<00:18:47.370> we<00:18:47.880> are<00:18:48.000> cooperating<00:18:48.540> with 00:18:48.920 --> 00:18:48.930 align:start position:0% implementation we are cooperating with 00:18:48.930 --> 00:18:51.800 align:start position:0% implementation we are cooperating with the<00:18:49.230> company<00:18:49.560> Bosh<00:18:49.940> to<00:18:50.940> provide<00:18:51.630> an 00:18:51.800 --> 00:18:51.810 align:start position:0% the company Bosh to provide an 00:18:51.810 --> 00:18:53.840 align:start position:0% the company Bosh to provide an open-source<00:18:52.260> implementation<00:18:52.980> for<00:18:53.250> a<00:18:53.460> cerium 00:18:53.840 --> 00:18:53.850 align:start position:0% open-source implementation for a cerium 00:18:53.850 --> 00:18:55.940 align:start position:0% open-source implementation for a cerium of<00:18:54.450> course<00:18:54.720> we<00:18:54.840> also<00:18:54.960> happy<00:18:55.650> to<00:18:55.770> cooperate 00:18:55.940 --> 00:18:55.950 align:start position:0% of course we also happy to cooperate 00:18:55.950 --> 00:18:58.670 align:start position:0% of course we also happy to cooperate with<00:18:56.250> other<00:18:56.370> people<00:18:56.700> we<00:18:57.510> are<00:18:57.600> like<00:18:57.750> a<00:18:57.780> research 00:18:58.670 --> 00:18:58.680 align:start position:0% with other people we are like a research 00:18:58.680 --> 00:19:02.060 align:start position:0% with other people we are like a research project<00:18:58.890> mainly<00:18:59.610> at<00:18:59.730> the<00:18:59.820> moment<00:19:00.180> I<00:19:00.950> talked<00:19:01.950> to 00:19:02.060 --> 00:19:02.070 align:start position:0% project mainly at the moment I talked to 00:19:02.070 --> 00:19:03.350 align:start position:0% project mainly at the moment I talked to our<00:19:02.100> colleagues<00:19:02.700> from<00:19:02.760> Porsche<00:19:03.000> and<00:19:03.150> they<00:19:03.270> are 00:19:03.350 --> 00:19:03.360 align:start position:0% our colleagues from Porsche and they are 00:19:03.360 --> 00:19:05.090 align:start position:0% our colleagues from Porsche and they are currently<00:19:03.660> developing<00:19:04.020> the<00:19:04.470> note<00:19:04.620> software 00:19:05.090 --> 00:19:05.100 align:start position:0% currently developing the note software 00:19:05.100 --> 00:19:07.340 align:start position:0% currently developing the note software for<00:19:05.280> later<00:19:05.460> state<00:19:05.790> channels<00:19:06.200> they<00:19:07.200> will 00:19:07.340 --> 00:19:07.350 align:start position:0% for later state channels they will 00:19:07.350 --> 00:19:10.840 align:start position:0% for later state channels they will release<00:19:07.620> this<00:19:07.890> in<00:19:08.720> at<00:19:09.720> the<00:19:09.840> end<00:19:09.990> of<00:19:10.140> this<00:19:10.260> year 00:19:10.840 --> 00:19:10.850 align:start position:0% release this in at the end of this year 00:19:10.850 --> 00:19:15.290 align:start position:0% release this in at the end of this year as<00:19:11.850> an<00:19:12.000> open<00:19:12.210> source<00:19:12.330> project<00:19:12.570> then<00:19:13.380> in<00:19:13.730> hue<00:19:14.730> so 00:19:15.290 --> 00:19:15.300 align:start position:0% as an open source project then in hue so 00:19:15.300 --> 00:19:18.230 align:start position:0% as an open source project then in hue so on<00:19:15.390> the<00:19:15.450> second<00:19:16.250> half<00:19:17.250> on<00:19:17.520> the<00:19:17.580> first<00:19:17.880> half<00:19:18.060> of 00:19:18.230 --> 00:19:18.240 align:start position:0% on the second half on the first half of 00:19:18.240 --> 00:19:21.410 align:start position:0% on the second half on the first half of 2019<00:19:19.040> we<00:19:20.040> will<00:19:20.250> they<00:19:20.730> will<00:19:20.880> release<00:19:21.120> an 00:19:21.410 --> 00:19:21.420 align:start position:0% 2019 we will they will release an 00:19:21.420 --> 00:19:22.940 align:start position:0% 2019 we will they will release an implementation<00:19:22.200> of<00:19:22.320> the<00:19:22.440> visual<00:19:22.740> state 00:19:22.940 --> 00:19:22.950 align:start position:0% implementation of the visual state 00:19:22.950 --> 00:19:26.180 align:start position:0% implementation of the visual state channels<00:19:23.280> and<00:19:23.460> the<00:19:23.520> Hopf<00:19:23.670> software<00:19:24.150> and<00:19:25.190> then 00:19:26.180 --> 00:19:26.190 align:start position:0% channels and the Hopf software and then 00:19:26.190 --> 00:19:28.190 align:start position:0% channels and the Hopf software and then later<00:19:26.670> at<00:19:27.030> the<00:19:27.210> end<00:19:27.330> of<00:19:27.420> the<00:19:27.540> year<00:19:27.750> they<00:19:27.960> plan 00:19:28.190 --> 00:19:28.200 align:start position:0% later at the end of the year they plan 00:19:28.200 --> 00:19:29.840 align:start position:0% later at the end of the year they plan to<00:19:28.260> integrate<00:19:28.770> it<00:19:28.920> in<00:19:29.070> some<00:19:29.250> industry<00:19:29.700> use 00:19:29.840 --> 00:19:29.850 align:start position:0% to integrate it in some industry use 00:19:29.850 --> 00:19:32.540 align:start position:0% to integrate it in some industry use cases<00:19:30.120> okay<00:19:30.690> so<00:19:30.750> this<00:19:31.470> is<00:19:31.650> for<00:19:32.490> the 00:19:32.540 --> 00:19:32.550 align:start position:0% cases okay so this is for the 00:19:32.550 --> 00:19:33.710 align:start position:0% cases okay so this is for the implementation<00:19:32.760> at<00:19:33.150> the<00:19:33.240> moment<00:19:33.540> we<00:19:33.630> of 00:19:33.710 --> 00:19:33.720 align:start position:0% implementation at the moment we of 00:19:33.720 --> 00:19:35.600 align:start position:0% implementation at the moment we of course<00:19:33.960> happy<00:19:34.230> to<00:19:34.740> like<00:19:35.010> this<00:19:35.130> would<00:19:35.250> be<00:19:35.280> open 00:19:35.600 --> 00:19:35.610 align:start position:0% course happy to like this would be open 00:19:35.610 --> 00:19:38.600 align:start position:0% course happy to like this would be open source<00:19:35.820> released<00:19:36.720> soon<00:19:37.530> and<00:19:37.800> it<00:19:38.370> would<00:19:38.520> be 00:19:38.600 --> 00:19:38.610 align:start position:0% source released soon and it would be 00:19:38.610 --> 00:19:40.640 align:start position:0% source released soon and it would be great<00:19:38.820> if<00:19:38.970> people<00:19:39.000> here<00:19:39.810> collaborate<00:19:40.380> on<00:19:40.530> this 00:19:40.640 --> 00:19:40.650 align:start position:0% great if people here collaborate on this 00:19:40.650 --> 00:19:46.520 align:start position:0% great if people here collaborate on this with<00:19:41.130> us<00:19:42.020> so<00:19:43.020> let<00:19:43.770> me<00:19:43.980> conclude<00:19:44.310> my<00:19:44.700> talk<00:19:45.530> so 00:19:46.520 --> 00:19:46.530 align:start position:0% with us so let me conclude my talk so 00:19:46.530 --> 00:19:49.370 align:start position:0% with us so let me conclude my talk so what<00:19:47.130> we<00:19:47.310> are<00:19:47.430> trying<00:19:47.580> to<00:19:47.820> build<00:19:47.970> is<00:19:48.380> provably 00:19:49.370 --> 00:19:49.380 align:start position:0% what we are trying to build is provably 00:19:49.380 --> 00:19:51.950 align:start position:0% what we are trying to build is provably secure<00:19:49.470> layer<00:19:50.130> two<00:19:50.370> solutions<00:19:50.880> we<00:19:51.690> will<00:19:51.840> also 00:19:51.950 --> 00:19:51.960 align:start position:0% secure layer two solutions we will also 00:19:51.960 --> 00:19:53.660 align:start position:0% secure layer two solutions we will also look<00:19:52.140> into<00:19:52.350> other<00:19:52.470> possibly<00:19:53.160> soon<00:19:53.400> other 00:19:53.660 --> 00:19:53.670 align:start position:0% look into other possibly soon other 00:19:53.670 --> 00:19:56.450 align:start position:0% look into other possibly soon other solutions<00:19:54.120> like<00:19:54.180> plasma<00:19:54.450> and<00:19:54.750> so<00:19:54.810> on<00:19:54.960> and<00:19:55.460> we 00:19:56.450 --> 00:19:56.460 align:start position:0% solutions like plasma and so on and we 00:19:56.460 --> 00:19:59.930 align:start position:0% solutions like plasma and so on and we believe<00:19:56.730> that<00:19:56.760> to<00:19:58.040> make<00:19:59.040> them<00:19:59.280> ready<00:19:59.460> for<00:19:59.730> mass 00:19:59.930 --> 00:19:59.940 align:start position:0% believe that to make them ready for mass 00:19:59.940 --> 00:20:01.320 align:start position:0% believe that to make them ready for mass for<00:20:00.330> mass<00:20:00.360> of<00:20:00.630> users 00:20:01.320 --> 00:20:01.330 align:start position:0% for mass of users 00:20:01.330 --> 00:20:03.240 align:start position:0% for mass of users should<00:20:01.480> there<00:20:02.200> should<00:20:02.320> be<00:20:02.440> solid<00:20:02.740> foundations 00:20:03.240 --> 00:20:03.250 align:start position:0% should there should be solid foundations 00:20:03.250 --> 00:20:05.640 align:start position:0% should there should be solid foundations for<00:20:03.460> these<00:20:03.610> protocols<00:20:03.940> okay<00:20:04.540> so<00:20:04.600> and<00:20:05.110> that 00:20:05.640 --> 00:20:05.650 align:start position:0% for these protocols okay so and that 00:20:05.650 --> 00:20:06.870 align:start position:0% for these protocols okay so and that just<00:20:05.890> explained<00:20:06.250> you<00:20:06.340> at<00:20:06.490> a<00:20:06.520> very<00:20:06.730> high<00:20:06.850> level 00:20:06.870 --> 00:20:06.880 align:start position:0% just explained you at a very high level 00:20:06.880 --> 00:20:08.250 align:start position:0% just explained you at a very high level what<00:20:07.270> this<00:20:07.450> is<00:20:07.630> like<00:20:07.870> giving<00:20:08.140> these 00:20:08.250 --> 00:20:08.260 align:start position:0% what this is like giving these 00:20:08.260 --> 00:20:11.370 align:start position:0% what this is like giving these definitions<00:20:09.060> making<00:20:10.060> a<00:20:10.380> protocol 00:20:11.370 --> 00:20:11.380 align:start position:0% definitions making a protocol 00:20:11.380 --> 00:20:13.350 align:start position:0% definitions making a protocol specification<00:20:12.280> really<00:20:12.520> formal<00:20:13.090> and 00:20:13.350 --> 00:20:13.360 align:start position:0% specification really formal and 00:20:13.360 --> 00:20:15.120 align:start position:0% specification really formal and releasing<00:20:13.750> it<00:20:13.840> to<00:20:13.960> the<00:20:13.990> public<00:20:14.080> and<00:20:14.620> then 00:20:15.120 --> 00:20:15.130 align:start position:0% releasing it to the public and then 00:20:15.130 --> 00:20:16.920 align:start position:0% releasing it to the public and then proving<00:20:15.400> the<00:20:15.610> security<00:20:16.090> so<00:20:16.630> this<00:20:16.810> is 00:20:16.920 --> 00:20:16.930 align:start position:0% proving the security so this is 00:20:16.930 --> 00:20:18.480 align:start position:0% proving the security so this is essentially<00:20:17.380> what<00:20:17.500> we<00:20:17.680> did<00:20:17.830> we<00:20:18.040> designed<00:20:18.370> a 00:20:18.480 --> 00:20:18.490 align:start position:0% essentially what we did we designed a 00:20:18.490 --> 00:20:20.310 align:start position:0% essentially what we did we designed a protocol<00:20:18.760> it's<00:20:19.210> out<00:20:19.480> there<00:20:19.750> you<00:20:19.930> can<00:20:20.110> go<00:20:20.260> to 00:20:20.310 --> 00:20:20.320 align:start position:0% protocol it's out there you can go to 00:20:20.320 --> 00:20:22.140 align:start position:0% protocol it's out there you can go to our<00:20:20.560> web<00:20:20.680> page<00:20:20.710> you<00:20:21.010> can<00:20:21.190> read<00:20:21.340> it<00:20:21.490> and<00:20:21.640> it's 00:20:22.140 --> 00:20:22.150 align:start position:0% our web page you can read it and it's 00:20:22.150 --> 00:20:24.300 align:start position:0% our web page you can read it and it's it's<00:20:22.450> really<00:20:22.630> like<00:20:23.170> I<00:20:23.290> think<00:20:23.350> fully<00:20:23.830> described 00:20:24.300 --> 00:20:24.310 align:start position:0% it's really like I think fully described 00:20:24.310 --> 00:20:26.930 align:start position:0% it's really like I think fully described so<00:20:24.550> you<00:20:24.610> can<00:20:24.880> like<00:20:25.060> take<00:20:25.450> it<00:20:25.480> and<00:20:25.780> implement<00:20:26.170> it 00:20:26.930 --> 00:20:26.940 align:start position:0% so you can like take it and implement it 00:20:26.940 --> 00:20:29.340 align:start position:0% so you can like take it and implement it where<00:20:27.940> maybe<00:20:28.120> not<00:20:28.330> tonight<00:20:28.450> but<00:20:28.630> maybe<00:20:29.140> in 00:20:29.340 --> 00:20:29.350 align:start position:0% where maybe not tonight but maybe in 00:20:29.350 --> 00:20:30.210 align:start position:0% where maybe not tonight but maybe in five<00:20:29.530> nights<00:20:29.710> okay 00:20:30.210 --> 00:20:30.220 align:start position:0% five nights okay 00:20:30.220 --> 00:20:33.540 align:start position:0% five nights okay so<00:20:30.640> then<00:20:31.480> you<00:20:32.140> can<00:20:32.410> then<00:20:32.980> we<00:20:33.100> have<00:20:33.220> security 00:20:33.540 --> 00:20:33.550 align:start position:0% so then you can then we have security 00:20:33.550 --> 00:20:35.340 align:start position:0% so then you can then we have security proofs<00:20:33.850> we<00:20:34.090> prove<00:20:34.300> that<00:20:34.330> these<00:20:34.660> protocols<00:20:34.900> are 00:20:35.340 --> 00:20:35.350 align:start position:0% proofs we prove that these protocols are 00:20:35.350 --> 00:20:38.460 align:start position:0% proofs we prove that these protocols are secure<00:20:35.830> and<00:20:36.630> the<00:20:37.630> next<00:20:37.840> step<00:20:38.020> that<00:20:38.050> we<00:20:38.320> would 00:20:38.460 --> 00:20:38.470 align:start position:0% secure and the next step that we would 00:20:38.470 --> 00:20:40.080 align:start position:0% secure and the next step that we would like<00:20:38.650> to<00:20:38.800> do<00:20:38.980> is<00:20:39.160> because<00:20:39.340> these<00:20:39.640> proofs<00:20:40.000> are 00:20:40.080 --> 00:20:40.090 align:start position:0% like to do is because these proofs are 00:20:40.090 --> 00:20:42.300 align:start position:0% like to do is because these proofs are quite<00:20:40.540> complicated<00:20:40.900> very<00:20:41.740> involved<00:20:42.040> like 00:20:42.300 --> 00:20:42.310 align:start position:0% quite complicated very involved like 00:20:42.310 --> 00:20:43.890 align:start position:0% quite complicated very involved like many<00:20:42.520> corner<00:20:42.820> cases<00:20:43.150> we<00:20:43.270> have<00:20:43.390> to<00:20:43.510> take<00:20:43.690> care 00:20:43.890 --> 00:20:43.900 align:start position:0% many corner cases we have to take care 00:20:43.900 --> 00:20:45.780 align:start position:0% many corner cases we have to take care of<00:20:43.930> we<00:20:44.740> would<00:20:44.860> actually<00:20:45.160> like<00:20:45.340> to<00:20:45.370> formally 00:20:45.780 --> 00:20:45.790 align:start position:0% of we would actually like to formally 00:20:45.790 --> 00:20:47.640 align:start position:0% of we would actually like to formally verify<00:20:46.270> them<00:20:46.480> by<00:20:46.630> machines<00:20:47.020> so<00:20:47.380> there<00:20:47.590> are 00:20:47.640 --> 00:20:47.650 align:start position:0% verify them by machines so there are 00:20:47.650 --> 00:20:49.110 align:start position:0% verify them by machines so there are some<00:20:47.770> kind<00:20:47.920> of<00:20:48.040> tools<00:20:48.280> like<00:20:48.370> easy<00:20:48.700> crypt<00:20:48.970> and 00:20:49.110 --> 00:20:49.120 align:start position:0% some kind of tools like easy crypt and 00:20:49.120 --> 00:20:51.600 align:start position:0% some kind of tools like easy crypt and so<00:20:49.210> on<00:20:49.360> we<00:20:49.960> would<00:20:50.080> like<00:20:50.260> to<00:20:50.290> use<00:20:50.620> to<00:20:50.920> use<00:20:51.370> them 00:20:51.600 --> 00:20:51.610 align:start position:0% so on we would like to use to use them 00:20:51.610 --> 00:20:53.580 align:start position:0% so on we would like to use to use them to<00:20:52.030> verify<00:20:52.240> that<00:20:52.510> actually<00:20:52.960> our<00:20:52.990> proofs<00:20:53.440> are 00:20:53.580 --> 00:20:53.590 align:start position:0% to verify that actually our proofs are 00:20:53.590 --> 00:20:55.620 align:start position:0% to verify that actually our proofs are correct<00:20:53.890> we<00:20:54.490> of<00:20:54.670> course<00:20:55.000> hope<00:20:55.150> that<00:20:55.450> they<00:20:55.540> are 00:20:55.620 --> 00:20:55.630 align:start position:0% correct we of course hope that they are 00:20:55.630 --> 00:20:57.660 align:start position:0% correct we of course hope that they are correct<00:20:55.810> already<00:20:56.140> but<00:20:56.350> better<00:20:56.950> to<00:20:57.160> let<00:20:57.520> them 00:20:57.660 --> 00:20:57.670 align:start position:0% correct already but better to let them 00:20:57.670 --> 00:20:59.430 align:start position:0% correct already but better to let them check<00:20:57.850> by<00:20:58.000> a<00:20:58.030> machine<00:20:58.210> this<00:20:58.990> is<00:20:59.080> what<00:20:59.230> we<00:20:59.350> are 00:20:59.430 --> 00:20:59.440 align:start position:0% check by a machine this is what we are 00:20:59.440 --> 00:21:01.890 align:start position:0% check by a machine this is what we are currently<00:20:59.620> doing<00:21:00.010> we<00:21:00.880> want<00:21:01.330> to<00:21:01.450> in<00:21:01.690> the<00:21:01.720> future 00:21:01.890 --> 00:21:01.900 align:start position:0% currently doing we want to in the future 00:21:01.900 --> 00:21:04.050 align:start position:0% currently doing we want to in the future work<00:21:02.590> more<00:21:02.800> on<00:21:02.830> implementations<00:21:03.610> and<00:21:03.880> in 00:21:04.050 --> 00:21:04.060 align:start position:0% work more on implementations and in 00:21:04.060 --> 00:21:06.120 align:start position:0% work more on implementations and in particular<00:21:04.230> this<00:21:05.230> is<00:21:05.410> maybe<00:21:05.590> a<00:21:05.710> long-term 00:21:06.120 --> 00:21:06.130 align:start position:0% particular this is maybe a long-term 00:21:06.130 --> 00:21:08.370 align:start position:0% particular this is maybe a long-term goal<00:21:06.340> also<00:21:06.610> provides<00:21:07.480> some<00:21:07.780> formally 00:21:08.370 --> 00:21:08.380 align:start position:0% goal also provides some formally 00:21:08.380 --> 00:21:11.340 align:start position:0% goal also provides some formally verified<00:21:09.360> implementation<00:21:10.360> and<00:21:10.690> of<00:21:10.960> course<00:21:11.170> is 00:21:11.340 --> 00:21:11.350 align:start position:0% verified implementation and of course is 00:21:11.350 --> 00:21:12.870 align:start position:0% verified implementation and of course is it's<00:21:11.620> very<00:21:11.800> necessary<00:21:11.950> to<00:21:12.340> start<00:21:12.640> with<00:21:12.850> a 00:21:12.870 --> 00:21:12.880 align:start position:0% it's very necessary to start with a 00:21:12.880 --> 00:21:15.840 align:start position:0% it's very necessary to start with a sound<00:21:13.180> protocol<00:21:13.630> before<00:21:14.080> you<00:21:14.400> like<00:21:15.400> implement 00:21:15.840 --> 00:21:15.850 align:start position:0% sound protocol before you like implement 00:21:15.850 --> 00:21:17.490 align:start position:0% sound protocol before you like implement something<00:21:16.030> as<00:21:16.240> complicated<00:21:16.540> as<00:21:16.900> this<00:21:17.080> because 00:21:17.490 --> 00:21:17.500 align:start position:0% something as complicated as this because 00:21:17.500 --> 00:21:19.440 align:start position:0% something as complicated as this because if<00:21:17.680> you<00:21:17.800> make<00:21:17.980> mistakes<00:21:18.820> at<00:21:19.000> the<00:21:19.090> protocol 00:21:19.440 --> 00:21:19.450 align:start position:0% if you make mistakes at the protocol 00:21:19.450 --> 00:21:22.770 align:start position:0% if you make mistakes at the protocol level<00:21:19.510> already<00:21:20.080> then<00:21:20.800> you<00:21:21.180> don't<00:21:22.180> need<00:21:22.570> even 00:21:22.770 --> 00:21:22.780 align:start position:0% level already then you don't need even 00:21:22.780 --> 00:21:24.270 align:start position:0% level already then you don't need even to<00:21:23.020> formally<00:21:23.350> formally<00:21:23.710> verify<00:21:24.070> your 00:21:24.270 --> 00:21:24.280 align:start position:0% to formally formally verify your 00:21:24.280 --> 00:21:28.080 align:start position:0% to formally formally verify your implementation<00:21:24.940> so<00:21:26.340> talk<00:21:27.340> further 00:21:28.080 --> 00:21:28.090 align:start position:0% implementation so talk further 00:21:28.090 --> 00:21:29.850 align:start position:0% implementation so talk further information<00:21:28.630> I<00:21:28.720> hear<00:21:28.960> I<00:21:28.990> would<00:21:29.170> like<00:21:29.440> to<00:21:29.590> thank 00:21:29.850 --> 00:21:29.860 align:start position:0% information I hear I would like to thank 00:21:29.860 --> 00:21:32.040 align:start position:0% information I hear I would like to thank all<00:21:30.040> our<00:21:30.070> sponsors<00:21:30.520> here<00:21:30.940> it's<00:21:31.600> for<00:21:31.930> our 00:21:32.040 --> 00:21:32.050 align:start position:0% all our sponsors here it's for our 00:21:32.050 --> 00:21:40.390 align:start position:0% all our sponsors here it's for our research<00:21:32.500> and<00:21:33.370> I'm<00:21:33.700> happy<00:21:33.880> to<00:21:33.970> take<00:21:34.090> questions 00:21:40.390 --> 00:21:40.400 align:start position:0% 00:21:40.400 --> 00:21:53.790 align:start position:0% you 00:21:53.790 --> 00:21:53.800 align:start position:0% 00:21:53.800 --> 00:21:57.970 align:start position:0% so<00:21:54.800> when<00:21:55.370> you're<00:21:55.630> writing<00:21:56.630> these<00:21:56.980> protocol 00:21:57.970 --> 00:21:57.980 align:start position:0% so when you're writing these protocol 00:21:57.980 --> 00:22:00.880 align:start position:0% so when you're writing these protocol specs<00:21:58.309> to<00:21:58.580> basically<00:21:58.970> like<00:21:59.380> specify<00:22:00.380> or<00:22:00.710> come 00:22:00.880 --> 00:22:00.890 align:start position:0% specs to basically like specify or come 00:22:00.890 --> 00:22:03.790 align:start position:0% specs to basically like specify or come up<00:22:01.010> with<00:22:01.720> set<00:22:02.720> of<00:22:02.870> failure<00:22:03.200> modes<00:22:03.440> and<00:22:03.620> then 00:22:03.790 --> 00:22:03.800 align:start position:0% up with set of failure modes and then 00:22:03.800 --> 00:22:05.049 align:start position:0% up with set of failure modes and then prove<00:22:04.040> that<00:22:04.070> those<00:22:04.370> failure<00:22:04.670> modes<00:22:04.910> can 00:22:05.049 --> 00:22:05.059 align:start position:0% prove that those failure modes can 00:22:05.059 --> 00:22:08.230 align:start position:0% prove that those failure modes can happen<00:22:05.420> and<00:22:05.710> if<00:22:06.710> so<00:22:06.920> then<00:22:07.130> then<00:22:07.880> of<00:22:08.000> course 00:22:08.230 --> 00:22:08.240 align:start position:0% happen and if so then then of course 00:22:08.240 --> 00:22:09.790 align:start position:0% happen and if so then then of course there<00:22:08.570> might<00:22:08.750> be<00:22:08.780> failure<00:22:09.200> modes<00:22:09.440> that<00:22:09.620> you 00:22:09.790 --> 00:22:09.800 align:start position:0% there might be failure modes that you 00:22:09.800 --> 00:22:12.190 align:start position:0% there might be failure modes that you did<00:22:10.309> not<00:22:10.460> think<00:22:10.820> of<00:22:10.910> right<00:22:11.150> yeah<00:22:11.630> and<00:22:11.809> another 00:22:12.190 --> 00:22:12.200 align:start position:0% did not think of right yeah and another 00:22:12.200 --> 00:22:15.400 align:start position:0% did not think of right yeah and another question<00:22:12.500> is<00:22:13.120> which<00:22:14.120> frameworks<00:22:14.630> are<00:22:15.020> using 00:22:15.400 --> 00:22:15.410 align:start position:0% question is which frameworks are using 00:22:15.410 --> 00:22:17.350 align:start position:0% question is which frameworks are using like<00:22:15.590> what<00:22:15.800> protocol<00:22:16.730> specification 00:22:17.350 --> 00:22:17.360 align:start position:0% like what protocol specification 00:22:17.360 --> 00:22:18.910 align:start position:0% like what protocol specification languages<00:22:17.690> and<00:22:17.960> proving<00:22:18.380> languages<00:22:18.770> are 00:22:18.910 --> 00:22:18.920 align:start position:0% languages and proving languages are 00:22:18.920 --> 00:22:22.840 align:start position:0% languages and proving languages are using<00:22:19.929> so<00:22:20.929> the<00:22:21.050> first<00:22:21.260> question<00:22:21.380> was<00:22:22.370> if<00:22:22.610> there 00:22:22.840 --> 00:22:22.850 align:start position:0% using so the first question was if there 00:22:22.850 --> 00:22:24.610 align:start position:0% using so the first question was if there can<00:22:23.000> be<00:22:23.059> connect<00:22:23.540> is<00:22:23.780> I<00:22:23.960> mean<00:22:24.140> like<00:22:24.260> of<00:22:24.559> course 00:22:24.610 --> 00:22:24.620 align:start position:0% can be connect is I mean like of course 00:22:24.620 --> 00:22:26.110 align:start position:0% can be connect is I mean like of course what<00:22:25.130> we<00:22:25.250> do<00:22:25.429> is<00:22:25.610> like<00:22:25.790> we<00:22:25.940> have<00:22:25.970> a 00:22:26.110 --> 00:22:26.120 align:start position:0% what we do is like we have a 00:22:26.120 --> 00:22:28.630 align:start position:0% what we do is like we have a specification<00:22:26.870> of<00:22:27.410> the<00:22:27.679> after<00:22:28.040> after<00:22:28.160> of<00:22:28.460> the 00:22:28.630 --> 00:22:28.640 align:start position:0% specification of the after after of the 00:22:28.640 --> 00:22:30.549 align:start position:0% specification of the after after of the of<00:22:28.850> the<00:22:28.970> protocol<00:22:29.210> okay<00:22:29.600> we<00:22:29.720> give<00:22:29.870> this<00:22:30.080> then 00:22:30.549 --> 00:22:30.559 align:start position:0% of the protocol okay we give this then 00:22:30.559 --> 00:22:32.590 align:start position:0% of the protocol okay we give this then we<00:22:30.650> have<00:22:30.770> also<00:22:30.920> model<00:22:31.370> and<00:22:31.580> then<00:22:32.000> we<00:22:32.030> show<00:22:32.300> that 00:22:32.590 --> 00:22:32.600 align:start position:0% we have also model and then we show that 00:22:32.600 --> 00:22:34.660 align:start position:0% we have also model and then we show that whatever<00:22:33.470> and<00:22:33.770> at<00:22:33.830> worst<00:22:34.010> we<00:22:34.130> can<00:22:34.280> do<00:22:34.429> in<00:22:34.550> this 00:22:34.660 --> 00:22:34.670 align:start position:0% whatever and at worst we can do in this 00:22:34.670 --> 00:22:35.200 align:start position:0% whatever and at worst we can do in this model 00:22:35.200 --> 00:22:35.210 align:start position:0% model 00:22:35.210 --> 00:22:36.790 align:start position:0% model he<00:22:35.510> will<00:22:35.630> not<00:22:35.780> succeed<00:22:35.960> whatever<00:22:36.559> this<00:22:36.650> means 00:22:36.790 --> 00:22:36.800 align:start position:0% he will not succeed whatever this means 00:22:36.800 --> 00:22:39.010 align:start position:0% he will not succeed whatever this means for<00:22:37.040> example<00:22:37.400> he<00:22:37.490> will<00:22:37.640> not<00:22:37.820> be<00:22:37.970> able<00:22:38.090> to<00:22:38.750> steal 00:22:39.010 --> 00:22:39.020 align:start position:0% for example he will not be able to steal 00:22:39.020 --> 00:22:41.799 align:start position:0% for example he will not be able to steal money<00:22:39.920> from<00:22:40.100> the<00:22:40.520> intermediary<00:22:41.090> okay<00:22:41.570> like 00:22:41.799 --> 00:22:41.809 align:start position:0% money from the intermediary okay like 00:22:41.809 --> 00:22:44.260 align:start position:0% money from the intermediary okay like whatever<00:22:42.290> his<00:22:42.559> behavior<00:22:43.010> is<00:22:43.190> as<00:22:43.610> long<00:22:43.850> as<00:22:44.059> he 00:22:44.260 --> 00:22:44.270 align:start position:0% whatever his behavior is as long as he 00:22:44.270 --> 00:22:46.930 align:start position:0% whatever his behavior is as long as he behaves<00:22:45.170> as<00:22:45.650> specified<00:22:46.190> in<00:22:46.220> the<00:22:46.370> model<00:22:46.670> so<00:22:46.790> all 00:22:46.930 --> 00:22:46.940 align:start position:0% behaves as specified in the model so all 00:22:46.940 --> 00:22:47.919 align:start position:0% behaves as specified in the model so all this<00:22:47.059> kind<00:22:47.210> of<00:22:47.330> stuff<00:22:47.390> that<00:22:47.690> you<00:22:47.780> heard<00:22:47.900> today 00:22:47.919 --> 00:22:47.929 align:start position:0% this kind of stuff that you heard today 00:22:47.929 --> 00:22:49.750 align:start position:0% this kind of stuff that you heard today like<00:22:48.470> replay<00:22:48.860> attacks<00:22:49.190> and<00:22:49.370> this<00:22:49.490> kind<00:22:49.700> of 00:22:49.750 --> 00:22:49.760 align:start position:0% like replay attacks and this kind of 00:22:49.760 --> 00:22:51.130 align:start position:0% like replay attacks and this kind of stuff<00:22:49.850> this<00:22:50.090> is<00:22:50.150> all<00:22:50.300> covered<00:22:50.630> by<00:22:50.660> our<00:22:50.870> model 00:22:51.130 --> 00:22:51.140 align:start position:0% stuff this is all covered by our model 00:22:51.140 --> 00:22:53.080 align:start position:0% stuff this is all covered by our model automatically<00:22:51.920> by<00:22:52.190> this<00:22:52.250> you<00:22:52.490> see<00:22:52.670> framework 00:22:53.080 --> 00:22:53.090 align:start position:0% automatically by this you see framework 00:22:53.090 --> 00:22:54.910 align:start position:0% automatically by this you see framework but<00:22:53.570> other<00:22:53.720> stuff<00:22:54.020> maybe<00:22:54.290> it's<00:22:54.500> not<00:22:54.559> covered 00:22:54.910 --> 00:22:54.920 align:start position:0% but other stuff maybe it's not covered 00:22:54.920 --> 00:22:56.830 align:start position:0% but other stuff maybe it's not covered like<00:22:55.100> for<00:22:55.280> example<00:22:55.340> side<00:22:56.300> channel<00:22:56.570> attacks 00:22:56.830 --> 00:22:56.840 align:start position:0% like for example side channel attacks 00:22:56.840 --> 00:22:58.299 align:start position:0% like for example side channel attacks okay<00:22:57.110> if<00:22:57.230> there<00:22:57.380> is<00:22:57.470> some<00:22:57.620> kind<00:22:57.710> of<00:22:57.860> adversary 00:22:58.299 --> 00:22:58.309 align:start position:0% okay if there is some kind of adversary 00:22:58.309 --> 00:23:01.120 align:start position:0% okay if there is some kind of adversary who<00:22:58.880> tries<00:22:59.210> to<00:22:59.480> break<00:22:59.780> it<00:23:00.020> by<00:23:00.200> doing<00:23:00.770> some<00:23:00.950> side 00:23:01.120 --> 00:23:01.130 align:start position:0% who tries to break it by doing some side 00:23:01.130 --> 00:23:02.500 align:start position:0% who tries to break it by doing some side channel<00:23:01.370> attack<00:23:01.610> or<00:23:01.820> I<00:23:02.120> don't<00:23:02.179> know<00:23:02.360> some 00:23:02.500 --> 00:23:02.510 align:start position:0% channel attack or I don't know some 00:23:02.510 --> 00:23:03.970 align:start position:0% channel attack or I don't know some other<00:23:02.600> stuff<00:23:02.870> this<00:23:03.080> is<00:23:03.260> the<00:23:03.350> not<00:23:03.500> covered<00:23:03.830> by 00:23:03.970 --> 00:23:03.980 align:start position:0% other stuff this is the not covered by 00:23:03.980 --> 00:23:05.620 align:start position:0% other stuff this is the not covered by our<00:23:04.010> our<00:23:04.490> model<00:23:05.090> and<00:23:05.210> you<00:23:05.300> would<00:23:05.420> have<00:23:05.540> to 00:23:05.620 --> 00:23:05.630 align:start position:0% our our model and you would have to 00:23:05.630 --> 00:23:07.600 align:start position:0% our our model and you would have to extend<00:23:05.900> it<00:23:06.110> also<00:23:06.530> currently<00:23:06.980> our<00:23:07.190> model<00:23:07.490> we 00:23:07.600 --> 00:23:07.610 align:start position:0% extend it also currently our model we 00:23:07.610 --> 00:23:09.940 align:start position:0% extend it also currently our model we don't<00:23:07.850> really<00:23:08.059> like<00:23:08.360> have<00:23:09.200> integrated<00:23:09.620> fees 00:23:09.940 --> 00:23:09.950 align:start position:0% don't really like have integrated fees 00:23:09.950 --> 00:23:11.530 align:start position:0% don't really like have integrated fees yet<00:23:10.190> so<00:23:10.400> this<00:23:10.580> is<00:23:10.700> something<00:23:11.030> also<00:23:11.179> that<00:23:11.300> we 00:23:11.530 --> 00:23:11.540 align:start position:0% yet so this is something also that we 00:23:11.540 --> 00:23:13.890 align:start position:0% yet so this is something also that we would<00:23:11.660> like<00:23:11.840> so<00:23:12.110> gasps<00:23:12.320> you<00:23:13.070> don't<00:23:13.220> have<00:23:13.400> this 00:23:13.890 --> 00:23:13.900 align:start position:0% would like so gasps you don't have this 00:23:13.900 --> 00:23:15.820 align:start position:0% would like so gasps you don't have this probe<00:23:14.900> you<00:23:15.080> don't<00:23:15.230> have<00:23:15.320> this<00:23:15.440> formally 00:23:15.820 --> 00:23:15.830 align:start position:0% probe you don't have this formally 00:23:15.830 --> 00:23:17.500 align:start position:0% probe you don't have this formally modelled<00:23:16.130> yet<00:23:16.250> and<00:23:16.640> this<00:23:16.850> would<00:23:16.970> also<00:23:17.120> be<00:23:17.300> some 00:23:17.500 --> 00:23:17.510 align:start position:0% modelled yet and this would also be some 00:23:17.510 --> 00:23:20.560 align:start position:0% modelled yet and this would also be some next<00:23:17.809> step<00:23:18.170> the<00:23:18.770> second<00:23:19.040> question<00:23:19.370> was<00:23:19.570> well 00:23:20.560 --> 00:23:20.570 align:start position:0% next step the second question was well 00:23:20.570 --> 00:23:23.710 align:start position:0% next step the second question was well yeah<00:23:20.750> second<00:23:21.080> part<00:23:21.290> was<00:23:21.440> just<00:23:21.650> a<00:23:21.830> twitch<00:23:22.720> so 00:23:23.710 --> 00:23:23.720 align:start position:0% yeah second part was just a twitch so 00:23:23.720 --> 00:23:25.330 align:start position:0% yeah second part was just a twitch so yeah<00:23:23.900> at<00:23:24.530> the<00:23:24.590> moment<00:23:24.860> we<00:23:24.920> have<00:23:25.040> like<00:23:25.190> some 00:23:25.330 --> 00:23:25.340 align:start position:0% yeah at the moment we have like some 00:23:25.340 --> 00:23:28.150 align:start position:0% yeah at the moment we have like some abstract<00:23:25.730> specification<00:23:26.600> of<00:23:27.200> the<00:23:27.380> pseudo 00:23:28.150 --> 00:23:28.160 align:start position:0% abstract specification of the pseudo 00:23:28.160 --> 00:23:29.830 align:start position:0% abstract specification of the pseudo code<00:23:28.340> of<00:23:28.520> the<00:23:28.640> protocols<00:23:29.059> okay<00:23:29.360> so<00:23:29.420> it<00:23:29.660> says 00:23:29.830 --> 00:23:29.840 align:start position:0% code of the protocols okay so it says 00:23:29.840 --> 00:23:32.260 align:start position:0% code of the protocols okay so it says okay<00:23:30.170> party<00:23:30.530> a<00:23:30.650> creates<00:23:31.250> a<00:23:31.340> signature<00:23:31.700> sends 00:23:32.260 --> 00:23:32.270 align:start position:0% okay party a creates a signature sends 00:23:32.270 --> 00:23:35.110 align:start position:0% okay party a creates a signature sends it<00:23:32.390> to<00:23:32.540> Bob<00:23:32.809> then<00:23:33.740> Bob<00:23:34.070> does<00:23:34.490> something<00:23:34.880> waits 00:23:35.110 --> 00:23:35.120 align:start position:0% it to Bob then Bob does something waits 00:23:35.120 --> 00:23:37.450 align:start position:0% it to Bob then Bob does something waits five<00:23:35.480> seconds<00:23:35.960> it<00:23:36.530> creates<00:23:36.890> a<00:23:36.980> signature<00:23:37.309> of 00:23:37.450 --> 00:23:37.460 align:start position:0% five seconds it creates a signature of 00:23:37.460 --> 00:23:39.610 align:start position:0% five seconds it creates a signature of this<00:23:37.730> sense<00:23:38.030> it<00:23:38.179> to<00:23:38.390> others<00:23:39.080> and<00:23:39.230> so<00:23:39.320> on<00:23:39.380> so 00:23:39.610 --> 00:23:39.620 align:start position:0% this sense it to others and so on so 00:23:39.620 --> 00:23:41.500 align:start position:0% this sense it to others and so on so there<00:23:39.800> is<00:23:39.890> something<00:23:40.190> like<00:23:40.309> this<00:23:40.370> it's<00:23:41.300> like<00:23:41.480> a 00:23:41.500 --> 00:23:41.510 align:start position:0% there is something like this it's like a 00:23:41.510 --> 00:23:43.660 align:start position:0% there is something like this it's like a like<00:23:42.200> a<00:23:42.230> pseudo<00:23:42.500> code<00:23:42.740> essentially<00:23:43.250> but<00:23:43.520> we 00:23:43.660 --> 00:23:43.670 align:start position:0% like a pseudo code essentially but we 00:23:43.670 --> 00:23:45.820 align:start position:0% like a pseudo code essentially but we are<00:23:43.760> trying<00:23:44.030> now<00:23:44.210> to<00:23:44.240> move<00:23:45.200> it<00:23:45.350> closer<00:23:45.710> to 00:23:45.820 --> 00:23:45.830 align:start position:0% are trying now to move it closer to 00:23:45.830 --> 00:23:48.190 align:start position:0% are trying now to move it closer to something<00:23:46.340> like<00:23:46.520> formal<00:23:47.420> language<00:23:47.750> that<00:23:48.020> can 00:23:48.190 --> 00:23:48.200 align:start position:0% something like formal language that can 00:23:48.200 --> 00:23:50.110 align:start position:0% something like formal language that can then<00:23:48.320> be<00:23:48.380> checked<00:23:48.740> by<00:23:48.920> these<00:23:49.070> automated<00:23:49.640> tools 00:23:50.110 --> 00:23:50.120 align:start position:0% then be checked by these automated tools 00:23:50.120 --> 00:23:52.240 align:start position:0% then be checked by these automated tools okay<00:23:50.660> so<00:23:50.840> you<00:23:51.230> haven't<00:23:51.530> like<00:23:51.890> written 00:23:52.240 --> 00:23:52.250 align:start position:0% okay so you haven't like written 00:23:52.250 --> 00:23:54.940 align:start position:0% okay so you haven't like written anything<00:23:52.580> like<00:23:52.990> from<00:23:53.990> a<00:23:54.050> large<00:23:54.230> specification 00:23:54.940 --> 00:23:54.950 align:start position:0% anything like from a large specification 00:23:54.950 --> 00:23:57.310 align:start position:0% anything like from a large specification and<00:23:55.040> like<00:23:55.250> like<00:23:55.670> temporal<00:23:56.059> if<00:23:56.540> we<00:23:56.809> have<00:23:57.169> not 00:23:57.310 --> 00:23:57.320 align:start position:0% and like like temporal if we have not 00:23:57.320 --> 00:23:58.900 align:start position:0% and like like temporal if we have not written<00:23:57.440> it<00:23:57.590> in<00:23:57.710> Coke<00:23:57.860> yet<00:23:58.070> or<00:23:58.190> some<00:23:58.340> like<00:23:58.490> I<00:23:58.730> do 00:23:58.900 --> 00:23:58.910 align:start position:0% written it in Coke yet or some like I do 00:23:58.910 --> 00:24:00.190 align:start position:0% written it in Coke yet or some like I do wanna<00:23:59.150> yeah<00:23:59.450> we<00:23:59.570> will<00:23:59.690> do<00:23:59.780> this<00:23:59.900> we<00:24:00.110> are 00:24:00.190 --> 00:24:00.200 align:start position:0% wanna yeah we will do this we are 00:24:00.200 --> 00:24:08.279 align:start position:0% wanna yeah we will do this we are working<00:24:00.320> on<00:24:00.530> this 00:24:08.279 --> 00:24:08.289 align:start position:0% 00:24:08.289 --> 00:24:11.940 align:start position:0% we<00:24:09.289> also<00:24:09.409> here<00:24:09.740> so<00:24:09.860> you<00:24:10.190> can<00:24:10.399> catch<00:24:10.580> us<00:24:10.730> later 00:24:11.940 --> 00:24:11.950 align:start position:0% we also here so you can catch us later 00:24:11.950 --> 00:24:16.210 align:start position:0% we also here so you can catch us later all<00:24:12.950> right<00:24:13.070> thanks<00:24:13.279> passion 00:24:16.210 --> 00:24:16.220 align:start position:0% 00:24:16.220 --> 00:24:20.009 align:start position:0% [Applause]