WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.840 align:start position:0% [Applause] 00:00:11.840 --> 00:00:11.850 align:start position:0% 00:00:11.850 --> 00:00:14.970 align:start position:0% my<00:00:12.850> name<00:00:13.150> is<00:00:13.330> Yuri<00:00:13.570> go<00:00:13.810> I<00:00:14.050> work<00:00:14.530> at<00:00:14.740> a<00:00:14.770> company 00:00:14.970 --> 00:00:14.980 align:start position:0% my name is Yuri go I work at a company 00:00:14.980 --> 00:00:17.780 align:start position:0% my name is Yuri go I work at a company called<00:00:15.280> crypto<00:00:15.820> but<00:00:15.850> a<00:00:16.030> meet-up 00:00:17.780 --> 00:00:17.790 align:start position:0% called crypto but a meet-up 00:00:17.790 --> 00:00:22.700 align:start position:0% called crypto but a meet-up allocation<00:00:18.790> framework<00:00:19.300> five<00:00:19.840> containers<00:00:20.700> so 00:00:22.700 --> 00:00:22.710 align:start position:0% allocation framework five containers so 00:00:22.710 --> 00:00:25.080 align:start position:0% allocation framework five containers so today<00:00:23.710> I'll<00:00:23.980> be<00:00:24.010> giving<00:00:24.250> the<00:00:24.430> latest<00:00:24.850> research 00:00:25.080 --> 00:00:25.090 align:start position:0% today I'll be giving the latest research 00:00:25.090 --> 00:00:27.510 align:start position:0% today I'll be giving the latest research update<00:00:25.689> of<00:00:25.840> their<00:00:25.990> technology<00:00:26.829> and<00:00:27.009> the 00:00:27.510 --> 00:00:27.520 align:start position:0% update of their technology and the 00:00:27.520 --> 00:00:29.280 align:start position:0% update of their technology and the engine<00:00:27.820> is<00:00:27.939> another<00:00:28.210> favorite<00:00:28.509> called<00:00:28.930> as 00:00:29.280 --> 00:00:29.290 align:start position:0% engine is another favorite called as 00:00:29.290 --> 00:00:33.660 align:start position:0% engine is another favorite called as much<00:00:29.680> chamber<00:00:30.130> and<00:00:30.840> the<00:00:31.840> Gulf<00:00:32.110> a<00:00:32.439> stock<00:00:32.800> and<00:00:33.160> I 00:00:33.660 --> 00:00:33.670 align:start position:0% much chamber and the Gulf a stock and I 00:00:33.670 --> 00:00:36.120 align:start position:0% much chamber and the Gulf a stock and I won<00:00:33.880> everyone<00:00:34.390> in<00:00:34.540> this<00:00:34.630> room<00:00:34.840> to<00:00:35.050> know<00:00:35.380> what 00:00:36.120 --> 00:00:36.130 align:start position:0% won everyone in this room to know what 00:00:36.130 --> 00:00:38.700 align:start position:0% won everyone in this room to know what exactly<00:00:36.310> it's<00:00:36.850> like<00:00:36.910> the<00:00:37.210> mother<00:00:37.450> not<00:00:37.690> on<00:00:38.440> top 00:00:38.700 --> 00:00:38.710 align:start position:0% exactly it's like the mother not on top 00:00:38.710 --> 00:00:44.400 align:start position:0% exactly it's like the mother not on top of<00:00:38.739> negative<00:00:42.000> first<00:00:43.000> before<00:00:43.540> we<00:00:43.840> start<00:00:44.170> I 00:00:44.400 --> 00:00:44.410 align:start position:0% of negative first before we start I 00:00:44.410 --> 00:00:46.290 align:start position:0% of negative first before we start I wanna<00:00:44.650> I<00:00:45.010> just<00:00:45.310> want<00:00:45.460> to<00:00:45.520> give<00:00:45.640> a<00:00:45.670> learned<00:00:46.030> of 00:00:46.290 --> 00:00:46.300 align:start position:0% wanna I just want to give a learned of 00:00:46.300 --> 00:00:49.080 align:start position:0% wanna I just want to give a learned of our<00:00:46.570> background<00:00:47.410> of<00:00:47.650> food<00:00:47.920> yard<00:00:48.250> and<00:00:48.490> where<00:00:49.000> we 00:00:49.080 --> 00:00:49.090 align:start position:0% our background of food yard and where we 00:00:49.090 --> 00:00:52.140 align:start position:0% our background of food yard and where we came<00:00:49.270> from<00:00:49.330> so<00:00:50.130> big<00:00:51.130> time<00:00:51.310> for<00:00:51.490> the<00:00:51.580> Moustakas 00:00:52.140 --> 00:00:52.150 align:start position:0% came from so big time for the Moustakas 00:00:52.150 --> 00:00:54.210 align:start position:0% came from so big time for the Moustakas research<00:00:52.690> and<00:00:52.870> development<00:00:53.380> team<00:00:53.530> consists 00:00:54.210 --> 00:00:54.220 align:start position:0% research and development team consists 00:00:54.220 --> 00:00:57.510 align:start position:0% research and development team consists of<00:00:54.540> three<00:00:55.540> people<00:00:55.720> on<00:00:55.960> the<00:00:55.990> top<00:00:56.260> row<00:00:56.520> including 00:00:57.510 --> 00:00:57.520 align:start position:0% of three people on the top row including 00:00:57.520 --> 00:01:01.140 align:start position:0% of three people on the top row including myself<00:00:58.410> and<00:00:59.410> we<00:00:59.950> focus<00:01:00.280> on<00:01:00.430> some<00:01:00.670> of<00:01:00.790> the 00:01:01.140 --> 00:01:01.150 align:start position:0% myself and we focus on some of the 00:01:01.150 --> 00:01:04.200 align:start position:0% myself and we focus on some of the flavoring<00:01:01.870> that<00:01:02.350> I<00:01:02.380> just<00:01:02.680> mentioned<00:01:02.920> and<00:01:03.280> the 00:01:04.200 --> 00:01:04.210 align:start position:0% flavoring that I just mentioned and the 00:01:04.210 --> 00:01:06.179 align:start position:0% flavoring that I just mentioned and the other<00:01:04.330> three<00:01:04.600> on<00:01:04.930> the<00:01:05.110> second<00:01:05.439> row<00:01:05.650> are<00:01:05.979> in 00:01:06.179 --> 00:01:06.189 align:start position:0% other three on the second row are in 00:01:06.189 --> 00:01:08.340 align:start position:0% other three on the second row are in adoption<00:01:06.520> team<00:01:06.880> and<00:01:07.150> they<00:01:07.750> are<00:01:07.780> internal 00:01:08.340 --> 00:01:08.350 align:start position:0% adoption team and they are internal 00:01:08.350 --> 00:01:11.249 align:start position:0% adoption team and they are internal running<00:01:08.770> EEOC<00:01:09.130> projects<00:01:09.790> putting<00:01:10.570> our<00:01:10.720> R&D 00:01:11.249 --> 00:01:11.259 align:start position:0% running EEOC projects putting our R&D 00:01:11.259 --> 00:01:14.970 align:start position:0% running EEOC projects putting our R&D efforts<00:01:11.770> and<00:01:12.100> out<00:01:12.250> comes<00:01:12.490> into<00:01:12.880> the<00:01:13.980> putting 00:01:14.970 --> 00:01:14.980 align:start position:0% efforts and out comes into the putting 00:01:14.980 --> 00:01:17.340 align:start position:0% efforts and out comes into the putting into<00:01:15.130> practice<00:01:15.300> and<00:01:16.300> when<00:01:16.570> the<00:01:16.720> real<00:01:16.870> work<00:01:17.140> is 00:01:17.340 --> 00:01:17.350 align:start position:0% into practice and when the real work is 00:01:17.350 --> 00:01:23.010 align:start position:0% into practice and when the real work is pieces<00:01:18.900> and<00:01:20.460> how<00:01:21.460> exactly<00:01:21.840> quick<00:01:22.840> talk 00:01:23.010 --> 00:01:23.020 align:start position:0% pieces and how exactly quick talk 00:01:23.020 --> 00:01:25.260 align:start position:0% pieces and how exactly quick talk economics<00:01:23.409> thought<00:01:23.920> started<00:01:24.400> and<00:01:24.610> what<00:01:25.150> he 00:01:25.260 --> 00:01:25.270 align:start position:0% economics thought started and what he 00:01:25.270 --> 00:01:28.560 align:start position:0% economics thought started and what he focus<00:01:25.600> on<00:01:25.750> the<00:01:26.080> obstruction<00:01:26.860> of<00:01:27.040> layer<00:01:27.220> two<00:01:27.570> so 00:01:28.560 --> 00:01:28.570 align:start position:0% focus on the obstruction of layer two so 00:01:28.570 --> 00:01:31.040 align:start position:0% focus on the obstruction of layer two so ever<00:01:28.990> since<00:01:29.290> the<00:01:29.500> company<00:01:29.950> was<00:01:30.010> founded 00:01:31.040 --> 00:01:31.050 align:start position:0% ever since the company was founded 00:01:31.050 --> 00:01:34.620 align:start position:0% ever since the company was founded plasma<00:01:32.050> has<00:01:32.200> been<00:01:32.440> on<00:01:32.590> a<00:01:32.620> research<00:01:32.920> focus<00:01:33.630> but 00:01:34.620 --> 00:01:34.630 align:start position:0% plasma has been on a research focus but 00:01:34.630 --> 00:01:37.200 align:start position:0% plasma has been on a research focus but we<00:01:35.110> had<00:01:35.530> this<00:01:35.650> major<00:01:35.920> breakthrough<00:01:36.550> when<00:01:36.850> this 00:01:37.200 --> 00:01:37.210 align:start position:0% we had this major breakthrough when this 00:01:37.210 --> 00:01:39.840 align:start position:0% we had this major breakthrough when this blog<00:01:37.479> post<00:01:37.510> was<00:01:37.960> released<00:01:38.350> it<00:01:39.190> was<00:01:39.250> written<00:01:39.549> by 00:01:39.840 --> 00:01:39.850 align:start position:0% blog post was released it was written by 00:01:39.850 --> 00:01:41.310 align:start position:0% blog post was released it was written by covering<00:01:40.450> major 00:01:41.310 --> 00:01:41.320 align:start position:0% covering major 00:01:41.320 --> 00:01:43.469 align:start position:0% covering major former<00:01:41.740> plasma<00:01:42.250> researcher<00:01:42.640> at<00:01:42.850> plasma<00:01:43.299> group 00:01:43.469 --> 00:01:43.479 align:start position:0% former plasma researcher at plasma group 00:01:43.479 --> 00:01:46.830 align:start position:0% former plasma researcher at plasma group and<00:01:43.690> he<00:01:44.560> was<00:01:44.740> this<00:01:44.890> article<00:01:45.100> last<00:01:45.460> summer<00:01:45.840> so 00:01:46.830 --> 00:01:46.840 align:start position:0% and he was this article last summer so 00:01:46.840 --> 00:01:49.170 align:start position:0% and he was this article last summer so back<00:01:47.350> then<00:01:47.620> we<00:01:48.040> were<00:01:48.250> researching<00:01:48.580> all 00:01:49.170 --> 00:01:49.180 align:start position:0% back then we were researching all 00:01:49.180 --> 00:01:51.840 align:start position:0% back then we were researching all different<00:01:49.690> kinds<00:01:49.960> of<00:01:50.020> platinum<00:01:50.440> flavors<00:01:50.850> but 00:01:51.840 --> 00:01:51.850 align:start position:0% different kinds of platinum flavors but 00:01:51.850 --> 00:01:53.580 align:start position:0% different kinds of platinum flavors but it<00:01:52.090> took<00:01:52.270> us<00:01:52.420> like<00:01:52.630> a<00:01:52.690> whole<00:01:53.049> months<00:01:53.320> to 00:01:53.580 --> 00:01:53.590 align:start position:0% it took us like a whole months to 00:01:53.590 --> 00:01:56.700 align:start position:0% it took us like a whole months to convince<00:01:53.830> ourselves<00:01:54.360> why<00:01:55.380> exactly 00:01:56.700 --> 00:01:56.710 align:start position:0% convince ourselves why exactly 00:01:56.710 --> 00:01:58.280 align:start position:0% convince ourselves why exactly me<00:01:57.250> and<00:01:57.400> plasma<00:01:57.820> was 00:01:58.280 --> 00:01:58.290 align:start position:0% me and plasma was 00:01:58.290 --> 00:02:01.100 align:start position:0% me and plasma was really<00:01:58.560> feasible<00:01:58.770> and<00:01:59.630> after<00:02:00.630> reading<00:02:00.870> this 00:02:01.100 --> 00:02:01.110 align:start position:0% really feasible and after reading this 00:02:01.110 --> 00:02:03.890 align:start position:0% really feasible and after reading this post<00:02:01.410> we<00:02:02.220> thought<00:02:02.670> as<00:02:03.030> the<00:02:03.330> game<00:02:03.570> should<00:02:03.840> be 00:02:03.890 --> 00:02:03.900 align:start position:0% post we thought as the game should be 00:02:03.900 --> 00:02:06.230 align:start position:0% post we thought as the game should be really<00:02:04.350> really<00:02:04.710> application-specific 00:02:06.230 --> 00:02:06.240 align:start position:0% really really application-specific 00:02:06.240 --> 00:02:08.870 align:start position:0% really really application-specific then<00:02:07.200> we<00:02:07.590> concluded<00:02:08.130> that<00:02:08.160> there<00:02:08.580> should<00:02:08.729> be<00:02:08.850> a 00:02:08.870 --> 00:02:08.880 align:start position:0% then we concluded that there should be a 00:02:08.880 --> 00:02:11.440 align:start position:0% then we concluded that there should be a programming<00:02:09.390> language<00:02:09.500> they<00:02:10.500> can<00:02:10.560> handle 00:02:11.440 --> 00:02:11.450 align:start position:0% programming language they can handle 00:02:11.450 --> 00:02:14.260 align:start position:0% programming language they can handle application<00:02:12.450> specific<00:02:12.990> exit<00:02:13.410> games<00:02:13.650> instead 00:02:14.260 --> 00:02:14.270 align:start position:0% application specific exit games instead 00:02:14.270 --> 00:02:22.160 align:start position:0% application specific exit games instead so<00:02:16.040> so<00:02:18.650> unlikely<00:02:19.650> shoelace<00:02:20.520> focus<00:02:21.420> our 00:02:22.160 --> 00:02:22.170 align:start position:0% so so unlikely shoelace focus our 00:02:22.170 --> 00:02:27.350 align:start position:0% so so unlikely shoelace focus our research<00:02:23.090> scientists<00:02:24.530> she<00:02:25.530> hates<00:02:26.360> speciality 00:02:27.350 --> 00:02:27.360 align:start position:0% research scientists she hates speciality 00:02:27.360 --> 00:02:29.870 align:start position:0% research scientists she hates speciality was<00:02:27.660> designing<00:02:28.230> programming<00:02:29.160> language<00:02:29.580> to 00:02:29.870 --> 00:02:29.880 align:start position:0% was designing programming language to 00:02:29.880 --> 00:02:32.440 align:start position:0% was designing programming language to define<00:02:30.810> a<00:02:31.020> set<00:02:31.230> of<00:02:31.320> problems<00:02:31.560> that<00:02:32.040> can<00:02:32.220> handle 00:02:32.440 --> 00:02:32.450 align:start position:0% define a set of problems that can handle 00:02:32.450 --> 00:02:35.660 align:start position:0% define a set of problems that can handle we<00:02:33.450> decided<00:02:33.960> with<00:02:34.230> our<00:02:34.470> research<00:02:34.890> focus<00:02:35.400> on 00:02:35.660 --> 00:02:35.670 align:start position:0% we decided with our research focus on 00:02:35.670 --> 00:02:37.960 align:start position:0% we decided with our research focus on the<00:02:36.300> generalization<00:02:37.080> of<00:02:37.290> thousand 00:02:37.960 --> 00:02:37.970 align:start position:0% the generalization of thousand 00:02:37.970 --> 00:02:43.760 align:start position:0% the generalization of thousand applications<00:02:38.970> on<00:02:39.330> top<00:02:39.360> of<00:02:39.690> plasma<00:02:40.250> and<00:02:42.770> then 00:02:43.760 --> 00:02:43.770 align:start position:0% applications on top of plasma and then 00:02:43.770 --> 00:02:46.850 align:start position:0% applications on top of plasma and then we<00:02:43.980> decided<00:02:44.780> we<00:02:45.780> chose<00:02:46.080> partner<00:02:46.590> - 00:02:46.850 --> 00:02:46.860 align:start position:0% we decided we chose partner - 00:02:46.860 --> 00:02:50.500 align:start position:0% we decided we chose partner - construction<00:02:47.550> which<00:02:48.540> prioritizes<00:02:48.900> fury<00:02:49.709> over 00:02:50.500 --> 00:02:50.510 align:start position:0% construction which prioritizes fury over 00:02:50.510 --> 00:02:53.470 align:start position:0% construction which prioritizes fury over expressiveness<00:02:51.510> of<00:02:51.900> the<00:02:52.050> application<00:02:52.740> and 00:02:53.470 --> 00:02:53.480 align:start position:0% expressiveness of the application and 00:02:53.480 --> 00:02:56.210 align:start position:0% expressiveness of the application and immediately<00:02:54.480> immediately<00:02:54.930> started<00:02:55.770> working 00:02:56.210 --> 00:02:56.220 align:start position:0% immediately immediately started working 00:02:56.220 --> 00:03:01.120 align:start position:0% immediately immediately started working on<00:02:56.340> the<00:02:56.490> implementation<00:02:58.940> interested<00:02:59.940> and 00:03:01.120 --> 00:03:01.130 align:start position:0% on the implementation interested and 00:03:01.130 --> 00:03:04.960 align:start position:0% on the implementation interested and thanks<00:03:02.130> to<00:03:02.280> this<00:03:02.640> huge<00:03:03.090> effort<00:03:03.330> on 00:03:04.960 --> 00:03:04.970 align:start position:0% thanks to this huge effort on 00:03:04.970 --> 00:03:09.350 align:start position:0% thanks to this huge effort on implementation<00:03:06.739> went<00:03:07.739> forward<00:03:08.360> proceeded 00:03:09.350 --> 00:03:09.360 align:start position:0% implementation went forward proceeded 00:03:09.360 --> 00:03:12.470 align:start position:0% implementation went forward proceeded pretty<00:03:09.660> fast<00:03:09.989> and<00:03:10.320> we<00:03:11.070> titled<00:03:11.580> the<00:03:11.670> framework 00:03:12.470 --> 00:03:12.480 align:start position:0% pretty fast and we titled the framework 00:03:12.480 --> 00:03:15.350 align:start position:0% pretty fast and we titled the framework magma<00:03:13.080> chamber<00:03:13.470> and<00:03:13.709> introduced<00:03:14.640> it<00:03:14.850> at 00:03:15.350 --> 00:03:15.360 align:start position:0% magma chamber and introduced it at 00:03:15.360 --> 00:03:20.420 align:start position:0% magma chamber and introduced it at common<00:03:15.750> this<00:03:15.959> made<00:03:16.170> a<00:03:18.590> same<00:03:19.590> time<00:03:19.860> we<00:03:20.280> have 00:03:20.420 --> 00:03:20.430 align:start position:0% common this made a same time we have 00:03:20.430 --> 00:03:22.970 align:start position:0% common this made a same time we have been<00:03:20.459> writing<00:03:20.760> GOC<00:03:21.420> projects<00:03:21.870> but<00:03:22.380> all<00:03:22.709> our 00:03:22.970 --> 00:03:22.980 align:start position:0% been writing GOC projects but all our 00:03:22.980 --> 00:03:28.840 align:start position:0% been writing GOC projects but all our clients<00:03:23.510> for<00:03:24.510> example<00:03:24.570> we<00:03:25.440> developed<00:03:26.220> a 00:03:28.840 --> 00:03:28.850 align:start position:0% clients for example we developed a 00:03:28.850 --> 00:03:33.170 align:start position:0% clients for example we developed a trading<00:03:29.850> system<00:03:31.100> home<00:03:32.100> generated<00:03:32.730> and<00:03:32.910> a 00:03:33.170 --> 00:03:33.180 align:start position:0% trading system home generated and a 00:03:33.180 --> 00:03:35.710 align:start position:0% trading system home generated and a Christine<00:03:33.930> worship<00:03:34.410> electric<00:03:34.920> power<00:03:35.160> and 00:03:35.710 --> 00:03:35.720 align:start position:0% Christine worship electric power and 00:03:35.720 --> 00:03:39.350 align:start position:0% Christine worship electric power and also<00:03:36.720> we<00:03:37.050> we<00:03:37.830> cooperate<00:03:38.459> with<00:03:38.489> an<00:03:38.880> antique 00:03:39.350 --> 00:03:39.360 align:start position:0% also we we cooperate with an antique 00:03:39.360 --> 00:03:42.800 align:start position:0% also we we cooperate with an antique phone<00:03:39.900> company<00:03:40.350> to<00:03:40.800> research<00:03:41.450> cloud<00:03:42.450> main<00:03:42.660> use 00:03:42.800 --> 00:03:42.810 align:start position:0% phone company to research cloud main use 00:03:42.810 --> 00:03:44.370 align:start position:0% phone company to research cloud main use cases<00:03:43.110> on<00:03:43.530> their<00:03:43.800> platform 00:03:44.370 --> 00:03:44.380 align:start position:0% cases on their platform 00:03:44.380 --> 00:03:46.060 align:start position:0% cases on their platform [Music] 00:03:46.060 --> 00:03:46.070 align:start position:0% [Music] 00:03:46.070 --> 00:03:49.940 align:start position:0% [Music] I<00:03:47.150> just<00:03:48.150> wanna<00:03:48.330> stress<00:03:48.690> together<00:03:48.989> we<00:03:49.410> are<00:03:49.560> very 00:03:49.940 --> 00:03:49.950 align:start position:0% I just wanna stress together we are very 00:03:49.950 --> 00:03:52.180 align:start position:0% I just wanna stress together we are very very<00:03:50.190> grateful<00:03:50.940> to<00:03:51.600> another 00:03:52.180 --> 00:03:52.190 align:start position:0% very grateful to another 00:03:52.190 --> 00:03:54.520 align:start position:0% very grateful to another clients<00:03:52.640> because<00:03:53.330> without<00:03:53.540> them<00:03:53.930> we<00:03:54.170> wouldn't 00:03:54.520 --> 00:03:54.530 align:start position:0% clients because without them we wouldn't 00:03:54.530 --> 00:03:56.950 align:start position:0% clients because without them we wouldn't have<00:03:54.770> been<00:03:54.890> able<00:03:55.040> to<00:03:55.220> run<00:03:55.580> a<00:03:55.790> sustainable<00:03:56.450> R&D 00:03:56.950 --> 00:03:56.960 align:start position:0% have been able to run a sustainable R&D 00:03:56.960 --> 00:04:01.530 align:start position:0% have been able to run a sustainable R&D and<00:03:57.430> create<00:03:58.430> your<00:03:58.850> digital<00:03:59.630> plan<00:04:00.140> last<00:04:01.100> month 00:04:01.530 --> 00:04:01.540 align:start position:0% and create your digital plan last month 00:04:01.540 --> 00:04:06.250 align:start position:0% and create your digital plan last month but<00:04:03.370> however<00:04:04.370> sometimes<00:04:05.150> it<00:04:05.630> was<00:04:05.930> tough<00:04:06.230> to 00:04:06.250 --> 00:04:06.260 align:start position:0% but however sometimes it was tough to 00:04:06.260 --> 00:04:10.510 align:start position:0% but however sometimes it was tough to run<00:04:06.710> POC<00:04:07.580> projects<00:04:08.120> and<00:04:08.500> do<00:04:09.500> the<00:04:09.650> research<00:04:09.800> at 00:04:10.510 --> 00:04:10.520 align:start position:0% run POC projects and do the research at 00:04:10.520 --> 00:04:13.390 align:start position:0% run POC projects and do the research at the<00:04:10.730> same<00:04:10.940> time<00:04:11.240> because<00:04:12.110> POC<00:04:12.830> projects 00:04:13.390 --> 00:04:13.400 align:start position:0% the same time because POC projects 00:04:13.400 --> 00:04:15.730 align:start position:0% the same time because POC projects expecting<00:04:14.090> birth<00:04:14.330> and<00:04:14.570> the<00:04:14.960> base<00:04:15.140> design<00:04:15.530> of 00:04:15.730 --> 00:04:15.740 align:start position:0% expecting birth and the base design of 00:04:15.740 --> 00:04:22.300 align:start position:0% expecting birth and the base design of the<00:04:16.540> framework<00:04:17.540> it's<00:04:17.870> updated<00:04:18.470> so<00:04:20.380> here<00:04:21.380> after 00:04:22.300 --> 00:04:22.310 align:start position:0% the framework it's updated so here after 00:04:22.310 --> 00:04:25.630 align:start position:0% the framework it's updated so here after addcom<00:04:22.970> we<00:04:23.390> stopped<00:04:23.810> took<00:04:24.530> time<00:04:24.830> and<00:04:25.100> started 00:04:25.630 --> 00:04:25.640 align:start position:0% addcom we stopped took time and started 00:04:25.640 --> 00:04:28.510 align:start position:0% addcom we stopped took time and started linking<00:04:25.940> over<00:04:26.410> the<00:04:27.410> core<00:04:27.710> values<00:04:28.250> that<00:04:28.280> we 00:04:28.510 --> 00:04:28.520 align:start position:0% linking over the core values that we 00:04:28.520 --> 00:04:30.730 align:start position:0% linking over the core values that we want<00:04:28.760> to<00:04:28.940> create<00:04:29.180> in<00:04:29.450> our<00:04:29.570> framework<00:04:30.170> once 00:04:30.730 --> 00:04:30.740 align:start position:0% want to create in our framework once 00:04:30.740 --> 00:04:33.340 align:start position:0% want to create in our framework once again<00:04:31.330> so<00:04:32.330> here's<00:04:32.600> the<00:04:32.810> exact<00:04:33.080> conclusion 00:04:33.340 --> 00:04:33.350 align:start position:0% again so here's the exact conclusion 00:04:33.350 --> 00:04:39.280 align:start position:0% again so here's the exact conclusion that<00:04:34.220> they've<00:04:34.370> got<00:04:37.180> first<00:04:38.180> if<00:04:38.870> you<00:04:39.050> build 00:04:39.280 --> 00:04:39.290 align:start position:0% that they've got first if you build 00:04:39.290 --> 00:04:43.270 align:start position:0% that they've got first if you build applications<00:04:39.530> very<00:04:40.490> easily<00:04:41.080> so<00:04:42.280> boxing 00:04:43.270 --> 00:04:43.280 align:start position:0% applications very easily so boxing 00:04:43.280 --> 00:04:45.610 align:start position:0% applications very easily so boxing developers<00:04:43.790> will<00:04:44.000> be<00:04:44.180> able<00:04:44.210> to<00:04:44.750> application 00:04:45.610 --> 00:04:45.620 align:start position:0% developers will be able to application 00:04:45.620 --> 00:04:47.320 align:start position:0% developers will be able to application developers<00:04:46.130> will<00:04:46.370> be<00:04:46.490> able<00:04:46.520> to<00:04:46.970> build<00:04:47.180> their 00:04:47.320 --> 00:04:47.330 align:start position:0% developers will be able to build their 00:04:47.330 --> 00:04:50.380 align:start position:0% developers will be able to build their apps<00:04:47.570> both<00:04:48.170> LT<00:04:48.680> specific<00:04:49.220> features<00:04:49.610> such<00:04:50.360> as 00:04:50.380 --> 00:04:50.390 align:start position:0% apps both LT specific features such as 00:04:50.390 --> 00:04:52.900 align:start position:0% apps both LT specific features such as instant<00:04:51.200> payments<00:04:51.830> and<00:04:52.010> gaseous 00:04:52.900 --> 00:04:52.910 align:start position:0% instant payments and gaseous 00:04:52.910 --> 00:04:55.860 align:start position:0% instant payments and gaseous transactions<00:04:53.660> very<00:04:54.350> easily<00:04:54.770> model<00:04:55.310> as<00:04:55.520> well 00:04:55.860 --> 00:04:55.870 align:start position:0% transactions very easily model as well 00:04:55.870 --> 00:04:58.210 align:start position:0% transactions very easily model as well so<00:04:56.870> they<00:04:57.080> can<00:04:57.290> cut<00:04:57.500> the<00:04:57.680> repetitive<00:04:58.190> the 00:04:58.210 --> 00:04:58.220 align:start position:0% so they can cut the repetitive the 00:04:58.220 --> 00:05:01.330 align:start position:0% so they can cut the repetitive the moments<00:04:58.820> for<00:04:59.030> those<00:04:59.300> features<00:05:00.070> either<00:05:01.070> if 00:05:01.330 --> 00:05:01.340 align:start position:0% moments for those features either if 00:05:01.340 --> 00:05:03.790 align:start position:0% moments for those features either if they<00:05:01.520> use<00:05:01.730> a<00:05:01.760> framework<00:05:02.090> and<00:05:02.540> every<00:05:03.500> function 00:05:03.790 --> 00:05:03.800 align:start position:0% they use a framework and every function 00:05:03.800 --> 00:05:06.370 align:start position:0% they use a framework and every function application<00:05:04.430> developers<00:05:05.360> will<00:05:05.660> be<00:05:05.840> able<00:05:05.870> to 00:05:06.370 --> 00:05:06.380 align:start position:0% application developers will be able to 00:05:06.380 --> 00:05:09.190 align:start position:0% application developers will be able to fold<00:05:06.950> them<00:05:07.190> in<00:05:07.370> the<00:05:07.580> same<00:05:08.570> manner<00:05:08.810> from 00:05:09.190 --> 00:05:09.200 align:start position:0% fold them in the same manner from 00:05:09.200 --> 00:05:11.440 align:start position:0% fold them in the same manner from foreigners<00:05:10.130> to<00:05:10.640> a<00:05:10.910> skilled<00:05:11.270> software 00:05:11.440 --> 00:05:11.450 align:start position:0% foreigners to a skilled software 00:05:11.450 --> 00:05:16.450 align:start position:0% foreigners to a skilled software engineers<00:05:13.660> the<00:05:14.660> second<00:05:15.080> thing<00:05:15.290> is<00:05:15.650> you<00:05:16.280> can 00:05:16.450 --> 00:05:16.460 align:start position:0% engineers the second thing is you can 00:05:16.460 --> 00:05:19.450 align:start position:0% engineers the second thing is you can build<00:05:16.669> applications<00:05:16.880> securely<00:05:18.070> so<00:05:19.070> the 00:05:19.450 --> 00:05:19.460 align:start position:0% build applications securely so the 00:05:19.460 --> 00:05:22.270 align:start position:0% build applications securely so the expression<00:05:20.090> of<00:05:20.390> all<00:05:20.690> the<00:05:20.750> fraud<00:05:21.280> Reformation 00:05:22.270 --> 00:05:22.280 align:start position:0% expression of all the fraud Reformation 00:05:22.280 --> 00:05:24.850 align:start position:0% expression of all the fraud Reformation is<00:05:22.870> standardized<00:05:23.870> with<00:05:24.200> a<00:05:24.260> universal 00:05:24.850 --> 00:05:24.860 align:start position:0% is standardized with a universal 00:05:24.860 --> 00:05:29.110 align:start position:0% is standardized with a universal notation<00:05:25.690> so<00:05:26.690> before<00:05:27.340> discussing<00:05:28.340> all<00:05:28.820> the 00:05:29.110 --> 00:05:29.120 align:start position:0% notation so before discussing all the 00:05:29.120 --> 00:05:32.440 align:start position:0% notation so before discussing all the different<00:05:29.720> types<00:05:29.900> of<00:05:30.050> exit<00:05:30.470> games<00:05:31.419> by<00:05:32.419> a 00:05:32.440 --> 00:05:32.450 align:start position:0% different types of exit games by a 00:05:32.450 --> 00:05:32.950 align:start position:0% different types of exit games by a natural 00:05:32.950 --> 00:05:32.960 align:start position:0% natural 00:05:32.960 --> 00:05:36.370 align:start position:0% natural and<00:05:33.740> improving<00:05:34.639> the<00:05:35.240> security<00:05:35.389> of<00:05:35.750> the<00:05:36.050> design 00:05:36.370 --> 00:05:36.380 align:start position:0% and improving the security of the design 00:05:36.380 --> 00:05:39.749 align:start position:0% and improving the security of the design was<00:05:37.100> very<00:05:37.370> challenging<00:05:37.729> and<00:05:38.360> time-consuming 00:05:39.749 --> 00:05:39.759 align:start position:0% was very challenging and time-consuming 00:05:39.759 --> 00:05:43.570 align:start position:0% was very challenging and time-consuming time-consuming<00:05:40.990> but<00:05:41.990> now<00:05:42.430> with<00:05:43.430> an 00:05:43.570 --> 00:05:43.580 align:start position:0% time-consuming but now with an 00:05:43.580 --> 00:05:45.939 align:start position:0% time-consuming but now with an application<00:05:44.210> framework<00:05:44.500> it's<00:05:45.500> going<00:05:45.770> to<00:05:45.860> be 00:05:45.939 --> 00:05:45.949 align:start position:0% application framework it's going to be 00:05:45.949 --> 00:05:48.550 align:start position:0% application framework it's going to be much<00:05:46.190> easier<00:05:46.430> to<00:05:46.610> check<00:05:47.030> and<00:05:47.470> strengthen<00:05:48.470> the 00:05:48.550 --> 00:05:48.560 align:start position:0% much easier to check and strengthen the 00:05:48.560 --> 00:05:51.510 align:start position:0% much easier to check and strengthen the security<00:05:48.710> of<00:05:48.979> the<00:05:49.220> design<00:05:49.580> from<00:05:50.330> two<00:05:50.509> aspects 00:05:51.510 --> 00:05:51.520 align:start position:0% security of the design from two aspects 00:05:51.520 --> 00:05:54.730 align:start position:0% security of the design from two aspects the<00:05:52.520> first<00:05:53.030> one<00:05:53.300> is<00:05:53.539> you<00:05:53.960> will<00:05:54.139> simply<00:05:54.500> write 00:05:54.730 --> 00:05:54.740 align:start position:0% the first one is you will simply write 00:05:54.740 --> 00:05:57.580 align:start position:0% the first one is you will simply write less<00:05:55.669> code<00:05:55.699> so<00:05:56.509> there's<00:05:57.020> going<00:05:57.169> to<00:05:57.229> be<00:05:57.289> a<00:05:57.380> few 00:05:57.580 --> 00:05:57.590 align:start position:0% less code so there's going to be a few 00:05:57.590 --> 00:06:00.550 align:start position:0% less code so there's going to be a few of<00:05:57.680> potential<00:05:57.979> bugs<00:05:58.370> and<00:05:58.990> the<00:05:59.990> second<00:06:00.319> thing 00:06:00.550 --> 00:06:00.560 align:start position:0% of potential bugs and the second thing 00:06:00.560 --> 00:06:03.430 align:start position:0% of potential bugs and the second thing is<00:06:00.889> acclaims<00:06:01.849> design<00:06:02.389> for<00:06:02.599> an<00:06:02.720> application 00:06:03.430 --> 00:06:03.440 align:start position:0% is acclaims design for an application 00:06:03.440 --> 00:06:06.159 align:start position:0% is acclaims design for an application will<00:06:03.949> be<00:06:03.979> interpreted<00:06:04.849> in<00:06:04.970> smart<00:06:05.599> contracts 00:06:06.159 --> 00:06:06.169 align:start position:0% will be interpreted in smart contracts 00:06:06.169 --> 00:06:11.260 align:start position:0% will be interpreted in smart contracts and<00:06:06.320> client<00:06:07.099> by<00:06:07.849> the<00:06:07.910> same<00:06:08.210> interface<00:06:08.830> so<00:06:10.270> so 00:06:11.260 --> 00:06:11.270 align:start position:0% and client by the same interface so so 00:06:11.270 --> 00:06:13.240 align:start position:0% and client by the same interface so so in<00:06:11.449> the<00:06:11.479> same<00:06:11.690> manner<00:06:11.960> so<00:06:12.470> there's<00:06:13.009> going<00:06:13.190> to 00:06:13.240 --> 00:06:13.250 align:start position:0% in the same manner so there's going to 00:06:13.250 --> 00:06:18.460 align:start position:0% in the same manner so there's going to be<00:06:13.310> you<00:06:13.639> can<00:06:14.120> reduce<00:06:14.509> bugs<00:06:15.940> and<00:06:17.229> the<00:06:18.229> third 00:06:18.460 --> 00:06:18.470 align:start position:0% be you can reduce bugs and the third 00:06:18.470 --> 00:06:20.400 align:start position:0% be you can reduce bugs and the third thing<00:06:18.710> is<00:06:19.039> you<00:06:19.310> can<00:06:19.490> build<00:06:19.669> application 00:06:20.400 --> 00:06:20.410 align:start position:0% thing is you can build application 00:06:20.410 --> 00:06:24.899 align:start position:0% thing is you can build application flexibly<00:06:22.090> so<00:06:23.259> block<00:06:24.259> sheet<00:06:24.500> average 00:06:24.899 --> 00:06:24.909 align:start position:0% flexibly so block sheet average 00:06:24.909 --> 00:06:27.370 align:start position:0% flexibly so block sheet average application<00:06:25.909> developers<00:06:26.419> will<00:06:26.720> be<00:06:26.900> able<00:06:26.930> to 00:06:27.370 --> 00:06:27.380 align:start position:0% application developers will be able to 00:06:27.380 --> 00:06:30.430 align:start position:0% application developers will be able to vote<00:06:27.530> apps<00:06:27.919> with<00:06:28.930> decomposable<00:06:29.930> building 00:06:30.430 --> 00:06:30.440 align:start position:0% vote apps with decomposable building 00:06:30.440 --> 00:06:34.990 align:start position:0% vote apps with decomposable building blocks<00:06:31.539> dick<00:06:32.539> him<00:06:32.750> we<00:06:33.440> used<00:06:33.470> in<00:06:34.460> composite 00:06:34.990 --> 00:06:35.000 align:start position:0% blocks dick him we used in composite 00:06:35.000 --> 00:06:36.999 align:start position:0% blocks dick him we used in composite because<00:06:35.210> of<00:06:35.930> our<00:06:36.080> building<00:06:36.409> blocks<00:06:36.620> or 00:06:36.999 --> 00:06:37.009 align:start position:0% because of our building blocks or 00:06:37.009 --> 00:06:40.420 align:start position:0% because of our building blocks or different<00:06:37.400> types<00:06:37.610> of<00:06:38.320> applications<00:06:39.430> for 00:06:40.420 --> 00:06:40.430 align:start position:0% different types of applications for 00:06:40.430 --> 00:06:43.270 align:start position:0% different types of applications for example<00:06:40.960> essentially<00:06:41.960> plasma<00:06:42.770> and<00:06:43.009> state 00:06:43.270 --> 00:06:43.280 align:start position:0% example essentially plasma and state 00:06:43.280 --> 00:06:46.089 align:start position:0% example essentially plasma and state channels<00:06:43.669> can<00:06:44.300> be<00:06:44.330> built<00:06:44.720> with<00:06:45.050> exact<00:06:45.440> common 00:06:46.089 --> 00:06:46.099 align:start position:0% channels can be built with exact common 00:06:46.099 --> 00:06:51.640 align:start position:0% channels can be built with exact common components<00:06:48.820> and<00:06:49.820> then<00:06:50.000> this<00:06:50.419> income<00:06:50.900> from 00:06:51.640 --> 00:06:51.650 align:start position:0% components and then this income from 00:06:51.650 --> 00:06:54.640 align:start position:0% components and then this income from position<00:06:52.219> and<00:06:52.870> reconstruction<00:06:53.870> is<00:06:54.169> a<00:06:54.349> huge 00:06:54.640 --> 00:06:54.650 align:start position:0% position and reconstruction is a huge 00:06:54.650 --> 00:06:58.450 align:start position:0% position and reconstruction is a huge goal<00:06:54.889> in<00:06:55.190> the<00:06:55.849> abstraction<00:06:56.419> of<00:06:56.750> layer<00:06:57.020> 2<00:06:57.460> but 00:06:58.450 --> 00:06:58.460 align:start position:0% goal in the abstraction of layer 2 but 00:06:58.460 --> 00:07:01.089 align:start position:0% goal in the abstraction of layer 2 but the<00:06:58.669> impossible<00:06:59.599> combination<00:06:59.750> of<00:07:00.380> all<00:07:00.800> these 00:07:01.089 --> 00:07:01.099 align:start position:0% the impossible combination of all these 00:07:01.099 --> 00:07:03.070 align:start position:0% the impossible combination of all these little<00:07:01.789> building<00:07:02.300> blocks<00:07:02.330> will<00:07:02.870> be 00:07:03.070 --> 00:07:03.080 align:start position:0% little building blocks will be 00:07:03.080 --> 00:07:05.969 align:start position:0% little building blocks will be automatically<00:07:04.070> deducted<00:07:04.340> by<00:07:04.880> a<00:07:04.909> compiler<00:07:05.449> and 00:07:05.969 --> 00:07:05.979 align:start position:0% automatically deducted by a compiler and 00:07:05.979 --> 00:07:09.100 align:start position:0% automatically deducted by a compiler and you<00:07:06.979> me<00:07:07.130> you<00:07:07.460> me<00:07:07.490> you<00:07:07.639> will<00:07:08.270> be<00:07:08.300> able<00:07:08.719> to<00:07:08.870> know 00:07:09.100 --> 00:07:09.110 align:start position:0% you me you me you will be able to know 00:07:09.110 --> 00:07:11.709 align:start position:0% you me you me you will be able to know that<00:07:09.349> it<00:07:09.620> doesn't<00:07:09.830> work<00:07:10.070> as<00:07:10.370> an<00:07:11.210> application 00:07:11.709 --> 00:07:11.719 align:start position:0% that it doesn't work as an application 00:07:11.719 --> 00:07:18.070 align:start position:0% that it doesn't work as an application beforehand<00:07:14.889> so<00:07:16.419> teeny 00:07:18.070 --> 00:07:18.080 align:start position:0% beforehand so teeny 00:07:18.080 --> 00:07:22.839 align:start position:0% beforehand so teeny these<00:07:18.379> three<00:07:18.710> values<00:07:20.080> we<00:07:21.080> decided<00:07:21.680> to<00:07:21.919> discuss 00:07:22.839 --> 00:07:22.849 align:start position:0% these three values we decided to discuss 00:07:22.849 --> 00:07:25.300 align:start position:0% these three values we decided to discuss there<00:07:23.449> should<00:07:23.720> definitely<00:07:23.900> be<00:07:24.470> a<00:07:24.830> universal 00:07:25.300 --> 00:07:25.310 align:start position:0% there should definitely be a universal 00:07:25.310 --> 00:07:28.749 align:start position:0% there should definitely be a universal language<00:07:25.430> for<00:07:25.909> help<00:07:26.539> there<00:07:26.870> too<00:07:27.250> so<00:07:28.250> there's<00:07:28.669> a 00:07:28.749 --> 00:07:28.759 align:start position:0% language for help there too so there's a 00:07:28.759 --> 00:07:30.760 align:start position:0% language for help there too so there's a saying<00:07:29.030> that<00:07:29.150> math<00:07:29.780> did<00:07:30.020> not<00:07:30.199> alone 00:07:30.760 --> 00:07:30.770 align:start position:0% saying that math did not alone 00:07:30.770 --> 00:07:32.800 align:start position:0% saying that math did not alone pretty<00:07:31.129> fast<00:07:31.430> until<00:07:31.940> some<00:07:32.210> early<00:07:32.509> year 00:07:32.800 --> 00:07:32.810 align:start position:0% pretty fast until some early year 00:07:32.810 --> 00:07:35.200 align:start position:0% pretty fast until some early year because<00:07:33.710> there<00:07:33.860> was<00:07:33.979> no<00:07:34.159> universal<00:07:34.639> notation 00:07:35.200 --> 00:07:35.210 align:start position:0% because there was no universal notation 00:07:35.210 --> 00:07:38.020 align:start position:0% because there was no universal notation to<00:07:35.449> describe<00:07:35.629> all<00:07:36.440> the<00:07:36.770> basic<00:07:37.129> math<00:07:37.400> equations 00:07:38.020 --> 00:07:38.030 align:start position:0% to describe all the basic math equations 00:07:38.030 --> 00:07:42.189 align:start position:0% to describe all the basic math equations that<00:07:38.300> we're<00:07:38.509> now<00:07:38.750> very<00:07:39.470> familiar<00:07:39.919> well<00:07:40.490> and<00:07:41.199> if 00:07:42.189 --> 00:07:42.199 align:start position:0% that we're now very familiar well and if 00:07:42.199 --> 00:07:44.529 align:start position:0% that we're now very familiar well and if you're<00:07:42.440> familiar<00:07:42.650> with<00:07:43.099> all<00:07:43.310> the<00:07:43.580> discussions 00:07:44.529 --> 00:07:44.539 align:start position:0% you're familiar with all the discussions 00:07:44.539 --> 00:07:47.950 align:start position:0% you're familiar with all the discussions and<00:07:44.870> proposal<00:07:45.770> made<00:07:46.159> today<00:07:46.699> in<00:07:47.539> research 00:07:47.950 --> 00:07:47.960 align:start position:0% and proposal made today in research 00:07:47.960 --> 00:07:52.689 align:start position:0% and proposal made today in research before<00:07:48.379> you<00:07:49.060> probably<00:07:50.060> know<00:07:50.330> that<00:07:51.669> every<00:07:52.669> time 00:07:52.689 --> 00:07:52.699 align:start position:0% before you probably know that every time 00:07:52.699 --> 00:07:55.749 align:start position:0% before you probably know that every time making<00:07:53.180> a<00:07:53.240> post<00:07:53.509> you<00:07:54.039> always<00:07:55.039> had<00:07:55.219> to<00:07:55.250> write<00:07:55.520> so 00:07:55.749 --> 00:07:55.759 align:start position:0% making a post you always had to write so 00:07:55.759 --> 00:07:59.649 align:start position:0% making a post you always had to write so many<00:07:55.969> definitions<00:07:56.240> at<00:07:56.690> first<00:07:56.960> and<00:07:57.940> point<00:07:58.940> we 00:07:59.649 --> 00:07:59.659 align:start position:0% many definitions at first and point we 00:07:59.659 --> 00:08:02.140 align:start position:0% many definitions at first and point we started<00:08:00.319> wondering<00:08:00.500> maybe<00:08:01.340> it's<00:08:01.639> better<00:08:01.909> to 00:08:02.140 --> 00:08:02.150 align:start position:0% started wondering maybe it's better to 00:08:02.150 --> 00:08:04.899 align:start position:0% started wondering maybe it's better to create<00:08:02.300> some<00:08:02.870> Universal<00:08:03.590> way<00:08:03.770> to<00:08:03.830> melted<00:08:04.430> all 00:08:04.899 --> 00:08:04.909 align:start position:0% create some Universal way to melted all 00:08:04.909 --> 00:08:07.360 align:start position:0% create some Universal way to melted all different<00:08:05.479> kinds<00:08:05.780> of<00:08:05.870> predicates<00:08:06.409> for<00:08:06.650> last 00:08:07.360 --> 00:08:07.370 align:start position:0% different kinds of predicates for last 00:08:07.370 --> 00:08:10.869 align:start position:0% different kinds of predicates for last month<00:08:07.610> and<00:08:08.060> we<00:08:08.719> thought<00:08:08.930> it<00:08:09.289> would<00:08:09.469> bring<00:08:09.879> more 00:08:10.869 --> 00:08:10.879 align:start position:0% month and we thought it would bring more 00:08:10.879 --> 00:08:14.110 align:start position:0% month and we thought it would bring more efficiency<00:08:11.599> and<00:08:12.190> in<00:08:13.190> the<00:08:13.370> communication 00:08:14.110 --> 00:08:14.120 align:start position:0% efficiency and in the communication 00:08:14.120 --> 00:08:16.689 align:start position:0% efficiency and in the communication between<00:08:14.270> researchers<00:08:15.020> and<00:08:15.310> be<00:08:16.310> able<00:08:16.580> to 00:08:16.689 --> 00:08:16.699 align:start position:0% between researchers and be able to 00:08:16.699 --> 00:08:19.089 align:start position:0% between researchers and be able to provide<00:08:17.120> them<00:08:17.360> with<00:08:17.629> more<00:08:18.169> logical<00:08:18.889> way<00:08:19.069> to 00:08:19.089 --> 00:08:19.099 align:start position:0% provide them with more logical way to 00:08:19.099 --> 00:08:22.029 align:start position:0% provide them with more logical way to prove<00:08:19.580> this<00:08:19.759> beauty<00:08:20.199> so<00:08:21.199> if<00:08:21.469> you<00:08:21.620> want<00:08:21.770> to<00:08:21.860> know 00:08:22.029 --> 00:08:22.039 align:start position:0% prove this beauty so if you want to know 00:08:22.039 --> 00:08:25.149 align:start position:0% prove this beauty so if you want to know more<00:08:22.370> detail<00:08:22.789> but<00:08:23.090> we<00:08:23.840> describe<00:08:24.319> that<00:08:24.620> in<00:08:24.889> our 00:08:25.149 --> 00:08:25.159 align:start position:0% more detail but we describe that in our 00:08:25.159 --> 00:08:28.330 align:start position:0% more detail but we describe that in our class<00:08:26.060> memory<00:08:26.389> predicates<00:08:27.259> research<00:08:27.770> repo<00:08:28.130> on 00:08:28.330 --> 00:08:28.340 align:start position:0% class memory predicates research repo on 00:08:28.340 --> 00:08:31.870 align:start position:0% class memory predicates research repo on our<00:08:28.460> github<00:08:28.759> and<00:08:29.360> when<00:08:30.169> we<00:08:30.259> first<00:08:30.520> saw<00:08:31.520> thought 00:08:31.870 --> 00:08:31.880 align:start position:0% our github and when we first saw thought 00:08:31.880 --> 00:08:38.290 align:start position:0% our github and when we first saw thought of<00:08:32.089> the<00:08:32.409> plasma<00:08:33.409> predicate<00:08:34.070> in<00:08:34.250> song<00:08:37.300> then 00:08:38.290 --> 00:08:38.300 align:start position:0% of the plasma predicate in song then 00:08:38.300 --> 00:08:43.060 align:start position:0% of the plasma predicate in song then plasma<00:08:39.079> group<00:08:39.729> proposed<00:08:40.729> obn<00:08:41.570> and<00:08:41.899> as<00:08:42.829> soon<00:08:43.039> as 00:08:43.060 --> 00:08:43.070 align:start position:0% plasma group proposed obn and as soon as 00:08:43.070 --> 00:08:45.940 align:start position:0% plasma group proposed obn and as soon as it<00:08:43.310> was<00:08:43.430> proposed<00:08:43.849> we<00:08:44.390> decided<00:08:44.839> to<00:08:44.990> go<00:08:45.170> over<00:08:45.800> it 00:08:45.940 --> 00:08:45.950 align:start position:0% it was proposed we decided to go over it 00:08:45.950 --> 00:08:48.120 align:start position:0% it was proposed we decided to go over it because<00:08:46.250> that<00:08:46.640> was<00:08:46.820> exactly<00:08:46.970> what<00:08:47.390> we<00:08:47.660> wanted 00:08:48.120 --> 00:08:48.130 align:start position:0% because that was exactly what we wanted 00:08:48.130 --> 00:08:54.480 align:start position:0% because that was exactly what we wanted and<00:08:51.820> what<00:08:52.820> does<00:08:53.360> it<00:08:53.480> really<00:08:53.810> mean<00:08:53.959> to 00:08:54.480 --> 00:08:54.490 align:start position:0% and what does it really mean to 00:08:54.490 --> 00:08:57.880 align:start position:0% and what does it really mean to generalize<00:08:55.490> all<00:08:56.390> the<00:08:56.779> Frog<00:08:57.020> group<00:08:57.350> secondly 00:08:57.880 --> 00:08:57.890 align:start position:0% generalize all the Frog group secondly 00:08:57.890 --> 00:09:02.590 align:start position:0% generalize all the Frog group secondly of<00:08:58.160> solutions<00:09:00.160> putting<00:09:01.160> it's<00:09:01.370> a<00:09:01.610> simple<00:09:02.000> word 00:09:02.590 --> 00:09:02.600 align:start position:0% of solutions putting it's a simple word 00:09:02.600 --> 00:09:06.000 align:start position:0% of solutions putting it's a simple word I<00:09:02.630> think<00:09:03.500> frog<00:09:03.920> proof<00:09:04.250> can<00:09:04.610> be<00:09:05.089> compared<00:09:05.810> to 00:09:06.000 --> 00:09:06.010 align:start position:0% I think frog proof can be compared to 00:09:06.010 --> 00:09:08.439 align:start position:0% I think frog proof can be compared to traditional<00:09:07.010> system<00:09:07.699> all<00:09:07.880> of<00:09:08.089> them<00:09:08.240> can 00:09:08.439 --> 00:09:08.449 align:start position:0% traditional system all of them can 00:09:08.449 --> 00:09:08.940 align:start position:0% traditional system all of them can become 00:09:08.940 --> 00:09:08.950 align:start position:0% become 00:09:08.950 --> 00:09:12.269 align:start position:0% become judicial<00:09:09.610> system<00:09:10.470> there<00:09:11.470> is<00:09:11.500> a<00:09:11.620> constitution 00:09:12.269 --> 00:09:12.279 align:start position:0% judicial system there is a constitution 00:09:12.279 --> 00:09:14.639 align:start position:0% judicial system there is a constitution a<00:09:12.579> strongest<00:09:13.180> though<00:09:13.389> sitting<00:09:13.899> on<00:09:14.050> a<00:09:14.200> pagan 00:09:14.639 --> 00:09:14.649 align:start position:0% a strongest though sitting on a pagan 00:09:14.649 --> 00:09:17.850 align:start position:0% a strongest though sitting on a pagan and<00:09:15.269> in<00:09:16.269> the<00:09:16.420> case<00:09:16.660> of<00:09:17.019> a<00:09:17.260> chain<00:09:17.529> it<00:09:17.769> is 00:09:17.850 --> 00:09:17.860 align:start position:0% and in the case of a chain it is 00:09:17.860 --> 00:09:21.449 align:start position:0% and in the case of a chain it is immutable<00:09:18.360> but<00:09:19.360> the<00:09:19.450> point<00:09:19.720> here<00:09:19.810> as<00:09:20.459> brother 00:09:21.449 --> 00:09:21.459 align:start position:0% immutable but the point here as brother 00:09:21.459 --> 00:09:24.120 align:start position:0% immutable but the point here as brother is<00:09:21.639> plasma<00:09:22.209> state<00:09:22.870> general<00:09:23.260> we're<00:09:23.589> optimistic 00:09:24.120 --> 00:09:24.130 align:start position:0% is plasma state general we're optimistic 00:09:24.130 --> 00:09:28.439 align:start position:0% is plasma state general we're optimistic rola<00:09:25.500> all<00:09:26.500> the<00:09:26.889> claims<00:09:27.220> submitted<00:09:28.029> from<00:09:28.300> the 00:09:28.439 --> 00:09:28.449 align:start position:0% rola all the claims submitted from the 00:09:28.449 --> 00:09:30.660 align:start position:0% rola all the claims submitted from the second<00:09:28.810> layer<00:09:28.990> to<00:09:29.560> the<00:09:29.709> strong<00:09:29.980> strongest 00:09:30.660 --> 00:09:30.670 align:start position:0% second layer to the strong strongest 00:09:30.670 --> 00:09:33.420 align:start position:0% second layer to the strong strongest well<00:09:30.850> the<00:09:31.089> Constitution<00:09:31.810> will<00:09:32.440> be<00:09:32.649> following 00:09:33.420 --> 00:09:33.430 align:start position:0% well the Constitution will be following 00:09:33.430 --> 00:09:36.000 align:start position:0% well the Constitution will be following the<00:09:33.639> same<00:09:33.820> format<00:09:34.269> and<00:09:34.600> it<00:09:35.470> is<00:09:35.500> on<00:09:35.709> claiming 00:09:36.000 --> 00:09:36.010 align:start position:0% the same format and it is on claiming 00:09:36.010 --> 00:09:43.410 align:start position:0% the same format and it is on claiming property<00:09:39.449> so<00:09:40.449> how<00:09:41.079> did<00:09:41.350> it<00:09:41.529> exempt<00:09:42.100> the<00:09:42.420> state 00:09:43.410 --> 00:09:43.420 align:start position:0% property so how did it exempt the state 00:09:43.420 --> 00:09:46.860 align:start position:0% property so how did it exempt the state claimed<00:09:43.990> this<00:09:44.920> information<00:09:45.699> is<00:09:45.850> correct<00:09:46.120> to 00:09:46.860 --> 00:09:46.870 align:start position:0% claimed this information is correct to 00:09:46.870 --> 00:09:53.430 align:start position:0% claimed this information is correct to the<00:09:51.060> Constitution<00:09:52.060> the<00:09:52.690> example<00:09:53.139> that<00:09:53.170> I<00:09:53.350> used 00:09:53.430 --> 00:09:53.440 align:start position:0% the Constitution the example that I used 00:09:53.440 --> 00:09:55.680 align:start position:0% the Constitution the example that I used on<00:09:54.010> the<00:09:54.519> strongest<00:09:54.910> lobe<00:09:55.180> is<00:09:55.389> called 00:09:55.680 --> 00:09:55.690 align:start position:0% on the strongest lobe is called 00:09:55.690 --> 00:09:59.269 align:start position:0% on the strongest lobe is called adjudication<00:09:56.440> contracts<00:09:57.010> on<00:09:57.300> Ethernet<00:09:58.300> and 00:09:59.269 --> 00:09:59.279 align:start position:0% adjudication contracts on Ethernet and 00:09:59.279 --> 00:10:03.569 align:start position:0% adjudication contracts on Ethernet and then<00:10:00.510> how<00:10:01.510> do<00:10:01.570> you<00:10:01.930> exactly<00:10:02.589> claim<00:10:02.920> that<00:10:03.220> some 00:10:03.569 --> 00:10:03.579 align:start position:0% then how do you exactly claim that some 00:10:03.579 --> 00:10:06.740 align:start position:0% then how do you exactly claim that some information<00:10:03.850> is<00:10:04.329> correct<00:10:04.720> to<00:10:05.380> New<00:10:05.560> Jersey 00:10:06.740 --> 00:10:06.750 align:start position:0% information is correct to New Jersey 00:10:06.750 --> 00:10:11.370 align:start position:0% information is correct to New Jersey here<00:10:07.750> you<00:10:08.079> use<00:10:08.550> first<00:10:09.550> order<00:10:09.970> logic<00:10:10.380> first 00:10:11.370 --> 00:10:11.380 align:start position:0% here you use first order logic first 00:10:11.380 --> 00:10:14.430 align:start position:0% here you use first order logic first order<00:10:11.769> logic<00:10:11.980> is<00:10:12.480> preposition<00:10:13.480> that<00:10:13.930> contains 00:10:14.430 --> 00:10:14.440 align:start position:0% order logic is preposition that contains 00:10:14.440 --> 00:10:18.720 align:start position:0% order logic is preposition that contains sentences<00:10:15.160> with<00:10:15.490> 25<00:10:16.449> variables<00:10:17.260> for<00:10:18.250> example 00:10:18.720 --> 00:10:18.730 align:start position:0% sentences with 25 variables for example 00:10:18.730 --> 00:10:21.340 align:start position:0% sentences with 25 variables for example if<00:10:18.880> you<00:10:19.029> an<00:10:19.149> estate<00:10:19.570> that<00:10:19.600> taro<00:10:20.350> is<00:10:20.680> a 00:10:21.340 --> 00:10:21.350 align:start position:0% if you an estate that taro is a 00:10:21.350 --> 00:10:23.920 align:start position:0% if you an estate that taro is a and<00:10:22.040> you<00:10:22.430> can<00:10:22.610> claim<00:10:22.910> the<00:10:22.940> sentence<00:10:23.570> in<00:10:23.750> this 00:10:23.920 --> 00:10:23.930 align:start position:0% and you can claim the sentence in this 00:10:23.930 --> 00:10:27.490 align:start position:0% and you can claim the sentence in this format<00:10:24.350> there<00:10:25.160> exists<00:10:25.730> X<00:10:26.090> such<00:10:26.300> that<00:10:26.720> X<00:10:27.080> s 00:10:27.490 --> 00:10:27.500 align:start position:0% format there exists X such that X s 00:10:27.500 --> 00:10:31.470 align:start position:0% format there exists X such that X s Kotaro<00:10:28.190> and<00:10:28.580> X<00:10:29.120> is<00:10:29.300> ax<00:10:29.330> men<00:10:29.690> where<00:10:30.410> there<00:10:30.950> exist 00:10:31.470 --> 00:10:31.480 align:start position:0% Kotaro and X is ax men where there exist 00:10:31.480 --> 00:10:35.350 align:start position:0% Kotaro and X is ax men where there exist works<00:10:32.480> as<00:10:32.750> a<00:10:32.780> quantifier<00:10:33.530> and<00:10:33.860> X<00:10:34.670> is<00:10:34.970> work 00:10:35.350 --> 00:10:35.360 align:start position:0% works as a quantifier and X is work 00:10:35.360 --> 00:10:38.850 align:start position:0% works as a quantifier and X is work center<00:10:35.750> variable<00:10:36.200> and<00:10:37.180> OPM<00:10:38.180> employed<00:10:38.660> this 00:10:38.850 --> 00:10:38.860 align:start position:0% center variable and OPM employed this 00:10:38.860 --> 00:10:40.840 align:start position:0% center variable and OPM employed this standardized<00:10:39.860> notation 00:10:40.840 --> 00:10:40.850 align:start position:0% standardized notation 00:10:40.850 --> 00:10:42.760 align:start position:0% standardized notation they<00:10:41.120> expressed<00:10:41.750> all<00:10:41.990> different<00:10:42.350> kind<00:10:42.590> of 00:10:42.760 --> 00:10:42.770 align:start position:0% they expressed all different kind of 00:10:42.770 --> 00:10:46.450 align:start position:0% they expressed all different kind of properties<00:10:44.230> to<00:10:45.230> the<00:10:45.380> adjudication<00:10:45.890> contract 00:10:46.450 --> 00:10:46.460 align:start position:0% properties to the adjudication contract 00:10:46.460 --> 00:10:51.040 align:start position:0% properties to the adjudication contract and<00:10:48.220> so<00:10:49.220> let's<00:10:49.490> see<00:10:49.670> some<00:10:49.910> examples<00:10:50.060> of<00:10:50.870> the 00:10:51.040 --> 00:10:51.050 align:start position:0% and so let's see some examples of the 00:10:51.050 --> 00:10:54.750 align:start position:0% and so let's see some examples of the quantifiers<00:10:51.730> so<00:10:52.730> in<00:10:53.240> the<00:10:53.420> eunice<00:10:53.720> state 00:10:54.750 --> 00:10:54.760 align:start position:0% quantifiers so in the eunice state 00:10:54.760 --> 00:10:58.480 align:start position:0% quantifiers so in the eunice state something<00:10:55.760> this<00:10:56.630> injured<00:10:57.320> neat<00:10:57.650> feature<00:10:57.980> only 00:10:58.480 --> 00:10:58.490 align:start position:0% something this injured neat feature only 00:10:58.490 --> 00:11:01.450 align:start position:0% something this injured neat feature only comment<00:10:58.970> then<00:10:59.510> you<00:10:59.720> have<00:10:59.930> to<00:11:00.080> use<00:11:00.460> universal 00:11:01.450 --> 00:11:01.460 align:start position:0% comment then you have to use universal 00:11:01.460 --> 00:11:04.330 align:start position:0% comment then you have to use universal quantifier<00:11:02.110> for<00:11:03.110> example<00:11:03.590> you<00:11:03.710> have<00:11:03.920> if<00:11:04.130> you 00:11:04.330 --> 00:11:04.340 align:start position:0% quantifier for example you have if you 00:11:04.340 --> 00:11:07.930 align:start position:0% quantifier for example you have if you want<00:11:04.370> to<00:11:04.670> claim<00:11:04.940> that<00:11:05.620> every<00:11:06.620> cat<00:11:06.890> s<00:11:07.220> cute<00:11:07.670> and 00:11:07.930 --> 00:11:07.940 align:start position:0% want to claim that every cat s cute and 00:11:07.940 --> 00:11:09.850 align:start position:0% want to claim that every cat s cute and you<00:11:08.480> want<00:11:08.660> to<00:11:08.750> make<00:11:08.870> this<00:11:09.050> point<00:11:09.290> to<00:11:09.500> be<00:11:09.620> true 00:11:09.850 --> 00:11:09.860 align:start position:0% you want to make this point to be true 00:11:09.860 --> 00:11:12.700 align:start position:0% you want to make this point to be true and<00:11:10.190> you<00:11:10.970> have<00:11:11.150> to<00:11:11.360> submit<00:11:11.720> this<00:11:11.990> claim<00:11:12.290> to<00:11:12.590> an 00:11:12.700 --> 00:11:12.710 align:start position:0% and you have to submit this claim to an 00:11:12.710 --> 00:11:15.310 align:start position:0% and you have to submit this claim to an adjudicator<00:11:13.370> contract<00:11:13.820> and<00:11:14.060> you<00:11:14.840> can<00:11:14.990> decide 00:11:15.310 --> 00:11:15.320 align:start position:0% adjudicator contract and you can decide 00:11:15.320 --> 00:11:18.280 align:start position:0% adjudicator contract and you can decide this<00:11:15.500> plain<00:11:15.920> true<00:11:16.340> if<00:11:16.670> there<00:11:17.000> is<00:11:17.090> no<00:11:17.360> picture 00:11:18.280 --> 00:11:18.290 align:start position:0% this plain true if there is no picture 00:11:18.290 --> 00:11:20.980 align:start position:0% this plain true if there is no picture of<00:11:18.470> I'm<00:11:18.830> going<00:11:19.040> you<00:11:19.100> can't<00:11:19.160> submit<00:11:19.730> it<00:11:19.910> to<00:11:19.990> to 00:11:20.980 --> 00:11:20.990 align:start position:0% of I'm going you can't submit it to to 00:11:20.990 --> 00:11:22.990 align:start position:0% of I'm going you can't submit it to to adjudication<00:11:21.740> contracts<00:11:22.280> as<00:11:22.490> a<00:11:22.520> challenge 00:11:22.990 --> 00:11:23.000 align:start position:0% adjudication contracts as a challenge 00:11:23.000 --> 00:11:26.890 align:start position:0% adjudication contracts as a challenge and<00:11:23.330> then<00:11:24.320> if<00:11:25.100> you<00:11:25.340> want<00:11:25.580> the<00:11:25.790> another<00:11:26.180> example 00:11:26.890 --> 00:11:26.900 align:start position:0% and then if you want the another example 00:11:26.900 --> 00:11:31.450 align:start position:0% and then if you want the another example as<00:11:27.170> a<00:11:27.800> quantifier<00:11:28.610> as<00:11:28.970> a<00:11:29.210> decision<00:11:29.930> on<00:11:30.170> fire<00:11:30.460> so 00:11:31.450 --> 00:11:31.460 align:start position:0% as a quantifier as a decision on fire so 00:11:31.460 --> 00:11:34.060 align:start position:0% as a quantifier as a decision on fire so if<00:11:32.030> you<00:11:32.270> want<00:11:32.510> to<00:11:32.660> claim<00:11:32.900> that<00:11:32.960> there<00:11:33.860> is<00:11:34.040> a 00:11:34.060 --> 00:11:34.070 align:start position:0% if you want to claim that there is a 00:11:34.070 --> 00:11:36.850 align:start position:0% if you want to claim that there is a fine<00:11:34.430> cup<00:11:34.790> of<00:11:35.030> -<00:11:35.450> then<00:11:35.930> you<00:11:36.110> just<00:11:36.290> simply<00:11:36.470> want 00:11:36.850 --> 00:11:36.860 align:start position:0% fine cup of - then you just simply want 00:11:36.860 --> 00:11:40.000 align:start position:0% fine cup of - then you just simply want to<00:11:36.890> submit<00:11:37.250> a<00:11:37.670> single<00:11:38.090> picture<00:11:38.620> as<00:11:39.620> an 00:11:40.000 --> 00:11:40.010 align:start position:0% to submit a single picture as an 00:11:40.010 --> 00:11:43.900 align:start position:0% to submit a single picture as an evidence<00:11:40.460> that<00:11:40.730> has<00:11:41.510> a<00:11:41.540> cat<00:11:42.410> with<00:11:43.250> wings<00:11:43.550> and 00:11:43.900 --> 00:11:43.910 align:start position:0% evidence that has a cat with wings and 00:11:43.910 --> 00:11:46.860 align:start position:0% evidence that has a cat with wings and fly 00:11:46.860 --> 00:11:46.870 align:start position:0% 00:11:46.870 --> 00:11:52.080 align:start position:0% so<00:11:48.070> using<00:11:49.070> these<00:11:49.520> basic<00:11:50.710> property<00:11:51.710> on 00:11:52.080 --> 00:11:52.090 align:start position:0% so using these basic property on 00:11:52.090 --> 00:11:55.300 align:start position:0% so using these basic property on standardized<00:11:53.090> notation<00:11:53.620> you<00:11:54.620> can<00:11:54.650> even<00:11:55.040> make 00:11:55.300 --> 00:11:55.310 align:start position:0% standardized notation you can even make 00:11:55.310 --> 00:11:58.930 align:start position:0% standardized notation you can even make plasma<00:11:56.120> which<00:11:56.390> is<00:11:56.420> very<00:11:57.080> complicated 00:11:58.930 --> 00:11:58.940 align:start position:0% plasma which is very complicated 00:11:58.940 --> 00:12:02.560 align:start position:0% plasma which is very complicated their<00:11:59.110> solutions<00:12:00.110> and<00:12:00.460> before<00:12:01.460> before<00:12:02.360> deep 00:12:02.560 --> 00:12:02.570 align:start position:0% their solutions and before before deep 00:12:02.570 --> 00:12:06.160 align:start position:0% their solutions and before before deep diving<00:12:02.870> into<00:12:03.730> all<00:12:04.730> the<00:12:05.090> properties<00:12:05.930> that<00:12:05.960> are 00:12:06.160 --> 00:12:06.170 align:start position:0% diving into all the properties that are 00:12:06.170 --> 00:12:08.830 align:start position:0% diving into all the properties that are needing<00:12:06.620> for<00:12:06.800> plasma<00:12:07.340> and<00:12:07.880> we<00:12:07.940> first<00:12:08.300> explain 00:12:08.830 --> 00:12:08.840 align:start position:0% needing for plasma and we first explain 00:12:08.840 --> 00:12:11.050 align:start position:0% needing for plasma and we first explain how<00:12:09.320> plasma<00:12:09.920> cash<00:12:10.130> works<00:12:10.490> in<00:12:10.610> general 00:12:11.050 --> 00:12:11.060 align:start position:0% how plasma cash works in general 00:12:11.060 --> 00:12:13.750 align:start position:0% how plasma cash works in general so<00:12:11.720> there<00:12:12.200> are<00:12:12.230> two<00:12:12.650> users<00:12:13.010> who<00:12:13.190> want<00:12:13.340> to<00:12:13.460> make 00:12:13.750 --> 00:12:13.760 align:start position:0% so there are two users who want to make 00:12:13.760 --> 00:12:16.030 align:start position:0% so there are two users who want to make payments<00:12:14.210> to<00:12:14.270> each<00:12:14.480> other<00:12:14.690> so<00:12:15.500> they<00:12:15.650> have<00:12:15.860> to 00:12:16.030 --> 00:12:16.040 align:start position:0% payments to each other so they have to 00:12:16.040 --> 00:12:19.180 align:start position:0% payments to each other so they have to lock<00:12:16.460> their<00:12:16.970> funds<00:12:17.240> on<00:12:17.510> -<00:12:17.690> Padma<00:12:17.990> chain<00:12:18.350> make 00:12:19.180 --> 00:12:19.190 align:start position:0% lock their funds on - Padma chain make 00:12:19.190 --> 00:12:22.000 align:start position:0% lock their funds on - Padma chain make transactions<00:12:20.000> and<00:12:20.390> after<00:12:21.140> Don<00:12:21.380> interacting 00:12:22.000 --> 00:12:22.010 align:start position:0% transactions and after Don interacting 00:12:22.010 --> 00:12:23.590 align:start position:0% transactions and after Don interacting with<00:12:22.130> each<00:12:22.250> other<00:12:22.610> and<00:12:22.760> the<00:12:22.970> plasma<00:12:23.180> chain 00:12:23.590 --> 00:12:23.600 align:start position:0% with each other and the plasma chain 00:12:23.600 --> 00:12:26.260 align:start position:0% with each other and the plasma chain they<00:12:24.290> have<00:12:24.530> to<00:12:24.710> make<00:12:24.920> a<00:12:25.160> plaintiff<00:12:25.640> exit<00:12:26.060> to 00:12:26.260 --> 00:12:26.270 align:start position:0% they have to make a plaintiff exit to 00:12:26.270 --> 00:12:28.960 align:start position:0% they have to make a plaintiff exit to the<00:12:26.420> main<00:12:26.450> chain<00:12:26.930> and<00:12:27.280> after<00:12:28.280> passing<00:12:28.550> a 00:12:28.960 --> 00:12:28.970 align:start position:0% the main chain and after passing a 00:12:28.970 --> 00:12:31.000 align:start position:0% the main chain and after passing a dispute<00:12:29.480> period<00:12:29.930> without<00:12:30.290> getting<00:12:30.800> any 00:12:31.000 --> 00:12:31.010 align:start position:0% dispute period without getting any 00:12:31.010 --> 00:12:33.520 align:start position:0% dispute period without getting any challenge<00:12:31.490> they<00:12:32.090> can<00:12:32.270> finally<00:12:32.630> we<00:12:32.810> will<00:12:33.200> draw 00:12:33.520 --> 00:12:33.530 align:start position:0% challenge they can finally we will draw 00:12:33.530 --> 00:12:36.670 align:start position:0% challenge they can finally we will draw their<00:12:33.800> funds<00:12:34.070> and<00:12:34.840> that's<00:12:35.840> how<00:12:36.020> a<00:12:36.050> plasma<00:12:36.320> cash 00:12:36.670 --> 00:12:36.680 align:start position:0% their funds and that's how a plasma cash 00:12:36.680 --> 00:12:40.600 align:start position:0% their funds and that's how a plasma cash cars<00:12:36.920> in<00:12:37.100> general<00:12:37.400> and<00:12:37.730> to<00:12:39.190> enable<00:12:40.190> this<00:12:40.310> whole 00:12:40.600 --> 00:12:40.610 align:start position:0% cars in general and to enable this whole 00:12:40.610 --> 00:12:43.420 align:start position:0% cars in general and to enable this whole process<00:12:41.420> you<00:12:42.170> mean<00:12:42.380> three<00:12:42.830> different<00:12:43.160> kinds 00:12:43.420 --> 00:12:43.430 align:start position:0% process you mean three different kinds 00:12:43.430 --> 00:12:46.300 align:start position:0% process you mean three different kinds of<00:12:43.460> properties<00:12:44.200> checkpoint<00:12:45.200> property<00:12:45.650> exit 00:12:46.300 --> 00:12:46.310 align:start position:0% of properties checkpoint property exit 00:12:46.310 --> 00:12:49.510 align:start position:0% of properties checkpoint property exit property<00:12:46.760> and<00:12:47.060> ownership<00:12:47.480> property<00:12:48.490> so<00:12:49.490> I 00:12:49.510 --> 00:12:49.520 align:start position:0% property and ownership property so I 00:12:49.520 --> 00:12:52.540 align:start position:0% property and ownership property so I will<00:12:49.850> oliver<00:12:50.270> each<00:12:50.780> property<00:12:51.550> checkpoint 00:12:52.540 --> 00:12:52.550 align:start position:0% will oliver each property checkpoint 00:12:52.550 --> 00:12:55.390 align:start position:0% will oliver each property checkpoint property<00:12:53.270> is<00:12:53.540> to<00:12:53.780> claim<00:12:54.080> the<00:12:54.350> validity<00:12:54.650> of<00:12:55.160> the 00:12:55.390 --> 00:12:55.400 align:start position:0% property is to claim the validity of the 00:12:55.400 --> 00:12:58.780 align:start position:0% property is to claim the validity of the coin<00:12:55.730> history<00:12:56.150> so<00:12:57.050> it<00:12:57.530> says<00:12:57.860> all<00:12:58.100> of<00:12:58.430> the<00:12:58.520> stage 00:12:58.780 --> 00:12:58.790 align:start position:0% coin history so it says all of the stage 00:12:58.790 --> 00:13:01.770 align:start position:0% coin history so it says all of the stage updates<00:12:59.450> within<00:13:00.290> a<00:13:00.410> certain<00:13:00.620> going<00:13:01.100> range 00:13:01.770 --> 00:13:01.780 align:start position:0% updates within a certain going range 00:13:01.780 --> 00:13:05.470 align:start position:0% updates within a certain going range before<00:13:02.780> it<00:13:03.250> and<00:13:04.250> in<00:13:04.490> that<00:13:04.520> every<00:13:04.850> single<00:13:05.060> block 00:13:05.470 --> 00:13:05.480 align:start position:0% before it and in that every single block 00:13:05.480 --> 00:13:07.990 align:start position:0% before it and in that every single block before<00:13:06.050> the<00:13:06.170> current<00:13:06.380> block<00:13:06.740> are<00:13:07.610> all 00:13:07.990 --> 00:13:08.000 align:start position:0% before the current block are all 00:13:08.000 --> 00:13:11.860 align:start position:0% before the current block are all deprecated<00:13:08.780> so<00:13:09.670> to<00:13:10.670> noted<00:13:11.060> this<00:13:11.330> statement 00:13:11.860 --> 00:13:11.870 align:start position:0% deprecated so to noted this statement 00:13:11.870 --> 00:13:14.980 align:start position:0% deprecated so to noted this statement you<00:13:12.380> use<00:13:12.850> universal<00:13:13.850> quantifier<00:13:14.360> two<00:13:14.720> times 00:13:14.980 --> 00:13:14.990 align:start position:0% you use universal quantifier two times 00:13:14.990 --> 00:13:19.230 align:start position:0% you use universal quantifier two times and<00:13:15.700> to<00:13:16.700> specify<00:13:16.970> the<00:13:17.210> certain<00:13:17.990> coinage<00:13:18.440> and 00:13:19.230 --> 00:13:19.240 align:start position:0% and to specify the certain coinage and 00:13:19.240 --> 00:13:23.050 align:start position:0% and to specify the certain coinage and exit<00:13:20.240> property<00:13:20.810> is<00:13:21.140> to<00:13:21.620> claim<00:13:21.920> the<00:13:22.460> coin<00:13:22.760> has 00:13:23.050 --> 00:13:23.060 align:start position:0% exit property is to claim the coin has 00:13:23.060 --> 00:13:24.190 align:start position:0% exit property is to claim the coin has never<00:13:23.300> being<00:13:23.630> used 00:13:24.190 --> 00:13:24.200 align:start position:0% never being used 00:13:24.200 --> 00:13:26.710 align:start position:0% never being used what<00:13:24.500> does<00:13:24.680> not<00:13:24.920> predicate<00:13:25.610> in<00:13:26.000> a<00:13:26.180> notation 00:13:26.710 --> 00:13:26.720 align:start position:0% what does not predicate in a notation 00:13:26.720 --> 00:13:31.360 align:start position:0% what does not predicate in a notation and<00:13:26.930> then<00:13:27.890> the<00:13:28.160> third<00:13:28.400> one<00:13:29.500> this<00:13:30.500> is<00:13:30.920> a<00:13:31.010> key 00:13:31.360 --> 00:13:31.370 align:start position:0% and then the third one this is a key 00:13:31.370 --> 00:13:35.290 align:start position:0% and then the third one this is a key point<00:13:31.610> of<00:13:31.970> this<00:13:32.390> presentation<00:13:33.400> it<00:13:34.400> plays<00:13:35.120> a 00:13:35.290 --> 00:13:35.300 align:start position:0% point of this presentation it plays a 00:13:35.300 --> 00:13:37.840 align:start position:0% point of this presentation it plays a huge<00:13:35.630> role<00:13:35.990> in<00:13:36.020> the<00:13:36.320> generalization<00:13:37.100> of<00:13:37.460> the 00:13:37.840 --> 00:13:37.850 align:start position:0% huge role in the generalization of the 00:13:37.850 --> 00:13:41.380 align:start position:0% huge role in the generalization of the altitude<00:13:38.350> application<00:13:39.350> design<00:13:39.730> so<00:13:40.730> here<00:13:41.120> it 00:13:41.380 --> 00:13:41.390 align:start position:0% altitude application design so here it 00:13:41.390 --> 00:13:44.170 align:start position:0% altitude application design so here it says<00:13:41.420> ownership<00:13:42.140> property<00:13:42.620> is<00:13:43.010> simply<00:13:43.610> to 00:13:44.170 --> 00:13:44.180 align:start position:0% says ownership property is simply to 00:13:44.180 --> 00:13:47.920 align:start position:0% says ownership property is simply to claim<00:13:44.480> that<00:13:44.780> is<00:13:45.790> to<00:13:46.790> validate<00:13:47.300> the<00:13:47.450> ownership 00:13:47.920 --> 00:13:47.930 align:start position:0% claim that is to validate the ownership 00:13:47.930 --> 00:13:50.260 align:start position:0% claim that is to validate the ownership of<00:13:48.110> the<00:13:48.260> coin<00:13:48.470> and<00:13:48.920> it<00:13:49.580> requires<00:13:50.060> the 00:13:50.260 --> 00:13:50.270 align:start position:0% of the coin and it requires the 00:13:50.270 --> 00:13:53.240 align:start position:0% of the coin and it requires the signature<00:13:50.690> of<00:13:51.320> the 00:13:53.240 --> 00:13:53.250 align:start position:0% signature of the 00:13:53.250 --> 00:13:56.550 align:start position:0% signature of the but<00:13:54.250> if<00:13:54.850> you<00:13:55.090> want<00:13:55.300> to<00:13:55.480> make<00:13:56.050> this<00:13:56.290> application 00:13:56.550 --> 00:13:56.560 align:start position:0% but if you want to make this application 00:13:56.560 --> 00:13:59.610 align:start position:0% but if you want to make this application design<00:13:57.340> as<00:13:57.670> requiring<00:13:58.390> the<00:13:58.750> multi<00:13:59.110> signature 00:13:59.610 --> 00:13:59.620 align:start position:0% design as requiring the multi signature 00:13:59.620 --> 00:14:01.940 align:start position:0% design as requiring the multi signature then<00:14:00.250> you<00:14:00.490> have<00:14:00.670> to<00:14:00.850> simply<00:14:01.330> add<00:14:01.570> another 00:14:01.940 --> 00:14:01.950 align:start position:0% then you have to simply add another 00:14:01.950 --> 00:14:07.190 align:start position:0% then you have to simply add another address<00:14:02.950> to<00:14:03.490> the<00:14:03.760> signed<00:14:04.060> out<00:14:04.390> conduction<00:14:05.350> so 00:14:07.190 --> 00:14:07.200 align:start position:0% address to the signed out conduction so 00:14:07.200 --> 00:14:10.380 align:start position:0% address to the signed out conduction so enabling<00:14:08.200> switch<00:14:08.560> and<00:14:08.890> enabling<00:14:09.880> to<00:14:10.090> switch 00:14:10.380 --> 00:14:10.390 align:start position:0% enabling switch and enabling to switch 00:14:10.390 --> 00:14:15.690 align:start position:0% enabling switch and enabling to switch this<00:14:10.660> third<00:14:10.960> property<00:14:11.950> here<00:14:13.890> makes<00:14:14.890> here 00:14:15.690 --> 00:14:15.700 align:start position:0% this third property here makes here 00:14:15.700 --> 00:14:18.150 align:start position:0% this third property here makes here makes<00:14:16.060> it<00:14:16.450> in<00:14:16.960> plays<00:14:17.170> a<00:14:17.200> huge<00:14:17.500> role<00:14:17.830> in<00:14:17.860> the 00:14:18.150 --> 00:14:18.160 align:start position:0% makes it in plays a huge role in the 00:14:18.160 --> 00:14:21.900 align:start position:0% makes it in plays a huge role in the obstruction<00:14:18.820> of<00:14:19.360> the<00:14:20.130> legacy<00:14:21.130> application 00:14:21.900 --> 00:14:21.910 align:start position:0% obstruction of the legacy application 00:14:21.910 --> 00:14:31.560 align:start position:0% obstruction of the legacy application design<00:14:24.870> so<00:14:25.870> to<00:14:28.140> analyze<00:14:29.140> notation<00:14:30.120> he<00:14:31.120> stopped 00:14:31.560 --> 00:14:31.570 align:start position:0% design so to analyze notation he stopped 00:14:31.570 --> 00:14:36.390 align:start position:0% design so to analyze notation he stopped and<00:14:32.790> think<00:14:33.790> covenant<00:14:34.330> over<00:14:35.020> the<00:14:35.400> favorite 00:14:36.390 --> 00:14:36.400 align:start position:0% and think covenant over the favorite 00:14:36.400 --> 00:14:39.570 align:start position:0% and think covenant over the favorite design<00:14:36.760> again<00:14:37.150> and<00:14:37.890> implemented<00:14:38.890> plasma<00:14:39.370> cash 00:14:39.570 --> 00:14:39.580 align:start position:0% design again and implemented plasma cash 00:14:39.580 --> 00:14:42.240 align:start position:0% design again and implemented plasma cash based<00:14:39.940> on<00:14:40.180> the<00:14:40.330> IBM<00:14:40.480> again<00:14:41.260> after<00:14:41.800> have<00:14:41.950> gone 00:14:42.240 --> 00:14:42.250 align:start position:0% based on the IBM again after have gone 00:14:42.250 --> 00:14:46.680 align:start position:0% based on the IBM again after have gone so<00:14:43.150> it's<00:14:43.390> now<00:14:43.710> it's<00:14:44.710> of<00:14:44.980> course<00:14:45.160> secure<00:14:45.690> proud 00:14:46.680 --> 00:14:46.690 align:start position:0% so it's now it's of course secure proud 00:14:46.690 --> 00:14:49.200 align:start position:0% so it's now it's of course secure proud that<00:14:46.960> the<00:14:47.080> authority<00:14:47.680> but<00:14:48.460> now<00:14:48.670> even<00:14:48.970> more 00:14:49.200 --> 00:14:49.210 align:start position:0% that the authority but now even more 00:14:49.210 --> 00:14:52.620 align:start position:0% that the authority but now even more simple<00:14:49.660> and<00:14:49.810> in<00:14:49.960> flex<00:14:50.200> flexible<00:14:51.100> but<00:14:52.090> the<00:14:52.240> OPM 00:14:52.620 --> 00:14:52.630 align:start position:0% simple and in flex flexible but the OPM 00:14:52.630 --> 00:14:56.280 align:start position:0% simple and in flex flexible but the OPM so<00:14:53.380> the<00:14:53.890> application<00:14:54.880> developers<00:14:55.510> will<00:14:55.750> be 00:14:56.280 --> 00:14:56.290 align:start position:0% so the application developers will be 00:14:56.290 --> 00:14:58.290 align:start position:0% so the application developers will be able<00:14:56.500> to<00:14:56.680> focus<00:14:57.010> on<00:14:57.160> designing<00:14:57.520> application 00:14:58.290 --> 00:14:58.300 align:start position:0% able to focus on designing application 00:14:58.300 --> 00:15:02.280 align:start position:0% able to focus on designing application logic<00:14:58.450> and<00:14:59.130> front-end<00:15:00.130> development<00:15:01.020> so<00:15:02.020> they 00:15:02.280 --> 00:15:02.290 align:start position:0% logic and front-end development so they 00:15:02.290 --> 00:15:06.960 align:start position:0% logic and front-end development so they can<00:15:04.950> repent<00:15:05.950> an<00:15:06.160> implementation 00:15:06.960 --> 00:15:06.970 align:start position:0% can repent an implementation 00:15:06.970 --> 00:15:09.300 align:start position:0% can repent an implementation implementation<00:15:07.360> for<00:15:08.260> those<00:15:08.860> are<00:15:09.130> two 00:15:09.300 --> 00:15:09.310 align:start position:0% implementation for those are two 00:15:09.310 --> 00:15:11.670 align:start position:0% implementation for those are two oriented<00:15:09.730> features<00:15:10.020> and<00:15:11.020> also<00:15:11.440> the 00:15:11.670 --> 00:15:11.680 align:start position:0% oriented features and also the 00:15:11.680 --> 00:15:14.310 align:start position:0% oriented features and also the combinations<00:15:12.370> of<00:15:12.640> different<00:15:13.320> constructions 00:15:14.310 --> 00:15:14.320 align:start position:0% combinations of different constructions 00:15:14.320 --> 00:15:16.710 align:start position:0% combinations of different constructions on<00:15:14.500> the<00:15:14.650> layer<00:15:14.920> two<00:15:15.220> you<00:15:15.340> are<00:15:15.550> possible<00:15:16.060> so<00:15:16.660> you 00:15:16.710 --> 00:15:16.720 align:start position:0% on the layer two you are possible so you 00:15:16.720 --> 00:15:18.900 align:start position:0% on the layer two you are possible so you can<00:15:17.080> for<00:15:17.200> example<00:15:17.260> make<00:15:17.650> channels<00:15:18.550> or<00:15:18.640> asthma 00:15:18.900 --> 00:15:18.910 align:start position:0% can for example make channels or asthma 00:15:18.910 --> 00:15:24.040 align:start position:0% can for example make channels or asthma attacks<00:15:19.870> of<00:15:20.050> Cosmo 00:15:24.040 --> 00:15:24.050 align:start position:0% 00:15:24.050 --> 00:15:27.040 align:start position:0% and<00:15:24.490> here<00:15:25.490> this<00:15:25.910> is<00:15:25.970> gonna<00:15:26.570> be<00:15:26.750> the<00:15:26.870> highlight 00:15:27.040 --> 00:15:27.050 align:start position:0% and here this is gonna be the highlight 00:15:27.050 --> 00:15:31.720 align:start position:0% and here this is gonna be the highlight of<00:15:27.260> this<00:15:27.560> presentation<00:15:28.220> and<00:15:28.670> we<00:15:29.390> took<00:15:29.990> a<00:15:30.730> video 00:15:31.720 --> 00:15:31.730 align:start position:0% of this presentation and we took a video 00:15:31.730 --> 00:15:35.500 align:start position:0% of this presentation and we took a video of<00:15:32.060> our<00:15:32.390> demo<00:15:32.800> kind<00:15:33.800> of<00:15:33.860> to<00:15:34.490> showcase<00:15:34.970> what 00:15:35.500 --> 00:15:35.510 align:start position:0% of our demo kind of to showcase what 00:15:35.510 --> 00:15:37.690 align:start position:0% of our demo kind of to showcase what kind<00:15:35.779> of<00:15:35.870> application<00:15:36.589> think<00:15:37.100> it<00:15:37.190> actually 00:15:37.690 --> 00:15:37.700 align:start position:0% kind of application think it actually 00:15:37.700 --> 00:15:44.550 align:start position:0% kind of application think it actually felt<00:15:37.970> with<00:15:38.300> cosmic<00:15:38.779> chamber<00:15:40.779> here<00:15:43.330> so 00:15:44.550 --> 00:15:44.560 align:start position:0% felt with cosmic chamber here so 00:15:44.560 --> 00:15:48.360 align:start position:0% felt with cosmic chamber here so disconnects<00:15:45.560> flavors<00:15:46.250> what's<00:15:46.700> going<00:15:47.060> on<00:15:47.180> here 00:15:48.360 --> 00:15:48.370 align:start position:0% disconnects flavors what's going on here 00:15:48.370 --> 00:15:52.290 align:start position:0% disconnects flavors what's going on here he's<00:15:49.370> trying<00:15:49.820> to<00:15:50.029> make<00:15:50.270> a<00:15:50.300> payment<00:15:50.690> from 00:15:52.290 --> 00:15:52.300 align:start position:0% he's trying to make a payment from 00:15:52.300 --> 00:15:55.120 align:start position:0% he's trying to make a payment from rights<00:15:53.300> on<00:15:53.990> the<00:15:54.110> wallet<00:15:54.320> on<00:15:54.529> the<00:15:54.620> right<00:15:54.860> side 00:15:55.120 --> 00:15:55.130 align:start position:0% rights on the wallet on the right side 00:15:55.130 --> 00:15:57.760 align:start position:0% rights on the wallet on the right side to<00:15:55.310> the<00:15:55.640> wallet<00:15:56.330> another<00:15:56.810> on<00:15:57.110> the<00:15:57.290> left<00:15:57.500> side 00:15:57.760 --> 00:15:57.770 align:start position:0% to the wallet another on the left side 00:15:57.770 --> 00:16:05.410 align:start position:0% to the wallet another on the left side and<00:15:58.070> he<00:15:58.670> sending<00:16:01.839> instead<00:16:02.839> day<00:16:03.050> I<00:16:04.120> think<00:16:05.120> it 00:16:05.410 --> 00:16:05.420 align:start position:0% and he sending instead day I think it 00:16:05.420 --> 00:16:10.210 align:start position:0% and he sending instead day I think it was<00:16:05.450> five<00:16:05.810> died<00:16:06.080> yeah<00:16:06.470> fine<00:16:06.920> die<00:16:08.260> to<00:16:09.260> wallet<00:16:10.040> on 00:16:10.210 --> 00:16:10.220 align:start position:0% was five died yeah fine die to wallet on 00:16:10.220 --> 00:16:14.230 align:start position:0% was five died yeah fine die to wallet on the<00:16:10.250> left<00:16:10.550> side<00:16:10.820> so<00:16:11.089> now<00:16:11.390> he<00:16:11.450> is<00:16:11.839> face<00:16:12.080> thing<00:16:13.240> I 00:16:14.230 --> 00:16:14.240 align:start position:0% the left side so now he is face thing I 00:16:14.240 --> 00:16:16.389 align:start position:0% the left side so now he is face thing I dress<00:16:14.690> up<00:16:14.930> the<00:16:15.200> wallet<00:16:15.649> on<00:16:15.800> the<00:16:15.830> left<00:16:16.130> side 00:16:16.389 --> 00:16:16.399 align:start position:0% dress up the wallet on the left side 00:16:16.399 --> 00:16:23.139 align:start position:0% dress up the wallet on the left side here<00:16:16.790> and<00:16:17.570> the<00:16:18.350> bottle<00:16:18.680> sets<00:16:18.890> and<00:16:21.700> so<00:16:22.700> the 00:16:23.139 --> 00:16:23.149 align:start position:0% here and the bottle sets and so the 00:16:23.149 --> 00:16:26.889 align:start position:0% here and the bottle sets and so the transaction<00:16:23.660> is<00:16:24.200> completed<00:16:24.680> here<00:16:25.600> now<00:16:26.600> he's 00:16:26.889 --> 00:16:26.899 align:start position:0% transaction is completed here now he's 00:16:26.899 --> 00:16:30.850 align:start position:0% transaction is completed here now he's checking<00:16:27.310> the<00:16:28.310> payment<00:16:28.820> under<00:16:29.750> the<00:16:30.020> wallet<00:16:30.589> on 00:16:30.850 --> 00:16:30.860 align:start position:0% checking the payment under the wallet on 00:16:30.860 --> 00:16:35.110 align:start position:0% checking the payment under the wallet on the<00:16:31.040> left<00:16:31.250> side<00:16:31.490> as<00:16:32.060> well<00:16:33.220> here<00:16:34.220> now<00:16:34.490> the 00:16:35.110 --> 00:16:35.120 align:start position:0% the left side as well here now the 00:16:35.120 --> 00:16:37.050 align:start position:0% the left side as well here now the volume<00:16:35.390> on<00:16:35.510> the<00:16:35.540> left<00:16:35.779> side<00:16:35.990> has<00:16:36.230> five<00:16:36.529> times 00:16:37.050 --> 00:16:37.060 align:start position:0% volume on the left side has five times 00:16:37.060 --> 00:16:39.880 align:start position:0% volume on the left side has five times this<00:16:38.060> is<00:16:38.270> the<00:16:38.450> payment<00:16:38.779> after<00:16:39.140> we've<00:16:39.470> created 00:16:39.880 --> 00:16:39.890 align:start position:0% this is the payment after we've created 00:16:39.890 --> 00:16:46.660 align:start position:0% this is the payment after we've created with<00:16:40.670> and<00:16:41.920> the<00:16:42.920> next<00:16:43.339> showcase<00:16:44.270> app<00:16:44.750> is<00:16:45.670> next 00:16:46.660 --> 00:16:46.670 align:start position:0% with and the next showcase app is next 00:16:46.670 --> 00:16:48.940 align:start position:0% with and the next showcase app is next up<00:16:46.850> and<00:16:47.300> some<00:16:47.600> exit 00:16:48.940 --> 00:16:48.950 align:start position:0% up and some exit 00:16:48.950 --> 00:16:57.340 align:start position:0% up and some exit changing<00:16:50.139> 1/8<00:16:51.139> to<00:16:51.649> $10<00:16:53.649> so<00:16:54.649> he's<00:16:55.600> choosing<00:16:56.600> 1/8 00:16:57.340 --> 00:16:57.350 align:start position:0% changing 1/8 to $10 so he's choosing 1/8 00:16:57.350 --> 00:17:03.550 align:start position:0% changing 1/8 to $10 so he's choosing 1/8 and<00:16:57.730> 10<00:16:59.170> died<00:17:00.490> to<00:17:01.490> exchange<00:17:02.290> making<00:17:03.290> those 00:17:03.550 --> 00:17:03.560 align:start position:0% and 10 died to exchange making those 00:17:03.560 --> 00:17:07.750 align:start position:0% and 10 died to exchange making those wallets<00:17:04.990> he<00:17:05.990> says<00:17:06.199> new<00:17:06.439> offer<00:17:06.709> on<00:17:07.010> the<00:17:07.250> button 00:17:07.750 --> 00:17:07.760 align:start position:0% wallets he says new offer on the button 00:17:07.760 --> 00:17:11.110 align:start position:0% wallets he says new offer on the button so<00:17:08.000> the<00:17:08.929> offer<00:17:09.589> on<00:17:09.799> that<00:17:10.010> exchange<00:17:10.339> is<00:17:10.880> a 00:17:11.110 --> 00:17:11.120 align:start position:0% so the offer on that exchange is a 00:17:11.120 --> 00:17:12.390 align:start position:0% so the offer on that exchange is a minute 00:17:12.390 --> 00:17:12.400 align:start position:0% minute 00:17:12.400 --> 00:17:16.960 align:start position:0% minute then<00:17:13.569> he<00:17:14.620> wallet<00:17:15.620> on<00:17:15.770> the<00:17:15.919> right<00:17:16.100> side<00:17:16.459> has<00:17:16.730> to 00:17:16.960 --> 00:17:16.970 align:start position:0% then he wallet on the right side has to 00:17:16.970 --> 00:17:19.120 align:start position:0% then he wallet on the right side has to confirm<00:17:17.449> the<00:17:17.990> meet<00:17:18.319> author<00:17:18.500> of<00:17:18.799> that<00:17:18.980> exchange 00:17:19.120 --> 00:17:19.130 align:start position:0% confirm the meet author of that exchange 00:17:19.130 --> 00:17:23.650 align:start position:0% confirm the meet author of that exchange so<00:17:20.770> he<00:17:21.770> clicks<00:17:22.040> and<00:17:22.400> confirms<00:17:22.970> that<00:17:23.270> exchange 00:17:23.650 --> 00:17:23.660 align:start position:0% so he clicks and confirms that exchange 00:17:23.660 --> 00:17:25.650 align:start position:0% so he clicks and confirms that exchange offer 00:17:25.650 --> 00:17:25.660 align:start position:0% offer 00:17:25.660 --> 00:17:31.570 align:start position:0% offer now<00:17:26.660> it's<00:17:26.959> completed<00:17:27.470> so<00:17:29.860> if<00:17:30.860> you<00:17:31.040> check<00:17:31.340> the 00:17:31.570 --> 00:17:31.580 align:start position:0% now it's completed so if you check the 00:17:31.580 --> 00:17:35.770 align:start position:0% now it's completed so if you check the history<00:17:31.940> of<00:17:32.150> the<00:17:32.390> exchange<00:17:32.840> it<00:17:33.650> says<00:17:34.100> oh<00:17:34.780> if 00:17:35.770 --> 00:17:35.780 align:start position:0% history of the exchange it says oh if 00:17:35.780 --> 00:17:37.990 align:start position:0% history of the exchange it says oh if you<00:17:35.960> check<00:17:36.169> the<00:17:36.530> balance<00:17:36.770> of<00:17:37.130> each<00:17:37.400> wallet 00:17:37.990 --> 00:17:38.000 align:start position:0% you check the balance of each wallet 00:17:38.000 --> 00:17:40.440 align:start position:0% you check the balance of each wallet now<00:17:38.419> the<00:17:38.630> lot<00:17:39.140> of<00:17:39.260> them<00:17:39.410> the<00:17:39.559> right<00:17:39.740> side<00:17:40.070> has 00:17:40.440 --> 00:17:40.450 align:start position:0% now the lot of them the right side has 00:17:40.450 --> 00:17:42.060 align:start position:0% now the lot of them the right side has [Music] 00:17:42.060 --> 00:17:42.070 align:start position:0% [Music] 00:17:42.070 --> 00:17:46.810 align:start position:0% [Music] one<00:17:43.870> money<00:17:44.870> and<00:17:45.290> then<00:17:45.830> enough<00:17:46.160> both<00:17:46.400> of<00:17:46.429> the 00:17:46.810 --> 00:17:46.820 align:start position:0% one money and then enough both of the 00:17:46.820 --> 00:17:52.360 align:start position:0% one money and then enough both of the left<00:17:47.030> side<00:17:47.240> has<00:17:47.480> Tendai<00:17:48.940> so<00:17:50.110> these<00:17:51.110> were<00:17:51.530> one 00:17:52.360 --> 00:17:52.370 align:start position:0% left side has Tendai so these were one 00:17:52.370 --> 00:17:55.419 align:start position:0% left side has Tendai so these were one application<00:17:53.150> and<00:17:53.950> showcase<00:17:54.950> our<00:17:55.160> study 00:17:55.419 --> 00:17:55.429 align:start position:0% application and showcase our study 00:17:55.429 --> 00:18:05.980 align:start position:0% application and showcase our study created<00:17:56.120> with<00:17:57.049> our<00:17:57.140> framework<00:18:04.540> this<00:18:05.540> is<00:18:05.929> a 00:18:05.980 --> 00:18:05.990 align:start position:0% created with our framework this is a 00:18:05.990 --> 00:18:07.990 align:start position:0% created with our framework this is a favorite<00:18:06.710> the<00:18:06.860> moment<00:18:07.250> that<00:18:07.460> we<00:18:07.610> have<00:18:07.640> been 00:18:07.990 --> 00:18:08.000 align:start position:0% favorite the moment that we have been 00:18:08.000 --> 00:18:11.080 align:start position:0% favorite the moment that we have been doing<00:18:08.210> to<00:18:08.690> create<00:18:08.840> these<00:18:09.110> apps<00:18:09.470> so<00:18:10.370> it 00:18:11.080 --> 00:18:11.090 align:start position:0% doing to create these apps so it 00:18:11.090 --> 00:18:13.690 align:start position:0% doing to create these apps so it basically<00:18:11.299> has<00:18:11.809> two<00:18:12.049> components<00:18:12.770> obn 00:18:13.690 --> 00:18:13.700 align:start position:0% basically has two components obn 00:18:13.700 --> 00:18:15.850 align:start position:0% basically has two components obn contracts<00:18:14.240> on<00:18:14.450> the<00:18:14.480> second<00:18:15.080> layer<00:18:15.260> one<00:18:15.620> and 00:18:15.850 --> 00:18:15.860 align:start position:0% contracts on the second layer one and 00:18:15.860 --> 00:18:18.940 align:start position:0% contracts on the second layer one and client<00:18:16.780> implementation<00:18:17.780> the<00:18:18.500> option 00:18:18.940 --> 00:18:18.950 align:start position:0% client implementation the option 00:18:18.950 --> 00:18:21.640 align:start position:0% client implementation the option contract<00:18:19.220> has<00:18:19.910> inverse<00:18:20.540> education<00:18:21.290> mantra 00:18:21.640 --> 00:18:21.650 align:start position:0% contract has inverse education mantra 00:18:21.650 --> 00:18:23.710 align:start position:0% contract has inverse education mantra that<00:18:22.100> I<00:18:22.160> just<00:18:22.400> explained<00:18:22.940> the<00:18:23.120> strongest<00:18:23.510> of 00:18:23.710 --> 00:18:23.720 align:start position:0% that I just explained the strongest of 00:18:23.720 --> 00:18:25.130 align:start position:0% that I just explained the strongest of and<00:18:24.020> then<00:18:24.559> the 00:18:25.130 --> 00:18:25.140 align:start position:0% and then the 00:18:25.140 --> 00:18:28.640 align:start position:0% and then the little<00:18:26.070> building<00:18:26.760> box<00:18:27.240> to<00:18:27.960> pay<00:18:28.200> for<00:18:28.500> the 00:18:28.640 --> 00:18:28.650 align:start position:0% little building box to pay for the 00:18:28.650 --> 00:18:31.520 align:start position:0% little building box to pay for the standardized<00:18:29.160> notation<00:18:29.370> and<00:18:30.530> client-side 00:18:31.520 --> 00:18:31.530 align:start position:0% standardized notation and client-side 00:18:31.530 --> 00:18:36.080 align:start position:0% standardized notation and client-side has<00:18:32.990> basically<00:18:33.990> two<00:18:34.320> three<00:18:34.770> big<00:18:35.309> components 00:18:36.080 --> 00:18:36.090 align:start position:0% has basically two three big components 00:18:36.090 --> 00:18:38.930 align:start position:0% has basically two three big components of<00:18:36.120> the<00:18:36.750> important<00:18:37.230> decider<00:18:37.590> and<00:18:38.070> plasma 00:18:38.930 --> 00:18:38.940 align:start position:0% of the important decider and plasma 00:18:38.940 --> 00:18:44.720 align:start position:0% of the important decider and plasma hanging<00:18:39.240> anime<00:18:39.600> and<00:18:40.130> science<00:18:43.190> now<00:18:44.190> I'm<00:18:44.370> going 00:18:44.720 --> 00:18:44.730 align:start position:0% hanging anime and science now I'm going 00:18:44.730 --> 00:18:46.039 align:start position:0% hanging anime and science now I'm going to<00:18:44.850> talk<00:18:45.059> about<00:18:45.270> some<00:18:45.600> of<00:18:45.720> the<00:18:45.870> challenges 00:18:46.039 --> 00:18:46.049 align:start position:0% to talk about some of the challenges 00:18:46.049 --> 00:18:48.410 align:start position:0% to talk about some of the challenges that<00:18:46.710> we<00:18:47.280> have<00:18:47.429> been<00:18:47.580> facing<00:18:47.790> during<00:18:48.240> our 00:18:48.410 --> 00:18:48.420 align:start position:0% that we have been facing during our 00:18:48.420 --> 00:18:51.740 align:start position:0% that we have been facing during our favorite<00:18:49.020> moment<00:18:49.760> so<00:18:50.760> it<00:18:51.270> was<00:18:51.420> kind<00:18:51.660> of 00:18:51.740 --> 00:18:51.750 align:start position:0% favorite moment so it was kind of 00:18:51.750 --> 00:18:54.710 align:start position:0% favorite moment so it was kind of difficult<00:18:52.049> to<00:18:52.410> balance<00:18:52.799> between<00:18:53.280> the<00:18:54.179> runtime 00:18:54.710 --> 00:18:54.720 align:start position:0% difficult to balance between the runtime 00:18:54.720 --> 00:18:58.130 align:start position:0% difficult to balance between the runtime design<00:18:55.080> and<00:18:55.410> its<00:18:56.400> implementation<00:18:57.270> at<00:18:58.110> the 00:18:58.130 --> 00:18:58.140 align:start position:0% design and its implementation at the 00:18:58.140 --> 00:19:00.770 align:start position:0% design and its implementation at the same<00:18:58.410> time<00:18:58.679> because<00:18:58.890> all<00:18:59.669> the<00:19:00.179> applications 00:19:00.770 --> 00:19:00.780 align:start position:0% same time because all the applications 00:19:00.780 --> 00:19:03.860 align:start position:0% same time because all the applications out<00:19:01.110> on<00:19:01.380> top<00:19:01.590> of<00:19:01.770> their<00:19:01.980> runtimes<00:19:02.490> is<00:19:03.270> usually 00:19:03.860 --> 00:19:03.870 align:start position:0% out on top of their runtimes is usually 00:19:03.870 --> 00:19:06.140 align:start position:0% out on top of their runtimes is usually depending<00:19:04.320> upon<00:19:04.410> the<00:19:04.710> runtime<00:19:05.070> design<00:19:05.460> so<00:19:05.910> we 00:19:06.140 --> 00:19:06.150 align:start position:0% depending upon the runtime design so we 00:19:06.150 --> 00:19:09.669 align:start position:0% depending upon the runtime design so we have<00:19:06.330> to<00:19:06.510> think<00:19:07.290> about<00:19:07.760> runtime<00:19:08.760> design 00:19:09.669 --> 00:19:09.679 align:start position:0% have to think about runtime design 00:19:09.679 --> 00:19:12.380 align:start position:0% have to think about runtime design abstraction<00:19:10.679> of<00:19:10.890> the<00:19:11.100> application<00:19:11.820> or<00:19:12.179> kind 00:19:12.380 --> 00:19:12.390 align:start position:0% abstraction of the application or kind 00:19:12.390 --> 00:19:14.360 align:start position:0% abstraction of the application or kind of<00:19:12.510> obligation<00:19:13.080> that<00:19:13.290> you<00:19:13.440> can<00:19:13.620> build<00:19:13.830> it<00:19:14.160> can 00:19:14.360 --> 00:19:14.370 align:start position:0% of obligation that you can build it can 00:19:14.370 --> 00:19:17.659 align:start position:0% of obligation that you can build it can be<00:19:14.490> felt<00:19:14.790> at<00:19:15.210> the<00:19:15.390> same<00:19:15.419> time<00:19:15.980> so<00:19:16.980> and<00:19:17.400> the 00:19:17.659 --> 00:19:17.669 align:start position:0% be felt at the same time so and the 00:19:17.669 --> 00:19:20.299 align:start position:0% be felt at the same time so and the interesting<00:19:18.270> part<00:19:18.540> about<00:19:18.809> runtime<00:19:19.770> design 00:19:20.299 --> 00:19:20.309 align:start position:0% interesting part about runtime design 00:19:20.309 --> 00:19:24.200 align:start position:0% interesting part about runtime design was<00:19:21.090> designing<00:19:21.780> criminal<00:19:22.410> bulging<00:19:23.309> box<00:19:23.669> for 00:19:24.200 --> 00:19:24.210 align:start position:0% was designing criminal bulging box for 00:19:24.210 --> 00:19:27.200 align:start position:0% was designing criminal bulging box for the<00:19:24.299> properties<00:19:24.840> for<00:19:25.650> example<00:19:25.679> it<00:19:26.669> showed<00:19:27.059> up 00:19:27.200 --> 00:19:27.210 align:start position:0% the properties for example it showed up 00:19:27.210 --> 00:19:29.690 align:start position:0% the properties for example it showed up on<00:19:27.390> the<00:19:27.780> example<00:19:28.320> as<00:19:29.130> more<00:19:29.429> than<00:19:29.549> I<00:19:29.669> just 00:19:29.690 --> 00:19:29.700 align:start position:0% on the example as more than I just 00:19:29.700 --> 00:19:33.140 align:start position:0% on the example as more than I just explained<00:19:30.330> that<00:19:31.260> I<00:19:31.470> explained<00:19:31.860> before<00:19:32.220> but 00:19:33.140 --> 00:19:33.150 align:start position:0% explained that I explained before but 00:19:33.150 --> 00:19:37.820 align:start position:0% explained that I explained before but the<00:19:33.510> fine<00:19:33.750> by<00:19:34.080> Sundberg<00:19:34.710> etiquette<00:19:36.830> primitive 00:19:37.820 --> 00:19:37.830 align:start position:0% the fine by Sundberg etiquette primitive 00:19:37.830 --> 00:19:42.020 align:start position:0% the fine by Sundberg etiquette primitive profit<00:19:38.480> predicates<00:19:39.480> as<00:19:39.890> its<00:19:40.910> it's<00:19:41.910> a 00:19:42.020 --> 00:19:42.030 align:start position:0% profit predicates as its it's a 00:19:42.030 --> 00:19:44.650 align:start position:0% profit predicates as its it's a predicate<00:19:42.390> to<00:19:42.450> check<00:19:43.260> that<00:19:43.770> the<00:19:43.950> data<00:19:44.190> is 00:19:44.650 --> 00:19:44.660 align:start position:0% predicate to check that the data is 00:19:44.660 --> 00:19:47.289 align:start position:0% predicate to check that the data is signed<00:19:45.660> by<00:19:45.870> this<00:19:45.929> certain<00:19:46.500> address<00:19:46.890> and 00:19:47.289 --> 00:19:47.299 align:start position:0% signed by this certain address and 00:19:47.299 --> 00:19:49.640 align:start position:0% signed by this certain address and another<00:19:48.299> example<00:19:48.960> of<00:19:49.080> the<00:19:49.260> preeminent 00:19:49.640 --> 00:19:49.650 align:start position:0% another example of the preeminent 00:19:49.650 --> 00:19:53.470 align:start position:0% another example of the preeminent premature<00:19:50.419> predicate<00:19:51.419> s<00:19:51.660> and<00:19:52.080> predicate<00:19:52.710> and 00:19:53.470 --> 00:19:53.480 align:start position:0% premature predicate s and predicate and 00:19:53.480 --> 00:19:56.060 align:start position:0% premature predicate s and predicate and it's<00:19:54.480> a<00:19:54.600> predicate<00:19:54.960> to<00:19:55.020> combine<00:19:55.620> two 00:19:56.060 --> 00:19:56.070 align:start position:0% it's a predicate to combine two 00:19:56.070 --> 00:20:00.470 align:start position:0% it's a predicate to combine two different<00:19:56.340> predicates<00:19:57.179> and<00:19:59.030> the<00:20:00.030> next 00:20:00.470 --> 00:20:00.480 align:start position:0% different predicates and the next 00:20:00.480 --> 00:20:02.040 align:start position:0% different predicates and the next challenge 00:20:02.040 --> 00:20:02.050 align:start position:0% challenge 00:20:02.050 --> 00:20:06.000 align:start position:0% challenge is<00:20:02.110> a<00:20:02.620> property<00:20:03.480> serialization<00:20:04.480> so<00:20:05.290> property 00:20:06.000 --> 00:20:06.010 align:start position:0% is a property serialization so property 00:20:06.010 --> 00:20:08.610 align:start position:0% is a property serialization so property has<00:20:06.460> to<00:20:06.700> be<00:20:06.880> interpreted<00:20:07.510> about<00:20:08.110> these<00:20:08.290> smart 00:20:08.610 --> 00:20:08.620 align:start position:0% has to be interpreted about these smart 00:20:08.620 --> 00:20:13.170 align:start position:0% has to be interpreted about these smart contracts<00:20:09.310> and<00:20:09.520> clients<00:20:10.480> so<00:20:11.130> one<00:20:12.130> woman<00:20:12.490> okay 00:20:13.170 --> 00:20:13.180 align:start position:0% contracts and clients so one woman okay 00:20:13.180 --> 00:20:16.830 align:start position:0% contracts and clients so one woman okay so<00:20:13.470> it<00:20:14.470> has<00:20:14.530> to<00:20:15.130> be<00:20:15.850> method<00:20:16.150> design<00:20:16.450> like<00:20:16.720> a 00:20:16.830 --> 00:20:16.840 align:start position:0% so it has to be method design like a 00:20:16.840 --> 00:20:21.300 align:start position:0% so it has to be method design like a better<00:20:17.730> better<00:20:18.730> efficient<00:20:19.300> way<00:20:19.540> to<00:20:20.200> earn<00:20:20.860> the 00:20:21.300 --> 00:20:21.310 align:start position:0% better better efficient way to earn the 00:20:21.310 --> 00:20:25.020 align:start position:0% better better efficient way to earn the smart<00:20:21.580> contract<00:20:21.790> giving<00:20:22.750> to<00:20:23.410> to<00:20:24.400> interpret 00:20:25.020 --> 00:20:25.030 align:start position:0% smart contract giving to to interpret 00:20:25.030 --> 00:20:27.960 align:start position:0% smart contract giving to to interpret all<00:20:25.300> the<00:20:25.480> properties<00:20:26.200> and<00:20:26.530> because<00:20:27.310> all<00:20:27.730> the 00:20:27.960 --> 00:20:27.970 align:start position:0% all the properties and because all the 00:20:27.970 --> 00:20:30.150 align:start position:0% all the properties and because all the properties<00:20:28.510> some<00:20:29.290> of<00:20:29.410> the<00:20:29.530> relatives<00:20:29.800> can 00:20:30.150 --> 00:20:30.160 align:start position:0% properties some of the relatives can 00:20:30.160 --> 00:20:32.100 align:start position:0% properties some of the relatives can have<00:20:30.400> dynamic<00:20:30.640> variable<00:20:31.420> they<00:20:31.570> decide<00:20:31.840> if<00:20:32.020> you 00:20:32.100 --> 00:20:32.110 align:start position:0% have dynamic variable they decide if you 00:20:32.110 --> 00:20:34.260 align:start position:0% have dynamic variable they decide if you have<00:20:32.260> to<00:20:32.380> think<00:20:32.530> about<00:20:32.680> data<00:20:33.610> structure<00:20:34.210> of 00:20:34.260 --> 00:20:34.270 align:start position:0% have to think about data structure of 00:20:34.270 --> 00:20:36.570 align:start position:0% have to think about data structure of the<00:20:34.450> provinces<00:20:34.900> better<00:20:35.200> and<00:20:35.530> the<00:20:36.400> most 00:20:36.570 --> 00:20:36.580 align:start position:0% the provinces better and the most 00:20:36.580 --> 00:20:38.790 align:start position:0% the provinces better and the most difficult<00:20:37.090> thing<00:20:37.450> was<00:20:37.800> multi-platform 00:20:38.790 --> 00:20:38.800 align:start position:0% difficult thing was multi-platform 00:20:38.800 --> 00:20:41.690 align:start position:0% difficult thing was multi-platform implementation<00:20:39.790> for<00:20:40.570> Android<00:20:41.410> and 00:20:41.690 --> 00:20:41.700 align:start position:0% implementation for Android and 00:20:41.700 --> 00:20:44.610 align:start position:0% implementation for Android and multi-threaded<00:20:42.700> programming<00:20:43.180> using<00:20:43.750> j9<00:20:44.350> for 00:20:44.610 --> 00:20:44.620 align:start position:0% multi-threaded programming using j9 for 00:20:44.620 --> 00:20:49.110 align:start position:0% multi-threaded programming using j9 for Android<00:20:44.980> was<00:20:45.640> very<00:20:46.180> very<00:20:46.480> good<00:20:46.840> and<00:20:48.120> so 00:20:49.110 --> 00:20:49.120 align:start position:0% Android was very very good and so 00:20:49.120 --> 00:20:51.590 align:start position:0% Android was very very good and so considering<00:20:49.990> needs<00:20:50.260> challenges<00:20:50.890> we<00:20:51.160> have<00:20:51.340> to 00:20:51.590 --> 00:20:51.600 align:start position:0% considering needs challenges we have to 00:20:51.600 --> 00:20:54.750 align:start position:0% considering needs challenges we have to be<00:20:52.600> decided<00:20:53.110> our<00:20:53.380> next<00:20:53.740> major<00:20:53.890> milestone<00:20:54.040> to 00:20:54.750 --> 00:20:54.760 align:start position:0% be decided our next major milestone to 00:20:54.760 --> 00:20:57.390 align:start position:0% be decided our next major milestone to create<00:20:55.270> quality<00:20:55.510> for<00:20:56.040> developers<00:20:57.040> and 00:20:57.390 --> 00:20:57.400 align:start position:0% create quality for developers and 00:20:57.400 --> 00:20:59.880 align:start position:0% create quality for developers and developer<00:20:58.210> for<00:20:58.420> all<00:20:58.630> by<00:20:59.260> the<00:20:59.320> end<00:20:59.590> of<00:20:59.740> this 00:20:59.880 --> 00:20:59.890 align:start position:0% developer for all by the end of this 00:20:59.890 --> 00:21:04.080 align:start position:0% developer for all by the end of this year<00:21:00.220> so<00:21:02.250> I'm<00:21:03.250> just<00:21:03.460> going<00:21:03.610> to<00:21:03.730> explain<00:21:04.030> a 00:21:04.080 --> 00:21:04.090 align:start position:0% year so I'm just going to explain a 00:21:04.090 --> 00:21:08.340 align:start position:0% year so I'm just going to explain a little<00:21:04.570> test<00:21:04.810> of<00:21:05.110> your<00:21:05.820> coming<00:21:06.820> next<00:21:07.030> term<00:21:07.720> so 00:21:08.340 --> 00:21:08.350 align:start position:0% little test of your coming next term so 00:21:08.350 --> 00:21:12.210 align:start position:0% little test of your coming next term so we<00:21:09.190> are<00:21:09.460> actually<00:21:09.670> putting<00:21:10.150> all<00:21:10.450> this<00:21:11.220> little 00:21:12.210 --> 00:21:12.220 align:start position:0% we are actually putting all this little 00:21:12.220 --> 00:21:14.730 align:start position:0% we are actually putting all this little tasks<00:21:12.460> on<00:21:12.700> it<00:21:13.120> only<00:21:13.540> fondant<00:21:13.990> issues<00:21:14.260> so 00:21:14.730 --> 00:21:14.740 align:start position:0% tasks on it only fondant issues so 00:21:14.740 --> 00:21:17.340 align:start position:0% tasks on it only fondant issues so please<00:21:15.100> find<00:21:15.370> us<00:21:15.640> and<00:21:15.880> if<00:21:16.600> you<00:21:16.720> wanna<00:21:16.900> go<00:21:17.110> pitch 00:21:17.340 --> 00:21:17.350 align:start position:0% please find us and if you wanna go pitch 00:21:17.350 --> 00:21:18.930 align:start position:0% please find us and if you wanna go pitch velocity<00:21:17.650> creates 00:21:18.930 --> 00:21:18.940 align:start position:0% velocity creates 00:21:18.940 --> 00:21:20.850 align:start position:0% velocity creates joke<00:21:19.090> these<00:21:19.270> ups<00:21:19.540> all<00:21:19.840> right<00:21:20.320> we<00:21:20.530> all<00:21:20.650> work 00:21:20.850 --> 00:21:20.860 align:start position:0% joke these ups all right we all work 00:21:20.860 --> 00:21:23.010 align:start position:0% joke these ups all right we all work these<00:21:21.100> cases<00:21:21.210> please<00:21:22.210> come<00:21:22.450> to<00:21:22.630> talk<00:21:22.840> to<00:21:22.870> us 00:21:23.010 --> 00:21:23.020 align:start position:0% these cases please come to talk to us 00:21:23.020 --> 00:21:29.270 align:start position:0% these cases please come to talk to us come<00:21:23.650> up<00:21:23.890> to<00:21:24.130> us<00:21:24.160> and<00:21:24.550> let's<00:21:25.150> open<00:21:25.360> it<00:21:25.690> together 00:21:29.270 --> 00:21:29.280 align:start position:0% 00:21:29.280 --> 00:21:35.320 align:start position:0% thank<00:21:30.280> you<00:21:30.490> for<00:21:30.960> listening 00:21:35.320 --> 00:21:35.330 align:start position:0% 00:21:35.330 --> 00:21:41.750 align:start position:0% [Applause]