WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.950 align:start position:0% [Applause] 00:00:11.950 --> 00:00:11.960 align:start position:0% 00:00:11.960 --> 00:00:16.280 align:start position:0% this<00:00:12.960> very<00:00:13.770> lousy<00:00:14.520> technical<00:00:15.270> talk<00:00:15.510> also<00:00:16.049> one 00:00:16.280 --> 00:00:16.290 align:start position:0% this very lousy technical talk also one 00:00:16.290 --> 00:00:19.100 align:start position:0% this very lousy technical talk also one layer<00:00:16.530> to<00:00:16.800> UX<00:00:17.700> design<00:00:18.270> patterns<00:00:18.720> I<00:00:18.840> shoulda 00:00:19.100 --> 00:00:19.110 align:start position:0% layer to UX design patterns I shoulda 00:00:19.110 --> 00:00:21.590 align:start position:0% layer to UX design patterns I shoulda landed<00:00:19.460> other<00:00:20.460> people<00:00:20.790> studies<00:00:21.060> about 00:00:21.590 --> 00:00:21.600 align:start position:0% landed other people studies about 00:00:21.600 --> 00:00:23.510 align:start position:0% landed other people studies about development<00:00:22.500> but<00:00:22.619> it's<00:00:22.770> about<00:00:22.980> design 00:00:23.510 --> 00:00:23.520 align:start position:0% development but it's about design 00:00:23.520 --> 00:00:25.670 align:start position:0% development but it's about design actually<00:00:23.760> so<00:00:24.600> how<00:00:24.810> many<00:00:24.869> of<00:00:25.050> you<00:00:25.140> are<00:00:25.380> actually 00:00:25.670 --> 00:00:25.680 align:start position:0% actually so how many of you are actually 00:00:25.680 --> 00:00:28.339 align:start position:0% actually so how many of you are actually familiar<00:00:26.040> with<00:00:26.579> layer<00:00:26.910> 2<00:00:27.270> technologies 00:00:28.339 --> 00:00:28.349 align:start position:0% familiar with layer 2 technologies 00:00:28.349 --> 00:00:32.359 align:start position:0% familiar with layer 2 technologies NoHo<00:00:28.980> plasma<00:00:29.700> state<00:00:30.240> channels<00:00:30.750> work<00:00:31.369> comic 00:00:32.359 --> 00:00:32.369 align:start position:0% NoHo plasma state channels work comic 00:00:32.369 --> 00:00:36.530 align:start position:0% NoHo plasma state channels work comic don't<00:00:34.100> okay<00:00:35.100> a<00:00:35.130> few<00:00:35.610> we<00:00:35.940> will<00:00:36.090> have<00:00:36.239> a<00:00:36.270> tiny 00:00:36.530 --> 00:00:36.540 align:start position:0% don't okay a few we will have a tiny 00:00:36.540 --> 00:00:38.750 align:start position:0% don't okay a few we will have a tiny tiny<00:00:36.840> primer<00:00:37.230> above<00:00:37.590> that<00:00:37.739> so<00:00:37.980> that<00:00:38.220> you<00:00:38.579> can 00:00:38.750 --> 00:00:38.760 align:start position:0% tiny primer above that so that you can 00:00:38.760 --> 00:00:42.800 align:start position:0% tiny primer above that so that you can get<00:00:39.060> out<00:00:39.210> dispute<00:00:39.630> so<00:00:40.250> on<00:00:41.250> the<00:00:41.370> agenda<00:00:41.520> I<00:00:42.180> will 00:00:42.800 --> 00:00:42.810 align:start position:0% get out dispute so on the agenda I will 00:00:42.810 --> 00:00:46.640 align:start position:0% get out dispute so on the agenda I will give<00:00:43.140> a<00:00:43.170> tiny<00:00:43.950> detail<00:00:44.340> about<00:00:45.050> precedents<00:00:46.050> for 00:00:46.640 --> 00:00:46.650 align:start position:0% give a tiny detail about precedents for 00:00:46.650 --> 00:00:49.910 align:start position:0% give a tiny detail about precedents for the<00:00:46.920> framework<00:00:47.310> of<00:00:47.850> how<00:00:48.360> we<00:00:48.420> went<00:00:49.350> out<00:00:49.650> and 00:00:49.910 --> 00:00:49.920 align:start position:0% the framework of how we went out and 00:00:49.920 --> 00:00:52.450 align:start position:0% the framework of how we went out and found<00:00:50.010> these<00:00:50.490> principles<00:00:51.120> tiny<00:00:51.750> principles 00:00:52.450 --> 00:00:52.460 align:start position:0% found these principles tiny principles 00:00:52.460 --> 00:00:55.310 align:start position:0% found these principles tiny principles at<00:00:53.460> the<00:00:53.640> primer<00:00:53.910> only<00:00:54.270> to<00:00:54.510> technology<00:00:54.960> so<00:00:55.140> that 00:00:55.310 --> 00:00:55.320 align:start position:0% at the primer only to technology so that 00:00:55.320 --> 00:00:56.279 align:start position:0% at the primer only to technology so that those<00:00:55.770> of 00:00:56.279 --> 00:00:56.289 align:start position:0% those of 00:00:56.289 --> 00:00:58.110 align:start position:0% those of understand<00:00:56.890> what<00:00:57.250> we're<00:00:57.399> talking<00:00:57.640> about<00:00:57.699> and 00:00:58.110 --> 00:00:58.120 align:start position:0% understand what we're talking about and 00:00:58.120 --> 00:01:00.329 align:start position:0% understand what we're talking about and then<00:00:58.660> there<00:00:58.899> are<00:00:59.019> these<00:00:59.199> leads<00:00:59.800> to<00:00:59.980> design 00:01:00.329 --> 00:01:00.339 align:start position:0% then there are these leads to design 00:01:00.339 --> 00:01:03.149 align:start position:0% then there are these leads to design patterns<00:01:00.789> very<00:01:01.300> very<00:01:01.660> little<00:01:02.589> and<00:01:02.859> few 00:01:03.149 --> 00:01:03.159 align:start position:0% patterns very very little and few 00:01:03.159 --> 00:01:08.760 align:start position:0% patterns very very little and few patterns<00:01:03.399> because<00:01:04.710> there's<00:01:06.930> not<00:01:07.930> being<00:01:08.259> much 00:01:08.760 --> 00:01:08.770 align:start position:0% patterns because there's not being much 00:01:08.770 --> 00:01:11.249 align:start position:0% patterns because there's not being much time<00:01:09.100> to<00:01:09.280> test<00:01:09.490> with<00:01:09.790> real<00:01:10.060> users<00:01:10.119> I<00:01:10.659> test<00:01:11.080> only 00:01:11.249 --> 00:01:11.259 align:start position:0% time to test with real users I test only 00:01:11.259 --> 00:01:12.840 align:start position:0% time to test with real users I test only with<00:01:11.409> you<00:01:11.560> who<00:01:11.860> will<00:01:12.280> tell<00:01:12.490> you<00:01:12.580> about<00:01:12.640> that 00:01:12.840 --> 00:01:12.850 align:start position:0% with you who will tell you about that 00:01:12.850 --> 00:01:16.350 align:start position:0% with you who will tell you about that and<00:01:13.090> a<00:01:13.210> summary<00:01:13.509> of<00:01:13.600> insights<00:01:14.369> and<00:01:15.369> of<00:01:16.030> course 00:01:16.350 --> 00:01:16.360 align:start position:0% and a summary of insights and of course 00:01:16.360 --> 00:01:20.789 align:start position:0% and a summary of insights and of course in<00:01:16.630> the<00:01:16.780> middle<00:01:17.080> is<00:01:17.920> it<00:01:18.100> going<00:01:18.390> yeah<00:01:19.390> okay<00:01:20.170> we 00:01:20.789 --> 00:01:20.799 align:start position:0% in the middle is it going yeah okay we 00:01:20.799 --> 00:01:22.920 align:start position:0% in the middle is it going yeah okay we will<00:01:21.009> have<00:01:21.220> the<00:01:21.399> voices<00:01:21.880> of<00:01:22.030> the<00:01:22.149> users<00:01:22.539> okay 00:01:22.920 --> 00:01:22.930 align:start position:0% will have the voices of the users okay 00:01:22.930 --> 00:01:25.980 align:start position:0% will have the voices of the users okay that<00:01:23.110> is<00:01:23.200> these<00:01:23.320> bubbles<00:01:23.770> of<00:01:24.780> things<00:01:25.780> that 00:01:25.980 --> 00:01:25.990 align:start position:0% that is these bubbles of things that 00:01:25.990 --> 00:01:28.260 align:start position:0% that is these bubbles of things that people<00:01:26.140> and<00:01:26.680> users<00:01:27.039> actually<00:01:27.549> told<00:01:27.850> me<00:01:28.000> I<00:01:28.030> mean 00:01:28.260 --> 00:01:28.270 align:start position:0% people and users actually told me I mean 00:01:28.270 --> 00:01:30.930 align:start position:0% people and users actually told me I mean to<00:01:28.330> do<00:01:28.569> that<00:01:28.600> non<00:01:29.229> crypto<00:01:29.770> users<00:01:30.340> but<00:01:30.550> Victor 00:01:30.930 --> 00:01:30.940 align:start position:0% to do that non crypto users but Victor 00:01:30.940 --> 00:01:33.930 align:start position:0% to do that non crypto users but Victor of<00:01:31.060> Korean<00:01:31.509> users<00:01:31.780> also<00:01:32.140> and<00:01:32.560> they<00:01:33.550> will<00:01:33.759> be 00:01:33.930 --> 00:01:33.940 align:start position:0% of Korean users also and they will be 00:01:33.940 --> 00:01:35.309 align:start position:0% of Korean users also and they will be speaking<00:01:34.240> in<00:01:34.569> the<00:01:34.750> middle<00:01:35.020> of<00:01:35.229> the 00:01:35.309 --> 00:01:35.319 align:start position:0% speaking in the middle of the 00:01:35.319 --> 00:01:36.930 align:start position:0% speaking in the middle of the presentation<00:01:35.920> so<00:01:36.130> that<00:01:36.280> you<00:01:36.340> can<00:01:36.520> hear<00:01:36.789> the 00:01:36.930 --> 00:01:36.940 align:start position:0% presentation so that you can hear the 00:01:36.940 --> 00:01:39.300 align:start position:0% presentation so that you can hear the voice<00:01:36.970> as<00:01:37.300> well<00:01:37.569> so<00:01:38.200> unless<00:01:38.440> you<00:01:38.649> represented 00:01:39.300 --> 00:01:39.310 align:start position:0% voice as well so unless you represented 00:01:39.310 --> 00:01:42.210 align:start position:0% voice as well so unless you represented this<00:01:39.520> Web<00:01:40.420> 3<00:01:40.659> design<00:01:41.110> decision<00:01:41.799> making 00:01:42.210 --> 00:01:42.220 align:start position:0% this Web 3 design decision making 00:01:42.220 --> 00:01:44.070 align:start position:0% this Web 3 design decision making framework<00:01:42.460> was<00:01:42.880> a<00:01:42.909> tool<00:01:43.240> that<00:01:43.539> came<00:01:43.690> out<00:01:43.869> from 00:01:44.070 --> 00:01:44.080 align:start position:0% framework was a tool that came out from 00:01:44.080 --> 00:01:46.230 align:start position:0% framework was a tool that came out from the<00:01:44.170> interviews<00:01:44.799> of<00:01:45.039> many<00:01:45.729> different 00:01:46.230 --> 00:01:46.240 align:start position:0% the interviews of many different 00:01:46.240 --> 00:01:48.630 align:start position:0% the interviews of many different companies<00:01:46.420> in<00:01:46.780> this<00:01:46.869> race<00:01:47.110> that<00:01:48.100> helped<00:01:48.490> us 00:01:48.630 --> 00:01:48.640 align:start position:0% companies in this race that helped us 00:01:48.640 --> 00:01:51.240 align:start position:0% companies in this race that helped us map<00:01:49.299> the<00:01:49.600> different<00:01:49.990> problems<00:01:50.319> users<00:01:51.039> have 00:01:51.240 --> 00:01:51.250 align:start position:0% map the different problems users have 00:01:51.250 --> 00:01:53.550 align:start position:0% map the different problems users have into<00:01:52.000> different<00:01:52.420> types<00:01:52.659> of<00:01:52.869> buckets<00:01:53.259> of 00:01:53.550 --> 00:01:53.560 align:start position:0% into different types of buckets of 00:01:53.560 --> 00:01:55.320 align:start position:0% into different types of buckets of questions<00:01:54.369> that<00:01:54.459> were<00:01:54.729> fundamental<00:01:55.299> to 00:01:55.320 --> 00:01:55.330 align:start position:0% questions that were fundamental to 00:01:55.330 --> 00:01:57.990 align:start position:0% questions that were fundamental to decentralization<00:01:56.020> and<00:01:56.640> things<00:01:57.640> that<00:01:57.759> are 00:01:57.990 --> 00:01:58.000 align:start position:0% decentralization and things that are 00:01:58.000 --> 00:01:59.940 align:start position:0% decentralization and things that are related<00:01:58.330> to<00:01:58.600> the<00:01:58.810> technicalities<00:01:59.470> of<00:01:59.500> the 00:01:59.940 --> 00:01:59.950 align:start position:0% related to the technicalities of the 00:01:59.950 --> 00:02:01.830 align:start position:0% related to the technicalities of the object<00:02:00.520> this<00:02:00.670> is<00:02:00.789> interesting<00:02:01.270> because<00:02:01.569> it 00:02:01.830 --> 00:02:01.840 align:start position:0% object this is interesting because it 00:02:01.840 --> 00:02:04.139 align:start position:0% object this is interesting because it leads<00:02:02.020> to<00:02:02.200> how<00:02:02.890> we<00:02:02.950> found<00:02:03.220> the<00:02:03.789> design 00:02:04.139 --> 00:02:04.149 align:start position:0% leads to how we found the design 00:02:04.149 --> 00:02:06.600 align:start position:0% leads to how we found the design patterns<00:02:04.599> and<00:02:04.899> also<00:02:05.050> why<00:02:05.739> we<00:02:06.190> started<00:02:06.520> doing 00:02:06.600 --> 00:02:06.610 align:start position:0% patterns and also why we started doing 00:02:06.610 --> 00:02:09.449 align:start position:0% patterns and also why we started doing the<00:02:06.879> layer<00:02:07.119> 2<00:02:07.360> design<00:02:07.629> happens<00:02:07.810> so<00:02:08.560> what<00:02:09.250> we 00:02:09.449 --> 00:02:09.459 align:start position:0% the layer 2 design happens so what we 00:02:09.459 --> 00:02:12.990 align:start position:0% the layer 2 design happens so what we found<00:02:09.670> out<00:02:09.940> is<00:02:10.270> at<00:02:10.569> work<00:02:10.899> there's<00:02:11.459> new<00:02:12.459> mental 00:02:12.990 --> 00:02:13.000 align:start position:0% found out is at work there's new mental 00:02:13.000 --> 00:02:16.350 align:start position:0% found out is at work there's new mental models<00:02:13.450> and<00:02:13.780> there<00:02:14.440> are<00:02:14.700> there<00:02:15.700> are<00:02:15.849> also<00:02:16.060> new 00:02:16.350 --> 00:02:16.360 align:start position:0% models and there are there are also new 00:02:16.360 --> 00:02:20.100 align:start position:0% models and there are there are also new complicated<00:02:16.930> concepts<00:02:17.470> and<00:02:17.700> these<00:02:18.700> fits<00:02:19.180> in 00:02:20.100 --> 00:02:20.110 align:start position:0% complicated concepts and these fits in 00:02:20.110 --> 00:02:21.900 align:start position:0% complicated concepts and these fits in different<00:02:20.470> things<00:02:20.710> and<00:02:21.010> the<00:02:21.250> solutions<00:02:21.790> that 00:02:21.900 --> 00:02:21.910 align:start position:0% different things and the solutions that 00:02:21.910 --> 00:02:25.440 align:start position:0% different things and the solutions that these<00:02:22.210> companies<00:02:22.660> were<00:02:22.930> using<00:02:23.730> range<00:02:24.730> in<00:02:25.090> two 00:02:25.440 --> 00:02:25.450 align:start position:0% these companies were using range in two 00:02:25.450 --> 00:02:27.840 align:start position:0% these companies were using range in two different<00:02:25.870> buckets<00:02:26.680> as<00:02:26.830> well<00:02:27.040> if<00:02:27.520> you<00:02:27.670> want 00:02:27.840 --> 00:02:27.850 align:start position:0% different buckets as well if you want 00:02:27.850 --> 00:02:29.850 align:start position:0% different buckets as well if you want things<00:02:28.330> that<00:02:28.480> you<00:02:28.900> could<00:02:29.110> hide<00:02:29.350> you<00:02:29.680> should 00:02:29.850 --> 00:02:29.860 align:start position:0% things that you could hide you should 00:02:29.860 --> 00:02:32.430 align:start position:0% things that you could hide you should type<00:02:30.100> to<00:02:30.400> the<00:02:30.520> user<00:02:30.700> and<00:02:31.140> things<00:02:32.140> that<00:02:32.230> are 00:02:32.430 --> 00:02:32.440 align:start position:0% type to the user and things that are 00:02:32.440 --> 00:02:34.530 align:start position:0% type to the user and things that are technical<00:02:32.950> you<00:02:33.310> should<00:02:33.550> oh<00:02:33.790> and<00:02:34.330> you<00:02:34.390> can 00:02:34.530 --> 00:02:34.540 align:start position:0% technical you should oh and you can 00:02:34.540 --> 00:02:36.300 align:start position:0% technical you should oh and you can alight<00:02:34.810> you<00:02:35.080> should<00:02:35.260> explain<00:02:35.590> better<00:02:35.830> I'm<00:02:36.250> not 00:02:36.300 --> 00:02:36.310 align:start position:0% alight you should explain better I'm not 00:02:36.310 --> 00:02:37.830 align:start position:0% alight you should explain better I'm not going<00:02:36.700> through<00:02:36.880> the<00:02:37.090> whole<00:02:37.120> presentation<00:02:37.390> I 00:02:37.830 --> 00:02:37.840 align:start position:0% going through the whole presentation I 00:02:37.840 --> 00:02:40.560 align:start position:0% going through the whole presentation I would<00:02:37.960> love<00:02:38.110> you<00:02:38.320> but<00:02:38.890> just<00:02:39.760> a<00:02:39.940> simple<00:02:40.330> example 00:02:40.560 --> 00:02:40.570 align:start position:0% would love you but just a simple example 00:02:40.570 --> 00:02:42.210 align:start position:0% would love you but just a simple example to<00:02:41.020> the<00:02:41.110> sound<00:02:41.350> like<00:02:41.620> gas<00:02:41.860> is<00:02:42.100> a 00:02:42.210 --> 00:02:42.220 align:start position:0% to the sound like gas is a 00:02:42.220 --> 00:02:44.610 align:start position:0% to the sound like gas is a multi-dimensional<00:02:43.210> problem<00:02:43.990> you<00:02:44.140> can't<00:02:44.380> have 00:02:44.610 --> 00:02:44.620 align:start position:0% multi-dimensional problem you can't have 00:02:44.620 --> 00:02:47.010 align:start position:0% multi-dimensional problem you can't have things<00:02:45.550> that<00:02:45.730> you<00:02:45.850> can<00:02:46.060> hide<00:02:46.300> away<00:02:46.330> like<00:02:46.870> what 00:02:47.010 --> 00:02:47.020 align:start position:0% things that you can hide away like what 00:02:47.020 --> 00:02:51.300 align:start position:0% things that you can hide away like what is<00:02:47.170> got<00:02:47.380> right<00:02:48.660> designers<00:02:49.660> and<00:02:50.190> projects<00:02:51.190> have 00:02:51.300 --> 00:02:51.310 align:start position:0% is got right designers and projects have 00:02:51.310 --> 00:02:52.800 align:start position:0% is got right designers and projects have had<00:02:51.460> a<00:02:51.670> lot<00:02:51.970> of<00:02:52.000> success<00:02:52.450> in<00:02:52.480> finding 00:02:52.800 --> 00:02:52.810 align:start position:0% had a lot of success in finding 00:02:52.810 --> 00:02:54.510 align:start position:0% had a lot of success in finding different<00:02:53.320> questions<00:02:53.680> but<00:02:54.040> there<00:02:54.190> are<00:02:54.340> other 00:02:54.510 --> 00:02:54.520 align:start position:0% different questions but there are other 00:02:54.520 --> 00:02:58.020 align:start position:0% different questions but there are other things<00:02:54.700> like<00:02:55.440> why<00:02:56.440> is<00:02:56.830> there<00:02:57.220> a<00:02:57.250> price<00:02:57.550> at<00:02:57.850> all 00:02:58.020 --> 00:02:58.030 align:start position:0% things like why is there a price at all 00:02:58.030 --> 00:03:00.150 align:start position:0% things like why is there a price at all who<00:02:58.360> is<00:02:58.480> it<00:02:58.630> getting<00:02:59.020> it<00:02:59.140> that<00:02:59.380> you<00:02:59.740> need<00:02:59.950> to 00:03:00.150 --> 00:03:00.160 align:start position:0% who is it getting it that you need to 00:03:00.160 --> 00:03:03.270 align:start position:0% who is it getting it that you need to find<00:03:00.490> better<00:03:01.770> explainers<00:03:02.770> for<00:03:02.950> this<00:03:03.070> and 00:03:03.270 --> 00:03:03.280 align:start position:0% find better explainers for this and 00:03:03.280 --> 00:03:07.830 align:start position:0% find better explainers for this and these<00:03:03.660> happen<00:03:04.660> also<00:03:04.990> in<00:03:05.380> the<00:03:05.740> negative<00:03:06.010> and<00:03:06.840> of 00:03:07.830 --> 00:03:07.840 align:start position:0% these happen also in the negative and of 00:03:07.840 --> 00:03:09.840 align:start position:0% these happen also in the negative and of course<00:03:08.140> the<00:03:08.650> solutions<00:03:09.220> these<00:03:09.490> companies 00:03:09.840 --> 00:03:09.850 align:start position:0% course the solutions these companies 00:03:09.850 --> 00:03:12.930 align:start position:0% course the solutions these companies were<00:03:10.120> using<00:03:10.600> could<00:03:11.440> be<00:03:11.860> mapped<00:03:12.130> out<00:03:12.370> in<00:03:12.610> here 00:03:12.930 --> 00:03:12.940 align:start position:0% were using could be mapped out in here 00:03:12.940 --> 00:03:15.510 align:start position:0% were using could be mapped out in here and<00:03:12.970> so<00:03:13.420> this<00:03:13.840> is<00:03:13.900> where<00:03:14.500> the<00:03:14.740> layer<00:03:14.920> two<00:03:15.190> comes 00:03:15.510 --> 00:03:15.520 align:start position:0% and so this is where the layer two comes 00:03:15.520 --> 00:03:18.350 align:start position:0% and so this is where the layer two comes in<00:03:15.700> which<00:03:16.000> is<00:03:16.150> there<00:03:16.840> was<00:03:17.020> a<00:03:17.050> high<00:03:17.500> degree<00:03:17.830> of 00:03:18.350 --> 00:03:18.360 align:start position:0% in which is there was a high degree of 00:03:18.360 --> 00:03:20.760 align:start position:0% in which is there was a high degree of consensus<00:03:19.360> among<00:03:19.780> developers<00:03:20.410> and<00:03:20.680> designers 00:03:20.760 --> 00:03:20.770 align:start position:0% consensus among developers and designers 00:03:20.770 --> 00:03:23.640 align:start position:0% consensus among developers and designers and<00:03:21.520> working<00:03:22.330> in<00:03:22.450> the<00:03:22.540> space<00:03:22.750> but<00:03:22.959> sometimes 00:03:23.640 --> 00:03:23.650 align:start position:0% and working in the space but sometimes 00:03:23.650 --> 00:03:26.460 align:start position:0% and working in the space but sometimes it's<00:03:23.980> okay<00:03:24.250> to<00:03:24.280> have<00:03:24.670> a<00:03:24.730> server<00:03:25.180> a<00:03:25.720> server<00:03:25.840> that 00:03:26.460 --> 00:03:26.470 align:start position:0% it's okay to have a server a server that 00:03:26.470 --> 00:03:28.890 align:start position:0% it's okay to have a server a server that helps<00:03:26.800> you<00:03:26.920> in<00:03:27.070> the<00:03:27.190> middle<00:03:27.370> that<00:03:27.750> there<00:03:28.750> is<00:03:28.870> a 00:03:28.890 --> 00:03:28.900 align:start position:0% helps you in the middle that there is a 00:03:28.900 --> 00:03:31.820 align:start position:0% helps you in the middle that there is a degree<00:03:29.530> of<00:03:29.560> centralization<00:03:30.480> especially<00:03:31.480> for 00:03:31.820 --> 00:03:31.830 align:start position:0% degree of centralization especially for 00:03:31.830 --> 00:03:35.940 align:start position:0% degree of centralization especially for newcomers<00:03:32.830> for<00:03:33.060> non<00:03:34.060> crypto<00:03:34.660> user<00:03:34.930> it's<00:03:35.470> okay 00:03:35.940 --> 00:03:35.950 align:start position:0% newcomers for non crypto user it's okay 00:03:35.950 --> 00:03:38.790 align:start position:0% newcomers for non crypto user it's okay to<00:03:36.370> build<00:03:36.580> them<00:03:36.940> by<00:03:37.120> the<00:03:37.180> hand<00:03:37.510> and<00:03:37.810> then<00:03:38.650> on 00:03:38.790 --> 00:03:38.800 align:start position:0% to build them by the hand and then on 00:03:38.800 --> 00:03:40.440 align:start position:0% to build them by the hand and then on portable<00:03:39.190> to<00:03:39.430> real<00:03:39.760> decentralized 00:03:40.440 --> 00:03:40.450 align:start position:0% portable to real decentralized 00:03:40.450 --> 00:03:45.240 align:start position:0% portable to real decentralized technology<00:03:40.570> and<00:03:41.410> so<00:03:41.650> this<00:03:41.860> is<00:03:42.070> why<00:03:42.880> I<00:03:44.250> thought 00:03:45.240 --> 00:03:45.250 align:start position:0% technology and so this is why I thought 00:03:45.250 --> 00:03:47.640 align:start position:0% technology and so this is why I thought that<00:03:45.700> lady<00:03:46.000> two<00:03:46.239> had<00:03:46.630> that<00:03:46.870> promise<00:03:47.380> of 00:03:47.640 --> 00:03:47.650 align:start position:0% that lady two had that promise of 00:03:47.650 --> 00:03:50.250 align:start position:0% that lady two had that promise of bringing<00:03:48.209> the<00:03:49.209> degree<00:03:49.810> of<00:03:49.989> centralization 00:03:50.250 --> 00:03:50.260 align:start position:0% bringing the degree of centralization 00:03:50.260 --> 00:03:54.180 align:start position:0% bringing the degree of centralization but<00:03:51.250> it<00:03:51.519> still<00:03:51.880> has<00:03:52.090> the<00:03:52.780> security<00:03:53.530> of<00:03:53.560> layer<00:03:53.769> 1 00:03:54.180 --> 00:03:54.190 align:start position:0% but it still has the security of layer 1 00:03:54.190 --> 00:03:56.820 align:start position:0% but it still has the security of layer 1 so<00:03:54.340> right<00:03:55.239> now<00:03:55.390> a<00:03:55.420> primer<00:03:55.840> on<00:03:55.959> state<00:03:56.440> channels 00:03:56.820 --> 00:03:56.830 align:start position:0% so right now a primer on state channels 00:03:56.830 --> 00:04:00.060 align:start position:0% so right now a primer on state channels and<00:03:57.040> on<00:03:57.430> plasma<00:03:57.910> and<00:03:58.180> state<00:03:59.140> channels<00:03:59.560> they 00:04:00.060 --> 00:04:00.070 align:start position:0% and on plasma and state channels they 00:04:00.070 --> 00:04:02.130 align:start position:0% and on plasma and state channels they all<00:04:00.400> basically<00:04:00.850> work<00:04:01.150> more<00:04:01.690> or<00:04:01.750> less<00:04:01.870> the<00:04:01.989> same 00:04:02.130 --> 00:04:02.140 align:start position:0% all basically work more or less the same 00:04:02.140 --> 00:04:03.960 align:start position:0% all basically work more or less the same thing<00:04:02.380> you<00:04:02.560> have<00:04:02.709> layer<00:04:02.950> one<00:04:03.340> technology<00:04:03.700> that 00:04:03.960 --> 00:04:03.970 align:start position:0% thing you have layer one technology that 00:04:03.970 --> 00:04:05.370 align:start position:0% thing you have layer one technology that will<00:04:04.239> all<00:04:04.330> change<00:04:04.570> if<00:04:04.780> you<00:04:04.900> I'm<00:04:05.019> not<00:04:05.170> saying 00:04:05.370 --> 00:04:05.380 align:start position:0% will all change if you I'm not saying 00:04:05.380 --> 00:04:08.040 align:start position:0% will all change if you I'm not saying where<00:04:05.620> you<00:04:05.709> have<00:04:05.860> a<00:04:05.890> smart<00:04:06.430> contract<00:04:06.940> you<00:04:07.510> drop 00:04:08.040 --> 00:04:08.050 align:start position:0% where you have a smart contract you drop 00:04:08.050 --> 00:04:11.729 align:start position:0% where you have a smart contract you drop in<00:04:08.230> or<00:04:08.440> you<00:04:08.560> lock<00:04:08.830> in<00:04:09.660> some<00:04:10.660> tokens<00:04:11.320> some<00:04:11.530> ether 00:04:11.729 --> 00:04:11.739 align:start position:0% in or you lock in some tokens some ether 00:04:11.739 --> 00:04:13.560 align:start position:0% in or you lock in some tokens some ether ok<00:04:12.489> and 00:04:13.560 --> 00:04:13.570 align:start position:0% ok and 00:04:13.570 --> 00:04:14.630 align:start position:0% ok and anything 00:04:14.630 --> 00:04:14.640 align:start position:0% anything 00:04:14.640 --> 00:04:17.720 align:start position:0% anything have<00:04:14.850> been<00:04:15.000> obtained<00:04:15.660> either<00:04:16.290> in<00:04:16.950> the<00:04:17.220> case<00:04:17.400> of 00:04:17.720 --> 00:04:17.730 align:start position:0% have been obtained either in the case of 00:04:17.730 --> 00:04:20.210 align:start position:0% have been obtained either in the case of state<00:04:18.269> panels<00:04:18.690> these<00:04:19.200> are<00:04:19.440> like<00:04:19.769> normal 00:04:20.210 --> 00:04:20.220 align:start position:0% state panels these are like normal 00:04:20.220 --> 00:04:23.060 align:start position:0% state panels these are like normal server<00:04:20.660> transactions<00:04:21.660> where<00:04:22.019> two<00:04:22.590> parties 00:04:23.060 --> 00:04:23.070 align:start position:0% server transactions where two parties 00:04:23.070 --> 00:04:26.090 align:start position:0% server transactions where two parties Alice<00:04:23.520> and<00:04:23.700> Bob<00:04:23.880> sign<00:04:24.660> each<00:04:24.900> other<00:04:25.230> messages 00:04:26.090 --> 00:04:26.100 align:start position:0% Alice and Bob sign each other messages 00:04:26.100 --> 00:04:28.580 align:start position:0% Alice and Bob sign each other messages and<00:04:26.430> so<00:04:26.640> you<00:04:26.700> are<00:04:26.940> constantly<00:04:27.540> like<00:04:28.170> messaging 00:04:28.580 --> 00:04:28.590 align:start position:0% and so you are constantly like messaging 00:04:28.590 --> 00:04:31.250 align:start position:0% and so you are constantly like messaging each<00:04:28.980> other<00:04:29.250> the<00:04:29.580> new<00:04:29.790> state<00:04:30.270> and<00:04:30.660> you<00:04:30.840> agree 00:04:31.250 --> 00:04:31.260 align:start position:0% each other the new state and you agree 00:04:31.260 --> 00:04:33.170 align:start position:0% each other the new state and you agree on<00:04:31.410> that<00:04:31.440> space<00:04:32.010> it's<00:04:32.400> always<00:04:32.850> the<00:04:33.030> last 00:04:33.170 --> 00:04:33.180 align:start position:0% on that space it's always the last 00:04:33.180 --> 00:04:36.050 align:start position:0% on that space it's always the last Tuesday<00:04:33.750> and<00:04:34.430> whenever<00:04:35.430> you<00:04:35.669> want<00:04:35.940> to 00:04:36.050 --> 00:04:36.060 align:start position:0% Tuesday and whenever you want to 00:04:36.060 --> 00:04:38.990 align:start position:0% Tuesday and whenever you want to withdraw<00:04:36.390> you<00:04:37.140> go<00:04:37.440> back<00:04:37.680> to<00:04:38.040> layer<00:04:38.370> one<00:04:38.700> and 00:04:38.990 --> 00:04:39.000 align:start position:0% withdraw you go back to layer one and 00:04:39.000 --> 00:04:41.210 align:start position:0% withdraw you go back to layer one and there<00:04:39.419> is<00:04:39.450> where<00:04:39.840> the<00:04:40.110> security<00:04:40.770> comes<00:04:41.010> in 00:04:41.210 --> 00:04:41.220 align:start position:0% there is where the security comes in 00:04:41.220 --> 00:04:44.090 align:start position:0% there is where the security comes in through<00:04:41.790> a<00:04:41.850> challenge<00:04:42.720> period<00:04:43.200> maybe<00:04:43.380> this 00:04:44.090 --> 00:04:44.100 align:start position:0% through a challenge period maybe this 00:04:44.100 --> 00:04:47.630 align:start position:0% through a challenge period maybe this guy<00:04:44.340> wants<00:04:44.669> to<00:04:44.790> cheat<00:04:45.060> but<00:04:46.020> this<00:04:46.500> guy<00:04:47.010> here<00:04:47.430> has 00:04:47.630 --> 00:04:47.640 align:start position:0% guy wants to cheat but this guy here has 00:04:47.640 --> 00:04:49.670 align:start position:0% guy wants to cheat but this guy here has the<00:04:47.970> last<00:04:48.330> the<00:04:48.750> state<00:04:49.050> and<00:04:49.350> so<00:04:49.500> it's 00:04:49.670 --> 00:04:49.680 align:start position:0% the last the state and so it's 00:04:49.680 --> 00:04:52.250 align:start position:0% the last the state and so it's mathematically<00:04:50.400> provable<00:04:51.090> that<00:04:51.150> this<00:04:52.020> guy 00:04:52.250 --> 00:04:52.260 align:start position:0% mathematically provable that this guy 00:04:52.260 --> 00:04:54.830 align:start position:0% mathematically provable that this guy will<00:04:52.320> win<00:04:52.680> the<00:04:53.160> layer<00:04:53.400> 1<00:04:53.700> security<00:04:54.300> ensures 00:04:54.830 --> 00:04:54.840 align:start position:0% will win the layer 1 security ensures 00:04:54.840 --> 00:04:56.930 align:start position:0% will win the layer 1 security ensures that<00:04:55.020> anything<00:04:55.530> that<00:04:55.560> happens<00:04:55.830> off<00:04:56.220> chain<00:04:56.550> is 00:04:56.930 --> 00:04:56.940 align:start position:0% that anything that happens off chain is 00:04:56.940 --> 00:05:00.680 align:start position:0% that anything that happens off chain is secure<00:04:57.480> ok<00:04:58.110> and<00:04:58.410> there<00:04:59.160> is<00:04:59.280> few<00:05:00.180> to<00:05:00.419> clear 00:05:00.680 --> 00:05:00.690 align:start position:0% secure ok and there is few to clear 00:05:00.690 --> 00:05:04.640 align:start position:0% secure ok and there is few to clear networks<00:05:01.290> like<00:05:01.700> me<00:05:02.700> connected<00:05:03.120> with<00:05:03.650> Berto 00:05:04.640 --> 00:05:04.650 align:start position:0% networks like me connected with Berto 00:05:04.650 --> 00:05:09.140 align:start position:0% networks like me connected with Berto right<00:05:05.419> or<00:05:06.419> through<00:05:07.410> hubs<00:05:07.940> intermediary<00:05:08.940> six 00:05:09.140 --> 00:05:09.150 align:start position:0% right or through hubs intermediary six 00:05:09.150 --> 00:05:11.659 align:start position:0% right or through hubs intermediary six month<00:05:09.419> where<00:05:09.720> a<00:05:09.750> lot<00:05:10.140> of<00:05:10.320> users<00:05:10.770> are<00:05:10.800> connected 00:05:11.659 --> 00:05:11.669 align:start position:0% month where a lot of users are connected 00:05:11.669 --> 00:05:14.810 align:start position:0% month where a lot of users are connected together<00:05:12.090> ok<00:05:12.950> plasma<00:05:13.950> is<00:05:14.250> a<00:05:14.280> little<00:05:14.730> bit 00:05:14.810 --> 00:05:14.820 align:start position:0% together ok plasma is a little bit 00:05:14.820 --> 00:05:16.490 align:start position:0% together ok plasma is a little bit different<00:05:15.150> but<00:05:15.330> as<00:05:15.600> the<00:05:15.720> same<00:05:15.900> concept<00:05:16.440> you 00:05:16.490 --> 00:05:16.500 align:start position:0% different but as the same concept you 00:05:16.500 --> 00:05:19.280 align:start position:0% different but as the same concept you have<00:05:16.590> the<00:05:16.890> main<00:05:17.100> layer<00:05:17.550> one<00:05:17.910> chain<00:05:18.270> where<00:05:19.110> you 00:05:19.280 --> 00:05:19.290 align:start position:0% have the main layer one chain where you 00:05:19.290 --> 00:05:21.440 align:start position:0% have the main layer one chain where you have<00:05:19.440> contract<00:05:20.100> you<00:05:20.190> deposit<00:05:20.640> tokens<00:05:21.330> of 00:05:21.440 --> 00:05:21.450 align:start position:0% have contract you deposit tokens of 00:05:21.450 --> 00:05:23.840 align:start position:0% have contract you deposit tokens of ether<00:05:21.600> in<00:05:21.840> there<00:05:22.050> as<00:05:22.169> well<00:05:22.350> and<00:05:22.650> what<00:05:23.490> happens 00:05:23.840 --> 00:05:23.850 align:start position:0% ether in there as well and what happens 00:05:23.850 --> 00:05:26.390 align:start position:0% ether in there as well and what happens of<00:05:24.000> chain<00:05:24.270> is<00:05:24.450> actually<00:05:24.870> another<00:05:25.229> chain<00:05:25.919> but 00:05:26.390 --> 00:05:26.400 align:start position:0% of chain is actually another chain but 00:05:26.400 --> 00:05:30.200 align:start position:0% of chain is actually another chain but that<00:05:26.610> has<00:05:26.820> a<00:05:27.500> faster<00:05:28.500> throughput<00:05:29.070> they<00:05:30.000> have 00:05:30.200 --> 00:05:30.210 align:start position:0% that has a faster throughput they have 00:05:30.210 --> 00:05:34.520 align:start position:0% that has a faster throughput they have less<00:05:30.960> validators<00:05:31.740> there<00:05:32.190> is<00:05:33.200> you<00:05:34.200> can<00:05:34.380> have 00:05:34.520 --> 00:05:34.530 align:start position:0% less validators there is you can have 00:05:34.530 --> 00:05:36.800 align:start position:0% less validators there is you can have like<00:05:34.800> two<00:05:35.310> thousand<00:05:36.090> transactions<00:05:36.660> per 00:05:36.800 --> 00:05:36.810 align:start position:0% like two thousand transactions per 00:05:36.810 --> 00:05:38.330 align:start position:0% like two thousand transactions per second<00:05:37.140> more<00:05:37.440> or<00:05:37.500> less<00:05:37.650> here<00:05:37.950> and<00:05:38.160> you're 00:05:38.330 --> 00:05:38.340 align:start position:0% second more or less here and you're 00:05:38.340 --> 00:05:43.790 align:start position:0% second more or less here and you're competing<00:05:39.290> periodically<00:05:40.290> every<00:05:41.450> 32<00:05:42.800> seconds 00:05:43.790 --> 00:05:43.800 align:start position:0% competing periodically every 32 seconds 00:05:43.800 --> 00:05:47.690 align:start position:0% competing periodically every 32 seconds Morelos<00:05:44.520> minutes<00:05:45.740> 32<00:05:46.740> blocks<00:05:46.860> thank<00:05:47.280> you 00:05:47.690 --> 00:05:47.700 align:start position:0% Morelos minutes 32 blocks thank you 00:05:47.700 --> 00:05:51.230 align:start position:0% Morelos minutes 32 blocks thank you you're<00:05:48.090> committing<00:05:48.950> that<00:05:49.950> space<00:05:50.460> into<00:05:51.120> the 00:05:51.230 --> 00:05:51.240 align:start position:0% you're committing that space into the 00:05:51.240 --> 00:05:52.490 align:start position:0% you're committing that space into the chain<00:05:51.450> so<00:05:51.690> this<00:05:51.810> is<00:05:51.960> the<00:05:52.080> difference<00:05:52.440> between 00:05:52.490 --> 00:05:52.500 align:start position:0% chain so this is the difference between 00:05:52.500 --> 00:05:56.930 align:start position:0% chain so this is the difference between state<00:05:52.979> channels<00:05:53.400> and<00:05:54.500> plasma<00:05:55.500> which<00:05:56.130> is<00:05:56.370> in 00:05:56.930 --> 00:05:56.940 align:start position:0% state channels and plasma which is in 00:05:56.940 --> 00:06:00.020 align:start position:0% state channels and plasma which is in plasma<00:05:57.570> you<00:05:57.780> need<00:05:58.080> periodically<00:05:59.070> to<00:05:59.460> send 00:06:00.020 --> 00:06:00.030 align:start position:0% plasma you need periodically to send 00:06:00.030 --> 00:06:01.670 align:start position:0% plasma you need periodically to send transactions<00:06:00.750> on<00:06:00.900> chain<00:06:01.140> and<00:06:01.440> to<00:06:01.530> register 00:06:01.670 --> 00:06:01.680 align:start position:0% transactions on chain and to register 00:06:01.680 --> 00:06:04.520 align:start position:0% transactions on chain and to register information<00:06:02.550> in<00:06:03.300> state<00:06:03.600> channels<00:06:03.960> you<00:06:04.229> don't 00:06:04.520 --> 00:06:04.530 align:start position:0% information in state channels you don't 00:06:04.530 --> 00:06:07.790 align:start position:0% information in state channels you don't and<00:06:04.830> they<00:06:05.370> are<00:06:05.520> called<00:06:06.050> optimistic<00:06:07.050> layers<00:06:07.410> if 00:06:07.790 --> 00:06:07.800 align:start position:0% and they are called optimistic layers if 00:06:07.800 --> 00:06:10.100 align:start position:0% and they are called optimistic layers if you<00:06:07.919> want<00:06:08.130> because<00:06:08.580> you<00:06:09.000> don't<00:06:09.300> resort<00:06:09.960> to 00:06:10.100 --> 00:06:10.110 align:start position:0% you want because you don't resort to 00:06:10.110 --> 00:06:14.360 align:start position:0% you want because you don't resort to layer<00:06:10.410> one<00:06:10.800> until<00:06:12.169> you<00:06:13.169> actually<00:06:13.740> need<00:06:13.890> it<00:06:14.039> if 00:06:14.360 --> 00:06:14.370 align:start position:0% layer one until you actually need it if 00:06:14.370 --> 00:06:17.510 align:start position:0% layer one until you actually need it if L<00:06:14.669> if<00:06:14.850> we<00:06:15.030> are<00:06:15.210> behaving<00:06:15.600> well<00:06:16.190> you<00:06:17.190> don't<00:06:17.370> need 00:06:17.510 --> 00:06:17.520 align:start position:0% L if we are behaving well you don't need 00:06:17.520 --> 00:06:20.890 align:start position:0% L if we are behaving well you don't need to<00:06:17.580> go<00:06:17.880> on<00:06:17.910> the<00:06:18.390> plasma<00:06:19.140> does<00:06:19.500> this<00:06:20.100> thing<00:06:20.340> but 00:06:20.890 --> 00:06:20.900 align:start position:0% to go on the plasma does this thing but 00:06:20.900 --> 00:06:23.600 align:start position:0% to go on the plasma does this thing but if<00:06:21.900> only<00:06:22.620> in<00:06:22.919> the<00:06:23.099> case<00:06:23.250> we<00:06:23.430> are 00:06:23.600 --> 00:06:23.610 align:start position:0% if only in the case we are 00:06:23.610 --> 00:06:25.550 align:start position:0% if only in the case we are behaving<00:06:23.939> badly<00:06:24.090> you've<00:06:24.569> gone<00:06:24.720> to<00:06:25.080> a<00:06:25.110> fair<00:06:25.349> one 00:06:25.550 --> 00:06:25.560 align:start position:0% behaving badly you've gone to a fair one 00:06:25.560 --> 00:06:29.659 align:start position:0% behaving badly you've gone to a fair one and<00:06:26.960> site<00:06:27.960> change<00:06:28.319> maybe<00:06:28.860> you<00:06:29.069> have<00:06:29.220> heard<00:06:29.490> of 00:06:29.659 --> 00:06:29.669 align:start position:0% and site change maybe you have heard of 00:06:29.669 --> 00:06:31.969 align:start position:0% and site change maybe you have heard of this<00:06:29.789> things<00:06:30.120> tide<00:06:30.449> change<00:06:30.750> are<00:06:31.319> not<00:06:31.379> they<00:06:31.740> do 00:06:31.969 --> 00:06:31.979 align:start position:0% this things tide change are not they do 00:06:31.979 --> 00:06:34.520 align:start position:0% this things tide change are not they do we'll<00:06:32.310> talk<00:06:32.639> about<00:06:32.759> that<00:06:33.030> is<00:06:33.300> basically<00:06:34.199> an 00:06:34.520 --> 00:06:34.530 align:start position:0% we'll talk about that is basically an 00:06:34.530 --> 00:06:37.490 align:start position:0% we'll talk about that is basically an atomic<00:06:35.400> well<00:06:35.639> swap<00:06:36.120> between<00:06:36.300> two<00:06:36.840> different 00:06:37.490 --> 00:06:37.500 align:start position:0% atomic well swap between two different 00:06:37.500 --> 00:06:39.559 align:start position:0% atomic well swap between two different chains<00:06:38.009> so<00:06:38.340> there's<00:06:38.550> a<00:06:38.639> few<00:06:38.879> more<00:06:39.120> Bitcoin 00:06:39.559 --> 00:06:39.569 align:start position:0% chains so there's a few more Bitcoin 00:06:39.569 --> 00:06:41.869 align:start position:0% chains so there's a few more Bitcoin whatever<00:06:40.020> we<00:06:40.590> the<00:06:40.949> public<00:06:41.250> ones<00:06:41.460> open 00:06:41.869 --> 00:06:41.879 align:start position:0% whatever we the public ones open 00:06:41.879 --> 00:06:44.119 align:start position:0% whatever we the public ones open and<00:06:42.090> it's<00:06:42.270> minted<00:06:42.810> on<00:06:42.930> the<00:06:43.050> other<00:06:43.169> side<00:06:43.469> but 00:06:44.119 --> 00:06:44.129 align:start position:0% and it's minted on the other side but 00:06:44.129 --> 00:06:45.980 align:start position:0% and it's minted on the other side but I'm<00:06:44.939> not<00:06:45.120> going<00:06:45.300> to<00:06:45.389> talk<00:06:45.539> about<00:06:45.569> this<00:06:45.840> because 00:06:45.980 --> 00:06:45.990 align:start position:0% I'm not going to talk about this because 00:06:45.990 --> 00:06:48.110 align:start position:0% I'm not going to talk about this because the<00:06:46.349> side<00:06:46.620> chains<00:06:46.830> are<00:06:47.039> not<00:06:47.159> layered<00:06:47.819> to<00:06:47.939> and 00:06:48.110 --> 00:06:48.120 align:start position:0% the side chains are not layered to and 00:06:48.120 --> 00:06:49.670 align:start position:0% the side chains are not layered to and actually<00:06:48.240> right<00:06:48.689> now<00:06:48.840> there's<00:06:49.080> another<00:06:49.379> talk 00:06:49.670 --> 00:06:49.680 align:start position:0% actually right now there's another talk 00:06:49.680 --> 00:06:51.830 align:start position:0% actually right now there's another talk somewhere<00:06:50.099> downstairs<00:06:50.610> exactly<00:06:51.360> about<00:06:51.689> this 00:06:51.830 --> 00:06:51.840 align:start position:0% somewhere downstairs exactly about this 00:06:51.840 --> 00:06:56.149 align:start position:0% somewhere downstairs exactly about this site<00:06:52.169> no<00:06:52.439> site<00:06:53.159> is<00:06:53.520> really<00:06:54.469> so<00:06:55.469> if<00:06:55.800> you<00:06:55.919> hear 00:06:56.149 --> 00:06:56.159 align:start position:0% site no site is really so if you hear 00:06:56.159 --> 00:07:00.459 align:start position:0% site no site is really so if you hear sightings<00:06:57.000> are<00:06:57.210> nothing<00:06:57.629> to<00:06:57.810> and<00:06:58.789> okay 00:07:00.459 --> 00:07:00.469 align:start position:0% sightings are nothing to and okay 00:07:00.469 --> 00:07:04.850 align:start position:0% sightings are nothing to and okay basically<00:07:01.469> to<00:07:01.620> speed<00:07:02.039> up<00:07:03.020> we<00:07:04.020> did<00:07:04.229> interview 00:07:04.850 --> 00:07:04.860 align:start position:0% basically to speed up we did interview 00:07:04.860 --> 00:07:09.379 align:start position:0% basically to speed up we did interview people<00:07:05.370> in<00:07:05.729> the<00:07:05.849> space<00:07:06.120> and<00:07:06.680> users<00:07:07.710> I<00:07:07.889> want<00:07:08.550> my 00:07:09.379 --> 00:07:09.389 align:start position:0% people in the space and users I want my 00:07:09.389 --> 00:07:11.029 align:start position:0% people in the space and users I want my mission<00:07:09.719> is<00:07:09.840> to<00:07:09.870> unboard<00:07:10.349> my<00:07:10.560> mother<00:07:10.740> and<00:07:10.979> my 00:07:11.029 --> 00:07:11.039 align:start position:0% mission is to unboard my mother and my 00:07:11.039 --> 00:07:13.540 align:start position:0% mission is to unboard my mother and my brother<00:07:11.250> okay<00:07:11.759> and<00:07:11.940> so<00:07:12.449> I<00:07:12.479> try<00:07:12.840> to<00:07:12.870> talk<00:07:13.199> to 00:07:13.540 --> 00:07:13.550 align:start position:0% brother okay and so I try to talk to 00:07:13.550 --> 00:07:17.570 align:start position:0% brother okay and so I try to talk to non-critical<00:07:14.550> users<00:07:14.909> only<00:07:15.949> few<00:07:16.949> of<00:07:17.009> them<00:07:17.340> five 00:07:17.570 --> 00:07:17.580 align:start position:0% non-critical users only few of them five 00:07:17.580 --> 00:07:20.689 align:start position:0% non-critical users only few of them five of<00:07:17.729> them<00:07:17.879> because<00:07:18.539> there<00:07:19.169> wasn't<00:07:19.919> much<00:07:20.219> time 00:07:20.689 --> 00:07:20.699 align:start position:0% of them because there wasn't much time 00:07:20.699 --> 00:07:23.089 align:start position:0% of them because there wasn't much time with<00:07:21.180> people<00:07:21.449> releasing<00:07:22.439> stuff<00:07:22.620> right<00:07:22.919> before 00:07:23.089 --> 00:07:23.099 align:start position:0% with people releasing stuff right before 00:07:23.099 --> 00:07:24.649 align:start position:0% with people releasing stuff right before they're<00:07:23.430> going<00:07:23.669> to<00:07:23.759> actually<00:07:23.969> have<00:07:24.300> something 00:07:24.649 --> 00:07:24.659 align:start position:0% they're going to actually have something 00:07:24.659 --> 00:07:27.709 align:start position:0% they're going to actually have something in<00:07:25.110> our<00:07:25.349> hands<00:07:25.590> to<00:07:25.860> touch<00:07:26.069> with<00:07:26.340> there's<00:07:26.969> three 00:07:27.709 --> 00:07:27.719 align:start position:0% in our hands to touch with there's three 00:07:27.719 --> 00:07:30.529 align:start position:0% in our hands to touch with there's three main<00:07:28.020> moments<00:07:28.590> in<00:07:28.800> the<00:07:29.400> design<00:07:29.789> or<00:07:29.819> the<00:07:30.180> user 00:07:30.529 --> 00:07:30.539 align:start position:0% main moments in the design or the user 00:07:30.539 --> 00:07:33.320 align:start position:0% main moments in the design or the user flow<00:07:30.810> okay<00:07:31.259> you<00:07:31.319> need<00:07:31.680> to<00:07:31.800> enter<00:07:32.250> this<00:07:32.490> you 00:07:33.320 --> 00:07:33.330 align:start position:0% flow okay you need to enter this you 00:07:33.330 --> 00:07:35.149 align:start position:0% flow okay you need to enter this you need<00:07:33.479> to<00:07:33.599> use<00:07:33.810> the<00:07:34.050> system<00:07:34.379> and<00:07:34.469> exit<00:07:35.009> the 00:07:35.149 --> 00:07:35.159 align:start position:0% need to use the system and exit the 00:07:35.159 --> 00:07:38.959 align:start position:0% need to use the system and exit the system<00:07:35.370> and<00:07:35.759> in<00:07:36.569> these<00:07:36.930> two<00:07:37.139> cases<00:07:37.639> you<00:07:38.639> also 00:07:38.959 --> 00:07:38.969 align:start position:0% system and in these two cases you also 00:07:38.969 --> 00:07:42.920 align:start position:0% system and in these two cases you also have<00:07:39.889> to<00:07:40.889> sign<00:07:41.339> things<00:07:41.699> which<00:07:41.969> is<00:07:42.120> normally 00:07:42.920 --> 00:07:42.930 align:start position:0% have to sign things which is normally 00:07:42.930 --> 00:07:44.839 align:start position:0% have to sign things which is normally you<00:07:43.199> will<00:07:43.379> think<00:07:43.589> of<00:07:43.650> transactions<00:07:44.520> but 00:07:44.839 --> 00:07:44.849 align:start position:0% you will think of transactions but 00:07:44.849 --> 00:07:48.079 align:start position:0% you will think of transactions but transactions<00:07:45.719> are<00:07:45.900> is<00:07:46.080> a<00:07:46.110> pattern<00:07:46.740> that<00:07:47.089> works 00:07:48.079 --> 00:07:48.089 align:start position:0% transactions are is a pattern that works 00:07:48.089 --> 00:07:51.469 align:start position:0% transactions are is a pattern that works inside<00:07:48.539> of<00:07:49.110> a<00:07:49.589> wallet<00:07:50.219> or<00:07:50.460> when<00:07:50.969> you<00:07:51.060> transact 00:07:51.469 --> 00:07:51.479 align:start position:0% inside of a wallet or when you transact 00:07:51.479 --> 00:07:53.300 align:start position:0% inside of a wallet or when you transact value<00:07:51.930> but<00:07:52.110> in<00:07:52.229> this<00:07:52.379> cases<00:07:52.620> you<00:07:52.949> can<00:07:53.129> also 00:07:53.300 --> 00:07:53.310 align:start position:0% value but in this cases you can also 00:07:53.310 --> 00:07:56.409 align:start position:0% value but in this cases you can also transact<00:07:53.849> stage<00:07:54.479> of<00:07:54.870> applications<00:07:55.710> you<00:07:55.830> know 00:07:56.409 --> 00:07:56.419 align:start position:0% transact stage of applications you know 00:07:56.419 --> 00:07:59.450 align:start position:0% transact stage of applications you know so<00:07:57.419> you<00:07:57.479> should<00:07:58.110> not<00:07:58.229> call<00:07:58.500> them<00:07:58.680> transactions 00:07:59.450 --> 00:07:59.460 align:start position:0% so you should not call them transactions 00:07:59.460 --> 00:08:03.050 align:start position:0% so you should not call them transactions if<00:08:00.029> you<00:08:00.210> want<00:08:00.479> and<00:08:00.830> the<00:08:01.830> exit<00:08:02.339> has<00:08:02.610> two 00:08:03.050 --> 00:08:03.060 align:start position:0% if you want and the exit has two 00:08:03.060 --> 00:08:05.600 align:start position:0% if you want and the exit has two patterns<00:08:03.690> which<00:08:03.870> is<00:08:04.080> I'm<00:08:04.469> exiting<00:08:05.039> fine<00:08:05.370> and 00:08:05.600 --> 00:08:05.610 align:start position:0% patterns which is I'm exiting fine and 00:08:05.610 --> 00:08:07.790 align:start position:0% patterns which is I'm exiting fine and friends<00:08:05.969> with<00:08:06.120> my<00:08:06.270> friend<00:08:06.930> and<00:08:07.169> I<00:08:07.289> just<00:08:07.319> go 00:08:07.790 --> 00:08:07.800 align:start position:0% friends with my friend and I just go 00:08:07.800 --> 00:08:10.670 align:start position:0% friends with my friend and I just go fine<00:08:08.069> or<00:08:08.310> adversarial<00:08:09.089> and<00:08:09.589> entering<00:08:10.589> the 00:08:10.670 --> 00:08:10.680 align:start position:0% fine or adversarial and entering the 00:08:10.680 --> 00:08:11.059 align:start position:0% fine or adversarial and entering the system 00:08:11.059 --> 00:08:11.069 align:start position:0% system 00:08:11.069 --> 00:08:14.749 align:start position:0% system so<00:08:12.029> unfortunately<00:08:12.949> today<00:08:13.949> this<00:08:14.159> is<00:08:14.310> a<00:08:14.339> problem 00:08:14.749 --> 00:08:14.759 align:start position:0% so unfortunately today this is a problem 00:08:14.759 --> 00:08:16.939 align:start position:0% so unfortunately today this is a problem you<00:08:15.210> still<00:08:15.599> need<00:08:15.960> to<00:08:16.139> go<00:08:16.349> through<00:08:16.379> then<00:08:16.860> you 00:08:16.939 --> 00:08:16.949 align:start position:0% you still need to go through then you 00:08:16.949 --> 00:08:19.360 align:start position:0% you still need to go through then you want<00:08:17.219> to<00:08:17.580> get<00:08:17.789> into<00:08:18.060> later<00:08:18.300> too<00:08:18.599> and<00:08:18.990> so 00:08:19.360 --> 00:08:19.370 align:start position:0% want to get into later too and so 00:08:19.370 --> 00:08:20.540 align:start position:0% want to get into later too and so everybody 00:08:20.540 --> 00:08:20.550 align:start position:0% everybody 00:08:20.550 --> 00:08:25.310 align:start position:0% everybody still<00:08:20.700> presenting<00:08:22.010> with<00:08:23.010> a<00:08:23.630> savior<00:08:24.630> key<00:08:24.870> but 00:08:25.310 --> 00:08:25.320 align:start position:0% still presenting with a savior key but 00:08:25.320 --> 00:08:28.910 align:start position:0% still presenting with a savior key but Capulets<00:08:26.220> of<00:08:26.490> my<00:08:26.970> dream<00:08:27.390> was<00:08:27.990> shattered<00:08:28.290> right 00:08:28.910 --> 00:08:28.920 align:start position:0% Capulets of my dream was shattered right 00:08:28.920 --> 00:08:31.340 align:start position:0% Capulets of my dream was shattered right of<00:08:29.100> the<00:08:29.190> first<00:08:29.430> stab<00:08:29.730> you<00:08:29.850> know<00:08:30.000> yes<00:08:30.690> we<00:08:31.020> can<00:08:31.200> on 00:08:31.340 --> 00:08:31.350 align:start position:0% of the first stab you know yes we can on 00:08:31.350 --> 00:08:34.660 align:start position:0% of the first stab you know yes we can on board<00:08:31.560> non<00:08:31.830> proof<00:08:32.130> to<00:08:32.250> use<00:08:32.400> it<00:08:32.580> no<00:08:32.820> not<00:08:33.210> yet<00:08:33.450> and 00:08:34.660 --> 00:08:34.670 align:start position:0% board non proof to use it no not yet and 00:08:34.670 --> 00:08:37.610 align:start position:0% board non proof to use it no not yet and of<00:08:35.670> course<00:08:35.970> their<00:08:36.210> solution<00:08:36.720> for<00:08:36.870> this<00:08:37.020> of 00:08:37.610 --> 00:08:37.620 align:start position:0% of course their solution for this of 00:08:37.620 --> 00:08:39.230 align:start position:0% of course their solution for this of course<00:08:37.920> the<00:08:38.040> question<00:08:38.340> is<00:08:38.490> what<00:08:38.940> the<00:08:39.030> is 00:08:39.230 --> 00:08:39.240 align:start position:0% course the question is what the is 00:08:39.240 --> 00:08:42.200 align:start position:0% course the question is what the is a<00:08:39.330> key<00:08:39.510> ok<00:08:40.020> this<00:08:40.170> is<00:08:40.350> a<00:08:40.440> literal<00:08:40.980> question<00:08:41.490> use 00:08:42.200 --> 00:08:42.210 align:start position:0% a key ok this is a literal question use 00:08:42.210 --> 00:08:46.670 align:start position:0% a key ok this is a literal question use of<00:08:42.390> us<00:08:42.570> and<00:08:44.300> this<00:08:45.300> solution<00:08:45.450> is<00:08:45.810> of<00:08:45.960> course<00:08:46.230> to 00:08:46.670 --> 00:08:46.680 align:start position:0% of us and this solution is of course to 00:08:46.680 --> 00:08:48.920 align:start position:0% of us and this solution is of course to use<00:08:46.760> contract<00:08:47.760> base<00:08:47.940> account<00:08:48.210> the<00:08:48.390> universal 00:08:48.920 --> 00:08:48.930 align:start position:0% use contract base account the universal 00:08:48.930 --> 00:08:50.990 align:start position:0% use contract base account the universal of<00:08:49.050> you<00:08:49.200> might<00:08:49.560> have<00:08:49.680> heard<00:08:49.920> those<00:08:50.280> those 00:08:50.990 --> 00:08:51.000 align:start position:0% of you might have heard those those 00:08:51.000 --> 00:08:54.350 align:start position:0% of you might have heard those those solve<00:08:51.720> that<00:08:52.560> onboarding<00:08:53.370> process<00:08:53.910> please 00:08:54.350 --> 00:08:54.360 align:start position:0% solve that onboarding process please 00:08:54.360 --> 00:08:56.300 align:start position:0% solve that onboarding process please start<00:08:54.720> using<00:08:54.930> contract<00:08:55.740> base<00:08:55.920> accounts 00:08:56.300 --> 00:08:56.310 align:start position:0% start using contract base accounts 00:08:56.310 --> 00:08:58.910 align:start position:0% start using contract base accounts everybody<00:08:56.870> then<00:08:57.870> there<00:08:58.410> are<00:08:58.500> so<00:08:58.680> many 00:08:58.910 --> 00:08:58.920 align:start position:0% everybody then there are so many 00:08:58.920 --> 00:09:00.920 align:start position:0% everybody then there are so many accounts<00:08:59.640> in<00:08:59.760> some<00:08:59.940> cases<00:09:00.180> you<00:09:00.480> need<00:09:00.630> to<00:09:00.780> have 00:09:00.920 --> 00:09:00.930 align:start position:0% accounts in some cases you need to have 00:09:00.930 --> 00:09:02.860 align:start position:0% accounts in some cases you need to have your<00:09:01.140> a<00:09:01.200> theorem<00:09:01.710> key<00:09:02.010> or<00:09:02.250> your<00:09:02.580> normal 00:09:02.860 --> 00:09:02.870 align:start position:0% your a theorem key or your normal 00:09:02.870 --> 00:09:05.300 align:start position:0% your a theorem key or your normal theorem<00:09:03.870> will<00:09:04.050> have<00:09:04.200> been<00:09:04.440> a<00:09:04.470> contract<00:09:05.130> base 00:09:05.300 --> 00:09:05.310 align:start position:0% theorem will have been a contract base 00:09:05.310 --> 00:09:06.740 align:start position:0% theorem will have been a contract base account<00:09:05.580> and<00:09:05.850> in<00:09:05.940> some<00:09:06.120> cases<00:09:06.330> you<00:09:06.510> need<00:09:06.600> to 00:09:06.740 --> 00:09:06.750 align:start position:0% account and in some cases you need to 00:09:06.750 --> 00:09:09.400 align:start position:0% account and in some cases you need to have<00:09:06.900> your<00:09:07.050> own<00:09:07.280> peeler<00:09:08.280> alert<00:09:08.640> your<00:09:09.090> own 00:09:09.400 --> 00:09:09.410 align:start position:0% have your own peeler alert your own 00:09:09.410 --> 00:09:12.230 align:start position:0% have your own peeler alert your own sidechain<00:09:10.410> stylist<00:09:11.070> is<00:09:11.280> the<00:09:11.580> state<00:09:11.820> channel 00:09:12.230 --> 00:09:12.240 align:start position:0% sidechain stylist is the state channel 00:09:12.240 --> 00:09:15.260 align:start position:0% sidechain stylist is the state channel or<00:09:12.510> plasma<00:09:13.050> car<00:09:13.680> like<00:09:14.400> if<00:09:14.550> it<00:09:14.760> was<00:09:14.910> a<00:09:14.940> bank 00:09:15.260 --> 00:09:15.270 align:start position:0% or plasma car like if it was a bank 00:09:15.270 --> 00:09:17.360 align:start position:0% or plasma car like if it was a bank account<00:09:15.630> if<00:09:15.900> you<00:09:15.990> want<00:09:16.020> so<00:09:16.380> these<00:09:16.800> are<00:09:17.130> like 00:09:17.360 --> 00:09:17.370 align:start position:0% account if you want so these are like 00:09:17.370 --> 00:09:19.700 align:start position:0% account if you want so these are like three<00:09:17.400> wellnitz<00:09:18.180> and<00:09:18.390> people<00:09:19.050> of<00:09:19.170> course<00:09:19.410> ask 00:09:19.700 --> 00:09:19.710 align:start position:0% three wellnitz and people of course ask 00:09:19.710 --> 00:09:23.030 align:start position:0% three wellnitz and people of course ask why<00:09:20.670> do<00:09:20.730> we<00:09:20.970> need<00:09:21.090> another<00:09:21.150> one<00:09:21.590> no<00:09:22.590> seriously 00:09:23.030 --> 00:09:23.040 align:start position:0% why do we need another one no seriously 00:09:23.040 --> 00:09:24.920 align:start position:0% why do we need another one no seriously why<00:09:23.430> do<00:09:23.490> I<00:09:23.640> need<00:09:23.760> another<00:09:24.000> volunteer<00:09:24.150> repeat 00:09:24.920 --> 00:09:24.930 align:start position:0% why do I need another volunteer repeat 00:09:24.930 --> 00:09:26.420 align:start position:0% why do I need another volunteer repeat this<00:09:25.170> thing<00:09:25.380> they<00:09:25.620> know<00:09:25.830> they<00:09:26.010> have<00:09:26.040> to<00:09:26.310> do 00:09:26.420 --> 00:09:26.430 align:start position:0% this thing they know they have to do 00:09:26.430 --> 00:09:28.190 align:start position:0% this thing they know they have to do this<00:09:26.610> yet<00:09:26.850> but<00:09:27.000> they<00:09:27.120> don't<00:09:27.540> grasp<00:09:27.930> the 00:09:28.190 --> 00:09:28.200 align:start position:0% this yet but they don't grasp the 00:09:28.200 --> 00:09:30.410 align:start position:0% this yet but they don't grasp the meaning<00:09:28.380> and<00:09:28.800> Wallis<00:09:29.520> to<00:09:29.730> date<00:09:29.910> and<00:09:30.120> make<00:09:30.270> the 00:09:30.410 --> 00:09:30.420 align:start position:0% meaning and Wallis to date and make the 00:09:30.420 --> 00:09:32.330 align:start position:0% meaning and Wallis to date and make the effort<00:09:30.510> to<00:09:30.690> explain<00:09:31.080> what<00:09:31.770> are<00:09:31.920> these<00:09:32.100> things 00:09:32.330 --> 00:09:32.340 align:start position:0% effort to explain what are these things 00:09:32.340 --> 00:09:36.740 align:start position:0% effort to explain what are these things and<00:09:33.090> of<00:09:34.050> course<00:09:34.410> if<00:09:34.770> you<00:09:34.950> can<00:09:35.160> just<00:09:36.120> pour<00:09:36.570> them 00:09:36.740 --> 00:09:36.750 align:start position:0% and of course if you can just pour them 00:09:36.750 --> 00:09:38.750 align:start position:0% and of course if you can just pour them directly<00:09:37.260> here<00:09:37.710> obstructing<00:09:38.520> this 00:09:38.750 --> 00:09:38.760 align:start position:0% directly here obstructing this 00:09:38.760 --> 00:09:41.690 align:start position:0% directly here obstructing this information<00:09:39.510> and<00:09:39.900> getting<00:09:40.830> them<00:09:41.220> directly 00:09:41.690 --> 00:09:41.700 align:start position:0% information and getting them directly 00:09:41.700 --> 00:09:44.570 align:start position:0% information and getting them directly onto<00:09:41.970> later<00:09:42.810> too<00:09:42.990> if<00:09:43.110> you<00:09:43.200> want<00:09:43.380> or<00:09:43.650> explain<00:09:44.310> if 00:09:44.570 --> 00:09:44.580 align:start position:0% onto later too if you want or explain if 00:09:44.580 --> 00:09:47.060 align:start position:0% onto later too if you want or explain if you<00:09:44.670> want<00:09:44.970> what<00:09:45.390> is<00:09:45.630> one<00:09:46.020> wallet<00:09:46.380> why<00:09:46.650> doing<00:09:46.950> it 00:09:47.060 --> 00:09:47.070 align:start position:0% you want what is one wallet why doing it 00:09:47.070 --> 00:09:47.720 align:start position:0% you want what is one wallet why doing it another<00:09:47.280> wallet 00:09:47.720 --> 00:09:47.730 align:start position:0% another wallet 00:09:47.730 --> 00:09:51.530 align:start position:0% another wallet etc<00:09:48.530> Vika<00:09:49.530> token<00:09:49.920> this<00:09:50.610> is<00:09:50.760> a<00:09:50.790> problem<00:09:51.210> state 00:09:51.530 --> 00:09:51.540 align:start position:0% etc Vika token this is a problem state 00:09:51.540 --> 00:09:53.360 align:start position:0% etc Vika token this is a problem state channels<00:09:51.960> and<00:09:52.200> all<00:09:52.290> the<00:09:52.410> plasma<00:09:52.830> say<00:09:53.010> hey<00:09:53.310> you 00:09:53.360 --> 00:09:53.370 align:start position:0% channels and all the plasma say hey you 00:09:53.370 --> 00:09:55.880 align:start position:0% channels and all the plasma say hey you can<00:09:53.820> onboard<00:09:54.330> with<00:09:54.540> any<00:09:54.660> token<00:09:55.110> deposit<00:09:55.740> any 00:09:55.880 --> 00:09:55.890 align:start position:0% can onboard with any token deposit any 00:09:55.890 --> 00:09:58.250 align:start position:0% can onboard with any token deposit any token<00:09:56.280> so<00:09:56.490> a<00:09:56.850> new<00:09:57.030> user<00:09:57.300> goes<00:09:57.630> there<00:09:57.900> and<00:09:58.080> see 00:09:58.250 --> 00:09:58.260 align:start position:0% token so a new user goes there and see 00:09:58.260 --> 00:10:00.290 align:start position:0% token so a new user goes there and see that<00:09:58.290> which<00:09:58.680> one<00:09:58.890> do<00:09:58.980> I<00:09:59.040> choose<00:09:59.070> and<00:09:59.970> there<00:10:00.210> is 00:10:00.290 --> 00:10:00.300 align:start position:0% that which one do I choose and there is 00:10:00.300 --> 00:10:02.570 align:start position:0% that which one do I choose and there is a<00:10:00.330> lot<00:10:00.630> of<00:10:00.840> things<00:10:01.320> with<00:10:01.530> all<00:10:01.680> the<00:10:01.710> easy<00:10:01.980> easy 00:10:02.570 --> 00:10:02.580 align:start position:0% a lot of things with all the easy easy 00:10:02.580 --> 00:10:04.820 align:start position:0% a lot of things with all the easy easy and<00:10:03.570> this<00:10:03.780> is<00:10:03.900> one<00:10:04.080> of<00:10:04.200> the<00:10:04.260> questions<00:10:04.560> we<00:10:04.650> have 00:10:04.820 --> 00:10:04.830 align:start position:0% and this is one of the questions we have 00:10:04.830 --> 00:10:06.380 align:start position:0% and this is one of the questions we have like<00:10:05.070> which<00:10:05.610> one<00:10:05.850> do<00:10:06.000> I<00:10:06.060> take 00:10:06.380 --> 00:10:06.390 align:start position:0% like which one do I take 00:10:06.390 --> 00:10:09.020 align:start position:0% like which one do I take you<00:10:06.600> know<00:10:07.220> well<00:10:08.220> what<00:10:08.460> the<00:10:08.700> is<00:10:08.820> a<00:10:08.880> token 00:10:09.020 --> 00:10:09.030 align:start position:0% you know well what the is a token 00:10:09.030 --> 00:10:10.319 align:start position:0% you know well what the is a token also<00:10:09.540> is<00:10:09.690> the<00:10:09.930> one 00:10:10.319 --> 00:10:10.329 align:start position:0% also is the one 00:10:10.329 --> 00:10:12.869 align:start position:0% also is the one questions<00:10:10.779> and<00:10:11.399> which<00:10:12.399> one<00:10:12.579> should<00:10:12.610> I<00:10:12.850> pick 00:10:12.869 --> 00:10:12.879 align:start position:0% questions and which one should I pick 00:10:12.879 --> 00:10:16.859 align:start position:0% questions and which one should I pick and<00:10:14.429> what<00:10:15.429> am<00:10:15.519> I<00:10:15.639> paying<00:10:15.819> this<00:10:15.970> tube<00:10:16.360> yeah<00:10:16.629> so 00:10:16.859 --> 00:10:16.869 align:start position:0% and what am I paying this tube yeah so 00:10:16.869 --> 00:10:19.169 align:start position:0% and what am I paying this tube yeah so they<00:10:17.079> have<00:10:17.319> no<00:10:17.589> clue<00:10:17.860> of<00:10:17.889> why<00:10:18.339> you<00:10:18.399> have<00:10:18.910> to<00:10:19.029> die 00:10:19.169 --> 00:10:19.179 align:start position:0% they have no clue of why you have to die 00:10:19.179 --> 00:10:20.939 align:start position:0% they have no clue of why you have to die doing<00:10:19.389> this<00:10:19.509> and<00:10:19.989> white<00:10:20.319> or<00:10:20.529> everybody 00:10:20.939 --> 00:10:20.949 align:start position:0% doing this and white or everybody 00:10:20.949 --> 00:10:24.090 align:start position:0% doing this and white or everybody confusing<00:10:21.610> with<00:10:21.699> wallets<00:10:22.059> so<00:10:22.739> pattern<00:10:23.739> here 00:10:24.090 --> 00:10:24.100 align:start position:0% confusing with wallets so pattern here 00:10:24.100 --> 00:10:27.689 align:start position:0% confusing with wallets so pattern here is<00:10:24.129> game<00:10:24.910> of<00:10:25.089> tonality<00:10:26.160> new<00:10:27.160> users 00:10:27.689 --> 00:10:27.699 align:start position:0% is game of tonality new users 00:10:27.699 --> 00:10:30.660 align:start position:0% is game of tonality new users simplifying<00:10:28.360> just<00:10:28.720> one<00:10:29.049> option<00:10:29.259> maybe<00:10:30.040> die<00:10:30.279> or 00:10:30.660 --> 00:10:30.670 align:start position:0% simplifying just one option maybe die or 00:10:30.670 --> 00:10:33.600 align:start position:0% simplifying just one option maybe die or whatever<00:10:31.059> and<00:10:31.869> expert<00:10:32.589> the<00:10:32.709> s<00:10:32.829> you<00:10:33.009> can<00:10:33.189> expand 00:10:33.600 --> 00:10:33.610 align:start position:0% whatever and expert the s you can expand 00:10:33.610 --> 00:10:36.319 align:start position:0% whatever and expert the s you can expand and<00:10:33.759> chew<00:10:33.970> their<00:10:34.179> own<00:10:34.389> always<00:10:35.259> be<00:10:35.410> there<00:10:35.649> and 00:10:36.319 --> 00:10:36.329 align:start position:0% and chew their own always be there and 00:10:36.329 --> 00:10:39.989 align:start position:0% and chew their own always be there and options<00:10:37.329> until<00:10:37.660> exit<00:10:38.350> maybe<00:10:38.709> you<00:10:39.369> decide<00:10:39.850> when 00:10:39.989 --> 00:10:39.999 align:start position:0% options until exit maybe you decide when 00:10:39.999 --> 00:10:44.100 align:start position:0% options until exit maybe you decide when you<00:10:40.029> exit<00:10:41.970> and<00:10:42.970> explain<00:10:43.509> better<00:10:43.839> the 00:10:44.100 --> 00:10:44.110 align:start position:0% you exit and explain better the 00:10:44.110 --> 00:10:45.479 align:start position:0% you exit and explain better the difference<00:10:44.470> this<00:10:44.619> was<00:10:44.920> one<00:10:45.189> of<00:10:45.220> these 00:10:45.479 --> 00:10:45.489 align:start position:0% difference this was one of these 00:10:45.489 --> 00:10:47.970 align:start position:0% difference this was one of these solutions<00:10:45.730> from<00:10:46.569> the<00:10:46.689> previous<00:10:47.139> framework 00:10:47.970 --> 00:10:47.980 align:start position:0% solutions from the previous framework 00:10:47.980 --> 00:10:51.329 align:start position:0% solutions from the previous framework that<00:10:48.549> works<00:10:48.999> then<00:10:49.779> what's<00:10:50.290> your<00:10:50.410> language<00:10:51.040> is 00:10:51.329 --> 00:10:51.339 align:start position:0% that works then what's your language is 00:10:51.339 --> 00:10:53.039 align:start position:0% that works then what's your language is the<00:10:51.549> end<00:10:51.670> another<00:10:51.939> pattern<00:10:52.179> that<00:10:52.389> all<00:10:52.839> these 00:10:53.039 --> 00:10:53.049 align:start position:0% the end another pattern that all these 00:10:53.049 --> 00:10:56.579 align:start position:0% the end another pattern that all these people<00:10:53.499> start<00:10:54.100> using<00:10:54.879> developer<00:10:55.660> lingo<00:10:56.230> okay 00:10:56.579 --> 00:10:56.589 align:start position:0% people start using developer lingo okay 00:10:56.589 --> 00:10:59.030 align:start position:0% people start using developer lingo okay these<00:10:57.549> words<00:10:57.970> don't<00:10:58.149> mean<00:10:58.329> anything<00:10:58.480> and 00:10:59.030 --> 00:10:59.040 align:start position:0% these words don't mean anything and 00:10:59.040 --> 00:11:01.799 align:start position:0% these words don't mean anything and deploy<00:11:00.040> doesn't<00:11:00.610> mean<00:11:00.819> divide<00:11:01.239> this<00:11:01.629> is<00:11:01.779> a 00:11:01.799 --> 00:11:01.809 align:start position:0% deploy doesn't mean divide this is a 00:11:01.809 --> 00:11:05.009 align:start position:0% deploy doesn't mean divide this is a factual<00:11:02.199> question<00:11:02.499> user<00:11:03.249> had<00:11:03.610> so<00:11:04.239> floor 00:11:05.009 --> 00:11:05.019 align:start position:0% factual question user had so floor 00:11:05.019 --> 00:11:07.590 align:start position:0% factual question user had so floor legged<00:11:05.649> to<00:11:05.860> later<00:11:06.489> one<00:11:06.850> doesn't<00:11:07.449> mean 00:11:07.590 --> 00:11:07.600 align:start position:0% legged to later one doesn't mean 00:11:07.600 --> 00:11:09.900 align:start position:0% legged to later one doesn't mean anything<00:11:08.199> at<00:11:08.319> all<00:11:08.410> for<00:11:08.799> usual<00:11:09.670> so 00:11:09.900 --> 00:11:09.910 align:start position:0% anything at all for usual so 00:11:09.910 --> 00:11:12.179 align:start position:0% anything at all for usual so experimentally<00:11:10.509> -<00:11:11.290> yes<00:11:11.529> it's<00:11:11.739> experimental 00:11:12.179 --> 00:11:12.189 align:start position:0% experimentally - yes it's experimental 00:11:12.189 --> 00:11:15.030 align:start position:0% experimentally - yes it's experimental its<00:11:12.489> internal<00:11:12.879> for<00:11:13.029> us<00:11:13.149> but<00:11:13.360> not<00:11:13.689> good<00:11:13.989> for<00:11:14.040> non 00:11:15.030 --> 00:11:15.040 align:start position:0% its internal for us but not good for non 00:11:15.040 --> 00:11:18.090 align:start position:0% its internal for us but not good for non people<00:11:15.399> users<00:11:15.699> we<00:11:15.850> had<00:11:16.029> so<00:11:17.100> simplified 00:11:18.090 --> 00:11:18.100 align:start position:0% people users we had so simplified 00:11:18.100 --> 00:11:20.039 align:start position:0% people users we had so simplified language<00:11:18.309> hi<00:11:18.970> the<00:11:19.029> technical<00:11:19.629> complexity 00:11:20.039 --> 00:11:20.049 align:start position:0% language hi the technical complexity 00:11:20.049 --> 00:11:23.470 align:start position:0% language hi the technical complexity possible<00:11:20.679> which<00:11:21.009> was<00:11:21.220> a<00:11:21.249> solution 00:11:23.470 --> 00:11:23.480 align:start position:0% possible which was a solution 00:11:23.480 --> 00:11:25.960 align:start position:0% possible which was a solution then<00:11:23.870> using<00:11:24.530> the<00:11:24.650> system<00:11:24.980> you're<00:11:25.220> on<00:11:25.280> step<00:11:25.640> 2 00:11:25.960 --> 00:11:25.970 align:start position:0% then using the system you're on step 2 00:11:25.970 --> 00:11:31.300 align:start position:0% then using the system you're on step 2 and<00:11:27.730> right<00:11:28.730> now<00:11:28.970> this<00:11:29.630> is<00:11:29.870> not<00:11:30.170> a<00:11:30.200> diet<00:11:30.590> okay 00:11:31.300 --> 00:11:31.310 align:start position:0% and right now this is not a diet okay 00:11:31.310 --> 00:11:34.330 align:start position:0% and right now this is not a diet okay this<00:11:31.520> is<00:11:31.670> one<00:11:31.850> of<00:11:31.970> the<00:11:32.120> biggest<00:11:33.070> insights<00:11:34.070> if 00:11:34.330 --> 00:11:34.340 align:start position:0% this is one of the biggest insights if 00:11:34.340 --> 00:11:37.600 align:start position:0% this is one of the biggest insights if you<00:11:34.460> want<00:11:34.700> of<00:11:35.710> others<00:11:36.710> research<00:11:37.130> they<00:11:37.460> were 00:11:37.600 --> 00:11:37.610 align:start position:0% you want of others research they were 00:11:37.610 --> 00:11:41.290 align:start position:0% you want of others research they were very<00:11:38.210> confused<00:11:38.990> because<00:11:39.730> these<00:11:40.730> wallets 00:11:41.290 --> 00:11:41.300 align:start position:0% very confused because these wallets 00:11:41.300 --> 00:11:43.600 align:start position:0% very confused because these wallets there's<00:11:41.900> different<00:11:42.290> by<00:11:42.710> the<00:11:42.770> wallet<00:11:43.250> single 00:11:43.600 --> 00:11:43.610 align:start position:0% there's different by the wallet single 00:11:43.610 --> 00:11:46.750 align:start position:0% there's different by the wallet single state<00:11:43.880> channels<00:11:44.300> in<00:11:44.750> plasma<00:11:45.530> etc<00:11:46.130> they<00:11:46.460> all 00:11:46.750 --> 00:11:46.760 align:start position:0% state channels in plasma etc they all 00:11:46.760 --> 00:11:49.870 align:start position:0% state channels in plasma etc they all use<00:11:47.210> dye<00:11:47.690> but<00:11:48.530> when<00:11:48.740> you<00:11:48.860> are<00:11:49.040> inside<00:11:49.520> of<00:11:49.730> these 00:11:49.870 --> 00:11:49.880 align:start position:0% use dye but when you are inside of these 00:11:49.880 --> 00:11:54.790 align:start position:0% use dye but when you are inside of these networks<00:11:50.980> the<00:11:51.980> dye<00:11:52.280> of<00:11:52.730> network<00:11:53.360> one<00:11:53.690> is<00:11:54.080> not 00:11:54.790 --> 00:11:54.800 align:start position:0% networks the dye of network one is not 00:11:54.800 --> 00:11:57.640 align:start position:0% networks the dye of network one is not the<00:11:55.040> diode<00:11:55.520> network<00:11:55.970> two<00:11:56.180> is<00:11:56.600> not<00:11:56.990> the<00:11:57.200> dye<00:11:57.440> of 00:11:57.640 --> 00:11:57.650 align:start position:0% the diode network two is not the dye of 00:11:57.650 --> 00:12:00.640 align:start position:0% the diode network two is not the dye of the<00:11:57.950> main<00:11:58.160> chain<00:11:58.640> so<00:11:59.270> my<00:11:59.930> user<00:12:00.170> is<00:12:00.410> actually 00:12:00.640 --> 00:12:00.650 align:start position:0% the main chain so my user is actually 00:12:00.650 --> 00:12:04.810 align:start position:0% the main chain so my user is actually trying<00:12:01.280> to<00:12:01.640> send<00:12:02.030> each<00:12:02.270> other<00:12:02.510> die<00:12:02.840> from<00:12:03.820> state 00:12:04.810 --> 00:12:04.820 align:start position:0% trying to send each other die from state 00:12:04.820 --> 00:12:09.640 align:start position:0% trying to send each other die from state channel<00:12:05.360> from<00:12:06.110> the<00:12:06.880> layer<00:12:07.880> one<00:12:08.330> wallet<00:12:08.900> or<00:12:09.230> to 00:12:09.640 --> 00:12:09.650 align:start position:0% channel from the layer one wallet or to 00:12:09.650 --> 00:12:13.120 align:start position:0% channel from the layer one wallet or to another<00:12:10.960> state<00:12:11.960> channel<00:12:12.290> wallet<00:12:12.890> and<00:12:13.010> they 00:12:13.120 --> 00:12:13.130 align:start position:0% another state channel wallet and they 00:12:13.130 --> 00:12:15.310 align:start position:0% another state channel wallet and they did<00:12:13.460> not<00:12:13.700> understand<00:12:14.150> why<00:12:14.510> we're<00:12:14.960> not<00:12:15.170> the 00:12:15.310 --> 00:12:15.320 align:start position:0% did not understand why we're not the 00:12:15.320 --> 00:12:17.340 align:start position:0% did not understand why we're not the same<00:12:15.470> diagram<00:12:15.830> there's<00:12:16.310> no<00:12:16.670> sign<00:12:16.970> whatsoever 00:12:17.340 --> 00:12:17.350 align:start position:0% same diagram there's no sign whatsoever 00:12:17.350 --> 00:12:21.130 align:start position:0% same diagram there's no sign whatsoever in<00:12:18.350> these<00:12:18.790> softwares<00:12:19.790> already<00:12:20.390> that<00:12:20.690> this<00:12:20.930> is 00:12:21.130 --> 00:12:21.140 align:start position:0% in these softwares already that this is 00:12:21.140 --> 00:12:24.880 align:start position:0% in these softwares already that this is a<00:12:21.170> custom<00:12:21.710> die<00:12:22.010> if<00:12:22.280> you<00:12:22.370> want<00:12:22.550> so<00:12:23.680> then<00:12:24.680> you<00:12:24.770> try 00:12:24.880 --> 00:12:24.890 align:start position:0% a custom die if you want so then you try 00:12:24.890 --> 00:12:27.460 align:start position:0% a custom die if you want so then you try to<00:12:24.980> send<00:12:25.250> it<00:12:25.370> to<00:12:25.580> a<00:12:25.640> friend<00:12:25.670> okay<00:12:26.360> this<00:12:27.170> is<00:12:27.320> one 00:12:27.460 --> 00:12:27.470 align:start position:0% to send it to a friend okay this is one 00:12:27.470 --> 00:12:29.650 align:start position:0% to send it to a friend okay this is one of<00:12:27.500> the<00:12:27.830> insights<00:12:28.700> that<00:12:28.790> we<00:12:28.970> are<00:12:29.060> multiplying 00:12:29.650 --> 00:12:29.660 align:start position:0% of the insights that we are multiplying 00:12:29.660 --> 00:12:31.740 align:start position:0% of the insights that we are multiplying the<00:12:29.840> complexity<00:12:30.440> not<00:12:30.800> simply<00:12:31.220> funny 00:12:31.740 --> 00:12:31.750 align:start position:0% the complexity not simply funny 00:12:31.750 --> 00:12:34.570 align:start position:0% the complexity not simply funny unfortunately<00:12:32.750> and<00:12:32.990> so<00:12:33.500> solutions<00:12:34.040> here<00:12:34.340> is 00:12:34.570 --> 00:12:34.580 align:start position:0% unfortunately and so solutions here is 00:12:34.580 --> 00:12:36.070 align:start position:0% unfortunately and so solutions here is of<00:12:34.790> course<00:12:34.820> like<00:12:35.630> God 00:12:36.070 --> 00:12:36.080 align:start position:0% of course like God 00:12:36.080 --> 00:12:38.800 align:start position:0% of course like God it<00:12:36.140> was<00:12:36.290> retaining<00:12:36.980> the<00:12:37.280> design<00:12:37.820> principles<00:12:38.570> a 00:12:38.800 --> 00:12:38.810 align:start position:0% it was retaining the design principles a 00:12:38.810 --> 00:12:41.890 align:start position:0% it was retaining the design principles a very<00:12:39.050> long<00:12:39.320> time<00:12:39.590> ago<00:12:39.940> define<00:12:40.940> now<00:12:41.390> explain 00:12:41.890 --> 00:12:41.900 align:start position:0% very long time ago define now explain 00:12:41.900 --> 00:12:45.160 align:start position:0% very long time ago define now explain what<00:12:42.590> the<00:12:43.040> network<00:12:43.580> you<00:12:44.030> are<00:12:44.270> using<00:12:44.480> you<00:12:45.020> need 00:12:45.160 --> 00:12:45.170 align:start position:0% what the network you are using you need 00:12:45.170 --> 00:12:48.190 align:start position:0% what the network you are using you need to<00:12:45.320> be<00:12:45.440> transparent<00:12:45.770> about<00:12:46.070> that<00:12:46.130> or<00:12:46.660> you<00:12:47.660> make 00:12:48.190 --> 00:12:48.200 align:start position:0% to be transparent about that or you make 00:12:48.200 --> 00:12:50.860 align:start position:0% to be transparent about that or you make it<00:12:48.400> interoperable<00:12:49.400> this<00:12:49.670> is<00:12:49.820> a<00:12:49.850> an<00:12:50.330> invitation 00:12:50.860 --> 00:12:50.870 align:start position:0% it interoperable this is a an invitation 00:12:50.870 --> 00:12:54.010 align:start position:0% it interoperable this is a an invitation for<00:12:51.020> all<00:12:51.170> the<00:12:51.350> layer<00:12:52.040> two<00:12:52.280> and<00:12:52.630> developers<00:12:53.630> to 00:12:54.010 --> 00:12:54.020 align:start position:0% for all the layer two and developers to 00:12:54.020 --> 00:12:56.920 align:start position:0% for all the layer two and developers to talk<00:12:54.620> together<00:12:54.830> and<00:12:55.190> say<00:12:55.670> hey<00:12:55.700> yes<00:12:56.390> we<00:12:56.750> can 00:12:56.920 --> 00:12:56.930 align:start position:0% talk together and say hey yes we can 00:12:56.930 --> 00:12:59.440 align:start position:0% talk together and say hey yes we can call<00:12:57.110> it<00:12:57.200> die<00:12:57.410> if<00:12:57.800> somebody<00:12:58.610> tries<00:12:58.880> to<00:12:59.060> send<00:12:59.330> it 00:12:59.440 --> 00:12:59.450 align:start position:0% call it die if somebody tries to send it 00:12:59.450 --> 00:13:00.310 align:start position:0% call it die if somebody tries to send it to<00:12:59.540> someone<00:12:59.900> else 00:13:00.310 --> 00:13:00.320 align:start position:0% to someone else 00:13:00.320 --> 00:13:02.440 align:start position:0% to someone else we<00:13:00.800> should<00:13:01.070> behind<00:13:01.610> the<00:13:01.700> curtains<00:13:02.090> be 00:13:02.440 --> 00:13:02.450 align:start position:0% we should behind the curtains be 00:13:02.450 --> 00:13:04.810 align:start position:0% we should behind the curtains be comforting<00:13:03.050> and<00:13:03.410> I'm<00:13:03.680> pouring<00:13:04.100> this<00:13:04.370> on<00:13:04.640> to 00:13:04.810 --> 00:13:04.820 align:start position:0% comforting and I'm pouring this on to 00:13:04.820 --> 00:13:07.900 align:start position:0% comforting and I'm pouring this on to the<00:13:04.850> other<00:13:05.120> network<00:13:05.930> and<00:13:06.860> more<00:13:07.100> work<00:13:07.670> together 00:13:07.900 --> 00:13:07.910 align:start position:0% the other network and more work together 00:13:07.910 --> 00:13:10.390 align:start position:0% the other network and more work together somehow<00:13:08.360> I'm<00:13:08.930> better<00:13:09.320> naming<00:13:09.740> of<00:13:10.010> course 00:13:10.390 --> 00:13:10.400 align:start position:0% somehow I'm better naming of course 00:13:10.400 --> 00:13:14.050 align:start position:0% somehow I'm better naming of course because<00:13:10.730> of<00:13:10.760> this<00:13:11.470> problem<00:13:12.580> here<00:13:13.580> the<00:13:13.820> many 00:13:14.050 --> 00:13:14.060 align:start position:0% because of this problem here the many 00:13:14.060 --> 00:13:17.980 align:start position:0% because of this problem here the many tokens<00:13:14.540> okay<00:13:16.210> maybe<00:13:17.210> they<00:13:17.420> should<00:13:17.600> be<00:13:17.720> called 00:13:17.980 --> 00:13:17.990 align:start position:0% tokens okay maybe they should be called 00:13:17.990 --> 00:13:21.640 align:start position:0% tokens okay maybe they should be called die<00:13:18.620> space<00:13:19.280> channel<00:13:19.490> once<00:13:19.820> I<00:13:20.300> plasma<00:13:21.020> one<00:13:21.230> and 00:13:21.640 --> 00:13:21.650 align:start position:0% die space channel once I plasma one and 00:13:21.650 --> 00:13:25.030 align:start position:0% die space channel once I plasma one and spectrum<00:13:22.100> I<00:13:22.280> saw<00:13:22.610> that<00:13:22.760> so<00:13:23.720> also<00:13:24.080> because<00:13:24.440> they 00:13:25.030 --> 00:13:25.040 align:start position:0% spectrum I saw that so also because they 00:13:25.040 --> 00:13:29.500 align:start position:0% spectrum I saw that so also because they could<00:13:25.280> find<00:13:25.670> each<00:13:25.940> other<00:13:26.270> better<00:13:28.240> so<00:13:29.240> this<00:13:29.360> is 00:13:29.500 --> 00:13:29.510 align:start position:0% could find each other better so this is 00:13:29.510 --> 00:13:30.740 align:start position:0% could find each other better so this is not<00:13:29.690> a<00:13:29.720> time 00:13:30.740 --> 00:13:30.750 align:start position:0% not a time 00:13:30.750 --> 00:13:33.139 align:start position:0% not a time what<00:13:31.290> else<00:13:31.680> multiple<00:13:32.310> transactions<00:13:32.850> this'll 00:13:33.139 --> 00:13:33.149 align:start position:0% what else multiple transactions this'll 00:13:33.149 --> 00:13:36.410 align:start position:0% what else multiple transactions this'll go<00:13:33.360> very<00:13:33.629> fast<00:13:33.870> away<00:13:34.910> there<00:13:35.910> is<00:13:35.939> a<00:13:36.060> the 00:13:36.410 --> 00:13:36.420 align:start position:0% go very fast away there is a the 00:13:36.420 --> 00:13:38.840 align:start position:0% go very fast away there is a the ideality<00:13:36.870> protections<00:13:37.620> go<00:13:37.829> very<00:13:38.100> fast<00:13:38.399> but<00:13:38.730> in 00:13:38.840 --> 00:13:38.850 align:start position:0% ideality protections go very fast but in 00:13:38.850 --> 00:13:43.069 align:start position:0% ideality protections go very fast but in the<00:13:39.029> case<00:13:39.329> of<00:13:39.980> plasma<00:13:41.120> you<00:13:42.120> still<00:13:42.449> need<00:13:42.899> to 00:13:43.069 --> 00:13:43.079 align:start position:0% the case of plasma you still need to 00:13:43.079 --> 00:13:45.470 align:start position:0% the case of plasma you still need to have<00:13:43.259> nonces<00:13:43.920> and<00:13:44.370> wait<00:13:44.730> for<00:13:45.029> a<00:13:45.060> transaction 00:13:45.470 --> 00:13:45.480 align:start position:0% have nonces and wait for a transaction 00:13:45.480 --> 00:13:49.639 align:start position:0% have nonces and wait for a transaction to<00:13:45.899> be<00:13:46.470> there<00:13:46.860> and<00:13:47.779> plasma<00:13:48.779> has<00:13:48.930> the<00:13:49.139> problem 00:13:49.639 --> 00:13:49.649 align:start position:0% to be there and plasma has the problem 00:13:49.649 --> 00:13:52.550 align:start position:0% to be there and plasma has the problem that<00:13:49.920> the<00:13:50.459> finality<00:13:51.120> of<00:13:51.149> that<00:13:51.899> transaction<00:13:52.259> is 00:13:52.550 --> 00:13:52.560 align:start position:0% that the finality of that transaction is 00:13:52.560 --> 00:13:54.800 align:start position:0% that the finality of that transaction is not<00:13:52.800> instant<00:13:53.220> in<00:13:53.310> say<00:13:53.490> channel<00:13:53.850> is<00:13:53.970> instant<00:13:54.389> as 00:13:54.800 --> 00:13:54.810 align:start position:0% not instant in say channel is instant as 00:13:54.810 --> 00:13:57.559 align:start position:0% not instant in say channel is instant as soon<00:13:55.019> as<00:13:55.139> you<00:13:55.259> receive<00:13:55.529> it<00:13:55.800> that's<00:13:56.250> it<00:13:56.569> in 00:13:57.559 --> 00:13:57.569 align:start position:0% soon as you receive it that's it in 00:13:57.569 --> 00:13:59.949 align:start position:0% soon as you receive it that's it in plasma<00:13:58.079> you<00:13:58.259> need<00:13:58.410> to<00:13:58.529> wait<00:13:58.800> that<00:13:59.370> this 00:13:59.949 --> 00:13:59.959 align:start position:0% plasma you need to wait that this 00:13:59.959 --> 00:14:02.600 align:start position:0% plasma you need to wait that this information<00:14:00.959> is<00:14:01.079> actually<00:14:01.290> put<00:14:01.920> the<00:14:02.160> 32 00:14:02.600 --> 00:14:02.610 align:start position:0% information is actually put the 32 00:14:02.610 --> 00:14:05.059 align:start position:0% information is actually put the 32 blocks<00:14:02.879> later<00:14:03.360> but<00:14:04.050> you<00:14:04.410> can<00:14:04.439> assume<00:14:05.040> that 00:14:05.059 --> 00:14:05.069 align:start position:0% blocks later but you can assume that 00:14:05.069 --> 00:14:07.579 align:start position:0% blocks later but you can assume that everything<00:14:05.670> but<00:14:06.660> there<00:14:06.810> is<00:14:06.899> that<00:14:07.050> problem<00:14:07.259> of 00:14:07.579 --> 00:14:07.589 align:start position:0% everything but there is that problem of 00:14:07.589 --> 00:14:09.949 align:start position:0% everything but there is that problem of timing<00:14:08.100> in<00:14:08.370> there<00:14:08.639> and<00:14:08.970> there's<00:14:09.569> a<00:14:09.629> new 00:14:09.949 --> 00:14:09.959 align:start position:0% timing in there and there's a new 00:14:09.959 --> 00:14:13.369 align:start position:0% timing in there and there's a new pattern<00:14:10.829> emerging<00:14:11.819> of<00:14:12.060> using<00:14:12.540> state<00:14:12.990> channels 00:14:13.369 --> 00:14:13.379 align:start position:0% pattern emerging of using state channels 00:14:13.379 --> 00:14:15.259 align:start position:0% pattern emerging of using state channels inside<00:14:13.829> plasma<00:14:14.279> channel<00:14:14.610> which<00:14:14.759> is<00:14:14.910> an<00:14:15.029> open 00:14:15.259 --> 00:14:15.269 align:start position:0% inside plasma channel which is an open 00:14:15.269 --> 00:14:17.780 align:start position:0% inside plasma channel which is an open question<00:14:15.360> how<00:14:16.019> that<00:14:16.230> works<00:14:16.529> although<00:14:16.980> we<00:14:17.519> work 00:14:17.780 --> 00:14:17.790 align:start position:0% question how that works although we work 00:14:17.790 --> 00:14:21.230 align:start position:0% question how that works although we work for<00:14:18.120> the<00:14:18.389> users<00:14:18.750> over<00:14:19.529> question<00:14:19.860> and<00:14:20.100> for<00:14:21.089> me 00:14:21.230 --> 00:14:21.240 align:start position:0% for the users over question and for me 00:14:21.240 --> 00:14:23.720 align:start position:0% for the users over question and for me personally<00:14:21.509> I<00:14:21.810> think<00:14:22.110> that<00:14:22.230> we<00:14:22.439> should<00:14:22.680> find<00:14:23.490> a 00:14:23.720 --> 00:14:23.730 align:start position:0% personally I think that we should find a 00:14:23.730 --> 00:14:24.829 align:start position:0% personally I think that we should find a technical<00:14:24.209> solution<00:14:24.329> to<00:14:24.689> overcome 00:14:24.829 --> 00:14:24.839 align:start position:0% technical solution to overcome 00:14:24.839 --> 00:14:27.710 align:start position:0% technical solution to overcome transaction<00:14:25.829> sequentiality<00:14:26.399> the<00:14:27.269> announcers 00:14:27.710 --> 00:14:27.720 align:start position:0% transaction sequentiality the announcers 00:14:27.720 --> 00:14:30.679 align:start position:0% transaction sequentiality the announcers have<00:14:27.899> confused<00:14:28.319> a<00:14:28.560> lot<00:14:28.829> of<00:14:29.040> users<00:14:29.459> that<00:14:29.689> they 00:14:30.679 --> 00:14:30.689 align:start position:0% have confused a lot of users that they 00:14:30.689 --> 00:14:32.329 align:start position:0% have confused a lot of users that they needed<00:14:30.899> to<00:14:31.079> wait<00:14:31.350> until<00:14:31.769> one<00:14:32.009> transaction 00:14:32.329 --> 00:14:32.339 align:start position:0% needed to wait until one transaction 00:14:32.339 --> 00:14:38.389 align:start position:0% needed to wait until one transaction came<00:14:32.759> back<00:14:33.029> or<00:14:33.389> that<00:14:34.050> has<00:14:34.879> passed<00:14:35.879> and<00:14:37.399> talk 00:14:38.389 --> 00:14:38.399 align:start position:0% came back or that has passed and talk 00:14:38.399 --> 00:14:41.420 align:start position:0% came back or that has passed and talk about<00:14:38.759> using<00:14:39.470> like<00:14:40.470> there's<00:14:40.740> generic 00:14:41.420 --> 00:14:41.430 align:start position:0% about using like there's generic 00:14:41.430 --> 00:14:44.240 align:start position:0% about using like there's generic problems<00:14:41.939> like<00:14:42.209> you<00:14:42.629> on<00:14:43.319> board<00:14:43.649> it<00:14:43.860> but<00:14:44.100> then 00:14:44.240 --> 00:14:44.250 align:start position:0% problems like you on board it but then 00:14:44.250 --> 00:14:46.100 align:start position:0% problems like you on board it but then you<00:14:44.430> don't<00:14:44.670> offer<00:14:44.879> the<00:14:45.149> next<00:14:45.300> thing<00:14:45.660> there<00:14:46.019> is 00:14:46.100 --> 00:14:46.110 align:start position:0% you don't offer the next thing there is 00:14:46.110 --> 00:14:48.079 align:start position:0% you don't offer the next thing there is a<00:14:46.139> user<00:14:46.470> like<00:14:46.680> say<00:14:46.889> what<00:14:47.069> do<00:14:47.160> I<00:14:47.189> do<00:14:47.309> now 00:14:48.079 --> 00:14:48.089 align:start position:0% a user like say what do I do now 00:14:48.089 --> 00:14:51.980 align:start position:0% a user like say what do I do now I<00:14:49.040> don't<00:14:50.040> know<00:14:50.220> so<00:14:50.490> it<00:14:50.939> said<00:14:51.269> free<00:14:51.660> but<00:14:51.959> I 00:14:51.980 --> 00:14:51.990 align:start position:0% I don't know so it said free but I 00:14:51.990 --> 00:14:54.350 align:start position:0% I don't know so it said free but I continuously<00:14:52.680> see<00:14:52.980> different<00:14:53.430> transaction 00:14:54.350 --> 00:14:54.360 align:start position:0% continuously see different transaction 00:14:54.360 --> 00:14:55.879 align:start position:0% continuously see different transaction fees<00:14:54.600> and<00:14:54.899> I<00:14:54.959> they<00:14:55.079> they<00:14:55.259> don't<00:14:55.500> understand 00:14:55.879 --> 00:14:55.889 align:start position:0% fees and I they they don't understand 00:14:55.889 --> 00:14:57.799 align:start position:0% fees and I they they don't understand what<00:14:56.100> these<00:14:56.279> transaction<00:14:56.759> fees<00:14:56.970> are<00:14:57.209> so<00:14:57.750> you 00:14:57.799 --> 00:14:57.809 align:start position:0% what these transaction fees are so you 00:14:57.809 --> 00:15:00.319 align:start position:0% what these transaction fees are so you need<00:14:58.139> to<00:14:58.319> be<00:14:58.620> wary<00:14:59.100> of<00:14:59.279> using<00:14:59.610> the<00:14:59.879> right<00:15:00.029> words 00:15:00.319 --> 00:15:00.329 align:start position:0% need to be wary of using the right words 00:15:00.329 --> 00:15:01.730 align:start position:0% need to be wary of using the right words because<00:15:00.600> this<00:15:00.750> is<00:15:00.899> actually<00:15:01.230> I<00:15:01.259> said<00:15:01.529> it<00:15:01.620> was 00:15:01.730 --> 00:15:01.740 align:start position:0% because this is actually I said it was 00:15:01.740 --> 00:15:04.610 align:start position:0% because this is actually I said it was fog<00:15:01.980> it<00:15:02.129> says<00:15:02.399> free<00:15:02.759> but<00:15:03.329> it's<00:15:03.509> a<00:15:03.629> worse<00:15:04.379> than 00:15:04.610 --> 00:15:04.620 align:start position:0% fog it says free but it's a worse than 00:15:04.620 --> 00:15:06.559 align:start position:0% fog it says free but it's a worse than monopoly<00:15:04.769> they<00:15:05.250> are<00:15:05.309> screwing<00:15:06.000> me<00:15:06.120> and<00:15:06.300> every 00:15:06.559 --> 00:15:06.569 align:start position:0% monopoly they are screwing me and every 00:15:06.569 --> 00:15:10.460 align:start position:0% monopoly they are screwing me and every step<00:15:07.199> we<00:15:07.379> made<00:15:07.639> this<00:15:08.639> was<00:15:08.910> actual<00:15:09.350> comment<00:15:10.350> so 00:15:10.460 --> 00:15:10.470 align:start position:0% step we made this was actual comment so 00:15:10.470 --> 00:15:15.829 align:start position:0% step we made this was actual comment so that<00:15:10.500> we<00:15:10.769> had<00:15:10.920> very<00:15:11.509> snarky<00:15:12.509> users<00:15:13.379> and<00:15:14.839> design 00:15:15.829 --> 00:15:15.839 align:start position:0% that we had very snarky users and design 00:15:15.839 --> 00:15:17.720 align:start position:0% that we had very snarky users and design the<00:15:16.019> users<00:15:16.350> next<00:15:16.649> step<00:15:16.800> this<00:15:17.009> is<00:15:17.069> basic 00:15:17.720 --> 00:15:17.730 align:start position:0% the users next step this is basic 00:15:17.730 --> 00:15:19.410 align:start position:0% the users next step this is basic behavioral<00:15:18.180> design 00:15:19.410 --> 00:15:19.420 align:start position:0% behavioral design 00:15:19.420 --> 00:15:23.070 align:start position:0% behavioral design doesn't<00:15:19.720> pertain<00:15:20.020> to<00:15:20.220> their<00:15:21.220> -<00:15:21.600> and<00:15:22.600> don't<00:15:22.930> say 00:15:23.070 --> 00:15:23.080 align:start position:0% doesn't pertain to their - and don't say 00:15:23.080 --> 00:15:24.990 align:start position:0% doesn't pertain to their - and don't say free<00:15:23.440> or<00:15:23.620> don't<00:15:23.800> say<00:15:23.980> layer<00:15:24.250> one<00:15:24.520> what<00:15:24.820> your 00:15:24.990 --> 00:15:25.000 align:start position:0% free or don't say layer one what your 00:15:25.000 --> 00:15:28.650 align:start position:0% free or don't say layer one what your name<00:15:25.150> was<00:15:25.270> again<00:15:25.420> etc<00:15:26.130> open<00:15:27.130> questions<00:15:27.700> phases 00:15:28.650 --> 00:15:28.660 align:start position:0% name was again etc open questions phases 00:15:28.660 --> 00:15:33.810 align:start position:0% name was again etc open questions phases because<00:15:30.150> not<00:15:31.150> much<00:15:31.510> could<00:15:31.840> be<00:15:31.900> used<00:15:32.410> yet<00:15:33.100> again 00:15:33.810 --> 00:15:33.820 align:start position:0% because not much could be used yet again 00:15:33.820 --> 00:15:37.290 align:start position:0% because not much could be used yet again there<00:15:34.660> is<00:15:34.840> this<00:15:35.230> idea<00:15:36.100> of<00:15:36.190> agreements<00:15:37.120> in 00:15:37.290 --> 00:15:37.300 align:start position:0% there is this idea of agreements in 00:15:37.300 --> 00:15:39.870 align:start position:0% there is this idea of agreements in state<00:15:37.570> channels<00:15:38.020> when<00:15:38.680> you<00:15:38.920> enter<00:15:39.370> a<00:15:39.400> channel 00:15:39.870 --> 00:15:39.880 align:start position:0% state channels when you enter a channel 00:15:39.880 --> 00:15:42.120 align:start position:0% state channels when you enter a channel with<00:15:40.120> someone<00:15:40.690> okay<00:15:41.080> you<00:15:41.140> are<00:15:41.440> making<00:15:41.770> an 00:15:42.120 --> 00:15:42.130 align:start position:0% with someone okay you are making an 00:15:42.130 --> 00:15:45.840 align:start position:0% with someone okay you are making an agreement<00:15:42.660> about<00:15:43.660> when<00:15:44.650> the<00:15:44.860> exit<00:15:45.490> will 00:15:45.840 --> 00:15:45.850 align:start position:0% agreement about when the exit will 00:15:45.850 --> 00:15:47.790 align:start position:0% agreement about when the exit will happen<00:15:46.300> how<00:15:46.540> long<00:15:46.900> it<00:15:47.110> will<00:15:47.290> take 00:15:47.790 --> 00:15:47.800 align:start position:0% happen how long it will take 00:15:47.800 --> 00:15:50.880 align:start position:0% happen how long it will take okay<00:15:48.130> so<00:15:48.550> this<00:15:48.820> agreement<00:15:49.810> is<00:15:50.020> a<00:15:50.080> new<00:15:50.500> pattern 00:15:50.880 --> 00:15:50.890 align:start position:0% okay so this agreement is a new pattern 00:15:50.890 --> 00:15:54.030 align:start position:0% okay so this agreement is a new pattern okay<00:15:51.610> there<00:15:52.240> is<00:15:52.390> not<00:15:52.750> yet<00:15:53.140> anything<00:15:53.800> that<00:15:53.950> we 00:15:54.030 --> 00:15:54.040 align:start position:0% okay there is not yet anything that we 00:15:54.040 --> 00:15:56.340 align:start position:0% okay there is not yet anything that we could<00:15:54.190> test<00:15:54.460> I<00:15:54.760> personally<00:15:55.600> think<00:15:55.810> that<00:15:55.990> we 00:15:56.340 --> 00:15:56.350 align:start position:0% could test I personally think that we 00:15:56.350 --> 00:16:00.750 align:start position:0% could test I personally think that we should<00:15:56.650> make<00:15:57.040> them<00:15:58.260> flexible<00:15:59.260> and<00:15:59.920> dependent 00:16:00.750 --> 00:16:00.760 align:start position:0% should make them flexible and dependent 00:16:00.760 --> 00:16:03.390 align:start position:0% should make them flexible and dependent on<00:16:01.030> the<00:16:01.480> amount<00:16:02.050> of<00:16:02.350> balance<00:16:02.890> that<00:16:03.040> you<00:16:03.220> are 00:16:03.390 --> 00:16:03.400 align:start position:0% on the amount of balance that you are 00:16:03.400 --> 00:16:05.430 align:start position:0% on the amount of balance that you are exiting<00:16:03.760> if<00:16:04.090> you<00:16:04.270> are<00:16:04.390> editing<00:16:04.750> one<00:16:05.140> coffee 00:16:05.430 --> 00:16:05.440 align:start position:0% exiting if you are editing one coffee 00:16:05.440 --> 00:16:09.210 align:start position:0% exiting if you are editing one coffee value<00:16:06.130> you<00:16:06.700> simply<00:16:07.320> do<00:16:08.320> it<00:16:08.440> right<00:16:08.680> away<00:16:08.800> or 00:16:09.210 --> 00:16:09.220 align:start position:0% value you simply do it right away or 00:16:09.220 --> 00:16:11.190 align:start position:0% value you simply do it right away or it's<00:16:09.490> two<00:16:09.940> minutes<00:16:10.300> or<00:16:10.480> whatever<00:16:10.600> if<00:16:10.960> you<00:16:11.080> are 00:16:11.190 --> 00:16:11.200 align:start position:0% it's two minutes or whatever if you are 00:16:11.200 --> 00:16:13.200 align:start position:0% it's two minutes or whatever if you are exiting<00:16:11.500> two<00:16:11.830> hundred<00:16:12.070> dollars<00:16:12.340> or<00:16:12.670> one 00:16:13.200 --> 00:16:13.210 align:start position:0% exiting two hundred dollars or one 00:16:13.210 --> 00:16:15.300 align:start position:0% exiting two hundred dollars or one thousand<00:16:13.570> dollars<00:16:13.840> maybe<00:16:14.020> that<00:16:14.680> time<00:16:14.980> span 00:16:15.300 --> 00:16:15.310 align:start position:0% thousand dollars maybe that time span 00:16:15.310 --> 00:16:19.170 align:start position:0% thousand dollars maybe that time span expands<00:16:16.410> flexibly<00:16:17.410> right<00:16:18.310> now<00:16:18.400> in<00:16:18.550> space<00:16:18.850> so 00:16:19.170 --> 00:16:19.180 align:start position:0% expands flexibly right now in space so 00:16:19.180 --> 00:16:20.700 align:start position:0% expands flexibly right now in space so that's<00:16:19.480> one<00:16:19.870> of<00:16:19.990> the<00:16:20.080> things<00:16:20.260> that<00:16:20.440> I<00:16:20.620> think 00:16:20.700 --> 00:16:20.710 align:start position:0% that's one of the things that I think 00:16:20.710 --> 00:16:23.250 align:start position:0% that's one of the things that I think they<00:16:20.980> need<00:16:21.160> to<00:16:21.310> work<00:16:21.520> on<00:16:21.730> and<00:16:22.060> how<00:16:22.990> are<00:16:23.170> we 00:16:23.250 --> 00:16:23.260 align:start position:0% they need to work on and how are we 00:16:23.260 --> 00:16:25.050 align:start position:0% they need to work on and how are we going<00:16:23.500> to<00:16:23.620> manage<00:16:24.010> many<00:16:24.340> open<00:16:24.730> channels 00:16:25.050 --> 00:16:25.060 align:start position:0% going to manage many open channels 00:16:25.060 --> 00:16:27.210 align:start position:0% going to manage many open channels because<00:16:25.300> if<00:16:25.420> it's<00:16:25.570> peer-to-peer<00:16:26.220> technically 00:16:27.210 --> 00:16:27.220 align:start position:0% because if it's peer-to-peer technically 00:16:27.220 --> 00:16:28.770 align:start position:0% because if it's peer-to-peer technically I<00:16:27.250> could<00:16:27.340> have<00:16:27.610> a<00:16:27.640> channel<00:16:28.000> with<00:16:28.150> each<00:16:28.420> of<00:16:28.630> you 00:16:28.770 --> 00:16:28.780 align:start position:0% I could have a channel with each of you 00:16:28.780 --> 00:16:31.320 align:start position:0% I could have a channel with each of you in<00:16:28.990> my<00:16:29.110> wallet<00:16:29.140> I<00:16:29.560> would<00:16:29.740> have<00:16:29.890> like<00:16:30.330> thousands 00:16:31.320 --> 00:16:31.330 align:start position:0% in my wallet I would have like thousands 00:16:31.330 --> 00:16:33.720 align:start position:0% in my wallet I would have like thousands of<00:16:31.450> lines<00:16:31.690> or<00:16:31.960> if<00:16:32.230> I<00:16:32.350> have<00:16:32.530> a<00:16:32.560> hub<00:16:32.830> I<00:16:33.100> would<00:16:33.580> have 00:16:33.720 --> 00:16:33.730 align:start position:0% of lines or if I have a hub I would have 00:16:33.730 --> 00:16:35.700 align:start position:0% of lines or if I have a hub I would have the<00:16:33.940> hub<00:16:34.120> with<00:16:34.450> a<00:16:34.480> thousand<00:16:34.930> align<00:16:35.230> with 00:16:35.700 --> 00:16:35.710 align:start position:0% the hub with a thousand align with 00:16:35.710 --> 00:16:37.470 align:start position:0% the hub with a thousand align with people<00:16:36.340> like<00:16:36.430> might<00:16:36.670> have<00:16:36.820> connections<00:16:37.420> with 00:16:37.470 --> 00:16:37.480 align:start position:0% people like might have connections with 00:16:37.480 --> 00:16:40.680 align:start position:0% people like might have connections with the<00:16:38.170> apps<00:16:38.410> will<00:16:38.860> be<00:16:39.130> installed<00:16:39.760> in<00:16:40.180> my<00:16:40.330> wallet 00:16:40.680 --> 00:16:40.690 align:start position:0% the apps will be installed in my wallet 00:16:40.690 --> 00:16:42.680 align:start position:0% the apps will be installed in my wallet and<00:16:40.960> this<00:16:41.110> is<00:16:41.260> good<00:16:41.800> to<00:16:41.890> hear<00:16:42.040> that<00:16:42.220> also 00:16:42.680 --> 00:16:42.690 align:start position:0% and this is good to hear that also 00:16:42.690 --> 00:16:45.900 align:start position:0% and this is good to hear that also minimize<00:16:43.690> yesterday's<00:16:44.370> introduce<00:16:45.370> the<00:16:45.520> fact 00:16:45.900 --> 00:16:45.910 align:start position:0% minimize yesterday's introduce the fact 00:16:45.910 --> 00:16:48.840 align:start position:0% minimize yesterday's introduce the fact that<00:16:46.060> they<00:16:46.570> have<00:16:46.840> these<00:16:47.020> plugins<00:16:47.590> ideas<00:16:48.220> that 00:16:48.840 --> 00:16:48.850 align:start position:0% that they have these plugins ideas that 00:16:48.850 --> 00:16:50.790 align:start position:0% that they have these plugins ideas that you<00:16:49.180> will<00:16:49.390> have<00:16:49.570> absolute<00:16:50.230> side<00:16:50.440> of<00:16:50.650> your 00:16:50.790 --> 00:16:50.800 align:start position:0% you will have absolute side of your 00:16:50.800 --> 00:16:54.240 align:start position:0% you will have absolute side of your wallet<00:16:51.670> to<00:16:51.790> to<00:16:52.000> manage<00:16:52.330> and<00:16:52.690> yeah<00:16:53.500> you<00:16:53.770> need<00:16:54.130> to 00:16:54.240 --> 00:16:54.250 align:start position:0% wallet to to manage and yeah you need to 00:16:54.250 --> 00:16:56.820 align:start position:0% wallet to to manage and yeah you need to differentiate<00:16:54.610> these<00:16:54.940> things<00:16:55.270> and<00:16:55.720> yeah<00:16:56.650> I 00:16:56.820 --> 00:16:56.830 align:start position:0% differentiate these things and yeah I 00:16:56.830 --> 00:16:59.010 align:start position:0% differentiate these things and yeah I was<00:16:56.980> stationary<00:16:57.580> cytoplasm<00:16:58.240> will<00:16:58.570> work<00:16:58.720> we 00:16:59.010 --> 00:16:59.020 align:start position:0% was stationary cytoplasm will work we 00:16:59.020 --> 00:17:01.070 align:start position:0% was stationary cytoplasm will work we have<00:16:59.200> no<00:16:59.350> food 00:17:01.070 --> 00:17:01.080 align:start position:0% have no food 00:17:01.080 --> 00:17:03.350 align:start position:0% have no food hide<00:17:01.410> as<00:17:01.590> much<00:17:01.620> as<00:17:01.980> possible<00:17:02.360> interoperate 00:17:03.350 --> 00:17:03.360 align:start position:0% hide as much as possible interoperate 00:17:03.360 --> 00:17:05.750 align:start position:0% hide as much as possible interoperate this<00:17:03.660> is<00:17:03.840> what<00:17:04.140> these<00:17:04.589> solutions<00:17:04.980> so<00:17:05.430> probably 00:17:05.750 --> 00:17:05.760 align:start position:0% this is what these solutions so probably 00:17:05.760 --> 00:17:09.680 align:start position:0% this is what these solutions so probably are<00:17:06.150> and<00:17:07.400> exiting<00:17:08.400> the<00:17:08.430> system<00:17:08.880> this<00:17:09.089> is<00:17:09.300> the 00:17:09.680 --> 00:17:09.690 align:start position:0% are and exiting the system this is the 00:17:09.690 --> 00:17:12.650 align:start position:0% are and exiting the system this is the science<00:17:10.680> fictiony<00:17:11.190> because<00:17:11.640> right<00:17:12.300> now<00:17:12.450> it's 00:17:12.650 --> 00:17:12.660 align:start position:0% science fictiony because right now it's 00:17:12.660 --> 00:17:14.090 align:start position:0% science fictiony because right now it's only<00:17:13.200> ideas 00:17:14.090 --> 00:17:14.100 align:start position:0% only ideas 00:17:14.100 --> 00:17:17.420 align:start position:0% only ideas there's<00:17:14.459> nothing<00:17:14.910> implemented<00:17:15.950> the<00:17:16.950> only 00:17:17.420 --> 00:17:17.430 align:start position:0% there's nothing implemented the only 00:17:17.430 --> 00:17:20.360 align:start position:0% there's nothing implemented the only company<00:17:18.390> that<00:17:18.570> had<00:17:18.750> designed<00:17:19.380> something<00:17:19.860> is 00:17:20.360 --> 00:17:20.370 align:start position:0% company that had designed something is 00:17:20.370 --> 00:17:23.870 align:start position:0% company that had designed something is seller<00:17:20.970> is<00:17:21.270> again<00:17:21.660> actually<00:17:22.230> seller<00:17:22.740> x<00:17:23.100> worth 00:17:23.870 --> 00:17:23.880 align:start position:0% seller is again actually seller x worth 00:17:23.880 --> 00:17:26.300 align:start position:0% seller is again actually seller x worth it<00:17:24.150> at<00:17:24.270> the<00:17:24.390> job<00:17:24.630> in<00:17:24.810> calling<00:17:25.200> it<00:17:25.320> court<00:17:25.860> mode 00:17:26.300 --> 00:17:26.310 align:start position:0% it at the job in calling it court mode 00:17:26.310 --> 00:17:29.960 align:start position:0% it at the job in calling it court mode okay<00:17:27.030> so<00:17:27.570> they<00:17:28.140> use<00:17:28.410> a<00:17:28.440> nice<00:17:29.040> language<00:17:29.490> to 00:17:29.960 --> 00:17:29.970 align:start position:0% okay so they use a nice language to 00:17:29.970 --> 00:17:32.290 align:start position:0% okay so they use a nice language to explain<00:17:30.390> that<00:17:30.870> there<00:17:31.500> is<00:17:31.590> a<00:17:31.620> challenge 00:17:32.290 --> 00:17:32.300 align:start position:0% explain that there is a challenge 00:17:32.300 --> 00:17:36.920 align:start position:0% explain that there is a challenge happening<00:17:33.300> and<00:17:33.630> how<00:17:34.380> it<00:17:34.860> works<00:17:35.070> and<00:17:35.520> so<00:17:36.420> this 00:17:36.920 --> 00:17:36.930 align:start position:0% happening and how it works and so this 00:17:36.930 --> 00:17:41.590 align:start position:0% happening and how it works and so this idea<00:17:37.320> of<00:17:39.320> exiting<00:17:40.320> that<00:17:40.560> you<00:17:40.680> could<00:17:40.860> have 00:17:41.590 --> 00:17:41.600 align:start position:0% idea of exiting that you could have 00:17:41.600 --> 00:17:43.850 align:start position:0% idea of exiting that you could have challenges<00:17:42.600> happening<00:17:43.200> okay<00:17:43.530> it<00:17:43.680> has<00:17:43.830> a 00:17:43.850 --> 00:17:43.860 align:start position:0% challenges happening okay it has a 00:17:43.860 --> 00:17:46.700 align:start position:0% challenges happening okay it has a requirement<00:17:44.550> on<00:17:45.090> the<00:17:45.300> technology<00:17:45.870> that<00:17:46.200> you 00:17:46.700 --> 00:17:46.710 align:start position:0% requirement on the technology that you 00:17:46.710 --> 00:17:49.040 align:start position:0% requirement on the technology that you as<00:17:46.860> a<00:17:46.890> user<00:17:47.010> need<00:17:47.610> to<00:17:47.730> be<00:17:47.970> looking<00:17:48.480> all<00:17:48.750> the 00:17:49.040 --> 00:17:49.050 align:start position:0% as a user need to be looking all the 00:17:49.050 --> 00:17:52.910 align:start position:0% as a user need to be looking all the time<00:17:49.650> at<00:17:50.010> the<00:17:50.370> chain<00:17:50.670> this<00:17:51.300> is<00:17:51.480> no<00:17:52.230> no<00:17:52.440> go<00:17:52.650> for 00:17:52.910 --> 00:17:52.920 align:start position:0% time at the chain this is no no go for 00:17:52.920 --> 00:17:56.380 align:start position:0% time at the chain this is no no go for ux<00:17:53.400> so<00:17:54.150> there<00:17:54.540> are<00:17:54.690> people<00:17:55.290> coming<00:17:55.590> out<00:17:55.680> with 00:17:56.380 --> 00:17:56.390 align:start position:0% ux so there are people coming out with 00:17:56.390 --> 00:18:00.560 align:start position:0% ux so there are people coming out with watchtowers<00:17:57.390> these<00:17:58.260> are<00:17:58.530> the<00:17:59.370> name<00:17:59.550> one<00:18:00.540> of 00:18:00.560 --> 00:18:00.570 align:start position:0% watchtowers these are the name one of 00:18:00.570 --> 00:18:02.660 align:start position:0% watchtowers these are the name one of the<00:18:00.720> company's<00:18:01.080> called<00:18:01.320> pisa<00:18:01.620> is<00:18:02.010> becoming<00:18:02.520> in 00:18:02.660 --> 00:18:02.670 align:start position:0% the company's called pisa is becoming in 00:18:02.670 --> 00:18:08.000 align:start position:0% the company's called pisa is becoming in the<00:18:02.730> watchtowers<00:18:03.420> and<00:18:05.510> and<00:18:06.510> so<00:18:06.720> this<00:18:06.930> is<00:18:07.140> one 00:18:08.000 --> 00:18:08.010 align:start position:0% the watchtowers and and so this is one 00:18:08.010 --> 00:18:10.490 align:start position:0% the watchtowers and and so this is one of<00:18:08.220> the<00:18:08.400> unknowns<00:18:08.970> how<00:18:09.480> this<00:18:09.810> part<00:18:10.200> will 00:18:10.490 --> 00:18:10.500 align:start position:0% of the unknowns how this part will 00:18:10.500 --> 00:18:12.050 align:start position:0% of the unknowns how this part will behave<00:18:10.890> you<00:18:11.130> know<00:18:11.250> for<00:18:11.490> from<00:18:11.790> the<00:18:11.910> user 00:18:12.050 --> 00:18:12.060 align:start position:0% behave you know for from the user 00:18:12.060 --> 00:18:15.800 align:start position:0% behave you know for from the user perspective<00:18:12.270> my<00:18:13.170> opinion<00:18:13.710> is<00:18:14.070> users<00:18:15.000> won't 00:18:15.800 --> 00:18:15.810 align:start position:0% perspective my opinion is users won't 00:18:15.810 --> 00:18:17.690 align:start position:0% perspective my opinion is users won't need<00:18:16.080> to<00:18:16.230> worry<00:18:16.530> too<00:18:16.650> much<00:18:16.890> about<00:18:17.070> the 00:18:17.690 --> 00:18:17.700 align:start position:0% need to worry too much about the 00:18:17.700 --> 00:18:20.210 align:start position:0% need to worry too much about the challenge<00:18:18.120> if<00:18:18.330> you<00:18:18.600> can<00:18:18.840> find<00:18:19.320> it<00:18:19.530> there's<00:18:20.130> a 00:18:20.210 --> 00:18:20.220 align:start position:0% challenge if you can find it there's a 00:18:20.220 --> 00:18:21.770 align:start position:0% challenge if you can find it there's a consensus<00:18:20.850> or<00:18:20.970> there's<00:18:21.300> three<00:18:21.660> different 00:18:21.770 --> 00:18:21.780 align:start position:0% consensus or there's three different 00:18:21.780 --> 00:18:24.260 align:start position:0% consensus or there's three different approaches<00:18:22.470> right<00:18:22.680> now<00:18:22.830> either<00:18:23.490> the<00:18:24.060> app 00:18:24.260 --> 00:18:24.270 align:start position:0% approaches right now either the app 00:18:24.270 --> 00:18:26.540 align:start position:0% approaches right now either the app itself<00:18:24.690> watches<00:18:25.410> the<00:18:25.530> change<00:18:25.770> for<00:18:26.010> you<00:18:26.130> so<00:18:26.400> if 00:18:26.540 --> 00:18:26.550 align:start position:0% itself watches the change for you so if 00:18:26.550 --> 00:18:28.340 align:start position:0% itself watches the change for you so if you<00:18:26.670> connect<00:18:27.000> every<00:18:27.240> once<00:18:27.720> a<00:18:27.930> week<00:18:28.110> or 00:18:28.340 --> 00:18:28.350 align:start position:0% you connect every once a week or 00:18:28.350 --> 00:18:30.110 align:start position:0% you connect every once a week or whatever<00:18:28.500> it<00:18:28.920> solves<00:18:29.280> it<00:18:29.370> automatically<00:18:29.880> for 00:18:30.110 --> 00:18:30.120 align:start position:0% whatever it solves it automatically for 00:18:30.120 --> 00:18:34.700 align:start position:0% whatever it solves it automatically for you<00:18:30.240> if<00:18:31.400> you<00:18:32.400> or<00:18:32.910> they<00:18:33.330> have<00:18:33.570> by<00:18:33.990> the<00:18:34.050> service 00:18:34.700 --> 00:18:34.710 align:start position:0% you if you or they have by the service 00:18:34.710 --> 00:18:36.530 align:start position:0% you if you or they have by the service of<00:18:34.860> a<00:18:34.950> watchtower<00:18:35.400> so<00:18:35.670> it's<00:18:35.820> a<00:18:35.910> service<00:18:36.390> and 00:18:36.530 --> 00:18:36.540 align:start position:0% of a watchtower so it's a service and 00:18:36.540 --> 00:18:38.420 align:start position:0% of a watchtower so it's a service and it's<00:18:36.660> looking<00:18:37.020> addition<00:18:37.350> is<00:18:37.470> a<00:18:37.590> name<00:18:37.740> you<00:18:38.400> have 00:18:38.420 --> 00:18:38.430 align:start position:0% it's looking addition is a name you have 00:18:38.430 --> 00:18:40.700 align:start position:0% it's looking addition is a name you have a<00:18:38.640> problem<00:18:38.910> i'll<00:18:39.240> send<00:18:39.480> you<00:18:39.540> notification<00:18:40.410> on 00:18:40.700 --> 00:18:40.710 align:start position:0% a problem i'll send you notification on 00:18:40.710 --> 00:18:45.650 align:start position:0% a problem i'll send you notification on your<00:18:40.770> phone<00:18:41.220> about<00:18:42.030> basis<00:18:42.600> fate<00:18:42.810> or<00:18:44.660> dollars 00:18:45.650 --> 00:18:45.660 align:start position:0% your phone about basis fate or dollars 00:18:45.660 --> 00:18:47.990 align:start position:0% your phone about basis fate or dollars among<00:18:46.260> the<00:18:46.590> people<00:18:46.950> participating<00:18:47.310> in<00:18:47.850> this 00:18:47.990 --> 00:18:48.000 align:start position:0% among the people participating in this 00:18:48.000 --> 00:18:50.720 align:start position:0% among the people participating in this channel<00:18:48.390> saying<00:18:48.660> that<00:18:49.260> company<00:18:50.100> product<00:18:50.610> or 00:18:50.720 --> 00:18:50.730 align:start position:0% channel saying that company product or 00:18:50.730 --> 00:18:57.380 align:start position:0% channel saying that company product or user<00:18:51.210> is<00:18:51.600> being<00:18:52.290> malicious<00:18:52.650> I'll<00:18:56.270> kick<00:18:57.270> him 00:18:57.380 --> 00:18:57.390 align:start position:0% user is being malicious I'll kick him 00:18:57.390 --> 00:19:01.760 align:start position:0% user is being malicious I'll kick him out<00:18:57.510> and<00:18:58.910> simply<00:19:00.050> offset 00:19:01.760 --> 00:19:01.770 align:start position:0% out and simply offset 00:19:01.770 --> 00:19:05.900 align:start position:0% out and simply offset for<00:19:02.070> the<00:19:02.280> user<00:19:02.840> in<00:19:03.840> plasma<00:19:04.410> you<00:19:04.710> are<00:19:04.890> also<00:19:05.100> you 00:19:05.900 --> 00:19:05.910 align:start position:0% for the user in plasma you are also you 00:19:05.910 --> 00:19:08.450 align:start position:0% for the user in plasma you are also you have<00:19:06.120> also<00:19:06.270> these<00:19:06.650> multiple<00:19:07.650> speeds<00:19:08.010> to 00:19:08.450 --> 00:19:08.460 align:start position:0% have also these multiple speeds to 00:19:08.460 --> 00:19:12.080 align:start position:0% have also these multiple speeds to exiting<00:19:09.179> okay<00:19:09.690> since<00:19:10.350> in<00:19:10.980> plasma<00:19:11.700> right<00:19:11.940> now 00:19:12.080 --> 00:19:12.090 align:start position:0% exiting okay since in plasma right now 00:19:12.090 --> 00:19:14.450 align:start position:0% exiting okay since in plasma right now one<00:19:12.330> of<00:19:12.360> the<00:19:12.540> Constructors<00:19:13.050> to<00:19:13.200> have<00:19:13.460> two 00:19:14.450 --> 00:19:14.460 align:start position:0% one of the Constructors to have two 00:19:14.460 --> 00:19:17.240 align:start position:0% one of the Constructors to have two weeks<00:19:14.730> or<00:19:14.940> one<00:19:15.210> week<00:19:15.240> when<00:19:16.170> you<00:19:16.320> actually<00:19:16.530> exit 00:19:17.240 --> 00:19:17.250 align:start position:0% weeks or one week when you actually exit 00:19:17.250 --> 00:19:20.060 align:start position:0% weeks or one week when you actually exit before<00:19:17.460> you<00:19:17.790> can<00:19:18.030> get<00:19:18.330> your<00:19:18.570> money<00:19:18.780> okay<00:19:19.140> there 00:19:20.060 --> 00:19:20.070 align:start position:0% before you can get your money okay there 00:19:20.070 --> 00:19:22.250 align:start position:0% before you can get your money okay there are<00:19:20.190> people<00:19:20.670> that<00:19:20.880> are<00:19:21.030> creating<00:19:21.630> crypto 00:19:22.250 --> 00:19:22.260 align:start position:0% are people that are creating crypto 00:19:22.260 --> 00:19:24.530 align:start position:0% are people that are creating crypto economic<00:19:22.860> phenology<00:19:23.220> so<00:19:23.670> there<00:19:23.850> are<00:19:23.970> services 00:19:24.530 --> 00:19:24.540 align:start position:0% economic phenology so there are services 00:19:24.540 --> 00:19:28.010 align:start position:0% economic phenology so there are services that<00:19:24.600> say<00:19:25.080> hey<00:19:25.760> you<00:19:26.760> as<00:19:27.000> a<00:19:27.030> user<00:19:27.330> you<00:19:27.780> don't 00:19:28.010 --> 00:19:28.020 align:start position:0% that say hey you as a user you don't 00:19:28.020 --> 00:19:31.460 align:start position:0% that say hey you as a user you don't want<00:19:28.410> to<00:19:28.650> wait<00:19:28.830> one<00:19:29.130> week<00:19:29.160> so<00:19:29.970> let<00:19:30.450> me<00:19:30.780> take 00:19:31.460 --> 00:19:31.470 align:start position:0% want to wait one week so let me take 00:19:31.470 --> 00:19:34.910 align:start position:0% want to wait one week so let me take your<00:19:31.860> risk<00:19:32.370> I'll<00:19:32.760> buy<00:19:33.120> your<00:19:33.480> one<00:19:34.320> you're 00:19:34.910 --> 00:19:34.920 align:start position:0% your risk I'll buy your one you're 00:19:34.920 --> 00:19:37.340 align:start position:0% your risk I'll buy your one you're either<00:19:35.280> within<00:19:35.640> one<00:19:35.880> week<00:19:36.030> for<00:19:36.360> one<00:19:36.990> percent 00:19:37.340 --> 00:19:37.350 align:start position:0% either within one week for one percent 00:19:37.350 --> 00:19:38.660 align:start position:0% either within one week for one percent fee<00:19:37.470> or<00:19:37.710> for<00:19:37.890> two<00:19:38.010> percent<00:19:38.280> fee 00:19:38.660 --> 00:19:38.670 align:start position:0% fee or for two percent fee 00:19:38.670 --> 00:19:40.940 align:start position:0% fee or for two percent fee so<00:19:38.940> there<00:19:39.120> are<00:19:39.240> services<00:19:39.960> that<00:19:40.440> are<00:19:40.559> going<00:19:40.800> to 00:19:40.940 --> 00:19:40.950 align:start position:0% so there are services that are going to 00:19:40.950 --> 00:19:43.250 align:start position:0% so there are services that are going to gather<00:19:41.190> a<00:19:41.400> thief<00:19:41.850> for<00:19:42.179> you<00:19:42.450> to<00:19:42.660> recover<00:19:43.080> your 00:19:43.250 --> 00:19:43.260 align:start position:0% gather a thief for you to recover your 00:19:43.260 --> 00:19:45.530 align:start position:0% gather a thief for you to recover your money<00:19:43.470> right<00:19:43.830> away<00:19:43.860> a<00:19:44.400> user<00:19:44.820> wants<00:19:45.179> to<00:19:45.240> recover 00:19:45.530 --> 00:19:45.540 align:start position:0% money right away a user wants to recover 00:19:45.540 --> 00:19:47.299 align:start position:0% money right away a user wants to recover the<00:19:45.750> money<00:19:45.840> right<00:19:46.110> away<00:19:46.140> and<00:19:46.710> this<00:19:46.890> is<00:19:47.040> the 00:19:47.299 --> 00:19:47.309 align:start position:0% the money right away and this is the 00:19:47.309 --> 00:19:49.760 align:start position:0% the money right away and this is the original<00:19:47.490> solution<00:19:48.330> this<00:19:48.990> is<00:19:49.140> why<00:19:49.290> I'm<00:19:49.440> not 00:19:49.760 --> 00:19:49.770 align:start position:0% original solution this is why I'm not 00:19:49.770 --> 00:19:51.490 align:start position:0% original solution this is why I'm not totally<00:19:50.100> convinced<00:19:50.550> about<00:19:50.850> the<00:19:51.000> plasma 00:19:51.490 --> 00:19:51.500 align:start position:0% totally convinced about the plasma 00:19:51.500 --> 00:19:53.330 align:start position:0% totally convinced about the plasma construct<00:19:52.500> especially<00:19:52.920> for<00:19:53.070> my<00:19:53.160> user 00:19:53.330 --> 00:19:53.340 align:start position:0% construct especially for my user 00:19:53.340 --> 00:19:55.100 align:start position:0% construct especially for my user perspective<00:19:53.580> but<00:19:54.059> those<00:19:54.270> are<00:19:54.510> solutions<00:19:54.750> that 00:19:55.100 --> 00:19:55.110 align:start position:0% perspective but those are solutions that 00:19:55.110 --> 00:19:58.130 align:start position:0% perspective but those are solutions that are<00:19:55.230> coming<00:19:55.890> and<00:19:56.640> so<00:19:57.179> you<00:19:57.240> see<00:19:57.450> there's<00:19:57.660> a<00:19:57.720> more 00:19:58.130 --> 00:19:58.140 align:start position:0% are coming and so you see there's a more 00:19:58.140 --> 00:20:01.010 align:start position:0% are coming and so you see there's a more complexity<00:19:58.950> still<00:19:59.280> rather<00:20:00.000> than<00:20:00.270> less<00:20:00.540> which 00:20:01.010 --> 00:20:01.020 align:start position:0% complexity still rather than less which 00:20:01.020 --> 00:20:05.000 align:start position:0% complexity still rather than less which was<00:20:01.590> my<00:20:02.490> hope<00:20:02.970> and<00:20:03.360> in<00:20:04.020> general<00:20:04.530> in<00:20:04.830> the<00:20:04.980> whole 00:20:05.000 --> 00:20:05.010 align:start position:0% was my hope and in general in the whole 00:20:05.010 --> 00:20:07.910 align:start position:0% was my hope and in general in the whole space<00:20:05.429> and<00:20:05.490> in<00:20:06.090> layer<00:20:06.360> two<00:20:06.600> space<00:20:06.870> as<00:20:07.050> well<00:20:07.200> we 00:20:07.910 --> 00:20:07.920 align:start position:0% space and in layer two space as well we 00:20:07.920 --> 00:20:11.120 align:start position:0% space and in layer two space as well we need<00:20:08.880> to<00:20:09.059> balance<00:20:09.300> or<00:20:09.809> explain<00:20:10.440> better<00:20:10.740> this 00:20:11.120 --> 00:20:11.130 align:start position:0% need to balance or explain better this 00:20:11.130 --> 00:20:13.760 align:start position:0% need to balance or explain better this idea<00:20:11.550> between<00:20:11.730> cost<00:20:12.300> and<00:20:12.770> responsibility 00:20:13.760 --> 00:20:13.770 align:start position:0% idea between cost and responsibility 00:20:13.770 --> 00:20:15.650 align:start position:0% idea between cost and responsibility okay<00:20:14.040> and<00:20:14.340> in<00:20:14.460> later<00:20:14.640> to<00:20:14.880> is<00:20:14.970> becoming<00:20:15.390> more<00:20:15.600> a 00:20:15.650 --> 00:20:15.660 align:start position:0% okay and in later to is becoming more a 00:20:15.660 --> 00:20:16.340 align:start position:0% okay and in later to is becoming more a theorem 00:20:16.340 --> 00:20:16.350 align:start position:0% theorem 00:20:16.350 --> 00:20:20.030 align:start position:0% theorem okay<00:20:16.620> you<00:20:17.460> can<00:20:17.850> have<00:20:18.150> more<00:20:18.840> cost<00:20:19.260> or<00:20:19.530> less<00:20:19.770> cost 00:20:20.030 --> 00:20:20.040 align:start position:0% okay you can have more cost or less cost 00:20:20.040 --> 00:20:22.130 align:start position:0% okay you can have more cost or less cost or<00:20:20.190> a<00:20:20.220> bit<00:20:20.460> cheaper<00:20:20.820> the<00:20:21.150> transaction<00:20:21.690> if<00:20:21.870> you 00:20:22.130 --> 00:20:22.140 align:start position:0% or a bit cheaper the transaction if you 00:20:22.140 --> 00:20:24.169 align:start position:0% or a bit cheaper the transaction if you as<00:20:22.320> a<00:20:22.350> user<00:20:22.620> take<00:20:22.950> more<00:20:23.220> responsibility<00:20:24.030> on 00:20:24.169 --> 00:20:24.179 align:start position:0% as a user take more responsibility on 00:20:24.179 --> 00:20:28.190 align:start position:0% as a user take more responsibility on waiting<00:20:25.140> doing<00:20:25.920> watching<00:20:26.870> waiting<00:20:27.870> the<00:20:28.050> X 00:20:28.190 --> 00:20:28.200 align:start position:0% waiting doing watching waiting the X 00:20:28.200 --> 00:20:30.710 align:start position:0% waiting doing watching waiting the X days<00:20:28.470> etc<00:20:28.740> or<00:20:29.370> if<00:20:29.850> you<00:20:30.120> want<00:20:30.330> the<00:20:30.510> convenience 00:20:30.710 --> 00:20:30.720 align:start position:0% days etc or if you want the convenience 00:20:30.720 --> 00:20:33.710 align:start position:0% days etc or if you want the convenience is<00:20:31.500> going<00:20:31.710> to<00:20:31.830> be<00:20:31.950> more<00:20:32.190> expensive<00:20:32.700> but<00:20:33.540> it's 00:20:33.710 --> 00:20:33.720 align:start position:0% is going to be more expensive but it's 00:20:33.720 --> 00:20:36.110 align:start position:0% is going to be more expensive but it's more<00:20:33.840> convenient<00:20:34.200> so<00:20:34.559> this<00:20:35.340> is<00:20:35.520> something 00:20:36.110 --> 00:20:36.120 align:start position:0% more convenient so this is something 00:20:36.120 --> 00:20:39.200 align:start position:0% more convenient so this is something that<00:20:36.150> is<00:20:36.540> unsolved<00:20:37.440> today<00:20:37.800> I<00:20:38.370> think<00:20:38.910> in<00:20:39.090> the 00:20:39.200 --> 00:20:39.210 align:start position:0% that is unsolved today I think in the 00:20:39.210 --> 00:20:42.650 align:start position:0% that is unsolved today I think in the whole<00:20:39.390> ecosystem<00:20:40.230> and<00:20:40.800> especially<00:20:41.760> later<00:20:42.210> I'm 00:20:42.650 --> 00:20:42.660 align:start position:0% whole ecosystem and especially later I'm 00:20:42.660 --> 00:20:46.570 align:start position:0% whole ecosystem and especially later I'm done<00:20:42.960> most<00:20:43.740> by<00:20:43.890> data<00:20:44.750> so<00:20:45.750> this<00:20:45.900> is<00:20:46.050> the<00:20:46.140> summary 00:20:46.570 --> 00:20:46.580 align:start position:0% done most by data so this is the summary 00:20:46.580 --> 00:20:52.400 align:start position:0% done most by data so this is the summary basically<00:20:49.280> trying<00:20:50.280> to<00:20:50.520> interoperate<00:20:51.420> so<00:20:52.230> that 00:20:52.400 --> 00:20:52.410 align:start position:0% basically trying to interoperate so that 00:20:52.410 --> 00:20:54.740 align:start position:0% basically trying to interoperate so that people<00:20:52.800> are<00:20:52.860> not<00:20:52.980> confused<00:20:53.490> with<00:20:53.700> as<00:20:54.059> multiple 00:20:54.740 --> 00:20:54.750 align:start position:0% people are not confused with as multiple 00:20:54.750 --> 00:20:57.629 align:start position:0% people are not confused with as multiple kind<00:20:55.050> of<00:20:55.170> tokens<00:20:55.620> try<00:20:56.309> to<00:20:56.370> hide<00:20:56.730> as<00:20:56.970> monster 00:20:57.629 --> 00:20:57.639 align:start position:0% kind of tokens try to hide as monster 00:20:57.639 --> 00:21:01.560 align:start position:0% kind of tokens try to hide as monster the<00:20:57.989> technological<00:21:00.059> methodologies<00:21:01.059> behind 00:21:01.560 --> 00:21:01.570 align:start position:0% the technological methodologies behind 00:21:01.570 --> 00:21:05.519 align:start position:0% the technological methodologies behind okay<00:21:02.409> and<00:21:02.709> make<00:21:03.429> it<00:21:03.700> simpler<00:21:04.209> to<00:21:04.329> the<00:21:04.570> user<00:21:04.719> use 00:21:05.519 --> 00:21:05.529 align:start position:0% okay and make it simpler to the user use 00:21:05.529 --> 00:21:08.399 align:start position:0% okay and make it simpler to the user use Universal<00:21:06.489> login<00:21:06.820> type<00:21:07.119> of<00:21:07.299> wallet<00:21:07.899> or 00:21:08.399 --> 00:21:08.409 align:start position:0% Universal login type of wallet or 00:21:08.409 --> 00:21:10.829 align:start position:0% Universal login type of wallet or contract<00:21:09.009> based<00:21:09.190> wallets<00:21:09.789> or<00:21:09.909> accounts<00:21:10.329> so 00:21:10.829 --> 00:21:10.839 align:start position:0% contract based wallets or accounts so 00:21:10.839 --> 00:21:13.259 align:start position:0% contract based wallets or accounts so that<00:21:11.019> users<00:21:11.469> don't<00:21:11.649> need<00:21:11.829> to<00:21:12.129> store<00:21:12.429> private 00:21:13.259 --> 00:21:13.269 align:start position:0% that users don't need to store private 00:21:13.269 --> 00:21:15.719 align:start position:0% that users don't need to store private keys<00:21:13.450> etc<00:21:13.629> we<00:21:14.079> simplify<00:21:14.649> that<00:21:14.679> initial<00:21:15.459> step 00:21:15.719 --> 00:21:15.729 align:start position:0% keys etc we simplify that initial step 00:21:15.729 --> 00:21:19.769 align:start position:0% keys etc we simplify that initial step and<00:21:16.769> maybe<00:21:17.769> we<00:21:18.249> have<00:21:18.489> something<00:21:19.119> to<00:21:19.389> onboard 00:21:19.769 --> 00:21:19.779 align:start position:0% and maybe we have something to onboard 00:21:19.779 --> 00:21:26.090 align:start position:0% and maybe we have something to onboard my<00:21:20.229> mother<00:21:20.469> and<00:21:20.709> my<00:21:20.829> brother<00:21:21.070> thank<00:21:21.729> you 00:21:26.090 --> 00:21:26.100 align:start position:0% 00:21:26.100 --> 00:21:33.240 align:start position:0% [Applause]