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:16.330 align:start position:0% [Music] 00:00:16.330 --> 00:00:16.340 align:start position:0% 00:00:16.340 --> 00:00:19.130 align:start position:0% gas<00:00:17.340> station<00:00:17.520> network<00:00:17.880> but<00:00:18.300> recently<00:00:18.960> we're 00:00:19.130 --> 00:00:19.140 align:start position:0% gas station network but recently we're 00:00:19.140 --> 00:00:21.109 align:start position:0% gas station network but recently we're working<00:00:19.320> with<00:00:19.560> your<00:00:19.980> Weiss<00:00:20.460> which<00:00:20.939> was 00:00:21.109 --> 00:00:21.119 align:start position:0% working with your Weiss which was 00:00:21.119 --> 00:00:23.750 align:start position:0% working with your Weiss which was supposed<00:00:21.300> to<00:00:21.539> pass<00:00:22.080> this<00:00:22.320> presentation<00:00:22.740> but 00:00:23.750 --> 00:00:23.760 align:start position:0% supposed to pass this presentation but 00:00:23.760 --> 00:00:26.090 align:start position:0% supposed to pass this presentation but he's<00:00:24.240> sick<00:00:24.480> in<00:00:24.720> the<00:00:24.840> hotel<00:00:25.019> so<00:00:25.619> we<00:00:25.859> are 00:00:26.090 --> 00:00:26.100 align:start position:0% he's sick in the hotel so we are 00:00:26.100 --> 00:00:28.370 align:start position:0% he's sick in the hotel so we are covering<00:00:26.699> him<00:00:26.880> up<00:00:27.480> we'll<00:00:27.779> talk<00:00:28.080> about<00:00:28.199> account 00:00:28.370 --> 00:00:28.380 align:start position:0% covering him up we'll talk about account 00:00:28.380 --> 00:00:31.009 align:start position:0% covering him up we'll talk about account obstruction<00:00:28.939> and<00:00:29.939> the 00:00:31.009 --> 00:00:31.019 align:start position:0% obstruction and the 00:00:31.019 --> 00:00:33.770 align:start position:0% obstruction and the what<00:00:31.560> can<00:00:31.679> be<00:00:31.800> done<00:00:31.920> with<00:00:32.099> it<00:00:32.279> first<00:00:32.640> what<00:00:33.600> is 00:00:33.770 --> 00:00:33.780 align:start position:0% what can be done with it first what is 00:00:33.780 --> 00:00:35.569 align:start position:0% what can be done with it first what is account<00:00:33.960> obstruction<00:00:34.440> but<00:00:34.980> before<00:00:35.280> we<00:00:35.460> talk 00:00:35.569 --> 00:00:35.579 align:start position:0% account obstruction but before we talk 00:00:35.579 --> 00:00:36.830 align:start position:0% account obstruction but before we talk about<00:00:35.700> his<00:00:35.880> account<00:00:36.059> obstruction<00:00:36.360> what<00:00:36.600> is<00:00:36.719> an 00:00:36.830 --> 00:00:36.840 align:start position:0% about his account obstruction what is an 00:00:36.840 --> 00:00:38.630 align:start position:0% about his account obstruction what is an account<00:00:36.960> on<00:00:37.680> ethereum 00:00:38.630 --> 00:00:38.640 align:start position:0% account on ethereum 00:00:38.640 --> 00:00:41.810 align:start position:0% account on ethereum account<00:00:39.180> comes<00:00:39.840> in<00:00:39.960> two<00:00:40.320> flavors<00:00:40.739> one<00:00:41.640> of<00:00:41.760> them 00:00:41.810 --> 00:00:41.820 align:start position:0% account comes in two flavors one of them 00:00:41.820 --> 00:00:44.270 align:start position:0% account comes in two flavors one of them is<00:00:42.120> externally<00:00:42.660> on<00:00:42.899> account<00:00:43.079> but<00:00:43.860> we<00:00:44.040> all<00:00:44.100> know 00:00:44.270 --> 00:00:44.280 align:start position:0% is externally on account but we all know 00:00:44.280 --> 00:00:46.729 align:start position:0% is externally on account but we all know in<00:00:44.399> the<00:00:44.579> other<00:00:44.640> are<00:00:44.879> contract<00:00:45.239> based<00:00:45.660> accounts 00:00:46.729 --> 00:00:46.739 align:start position:0% in the other are contract based accounts 00:00:46.739 --> 00:00:49.190 align:start position:0% in the other are contract based accounts and<00:00:47.399> if<00:00:47.820> you<00:00:48.120> have<00:00:48.360> a<00:00:48.480> wallet<00:00:48.840> you're<00:00:49.020> probably 00:00:49.190 --> 00:00:49.200 align:start position:0% and if you have a wallet you're probably 00:00:49.200 --> 00:00:54.850 align:start position:0% and if you have a wallet you're probably using<00:00:49.620> an<00:00:49.980> UI<00:00:50.820> account 00:00:54.850 --> 00:00:54.860 align:start position:0% 00:00:54.860 --> 00:00:57.170 align:start position:0% UI<00:00:55.860> accounts<00:00:56.340> are<00:00:56.460> very<00:00:56.579> easy<00:00:56.760> to<00:00:56.879> start<00:00:57.059> to 00:00:57.170 --> 00:00:57.180 align:start position:0% UI accounts are very easy to start to 00:00:57.180 --> 00:00:59.270 align:start position:0% UI accounts are very easy to start to work<00:00:57.360> with<00:00:57.480> but<00:00:57.780> they<00:00:57.960> have<00:00:58.199> quite<00:00:58.620> a<00:00:58.920> few 00:00:59.270 --> 00:00:59.280 align:start position:0% work with but they have quite a few 00:00:59.280 --> 00:01:01.130 align:start position:0% work with but they have quite a few limitations 00:01:01.130 --> 00:01:01.140 align:start position:0% limitations 00:01:01.140 --> 00:01:03.590 align:start position:0% limitations first<00:01:01.739> of<00:01:01.860> all<00:01:01.980> key<00:01:02.280> management<00:01:02.520> is<00:01:03.239> very<00:01:03.420> very 00:01:03.590 --> 00:01:03.600 align:start position:0% first of all key management is very very 00:01:03.600 --> 00:01:06.530 align:start position:0% first of all key management is very very problematic<00:01:04.260> the<00:01:05.100> private<00:01:05.460> key<00:01:05.640> is<00:01:06.119> tightly 00:01:06.530 --> 00:01:06.540 align:start position:0% problematic the private key is tightly 00:01:06.540 --> 00:01:08.210 align:start position:0% problematic the private key is tightly coupled<00:01:06.840> with<00:01:06.960> the<00:01:07.140> address<00:01:07.320> which<00:01:07.799> means<00:01:08.040> you 00:01:08.210 --> 00:01:08.220 align:start position:0% coupled with the address which means you 00:01:08.220 --> 00:01:10.850 align:start position:0% coupled with the address which means you can<00:01:08.340> change<00:01:08.520> it<00:01:08.760> you<00:01:09.360> have<00:01:09.540> to<00:01:09.659> keep<00:01:09.780> it<00:01:09.960> secret 00:01:10.850 --> 00:01:10.860 align:start position:0% can change it you have to keep it secret 00:01:10.860 --> 00:01:12.830 align:start position:0% can change it you have to keep it secret because<00:01:11.340> if<00:01:11.580> you<00:01:11.700> lose<00:01:11.880> it<00:01:12.119> you<00:01:12.720> lose 00:01:12.830 --> 00:01:12.840 align:start position:0% because if you lose it you lose 00:01:12.840 --> 00:01:16.850 align:start position:0% because if you lose it you lose everything<00:01:13.280> but<00:01:14.479> if<00:01:15.479> you<00:01:15.720> make<00:01:16.140> copies<00:01:16.619> in 00:01:16.850 --> 00:01:16.860 align:start position:0% everything but if you make copies in 00:01:16.860 --> 00:01:18.950 align:start position:0% everything but if you make copies in order<00:01:16.979> not<00:01:17.220> to<00:01:17.400> lose<00:01:17.520> it<00:01:17.700> someone<00:01:18.240> can<00:01:18.540> find<00:01:18.720> it 00:01:18.950 --> 00:01:18.960 align:start position:0% order not to lose it someone can find it 00:01:18.960 --> 00:01:21.050 align:start position:0% order not to lose it someone can find it and<00:01:19.560> then<00:01:19.740> he<00:01:20.220> will<00:01:20.400> get<00:01:20.520> everything<00:01:20.700> and<00:01:20.939> you 00:01:21.050 --> 00:01:21.060 align:start position:0% and then he will get everything and you 00:01:21.060 --> 00:01:22.609 align:start position:0% and then he will get everything and you will<00:01:21.180> lose<00:01:21.299> everything<00:01:21.540> so<00:01:22.140> Key<00:01:22.380> Management 00:01:22.609 --> 00:01:22.619 align:start position:0% will lose everything so Key Management 00:01:22.619 --> 00:01:26.990 align:start position:0% will lose everything so Key Management is<00:01:23.220> hard 00:01:26.990 --> 00:01:27.000 align:start position:0% 00:01:27.000 --> 00:01:30.649 align:start position:0% there's<00:01:27.659> also<00:01:28.080> there's<00:01:28.740> one<00:01:29.640> one<00:01:30.119> fits<00:01:30.540> all 00:01:30.649 --> 00:01:30.659 align:start position:0% there's also there's one one fits all 00:01:30.659 --> 00:01:32.630 align:start position:0% there's also there's one one fits all access<00:01:30.900> control<00:01:31.200> you<00:01:31.619> can<00:01:31.680> do<00:01:31.799> everything<00:01:32.040> it 00:01:32.630 --> 00:01:32.640 align:start position:0% access control you can do everything it 00:01:32.640 --> 00:01:35.450 align:start position:0% access control you can do everything it might<00:01:32.759> be<00:01:32.880> good<00:01:33.060> for<00:01:33.299> you<00:01:33.420> for<00:01:33.780> personal<00:01:34.460> usage 00:01:35.450 --> 00:01:35.460 align:start position:0% might be good for you for personal usage 00:01:35.460 --> 00:01:37.969 align:start position:0% might be good for you for personal usage that<00:01:35.700> you<00:01:35.820> can<00:01:35.880> do<00:01:36.060> everything<00:01:36.299> but<00:01:37.259> it<00:01:37.799> is 00:01:37.969 --> 00:01:37.979 align:start position:0% that you can do everything but it is 00:01:37.979 --> 00:01:39.730 align:start position:0% that you can do everything but it is very<00:01:38.100> very<00:01:38.280> limiting<00:01:38.759> if 00:01:39.730 --> 00:01:39.740 align:start position:0% very very limiting if 00:01:39.740 --> 00:01:43.490 align:start position:0% very very limiting if you<00:01:40.740> know<00:01:40.860> a 00:01:43.490 --> 00:01:43.500 align:start position:0% 00:01:43.500 --> 00:01:45.469 align:start position:0% all<00:01:43.799> these<00:01:44.040> operations<00:01:44.340> by<00:01:44.820> abstracting<00:01:45.299> them 00:01:45.469 --> 00:01:45.479 align:start position:0% all these operations by abstracting them 00:01:45.479 --> 00:01:48.890 align:start position:0% all these operations by abstracting them away<00:01:45.780> we<00:01:46.079> mean<00:01:46.259> it<00:01:46.920> is<00:01:47.040> not<00:01:47.280> the<00:01:47.640> node<00:01:48.000> that 00:01:48.890 --> 00:01:48.900 align:start position:0% away we mean it is not the node that 00:01:48.900 --> 00:01:50.630 align:start position:0% away we mean it is not the node that performed<00:01:49.320> operation<00:01:49.680> that<00:01:50.040> checks<00:01:50.460> the 00:01:50.630 --> 00:01:50.640 align:start position:0% performed operation that checks the 00:01:50.640 --> 00:01:53.030 align:start position:0% performed operation that checks the signature<00:01:51.060> that<00:01:51.479> checks<00:01:52.079> the<00:01:52.320> the<00:01:52.799> security 00:01:53.030 --> 00:01:53.040 align:start position:0% signature that checks the the security 00:01:53.040 --> 00:01:54.770 align:start position:0% signature that checks the the security of<00:01:53.280> the<00:01:53.460> node<00:01:53.700> check<00:01:53.880> the<00:01:54.060> balance<00:01:54.420> perform 00:01:54.770 --> 00:01:54.780 align:start position:0% of the node check the balance perform 00:01:54.780 --> 00:01:58.910 align:start position:0% of the node check the balance perform the<00:01:55.399> payment<00:01:56.420> but<00:01:57.420> we<00:01:57.899> abstract<00:01:58.380> it<00:01:58.560> away<00:01:58.680> and 00:01:58.910 --> 00:01:58.920 align:start position:0% the payment but we abstract it away and 00:01:58.920 --> 00:02:00.350 align:start position:0% the payment but we abstract it away and make<00:01:59.100> a<00:01:59.220> contract<00:01:59.520> the<00:01:59.700> wallet<00:02:00.060> contract 00:02:00.350 --> 00:02:00.360 align:start position:0% make a contract the wallet contract 00:02:00.360 --> 00:02:03.170 align:start position:0% make a contract the wallet contract being<00:02:00.720> responsible<00:02:01.560> for<00:02:01.740> all<00:02:01.860> of<00:02:02.040> these 00:02:03.170 --> 00:02:03.180 align:start position:0% being responsible for all of these 00:02:03.180 --> 00:02:04.550 align:start position:0% being responsible for all of these so 00:02:04.550 --> 00:02:04.560 align:start position:0% so 00:02:04.560 --> 00:02:06.590 align:start position:0% so the<00:02:05.040> key<00:02:05.159> management<00:02:05.399> becomes<00:02:06.299> simpler 00:02:06.590 --> 00:02:06.600 align:start position:0% the key management becomes simpler 00:02:06.600 --> 00:02:08.029 align:start position:0% the key management becomes simpler because<00:02:06.780> the<00:02:07.079> world<00:02:07.200> can<00:02:07.560> do<00:02:07.740> a<00:02:07.920> key 00:02:08.029 --> 00:02:08.039 align:start position:0% because the world can do a key 00:02:08.039 --> 00:02:11.089 align:start position:0% because the world can do a key management<00:02:08.220> by<00:02:08.580> itself<00:02:09.319> a<00:02:10.319> Access<00:02:10.739> Control 00:02:11.089 --> 00:02:11.099 align:start position:0% management by itself a Access Control 00:02:11.099 --> 00:02:13.309 align:start position:0% management by itself a Access Control mechanism<00:02:11.700> if<00:02:12.000> we<00:02:12.180> want<00:02:12.300> the<00:02:12.599> Gas<00:02:12.780> payment<00:02:13.020> he 00:02:13.309 --> 00:02:13.319 align:start position:0% mechanism if we want the Gas payment he 00:02:13.319 --> 00:02:15.790 align:start position:0% mechanism if we want the Gas payment he does 00:02:15.790 --> 00:02:15.800 align:start position:0% 00:02:15.800 --> 00:02:18.050 align:start position:0% a<00:02:16.800> lot<00:02:16.920> of<00:02:16.980> things<00:02:17.099> become<00:02:17.400> easier<00:02:17.700> but<00:02:17.879> just 00:02:18.050 --> 00:02:18.060 align:start position:0% a lot of things become easier but just 00:02:18.060 --> 00:02:19.910 align:start position:0% a lot of things become easier but just the<00:02:18.239> easiest<00:02:18.540> way<00:02:18.840> to<00:02:19.140> think<00:02:19.260> about<00:02:19.440> this<00:02:19.680> is 00:02:19.910 --> 00:02:19.920 align:start position:0% the easiest way to think about this is 00:02:19.920 --> 00:02:22.250 align:start position:0% the easiest way to think about this is making<00:02:20.099> contracts<00:02:20.819> while<00:02:21.420> contracts<00:02:22.020> first 00:02:22.250 --> 00:02:22.260 align:start position:0% making contracts while contracts first 00:02:22.260 --> 00:02:24.050 align:start position:0% making contracts while contracts first class<00:02:22.560> citizens<00:02:22.980> they're<00:02:23.580> no<00:02:23.819> longer 00:02:24.050 --> 00:02:24.060 align:start position:0% class citizens they're no longer 00:02:24.060 --> 00:02:25.850 align:start position:0% class citizens they're no longer second-class<00:02:24.599> citizens<00:02:25.020> of<00:02:25.200> ethereum<00:02:25.680> and 00:02:25.850 --> 00:02:25.860 align:start position:0% second-class citizens of ethereum and 00:02:25.860 --> 00:02:27.410 align:start position:0% second-class citizens of ethereum and that<00:02:25.980> you<00:02:26.099> don't<00:02:26.160> need<00:02:26.340> an<00:02:26.459> eoa<00:02:26.940> in<00:02:27.120> order<00:02:27.239> to 00:02:27.410 --> 00:02:27.420 align:start position:0% that you don't need an eoa in order to 00:02:27.420 --> 00:02:30.530 align:start position:0% that you don't need an eoa in order to operate<00:02:27.900> your<00:02:28.680> contract<00:02:29.040> wallet<00:02:29.520> right<00:02:30.120> you 00:02:30.530 --> 00:02:30.540 align:start position:0% operate your contract wallet right you 00:02:30.540 --> 00:02:32.390 align:start position:0% operate your contract wallet right you can<00:02:30.599> start<00:02:30.780> from<00:02:30.959> a<00:02:31.140> contract<00:02:31.440> wallet<00:02:31.860> and 00:02:32.390 --> 00:02:32.400 align:start position:0% can start from a contract wallet and 00:02:32.400 --> 00:02:34.430 align:start position:0% can start from a contract wallet and you'll<00:02:32.580> never<00:02:32.760> need<00:02:32.940> to<00:02:33.060> have<00:02:33.180> an<00:02:33.300> eoa 00:02:34.430 --> 00:02:34.440 align:start position:0% you'll never need to have an eoa 00:02:34.440 --> 00:02:37.070 align:start position:0% you'll never need to have an eoa okay<00:02:35.040> from<00:02:35.700> now<00:02:35.940> when<00:02:36.720> we're<00:02:36.840> talking<00:02:36.959> about 00:02:37.070 --> 00:02:37.080 align:start position:0% okay from now when we're talking about 00:02:37.080 --> 00:02:38.510 align:start position:0% okay from now when we're talking about the<00:02:37.200> contextraction<00:02:37.860> now<00:02:38.160> we're<00:02:38.340> talking 00:02:38.510 --> 00:02:38.520 align:start position:0% the contextraction now we're talking 00:02:38.520 --> 00:02:40.729 align:start position:0% the contextraction now we're talking what<00:02:38.940> can<00:02:39.239> be<00:02:39.420> done<00:02:39.540> with<00:02:39.720> it<00:02:39.900> now<00:02:40.379> with<00:02:40.560> the 00:02:40.729 --> 00:02:40.739 align:start position:0% what can be done with it now with the 00:02:40.739 --> 00:02:43.369 align:start position:0% what can be done with it now with the next<00:02:40.860> slide<00:02:41.160> with<00:02:41.340> all<00:02:41.519> the<00:02:41.640> features<00:02:42.420> none<00:02:43.200> of 00:02:43.369 --> 00:02:43.379 align:start position:0% next slide with all the features none of 00:02:43.379 --> 00:02:45.110 align:start position:0% next slide with all the features none of them<00:02:43.500> are<00:02:43.739> implemented<00:02:44.099> by<00:02:44.340> us<00:02:44.519> they<00:02:44.940> are 00:02:45.110 --> 00:02:45.120 align:start position:0% them are implemented by us they are 00:02:45.120 --> 00:02:47.210 align:start position:0% them are implemented by us they are about<00:02:45.180> to<00:02:45.360> be<00:02:45.480> implemented<00:02:45.840> by<00:02:46.080> you<00:02:46.319> we<00:02:47.040> only 00:02:47.210 --> 00:02:47.220 align:start position:0% about to be implemented by you we only 00:02:47.220 --> 00:02:50.449 align:start position:0% about to be implemented by you we only open<00:02:47.760> the<00:02:48.300> door<00:02:48.540> with<00:02:49.319> accounts<00:02:49.800> in<00:02:50.220> order<00:02:50.340> to 00:02:50.449 --> 00:02:50.459 align:start position:0% open the door with accounts in order to 00:02:50.459 --> 00:02:53.330 align:start position:0% open the door with accounts in order to be<00:02:50.640> able<00:02:50.760> to<00:02:50.940> add<00:02:51.120> all<00:02:51.300> these<00:02:51.420> cool<00:02:51.660> features 00:02:53.330 --> 00:02:53.340 align:start position:0% be able to add all these cool features 00:02:53.340 --> 00:02:54.410 align:start position:0% be able to add all these cool features so 00:02:54.410 --> 00:02:54.420 align:start position:0% so 00:02:54.420 --> 00:02:56.270 align:start position:0% so the<00:02:54.599> first<00:02:54.780> use<00:02:54.900> case<00:02:55.140> is<00:02:55.260> recovery<00:02:55.680> right<00:02:56.160> now 00:02:56.270 --> 00:02:56.280 align:start position:0% the first use case is recovery right now 00:02:56.280 --> 00:02:58.490 align:start position:0% the first use case is recovery right now the<00:02:56.459> recovery<00:02:56.879> sucks<00:02:57.120> you<00:02:57.840> can't<00:02:57.959> recap<00:02:58.319> your 00:02:58.490 --> 00:02:58.500 align:start position:0% the recovery sucks you can't recap your 00:02:58.500 --> 00:03:00.350 align:start position:0% the recovery sucks you can't recap your private<00:02:58.860> key<00:02:59.040> you<00:02:59.519> can't<00:02:59.760> really<00:02:59.879> recover<00:03:00.180> it 00:03:00.350 --> 00:03:00.360 align:start position:0% private key you can't really recover it 00:03:00.360 --> 00:03:01.970 align:start position:0% private key you can't really recover it you<00:03:00.599> have<00:03:00.720> to<00:03:00.840> save<00:03:01.140> this<00:03:01.500> private<00:03:01.860> key 00:03:01.970 --> 00:03:01.980 align:start position:0% you have to save this private key 00:03:01.980 --> 00:03:06.050 align:start position:0% you have to save this private key somewhere<00:03:02.760> as<00:03:03.599> a<00:03:03.959> multiple<00:03:04.860> funny<00:03:05.340> words<00:03:05.700> or 00:03:06.050 --> 00:03:06.060 align:start position:0% somewhere as a multiple funny words or 00:03:06.060 --> 00:03:07.210 align:start position:0% somewhere as a multiple funny words or otherwise 00:03:07.210 --> 00:03:07.220 align:start position:0% otherwise 00:03:07.220 --> 00:03:09.170 align:start position:0% otherwise with<00:03:08.220> account<00:03:08.340> obstruction<00:03:08.819> you<00:03:09.060> can 00:03:09.170 --> 00:03:09.180 align:start position:0% with account obstruction you can 00:03:09.180 --> 00:03:10.670 align:start position:0% with account obstruction you can Implement<00:03:09.420> into<00:03:09.660> your<00:03:09.959> wallet<00:03:10.260> social 00:03:10.670 --> 00:03:10.680 align:start position:0% Implement into your wallet social 00:03:10.680 --> 00:03:13.130 align:start position:0% Implement into your wallet social recovery<00:03:11.220> or<00:03:11.459> other<00:03:11.580> recovery<00:03:12.060> mechanism 00:03:13.130 --> 00:03:13.140 align:start position:0% recovery or other recovery mechanism 00:03:13.140 --> 00:03:16.070 align:start position:0% recovery or other recovery mechanism and<00:03:13.680> you<00:03:13.860> can<00:03:13.980> add<00:03:14.040> a<00:03:14.220> Deadman<00:03:14.400> switch<00:03:14.640> like<00:03:15.540> if 00:03:16.070 --> 00:03:16.080 align:start position:0% and you can add a Deadman switch like if 00:03:16.080 --> 00:03:19.309 align:start position:0% and you can add a Deadman switch like if I'm<00:03:16.459> unfortunately<00:03:17.459> or<00:03:17.940> someone<00:03:18.239> is<00:03:19.019> about 00:03:19.309 --> 00:03:19.319 align:start position:0% I'm unfortunately or someone is about 00:03:19.319 --> 00:03:21.770 align:start position:0% I'm unfortunately or someone is about died<00:03:19.980> and<00:03:20.400> you<00:03:20.519> don't<00:03:20.640> want<00:03:20.819> everyone<00:03:21.300> to<00:03:21.659> lose 00:03:21.770 --> 00:03:21.780 align:start position:0% died and you don't want everyone to lose 00:03:21.780 --> 00:03:23.990 align:start position:0% died and you don't want everyone to lose all<00:03:22.019> the<00:03:22.140> the<00:03:22.319> assets<00:03:22.620> he<00:03:22.800> has<00:03:22.980> it<00:03:23.519> can<00:03:23.700> set<00:03:23.819> a 00:03:23.990 --> 00:03:24.000 align:start position:0% all the the assets he has it can set a 00:03:24.000 --> 00:03:25.910 align:start position:0% all the the assets he has it can set a Deadman<00:03:24.180> switch<00:03:24.480> that<00:03:24.900> is<00:03:25.019> after<00:03:25.319> a<00:03:25.560> period<00:03:25.800> of 00:03:25.910 --> 00:03:25.920 align:start position:0% Deadman switch that is after a period of 00:03:25.920 --> 00:03:27.530 align:start position:0% Deadman switch that is after a period of time<00:03:26.159> that<00:03:26.640> he's<00:03:26.760> not<00:03:27.000> using<00:03:27.180> the<00:03:27.360> account 00:03:27.530 --> 00:03:27.540 align:start position:0% time that he's not using the account 00:03:27.540 --> 00:03:30.710 align:start position:0% time that he's not using the account someone<00:03:28.140> else<00:03:28.560> uh 00:03:30.710 --> 00:03:30.720 align:start position:0% someone else uh 00:03:30.720 --> 00:03:33.530 align:start position:0% someone else uh will<00:03:31.200> inherit<00:03:31.739> this<00:03:32.099> account<00:03:32.280> this<00:03:33.060> I<00:03:33.420> can 00:03:33.530 --> 00:03:33.540 align:start position:0% will inherit this account this I can 00:03:33.540 --> 00:03:35.570 align:start position:0% will inherit this account this I can multi-sake<00:03:33.959> that<00:03:34.140> your<00:03:34.319> family<00:03:34.440> controls<00:03:35.099> but 00:03:35.570 --> 00:03:35.580 align:start position:0% multi-sake that your family controls but 00:03:35.580 --> 00:03:38.449 align:start position:0% multi-sake that your family controls but it<00:03:35.760> only<00:03:35.879> becomes<00:03:36.300> active<00:03:36.659> a<00:03:37.080> year<00:03:37.200> after<00:03:37.500> your 00:03:38.449 --> 00:03:38.459 align:start position:0% it only becomes active a year after your 00:03:38.459 --> 00:03:41.210 align:start position:0% it only becomes active a year after your you<00:03:38.700> know<00:03:38.819> your<00:03:39.000> your<00:03:39.239> key<00:03:39.540> is<00:03:39.720> is<00:03:39.959> not<00:03:40.140> active 00:03:41.210 --> 00:03:41.220 align:start position:0% you know your your key is is not active 00:03:41.220 --> 00:03:43.250 align:start position:0% you know your your key is is not active yes<00:03:41.580> we're<00:03:41.819> talking<00:03:41.940> about<00:03:42.060> recovery<00:03:42.659> but 00:03:43.250 --> 00:03:43.260 align:start position:0% yes we're talking about recovery but 00:03:43.260 --> 00:03:45.110 align:start position:0% yes we're talking about recovery but multisig<00:03:43.860> of<00:03:44.099> course<00:03:44.220> when<00:03:44.819> you're<00:03:44.940> talking 00:03:45.110 --> 00:03:45.120 align:start position:0% multisig of course when you're talking 00:03:45.120 --> 00:03:49.789 align:start position:0% multisig of course when you're talking about<00:03:45.360> a<00:03:45.959> signature<00:03:46.620> cases<00:03:47.120> multisig<00:03:48.120> is<00:03:48.480> a 00:03:49.789 --> 00:03:49.799 align:start position:0% about a signature cases multisig is a 00:03:49.799 --> 00:03:52.789 align:start position:0% about a signature cases multisig is a uh<00:03:50.760> something<00:03:51.120> that<00:03:51.360> we<00:03:51.599> see<00:03:51.720> we<00:03:51.959> want<00:03:52.560> to<00:03:52.680> have 00:03:52.789 --> 00:03:52.799 align:start position:0% uh something that we see we want to have 00:03:52.799 --> 00:03:54.949 align:start position:0% uh something that we see we want to have for<00:03:52.980> accounts<00:03:53.459> another<00:03:54.120> option<00:03:54.599> is<00:03:54.780> per 00:03:54.949 --> 00:03:54.959 align:start position:0% for accounts another option is per 00:03:54.959 --> 00:03:56.750 align:start position:0% for accounts another option is per device<00:03:55.140> Keys<00:03:55.620> you<00:03:56.099> might<00:03:56.220> want<00:03:56.400> your<00:03:56.580> phone 00:03:56.750 --> 00:03:56.760 align:start position:0% device Keys you might want your phone 00:03:56.760 --> 00:03:59.630 align:start position:0% device Keys you might want your phone your<00:03:57.239> phone<00:03:57.420> is<00:03:57.780> a<00:03:58.019> very<00:03:58.140> strong<00:03:58.379> Hardware<00:03:58.680> to 00:03:59.630 --> 00:03:59.640 align:start position:0% your phone is a very strong Hardware to 00:03:59.640 --> 00:04:02.030 align:start position:0% your phone is a very strong Hardware to protect<00:03:59.940> keys<00:04:00.840> so<00:04:01.260> it<00:04:01.500> might<00:04:01.680> be<00:04:01.799> very<00:04:01.860> easy 00:04:02.030 --> 00:04:02.040 align:start position:0% protect keys so it might be very easy 00:04:02.040 --> 00:04:03.530 align:start position:0% protect keys so it might be very easy that<00:04:02.340> you<00:04:02.640> know<00:04:02.700> the<00:04:03.000> protection<00:04:03.239> of<00:04:03.420> your 00:04:03.530 --> 00:04:03.540 align:start position:0% that you know the protection of your 00:04:03.540 --> 00:04:04.610 align:start position:0% that you know the protection of your phone<00:04:03.659> whether<00:04:03.840> it's<00:04:04.019> fingerprint<00:04:04.440> or 00:04:04.610 --> 00:04:04.620 align:start position:0% phone whether it's fingerprint or 00:04:04.620 --> 00:04:07.250 align:start position:0% phone whether it's fingerprint or whatever<00:04:04.799> or<00:04:05.580> other<00:04:05.819> biometric<00:04:06.299> check<00:04:06.480> this 00:04:07.250 --> 00:04:07.260 align:start position:0% whatever or other biometric check this 00:04:07.260 --> 00:04:10.070 align:start position:0% whatever or other biometric check this is<00:04:07.440> the<00:04:07.560> way<00:04:07.739> to<00:04:08.099> control<00:04:08.940> your<00:04:09.239> account 00:04:10.070 --> 00:04:10.080 align:start position:0% is the way to control your account 00:04:10.080 --> 00:04:12.229 align:start position:0% is the way to control your account and<00:04:10.500> if<00:04:10.680> you<00:04:10.799> lose<00:04:10.920> this<00:04:11.159> device<00:04:11.340> yes<00:04:11.939> we<00:04:12.120> have 00:04:12.229 --> 00:04:12.239 align:start position:0% and if you lose this device yes we have 00:04:12.239 --> 00:04:14.929 align:start position:0% and if you lose this device yes we have recovery<00:04:12.659> we<00:04:13.080> use<00:04:13.379> another<00:04:13.560> I<00:04:14.159> will<00:04:14.280> assign 00:04:14.929 --> 00:04:14.939 align:start position:0% recovery we use another I will assign 00:04:14.939 --> 00:04:16.969 align:start position:0% recovery we use another I will assign another<00:04:15.239> device<00:04:15.599> as<00:04:15.959> my 00:04:16.969 --> 00:04:16.979 align:start position:0% another device as my 00:04:16.979 --> 00:04:19.909 align:start position:0% another device as my a<00:04:17.699> wallet<00:04:18.380> signer 00:04:19.909 --> 00:04:19.919 align:start position:0% a wallet signer 00:04:19.919 --> 00:04:22.850 align:start position:0% a wallet signer a<00:04:20.880> disappear<00:04:21.479> device<00:04:21.660> keys 00:04:22.850 --> 00:04:22.860 align:start position:0% a disappear device keys 00:04:22.860 --> 00:04:24.950 align:start position:0% a disappear device keys there<00:04:23.520> are<00:04:23.759> other<00:04:24.000> signature<00:04:24.479> scheme<00:04:24.780> you<00:04:24.840> can 00:04:24.950 --> 00:04:24.960 align:start position:0% there are other signature scheme you can 00:04:24.960 --> 00:04:27.050 align:start position:0% there are other signature scheme you can use<00:04:25.080> BLS<00:04:25.860> signature<00:04:26.220> is<00:04:26.340> a<00:04:26.520> very<00:04:26.580> has<00:04:26.820> a<00:04:27.000> very 00:04:27.050 --> 00:04:27.060 align:start position:0% use BLS signature is a very has a very 00:04:27.060 --> 00:04:28.909 align:start position:0% use BLS signature is a very has a very cool<00:04:27.300> feature<00:04:27.660> which<00:04:28.020> can<00:04:28.259> be<00:04:28.440> compressed 00:04:28.909 --> 00:04:28.919 align:start position:0% cool feature which can be compressed 00:04:28.919 --> 00:04:32.810 align:start position:0% cool feature which can be compressed very<00:04:29.160> nicely<00:04:29.520> and<00:04:30.419> which<00:04:30.660> reduce<00:04:30.960> gas<00:04:31.320> on<00:04:31.979> a<00:04:32.280> L2 00:04:32.810 --> 00:04:32.820 align:start position:0% very nicely and which reduce gas on a L2 00:04:32.820 --> 00:04:34.430 align:start position:0% very nicely and which reduce gas on a L2 Networks 00:04:34.430 --> 00:04:34.440 align:start position:0% Networks 00:04:34.440 --> 00:04:36.890 align:start position:0% Networks so<00:04:34.919> it's<00:04:35.520> an<00:04:35.699> extension<00:04:36.060> that<00:04:36.240> can<00:04:36.419> be<00:04:36.540> added 00:04:36.890 --> 00:04:36.900 align:start position:0% so it's an extension that can be added 00:04:36.900 --> 00:04:38.510 align:start position:0% so it's an extension that can be added on<00:04:37.080> top<00:04:37.199> of<00:04:37.259> account<00:04:37.380> obstruction<00:04:37.860> on<00:04:38.340> those 00:04:38.510 --> 00:04:38.520 align:start position:0% on top of account obstruction on those 00:04:38.520 --> 00:04:39.650 align:start position:0% on top of account obstruction on those Networks 00:04:39.650 --> 00:04:39.660 align:start position:0% Networks 00:04:39.660 --> 00:04:41.870 align:start position:0% Networks to<00:04:39.900> reduce<00:04:40.139> the<00:04:40.380> gas<00:04:40.680> fees 00:04:41.870 --> 00:04:41.880 align:start position:0% to reduce the gas fees 00:04:41.880 --> 00:04:44.330 align:start position:0% to reduce the gas fees and<00:04:42.720> if<00:04:43.199> you<00:04:43.320> are<00:04:43.440> looking<00:04:43.560> into<00:04:43.919> the<00:04:44.160> future 00:04:44.330 --> 00:04:44.340 align:start position:0% and if you are looking into the future 00:04:44.340 --> 00:04:47.330 align:start position:0% and if you are looking into the future we<00:04:44.699> know<00:04:44.820> that<00:04:45.000> ecdsa<00:04:45.720> signatures<00:04:46.340> sometime 00:04:47.330 --> 00:04:47.340 align:start position:0% we know that ecdsa signatures sometime 00:04:47.340 --> 00:04:49.790 align:start position:0% we know that ecdsa signatures sometime in<00:04:47.580> the<00:04:47.699> future<00:04:47.880> will<00:04:48.300> become<00:04:48.600> weaker<00:04:49.020> that<00:04:49.680> is 00:04:49.790 --> 00:04:49.800 align:start position:0% in the future will become weaker that is 00:04:49.800 --> 00:04:52.969 align:start position:0% in the future will become weaker that is the<00:04:50.220> attack<00:04:50.340> will<00:04:50.639> become<00:04:50.880> stronger<00:04:51.320> and<00:04:52.320> with 00:04:52.969 --> 00:04:52.979 align:start position:0% the attack will become stronger and with 00:04:52.979 --> 00:04:55.790 align:start position:0% the attack will become stronger and with the<00:04:53.100> quantum<00:04:53.460> machines<00:04:53.759> eventually<00:04:54.660> within<00:04:55.620> 5 00:04:55.790 --> 00:04:55.800 align:start position:0% the quantum machines eventually within 5 00:04:55.800 --> 00:04:58.490 align:start position:0% the quantum machines eventually within 5 10<00:04:56.040> or<00:04:56.280> 20<00:04:56.520> years<00:04:56.759> they<00:04:57.180> will<00:04:57.360> be<00:04:57.600> able<00:04:58.199> to<00:04:58.320> be 00:04:58.490 --> 00:04:58.500 align:start position:0% 10 or 20 years they will be able to be 00:04:58.500 --> 00:05:01.070 align:start position:0% 10 or 20 years they will be able to be cracked<00:04:59.100> we<00:04:59.820> want<00:04:59.940> to<00:05:00.060> be<00:05:00.180> able<00:05:00.360> to<00:05:00.780> upgrade 00:05:01.070 --> 00:05:01.080 align:start position:0% cracked we want to be able to upgrade 00:05:01.080 --> 00:05:02.990 align:start position:0% cracked we want to be able to upgrade our<00:05:01.320> accounts<00:05:01.680> at<00:05:01.860> least<00:05:02.040> our<00:05:02.280> important<00:05:02.699> ones 00:05:02.990 --> 00:05:03.000 align:start position:0% our accounts at least our important ones 00:05:03.000 --> 00:05:06.249 align:start position:0% our accounts at least our important ones before<00:05:03.780> them 00:05:06.249 --> 00:05:06.259 align:start position:0% 00:05:06.259 --> 00:05:09.110 align:start position:0% Quantum<00:05:07.259> resistant<00:05:07.740> signatures<00:05:08.400> might<00:05:08.699> be<00:05:08.940> a 00:05:09.110 --> 00:05:09.120 align:start position:0% Quantum resistant signatures might be a 00:05:09.120 --> 00:05:11.510 align:start position:0% Quantum resistant signatures might be a way<00:05:09.240> and<00:05:10.080> again<00:05:10.320> each<00:05:10.979> of<00:05:11.100> those<00:05:11.280> cool 00:05:11.510 --> 00:05:11.520 align:start position:0% way and again each of those cool 00:05:11.520 --> 00:05:13.430 align:start position:0% way and again each of those cool features<00:05:11.820> we<00:05:12.000> are<00:05:12.120> talking<00:05:12.240> is<00:05:12.720> not<00:05:12.960> a 00:05:13.430 --> 00:05:13.440 align:start position:0% features we are talking is not a 00:05:13.440 --> 00:05:16.370 align:start position:0% features we are talking is not a systematic<00:05:14.040> change<00:05:14.340> of<00:05:14.580> all<00:05:14.759> accounts<00:05:15.300> is<00:05:15.720> a 00:05:16.370 --> 00:05:16.380 align:start position:0% systematic change of all accounts is a 00:05:16.380 --> 00:05:18.170 align:start position:0% systematic change of all accounts is a specific<00:05:16.680> account<00:05:16.919> want<00:05:17.340> to<00:05:17.520> experiment<00:05:17.940> or 00:05:18.170 --> 00:05:18.180 align:start position:0% specific account want to experiment or 00:05:18.180 --> 00:05:20.330 align:start position:0% specific account want to experiment or want<00:05:18.360> to<00:05:18.540> add<00:05:18.780> a<00:05:18.960> feature<00:05:19.259> okay<00:05:19.680> you<00:05:19.979> upgrade 00:05:20.330 --> 00:05:20.340 align:start position:0% want to add a feature okay you upgrade 00:05:20.340 --> 00:05:22.129 align:start position:0% want to add a feature okay you upgrade your<00:05:20.520> account<00:05:20.759> and<00:05:21.600> now<00:05:21.720> you<00:05:21.840> have<00:05:21.960> those 00:05:22.129 --> 00:05:22.139 align:start position:0% your account and now you have those 00:05:22.139 --> 00:05:24.710 align:start position:0% your account and now you have those features<00:05:22.560> like<00:05:23.280> any<00:05:23.699> of<00:05:23.880> those 00:05:24.710 --> 00:05:24.720 align:start position:0% features like any of those 00:05:24.720 --> 00:05:28.610 align:start position:0% features like any of those on<00:05:25.080> the<00:05:25.199> slides<00:05:25.440> around 00:05:28.610 --> 00:05:28.620 align:start position:0% 00:05:28.620 --> 00:05:31.810 align:start position:0% sorry 00:05:31.810 --> 00:05:31.820 align:start position:0% 00:05:31.820 --> 00:05:33.890 align:start position:0% dismiss<00:05:32.820> anyone 00:05:33.890 --> 00:05:33.900 align:start position:0% dismiss anyone 00:05:33.900 --> 00:05:36.110 align:start position:0% dismiss anyone okay<00:05:34.380> now<00:05:34.620> we're<00:05:34.740> talking<00:05:34.979> about<00:05:35.160> some<00:05:35.639> roles 00:05:36.110 --> 00:05:36.120 align:start position:0% okay now we're talking about some roles 00:05:36.120 --> 00:05:37.850 align:start position:0% okay now we're talking about some roles you<00:05:36.419> know<00:05:36.539> you<00:05:36.840> have 00:05:37.850 --> 00:05:37.860 align:start position:0% you know you have 00:05:37.860 --> 00:05:41.090 align:start position:0% you know you have right<00:05:38.280> now<00:05:38.460> as<00:05:38.639> I<00:05:38.820> said<00:05:38.940> with<00:05:39.660> EOS<00:05:40.080> you<00:05:40.860> have<00:05:40.979> a 00:05:41.090 --> 00:05:41.100 align:start position:0% right now as I said with EOS you have a 00:05:41.100 --> 00:05:43.070 align:start position:0% right now as I said with EOS you have a signature<00:05:41.340> and<00:05:41.460> you<00:05:41.520> can<00:05:41.639> do<00:05:41.759> everything 00:05:43.070 --> 00:05:43.080 align:start position:0% signature and you can do everything 00:05:43.080 --> 00:05:44.890 align:start position:0% signature and you can do everything when<00:05:43.560> you<00:05:43.620> use<00:05:43.800> Smart<00:05:43.979> account<00:05:44.160> you<00:05:44.460> can<00:05:44.580> put 00:05:44.890 --> 00:05:44.900 align:start position:0% when you use Smart account you can put 00:05:44.900 --> 00:05:47.210 align:start position:0% when you use Smart account you can put roles<00:05:45.900> you<00:05:46.259> can<00:05:46.320> allow<00:05:46.560> different<00:05:46.740> roles<00:05:47.100> to 00:05:47.210 --> 00:05:47.220 align:start position:0% roles you can allow different roles to 00:05:47.220 --> 00:05:49.430 align:start position:0% roles you can allow different roles to do<00:05:47.400> different<00:05:47.639> things<00:05:47.880> maybe<00:05:48.660> on<00:05:49.020> your<00:05:49.199> home 00:05:49.430 --> 00:05:49.440 align:start position:0% do different things maybe on your home 00:05:49.440 --> 00:05:51.529 align:start position:0% do different things maybe on your home on<00:05:49.800> your<00:05:49.979> personal<00:05:50.100> account<00:05:50.520> you<00:05:51.180> want<00:05:51.300> to<00:05:51.419> do 00:05:51.529 --> 00:05:51.539 align:start position:0% on your personal account you want to do 00:05:51.539 --> 00:05:53.689 align:start position:0% on your personal account you want to do the<00:05:51.720> master<00:05:51.840> to<00:05:52.080> do<00:05:52.199> it<00:05:52.320> all<00:05:52.500> but<00:05:53.220> if<00:05:53.460> it's<00:05:53.580> a 00:05:53.689 --> 00:05:53.699 align:start position:0% the master to do it all but if it's a 00:05:53.699 --> 00:05:55.430 align:start position:0% the master to do it all but if it's a corporate<00:05:54.000> account<00:05:54.180> you<00:05:54.479> might<00:05:54.600> say<00:05:54.840> that<00:05:55.139> you 00:05:55.430 --> 00:05:55.440 align:start position:0% corporate account you might say that you 00:05:55.440 --> 00:05:57.170 align:start position:0% corporate account you might say that you want<00:05:55.620> the<00:05:55.860> legal<00:05:56.280> department<00:05:56.460> to<00:05:56.820> be<00:05:56.940> able<00:05:57.000> to 00:05:57.170 --> 00:05:57.180 align:start position:0% want the legal department to be able to 00:05:57.180 --> 00:05:59.510 align:start position:0% want the legal department to be able to vote<00:05:57.360> but<00:05:57.600> not<00:05:57.720> move<00:05:57.900> tokens<00:05:58.320> you<00:05:59.039> want<00:05:59.220> an 00:05:59.510 --> 00:05:59.520 align:start position:0% vote but not move tokens you want an 00:05:59.520 --> 00:06:01.850 align:start position:0% vote but not move tokens you want an auditor<00:06:00.120> to<00:06:00.300> be<00:06:00.419> able<00:06:00.600> to<00:06:00.960> cancel<00:06:01.320> pending 00:06:01.850 --> 00:06:01.860 align:start position:0% auditor to be able to cancel pending 00:06:01.860 --> 00:06:04.129 align:start position:0% auditor to be able to cancel pending events<00:06:02.160> but<00:06:02.340> not<00:06:02.639> generate<00:06:03.120> events 00:06:04.129 --> 00:06:04.139 align:start position:0% events but not generate events 00:06:04.139 --> 00:06:07.010 align:start position:0% events but not generate events is<00:06:04.979> set<00:06:05.340> to<00:06:05.639> a<00:06:05.820> I<00:06:06.300> don't<00:06:06.360> know 00:06:07.010 --> 00:06:07.020 align:start position:0% is set to a I don't know 00:06:07.020 --> 00:06:09.290 align:start position:0% is set to a I don't know set<00:06:07.500> to<00:06:07.680> a<00:06:07.860> payroll<00:06:08.160> system<00:06:08.400> to<00:06:08.880> be<00:06:09.000> able<00:06:09.120> to 00:06:09.290 --> 00:06:09.300 align:start position:0% set to a payroll system to be able to 00:06:09.300 --> 00:06:12.350 align:start position:0% set to a payroll system to be able to submit<00:06:09.780> to<00:06:10.320> known<00:06:10.740> addresses<00:06:11.340> again<00:06:12.120> the 00:06:12.350 --> 00:06:12.360 align:start position:0% submit to known addresses again the 00:06:12.360 --> 00:06:13.790 align:start position:0% submit to known addresses again the sky's<00:06:12.539> the<00:06:12.660> limit<00:06:12.780> what<00:06:13.020> you<00:06:13.199> can<00:06:13.259> do<00:06:13.380> and<00:06:13.680> it 00:06:13.790 --> 00:06:13.800 align:start position:0% sky's the limit what you can do and it 00:06:13.800 --> 00:06:20.749 align:start position:0% sky's the limit what you can do and it is<00:06:13.919> still<00:06:14.160> you<00:06:15.120> can<00:06:15.180> add<00:06:15.360> it<00:06:15.479> to<00:06:15.660> this<00:06:15.900> account 00:06:20.749 --> 00:06:20.759 align:start position:0% 00:06:20.759 --> 00:06:21.770 align:start position:0% okay 00:06:21.770 --> 00:06:21.780 align:start position:0% okay 00:06:21.780 --> 00:06:23.270 align:start position:0% okay wait<00:06:22.199> maybe<00:06:22.440> a<00:06:22.620> little<00:06:22.740> bit<00:06:22.860> about<00:06:22.979> session 00:06:23.270 --> 00:06:23.280 align:start position:0% wait maybe a little bit about session 00:06:23.280 --> 00:06:25.850 align:start position:0% wait maybe a little bit about session Keys<00:06:23.699> ah<00:06:24.180> sorry<00:06:24.300> okay<00:06:25.020> we<00:06:25.319> talked<00:06:25.560> about<00:06:25.620> the 00:06:25.850 --> 00:06:25.860 align:start position:0% Keys ah sorry okay we talked about the 00:06:25.860 --> 00:06:28.790 align:start position:0% Keys ah sorry okay we talked about the the<00:06:26.100> high<00:06:26.580> end<00:06:27.000> of<00:06:27.360> a<00:06:27.720> account<00:06:28.259> that<00:06:28.680> is 00:06:28.790 --> 00:06:28.800 align:start position:0% the high end of a account that is 00:06:28.800 --> 00:06:30.890 align:start position:0% the high end of a account that is accounts<00:06:29.220> corporate<00:06:29.520> account<00:06:29.699> there<00:06:30.479> is<00:06:30.660> also 00:06:30.890 --> 00:06:30.900 align:start position:0% accounts corporate account there is also 00:06:30.900 --> 00:06:32.330 align:start position:0% accounts corporate account there is also the<00:06:31.020> lower<00:06:31.199> end<00:06:31.380> you<00:06:31.560> know<00:06:31.680> you<00:06:31.860> have<00:06:31.979> your 00:06:32.330 --> 00:06:32.340 align:start position:0% the lower end you know you have your 00:06:32.340 --> 00:06:34.370 align:start position:0% the lower end you know you have your personal<00:06:32.639> account<00:06:33.000> but<00:06:33.720> you<00:06:33.840> also<00:06:34.080> want<00:06:34.259> to 00:06:34.370 --> 00:06:34.380 align:start position:0% personal account but you also want to 00:06:34.380 --> 00:06:37.010 align:start position:0% personal account but you also want to play<00:06:34.500> games<00:06:34.800> with<00:06:35.520> games<00:06:35.759> even<00:06:36.180> the<00:06:36.600> single 00:06:37.010 --> 00:06:37.020 align:start position:0% play games with games even the single 00:06:37.020 --> 00:06:40.730 align:start position:0% play games with games even the single accept<00:06:37.440> per<00:06:38.039> request<00:06:38.520> might<00:06:39.000> be<00:06:39.500> annoying<00:06:40.500> you 00:06:40.730 --> 00:06:40.740 align:start position:0% accept per request might be annoying you 00:06:40.740 --> 00:06:42.830 align:start position:0% accept per request might be annoying you don't<00:06:40.860> want<00:06:41.039> to<00:06:41.100> accept<00:06:41.220> each<00:06:41.520> operation<00:06:41.940> so 00:06:42.830 --> 00:06:42.840 align:start position:0% don't want to accept each operation so 00:06:42.840 --> 00:06:45.710 align:start position:0% don't want to accept each operation so for<00:06:43.440> games<00:06:43.680> you<00:06:43.919> might<00:06:44.100> assign<00:06:45.000> your<00:06:45.180> account 00:06:45.710 --> 00:06:45.720 align:start position:0% for games you might assign your account 00:06:45.720 --> 00:06:48.350 align:start position:0% for games you might assign your account a<00:06:46.080> session<00:06:46.380> key<00:06:47.100> this<00:06:47.639> key<00:06:47.759> is<00:06:48.000> allowed<00:06:48.240> to 00:06:48.350 --> 00:06:48.360 align:start position:0% a session key this key is allowed to 00:06:48.360 --> 00:06:50.270 align:start position:0% a session key this key is allowed to make<00:06:48.479> transaction<00:06:48.900> for<00:06:49.620> specific<00:06:50.100> Target 00:06:50.270 --> 00:06:50.280 align:start position:0% make transaction for specific Target 00:06:50.280 --> 00:06:53.210 align:start position:0% make transaction for specific Target specific<00:06:50.759> game<00:06:51.060> and<00:06:51.780> now<00:06:52.020> you<00:06:52.500> are 00:06:53.210 --> 00:06:53.220 align:start position:0% specific game and now you are 00:06:53.220 --> 00:06:55.990 align:start position:0% specific game and now you are Wallet<00:06:54.000> free<00:06:54.120> you<00:06:54.600> free<00:06:54.960> the<00:06:55.199> ux<00:06:55.500> from 00:06:55.990 --> 00:06:56.000 align:start position:0% Wallet free you free the ux from 00:06:56.000 --> 00:06:58.249 align:start position:0% Wallet free you free the ux from accepting<00:06:57.000> each<00:06:57.180> transaction<00:06:57.600> and<00:06:58.020> you<00:06:58.139> know 00:06:58.249 --> 00:06:58.259 align:start position:0% accepting each transaction and you know 00:06:58.259 --> 00:07:00.830 align:start position:0% accepting each transaction and you know it<00:06:58.500> is<00:06:58.560> limited<00:06:58.919> it's<00:06:59.100> only<00:06:59.340> this<00:06:59.580> game<00:06:59.819> so<00:07:00.539> it 00:07:00.830 --> 00:07:00.840 align:start position:0% it is limited it's only this game so it 00:07:00.840 --> 00:07:02.930 align:start position:0% it is limited it's only this game so it can<00:07:00.960> be<00:07:01.139> your<00:07:01.440> own<00:07:01.500> wallet<00:07:01.919> but<00:07:02.280> you<00:07:02.759> didn't 00:07:02.930 --> 00:07:02.940 align:start position:0% can be your own wallet but you didn't 00:07:02.940 --> 00:07:04.790 align:start position:0% can be your own wallet but you didn't sacrifice<00:07:03.419> for<00:07:03.840> this<00:07:04.020> game<00:07:04.259> you're<00:07:04.500> a<00:07:04.680> nice 00:07:04.790 --> 00:07:04.800 align:start position:0% sacrifice for this game you're a nice 00:07:04.800 --> 00:07:10.629 align:start position:0% sacrifice for this game you're a nice security 00:07:10.629 --> 00:07:10.639 align:start position:0% 00:07:10.639 --> 00:07:13.189 align:start position:0% is<00:07:11.639> this<00:07:11.699> the<00:07:11.880> next 00:07:13.189 --> 00:07:13.199 align:start position:0% is this the next 00:07:13.199 --> 00:07:15.290 align:start position:0% is this the next yes<00:07:13.440> okay<00:07:13.680> we<00:07:13.979> talked<00:07:14.220> about<00:07:14.340> the<00:07:15.000> security 00:07:15.290 --> 00:07:15.300 align:start position:0% yes okay we talked about the security 00:07:15.300 --> 00:07:17.450 align:start position:0% yes okay we talked about the security about<00:07:15.720> the<00:07:16.080> role<00:07:16.560> access<00:07:16.680> now<00:07:16.979> let's<00:07:17.280> talk 00:07:17.450 --> 00:07:17.460 align:start position:0% about the role access now let's talk 00:07:17.460 --> 00:07:20.089 align:start position:0% about the role access now let's talk about<00:07:17.639> the<00:07:17.880> gas<00:07:18.120> gas<00:07:18.660> obstruction 00:07:20.089 --> 00:07:20.099 align:start position:0% about the gas gas obstruction 00:07:20.099 --> 00:07:23.029 align:start position:0% about the gas gas obstruction with<00:07:20.580> normal<00:07:20.819> accounts<00:07:21.500> the<00:07:22.500> account<00:07:22.620> has<00:07:22.860> to 00:07:23.029 --> 00:07:23.039 align:start position:0% with normal accounts the account has to 00:07:23.039 --> 00:07:24.230 align:start position:0% with normal accounts the account has to have<00:07:23.099> if<00:07:23.280> in<00:07:23.580> order<00:07:23.639> to<00:07:23.759> pay<00:07:23.940> for<00:07:24.060> the 00:07:24.230 --> 00:07:24.240 align:start position:0% have if in order to pay for the 00:07:24.240 --> 00:07:25.129 align:start position:0% have if in order to pay for the transaction 00:07:25.129 --> 00:07:25.139 align:start position:0% transaction 00:07:25.139 --> 00:07:26.870 align:start position:0% transaction with<00:07:25.680> account<00:07:25.800> obstruction<00:07:26.220> we<00:07:26.580> want<00:07:26.759> to 00:07:26.870 --> 00:07:26.880 align:start position:0% with account obstruction we want to 00:07:26.880 --> 00:07:29.689 align:start position:0% with account obstruction we want to abstract<00:07:27.419> away<00:07:27.720> the<00:07:28.199> gas<00:07:28.319> we<00:07:29.039> want<00:07:29.220> to<00:07:29.280> be<00:07:29.460> able 00:07:29.689 --> 00:07:29.699 align:start position:0% abstract away the gas we want to be able 00:07:29.699 --> 00:07:31.430 align:start position:0% abstract away the gas we want to be able for 00:07:31.430 --> 00:07:31.440 align:start position:0% for 00:07:31.440 --> 00:07:32.930 align:start position:0% for a third<00:07:31.860> party<00:07:32.039> to<00:07:32.280> pay<00:07:32.400> for<00:07:32.520> a<00:07:32.639> transaction 00:07:32.930 --> 00:07:32.940 align:start position:0% a third party to pay for a transaction 00:07:32.940 --> 00:07:36.409 align:start position:0% a third party to pay for a transaction which<00:07:33.780> is<00:07:34.020> very<00:07:34.380> very<00:07:34.699> good<00:07:35.699> for<00:07:35.880> onboarding 00:07:36.409 --> 00:07:36.419 align:start position:0% which is very very good for onboarding 00:07:36.419 --> 00:07:39.290 align:start position:0% which is very very good for onboarding like<00:07:37.020> adapt<00:07:37.560> want<00:07:37.740> to<00:07:37.919> pay<00:07:38.099> for<00:07:38.880> transaction 00:07:39.290 --> 00:07:39.300 align:start position:0% like adapt want to pay for transaction 00:07:39.300 --> 00:07:43.430 align:start position:0% like adapt want to pay for transaction for<00:07:39.599> is<00:07:40.259> deployment<00:07:40.800> of<00:07:41.580> each<00:07:41.759> client<00:07:42.440> or 00:07:43.430 --> 00:07:43.440 align:start position:0% for is deployment of each client or 00:07:43.440 --> 00:07:45.710 align:start position:0% for is deployment of each client or client<00:07:43.680> that<00:07:43.800> uses<00:07:44.099> its<00:07:44.280> own<00:07:44.340> account 00:07:45.710 --> 00:07:45.720 align:start position:0% client that uses its own account 00:07:45.720 --> 00:07:48.589 align:start position:0% client that uses its own account if<00:07:46.080> you<00:07:46.199> have<00:07:46.440> a<00:07:46.800> token<00:07:47.400> it<00:07:47.819> might<00:07:47.940> be<00:07:48.120> useful 00:07:48.589 --> 00:07:48.599 align:start position:0% if you have a token it might be useful 00:07:48.599 --> 00:07:50.990 align:start position:0% if you have a token it might be useful to<00:07:48.780> use<00:07:48.900> your<00:07:49.080> own<00:07:49.199> token<00:07:49.560> your<00:07:50.039> for<00:07:50.580> the<00:07:50.759> so 00:07:50.990 --> 00:07:51.000 align:start position:0% to use your own token your for the so 00:07:51.000 --> 00:07:53.089 align:start position:0% to use your own token your for the so the<00:07:51.120> user<00:07:51.360> will<00:07:51.539> be<00:07:51.660> able<00:07:51.780> to<00:07:51.900> pay<00:07:52.139> with<00:07:52.680> your 00:07:53.089 --> 00:07:53.099 align:start position:0% the user will be able to pay with your 00:07:53.099 --> 00:07:55.790 align:start position:0% the user will be able to pay with your dapps<00:07:53.639> token<00:07:53.940> for<00:07:54.660> transactions 00:07:55.790 --> 00:07:55.800 align:start position:0% dapps token for transactions 00:07:55.800 --> 00:07:59.689 align:start position:0% dapps token for transactions and<00:07:56.759> for<00:07:56.940> Traders<00:07:57.900> if<00:07:58.440> a<00:07:58.620> Trader<00:07:59.099> want<00:07:59.520> to 00:07:59.689 --> 00:07:59.699 align:start position:0% and for Traders if a Trader want to 00:07:59.699 --> 00:08:02.990 align:start position:0% and for Traders if a Trader want to trade<00:07:59.940> on<00:08:00.120> uniswap<00:08:00.780> with<00:08:01.440> a<00:08:01.800> die<00:08:02.220> why<00:08:02.880> should 00:08:02.990 --> 00:08:03.000 align:start position:0% trade on uniswap with a die why should 00:08:03.000 --> 00:08:05.029 align:start position:0% trade on uniswap with a die why should he<00:08:03.180> have<00:08:03.300> Heath<00:08:03.660> to<00:08:03.780> pay<00:08:03.900> for<00:08:04.020> gas<00:08:04.199> he<00:08:04.500> has<00:08:04.800> died 00:08:05.029 --> 00:08:05.039 align:start position:0% he have Heath to pay for gas he has died 00:08:05.039 --> 00:08:07.070 align:start position:0% he have Heath to pay for gas he has died why<00:08:05.280> not<00:08:05.460> pay<00:08:05.699> with<00:08:05.940> that<00:08:06.120> so<00:08:06.599> paying<00:08:06.960> with 00:08:07.070 --> 00:08:07.080 align:start position:0% why not pay with that so paying with 00:08:07.080 --> 00:08:10.909 align:start position:0% why not pay with that so paying with token<00:08:07.500> is<00:08:07.860> a<00:08:08.460> cool<00:08:08.880> use<00:08:09.180> case<00:08:09.419> that<00:08:10.199> we<00:08:10.440> really 00:08:10.909 --> 00:08:10.919 align:start position:0% token is a cool use case that we really 00:08:10.919 --> 00:08:13.670 align:start position:0% token is a cool use case that we really want<00:08:11.099> to<00:08:11.220> have<00:08:11.400> a 00:08:13.670 --> 00:08:13.680 align:start position:0% want to have a 00:08:13.680 --> 00:08:17.330 align:start position:0% want to have a in<00:08:14.039> in<00:08:14.160> the<00:08:14.940> system<00:08:15.259> a<00:08:16.259> privacy 00:08:17.330 --> 00:08:17.340 align:start position:0% in in the system a privacy 00:08:17.340 --> 00:08:20.510 align:start position:0% in in the system a privacy if<00:08:17.940> you<00:08:18.419> think<00:08:18.599> about<00:08:18.720> it<00:08:18.960> if<00:08:19.319> you<00:08:19.500> go<00:08:19.740> and<00:08:20.340> you 00:08:20.510 --> 00:08:20.520 align:start position:0% if you think about it if you go and you 00:08:20.520 --> 00:08:22.309 align:start position:0% if you think about it if you go and you want<00:08:20.639> to<00:08:20.759> protect<00:08:21.180> this<00:08:21.300> privacy<00:08:21.720> and<00:08:21.900> use<00:08:22.080> a 00:08:22.309 --> 00:08:22.319 align:start position:0% want to protect this privacy and use a 00:08:22.319 --> 00:08:25.010 align:start position:0% want to protect this privacy and use a mixer<00:08:22.800> like<00:08:23.099> to<00:08:23.340> another<00:08:23.580> cache<00:08:24.000> or<00:08:24.180> other 00:08:25.010 --> 00:08:25.020 align:start position:0% mixer like to another cache or other 00:08:25.020 --> 00:08:26.749 align:start position:0% mixer like to another cache or other and 00:08:26.749 --> 00:08:26.759 align:start position:0% and 00:08:26.759 --> 00:08:28.490 align:start position:0% and yes<00:08:27.180> you<00:08:27.419> put<00:08:27.539> the<00:08:27.660> money<00:08:27.780> in<00:08:27.960> now<00:08:28.139> we<00:08:28.319> want<00:08:28.440> to 00:08:28.490 --> 00:08:28.500 align:start position:0% yes you put the money in now we want to 00:08:28.500 --> 00:08:31.670 align:start position:0% yes you put the money in now we want to get<00:08:28.620> the<00:08:28.740> money<00:08:28.979> out<00:08:29.300> but<00:08:30.300> you<00:08:31.080> have<00:08:31.259> to<00:08:31.440> have 00:08:31.670 --> 00:08:31.680 align:start position:0% get the money out but you have to have 00:08:31.680 --> 00:08:34.969 align:start position:0% get the money out but you have to have gas<00:08:31.919> in<00:08:32.399> order<00:08:32.520> to<00:08:32.880> withdraw<00:08:33.539> this<00:08:33.779> amount<00:08:34.200> how 00:08:34.969 --> 00:08:34.979 align:start position:0% gas in order to withdraw this amount how 00:08:34.979 --> 00:08:36.889 align:start position:0% gas in order to withdraw this amount how did<00:08:35.159> you<00:08:35.279> get<00:08:35.399> that<00:08:35.520> gas<00:08:35.700> from<00:08:36.180> some<00:08:36.300> kyc 00:08:36.889 --> 00:08:36.899 align:start position:0% did you get that gas from some kyc 00:08:36.899 --> 00:08:39.050 align:start position:0% did you get that gas from some kyc account<00:08:37.140> so<00:08:37.860> you're<00:08:38.279> not<00:08:38.459> really<00:08:38.580> Anonymous 00:08:39.050 --> 00:08:39.060 align:start position:0% account so you're not really Anonymous 00:08:39.060 --> 00:08:42.529 align:start position:0% account so you're not really Anonymous when<00:08:39.719> you<00:08:39.839> withdraw<00:08:40.260> funds<00:08:41.219> from<00:08:41.520> a 00:08:42.529 --> 00:08:42.539 align:start position:0% when you withdraw funds from a 00:08:42.539 --> 00:08:45.829 align:start position:0% when you withdraw funds from a mixer<00:08:43.440> you<00:08:43.680> are<00:08:43.800> not<00:08:43.979> Anonymous<00:08:44.520> even<00:08:44.880> though 00:08:45.829 --> 00:08:45.839 align:start position:0% mixer you are not Anonymous even though 00:08:45.839 --> 00:08:48.230 align:start position:0% mixer you are not Anonymous even though you<00:08:46.080> would<00:08:46.380> like<00:08:46.500> to<00:08:46.620> be<00:08:46.740> so 00:08:48.230 --> 00:08:48.240 align:start position:0% you would like to be so 00:08:48.240 --> 00:08:50.509 align:start position:0% you would like to be so if<00:08:48.480> you're<00:08:48.600> using<00:08:48.899> a<00:08:49.019> count<00:08:49.440> absorption<00:08:49.980> model 00:08:50.509 --> 00:08:50.519 align:start position:0% if you're using a count absorption model 00:08:50.519 --> 00:08:53.509 align:start position:0% if you're using a count absorption model you<00:08:51.180> can<00:08:51.300> use 00:08:53.509 --> 00:08:53.519 align:start position:0% you can use 00:08:53.519 --> 00:08:56.050 align:start position:0% you can use part<00:08:54.120> of<00:08:54.360> the<00:08:54.600> amount<00:08:55.260> that<00:08:55.380> you<00:08:55.560> withdraw 00:08:56.050 --> 00:08:56.060 align:start position:0% part of the amount that you withdraw 00:08:56.060 --> 00:09:00.290 align:start position:0% part of the amount that you withdraw from<00:08:57.060> the<00:08:57.180> mixer<00:08:57.540> is<00:08:58.260> a<00:08:58.500> gas<00:08:58.680> payment 00:09:00.290 --> 00:09:00.300 align:start position:0% from the mixer is a gas payment 00:09:00.300 --> 00:09:02.630 align:start position:0% from the mixer is a gas payment so<00:09:00.839> this<00:09:01.200> way<00:09:01.320> you<00:09:01.620> can<00:09:01.740> withdraw<00:09:02.220> and 00:09:02.630 --> 00:09:02.640 align:start position:0% so this way you can withdraw and 00:09:02.640 --> 00:09:05.870 align:start position:0% so this way you can withdraw and completely<00:09:03.600> Anonymous<00:09:04.080> from<00:09:04.440> a<00:09:04.620> mixer 00:09:05.870 --> 00:09:05.880 align:start position:0% completely Anonymous from a mixer 00:09:05.880 --> 00:09:08.389 align:start position:0% completely Anonymous from a mixer well<00:09:06.300> one<00:09:06.600> thing<00:09:06.720> quick<00:09:07.080> to<00:09:07.320> add<00:09:07.500> is<00:09:08.040> the<00:09:08.279> gas 00:09:08.389 --> 00:09:08.399 align:start position:0% well one thing quick to add is the gas 00:09:08.399 --> 00:09:11.030 align:start position:0% well one thing quick to add is the gas sponsorship<00:09:08.880> model<00:09:09.120> is<00:09:09.360> very<00:09:09.540> flexible 00:09:11.030 --> 00:09:11.040 align:start position:0% sponsorship model is very flexible 00:09:11.040 --> 00:09:13.070 align:start position:0% sponsorship model is very flexible um<00:09:11.100> toll<00:09:11.580> gave<00:09:11.760> an<00:09:11.880> example<00:09:12.120> of<00:09:12.420> onboarding 00:09:13.070 --> 00:09:13.080 align:start position:0% um toll gave an example of onboarding 00:09:13.080 --> 00:09:14.269 align:start position:0% um toll gave an example of onboarding where<00:09:13.320> you're<00:09:13.440> subsidizing<00:09:13.980> the<00:09:14.040> fee 00:09:14.269 --> 00:09:14.279 align:start position:0% where you're subsidizing the fee 00:09:14.279 --> 00:09:16.370 align:start position:0% where you're subsidizing the fee entirely<00:09:14.700> but<00:09:15.360> you<00:09:15.540> can<00:09:15.720> have<00:09:15.839> arbitrary 00:09:16.370 --> 00:09:16.380 align:start position:0% entirely but you can have arbitrary 00:09:16.380 --> 00:09:19.250 align:start position:0% entirely but you can have arbitrary logic<00:09:16.800> it's<00:09:17.160> implemented<00:09:17.700> by<00:09:17.880> a<00:09:18.060> contract<00:09:18.420> you 00:09:19.250 --> 00:09:19.260 align:start position:0% logic it's implemented by a contract you 00:09:19.260 --> 00:09:21.230 align:start position:0% logic it's implemented by a contract you can<00:09:19.380> limit<00:09:19.500> that<00:09:19.800> in<00:09:19.920> any<00:09:20.040> way<00:09:20.279> you<00:09:20.459> want<00:09:20.700> you 00:09:21.230 --> 00:09:21.240 align:start position:0% can limit that in any way you want you 00:09:21.240 --> 00:09:23.030 align:start position:0% can limit that in any way you want you can<00:09:21.360> subsidize<00:09:21.899> if<00:09:22.140> you<00:09:22.260> want<00:09:22.440> only<00:09:22.740> some 00:09:23.030 --> 00:09:23.040 align:start position:0% can subsidize if you want only some 00:09:23.040 --> 00:09:26.090 align:start position:0% can subsidize if you want only some transactions<00:09:23.959> you<00:09:24.959> can<00:09:25.080> make<00:09:25.320> a<00:09:25.680> user<00:09:25.980> is 00:09:26.090 --> 00:09:26.100 align:start position:0% transactions you can make a user is 00:09:26.100 --> 00:09:28.430 align:start position:0% transactions you can make a user is authenticate<00:09:26.580> in<00:09:26.760> some<00:09:26.940> way<00:09:27.140> you<00:09:28.140> can<00:09:28.200> decide 00:09:28.430 --> 00:09:28.440 align:start position:0% authenticate in some way you can decide 00:09:28.440 --> 00:09:30.130 align:start position:0% authenticate in some way you can decide only<00:09:28.620> to<00:09:28.860> subsidize 00:09:30.130 --> 00:09:30.140 align:start position:0% only to subsidize 00:09:30.140 --> 00:09:33.290 align:start position:0% only to subsidize governance<00:09:31.140> actions<00:09:31.860> I<00:09:32.160> mean<00:09:32.339> it's<00:09:32.820> arbitrary 00:09:33.290 --> 00:09:33.300 align:start position:0% governance actions I mean it's arbitrary 00:09:33.300 --> 00:09:35.269 align:start position:0% governance actions I mean it's arbitrary logic<00:09:33.720> so<00:09:33.959> anything<00:09:34.260> you<00:09:34.620> want<00:09:34.800> you<00:09:35.040> can<00:09:35.160> do 00:09:35.269 --> 00:09:35.279 align:start position:0% logic so anything you want you can do 00:09:35.279 --> 00:09:38.210 align:start position:0% logic so anything you want you can do with<00:09:35.459> this<00:09:35.700> just<00:09:36.480> you<00:09:36.779> decide<00:09:37.140> what<00:09:38.100> the 00:09:38.210 --> 00:09:38.220 align:start position:0% with this just you decide what the 00:09:38.220 --> 00:09:40.070 align:start position:0% with this just you decide what the conditions<00:09:38.580> are<00:09:38.760> including<00:09:39.240> asking<00:09:39.720> for 00:09:40.070 --> 00:09:40.080 align:start position:0% conditions are including asking for 00:09:40.080 --> 00:09:42.829 align:start position:0% conditions are including asking for repayment<00:09:40.800> in<00:09:40.980> another<00:09:41.100> token 00:09:42.829 --> 00:09:42.839 align:start position:0% repayment in another token 00:09:42.839 --> 00:09:45.050 align:start position:0% repayment in another token as<00:09:43.440> I<00:09:43.620> said<00:09:43.740> all<00:09:44.220> of<00:09:44.339> these<00:09:44.459> are<00:09:44.640> features<00:09:44.940> that 00:09:45.050 --> 00:09:45.060 align:start position:0% as I said all of these are features that 00:09:45.060 --> 00:09:46.850 align:start position:0% as I said all of these are features that you<00:09:45.180> have<00:09:45.300> to<00:09:45.360> implement<00:09:45.600> we<00:09:46.140> implement<00:09:46.500> the 00:09:46.850 --> 00:09:46.860 align:start position:0% you have to implement we implement the 00:09:46.860 --> 00:09:48.050 align:start position:0% you have to implement we implement the infrastructure 00:09:48.050 --> 00:09:48.060 align:start position:0% infrastructure 00:09:48.060 --> 00:09:50.449 align:start position:0% infrastructure I'm<00:09:48.300> only<00:09:48.480> suggesting<00:09:48.980> a<00:09:49.980> cross<00:09:50.220> chain 00:09:50.449 --> 00:09:50.459 align:start position:0% I'm only suggesting a cross chain 00:09:50.459 --> 00:09:51.710 align:start position:0% I'm only suggesting a cross chain operation 00:09:51.710 --> 00:09:51.720 align:start position:0% operation 00:09:51.720 --> 00:09:53.389 align:start position:0% operation a 00:09:53.389 --> 00:09:53.399 align:start position:0% a 00:09:53.399 --> 00:09:55.490 align:start position:0% a since<00:09:53.700> we<00:09:53.940> are<00:09:54.000> abstracting<00:09:54.420> as<00:09:54.600> we<00:09:55.200> have<00:09:55.380> a 00:09:55.490 --> 00:09:55.500 align:start position:0% since we are abstracting as we have a 00:09:55.500 --> 00:09:57.470 align:start position:0% since we are abstracting as we have a contract<00:09:55.740> you<00:09:56.339> have<00:09:56.459> a<00:09:56.640> contract<00:09:56.880> that<00:09:57.120> can 00:09:57.470 --> 00:09:57.480 align:start position:0% contract you have a contract that can 00:09:57.480 --> 00:09:59.449 align:start position:0% contract you have a contract that can pay<00:09:58.019> for<00:09:58.200> its<00:09:58.380> own<00:09:58.500> deployment<00:09:58.860> and<00:09:59.279> you<00:09:59.339> have 00:09:59.449 --> 00:09:59.459 align:start position:0% pay for its own deployment and you have 00:09:59.459 --> 00:10:02.509 align:start position:0% pay for its own deployment and you have a<00:09:59.580> mechanism<00:09:59.940> that<00:10:00.240> can<00:10:00.480> pay<00:10:01.140> for<00:10:01.519> the 00:10:02.509 --> 00:10:02.519 align:start position:0% a mechanism that can pay for the 00:10:02.519 --> 00:10:03.650 align:start position:0% a mechanism that can pay for the deployment<00:10:02.820> and<00:10:03.120> for<00:10:03.300> execution 00:10:03.650 --> 00:10:03.660 align:start position:0% deployment and for execution 00:10:03.660 --> 00:10:05.810 align:start position:0% deployment and for execution transactions<00:10:04.320> the<00:10:05.160> next<00:10:05.279> thing<00:10:05.399> to<00:10:05.580> think 00:10:05.810 --> 00:10:05.820 align:start position:0% transactions the next thing to think 00:10:05.820 --> 00:10:07.850 align:start position:0% transactions the next thing to think about<00:10:06.000> is<00:10:06.720> that<00:10:06.899> I<00:10:07.080> want<00:10:07.200> to<00:10:07.320> make<00:10:07.440> operation 00:10:07.850 --> 00:10:07.860 align:start position:0% about is that I want to make operation 00:10:07.860 --> 00:10:10.850 align:start position:0% about is that I want to make operation on<00:10:08.399> multiple<00:10:09.060> networks<00:10:09.779> I<00:10:10.260> am<00:10:10.440> on<00:10:10.560> first 00:10:10.850 --> 00:10:10.860 align:start position:0% on multiple networks I am on first 00:10:10.860 --> 00:10:14.210 align:start position:0% on multiple networks I am on first Network<00:10:11.100> I<00:10:11.519> can<00:10:11.760> pay<00:10:11.940> on<00:10:12.120> there<00:10:12.779> but<00:10:13.560> I<00:10:13.980> want<00:10:14.100> to 00:10:14.210 --> 00:10:14.220 align:start position:0% Network I can pay on there but I want to 00:10:14.220 --> 00:10:17.449 align:start position:0% Network I can pay on there but I want to use<00:10:14.519> my<00:10:15.000> account<00:10:15.240> on<00:10:15.720> other<00:10:15.959> networks 00:10:17.449 --> 00:10:17.459 align:start position:0% use my account on other networks 00:10:17.459 --> 00:10:20.269 align:start position:0% use my account on other networks so<00:10:18.060> it<00:10:18.420> is<00:10:18.540> possible<00:10:18.839> to<00:10:19.080> create<00:10:19.260> a<00:10:19.860> paymaster 00:10:20.269 --> 00:10:20.279 align:start position:0% so it is possible to create a paymaster 00:10:20.279 --> 00:10:23.389 align:start position:0% so it is possible to create a paymaster mechanism<00:10:20.760> a<00:10:21.180> payment<00:10:21.839> mechanism<00:10:22.320> that<00:10:23.160> I 00:10:23.389 --> 00:10:23.399 align:start position:0% mechanism a payment mechanism that I 00:10:23.399 --> 00:10:24.949 align:start position:0% mechanism a payment mechanism that I will<00:10:23.519> be<00:10:23.700> able<00:10:23.820> to<00:10:23.940> perform<00:10:24.120> that<00:10:24.600> operation 00:10:24.949 --> 00:10:24.959 align:start position:0% will be able to perform that operation 00:10:24.959 --> 00:10:28.009 align:start position:0% will be able to perform that operation on<00:10:25.260> those<00:10:25.500> and<00:10:26.160> other<00:10:26.459> network 00:10:28.009 --> 00:10:28.019 align:start position:0% on those and other network 00:10:28.019 --> 00:10:30.530 align:start position:0% on those and other network if<00:10:28.200> you<00:10:28.200> use<00:10:28.500> my<00:10:28.620> signature<00:10:29.040> I<00:10:29.580> approve<00:10:30.240> these 00:10:30.530 --> 00:10:30.540 align:start position:0% if you use my signature I approve these 00:10:30.540 --> 00:10:32.509 align:start position:0% if you use my signature I approve these transactions<00:10:31.080> so<00:10:31.320> it's<00:10:31.680> not<00:10:31.860> some<00:10:32.220> other 00:10:32.509 --> 00:10:32.519 align:start position:0% transactions so it's not some other 00:10:32.519 --> 00:10:35.389 align:start position:0% transactions so it's not some other party<00:10:32.820> acting<00:10:33.480> on<00:10:33.600> my<00:10:33.779> behalf<00:10:34.019> it's<00:10:34.320> me<00:10:34.560> acting 00:10:35.389 --> 00:10:35.399 align:start position:0% party acting on my behalf it's me acting 00:10:35.399 --> 00:10:38.150 align:start position:0% party acting on my behalf it's me acting on<00:10:35.640> those<00:10:35.760> networks<00:10:36.300> but<00:10:37.260> I<00:10:37.800> don't<00:10:37.920> have<00:10:38.040> any 00:10:38.150 --> 00:10:38.160 align:start position:0% on those networks but I don't have any 00:10:38.160 --> 00:10:40.009 align:start position:0% on those networks but I don't have any balance<00:10:38.459> on<00:10:38.519> it<00:10:38.700> I<00:10:38.880> don't<00:10:39.000> have<00:10:39.240> to<00:10:39.420> have<00:10:39.660> any 00:10:40.009 --> 00:10:40.019 align:start position:0% balance on it I don't have to have any 00:10:40.019 --> 00:10:42.170 align:start position:0% balance on it I don't have to have any if<00:10:40.440> balance<00:10:40.860> or<00:10:40.980> native<00:10:41.160> token<00:10:41.760> balance<00:10:42.000> on 00:10:42.170 --> 00:10:42.180 align:start position:0% if balance or native token balance on 00:10:42.180 --> 00:10:44.150 align:start position:0% if balance or native token balance on those<00:10:42.300> Networks 00:10:44.150 --> 00:10:44.160 align:start position:0% those Networks 00:10:44.160 --> 00:10:47.269 align:start position:0% those Networks it's<00:10:44.640> a<00:10:44.880> system<00:10:45.000> that<00:10:45.360> can<00:10:45.860> move<00:10:46.860> the<00:10:47.100> payment 00:10:47.269 --> 00:10:47.279 align:start position:0% it's a system that can move the payment 00:10:47.279 --> 00:10:55.870 align:start position:0% it's a system that can move the payment between<00:10:47.640> the<00:10:48.000> networks 00:10:55.870 --> 00:10:55.880 align:start position:0% 00:10:55.880 --> 00:10:59.090 align:start position:0% why<00:10:56.880> am<00:10:57.300> I<00:10:57.360> keeping<00:10:57.600> people<00:10:57.660> moving<00:10:57.899> back 00:10:59.090 --> 00:10:59.100 align:start position:0% why am I keeping people moving back 00:10:59.100 --> 00:11:03.829 align:start position:0% why am I keeping people moving back and<00:11:00.000> lastly<00:11:00.980> we<00:11:01.980> have<00:11:02.040> a<00:11:02.160> wallet<00:11:02.459> so<00:11:02.940> there's<00:11:03.600> a 00:11:03.829 --> 00:11:03.839 align:start position:0% and lastly we have a wallet so there's a 00:11:03.839 --> 00:11:04.790 align:start position:0% and lastly we have a wallet so there's a link<00:11:03.899> for<00:11:04.140> them<00:11:04.260> for<00:11:04.560> the<00:11:04.680> entire 00:11:04.790 --> 00:11:04.800 align:start position:0% link for them for the entire 00:11:04.800 --> 00:11:06.410 align:start position:0% link for them for the entire presentation<00:11:05.220> of<00:11:05.459> the<00:11:05.579> everything<00:11:06.000> at<00:11:06.300> the 00:11:06.410 --> 00:11:06.420 align:start position:0% presentation of the everything at the 00:11:06.420 --> 00:11:09.949 align:start position:0% presentation of the everything at the end<00:11:06.480> uh 00:11:09.949 --> 00:11:09.959 align:start position:0% 00:11:09.959 --> 00:11:12.650 align:start position:0% as<00:11:10.440> we<00:11:10.560> said<00:11:10.740> with<00:11:11.100> the<00:11:11.339> eoa<00:11:11.820> accounts<00:11:12.240> I'm 00:11:12.650 --> 00:11:12.660 align:start position:0% as we said with the eoa accounts I'm 00:11:12.660 --> 00:11:14.210 align:start position:0% as we said with the eoa accounts I'm limited<00:11:13.079> for<00:11:13.320> performing<00:11:13.800> a<00:11:13.920> single 00:11:14.210 --> 00:11:14.220 align:start position:0% limited for performing a single 00:11:14.220 --> 00:11:17.210 align:start position:0% limited for performing a single operation<00:11:14.579> at<00:11:14.760> a<00:11:14.940> time<00:11:15.260> which<00:11:16.260> cannot<00:11:17.100> be 00:11:17.210 --> 00:11:17.220 align:start position:0% operation at a time which cannot be 00:11:17.220 --> 00:11:19.310 align:start position:0% operation at a time which cannot be batched<00:11:17.640> and<00:11:17.760> cannot<00:11:18.120> and<00:11:18.420> requires<00:11:19.019> a 00:11:19.310 --> 00:11:19.320 align:start position:0% batched and cannot and requires a 00:11:19.320 --> 00:11:21.230 align:start position:0% batched and cannot and requires a exception<00:11:19.740> on<00:11:19.860> each<00:11:19.980> operation<00:11:20.339> it's<00:11:21.000> very 00:11:21.230 --> 00:11:21.240 align:start position:0% exception on each operation it's very 00:11:21.240 --> 00:11:23.269 align:start position:0% exception on each operation it's very easy<00:11:21.360> to<00:11:21.540> add<00:11:21.660> to<00:11:21.839> a<00:11:22.019> Wallet<00:11:22.500> account 00:11:23.269 --> 00:11:23.279 align:start position:0% easy to add to a Wallet account 00:11:23.279 --> 00:11:26.810 align:start position:0% easy to add to a Wallet account create<00:11:23.760> performing<00:11:24.360> a<00:11:24.540> batch<00:11:24.980> and<00:11:25.980> doing 00:11:26.810 --> 00:11:26.820 align:start position:0% create performing a batch and doing 00:11:26.820 --> 00:11:28.990 align:start position:0% create performing a batch and doing atomically<00:11:27.420> a<00:11:27.660> sequence<00:11:27.959> of<00:11:28.079> operation 00:11:28.990 --> 00:11:29.000 align:start position:0% atomically a sequence of operation 00:11:29.000 --> 00:11:31.730 align:start position:0% atomically a sequence of operation another<00:11:30.000> use<00:11:30.360> case<00:11:30.540> we<00:11:30.959> can<00:11:31.079> see<00:11:31.260> that<00:11:31.560> you 00:11:31.730 --> 00:11:31.740 align:start position:0% another use case we can see that you 00:11:31.740 --> 00:11:33.230 align:start position:0% another use case we can see that you want<00:11:32.040> a 00:11:33.230 --> 00:11:33.240 align:start position:0% want a 00:11:33.240 --> 00:11:35.930 align:start position:0% want a Atomic<00:11:33.779> operation<00:11:34.140> or<00:11:34.440> a<00:11:34.680> delayed<00:11:35.220> operation 00:11:35.930 --> 00:11:35.940 align:start position:0% Atomic operation or a delayed operation 00:11:35.940 --> 00:11:38.210 align:start position:0% Atomic operation or a delayed operation that<00:11:36.360> is<00:11:36.480> I<00:11:36.839> create<00:11:37.019> an<00:11:37.260> operation<00:11:37.620> and<00:11:37.980> I<00:11:38.100> want 00:11:38.210 --> 00:11:38.220 align:start position:0% that is I create an operation and I want 00:11:38.220 --> 00:11:40.250 align:start position:0% that is I create an operation and I want it<00:11:38.339> to<00:11:38.519> be<00:11:38.700> executed<00:11:39.360> later 00:11:40.250 --> 00:11:40.260 align:start position:0% it to be executed later 00:11:40.260 --> 00:11:42.470 align:start position:0% it to be executed later a<00:11:40.500> service<00:11:40.680> can<00:11:40.920> do<00:11:41.100> it<00:11:41.160> and<00:11:41.279> again<00:11:41.399> it<00:11:42.000> is<00:11:42.180> my 00:11:42.470 --> 00:11:42.480 align:start position:0% a service can do it and again it is my 00:11:42.480 --> 00:11:44.449 align:start position:0% a service can do it and again it is my account<00:11:42.720> that<00:11:43.620> performs<00:11:43.980> this<00:11:44.100> operation 00:11:44.449 --> 00:11:44.459 align:start position:0% account that performs this operation 00:11:44.459 --> 00:11:48.110 align:start position:0% account that performs this operation because<00:11:44.820> I<00:11:45.779> gave<00:11:45.899> some<00:11:46.200> service<00:11:46.820> the<00:11:47.820> rights 00:11:48.110 --> 00:11:48.120 align:start position:0% because I gave some service the rights 00:11:48.120 --> 00:11:54.970 align:start position:0% because I gave some service the rights to<00:11:48.240> do<00:11:48.360> it<00:11:48.480> at<00:11:49.079> a<00:11:49.200> later<00:11:49.320> time 00:11:54.970 --> 00:11:54.980 align:start position:0% 00:11:54.980 --> 00:11:59.150 align:start position:0% uh<00:11:55.980> okay<00:11:56.660> these<00:11:57.660> are<00:11:57.720> all<00:11:57.839> cool<00:11:58.019> ideas<00:11:58.200> some<00:11:59.040> of 00:11:59.150 --> 00:11:59.160 align:start position:0% uh okay these are all cool ideas some of 00:11:59.160 --> 00:12:01.490 align:start position:0% uh okay these are all cool ideas some of them<00:11:59.279> are<00:11:59.519> very<00:11:59.700> old<00:11:59.880> some<00:12:00.380> regarding<00:12:01.380> just 00:12:01.490 --> 00:12:01.500 align:start position:0% them are very old some regarding just 00:12:01.500 --> 00:12:02.930 align:start position:0% them are very old some regarding just the<00:12:01.680> event<00:12:01.740> driven<00:12:02.160> flows<00:12:02.519> because<00:12:02.700> they're 00:12:02.930 --> 00:12:02.940 align:start position:0% the event driven flows because they're 00:12:02.940 --> 00:12:05.090 align:start position:0% the event driven flows because they're very<00:12:03.180> interesting<00:12:03.620> maybe<00:12:04.620> a<00:12:04.860> couple<00:12:04.980> of 00:12:05.090 --> 00:12:05.100 align:start position:0% very interesting maybe a couple of 00:12:05.100 --> 00:12:07.550 align:start position:0% very interesting maybe a couple of examples<00:12:05.579> one<00:12:06.480> let's<00:12:06.779> say<00:12:06.899> there's<00:12:07.140> an<00:12:07.320> nft 00:12:07.550 --> 00:12:07.560 align:start position:0% examples one let's say there's an nft 00:12:07.560 --> 00:12:09.829 align:start position:0% examples one let's say there's an nft that<00:12:07.860> means<00:12:08.160> at<00:12:08.279> a<00:12:08.399> certain<00:12:08.519> time<00:12:08.760> then<00:12:09.540> you 00:12:09.829 --> 00:12:09.839 align:start position:0% that means at a certain time then you 00:12:09.839 --> 00:12:10.790 align:start position:0% that means at a certain time then you don't<00:12:09.899> have<00:12:10.019> to<00:12:10.140> wait<00:12:10.260> in<00:12:10.440> front<00:12:10.560> of<00:12:10.680> your 00:12:10.790 --> 00:12:10.800 align:start position:0% don't have to wait in front of your 00:12:10.800 --> 00:12:13.430 align:start position:0% don't have to wait in front of your computer<00:12:11.180> and<00:12:12.180> then<00:12:12.300> you<00:12:12.540> just<00:12:12.720> like<00:12:13.079> create 00:12:13.430 --> 00:12:13.440 align:start position:0% computer and then you just like create 00:12:13.440 --> 00:12:15.050 align:start position:0% computer and then you just like create the<00:12:13.680> transaction<00:12:13.980> then<00:12:14.339> you<00:12:14.940> could 00:12:15.050 --> 00:12:15.060 align:start position:0% the transaction then you could 00:12:15.060 --> 00:12:17.569 align:start position:0% the transaction then you could pre-register<00:12:15.600> the<00:12:15.839> transaction<00:12:16.200> into<00:12:16.680> into<00:12:17.220> a 00:12:17.569 --> 00:12:17.579 align:start position:0% pre-register the transaction into into a 00:12:17.579 --> 00:12:19.610 align:start position:0% pre-register the transaction into into a like<00:12:18.000> a<00:12:18.180> registry<00:12:18.480> contract<00:12:18.899> of<00:12:19.200> pending 00:12:19.610 --> 00:12:19.620 align:start position:0% like a registry contract of pending 00:12:19.620 --> 00:12:21.710 align:start position:0% like a registry contract of pending transactions<00:12:20.100> and<00:12:20.339> then<00:12:20.459> Searchers<00:12:21.000> you 00:12:21.710 --> 00:12:21.720 align:start position:0% transactions and then Searchers you 00:12:21.720 --> 00:12:23.590 align:start position:0% transactions and then Searchers you provide<00:12:21.959> them<00:12:22.079> an<00:12:22.260> incentive<00:12:22.680> to 00:12:23.590 --> 00:12:23.600 align:start position:0% provide them an incentive to 00:12:23.600 --> 00:12:25.670 align:start position:0% provide them an incentive to execute<00:12:24.600> the<00:12:24.720> transaction<00:12:25.019> when<00:12:25.380> the<00:12:25.560> time 00:12:25.670 --> 00:12:25.680 align:start position:0% execute the transaction when the time 00:12:25.680 --> 00:12:26.990 align:start position:0% execute the transaction when the time comes<00:12:26.040> and<00:12:26.279> they're<00:12:26.399> competing<00:12:26.760> with<00:12:26.880> each 00:12:26.990 --> 00:12:27.000 align:start position:0% comes and they're competing with each 00:12:27.000 --> 00:12:28.550 align:start position:0% comes and they're competing with each other<00:12:27.120> right<00:12:27.720> now<00:12:27.959> the<00:12:28.019> use<00:12:28.200> case<00:12:28.320> would<00:12:28.500> be 00:12:28.550 --> 00:12:28.560 align:start position:0% other right now the use case would be 00:12:28.560 --> 00:12:30.290 align:start position:0% other right now the use case would be let's<00:12:28.740> say<00:12:28.860> you<00:12:28.980> want<00:12:29.160> to<00:12:29.220> perform<00:12:29.399> some<00:12:30.060> trade 00:12:30.290 --> 00:12:30.300 align:start position:0% let's say you want to perform some trade 00:12:30.300 --> 00:12:31.490 align:start position:0% let's say you want to perform some trade in<00:12:30.480> the<00:12:30.600> future<00:12:30.660> or<00:12:30.839> pending<00:12:31.200> on<00:12:31.320> certain 00:12:31.490 --> 00:12:31.500 align:start position:0% in the future or pending on certain 00:12:31.500 --> 00:12:34.069 align:start position:0% in the future or pending on certain conditions<00:12:32.100> price 00:12:34.069 --> 00:12:34.079 align:start position:0% conditions price 00:12:34.079 --> 00:12:36.490 align:start position:0% conditions price um you<00:12:34.560> know<00:12:34.680> whatever<00:12:34.980> whatever<00:12:35.640> you<00:12:36.060> want 00:12:36.490 --> 00:12:36.500 align:start position:0% um you know whatever whatever you want 00:12:36.500 --> 00:12:39.170 align:start position:0% um you know whatever whatever you want so<00:12:37.500> all<00:12:37.680> this<00:12:37.860> becomes<00:12:38.220> possible<00:12:38.519> and<00:12:38.880> doesn't 00:12:39.170 --> 00:12:39.180 align:start position:0% so all this becomes possible and doesn't 00:12:39.180 --> 00:12:41.810 align:start position:0% so all this becomes possible and doesn't require<00:12:39.420> any<00:12:39.839> Trust 00:12:41.810 --> 00:12:41.820 align:start position:0% require any Trust 00:12:41.820 --> 00:12:51.710 align:start position:0% require any Trust foreign 00:12:51.710 --> 00:12:51.720 align:start position:0% 00:12:51.720 --> 00:12:53.870 align:start position:0% okay<00:12:52.200> with<00:12:52.680> the 00:12:53.870 --> 00:12:53.880 align:start position:0% okay with the 00:12:53.880 --> 00:12:56.449 align:start position:0% okay with the ear<00:12:54.360> three<00:12:54.720> four<00:12:55.079> three<00:12:55.380> four<00:12:55.920> three<00:12:56.220> two 00:12:56.449 --> 00:12:56.459 align:start position:0% ear three four three four three two 00:12:56.459 --> 00:12:57.170 align:start position:0% ear three four three four three two seven 00:12:57.170 --> 00:12:57.180 align:start position:0% seven 00:12:57.180 --> 00:12:59.509 align:start position:0% seven uh<00:12:58.019> we<00:12:58.440> wanted<00:12:58.500> to<00:12:58.680> create<00:12:58.800> an<00:12:59.040> implementation 00:12:59.509 --> 00:12:59.519 align:start position:0% uh we wanted to create an implementation 00:12:59.519 --> 00:13:02.810 align:start position:0% uh we wanted to create an implementation of<00:13:00.240> a<00:13:00.360> counter<00:13:00.600> obstruction<00:13:00.839> that<00:13:01.260> can<00:13:01.380> be<00:13:01.620> a 00:13:02.810 --> 00:13:02.820 align:start position:0% of a counter obstruction that can be a 00:13:02.820 --> 00:13:05.150 align:start position:0% of a counter obstruction that can be a executed<00:13:03.480> today<00:13:03.660> not<00:13:04.380> something<00:13:04.560> we<00:13:04.860> have<00:13:05.040> to 00:13:05.150 --> 00:13:05.160 align:start position:0% executed today not something we have to 00:13:05.160 --> 00:13:07.790 align:start position:0% executed today not something we have to change<00:13:05.519> the<00:13:06.060> protocol<00:13:06.839> but<00:13:07.320> something<00:13:07.440> we<00:13:07.680> can 00:13:07.790 --> 00:13:07.800 align:start position:0% change the protocol but something we can 00:13:07.800 --> 00:13:08.870 align:start position:0% change the protocol but something we can add<00:13:07.920> today 00:13:08.870 --> 00:13:08.880 align:start position:0% add today 00:13:08.880 --> 00:13:10.009 align:start position:0% add today so 00:13:10.009 --> 00:13:10.019 align:start position:0% so 00:13:10.019 --> 00:13:12.290 align:start position:0% so we<00:13:10.680> Define<00:13:10.860> a<00:13:11.100> mempool 00:13:12.290 --> 00:13:12.300 align:start position:0% we Define a mempool 00:13:12.300 --> 00:13:14.990 align:start position:0% we Define a mempool of<00:13:13.019> what<00:13:13.500> we<00:13:13.620> call<00:13:13.740> a<00:13:13.800> user<00:13:14.040> operation<00:13:14.339> user 00:13:14.990 --> 00:13:15.000 align:start position:0% of what we call a user operation user 00:13:15.000 --> 00:13:17.329 align:start position:0% of what we call a user operation user production<00:13:15.240> is<00:13:16.019> a<00:13:16.260> transaction<00:13:16.620> in<00:13:17.100> our 00:13:17.329 --> 00:13:17.339 align:start position:0% production is a transaction in our 00:13:17.339 --> 00:13:18.410 align:start position:0% production is a transaction in our terminology 00:13:18.410 --> 00:13:18.420 align:start position:0% terminology 00:13:18.420 --> 00:13:21.110 align:start position:0% terminology so<00:13:18.839> just<00:13:18.959> like<00:13:19.139> the<00:13:19.380> normal<00:13:19.560> user<00:13:19.980> a<00:13:20.279> mempool 00:13:21.110 --> 00:13:21.120 align:start position:0% so just like the normal user a mempool 00:13:21.120 --> 00:13:23.030 align:start position:0% so just like the normal user a mempool of<00:13:21.360> transaction<00:13:21.779> there<00:13:22.079> is<00:13:22.260> the<00:13:22.380> mempool<00:13:22.860> of 00:13:23.030 --> 00:13:23.040 align:start position:0% of transaction there is the mempool of 00:13:23.040 --> 00:13:25.430 align:start position:0% of transaction there is the mempool of user<00:13:23.279> operation<00:13:23.639> that<00:13:24.060> nodes<00:13:24.360> can<00:13:24.600> withdraw 00:13:25.430 --> 00:13:25.440 align:start position:0% user operation that nodes can withdraw 00:13:25.440 --> 00:13:27.530 align:start position:0% user operation that nodes can withdraw transactions<00:13:25.920> from<00:13:26.040> they 00:13:27.530 --> 00:13:27.540 align:start position:0% transactions from they 00:13:27.540 --> 00:13:32.170 align:start position:0% transactions from they collect<00:13:28.079> them<00:13:28.260> and<00:13:28.620> is<00:13:28.740> to<00:13:28.980> send<00:13:29.160> a 00:13:32.170 --> 00:13:32.180 align:start position:0% 00:13:32.180 --> 00:13:34.370 align:start position:0% to<00:13:33.180> batch<00:13:33.360> them<00:13:33.600> and<00:13:33.720> send<00:13:33.839> them<00:13:34.019> on<00:13:34.260> the 00:13:34.370 --> 00:13:34.380 align:start position:0% to batch them and send them on the 00:13:34.380 --> 00:13:35.690 align:start position:0% to batch them and send them on the network 00:13:35.690 --> 00:13:35.700 align:start position:0% network 00:13:35.700 --> 00:13:38.750 align:start position:0% network but 00:13:38.750 --> 00:13:38.760 align:start position:0% 00:13:38.760 --> 00:13:41.269 align:start position:0% the<00:13:39.240> key<00:13:39.899> thing<00:13:40.079> about<00:13:40.380> about<00:13:40.680> this<00:13:40.980> separate 00:13:41.269 --> 00:13:41.279 align:start position:0% the key thing about about this separate 00:13:41.279 --> 00:13:43.190 align:start position:0% the key thing about about this separate mempool<00:13:41.760> it's<00:13:42.060> not<00:13:42.300> a<00:13:42.480> private<00:13:42.720> mempool<00:13:43.019> like 00:13:43.190 --> 00:13:43.200 align:start position:0% mempool it's not a private mempool like 00:13:43.200 --> 00:13:45.110 align:start position:0% mempool it's not a private mempool like flashbots<00:13:43.860> it's<00:13:44.339> just<00:13:44.519> separate<00:13:44.880> because 00:13:45.110 --> 00:13:45.120 align:start position:0% flashbots it's just separate because 00:13:45.120 --> 00:13:48.410 align:start position:0% flashbots it's just separate because it's<00:13:45.420> accepting<00:13:45.899> this<00:13:46.139> this<00:13:46.440> user<00:13:46.800> operation 00:13:48.410 --> 00:13:48.420 align:start position:0% it's accepting this this user operation 00:13:48.420 --> 00:13:49.970 align:start position:0% it's accepting this this user operation um<00:13:48.480> instead<00:13:48.779> of<00:13:48.839> a<00:13:49.019> regular<00:13:49.260> transaction<00:13:49.680> but 00:13:49.970 --> 00:13:49.980 align:start position:0% um instead of a regular transaction but 00:13:49.980 --> 00:13:51.410 align:start position:0% um instead of a regular transaction but the<00:13:50.100> key<00:13:50.279> thing 00:13:51.410 --> 00:13:51.420 align:start position:0% the key thing 00:13:51.420 --> 00:13:52.970 align:start position:0% the key thing um<00:13:51.480> that's<00:13:51.839> different<00:13:52.139> about<00:13:52.380> this<00:13:52.620> is<00:13:52.860> just 00:13:52.970 --> 00:13:52.980 align:start position:0% um that's different about this is just 00:13:52.980 --> 00:13:55.730 align:start position:0% um that's different about this is just it<00:13:53.220> doesn't<00:13:53.399> require<00:13:53.760> you<00:13:54.600> to<00:13:54.839> have<00:13:55.079> like<00:13:55.560> an 00:13:55.730 --> 00:13:55.740 align:start position:0% it doesn't require you to have like an 00:13:55.740 --> 00:13:57.350 align:start position:0% it doesn't require you to have like an eua<00:13:56.100> to<00:13:56.339> interact<00:13:56.639> it<00:13:56.820> doesn't<00:13:56.940> require<00:13:57.120> you 00:13:57.350 --> 00:13:57.360 align:start position:0% eua to interact it doesn't require you 00:13:57.360 --> 00:13:59.150 align:start position:0% eua to interact it doesn't require you to<00:13:57.480> have<00:13:57.660> the<00:13:57.839> eth 00:13:59.150 --> 00:13:59.160 align:start position:0% to have the eth 00:13:59.160 --> 00:14:00.710 align:start position:0% to have the eth um the<00:13:59.399> paper<00:13:59.579> it<00:13:59.880> because<00:14:00.060> what<00:14:00.600> you're 00:14:00.710 --> 00:14:00.720 align:start position:0% um the paper it because what you're 00:14:00.720 --> 00:14:02.449 align:start position:0% um the paper it because what you're doing<00:14:00.899> is<00:14:01.079> you're<00:14:01.260> specifying<00:14:01.800> within<00:14:02.339> the 00:14:02.449 --> 00:14:02.459 align:start position:0% doing is you're specifying within the 00:14:02.459 --> 00:14:04.670 align:start position:0% doing is you're specifying within the user<00:14:02.760> operation<00:14:03.120> the<00:14:03.839> conditions<00:14:04.320> that<00:14:04.500> will 00:14:04.670 --> 00:14:04.680 align:start position:0% user operation the conditions that will 00:14:04.680 --> 00:14:07.910 align:start position:0% user operation the conditions that will make<00:14:04.800> it<00:14:04.920> worthwhile<00:14:05.279> for<00:14:05.519> bunders<00:14:06.139> to<00:14:07.139> uh 00:14:07.910 --> 00:14:07.920 align:start position:0% make it worthwhile for bunders to uh 00:14:07.920 --> 00:14:10.490 align:start position:0% make it worthwhile for bunders to uh submit<00:14:08.339> your<00:14:08.459> transaction<00:14:08.760> on<00:14:09.060> chain 00:14:10.490 --> 00:14:10.500 align:start position:0% submit your transaction on chain 00:14:10.500 --> 00:14:12.350 align:start position:0% submit your transaction on chain um and<00:14:10.740> they<00:14:10.860> they<00:14:11.100> make<00:14:11.459> sure<00:14:11.639> they<00:14:11.880> get<00:14:12.060> like 00:14:12.350 --> 00:14:12.360 align:start position:0% um and they they make sure they get like 00:14:12.360 --> 00:14:14.030 align:start position:0% um and they they make sure they get like refunded<00:14:12.779> for<00:14:12.959> gas 00:14:14.030 --> 00:14:14.040 align:start position:0% refunded for gas 00:14:14.040 --> 00:14:17.629 align:start position:0% refunded for gas um so<00:14:14.519> it<00:14:15.120> works<00:14:15.360> out 00:14:17.629 --> 00:14:17.639 align:start position:0% 00:14:17.639 --> 00:14:20.269 align:start position:0% Okay<00:14:18.060> so<00:14:18.779> our<00:14:19.200> implementation<00:14:19.740> what<00:14:19.980> it<00:14:20.160> does 00:14:20.269 --> 00:14:20.279 align:start position:0% Okay so our implementation what it does 00:14:20.279 --> 00:14:23.509 align:start position:0% Okay so our implementation what it does it<00:14:20.579> takes<00:14:21.000> I<00:14:21.420> said<00:14:21.540> these<00:14:21.720> user<00:14:22.079> operations<00:14:22.519> uh 00:14:23.509 --> 00:14:23.519 align:start position:0% it takes I said these user operations uh 00:14:23.519 --> 00:14:26.329 align:start position:0% it takes I said these user operations uh they<00:14:24.180> know<00:14:24.300> you<00:14:24.660> no<00:14:24.839> longer<00:14:25.320> need<00:14:25.560> an<00:14:25.740> eoa<00:14:26.160> to 00:14:26.329 --> 00:14:26.339 align:start position:0% they know you no longer need an eoa to 00:14:26.339 --> 00:14:28.310 align:start position:0% they know you no longer need an eoa to send<00:14:26.399> this<00:14:26.519> user<00:14:26.820> operation<00:14:27.180> the<00:14:27.959> node 00:14:28.310 --> 00:14:28.320 align:start position:0% send this user operation the node 00:14:28.320 --> 00:14:29.990 align:start position:0% send this user operation the node themselves<00:14:28.680> take<00:14:29.279> the<00:14:29.459> user<00:14:29.700> operation 00:14:29.990 --> 00:14:30.000 align:start position:0% themselves take the user operation 00:14:30.000 --> 00:14:32.150 align:start position:0% themselves take the user operation collect<00:14:30.779> them<00:14:30.899> into<00:14:31.079> batches<00:14:31.500> and<00:14:31.680> put<00:14:31.980> them 00:14:32.150 --> 00:14:32.160 align:start position:0% collect them into batches and put them 00:14:32.160 --> 00:14:34.730 align:start position:0% collect them into batches and put them on<00:14:32.519> chain<00:14:32.700> perform<00:14:33.360> the<00:14:33.660> validation 00:14:34.730 --> 00:14:34.740 align:start position:0% on chain perform the validation 00:14:34.740 --> 00:14:37.610 align:start position:0% on chain perform the validation that<00:14:35.279> is<00:14:35.480> validation<00:14:36.480> is<00:14:36.779> the<00:14:37.260> signature 00:14:37.610 --> 00:14:37.620 align:start position:0% that is validation is the signature 00:14:37.620 --> 00:14:39.710 align:start position:0% that is validation is the signature nonce<00:14:38.160> and<00:14:38.339> the<00:14:38.399> payment<00:14:38.639> and<00:14:39.420> then<00:14:39.540> perform 00:14:39.710 --> 00:14:39.720 align:start position:0% nonce and the payment and then perform 00:14:39.720 --> 00:14:41.410 align:start position:0% nonce and the payment and then perform the<00:14:39.959> execution<00:14:40.320> that 00:14:41.410 --> 00:14:41.420 align:start position:0% the execution that 00:14:41.420 --> 00:14:43.610 align:start position:0% the execution that you<00:14:42.420> want<00:14:42.480> to<00:14:42.600> make 00:14:43.610 --> 00:14:43.620 align:start position:0% you want to make 00:14:43.620 --> 00:14:45.590 align:start position:0% you want to make a 00:14:45.590 --> 00:14:45.600 align:start position:0% a 00:14:45.600 --> 00:14:48.230 align:start position:0% a if<00:14:46.019> you<00:14:46.199> read<00:14:46.320> the<00:14:46.440> AP<00:14:46.620> most<00:14:46.980> of<00:14:47.100> the<00:14:47.220> AP<00:14:47.339> is<00:14:47.940> not 00:14:48.230 --> 00:14:48.240 align:start position:0% if you read the AP most of the AP is not 00:14:48.240 --> 00:14:50.509 align:start position:0% if you read the AP most of the AP is not about<00:14:48.420> usability<00:14:49.199> about<00:14:49.620> how<00:14:49.980> wallets<00:14:50.339> work 00:14:50.509 --> 00:14:50.519 align:start position:0% about usability about how wallets work 00:14:50.519 --> 00:14:52.790 align:start position:0% about usability about how wallets work but<00:14:50.760> how<00:14:51.060> we<00:14:51.240> protect<00:14:51.540> the<00:14:51.779> network<00:14:52.139> it<00:14:52.740> is 00:14:52.790 --> 00:14:52.800 align:start position:0% but how we protect the network it is 00:14:52.800 --> 00:14:55.430 align:start position:0% but how we protect the network it is very<00:14:52.980> important<00:14:53.339> that<00:14:54.000> those<00:14:54.240> nodes<00:14:55.019> that 00:14:55.430 --> 00:14:55.440 align:start position:0% very important that those nodes that 00:14:55.440 --> 00:14:58.069 align:start position:0% very important that those nodes that handle<00:14:55.800> operations<00:14:56.639> like<00:14:57.240> when<00:14:57.600> they<00:14:57.720> handle 00:14:58.069 --> 00:14:58.079 align:start position:0% handle operations like when they handle 00:14:58.079 --> 00:14:59.410 align:start position:0% handle operations like when they handle transactions 00:14:59.410 --> 00:14:59.420 align:start position:0% transactions 00:14:59.420 --> 00:15:02.150 align:start position:0% transactions are<00:15:00.420> not<00:15:00.600> susceptible<00:15:01.320> to<00:15:01.500> denial<00:15:01.920> of<00:15:02.040> service 00:15:02.150 --> 00:15:02.160 align:start position:0% are not susceptible to denial of service 00:15:02.160 --> 00:15:03.230 align:start position:0% are not susceptible to denial of service attacks 00:15:03.230 --> 00:15:03.240 align:start position:0% attacks 00:15:03.240 --> 00:15:05.569 align:start position:0% attacks so<00:15:03.660> we<00:15:04.079> had<00:15:04.260> a<00:15:04.440> lot<00:15:04.500> of<00:15:04.560> mechanism 00:15:05.569 --> 00:15:05.579 align:start position:0% so we had a lot of mechanism 00:15:05.579 --> 00:15:07.129 align:start position:0% so we had a lot of mechanism to<00:15:05.940> make<00:15:06.060> sure<00:15:06.180> that<00:15:06.420> they<00:15:06.779> cannot<00:15:07.019> be 00:15:07.129 --> 00:15:07.139 align:start position:0% to make sure that they cannot be 00:15:07.139 --> 00:15:08.389 align:start position:0% to make sure that they cannot be attacked 00:15:08.389 --> 00:15:08.399 align:start position:0% attacked 00:15:08.399 --> 00:15:11.150 align:start position:0% attacked so<00:15:08.880> we<00:15:09.660> batch<00:15:10.079> them<00:15:10.320> together 00:15:11.150 --> 00:15:11.160 align:start position:0% so we batch them together 00:15:11.160 --> 00:15:13.550 align:start position:0% so we batch them together so<00:15:11.699> that<00:15:11.820> they<00:15:12.120> will<00:15:12.300> be<00:15:12.420> cheaper 00:15:13.550 --> 00:15:13.560 align:start position:0% so that they will be cheaper 00:15:13.560 --> 00:15:16.009 align:start position:0% so that they will be cheaper and<00:15:14.459> they 00:15:16.009 --> 00:15:16.019 align:start position:0% and they 00:15:16.019 --> 00:15:19.009 align:start position:0% and they sending<00:15:16.740> them<00:15:16.800> on<00:15:17.459> chain<00:15:17.639> it<00:15:18.060> is<00:15:18.240> since<00:15:18.720> it<00:15:18.899> is 00:15:19.009 --> 00:15:19.019 align:start position:0% sending them on chain it is since it is 00:15:19.019 --> 00:15:20.810 align:start position:0% sending them on chain it is since it is contract<00:15:19.320> based<00:15:19.740> it<00:15:19.860> can<00:15:19.980> work<00:15:20.100> on<00:15:20.279> any<00:15:20.399> evm 00:15:20.810 --> 00:15:20.820 align:start position:0% contract based it can work on any evm 00:15:20.820 --> 00:15:28.310 align:start position:0% contract based it can work on any evm based<00:15:21.120> Network<00:15:21.420> today 00:15:28.310 --> 00:15:28.320 align:start position:0% 00:15:28.320 --> 00:15:30.829 align:start position:0% where<00:15:28.680> we<00:15:28.920> we<00:15:29.459> want<00:15:29.639> to<00:15:29.760> take<00:15:30.060> it<00:15:30.240> to<00:15:30.420> the<00:15:30.779> next 00:15:30.829 --> 00:15:30.839 align:start position:0% where we we want to take it to the next 00:15:30.839 --> 00:15:35.210 align:start position:0% where we we want to take it to the next level<00:15:31.019> right<00:15:31.860> now<00:15:32.040> when<00:15:32.820> you<00:15:32.940> create<00:15:33.560> a<00:15:34.560> an 00:15:35.210 --> 00:15:35.220 align:start position:0% level right now when you create a an 00:15:35.220 --> 00:15:37.370 align:start position:0% level right now when you create a an account<00:15:35.519> obstructed<00:15:36.120> wallet 00:15:37.370 --> 00:15:37.380 align:start position:0% account obstructed wallet 00:15:37.380 --> 00:15:39.410 align:start position:0% account obstructed wallet we<00:15:37.800> want<00:15:37.920> to<00:15:38.040> make<00:15:38.160> it<00:15:38.339> a<00:15:38.519> first-class<00:15:38.940> citizen 00:15:39.410 --> 00:15:39.420 align:start position:0% we want to make it a first-class citizen 00:15:39.420 --> 00:15:42.290 align:start position:0% we want to make it a first-class citizen on<00:15:39.720> the<00:15:39.839> network<00:15:39.959> First<00:15:40.380> Class<00:15:40.680> A<00:15:41.100> account<00:15:41.940> on 00:15:42.290 --> 00:15:42.300 align:start position:0% on the network First Class A account on 00:15:42.300 --> 00:15:43.189 align:start position:0% on the network First Class A account on the<00:15:42.420> network 00:15:43.189 --> 00:15:43.199 align:start position:0% the network 00:15:43.199 --> 00:15:45.530 align:start position:0% the network right<00:15:43.800> now<00:15:43.920> it<00:15:44.100> isn't<00:15:44.399> it<00:15:44.760> is<00:15:44.940> second<00:15:45.240> class 00:15:45.530 --> 00:15:45.540 align:start position:0% right now it isn't it is second class 00:15:45.540 --> 00:15:47.150 align:start position:0% right now it isn't it is second class because<00:15:46.019> there<00:15:46.380> are<00:15:46.500> some<00:15:46.740> differences 00:15:47.150 --> 00:15:47.160 align:start position:0% because there are some differences 00:15:47.160 --> 00:15:49.310 align:start position:0% because there are some differences between<00:15:47.600> UI<00:15:48.600> accounts<00:15:49.019> and<00:15:49.079> some 00:15:49.310 --> 00:15:49.320 align:start position:0% between UI accounts and some 00:15:49.320 --> 00:15:52.009 align:start position:0% between UI accounts and some applications<00:15:49.740> require<00:15:50.540> eoa<00:15:51.540> accounts<00:15:51.839> in<00:15:51.899> the 00:15:52.009 --> 00:15:52.019 align:start position:0% applications require eoa accounts in the 00:15:52.019 --> 00:15:52.970 align:start position:0% applications require eoa accounts in the way<00:15:52.139> they<00:15:52.260> work<00:15:52.380> in<00:15:52.560> the<00:15:52.680> way<00:15:52.800> they<00:15:52.920> require 00:15:52.970 --> 00:15:52.980 align:start position:0% way they work in the way they require 00:15:52.980 --> 00:15:55.670 align:start position:0% way they work in the way they require signature<00:15:53.699> think<00:15:54.360> of<00:15:54.600> permit<00:15:54.959> you<00:15:55.320> cannot<00:15:55.560> do 00:15:55.670 --> 00:15:55.680 align:start position:0% signature think of permit you cannot do 00:15:55.680 --> 00:15:58.670 align:start position:0% signature think of permit you cannot do permit<00:15:56.040> directly<00:15:56.699> with<00:15:56.940> a<00:15:57.120> Wallet<00:15:57.779> account<00:15:57.899> we 00:15:58.670 --> 00:15:58.680 align:start position:0% permit directly with a Wallet account we 00:15:58.680 --> 00:16:01.030 align:start position:0% permit directly with a Wallet account we do<00:15:58.740> want<00:15:58.980> to<00:15:59.579> make<00:15:59.639> them<00:15:59.820> first<00:16:00.060> class 00:16:01.030 --> 00:16:01.040 align:start position:0% do want to make them first class 00:16:01.040 --> 00:16:04.250 align:start position:0% do want to make them first class citizens<00:16:02.040> so<00:16:02.339> the<00:16:02.699> next<00:16:02.820> stage<00:16:03.120> after 00:16:04.250 --> 00:16:04.260 align:start position:0% citizens so the next stage after 00:16:04.260 --> 00:16:06.829 align:start position:0% citizens so the next stage after uh<00:16:04.860> what<00:16:05.160> we've<00:16:05.399> done<00:16:05.519> today<00:16:05.639> which<00:16:06.000> is 00:16:06.829 --> 00:16:06.839 align:start position:0% uh what we've done today which is 00:16:06.839 --> 00:16:09.889 align:start position:0% uh what we've done today which is having<00:16:07.500> a<00:16:08.100> contract-based<00:16:08.940> mechanism<00:16:09.360> to 00:16:09.889 --> 00:16:09.899 align:start position:0% having a contract-based mechanism to 00:16:09.899 --> 00:16:12.590 align:start position:0% having a contract-based mechanism to deploy<00:16:10.740> them<00:16:10.920> on<00:16:11.100> chain<00:16:11.279> we<00:16:11.940> want<00:16:12.060> to<00:16:12.180> add<00:16:12.420> them 00:16:12.590 --> 00:16:12.600 align:start position:0% deploy them on chain we want to add them 00:16:12.600 --> 00:16:15.050 align:start position:0% deploy them on chain we want to add them into<00:16:12.839> the<00:16:13.199> network<00:16:13.500> to<00:16:14.459> what<00:16:14.820> we<00:16:14.880> call 00:16:15.050 --> 00:16:15.060 align:start position:0% into the network to what we call 00:16:15.060 --> 00:16:18.170 align:start position:0% into the network to what we call enshrine<00:16:15.860> 437<00:16:16.860> into<00:16:17.100> the<00:16:17.339> network<00:16:17.459> so<00:16:17.880> that 00:16:18.170 --> 00:16:18.180 align:start position:0% enshrine 437 into the network so that 00:16:18.180 --> 00:16:20.870 align:start position:0% enshrine 437 into the network so that account<00:16:18.720> abstracted<00:16:19.320> accounts<00:16:19.680> will<00:16:19.800> be 00:16:20.870 --> 00:16:20.880 align:start position:0% account abstracted accounts will be 00:16:20.880 --> 00:16:22.490 align:start position:0% account abstracted accounts will be account<00:16:21.240> and<00:16:21.540> transaction<00:16:21.839> in<00:16:22.199> the<00:16:22.320> system 00:16:22.490 --> 00:16:22.500 align:start position:0% account and transaction in the system 00:16:22.500 --> 00:16:26.269 align:start position:0% account and transaction in the system just<00:16:23.100> like<00:16:23.279> normal<00:16:23.519> accounts<00:16:24.480> and<00:16:25.199> then 00:16:26.269 --> 00:16:26.279 align:start position:0% just like normal accounts and then 00:16:26.279 --> 00:16:29.449 align:start position:0% just like normal accounts and then to<00:16:26.639> make<00:16:26.760> it<00:16:26.940> possible<00:16:27.240> to<00:16:27.660> convert<00:16:28.380> any<00:16:28.860> eoa 00:16:29.449 --> 00:16:29.459 align:start position:0% to make it possible to convert any eoa 00:16:29.459 --> 00:16:32.090 align:start position:0% to make it possible to convert any eoa account<00:16:29.639> into<00:16:30.180> a<00:16:30.540> smarter<00:16:30.959> into<00:16:31.800> account 00:16:32.090 --> 00:16:32.100 align:start position:0% account into a smarter into account 00:16:32.100 --> 00:16:34.610 align:start position:0% account into a smarter into account obstructed<00:16:32.760> that<00:16:33.420> is<00:16:33.540> there's<00:16:33.839> going<00:16:34.139> to<00:16:34.260> be<00:16:34.380> a 00:16:34.610 --> 00:16:34.620 align:start position:0% obstructed that is there's going to be a 00:16:34.620 --> 00:16:38.030 align:start position:0% obstructed that is there's going to be a way<00:16:35.279> it<00:16:35.699> is<00:16:35.880> not<00:16:36.000> fully<00:16:36.360> hashed<00:16:36.959> yet<00:16:37.079> it<00:16:37.860> will 00:16:38.030 --> 00:16:38.040 align:start position:0% way it is not fully hashed yet it will 00:16:38.040 --> 00:16:39.829 align:start position:0% way it is not fully hashed yet it will take<00:16:38.220> some<00:16:38.399> time<00:16:38.579> until<00:16:38.820> we<00:16:39.120> finish<00:16:39.420> it<00:16:39.660> and 00:16:39.829 --> 00:16:39.839 align:start position:0% take some time until we finish it and 00:16:39.839 --> 00:16:41.210 align:start position:0% take some time until we finish it and until<00:16:40.019> it<00:16:40.259> be<00:16:40.440> approved<00:16:40.680> into<00:16:40.860> the<00:16:41.040> network 00:16:41.210 --> 00:16:41.220 align:start position:0% until it be approved into the network 00:16:41.220 --> 00:16:42.220 align:start position:0% until it be approved into the network but 00:16:42.220 --> 00:16:42.230 align:start position:0% but 00:16:42.230 --> 00:16:43.610 align:start position:0% but [Music] 00:16:43.610 --> 00:16:43.620 align:start position:0% [Music] 00:16:43.620 --> 00:16:45.769 align:start position:0% [Music] there's<00:16:44.040> going<00:16:44.279> to<00:16:44.399> be<00:16:44.519> a<00:16:44.639> way<00:16:44.759> that<00:16:45.180> you<00:16:45.600> have 00:16:45.769 --> 00:16:45.779 align:start position:0% there's going to be a way that you have 00:16:45.779 --> 00:16:47.810 align:start position:0% there's going to be a way that you have a<00:16:45.899> normal<00:16:46.079> account<00:16:46.320> and<00:16:47.220> you<00:16:47.339> want<00:16:47.459> to<00:16:47.579> have 00:16:47.810 --> 00:16:47.820 align:start position:0% a normal account and you want to have 00:16:47.820 --> 00:16:51.110 align:start position:0% a normal account and you want to have those<00:16:48.779> uh<00:16:49.199> extra<00:16:49.920> features 00:16:51.110 --> 00:16:51.120 align:start position:0% those uh extra features 00:16:51.120 --> 00:16:53.949 align:start position:0% those uh extra features so<00:16:52.079> you<00:16:52.259> will<00:16:52.380> be<00:16:52.500> able<00:16:52.740> to 00:16:53.949 --> 00:16:53.959 align:start position:0% so you will be able to 00:16:53.959 --> 00:16:57.110 align:start position:0% so you will be able to enable<00:16:54.959> this<00:16:55.560> account<00:16:55.860> there<00:16:56.699> are<00:16:56.880> several 00:16:57.110 --> 00:16:57.120 align:start position:0% enable this account there are several 00:16:57.120 --> 00:16:59.150 align:start position:0% enable this account there are several ways<00:16:57.420> how<00:16:57.600> to<00:16:57.720> do<00:16:57.899> it<00:16:58.019> one<00:16:58.620> of<00:16:58.680> them<00:16:58.800> is<00:16:58.980> that 00:16:59.150 --> 00:16:59.160 align:start position:0% ways how to do it one of them is that 00:16:59.160 --> 00:17:01.129 align:start position:0% ways how to do it one of them is that you<00:16:59.339> will<00:16:59.579> actively<00:17:00.180> have<00:17:00.360> to 00:17:01.129 --> 00:17:01.139 align:start position:0% you will actively have to 00:17:01.139 --> 00:17:04.370 align:start position:0% you will actively have to convert<00:17:01.980> your<00:17:02.220> account<00:17:02.759> your<00:17:03.120> account<00:17:03.480> into<00:17:04.020> a 00:17:04.370 --> 00:17:04.380 align:start position:0% convert your account your account into a 00:17:04.380 --> 00:17:07.309 align:start position:0% convert your account your account into a smart<00:17:04.740> account<00:17:05.059> abstract<00:17:06.059> account<00:17:06.360> the<00:17:07.199> other 00:17:07.309 --> 00:17:07.319 align:start position:0% smart account abstract account the other 00:17:07.319 --> 00:17:09.530 align:start position:0% smart account abstract account the other way<00:17:07.559> is<00:17:07.679> that<00:17:08.040> they're<00:17:08.400> going<00:17:08.520> to<00:17:08.699> be<00:17:08.819> some 00:17:09.530 --> 00:17:09.540 align:start position:0% way is that they're going to be some 00:17:09.540 --> 00:17:12.650 align:start position:0% way is that they're going to be some point<00:17:10.020> of<00:17:10.199> in<00:17:10.439> time<00:17:10.679> where<00:17:11.520> all<00:17:11.819> eoa<00:17:12.240> accounts 00:17:12.650 --> 00:17:12.660 align:start position:0% point of in time where all eoa accounts 00:17:12.660 --> 00:17:13.750 align:start position:0% point of in time where all eoa accounts will<00:17:12.839> become 00:17:13.750 --> 00:17:13.760 align:start position:0% will become 00:17:13.760 --> 00:17:16.250 align:start position:0% will become abstracted<00:17:14.760> but<00:17:15.480> with<00:17:15.780> a<00:17:15.959> default 00:17:16.250 --> 00:17:16.260 align:start position:0% abstracted but with a default 00:17:16.260 --> 00:17:18.770 align:start position:0% abstracted but with a default implementation<00:17:16.799> that<00:17:17.339> emulate<00:17:18.299> completely 00:17:18.770 --> 00:17:18.780 align:start position:0% implementation that emulate completely 00:17:18.780 --> 00:17:21.530 align:start position:0% implementation that emulate completely the<00:17:19.559> normal<00:17:19.679> eoa<00:17:20.220> account<00:17:20.339> and<00:17:21.240> from<00:17:21.360> that 00:17:21.530 --> 00:17:21.540 align:start position:0% the normal eoa account and from that 00:17:21.540 --> 00:17:23.829 align:start position:0% the normal eoa account and from that point<00:17:21.660> you<00:17:21.900> can<00:17:22.020> yes<00:17:22.319> you<00:17:22.620> can<00:17:22.740> keep<00:17:23.220> the<00:17:23.459> same 00:17:23.829 --> 00:17:23.839 align:start position:0% point you can yes you can keep the same 00:17:23.839 --> 00:17:27.110 align:start position:0% point you can yes you can keep the same implementation<00:17:24.839> or<00:17:25.319> you<00:17:25.620> can<00:17:25.799> switch<00:17:26.760> to<00:17:26.939> a 00:17:27.110 --> 00:17:27.120 align:start position:0% implementation or you can switch to a 00:17:27.120 --> 00:17:28.730 align:start position:0% implementation or you can switch to a different<00:17:27.179> implementation<00:17:27.720> if<00:17:28.020> you<00:17:28.140> want<00:17:28.380> a 00:17:28.730 --> 00:17:28.740 align:start position:0% different implementation if you want a 00:17:28.740 --> 00:17:30.650 align:start position:0% different implementation if you want a extra<00:17:29.580> features 00:17:30.650 --> 00:17:30.660 align:start position:0% extra features 00:17:30.660 --> 00:17:33.289 align:start position:0% extra features like<00:17:31.320> all<00:17:31.980> of<00:17:32.100> those<00:17:32.220> that<00:17:32.520> we<00:17:32.940> described 00:17:33.289 --> 00:17:33.299 align:start position:0% like all of those that we described 00:17:33.299 --> 00:17:34.789 align:start position:0% like all of those that we described earlier 00:17:34.789 --> 00:17:34.799 align:start position:0% earlier 00:17:34.799 --> 00:17:37.310 align:start position:0% earlier so<00:17:35.340> one<00:17:35.580> one<00:17:36.179> um 00:17:37.310 --> 00:17:37.320 align:start position:0% so one one um 00:17:37.320 --> 00:17:39.650 align:start position:0% so one one um um<00:17:37.500> one<00:17:37.679> thing<00:17:38.100> to<00:17:38.520> maybe<00:17:38.880> refine<00:17:39.299> a<00:17:39.539> little 00:17:39.650 --> 00:17:39.660 align:start position:0% um one thing to maybe refine a little 00:17:39.660 --> 00:17:41.510 align:start position:0% um one thing to maybe refine a little bit<00:17:39.780> is 00:17:41.510 --> 00:17:41.520 align:start position:0% bit is 00:17:41.520 --> 00:17:44.570 align:start position:0% bit is um we<00:17:42.179> believe<00:17:42.360> eoas<00:17:43.200> will<00:17:44.039> need<00:17:44.220> to<00:17:44.280> go<00:17:44.400> away 00:17:44.570 --> 00:17:44.580 align:start position:0% um we believe eoas will need to go away 00:17:44.580 --> 00:17:46.190 align:start position:0% um we believe eoas will need to go away at<00:17:44.880> some<00:17:45.000> point 00:17:46.190 --> 00:17:46.200 align:start position:0% at some point 00:17:46.200 --> 00:17:48.650 align:start position:0% at some point um<00:17:46.260> so<00:17:46.919> right<00:17:47.580> now<00:17:47.700> they<00:17:47.880> are<00:17:48.059> enshrined<00:17:48.539> into 00:17:48.650 --> 00:17:48.660 align:start position:0% um so right now they are enshrined into 00:17:48.660 --> 00:17:50.630 align:start position:0% um so right now they are enshrined into the<00:17:48.840> protocol 00:17:50.630 --> 00:17:50.640 align:start position:0% the protocol 00:17:50.640 --> 00:17:51.650 align:start position:0% the protocol um<00:17:50.700> and<00:17:50.880> we've<00:17:51.000> discussed<00:17:51.299> some<00:17:51.419> of<00:17:51.539> the 00:17:51.650 --> 00:17:51.660 align:start position:0% um and we've discussed some of the 00:17:51.660 --> 00:17:53.210 align:start position:0% um and we've discussed some of the limitations<00:17:52.080> around<00:17:52.320> that<00:17:52.559> so<00:17:52.799> at<00:17:52.980> some<00:17:53.100> point 00:17:53.210 --> 00:17:53.220 align:start position:0% limitations around that so at some point 00:17:53.220 --> 00:17:55.549 align:start position:0% limitations around that so at some point eoas<00:17:53.880> even<00:17:54.660> if<00:17:54.900> there's<00:17:55.020> backwards 00:17:55.549 --> 00:17:55.559 align:start position:0% eoas even if there's backwards 00:17:55.559 --> 00:17:58.490 align:start position:0% eoas even if there's backwards compatibility<00:17:56.039> they<00:17:57.000> will<00:17:57.240> they<00:17:57.900> will<00:17:58.080> not<00:17:58.260> be 00:17:58.490 --> 00:17:58.500 align:start position:0% compatibility they will they will not be 00:17:58.500 --> 00:18:00.950 align:start position:0% compatibility they will they will not be a<00:17:58.799> part<00:17:58.919> of<00:17:59.039> the<00:17:59.100> protocol<00:17:59.340> anymore 00:18:00.950 --> 00:18:00.960 align:start position:0% a part of the protocol anymore 00:18:00.960 --> 00:18:02.930 align:start position:0% a part of the protocol anymore um<00:18:01.080> we<00:18:01.440> don't<00:18:01.559> necessarily<00:18:02.100> think<00:18:02.460> that<00:18:02.760> it 00:18:02.930 --> 00:18:02.940 align:start position:0% um we don't necessarily think that it 00:18:02.940 --> 00:18:05.029 align:start position:0% um we don't necessarily think that it makes<00:18:03.120> sense<00:18:03.299> to<00:18:03.720> enshrine<00:18:04.260> any<00:18:04.620> specific 00:18:05.029 --> 00:18:05.039 align:start position:0% makes sense to enshrine any specific 00:18:05.039 --> 00:18:07.549 align:start position:0% makes sense to enshrine any specific alternative<00:18:05.700> like<00:18:06.539> you<00:18:06.720> know<00:18:06.840> this<00:18:06.900> is<00:18:07.020> an<00:18:07.140> ERC 00:18:07.549 --> 00:18:07.559 align:start position:0% alternative like you know this is an ERC 00:18:07.559 --> 00:18:09.049 align:start position:0% alternative like you know this is an ERC maybe<00:18:07.799> there<00:18:08.039> will<00:18:08.220> be<00:18:08.340> like<00:18:08.760> you<00:18:08.940> know 00:18:09.049 --> 00:18:09.059 align:start position:0% maybe there will be like you know 00:18:09.059 --> 00:18:11.090 align:start position:0% maybe there will be like you know improvements<00:18:09.780> in<00:18:09.900> the<00:18:10.020> future<00:18:10.140> because<00:18:10.740> that 00:18:11.090 --> 00:18:11.100 align:start position:0% improvements in the future because that 00:18:11.100 --> 00:18:12.710 align:start position:0% improvements in the future because that could<00:18:11.220> be<00:18:11.340> dangerous<00:18:11.700> but 00:18:12.710 --> 00:18:12.720 align:start position:0% could be dangerous but 00:18:12.720 --> 00:18:15.350 align:start position:0% could be dangerous but what's<00:18:13.200> clear<00:18:13.440> is<00:18:13.919> abstract<00:18:14.700> accounts<00:18:15.179> are 00:18:15.350 --> 00:18:15.360 align:start position:0% what's clear is abstract accounts are 00:18:15.360 --> 00:18:17.150 align:start position:0% what's clear is abstract accounts are going<00:18:15.539> to<00:18:15.660> be<00:18:15.840> enshrined<00:18:16.500> into<00:18:16.620> the<00:18:16.860> protocol 00:18:17.150 --> 00:18:17.160 align:start position:0% going to be enshrined into the protocol 00:18:17.160 --> 00:18:19.070 align:start position:0% going to be enshrined into the protocol there<00:18:17.580> are<00:18:17.760> going<00:18:17.880> to<00:18:18.000> be<00:18:18.179> there<00:18:18.780> are<00:18:18.900> going<00:18:19.020> to 00:18:19.070 --> 00:18:19.080 align:start position:0% there are going to be there are going to 00:18:19.080 --> 00:18:20.810 align:start position:0% there are going to be there are going to be<00:18:19.200> accounts<00:18:19.559> that<00:18:19.679> can<00:18:19.860> do<00:18:19.980> all<00:18:20.520> the<00:18:20.640> things 00:18:20.810 --> 00:18:20.820 align:start position:0% be accounts that can do all the things 00:18:20.820 --> 00:18:23.810 align:start position:0% be accounts that can do all the things that<00:18:20.940> we<00:18:21.059> discussed<00:18:21.480> out<00:18:22.140> of<00:18:22.260> the<00:18:22.380> box<00:18:22.640> for<00:18:23.640> new 00:18:23.810 --> 00:18:23.820 align:start position:0% that we discussed out of the box for new 00:18:23.820 --> 00:18:26.270 align:start position:0% that we discussed out of the box for new deployments<00:18:24.360> and<00:18:24.660> for<00:18:24.900> older<00:18:25.260> deployments<00:18:25.860> so 00:18:26.270 --> 00:18:26.280 align:start position:0% deployments and for older deployments so 00:18:26.280 --> 00:18:27.830 align:start position:0% deployments and for older deployments so otherwise<00:18:26.880> you<00:18:27.000> would<00:18:27.120> need<00:18:27.240> to<00:18:27.360> transfer<00:18:27.660> all 00:18:27.830 --> 00:18:27.840 align:start position:0% otherwise you would need to transfer all 00:18:27.840 --> 00:18:29.330 align:start position:0% otherwise you would need to transfer all your<00:18:28.020> assets<00:18:28.260> from<00:18:28.559> money<00:18:28.740> away<00:18:28.980> to<00:18:29.220> another 00:18:29.330 --> 00:18:29.340 align:start position:0% your assets from money away to another 00:18:29.340 --> 00:18:31.250 align:start position:0% your assets from money away to another and<00:18:29.640> that's<00:18:29.760> very<00:18:30.000> expensive<00:18:30.480> and<00:18:30.720> cumbersome 00:18:31.250 --> 00:18:31.260 align:start position:0% and that's very expensive and cumbersome 00:18:31.260 --> 00:18:35.150 align:start position:0% and that's very expensive and cumbersome and<00:18:31.559> you<00:18:32.340> know<00:18:32.400> potentially<00:18:32.820> risky<00:18:33.740> so<00:18:34.740> that's 00:18:35.150 --> 00:18:35.160 align:start position:0% and you know potentially risky so that's 00:18:35.160 --> 00:18:36.409 align:start position:0% and you know potentially risky so that's where<00:18:35.340> we're<00:18:35.520> headed<00:18:35.760> and<00:18:35.880> in<00:18:36.059> terms<00:18:36.179> of<00:18:36.240> the 00:18:36.409 --> 00:18:36.419 align:start position:0% where we're headed and in terms of the 00:18:36.419 --> 00:18:37.970 align:start position:0% where we're headed and in terms of the implementation<00:18:36.900> yeah<00:18:37.200> like<00:18:37.440> they<00:18:37.620> all<00:18:37.799> said 00:18:37.970 --> 00:18:37.980 align:start position:0% implementation yeah like they all said 00:18:37.980 --> 00:18:41.029 align:start position:0% implementation yeah like they all said there<00:18:38.220> are<00:18:38.340> various<00:18:38.880> ways<00:18:39.179> of<00:18:39.240> going<00:18:39.419> about<00:18:39.600> it 00:18:41.029 --> 00:18:41.039 align:start position:0% there are various ways of going about it 00:18:41.039 --> 00:18:45.010 align:start position:0% there are various ways of going about it um to<00:18:41.280> be<00:18:41.400> determined 00:18:45.010 --> 00:18:45.020 align:start position:0% 00:18:45.020 --> 00:18:49.150 align:start position:0% okay<00:18:46.400> what<00:18:47.400> can<00:18:47.520> we<00:18:47.700> do 00:18:49.150 --> 00:18:49.160 align:start position:0% okay what can we do 00:18:49.160 --> 00:18:52.930 align:start position:0% okay what can we do uh<00:18:50.160> you<00:18:50.820> can<00:18:50.940> start<00:18:51.059> experimenting<00:18:51.720> with<00:18:52.140> a 00:18:52.930 --> 00:18:52.940 align:start position:0% uh you can start experimenting with a 00:18:52.940 --> 00:18:55.669 align:start position:0% uh you can start experimenting with a esc-4337a<00:18:53.940> now<00:18:54.600> I<00:18:55.140> see<00:18:55.320> people<00:18:55.500> who 00:18:55.669 --> 00:18:55.679 align:start position:0% esc-4337a now I see people who 00:18:55.679 --> 00:18:57.950 align:start position:0% esc-4337a now I see people who experimented<00:18:56.160> here<00:18:56.340> in<00:18:56.460> the<00:18:56.580> hackathon 00:18:57.950 --> 00:18:57.960 align:start position:0% experimented here in the hackathon 00:18:57.960 --> 00:18:59.870 align:start position:0% experimented here in the hackathon and<00:18:58.559> yes 00:18:59.870 --> 00:18:59.880 align:start position:0% and yes 00:18:59.880 --> 00:19:03.470 align:start position:0% and yes over<00:19:00.120> there<00:19:00.480> also<00:19:00.900> a 00:19:03.470 --> 00:19:03.480 align:start position:0% over there also a 00:19:03.480 --> 00:19:05.870 align:start position:0% over there also a you<00:19:03.960> can<00:19:04.080> add<00:19:04.919> useful<00:19:05.220> features<00:19:05.580> to<00:19:05.700> your 00:19:05.870 --> 00:19:05.880 align:start position:0% you can add useful features to your 00:19:05.880 --> 00:19:08.630 align:start position:0% you can add useful features to your accounts<00:19:06.360> innovate<00:19:07.080> do<00:19:07.380> whatever<00:19:07.559> you<00:19:07.860> like 00:19:08.630 --> 00:19:08.640 align:start position:0% accounts innovate do whatever you like 00:19:08.640 --> 00:19:10.909 align:start position:0% accounts innovate do whatever you like and<00:19:09.179> if<00:19:09.600> you<00:19:09.780> find<00:19:10.020> something<00:19:10.260> that<00:19:10.500> you<00:19:10.679> think 00:19:10.909 --> 00:19:10.919 align:start position:0% and if you find something that you think 00:19:10.919 --> 00:19:14.029 align:start position:0% and if you find something that you think is<00:19:11.400> good<00:19:12.299> for<00:19:12.539> the<00:19:12.900> public<00:19:13.020> you<00:19:13.559> can<00:19:13.620> apply<00:19:13.860> for 00:19:14.029 --> 00:19:14.039 align:start position:0% is good for the public you can apply for 00:19:14.039 --> 00:19:15.590 align:start position:0% is good for the public you can apply for an<00:19:14.160> EF<00:19:14.460> Grant 00:19:15.590 --> 00:19:15.600 align:start position:0% an EF Grant 00:19:15.600 --> 00:19:20.450 align:start position:0% an EF Grant and<00:19:16.260> they 00:19:20.450 --> 00:19:20.460 align:start position:0% 00:19:20.460 --> 00:19:23.690 align:start position:0% what<00:19:21.179> they<00:19:21.480> and<00:19:21.960> anything<00:19:22.140> building<00:19:22.500> adapt 00:19:23.690 --> 00:19:23.700 align:start position:0% what they and anything building adapt 00:19:23.700 --> 00:19:26.510 align:start position:0% what they and anything building adapt as<00:19:24.539> we<00:19:24.660> said<00:19:24.780> accounts<00:19:25.500> wallet<00:19:26.100> accounts<00:19:26.400> are 00:19:26.510 --> 00:19:26.520 align:start position:0% as we said accounts wallet accounts are 00:19:26.520 --> 00:19:30.110 align:start position:0% as we said accounts wallet accounts are a<00:19:26.640> bit<00:19:26.700> different<00:19:26.820> from<00:19:27.380> UI<00:19:28.380> accounts<00:19:28.799> so<00:19:29.520> even 00:19:30.110 --> 00:19:30.120 align:start position:0% a bit different from UI accounts so even 00:19:30.120 --> 00:19:32.390 align:start position:0% a bit different from UI accounts so even today<00:19:30.360> when<00:19:30.660> you're<00:19:30.780> working<00:19:31.020> with<00:19:31.500> apps<00:19:31.860> this 00:19:32.390 --> 00:19:32.400 align:start position:0% today when you're working with apps this 00:19:32.400 --> 00:19:33.890 align:start position:0% today when you're working with apps this is<00:19:32.520> not<00:19:32.880> strictly<00:19:33.299> related<00:19:33.600> to<00:19:33.780> account 00:19:33.890 --> 00:19:33.900 align:start position:0% is not strictly related to account 00:19:33.900 --> 00:19:36.110 align:start position:0% is not strictly related to account abstraction<00:19:34.440> but<00:19:34.679> to<00:19:34.860> Wallet<00:19:35.220> account<00:19:35.340> in 00:19:36.110 --> 00:19:36.120 align:start position:0% abstraction but to Wallet account in 00:19:36.120 --> 00:19:38.450 align:start position:0% abstraction but to Wallet account in general<00:19:36.380> make<00:19:37.380> sure<00:19:37.559> that<00:19:37.860> you<00:19:38.039> are<00:19:38.160> not 00:19:38.450 --> 00:19:38.460 align:start position:0% general make sure that you are not 00:19:38.460 --> 00:19:41.750 align:start position:0% general make sure that you are not forcing<00:19:39.240> the<00:19:39.360> user<00:19:39.660> to<00:19:39.780> use<00:19:40.020> a<00:19:40.260> accounts<00:19:41.100> like 00:19:41.750 --> 00:19:41.760 align:start position:0% forcing the user to use a accounts like 00:19:41.760 --> 00:19:43.909 align:start position:0% forcing the user to use a accounts like if<00:19:41.940> you're<00:19:42.059> checking<00:19:42.419> signatures<00:19:42.900> there<00:19:43.799> is 00:19:43.909 --> 00:19:43.919 align:start position:0% if you're checking signatures there is 00:19:43.919 --> 00:19:47.330 align:start position:0% if you're checking signatures there is an<00:19:44.039> extension<00:19:44.460> the<00:19:44.880> 1271<00:19:45.840> that<00:19:46.320> allows<00:19:47.100> a 00:19:47.330 --> 00:19:47.340 align:start position:0% an extension the 1271 that allows a 00:19:47.340 --> 00:19:49.070 align:start position:0% an extension the 1271 that allows a Wallet<00:19:47.640> account<00:19:47.760> to<00:19:47.940> check<00:19:48.059> a<00:19:48.240> signature 00:19:49.070 --> 00:19:49.080 align:start position:0% Wallet account to check a signature 00:19:49.080 --> 00:19:50.270 align:start position:0% Wallet account to check a signature because 00:19:50.270 --> 00:19:50.280 align:start position:0% because 00:19:50.280 --> 00:19:52.730 align:start position:0% because it<00:19:50.640> doesn't<00:19:51.120> have<00:19:51.299> a<00:19:51.419> signature<00:19:51.840> by<00:19:51.960> itself 00:19:52.730 --> 00:19:52.740 align:start position:0% it doesn't have a signature by itself 00:19:52.740 --> 00:19:55.490 align:start position:0% it doesn't have a signature by itself a<00:19:53.760> Wallet<00:19:54.539> account<00:19:54.720> just<00:19:54.900> to<00:19:55.020> be<00:19:55.080> clear<00:19:55.200> we're 00:19:55.490 --> 00:19:55.500 align:start position:0% a Wallet account just to be clear we're 00:19:55.500 --> 00:19:57.669 align:start position:0% a Wallet account just to be clear we're talking<00:19:55.620> about<00:19:55.799> contract<00:19:56.160> wallet<00:19:56.580> yes<00:19:56.820> yeah 00:19:57.669 --> 00:19:57.679 align:start position:0% talking about contract wallet yes yeah 00:19:57.679 --> 00:19:59.810 align:start position:0% talking about contract wallet yes yeah if<00:19:58.679> you<00:19:58.740> have<00:19:58.919> a<00:19:59.039> token<00:19:59.220> you<00:19:59.460> want<00:19:59.520> to<00:19:59.640> have 00:19:59.810 --> 00:19:59.820 align:start position:0% if you have a token you want to have 00:19:59.820 --> 00:20:02.570 align:start position:0% if you have a token you want to have permits<00:20:00.720> be<00:20:01.080> aware<00:20:01.380> that<00:20:01.559> permit<00:20:01.980> as<00:20:02.280> it<00:20:02.460> is 00:20:02.570 --> 00:20:02.580 align:start position:0% permits be aware that permit as it is 00:20:02.580 --> 00:20:05.870 align:start position:0% permits be aware that permit as it is today<00:20:02.760> in<00:20:03.120> usdt<00:20:03.600> and<00:20:03.780> die<00:20:03.960> does<00:20:04.440> not<00:20:04.620> support<00:20:04.980> a 00:20:05.870 --> 00:20:05.880 align:start position:0% today in usdt and die does not support a 00:20:05.880 --> 00:20:07.549 align:start position:0% today in usdt and die does not support a Wallet<00:20:06.299> account<00:20:06.480> you<00:20:06.840> cannot<00:20:07.080> use<00:20:07.200> it<00:20:07.320> from<00:20:07.500> a 00:20:07.549 --> 00:20:07.559 align:start position:0% Wallet account you cannot use it from a 00:20:07.559 --> 00:20:09.169 align:start position:0% Wallet account you cannot use it from a Wallet<00:20:07.919> account 00:20:09.169 --> 00:20:09.179 align:start position:0% Wallet account 00:20:09.179 --> 00:20:11.450 align:start position:0% Wallet account but<00:20:09.360> again<00:20:09.780> because<00:20:10.080> it<00:20:10.320> uses<00:20:10.559> the<00:20:10.679> signature 00:20:11.450 --> 00:20:11.460 align:start position:0% but again because it uses the signature 00:20:11.460 --> 00:20:14.870 align:start position:0% but again because it uses the signature there<00:20:11.940> are<00:20:12.059> some<00:20:12.240> other<00:20:12.480> tweaks<00:20:13.400> like<00:20:14.400> TX 00:20:14.870 --> 00:20:14.880 align:start position:0% there are some other tweaks like TX 00:20:14.880 --> 00:20:16.669 align:start position:0% there are some other tweaks like TX origin<00:20:15.240> and<00:20:15.419> stuff 00:20:16.669 --> 00:20:16.679 align:start position:0% origin and stuff 00:20:16.679 --> 00:20:19.250 align:start position:0% origin and stuff again<00:20:17.220> in<00:20:17.460> general<00:20:17.580> try<00:20:18.179> to<00:20:18.360> be<00:20:18.780> supportive 00:20:19.250 --> 00:20:19.260 align:start position:0% again in general try to be supportive 00:20:19.260 --> 00:20:21.049 align:start position:0% again in general try to be supportive for<00:20:19.500> wallet<00:20:19.980> accounts<00:20:20.340> because<00:20:20.520> these<00:20:20.940> are 00:20:21.049 --> 00:20:21.059 align:start position:0% for wallet accounts because these are 00:20:21.059 --> 00:20:23.029 align:start position:0% for wallet accounts because these are the<00:20:21.179> future<00:20:21.360> not<00:20:22.200> only<00:20:22.320> the<00:20:22.500> glossy<00:20:22.919> safe 00:20:23.029 --> 00:20:23.039 align:start position:0% the future not only the glossy safe 00:20:23.039 --> 00:20:25.789 align:start position:0% the future not only the glossy safe today<00:20:23.220> but<00:20:23.520> also<00:20:24.360> account<00:20:24.900> obstructed<00:20:25.500> in<00:20:25.679> the 00:20:25.789 --> 00:20:25.799 align:start position:0% today but also account obstructed in the 00:20:25.799 --> 00:20:27.110 align:start position:0% today but also account obstructed in the future 00:20:27.110 --> 00:20:27.120 align:start position:0% future 00:20:27.120 --> 00:20:30.529 align:start position:0% future and<00:20:27.960> also<00:20:28.320> if<00:20:28.500> you're<00:20:28.620> using<00:20:29.460> gas<00:20:30.000> sponsorship 00:20:30.529 --> 00:20:30.539 align:start position:0% and also if you're using gas sponsorship 00:20:30.539 --> 00:20:32.450 align:start position:0% and also if you're using gas sponsorship models<00:20:30.960> should<00:20:31.320> also<00:20:31.620> think<00:20:31.740> about<00:20:31.919> it<00:20:32.100> how<00:20:32.400> to 00:20:32.450 --> 00:20:32.460 align:start position:0% models should also think about it how to 00:20:32.460 --> 00:20:34.789 align:start position:0% models should also think about it how to interact<00:20:32.940> this<00:20:33.480> probably<00:20:34.020> will<00:20:34.380> need<00:20:34.559> an 00:20:34.789 --> 00:20:34.799 align:start position:0% interact this probably will need an 00:20:34.799 --> 00:20:36.710 align:start position:0% interact this probably will need an interaction<00:20:35.039> between<00:20:35.220> your<00:20:35.520> application<00:20:35.940> and 00:20:36.710 --> 00:20:36.720 align:start position:0% interaction between your application and 00:20:36.720 --> 00:20:39.169 align:start position:0% interaction between your application and the<00:20:36.900> wallet<00:20:37.200> in<00:20:37.980> order<00:20:38.160> to<00:20:38.460> provide<00:20:38.760> the<00:20:38.880> ux 00:20:39.169 --> 00:20:39.179 align:start position:0% the wallet in order to provide the ux 00:20:39.179 --> 00:20:47.810 align:start position:0% the wallet in order to provide the ux how<00:20:39.360> to<00:20:39.480> provide<00:20:39.720> is<00:20:39.960> a<00:20:40.140> to<00:20:40.500> your<00:20:40.620> users 00:20:47.810 --> 00:20:47.820 align:start position:0% 00:20:47.820 --> 00:20:49.789 align:start position:0% and<00:20:48.179> and<00:20:48.240> the<00:20:48.539> last<00:20:48.660> item<00:20:48.960> would<00:20:49.200> be<00:20:49.320> regarding 00:20:49.789 --> 00:20:49.799 align:start position:0% and and the last item would be regarding 00:20:49.799 --> 00:20:52.310 align:start position:0% and and the last item would be regarding uh<00:20:50.160> wallets<00:20:50.520> if<00:20:50.820> you're<00:20:50.940> developing<00:20:51.480> dapps 00:20:52.310 --> 00:20:52.320 align:start position:0% uh wallets if you're developing dapps 00:20:52.320 --> 00:20:54.590 align:start position:0% uh wallets if you're developing dapps then<00:20:53.039> maybe 00:20:54.590 --> 00:20:54.600 align:start position:0% then maybe 00:20:54.600 --> 00:20:56.630 align:start position:0% then maybe um<00:20:54.660> there's<00:20:55.260> some<00:20:55.440> space<00:20:55.679> if<00:20:56.039> you<00:20:56.160> you<00:20:56.340> find 00:20:56.630 --> 00:20:56.640 align:start position:0% um there's some space if you you find 00:20:56.640 --> 00:20:59.570 align:start position:0% um there's some space if you you find that<00:20:57.000> well<00:20:57.600> it's<00:20:57.840> not<00:20:58.080> supportive<00:20:58.679> enough<00:20:58.860> of 00:20:59.570 --> 00:20:59.580 align:start position:0% that well it's not supportive enough of 00:20:59.580 --> 00:21:03.110 align:start position:0% that well it's not supportive enough of a<00:21:00.120> contract<00:21:01.080> wallets<00:21:01.860> then<00:21:02.700> you<00:21:02.880> can<00:21:03.000> voice 00:21:03.110 --> 00:21:03.120 align:start position:0% a contract wallets then you can voice 00:21:03.120 --> 00:21:06.650 align:start position:0% a contract wallets then you can voice your<00:21:03.419> concerns<00:21:03.960> and<00:21:04.559> and<00:21:05.160> uh<00:21:05.640> try<00:21:06.120> to<00:21:06.360> lobby 00:21:06.650 --> 00:21:06.660 align:start position:0% your concerns and and uh try to lobby 00:21:06.660 --> 00:21:08.990 align:start position:0% your concerns and and uh try to lobby for<00:21:06.900> that<00:21:07.080> as<00:21:07.559> a<00:21:07.799> as<00:21:07.919> adapt<00:21:08.280> developer<00:21:08.760> that 00:21:08.990 --> 00:21:09.000 align:start position:0% for that as a as adapt developer that 00:21:09.000 --> 00:21:11.029 align:start position:0% for that as a as adapt developer that that<00:21:09.179> really<00:21:09.419> helps 00:21:11.029 --> 00:21:11.039 align:start position:0% that really helps 00:21:11.039 --> 00:21:13.370 align:start position:0% that really helps um<00:21:11.520> um<00:21:11.640> so<00:21:12.059> you<00:21:12.539> know 00:21:13.370 --> 00:21:13.380 align:start position:0% um um so you know 00:21:13.380 --> 00:21:16.190 align:start position:0% um um so you know getting<00:21:13.860> everyone<00:21:14.100> on<00:21:14.460> board<00:21:14.640> is<00:21:14.940> is<00:21:15.299> a<00:21:15.600> is<00:21:15.960> a 00:21:16.190 --> 00:21:16.200 align:start position:0% getting everyone on board is is a is a 00:21:16.200 --> 00:21:17.810 align:start position:0% getting everyone on board is is a is a process<00:21:16.380> that 00:21:17.810 --> 00:21:17.820 align:start position:0% process that 00:21:17.820 --> 00:21:21.350 align:start position:0% process that um we<00:21:18.000> could<00:21:18.179> use<00:21:18.299> your<00:21:18.419> help<00:21:18.600> on 00:21:21.350 --> 00:21:21.360 align:start position:0% 00:21:21.360 --> 00:21:23.990 align:start position:0% okay 00:21:23.990 --> 00:21:24.000 align:start position:0% 00:21:24.000 --> 00:21:26.450 align:start position:0% okay<00:21:24.360> it<00:21:24.600> is<00:21:24.720> before<00:21:24.900> the<00:21:25.200> last<00:21:25.380> the<00:21:25.980> QR<00:21:26.280> code 00:21:26.450 --> 00:21:26.460 align:start position:0% okay it is before the last the QR code 00:21:26.460 --> 00:21:28.430 align:start position:0% okay it is before the last the QR code is<00:21:26.580> missing<00:21:26.820> here 00:21:28.430 --> 00:21:28.440 align:start position:0% is missing here 00:21:28.440 --> 00:21:30.230 align:start position:0% is missing here so<00:21:28.799> if<00:21:28.919> you<00:21:29.039> want<00:21:29.159> the<00:21:29.280> link<00:21:29.400> to<00:21:29.580> all<00:21:29.760> these<00:21:30.000> I 00:21:30.230 --> 00:21:30.240 align:start position:0% so if you want the link to all these I 00:21:30.240 --> 00:21:32.210 align:start position:0% so if you want the link to all these I can<00:21:30.360> give<00:21:30.539> you<00:21:30.600> it<00:21:30.780> but<00:21:31.020> it<00:21:31.320> doesn't<00:21:31.799> appear<00:21:32.100> on 00:21:32.210 --> 00:21:32.220 align:start position:0% can give you it but it doesn't appear on 00:21:32.220 --> 00:21:35.090 align:start position:0% can give you it but it doesn't appear on this<00:21:32.340> version<00:21:32.460> of<00:21:32.700> the<00:21:32.940> presentation 00:21:35.090 --> 00:21:35.100 align:start position:0% this version of the presentation 00:21:35.100 --> 00:21:37.850 align:start position:0% this version of the presentation any<00:21:35.820> question 00:21:37.850 --> 00:21:37.860 align:start position:0% any question 00:21:37.860 --> 00:21:46.549 align:start position:0% any question yes 00:21:46.549 --> 00:21:46.559 align:start position:0% 00:21:46.559 --> 00:21:49.130 align:start position:0% so<00:21:47.100> I<00:21:47.400> have<00:21:47.520> like<00:21:47.760> two<00:21:48.059> questions<00:21:48.299> like<00:21:48.780> one 00:21:49.130 --> 00:21:49.140 align:start position:0% so I have like two questions like one 00:21:49.140 --> 00:21:51.950 align:start position:0% so I have like two questions like one are<00:21:49.440> related<00:21:49.799> to<00:21:50.100> how<00:21:50.700> uh<00:21:51.120> currently<00:21:51.539> like 00:21:51.950 --> 00:21:51.960 align:start position:0% are related to how uh currently like 00:21:51.960 --> 00:21:54.529 align:start position:0% are related to how uh currently like account<00:21:52.320> abstraction<00:21:53.280> exists<00:21:54.000> as<00:21:54.179> of<00:21:54.360> today 00:21:54.529 --> 00:21:54.539 align:start position:0% account abstraction exists as of today 00:21:54.539 --> 00:21:57.110 align:start position:0% account abstraction exists as of today as<00:21:54.900> an<00:21:55.080> implementation<00:21:55.679> can<00:21:56.460> you<00:21:56.640> provide<00:21:56.880> an 00:21:57.110 --> 00:21:57.120 align:start position:0% as an implementation can you provide an 00:21:57.120 --> 00:21:59.450 align:start position:0% as an implementation can you provide an example<00:21:57.480> like<00:21:57.900> how<00:21:58.740> like<00:21:58.919> it<00:21:59.159> can<00:21:59.340> be 00:21:59.450 --> 00:21:59.460 align:start position:0% example like how like it can be 00:21:59.460 --> 00:22:02.690 align:start position:0% example like how like it can be potentially<00:22:00.000> used<00:22:00.299> in<00:22:00.780> a<00:22:00.960> way<00:22:01.080> as<00:22:01.740> it<00:22:01.980> is<00:22:02.100> in 00:22:02.690 --> 00:22:02.700 align:start position:0% potentially used in a way as it is in 00:22:02.700 --> 00:22:05.090 align:start position:0% potentially used in a way as it is in present<00:22:03.120> form<00:22:03.299> and<00:22:04.260> the<00:22:04.380> second<00:22:04.559> question<00:22:04.799> is 00:22:05.090 --> 00:22:05.100 align:start position:0% present form and the second question is 00:22:05.100 --> 00:22:06.770 align:start position:0% present form and the second question is related<00:22:05.340> to<00:22:05.580> The<00:22:05.760> Next<00:22:05.820> Step<00:22:06.120> like<00:22:06.480> they're 00:22:06.770 --> 00:22:06.780 align:start position:0% related to The Next Step like they're 00:22:06.780 --> 00:22:09.830 align:start position:0% related to The Next Step like they're like<00:22:07.260> uh<00:22:07.980> curious<00:22:08.640> about<00:22:08.820> like<00:22:09.299> smart 00:22:09.830 --> 00:22:09.840 align:start position:0% like uh curious about like smart 00:22:09.840 --> 00:22:12.350 align:start position:0% like uh curious about like smart contracts<00:22:10.500> containing<00:22:10.980> code<00:22:11.220> then<00:22:11.580> like<00:22:11.940> is 00:22:12.350 --> 00:22:12.360 align:start position:0% contracts containing code then like is 00:22:12.360 --> 00:22:14.390 align:start position:0% contracts containing code then like is there<00:22:12.780> a<00:22:13.020> distinction<00:22:13.320> between<00:22:13.679> operation 00:22:14.390 --> 00:22:14.400 align:start position:0% there a distinction between operation 00:22:14.400 --> 00:22:17.510 align:start position:0% there a distinction between operation that<00:22:14.880> involves<00:22:15.840> uh<00:22:16.200> the<00:22:16.860> smart<00:22:17.039> wallet 00:22:17.510 --> 00:22:17.520 align:start position:0% that involves uh the smart wallet 00:22:17.520 --> 00:22:20.390 align:start position:0% that involves uh the smart wallet calling<00:22:18.179> its<00:22:18.480> own<00:22:18.600> code<00:22:18.840> versus<00:22:19.200> uh<00:22:19.980> calling 00:22:20.390 --> 00:22:20.400 align:start position:0% calling its own code versus uh calling 00:22:20.400 --> 00:22:23.330 align:start position:0% calling its own code versus uh calling uh<00:22:21.000> the<00:22:21.480> code<00:22:21.659> uh<00:22:22.260> from<00:22:22.559> a<00:22:22.740> different<00:22:22.860> contract 00:22:23.330 --> 00:22:23.340 align:start position:0% uh the code uh from a different contract 00:22:23.340 --> 00:22:26.330 align:start position:0% uh the code uh from a different contract is<00:22:23.580> it<00:22:23.820> like<00:22:24.000> uh<00:22:24.480> on<00:22:24.960> code<00:22:25.200> becomes<00:22:25.679> uh<00:22:25.860> like<00:22:26.100> a 00:22:26.330 --> 00:22:26.340 align:start position:0% is it like uh on code becomes uh like a 00:22:26.340 --> 00:22:29.390 align:start position:0% is it like uh on code becomes uh like a proxy<00:22:26.700> for<00:22:27.299> uh<00:22:27.960> other<00:22:28.500> contract<00:22:28.919> call<00:22:29.100> while 00:22:29.390 --> 00:22:29.400 align:start position:0% proxy for uh other contract call while 00:22:29.400 --> 00:22:32.330 align:start position:0% proxy for uh other contract call while interacting<00:22:29.940> with<00:22:30.179> other<00:22:30.360> uh<00:22:31.140> contracts<00:22:31.799> in 00:22:32.330 --> 00:22:32.340 align:start position:0% interacting with other uh contracts in 00:22:32.340 --> 00:22:34.549 align:start position:0% interacting with other uh contracts in that<00:22:32.520> ecosystem 00:22:34.549 --> 00:22:34.559 align:start position:0% that ecosystem 00:22:34.559 --> 00:22:36.070 align:start position:0% that ecosystem okay 00:22:36.070 --> 00:22:36.080 align:start position:0% okay 00:22:36.080 --> 00:22:39.590 align:start position:0% okay okay<00:22:37.080> for<00:22:37.860> the<00:22:37.980> first<00:22:38.039> question<00:22:38.220> how<00:22:38.700> to<00:22:38.880> edit 00:22:39.590 --> 00:22:39.600 align:start position:0% okay for the first question how to edit 00:22:39.600 --> 00:22:42.649 align:start position:0% okay for the first question how to edit account<00:22:40.500> obstruction<00:22:40.980> is<00:22:41.460> an<00:22:41.640> interface<00:22:42.120> that 00:22:42.649 --> 00:22:42.659 align:start position:0% account obstruction is an interface that 00:22:42.659 --> 00:22:45.470 align:start position:0% account obstruction is an interface that a<00:22:43.140> basic<00:22:43.860> implementation<00:22:44.340> that<00:22:45.000> we<00:22:45.120> have<00:22:45.240> in 00:22:45.470 --> 00:22:45.480 align:start position:0% a basic implementation that we have in 00:22:45.480 --> 00:22:47.810 align:start position:0% a basic implementation that we have in our<00:22:45.659> source<00:22:46.200> code<00:22:46.740> that<00:22:47.159> your<00:22:47.340> wallet<00:22:47.580> need<00:22:47.760> to 00:22:47.810 --> 00:22:47.820 align:start position:0% our source code that your wallet need to 00:22:47.820 --> 00:22:50.570 align:start position:0% our source code that your wallet need to inherit<00:22:48.260> provide<00:22:49.260> a<00:22:49.440> method<00:22:49.679> or<00:22:49.860> two<00:22:49.980> and<00:22:50.460> then 00:22:50.570 --> 00:22:50.580 align:start position:0% inherit provide a method or two and then 00:22:50.580 --> 00:22:52.970 align:start position:0% inherit provide a method or two and then the<00:22:50.940> contract<00:22:51.840> wallet<00:22:52.320> supports<00:22:52.860> account 00:22:52.970 --> 00:22:52.980 align:start position:0% the contract wallet supports account 00:22:52.980 --> 00:22:55.430 align:start position:0% the contract wallet supports account obstruction<00:22:53.400> there's<00:22:54.299> also<00:22:54.600> sample<00:22:54.900> how<00:22:55.200> we 00:22:55.430 --> 00:22:55.440 align:start position:0% obstruction there's also sample how we 00:22:55.440 --> 00:22:58.310 align:start position:0% obstruction there's also sample how we add<00:22:55.740> on<00:22:56.400> top<00:22:56.520> of<00:22:56.700> existing<00:22:57.320> ignosisafe 00:22:58.310 --> 00:22:58.320 align:start position:0% add on top of existing ignosisafe 00:22:58.320 --> 00:22:59.930 align:start position:0% add on top of existing ignosisafe without<00:22:58.799> touching<00:22:59.220> the<00:22:59.280> code<00:22:59.400> adding<00:22:59.820> a 00:22:59.930 --> 00:22:59.940 align:start position:0% without touching the code adding a 00:22:59.940 --> 00:23:02.090 align:start position:0% without touching the code adding a module<00:23:00.240> to<00:23:00.360> make<00:23:00.659> it<00:23:00.840> account<00:23:01.500> obstructed 00:23:02.090 --> 00:23:02.100 align:start position:0% module to make it account obstructed 00:23:02.100 --> 00:23:05.029 align:start position:0% module to make it account obstructed enabled<00:23:03.299> and<00:23:03.960> you<00:23:04.260> do<00:23:04.380> need<00:23:04.559> a<00:23:04.740> wallet 00:23:05.029 --> 00:23:05.039 align:start position:0% enabled and you do need a wallet 00:23:05.039 --> 00:23:08.450 align:start position:0% enabled and you do need a wallet application<00:23:05.880> or<00:23:06.780> browser<00:23:07.440> extension<00:23:07.860> that 00:23:08.450 --> 00:23:08.460 align:start position:0% application or browser extension that 00:23:08.460 --> 00:23:09.950 align:start position:0% application or browser extension that will<00:23:08.760> be<00:23:08.880> able<00:23:09.000> to<00:23:09.120> use<00:23:09.240> it 00:23:09.950 --> 00:23:09.960 align:start position:0% will be able to use it 00:23:09.960 --> 00:23:12.110 align:start position:0% will be able to use it we<00:23:10.500> have<00:23:10.620> the<00:23:10.799> basic<00:23:11.039> SDK<00:23:11.460> how<00:23:11.640> to<00:23:11.760> write<00:23:11.880> it 00:23:12.110 --> 00:23:12.120 align:start position:0% we have the basic SDK how to write it 00:23:12.120 --> 00:23:14.870 align:start position:0% we have the basic SDK how to write it there<00:23:12.419> are<00:23:12.539> several<00:23:12.840> wallets<00:23:13.200> uh<00:23:14.100> Soul<00:23:14.460> wallet 00:23:14.870 --> 00:23:14.880 align:start position:0% there are several wallets uh Soul wallet 00:23:14.880 --> 00:23:17.390 align:start position:0% there are several wallets uh Soul wallet described<00:23:15.539> behind<00:23:16.140> the<00:23:16.320> behind<00:23:16.919> you<00:23:17.039> a 00:23:17.390 --> 00:23:17.400 align:start position:0% described behind the behind you a 00:23:17.400 --> 00:23:19.850 align:start position:0% described behind the behind you a demonstrated<00:23:18.000> the<00:23:18.299> hackathon<00:23:18.720> and<00:23:19.080> also<00:23:19.380> a 00:23:19.850 --> 00:23:19.860 align:start position:0% demonstrated the hackathon and also a 00:23:19.860 --> 00:23:22.909 align:start position:0% demonstrated the hackathon and also a proton<00:23:20.280> wallet<00:23:20.640> a<00:23:21.480> hackathon<00:23:21.960> project<00:23:22.200> that 00:23:22.909 --> 00:23:22.919 align:start position:0% proton wallet a hackathon project that 00:23:22.919 --> 00:23:24.049 align:start position:0% proton wallet a hackathon project that try<00:23:23.280> to<00:23:23.340> use 00:23:24.049 --> 00:23:24.059 align:start position:0% try to use 00:23:24.059 --> 00:23:25.970 align:start position:0% try to use there<00:23:24.539> are<00:23:24.659> no 00:23:25.970 --> 00:23:25.980 align:start position:0% there are no 00:23:25.980 --> 00:23:27.890 align:start position:0% there are no implementation<00:23:26.760> in<00:23:27.000> existing<00:23:27.360> wallet<00:23:27.659> like 00:23:27.890 --> 00:23:27.900 align:start position:0% implementation in existing wallet like 00:23:27.900 --> 00:23:29.750 align:start position:0% implementation in existing wallet like metamask<00:23:28.679> doesn't<00:23:28.980> support<00:23:29.280> it<00:23:29.460> right 00:23:29.750 --> 00:23:29.760 align:start position:0% metamask doesn't support it right 00:23:29.760 --> 00:23:32.090 align:start position:0% metamask doesn't support it right correct<00:23:30.299> currently<00:23:30.900> you<00:23:31.440> have<00:23:31.620> to<00:23:31.740> use<00:23:31.860> some 00:23:32.090 --> 00:23:32.100 align:start position:0% correct currently you have to use some 00:23:32.100 --> 00:23:33.770 align:start position:0% correct currently you have to use some other<00:23:32.220> wallets<00:23:32.640> but<00:23:33.000> this<00:23:33.179> is<00:23:33.299> now<00:23:33.480> in<00:23:33.659> the 00:23:33.770 --> 00:23:33.780 align:start position:0% other wallets but this is now in the 00:23:33.780 --> 00:23:35.210 align:start position:0% other wallets but this is now in the work<00:23:33.900> there<00:23:34.140> are<00:23:34.320> several<00:23:34.500> wallets<00:23:34.919> that<00:23:35.039> are 00:23:35.210 --> 00:23:35.220 align:start position:0% work there are several wallets that are 00:23:35.220 --> 00:23:37.370 align:start position:0% work there are several wallets that are adding<00:23:35.760> account<00:23:36.059> obstruction<00:23:36.419> support 00:23:37.370 --> 00:23:37.380 align:start position:0% adding account obstruction support 00:23:37.380 --> 00:23:40.549 align:start position:0% adding account obstruction support regarding<00:23:38.220> how<00:23:38.460> the<00:23:38.700> call<00:23:38.940> is<00:23:39.179> done 00:23:40.549 --> 00:23:40.559 align:start position:0% regarding how the call is done 00:23:40.559 --> 00:23:42.890 align:start position:0% regarding how the call is done the<00:23:40.919> basic<00:23:41.159> solidity<00:23:41.580> it's<00:23:41.880> a<00:23:42.059> wallet<00:23:42.600> is<00:23:42.720> a 00:23:42.890 --> 00:23:42.900 align:start position:0% the basic solidity it's a wallet is a 00:23:42.900 --> 00:23:43.669 align:start position:0% the basic solidity it's a wallet is a contract 00:23:43.669 --> 00:23:43.679 align:start position:0% contract 00:23:43.679 --> 00:23:46.070 align:start position:0% contract when 00:23:46.070 --> 00:23:46.080 align:start position:0% when 00:23:46.080 --> 00:23:48.409 align:start position:0% when when someone<00:23:46.679> make<00:23:46.919> a<00:23:47.100> call<00:23:47.220> it<00:23:47.460> validates<00:23:48.000> it 00:23:48.409 --> 00:23:48.419 align:start position:0% when someone make a call it validates it 00:23:48.419 --> 00:23:50.090 align:start position:0% when someone make a call it validates it is<00:23:48.600> allowed<00:23:48.960> to<00:23:49.080> make<00:23:49.200> this<00:23:49.380> call<00:23:49.559> that<00:23:49.919> is 00:23:50.090 --> 00:23:50.100 align:start position:0% is allowed to make this call that is 00:23:50.100 --> 00:23:51.649 align:start position:0% is allowed to make this call that is either<00:23:50.340> the<00:23:50.640> owner<00:23:50.940> or<00:23:51.240> through<00:23:51.480> account 00:23:51.649 --> 00:23:51.659 align:start position:0% either the owner or through account 00:23:51.659 --> 00:23:53.930 align:start position:0% either the owner or through account obstruction<00:23:52.020> the<00:23:52.440> validation<00:23:53.400> method<00:23:53.760> and 00:23:53.930 --> 00:23:53.940 align:start position:0% obstruction the validation method and 00:23:53.940 --> 00:23:56.930 align:start position:0% obstruction the validation method and then<00:23:54.120> it<00:23:54.299> makes<00:23:54.539> a<00:23:54.780> call<00:23:54.900> outside<00:23:55.200> so<00:23:56.039> anyone 00:23:56.930 --> 00:23:56.940 align:start position:0% then it makes a call outside so anyone 00:23:56.940 --> 00:23:58.789 align:start position:0% then it makes a call outside so anyone any<00:23:57.240> other<00:23:57.480> contract<00:23:57.840> sees<00:23:58.140> this<00:23:58.320> contract<00:23:58.620> as 00:23:58.789 --> 00:23:58.799 align:start position:0% any other contract sees this contract as 00:23:58.799 --> 00:24:00.409 align:start position:0% any other contract sees this contract as the<00:23:58.980> account<00:23:59.100> that<00:23:59.340> makes<00:23:59.580> the<00:24:00.059> operation 00:24:00.409 --> 00:24:00.419 align:start position:0% the account that makes the operation 00:24:00.419 --> 00:24:02.690 align:start position:0% the account that makes the operation like<00:24:00.720> whether<00:24:01.260> it's<00:24:01.380> a<00:24:01.559> token<00:24:02.039> transfer<00:24:02.460> or 00:24:02.690 --> 00:24:02.700 align:start position:0% like whether it's a token transfer or 00:24:02.700 --> 00:24:06.110 align:start position:0% like whether it's a token transfer or voting<00:24:03.179> or<00:24:03.419> whatever 00:24:06.110 --> 00:24:06.120 align:start position:0% 00:24:06.120 --> 00:24:07.970 align:start position:0% we<00:24:06.539> have<00:24:06.720> another<00:24:06.840> question 00:24:07.970 --> 00:24:07.980 align:start position:0% we have another question 00:24:07.980 --> 00:24:11.330 align:start position:0% we have another question so<00:24:08.760> regarding<00:24:09.360> smart<00:24:09.720> contract<00:24:10.140> wallets 00:24:11.330 --> 00:24:11.340 align:start position:0% so regarding smart contract wallets 00:24:11.340 --> 00:24:13.370 align:start position:0% so regarding smart contract wallets um<00:24:11.400> so<00:24:12.120> can<00:24:12.419> you<00:24:12.539> can<00:24:12.720> you<00:24:12.840> comment<00:24:13.080> on<00:24:13.260> the 00:24:13.370 --> 00:24:13.380 align:start position:0% um so can you can you comment on the 00:24:13.380 --> 00:24:16.130 align:start position:0% um so can you can you comment on the situation<00:24:13.740> on<00:24:13.980> when<00:24:14.460> you<00:24:14.700> need<00:24:14.880> to<00:24:15.120> use<00:24:15.419> L2 00:24:16.130 --> 00:24:16.140 align:start position:0% situation on when you need to use L2 00:24:16.140 --> 00:24:18.789 align:start position:0% situation on when you need to use L2 Solutions<00:24:16.679> because<00:24:17.220> in<00:24:17.760> most<00:24:18.000> of<00:24:18.179> the<00:24:18.299> cases 00:24:18.789 --> 00:24:18.799 align:start position:0% Solutions because in most of the cases 00:24:18.799 --> 00:24:21.710 align:start position:0% Solutions because in most of the cases you<00:24:19.799> you<00:24:19.980> cannot<00:24:20.460> because<00:24:20.880> you<00:24:21.179> have<00:24:21.299> a<00:24:21.480> small 00:24:21.710 --> 00:24:21.720 align:start position:0% you you cannot because you have a small 00:24:21.720 --> 00:24:24.230 align:start position:0% you you cannot because you have a small contract<00:24:22.080> wallet<00:24:22.440> Deploy<00:24:22.799> on<00:24:23.100> mainnet<00:24:23.580> and 00:24:24.230 --> 00:24:24.240 align:start position:0% contract wallet Deploy on mainnet and 00:24:24.240 --> 00:24:27.110 align:start position:0% contract wallet Deploy on mainnet and you<00:24:24.419> cannot<00:24:24.780> deploy<00:24:25.200> it<00:24:25.320> on<00:24:25.679> the<00:24:25.860> same<00:24:26.039> on<00:24:26.940> this 00:24:27.110 --> 00:24:27.120 align:start position:0% you cannot deploy it on the same on this 00:24:27.120 --> 00:24:31.010 align:start position:0% you cannot deploy it on the same on this uh<00:24:27.960> um<00:24:28.020> on<00:24:28.559> on<00:24:28.799> every<00:24:29.100> L2<00:24:29.640> like<00:24:30.000> arbit<00:24:30.539> room<00:24:30.780> or 00:24:31.010 --> 00:24:31.020 align:start position:0% uh um on on every L2 like arbit room or 00:24:31.020 --> 00:24:34.549 align:start position:0% uh um on on every L2 like arbit room or Optimus<00:24:31.500> because<00:24:32.039> it<00:24:32.760> you<00:24:33.179> know<00:24:33.240> it's<00:24:33.539> it's<00:24:33.900> uh 00:24:34.549 --> 00:24:34.559 align:start position:0% Optimus because it you know it's it's uh 00:24:34.559 --> 00:24:37.070 align:start position:0% Optimus because it you know it's it's uh for<00:24:34.980> instance<00:24:35.159> sorry<00:24:36.240> it<00:24:36.659> will<00:24:36.780> become<00:24:37.020> a 00:24:37.070 --> 00:24:37.080 align:start position:0% for instance sorry it will become a 00:24:37.080 --> 00:24:38.390 align:start position:0% for instance sorry it will become a different<00:24:37.200> answers<00:24:37.559> that's<00:24:37.799> what<00:24:38.039> you<00:24:38.220> mean 00:24:38.390 --> 00:24:38.400 align:start position:0% different answers that's what you mean 00:24:38.400 --> 00:24:41.390 align:start position:0% different answers that's what you mean so<00:24:39.059> so<00:24:39.299> you<00:24:39.900> you<00:24:40.140> will<00:24:40.380> need<00:24:40.620> to<00:24:40.740> represent<00:24:41.159> the 00:24:41.390 --> 00:24:41.400 align:start position:0% so so you you will need to represent the 00:24:41.400 --> 00:24:45.770 align:start position:0% so so you you will need to represent the exact<00:24:42.320> the<00:24:43.320> exact<00:24:43.679> deployment<00:24:44.360> to<00:24:45.360> get<00:24:45.539> the 00:24:45.770 --> 00:24:45.780 align:start position:0% exact the exact deployment to get the 00:24:45.780 --> 00:24:48.289 align:start position:0% exact the exact deployment to get the same<00:24:45.960> address<00:24:46.200> in<00:24:46.799> order<00:24:46.919> to<00:24:47.340> do<00:24:47.820> things<00:24:48.059> like 00:24:48.289 --> 00:24:48.299 align:start position:0% same address in order to do things like 00:24:48.299 --> 00:24:51.169 align:start position:0% same address in order to do things like claims<00:24:48.780> of<00:24:49.380> course<00:24:49.500> yes<00:24:50.280> the<00:24:50.820> short<00:24:50.940> answer 00:24:51.169 --> 00:24:51.179 align:start position:0% claims of course yes the short answer 00:24:51.179 --> 00:24:53.810 align:start position:0% claims of course yes the short answer yes<00:24:51.600> we<00:24:52.080> built<00:24:52.320> it<00:24:52.440> in<00:24:52.620> a<00:24:52.740> way<00:24:52.860> that<00:24:53.340> it<00:24:53.640> will 00:24:53.810 --> 00:24:53.820 align:start position:0% yes we built it in a way that it will 00:24:53.820 --> 00:24:55.789 align:start position:0% yes we built it in a way that it will create<00:24:54.120> the<00:24:54.480> same<00:24:54.659> address<00:24:54.900> so<00:24:55.440> you<00:24:55.559> can<00:24:55.620> have 00:24:55.789 --> 00:24:55.799 align:start position:0% create the same address so you can have 00:24:55.799 --> 00:24:57.350 align:start position:0% create the same address so you can have the<00:24:55.980> same<00:24:56.100> address<00:24:56.280> on<00:24:56.580> multiple<00:24:56.880> networks 00:24:57.350 --> 00:24:57.360 align:start position:0% the same address on multiple networks 00:24:57.360 --> 00:24:59.750 align:start position:0% the same address on multiple networks yes<00:24:57.900> as<00:24:58.140> a<00:24:58.380> wallet<00:24:58.679> developer<00:24:59.220> it<00:24:59.460> requires 00:24:59.750 --> 00:24:59.760 align:start position:0% yes as a wallet developer it requires 00:24:59.760 --> 00:25:01.909 align:start position:0% yes as a wallet developer it requires some<00:25:00.000> work<00:25:00.179> from<00:25:00.360> you<00:25:00.539> in<00:25:00.900> order<00:25:01.020> for<00:25:01.620> that<00:25:01.740> to 00:25:01.909 --> 00:25:01.919 align:start position:0% some work from you in order for that to 00:25:01.919 --> 00:25:04.370 align:start position:0% some work from you in order for that to be<00:25:02.039> possible<00:25:02.940> but<00:25:03.539> it<00:25:03.659> is<00:25:03.840> not<00:25:03.960> that<00:25:04.080> difficult 00:25:04.370 --> 00:25:04.380 align:start position:0% be possible but it is not that difficult 00:25:04.380 --> 00:25:05.810 align:start position:0% be possible but it is not that difficult and<00:25:04.740> it<00:25:04.980> can<00:25:05.159> be 00:25:05.810 --> 00:25:05.820 align:start position:0% and it can be 00:25:05.820 --> 00:25:07.010 align:start position:0% and it can be done<00:25:06.059> even 00:25:07.010 --> 00:25:07.020 align:start position:0% done even 00:25:07.020 --> 00:25:10.970 align:start position:0% done even the<00:25:07.740> minimals 00:25:10.970 --> 00:25:10.980 align:start position:0% 00:25:10.980 --> 00:25:12.230 align:start position:0% the 00:25:12.230 --> 00:25:12.240 align:start position:0% the 00:25:12.240 --> 00:25:13.909 align:start position:0% the the<00:25:12.539> minimally 00:25:13.909 --> 00:25:13.919 align:start position:0% the minimally 00:25:13.919 --> 00:25:16.190 align:start position:0% the minimally implementation<00:25:14.520> of<00:25:14.640> that<00:25:14.760> is<00:25:14.940> happening<00:25:15.480> when 00:25:16.190 --> 00:25:16.200 align:start position:0% implementation of that is happening when 00:25:16.200 --> 00:25:17.930 align:start position:0% implementation of that is happening when you<00:25:16.380> just<00:25:16.740> funding<00:25:17.340> your<00:25:17.460> wallet<00:25:17.700> the<00:25:17.880> first 00:25:17.930 --> 00:25:17.940 align:start position:0% you just funding your wallet the first 00:25:17.940 --> 00:25:20.090 align:start position:0% you just funding your wallet the first time<00:25:18.120> think<00:25:18.419> of<00:25:18.539> it<00:25:18.720> you<00:25:19.020> open<00:25:19.380> your<00:25:19.679> wallet 00:25:20.090 --> 00:25:20.100 align:start position:0% time think of it you open your wallet 00:25:20.100 --> 00:25:21.890 align:start position:0% time think of it you open your wallet software<00:25:20.340> you<00:25:20.520> see<00:25:20.700> the<00:25:20.820> address<00:25:20.940> it<00:25:21.659> is<00:25:21.780> not 00:25:21.890 --> 00:25:21.900 align:start position:0% software you see the address it is not 00:25:21.900 --> 00:25:23.450 align:start position:0% software you see the address it is not deployed<00:25:22.200> anywhere<00:25:22.500> you<00:25:22.980> see<00:25:23.100> my<00:25:23.280> your 00:25:23.450 --> 00:25:23.460 align:start position:0% deployed anywhere you see my your 00:25:23.460 --> 00:25:26.029 align:start position:0% deployed anywhere you see my your address<00:25:23.700> you<00:25:24.299> go<00:25:24.419> to<00:25:24.539> index<00:25:24.840> and<00:25:25.080> you<00:25:25.200> move<00:25:25.380> eth 00:25:26.029 --> 00:25:26.039 align:start position:0% address you go to index and you move eth 00:25:26.039 --> 00:25:28.370 align:start position:0% address you go to index and you move eth or<00:25:26.220> whatever<00:25:26.460> into<00:25:26.760> it<00:25:27.000> and<00:25:27.720> then<00:25:27.840> you<00:25:28.020> make<00:25:28.260> a 00:25:28.370 --> 00:25:28.380 align:start position:0% or whatever into it and then you make a 00:25:28.380 --> 00:25:30.289 align:start position:0% or whatever into it and then you make a transaction<00:25:28.740> with<00:25:28.980> that<00:25:29.159> wallet 00:25:30.289 --> 00:25:30.299 align:start position:0% transaction with that wallet 00:25:30.299 --> 00:25:32.510 align:start position:0% transaction with that wallet if<00:25:30.659> you're<00:25:30.720> thinking<00:25:30.900> of<00:25:31.500> it<00:25:31.679> this<00:25:32.159> wallet 00:25:32.510 --> 00:25:32.520 align:start position:0% if you're thinking of it this wallet 00:25:32.520 --> 00:25:35.029 align:start position:0% if you're thinking of it this wallet contract<00:25:32.940> will<00:25:33.539> pay<00:25:34.200> for<00:25:34.380> its<00:25:34.559> own<00:25:34.679> deployment 00:25:35.029 --> 00:25:35.039 align:start position:0% contract will pay for its own deployment 00:25:35.039 --> 00:25:37.250 align:start position:0% contract will pay for its own deployment and<00:25:35.340> then<00:25:35.520> execute<00:25:35.940> yes<00:25:36.600> that's<00:25:36.900> how<00:25:37.080> account 00:25:37.250 --> 00:25:37.260 align:start position:0% and then execute yes that's how account 00:25:37.260 --> 00:25:39.289 align:start position:0% and then execute yes that's how account abstraction<00:25:37.740> implementation<00:25:38.220> works<00:25:38.520> today 00:25:39.289 --> 00:25:39.299 align:start position:0% abstraction implementation works today 00:25:39.299 --> 00:25:45.890 align:start position:0% abstraction implementation works today so<00:25:39.659> it<00:25:39.840> works<00:25:40.200> any<00:25:40.679> more<00:25:40.980> questions 00:25:45.890 --> 00:25:45.900 align:start position:0% 00:25:45.900 --> 00:25:48.409 align:start position:0% thank<00:25:46.440> you<00:25:46.559> for<00:25:46.740> your<00:25:46.919> presentation 00:25:48.409 --> 00:25:48.419 align:start position:0% thank you for your presentation 00:25:48.419 --> 00:25:50.450 align:start position:0% thank you for your presentation um I<00:25:48.960> guess<00:25:49.080> we<00:25:49.260> all<00:25:49.380> agree<00:25:49.679> about<00:25:49.860> like<00:25:50.220> the 00:25:50.450 --> 00:25:50.460 align:start position:0% um I guess we all agree about like the 00:25:50.460 --> 00:25:52.669 align:start position:0% um I guess we all agree about like the importance<00:25:50.820> of<00:25:51.120> account<00:25:51.360> abstraction<00:25:51.960> and 00:25:52.669 --> 00:25:52.679 align:start position:0% importance of account abstraction and 00:25:52.679 --> 00:25:54.950 align:start position:0% importance of account abstraction and this<00:25:52.860> is<00:25:52.919> what<00:25:53.159> Luxo<00:25:53.640> was<00:25:53.880> working<00:25:54.480> on<00:25:54.720> like 00:25:54.950 --> 00:25:54.960 align:start position:0% this is what Luxo was working on like 00:25:54.960 --> 00:25:57.649 align:start position:0% this is what Luxo was working on like starting<00:25:55.260> from<00:25:55.620> 2018<00:25:56.120> and<00:25:57.120> like<00:25:57.299> starting 00:25:57.649 --> 00:25:57.659 align:start position:0% starting from 2018 and like starting 00:25:57.659 --> 00:26:00.830 align:start position:0% starting from 2018 and like starting with<00:25:57.840> ERC<00:25:58.320> 725<00:25:58.919> standard<00:25:59.400> but<00:26:00.240> and<00:26:00.539> I<00:26:00.720> was 00:26:00.830 --> 00:26:00.840 align:start position:0% with ERC 725 standard but and I was 00:26:00.840 --> 00:26:04.669 align:start position:0% with ERC 725 standard but and I was checking<00:26:01.260> the<00:26:01.799> the<00:26:02.400> CRC<00:26:02.940> like<00:26:03.360> way<00:26:03.600> before<00:26:03.840> and 00:26:04.669 --> 00:26:04.679 align:start position:0% checking the the CRC like way before and 00:26:04.679 --> 00:26:07.010 align:start position:0% checking the the CRC like way before and like<00:26:04.980> I<00:26:05.460> couldn't<00:26:05.820> understand<00:26:06.179> because<00:26:06.659> it 00:26:07.010 --> 00:26:07.020 align:start position:0% like I couldn't understand because it 00:26:07.020 --> 00:26:09.890 align:start position:0% like I couldn't understand because it was<00:26:07.140> way<00:26:07.440> like<00:26:08.279> too<00:26:08.520> complicated<00:26:09.000> but<00:26:09.480> I<00:26:09.720> have 00:26:09.890 --> 00:26:09.900 align:start position:0% was way like too complicated but I have 00:26:09.900 --> 00:26:11.630 align:start position:0% was way like too complicated but I have just<00:26:10.140> two<00:26:10.440> questions 00:26:11.630 --> 00:26:11.640 align:start position:0% just two questions 00:26:11.640 --> 00:26:14.450 align:start position:0% just two questions like<00:26:12.360> can<00:26:12.600> you<00:26:12.779> explain<00:26:13.020> more<00:26:13.559> about<00:26:13.799> like<00:26:14.159> how 00:26:14.450 --> 00:26:14.460 align:start position:0% like can you explain more about like how 00:26:14.460 --> 00:26:17.269 align:start position:0% like can you explain more about like how users<00:26:14.880> can<00:26:15.179> choose<00:26:15.539> the<00:26:16.080> implementation 00:26:17.269 --> 00:26:17.279 align:start position:0% users can choose the implementation 00:26:17.279 --> 00:26:19.909 align:start position:0% users can choose the implementation and<00:26:17.820> about<00:26:18.000> like<00:26:18.480> the<00:26:18.779> cross<00:26:18.960> chain<00:26:19.260> execution 00:26:19.909 --> 00:26:19.919 align:start position:0% and about like the cross chain execution 00:26:19.919 --> 00:26:22.070 align:start position:0% and about like the cross chain execution and<00:26:20.520> just<00:26:20.760> an<00:26:20.880> open<00:26:21.000> question<00:26:21.360> maybe<00:26:21.659> we<00:26:21.960> can 00:26:22.070 --> 00:26:22.080 align:start position:0% and just an open question maybe we can 00:26:22.080 --> 00:26:24.350 align:start position:0% and just an open question maybe we can discuss<00:26:22.440> that<00:26:22.679> later<00:26:22.919> like<00:26:23.700> don't<00:26:24.000> you<00:26:24.179> think 00:26:24.350 --> 00:26:24.360 align:start position:0% discuss that later like don't you think 00:26:24.360 --> 00:26:26.450 align:start position:0% discuss that later like don't you think that<00:26:24.600> the<00:26:24.779> standardization<00:26:25.559> of<00:26:26.220> the<00:26:26.340> account 00:26:26.450 --> 00:26:26.460 align:start position:0% that the standardization of the account 00:26:26.460 --> 00:26:29.149 align:start position:0% that the standardization of the account up<00:26:27.000> like<00:26:27.360> the<00:26:27.600> account<00:26:27.840> need<00:26:28.380> more<00:26:28.679> standard 00:26:29.149 --> 00:26:29.159 align:start position:0% up like the account need more standard 00:26:29.159 --> 00:26:32.570 align:start position:0% up like the account need more standard laser<00:26:29.960> standardization<00:26:30.960> of<00:26:31.559> other<00:26:32.220> stuff 00:26:32.570 --> 00:26:32.580 align:start position:0% laser standardization of other stuff 00:26:32.580 --> 00:26:35.210 align:start position:0% laser standardization of other stuff like<00:26:33.179> I<00:26:33.480> will<00:26:33.600> give<00:26:33.720> you<00:26:33.840> an<00:26:34.020> example<00:26:34.320> if<00:26:35.100> you 00:26:35.210 --> 00:26:35.220 align:start position:0% like I will give you an example if you 00:26:35.220 --> 00:26:37.669 align:start position:0% like I will give you an example if you have<00:26:35.340> a<00:26:35.520> like<00:26:35.700> a<00:26:36.059> your<00:26:36.659> account<00:26:36.960> needs<00:26:37.500> to 00:26:37.669 --> 00:26:37.679 align:start position:0% have a like a your account needs to 00:26:37.679 --> 00:26:39.350 align:start position:0% have a like a your account needs to receive<00:26:38.039> token 00:26:39.350 --> 00:26:39.360 align:start position:0% receive token 00:26:39.360 --> 00:26:41.950 align:start position:0% receive token it<00:26:39.720> needs<00:26:40.020> to<00:26:40.140> implement<00:26:40.500> on 00:26:41.950 --> 00:26:41.960 align:start position:0% it needs to implement on 00:26:41.960 --> 00:26:46.490 align:start position:0% it needs to implement on erc721<00:26:42.960> received<00:26:43.520> on<00:26:44.520> your<00:26:44.779> c1155<00:26:45.779> received 00:26:46.490 --> 00:26:46.500 align:start position:0% erc721 received on your c1155 received 00:26:46.500 --> 00:26:49.549 align:start position:0% erc721 received on your c1155 received and<00:26:46.919> token<00:26:47.400> received<00:26:47.760> for<00:26:48.000> erc223 00:26:49.549 --> 00:26:49.559 align:start position:0% and token received for erc223 00:26:49.559 --> 00:26:52.190 align:start position:0% and token received for erc223 but<00:26:50.279> like<00:26:50.520> what<00:26:50.880> if<00:26:51.120> we<00:26:51.299> come<00:26:51.480> up<00:26:51.659> with<00:26:51.900> a<00:26:52.020> new 00:26:52.190 --> 00:26:52.200 align:start position:0% but like what if we come up with a new 00:26:52.200 --> 00:26:53.990 align:start position:0% but like what if we come up with a new standard<00:26:52.620> in<00:26:52.799> the<00:26:52.919> future 00:26:53.990 --> 00:26:54.000 align:start position:0% standard in the future 00:26:54.000 --> 00:26:57.549 align:start position:0% standard in the future like<00:26:54.720> on<00:26:55.080> we<00:26:55.380> need<00:26:55.559> on<00:26:55.980> ERC 00:26:57.549 --> 00:26:57.559 align:start position:0% like on we need on ERC 00:26:57.559 --> 00:27:02.330 align:start position:0% like on we need on ERC 6700<00:26:58.559> maybe<00:26:59.100> and<00:26:59.700> like<00:27:00.240> maybe<00:27:00.539> also<00:27:01.080> we<00:27:01.380> need 00:27:02.330 --> 00:27:02.340 align:start position:0% 6700 maybe and like maybe also we need 00:27:02.340 --> 00:27:05.810 align:start position:0% 6700 maybe and like maybe also we need something<00:27:03.179> related<00:27:03.900> to<00:27:04.320> followers<00:27:04.799> or<00:27:05.279> like<00:27:05.520> I 00:27:05.810 --> 00:27:05.820 align:start position:0% something related to followers or like I 00:27:05.820 --> 00:27:07.730 align:start position:0% something related to followers or like I don't<00:27:05.880> know<00:27:06.000> why<00:27:06.240> because<00:27:06.659> now<00:27:07.080> it's<00:27:07.380> related 00:27:07.730 --> 00:27:07.740 align:start position:0% don't know why because now it's related 00:27:07.740 --> 00:27:10.549 align:start position:0% don't know why because now it's related to<00:27:07.980> token<00:27:08.460> now<00:27:08.940> the<00:27:09.179> hype<00:27:09.539> is<00:27:09.600> token<00:27:09.960> maybe<00:27:10.320> in 00:27:10.549 --> 00:27:10.559 align:start position:0% to token now the hype is token maybe in 00:27:10.559 --> 00:27:12.350 align:start position:0% to token now the hype is token maybe in the<00:27:10.679> future<00:27:10.799> it's<00:27:11.100> not 00:27:12.350 --> 00:27:12.360 align:start position:0% the future it's not 00:27:12.360 --> 00:27:14.029 align:start position:0% the future it's not we<00:27:12.720> can<00:27:12.840> discuss<00:27:13.140> that<00:27:13.380> later<00:27:13.559> if<00:27:13.799> you<00:27:13.980> want 00:27:14.029 --> 00:27:14.039 align:start position:0% we can discuss that later if you want 00:27:14.039 --> 00:27:16.430 align:start position:0% we can discuss that later if you want I'll<00:27:14.400> try<00:27:14.520> from<00:27:14.700> the<00:27:14.880> beginning<00:27:15.059> yes<00:27:16.020> there 00:27:16.430 --> 00:27:16.440 align:start position:0% I'll try from the beginning yes there 00:27:16.440 --> 00:27:17.810 align:start position:0% I'll try from the beginning yes there were<00:27:16.620> wallet<00:27:17.039> accounts<00:27:17.400> before<00:27:17.580> account 00:27:17.810 --> 00:27:17.820 align:start position:0% were wallet accounts before account 00:27:17.820 --> 00:27:19.789 align:start position:0% were wallet accounts before account obstruction<00:27:18.240> they<00:27:18.600> exist<00:27:18.960> from<00:27:19.679> the 00:27:19.789 --> 00:27:19.799 align:start position:0% obstruction they exist from the 00:27:19.799 --> 00:27:21.649 align:start position:0% obstruction they exist from the beginning<00:27:19.919> of<00:27:20.279> a<00:27:20.520> ethereum<00:27:20.940> which<00:27:21.179> is<00:27:21.360> not<00:27:21.480> far 00:27:21.649 --> 00:27:21.659 align:start position:0% beginning of a ethereum which is not far 00:27:21.659 --> 00:27:23.890 align:start position:0% beginning of a ethereum which is not far away<00:27:21.840> but<00:27:22.440> they<00:27:22.860> exist 00:27:23.890 --> 00:27:23.900 align:start position:0% away but they exist 00:27:23.900 --> 00:27:26.810 align:start position:0% away but they exist we<00:27:24.900> didn't<00:27:25.020> invent<00:27:25.260> the<00:27:25.440> wheel<00:27:25.559> we<00:27:26.279> created<00:27:26.580> a 00:27:26.810 --> 00:27:26.820 align:start position:0% we didn't invent the wheel we created a 00:27:26.820 --> 00:27:29.210 align:start position:0% we didn't invent the wheel we created a standard<00:27:27.120> which<00:27:27.659> allows<00:27:28.200> the<00:27:28.860> framework 00:27:29.210 --> 00:27:29.220 align:start position:0% standard which allows the framework 00:27:29.220 --> 00:27:31.130 align:start position:0% standard which allows the framework which<00:27:29.580> allowed<00:27:29.880> nodes<00:27:30.240> to<00:27:30.539> support<00:27:30.779> such 00:27:31.130 --> 00:27:31.140 align:start position:0% which allowed nodes to support such 00:27:31.140 --> 00:27:33.529 align:start position:0% which allowed nodes to support such accounts<00:27:31.679> accounts<00:27:32.460> to<00:27:32.580> be<00:27:32.760> able<00:27:32.940> to<00:27:33.059> behave 00:27:33.529 --> 00:27:33.539 align:start position:0% accounts accounts to be able to behave 00:27:33.539 --> 00:27:36.649 align:start position:0% accounts accounts to be able to behave as<00:27:34.440> close<00:27:34.980> as<00:27:35.220> possible<00:27:35.520> to<00:27:35.820> your<00:27:36.120> accounts 00:27:36.649 --> 00:27:36.659 align:start position:0% as close as possible to your accounts 00:27:36.659 --> 00:27:40.789 align:start position:0% as close as possible to your accounts like<00:27:36.900> pay<00:27:37.320> for<00:27:37.500> their<00:27:37.620> own<00:27:37.799> deployments<00:27:38.340> which 00:27:40.789 --> 00:27:40.799 align:start position:0% like pay for their own deployments which 00:27:40.799 --> 00:27:43.730 align:start position:0% like pay for their own deployments which would<00:27:40.860> be<00:27:40.919> tricky<00:27:41.279> it's<00:27:41.460> possible<00:27:41.700> we 00:27:43.730 --> 00:27:43.740 align:start position:0% would be tricky it's possible we 00:27:43.740 --> 00:27:45.890 align:start position:0% would be tricky it's possible we we<00:27:43.860> created<00:27:44.159> one<00:27:44.460> there 00:27:45.890 --> 00:27:45.900 align:start position:0% we created one there 00:27:45.900 --> 00:27:48.909 align:start position:0% we created one there we<00:27:46.320> did<00:27:46.440> standardize<00:27:47.039> on<00:27:47.340> a<00:27:47.520> way<00:27:47.760> to<00:27:48.240> perform 00:27:48.909 --> 00:27:48.919 align:start position:0% we did standardize on a way to perform 00:27:48.919 --> 00:27:51.950 align:start position:0% we did standardize on a way to perform validate<00:27:49.919> to<00:27:50.220> separate<00:27:50.460> validation<00:27:51.120> from 00:27:51.950 --> 00:27:51.960 align:start position:0% validate to separate validation from 00:27:51.960 --> 00:27:53.090 align:start position:0% validate to separate validation from execution 00:27:53.090 --> 00:27:53.100 align:start position:0% execution 00:27:53.100 --> 00:27:56.350 align:start position:0% execution in<00:27:53.700> order<00:27:53.880> to<00:27:54.360> that<00:27:54.600> in<00:27:55.200> order<00:27:55.380> that<00:27:55.679> they 00:27:56.350 --> 00:27:56.360 align:start position:0% in order to that in order that they 00:27:56.360 --> 00:27:59.830 align:start position:0% in order to that in order that they validate<00:27:57.360> us<00:27:57.539> what<00:27:57.900> we<00:27:58.020> call<00:27:58.140> bundlers<00:27:58.620> can<00:27:59.520> be 00:27:59.830 --> 00:27:59.840 align:start position:0% validate us what we call bundlers can be 00:27:59.840 --> 00:28:02.750 align:start position:0% validate us what we call bundlers can be self-sustained<00:28:00.840> and<00:28:01.020> can<00:28:01.200> be<00:28:01.500> a<00:28:01.860> dose 00:28:02.750 --> 00:28:02.760 align:start position:0% self-sustained and can be a dose 00:28:02.760 --> 00:28:04.310 align:start position:0% self-sustained and can be a dose protected 00:28:04.310 --> 00:28:04.320 align:start position:0% protected 00:28:04.320 --> 00:28:06.769 align:start position:0% protected yes<00:28:04.740> the<00:28:04.919> AP<00:28:05.100> is<00:28:05.340> complex<00:28:05.640> but<00:28:06.120> most<00:28:06.419> of<00:28:06.600> these 00:28:06.769 --> 00:28:06.779 align:start position:0% yes the AP is complex but most of these 00:28:06.779 --> 00:28:09.289 align:start position:0% yes the AP is complex but most of these complexity<00:28:07.740> comes<00:28:08.640> from<00:28:08.820> these<00:28:09.059> protection 00:28:09.289 --> 00:28:09.299 align:start position:0% complexity comes from these protection 00:28:09.299 --> 00:28:10.430 align:start position:0% complexity comes from these protection mechanisms 00:28:10.430 --> 00:28:10.440 align:start position:0% mechanisms 00:28:10.440 --> 00:28:13.610 align:start position:0% mechanisms if<00:28:11.240> we<00:28:12.240> should<00:28:12.360> rewrite<00:28:12.720> it<00:28:12.900> in<00:28:13.020> a<00:28:13.140> way<00:28:13.260> that<00:28:13.440> is 00:28:13.610 --> 00:28:13.620 align:start position:0% if we should rewrite it in a way that is 00:28:13.620 --> 00:28:15.649 align:start position:0% if we should rewrite it in a way that is more<00:28:13.860> account<00:28:14.279> friendly<00:28:14.760> because<00:28:15.360> most 00:28:15.649 --> 00:28:15.659 align:start position:0% more account friendly because most 00:28:15.659 --> 00:28:17.810 align:start position:0% more account friendly because most people<00:28:15.900> don't<00:28:16.140> Implement<00:28:16.500> a<00:28:16.860> bundler<00:28:17.279> they 00:28:17.810 --> 00:28:17.820 align:start position:0% people don't Implement a bundler they 00:28:17.820 --> 00:28:19.250 align:start position:0% people don't Implement a bundler they want<00:28:18.059> to<00:28:18.179> implement<00:28:18.480> an<00:28:18.659> account<00:28:18.840> so<00:28:19.020> they 00:28:19.250 --> 00:28:19.260 align:start position:0% want to implement an account so they 00:28:19.260 --> 00:28:21.230 align:start position:0% want to implement an account so they need<00:28:19.380> to<00:28:19.440> know<00:28:19.559> what<00:28:19.860> they<00:28:19.980> have<00:28:20.159> to<00:28:20.220> do<00:28:20.400> maybe 00:28:21.230 --> 00:28:21.240 align:start position:0% need to know what they have to do maybe 00:28:21.240 --> 00:28:22.610 align:start position:0% need to know what they have to do maybe some<00:28:21.480> of<00:28:21.600> the<00:28:21.720> limitations<00:28:22.020> they<00:28:22.320> have<00:28:22.440> on 00:28:22.610 --> 00:28:22.620 align:start position:0% some of the limitations they have on 00:28:22.620 --> 00:28:24.470 align:start position:0% some of the limitations they have on what<00:28:22.919> they<00:28:23.039> do<00:28:23.220> and<00:28:23.580> they<00:28:23.940> don't<00:28:24.059> care<00:28:24.299> about 00:28:24.470 --> 00:28:24.480 align:start position:0% what they do and they don't care about 00:28:24.480 --> 00:28:26.769 align:start position:0% what they do and they don't care about the<00:28:24.779> low<00:28:24.900> level<00:28:25.080> implementation<00:28:25.740> yes 00:28:26.769 --> 00:28:26.779 align:start position:0% the low level implementation yes 00:28:26.779 --> 00:28:29.990 align:start position:0% the low level implementation yes editorial<00:28:27.779> work<00:28:28.320> is<00:28:28.799> required<00:28:29.220> for<00:28:29.400> this<00:28:29.700> uh 00:28:29.990 --> 00:28:30.000 align:start position:0% editorial work is required for this uh 00:28:30.000 --> 00:28:32.090 align:start position:0% editorial work is required for this uh spec<00:28:30.419> I<00:28:30.960> agree 00:28:32.090 --> 00:28:32.100 align:start position:0% spec I agree 00:28:32.100 --> 00:28:33.710 align:start position:0% spec I agree and<00:28:32.940> they 00:28:33.710 --> 00:28:33.720 align:start position:0% and they 00:28:33.720 --> 00:28:35.570 align:start position:0% and they of<00:28:34.200> course<00:28:34.260> change<00:28:34.559> the<00:28:34.740> execution<00:28:35.100> a<00:28:35.460> cross 00:28:35.570 --> 00:28:35.580 align:start position:0% of course change the execution a cross 00:28:35.580 --> 00:28:37.370 align:start position:0% of course change the execution a cross chain<00:28:35.820> execution<00:28:36.299> let's<00:28:36.659> take<00:28:36.840> it<00:28:37.020> off<00:28:37.140> chain 00:28:37.370 --> 00:28:37.380 align:start position:0% chain execution let's take it off chain 00:28:37.380 --> 00:28:40.130 align:start position:0% chain execution let's take it off chain again<00:28:38.039> nothing<00:28:38.700> of<00:28:39.000> it<00:28:39.120> is<00:28:39.360> in<00:28:39.600> the<00:28:39.720> core<00:28:39.900> of 00:28:40.130 --> 00:28:40.140 align:start position:0% again nothing of it is in the core of 00:28:40.140 --> 00:28:42.409 align:start position:0% again nothing of it is in the core of the<00:28:40.260> EIP<00:28:40.620> like<00:28:41.159> BLS 00:28:42.409 --> 00:28:42.419 align:start position:0% the EIP like BLS 00:28:42.419 --> 00:28:44.570 align:start position:0% the EIP like BLS there's<00:28:42.779> no<00:28:42.900> BLS<00:28:43.380> in<00:28:43.559> the<00:28:43.740> core 00:28:44.570 --> 00:28:44.580 align:start position:0% there's no BLS in the core 00:28:44.580 --> 00:28:46.610 align:start position:0% there's no BLS in the core what<00:28:45.120> there<00:28:45.240> is<00:28:45.419> in<00:28:45.539> the<00:28:45.659> core<00:28:45.779> for<00:28:46.020> example<00:28:46.260> is 00:28:46.610 --> 00:28:46.620 align:start position:0% what there is in the core for example is 00:28:46.620 --> 00:28:49.070 align:start position:0% what there is in the core for example is the<00:28:46.980> ability<00:28:47.220> to<00:28:47.400> do<00:28:47.880> signature<00:28:48.600> aggregation 00:28:49.070 --> 00:28:49.080 align:start position:0% the ability to do signature aggregation 00:28:49.080 --> 00:28:50.029 align:start position:0% the ability to do signature aggregation that 00:28:50.029 --> 00:28:50.039 align:start position:0% that 00:28:50.039 --> 00:28:51.590 align:start position:0% that you<00:28:50.400> check<00:28:50.580> the<00:28:50.700> aggregation<00:28:51.120> in<00:28:51.299> one<00:28:51.480> place 00:28:51.590 --> 00:28:51.600 align:start position:0% you check the aggregation in one place 00:28:51.600 --> 00:28:53.210 align:start position:0% you check the aggregation in one place for<00:28:51.840> entire<00:28:52.260> batch 00:28:53.210 --> 00:28:53.220 align:start position:0% for entire batch 00:28:53.220 --> 00:28:54.890 align:start position:0% for entire batch this<00:28:53.640> is<00:28:53.700> in<00:28:53.880> the<00:28:54.059> core 00:28:54.890 --> 00:28:54.900 align:start position:0% this is in the core 00:28:54.900 --> 00:28:57.649 align:start position:0% this is in the core BLS<00:28:55.559> is<00:28:55.740> merely<00:28:56.100> an<00:28:56.220> implementation<00:28:56.640> of<00:28:56.760> that 00:28:57.649 --> 00:28:57.659 align:start position:0% BLS is merely an implementation of that 00:28:57.659 --> 00:28:59.450 align:start position:0% BLS is merely an implementation of that we<00:28:58.140> narrowed<00:28:58.559> several<00:28:58.799> interface<00:28:59.100> you<00:28:59.279> add 00:28:59.450 --> 00:28:59.460 align:start position:0% we narrowed several interface you add 00:28:59.460 --> 00:29:01.850 align:start position:0% we narrowed several interface you add another<00:28:59.640> contract<00:29:00.059> to<00:29:00.240> perform<00:29:00.360> it<00:29:00.659> but<00:29:01.380> it's 00:29:01.850 --> 00:29:01.860 align:start position:0% another contract to perform it but it's 00:29:01.860 --> 00:29:03.289 align:start position:0% another contract to perform it but it's separate<00:29:02.159> from<00:29:02.340> the<00:29:02.520> core 00:29:03.289 --> 00:29:03.299 align:start position:0% separate from the core 00:29:03.299 --> 00:29:06.190 align:start position:0% separate from the core so<00:29:03.900> it<00:29:04.140> is<00:29:04.260> modular<00:29:04.620> all<00:29:05.279> the<00:29:05.460> features<00:29:05.760> like 00:29:06.190 --> 00:29:06.200 align:start position:0% so it is modular all the features like 00:29:06.200 --> 00:29:08.630 align:start position:0% so it is modular all the features like specific<00:29:07.200> feature<00:29:07.559> of<00:29:07.679> wallets<00:29:08.039> you 00:29:08.630 --> 00:29:08.640 align:start position:0% specific feature of wallets you 00:29:08.640 --> 00:29:10.310 align:start position:0% specific feature of wallets you suggested<00:29:09.059> some<00:29:09.240> callback<00:29:09.539> that<00:29:09.960> exists 00:29:10.310 --> 00:29:10.320 align:start position:0% suggested some callback that exists 00:29:10.320 --> 00:29:12.289 align:start position:0% suggested some callback that exists today<00:29:10.440> and<00:29:10.919> maybe<00:29:11.279> a<00:29:11.580> callback<00:29:12.000> that<00:29:12.179> will 00:29:12.289 --> 00:29:12.299 align:start position:0% today and maybe a callback that will 00:29:12.299 --> 00:29:14.870 align:start position:0% today and maybe a callback that will exist<00:29:12.600> in<00:29:13.020> the<00:29:13.140> future<00:29:13.260> the<00:29:14.159> wallets<00:29:14.520> will 00:29:14.870 --> 00:29:14.880 align:start position:0% exist in the future the wallets will 00:29:14.880 --> 00:29:16.669 align:start position:0% exist in the future the wallets will have<00:29:15.059> to<00:29:15.179> implement<00:29:15.419> them<00:29:15.659> right<00:29:16.200> now<00:29:16.380> your 00:29:16.669 --> 00:29:16.679 align:start position:0% have to implement them right now your 00:29:16.679 --> 00:29:20.269 align:start position:0% have to implement them right now your eoa<00:29:17.159> doesn't<00:29:17.460> support<00:29:17.700> them<00:29:17.940> anyway 00:29:20.269 --> 00:29:20.279 align:start position:0% eoa doesn't support them anyway 00:29:20.279 --> 00:29:23.210 align:start position:0% eoa doesn't support them anyway the<00:29:20.760> idea<00:29:21.000> is<00:29:21.179> that<00:29:21.360> when<00:29:21.539> you<00:29:21.659> deploy<00:29:22.020> a<00:29:22.860> an 00:29:23.210 --> 00:29:23.220 align:start position:0% the idea is that when you deploy a an 00:29:23.220 --> 00:29:25.370 align:start position:0% the idea is that when you deploy a an accountability<00:29:23.760> contract 00:29:25.370 --> 00:29:25.380 align:start position:0% accountability contract 00:29:25.380 --> 00:29:27.529 align:start position:0% accountability contract I'm<00:29:25.980> not<00:29:26.220> think<00:29:26.399> it's<00:29:26.520> even<00:29:26.700> written<00:29:27.120> in<00:29:27.360> the 00:29:27.529 --> 00:29:27.539 align:start position:0% I'm not think it's even written in the 00:29:27.539 --> 00:29:29.570 align:start position:0% I'm not think it's even written in the spec<00:29:27.840> but<00:29:28.140> we<00:29:28.679> expect<00:29:28.799> it<00:29:29.100> to<00:29:29.220> be<00:29:29.340> an 00:29:29.570 --> 00:29:29.580 align:start position:0% spec but we expect it to be an 00:29:29.580 --> 00:29:31.730 align:start position:0% spec but we expect it to be an upgradable<00:29:30.120> proxy<00:29:30.659> that<00:29:31.140> the<00:29:31.260> owner<00:29:31.559> can 00:29:31.730 --> 00:29:31.740 align:start position:0% upgradable proxy that the owner can 00:29:31.740 --> 00:29:34.370 align:start position:0% upgradable proxy that the owner can upgrade<00:29:32.100> and<00:29:32.700> if<00:29:32.820> it<00:29:32.940> isn't<00:29:33.240> a<00:29:33.360> creative<00:29:33.720> proxy 00:29:34.370 --> 00:29:34.380 align:start position:0% upgrade and if it isn't a creative proxy 00:29:34.380 --> 00:29:37.010 align:start position:0% upgrade and if it isn't a creative proxy we<00:29:34.980> have<00:29:35.220> a<00:29:35.340> basic<00:29:35.760> implementation<00:29:36.299> and<00:29:36.840> then 00:29:37.010 --> 00:29:37.020 align:start position:0% we have a basic implementation and then 00:29:37.020 --> 00:29:39.230 align:start position:0% we have a basic implementation and then the<00:29:37.200> owner<00:29:37.620> can<00:29:37.799> change<00:29:37.980> it<00:29:38.220> don't<00:29:38.700> don't<00:29:39.000> you 00:29:39.230 --> 00:29:39.240 align:start position:0% the owner can change it don't don't you 00:29:39.240 --> 00:29:41.810 align:start position:0% the owner can change it don't don't you think<00:29:39.419> we're<00:29:39.659> sacrificing<00:29:40.559> security<00:29:40.980> if<00:29:41.460> like 00:29:41.810 --> 00:29:41.820 align:start position:0% think we're sacrificing security if like 00:29:41.820 --> 00:29:44.090 align:start position:0% think we're sacrificing security if like we're<00:29:42.059> going<00:29:42.299> with<00:29:42.539> upgradable 00:29:44.090 --> 00:29:44.100 align:start position:0% we're going with upgradable 00:29:44.100 --> 00:29:46.850 align:start position:0% we're going with upgradable what<00:29:44.760> you<00:29:45.000> do<00:29:45.120> need<00:29:45.299> to<00:29:45.480> do<00:29:45.600> is<00:29:46.320> to<00:29:46.500> make<00:29:46.679> sure 00:29:46.850 --> 00:29:46.860 align:start position:0% what you do need to do is to make sure 00:29:46.860 --> 00:29:49.370 align:start position:0% what you do need to do is to make sure that<00:29:47.100> on<00:29:47.340> your<00:29:47.580> first<00:29:47.760> upgrade<00:29:48.600> you<00:29:49.140> upgrade 00:29:49.370 --> 00:29:49.380 align:start position:0% that on your first upgrade you upgrade 00:29:49.380 --> 00:29:51.289 align:start position:0% that on your first upgrade you upgrade it<00:29:49.559> in<00:29:49.740> a<00:29:49.860> way<00:29:49.980> that<00:29:50.340> now<00:29:50.580> you<00:29:50.820> add<00:29:51.059> security 00:29:51.289 --> 00:29:51.299 align:start position:0% it in a way that now you add security 00:29:51.299 --> 00:29:54.230 align:start position:0% it in a way that now you add security for<00:29:51.899> example<00:29:52.200> after<00:29:52.740> the<00:29:52.980> first<00:29:53.100> upgrade<00:29:53.520> you 00:29:54.230 --> 00:29:54.240 align:start position:0% for example after the first upgrade you 00:29:54.240 --> 00:29:55.909 align:start position:0% for example after the first upgrade you can<00:29:54.360> only 00:29:55.909 --> 00:29:55.919 align:start position:0% can only 00:29:55.919 --> 00:29:57.409 align:start position:0% can only specific<00:29:56.460> mechanism<00:29:56.880> will<00:29:57.059> be<00:29:57.179> able<00:29:57.299> to 00:29:57.409 --> 00:29:57.419 align:start position:0% specific mechanism will be able to 00:29:57.419 --> 00:29:59.570 align:start position:0% specific mechanism will be able to upgrade<00:29:57.899> it 00:29:59.570 --> 00:29:59.580 align:start position:0% upgrade it 00:29:59.580 --> 00:30:02.330 align:start position:0% upgrade it okay<00:30:00.000> account<00:30:00.419> abstraction<00:30:00.899> can<00:30:01.200> be<00:30:01.320> abused 00:30:02.330 --> 00:30:02.340 align:start position:0% okay account abstraction can be abused 00:30:02.340 --> 00:30:04.669 align:start position:0% okay account abstraction can be abused it<00:30:02.760> is<00:30:03.000> I<00:30:03.419> will<00:30:03.600> not<00:30:03.779> prevent<00:30:04.200> you<00:30:04.380> from 00:30:04.669 --> 00:30:04.679 align:start position:0% it is I will not prevent you from 00:30:04.679 --> 00:30:07.490 align:start position:0% it is I will not prevent you from creating<00:30:05.039> an<00:30:05.520> insecure<00:30:06.059> wallet<00:30:06.480> I<00:30:07.080> think<00:30:07.200> you 00:30:07.490 --> 00:30:07.500 align:start position:0% creating an insecure wallet I think you 00:30:07.500 --> 00:30:11.289 align:start position:0% creating an insecure wallet I think you can<00:30:07.620> create<00:30:07.860> a<00:30:08.159> secure<00:30:08.460> wallet<00:30:08.820> with<00:30:08.940> it 00:30:11.289 --> 00:30:11.299 align:start position:0% 00:30:11.299 --> 00:30:13.909 align:start position:0% thank<00:30:12.299> you<00:30:12.419> your<00:30:12.960> office<00:30:13.200> your<00:30:13.559> office<00:30:13.740> is 00:30:13.909 --> 00:30:13.919 align:start position:0% thank you your office your office is 00:30:13.919 --> 00:30:17.090 align:start position:0% thank you your office your office is watching<00:30:14.399> us<00:30:14.720> and<00:30:15.720> sending<00:30:16.140> us<00:30:16.260> uh<00:30:16.620> sending<00:30:16.980> us 00:30:17.090 --> 00:30:17.100 align:start position:0% watching us and sending us uh sending us 00:30:17.100 --> 00:30:19.970 align:start position:0% watching us and sending us uh sending us messages<00:30:17.720> trying<00:30:18.720> to<00:30:19.020> participate<00:30:19.440> in<00:30:19.740> the 00:30:19.970 --> 00:30:19.980 align:start position:0% messages trying to participate in the 00:30:19.980 --> 00:30:22.130 align:start position:0% messages trying to participate in the question<00:30:20.279> and<00:30:20.520> answer<00:30:20.640> session<00:30:21.120> you've<00:30:21.960> just 00:30:22.130 --> 00:30:22.140 align:start position:0% question and answer session you've just 00:30:22.140 --> 00:30:24.230 align:start position:0% question and answer session you've just said<00:30:22.320> hey<00:30:22.679> like<00:30:23.100> uh<00:30:23.580> what<00:30:23.760> happens<00:30:23.940> post 00:30:24.230 --> 00:30:24.240 align:start position:0% said hey like uh what happens post 00:30:24.240 --> 00:30:26.149 align:start position:0% said hey like uh what happens post validation<00:30:24.779> is<00:30:25.260> not<00:30:25.440> part<00:30:25.620> of<00:30:25.740> the<00:30:25.860> standard 00:30:26.149 --> 00:30:26.159 align:start position:0% validation is not part of the standard 00:30:26.159 --> 00:30:29.750 align:start position:0% validation is not part of the standard it's<00:30:26.340> not<00:30:26.520> part<00:30:26.700> of<00:30:27.200> erc4337<00:30:28.399> and<00:30:29.399> anything 00:30:29.750 --> 00:30:29.760 align:start position:0% it's not part of erc4337 and anything 00:30:29.760 --> 00:30:31.970 align:start position:0% it's not part of erc4337 and anything anything<00:30:30.659> can<00:30:31.020> happen 00:30:31.970 --> 00:30:31.980 align:start position:0% anything can happen 00:30:31.980 --> 00:30:33.889 align:start position:0% anything can happen um<00:30:32.039> we<00:30:32.279> can<00:30:32.399> talk<00:30:32.580> about<00:30:32.760> ideas<00:30:33.240> on<00:30:33.600> how<00:30:33.779> to 00:30:33.889 --> 00:30:33.899 align:start position:0% um we can talk about ideas on how to 00:30:33.899 --> 00:30:36.049 align:start position:0% um we can talk about ideas on how to make<00:30:33.960> it<00:30:34.140> happen<00:30:34.320> but<00:30:34.860> it's<00:30:35.399> not<00:30:35.580> specifically 00:30:36.049 --> 00:30:36.059 align:start position:0% make it happen but it's not specifically 00:30:36.059 --> 00:30:37.970 align:start position:0% make it happen but it's not specifically related<00:30:36.480> to<00:30:36.899> The<00:30:37.500> Standard<00:30:37.740> that<00:30:37.860> we're 00:30:37.970 --> 00:30:37.980 align:start position:0% related to The Standard that we're 00:30:37.980 --> 00:30:40.730 align:start position:0% related to The Standard that we're working<00:30:38.159> on<00:30:38.340> right<00:30:38.580> now<00:30:38.700> it's<00:30:39.539> kind<00:30:39.779> of<00:30:39.960> uh<00:30:40.380> you 00:30:40.730 --> 00:30:40.740 align:start position:0% working on right now it's kind of uh you 00:30:40.740 --> 00:30:42.769 align:start position:0% working on right now it's kind of uh you know<00:30:40.799> outside<00:30:41.100> of<00:30:41.399> the<00:30:41.520> core<00:30:41.700> because<00:30:42.299> we<00:30:42.600> want 00:30:42.769 --> 00:30:42.779 align:start position:0% know outside of the core because we want 00:30:42.779 --> 00:30:44.930 align:start position:0% know outside of the core because we want to<00:30:42.899> make<00:30:43.020> the<00:30:43.500> core<00:30:43.740> as<00:30:44.159> general<00:30:44.340> purpose<00:30:44.760> as 00:30:44.930 --> 00:30:44.940 align:start position:0% to make the core as general purpose as 00:30:44.940 --> 00:30:46.610 align:start position:0% to make the core as general purpose as possible<00:30:45.240> because<00:30:45.720> maybe<00:30:45.960> we<00:30:46.140> don't<00:30:46.260> have<00:30:46.380> all 00:30:46.610 --> 00:30:46.620 align:start position:0% possible because maybe we don't have all 00:30:46.620 --> 00:30:48.769 align:start position:0% possible because maybe we don't have all the<00:30:46.740> best<00:30:46.860> ideas<00:30:47.100> yet 00:30:48.769 --> 00:30:48.779 align:start position:0% the best ideas yet 00:30:48.779 --> 00:30:51.230 align:start position:0% the best ideas yet by<00:30:49.559> the<00:30:49.679> way<00:30:49.679> if<00:30:49.980> you<00:30:50.039> think<00:30:50.279> there<00:30:50.760> is<00:30:50.940> a 00:30:51.230 --> 00:30:51.240 align:start position:0% by the way if you think there is a 00:30:51.240 --> 00:30:52.669 align:start position:0% by the way if you think there is a security<00:30:51.360> breach<00:30:51.840> and<00:30:51.960> something<00:30:52.140> we<00:30:52.380> can<00:30:52.500> add 00:30:52.669 --> 00:30:52.679 align:start position:0% security breach and something we can add 00:30:52.679 --> 00:30:54.950 align:start position:0% security breach and something we can add to<00:30:53.100> this<00:30:53.279> definition<00:30:53.640> I'll<00:30:54.419> be<00:30:54.539> glad<00:30:54.720> to<00:30:54.840> talk 00:30:54.950 --> 00:30:54.960 align:start position:0% to this definition I'll be glad to talk 00:30:54.960 --> 00:30:56.750 align:start position:0% to this definition I'll be glad to talk and<00:30:55.140> we'll<00:30:55.260> be<00:30:55.380> glad<00:30:55.559> to<00:30:55.679> edit<00:30:55.919> we<00:30:56.640> are 00:30:56.750 --> 00:30:56.760 align:start position:0% and we'll be glad to edit we are 00:30:56.760 --> 00:30:58.370 align:start position:0% and we'll be glad to edit we are overtime<00:30:57.179> however<00:30:57.480> with<00:30:57.779> this<00:30:58.020> is<00:30:58.140> a<00:30:58.320> break 00:30:58.370 --> 00:30:58.380 align:start position:0% overtime however with this is a break 00:30:58.380 --> 00:31:00.049 align:start position:0% overtime however with this is a break time<00:30:58.620> so<00:30:58.919> if<00:30:59.100> you<00:30:59.220> guys<00:30:59.340> have<00:30:59.580> lots<00:31:00.000> of 00:31:00.049 --> 00:31:00.059 align:start position:0% time so if you guys have lots of 00:31:00.059 --> 00:31:02.330 align:start position:0% time so if you guys have lots of questions<00:31:00.360> we're<00:31:01.080> happy<00:31:01.500> to<00:31:01.679> yield<00:31:01.860> them<00:31:02.039> if 00:31:02.330 --> 00:31:02.340 align:start position:0% questions we're happy to yield them if 00:31:02.340 --> 00:31:03.830 align:start position:0% questions we're happy to yield them if you<00:31:02.520> guys<00:31:02.640> are<00:31:02.820> happy<00:31:03.000> to<00:31:03.360> have<00:31:03.600> more 00:31:03.830 --> 00:31:03.840 align:start position:0% you guys are happy to have more 00:31:03.840 --> 00:31:05.350 align:start position:0% you guys are happy to have more questions 00:31:05.350 --> 00:31:05.360 align:start position:0% questions 00:31:05.360 --> 00:31:10.909 align:start position:0% questions anybody<00:31:06.360> else<00:31:06.539> anyone<00:31:06.960> else 00:31:10.909 --> 00:31:10.919 align:start position:0% 00:31:10.919 --> 00:31:13.610 align:start position:0% so<00:31:11.340> how<00:31:11.460> can<00:31:11.640> you<00:31:11.820> make<00:31:12.059> sure<00:31:12.360> that 00:31:13.610 --> 00:31:13.620 align:start position:0% so how can you make sure that 00:31:13.620 --> 00:31:16.250 align:start position:0% so how can you make sure that um<00:31:13.679> you<00:31:13.919> know<00:31:13.980> a<00:31:14.279> wallet<00:31:14.640> a<00:31:15.360> smart<00:31:15.960> contract 00:31:16.250 --> 00:31:16.260 align:start position:0% um you know a wallet a smart contract 00:31:16.260 --> 00:31:20.210 align:start position:0% um you know a wallet a smart contract wallet<00:31:16.820> will<00:31:17.820> be<00:31:18.000> able<00:31:18.240> to<00:31:18.720> prove<00:31:19.559> that<00:31:19.740> is<00:31:19.980> for 00:31:20.210 --> 00:31:20.220 align:start position:0% wallet will be able to prove that is for 00:31:20.220 --> 00:31:21.649 align:start position:0% wallet will be able to prove that is for example<00:31:20.460> only<00:31:20.760> controlled<00:31:21.240> by<00:31:21.360> one 00:31:21.649 --> 00:31:21.659 align:start position:0% example only controlled by one 00:31:21.659 --> 00:31:23.990 align:start position:0% example only controlled by one individual<00:31:22.080> versus<00:31:22.380> multi-six<00:31:23.340> such<00:31:23.700> that 00:31:23.990 --> 00:31:24.000 align:start position:0% individual versus multi-six such that 00:31:24.000 --> 00:31:26.630 align:start position:0% individual versus multi-six such that the<00:31:24.360> receiving<00:31:24.659> contract<00:31:25.440> can<00:31:26.220> make<00:31:26.399> a 00:31:26.630 --> 00:31:26.640 align:start position:0% the receiving contract can make a 00:31:26.640 --> 00:31:28.490 align:start position:0% the receiving contract can make a judgment<00:31:26.940> call<00:31:27.240> on<00:31:27.600> whether<00:31:27.899> it<00:31:28.380> should 00:31:28.490 --> 00:31:28.500 align:start position:0% judgment call on whether it should 00:31:28.500 --> 00:31:31.130 align:start position:0% judgment call on whether it should reject<00:31:28.799> or<00:31:29.100> accept<00:31:29.279> that<00:31:29.640> call<00:31:29.820> right<00:31:30.659> so<00:31:30.960> for 00:31:31.130 --> 00:31:31.140 align:start position:0% reject or accept that call right so for 00:31:31.140 --> 00:31:33.710 align:start position:0% reject or accept that call right so for example<00:31:31.380> if<00:31:31.620> I<00:31:32.100> if<00:31:32.340> I<00:31:32.520> have<00:31:32.700> right<00:31:33.179> so<00:31:33.480> we<00:31:33.659> have 00:31:33.710 --> 00:31:33.720 align:start position:0% example if I if I have right so we have 00:31:33.720 --> 00:31:36.110 align:start position:0% example if I if I have right so we have we<00:31:33.960> have<00:31:34.140> a<00:31:34.200> separation<00:31:34.500> okay<00:31:34.919> the<00:31:35.640> model<00:31:35.820> we 00:31:36.110 --> 00:31:36.120 align:start position:0% we have a separation okay the model we 00:31:36.120 --> 00:31:38.810 align:start position:0% we have a separation okay the model we have<00:31:36.240> is<00:31:36.419> like<00:31:36.600> this<00:31:36.779> a<00:31:37.380> smart<00:31:37.620> contract<00:31:38.039> has<00:31:38.700> a 00:31:38.810 --> 00:31:38.820 align:start position:0% have is like this a smart contract has a 00:31:38.820 --> 00:31:40.669 align:start position:0% have is like this a smart contract has a separation<00:31:39.120> between<00:31:39.360> validation<00:31:39.960> and 00:31:40.669 --> 00:31:40.679 align:start position:0% separation between validation and 00:31:40.679 --> 00:31:41.930 align:start position:0% separation between validation and execution 00:31:41.930 --> 00:31:41.940 align:start position:0% execution 00:31:41.940 --> 00:31:44.990 align:start position:0% execution execution<00:31:43.140> is<00:31:43.799> anything<00:31:44.100> it<00:31:44.340> calls<00:31:44.640> out<00:31:44.760> you 00:31:44.990 --> 00:31:45.000 align:start position:0% execution is anything it calls out you 00:31:45.000 --> 00:31:46.430 align:start position:0% execution is anything it calls out you know<00:31:45.059> you<00:31:45.360> execute<00:31:45.779> external<00:31:46.140> content 00:31:46.430 --> 00:31:46.440 align:start position:0% know you execute external content 00:31:46.440 --> 00:31:48.470 align:start position:0% know you execute external content whether<00:31:46.559> it's<00:31:46.740> atone<00:31:47.039> another<00:31:47.760> validation 00:31:48.470 --> 00:31:48.480 align:start position:0% whether it's atone another validation 00:31:48.480 --> 00:31:50.810 align:start position:0% whether it's atone another validation gets<00:31:49.260> the<00:31:49.380> user<00:31:49.679> operation 00:31:50.810 --> 00:31:50.820 align:start position:0% gets the user operation 00:31:50.820 --> 00:31:53.149 align:start position:0% gets the user operation and<00:31:51.360> validates<00:31:51.720> whatever<00:31:51.960> it<00:31:52.200> likes<00:31:52.500> the 00:31:53.149 --> 00:31:53.159 align:start position:0% and validates whatever it likes the 00:31:53.159 --> 00:31:54.710 align:start position:0% and validates whatever it likes the minimum<00:31:53.460> is<00:31:53.700> validated<00:31:54.179> signature<00:31:54.600> and 00:31:54.710 --> 00:31:54.720 align:start position:0% minimum is validated signature and 00:31:54.720 --> 00:31:55.909 align:start position:0% minimum is validated signature and validate<00:31:55.020> the<00:31:55.140> non<00:31:55.320> so<00:31:55.500> that<00:31:55.620> it's<00:31:55.740> not<00:31:55.860> a 00:31:55.909 --> 00:31:55.919 align:start position:0% validate the non so that it's not a 00:31:55.919 --> 00:31:59.029 align:start position:0% validate the non so that it's not a replay<00:31:56.100> and<00:31:56.460> it's<00:31:56.640> a<00:31:57.059> valid<00:31:57.840> signer<00:31:58.260> but<00:31:58.799> it 00:31:59.029 --> 00:31:59.039 align:start position:0% replay and it's a valid signer but it 00:31:59.039 --> 00:32:01.250 align:start position:0% replay and it's a valid signer but it can<00:31:59.159> do<00:31:59.340> more<00:31:59.520> it<00:32:00.120> can<00:32:00.240> check<00:32:00.480> the<00:32:01.020> actual 00:32:01.250 --> 00:32:01.260 align:start position:0% can do more it can check the actual 00:32:01.260 --> 00:32:06.169 align:start position:0% can do more it can check the actual executed<00:32:02.039> method<00:32:03.059> and<00:32:03.720> say<00:32:04.200> a<00:32:04.740> okay<00:32:05.179> I 00:32:06.169 --> 00:32:06.179 align:start position:0% executed method and say a okay I 00:32:06.179 --> 00:32:08.750 align:start position:0% executed method and say a okay I restrict<00:32:06.600> access<00:32:06.960> to<00:32:07.440> this<00:32:07.740> destination<00:32:08.220> or 00:32:08.750 --> 00:32:08.760 align:start position:0% restrict access to this destination or 00:32:08.760 --> 00:32:11.210 align:start position:0% restrict access to this destination or if<00:32:08.880> it's<00:32:09.000> a<00:32:09.179> complex<00:32:09.419> rule<00:32:09.840> I<00:32:10.320> restrict<00:32:10.799> access 00:32:11.210 --> 00:32:11.220 align:start position:0% if it's a complex rule I restrict access 00:32:11.220 --> 00:32:13.370 align:start position:0% if it's a complex rule I restrict access to<00:32:11.580> this<00:32:11.760> destination<00:32:12.179> for<00:32:12.659> this<00:32:12.899> signer 00:32:13.370 --> 00:32:13.380 align:start position:0% to this destination for this signer 00:32:13.380 --> 00:32:14.930 align:start position:0% to this destination for this signer because<00:32:13.620> I<00:32:13.799> have<00:32:13.919> multiple<00:32:14.220> sign<00:32:14.399> and<00:32:14.700> each 00:32:14.930 --> 00:32:14.940 align:start position:0% because I have multiple sign and each 00:32:14.940 --> 00:32:16.669 align:start position:0% because I have multiple sign and each one<00:32:15.059> has<00:32:15.299> a<00:32:15.480> different<00:32:15.600> role<00:32:15.899> and<00:32:16.020> is<00:32:16.200> allowed 00:32:16.669 --> 00:32:16.679 align:start position:0% one has a different role and is allowed 00:32:16.679 --> 00:32:20.029 align:start position:0% one has a different role and is allowed only<00:32:17.159> specific<00:32:17.640> method<00:32:18.140> the<00:32:19.140> Target<00:32:19.440> contract 00:32:20.029 --> 00:32:20.039 align:start position:0% only specific method the Target contract 00:32:20.039 --> 00:32:22.850 align:start position:0% only specific method the Target contract like<00:32:20.460> a<00:32:20.820> token<00:32:21.120> usdc<00:32:21.659> token<00:32:21.960> usdc<00:32:22.440> token 00:32:22.850 --> 00:32:22.860 align:start position:0% like a token usdc token usdc token 00:32:22.860 --> 00:32:25.070 align:start position:0% like a token usdc token usdc token doesn't<00:32:23.039> receive<00:32:23.520> all<00:32:23.640> this<00:32:23.820> information 00:32:25.070 --> 00:32:25.080 align:start position:0% doesn't receive all this information 00:32:25.080 --> 00:32:27.649 align:start position:0% doesn't receive all this information usdc<00:32:25.919> received<00:32:26.279> transfer<00:32:26.640> from<00:32:27.059> a<00:32:27.240> standard 00:32:27.649 --> 00:32:27.659 align:start position:0% usdc received transfer from a standard 00:32:27.659 --> 00:32:29.149 align:start position:0% usdc received transfer from a standard and<00:32:27.899> it<00:32:28.020> will<00:32:28.140> accept<00:32:28.260> it 00:32:29.149 --> 00:32:29.159 align:start position:0% and it will accept it 00:32:29.159 --> 00:32:30.710 align:start position:0% and it will accept it it<00:32:29.399> is<00:32:29.580> the<00:32:29.700> wallet 00:32:30.710 --> 00:32:30.720 align:start position:0% it is the wallet 00:32:30.720 --> 00:32:33.169 align:start position:0% it is the wallet Logic<00:32:31.380> the<00:32:31.620> logic<00:32:32.039> inside<00:32:32.279> the<00:32:32.520> wallet<00:32:32.820> within 00:32:33.169 --> 00:32:33.179 align:start position:0% Logic the logic inside the wallet within 00:32:33.179 --> 00:32:34.850 align:start position:0% Logic the logic inside the wallet within its<00:32:33.480> validation 00:32:34.850 --> 00:32:34.860 align:start position:0% its validation 00:32:34.860 --> 00:32:37.669 align:start position:0% its validation whether<00:32:35.340> to<00:32:35.580> allow<00:32:36.000> or<00:32:36.659> disallow<00:32:37.320> specific 00:32:37.669 --> 00:32:37.679 align:start position:0% whether to allow or disallow specific 00:32:37.679 --> 00:32:41.630 align:start position:0% whether to allow or disallow specific the<00:32:38.399> operation<00:32:39.240> we<00:32:39.480> are<00:32:39.659> now<00:32:39.779> trying<00:32:40.080> to<00:32:40.260> make 00:32:41.630 --> 00:32:41.640 align:start position:0% the operation we are now trying to make 00:32:41.640 --> 00:32:44.269 align:start position:0% the operation we are now trying to make did<00:32:41.880> I<00:32:42.059> make<00:32:42.179> myself<00:32:42.299> clear<00:32:42.600> I'm<00:32:43.080> not<00:32:43.260> sure<00:32:43.380> yes 00:32:44.269 --> 00:32:44.279 align:start position:0% did I make myself clear I'm not sure yes 00:32:44.279 --> 00:32:47.269 align:start position:0% did I make myself clear I'm not sure yes it<00:32:44.460> is<00:32:44.520> complex<00:32:44.960> yes<00:32:45.960> if<00:32:46.320> you're<00:32:46.620> if<00:32:46.860> you're<00:32:47.039> if 00:32:47.269 --> 00:32:47.279 align:start position:0% it is complex yes if you're if you're if 00:32:47.279 --> 00:32:49.490 align:start position:0% it is complex yes if you're if you're if your<00:32:47.520> target<00:32:47.700> smart<00:32:48.059> contract<00:32:48.539> does<00:32:48.840> not<00:32:49.020> have 00:32:49.490 --> 00:32:49.500 align:start position:0% your target smart contract does not have 00:32:49.500 --> 00:32:51.049 align:start position:0% your target smart contract does not have you<00:32:50.279> know 00:32:51.049 --> 00:32:51.059 align:start position:0% you know 00:32:51.059 --> 00:32:54.049 align:start position:0% you know um<00:32:51.120> additional<00:32:52.080> computational 00:32:54.049 --> 00:32:54.059 align:start position:0% um additional computational 00:32:54.059 --> 00:32:57.230 align:start position:0% um additional computational things<00:32:54.899> going<00:32:55.200> on<00:32:55.380> that<00:32:55.860> that<00:32:56.100> require<00:32:56.520> it<00:32:57.000> to 00:32:57.230 --> 00:32:57.240 align:start position:0% things going on that that require it to 00:32:57.240 --> 00:32:59.450 align:start position:0% things going on that that require it to for<00:32:57.419> example<00:32:57.720> if<00:32:58.080> so<00:32:58.320> take<00:32:58.740> royalties<00:32:59.220> for 00:32:59.450 --> 00:32:59.460 align:start position:0% for example if so take royalties for 00:32:59.460 --> 00:33:03.049 align:start position:0% for example if so take royalties for example<00:32:59.700> right<00:33:00.240> if<00:33:00.779> I<00:33:00.899> if<00:33:01.140> I<00:33:01.380> have<00:33:01.500> if<00:33:01.799> I'm<00:33:02.039> if<00:33:02.340> I 00:33:03.049 --> 00:33:03.059 align:start position:0% example right if I if I have if I'm if I 00:33:03.059 --> 00:33:05.029 align:start position:0% example right if I if I have if I'm if I can<00:33:03.120> I<00:33:03.360> can<00:33:03.539> circumvent<00:33:04.020> royalty<00:33:04.500> payments<00:33:04.860> if 00:33:05.029 --> 00:33:05.039 align:start position:0% can I can circumvent royalty payments if 00:33:05.039 --> 00:33:07.690 align:start position:0% can I can circumvent royalty payments if I<00:33:05.220> transfer<00:33:05.580> an<00:33:05.760> asset<00:33:06.120> from<00:33:06.840> from<00:33:07.200> from<00:33:07.320> from 00:33:07.690 --> 00:33:07.700 align:start position:0% I transfer an asset from from from from 00:33:07.700 --> 00:33:12.230 align:start position:0% I transfer an asset from from from from Alice<00:33:08.700> to<00:33:08.880> Bob<00:33:09.200> right<00:33:10.200> uh<00:33:11.279> um<00:33:11.399> and<00:33:11.760> and<00:33:11.940> right 00:33:12.230 --> 00:33:12.240 align:start position:0% Alice to Bob right uh um and and right 00:33:12.240 --> 00:33:14.450 align:start position:0% Alice to Bob right uh um and and right now<00:33:12.419> if<00:33:12.600> I<00:33:12.779> with<00:33:13.080> an<00:33:13.200> eoa<00:33:13.620> I<00:33:14.039> actually<00:33:14.159> have<00:33:14.340> to 00:33:14.450 --> 00:33:14.460 align:start position:0% now if I with an eoa I actually have to 00:33:14.460 --> 00:33:16.549 align:start position:0% now if I with an eoa I actually have to transfer<00:33:14.820> the<00:33:15.059> the<00:33:15.419> private<00:33:16.019> key<00:33:16.200> to 00:33:16.549 --> 00:33:16.559 align:start position:0% transfer the the private key to 00:33:16.559 --> 00:33:19.190 align:start position:0% transfer the the private key to circumvent<00:33:17.039> the<00:33:17.279> the<00:33:17.640> the<00:33:17.760> uh<00:33:18.600> the<00:33:18.840> royalty 00:33:19.190 --> 00:33:19.200 align:start position:0% circumvent the the the uh the royalty 00:33:19.200 --> 00:33:21.289 align:start position:0% circumvent the the the uh the royalty payment<00:33:19.380> if<00:33:20.100> I<00:33:20.159> allow<00:33:20.460> a<00:33:20.580> smart<00:33:20.760> contract 00:33:21.289 --> 00:33:21.299 align:start position:0% payment if I allow a smart contract 00:33:21.299 --> 00:33:24.049 align:start position:0% payment if I allow a smart contract doing<00:33:21.539> that<00:33:21.840> I<00:33:22.320> can<00:33:22.440> change<00:33:22.740> ownership<00:33:23.279> of 00:33:24.049 --> 00:33:24.059 align:start position:0% doing that I can change ownership of 00:33:24.059 --> 00:33:26.389 align:start position:0% doing that I can change ownership of that<00:33:24.299> of<00:33:24.720> that<00:33:25.019> of<00:33:25.380> that<00:33:25.559> of<00:33:25.799> that<00:33:25.980> no<00:33:26.159> because 00:33:26.389 --> 00:33:26.399 align:start position:0% that of that of that of that no because 00:33:26.399 --> 00:33:29.210 align:start position:0% that of that of that of that no because the<00:33:26.640> owner<00:33:27.120> of<00:33:27.539> the<00:33:27.659> tokens<00:33:28.380> is<00:33:28.799> the<00:33:29.039> Smart 00:33:29.210 --> 00:33:29.220 align:start position:0% the owner of the tokens is the Smart 00:33:29.220 --> 00:33:31.730 align:start position:0% the owner of the tokens is the Smart contract<00:33:29.580> yeah<00:33:30.179> I<00:33:30.419> understand<00:33:30.659> but<00:33:31.380> the<00:33:31.559> point 00:33:31.730 --> 00:33:31.740 align:start position:0% contract yeah I understand but the point 00:33:31.740 --> 00:33:33.950 align:start position:0% contract yeah I understand but the point is<00:33:31.919> if<00:33:32.220> I<00:33:32.460> can<00:33:32.580> transfer<00:33:33.059> the<00:33:33.240> ownership<00:33:33.539> of 00:33:33.950 --> 00:33:33.960 align:start position:0% is if I can transfer the ownership of 00:33:33.960 --> 00:33:36.769 align:start position:0% is if I can transfer the ownership of the<00:33:34.140> wallet<00:33:34.500> address<00:33:34.820> from<00:33:35.820> a<00:33:36.000> to<00:33:36.179> from<00:33:36.480> Alice 00:33:36.769 --> 00:33:36.779 align:start position:0% the wallet address from a to from Alice 00:33:36.779 --> 00:33:39.889 align:start position:0% the wallet address from a to from Alice to<00:33:36.960> to<00:33:37.260> you<00:33:37.559> yeah<00:33:38.399> that's<00:33:39.360> exactly<00:33:39.720> the 00:33:39.889 --> 00:33:39.899 align:start position:0% to to you yeah that's exactly the 00:33:39.899 --> 00:33:42.049 align:start position:0% to to you yeah that's exactly the problem<00:33:40.140> so<00:33:40.740> it's<00:33:40.980> like<00:33:41.100> it's<00:33:41.460> like<00:33:41.580> it's<00:33:41.820> that 00:33:42.049 --> 00:33:42.059 align:start position:0% problem so it's like it's like it's that 00:33:42.059 --> 00:33:44.090 align:start position:0% problem so it's like it's like it's that is<00:33:42.240> exactly<00:33:42.600> the<00:33:42.840> problem<00:33:43.019> if<00:33:43.679> you're<00:33:43.740> in<00:33:43.980> a 00:33:44.090 --> 00:33:44.100 align:start position:0% is exactly the problem if you're in a 00:33:44.100 --> 00:33:47.269 align:start position:0% is exactly the problem if you're in a royalty<00:33:44.460> situation<00:33:44.940> that<00:33:45.600> cannot<00:33:45.960> be<00:33:46.679> so<00:33:46.980> if 00:33:47.269 --> 00:33:47.279 align:start position:0% royalty situation that cannot be so if 00:33:47.279 --> 00:33:48.590 align:start position:0% royalty situation that cannot be so if you<00:33:47.460> want<00:33:47.580> a<00:33:47.700> wallet<00:33:48.000> otherwise<00:33:48.240> just<00:33:48.360> a 00:33:48.590 --> 00:33:48.600 align:start position:0% you want a wallet otherwise just a 00:33:48.600 --> 00:33:50.090 align:start position:0% you want a wallet otherwise just a second<00:33:48.720> otherwise<00:33:49.140> it's<00:33:49.260> your<00:33:49.559> circumventing 00:33:50.090 --> 00:33:50.100 align:start position:0% second otherwise it's your circumventing 00:33:50.100 --> 00:33:51.710 align:start position:0% second otherwise it's your circumventing royalty<00:33:50.460> if<00:33:50.880> you<00:33:51.000> want<00:33:51.179> and<00:33:51.419> while<00:33:51.539> you're 00:33:51.710 --> 00:33:51.720 align:start position:0% royalty if you want and while you're 00:33:51.720 --> 00:33:53.210 align:start position:0% royalty if you want and while you're doing<00:33:51.840> something<00:33:52.019> illegal<00:33:52.500> I'm<00:33:52.799> not<00:33:52.980> saying 00:33:53.210 --> 00:33:53.220 align:start position:0% doing something illegal I'm not saying 00:33:53.220 --> 00:33:55.789 align:start position:0% doing something illegal I'm not saying it<00:33:53.399> is<00:33:53.640> I'm<00:33:54.179> not<00:33:54.299> saying<00:33:54.600> that<00:33:54.840> we<00:33:55.320> support<00:33:55.620> it 00:33:55.789 --> 00:33:55.799 align:start position:0% it is I'm not saying that we support it 00:33:55.799 --> 00:33:57.710 align:start position:0% it is I'm not saying that we support it I'm<00:33:55.980> saying<00:33:56.279> that<00:33:56.340> a<00:33:56.519> contract<00:33:56.880> May<00:33:57.539> support 00:33:57.710 --> 00:33:57.720 align:start position:0% I'm saying that a contract May support 00:33:57.720 --> 00:33:59.990 align:start position:0% I'm saying that a contract May support it<00:33:57.960> for<00:33:58.140> example<00:33:58.380> if<00:33:58.679> you<00:33:58.799> want<00:33:58.980> a<00:33:59.519> soul-bound 00:33:59.990 --> 00:34:00.000 align:start position:0% it for example if you want a soul-bound 00:34:00.000 --> 00:34:02.509 align:start position:0% it for example if you want a soul-bound wallet<00:34:00.419> that<00:34:01.019> you<00:34:01.380> can't<00:34:01.500> transfer<00:34:02.039> the<00:34:02.159> owner 00:34:02.509 --> 00:34:02.519 align:start position:0% wallet that you can't transfer the owner 00:34:02.519 --> 00:34:05.210 align:start position:0% wallet that you can't transfer the owner at<00:34:02.880> all<00:34:03.059> right<00:34:03.779> go<00:34:04.260> ahead<00:34:04.500> create<00:34:04.740> such<00:34:05.039> a 00:34:05.210 --> 00:34:05.220 align:start position:0% at all right go ahead create such a 00:34:05.220 --> 00:34:06.889 align:start position:0% at all right go ahead create such a wallet<00:34:05.519> if<00:34:06.000> you<00:34:06.059> want<00:34:06.240> a<00:34:06.360> wallet<00:34:06.600> that<00:34:06.779> doesn't 00:34:06.889 --> 00:34:06.899 align:start position:0% wallet if you want a wallet that doesn't 00:34:06.899 --> 00:34:09.530 align:start position:0% wallet if you want a wallet that doesn't support<00:34:07.200> set<00:34:08.159> implementation 00:34:09.530 --> 00:34:09.540 align:start position:0% support set implementation 00:34:09.540 --> 00:34:11.810 align:start position:0% support set implementation then<00:34:10.020> create<00:34:10.260> a<00:34:10.500> wallet<00:34:10.740> that<00:34:10.859> will<00:34:11.040> refuse<00:34:11.399> to 00:34:11.810 --> 00:34:11.820 align:start position:0% then create a wallet that will refuse to 00:34:11.820 --> 00:34:13.730 align:start position:0% then create a wallet that will refuse to change<00:34:11.940> implementation<00:34:12.540> once<00:34:12.960> you<00:34:13.020> fixed<00:34:13.379> you 00:34:13.730 --> 00:34:13.740 align:start position:0% change implementation once you fixed you 00:34:13.740 --> 00:34:14.930 align:start position:0% change implementation once you fixed you reach<00:34:14.040> that<00:34:14.159> implementation<00:34:14.580> you<00:34:14.820> don't 00:34:14.930 --> 00:34:14.940 align:start position:0% reach that implementation you don't 00:34:14.940 --> 00:34:17.089 align:start position:0% reach that implementation you don't allow<00:34:15.119> to<00:34:15.300> change<00:34:15.480> you<00:34:16.080> can<00:34:16.200> create<00:34:16.440> such<00:34:16.980> an 00:34:17.089 --> 00:34:17.099 align:start position:0% allow to change you can create such an 00:34:17.099 --> 00:34:19.369 align:start position:0% allow to change you can create such an implementation<00:34:17.639> we<00:34:18.300> don't<00:34:18.480> block<00:34:18.839> such<00:34:19.200> an 00:34:19.369 --> 00:34:19.379 align:start position:0% implementation we don't block such an 00:34:19.379 --> 00:34:21.829 align:start position:0% implementation we don't block such an implementation<00:34:19.859> but<00:34:20.339> we<00:34:20.520> support<00:34:20.639> others 00:34:21.829 --> 00:34:21.839 align:start position:0% implementation but we support others 00:34:21.839 --> 00:34:24.050 align:start position:0% implementation but we support others understood<00:34:22.500> it's<00:34:22.919> just<00:34:23.099> is<00:34:23.280> there<00:34:23.639> is<00:34:23.879> there 00:34:24.050 --> 00:34:24.060 align:start position:0% understood it's just is there is there 00:34:24.060 --> 00:34:26.750 align:start position:0% understood it's just is there is there any<00:34:24.240> standard<00:34:24.780> way<00:34:25.020> to<00:34:25.320> to<00:34:25.619> communicate<00:34:26.220> what 00:34:26.750 --> 00:34:26.760 align:start position:0% any standard way to to communicate what 00:34:26.760 --> 00:34:29.270 align:start position:0% any standard way to to communicate what type<00:34:27.000> of<00:34:27.179> wallet<00:34:27.599> implementation<00:34:28.200> it<00:34:28.619> is<00:34:28.740> such 00:34:29.270 --> 00:34:29.280 align:start position:0% type of wallet implementation it is such 00:34:29.280 --> 00:34:31.669 align:start position:0% type of wallet implementation it is such that<00:34:29.520> the<00:34:29.820> the<00:34:30.060> targeting<00:34:30.540> contract<00:34:31.020> can<00:34:31.379> can 00:34:31.669 --> 00:34:31.679 align:start position:0% that the the targeting contract can can 00:34:31.679 --> 00:34:33.770 align:start position:0% that the the targeting contract can can check<00:34:31.919> whether<00:34:32.159> because<00:34:32.760> you<00:34:33.240> you<00:34:33.419> don't<00:34:33.599> know 00:34:33.770 --> 00:34:33.780 align:start position:0% check whether because you you don't know 00:34:33.780 --> 00:34:35.510 align:start position:0% check whether because you you don't know right<00:34:34.139> it's<00:34:34.440> like<00:34:34.619> it's<00:34:34.919> like<00:34:35.099> it's<00:34:35.399> like 00:34:35.510 --> 00:34:35.520 align:start position:0% right it's like it's like it's like 00:34:35.520 --> 00:34:37.730 align:start position:0% right it's like it's like it's like whether<00:34:35.879> the<00:34:36.359> targeting<00:34:36.780> contract<00:34:37.139> needs<00:34:37.619> to 00:34:37.730 --> 00:34:37.740 align:start position:0% whether the targeting contract needs to 00:34:37.740 --> 00:34:40.210 align:start position:0% whether the targeting contract needs to know<00:34:37.919> the<00:34:38.280> context<00:34:38.760> of<00:34:39.599> the<00:34:39.780> wall 00:34:40.210 --> 00:34:40.220 align:start position:0% know the context of the wall 00:34:40.220 --> 00:34:42.409 align:start position:0% know the context of the wall implementation<00:34:41.220> to<00:34:41.520> make<00:34:41.700> a<00:34:41.879> judgment<00:34:42.119> call 00:34:42.409 --> 00:34:42.419 align:start position:0% implementation to make a judgment call 00:34:42.419 --> 00:34:44.930 align:start position:0% implementation to make a judgment call about<00:34:42.659> the<00:34:42.960> owner<00:34:43.260> okay<00:34:43.619> first<00:34:43.980> of<00:34:44.099> all<00:34:44.220> target 00:34:44.930 --> 00:34:44.940 align:start position:0% about the owner okay first of all target 00:34:44.940 --> 00:34:46.550 align:start position:0% about the owner okay first of all target contracts 00:34:46.550 --> 00:34:46.560 align:start position:0% contracts 00:34:46.560 --> 00:34:48.889 align:start position:0% contracts out<00:34:47.159> there<00:34:47.339> in<00:34:47.520> the<00:34:47.639> wild<00:34:47.760> don't<00:34:48.599> know 00:34:48.889 --> 00:34:48.899 align:start position:0% out there in the wild don't know 00:34:48.899 --> 00:34:50.930 align:start position:0% out there in the wild don't know anything<00:34:49.260> about<00:34:49.679> the<00:34:49.919> collar<00:34:50.220> except<00:34:50.580> that<00:34:50.820> it 00:34:50.930 --> 00:34:50.940 align:start position:0% anything about the collar except that it 00:34:50.940 --> 00:34:52.730 align:start position:0% anything about the collar except that it is<00:34:51.060> a<00:34:51.179> message<00:34:51.300> center<00:34:51.599> they<00:34:52.260> can<00:34:52.379> check<00:34:52.560> the 00:34:52.730 --> 00:34:52.740 align:start position:0% is a message center they can check the 00:34:52.740 --> 00:34:54.589 align:start position:0% is a message center they can check the code<00:34:52.919> if<00:34:53.099> they<00:34:53.280> like<00:34:53.399> but<00:34:53.760> you<00:34:54.300> are<00:34:54.480> talking 00:34:54.589 --> 00:34:54.599 align:start position:0% code if they like but you are talking 00:34:54.599 --> 00:34:56.030 align:start position:0% code if they like but you are talking about<00:34:54.780> the<00:34:54.960> use<00:34:55.139> cases<00:34:55.379> that<00:34:55.619> don't<00:34:55.740> exist 00:34:56.030 --> 00:34:56.040 align:start position:0% about the use cases that don't exist 00:34:56.040 --> 00:34:59.829 align:start position:0% about the use cases that don't exist with<00:34:56.339> EOS<00:34:56.760> so<00:34:57.420> they<00:34:57.960> really<00:34:58.200> knew<00:34:59.040> also<00:34:59.280> for<00:34:59.520> us 00:34:59.829 --> 00:34:59.839 align:start position:0% with EOS so they really knew also for us 00:34:59.839 --> 00:35:02.930 align:start position:0% with EOS so they really knew also for us smart<00:35:00.839> contract<00:35:01.200> calls<00:35:01.619> for<00:35:02.220> any<00:35:02.460> operation 00:35:02.930 --> 00:35:02.940 align:start position:0% smart contract calls for any operation 00:35:02.940 --> 00:35:04.130 align:start position:0% smart contract calls for any operation you're<00:35:03.180> talking<00:35:03.420> about 00:35:04.130 --> 00:35:04.140 align:start position:0% you're talking about 00:35:04.140 --> 00:35:05.450 align:start position:0% you're talking about the<00:35:04.560> other<00:35:04.619> thing<00:35:04.800> you<00:35:05.099> talk<00:35:05.339> about 00:35:05.450 --> 00:35:05.460 align:start position:0% the other thing you talk about 00:35:05.460 --> 00:35:07.430 align:start position:0% the other thing you talk about standardization<00:35:06.060> how<00:35:06.540> to<00:35:06.660> know 00:35:07.430 --> 00:35:07.440 align:start position:0% standardization how to know 00:35:07.440 --> 00:35:10.190 align:start position:0% standardization how to know uh<00:35:08.220> yes<00:35:08.400> it<00:35:08.580> is<00:35:08.700> required<00:35:09.060> we<00:35:09.599> are<00:35:09.780> providing 00:35:10.190 --> 00:35:10.200 align:start position:0% uh yes it is required we are providing 00:35:10.200 --> 00:35:11.569 align:start position:0% uh yes it is required we are providing right<00:35:10.380> now<00:35:10.500> the<00:35:10.740> infrastructure<00:35:11.220> for<00:35:11.400> account 00:35:11.569 --> 00:35:11.579 align:start position:0% right now the infrastructure for account 00:35:11.579 --> 00:35:13.010 align:start position:0% right now the infrastructure for account obstructions<00:35:12.119> for<00:35:12.300> wallets<00:35:12.599> to<00:35:12.720> be<00:35:12.839> built 00:35:13.010 --> 00:35:13.020 align:start position:0% obstructions for wallets to be built 00:35:13.020 --> 00:35:15.349 align:start position:0% obstructions for wallets to be built about<00:35:13.140> on<00:35:13.859> top<00:35:13.980> of<00:35:14.099> it<00:35:14.359> standardization 00:35:15.349 --> 00:35:15.359 align:start position:0% about on top of it standardization 00:35:15.359 --> 00:35:17.630 align:start position:0% about on top of it standardization between<00:35:15.839> the<00:35:16.320> account<00:35:16.560> contracts<00:35:17.280> and<00:35:17.520> for 00:35:17.630 --> 00:35:17.640 align:start position:0% between the account contracts and for 00:35:17.640 --> 00:35:19.310 align:start position:0% between the account contracts and for example<00:35:17.880> the<00:35:18.180> wallet<00:35:18.480> application<00:35:18.900> that<00:35:19.140> use 00:35:19.310 --> 00:35:19.320 align:start position:0% example the wallet application that use 00:35:19.320 --> 00:35:20.270 align:start position:0% example the wallet application that use them 00:35:20.270 --> 00:35:20.280 align:start position:0% them 00:35:20.280 --> 00:35:23.510 align:start position:0% them something<00:35:20.940> that<00:35:21.500> the<00:35:22.500> the<00:35:22.560> ecosystem<00:35:23.220> will 00:35:23.510 --> 00:35:23.520 align:start position:0% something that the the ecosystem will 00:35:23.520 --> 00:35:25.490 align:start position:0% something that the the ecosystem will benefit<00:35:23.700> but<00:35:24.359> it<00:35:24.599> doesn't<00:35:24.720> exist<00:35:25.020> yet<00:35:25.200> because 00:35:25.490 --> 00:35:25.500 align:start position:0% benefit but it doesn't exist yet because 00:35:25.500 --> 00:35:27.890 align:start position:0% benefit but it doesn't exist yet because neither<00:35:26.099> the<00:35:26.280> wallet<00:35:26.579> nor<00:35:26.940> the<00:35:27.300> nor<00:35:27.660> the 00:35:27.890 --> 00:35:27.900 align:start position:0% neither the wallet nor the nor the 00:35:27.900 --> 00:35:30.170 align:start position:0% neither the wallet nor the nor the contracts<00:35:28.380> exist<00:35:28.740> today<00:35:28.920> so<00:35:29.579> usually<00:35:29.880> it<00:35:30.060> will 00:35:30.170 --> 00:35:30.180 align:start position:0% contracts exist today so usually it will 00:35:30.180 --> 00:35:33.230 align:start position:0% contracts exist today so usually it will be<00:35:30.359> a<00:35:30.540> siled<00:35:30.960> like<00:35:31.440> a<00:35:32.040> given<00:35:32.339> application<00:35:32.760> with 00:35:33.230 --> 00:35:33.240 align:start position:0% be a siled like a given application with 00:35:33.240 --> 00:35:36.050 align:start position:0% be a siled like a given application with a<00:35:33.420> given<00:35:33.720> a<00:35:33.960> a<00:35:34.619> given<00:35:34.980> wallet<00:35:35.339> contract<00:35:35.640> with<00:35:35.820> a 00:35:36.050 --> 00:35:36.060 align:start position:0% a given a a given wallet contract with a 00:35:36.060 --> 00:35:40.490 align:start position:0% a given a a given wallet contract with a given<00:35:36.720> a<00:35:36.920> UI<00:35:37.920> ux<00:35:38.280> for<00:35:38.520> it<00:35:38.640> but<00:35:39.180> we<00:35:39.359> won't<00:35:40.020> we 00:35:40.490 --> 00:35:40.500 align:start position:0% given a UI ux for it but we won't we 00:35:40.500 --> 00:35:42.470 align:start position:0% given a UI ux for it but we won't we will<00:35:41.099> try<00:35:41.339> to<00:35:41.520> push<00:35:41.700> and<00:35:41.880> try<00:35:42.300> to<00:35:42.359> find 00:35:42.470 --> 00:35:42.480 align:start position:0% will try to push and try to find 00:35:42.480 --> 00:35:45.190 align:start position:0% will try to push and try to find Innovations<00:35:42.980> from<00:35:43.980> the<00:35:44.280> from<00:35:44.760> the<00:35:44.940> community 00:35:45.190 --> 00:35:45.200 align:start position:0% Innovations from the from the community 00:35:45.200 --> 00:35:48.130 align:start position:0% Innovations from the from the community to<00:35:46.200> support<00:35:46.380> such<00:35:46.740> integration<00:35:47.339> in<00:35:47.700> such<00:35:47.940> a 00:35:48.130 --> 00:35:48.140 align:start position:0% to support such integration in such a 00:35:48.140 --> 00:35:51.290 align:start position:0% to support such integration in such a apis<00:35:49.140> your<00:35:49.680> scenarios<00:35:50.160> are<00:35:50.339> interesting<00:35:50.820> but 00:35:51.290 --> 00:35:51.300 align:start position:0% apis your scenarios are interesting but 00:35:51.300 --> 00:35:52.910 align:start position:0% apis your scenarios are interesting but I<00:35:51.540> don't<00:35:51.660> think<00:35:51.720> they<00:35:51.839> exist<00:35:52.200> at<00:35:52.380> all<00:35:52.560> in<00:35:52.800> the 00:35:52.910 --> 00:35:52.920 align:start position:0% I don't think they exist at all in the 00:35:52.920 --> 00:35:55.790 align:start position:0% I don't think they exist at all in the ethereum<00:35:53.280> ecosystem<00:35:54.079> the<00:35:55.079> short<00:35:55.260> answer<00:35:55.500> is 00:35:55.790 --> 00:35:55.800 align:start position:0% ethereum ecosystem the short answer is 00:35:55.800 --> 00:35:58.010 align:start position:0% ethereum ecosystem the short answer is an<00:35:56.040> nft<00:35:56.339> can<00:35:56.700> just<00:35:56.820> check<00:35:57.000> the<00:35:57.180> code<00:35:57.420> of<00:35:57.900> the 00:35:58.010 --> 00:35:58.020 align:start position:0% an nft can just check the code of the 00:35:58.020 --> 00:36:00.890 align:start position:0% an nft can just check the code of the color<00:35:58.200> and<00:35:59.099> if<00:35:59.280> they<00:35:59.400> want<00:35:59.579> to<00:35:59.700> restrict<00:36:00.119> uh 00:36:00.890 --> 00:36:00.900 align:start position:0% color and if they want to restrict uh 00:36:00.900 --> 00:36:02.750 align:start position:0% color and if they want to restrict uh you<00:36:01.260> know<00:36:01.320> themselves<00:36:01.859> the<00:36:02.220> Primitive 00:36:02.750 --> 00:36:02.760 align:start position:0% you know themselves the Primitive 00:36:02.760 --> 00:36:05.030 align:start position:0% you know themselves the Primitive wallets<00:36:03.119> they<00:36:03.420> can<00:36:03.540> certainly<00:36:03.780> do<00:36:03.960> that 00:36:05.030 --> 00:36:05.040 align:start position:0% wallets they can certainly do that 00:36:05.040 --> 00:36:06.950 align:start position:0% wallets they can certainly do that it<00:36:05.579> was<00:36:05.700> it<00:36:05.880> will<00:36:06.060> this<00:36:06.420> all<00:36:06.599> of<00:36:06.720> this<00:36:06.839> will 00:36:06.950 --> 00:36:06.960 align:start position:0% it was it will this all of this will 00:36:06.960 --> 00:36:10.849 align:start position:0% it was it will this all of this will happen<00:36:07.140> in<00:36:07.380> a<00:36:07.560> layer<00:36:07.800> above<00:36:08.160> what<00:36:08.520> we're<00:36:08.640> doing 00:36:10.849 --> 00:36:10.859 align:start position:0% 00:36:10.859 --> 00:36:12.410 align:start position:0% did<00:36:11.160> you<00:36:11.339> all<00:36:11.460> have<00:36:11.579> had<00:36:11.700> some<00:36:11.820> questions<00:36:12.060> that 00:36:12.410 --> 00:36:12.420 align:start position:0% did you all have had some questions that 00:36:12.420 --> 00:36:14.450 align:start position:0% did you all have had some questions that he<00:36:12.599> wanted 00:36:14.450 --> 00:36:14.460 align:start position:0% he wanted 00:36:14.460 --> 00:36:16.849 align:start position:0% he wanted you wanted<00:36:15.000> to<00:36:15.240> present<00:36:15.839> it<00:36:15.960> I'm<00:36:16.320> a<00:36:16.440> proxy<00:36:16.680> for 00:36:16.849 --> 00:36:16.859 align:start position:0% you wanted to present it I'm a proxy for 00:36:16.859 --> 00:36:18.290 align:start position:0% you wanted to present it I'm a proxy for you<00:36:16.920> right<00:36:17.220> now<00:36:17.339> are<00:36:17.520> you<00:36:17.640> guys<00:36:17.700> okay<00:36:17.880> for<00:36:18.180> a 00:36:18.290 --> 00:36:18.300 align:start position:0% you right now are you guys okay for a 00:36:18.300 --> 00:36:24.470 align:start position:0% you right now are you guys okay for a couple<00:36:18.420> more<00:36:18.660> or<00:36:19.200> okay 00:36:24.470 --> 00:36:24.480 align:start position:0% 00:36:24.480 --> 00:36:26.030 align:start position:0% oh<00:36:24.660> hi<00:36:24.839> uh<00:36:25.079> thanks<00:36:25.200> for<00:36:25.380> the<00:36:25.500> talk<00:36:25.619> I<00:36:25.859> believe 00:36:26.030 --> 00:36:26.040 align:start position:0% oh hi uh thanks for the talk I believe 00:36:26.040 --> 00:36:29.150 align:start position:0% oh hi uh thanks for the talk I believe you're<00:36:26.220> also<00:36:26.460> an<00:36:26.579> author<00:36:26.760> of<00:36:26.880> eip2771 00:36:29.150 --> 00:36:29.160 align:start position:0% you're also an author of eip2771 00:36:29.160 --> 00:36:31.910 align:start position:0% you're also an author of eip2771 uh<00:36:30.000> is<00:36:30.240> that<00:36:30.420> right 00:36:31.910 --> 00:36:31.920 align:start position:0% uh is that right 00:36:31.920 --> 00:36:35.569 align:start position:0% uh is that right uh<00:36:32.700> yes<00:36:33.000> okay<00:36:33.660> this<00:36:34.020> is<00:36:34.140> basically<00:36:34.680> self<00:36:34.980> a 00:36:35.569 --> 00:36:35.579 align:start position:0% uh yes okay this is basically self a 00:36:35.579 --> 00:36:38.630 align:start position:0% uh yes okay this is basically self a meta<00:36:36.240> transactions<00:36:36.780> and<00:36:37.079> with<00:36:37.440> open<00:36:37.619> GSN<00:36:38.160> yes 00:36:38.630 --> 00:36:38.640 align:start position:0% meta transactions and with open GSN yes 00:36:38.640 --> 00:36:42.349 align:start position:0% meta transactions and with open GSN yes so<00:36:39.380> yeah<00:36:40.380> I<00:36:40.619> was<00:36:40.680> just<00:36:40.740> curious<00:36:41.099> uh<00:36:41.640> what<00:36:42.240> you 00:36:42.349 --> 00:36:42.359 align:start position:0% so yeah I was just curious uh what you 00:36:42.359 --> 00:36:45.170 align:start position:0% so yeah I was just curious uh what you see<00:36:42.660> the<00:36:42.780> role<00:36:43.079> the<00:36:43.260> role<00:36:43.740> of<00:36:43.880> eip2771<00:36:44.880> having 00:36:45.170 --> 00:36:45.180 align:start position:0% see the role the role of eip2771 having 00:36:45.180 --> 00:36:47.390 align:start position:0% see the role the role of eip2771 having in<00:36:45.480> an<00:36:45.599> account<00:36:45.720> abstraction<00:36:46.200> world<00:36:46.440> and<00:36:47.160> also 00:36:47.390 --> 00:36:47.400 align:start position:0% in an account abstraction world and also 00:36:47.400 --> 00:36:49.490 align:start position:0% in an account abstraction world and also for<00:36:47.520> those<00:36:47.700> who<00:36:47.820> don't<00:36:48.000> know<00:36:48.660> it<00:36:48.839> uh<00:36:49.320> just 00:36:49.490 --> 00:36:49.500 align:start position:0% for those who don't know it uh just 00:36:49.500 --> 00:36:52.250 align:start position:0% for those who don't know it uh just explain<00:36:49.560> it<00:36:49.800> a<00:36:49.920> little<00:36:50.040> yeah<00:36:50.400> it<00:36:51.119> doesn't<00:36:51.720> it 00:36:52.250 --> 00:36:52.260 align:start position:0% explain it a little yeah it doesn't it 00:36:52.260 --> 00:36:53.329 align:start position:0% explain it a little yeah it doesn't it doesn't 00:36:53.329 --> 00:36:53.339 align:start position:0% doesn't 00:36:53.339 --> 00:36:55.670 align:start position:0% doesn't just<00:36:54.300> not<00:36:54.540> needed<00:36:54.900> because<00:36:55.079> I<00:36:55.320> don't<00:36:55.440> need<00:36:55.560> it 00:36:55.670 --> 00:36:55.680 align:start position:0% just not needed because I don't need it 00:36:55.680 --> 00:36:58.190 align:start position:0% just not needed because I don't need it anymore<00:36:55.740> open<00:36:56.160> GSN<00:36:56.700> tried<00:36:57.000> to<00:36:57.180> do<00:36:57.420> a<00:36:58.020> gas 00:36:58.190 --> 00:36:58.200 align:start position:0% anymore open GSN tried to do a gas 00:36:58.200 --> 00:37:01.069 align:start position:0% anymore open GSN tried to do a gas abstraction<00:36:58.740> which<00:36:59.339> we<00:37:00.000> later<00:37:00.540> implemented 00:37:01.069 --> 00:37:01.079 align:start position:0% abstraction which we later implemented 00:37:01.079 --> 00:37:03.589 align:start position:0% abstraction which we later implemented into<00:37:01.260> account<00:37:01.500> abstraction<00:37:02.119> for<00:37:03.119> existing 00:37:03.589 --> 00:37:03.599 align:start position:0% into account abstraction for existing 00:37:03.599 --> 00:37:05.210 align:start position:0% into account abstraction for existing eoa<00:37:04.140> accounts 00:37:05.210 --> 00:37:05.220 align:start position:0% eoa accounts 00:37:05.220 --> 00:37:07.970 align:start position:0% eoa accounts and<00:37:05.940> the<00:37:06.359> requirement<00:37:06.720> of<00:37:07.140> the<00:37:07.500> gas<00:37:07.740> station 00:37:07.970 --> 00:37:07.980 align:start position:0% and the requirement of the gas station 00:37:07.980 --> 00:37:09.710 align:start position:0% and the requirement of the gas station network<00:37:08.400> and<00:37:08.820> network<00:37:09.060> of<00:37:09.300> three<00:37:09.420> layers 00:37:09.710 --> 00:37:09.720 align:start position:0% network and network of three layers 00:37:09.720 --> 00:37:11.990 align:start position:0% network and network of three layers which<00:37:10.200> are<00:37:10.680> the<00:37:10.920> actually<00:37:11.160> standards<00:37:11.940> of 00:37:11.990 --> 00:37:12.000 align:start position:0% which are the actually standards of 00:37:12.000 --> 00:37:13.849 align:start position:0% which are the actually standards of transactions<00:37:12.540> meant<00:37:13.320> that<00:37:13.440> the<00:37:13.680> Target 00:37:13.849 --> 00:37:13.859 align:start position:0% transactions meant that the Target 00:37:13.859 --> 00:37:16.370 align:start position:0% transactions meant that the Target contract<00:37:14.400> being<00:37:14.820> token<00:37:15.359> or<00:37:15.540> other<00:37:15.720> couldn't 00:37:16.370 --> 00:37:16.380 align:start position:0% contract being token or other couldn't 00:37:16.380 --> 00:37:19.130 align:start position:0% contract being token or other couldn't tell<00:37:16.680> the<00:37:16.859> real<00:37:17.040> sender<00:37:17.520> so<00:37:18.240> we<00:37:18.480> they<00:37:18.780> had<00:37:18.960> to 00:37:19.130 --> 00:37:19.140 align:start position:0% tell the real sender so we they had to 00:37:19.140 --> 00:37:21.670 align:start position:0% tell the real sender so we they had to be<00:37:19.260> modified<00:37:19.640> support 00:37:21.670 --> 00:37:21.680 align:start position:0% be modified support 00:37:21.680 --> 00:37:24.109 align:start position:0% be modified support eip2771<00:37:22.680> at<00:37:23.040> the<00:37:23.220> method<00:37:23.460> so<00:37:23.700> that<00:37:23.820> it<00:37:24.000> can 00:37:24.109 --> 00:37:24.119 align:start position:0% eip2771 at the method so that it can 00:37:24.119 --> 00:37:26.030 align:start position:0% eip2771 at the method so that it can tell<00:37:24.180> the<00:37:24.359> real<00:37:24.420> sender<00:37:25.320> which<00:37:25.619> is<00:37:25.740> a<00:37:25.920> pain 00:37:26.030 --> 00:37:26.040 align:start position:0% tell the real sender which is a pain 00:37:26.040 --> 00:37:27.710 align:start position:0% tell the real sender which is a pain it's<00:37:26.640> it 00:37:27.710 --> 00:37:27.720 align:start position:0% it's it 00:37:27.720 --> 00:37:29.750 align:start position:0% it's it because 00:37:29.750 --> 00:37:29.760 align:start position:0% because 00:37:29.760 --> 00:37:32.030 align:start position:0% because adaptation<00:37:30.480> of<00:37:30.720> this<00:37:30.900> requires<00:37:31.680> the<00:37:31.859> Target 00:37:32.030 --> 00:37:32.040 align:start position:0% adaptation of this requires the Target 00:37:32.040 --> 00:37:34.130 align:start position:0% adaptation of this requires the Target contract<00:37:32.520> to<00:37:32.700> be<00:37:33.060> changed<00:37:33.420> doesn't<00:37:33.839> support 00:37:34.130 --> 00:37:34.140 align:start position:0% contract to be changed doesn't support 00:37:34.140 --> 00:37:36.589 align:start position:0% contract to be changed doesn't support existing<00:37:34.740> tokens<00:37:35.400> for<00:37:35.579> example<00:37:35.820> if<00:37:36.359> you<00:37:36.480> want 00:37:36.589 --> 00:37:36.599 align:start position:0% existing tokens for example if you want 00:37:36.599 --> 00:37:38.569 align:start position:0% existing tokens for example if you want your<00:37:36.839> token<00:37:37.200> to<00:37:37.320> be<00:37:37.500> meta<00:37:38.339> transaction 00:37:38.569 --> 00:37:38.579 align:start position:0% your token to be meta transaction 00:37:38.579 --> 00:37:41.089 align:start position:0% your token to be meta transaction enabled<00:37:39.060> you<00:37:39.180> have<00:37:39.300> to<00:37:39.420> rewrite<00:37:39.839> it<00:37:40.020> so<00:37:40.680> yes<00:37:40.859> it 00:37:41.089 --> 00:37:41.099 align:start position:0% enabled you have to rewrite it so yes it 00:37:41.099 --> 00:37:42.550 align:start position:0% enabled you have to rewrite it so yes it was<00:37:41.280> problematic 00:37:42.550 --> 00:37:42.560 align:start position:0% was problematic 00:37:42.560 --> 00:37:46.609 align:start position:0% was problematic it<00:37:43.560> was<00:37:43.680> good<00:37:43.920> for<00:37:44.720> dapps<00:37:45.720> to<00:37:45.960> add<00:37:46.140> support<00:37:46.380> for 00:37:46.609 --> 00:37:46.619 align:start position:0% it was good for dapps to add support for 00:37:46.619 --> 00:37:49.190 align:start position:0% it was good for dapps to add support for existing<00:37:46.980> users<00:37:47.400> to<00:37:48.180> sponsor<00:37:48.660> the<00:37:48.839> gas 00:37:49.190 --> 00:37:49.200 align:start position:0% existing users to sponsor the gas 00:37:49.200 --> 00:37:52.670 align:start position:0% existing users to sponsor the gas account<00:37:49.740> obstruction<00:37:50.220> they<00:37:51.119> has<00:37:51.900> a<00:37:52.200> Much 00:37:52.670 --> 00:37:52.680 align:start position:0% account obstruction they has a Much 00:37:52.680 --> 00:37:55.609 align:start position:0% account obstruction they has a Much Higher<00:37:53.339> Goals<00:37:53.700> to<00:37:54.240> replace<00:37:54.359> the<00:37:54.720> accounts 00:37:55.609 --> 00:37:55.619 align:start position:0% Higher Goals to replace the accounts 00:37:55.619 --> 00:37:58.849 align:start position:0% Higher Goals to replace the accounts and<00:37:56.160> it<00:37:56.339> supports<00:37:57.240> almost<00:37:57.960> all<00:37:58.440> existing 00:37:58.849 --> 00:37:58.859 align:start position:0% and it supports almost all existing 00:37:58.859 --> 00:38:00.890 align:start position:0% and it supports almost all existing contracts<00:37:59.400> as<00:37:59.820> I<00:37:59.940> said<00:38:00.060> with<00:38:00.240> the<00:38:00.420> limitation 00:38:00.890 --> 00:38:00.900 align:start position:0% contracts as I said with the limitation 00:38:00.900 --> 00:38:03.050 align:start position:0% contracts as I said with the limitation of<00:38:01.200> contracts<00:38:01.680> that<00:38:01.859> limit<00:38:02.520> themselves<00:38:02.880> to 00:38:03.050 --> 00:38:03.060 align:start position:0% of contracts that limit themselves to 00:38:03.060 --> 00:38:06.109 align:start position:0% of contracts that limit themselves to EOS<00:38:03.900> it<00:38:04.440> supports<00:38:04.680> any<00:38:05.040> contracts<00:38:05.880> on<00:38:06.000> the 00:38:06.109 --> 00:38:06.119 align:start position:0% EOS it supports any contracts on the 00:38:06.119 --> 00:38:08.089 align:start position:0% EOS it supports any contracts on the Chain<00:38:06.240> all<00:38:06.780> tokens<00:38:07.140> for<00:38:07.320> example 00:38:08.089 --> 00:38:08.099 align:start position:0% Chain all tokens for example 00:38:08.099 --> 00:38:09.829 align:start position:0% Chain all tokens for example so<00:38:08.579> we 00:38:09.829 --> 00:38:09.839 align:start position:0% so we 00:38:09.839 --> 00:38:11.630 align:start position:0% so we yes<00:38:10.320> with<00:38:10.619> the<00:38:10.740> limitation<00:38:11.099> you<00:38:11.280> need<00:38:11.400> to<00:38:11.520> add 00:38:11.630 --> 00:38:11.640 align:start position:0% yes with the limitation you need to add 00:38:11.640 --> 00:38:13.430 align:start position:0% yes with the limitation you need to add support<00:38:11.880> for<00:38:12.180> some<00:38:12.359> tokens<00:38:12.780> in<00:38:13.140> your<00:38:13.260> account 00:38:13.430 --> 00:38:13.440 align:start position:0% support for some tokens in your account 00:38:13.440 --> 00:38:17.569 align:start position:0% support for some tokens in your account that's<00:38:13.800> right<00:38:13.980> I<00:38:14.640> agree 00:38:17.569 --> 00:38:17.579 align:start position:0% 00:38:17.579 --> 00:38:19.550 align:start position:0% so<00:38:17.940> the<00:38:18.060> target<00:38:18.180> here<00:38:18.420> is<00:38:18.720> not 00:38:19.550 --> 00:38:19.560 align:start position:0% so the target here is not 00:38:19.560 --> 00:38:23.349 align:start position:0% so the target here is not helping<00:38:20.099> adapt<00:38:20.579> building<00:38:21.060> the 00:38:23.349 --> 00:38:23.359 align:start position:0% helping adapt building the 00:38:23.359 --> 00:38:26.030 align:start position:0% helping adapt building the account<00:38:24.359> obstruction<00:38:24.720> though<00:38:25.260> you<00:38:25.560> can<00:38:25.680> do<00:38:25.859> it 00:38:26.030 --> 00:38:26.040 align:start position:0% account obstruction though you can do it 00:38:26.040 --> 00:38:28.550 align:start position:0% account obstruction though you can do it the<00:38:26.760> target<00:38:26.880> is<00:38:27.240> letting<00:38:27.720> the<00:38:28.079> user<00:38:28.320> have 00:38:28.550 --> 00:38:28.560 align:start position:0% the target is letting the user have 00:38:28.560 --> 00:38:31.069 align:start position:0% the target is letting the user have control<00:38:28.740> of<00:38:29.040> his<00:38:29.280> own<00:38:29.579> account<00:38:29.880> and<00:38:30.599> do<00:38:30.780> it<00:38:30.900> in 00:38:31.069 --> 00:38:31.079 align:start position:0% control of his own account and do it in 00:38:31.079 --> 00:38:32.870 align:start position:0% control of his own account and do it in a<00:38:31.380> better<00:38:31.500> way 00:38:32.870 --> 00:38:32.880 align:start position:0% a better way 00:38:32.880 --> 00:38:34.370 align:start position:0% a better way thank<00:38:33.359> you<00:38:33.480> George<00:38:33.599> do<00:38:33.900> you<00:38:33.960> have<00:38:34.020> another<00:38:34.140> one 00:38:34.370 --> 00:38:34.380 align:start position:0% thank you George do you have another one 00:38:34.380 --> 00:38:38.210 align:start position:0% thank you George do you have another one what<00:38:34.859> I<00:38:35.339> mean<00:38:35.400> last<00:38:35.640> one<00:38:35.880> maybe 00:38:38.210 --> 00:38:38.220 align:start position:0% 00:38:38.220 --> 00:38:39.950 align:start position:0% thanks 00:38:39.950 --> 00:38:39.960 align:start position:0% thanks 00:38:39.960 --> 00:38:41.810 align:start position:0% thanks um<00:38:40.020> so<00:38:40.680> I<00:38:40.800> haven't<00:38:40.920> looked<00:38:41.220> at<00:38:41.339> four<00:38:41.579> three 00:38:41.810 --> 00:38:41.820 align:start position:0% um so I haven't looked at four three 00:38:41.820 --> 00:38:43.670 align:start position:0% um so I haven't looked at four three three<00:38:42.000> seven<00:38:42.240> so<00:38:42.420> it<00:38:42.599> might<00:38:42.720> be<00:38:42.900> like<00:38:43.260> a<00:38:43.380> basic 00:38:43.670 --> 00:38:43.680 align:start position:0% three seven so it might be like a basic 00:38:43.680 --> 00:38:45.230 align:start position:0% three seven so it might be like a basic question<00:38:43.920> but<00:38:44.640> um 00:38:45.230 --> 00:38:45.240 align:start position:0% question but um 00:38:45.240 --> 00:38:47.450 align:start position:0% question but um how<00:38:45.599> does<00:38:45.839> like<00:38:46.079> ownership<00:38:46.500> of<00:38:46.980> the<00:38:47.280> account 00:38:47.450 --> 00:38:47.460 align:start position:0% how does like ownership of the account 00:38:47.460 --> 00:38:49.730 align:start position:0% how does like ownership of the account work<00:38:48.060> like<00:38:48.480> the<00:38:48.660> abstracted<00:38:49.140> account<00:38:49.320> is<00:38:49.560> it 00:38:49.730 --> 00:38:49.740 align:start position:0% work like the abstracted account is it 00:38:49.740 --> 00:38:51.530 align:start position:0% work like the abstracted account is it is<00:38:49.920> it<00:38:50.099> private<00:38:50.400> key<00:38:50.520> held<00:38:50.940> so<00:38:51.119> it's<00:38:51.240> kind<00:38:51.480> of 00:38:51.530 --> 00:38:51.540 align:start position:0% is it private key held so it's kind of 00:38:51.540 --> 00:38:53.569 align:start position:0% is it private key held so it's kind of like<00:38:51.660> an<00:38:52.020> externally<00:38:52.440> owned<00:38:52.859> smart<00:38:53.099> contract 00:38:53.569 --> 00:38:53.579 align:start position:0% like an externally owned smart contract 00:38:53.579 --> 00:38:55.190 align:start position:0% like an externally owned smart contract account 00:38:55.190 --> 00:38:55.200 align:start position:0% account 00:38:55.200 --> 00:38:57.650 align:start position:0% account um<00:38:55.320> is<00:38:55.800> it<00:38:55.980> single<00:38:56.400> owner<00:38:56.700> is<00:38:56.820> it<00:38:57.000> multi-owner 00:38:57.650 --> 00:38:57.660 align:start position:0% um is it single owner is it multi-owner 00:38:57.660 --> 00:39:00.650 align:start position:0% um is it single owner is it multi-owner uh<00:38:58.380> and<00:38:58.500> the<00:38:58.619> other<00:38:58.740> question<00:38:58.920> I<00:38:59.160> have<00:38:59.280> is<00:38:59.660> is 00:39:00.650 --> 00:39:00.660 align:start position:0% uh and the other question I have is is 00:39:00.660 --> 00:39:02.510 align:start position:0% uh and the other question I have is is this<00:39:00.960> like<00:39:01.140> a<00:39:01.440> complimentary<00:39:01.980> standard<00:39:02.339> to 00:39:02.510 --> 00:39:02.520 align:start position:0% this like a complimentary standard to 00:39:02.520 --> 00:39:05.089 align:start position:0% this like a complimentary standard to off<00:39:02.760> and<00:39:02.940> off<00:39:03.060> call<00:39:03.359> or<00:39:03.780> is<00:39:03.900> this<00:39:04.200> like<00:39:04.920> how 00:39:05.089 --> 00:39:05.099 align:start position:0% off and off call or is this like how 00:39:05.099 --> 00:39:07.069 align:start position:0% off and off call or is this like how would<00:39:05.220> that<00:39:05.400> work<00:39:05.520> with<00:39:05.760> with<00:39:06.359> when<00:39:06.599> off<00:39:06.839> call 00:39:07.069 --> 00:39:07.079 align:start position:0% would that work with with when off call 00:39:07.079 --> 00:39:08.870 align:start position:0% would that work with with when off call is<00:39:07.260> implemented<00:39:07.800> okay<00:39:08.160> the<00:39:08.400> answer<00:39:08.520> for<00:39:08.760> the 00:39:08.870 --> 00:39:08.880 align:start position:0% is implemented okay the answer for the 00:39:08.880 --> 00:39:10.910 align:start position:0% is implemented okay the answer for the question<00:39:09.060> the<00:39:09.359> first<00:39:09.660> question<00:39:09.839> is<00:39:10.440> all<00:39:10.800> of 00:39:10.910 --> 00:39:10.920 align:start position:0% question the first question is all of 00:39:10.920 --> 00:39:12.650 align:start position:0% question the first question is all of the<00:39:11.040> above<00:39:11.280> or<00:39:11.460> any<00:39:11.640> of<00:39:11.820> them<00:39:11.880> because<00:39:12.180> each 00:39:12.650 --> 00:39:12.660 align:start position:0% the above or any of them because each 00:39:12.660 --> 00:39:14.870 align:start position:0% the above or any of them because each wallet<00:39:13.020> can<00:39:13.140> decide<00:39:13.440> as<00:39:14.040> I<00:39:14.220> said<00:39:14.339> we<00:39:14.520> had<00:39:14.640> a 00:39:14.870 --> 00:39:14.880 align:start position:0% wallet can decide as I said we had a 00:39:14.880 --> 00:39:17.030 align:start position:0% wallet can decide as I said we had a wallet<00:39:15.180> here<00:39:15.359> in<00:39:15.780> that<00:39:16.260> demonstrate<00:39:16.680> how<00:39:16.920> to 00:39:17.030 --> 00:39:17.040 align:start position:0% wallet here in that demonstrate how to 00:39:17.040 --> 00:39:18.290 align:start position:0% wallet here in that demonstrate how to use<00:39:17.160> zero<00:39:17.460> knowledge<00:39:17.700> proof<00:39:17.940> instead<00:39:18.240> of 00:39:18.290 --> 00:39:18.300 align:start position:0% use zero knowledge proof instead of 00:39:18.300 --> 00:39:20.030 align:start position:0% use zero knowledge proof instead of signatures<00:39:18.720> another<00:39:19.380> wallet<00:39:19.920> that 00:39:20.030 --> 00:39:20.040 align:start position:0% signatures another wallet that 00:39:20.040 --> 00:39:22.310 align:start position:0% signatures another wallet that implements<00:39:20.640> the<00:39:20.820> RSA<00:39:21.359> signatures<00:39:21.960> from<00:39:22.200> your 00:39:22.310 --> 00:39:22.320 align:start position:0% implements the RSA signatures from your 00:39:22.320 --> 00:39:24.710 align:start position:0% implements the RSA signatures from your phone<00:39:22.500> you<00:39:23.460> want<00:39:23.640> eoa<00:39:24.119> yes<00:39:24.300> our<00:39:24.540> simple 00:39:24.710 --> 00:39:24.720 align:start position:0% phone you want eoa yes our simple 00:39:24.720 --> 00:39:28.010 align:start position:0% phone you want eoa yes our simple implementation<00:39:25.260> uses<00:39:25.740> in<00:39:26.460> eoa<00:39:27.300> is<00:39:27.540> an<00:39:27.720> owner 00:39:28.010 --> 00:39:28.020 align:start position:0% implementation uses in eoa is an owner 00:39:28.020 --> 00:39:30.710 align:start position:0% implementation uses in eoa is an owner but<00:39:28.500> it's<00:39:29.160> just<00:39:29.339> one<00:39:29.520> implementation 00:39:30.710 --> 00:39:30.720 align:start position:0% but it's just one implementation 00:39:30.720 --> 00:39:32.750 align:start position:0% but it's just one implementation the<00:39:31.200> other<00:39:31.320> question<00:39:31.560> regarding<00:39:32.160> Earth<00:39:32.520> and 00:39:32.750 --> 00:39:32.760 align:start position:0% the other question regarding Earth and 00:39:32.760 --> 00:39:33.970 align:start position:0% the other question regarding Earth and Oscar 00:39:33.970 --> 00:39:33.980 align:start position:0% Oscar 00:39:33.980 --> 00:39:38.270 align:start position:0% Oscar it<00:39:34.980> is<00:39:35.280> possible<00:39:35.940> to<00:39:36.900> do<00:39:37.140> some<00:39:37.680> of<00:39:38.160> the 00:39:38.270 --> 00:39:38.280 align:start position:0% it is possible to do some of the 00:39:38.280 --> 00:39:39.950 align:start position:0% it is possible to do some of the features<00:39:38.579> with<00:39:38.820> Auto<00:39:39.000> and<00:39:39.300> Oscar<00:39:39.540> they 00:39:39.950 --> 00:39:39.960 align:start position:0% features with Auto and Oscar they 00:39:39.960 --> 00:39:42.650 align:start position:0% features with Auto and Oscar they basically<00:39:40.260> do<00:39:40.560> the 00:39:42.650 --> 00:39:42.660 align:start position:0% basically do the 00:39:42.660 --> 00:39:44.950 align:start position:0% basically do the abstracting<00:39:43.440> payment 00:39:44.950 --> 00:39:44.960 align:start position:0% abstracting payment 00:39:44.960 --> 00:39:49.270 align:start position:0% abstracting payment we<00:39:45.960> believe<00:39:46.079> that<00:39:46.760> it<00:39:47.760> is<00:39:47.940> far<00:39:48.119> too<00:39:48.300> complex 00:39:49.270 --> 00:39:49.280 align:start position:0% we believe that it is far too complex 00:39:49.280 --> 00:39:52.490 align:start position:0% we believe that it is far too complex feature<00:39:50.280> just<00:39:50.640> to<00:39:51.119> justify<00:39:51.599> these<00:39:52.140> two<00:39:52.260> op 00:39:52.490 --> 00:39:52.500 align:start position:0% feature just to justify these two op 00:39:52.500 --> 00:39:54.290 align:start position:0% feature just to justify these two op codes<00:39:52.740> because<00:39:53.460> they<00:39:53.760> don't<00:39:53.880> do<00:39:54.060> anything 00:39:54.290 --> 00:39:54.300 align:start position:0% codes because they don't do anything 00:39:54.300 --> 00:39:55.970 align:start position:0% codes because they don't do anything else<00:39:54.599> of<00:39:54.780> the<00:39:54.900> account<00:39:55.020> attraction<00:39:55.440> they 00:39:55.970 --> 00:39:55.980 align:start position:0% else of the account attraction they 00:39:55.980 --> 00:39:58.849 align:start position:0% else of the account attraction they don't<00:39:56.099> change<00:39:56.339> they<00:39:56.880> enshrine<00:39:57.420> the<00:39:58.020> ecdsa<00:39:58.680> for 00:39:58.849 --> 00:39:58.859 align:start position:0% don't change they enshrine the ecdsa for 00:39:58.859 --> 00:39:59.810 align:start position:0% don't change they enshrine the ecdsa for example 00:39:59.810 --> 00:39:59.820 align:start position:0% example 00:39:59.820 --> 00:40:01.010 align:start position:0% example so 00:40:01.010 --> 00:40:01.020 align:start position:0% so 00:40:01.020 --> 00:40:02.690 align:start position:0% so they<00:40:01.560> can<00:40:01.740> be<00:40:01.859> combined<00:40:02.160> they<00:40:02.339> can<00:40:02.460> be<00:40:02.520> used 00:40:02.690 --> 00:40:02.700 align:start position:0% they can be combined they can be used 00:40:02.700 --> 00:40:04.550 align:start position:0% they can be combined they can be used together<00:40:02.820> but 00:40:04.550 --> 00:40:04.560 align:start position:0% together but 00:40:04.560 --> 00:40:07.790 align:start position:0% together but we<00:40:05.220> hope<00:40:05.400> for<00:40:05.520> other<00:40:05.760> alternatives 00:40:07.790 --> 00:40:07.800 align:start position:0% we hope for other alternatives 00:40:07.800 --> 00:40:09.950 align:start position:0% we hope for other alternatives a<00:40:08.339> huge<00:40:08.520> round<00:40:08.579> of<00:40:08.820> applause<00:40:09.180> for<00:40:09.420> a<00:40:09.599> Syrian 00:40:09.950 --> 00:40:09.960 align:start position:0% a huge round of applause for a Syrian 00:40:09.960 --> 00:40:11.990 align:start position:0% a huge round of applause for a Syrian drawer<00:40:10.440> thank<00:40:11.040> you<00:40:11.160> very<00:40:11.280> much<00:40:11.460> thank<00:40:11.880> you 00:40:11.990 --> 00:40:12.000 align:start position:0% drawer thank you very much thank you 00:40:12.000 --> 00:40:13.190 align:start position:0% drawer thank you very much thank you everyone<00:40:12.119> thank<00:40:12.599> you<00:40:12.720> so<00:40:12.900> much 00:40:13.190 --> 00:40:13.200 align:start position:0% everyone thank you so much 00:40:13.200 --> 00:40:16.469 align:start position:0% everyone thank you so much [Applause]