WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:14.589 align:start position:0% [Music] 00:00:14.589 --> 00:00:14.599 align:start position:0% 00:00:14.599 --> 00:00:17.450 align:start position:0% and<00:00:15.599> thank<00:00:15.780> you<00:00:15.900> for<00:00:16.080> coming<00:00:16.260> to<00:00:16.680> this<00:00:17.279> talk 00:00:17.450 --> 00:00:17.460 align:start position:0% and thank you for coming to this talk 00:00:17.460 --> 00:00:21.410 align:start position:0% and thank you for coming to this talk I'm<00:00:18.240> Chang<00:00:18.539> Fong<00:00:19.199> I'm<00:00:19.440> talking<00:00:19.560> labs<00:00:20.220> and<00:00:21.060> I'm 00:00:21.410 --> 00:00:21.420 align:start position:0% I'm Chang Fong I'm talking labs and I'm 00:00:21.420 --> 00:00:23.510 align:start position:0% I'm Chang Fong I'm talking labs and I'm talking<00:00:21.600> it's<00:00:21.960> a<00:00:22.140> non-castew<00:00:22.980> valley<00:00:23.039> based 00:00:23.510 --> 00:00:23.520 align:start position:0% talking it's a non-castew valley based 00:00:23.520 --> 00:00:25.730 align:start position:0% talking it's a non-castew valley based in<00:00:23.580> Singapore<00:00:23.939> and<00:00:24.900> today<00:00:25.080> I'm<00:00:25.320> gonna<00:00:25.500> talk 00:00:25.730 --> 00:00:25.740 align:start position:0% in Singapore and today I'm gonna talk 00:00:25.740 --> 00:00:27.849 align:start position:0% in Singapore and today I'm gonna talk about<00:00:25.920> the<00:00:26.160> topic<00:00:26.580> which<00:00:27.180> is<00:00:27.300> called 00:00:27.849 --> 00:00:27.859 align:start position:0% about the topic which is called 00:00:27.859 --> 00:00:30.650 align:start position:0% about the topic which is called postmoduality<00:00:28.859> so<00:00:29.580> before<00:00:29.820> the<00:00:30.119> talk<00:00:30.240> I<00:00:30.539> would 00:00:30.650 --> 00:00:30.660 align:start position:0% postmoduality so before the talk I would 00:00:30.660 --> 00:00:33.049 align:start position:0% postmoduality so before the talk I would like<00:00:30.779> to<00:00:30.960> ask<00:00:31.140> you<00:00:31.380> guys<00:00:31.679> a<00:00:32.040> question<00:00:32.279> what<00:00:32.820> is 00:00:33.049 --> 00:00:33.059 align:start position:0% like to ask you guys a question what is 00:00:33.059 --> 00:00:35.510 align:start position:0% like to ask you guys a question what is your<00:00:33.239> ideal<00:00:33.719> wallet<00:00:34.200> I<00:00:34.680> think<00:00:34.800> many<00:00:35.100> of<00:00:35.280> you 00:00:35.510 --> 00:00:35.520 align:start position:0% your ideal wallet I think many of you 00:00:35.520 --> 00:00:38.090 align:start position:0% your ideal wallet I think many of you may<00:00:35.760> like<00:00:36.000> use<00:00:36.420> metal<00:00:36.780> mask<00:00:37.200> maybe<00:00:37.800> I'm 00:00:38.090 --> 00:00:38.100 align:start position:0% may like use metal mask maybe I'm 00:00:38.100 --> 00:00:41.330 align:start position:0% may like use metal mask maybe I'm talking<00:00:38.340> or<00:00:38.940> other<00:00:39.320> audits<00:00:40.320> so<00:00:40.739> what<00:00:41.040> is<00:00:41.160> your 00:00:41.330 --> 00:00:41.340 align:start position:0% talking or other audits so what is your 00:00:41.340 --> 00:00:44.150 align:start position:0% talking or other audits so what is your idea<00:00:41.700> what<00:00:41.940> it<00:00:42.180> looks<00:00:42.480> like 00:00:44.150 --> 00:00:44.160 align:start position:0% idea what it looks like 00:00:44.160 --> 00:00:46.490 align:start position:0% idea what it looks like you<00:00:44.700> don't<00:00:44.820> need<00:00:45.000> to<00:00:45.120> have<00:00:45.360> a<00:00:45.660> answer<00:00:46.200> a 00:00:46.490 --> 00:00:46.500 align:start position:0% you don't need to have a answer a 00:00:46.500 --> 00:00:49.850 align:start position:0% you don't need to have a answer a question<00:00:46.680> now<00:00:46.980> but<00:00:47.280> it's<00:00:47.760> a<00:00:48.000> worthy<00:00:49.260> um<00:00:49.260> to 00:00:49.850 --> 00:00:49.860 align:start position:0% question now but it's a worthy um to 00:00:49.860 --> 00:00:52.430 align:start position:0% question now but it's a worthy um to think<00:00:49.980> about<00:00:50.100> it 00:00:52.430 --> 00:00:52.440 align:start position:0% 00:00:52.440 --> 00:00:55.729 align:start position:0% so<00:00:52.920> let's<00:00:53.100> take<00:00:53.399> some<00:00:53.640> time<00:00:53.879> to<00:00:54.300> look<00:00:54.480> at<00:00:54.739> uh 00:00:55.729 --> 00:00:55.739 align:start position:0% so let's take some time to look at uh 00:00:55.739 --> 00:00:59.330 align:start position:0% so let's take some time to look at uh where<00:00:55.980> we<00:00:56.160> are<00:00:56.340> now<00:00:56.520> and<00:00:57.480> look<00:00:58.440> back<00:00:58.980> at<00:00:59.160> the 00:00:59.330 --> 00:00:59.340 align:start position:0% where we are now and look back at the 00:00:59.340 --> 00:01:02.150 align:start position:0% where we are now and look back at the past<00:00:59.640> the<00:01:00.120> past<00:01:00.420> I<00:01:01.199> would<00:01:01.320> like<00:01:01.440> to<00:01:01.620> go<00:01:01.920> through 00:01:02.150 --> 00:01:02.160 align:start position:0% past the past I would like to go through 00:01:02.160 --> 00:01:05.210 align:start position:0% past the past I would like to go through some<00:01:02.579> number<00:01:02.820> and<00:01:03.180> some<00:01:03.480> observation<00:01:04.140> uh<00:01:04.979> from 00:01:05.210 --> 00:01:05.220 align:start position:0% some number and some observation uh from 00:01:05.220 --> 00:01:07.550 align:start position:0% some number and some observation uh from what<00:01:05.460> we<00:01:05.700> have<00:01:06.000> right<00:01:06.360> now 00:01:07.550 --> 00:01:07.560 align:start position:0% what we have right now 00:01:07.560 --> 00:01:11.330 align:start position:0% what we have right now so<00:01:08.040> here<00:01:08.280> is<00:01:08.460> the<00:01:08.780> adoption<00:01:09.780> map<00:01:10.080> of<00:01:10.680> eastern 00:01:11.330 --> 00:01:11.340 align:start position:0% so here is the adoption map of eastern 00:01:11.340 --> 00:01:14.630 align:start position:0% so here is the adoption map of eastern uh<00:01:11.760> of<00:01:12.180> the<00:01:12.360> ethereum<00:01:12.900> users<00:01:13.439> so<00:01:13.979> we<00:01:14.159> can<00:01:14.340> see 00:01:14.630 --> 00:01:14.640 align:start position:0% uh of the ethereum users so we can see 00:01:14.640 --> 00:01:18.289 align:start position:0% uh of the ethereum users so we can see uh<00:01:15.240> many<00:01:15.600> users<00:01:16.140> are<00:01:16.560> distributed<00:01:17.159> in<00:01:17.400> North 00:01:18.289 --> 00:01:18.299 align:start position:0% uh many users are distributed in North 00:01:18.299 --> 00:01:23.090 align:start position:0% uh many users are distributed in North America<00:01:18.600> Europe<00:01:19.500> Asia<00:01:20.460> and<00:01:20.880> everywhere<00:01:21.900> but 00:01:23.090 --> 00:01:23.100 align:start position:0% America Europe Asia and everywhere but 00:01:23.100 --> 00:01:26.030 align:start position:0% America Europe Asia and everywhere but and<00:01:23.759> this<00:01:24.060> user<00:01:24.420> already<00:01:24.720> are<00:01:25.140> crypto<00:01:25.500> users 00:01:26.030 --> 00:01:26.040 align:start position:0% and this user already are crypto users 00:01:26.040 --> 00:01:29.390 align:start position:0% and this user already are crypto users so<00:01:26.640> how<00:01:26.939> do<00:01:27.119> I<00:01:27.299> Define<00:01:27.479> crypto<00:01:28.200> users<00:01:28.619> next<00:01:29.159> is 00:01:29.390 --> 00:01:29.400 align:start position:0% so how do I Define crypto users next is 00:01:29.400 --> 00:01:30.130 align:start position:0% so how do I Define crypto users next is because 00:01:30.130 --> 00:01:30.140 align:start position:0% because 00:01:30.140 --> 00:01:34.249 align:start position:0% because not<00:01:31.140> everyone<00:01:31.439> use<00:01:31.920> Liquid<00:01:32.400> toward<00:01:32.759> it<00:01:33.360> but<00:01:33.900> I 00:01:34.249 --> 00:01:34.259 align:start position:0% not everyone use Liquid toward it but I 00:01:34.259 --> 00:01:37.069 align:start position:0% not everyone use Liquid toward it but I think<00:01:34.380> uh<00:01:35.520> most<00:01:36.000> of<00:01:36.119> the<00:01:36.299> people<00:01:36.479> right<00:01:36.840> now 00:01:37.069 --> 00:01:37.079 align:start position:0% think uh most of the people right now 00:01:37.079 --> 00:01:39.590 align:start position:0% think uh most of the people right now they<00:01:37.500> just<00:01:37.680> use<00:01:37.920> the<00:01:38.220> decentralized<00:01:39.180> exchange 00:01:39.590 --> 00:01:39.600 align:start position:0% they just use the decentralized exchange 00:01:39.600 --> 00:01:43.069 align:start position:0% they just use the decentralized exchange like<00:01:39.900> Finance<00:01:40.439> like<00:01:40.860> FTS<00:01:41.460> exchange<00:01:42.000> so<00:01:42.600> how<00:01:42.840> do 00:01:43.069 --> 00:01:43.079 align:start position:0% like Finance like FTS exchange so how do 00:01:43.079 --> 00:01:47.030 align:start position:0% like Finance like FTS exchange so how do we<00:01:43.259> I<00:01:43.740> mean<00:01:44.000> turn<00:01:45.000> this<00:01:45.240> kind<00:01:45.479> of<00:01:45.600> situation 00:01:47.030 --> 00:01:47.040 align:start position:0% we I mean turn this kind of situation 00:01:47.040 --> 00:01:49.429 align:start position:0% we I mean turn this kind of situation so<00:01:47.579> make<00:01:47.820> more<00:01:48.119> people<00:01:48.420> to<00:01:48.780> get<00:01:49.020> into<00:01:49.200> the 00:01:49.429 --> 00:01:49.439 align:start position:0% so make more people to get into the 00:01:49.439 --> 00:01:52.130 align:start position:0% so make more people to get into the crypto<00:01:49.740> Valley<00:01:50.040> that<00:01:50.460> is<00:01:50.640> the<00:01:50.880> the<00:01:51.540> core<00:01:51.720> idea 00:01:52.130 --> 00:01:52.140 align:start position:0% crypto Valley that is the the core idea 00:01:52.140 --> 00:01:55.389 align:start position:0% crypto Valley that is the the core idea of<00:01:52.320> this<00:01:52.560> topic<00:01:53.460> so<00:01:54.000> for<00:01:54.180> now<00:01:54.360> there<00:01:54.720> are<00:01:54.899> over 00:01:55.389 --> 00:01:55.399 align:start position:0% of this topic so for now there are over 00:01:55.399 --> 00:01:58.450 align:start position:0% of this topic so for now there are over 221<00:01:56.399> million<00:01:56.820> people<00:01:57.060> uh<00:01:57.960> have<00:01:58.140> quick 00:01:58.450 --> 00:01:58.460 align:start position:0% 221 million people uh have quick 00:01:58.460 --> 00:02:01.190 align:start position:0% 221 million people uh have quick cryptocurrency<00:01:59.460> right<00:01:59.759> now<00:02:00.000> uh<00:02:00.780> this<00:02:01.020> number 00:02:01.190 --> 00:02:01.200 align:start position:0% cryptocurrency right now uh this number 00:02:01.200 --> 00:02:03.950 align:start position:0% cryptocurrency right now uh this number might<00:02:01.619> not<00:02:01.740> be<00:02:01.979> accurate<00:02:02.759> just<00:02:03.299> for<00:02:03.479> reference 00:02:03.950 --> 00:02:03.960 align:start position:0% might not be accurate just for reference 00:02:03.960 --> 00:02:08.290 align:start position:0% might not be accurate just for reference if<00:02:04.500> we<00:02:04.680> assume<00:02:05.460> the<00:02:05.579> number<00:02:05.820> is<00:02:06.299> correct<00:02:06.840> then 00:02:08.290 --> 00:02:08.300 align:start position:0% if we assume the number is correct then 00:02:08.300 --> 00:02:12.830 align:start position:0% if we assume the number is correct then 97<00:02:09.619> of<00:02:10.619> people<00:02:10.920> don't<00:02:11.220> know<00:02:11.400> crypto<00:02:11.879> or<00:02:12.480> don't 00:02:12.830 --> 00:02:12.840 align:start position:0% 97 of people don't know crypto or don't 00:02:12.840 --> 00:02:15.589 align:start position:0% 97 of people don't know crypto or don't have<00:02:13.080> any<00:02:13.440> kind<00:02:13.860> of<00:02:13.980> crypto<00:02:14.459> assets<00:02:14.819> so<00:02:15.360> one 00:02:15.589 --> 00:02:15.599 align:start position:0% have any kind of crypto assets so one 00:02:15.599 --> 00:02:18.290 align:start position:0% have any kind of crypto assets so one day<00:02:15.780> if<00:02:16.140> you<00:02:16.260> want<00:02:16.620> to<00:02:16.739> introduce<00:02:17.700> the<00:02:17.940> crypto 00:02:18.290 --> 00:02:18.300 align:start position:0% day if you want to introduce the crypto 00:02:18.300 --> 00:02:21.589 align:start position:0% day if you want to introduce the crypto wallet<00:02:18.720> to<00:02:18.900> your<00:02:19.200> parents<00:02:20.040> your<00:02:20.580> friend<00:02:20.940> or 00:02:21.589 --> 00:02:21.599 align:start position:0% wallet to your parents your friend or 00:02:21.599 --> 00:02:23.690 align:start position:0% wallet to your parents your friend or even<00:02:21.720> your<00:02:21.959> teacher<00:02:22.440> how<00:02:22.680> do<00:02:22.800> you<00:02:22.920> do<00:02:23.099> that<00:02:23.220> can 00:02:23.690 --> 00:02:23.700 align:start position:0% even your teacher how do you do that can 00:02:23.700 --> 00:02:25.490 align:start position:0% even your teacher how do you do that can you<00:02:23.879> help<00:02:24.120> them<00:02:24.360> to<00:02:24.599> set<00:02:24.840> up<00:02:25.020> a<00:02:25.200> crypto 00:02:25.490 --> 00:02:25.500 align:start position:0% you help them to set up a crypto 00:02:25.500 --> 00:02:28.130 align:start position:0% you help them to set up a crypto Wireless<00:02:25.680> in<00:02:26.220> two<00:02:26.400> minutes<00:02:26.580> five<00:02:27.420> minutes<00:02:27.599> or 00:02:28.130 --> 00:02:28.140 align:start position:0% Wireless in two minutes five minutes or 00:02:28.140 --> 00:02:30.610 align:start position:0% Wireless in two minutes five minutes or even<00:02:28.260> in<00:02:28.560> 10<00:02:28.860> minutes<00:02:29.099> I<00:02:29.760> think<00:02:29.879> the<00:02:30.239> answer 00:02:30.610 --> 00:02:30.620 align:start position:0% even in 10 minutes I think the answer 00:02:30.620 --> 00:02:34.430 align:start position:0% even in 10 minutes I think the answer for<00:02:31.620> now<00:02:31.739> probably<00:02:32.040> is<00:02:32.580> no<00:02:32.940> it's<00:02:33.840> really<00:02:34.140> hard 00:02:34.430 --> 00:02:34.440 align:start position:0% for now probably is no it's really hard 00:02:34.440 --> 00:02:36.830 align:start position:0% for now probably is no it's really hard for<00:02:34.680> them<00:02:34.860> to<00:02:35.160> know<00:02:35.459> what<00:02:35.819> is<00:02:36.000> crypto<00:02:36.420> because 00:02:36.830 --> 00:02:36.840 align:start position:0% for them to know what is crypto because 00:02:36.840 --> 00:02:38.930 align:start position:0% for them to know what is crypto because the<00:02:37.140> learning<00:02:37.500> curve<00:02:37.739> is<00:02:37.860> pretty<00:02:38.099> high<00:02:38.340> so 00:02:38.930 --> 00:02:38.940 align:start position:0% the learning curve is pretty high so 00:02:38.940 --> 00:02:40.910 align:start position:0% the learning curve is pretty high so here<00:02:39.180> are<00:02:39.420> the<00:02:39.720> challenges 00:02:40.910 --> 00:02:40.920 align:start position:0% here are the challenges 00:02:40.920 --> 00:02:43.309 align:start position:0% here are the challenges um<00:02:40.980> we<00:02:41.760> are<00:02:41.940> facing<00:02:42.360> every<00:02:42.599> day<00:02:42.780> if<00:02:42.959> you<00:02:43.140> are 00:02:43.309 --> 00:02:43.319 align:start position:0% um we are facing every day if you are 00:02:43.319 --> 00:02:45.589 align:start position:0% um we are facing every day if you are working<00:02:43.440> as<00:02:43.739> the<00:02:44.040> what<00:02:44.580> is<00:02:44.700> company<00:02:44.940> then<00:02:45.360> you 00:02:45.589 --> 00:02:45.599 align:start position:0% working as the what is company then you 00:02:45.599 --> 00:02:49.190 align:start position:0% working as the what is company then you you<00:02:46.319> will<00:02:46.560> receive<00:02:47.239> the<00:02:48.239> feedback<00:02:48.540> like<00:02:48.900> this 00:02:49.190 --> 00:02:49.200 align:start position:0% you will receive the feedback like this 00:02:49.200 --> 00:02:51.890 align:start position:0% you will receive the feedback like this every<00:02:49.620> day<00:02:49.860> so<00:02:50.340> people<00:02:50.580> don't<00:02:51.000> know<00:02:51.239> what<00:02:51.780> is 00:02:51.890 --> 00:02:51.900 align:start position:0% every day so people don't know what is 00:02:51.900 --> 00:02:55.250 align:start position:0% every day so people don't know what is the<00:02:52.080> crypto<00:02:52.440> what<00:02:52.920> is<00:02:53.040> the<00:02:53.400> C<00:02:53.940> phrase<00:02:54.360> and<00:02:55.019> also 00:02:55.250 --> 00:02:55.260 align:start position:0% the crypto what is the C phrase and also 00:02:55.260 --> 00:02:57.290 align:start position:0% the crypto what is the C phrase and also they<00:02:55.440> don't<00:02:55.620> know<00:02:55.739> how<00:02:56.040> to<00:02:56.220> speed<00:02:56.580> up<00:02:56.879> the 00:02:57.290 --> 00:02:57.300 align:start position:0% they don't know how to speed up the 00:02:57.300 --> 00:02:59.270 align:start position:0% they don't know how to speed up the transition<00:02:57.780> when<00:02:58.080> the<00:02:58.319> transaction<00:02:58.739> is<00:02:58.980> get 00:02:59.270 --> 00:02:59.280 align:start position:0% transition when the transaction is get 00:02:59.280 --> 00:03:01.670 align:start position:0% transition when the transaction is get stuck<00:02:59.640> for<00:03:00.180> those<00:03:00.540> questions<00:03:00.840> so<00:03:01.200> we<00:03:01.379> need<00:03:01.560> to 00:03:01.670 --> 00:03:01.680 align:start position:0% stuck for those questions so we need to 00:03:01.680 --> 00:03:04.070 align:start position:0% stuck for those questions so we need to come<00:03:01.860> up<00:03:02.040> with<00:03:02.220> some<00:03:02.519> solution<00:03:02.940> for<00:03:03.900> the 00:03:04.070 --> 00:03:04.080 align:start position:0% come up with some solution for the 00:03:04.080 --> 00:03:07.070 align:start position:0% come up with some solution for the future<00:03:04.200> one<00:03:04.500> is<00:03:04.739> how<00:03:04.980> do<00:03:05.160> we<00:03:05.340> fix<00:03:05.580> it<00:03:05.819> so<00:03:06.180> if<00:03:06.900> we 00:03:07.070 --> 00:03:07.080 align:start position:0% future one is how do we fix it so if we 00:03:07.080 --> 00:03:09.110 align:start position:0% future one is how do we fix it so if we want<00:03:07.260> to<00:03:07.440> make<00:03:07.680> the<00:03:07.920> message<00:03:08.340> adoption<00:03:08.879> to 00:03:09.110 --> 00:03:09.120 align:start position:0% want to make the message adoption to 00:03:09.120 --> 00:03:11.570 align:start position:0% want to make the message adoption to happen<00:03:09.300> crypto<00:03:09.840> wallet<00:03:10.260> is<00:03:10.319> a<00:03:10.680> important 00:03:11.570 --> 00:03:11.580 align:start position:0% happen crypto wallet is a important 00:03:11.580 --> 00:03:14.390 align:start position:0% happen crypto wallet is a important entry<00:03:12.060> point<00:03:12.239> for<00:03:13.080> Android<00:03:13.319> website<00:03:14.040> users 00:03:14.390 --> 00:03:14.400 align:start position:0% entry point for Android website users 00:03:14.400 --> 00:03:17.210 align:start position:0% entry point for Android website users yeah<00:03:14.879> so<00:03:15.180> we<00:03:15.360> need<00:03:15.540> to<00:03:15.659> fix<00:03:15.900> it<00:03:16.140> so<00:03:16.500> how<00:03:16.680> to<00:03:17.040> fix 00:03:17.210 --> 00:03:17.220 align:start position:0% yeah so we need to fix it so how to fix 00:03:17.220 --> 00:03:18.530 align:start position:0% yeah so we need to fix it so how to fix it 00:03:18.530 --> 00:03:18.540 align:start position:0% it 00:03:18.540 --> 00:03:21.530 align:start position:0% it so<00:03:18.959> let's<00:03:19.140> recap<00:03:19.620> it<00:03:19.920> again<00:03:20.159> so<00:03:20.940> if<00:03:21.239> you<00:03:21.360> want 00:03:21.530 --> 00:03:21.540 align:start position:0% so let's recap it again so if you want 00:03:21.540 --> 00:03:23.750 align:start position:0% so let's recap it again so if you want to<00:03:21.659> rebuild<00:03:22.019> a<00:03:22.260> wallet<00:03:22.620> then<00:03:22.800> when<00:03:23.040> you<00:03:23.280> when 00:03:23.750 --> 00:03:23.760 align:start position:0% to rebuild a wallet then when you when 00:03:23.760 --> 00:03:27.350 align:start position:0% to rebuild a wallet then when you when we<00:03:24.120> need<00:03:24.300> to<00:03:24.420> know<00:03:24.659> what<00:03:25.080> the<00:03:25.440> uh<00:03:26.220> future<00:03:27.060> what 00:03:27.350 --> 00:03:27.360 align:start position:0% we need to know what the uh future what 00:03:27.360 --> 00:03:31.790 align:start position:0% we need to know what the uh future what it<00:03:27.659> looks<00:03:27.959> like<00:03:28.560> so<00:03:29.599> uh<00:03:30.599> this<00:03:30.900> is<00:03:31.080> a<00:03:31.260> very<00:03:31.440> I 00:03:31.790 --> 00:03:31.800 align:start position:0% it looks like so uh this is a very I 00:03:31.800 --> 00:03:33.949 align:start position:0% it looks like so uh this is a very I mean<00:03:31.980> very<00:03:32.280> quick<00:03:32.519> question<00:03:32.700> because<00:03:33.120> if<00:03:33.840> you 00:03:33.949 --> 00:03:33.959 align:start position:0% mean very quick question because if you 00:03:33.959 --> 00:03:35.750 align:start position:0% mean very quick question because if you think<00:03:34.140> about<00:03:34.379> a<00:03:34.739> smart<00:03:34.920> contract<00:03:35.280> developer 00:03:35.750 --> 00:03:35.760 align:start position:0% think about a smart contract developer 00:03:35.760 --> 00:03:39.890 align:start position:0% think about a smart contract developer in<00:03:36.060> 2018<00:03:36.300> or<00:03:36.959> 2019<00:03:37.739> at<00:03:38.580> that<00:03:38.819> moment<00:03:39.239> because 00:03:39.890 --> 00:03:39.900 align:start position:0% in 2018 or 2019 at that moment because 00:03:39.900 --> 00:03:42.470 align:start position:0% in 2018 or 2019 at that moment because they<00:03:40.620> didn't<00:03:40.860> sense<00:03:41.459> or<00:03:41.700> they<00:03:42.000> didn't<00:03:42.180> know 00:03:42.470 --> 00:03:42.480 align:start position:0% they didn't sense or they didn't know 00:03:42.480 --> 00:03:44.990 align:start position:0% they didn't sense or they didn't know there<00:03:42.780> is<00:03:42.959> a<00:03:43.140> kind<00:03:43.379> of<00:03:43.560> attack<00:03:44.099> called<00:03:44.459> ndv 00:03:44.990 --> 00:03:45.000 align:start position:0% there is a kind of attack called ndv 00:03:45.000 --> 00:03:48.530 align:start position:0% there is a kind of attack called ndv attack<00:03:45.180> so<00:03:46.080> when<00:03:46.319> you<00:03:46.560> uh<00:03:47.340> when<00:03:47.700> you<00:03:47.879> design<00:03:48.239> a 00:03:48.530 --> 00:03:48.540 align:start position:0% attack so when you uh when you design a 00:03:48.540 --> 00:03:51.170 align:start position:0% attack so when you uh when you design a smart<00:03:48.659> contract<00:03:49.080> at<00:03:49.260> late<00:03:49.560> time<00:03:50.180> eventually 00:03:51.170 --> 00:03:51.180 align:start position:0% smart contract at late time eventually 00:03:51.180 --> 00:03:52.789 align:start position:0% smart contract at late time eventually you<00:03:51.599> will 00:03:52.789 --> 00:03:52.799 align:start position:0% you will 00:03:52.799 --> 00:03:55.490 align:start position:0% you will you're<00:03:53.400> really<00:03:53.640> hard<00:03:53.940> to<00:03:54.120> defense<00:03:54.540> uh<00:03:55.019> MVD 00:03:55.490 --> 00:03:55.500 align:start position:0% you're really hard to defense uh MVD 00:03:55.500 --> 00:03:58.130 align:start position:0% you're really hard to defense uh MVD anyv<00:03:56.220> attack<00:03:56.459> so<00:03:57.120> that's<00:03:57.239> why<00:03:57.599> we<00:03:57.840> need<00:03:58.019> to 00:03:58.130 --> 00:03:58.140 align:start position:0% anyv attack so that's why we need to 00:03:58.140 --> 00:04:00.170 align:start position:0% anyv attack so that's why we need to know<00:03:58.379> what<00:03:58.860> is<00:03:59.040> the<00:03:59.159> future<00:03:59.280> and<00:03:59.580> we<00:03:59.940> need<00:04:00.060> to 00:04:00.170 --> 00:04:00.180 align:start position:0% know what is the future and we need to 00:04:00.180 --> 00:04:02.570 align:start position:0% know what is the future and we need to know<00:04:00.299> how<00:04:00.420> to<00:04:00.599> design<00:04:00.720> the<00:04:01.080> wallet<00:04:01.799> and<00:04:02.459> so 00:04:02.570 --> 00:04:02.580 align:start position:0% know how to design the wallet and so 00:04:02.580 --> 00:04:04.250 align:start position:0% know how to design the wallet and so this<00:04:02.819> is<00:04:03.060> a<00:04:03.239> reason<00:04:03.420> this<00:04:03.780> topic<00:04:04.080> called 00:04:04.250 --> 00:04:04.260 align:start position:0% this is a reason this topic called 00:04:04.260 --> 00:04:07.009 align:start position:0% this is a reason this topic called possible<00:04:04.739> are<00:04:05.159> merge<00:04:05.519> wallet<00:04:05.819> so<00:04:06.299> let's<00:04:06.540> look 00:04:07.009 --> 00:04:07.019 align:start position:0% possible are merge wallet so let's look 00:04:07.019 --> 00:04:09.589 align:start position:0% possible are merge wallet so let's look at<00:04:07.200> the<00:04:07.500> future<00:04:07.680> the<00:04:08.580> concept<00:04:08.879> of<00:04:09.060> the<00:04:09.180> endgame 00:04:09.589 --> 00:04:09.599 align:start position:0% at the future the concept of the endgame 00:04:09.599 --> 00:04:13.550 align:start position:0% at the future the concept of the endgame is<00:04:09.840> proposed<00:04:10.319> by<00:04:10.439> vitalica<00:04:10.920> in<00:04:11.239> 2021<00:04:12.560> actually 00:04:13.550 --> 00:04:13.560 align:start position:0% is proposed by vitalica in 2021 actually 00:04:13.560 --> 00:04:15.830 align:start position:0% is proposed by vitalica in 2021 actually it's<00:04:14.099> uh<00:04:14.340> the<00:04:14.580> goal<00:04:14.879> is<00:04:15.000> to<00:04:15.239> scaling<00:04:15.720> the 00:04:15.830 --> 00:04:15.840 align:start position:0% it's uh the goal is to scaling the 00:04:15.840 --> 00:04:18.409 align:start position:0% it's uh the goal is to scaling the ethereum<00:04:16.260> for<00:04:16.440> many<00:04:16.620> users<00:04:17.100> so<00:04:17.579> we<00:04:17.820> can<00:04:18.000> come 00:04:18.409 --> 00:04:18.419 align:start position:0% ethereum for many users so we can come 00:04:18.419 --> 00:04:20.569 align:start position:0% ethereum for many users so we can come uh<00:04:18.900> we<00:04:19.139> can<00:04:19.260> onboard<00:04:19.620> more<00:04:19.859> users<00:04:20.220> to<00:04:20.400> the 00:04:20.569 --> 00:04:20.579 align:start position:0% uh we can onboard more users to the 00:04:20.579 --> 00:04:23.930 align:start position:0% uh we can onboard more users to the Syrian<00:04:20.940> ecosystem<00:04:21.359> for<00:04:21.900> the<00:04:22.139> in-game<00:04:22.620> uh 00:04:23.930 --> 00:04:23.940 align:start position:0% Syrian ecosystem for the in-game uh 00:04:23.940 --> 00:04:29.090 align:start position:0% Syrian ecosystem for the in-game uh is<00:04:24.600> uh<00:04:25.199> in<00:04:25.740> in<00:04:25.979> the<00:04:26.220> article<00:04:26.580> that<00:04:27.000> vitalika 00:04:29.090 --> 00:04:29.100 align:start position:0% is uh in in the article that vitalika 00:04:29.100 --> 00:04:32.210 align:start position:0% is uh in in the article that vitalika mentioned<00:04:29.940> it<00:04:30.419> is<00:04:30.660> private<00:04:31.500> into<00:04:31.620> a<00:04:31.979> lower 00:04:32.210 --> 00:04:32.220 align:start position:0% mentioned it is private into a lower 00:04:32.220 --> 00:04:35.930 align:start position:0% mentioned it is private into a lower solution<00:04:32.820> uh<00:04:33.840> uh<00:04:34.020> Centric<00:04:34.500> low<00:04:35.040> map<00:04:35.340> what<00:04:35.820> does 00:04:35.930 --> 00:04:35.940 align:start position:0% solution uh uh Centric low map what does 00:04:35.940 --> 00:04:38.810 align:start position:0% solution uh uh Centric low map what does this<00:04:36.120> mean<00:04:36.479> it<00:04:37.080> means<00:04:37.259> we<00:04:37.500> can<00:04:37.680> we<00:04:37.979> uh<00:04:38.340> today<00:04:38.520> we 00:04:38.810 --> 00:04:38.820 align:start position:0% this mean it means we can we uh today we 00:04:38.820 --> 00:04:40.610 align:start position:0% this mean it means we can we uh today we have<00:04:39.000> already<00:04:39.180> seen<00:04:39.540> lots<00:04:40.020> of<00:04:40.080> layer<00:04:40.500> 2 00:04:40.610 --> 00:04:40.620 align:start position:0% have already seen lots of layer 2 00:04:40.620 --> 00:04:43.370 align:start position:0% have already seen lots of layer 2 Solutions<00:04:41.160> coming<00:04:41.580> up<00:04:41.880> just<00:04:42.540> like<00:04:42.720> star<00:04:43.139> net 00:04:43.370 --> 00:04:43.380 align:start position:0% Solutions coming up just like star net 00:04:43.380 --> 00:04:47.330 align:start position:0% Solutions coming up just like star net uh<00:04:44.220> Edge<00:04:44.520> Tech<00:04:44.780> uptrunk<00:04:45.780> or<00:04:46.020> optimism<00:04:46.500> since 00:04:47.330 --> 00:04:47.340 align:start position:0% uh Edge Tech uptrunk or optimism since 00:04:47.340 --> 00:04:50.510 align:start position:0% uh Edge Tech uptrunk or optimism since uh<00:04:47.880> if<00:04:48.300> the<00:04:48.540> layer<00:04:48.900> 2<00:04:49.020> is<00:04:49.380> the<00:04:49.560> future<00:04:49.860> that 00:04:50.510 --> 00:04:50.520 align:start position:0% uh if the layer 2 is the future that 00:04:50.520 --> 00:04:53.210 align:start position:0% uh if the layer 2 is the future that means<00:04:50.940> we<00:04:51.479> need<00:04:51.720> to<00:04:51.840> have<00:04:52.139> more<00:04:52.560> data<00:04:53.040> space 00:04:53.210 --> 00:04:53.220 align:start position:0% means we need to have more data space 00:04:53.220 --> 00:04:56.629 align:start position:0% means we need to have more data space for<00:04:53.940> the<00:04:54.120> load<00:04:54.419> up<00:04:54.540> so<00:04:55.320> how<00:04:55.560> do<00:04:55.800> we<00:04:55.979> have<00:04:56.400> more 00:04:56.629 --> 00:04:56.639 align:start position:0% for the load up so how do we have more 00:04:56.639 --> 00:04:59.330 align:start position:0% for the load up so how do we have more data<00:04:57.120> on<00:04:57.360> the<00:04:57.479> raw<00:04:57.720> up<00:04:57.900> so<00:04:58.500> here<00:04:58.740> are<00:04:58.919> two<00:04:59.100> ways 00:04:59.330 --> 00:04:59.340 align:start position:0% data on the raw up so here are two ways 00:04:59.340 --> 00:05:01.909 align:start position:0% data on the raw up so here are two ways we<00:04:59.520> can<00:04:59.699> do<00:04:59.880> that<00:05:00.060> so<00:05:00.660> first<00:05:00.900> we<00:05:01.380> need<00:05:01.560> to<00:05:01.680> have 00:05:01.909 --> 00:05:01.919 align:start position:0% we can do that so first we need to have 00:05:01.919 --> 00:05:05.090 align:start position:0% we can do that so first we need to have more<00:05:02.280> large<00:05:03.060> get<00:05:03.300> more<00:05:03.600> larger<00:05:03.960> block 00:05:05.090 --> 00:05:05.100 align:start position:0% more large get more larger block 00:05:05.100 --> 00:05:08.570 align:start position:0% more large get more larger block and<00:05:06.000> the<00:05:06.540> block<00:05:07.020> need<00:05:07.380> to<00:05:07.560> be<00:05:07.740> verified<00:05:08.100> very 00:05:08.570 --> 00:05:08.580 align:start position:0% and the block need to be verified very 00:05:08.580 --> 00:05:11.390 align:start position:0% and the block need to be verified very easily<00:05:09.060> for<00:05:09.419> the<00:05:09.660> line<00:05:09.840> client<00:05:10.259> if<00:05:10.740> we<00:05:10.919> can<00:05:11.160> do 00:05:11.390 --> 00:05:11.400 align:start position:0% easily for the line client if we can do 00:05:11.400 --> 00:05:14.330 align:start position:0% easily for the line client if we can do so<00:05:11.580> then<00:05:12.300> we<00:05:12.900> can<00:05:13.020> have<00:05:13.199> a<00:05:13.380> large<00:05:13.500> block<00:05:13.800> and 00:05:14.330 --> 00:05:14.340 align:start position:0% so then we can have a large block and 00:05:14.340 --> 00:05:17.990 align:start position:0% so then we can have a large block and that<00:05:14.520> is<00:05:14.820> what<00:05:15.120> then<00:05:15.660> charting<00:05:16.259> uh<00:05:16.919> doing 00:05:17.990 --> 00:05:18.000 align:start position:0% that is what then charting uh doing 00:05:18.000 --> 00:05:21.469 align:start position:0% that is what then charting uh doing and<00:05:18.419> another<00:05:18.600> approach<00:05:19.440> to<00:05:19.919> to<00:05:20.460> do<00:05:20.820> this<00:05:21.060> is 00:05:21.469 --> 00:05:21.479 align:start position:0% and another approach to to do this is 00:05:21.479 --> 00:05:24.770 align:start position:0% and another approach to to do this is how<00:05:22.020> do<00:05:22.199> we<00:05:22.380> make<00:05:22.620> the<00:05:22.860> data<00:05:23.280> smaller<00:05:23.820> if<00:05:24.660> we 00:05:24.770 --> 00:05:24.780 align:start position:0% how do we make the data smaller if we 00:05:24.780 --> 00:05:27.350 align:start position:0% how do we make the data smaller if we can<00:05:25.020> make<00:05:25.259> each<00:05:26.039> load<00:05:26.639> of<00:05:26.759> transactions 00:05:27.350 --> 00:05:27.360 align:start position:0% can make each load of transactions 00:05:27.360 --> 00:05:30.230 align:start position:0% can make each load of transactions smaller<00:05:27.840> then<00:05:28.199> it<00:05:28.500> could<00:05:28.740> fit<00:05:29.100> into<00:05:29.820> the 00:05:30.230 --> 00:05:30.240 align:start position:0% smaller then it could fit into the 00:05:30.240 --> 00:05:32.570 align:start position:0% smaller then it could fit into the bigger<00:05:30.900> block<00:05:31.020> then<00:05:31.440> that<00:05:31.680> means<00:05:31.919> we<00:05:32.160> can<00:05:32.340> get 00:05:32.570 --> 00:05:32.580 align:start position:0% bigger block then that means we can get 00:05:32.580 --> 00:05:35.330 align:start position:0% bigger block then that means we can get a<00:05:33.060> lot<00:05:33.180> of<00:05:33.360> I<00:05:33.660> mean<00:05:33.840> transaction<00:05:34.259> get<00:05:34.860> into<00:05:35.100> the 00:05:35.330 --> 00:05:35.340 align:start position:0% a lot of I mean transaction get into the 00:05:35.340 --> 00:05:37.010 align:start position:0% a lot of I mean transaction get into the block 00:05:37.010 --> 00:05:37.020 align:start position:0% block 00:05:37.020 --> 00:05:39.770 align:start position:0% block so<00:05:37.740> in<00:05:38.220> the<00:05:38.280> future<00:05:38.460> ideally<00:05:39.000> we<00:05:39.360> think<00:05:39.539> that 00:05:39.770 --> 00:05:39.780 align:start position:0% so in the future ideally we think that 00:05:39.780 --> 00:05:43.670 align:start position:0% so in the future ideally we think that there<00:05:40.080> might<00:05:40.320> be<00:05:40.440> a<00:05:40.800> high<00:05:41.100> TPS<00:05:41.520> with<00:05:42.360> a<00:05:42.660> low<00:05:43.080> fee 00:05:43.670 --> 00:05:43.680 align:start position:0% there might be a high TPS with a low fee 00:05:43.680 --> 00:05:46.310 align:start position:0% there might be a high TPS with a low fee transaction<00:05:44.280> fee<00:05:44.580> into<00:05:45.479> the<00:05:45.720> bar<00:05:45.960> trans 00:05:46.310 --> 00:05:46.320 align:start position:0% transaction fee into the bar trans 00:05:46.320 --> 00:05:47.510 align:start position:0% transaction fee into the bar trans system 00:05:47.510 --> 00:05:47.520 align:start position:0% system 00:05:47.520 --> 00:05:50.270 align:start position:0% system this<00:05:48.000> is<00:05:48.180> important<00:05:48.780> because<00:05:49.440> if<00:05:49.979> we<00:05:50.100> look 00:05:50.270 --> 00:05:50.280 align:start position:0% this is important because if we look 00:05:50.280 --> 00:05:53.990 align:start position:0% this is important because if we look back<00:05:50.580> at<00:05:51.300> the<00:05:51.479> history<00:05:51.720> of<00:05:52.139> the<00:05:52.320> internet 00:05:53.990 --> 00:05:54.000 align:start position:0% back at the history of the internet 00:05:54.000 --> 00:05:55.909 align:start position:0% back at the history of the internet then<00:05:54.419> we<00:05:54.600> will<00:05:54.780> find<00:05:55.020> this<00:05:55.380> is<00:05:55.500> a<00:05:55.680> kind<00:05:55.800> of 00:05:55.909 --> 00:05:55.919 align:start position:0% then we will find this is a kind of 00:05:55.919 --> 00:05:57.110 align:start position:0% then we will find this is a kind of similar 00:05:57.110 --> 00:05:57.120 align:start position:0% similar 00:05:57.120 --> 00:05:59.870 align:start position:0% similar so<00:05:57.539> when<00:05:57.720> the<00:05:57.960> internet<00:05:58.139> was<00:05:58.560> formed<00:05:59.039> the 00:05:59.870 --> 00:05:59.880 align:start position:0% so when the internet was formed the 00:05:59.880 --> 00:06:03.469 align:start position:0% so when the internet was formed the bandwidth<00:06:00.419> is<00:06:00.600> a<00:06:01.139> synchronized<00:06:01.979> resource<00:06:02.699> and 00:06:03.469 --> 00:06:03.479 align:start position:0% bandwidth is a synchronized resource and 00:06:03.479 --> 00:06:06.590 align:start position:0% bandwidth is a synchronized resource and it<00:06:03.780> is<00:06:04.020> very<00:06:04.320> expensive<00:06:05.160> not<00:06:06.000> and<00:06:06.300> everyone 00:06:06.590 --> 00:06:06.600 align:start position:0% it is very expensive not and everyone 00:06:06.600 --> 00:06:09.409 align:start position:0% it is very expensive not and everyone can<00:06:06.960> afford<00:06:07.440> to<00:06:07.860> the<00:06:08.100> internet 00:06:09.409 --> 00:06:09.419 align:start position:0% can afford to the internet 00:06:09.419 --> 00:06:12.170 align:start position:0% can afford to the internet with<00:06:10.080> the<00:06:10.320> cost<00:06:10.500> decreasing<00:06:11.160> then<00:06:11.520> we<00:06:11.880> can<00:06:12.000> see 00:06:12.170 --> 00:06:12.180 align:start position:0% with the cost decreasing then we can see 00:06:12.180 --> 00:06:15.230 align:start position:0% with the cost decreasing then we can see many<00:06:12.539> of<00:06:12.780> many<00:06:13.380> applications<00:06:13.919> start<00:06:14.340> to<00:06:14.940> going 00:06:15.230 --> 00:06:15.240 align:start position:0% many of many applications start to going 00:06:15.240 --> 00:06:17.150 align:start position:0% many of many applications start to going on<00:06:16.199> the<00:06:16.320> internet 00:06:17.150 --> 00:06:17.160 align:start position:0% on the internet 00:06:17.160 --> 00:06:21.770 align:start position:0% on the internet so<00:06:17.699> if<00:06:17.880> you<00:06:18.539> if<00:06:18.960> it<00:06:19.139> was<00:06:19.380> in<00:06:19.860> 1998<00:06:20.639> you<00:06:21.539> probably 00:06:21.770 --> 00:06:21.780 align:start position:0% so if you if it was in 1998 you probably 00:06:21.780 --> 00:06:23.990 align:start position:0% so if you if it was in 1998 you probably don't<00:06:22.139> think<00:06:22.380> about<00:06:22.620> what<00:06:23.100> is<00:06:23.280> YouTube<00:06:23.520> what 00:06:23.990 --> 00:06:24.000 align:start position:0% don't think about what is YouTube what 00:06:24.000 --> 00:06:27.950 align:start position:0% don't think about what is YouTube what is<00:06:24.180> Netflix<00:06:24.419> but<00:06:25.259> if<00:06:25.560> you<00:06:25.740> are<00:06:25.979> in<00:06:26.340> uh<00:06:26.759> 2020<00:06:27.600> or 00:06:27.950 --> 00:06:27.960 align:start position:0% is Netflix but if you are in uh 2020 or 00:06:27.960 --> 00:06:29.110 align:start position:0% is Netflix but if you are in uh 2020 or into 00:06:29.110 --> 00:06:29.120 align:start position:0% into 00:06:29.120 --> 00:06:32.629 align:start position:0% into 2000<00:06:30.120> 2022<00:06:30.780> then 00:06:32.629 --> 00:06:32.639 align:start position:0% 2000 2022 then 00:06:32.639 --> 00:06:36.290 align:start position:0% 2000 2022 then you<00:06:33.060> uh<00:06:33.900> you<00:06:34.500> might<00:06:35.100> think<00:06:35.280> Netflix<00:06:35.639> it<00:06:36.120> makes 00:06:36.290 --> 00:06:36.300 align:start position:0% you uh you might think Netflix it makes 00:06:36.300 --> 00:06:40.309 align:start position:0% you uh you might think Netflix it makes sense<00:06:36.539> we<00:06:37.380> can<00:06:37.560> have<00:06:37.740> more<00:06:38.039> uh<00:06:38.900> uh<00:06:39.900> online 00:06:40.309 --> 00:06:40.319 align:start position:0% sense we can have more uh uh online 00:06:40.319 --> 00:06:42.830 align:start position:0% sense we can have more uh uh online video<00:06:40.740> with<00:06:41.460> cheaper<00:06:41.940> transaction<00:06:42.300> fee<00:06:42.660> we 00:06:42.830 --> 00:06:42.840 align:start position:0% video with cheaper transaction fee we 00:06:42.840 --> 00:06:45.529 align:start position:0% video with cheaper transaction fee we can<00:06:43.020> do<00:06:43.199> Morphine<00:06:43.740> not<00:06:44.280> just<00:06:44.460> Define<00:06:44.819> not<00:06:45.360> just 00:06:45.529 --> 00:06:45.539 align:start position:0% can do Morphine not just Define not just 00:06:45.539 --> 00:06:48.610 align:start position:0% can do Morphine not just Define not just nft<00:06:46.380> we<00:06:46.800> can<00:06:46.979> do<00:06:47.160> lots<00:06:47.819> of 00:06:48.610 --> 00:06:48.620 align:start position:0% nft we can do lots of 00:06:48.620 --> 00:06:52.249 align:start position:0% nft we can do lots of potential<00:06:49.620> application<00:06:50.520> in<00:06:50.880> the<00:06:51.000> market<00:06:51.259> so 00:06:52.249 --> 00:06:52.259 align:start position:0% potential application in the market so 00:06:52.259 --> 00:06:55.309 align:start position:0% potential application in the market so yeah<00:06:52.800> let's<00:06:53.280> let's<00:06:54.000> think<00:06:54.300> about<00:06:54.479> how<00:06:54.960> do<00:06:55.139> we 00:06:55.309 --> 00:06:55.319 align:start position:0% yeah let's let's think about how do we 00:06:55.319 --> 00:06:57.710 align:start position:0% yeah let's let's think about how do we make<00:06:55.620> the<00:06:55.860> world<00:06:56.220> better<00:06:56.639> so<00:06:57.120> we<00:06:57.360> can<00:06:57.479> have 00:06:57.710 --> 00:06:57.720 align:start position:0% make the world better so we can have 00:06:57.720 --> 00:07:00.590 align:start position:0% make the world better so we can have more<00:06:58.199> application<00:06:58.979> uh<00:06:59.759> on<00:06:59.940> board<00:07:00.120> into<00:07:00.360> the 00:07:00.590 --> 00:07:00.600 align:start position:0% more application uh on board into the 00:07:00.600 --> 00:07:02.749 align:start position:0% more application uh on board into the Ethereal<00:07:01.259> ecosystem 00:07:02.749 --> 00:07:02.759 align:start position:0% Ethereal ecosystem 00:07:02.759 --> 00:07:05.629 align:start position:0% Ethereal ecosystem so<00:07:03.600> yeah<00:07:03.960> we<00:07:04.259> need<00:07:04.440> to<00:07:04.560> have<00:07:04.800> a<00:07:05.039> wallet<00:07:05.460> which 00:07:05.629 --> 00:07:05.639 align:start position:0% so yeah we need to have a wallet which 00:07:05.639 --> 00:07:08.450 align:start position:0% so yeah we need to have a wallet which fits<00:07:06.120> a<00:07:06.240> lot<00:07:06.360> layer<00:07:07.020> 2<00:07:07.139> door<00:07:07.319> mat<00:07:07.560> and<00:07:08.160> there<00:07:08.340> is 00:07:08.450 --> 00:07:08.460 align:start position:0% fits a lot layer 2 door mat and there is 00:07:08.460 --> 00:07:11.270 align:start position:0% fits a lot layer 2 door mat and there is user<00:07:09.240> is<00:07:09.360> friendly<00:07:09.840> here<00:07:10.380> I<00:07:10.560> want<00:07:10.680> to<00:07:10.860> give<00:07:11.100> you 00:07:11.270 --> 00:07:11.280 align:start position:0% user is friendly here I want to give you 00:07:11.280 --> 00:07:14.330 align:start position:0% user is friendly here I want to give you a<00:07:11.580> very<00:07:11.699> brief<00:07:12.120> short<00:07:12.360> summary<00:07:12.780> so<00:07:13.380> first<00:07:13.800> it's 00:07:14.330 --> 00:07:14.340 align:start position:0% a very brief short summary so first it's 00:07:14.340 --> 00:07:16.070 align:start position:0% a very brief short summary so first it's really<00:07:14.580> hard<00:07:14.819> for<00:07:15.000> the<00:07:15.180> general<00:07:15.360> users<00:07:15.900> to 00:07:16.070 --> 00:07:16.080 align:start position:0% really hard for the general users to 00:07:16.080 --> 00:07:18.110 align:start position:0% really hard for the general users to know<00:07:16.259> what<00:07:16.680> is<00:07:16.860> crypto<00:07:17.160> what's<00:07:17.400> easier<00:07:17.880> and 00:07:18.110 --> 00:07:18.120 align:start position:0% know what is crypto what's easier and 00:07:18.120 --> 00:07:20.870 align:start position:0% know what is crypto what's easier and think<00:07:18.780> about<00:07:18.960> it<00:07:19.380> if<00:07:19.919> you<00:07:20.039> want<00:07:20.280> to<00:07:20.400> teach<00:07:20.639> your 00:07:20.870 --> 00:07:20.880 align:start position:0% think about it if you want to teach your 00:07:20.880 --> 00:07:23.210 align:start position:0% think about it if you want to teach your parents<00:07:21.300> to<00:07:21.599> set<00:07:21.780> up<00:07:21.960> awarded<00:07:22.500> the<00:07:23.039> first 00:07:23.210 --> 00:07:23.220 align:start position:0% parents to set up awarded the first 00:07:23.220 --> 00:07:25.070 align:start position:0% parents to set up awarded the first thing<00:07:23.400> the<00:07:23.880> first<00:07:24.060> thing<00:07:24.240> is<00:07:24.539> they<00:07:24.780> need<00:07:25.020> to 00:07:25.070 --> 00:07:25.080 align:start position:0% thing the first thing is they need to 00:07:25.080 --> 00:07:27.469 align:start position:0% thing the first thing is they need to write<00:07:25.319> up<00:07:25.560> the<00:07:25.919> difference<00:07:26.400> so<00:07:27.120> what<00:07:27.300> is 00:07:27.469 --> 00:07:27.479 align:start position:0% write up the difference so what is 00:07:27.479 --> 00:07:30.110 align:start position:0% write up the difference so what is difference<00:07:27.840> yeah<00:07:28.620> it's<00:07:28.919> difficult<00:07:29.400> to 00:07:30.110 --> 00:07:30.120 align:start position:0% difference yeah it's difficult to 00:07:30.120 --> 00:07:34.670 align:start position:0% difference yeah it's difficult to understand<00:07:30.259> and<00:07:31.259> then<00:07:31.440> next<00:07:31.740> they<00:07:32.520> need<00:07:32.819> to<00:07:33.000> uh 00:07:34.670 --> 00:07:34.680 align:start position:0% understand and then next they need to uh 00:07:34.680 --> 00:07:37.070 align:start position:0% understand and then next they need to uh if<00:07:35.160> they<00:07:35.460> want<00:07:35.639> to<00:07:35.759> send<00:07:36.060> some<00:07:36.300> token<00:07:36.840> then 00:07:37.070 --> 00:07:37.080 align:start position:0% if they want to send some token then 00:07:37.080 --> 00:07:39.529 align:start position:0% if they want to send some token then they<00:07:37.319> need<00:07:37.560> to<00:07:37.680> have<00:07:37.860> some<00:07:38.099> easer<00:07:38.580> so<00:07:39.180> this<00:07:39.419> is 00:07:39.529 --> 00:07:39.539 align:start position:0% they need to have some easer so this is 00:07:39.539 --> 00:07:41.749 align:start position:0% they need to have some easer so this is another<00:07:39.780> thing<00:07:40.139> that<00:07:40.620> uh 00:07:41.749 --> 00:07:41.759 align:start position:0% another thing that uh 00:07:41.759 --> 00:07:44.350 align:start position:0% another thing that uh quite<00:07:42.300> quite<00:07:42.599> challenging<00:07:43.020> for<00:07:43.139> them<00:07:43.380> because 00:07:44.350 --> 00:07:44.360 align:start position:0% quite quite challenging for them because 00:07:44.360 --> 00:07:48.730 align:start position:0% quite quite challenging for them because what<00:07:45.360> this<00:07:45.780> cannot<00:07:46.400> make<00:07:47.400> a<00:07:47.639> trans<00:07:47.880> transfer 00:07:48.730 --> 00:07:48.740 align:start position:0% what this cannot make a trans transfer 00:07:48.740 --> 00:07:52.010 align:start position:0% what this cannot make a trans transfer unless<00:07:49.740> I<00:07:50.039> got<00:07:50.220> some<00:07:50.400> easers<00:07:51.419> the<00:07:51.900> second 00:07:52.010 --> 00:07:52.020 align:start position:0% unless I got some easers the second 00:07:52.020 --> 00:07:53.990 align:start position:0% unless I got some easers the second thing<00:07:52.259> is<00:07:52.560> the<00:07:52.740> user<00:07:53.039> experience<00:07:53.340> is<00:07:53.639> pretty 00:07:53.990 --> 00:07:54.000 align:start position:0% thing is the user experience is pretty 00:07:54.000 --> 00:07:56.809 align:start position:0% thing is the user experience is pretty uh<00:07:54.419> bad<00:07:54.720> now 00:07:56.809 --> 00:07:56.819 align:start position:0% uh bad now 00:07:56.819 --> 00:07:57.830 align:start position:0% uh bad now um 00:07:57.830 --> 00:07:57.840 align:start position:0% um 00:07:57.840 --> 00:07:59.570 align:start position:0% um because 00:07:59.570 --> 00:07:59.580 align:start position:0% because 00:07:59.580 --> 00:08:02.270 align:start position:0% because I<00:08:00.060> think<00:08:00.419> because<00:08:00.780> the<00:08:01.080> learning<00:08:01.440> curve<00:08:01.680> is<00:08:01.860> is 00:08:02.270 --> 00:08:02.280 align:start position:0% I think because the learning curve is is 00:08:02.280 --> 00:08:04.670 align:start position:0% I think because the learning curve is is pretty<00:08:02.580> high<00:08:02.880> so<00:08:03.599> most<00:08:03.840> of<00:08:04.020> the<00:08:04.080> users<00:08:04.440> don't 00:08:04.670 --> 00:08:04.680 align:start position:0% pretty high so most of the users don't 00:08:04.680 --> 00:08:08.809 align:start position:0% pretty high so most of the users don't know<00:08:04.860> how<00:08:05.099> to<00:08:05.220> I<00:08:05.460> mean<00:08:05.720> run<00:08:06.720> the<00:08:07.039> awarded<00:08:08.039> like 00:08:08.809 --> 00:08:08.819 align:start position:0% know how to I mean run the awarded like 00:08:08.819 --> 00:08:11.450 align:start position:0% know how to I mean run the awarded like how<00:08:09.240> do<00:08:09.360> I<00:08:09.539> interact<00:08:09.900> with<00:08:10.259> the<00:08:10.440> device<00:08:10.740> if 00:08:11.450 --> 00:08:11.460 align:start position:0% how do I interact with the device if 00:08:11.460 --> 00:08:13.430 align:start position:0% how do I interact with the device if there<00:08:11.699> is<00:08:11.880> a<00:08:12.120> new<00:08:12.240> application<00:08:12.780> how<00:08:13.080> do<00:08:13.259> I 00:08:13.430 --> 00:08:13.440 align:start position:0% there is a new application how do I 00:08:13.440 --> 00:08:15.409 align:start position:0% there is a new application how do I access<00:08:13.740> the<00:08:14.099> application<00:08:14.580> they<00:08:15.060> need<00:08:15.300> to 00:08:15.409 --> 00:08:15.419 align:start position:0% access the application they need to 00:08:15.419 --> 00:08:18.950 align:start position:0% access the application they need to learn<00:08:15.780> it<00:08:16.080> from<00:08:16.440> the<00:08:16.740> video<00:08:17.160> or<00:08:17.759> some<00:08:18.060> kind 00:08:18.950 --> 00:08:18.960 align:start position:0% learn it from the video or some kind 00:08:18.960 --> 00:08:22.430 align:start position:0% learn it from the video or some kind or<00:08:19.680> they<00:08:20.160> really<00:08:20.460> uh<00:08:21.180> or<00:08:21.780> it's<00:08:22.080> really<00:08:22.259> hard 00:08:22.430 --> 00:08:22.440 align:start position:0% or they really uh or it's really hard 00:08:22.440 --> 00:08:24.409 align:start position:0% or they really uh or it's really hard for<00:08:22.620> them<00:08:22.800> to<00:08:22.979> know<00:08:23.160> how<00:08:23.280> to<00:08:23.460> do<00:08:23.580> that<00:08:23.759> and 00:08:24.409 --> 00:08:24.419 align:start position:0% for them to know how to do that and 00:08:24.419 --> 00:08:27.290 align:start position:0% for them to know how to do that and third<00:08:24.599> uh<00:08:25.080> just<00:08:25.500> like<00:08:25.620> I<00:08:25.919> mentioned<00:08:26.280> uh<00:08:27.120> for 00:08:27.290 --> 00:08:27.300 align:start position:0% third uh just like I mentioned uh for 00:08:27.300 --> 00:08:29.809 align:start position:0% third uh just like I mentioned uh for now<00:08:27.479> we<00:08:27.780> have<00:08:27.960> already<00:08:28.139> have<00:08:28.440> some<00:08:28.680> users<00:08:29.099> but 00:08:29.809 --> 00:08:29.819 align:start position:0% now we have already have some users but 00:08:29.819 --> 00:08:31.790 align:start position:0% now we have already have some users but most<00:08:30.180> of<00:08:30.360> the<00:08:30.479> users<00:08:30.840> are<00:08:30.960> not<00:08:31.080> crypto<00:08:31.379> user 00:08:31.790 --> 00:08:31.800 align:start position:0% most of the users are not crypto user 00:08:31.800 --> 00:08:34.850 align:start position:0% most of the users are not crypto user they<00:08:32.039> are<00:08:32.459> just<00:08:32.760> general<00:08:33.300> users<00:08:33.899> and<00:08:34.620> because 00:08:34.850 --> 00:08:34.860 align:start position:0% they are just general users and because 00:08:34.860 --> 00:08:38.510 align:start position:0% they are just general users and because of<00:08:35.399> this<00:08:35.700> challenge<00:08:36.140> uh<00:08:37.140> they<00:08:37.860> are<00:08:37.979> they<00:08:38.399> are 00:08:38.510 --> 00:08:38.520 align:start position:0% of this challenge uh they are they are 00:08:38.520 --> 00:08:40.730 align:start position:0% of this challenge uh they are they are just<00:08:38.700> uh<00:08:39.120> state<00:08:39.419> with<00:08:39.779> the<00:08:40.020> centralized 00:08:40.730 --> 00:08:40.740 align:start position:0% just uh state with the centralized 00:08:40.740 --> 00:08:45.530 align:start position:0% just uh state with the centralized exchange<00:08:41.219> how<00:08:41.760> do<00:08:41.940> we<00:08:42.120> I<00:08:42.360> mean<00:08:43.020> try<00:08:43.620> to 00:08:45.530 --> 00:08:45.540 align:start position:0% exchange how do we I mean try to 00:08:45.540 --> 00:08:48.530 align:start position:0% exchange how do we I mean try to try<00:08:46.080> to<00:08:46.260> get<00:08:46.440> them<00:08:46.620> into<00:08:46.860> the<00:08:47.100> ecosystem<00:08:47.519> so<00:08:48.300> we 00:08:48.530 --> 00:08:48.540 align:start position:0% try to get them into the ecosystem so we 00:08:48.540 --> 00:08:50.690 align:start position:0% try to get them into the ecosystem so we need<00:08:48.839> to<00:08:48.959> have<00:08:49.140> a<00:08:49.320> layer<00:08:49.560> 2<00:08:49.680> ready<00:08:49.860> Wally<00:08:50.339> which 00:08:50.690 --> 00:08:50.700 align:start position:0% need to have a layer 2 ready Wally which 00:08:50.700 --> 00:08:52.910 align:start position:0% need to have a layer 2 ready Wally which is<00:08:50.820> designed<00:08:51.360> for<00:08:51.480> the<00:08:51.660> future<00:08:51.899> I<00:08:52.440> think<00:08:52.560> this 00:08:52.910 --> 00:08:52.920 align:start position:0% is designed for the future I think this 00:08:52.920 --> 00:08:55.550 align:start position:0% is designed for the future I think this is<00:08:53.040> a<00:08:53.160> very<00:08:53.279> big<00:08:53.519> thing<00:08:53.760> because<00:08:54.360> in<00:08:54.839> Defcon<00:08:55.320> we 00:08:55.550 --> 00:08:55.560 align:start position:0% is a very big thing because in Defcon we 00:08:55.560 --> 00:08:58.610 align:start position:0% is a very big thing because in Defcon we see<00:08:55.740> the<00:08:55.980> merge<00:08:56.339> is<00:08:56.519> already<00:08:57.240> finished<00:08:57.720> so<00:08:58.380> the 00:08:58.610 --> 00:08:58.620 align:start position:0% see the merge is already finished so the 00:08:58.620 --> 00:09:01.130 align:start position:0% see the merge is already finished so the layer<00:08:58.920> 2<00:08:59.040> is<00:08:59.279> if<00:08:59.519> layer<00:09:00.000> 2<00:09:00.060> is<00:09:00.240> the<00:09:00.360> feature<00:09:00.720> so 00:09:01.130 --> 00:09:01.140 align:start position:0% layer 2 is if layer 2 is the feature so 00:09:01.140 --> 00:09:03.530 align:start position:0% layer 2 is if layer 2 is the feature so we<00:09:01.320> need<00:09:01.500> to<00:09:01.740> start<00:09:02.220> to<00:09:02.399> thinking<00:09:02.820> about<00:09:02.940> what 00:09:03.530 --> 00:09:03.540 align:start position:0% we need to start to thinking about what 00:09:03.540 --> 00:09:06.590 align:start position:0% we need to start to thinking about what is<00:09:03.779> the<00:09:03.899> future<00:09:04.080> what<00:09:04.860> it<00:09:05.100> look<00:09:05.279> like 00:09:06.590 --> 00:09:06.600 align:start position:0% is the future what it look like 00:09:06.600 --> 00:09:11.030 align:start position:0% is the future what it look like Safari<00:09:07.500> is<00:09:07.740> a<00:09:08.040> requirement<00:09:09.019> we<00:09:10.019> think 00:09:11.030 --> 00:09:11.040 align:start position:0% Safari is a requirement we think 00:09:11.040 --> 00:09:14.090 align:start position:0% Safari is a requirement we think uh<00:09:11.760> ideal<00:09:12.360> what<00:09:12.600> it<00:09:12.839> should<00:09:12.959> have<00:09:13.200> it's<00:09:13.800> open 00:09:14.090 --> 00:09:14.100 align:start position:0% uh ideal what it should have it's open 00:09:14.100 --> 00:09:16.250 align:start position:0% uh ideal what it should have it's open for<00:09:14.399> I<00:09:14.580> mean<00:09:14.700> if<00:09:15.000> you<00:09:15.120> are<00:09:15.240> working<00:09:15.420> again<00:09:15.899> if 00:09:16.250 --> 00:09:16.260 align:start position:0% for I mean if you are working again if 00:09:16.260 --> 00:09:18.350 align:start position:0% for I mean if you are working again if you<00:09:16.380> are<00:09:16.560> working<00:09:16.740> as<00:09:17.040> a<00:09:17.160> water<00:09:17.459> company<00:09:17.700> this 00:09:18.350 --> 00:09:18.360 align:start position:0% you are working as a water company this 00:09:18.360 --> 00:09:20.449 align:start position:0% you are working as a water company this is<00:09:18.540> really<00:09:18.839> overwhelming<00:09:19.620> every<00:09:20.040> day<00:09:20.279> you 00:09:20.449 --> 00:09:20.459 align:start position:0% is really overwhelming every day you 00:09:20.459 --> 00:09:23.269 align:start position:0% is really overwhelming every day you always<00:09:20.700> uh<00:09:21.420> receive<00:09:22.080> a<00:09:22.500> user's<00:09:22.980> feedback 00:09:23.269 --> 00:09:23.279 align:start position:0% always uh receive a user's feedback 00:09:23.279 --> 00:09:27.110 align:start position:0% always uh receive a user's feedback complaining<00:09:24.240> uh<00:09:25.019> their<00:09:25.620> token<00:09:25.980> was<00:09:26.160> stolen<00:09:26.640> or 00:09:27.110 --> 00:09:27.120 align:start position:0% complaining uh their token was stolen or 00:09:27.120 --> 00:09:29.210 align:start position:0% complaining uh their token was stolen or they<00:09:27.360> just<00:09:27.600> make<00:09:27.839> they<00:09:28.380> just<00:09:28.560> approved<00:09:29.040> to 00:09:29.210 --> 00:09:29.220 align:start position:0% they just make they just approved to 00:09:29.220 --> 00:09:31.730 align:start position:0% they just make they just approved to some<00:09:29.459> fake<00:09:29.820> contract<00:09:30.240> so<00:09:30.779> how<00:09:31.019> do<00:09:31.140> we<00:09:31.320> avoid 00:09:31.730 --> 00:09:31.740 align:start position:0% some fake contract so how do we avoid 00:09:31.740 --> 00:09:35.030 align:start position:0% some fake contract so how do we avoid that<00:09:31.980> avoid<00:09:32.700> it<00:09:32.880> and<00:09:33.480> even<00:09:33.660> though<00:09:33.959> they<00:09:34.860> are 00:09:35.030 --> 00:09:35.040 align:start position:0% that avoid it and even though they are 00:09:35.040 --> 00:09:38.030 align:start position:0% that avoid it and even though they are more<00:09:35.220> uh<00:09:35.700> important 00:09:38.030 --> 00:09:38.040 align:start position:0% more uh important 00:09:38.040 --> 00:09:41.090 align:start position:0% more uh important important<00:09:38.880> question<00:09:39.120> is<00:09:39.540> how<00:09:40.200> do<00:09:40.380> we<00:09:40.560> make 00:09:41.090 --> 00:09:41.100 align:start position:0% important question is how do we make 00:09:41.100 --> 00:09:44.210 align:start position:0% important question is how do we make sure<00:09:41.339> the<00:09:41.880> user's<00:09:42.420> assets<00:09:42.959> is<00:09:43.200> safe<00:09:43.440> and<00:09:43.980> how 00:09:44.210 --> 00:09:44.220 align:start position:0% sure the user's assets is safe and how 00:09:44.220 --> 00:09:48.170 align:start position:0% sure the user's assets is safe and how do<00:09:44.459> we<00:09:44.720> have<00:09:45.720> learned<00:09:46.200> to<00:09:46.320> manage<00:09:47.100> their<00:09:47.399> key 00:09:48.170 --> 00:09:48.180 align:start position:0% do we have learned to manage their key 00:09:48.180 --> 00:09:51.470 align:start position:0% do we have learned to manage their key so<00:09:48.660> today<00:09:48.839> I'm<00:09:49.260> not<00:09:49.500> go<00:09:49.740> off<00:09:49.980> this<00:09:50.339> topic<00:09:50.700> but<00:09:51.000> I 00:09:51.470 --> 00:09:51.480 align:start position:0% so today I'm not go off this topic but I 00:09:51.480 --> 00:09:53.350 align:start position:0% so today I'm not go off this topic but I will<00:09:51.660> just<00:09:51.839> focus<00:09:52.140> on<00:09:52.320> the<00:09:52.620> key<00:09:52.860> management 00:09:53.350 --> 00:09:53.360 align:start position:0% will just focus on the key management 00:09:53.360 --> 00:09:56.750 align:start position:0% will just focus on the key management and<00:09:54.360> the<00:09:54.899> how<00:09:55.380> do<00:09:55.560> we<00:09:55.740> make<00:09:56.100> their<00:09:56.399> account 00:09:56.750 --> 00:09:56.760 align:start position:0% and the how do we make their account 00:09:56.760 --> 00:09:59.210 align:start position:0% and the how do we make their account could<00:09:57.300> be<00:09:57.480> recoverable<00:09:58.140> here<00:09:58.860> are<00:09:59.040> two 00:09:59.210 --> 00:09:59.220 align:start position:0% could be recoverable here are two 00:09:59.220 --> 00:10:02.990 align:start position:0% could be recoverable here are two solutions<00:09:59.700> uh<00:10:00.240> one<00:10:00.540> one<00:10:01.080> is<00:10:01.380> MPC<00:10:02.040> any<00:10:02.399> other<00:10:02.700> is 00:10:02.990 --> 00:10:03.000 align:start position:0% solutions uh one one is MPC any other is 00:10:03.000 --> 00:10:05.810 align:start position:0% solutions uh one one is MPC any other is a<00:10:03.180> a<00:10:03.560> abstract<00:10:04.560> account<00:10:04.800> I<00:10:05.399> think<00:10:05.519> the 00:10:05.810 --> 00:10:05.820 align:start position:0% a a abstract account I think the 00:10:05.820 --> 00:10:08.269 align:start position:0% a a abstract account I think the abstract<00:10:06.180> account<00:10:06.420> is<00:10:06.899> a<00:10:07.380> very<00:10:07.560> popular<00:10:07.740> topic 00:10:08.269 --> 00:10:08.279 align:start position:0% abstract account is a very popular topic 00:10:08.279 --> 00:10:11.990 align:start position:0% abstract account is a very popular topic during<00:10:09.000> the<00:10:09.660> the<00:10:10.019> account<00:10:10.320> talk<00:10:10.620> every<00:10:11.279> day<00:10:11.519> so 00:10:11.990 --> 00:10:12.000 align:start position:0% during the the account talk every day so 00:10:12.000 --> 00:10:14.150 align:start position:0% during the the account talk every day so you<00:10:12.240> might<00:10:12.540> probably<00:10:13.019> might<00:10:13.440> heard<00:10:13.680> about<00:10:13.860> it 00:10:14.150 --> 00:10:14.160 align:start position:0% you might probably might heard about it 00:10:14.160 --> 00:10:17.570 align:start position:0% you might probably might heard about it but<00:10:14.580> for<00:10:14.820> NPC<00:10:15.300> who<00:10:15.540> is<00:10:15.720> NPC<00:10:16.200> MPC<00:10:16.980> actually<00:10:17.220> is<00:10:17.459> a 00:10:17.570 --> 00:10:17.580 align:start position:0% but for NPC who is NPC MPC actually is a 00:10:17.580 --> 00:10:20.230 align:start position:0% but for NPC who is NPC MPC actually is a multi-party<00:10:18.180> computation<00:10:18.720> so<00:10:19.320> think<00:10:19.560> about 00:10:20.230 --> 00:10:20.240 align:start position:0% multi-party computation so think about 00:10:20.240 --> 00:10:23.509 align:start position:0% multi-party computation so think about this<00:10:21.240> example<00:10:21.779> if<00:10:22.140> you<00:10:22.320> want<00:10:22.500> to<00:10:22.680> generate<00:10:23.160> a 00:10:23.509 --> 00:10:23.519 align:start position:0% this example if you want to generate a 00:10:23.519 --> 00:10:26.990 align:start position:0% this example if you want to generate a random<00:10:23.820> number<00:10:24.000> you<00:10:24.959> can<00:10:25.140> ask 00:10:26.990 --> 00:10:27.000 align:start position:0% random number you can ask 00:10:27.000 --> 00:10:28.610 align:start position:0% random number you can ask um if<00:10:27.240> you<00:10:27.420> want<00:10:27.540> to<00:10:27.660> Generate<00:10:28.019> random<00:10:28.320> some 00:10:28.610 --> 00:10:28.620 align:start position:0% um if you want to Generate random some 00:10:28.620 --> 00:10:31.430 align:start position:0% um if you want to Generate random some versus<00:10:28.860> three<00:10:29.339> people<00:10:29.519> you<00:10:30.120> can<00:10:30.300> ask<00:10:30.959> each<00:10:31.260> one 00:10:31.430 --> 00:10:31.440 align:start position:0% versus three people you can ask each one 00:10:31.440 --> 00:10:35.570 align:start position:0% versus three people you can ask each one to<00:10:32.100> to<00:10:32.760> uh<00:10:33.660> for<00:10:33.899> a<00:10:34.080> lumber<00:10:34.380> and<00:10:34.980> then<00:10:35.100> we<00:10:35.399> can 00:10:35.570 --> 00:10:35.580 align:start position:0% to to uh for a lumber and then we can 00:10:35.580 --> 00:10:38.329 align:start position:0% to to uh for a lumber and then we can sum<00:10:35.880> it<00:10:36.120> up<00:10:36.420> to<00:10:36.839> get<00:10:37.019> the<00:10:37.260> results<00:10:37.500> so<00:10:38.100> actually 00:10:38.329 --> 00:10:38.339 align:start position:0% sum it up to get the results so actually 00:10:38.339 --> 00:10:42.350 align:start position:0% sum it up to get the results so actually the<00:10:38.820> MPC<00:10:39.360> is<00:10:39.839> a<00:10:40.200> way<00:10:40.560> for<00:10:40.860> jointing<00:10:41.820> Computing 00:10:42.350 --> 00:10:42.360 align:start position:0% the MPC is a way for jointing Computing 00:10:42.360 --> 00:10:45.410 align:start position:0% the MPC is a way for jointing Computing a<00:10:42.480> function<00:10:42.839> over<00:10:43.200> the<00:10:43.440> input 00:10:45.410 --> 00:10:45.420 align:start position:0% a function over the input 00:10:45.420 --> 00:10:48.889 align:start position:0% a function over the input let's<00:10:45.899> take<00:10:46.140> another<00:10:46.380> example<00:10:47.000> uh<00:10:48.000> if<00:10:48.300> we<00:10:48.540> can 00:10:48.889 --> 00:10:48.899 align:start position:0% let's take another example uh if we can 00:10:48.899 --> 00:10:52.370 align:start position:0% let's take another example uh if we can take<00:10:49.560> the<00:10:49.800> signature<00:10:50.399> as<00:10:51.060> a<00:10:51.300> result 00:10:52.370 --> 00:10:52.380 align:start position:0% take the signature as a result 00:10:52.380 --> 00:10:55.610 align:start position:0% take the signature as a result we<00:10:52.980> can<00:10:53.160> ask<00:10:53.399> each<00:10:53.760> party<00:10:54.060> to<00:10:54.720> contribute<00:10:55.260> part 00:10:55.610 --> 00:10:55.620 align:start position:0% we can ask each party to contribute part 00:10:55.620 --> 00:10:58.009 align:start position:0% we can ask each party to contribute part of<00:10:55.860> its<00:10:56.519> secret<00:10:56.700> numbers 00:10:58.009 --> 00:10:58.019 align:start position:0% of its secret numbers 00:10:58.019 --> 00:11:01.069 align:start position:0% of its secret numbers of<00:10:58.560> the<00:10:58.800> input<00:10:59.160> and<00:10:59.820> then<00:10:59.940> we<00:11:00.120> can<00:11:00.360> get<00:11:00.839> the 00:11:01.069 --> 00:11:01.079 align:start position:0% of the input and then we can get the 00:11:01.079 --> 00:11:03.370 align:start position:0% of the input and then we can get the signature<00:11:01.680> so<00:11:02.160> this<00:11:02.279> is<00:11:02.459> kind<00:11:02.820> of<00:11:02.940> some 00:11:03.370 --> 00:11:03.380 align:start position:0% signature so this is kind of some 00:11:03.380 --> 00:11:07.550 align:start position:0% signature so this is kind of some movements<00:11:04.380> or<00:11:04.560> match<00:11:04.800> Magic<00:11:05.459> uh<00:11:06.420> we<00:11:07.019> do<00:11:07.200> we<00:11:07.380> do 00:11:07.550 --> 00:11:07.560 align:start position:0% movements or match Magic uh we do we do 00:11:07.560 --> 00:11:10.250 align:start position:0% movements or match Magic uh we do we do not<00:11:08.279> need<00:11:08.459> to<00:11:08.640> have<00:11:08.820> a<00:11:09.000> private<00:11:09.360> key<00:11:09.480> but<00:11:10.019> we 00:11:10.250 --> 00:11:10.260 align:start position:0% not need to have a private key but we 00:11:10.260 --> 00:11:13.670 align:start position:0% not need to have a private key but we can<00:11:10.440> generate<00:11:10.860> the<00:11:11.579> validate<00:11:12.180> signature<00:11:13.019> so 00:11:13.670 --> 00:11:13.680 align:start position:0% can generate the validate signature so 00:11:13.680 --> 00:11:16.069 align:start position:0% can generate the validate signature so the<00:11:13.980> input<00:11:14.339> is<00:11:14.579> not<00:11:14.820> related<00:11:15.240> to<00:11:15.540> the<00:11:15.720> private 00:11:16.069 --> 00:11:16.079 align:start position:0% the input is not related to the private 00:11:16.079 --> 00:11:17.990 align:start position:0% the input is not related to the private key<00:11:16.200> so<00:11:16.560> you<00:11:16.920> don't<00:11:17.160> need<00:11:17.279> to<00:11:17.459> worry<00:11:17.640> about 00:11:17.990 --> 00:11:18.000 align:start position:0% key so you don't need to worry about 00:11:18.000 --> 00:11:21.530 align:start position:0% key so you don't need to worry about once<00:11:18.839> your<00:11:19.019> device<00:11:19.260> got<00:11:19.860> lost<00:11:20.220> because<00:11:21.180> there 00:11:21.530 --> 00:11:21.540 align:start position:0% once your device got lost because there 00:11:21.540 --> 00:11:24.230 align:start position:0% once your device got lost because there is<00:11:21.720> no<00:11:21.839> privacy<00:11:22.380> store<00:11:22.620> in<00:11:22.860> the<00:11:23.040> device 00:11:24.230 --> 00:11:24.240 align:start position:0% is no privacy store in the device 00:11:24.240 --> 00:11:26.870 align:start position:0% is no privacy store in the device but<00:11:24.779> but<00:11:25.079> eventually<00:11:25.560> the<00:11:25.980> signature<00:11:26.519> will<00:11:26.700> be 00:11:26.870 --> 00:11:26.880 align:start position:0% but but eventually the signature will be 00:11:26.880 --> 00:11:29.690 align:start position:0% but but eventually the signature will be generated<00:11:27.260> the<00:11:28.260> way<00:11:28.380> it<00:11:28.620> operates<00:11:29.100> is<00:11:29.459> pretty 00:11:29.690 --> 00:11:29.700 align:start position:0% generated the way it operates is pretty 00:11:29.700 --> 00:11:32.150 align:start position:0% generated the way it operates is pretty similar<00:11:30.120> to<00:11:30.360> multi-seek<00:11:31.079> uh<00:11:31.740> think<00:11:31.980> about 00:11:32.150 --> 00:11:32.160 align:start position:0% similar to multi-seek uh think about 00:11:32.160 --> 00:11:36.050 align:start position:0% similar to multi-seek uh think about that<00:11:32.459> if<00:11:33.120> a<00:11:33.360> user<00:11:33.779> needs<00:11:34.200> to<00:11:34.320> uh<00:11:35.040> request<00:11:35.820> a 00:11:36.050 --> 00:11:36.060 align:start position:0% that if a user needs to uh request a 00:11:36.060 --> 00:11:39.730 align:start position:0% that if a user needs to uh request a transaction<00:11:36.779> you<00:11:37.500> need<00:11:37.680> to<00:11:37.920> have<00:11:38.579> another 00:11:39.730 --> 00:11:39.740 align:start position:0% transaction you need to have another 00:11:39.740 --> 00:11:44.090 align:start position:0% transaction you need to have another party<00:11:40.740> to<00:11:41.579> come<00:11:41.820> to<00:11:42.420> co-work<00:11:42.839> to<00:11:43.620> generate<00:11:43.920> the 00:11:44.090 --> 00:11:44.100 align:start position:0% party to come to co-work to generate the 00:11:44.100 --> 00:11:46.850 align:start position:0% party to come to co-work to generate the signature<00:11:44.640> so<00:11:45.180> this<00:11:45.360> is<00:11:45.600> uh<00:11:46.079> really<00:11:46.320> like<00:11:46.560> the 00:11:46.850 --> 00:11:46.860 align:start position:0% signature so this is uh really like the 00:11:46.860 --> 00:11:50.210 align:start position:0% signature so this is uh really like the artistic<00:11:47.420> Majestic<00:11:48.420> Way<00:11:48.660> to<00:11:49.079> uh<00:11:49.500> to<00:11:49.860> send<00:11:49.980> a 00:11:50.210 --> 00:11:50.220 align:start position:0% artistic Majestic Way to uh to send a 00:11:50.220 --> 00:11:52.670 align:start position:0% artistic Majestic Way to uh to send a transaction<00:11:50.579> so<00:11:51.300> this<00:11:51.480> is<00:11:51.660> a<00:11:51.959> very<00:11:52.140> uh 00:11:52.670 --> 00:11:52.680 align:start position:0% transaction so this is a very uh 00:11:52.680 --> 00:11:55.910 align:start position:0% transaction so this is a very uh important<00:11:53.100> feature<00:11:53.579> for<00:11:53.880> the<00:11:54.120> NPC<00:11:55.079> wallet<00:11:55.500> and 00:11:55.910 --> 00:11:55.920 align:start position:0% important feature for the NPC wallet and 00:11:55.920 --> 00:11:59.810 align:start position:0% important feature for the NPC wallet and the<00:11:56.040> mpc1<00:11:56.660> looks<00:11:57.660> like<00:11:57.779> an<00:11:58.019> eoa<00:11:58.740> with<00:11:59.459> an 00:11:59.810 --> 00:11:59.820 align:start position:0% the mpc1 looks like an eoa with an 00:11:59.820 --> 00:12:02.389 align:start position:0% the mpc1 looks like an eoa with an invisible<00:12:00.540> private<00:12:01.320> key 00:12:02.389 --> 00:12:02.399 align:start position:0% invisible private key 00:12:02.399 --> 00:12:04.610 align:start position:0% invisible private key besides<00:12:03.240> it<00:12:03.540> could<00:12:03.720> be<00:12:03.839> designed<00:12:04.260> with<00:12:04.380> the 00:12:04.610 --> 00:12:04.620 align:start position:0% besides it could be designed with the 00:12:04.620 --> 00:12:08.030 align:start position:0% besides it could be designed with the threshold<00:12:05.100> settings<00:12:05.540> for<00:12:06.540> example<00:12:06.839> like<00:12:07.200> two 00:12:08.030 --> 00:12:08.040 align:start position:0% threshold settings for example like two 00:12:08.040 --> 00:12:09.110 align:start position:0% threshold settings for example like two of<00:12:08.220> three 00:12:09.110 --> 00:12:09.120 align:start position:0% of three 00:12:09.120 --> 00:12:11.870 align:start position:0% of three so<00:12:09.600> for<00:12:09.839> example<00:12:10.079> if<00:12:10.380> we<00:12:10.620> uh<00:12:11.040> if<00:12:11.399> this<00:12:11.579> is<00:12:11.760> a 00:12:11.870 --> 00:12:11.880 align:start position:0% so for example if we uh if this is a 00:12:11.880 --> 00:12:14.569 align:start position:0% so for example if we uh if this is a threshold<00:12:12.240> signature<00:12:12.779> then<00:12:13.079> we<00:12:13.320> can<00:12:13.500> uh<00:12:14.100> if<00:12:14.459> we 00:12:14.569 --> 00:12:14.579 align:start position:0% threshold signature then we can uh if we 00:12:14.579 --> 00:12:16.790 align:start position:0% threshold signature then we can uh if we want<00:12:14.760> to<00:12:14.940> send<00:12:15.180> a<00:12:15.420> transaction<00:12:15.779> then<00:12:16.500> the 00:12:16.790 --> 00:12:16.800 align:start position:0% want to send a transaction then the 00:12:16.800 --> 00:12:18.430 align:start position:0% want to send a transaction then the device<00:12:17.100> need<00:12:17.700> to 00:12:18.430 --> 00:12:18.440 align:start position:0% device need to 00:12:18.440 --> 00:12:21.710 align:start position:0% device need to co-work<00:12:19.440> with<00:12:19.860> another<00:12:20.040> device<00:12:20.600> which<00:12:21.600> is 00:12:21.710 --> 00:12:21.720 align:start position:0% co-work with another device which is 00:12:21.720 --> 00:12:23.810 align:start position:0% co-work with another device which is online<00:12:21.959> together<00:12:22.440> to<00:12:23.100> generate<00:12:23.640> the 00:12:23.810 --> 00:12:23.820 align:start position:0% online together to generate the 00:12:23.820 --> 00:12:25.190 align:start position:0% online together to generate the signature 00:12:25.190 --> 00:12:25.200 align:start position:0% signature 00:12:25.200 --> 00:12:28.610 align:start position:0% signature but<00:12:25.740> also<00:12:26.040> this<00:12:26.399> is<00:12:26.519> the<00:12:26.820> uh<00:12:27.060> the<00:12:27.660> uh 00:12:28.610 --> 00:12:28.620 align:start position:0% but also this is the uh the uh 00:12:28.620 --> 00:12:31.790 align:start position:0% but also this is the uh the uh the weakness<00:12:29.459> of<00:12:29.700> the<00:12:29.880> MPC<00:12:30.360> it<00:12:30.899> needs<00:12:31.200> it 00:12:31.790 --> 00:12:31.800 align:start position:0% the weakness of the MPC it needs it 00:12:31.800 --> 00:12:34.430 align:start position:0% the weakness of the MPC it needs it needs<00:12:31.980> the<00:12:32.160> help<00:12:32.279> of<00:12:32.760> another<00:12:33.000> online<00:12:33.839> devices 00:12:34.430 --> 00:12:34.440 align:start position:0% needs the help of another online devices 00:12:34.440 --> 00:12:36.769 align:start position:0% needs the help of another online devices to<00:12:34.920> working<00:12:35.100> together<00:12:35.459> if<00:12:36.240> you<00:12:36.360> think<00:12:36.600> about 00:12:36.769 --> 00:12:36.779 align:start position:0% to working together if you think about 00:12:36.779 --> 00:12:38.090 align:start position:0% to working together if you think about that 00:12:38.090 --> 00:12:38.100 align:start position:0% that 00:12:38.100 --> 00:12:39.110 align:start position:0% that um 00:12:39.110 --> 00:12:39.120 align:start position:0% um 00:12:39.120 --> 00:12:43.069 align:start position:0% um for<00:12:39.779> this<00:12:40.019> secret<00:12:40.500> which<00:12:41.459> uh<00:12:42.180> distribute<00:12:42.839> to 00:12:43.069 --> 00:12:43.079 align:start position:0% for this secret which uh distribute to 00:12:43.079 --> 00:12:46.970 align:start position:0% for this secret which uh distribute to different<00:12:43.380> devices<00:12:44.160> it<00:12:45.000> could<00:12:45.120> be<00:12:45.800> stored<00:12:46.800> in 00:12:46.970 --> 00:12:46.980 align:start position:0% different devices it could be stored in 00:12:46.980 --> 00:12:48.550 align:start position:0% different devices it could be stored in some<00:12:47.279> it<00:12:47.760> could 00:12:48.550 --> 00:12:48.560 align:start position:0% some it could 00:12:48.560 --> 00:12:50.690 align:start position:0% some it could dedicate<00:12:49.560> to<00:12:49.860> some<00:12:50.100> decentralized 00:12:50.690 --> 00:12:50.700 align:start position:0% dedicate to some decentralized 00:12:50.700 --> 00:12:54.410 align:start position:0% dedicate to some decentralized centralized<00:12:51.600> service<00:12:51.839> so<00:12:52.800> for<00:12:53.579> example<00:12:53.880> if<00:12:54.300> we 00:12:54.410 --> 00:12:54.420 align:start position:0% centralized service so for example if we 00:12:54.420 --> 00:12:58.610 align:start position:0% centralized service so for example if we uh<00:12:55.139> if<00:12:55.920> the<00:12:56.279> if<00:12:56.940> the<00:12:57.120> service<00:12:57.360> help<00:12:57.899> to<00:12:58.260> store 00:12:58.610 --> 00:12:58.620 align:start position:0% uh if the if the service help to store 00:12:58.620 --> 00:13:01.370 align:start position:0% uh if the if the service help to store this<00:12:58.860> sequence<00:12:59.360> then<00:13:00.360> the<00:13:00.720> service<00:13:00.899> could 00:13:01.370 --> 00:13:01.380 align:start position:0% this sequence then the service could 00:13:01.380 --> 00:13:04.670 align:start position:0% this sequence then the service could help<00:13:01.560> the<00:13:01.800> user<00:13:02.220> to<00:13:02.519> identify<00:13:03.360> the<00:13:04.260> the 00:13:04.670 --> 00:13:04.680 align:start position:0% help the user to identify the the 00:13:04.680 --> 00:13:07.790 align:start position:0% help the user to identify the the transaction<00:13:05.220> it's<00:13:06.000> valid<00:13:06.540> or<00:13:06.839> not<00:13:07.019> because 00:13:07.790 --> 00:13:07.800 align:start position:0% transaction it's valid or not because 00:13:07.800 --> 00:13:10.610 align:start position:0% transaction it's valid or not because one<00:13:08.579> day<00:13:08.760> if<00:13:09.000> the<00:13:09.240> the<00:13:09.839> user<00:13:10.200> wants<00:13:10.560> to 00:13:10.610 --> 00:13:10.620 align:start position:0% one day if the the user wants to 00:13:10.620 --> 00:13:12.710 align:start position:0% one day if the the user wants to interact<00:13:11.339> with<00:13:11.700> the<00:13:11.820> app<00:13:12.060> or<00:13:12.360> some<00:13:12.540> device 00:13:12.710 --> 00:13:12.720 align:start position:0% interact with the app or some device 00:13:12.720 --> 00:13:16.250 align:start position:0% interact with the app or some device application<00:13:13.320> once<00:13:14.279> this<00:13:14.519> party<00:13:14.820> finds<00:13:15.660> the 00:13:16.250 --> 00:13:16.260 align:start position:0% application once this party finds the 00:13:16.260 --> 00:13:19.190 align:start position:0% application once this party finds the device<00:13:16.500> is<00:13:16.980> fake<00:13:17.339> or<00:13:17.760> it's<00:13:17.880> a<00:13:18.060> scam<00:13:18.360> then<00:13:18.959> it 00:13:19.190 --> 00:13:19.200 align:start position:0% device is fake or it's a scam then it 00:13:19.200 --> 00:13:21.829 align:start position:0% device is fake or it's a scam then it can<00:13:19.380> it<00:13:19.680> can<00:13:19.920> stop<00:13:20.160> to<00:13:20.820> help<00:13:21.000> to<00:13:21.300> generate<00:13:21.660> the 00:13:21.829 --> 00:13:21.839 align:start position:0% can it can stop to help to generate the 00:13:21.839 --> 00:13:24.230 align:start position:0% can it can stop to help to generate the signature<00:13:22.380> so<00:13:22.800> it's<00:13:22.980> it's<00:13:23.220> more<00:13:23.519> like<00:13:23.639> this<00:13:24.060> is 00:13:24.230 --> 00:13:24.240 align:start position:0% signature so it's it's more like this is 00:13:24.240 --> 00:13:27.170 align:start position:0% signature so it's it's more like this is a<00:13:24.420> kind<00:13:24.600> of<00:13:24.720> like<00:13:24.959> a<00:13:25.260> risk<00:13:26.040> Control<00:13:26.399> Function 00:13:27.170 --> 00:13:27.180 align:start position:0% a kind of like a risk Control Function 00:13:27.180 --> 00:13:30.970 align:start position:0% a kind of like a risk Control Function and<00:13:27.959> another<00:13:28.200> part<00:13:28.620> for<00:13:28.920> the<00:13:29.160> NPC<00:13:29.700> is 00:13:30.970 --> 00:13:30.980 align:start position:0% and another part for the NPC is 00:13:30.980 --> 00:13:35.030 align:start position:0% and another part for the NPC is it<00:13:31.980> could<00:13:32.160> support<00:13:32.420> multi-chan<00:13:33.420> because<00:13:34.320> as<00:13:34.800> I 00:13:35.030 --> 00:13:35.040 align:start position:0% it could support multi-chan because as I 00:13:35.040 --> 00:13:37.730 align:start position:0% it could support multi-chan because as I mentioned<00:13:35.339> the<00:13:35.760> MPC<00:13:36.300> only<00:13:36.540> looks<00:13:36.959> like<00:13:37.079> an<00:13:37.260> eoa 00:13:37.730 --> 00:13:37.740 align:start position:0% mentioned the MPC only looks like an eoa 00:13:37.740 --> 00:13:41.629 align:start position:0% mentioned the MPC only looks like an eoa with<00:13:38.100> a<00:13:38.339> invisible<00:13:39.000> foreign<00:13:39.300> key<00:13:40.200> so<00:13:40.920> all<00:13:41.459> of 00:13:41.629 --> 00:13:41.639 align:start position:0% with a invisible foreign key so all of 00:13:41.639 --> 00:13:44.629 align:start position:0% with a invisible foreign key so all of the<00:13:41.820> if<00:13:42.240> this<00:13:42.480> this<00:13:42.839> is<00:13:43.079> a<00:13:43.200> wallet<00:13:43.560> and<00:13:44.279> they 00:13:44.629 --> 00:13:44.639 align:start position:0% the if this this is a wallet and they 00:13:44.639 --> 00:13:47.449 align:start position:0% the if this this is a wallet and they are<00:13:44.880> all<00:13:45.180> go<00:13:45.720> with<00:13:45.959> this<00:13:46.320> invisible<00:13:46.860> private 00:13:47.449 --> 00:13:47.459 align:start position:0% are all go with this invisible private 00:13:47.459 --> 00:13:51.410 align:start position:0% are all go with this invisible private key<00:13:47.639> for<00:13:48.360> so<00:13:48.839> for<00:13:49.380> mpc1<00:13:49.980> it<00:13:50.279> could<00:13:50.459> support<00:13:50.639> BTC 00:13:51.410 --> 00:13:51.420 align:start position:0% key for so for mpc1 it could support BTC 00:13:51.420 --> 00:13:54.530 align:start position:0% key for so for mpc1 it could support BTC Bitcoin<00:13:52.260> it<00:13:52.740> also<00:13:53.040> can<00:13:53.279> support<00:13:53.519> the<00:13:54.060> easier 00:13:54.530 --> 00:13:54.540 align:start position:0% Bitcoin it also can support the easier 00:13:54.540 --> 00:13:57.470 align:start position:0% Bitcoin it also can support the easier and<00:13:54.720> all<00:13:55.620> of<00:13:55.800> the<00:13:55.980> uh<00:13:56.279> public<00:13:56.579> chain<00:13:56.940> is<00:13:57.240> uh 00:13:57.470 --> 00:13:57.480 align:start position:0% and all of the uh public chain is uh 00:13:57.480 --> 00:14:00.470 align:start position:0% and all of the uh public chain is uh layer<00:13:57.899> if<00:13:58.380> their<00:13:58.620> signature<00:13:59.279> is<00:13:59.579> NPC<00:14:00.060> friendly 00:14:00.470 --> 00:14:00.480 align:start position:0% layer if their signature is NPC friendly 00:14:00.480 --> 00:14:04.190 align:start position:0% layer if their signature is NPC friendly so<00:14:01.200> this<00:14:01.740> is<00:14:01.920> a<00:14:02.160> sounds<00:14:02.760> perfect<00:14:03.060> but<00:14:03.720> for<00:14:03.959> the 00:14:04.190 --> 00:14:04.200 align:start position:0% so this is a sounds perfect but for the 00:14:04.200 --> 00:14:07.310 align:start position:0% so this is a sounds perfect but for the mpcc<00:14:04.620> solution<00:14:05.160> just<00:14:06.000> uh<00:14:06.360> just<00:14:06.600> like<00:14:06.779> what<00:14:07.139> I 00:14:07.310 --> 00:14:07.320 align:start position:0% mpcc solution just uh just like what I 00:14:07.320 --> 00:14:09.170 align:start position:0% mpcc solution just uh just like what I mentioned<00:14:07.620> it<00:14:07.980> requires<00:14:08.459> having<00:14:08.639> an<00:14:08.940> online 00:14:09.170 --> 00:14:09.180 align:start position:0% mentioned it requires having an online 00:14:09.180 --> 00:14:12.889 align:start position:0% mentioned it requires having an online Computing<00:14:09.839> unit<00:14:10.160> to<00:14:11.160> code<00:14:11.339> work<00:14:11.639> with<00:14:11.899> uh 00:14:12.889 --> 00:14:12.899 align:start position:0% Computing unit to code work with uh 00:14:12.899 --> 00:14:15.650 align:start position:0% Computing unit to code work with uh these<00:14:13.380> are<00:14:13.440> accounts<00:14:13.980> in<00:14:14.820> Instagram<00:14:15.000> we<00:14:15.480> have 00:14:15.650 --> 00:14:15.660 align:start position:0% these are accounts in Instagram we have 00:14:15.660 --> 00:14:18.470 align:start position:0% these are accounts in Instagram we have these<00:14:16.380> two<00:14:16.620> two<00:14:17.279> types<00:14:17.579> of<00:14:17.760> account<00:14:17.880> one<00:14:18.300> is 00:14:18.470 --> 00:14:18.480 align:start position:0% these two two types of account one is 00:14:18.480 --> 00:14:20.210 align:start position:0% these two two types of account one is eoa<00:14:19.079> and<00:14:19.260> the<00:14:19.440> other<00:14:19.560> is<00:14:19.740> a<00:14:19.920> small<00:14:20.040> country 00:14:20.210 --> 00:14:20.220 align:start position:0% eoa and the other is a small country 00:14:20.220 --> 00:14:24.410 align:start position:0% eoa and the other is a small country account<00:14:20.579> so<00:14:21.420> I<00:14:21.839> just<00:14:22.079> talked<00:14:22.920> about<00:14:23.100> the<00:14:23.880> eoa 00:14:24.410 --> 00:14:24.420 align:start position:0% account so I just talked about the eoa 00:14:24.420 --> 00:14:26.930 align:start position:0% account so I just talked about the eoa over<00:14:24.660> the<00:14:24.899> NPC<00:14:25.260> solution<00:14:25.680> so<00:14:26.279> how<00:14:26.519> about<00:14:26.700> we 00:14:26.930 --> 00:14:26.940 align:start position:0% over the NPC solution so how about we 00:14:26.940 --> 00:14:29.269 align:start position:0% over the NPC solution so how about we talk<00:14:27.120> about<00:14:27.300> the<00:14:27.899> control<00:14:28.139> account<00:14:28.500> so<00:14:29.100> this 00:14:29.269 --> 00:14:29.279 align:start position:0% talk about the control account so this 00:14:29.279 --> 00:14:31.329 align:start position:0% talk about the control account so this is<00:14:29.459> a 00:14:31.329 --> 00:14:31.339 align:start position:0% is a 00:14:31.339 --> 00:14:34.550 align:start position:0% is a so<00:14:32.339> it's<00:14:32.639> a<00:14:32.880> kind<00:14:33.000> of<00:14:33.180> a<00:14:33.300> small<00:14:34.260> country 00:14:34.550 --> 00:14:34.560 align:start position:0% so it's a kind of a small country 00:14:34.560 --> 00:14:35.690 align:start position:0% so it's a kind of a small country warning 00:14:35.690 --> 00:14:35.700 align:start position:0% warning 00:14:35.700 --> 00:14:37.730 align:start position:0% warning so<00:14:36.180> the<00:14:36.300> nice<00:14:36.480> thing<00:14:36.720> lets<00:14:37.380> the<00:14:37.500> smart 00:14:37.730 --> 00:14:37.740 align:start position:0% so the nice thing lets the smart 00:14:37.740 --> 00:14:40.850 align:start position:0% so the nice thing lets the smart contract<00:14:38.220> is<00:14:38.700> it<00:14:39.360> is<00:14:39.540> flexible<00:14:40.019> you<00:14:40.560> can<00:14:40.680> call 00:14:40.850 --> 00:14:40.860 align:start position:0% contract is it is flexible you can call 00:14:40.860 --> 00:14:44.389 align:start position:0% contract is it is flexible you can call anything<00:14:41.279> into<00:14:42.120> a<00:14:42.360> smart<00:14:42.480> contract<00:14:42.959> so<00:14:43.620> you 00:14:44.389 --> 00:14:44.399 align:start position:0% anything into a smart contract so you 00:14:44.399 --> 00:14:47.150 align:start position:0% anything into a smart contract so you can<00:14:44.519> have<00:14:44.760> a<00:14:44.940> customized<00:14:45.779> lure<00:14:46.320> so<00:14:46.860> you<00:14:47.040> can 00:14:47.150 --> 00:14:47.160 align:start position:0% can have a customized lure so you can 00:14:47.160 --> 00:14:49.310 align:start position:0% can have a customized lure so you can Define<00:14:47.339> your<00:14:47.880> rule<00:14:48.180> into<00:14:48.839> this<00:14:49.079> smart 00:14:49.310 --> 00:14:49.320 align:start position:0% Define your rule into this smart 00:14:49.320 --> 00:14:53.030 align:start position:0% Define your rule into this smart contract<00:14:49.800> with<00:14:50.579> the<00:14:50.880> AAA<00:14:51.420> wallet<00:14:52.199> there<00:14:52.740> is<00:14:52.920> a 00:14:53.030 --> 00:14:53.040 align:start position:0% contract with the AAA wallet there is a 00:14:53.040 --> 00:14:57.110 align:start position:0% contract with the AAA wallet there is a entry<00:14:53.600> entry<00:14:54.600> point<00:14:54.839> with<00:14:55.500> two<00:14:55.740> faces 00:14:57.110 --> 00:14:57.120 align:start position:0% entry entry point with two faces 00:14:57.120 --> 00:15:01.069 align:start position:0% entry entry point with two faces verification<00:14:58.019> and<00:14:58.740> execution<00:14:59.360> because<00:15:00.360> in 00:15:01.069 --> 00:15:01.079 align:start position:0% verification and execution because in 00:15:01.079 --> 00:15:03.170 align:start position:0% verification and execution because in current<00:15:01.920> ECU<00:15:02.459> and<00:15:02.579> transactions<00:15:03.000> are 00:15:03.170 --> 00:15:03.180 align:start position:0% current ECU and transactions are 00:15:03.180 --> 00:15:05.949 align:start position:0% current ECU and transactions are verified<00:15:03.480> by<00:15:03.779> ecta<00:15:04.500> signature 00:15:05.949 --> 00:15:05.959 align:start position:0% verified by ecta signature 00:15:05.959 --> 00:15:09.829 align:start position:0% verified by ecta signature which<00:15:06.959> parents<00:15:07.560> and<00:15:07.920> the<00:15:08.279> nuns<00:15:08.820> check<00:15:09.000> and 00:15:09.829 --> 00:15:09.839 align:start position:0% which parents and the nuns check and 00:15:09.839 --> 00:15:10.569 align:start position:0% which parents and the nuns check and then 00:15:10.569 --> 00:15:10.579 align:start position:0% then 00:15:10.579 --> 00:15:15.470 align:start position:0% then SQ<00:15:11.579> the<00:15:11.880> transfer<00:15:12.300> of<00:15:12.839> all<00:15:13.560> the<00:15:13.800> core<00:15:14.040> function 00:15:15.470 --> 00:15:15.480 align:start position:0% SQ the transfer of all the core function 00:15:15.480 --> 00:15:18.170 align:start position:0% SQ the transfer of all the core function so<00:15:16.019> we<00:15:16.199> need<00:15:16.380> to<00:15:16.560> have<00:15:16.740> we<00:15:17.579> need<00:15:17.699> to<00:15:17.820> divide 00:15:18.170 --> 00:15:18.180 align:start position:0% so we need to have we need to divide 00:15:18.180 --> 00:15:21.650 align:start position:0% so we need to have we need to divide this<00:15:18.560> verification<00:15:19.560> and<00:15:20.279> the<00:15:20.399> execution<00:15:20.820> so 00:15:21.650 --> 00:15:21.660 align:start position:0% this verification and the execution so 00:15:21.660 --> 00:15:24.769 align:start position:0% this verification and the execution so this<00:15:21.899> is<00:15:22.079> a<00:15:22.260> pretty<00:15:22.380> easy<00:15:22.620> for<00:15:22.920> the<00:15:23.160> wallet<00:15:24.360> so 00:15:24.769 --> 00:15:24.779 align:start position:0% this is a pretty easy for the wallet so 00:15:24.779 --> 00:15:26.870 align:start position:0% this is a pretty easy for the wallet so what<00:15:24.959> does<00:15:25.199> is<00:15:25.440> important<00:15:25.920> if<00:15:26.459> we<00:15:26.639> can 00:15:26.870 --> 00:15:26.880 align:start position:0% what does is important if we can 00:15:26.880 --> 00:15:29.569 align:start position:0% what does is important if we can customize<00:15:27.540> uh<00:15:28.440> each<00:15:28.800> kind<00:15:28.980> of<00:15:29.100> verification 00:15:29.569 --> 00:15:29.579 align:start position:0% customize uh each kind of verification 00:15:29.579 --> 00:15:32.269 align:start position:0% customize uh each kind of verification dual<00:15:30.240> so<00:15:30.660> let's<00:15:30.839> mean<00:15:31.079> we<00:15:31.440> can<00:15:31.620> Define<00:15:31.800> any 00:15:32.269 --> 00:15:32.279 align:start position:0% dual so let's mean we can Define any 00:15:32.279 --> 00:15:34.569 align:start position:0% dual so let's mean we can Define any kind<00:15:32.519> of<00:15:32.639> signature<00:15:33.600> that 00:15:34.569 --> 00:15:34.579 align:start position:0% kind of signature that 00:15:34.579 --> 00:15:38.449 align:start position:0% kind of signature that in<00:15:35.579> the<00:15:35.699> smart<00:15:35.880> contract<00:15:36.360> like<00:15:36.959> POS<00:15:37.279> like<00:15:38.279> as 00:15:38.449 --> 00:15:38.459 align:start position:0% in the smart contract like POS like as 00:15:38.459 --> 00:15:41.269 align:start position:0% in the smart contract like POS like as you<00:15:38.639> know<00:15:38.760> or<00:15:39.300> like<00:15:39.540> eddsa 00:15:41.269 --> 00:15:41.279 align:start position:0% you know or like eddsa 00:15:41.279 --> 00:15:44.090 align:start position:0% you know or like eddsa so<00:15:41.760> we<00:15:41.880> can<00:15:42.060> have<00:15:42.240> all<00:15:42.540> kinds<00:15:42.899> of<00:15:43.100> signal 00:15:44.090 --> 00:15:44.100 align:start position:0% so we can have all kinds of signal 00:15:44.100 --> 00:15:46.850 align:start position:0% so we can have all kinds of signal signature<00:15:44.940> verification<00:15:45.480> rule<00:15:46.019> are<00:15:46.620> building 00:15:46.850 --> 00:15:46.860 align:start position:0% signature verification rule are building 00:15:46.860 --> 00:15:49.490 align:start position:0% signature verification rule are building into<00:15:47.279> a<00:15:47.579> smart<00:15:47.760> contract<00:15:48.180> and<00:15:48.779> also<00:15:49.019> if<00:15:49.320> we 00:15:49.490 --> 00:15:49.500 align:start position:0% into a smart contract and also if we 00:15:49.500 --> 00:15:52.730 align:start position:0% into a smart contract and also if we think<00:15:49.860> this<00:15:50.399> is<00:15:50.579> not<00:15:50.880> safe<00:15:51.120> we<00:15:51.660> can<00:15:51.779> make<00:15:52.019> it<00:15:52.260> uh 00:15:52.730 --> 00:15:52.740 align:start position:0% think this is not safe we can make it uh 00:15:52.740 --> 00:15:55.550 align:start position:0% think this is not safe we can make it uh as<00:15:53.339> a<00:15:53.639> multi-signature<00:15:54.480> wallet<00:15:54.959> so<00:15:55.380> that 00:15:55.550 --> 00:15:55.560 align:start position:0% as a multi-signature wallet so that 00:15:55.560 --> 00:15:58.389 align:start position:0% as a multi-signature wallet so that means<00:15:55.800> you<00:15:56.040> can<00:15:56.160> control<00:15:56.459> uh 00:15:58.389 --> 00:15:58.399 align:start position:0% means you can control uh 00:15:58.399 --> 00:16:00.889 align:start position:0% means you can control uh the<00:15:59.399> Water<00:15:59.579> could<00:16:00.000> be<00:16:00.120> controlled<00:16:00.480> by<00:16:00.660> five 00:16:00.889 --> 00:16:00.899 align:start position:0% the Water could be controlled by five 00:16:00.899 --> 00:16:03.590 align:start position:0% the Water could be controlled by five people<00:16:01.139> but<00:16:01.560> only<00:16:01.740> three<00:16:02.040> people<00:16:02.339> uh<00:16:03.120> approved 00:16:03.590 --> 00:16:03.600 align:start position:0% people but only three people uh approved 00:16:03.600 --> 00:16:06.290 align:start position:0% people but only three people uh approved then<00:16:03.839> the<00:16:04.019> transaction<00:16:04.380> can<00:16:04.860> be<00:16:04.980> execute 00:16:06.290 --> 00:16:06.300 align:start position:0% then the transaction can be execute 00:16:06.300 --> 00:16:08.769 align:start position:0% then the transaction can be execute and<00:16:06.839> then<00:16:07.019> the<00:16:07.139> other<00:16:07.380> uh 00:16:08.769 --> 00:16:08.779 align:start position:0% and then the other uh 00:16:08.779 --> 00:16:12.110 align:start position:0% and then the other uh Advantage<00:16:09.779> is<00:16:10.320> it<00:16:10.920> could<00:16:11.040> be<00:16:11.220> designed<00:16:12.000> to 00:16:12.110 --> 00:16:12.120 align:start position:0% Advantage is it could be designed to 00:16:12.120 --> 00:16:15.410 align:start position:0% Advantage is it could be designed to verify<00:16:13.079> of<00:16:13.380> trend<00:16:13.800> signing<00:16:14.100> messages<00:16:14.279> so<00:16:15.240> this 00:16:15.410 --> 00:16:15.420 align:start position:0% verify of trend signing messages so this 00:16:15.420 --> 00:16:17.329 align:start position:0% verify of trend signing messages so this is<00:16:15.540> pretty<00:16:15.899> important<00:16:16.380> because<00:16:16.620> if<00:16:17.040> you<00:16:17.160> think 00:16:17.329 --> 00:16:17.339 align:start position:0% is pretty important because if you think 00:16:17.339 --> 00:16:20.389 align:start position:0% is pretty important because if you think about<00:16:17.579> the<00:16:17.820> Meta<00:16:18.180> Meta<00:16:18.959> transaction 00:16:20.389 --> 00:16:20.399 align:start position:0% about the Meta Meta transaction 00:16:20.399 --> 00:16:22.069 align:start position:0% about the Meta Meta transaction um or 00:16:22.069 --> 00:16:22.079 align:start position:0% um or 00:16:22.079 --> 00:16:23.750 align:start position:0% um or yeah<00:16:22.560> if<00:16:22.800> you<00:16:22.860> think<00:16:23.100> about<00:16:23.220> a<00:16:23.459> meta 00:16:23.750 --> 00:16:23.760 align:start position:0% yeah if you think about a meta 00:16:23.760 --> 00:16:25.850 align:start position:0% yeah if you think about a meta transaction<00:16:24.060> or<00:16:24.420> some<00:16:24.660> gaming<00:16:25.079> app<00:16:25.260> because 00:16:25.850 --> 00:16:25.860 align:start position:0% transaction or some gaming app because 00:16:25.860 --> 00:16:27.949 align:start position:0% transaction or some gaming app because the<00:16:26.220> users<00:16:26.519> don't<00:16:26.699> know<00:16:26.880> how<00:16:27.360> to<00:16:27.480> get<00:16:27.660> the 00:16:27.949 --> 00:16:27.959 align:start position:0% the users don't know how to get the 00:16:27.959 --> 00:16:30.470 align:start position:0% the users don't know how to get the easers<00:16:28.380> so<00:16:28.860> if<00:16:29.100> you<00:16:29.339> can<00:16:29.459> have<00:16:29.639> some<00:16:29.820> relay<00:16:30.180> to 00:16:30.470 --> 00:16:30.480 align:start position:0% easers so if you can have some relay to 00:16:30.480 --> 00:16:33.769 align:start position:0% easers so if you can have some relay to help<00:16:30.660> them<00:16:30.899> to<00:16:31.260> relate<00:16:32.300> to<00:16:33.300> relate<00:16:33.720> a 00:16:33.769 --> 00:16:33.779 align:start position:0% help them to relate to relate a 00:16:33.779 --> 00:16:35.870 align:start position:0% help them to relate to relate a transaction<00:16:34.139> that<00:16:34.560> would<00:16:34.920> be<00:16:35.100> useful<00:16:35.519> because 00:16:35.870 --> 00:16:35.880 align:start position:0% transaction that would be useful because 00:16:35.880 --> 00:16:38.329 align:start position:0% transaction that would be useful because they<00:16:36.240> don't<00:16:36.420> need<00:16:36.660> to<00:16:36.899> buy<00:16:37.440> the<00:16:37.680> user<00:16:38.040> when 00:16:38.329 --> 00:16:38.339 align:start position:0% they don't need to buy the user when 00:16:38.339 --> 00:16:40.550 align:start position:0% they don't need to buy the user when they<00:16:38.519> want<00:16:38.759> to<00:16:38.880> send<00:16:39.060> a<00:16:39.180> transaction 00:16:40.550 --> 00:16:40.560 align:start position:0% they want to send a transaction 00:16:40.560 --> 00:16:43.430 align:start position:0% they want to send a transaction and<00:16:41.220> the<00:16:41.399> last<00:16:41.880> is<00:16:42.420> I<00:16:42.720> think<00:16:42.839> that<00:16:43.019> is<00:16:43.199> more 00:16:43.430 --> 00:16:43.440 align:start position:0% and the last is I think that is more 00:16:43.440 --> 00:16:45.710 align:start position:0% and the last is I think that is more important<00:16:43.800> is<00:16:43.980> we<00:16:44.279> can<00:16:44.459> change<00:16:44.940> the<00:16:45.240> signer 00:16:45.710 --> 00:16:45.720 align:start position:0% important is we can change the signer 00:16:45.720 --> 00:16:47.870 align:start position:0% important is we can change the signer okay<00:16:46.259> to<00:16:46.560> me<00:16:46.740> the<00:16:47.040> most<00:16:47.160> important<00:16:47.699> and 00:16:47.870 --> 00:16:47.880 align:start position:0% okay to me the most important and 00:16:47.880 --> 00:16:50.150 align:start position:0% okay to me the most important and interesting<00:16:48.420> thing<00:16:48.600> uh<00:16:49.199> for<00:16:49.380> abstract 00:16:50.150 --> 00:16:50.160 align:start position:0% interesting thing uh for abstract 00:16:50.160 --> 00:16:52.610 align:start position:0% interesting thing uh for abstract account<00:16:50.399> is<00:16:50.880> we<00:16:51.240> can<00:16:51.480> abstract<00:16:51.899> account<00:16:52.199> from 00:16:52.610 --> 00:16:52.620 align:start position:0% account is we can abstract account from 00:16:52.620 --> 00:16:55.850 align:start position:0% account is we can abstract account from the<00:16:52.860> signer<00:16:53.279> a<00:16:53.639> Founder<00:16:54.000> eoa<00:16:54.420> so<00:16:55.139> that<00:16:55.500> means 00:16:55.850 --> 00:16:55.860 align:start position:0% the signer a Founder eoa so that means 00:16:55.860 --> 00:16:57.710 align:start position:0% the signer a Founder eoa so that means we<00:16:56.100> can<00:16:56.279> have<00:16:56.399> a<00:16:56.579> signer 00:16:57.710 --> 00:16:57.720 align:start position:0% we can have a signer 00:16:57.720 --> 00:17:01.490 align:start position:0% we can have a signer and<00:16:58.199> we<00:16:58.440> can<00:16:58.620> have<00:16:58.800> a<00:16:59.040> account<00:16:59.480> uh<00:17:00.480> but<00:17:01.079> the 00:17:01.490 --> 00:17:01.500 align:start position:0% and we can have a account uh but the 00:17:01.500 --> 00:17:04.309 align:start position:0% and we can have a account uh but the account<00:17:01.680> doesn't<00:17:02.160> equal<00:17:02.519> to<00:17:02.759> final<00:17:03.300> so<00:17:04.140> this 00:17:04.309 --> 00:17:04.319 align:start position:0% account doesn't equal to final so this 00:17:04.319 --> 00:17:06.890 align:start position:0% account doesn't equal to final so this is<00:17:04.439> a<00:17:04.679> very<00:17:04.919> important<00:17:05.459> feature<00:17:05.880> because<00:17:06.480> one 00:17:06.890 --> 00:17:06.900 align:start position:0% is a very important feature because one 00:17:06.900 --> 00:17:09.590 align:start position:0% is a very important feature because one day<00:17:07.079> if<00:17:07.260> we<00:17:07.439> want<00:17:07.620> to<00:17:07.880> design<00:17:08.880> a<00:17:09.299> kind<00:17:09.480> of 00:17:09.590 --> 00:17:09.600 align:start position:0% day if we want to design a kind of 00:17:09.600 --> 00:17:13.549 align:start position:0% day if we want to design a kind of application<00:17:10.140> like<00:17:10.500> did<00:17:10.980> or<00:17:11.939> so<00:17:12.120> Bank<00:17:12.419> token 00:17:13.549 --> 00:17:13.559 align:start position:0% application like did or so Bank token 00:17:13.559 --> 00:17:16.730 align:start position:0% application like did or so Bank token the<00:17:14.220> account<00:17:14.400> could<00:17:14.819> be<00:17:15.000> fixed<00:17:15.360> and<00:17:15.959> it<00:17:16.620> could 00:17:16.730 --> 00:17:16.740 align:start position:0% the account could be fixed and it could 00:17:16.740 --> 00:17:19.250 align:start position:0% the account could be fixed and it could we<00:17:17.100> can<00:17:17.220> have<00:17:17.400> the<00:17:17.579> same<00:17:17.760> address<00:17:18.059> but<00:17:18.780> we<00:17:19.020> can 00:17:19.250 --> 00:17:19.260 align:start position:0% we can have the same address but we can 00:17:19.260 --> 00:17:22.429 align:start position:0% we can have the same address but we can have<00:17:20.220> a<00:17:20.400> different<00:17:20.640> signer<00:17:21.299> to<00:17:21.839> control<00:17:22.079> this 00:17:22.429 --> 00:17:22.439 align:start position:0% have a different signer to control this 00:17:22.439 --> 00:17:25.309 align:start position:0% have a different signer to control this account<00:17:22.699> uh<00:17:23.699> here<00:17:23.939> is<00:17:24.120> a<00:17:24.299> summarize 00:17:25.309 --> 00:17:25.319 align:start position:0% account uh here is a summarize 00:17:25.319 --> 00:17:27.049 align:start position:0% account uh here is a summarize of<00:17:26.280> the 00:17:27.049 --> 00:17:27.059 align:start position:0% of the 00:17:27.059 --> 00:17:29.750 align:start position:0% of the some<00:17:27.480> part<00:17:27.720> of<00:17:27.900> features<00:17:28.319> of<00:17:28.679> the<00:17:29.100> NPC<00:17:29.520> world 00:17:29.750 --> 00:17:29.760 align:start position:0% some part of features of the NPC world 00:17:29.760 --> 00:17:30.890 align:start position:0% some part of features of the NPC world and<00:17:30.059> the 00:17:30.890 --> 00:17:30.900 align:start position:0% and the 00:17:30.900 --> 00:17:35.390 align:start position:0% and the abstract<00:17:31.620> or<00:17:31.980> a<00:17:32.760> wallet<00:17:33.360> so<00:17:33.900> for<00:17:34.080> MPC<00:17:34.679> uh<00:17:35.100> it's 00:17:35.390 --> 00:17:35.400 align:start position:0% abstract or a wallet so for MPC uh it's 00:17:35.400 --> 00:17:38.390 align:start position:0% abstract or a wallet so for MPC uh it's developing<00:17:35.880> in<00:17:36.240> 2018<00:17:36.919> and<00:17:37.919> then<00:17:38.039> for<00:17:38.280> now 00:17:38.390 --> 00:17:38.400 align:start position:0% developing in 2018 and then for now 00:17:38.400 --> 00:17:41.810 align:start position:0% developing in 2018 and then for now there<00:17:38.820> are<00:17:39.059> many<00:17:39.539> Protocols<00:17:40.320> are<00:17:40.799> used<00:17:40.980> uh<00:17:41.460> so 00:17:41.810 --> 00:17:41.820 align:start position:0% there are many Protocols are used uh so 00:17:41.820 --> 00:17:44.210 align:start position:0% there are many Protocols are used uh so you<00:17:42.000> can<00:17:42.120> use<00:17:42.299> any<00:17:42.600> kind<00:17:42.840> of<00:17:42.960> this<00:17:43.380> uh<00:17:43.980> to 00:17:44.210 --> 00:17:44.220 align:start position:0% you can use any kind of this uh to 00:17:44.220 --> 00:17:47.090 align:start position:0% you can use any kind of this uh to design<00:17:44.340> your<00:17:44.580> NPC<00:17:45.000> body<00:17:45.179> for<00:17:45.960> AAA<00:17:46.500> recently 00:17:47.090 --> 00:17:47.100 align:start position:0% design your NPC body for AAA recently 00:17:47.100 --> 00:17:49.990 align:start position:0% design your NPC body for AAA recently there<00:17:47.520> are<00:17:47.760> some<00:17:48.059> EIP<00:17:48.660> like 00:17:49.990 --> 00:17:50.000 align:start position:0% there are some EIP like 00:17:50.000 --> 00:17:55.430 align:start position:0% there are some EIP like 2938<00:17:51.000> and<00:17:51.360> the<00:17:51.539> 23<00:17:52.260> 30<00:17:52.980> statement<00:17:54.299> yeah<00:17:54.900> so<00:17:55.260> if 00:17:55.430 --> 00:17:55.440 align:start position:0% 2938 and the 23 30 statement yeah so if 00:17:55.440 --> 00:17:57.590 align:start position:0% 2938 and the 23 30 statement yeah so if you<00:17:55.559> if<00:17:55.919> you<00:17:56.340> are<00:17:56.520> interested<00:17:56.820> in<00:17:56.940> then<00:17:57.299> you 00:17:57.590 --> 00:17:57.600 align:start position:0% you if you are interested in then you 00:17:57.600 --> 00:18:01.250 align:start position:0% you if you are interested in then you can<00:17:57.720> uh<00:17:58.260> try<00:17:58.799> to<00:17:58.980> read<00:17:59.400> it<00:18:00.120> and<00:18:00.780> the<00:18:01.080> address 00:18:01.250 --> 00:18:01.260 align:start position:0% can uh try to read it and the address 00:18:01.260 --> 00:18:04.549 align:start position:0% can uh try to read it and the address Alice<00:18:01.860> is<00:18:01.919> actually<00:18:02.460> is<00:18:02.940> a<00:18:03.559> hierarchical 00:18:04.549 --> 00:18:04.559 align:start position:0% Alice is actually is a hierarchical 00:18:04.559 --> 00:18:07.610 align:start position:0% Alice is actually is a hierarchical threshold<00:18:05.280> signatures<00:18:05.940> uh<00:18:06.539> protocol<00:18:06.900> which 00:18:07.610 --> 00:18:07.620 align:start position:0% threshold signatures uh protocol which 00:18:07.620 --> 00:18:11.090 align:start position:0% threshold signatures uh protocol which is<00:18:07.799> designed<00:18:08.400> by<00:18:08.640> me<00:18:08.880> and<00:18:09.120> my<00:18:09.360> colleague<00:18:09.840> uh 00:18:11.090 --> 00:18:11.100 align:start position:0% is designed by me and my colleague uh 00:18:11.100 --> 00:18:14.270 align:start position:0% is designed by me and my colleague uh this<00:18:11.880> is<00:18:12.000> a<00:18:12.360> different<00:18:13.080> social<00:18:13.440> signature 00:18:14.270 --> 00:18:14.280 align:start position:0% this is a different social signature 00:18:14.280 --> 00:18:16.909 align:start position:0% this is a different social signature because<00:18:14.520> we<00:18:15.000> can<00:18:15.179> have<00:18:15.780> a<00:18:16.020> different<00:18:16.260> asset 00:18:16.909 --> 00:18:16.919 align:start position:0% because we can have a different asset 00:18:16.919 --> 00:18:19.250 align:start position:0% because we can have a different asset structure<00:18:17.400> trying<00:18:17.700> to<00:18:17.940> make<00:18:18.120> lecture<00:18:18.600> with<00:18:19.140> a 00:18:19.250 --> 00:18:19.260 align:start position:0% structure trying to make lecture with a 00:18:19.260 --> 00:18:21.650 align:start position:0% structure trying to make lecture with a hierarchical<00:18:19.740> level<00:18:20.100> compare<00:18:21.059> some<00:18:21.240> of<00:18:21.419> the 00:18:21.650 --> 00:18:21.660 align:start position:0% hierarchical level compare some of the 00:18:21.660 --> 00:18:24.230 align:start position:0% hierarchical level compare some of the important<00:18:22.200> feature<00:18:22.559> with<00:18:22.860> the<00:18:23.039> NPC<00:18:23.460> and<00:18:23.700> the<00:18:23.880> a 00:18:24.230 --> 00:18:24.240 align:start position:0% important feature with the NPC and the a 00:18:24.240 --> 00:18:27.950 align:start position:0% important feature with the NPC and the a wallet<00:18:24.720> so<00:18:25.260> for<00:18:25.440> MPC<00:18:25.980> and<00:18:26.160> and<00:18:26.820> a<00:18:27.299> both<00:18:27.480> of<00:18:27.720> them 00:18:27.950 --> 00:18:27.960 align:start position:0% wallet so for MPC and and a both of them 00:18:27.960 --> 00:18:32.150 align:start position:0% wallet so for MPC and and a both of them are<00:18:28.380> good<00:18:29.160> around<00:18:29.940> in<00:18:30.840> multi-stick<00:18:31.440> way<00:18:31.679> so 00:18:32.150 --> 00:18:32.160 align:start position:0% are good around in multi-stick way so 00:18:32.160 --> 00:18:33.970 align:start position:0% are good around in multi-stick way so that<00:18:32.400> means<00:18:32.700> we<00:18:32.940> can<00:18:33.120> have<00:18:33.240> automatic 00:18:33.970 --> 00:18:33.980 align:start position:0% that means we can have automatic 00:18:33.980 --> 00:18:38.510 align:start position:0% that means we can have automatic multi-signature<00:18:34.980> uh<00:18:36.240> operation<00:18:37.080> to 00:18:38.510 --> 00:18:38.520 align:start position:0% multi-signature uh operation to 00:18:38.520 --> 00:18:41.450 align:start position:0% multi-signature uh operation to but<00:18:38.940> for<00:18:39.179> AAA<00:18:39.660> because<00:18:40.200> the<00:18:40.860> account<00:18:40.980> and<00:18:41.340> the 00:18:41.450 --> 00:18:41.460 align:start position:0% but for AAA because the account and the 00:18:41.460 --> 00:18:43.370 align:start position:0% but for AAA because the account and the sign<00:18:41.580> up<00:18:41.760> could<00:18:41.940> be<00:18:42.059> different<00:18:42.179> so<00:18:42.840> that<00:18:43.080> means 00:18:43.370 --> 00:18:43.380 align:start position:0% sign up could be different so that means 00:18:43.380 --> 00:18:45.289 align:start position:0% sign up could be different so that means the<00:18:43.740> account<00:18:43.860> could<00:18:44.280> be<00:18:44.400> changed<00:18:44.820> in<00:18:45.179> the 00:18:45.289 --> 00:18:45.299 align:start position:0% the account could be changed in the 00:18:45.299 --> 00:18:49.010 align:start position:0% the account could be changed in the future<00:18:45.480> so<00:18:46.080> this<00:18:46.260> is<00:18:46.380> pre<00:18:46.799> uh<00:18:47.299> uh<00:18:48.299> not<00:18:48.539> account 00:18:49.010 --> 00:18:49.020 align:start position:0% future so this is pre uh uh not account 00:18:49.020 --> 00:18:51.350 align:start position:0% future so this is pre uh uh not account the<00:18:49.860> sign<00:18:50.039> up<00:18:50.280> could<00:18:50.400> be<00:18:50.520> changed<00:18:50.820> or<00:18:51.120> this 00:18:51.350 --> 00:18:51.360 align:start position:0% the sign up could be changed or this 00:18:51.360 --> 00:18:54.590 align:start position:0% the sign up could be changed or this this<00:18:51.539> is<00:18:51.720> a<00:18:51.840> typo<00:18:52.200> okay<00:18:52.860> but<00:18:53.640> for<00:18:53.820> MPC<00:18:54.360> because 00:18:54.590 --> 00:18:54.600 align:start position:0% this is a typo okay but for MPC because 00:18:54.600 --> 00:18:57.110 align:start position:0% this is a typo okay but for MPC because the<00:18:54.900> private<00:18:55.320> key<00:18:55.500> is<00:18:55.919> equal<00:18:56.160> to<00:18:56.340> account<00:18:56.640> and 00:18:57.110 --> 00:18:57.120 align:start position:0% the private key is equal to account and 00:18:57.120 --> 00:19:00.770 align:start position:0% the private key is equal to account and the<00:18:57.360> signer<00:18:58.140> so<00:18:58.620> yeah<00:18:59.039> this<00:18:59.520> is<00:18:59.640> not<00:18:59.820> possible 00:19:00.770 --> 00:19:00.780 align:start position:0% the signer so yeah this is not possible 00:19:00.780 --> 00:19:03.230 align:start position:0% the signer so yeah this is not possible but<00:19:01.200> for<00:19:01.380> MPC<00:19:01.919> and<00:19:02.160> the<00:19:02.280> AA<00:19:02.640> Wireless<00:19:02.880> because 00:19:03.230 --> 00:19:03.240 align:start position:0% but for MPC and the AA Wireless because 00:19:03.240 --> 00:19:05.870 align:start position:0% but for MPC and the AA Wireless because they<00:19:03.600> they<00:19:03.900> all<00:19:04.080> could<00:19:04.320> be<00:19:04.559> designed<00:19:05.160> uh<00:19:05.580> with 00:19:05.870 --> 00:19:05.880 align:start position:0% they they all could be designed uh with 00:19:05.880 --> 00:19:08.210 align:start position:0% they they all could be designed uh with a<00:19:06.000> social<00:19:06.179> recovery<00:19:06.840> so<00:19:07.440> that<00:19:07.620> both<00:19:07.919> of<00:19:08.100> them 00:19:08.210 --> 00:19:08.220 align:start position:0% a social recovery so that both of them 00:19:08.220 --> 00:19:09.950 align:start position:0% a social recovery so that both of them work<00:19:08.460> with<00:19:08.700> that 00:19:09.950 --> 00:19:09.960 align:start position:0% work with that 00:19:09.960 --> 00:19:13.250 align:start position:0% work with that and<00:19:10.500> for<00:19:10.740> NPC<00:19:11.340> and<00:19:11.580> the<00:19:11.760> air<00:19:12.059> Wireless<00:19:12.360> all<00:19:13.200> of 00:19:13.250 --> 00:19:13.260 align:start position:0% and for NPC and the air Wireless all of 00:19:13.260 --> 00:19:15.830 align:start position:0% and for NPC and the air Wireless all of them<00:19:13.440> can<00:19:13.620> support<00:19:13.799> risk<00:19:14.460> control<00:19:14.640> just<00:19:15.600> like 00:19:15.830 --> 00:19:15.840 align:start position:0% them can support risk control just like 00:19:15.840 --> 00:19:18.529 align:start position:0% them can support risk control just like what<00:19:16.080> I<00:19:16.260> mentioned<00:19:16.559> NPC<00:19:17.220> one<00:19:17.400> is<00:19:17.700> you<00:19:18.000> can<00:19:18.120> if 00:19:18.529 --> 00:19:18.539 align:start position:0% what I mentioned NPC one is you can if 00:19:18.539 --> 00:19:20.330 align:start position:0% what I mentioned NPC one is you can if you<00:19:18.720> dedicate<00:19:19.200> your<00:19:19.380> sequencia<00:19:20.039> to<00:19:20.220> another 00:19:20.330 --> 00:19:20.340 align:start position:0% you dedicate your sequencia to another 00:19:20.340 --> 00:19:22.310 align:start position:0% you dedicate your sequencia to another centralized<00:19:21.000> service<00:19:21.179> then<00:19:21.900> this 00:19:22.310 --> 00:19:22.320 align:start position:0% centralized service then this 00:19:22.320 --> 00:19:25.070 align:start position:0% centralized service then this centralized<00:19:22.860> service<00:19:23.280> could<00:19:23.700> help<00:19:23.880> you<00:19:24.059> to<00:19:24.419> uh 00:19:25.070 --> 00:19:25.080 align:start position:0% centralized service could help you to uh 00:19:25.080 --> 00:19:28.130 align:start position:0% centralized service could help you to uh filter<00:19:25.520> those<00:19:26.520> malicious<00:19:27.240> operations<00:19:27.780> from 00:19:28.130 --> 00:19:28.140 align:start position:0% filter those malicious operations from 00:19:28.140 --> 00:19:31.250 align:start position:0% filter those malicious operations from your<00:19:28.380> users<00:19:28.799> but<00:19:29.520> for<00:19:29.640> AA<00:19:30.120> because<00:19:30.419> this<00:19:30.900> is<00:19:31.080> a 00:19:31.250 --> 00:19:31.260 align:start position:0% your users but for AA because this is a 00:19:31.260 --> 00:19:32.690 align:start position:0% your users but for AA because this is a smart<00:19:31.320> control<00:19:31.620> wireless<00:19:31.919> so<00:19:32.280> you<00:19:32.460> can<00:19:32.520> Define 00:19:32.690 --> 00:19:32.700 align:start position:0% smart control wireless so you can Define 00:19:32.700 --> 00:19:35.390 align:start position:0% smart control wireless so you can Define any<00:19:33.360> kind<00:19:33.600> of<00:19:33.720> lure<00:19:34.080> into<00:19:34.440> the<00:19:34.679> smart<00:19:34.919> contract 00:19:35.390 --> 00:19:35.400 align:start position:0% any kind of lure into the smart contract 00:19:35.400 --> 00:19:39.110 align:start position:0% any kind of lure into the smart contract like<00:19:36.000> you<00:19:36.600> can<00:19:36.720> set<00:19:37.080> the<00:19:37.740> daily<00:19:38.160> withdrawal 00:19:39.110 --> 00:19:39.120 align:start position:0% like you can set the daily withdrawal 00:19:39.120 --> 00:19:41.390 align:start position:0% like you can set the daily withdrawal limit<00:19:39.320> or<00:19:40.320> you<00:19:40.559> can 00:19:41.390 --> 00:19:41.400 align:start position:0% limit or you can 00:19:41.400 --> 00:19:46.010 align:start position:0% limit or you can have<00:19:42.299> some<00:19:42.740> Wireless<00:19:43.740> edges<00:19:44.520> but<00:19:45.240> for<00:19:45.480> NPC 00:19:46.010 --> 00:19:46.020 align:start position:0% have some Wireless edges but for NPC 00:19:46.020 --> 00:19:48.770 align:start position:0% have some Wireless edges but for NPC because<00:19:46.320> this<00:19:46.799> is<00:19:46.980> a<00:19:47.280> it's<00:19:48.059> more<00:19:48.299> like<00:19:48.539> a 00:19:48.770 --> 00:19:48.780 align:start position:0% because this is a it's more like a 00:19:48.780 --> 00:19:51.350 align:start position:0% because this is a it's more like a private<00:19:49.260> key<00:19:49.380> solution<00:19:49.980> so<00:19:50.520> it<00:19:50.820> could<00:19:51.000> support 00:19:51.350 --> 00:19:51.360 align:start position:0% private key solution so it could support 00:19:51.360 --> 00:19:54.110 align:start position:0% private key solution so it could support multi-chain<00:19:52.320> but<00:19:52.919> for<00:19:53.039> the<00:19:53.160> A1<00:19:53.640> it's<00:19:53.880> because 00:19:54.110 --> 00:19:54.120 align:start position:0% multi-chain but for the A1 it's because 00:19:54.120 --> 00:19:56.510 align:start position:0% multi-chain but for the A1 it's because it<00:19:54.419> runs<00:19:54.840> on<00:19:55.140> the<00:19:55.260> smart<00:19:55.500> contract<00:19:55.919> so<00:19:56.280> that 00:19:56.510 --> 00:19:56.520 align:start position:0% it runs on the smart contract so that 00:19:56.520 --> 00:19:58.909 align:start position:0% it runs on the smart contract so that means<00:19:56.880> if<00:19:57.419> the<00:19:57.600> public<00:19:57.840> chain<00:19:58.200> does<00:19:58.500> not<00:19:58.679> have 00:19:58.909 --> 00:19:58.919 align:start position:0% means if the public chain does not have 00:19:58.919 --> 00:20:02.270 align:start position:0% means if the public chain does not have a<00:19:59.100> smart<00:19:59.340> contract<00:19:59.820> or<00:20:00.539> things<00:20:01.020> or<00:20:01.500> or<00:20:02.039> it's 00:20:02.270 --> 00:20:02.280 align:start position:0% a smart contract or things or or it's 00:20:02.280 --> 00:20:04.970 align:start position:0% a smart contract or things or or it's not<00:20:02.400> even<00:20:02.640> comfortable<00:20:03.360> then<00:20:03.960> it<00:20:04.380> cannot<00:20:04.740> be 00:20:04.970 --> 00:20:04.980 align:start position:0% not even comfortable then it cannot be 00:20:04.980 --> 00:20:08.510 align:start position:0% not even comfortable then it cannot be support<00:20:05.340> multi-chan<00:20:06.120> and<00:20:06.600> for<00:20:06.840> MPC<00:20:07.440> uh 00:20:08.510 --> 00:20:08.520 align:start position:0% support multi-chan and for MPC uh 00:20:08.520 --> 00:20:10.789 align:start position:0% support multi-chan and for MPC uh because<00:20:09.059> this<00:20:09.480> is<00:20:09.600> not<00:20:09.840> the<00:20:10.080> smart<00:20:10.380> contract 00:20:10.789 --> 00:20:10.799 align:start position:0% because this is not the smart contract 00:20:10.799 --> 00:20:12.950 align:start position:0% because this is not the smart contract so<00:20:11.100> it<00:20:11.340> could<00:20:11.640> not<00:20:11.880> doing<00:20:12.360> some<00:20:12.660> meta 00:20:12.950 --> 00:20:12.960 align:start position:0% so it could not doing some meta 00:20:12.960 --> 00:20:16.789 align:start position:0% so it could not doing some meta transaction<00:20:13.380> uh<00:20:14.460> so<00:20:15.000> yeah<00:20:15.240> for<00:20:15.600> AAA<00:20:16.020> it<00:20:16.679> can 00:20:16.789 --> 00:20:16.799 align:start position:0% transaction uh so yeah for AAA it can 00:20:16.799 --> 00:20:19.669 align:start position:0% transaction uh so yeah for AAA it can take<00:20:16.980> advantage<00:20:17.760> of<00:20:18.120> the<00:20:18.299> meta<00:20:18.840> transaction 00:20:19.669 --> 00:20:19.679 align:start position:0% take advantage of the meta transaction 00:20:19.679 --> 00:20:22.970 align:start position:0% take advantage of the meta transaction but<00:20:20.280> for<00:20:20.700> D5<00:20:21.120> friendly<00:20:21.539> I<00:20:22.080> think<00:20:22.200> this<00:20:22.440> is<00:20:22.679> a 00:20:22.970 --> 00:20:22.980 align:start position:0% but for D5 friendly I think this is a 00:20:22.980 --> 00:20:26.870 align:start position:0% but for D5 friendly I think this is a very<00:20:23.100> very<00:20:23.280> important<00:20:23.880> Point<00:20:24.419> here<00:20:24.780> so<00:20:25.740> a 00:20:26.870 --> 00:20:26.880 align:start position:0% very very important Point here so a 00:20:26.880 --> 00:20:31.669 align:start position:0% very very important Point here so a sounds<00:20:27.840> like<00:20:28.080> a<00:20:28.320> pretty<00:20:28.559> cool<00:20:28.919> thing<00:20:29.360> but<00:20:30.679> uh 00:20:31.669 --> 00:20:31.679 align:start position:0% sounds like a pretty cool thing but uh 00:20:31.679 --> 00:20:34.130 align:start position:0% sounds like a pretty cool thing but uh if<00:20:32.280> you<00:20:32.460> try<00:20:32.640> to<00:20:32.760> look<00:20:32.940> at<00:20:33.120> all<00:20:33.600> of<00:20:33.780> the<00:20:33.900> smart 00:20:34.130 --> 00:20:34.140 align:start position:0% if you try to look at all of the smart 00:20:34.140 --> 00:20:36.890 align:start position:0% if you try to look at all of the smart contract<00:20:34.559> uh<00:20:35.340> development<00:20:35.880> right<00:20:36.120> now<00:20:36.240> not 00:20:36.890 --> 00:20:36.900 align:start position:0% contract uh development right now not 00:20:36.900 --> 00:20:39.350 align:start position:0% contract uh development right now not every<00:20:37.200> smart<00:20:37.500> contract<00:20:37.980> supports<00:20:38.760> Smart 00:20:39.350 --> 00:20:39.360 align:start position:0% every smart contract supports Smart 00:20:39.360 --> 00:20:40.610 align:start position:0% every smart contract supports Smart Control<00:20:39.600> body 00:20:40.610 --> 00:20:40.620 align:start position:0% Control body 00:20:40.620 --> 00:20:43.310 align:start position:0% Control body so<00:20:41.160> that's<00:20:41.340> mean<00:20:41.580> only<00:20:41.880> the<00:20:42.179> eoa<00:20:42.720> can<00:20:43.020> control 00:20:43.310 --> 00:20:43.320 align:start position:0% so that's mean only the eoa can control 00:20:43.320 --> 00:20:46.730 align:start position:0% so that's mean only the eoa can control or<00:20:44.100> can<00:20:44.460> interact<00:20:44.940> with<00:20:45.360> the<00:20:45.480> smart<00:20:45.720> contract 00:20:46.730 --> 00:20:46.740 align:start position:0% or can interact with the smart contract 00:20:46.740 --> 00:20:50.570 align:start position:0% or can interact with the smart contract and<00:20:47.460> also<00:20:47.760> another<00:20:48.120> thing<00:20:48.539> is<00:20:48.919> uh<00:20:49.919> most<00:20:50.280> people 00:20:50.570 --> 00:20:50.580 align:start position:0% and also another thing is uh most people 00:20:50.580 --> 00:20:53.510 align:start position:0% and also another thing is uh most people do<00:20:50.940> not<00:20:51.120> support<00:20:51.360> EIP<00:20:51.919> 2071<00:20:52.919> it's<00:20:53.280> an 00:20:53.510 --> 00:20:53.520 align:start position:0% do not support EIP 2071 it's an 00:20:53.520 --> 00:20:55.909 align:start position:0% do not support EIP 2071 it's an interface<00:20:53.940> for<00:20:54.360> the<00:20:54.539> Smart<00:20:54.720> Control<00:20:54.960> Wally 00:20:55.909 --> 00:20:55.919 align:start position:0% interface for the Smart Control Wally 00:20:55.919 --> 00:20:58.310 align:start position:0% interface for the Smart Control Wally yeah<00:20:56.400> so<00:20:56.880> this<00:20:57.120> is<00:20:57.360> uh 00:20:58.310 --> 00:20:58.320 align:start position:0% yeah so this is uh 00:20:58.320 --> 00:21:00.830 align:start position:0% yeah so this is uh um<00:20:58.440> I<00:20:58.679> think<00:20:58.799> this<00:20:59.340> is<00:20:59.460> the<00:20:59.640> advantage<00:21:00.059> of<00:21:00.240> MPC 00:21:00.830 --> 00:21:00.840 align:start position:0% um I think this is the advantage of MPC 00:21:00.840 --> 00:21:03.549 align:start position:0% um I think this is the advantage of MPC Wally<00:21:01.140> strongly<00:21:01.919> stable<00:21:02.340> we<00:21:02.760> can<00:21:02.940> see<00:21:03.120> the 00:21:03.549 --> 00:21:03.559 align:start position:0% Wally strongly stable we can see the 00:21:03.559 --> 00:21:07.250 align:start position:0% Wally strongly stable we can see the post<00:21:04.559> and<00:21:04.919> the<00:21:05.100> cons<00:21:05.400> of<00:21:05.820> this<00:21:06.360> kind<00:21:06.720> of<00:21:06.900> these 00:21:07.250 --> 00:21:07.260 align:start position:0% post and the cons of this kind of these 00:21:07.260 --> 00:21:11.570 align:start position:0% post and the cons of this kind of these two<00:21:07.440> uh<00:21:08.340> Solutions<00:21:08.880> I<00:21:09.480> just<00:21:09.720> follow<00:21:10.020> the<00:21:10.580> mean 00:21:11.570 --> 00:21:11.580 align:start position:0% two uh Solutions I just follow the mean 00:21:11.580 --> 00:21:13.190 align:start position:0% two uh Solutions I just follow the mean from<00:21:12.360> the 00:21:13.190 --> 00:21:13.200 align:start position:0% from the 00:21:13.200 --> 00:21:16.370 align:start position:0% from the is<00:21:13.860> too<00:21:14.100> much<00:21:14.280> yeah<00:21:14.760> Hey<00:21:15.600> where's<00:21:15.900> the<00:21:16.080> shower 00:21:16.370 --> 00:21:16.380 align:start position:0% is too much yeah Hey where's the shower 00:21:16.380 --> 00:21:18.650 align:start position:0% is too much yeah Hey where's the shower I<00:21:16.620> just<00:21:16.799> should<00:21:16.980> so<00:21:17.220> shallow<00:21:17.760> is<00:21:17.880> here 00:21:18.650 --> 00:21:18.660 align:start position:0% I just should so shallow is here 00:21:18.660 --> 00:21:22.370 align:start position:0% I just should so shallow is here okay<00:21:19.200> so<00:21:19.620> yeah<00:21:20.580> we<00:21:20.880> can<00:21:21.059> combine<00:21:21.480> NPC<00:21:22.020> and<00:21:22.200> the 00:21:22.370 --> 00:21:22.380 align:start position:0% okay so yeah we can combine NPC and the 00:21:22.380 --> 00:21:24.470 align:start position:0% okay so yeah we can combine NPC and the air<00:21:22.500> while<00:21:22.799> so<00:21:23.580> we<00:21:23.700> can<00:21:23.880> design<00:21:24.059> a<00:21:24.360> future 00:21:24.470 --> 00:21:24.480 align:start position:0% air while so we can design a future 00:21:24.480 --> 00:21:27.490 align:start position:0% air while so we can design a future wallet<00:21:24.960> you<00:21:25.559> can<00:21:25.620> have<00:21:25.799> a<00:21:25.980> worry<00:21:26.220> like<00:21:26.460> that 00:21:27.490 --> 00:21:27.500 align:start position:0% wallet you can have a worry like that 00:21:27.500 --> 00:21:30.289 align:start position:0% wallet you can have a worry like that if<00:21:28.500> you<00:21:28.679> consider<00:21:29.039> this<00:21:29.340> is<00:21:29.520> the<00:21:29.760> future<00:21:29.940> one 00:21:30.289 --> 00:21:30.299 align:start position:0% if you consider this is the future one 00:21:30.299 --> 00:21:33.649 align:start position:0% if you consider this is the future one then<00:21:31.080> have<00:21:31.620> a<00:21:31.799> sign<00:21:31.980> here<00:21:32.400> and<00:21:32.880> we<00:21:33.120> can<00:21:33.299> have<00:21:33.480> an 00:21:33.649 --> 00:21:33.659 align:start position:0% then have a sign here and we can have an 00:21:33.659 --> 00:21:36.470 align:start position:0% then have a sign here and we can have an account<00:21:33.840> into<00:21:34.440> the<00:21:34.740> Smart<00:21:34.919> Control<00:21:35.159> wallet 00:21:36.470 --> 00:21:36.480 align:start position:0% account into the Smart Control wallet 00:21:36.480 --> 00:21:40.130 align:start position:0% account into the Smart Control wallet and<00:21:37.080> also<00:21:37.380> uh<00:21:38.159> because<00:21:38.400> of<00:21:38.940> the<00:21:39.299> feature<00:21:40.020> of 00:21:40.130 --> 00:21:40.140 align:start position:0% and also uh because of the feature of 00:21:40.140 --> 00:21:42.950 align:start position:0% and also uh because of the feature of the<00:21:40.260> MPC<00:21:40.679> and<00:21:40.860> the<00:21:40.980> AAA<00:21:41.340> for<00:21:41.940> MPC<00:21:42.480> it<00:21:42.659> could<00:21:42.840> be 00:21:42.950 --> 00:21:42.960 align:start position:0% the MPC and the AAA for MPC it could be 00:21:42.960 --> 00:21:45.770 align:start position:0% the MPC and the AAA for MPC it could be long<00:21:43.140> in<00:21:43.620> of<00:21:43.919> chain<00:21:44.220> but<00:21:44.640> for<00:21:44.820> AAA<00:21:45.299> it<00:21:45.419> could<00:21:45.600> be 00:21:45.770 --> 00:21:45.780 align:start position:0% long in of chain but for AAA it could be 00:21:45.780 --> 00:21:49.190 align:start position:0% long in of chain but for AAA it could be it<00:21:46.380> because<00:21:47.159> of<00:21:47.640> the<00:21:47.880> operations<00:21:48.539> are<00:21:48.840> on<00:21:49.080> a 00:21:49.190 --> 00:21:49.200 align:start position:0% it because of the operations are on a 00:21:49.200 --> 00:21:51.049 align:start position:0% it because of the operations are on a smart<00:21:49.380> contract<00:21:49.799> so<00:21:49.980> it<00:21:50.159> should<00:21:50.340> be<00:21:50.460> Unchained 00:21:51.049 --> 00:21:51.059 align:start position:0% smart contract so it should be Unchained 00:21:51.059 --> 00:21:53.149 align:start position:0% smart contract so it should be Unchained so<00:21:51.419> there<00:21:51.600> are<00:21:51.720> two<00:21:51.900> different<00:21:52.080> features<00:21:52.679> but 00:21:53.149 --> 00:21:53.159 align:start position:0% so there are two different features but 00:21:53.159 --> 00:21:56.090 align:start position:0% so there are two different features but I<00:21:53.400> think<00:21:53.520> you<00:21:53.820> can<00:21:54.000> take<00:21:54.179> a<00:21:54.360> bit<00:21:54.600> advantage<00:21:55.140> of 00:21:56.090 --> 00:21:56.100 align:start position:0% I think you can take a bit advantage of 00:21:56.100 --> 00:21:58.010 align:start position:0% I think you can take a bit advantage of this<00:21:56.340> kind<00:21:56.520> of<00:21:56.640> two<00:21:56.820> solutions 00:21:58.010 --> 00:21:58.020 align:start position:0% this kind of two solutions 00:21:58.020 --> 00:22:01.010 align:start position:0% this kind of two solutions and<00:21:58.620> third<00:21:58.860> because<00:21:59.400> uh<00:22:00.360> just<00:22:00.539> like<00:22:00.780> I 00:22:01.010 --> 00:22:01.020 align:start position:0% and third because uh just like I 00:22:01.020 --> 00:22:03.289 align:start position:0% and third because uh just like I mentioned<00:22:01.260> NPC<00:22:01.799> needs<00:22:02.159> another<00:22:02.340> party<00:22:02.700> to<00:22:03.179> be 00:22:03.289 --> 00:22:03.299 align:start position:0% mentioned NPC needs another party to be 00:22:03.299 --> 00:22:06.409 align:start position:0% mentioned NPC needs another party to be online<00:22:03.480> to<00:22:03.960> help<00:22:04.080> to<00:22:04.320> co-work<00:22:04.740> to<00:22:05.520> generate<00:22:06.299> a 00:22:06.409 --> 00:22:06.419 align:start position:0% online to help to co-work to generate a 00:22:06.419 --> 00:22:08.570 align:start position:0% online to help to co-work to generate a signature<00:22:07.020> so<00:22:07.500> it<00:22:07.740> should<00:22:07.860> be<00:22:08.039> synchronized 00:22:08.570 --> 00:22:08.580 align:start position:0% signature so it should be synchronized 00:22:08.580 --> 00:22:12.169 align:start position:0% signature so it should be synchronized but<00:22:09.120> for<00:22:09.360> it<00:22:10.020> but<00:22:10.500> for<00:22:10.559> AAA<00:22:11.039> it<00:22:11.700> could<00:22:11.820> be<00:22:11.880> a 00:22:12.169 --> 00:22:12.179 align:start position:0% but for it but for AAA it could be a 00:22:12.179 --> 00:22:14.090 align:start position:0% but for it but for AAA it could be a synchronized<00:22:12.659> but<00:22:13.020> this<00:22:13.260> is<00:22:13.440> not<00:22:13.740> really 00:22:14.090 --> 00:22:14.100 align:start position:0% synchronized but this is not really 00:22:14.100 --> 00:22:16.610 align:start position:0% synchronized but this is not really friendly<00:22:14.520> for<00:22:14.820> multi-6<00:22:15.419> what<00:22:15.900> is<00:22:16.080> signature 00:22:16.610 --> 00:22:16.620 align:start position:0% friendly for multi-6 what is signature 00:22:16.620 --> 00:22:18.890 align:start position:0% friendly for multi-6 what is signature Wally<00:22:16.919> because<00:22:17.400> for<00:22:17.700> money<00:22:17.880> signology<00:22:18.419> when 00:22:18.890 --> 00:22:18.900 align:start position:0% Wally because for money signology when 00:22:18.900 --> 00:22:20.510 align:start position:0% Wally because for money signology when you<00:22:19.080> send<00:22:19.200> a<00:22:19.320> request<00:22:19.679> you<00:22:20.100> need<00:22:20.159> to<00:22:20.280> have 00:22:20.510 --> 00:22:20.520 align:start position:0% you send a request you need to have 00:22:20.520 --> 00:22:22.789 align:start position:0% you send a request you need to have another<00:22:20.760> party<00:22:21.120> to<00:22:21.360> sign<00:22:21.600> a<00:22:21.780> transaction<00:22:22.140> so 00:22:22.789 --> 00:22:22.799 align:start position:0% another party to sign a transaction so 00:22:22.799 --> 00:22:24.830 align:start position:0% another party to sign a transaction so there<00:22:23.159> is<00:22:23.400> a<00:22:23.580> lot<00:22:23.820> of<00:22:24.000> delay 00:22:24.830 --> 00:22:24.840 align:start position:0% there is a lot of delay 00:22:24.840 --> 00:22:27.590 align:start position:0% there is a lot of delay so<00:22:25.320> at<00:22:25.679> the<00:22:25.860> last<00:22:25.980> I<00:22:26.580> think<00:22:26.700> uh<00:22:27.059> if<00:22:27.240> we<00:22:27.360> can 00:22:27.590 --> 00:22:27.600 align:start position:0% so at the last I think uh if we can 00:22:27.600 --> 00:22:29.390 align:start position:0% so at the last I think uh if we can combine<00:22:27.960> these<00:22:28.320> two<00:22:28.380> kind<00:22:28.620> of<00:22:28.740> solution<00:22:29.100> this 00:22:29.390 --> 00:22:29.400 align:start position:0% combine these two kind of solution this 00:22:29.400 --> 00:22:31.610 align:start position:0% combine these two kind of solution this is<00:22:29.580> a<00:22:29.700> benefit<00:22:29.880> we<00:22:30.299> can<00:22:30.539> design<00:22:31.200> a<00:22:31.440> future 00:22:31.610 --> 00:22:31.620 align:start position:0% is a benefit we can design a future 00:22:31.620 --> 00:22:33.529 align:start position:0% is a benefit we can design a future world<00:22:31.860> for<00:22:32.280> this<00:22:32.460> kind<00:22:32.640> of<00:22:32.700> application<00:22:33.059> like 00:22:33.529 --> 00:22:33.539 align:start position:0% world for this kind of application like 00:22:33.539 --> 00:22:35.690 align:start position:0% world for this kind of application like for<00:22:33.840> payment<00:22:34.080> because<00:22:34.679> for<00:22:34.980> payment<00:22:35.220> you<00:22:35.520> need 00:22:35.690 --> 00:22:35.700 align:start position:0% for payment because for payment you need 00:22:35.700 --> 00:22:38.450 align:start position:0% for payment because for payment you need to<00:22:35.760> have<00:22:35.940> a<00:22:36.179> very<00:22:36.299> user-friendly<00:22:36.960> value<00:22:37.320> so 00:22:38.450 --> 00:22:38.460 align:start position:0% to have a very user-friendly value so 00:22:38.460 --> 00:22:40.850 align:start position:0% to have a very user-friendly value so and<00:22:39.000> for<00:22:39.240> did<00:22:39.480> you<00:22:39.900> need<00:22:40.080> to<00:22:40.200> have<00:22:40.380> a<00:22:40.620> account 00:22:40.850 --> 00:22:40.860 align:start position:0% and for did you need to have a account 00:22:40.860 --> 00:22:44.330 align:start position:0% and for did you need to have a account uh<00:22:41.460> have<00:22:41.760> a<00:22:41.940> address<00:22:42.720> which<00:22:43.440> is<00:22:43.559> a<00:22:43.740> sent<00:22:43.980> as<00:22:44.220> an 00:22:44.330 --> 00:22:44.340 align:start position:0% uh have a address which is a sent as an 00:22:44.340 --> 00:22:46.549 align:start position:0% uh have a address which is a sent as an account<00:22:44.520> yeah<00:22:45.240> so<00:22:45.659> we<00:22:45.840> can<00:22:45.960> do<00:22:46.140> a<00:22:46.320> lot<00:22:46.440> of 00:22:46.549 --> 00:22:46.559 align:start position:0% account yeah so we can do a lot of 00:22:46.559 --> 00:22:48.890 align:start position:0% account yeah so we can do a lot of things<00:22:46.679> if<00:22:47.340> we<00:22:47.460> can<00:22:47.700> combine<00:22:48.059> these<00:22:48.299> two<00:22:48.480> kinds 00:22:48.890 --> 00:22:48.900 align:start position:0% things if we can combine these two kinds 00:22:48.900 --> 00:22:53.840 align:start position:0% things if we can combine these two kinds of<00:22:48.960> solution<00:22:49.799> so<00:22:50.340> thank<00:22:50.580> you<00:22:50.760> this<00:22:51.299> is<00:22:51.360> my<00:22:51.600> talk