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:12.730 align:start position:0% [Music] 00:00:12.730 --> 00:00:12.740 align:start position:0% 00:00:12.740 --> 00:00:14.930 align:start position:0% today<00:00:13.740> I<00:00:13.920> have<00:00:14.040> the<00:00:14.160> pleasure<00:00:14.460> of<00:00:14.580> moderating 00:00:14.930 --> 00:00:14.940 align:start position:0% today I have the pleasure of moderating 00:00:14.940 --> 00:00:17.150 align:start position:0% today I have the pleasure of moderating a<00:00:15.240> panel<00:00:15.540> that<00:00:15.719> is<00:00:15.960> going<00:00:16.139> to<00:00:16.260> technically 00:00:17.150 --> 00:00:17.160 align:start position:0% a panel that is going to technically 00:00:17.160 --> 00:00:18.890 align:start position:0% a panel that is going to technically challenge<00:00:17.520> me<00:00:17.820> so<00:00:18.180> I'm<00:00:18.359> just<00:00:18.600> going<00:00:18.720> to<00:00:18.840> be 00:00:18.890 --> 00:00:18.900 align:start position:0% challenge me so I'm just going to be 00:00:18.900 --> 00:00:20.109 align:start position:0% challenge me so I'm just going to be really<00:00:19.080> good<00:00:19.260> at<00:00:19.440> asking<00:00:19.800> questions 00:00:20.109 --> 00:00:20.119 align:start position:0% really good at asking questions 00:00:20.119 --> 00:00:22.550 align:start position:0% really good at asking questions hopefully<00:00:21.119> uh<00:00:21.900> this<00:00:22.080> is<00:00:22.140> about<00:00:22.260> account 00:00:22.550 --> 00:00:22.560 align:start position:0% hopefully uh this is about account 00:00:22.560 --> 00:00:25.790 align:start position:0% hopefully uh this is about account abstraction<00:00:23.340> which<00:00:23.880> has<00:00:24.539> been<00:00:24.960> a<00:00:25.260> part<00:00:25.439> of 00:00:25.790 --> 00:00:25.800 align:start position:0% abstraction which has been a part of 00:00:25.800 --> 00:00:28.910 align:start position:0% abstraction which has been a part of ethereum<00:00:26.760> as<00:00:27.539> a<00:00:27.779> topic<00:00:28.080> for<00:00:28.320> a<00:00:28.439> very<00:00:28.500> long<00:00:28.740> time 00:00:28.910 --> 00:00:28.920 align:start position:0% ethereum as a topic for a very long time 00:00:28.920 --> 00:00:30.470 align:start position:0% ethereum as a topic for a very long time and<00:00:29.160> now<00:00:29.340> that<00:00:29.400> we<00:00:29.519> are<00:00:29.640> post<00:00:29.820> merge<00:00:30.119> maybe<00:00:30.300> we 00:00:30.470 --> 00:00:30.480 align:start position:0% and now that we are post merge maybe we 00:00:30.480 --> 00:00:32.470 align:start position:0% and now that we are post merge maybe we can<00:00:30.599> actually<00:00:30.720> redistribute<00:00:31.320> some<00:00:31.500> developer 00:00:32.470 --> 00:00:32.480 align:start position:0% can actually redistribute some developer 00:00:32.480 --> 00:00:35.150 align:start position:0% can actually redistribute some developer resources<00:00:33.480> to<00:00:34.020> building<00:00:34.260> something<00:00:34.559> that<00:00:34.860> has 00:00:35.150 --> 00:00:35.160 align:start position:0% resources to building something that has 00:00:35.160 --> 00:00:37.310 align:start position:0% resources to building something that has always<00:00:35.700> been<00:00:36.180> talked<00:00:36.719> about<00:00:36.840> as<00:00:37.140> something 00:00:37.310 --> 00:00:37.320 align:start position:0% always been talked about as something 00:00:37.320 --> 00:00:39.830 align:start position:0% always been talked about as something that<00:00:37.559> is<00:00:37.739> fundamentally<00:00:38.219> crucial<00:00:39.120> to<00:00:39.660> the 00:00:39.830 --> 00:00:39.840 align:start position:0% that is fundamentally crucial to the 00:00:39.840 --> 00:00:42.170 align:start position:0% that is fundamentally crucial to the future<00:00:39.960> of<00:00:40.140> ethereum<00:00:40.620> and<00:00:41.219> every<00:00:41.460> time<00:00:41.700> I<00:00:42.059> talk 00:00:42.170 --> 00:00:42.180 align:start position:0% future of ethereum and every time I talk 00:00:42.180 --> 00:00:43.910 align:start position:0% future of ethereum and every time I talk to<00:00:42.360> somebody<00:00:42.540> who's<00:00:43.079> technically<00:00:43.500> minded 00:00:43.910 --> 00:00:43.920 align:start position:0% to somebody who's technically minded 00:00:43.920 --> 00:00:45.830 align:start position:0% to somebody who's technically minded they<00:00:44.160> all<00:00:44.340> say<00:00:44.640> that<00:00:45.239> we<00:00:45.420> need<00:00:45.600> account 00:00:45.830 --> 00:00:45.840 align:start position:0% they all say that we need account 00:00:45.840 --> 00:00:48.709 align:start position:0% they all say that we need account abstraction<00:00:46.440> it's<00:00:47.160> not<00:00:47.460> an<00:00:48.000> option<00:00:48.239> we<00:00:48.600> have 00:00:48.709 --> 00:00:48.719 align:start position:0% abstraction it's not an option we have 00:00:48.719 --> 00:00:51.110 align:start position:0% abstraction it's not an option we have to<00:00:48.840> have<00:00:48.960> it<00:00:49.079> so<00:00:49.260> we're<00:00:49.440> going<00:00:49.559> to<00:00:49.620> explore<00:00:50.120> why 00:00:51.110 --> 00:00:51.120 align:start position:0% to have it so we're going to explore why 00:00:51.120 --> 00:00:53.330 align:start position:0% to have it so we're going to explore why everyone<00:00:51.660> who's<00:00:52.079> more<00:00:52.320> technical<00:00:52.620> to<00:00:52.860> me<00:00:52.920> are 00:00:53.330 --> 00:00:53.340 align:start position:0% everyone who's more technical to me are 00:00:53.340 --> 00:00:54.950 align:start position:0% everyone who's more technical to me are always<00:00:53.520> like<00:00:53.760> yes<00:00:54.059> accountants<00:00:54.780> attraction 00:00:54.950 --> 00:00:54.960 align:start position:0% always like yes accountants attraction 00:00:54.960 --> 00:00:58.850 align:start position:0% always like yes accountants attraction good<00:00:55.460> so<00:00:56.460> on<00:00:57.180> we<00:00:57.480> have<00:00:57.600> Julian<00:00:58.079> Julian<00:00:58.500> Nissa 00:00:58.850 --> 00:00:58.860 align:start position:0% good so on we have Julian Julian Nissa 00:00:58.860 --> 00:01:00.410 align:start position:0% good so on we have Julian Julian Nissa the<00:00:59.039> co-founder<00:00:59.340> of<00:00:59.460> Argent<00:00:59.820> he<00:01:00.000> is<00:01:00.120> here<00:01:00.360> in 00:01:00.410 --> 00:01:00.420 align:start position:0% the co-founder of Argent he is here in 00:01:00.420 --> 00:01:01.670 align:start position:0% the co-founder of Argent he is here in the<00:01:00.539> middle<00:01:00.600> there<00:01:00.780> we<00:01:00.899> go<00:01:01.020> and<00:01:01.199> then<00:01:01.320> on<00:01:01.559> the 00:01:01.670 --> 00:01:01.680 align:start position:0% the middle there we go and then on the 00:01:01.680 --> 00:01:03.590 align:start position:0% the middle there we go and then on the far<00:01:01.800> end<00:01:01.980> we<00:01:02.219> have<00:01:02.280> yoab<00:01:02.760> Weiss<00:01:03.120> the<00:01:03.420> security 00:01:03.590 --> 00:01:03.600 align:start position:0% far end we have yoab Weiss the security 00:01:03.600 --> 00:01:05.870 align:start position:0% far end we have yoab Weiss the security researcher<00:01:04.199> at<00:01:04.379> the<00:01:04.500> EF<00:01:04.799> and<00:01:05.400> then<00:01:05.519> in<00:01:05.700> the 00:01:05.870 --> 00:01:05.880 align:start position:0% researcher at the EF and then in the 00:01:05.880 --> 00:01:07.490 align:start position:0% researcher at the EF and then in the middle<00:01:05.939> here<00:01:06.180> sitting<00:01:06.540> next<00:01:06.659> to<00:01:06.780> vitalik<00:01:07.200> is 00:01:07.490 --> 00:01:07.500 align:start position:0% middle here sitting next to vitalik is 00:01:07.500 --> 00:01:09.950 align:start position:0% middle here sitting next to vitalik is light<00:01:07.799> clients<00:01:08.280> AKA<00:01:08.640> Matt<00:01:09.000> he's<00:01:09.479> on<00:01:09.659> the<00:01:09.780> guest 00:01:09.950 --> 00:01:09.960 align:start position:0% light clients AKA Matt he's on the guest 00:01:09.960 --> 00:01:11.690 align:start position:0% light clients AKA Matt he's on the guest team<00:01:10.140> and<00:01:10.860> then<00:01:10.920> there's<00:01:11.040> also<00:01:11.280> metallic 00:01:11.690 --> 00:01:11.700 align:start position:0% team and then there's also metallic 00:01:11.700 --> 00:01:13.609 align:start position:0% team and then there's also metallic what's<00:01:12.060> up<00:01:12.240> guys 00:01:13.609 --> 00:01:13.619 align:start position:0% what's up guys 00:01:13.619 --> 00:01:16.969 align:start position:0% what's up guys yo<00:01:14.280> yep<00:01:14.880> it's<00:01:15.240> great<00:01:15.479> to<00:01:15.659> be<00:01:15.720> here<00:01:15.840> so<00:01:16.619> you<00:01:16.920> guys 00:01:16.969 --> 00:01:16.979 align:start position:0% yo yep it's great to be here so you guys 00:01:16.979 --> 00:01:18.350 align:start position:0% yo yep it's great to be here so you guys can<00:01:17.159> each<00:01:17.340> introduce<00:01:17.700> yourself<00:01:17.880> better<00:01:18.180> than 00:01:18.350 --> 00:01:18.360 align:start position:0% can each introduce yourself better than 00:01:18.360 --> 00:01:19.910 align:start position:0% can each introduce yourself better than I<00:01:18.540> can<00:01:18.720> so<00:01:18.960> yeah<00:01:19.140> we'll<00:01:19.439> start<00:01:19.619> with<00:01:19.740> you<00:01:19.799> I 00:01:19.910 --> 00:01:19.920 align:start position:0% I can so yeah we'll start with you I 00:01:19.920 --> 00:01:20.870 align:start position:0% I can so yeah we'll start with you I want<00:01:20.040> to<00:01:20.100> give<00:01:20.220> a<00:01:20.400> little<00:01:20.580> bit<00:01:20.700> of<00:01:20.820> your 00:01:20.870 --> 00:01:20.880 align:start position:0% want to give a little bit of your 00:01:20.880 --> 00:01:22.429 align:start position:0% want to give a little bit of your background<00:01:21.180> and<00:01:21.600> your<00:01:21.840> relationship<00:01:22.140> with 00:01:22.429 --> 00:01:22.439 align:start position:0% background and your relationship with 00:01:22.439 --> 00:01:24.170 align:start position:0% background and your relationship with account<00:01:22.560> instruction<00:01:22.920> and<00:01:23.520> why<00:01:23.820> you<00:01:24.000> think 00:01:24.170 --> 00:01:24.180 align:start position:0% account instruction and why you think 00:01:24.180 --> 00:01:25.910 align:start position:0% account instruction and why you think it's<00:01:24.240> so<00:01:24.420> important 00:01:25.910 --> 00:01:25.920 align:start position:0% it's so important 00:01:25.920 --> 00:01:30.170 align:start position:0% it's so important well<00:01:26.460> I<00:01:26.880> think<00:01:27.140> yeah<00:01:28.140> sorry<00:01:28.500> uh<00:01:29.280> I<00:01:30.060> think 00:01:30.170 --> 00:01:30.180 align:start position:0% well I think yeah sorry uh I think 00:01:30.180 --> 00:01:32.390 align:start position:0% well I think yeah sorry uh I think account<00:01:30.479> obstruction<00:01:31.320> is<00:01:31.680> something<00:01:31.860> that<00:01:32.159> we 00:01:32.390 --> 00:01:32.400 align:start position:0% account obstruction is something that we 00:01:32.400 --> 00:01:34.730 align:start position:0% account obstruction is something that we must<00:01:32.580> have<00:01:33.020> both<00:01:34.020> for<00:01:34.200> some<00:01:34.439> technical 00:01:34.730 --> 00:01:34.740 align:start position:0% must have both for some technical 00:01:34.740 --> 00:01:37.310 align:start position:0% must have both for some technical reasons<00:01:35.220> such<00:01:35.520> as<00:01:35.640> obstructing<00:01:36.320> signatures 00:01:37.310 --> 00:01:37.320 align:start position:0% reasons such as obstructing signatures 00:01:37.320 --> 00:01:40.249 align:start position:0% reasons such as obstructing signatures for<00:01:37.680> a<00:01:37.920> future<00:01:38.159> Quantum<00:01:38.579> resistance<00:01:39.060> but<00:01:39.780> more 00:01:40.249 --> 00:01:40.259 align:start position:0% for a future Quantum resistance but more 00:01:40.259 --> 00:01:43.429 align:start position:0% for a future Quantum resistance but more importantly<00:01:40.680> for<00:01:41.400> you<00:01:41.579> for<00:01:41.939> usability<00:01:42.420> if<00:01:43.320> you 00:01:43.429 --> 00:01:43.439 align:start position:0% importantly for you for usability if you 00:01:43.439 --> 00:01:46.370 align:start position:0% importantly for you for usability if you want<00:01:43.680> the<00:01:44.280> um<00:01:44.280> I<00:01:45.240> mean<00:01:45.420> even<00:01:45.659> if<00:01:45.659> you<00:01:46.079> want<00:01:46.259> to 00:01:46.370 --> 00:01:46.380 align:start position:0% want the um I mean even if you want to 00:01:46.380 --> 00:01:48.429 align:start position:0% want the um I mean even if you want to really<00:01:46.680> go<00:01:47.280> Bank<00:01:47.520> less 00:01:48.429 --> 00:01:48.439 align:start position:0% really go Bank less 00:01:48.439 --> 00:01:51.530 align:start position:0% really go Bank less then<00:01:49.439> you<00:01:50.100> need<00:01:50.220> to<00:01:50.399> get<00:01:50.520> you<00:01:50.880> know<00:01:51.060> you<00:01:51.420> need 00:01:51.530 --> 00:01:51.540 align:start position:0% then you need to get you know you need 00:01:51.540 --> 00:01:53.690 align:start position:0% then you need to get you know you need to<00:01:51.659> get<00:01:51.840> to<00:01:52.079> a<00:01:52.259> usability<00:01:52.740> where<00:01:53.100> the<00:01:53.399> user 00:01:53.690 --> 00:01:53.700 align:start position:0% to get to a usability where the user 00:01:53.700 --> 00:01:56.270 align:start position:0% to get to a usability where the user never<00:01:53.880> sees<00:01:54.360> a<00:01:54.600> private<00:01:54.899> key<00:01:55.079> user<00:01:55.740> never<00:01:55.920> sees 00:01:56.270 --> 00:01:56.280 align:start position:0% never sees a private key user never sees 00:01:56.280 --> 00:02:00.469 align:start position:0% never sees a private key user never sees a<00:01:56.399> seed<00:01:56.579> phrase<00:01:57.020> so<00:01:58.020> that<00:01:58.640> so<00:01:59.640> that<00:01:59.820> my<00:02:00.299> mother 00:02:00.469 --> 00:02:00.479 align:start position:0% a seed phrase so that so that my mother 00:02:00.479 --> 00:02:02.870 align:start position:0% a seed phrase so that so that my mother can<00:02:00.840> can<00:02:01.320> use<00:02:01.619> it<00:02:01.799> and<00:02:01.979> if<00:02:02.220> she<00:02:02.399> loses<00:02:02.640> access 00:02:02.870 --> 00:02:02.880 align:start position:0% can can use it and if she loses access 00:02:02.880 --> 00:02:05.330 align:start position:0% can can use it and if she loses access to<00:02:03.180> it<00:02:03.299> she<00:02:03.479> wears<00:02:03.840> she<00:02:03.960> has<00:02:04.079> a<00:02:04.200> way<00:02:04.320> to<00:02:04.439> recover 00:02:05.330 --> 00:02:05.340 align:start position:0% to it she wears she has a way to recover 00:02:05.340 --> 00:02:08.870 align:start position:0% to it she wears she has a way to recover and<00:02:06.240> then<00:02:06.799> you<00:02:07.799> need<00:02:07.920> to<00:02:08.099> have<00:02:08.280> a<00:02:08.520> different 00:02:08.870 --> 00:02:08.880 align:start position:0% and then you need to have a different 00:02:08.880 --> 00:02:12.290 align:start position:0% and then you need to have a different security<00:02:09.179> policies<00:02:09.899> in<00:02:10.140> the<00:02:10.259> account<00:02:10.580> uh<00:02:11.580> such 00:02:12.290 --> 00:02:12.300 align:start position:0% security policies in the account uh such 00:02:12.300 --> 00:02:14.449 align:start position:0% security policies in the account uh such as<00:02:12.480> for<00:02:13.200> example<00:02:13.379> you<00:02:13.620> wouldn't<00:02:13.800> expect<00:02:14.099> your 00:02:14.449 --> 00:02:14.459 align:start position:0% as for example you wouldn't expect your 00:02:14.459 --> 00:02:16.729 align:start position:0% as for example you wouldn't expect your bank<00:02:14.700> account<00:02:14.940> to<00:02:15.480> be<00:02:15.599> the<00:02:15.840> same<00:02:16.020> if<00:02:16.319> you<00:02:16.500> are<00:02:16.620> a 00:02:16.729 --> 00:02:16.739 align:start position:0% bank account to be the same if you are a 00:02:16.739 --> 00:02:18.589 align:start position:0% bank account to be the same if you are a large<00:02:16.920> corporation<00:02:17.520> or<00:02:17.940> an<00:02:18.120> individual 00:02:18.589 --> 00:02:18.599 align:start position:0% large corporation or an individual 00:02:18.599 --> 00:02:19.970 align:start position:0% large corporation or an individual customer 00:02:19.970 --> 00:02:19.980 align:start position:0% customer 00:02:19.980 --> 00:02:21.949 align:start position:0% customer maybe<00:02:20.400> you<00:02:20.580> want<00:02:20.760> to<00:02:20.940> have<00:02:21.060> some<00:02:21.420> different 00:02:21.949 --> 00:02:21.959 align:start position:0% maybe you want to have some different 00:02:21.959 --> 00:02:24.589 align:start position:0% maybe you want to have some different spending<00:02:22.680> policies<00:02:23.160> so<00:02:23.879> all<00:02:24.060> of<00:02:24.239> these<00:02:24.420> things 00:02:24.589 --> 00:02:24.599 align:start position:0% spending policies so all of these things 00:02:24.599 --> 00:02:26.750 align:start position:0% spending policies so all of these things become<00:02:25.080> possible<00:02:25.500> anything<00:02:26.040> that<00:02:26.400> the<00:02:26.580> bank 00:02:26.750 --> 00:02:26.760 align:start position:0% become possible anything that the bank 00:02:26.760 --> 00:02:29.750 align:start position:0% become possible anything that the bank bank<00:02:27.239> account<00:02:27.480> can<00:02:27.900> do<00:02:28.080> for<00:02:28.319> you<00:02:28.440> and<00:02:28.800> more<00:02:29.040> can 00:02:29.750 --> 00:02:29.760 align:start position:0% bank account can do for you and more can 00:02:29.760 --> 00:02:31.309 align:start position:0% bank account can do for you and more can be<00:02:30.000> done<00:02:30.180> can<00:02:30.660> be<00:02:30.780> done<00:02:30.900> using<00:02:31.200> account 00:02:31.309 --> 00:02:31.319 align:start position:0% be done can be done using account 00:02:31.319 --> 00:02:33.589 align:start position:0% be done can be done using account obstruction<00:02:31.800> I<00:02:32.520> think<00:02:32.640> this<00:02:32.819> is<00:02:33.000> a<00:02:33.180> must<00:02:33.300> for 00:02:33.589 --> 00:02:33.599 align:start position:0% obstruction I think this is a must for 00:02:33.599 --> 00:02:36.589 align:start position:0% obstruction I think this is a must for ux<00:02:34.080> purposes<00:02:34.640> certainly<00:02:35.640> and<00:02:35.940> going<00:02:36.300> down<00:02:36.480> the 00:02:36.589 --> 00:02:36.599 align:start position:0% ux purposes certainly and going down the 00:02:36.599 --> 00:02:38.089 align:start position:0% ux purposes certainly and going down the line<00:02:36.720> of<00:02:36.900> course<00:02:37.020> we<00:02:37.200> have<00:02:37.379> a<00:02:37.500> Julian<00:02:37.860> from 00:02:38.089 --> 00:02:38.099 align:start position:0% line of course we have a Julian from 00:02:38.099 --> 00:02:40.670 align:start position:0% line of course we have a Julian from Argent<00:02:38.520> uh<00:02:39.420> Julian<00:02:39.840> so<00:02:40.140> can<00:02:40.260> you<00:02:40.379> explain<00:02:40.500> a 00:02:40.670 --> 00:02:40.680 align:start position:0% Argent uh Julian so can you explain a 00:02:40.680 --> 00:02:42.050 align:start position:0% Argent uh Julian so can you explain a little<00:02:40.800> bit<00:02:40.920> about<00:02:41.040> what<00:02:41.280> Arjun<00:02:41.640> is<00:02:41.819> for<00:02:41.940> those 00:02:42.050 --> 00:02:42.060 align:start position:0% little bit about what Arjun is for those 00:02:42.060 --> 00:02:43.670 align:start position:0% little bit about what Arjun is for those who<00:02:42.180> are<00:02:42.300> unfamiliar<00:02:42.720> and<00:02:42.900> how<00:02:43.200> it<00:02:43.319> relates<00:02:43.560> to 00:02:43.670 --> 00:02:43.680 align:start position:0% who are unfamiliar and how it relates to 00:02:43.680 --> 00:02:45.670 align:start position:0% who are unfamiliar and how it relates to account<00:02:43.800> instruction 00:02:45.670 --> 00:02:45.680 align:start position:0% account instruction 00:02:45.680 --> 00:02:48.410 align:start position:0% account instruction so<00:02:46.680> Arjun<00:02:47.099> it's<00:02:47.459> a<00:02:47.700> smart<00:02:47.819> contract<00:02:48.180> you<00:02:48.360> know 00:02:48.410 --> 00:02:48.420 align:start position:0% so Arjun it's a smart contract you know 00:02:48.420 --> 00:02:49.430 align:start position:0% so Arjun it's a smart contract you know we're<00:02:48.540> a<00:02:48.720> company<00:02:48.840> we've<00:02:49.140> been<00:02:49.260> building 00:02:49.430 --> 00:02:49.440 align:start position:0% we're a company we've been building 00:02:49.440 --> 00:02:52.550 align:start position:0% we're a company we've been building smart<00:02:49.739> contract<00:02:50.160> based<00:02:50.580> wallet<00:02:50.879> since<00:02:51.599> 2010 00:02:52.550 --> 00:02:52.560 align:start position:0% smart contract based wallet since 2010 00:02:52.560 --> 00:02:55.130 align:start position:0% smart contract based wallet since 2010 and<00:02:53.459> basically<00:02:53.760> we<00:02:54.000> started<00:02:54.300> on<00:02:54.420> a<00:02:54.599> mission<00:02:54.720> to 00:02:55.130 --> 00:02:55.140 align:start position:0% and basically we started on a mission to 00:02:55.140 --> 00:02:56.690 align:start position:0% and basically we started on a mission to actually<00:02:55.319> solve<00:02:55.860> exactly<00:02:56.340> what<00:02:56.519> account 00:02:56.690 --> 00:02:56.700 align:start position:0% actually solve exactly what account 00:02:56.700 --> 00:02:58.130 align:start position:0% actually solve exactly what account abstraction<00:02:57.180> is<00:02:57.420> trying<00:02:57.540> to<00:02:57.660> solve 00:02:58.130 --> 00:02:58.140 align:start position:0% abstraction is trying to solve 00:02:58.140 --> 00:03:00.470 align:start position:0% abstraction is trying to solve recognizing<00:02:59.099> that<00:02:59.400> the<00:02:59.580> user<00:02:59.940> experience<00:03:00.300> of 00:03:00.470 --> 00:03:00.480 align:start position:0% recognizing that the user experience of 00:03:00.480 --> 00:03:03.470 align:start position:0% recognizing that the user experience of EOS<00:03:00.900> will<00:03:01.680> basically<00:03:01.920> never<00:03:02.099> scale<00:03:02.519> and<00:03:03.180> so<00:03:03.300> if 00:03:03.470 --> 00:03:03.480 align:start position:0% EOS will basically never scale and so if 00:03:03.480 --> 00:03:05.210 align:start position:0% EOS will basically never scale and so if we<00:03:03.599> keep<00:03:03.780> that<00:03:04.019> Paradigm<00:03:04.560> I<00:03:04.680> think<00:03:04.800> we<00:03:04.980> will 00:03:05.210 --> 00:03:05.220 align:start position:0% we keep that Paradigm I think we will 00:03:05.220 --> 00:03:07.070 align:start position:0% we keep that Paradigm I think we will remain<00:03:05.640> in<00:03:05.819> the<00:03:05.940> bubble<00:03:06.300> that<00:03:06.540> we<00:03:06.660> are<00:03:06.780> in<00:03:06.900> but 00:03:07.070 --> 00:03:07.080 align:start position:0% remain in the bubble that we are in but 00:03:07.080 --> 00:03:08.869 align:start position:0% remain in the bubble that we are in but will<00:03:07.260> be<00:03:07.500> unable<00:03:07.739> to<00:03:07.920> reach<00:03:08.220> the<00:03:08.400> next<00:03:08.580> you 00:03:08.869 --> 00:03:08.879 align:start position:0% will be unable to reach the next you 00:03:08.879 --> 00:03:10.850 align:start position:0% will be unable to reach the next you know<00:03:09.000> 100<00:03:09.360> million<00:03:09.900> users<00:03:10.200> or<00:03:10.379> billion<00:03:10.680> of 00:03:10.850 --> 00:03:10.860 align:start position:0% know 100 million users or billion of 00:03:10.860 --> 00:03:12.589 align:start position:0% know 100 million users or billion of users<00:03:11.159> because<00:03:11.340> the<00:03:11.640> user<00:03:12.120> experience<00:03:12.420> of 00:03:12.589 --> 00:03:12.599 align:start position:0% users because the user experience of 00:03:12.599 --> 00:03:14.690 align:start position:0% users because the user experience of self-q<00:03:12.959> study<00:03:13.260> is<00:03:13.319> too<00:03:13.500> complicated<00:03:13.920> and<00:03:14.580> so 00:03:14.690 --> 00:03:14.700 align:start position:0% self-q study is too complicated and so 00:03:14.700 --> 00:03:17.030 align:start position:0% self-q study is too complicated and so we<00:03:14.879> started<00:03:15.180> building<00:03:15.420> Argent<00:03:16.200> based<00:03:16.739> on<00:03:16.800> you 00:03:17.030 --> 00:03:17.040 align:start position:0% we started building Argent based on you 00:03:17.040 --> 00:03:19.250 align:start position:0% we started building Argent based on you know<00:03:17.159> to<00:03:17.340> try<00:03:17.459> to<00:03:17.580> fix<00:03:17.879> that<00:03:18.120> and<00:03:18.780> we<00:03:18.959> did<00:03:19.140> that 00:03:19.250 --> 00:03:19.260 align:start position:0% know to try to fix that and we did that 00:03:19.260 --> 00:03:21.290 align:start position:0% know to try to fix that and we did that at<00:03:19.440> the<00:03:19.560> application<00:03:19.920> layer<00:03:20.519> on<00:03:20.640> ethereum<00:03:21.060> so 00:03:21.290 --> 00:03:21.300 align:start position:0% at the application layer on ethereum so 00:03:21.300 --> 00:03:23.390 align:start position:0% at the application layer on ethereum so trying<00:03:21.599> to<00:03:21.780> to<00:03:22.319> build<00:03:22.620> a<00:03:22.920> smart<00:03:23.040> contract 00:03:23.390 --> 00:03:23.400 align:start position:0% trying to to build a smart contract 00:03:23.400 --> 00:03:26.030 align:start position:0% trying to to build a smart contract based<00:03:23.819> wallet<00:03:24.200> enabling<00:03:25.200> different<00:03:25.680> security 00:03:26.030 --> 00:03:26.040 align:start position:0% based wallet enabling different security 00:03:26.040 --> 00:03:28.729 align:start position:0% based wallet enabling different security flows<00:03:26.819> to<00:03:27.540> actually<00:03:27.659> fix<00:03:28.019> the<00:03:28.200> issues<00:03:28.560> that 00:03:28.729 --> 00:03:28.739 align:start position:0% flows to actually fix the issues that 00:03:28.739 --> 00:03:30.290 align:start position:0% flows to actually fix the issues that you<00:03:29.040> have<00:03:29.159> mentioned<00:03:29.400> so<00:03:29.580> for<00:03:29.819> example<00:03:30.060> we 00:03:30.290 --> 00:03:30.300 align:start position:0% you have mentioned so for example we 00:03:30.300 --> 00:03:31.850 align:start position:0% you have mentioned so for example we introduced<00:03:30.659> social<00:03:30.840> recovery<00:03:31.379> which<00:03:31.620> is<00:03:31.739> a 00:03:31.850 --> 00:03:31.860 align:start position:0% introduced social recovery which is a 00:03:31.860 --> 00:03:33.290 align:start position:0% introduced social recovery which is a way<00:03:31.980> to<00:03:32.159> get<00:03:32.280> rid<00:03:32.459> of<00:03:32.640> seed<00:03:32.879> phrase<00:03:33.120> We 00:03:33.290 --> 00:03:33.300 align:start position:0% way to get rid of seed phrase We 00:03:33.300 --> 00:03:34.729 align:start position:0% way to get rid of seed phrase We introduced<00:03:33.659> some<00:03:33.840> kind<00:03:33.959> of<00:03:34.019> fraud<00:03:34.319> monitoring 00:03:34.729 --> 00:03:34.739 align:start position:0% introduced some kind of fraud monitoring 00:03:34.739 --> 00:03:36.770 align:start position:0% introduced some kind of fraud monitoring and<00:03:34.920> so<00:03:35.099> on<00:03:35.300> that<00:03:36.300> has<00:03:36.420> been<00:03:36.540> a<00:03:36.720> great 00:03:36.770 --> 00:03:36.780 align:start position:0% and so on that has been a great 00:03:36.780 --> 00:03:38.210 align:start position:0% and so on that has been a great experience<00:03:37.140> but<00:03:37.440> of<00:03:37.560> course<00:03:37.680> we<00:03:37.920> build<00:03:38.099> that 00:03:38.210 --> 00:03:38.220 align:start position:0% experience but of course we build that 00:03:38.220 --> 00:03:40.250 align:start position:0% experience but of course we build that at<00:03:38.400> the<00:03:38.519> application<00:03:38.879> layer<00:03:39.360> meaning<00:03:39.959> that 00:03:40.250 --> 00:03:40.260 align:start position:0% at the application layer meaning that 00:03:40.260 --> 00:03:42.470 align:start position:0% at the application layer meaning that smart<00:03:40.500> contract<00:03:40.860> wallet<00:03:41.340> are<00:03:41.819> a<00:03:42.060> second<00:03:42.239> class 00:03:42.470 --> 00:03:42.480 align:start position:0% smart contract wallet are a second class 00:03:42.480 --> 00:03:44.330 align:start position:0% smart contract wallet are a second class citizen<00:03:42.959> because<00:03:43.200> the<00:03:43.560> entire<00:03:43.799> ecosystem 00:03:44.330 --> 00:03:44.340 align:start position:0% citizen because the entire ecosystem 00:03:44.340 --> 00:03:46.430 align:start position:0% citizen because the entire ecosystem it's<00:03:44.819> still<00:03:45.060> built<00:03:45.420> around<00:03:45.540> this<00:03:45.840> Paradigm<00:03:46.319> of 00:03:46.430 --> 00:03:46.440 align:start position:0% it's still built around this Paradigm of 00:03:46.440 --> 00:03:49.250 align:start position:0% it's still built around this Paradigm of voas<00:03:46.860> I<00:03:47.099> mean<00:03:47.480> developers<00:03:48.480> the<00:03:48.780> tooling 00:03:49.250 --> 00:03:49.260 align:start position:0% voas I mean developers the tooling 00:03:49.260 --> 00:03:50.930 align:start position:0% voas I mean developers the tooling everybody<00:03:49.500> is<00:03:49.799> thinking<00:03:50.159> in<00:03:50.340> terms<00:03:50.459> of<00:03:50.580> EOS 00:03:50.930 --> 00:03:50.940 align:start position:0% everybody is thinking in terms of EOS 00:03:50.940 --> 00:03:52.670 align:start position:0% everybody is thinking in terms of EOS which<00:03:51.659> means<00:03:51.959> that<00:03:52.140> there's<00:03:52.319> some 00:03:52.670 --> 00:03:52.680 align:start position:0% which means that there's some 00:03:52.680 --> 00:03:54.589 align:start position:0% which means that there's some compatibility<00:03:53.459> issues<00:03:54.000> if<00:03:54.180> you're<00:03:54.360> a<00:03:54.480> smart 00:03:54.589 --> 00:03:54.599 align:start position:0% compatibility issues if you're a smart 00:03:54.599 --> 00:03:56.869 align:start position:0% compatibility issues if you're a smart contract<00:03:54.959> wallet<00:03:55.680> we<00:03:56.159> like<00:03:56.459> to<00:03:56.580> say<00:03:56.700> that 00:03:56.869 --> 00:03:56.879 align:start position:0% contract wallet we like to say that 00:03:56.879 --> 00:03:59.089 align:start position:0% contract wallet we like to say that we've<00:03:57.180> been<00:03:57.360> second<00:03:57.599> class<00:03:57.840> Citizen<00:03:58.379> and<00:03:58.980> so 00:03:59.089 --> 00:03:59.099 align:start position:0% we've been second class Citizen and so 00:03:59.099 --> 00:03:59.930 align:start position:0% we've been second class Citizen and so of<00:03:59.220> course<00:03:59.340> the<00:03:59.459> goal<00:03:59.700> of<00:03:59.760> account 00:03:59.930 --> 00:03:59.940 align:start position:0% of course the goal of account 00:03:59.940 --> 00:04:02.030 align:start position:0% of course the goal of account abstraction<00:04:00.420> is<00:04:00.780> to<00:04:01.019> make<00:04:01.260> smart<00:04:01.620> contract 00:04:02.030 --> 00:04:02.040 align:start position:0% abstraction is to make smart contract 00:04:02.040 --> 00:04:04.250 align:start position:0% abstraction is to make smart contract based<00:04:02.400> wallet<00:04:02.640> first<00:04:02.879> class<00:04:03.120> Citizen<00:04:03.659> and<00:04:04.140> of 00:04:04.250 --> 00:04:04.260 align:start position:0% based wallet first class Citizen and of 00:04:04.260 --> 00:04:06.770 align:start position:0% based wallet first class Citizen and of course<00:04:04.379> that<00:04:04.560> gets<00:04:04.860> us<00:04:04.980> very<00:04:05.220> very<00:04:05.400> excited 00:04:06.770 --> 00:04:06.780 align:start position:0% course that gets us very very excited 00:04:06.780 --> 00:04:09.050 align:start position:0% course that gets us very very excited uh<00:04:07.379> Matt<00:04:07.560> I've<00:04:07.799> got<00:04:07.980> a<00:04:08.099> special<00:04:08.340> question<00:04:08.640> for 00:04:09.050 --> 00:04:09.060 align:start position:0% uh Matt I've got a special question for 00:04:09.060 --> 00:04:11.030 align:start position:0% uh Matt I've got a special question for you<00:04:09.180> uh<00:04:09.840> but<00:04:10.019> also<00:04:10.319> uh<00:04:10.500> feel<00:04:10.739> free<00:04:10.860> to 00:04:11.030 --> 00:04:11.040 align:start position:0% you uh but also uh feel free to 00:04:11.040 --> 00:04:12.589 align:start position:0% you uh but also uh feel free to introduce<00:04:11.400> yourself<00:04:11.580> and<00:04:11.939> and<00:04:12.120> tell<00:04:12.299> us<00:04:12.420> what 00:04:12.589 --> 00:04:12.599 align:start position:0% introduce yourself and and tell us what 00:04:12.599 --> 00:04:15.050 align:start position:0% introduce yourself and and tell us what you<00:04:12.720> do<00:04:12.900> at<00:04:13.260> Geth<00:04:13.560> but<00:04:14.099> also<00:04:14.340> could<00:04:14.580> you<00:04:14.760> after 00:04:15.050 --> 00:04:15.060 align:start position:0% you do at Geth but also could you after 00:04:15.060 --> 00:04:17.569 align:start position:0% you do at Geth but also could you after you<00:04:15.299> do<00:04:15.420> that<00:04:15.659> explain<00:04:16.560> why<00:04:17.040> do<00:04:17.160> we<00:04:17.280> call<00:04:17.400> it 00:04:17.569 --> 00:04:17.579 align:start position:0% you do that explain why do we call it 00:04:17.579 --> 00:04:19.610 align:start position:0% you do that explain why do we call it account<00:04:17.820> abstraction<00:04:18.479> what<00:04:19.260> are<00:04:19.500> we 00:04:19.610 --> 00:04:19.620 align:start position:0% account abstraction what are we 00:04:19.620 --> 00:04:21.349 align:start position:0% account abstraction what are we abstracting<00:04:20.160> why<00:04:20.459> is<00:04:20.579> the<00:04:20.760> abstracting<00:04:21.180> word 00:04:21.349 --> 00:04:21.359 align:start position:0% abstracting why is the abstracting word 00:04:21.359 --> 00:04:23.629 align:start position:0% abstracting why is the abstracting word here<00:04:21.600> uh<00:04:22.260> just<00:04:22.500> to<00:04:22.620> really<00:04:22.800> get<00:04:23.040> things<00:04:23.220> at<00:04:23.460> the 00:04:23.629 --> 00:04:23.639 align:start position:0% here uh just to really get things at the 00:04:23.639 --> 00:04:25.310 align:start position:0% here uh just to really get things at the very<00:04:23.759> basement<00:04:23.940> level 00:04:25.310 --> 00:04:25.320 align:start position:0% very basement level 00:04:25.320 --> 00:04:27.950 align:start position:0% very basement level sure<00:04:25.800> so<00:04:26.280> I<00:04:26.880> recently<00:04:27.240> joined<00:04:27.479> the<00:04:27.540> guest<00:04:27.780> team 00:04:27.950 --> 00:04:27.960 align:start position:0% sure so I recently joined the guest team 00:04:27.960 --> 00:04:29.749 align:start position:0% sure so I recently joined the guest team actually<00:04:28.199> so<00:04:28.620> I'm<00:04:28.800> kind<00:04:28.979> of<00:04:29.100> like<00:04:29.220> looking<00:04:29.460> for 00:04:29.749 --> 00:04:29.759 align:start position:0% actually so I'm kind of like looking for 00:04:29.759 --> 00:04:32.390 align:start position:0% actually so I'm kind of like looking for my<00:04:30.000> home<00:04:30.240> amongst<00:04:30.900> the<00:04:31.020> guest<00:04:31.259> team<00:04:31.440> I<00:04:32.280> think 00:04:32.390 --> 00:04:32.400 align:start position:0% my home amongst the guest team I think 00:04:32.400 --> 00:04:34.550 align:start position:0% my home amongst the guest team I think that<00:04:32.820> there's<00:04:33.180> many<00:04:33.660> different<00:04:33.960> things<00:04:34.259> that 00:04:34.550 --> 00:04:34.560 align:start position:0% that there's many different things that 00:04:34.560 --> 00:04:37.189 align:start position:0% that there's many different things that the<00:04:34.800> get<00:04:35.100> team<00:04:35.580> has<00:04:35.940> focuses<00:04:36.600> on<00:04:36.780> and<00:04:36.900> so<00:04:37.080> I'm 00:04:37.189 --> 00:04:37.199 align:start position:0% the get team has focuses on and so I'm 00:04:37.199 --> 00:04:38.749 align:start position:0% the get team has focuses on and so I'm trying<00:04:37.320> to<00:04:37.440> find<00:04:37.560> like<00:04:37.800> where<00:04:38.220> am<00:04:38.340> I<00:04:38.520> a<00:04:38.580> very 00:04:38.749 --> 00:04:38.759 align:start position:0% trying to find like where am I a very 00:04:38.759 --> 00:04:41.090 align:start position:0% trying to find like where am I a very specific<00:04:39.000> Focus<00:04:39.419> will<00:04:39.720> end<00:04:39.960> up<00:04:40.139> being<00:04:40.320> so 00:04:41.090 --> 00:04:41.100 align:start position:0% specific Focus will end up being so 00:04:41.100 --> 00:04:42.830 align:start position:0% specific Focus will end up being so before<00:04:41.699> that<00:04:42.000> I<00:04:42.180> was<00:04:42.300> part<00:04:42.479> of<00:04:42.600> this<00:04:42.720> team 00:04:42.830 --> 00:04:42.840 align:start position:0% before that I was part of this team 00:04:42.840 --> 00:04:44.330 align:start position:0% before that I was part of this team called<00:04:43.080> quilt<00:04:43.500> and<00:04:43.620> we<00:04:43.800> did<00:04:43.919> a<00:04:44.100> lot<00:04:44.160> of 00:04:44.330 --> 00:04:44.340 align:start position:0% called quilt and we did a lot of 00:04:44.340 --> 00:04:46.610 align:start position:0% called quilt and we did a lot of research<00:04:44.820> and<00:04:45.000> development<00:04:45.419> on<00:04:45.960> future<00:04:46.320> ideas 00:04:46.610 --> 00:04:46.620 align:start position:0% research and development on future ideas 00:04:46.620 --> 00:04:49.550 align:start position:0% research and development on future ideas in<00:04:46.979> ethereum<00:04:47.460> and<00:04:48.180> the<00:04:48.660> first<00:04:48.900> place<00:04:49.139> that<00:04:49.380> I 00:04:49.550 --> 00:04:49.560 align:start position:0% in ethereum and the first place that I 00:04:49.560 --> 00:04:51.170 align:start position:0% in ethereum and the first place that I became<00:04:49.919> involved<00:04:50.220> with<00:04:50.340> account<00:04:50.520> abstraction 00:04:51.170 --> 00:04:51.180 align:start position:0% became involved with account abstraction 00:04:51.180 --> 00:04:53.210 align:start position:0% became involved with account abstraction was<00:04:51.540> back<00:04:52.080> in<00:04:52.259> the<00:04:52.380> earlier<00:04:52.560> days<00:04:52.800> when<00:04:53.040> we 00:04:53.210 --> 00:04:53.220 align:start position:0% was back in the earlier days when we 00:04:53.220 --> 00:04:55.790 align:start position:0% was back in the earlier days when we called<00:04:53.460> the<00:04:54.000> beacon<00:04:54.300> chain<00:04:54.419> eth2<00:04:55.020> and<00:04:55.560> we 00:04:55.790 --> 00:04:55.800 align:start position:0% called the beacon chain eth2 and we 00:04:55.800 --> 00:04:57.409 align:start position:0% called the beacon chain eth2 and we talked<00:04:56.040> about<00:04:56.100> the<00:04:56.460> different<00:04:56.639> phases<00:04:57.120> of<00:04:57.300> the 00:04:57.409 --> 00:04:57.419 align:start position:0% talked about the different phases of the 00:04:57.419 --> 00:04:59.629 align:start position:0% talked about the different phases of the eth2<00:04:57.780> deployments<00:04:58.380> and<00:04:58.620> so<00:04:58.800> the<00:04:59.220> quilt<00:04:59.520> team 00:04:59.629 --> 00:04:59.639 align:start position:0% eth2 deployments and so the quilt team 00:04:59.639 --> 00:05:02.450 align:start position:0% eth2 deployments and so the quilt team was<00:04:59.820> working<00:05:00.060> on<00:05:00.479> phase<00:05:00.840> two<00:05:01.080> for<00:05:01.320> eth2<00:05:01.800> for<00:05:02.160> a 00:05:02.450 --> 00:05:02.460 align:start position:0% was working on phase two for eth2 for a 00:05:02.460 --> 00:05:04.070 align:start position:0% was working on phase two for eth2 for a while<00:05:02.580> and<00:05:03.240> we<00:05:03.419> were<00:05:03.540> trying<00:05:03.660> to<00:05:03.780> think<00:05:03.900> about 00:05:04.070 --> 00:05:04.080 align:start position:0% while and we were trying to think about 00:05:04.080 --> 00:05:07.790 align:start position:0% while and we were trying to think about how<00:05:04.620> to<00:05:04.860> define<00:05:05.660> uh<00:05:06.660> execution<00:05:07.139> environments 00:05:07.790 --> 00:05:07.800 align:start position:0% how to define uh execution environments 00:05:07.800 --> 00:05:10.249 align:start position:0% how to define uh execution environments in<00:05:08.400> a<00:05:08.520> way<00:05:08.639> that<00:05:09.000> you<00:05:09.240> could<00:05:09.360> abstractly 00:05:10.249 --> 00:05:10.259 align:start position:0% in a way that you could abstractly 00:05:10.259 --> 00:05:12.230 align:start position:0% in a way that you could abstractly Define<00:05:10.560> all<00:05:11.040> of<00:05:11.160> the<00:05:11.280> execution<00:05:11.580> semantics 00:05:12.230 --> 00:05:12.240 align:start position:0% Define all of the execution semantics 00:05:12.240 --> 00:05:14.090 align:start position:0% Define all of the execution semantics about<00:05:12.840> the<00:05:13.080> virtual<00:05:13.440> machine<00:05:13.620> that<00:05:13.979> was 00:05:14.090 --> 00:05:14.100 align:start position:0% about the virtual machine that was 00:05:14.100 --> 00:05:16.070 align:start position:0% about the virtual machine that was executing<00:05:14.460> on<00:05:14.639> ethereum<00:05:15.120> and<00:05:15.600> of<00:05:15.720> course<00:05:15.840> like 00:05:16.070 --> 00:05:16.080 align:start position:0% executing on ethereum and of course like 00:05:16.080 --> 00:05:17.450 align:start position:0% executing on ethereum and of course like one<00:05:16.259> of<00:05:16.380> those<00:05:16.500> things<00:05:16.740> that<00:05:16.979> you<00:05:17.100> needed<00:05:17.340> to 00:05:17.450 --> 00:05:17.460 align:start position:0% one of those things that you needed to 00:05:17.460 --> 00:05:18.710 align:start position:0% one of those things that you needed to Define<00:05:17.520> abstractly<00:05:18.120> was<00:05:18.360> like<00:05:18.479> the<00:05:18.600> account 00:05:18.710 --> 00:05:18.720 align:start position:0% Define abstractly was like the account 00:05:18.720 --> 00:05:20.930 align:start position:0% Define abstractly was like the account of<00:05:18.960> logic<00:05:19.380> and<00:05:19.860> so<00:05:19.979> this<00:05:20.160> is<00:05:20.280> where<00:05:20.460> we<00:05:20.639> first 00:05:20.930 --> 00:05:20.940 align:start position:0% of logic and so this is where we first 00:05:20.940 --> 00:05:22.430 align:start position:0% of logic and so this is where we first started<00:05:21.300> running<00:05:21.479> into<00:05:21.660> this<00:05:21.900> problem<00:05:22.020> like 00:05:22.430 --> 00:05:22.440 align:start position:0% started running into this problem like 00:05:22.440 --> 00:05:24.710 align:start position:0% started running into this problem like vitalik<00:05:22.860> had<00:05:22.979> already<00:05:23.100> talked<00:05:23.340> about<00:05:23.520> in<00:05:24.240> the 00:05:24.710 --> 00:05:24.720 align:start position:0% vitalik had already talked about in the 00:05:24.720 --> 00:05:26.990 align:start position:0% vitalik had already talked about in the relation<00:05:25.020> to<00:05:25.139> the<00:05:25.259> evm<00:05:26.039> like<00:05:26.280> earlier<00:05:26.639> on<00:05:26.759> in 00:05:26.990 --> 00:05:27.000 align:start position:0% relation to the evm like earlier on in 00:05:27.000 --> 00:05:29.990 align:start position:0% relation to the evm like earlier on in 2016<00:05:27.419> and<00:05:27.720> so<00:05:27.900> and<00:05:28.500> so<00:05:28.800> I<00:05:29.220> guess<00:05:29.280> for<00:05:29.580> me<00:05:29.759> the 00:05:29.990 --> 00:05:30.000 align:start position:0% 2016 and so and so I guess for me the 00:05:30.000 --> 00:05:31.909 align:start position:0% 2016 and so and so I guess for me the the<00:05:30.120> meaning<00:05:30.660> of<00:05:30.900> account<00:05:31.020> abstraction<00:05:31.620> is 00:05:31.909 --> 00:05:31.919 align:start position:0% the meaning of account abstraction is 00:05:31.919 --> 00:05:34.969 align:start position:0% the meaning of account abstraction is actually<00:05:32.160> you<00:05:33.060> know<00:05:33.180> maybe<00:05:33.780> uh<00:05:34.560> not<00:05:34.800> the 00:05:34.969 --> 00:05:34.979 align:start position:0% actually you know maybe uh not the 00:05:34.979 --> 00:05:36.890 align:start position:0% actually you know maybe uh not the perfect<00:05:35.100> way<00:05:35.460> of<00:05:35.699> of<00:05:36.000> defining<00:05:36.539> like<00:05:36.720> what 00:05:36.890 --> 00:05:36.900 align:start position:0% perfect way of of defining like what 00:05:36.900 --> 00:05:38.810 align:start position:0% perfect way of of defining like what accounts<00:05:37.199> abstraction<00:05:37.560> actually<00:05:37.860> is<00:05:38.100> it's<00:05:38.639> a 00:05:38.810 --> 00:05:38.820 align:start position:0% accounts abstraction actually is it's a 00:05:38.820 --> 00:05:40.070 align:start position:0% accounts abstraction actually is it's a term<00:05:38.940> that<00:05:39.120> has<00:05:39.240> like<00:05:39.360> many<00:05:39.539> meanings<00:05:39.900> for 00:05:40.070 --> 00:05:40.080 align:start position:0% term that has like many meanings for 00:05:40.080 --> 00:05:41.810 align:start position:0% term that has like many meanings for many<00:05:40.259> different<00:05:40.500> people<00:05:40.800> and<00:05:41.520> for<00:05:41.699> me 00:05:41.810 --> 00:05:41.820 align:start position:0% many different people and for me 00:05:41.820 --> 00:05:43.070 align:start position:0% many different people and for me whenever<00:05:42.180> I<00:05:42.300> understand<00:05:42.539> accounts 00:05:43.070 --> 00:05:43.080 align:start position:0% whenever I understand accounts 00:05:43.080 --> 00:05:44.689 align:start position:0% whenever I understand accounts abstraction<00:05:43.440> I<00:05:43.800> think<00:05:43.919> of<00:05:44.100> it<00:05:44.220> more<00:05:44.400> as<00:05:44.520> like 00:05:44.689 --> 00:05:44.699 align:start position:0% abstraction I think of it more as like 00:05:44.699 --> 00:05:46.909 align:start position:0% abstraction I think of it more as like validation<00:05:45.180> abstraction<00:05:45.780> I<00:05:46.440> think<00:05:46.560> of<00:05:46.740> it 00:05:46.909 --> 00:05:46.919 align:start position:0% validation abstraction I think of it 00:05:46.919 --> 00:05:48.590 align:start position:0% validation abstraction I think of it like<00:05:47.039> we're<00:05:47.220> trying<00:05:47.460> to<00:05:47.580> abstract<00:05:48.060> what<00:05:48.419> it 00:05:48.590 --> 00:05:48.600 align:start position:0% like we're trying to abstract what it 00:05:48.600 --> 00:05:50.570 align:start position:0% like we're trying to abstract what it means<00:05:48.840> to<00:05:49.080> validate<00:05:49.500> an<00:05:49.740> account<00:05:49.860> in<00:05:50.100> ethereum 00:05:50.570 --> 00:05:50.580 align:start position:0% means to validate an account in ethereum 00:05:50.580 --> 00:05:52.909 align:start position:0% means to validate an account in ethereum and<00:05:51.000> so<00:05:51.180> today<00:05:51.360> if<00:05:51.780> you<00:05:51.900> want<00:05:52.020> to<00:05:52.199> validate<00:05:52.740> a 00:05:52.909 --> 00:05:52.919 align:start position:0% and so today if you want to validate a 00:05:52.919 --> 00:05:54.950 align:start position:0% and so today if you want to validate a transaction<00:05:53.280> in<00:05:53.520> ethereum<00:05:54.000> you're<00:05:54.479> going<00:05:54.780> to 00:05:54.950 --> 00:05:54.960 align:start position:0% transaction in ethereum you're going to 00:05:54.960 --> 00:05:58.129 align:start position:0% transaction in ethereum you're going to recover<00:05:55.620> some<00:05:55.979> address<00:05:56.280> from<00:05:57.060> a<00:05:57.479> signature 00:05:58.129 --> 00:05:58.139 align:start position:0% recover some address from a signature 00:05:58.139 --> 00:05:59.870 align:start position:0% recover some address from a signature look<00:05:58.560> at<00:05:58.680> that<00:05:58.860> address<00:05:59.039> in<00:05:59.400> the<00:05:59.580> state<00:05:59.699> to 00:05:59.870 --> 00:05:59.880 align:start position:0% look at that address in the state to 00:05:59.880 --> 00:06:02.990 align:start position:0% look at that address in the state to determine<00:06:00.240> if<00:06:00.419> the<00:06:00.600> nonce<00:06:01.020> is<00:06:01.440> uh<00:06:02.220> okay<00:06:02.520> for 00:06:02.990 --> 00:06:03.000 align:start position:0% determine if the nonce is uh okay for 00:06:03.000 --> 00:06:04.490 align:start position:0% determine if the nonce is uh okay for the<00:06:03.120> transaction<00:06:03.600> that's<00:06:03.900> been<00:06:04.139> sent<00:06:04.320> and 00:06:04.490 --> 00:06:04.500 align:start position:0% the transaction that's been sent and 00:06:04.500 --> 00:06:06.050 align:start position:0% the transaction that's been sent and that<00:06:04.680> the<00:06:04.800> account<00:06:04.919> has<00:06:05.160> enough<00:06:05.280> balance<00:06:05.699> and 00:06:06.050 --> 00:06:06.060 align:start position:0% that the account has enough balance and 00:06:06.060 --> 00:06:07.790 align:start position:0% that the account has enough balance and so<00:06:06.180> that's<00:06:06.360> one<00:06:06.600> way<00:06:06.780> of<00:06:06.960> validating<00:06:07.440> a 00:06:07.790 --> 00:06:07.800 align:start position:0% so that's one way of validating a 00:06:07.800 --> 00:06:09.230 align:start position:0% so that's one way of validating a transaction<00:06:08.280> but<00:06:08.699> there's<00:06:08.880> many<00:06:09.060> different 00:06:09.230 --> 00:06:09.240 align:start position:0% transaction but there's many different 00:06:09.240 --> 00:06:10.670 align:start position:0% transaction but there's many different ways<00:06:09.539> you<00:06:09.660> could<00:06:09.780> have<00:06:09.900> a<00:06:10.080> multi-signature 00:06:10.670 --> 00:06:10.680 align:start position:0% ways you could have a multi-signature 00:06:10.680 --> 00:06:12.170 align:start position:0% ways you could have a multi-signature you<00:06:10.860> could<00:06:10.979> use<00:06:11.220> different<00:06:11.460> cryptographic 00:06:12.170 --> 00:06:12.180 align:start position:0% you could use different cryptographic 00:06:12.180 --> 00:06:14.810 align:start position:0% you could use different cryptographic Primitives<00:06:12.960> to<00:06:13.199> to<00:06:13.500> validate<00:06:14.340> a<00:06:14.460> transaction 00:06:14.810 --> 00:06:14.820 align:start position:0% Primitives to to validate a transaction 00:06:14.820 --> 00:06:16.430 align:start position:0% Primitives to to validate a transaction and<00:06:15.060> so<00:06:15.180> when<00:06:15.240> I<00:06:15.419> think<00:06:15.539> of<00:06:15.720> accounts 00:06:16.430 --> 00:06:16.440 align:start position:0% and so when I think of accounts 00:06:16.440 --> 00:06:17.990 align:start position:0% and so when I think of accounts abstraction<00:06:16.800> that's<00:06:17.280> what<00:06:17.460> I<00:06:17.580> first<00:06:17.820> and 00:06:17.990 --> 00:06:18.000 align:start position:0% abstraction that's what I first and 00:06:18.000 --> 00:06:19.730 align:start position:0% abstraction that's what I first and foremost<00:06:18.300> think<00:06:18.539> about<00:06:18.660> but<00:06:19.380> I<00:06:19.500> also 00:06:19.730 --> 00:06:19.740 align:start position:0% foremost think about but I also 00:06:19.740 --> 00:06:21.650 align:start position:0% foremost think about but I also understand<00:06:19.919> accounts<00:06:20.520> abstraction<00:06:20.880> is<00:06:21.120> you 00:06:21.650 --> 00:06:21.660 align:start position:0% understand accounts abstraction is you 00:06:21.660 --> 00:06:23.749 align:start position:0% understand accounts abstraction is you know<00:06:21.720> used<00:06:22.380> more<00:06:22.800> generally<00:06:23.100> now<00:06:23.340> to<00:06:23.580> think 00:06:23.749 --> 00:06:23.759 align:start position:0% know used more generally now to think 00:06:23.759 --> 00:06:26.150 align:start position:0% know used more generally now to think about<00:06:23.940> smart<00:06:24.479> contract<00:06:24.840> wallets<00:06:25.199> and<00:06:25.740> how<00:06:26.039> can 00:06:26.150 --> 00:06:26.160 align:start position:0% about smart contract wallets and how can 00:06:26.160 --> 00:06:29.029 align:start position:0% about smart contract wallets and how can we<00:06:26.280> add<00:06:26.400> more<00:06:26.639> functionality<00:06:27.240> uh<00:06:28.080> you<00:06:28.860> know<00:06:28.919> to 00:06:29.029 --> 00:06:29.039 align:start position:0% we add more functionality uh you know to 00:06:29.039 --> 00:06:31.430 align:start position:0% we add more functionality uh you know to the<00:06:29.220> protocol<00:06:29.520> or<00:06:29.819> give<00:06:30.180> users<00:06:30.720> a<00:06:30.900> better<00:06:31.080> user 00:06:31.430 --> 00:06:31.440 align:start position:0% the protocol or give users a better user 00:06:31.440 --> 00:06:32.510 align:start position:0% the protocol or give users a better user experience<00:06:31.680> when<00:06:31.919> they're<00:06:32.039> interacting<00:06:32.400> with 00:06:32.510 --> 00:06:32.520 align:start position:0% experience when they're interacting with 00:06:32.520 --> 00:06:33.950 align:start position:0% experience when they're interacting with the<00:06:32.639> protocol<00:06:32.940> and<00:06:33.419> so<00:06:33.539> now<00:06:33.660> I<00:06:33.840> understand 00:06:33.950 --> 00:06:33.960 align:start position:0% the protocol and so now I understand 00:06:33.960 --> 00:06:35.330 align:start position:0% the protocol and so now I understand that<00:06:34.259> there's<00:06:34.440> like<00:06:34.560> many<00:06:34.740> ways<00:06:35.039> of<00:06:35.160> like 00:06:35.330 --> 00:06:35.340 align:start position:0% that there's like many ways of like 00:06:35.340 --> 00:06:37.370 align:start position:0% that there's like many ways of like thinking<00:06:35.639> about<00:06:35.759> it<00:06:36.000> uh<00:06:36.419> vitalik<00:06:36.900> every<00:06:37.199> time 00:06:37.370 --> 00:06:37.380 align:start position:0% thinking about it uh vitalik every time 00:06:37.380 --> 00:06:38.870 align:start position:0% thinking about it uh vitalik every time you<00:06:37.620> introduce<00:06:37.979> yourself<00:06:38.100> you<00:06:38.520> always<00:06:38.699> come 00:06:38.870 --> 00:06:38.880 align:start position:0% you introduce yourself you always come 00:06:38.880 --> 00:06:40.309 align:start position:0% you introduce yourself you always come up<00:06:39.000> with<00:06:39.120> a<00:06:39.300> new<00:06:39.360> funny<00:06:39.600> different<00:06:39.900> way<00:06:40.139> of 00:06:40.309 --> 00:06:40.319 align:start position:0% up with a new funny different way of 00:06:40.319 --> 00:06:42.050 align:start position:0% up with a new funny different way of doing<00:06:40.740> it<00:06:40.919> depending<00:06:41.340> on<00:06:41.460> what<00:06:41.699> era<00:06:41.940> of 00:06:42.050 --> 00:06:42.060 align:start position:0% doing it depending on what era of 00:06:42.060 --> 00:06:43.969 align:start position:0% doing it depending on what era of ethereum<00:06:42.419> you<00:06:42.840> are<00:06:42.960> so<00:06:43.199> I'd<00:06:43.440> love<00:06:43.620> for<00:06:43.740> you<00:06:43.860> to 00:06:43.969 --> 00:06:43.979 align:start position:0% ethereum you are so I'd love for you to 00:06:43.979 --> 00:06:45.529 align:start position:0% ethereum you are so I'd love for you to introduce<00:06:44.280> yourself<00:06:44.400> and<00:06:44.759> how<00:06:45.060> you<00:06:45.120> relate<00:06:45.419> to 00:06:45.529 --> 00:06:45.539 align:start position:0% introduce yourself and how you relate to 00:06:45.539 --> 00:06:48.050 align:start position:0% introduce yourself and how you relate to ethereum<00:06:46.139> these<00:06:46.440> days<00:06:46.560> and<00:06:47.280> also<00:06:47.520> answer<00:06:47.819> the 00:06:48.050 --> 00:06:48.060 align:start position:0% ethereum these days and also answer the 00:06:48.060 --> 00:06:50.570 align:start position:0% ethereum these days and also answer the question<00:06:48.240> for<00:06:48.600> you<00:06:48.740> why<00:06:49.740> does<00:06:49.919> everyone<00:06:50.160> say 00:06:50.570 --> 00:06:50.580 align:start position:0% question for you why does everyone say 00:06:50.580 --> 00:06:53.029 align:start position:0% question for you why does everyone say that<00:06:50.880> account<00:06:51.120> abstraction<00:06:51.660> is<00:06:51.900> inevitable 00:06:53.029 --> 00:06:53.039 align:start position:0% that account abstraction is inevitable 00:06:53.039 --> 00:06:55.610 align:start position:0% that account abstraction is inevitable yeah<00:06:53.400> yeah<00:06:53.460> so<00:06:53.819> hi<00:06:54.060> guys<00:06:54.240> I'm<00:06:54.539> vitalik<00:06:55.020> I'm<00:06:55.319> a 00:06:55.610 --> 00:06:55.620 align:start position:0% yeah yeah so hi guys I'm vitalik I'm a 00:06:55.620 --> 00:06:57.770 align:start position:0% yeah yeah so hi guys I'm vitalik I'm a fashion<00:06:56.460> influencer<00:06:56.940> and<00:06:57.060> travel<00:06:57.240> blogger<00:06:57.660> at 00:06:57.770 --> 00:06:57.780 align:start position:0% fashion influencer and travel blogger at 00:06:57.780 --> 00:06:59.809 align:start position:0% fashion influencer and travel blogger at the<00:06:57.900> ethereum<00:06:58.199> foundation 00:06:59.809 --> 00:06:59.819 align:start position:0% the ethereum foundation 00:06:59.819 --> 00:07:00.590 align:start position:0% the ethereum foundation um 00:07:00.590 --> 00:07:00.600 align:start position:0% um 00:07:00.600 --> 00:07:03.350 align:start position:0% um yeah<00:07:01.319> so<00:07:01.680> a<00:07:01.919> chaotic<00:07:02.280> reaction<00:07:02.580> has<00:07:03.000> been<00:07:03.180> a 00:07:03.350 --> 00:07:03.360 align:start position:0% yeah so a chaotic reaction has been a 00:07:03.360 --> 00:07:07.070 align:start position:0% yeah so a chaotic reaction has been a topic<00:07:04.080> I've<00:07:04.319> been<00:07:04.560> uh<00:07:05.300> like<00:07:06.300> really<00:07:06.600> trying<00:07:06.840> to 00:07:07.070 --> 00:07:07.080 align:start position:0% topic I've been uh like really trying to 00:07:07.080 --> 00:07:08.990 align:start position:0% topic I've been uh like really trying to push<00:07:07.259> for<00:07:07.979> um<00:07:08.039> almost<00:07:08.280> uh<00:07:08.580> since<00:07:08.759> the 00:07:08.990 --> 00:07:09.000 align:start position:0% push for um almost uh since the 00:07:09.000 --> 00:07:11.529 align:start position:0% push for um almost uh since the beginning<00:07:09.180> right<00:07:09.600> like<00:07:09.900> you<00:07:10.319> think<00:07:10.620> even 00:07:11.529 --> 00:07:11.539 align:start position:0% beginning right like you think even 00:07:11.539 --> 00:07:14.930 align:start position:0% beginning right like you think even actually<00:07:12.539> uh<00:07:13.080> when<00:07:13.440> ethereum<00:07:14.039> launched<00:07:14.580> the 00:07:14.930 --> 00:07:14.940 align:start position:0% actually uh when ethereum launched the 00:07:14.940 --> 00:07:17.210 align:start position:0% actually uh when ethereum launched the original<00:07:15.600> Vision<00:07:16.080> I<00:07:16.440> had<00:07:16.560> been<00:07:16.740> hoping<00:07:17.039> for 00:07:17.210 --> 00:07:17.220 align:start position:0% original Vision I had been hoping for 00:07:17.220 --> 00:07:19.730 align:start position:0% original Vision I had been hoping for was<00:07:17.580> to<00:07:17.819> try<00:07:18.000> to<00:07:18.180> get<00:07:18.720> people<00:07:18.900> to<00:07:19.259> use<00:07:19.380> Smart 00:07:19.730 --> 00:07:19.740 align:start position:0% was to try to get people to use Smart 00:07:19.740 --> 00:07:21.230 align:start position:0% was to try to get people to use Smart contract<00:07:20.039> while<00:07:20.340> it's<00:07:20.580> by<00:07:20.699> default<00:07:21.060> right 00:07:21.230 --> 00:07:21.240 align:start position:0% contract while it's by default right 00:07:21.240 --> 00:07:22.730 align:start position:0% contract while it's by default right because<00:07:21.419> I<00:07:21.720> mean<00:07:21.900> we<00:07:22.080> wanted<00:07:22.199> people's<00:07:22.560> money 00:07:22.730 --> 00:07:22.740 align:start position:0% because I mean we wanted people's money 00:07:22.740 --> 00:07:24.710 align:start position:0% because I mean we wanted people's money to<00:07:22.979> be<00:07:23.099> secure<00:07:23.340> and<00:07:24.000> we<00:07:24.240> thought<00:07:24.360> it<00:07:24.479> would<00:07:24.599> be 00:07:24.710 --> 00:07:24.720 align:start position:0% to be secure and we thought it would be 00:07:24.720 --> 00:07:26.689 align:start position:0% to be secure and we thought it would be really<00:07:24.900> nice<00:07:25.080> if<00:07:25.259> people<00:07:25.440> could<00:07:25.740> just<00:07:25.979> have 00:07:26.689 --> 00:07:26.699 align:start position:0% really nice if people could just have 00:07:26.699 --> 00:07:29.749 align:start position:0% really nice if people could just have the<00:07:26.880> default<00:07:27.180> type<00:07:27.419> of<00:07:27.539> accounts<00:07:28.020> be<00:07:28.319> a<00:07:29.039> two<00:07:29.520> of 00:07:29.749 --> 00:07:29.759 align:start position:0% the default type of accounts be a two of 00:07:29.759 --> 00:07:32.809 align:start position:0% the default type of accounts be a two of three<00:07:30.000> multi-sig<00:07:30.720> wallet<00:07:31.080> right<00:07:31.259> and 00:07:32.809 --> 00:07:32.819 align:start position:0% three multi-sig wallet right and 00:07:32.819 --> 00:07:35.510 align:start position:0% three multi-sig wallet right and that<00:07:33.539> that<00:07:33.780> ended<00:07:34.139> up<00:07:34.199> not<00:07:34.560> happening<00:07:34.979> I<00:07:35.400> think 00:07:35.510 --> 00:07:35.520 align:start position:0% that that ended up not happening I think 00:07:35.520 --> 00:07:38.089 align:start position:0% that that ended up not happening I think in<00:07:36.300> part<00:07:36.479> because<00:07:36.780> uh<00:07:37.199> the<00:07:37.560> community<00:07:37.680> was 00:07:38.089 --> 00:07:38.099 align:start position:0% in part because uh the community was 00:07:38.099 --> 00:07:39.890 align:start position:0% in part because uh the community was just<00:07:38.280> I'm<00:07:38.460> you<00:07:38.699> know<00:07:38.759> so<00:07:39.000> fed<00:07:39.180> up<00:07:39.360> by<00:07:39.660> yeah 00:07:39.890 --> 00:07:39.900 align:start position:0% just I'm you know so fed up by yeah 00:07:39.900 --> 00:07:41.990 align:start position:0% just I'm you know so fed up by yeah incest<00:07:40.800> and<00:07:40.919> kind<00:07:41.099> of<00:07:41.220> delays<00:07:41.580> on<00:07:41.759> top<00:07:41.880> of 00:07:41.990 --> 00:07:42.000 align:start position:0% incest and kind of delays on top of 00:07:42.000 --> 00:07:44.390 align:start position:0% incest and kind of delays on top of delays<00:07:42.360> for<00:07:42.599> the<00:07:42.840> ethereum<00:07:43.440> 1.0<00:07:43.919> launch<00:07:44.160> then 00:07:44.390 --> 00:07:44.400 align:start position:0% delays for the ethereum 1.0 launch then 00:07:44.400 --> 00:07:45.710 align:start position:0% delays for the ethereum 1.0 launch then at<00:07:44.580> some<00:07:44.639> point<00:07:44.819> we<00:07:44.940> just<00:07:45.060> put<00:07:45.240> our<00:07:45.360> foot<00:07:45.539> down 00:07:45.710 --> 00:07:45.720 align:start position:0% at some point we just put our foot down 00:07:45.720 --> 00:07:47.629 align:start position:0% at some point we just put our foot down and<00:07:45.960> said<00:07:46.139> okay<00:07:46.319> you<00:07:46.860> know<00:07:46.979> no<00:07:47.160> more<00:07:47.280> features 00:07:47.629 --> 00:07:47.639 align:start position:0% and said okay you know no more features 00:07:47.639 --> 00:07:49.370 align:start position:0% and said okay you know no more features unfortunately<00:07:48.240> we<00:07:48.539> have<00:07:48.780> to<00:07:48.900> just<00:07:49.020> like<00:07:49.139> cut 00:07:49.370 --> 00:07:49.380 align:start position:0% unfortunately we have to just like cut 00:07:49.380 --> 00:07:51.050 align:start position:0% unfortunately we have to just like cut everything<00:07:49.560> and<00:07:49.800> launch<00:07:50.039> something 00:07:51.050 --> 00:07:51.060 align:start position:0% everything and launch something 00:07:51.060 --> 00:07:53.570 align:start position:0% everything and launch something um<00:07:51.120> but<00:07:51.419> then<00:07:51.660> you<00:07:52.440> know<00:07:52.620> since<00:07:52.860> then<00:07:53.039> we've 00:07:53.570 --> 00:07:53.580 align:start position:0% um but then you know since then we've 00:07:53.580 --> 00:07:56.629 align:start position:0% um but then you know since then we've been<00:07:53.699> uh<00:07:54.060> trying<00:07:54.419> uh<00:07:54.780> very<00:07:55.259> hard<00:07:55.500> to<00:07:55.680> come<00:07:56.520> up 00:07:56.629 --> 00:07:56.639 align:start position:0% been uh trying uh very hard to come up 00:07:56.639 --> 00:07:59.570 align:start position:0% been uh trying uh very hard to come up with<00:07:56.880> uh<00:07:57.180> the<00:07:57.539> right<00:07:57.660> way<00:07:57.900> to<00:07:58.139> actually<00:07:58.500> get<00:07:59.460> to 00:07:59.570 --> 00:07:59.580 align:start position:0% with uh the right way to actually get to 00:07:59.580 --> 00:08:01.189 align:start position:0% with uh the right way to actually get to the<00:07:59.759> point<00:07:59.880> where<00:08:00.060> smart<00:08:00.360> contract<00:08:00.720> wallets 00:08:01.189 --> 00:08:01.199 align:start position:0% the point where smart contract wallets 00:08:01.199 --> 00:08:04.070 align:start position:0% the point where smart contract wallets can<00:08:01.440> be<00:08:01.620> the<00:08:01.940> default<00:08:02.940> type<00:08:03.419> of<00:08:03.599> wallet<00:08:03.960> that 00:08:04.070 --> 00:08:04.080 align:start position:0% can be the default type of wallet that 00:08:04.080 --> 00:08:05.689 align:start position:0% can be the default type of wallet that people<00:08:04.259> can<00:08:04.500> use<00:08:04.680> and<00:08:04.919> try<00:08:05.099> to<00:08:05.160> get<00:08:05.280> all<00:08:05.460> these 00:08:05.689 --> 00:08:05.699 align:start position:0% people can use and try to get all these 00:08:05.699 --> 00:08:07.850 align:start position:0% people can use and try to get all these benefits<00:08:06.060> like<00:08:06.300> uh<00:08:06.720> you<00:08:07.199> know<00:08:07.259> security<00:08:07.500> for 00:08:07.850 --> 00:08:07.860 align:start position:0% benefits like uh you know security for 00:08:07.860 --> 00:08:10.249 align:start position:0% benefits like uh you know security for multi-cigs<00:08:08.699> you<00:08:09.060> know<00:08:09.120> a<00:08:09.419> social<00:08:09.599> recovery 00:08:10.249 --> 00:08:10.259 align:start position:0% multi-cigs you know a social recovery 00:08:10.259 --> 00:08:12.950 align:start position:0% multi-cigs you know a social recovery other<00:08:11.039> types<00:08:11.460> of<00:08:11.520> cryptography<00:08:12.180> and<00:08:12.419> if<00:08:12.720> we 00:08:12.950 --> 00:08:12.960 align:start position:0% other types of cryptography and if we 00:08:12.960 --> 00:08:15.350 align:start position:0% other types of cryptography and if we want<00:08:13.139> Quantum<00:08:13.500> resistance<00:08:13.940> more<00:08:14.940> recently 00:08:15.350 --> 00:08:15.360 align:start position:0% want Quantum resistance more recently 00:08:15.360 --> 00:08:17.689 align:start position:0% want Quantum resistance more recently yeah<00:08:15.720> mineral<00:08:16.139> thanks<00:08:16.259> to<00:08:16.440> minnow<00:08:16.860> you<00:08:17.639> know 00:08:17.689 --> 00:08:17.699 align:start position:0% yeah mineral thanks to minnow you know 00:08:17.699 --> 00:08:19.670 align:start position:0% yeah mineral thanks to minnow you know your<00:08:17.880> evangelo<00:08:18.479> and<00:08:18.599> the<00:08:18.720> others<00:08:19.020> are<00:08:19.139> the<00:08:19.319> uh 00:08:19.670 --> 00:08:19.680 align:start position:0% your evangelo and the others are the uh 00:08:19.680 --> 00:08:22.490 align:start position:0% your evangelo and the others are the uh the<00:08:20.099> topic<00:08:20.340> of<00:08:20.580> kind<00:08:20.879> of<00:08:20.940> trying<00:08:21.180> to<00:08:21.360> get<00:08:21.539> where 00:08:22.490 --> 00:08:22.500 align:start position:0% the topic of kind of trying to get where 00:08:22.500 --> 00:08:25.969 align:start position:0% the topic of kind of trying to get where like<00:08:22.740> aggregation<00:08:23.580> to<00:08:24.360> be<00:08:24.539> in<00:08:25.020> here<00:08:25.139> in<00:08:25.440> there 00:08:25.969 --> 00:08:25.979 align:start position:0% like aggregation to be in here in there 00:08:25.979 --> 00:08:27.650 align:start position:0% like aggregation to be in here in there as<00:08:26.160> well<00:08:26.280> to<00:08:26.520> try<00:08:26.639> to<00:08:26.759> kind<00:08:26.940> of<00:08:27.000> save<00:08:27.180> gas<00:08:27.419> and 00:08:27.650 --> 00:08:27.660 align:start position:0% as well to try to kind of save gas and 00:08:27.660 --> 00:08:29.869 align:start position:0% as well to try to kind of save gas and save<00:08:28.080> data<00:08:28.919> um<00:08:29.039> so 00:08:29.869 --> 00:08:29.879 align:start position:0% save data um so 00:08:29.879 --> 00:08:32.690 align:start position:0% save data um so I'm<00:08:30.479> like<00:08:30.660> basically<00:08:31.440> trying<00:08:31.740> to<00:08:31.919> find<00:08:32.399> the 00:08:32.690 --> 00:08:32.700 align:start position:0% I'm like basically trying to find the 00:08:32.700 --> 00:08:35.269 align:start position:0% I'm like basically trying to find the way<00:08:32.880> to<00:08:33.120> bring<00:08:33.719> a<00:08:34.260> smart<00:08:34.380> contract<00:08:34.740> while<00:08:35.039> it's 00:08:35.269 --> 00:08:35.279 align:start position:0% way to bring a smart contract while it's 00:08:35.279 --> 00:08:38.029 align:start position:0% way to bring a smart contract while it's in<00:08:35.580> and<00:08:36.000> make<00:08:36.539> them<00:08:36.779> actually<00:08:37.020> be<00:08:37.440> as 00:08:38.029 --> 00:08:38.039 align:start position:0% in and make them actually be as 00:08:38.039 --> 00:08:39.350 align:start position:0% in and make them actually be as convenient<00:08:38.520> and<00:08:38.760> have<00:08:38.940> all<00:08:39.120> of<00:08:39.240> the 00:08:39.350 --> 00:08:39.360 align:start position:0% convenient and have all of the 00:08:39.360 --> 00:08:41.029 align:start position:0% convenient and have all of the properties<00:08:39.659> and<00:08:39.899> censorship<00:08:40.380> resistance<00:08:40.860> is 00:08:41.029 --> 00:08:41.039 align:start position:0% properties and censorship resistance is 00:08:41.039 --> 00:08:42.649 align:start position:0% properties and censorship resistance is another<00:08:41.279> important<00:08:41.640> property 00:08:42.649 --> 00:08:42.659 align:start position:0% another important property 00:08:42.659 --> 00:08:44.410 align:start position:0% another important property um<00:08:42.719> that<00:08:43.800> um 00:08:44.410 --> 00:08:44.420 align:start position:0% um that um 00:08:44.420 --> 00:08:46.790 align:start position:0% um that um externally<00:08:45.420> owned<00:08:45.779> accounts<00:08:46.140> so<00:08:46.200> the<00:08:46.560> default 00:08:46.790 --> 00:08:46.800 align:start position:0% externally owned accounts so the default 00:08:46.800 --> 00:08:48.730 align:start position:0% externally owned accounts so the default type<00:08:46.980> of<00:08:47.100> accounts<00:08:47.459> that<00:08:47.640> most<00:08:47.820> people<00:08:48.060> use<00:08:48.300> uh 00:08:48.730 --> 00:08:48.740 align:start position:0% type of accounts that most people use uh 00:08:48.740 --> 00:08:52.430 align:start position:0% type of accounts that most people use uh use<00:08:49.740> now<00:08:49.980> have<00:08:50.459> today<00:08:50.760> and<00:08:51.660> you<00:08:51.839> know<00:08:52.019> it<00:08:52.140> turns 00:08:52.430 --> 00:08:52.440 align:start position:0% use now have today and you know it turns 00:08:52.440 --> 00:08:55.670 align:start position:0% use now have today and you know it turns out<00:08:52.560> that<00:08:52.800> there's<00:08:53.040> actually<00:08:53.880> quite<00:08:54.560> a<00:08:55.560> bunch 00:08:55.670 --> 00:08:55.680 align:start position:0% out that there's actually quite a bunch 00:08:55.680 --> 00:08:57.889 align:start position:0% out that there's actually quite a bunch of<00:08:55.800> challenges<00:08:56.279> and<00:08:56.820> there<00:08:57.180> have<00:08:57.360> been<00:08:57.480> a 00:08:57.889 --> 00:08:57.899 align:start position:0% of challenges and there have been a 00:08:57.899 --> 00:08:59.630 align:start position:0% of challenges and there have been a whole<00:08:57.959> bunch<00:08:58.140> of<00:08:58.260> various<00:08:58.680> efforts<00:08:59.459> um<00:08:59.459> you 00:08:59.630 --> 00:08:59.640 align:start position:0% whole bunch of various efforts um you 00:08:59.640 --> 00:09:02.210 align:start position:0% whole bunch of various efforts um you know<00:08:59.700> there's<00:08:59.880> like<00:09:00.180> EIP<00:09:00.720> I<00:09:01.200> think<00:09:01.380> it<00:09:01.500> was<00:09:01.620> 86 00:09:02.210 --> 00:09:02.220 align:start position:0% know there's like EIP I think it was 86 00:09:02.220 --> 00:09:06.710 align:start position:0% know there's like EIP I think it was 86 and<00:09:02.580> then<00:09:02.760> 210<00:09:03.600> and<00:09:04.200> then<00:09:04.580> 29.38<00:09:05.580> and<00:09:06.240> then<00:09:06.480> you 00:09:06.710 --> 00:09:06.720 align:start position:0% and then 210 and then 29.38 and then you 00:09:06.720 --> 00:09:09.050 align:start position:0% and then 210 and then 29.38 and then you know<00:09:06.899> there's<00:09:07.140> a<00:09:07.920> kind<00:09:08.220> of<00:09:08.279> grab<00:09:08.580> bag<00:09:08.760> of 00:09:09.050 --> 00:09:09.060 align:start position:0% know there's a kind of grab bag of 00:09:09.060 --> 00:09:11.750 align:start position:0% know there's a kind of grab bag of different<00:09:09.480> proposals<00:09:10.500> um<00:09:10.500> separately<00:09:11.399> the 00:09:11.750 --> 00:09:11.760 align:start position:0% different proposals um separately the 00:09:11.760 --> 00:09:14.750 align:start position:0% different proposals um separately the kind<00:09:12.300> of<00:09:12.420> separately<00:09:13.380> the<00:09:13.740> the<00:09:13.920> strand<00:09:14.459> of 00:09:14.750 --> 00:09:14.760 align:start position:0% kind of separately the the strand of 00:09:14.760 --> 00:09:17.930 align:start position:0% kind of separately the the strand of kind<00:09:15.180> of<00:09:15.240> enabling<00:09:15.660> a<00:09:16.140> kind<00:09:16.560> of<00:09:16.680> Delegation<00:09:17.580> I 00:09:17.930 --> 00:09:17.940 align:start position:0% kind of enabling a kind of Delegation I 00:09:17.940 --> 00:09:20.449 align:start position:0% kind of enabling a kind of Delegation I might<00:09:18.180> which<00:09:18.660> has<00:09:19.040> basically<00:09:20.040> allowing 00:09:20.449 --> 00:09:20.459 align:start position:0% might which has basically allowing 00:09:20.459 --> 00:09:22.070 align:start position:0% might which has basically allowing people<00:09:20.640> to<00:09:20.880> pay<00:09:21.000> for<00:09:21.120> transactions<00:09:21.600> on<00:09:21.720> behalf 00:09:22.070 --> 00:09:22.080 align:start position:0% people to pay for transactions on behalf 00:09:22.080 --> 00:09:23.389 align:start position:0% people to pay for transactions on behalf of<00:09:22.140> other<00:09:22.320> people<00:09:22.500> which<00:09:22.740> I<00:09:22.860> think<00:09:22.980> is<00:09:23.100> part<00:09:23.279> of 00:09:23.389 --> 00:09:23.399 align:start position:0% of other people which I think is part of 00:09:23.399 --> 00:09:27.650 align:start position:0% of other people which I think is part of the<00:09:23.580> motivation<00:09:24.540> of<00:09:24.779> like<00:09:24.959> both<00:09:25.320> uh<00:09:26.180> 3074<00:09:27.180> and 00:09:27.650 --> 00:09:27.660 align:start position:0% the motivation of like both uh 3074 and 00:09:27.660 --> 00:09:30.949 align:start position:0% the motivation of like both uh 3074 and some<00:09:28.200> other<00:09:28.740> proposals<00:09:29.459> like<00:09:29.820> like 00:09:30.949 --> 00:09:30.959 align:start position:0% some other proposals like like 00:09:30.959 --> 00:09:33.470 align:start position:0% some other proposals like like that's<00:09:31.740> been<00:09:31.980> basically<00:09:32.940> there's<00:09:33.060> been<00:09:33.300> this 00:09:33.470 --> 00:09:33.480 align:start position:0% that's been basically there's been this 00:09:33.480 --> 00:09:35.210 align:start position:0% that's been basically there's been this you<00:09:33.720> know<00:09:33.779> really<00:09:34.140> long<00:09:34.380> strand<00:09:34.800> of<00:09:34.920> research 00:09:35.210 --> 00:09:35.220 align:start position:0% you know really long strand of research 00:09:35.220 --> 00:09:36.829 align:start position:0% you know really long strand of research of<00:09:35.399> trying<00:09:35.519> to<00:09:35.700> like<00:09:35.820> really<00:09:36.000> yeah<00:09:36.300> optimize 00:09:36.829 --> 00:09:36.839 align:start position:0% of trying to like really yeah optimize 00:09:36.839 --> 00:09:38.990 align:start position:0% of trying to like really yeah optimize and<00:09:37.019> figure<00:09:37.200> out<00:09:37.380> like<00:09:37.620> what<00:09:38.279> is<00:09:38.399> the<00:09:38.640> cleanest 00:09:38.990 --> 00:09:39.000 align:start position:0% and figure out like what is the cleanest 00:09:39.000 --> 00:09:40.610 align:start position:0% and figure out like what is the cleanest and<00:09:39.240> like<00:09:39.420> what<00:09:39.600> is<00:09:39.779> the<00:09:39.899> most<00:09:40.019> sensible<00:09:40.440> and 00:09:40.610 --> 00:09:40.620 align:start position:0% and like what is the most sensible and 00:09:40.620 --> 00:09:43.310 align:start position:0% and like what is the most sensible and secure<00:09:40.980> design<00:09:41.279> uh<00:09:42.120> to 00:09:43.310 --> 00:09:43.320 align:start position:0% secure design uh to 00:09:43.320 --> 00:09:44.750 align:start position:0% secure design uh to get<00:09:43.980> to 00:09:44.750 --> 00:09:44.760 align:start position:0% get to 00:09:44.760 --> 00:09:47.030 align:start position:0% get to um you<00:09:44.940> know<00:09:45.000> what<00:09:45.360> uh<00:09:45.720> actually<00:09:46.380> satisfying 00:09:47.030 --> 00:09:47.040 align:start position:0% um you know what uh actually satisfying 00:09:47.040 --> 00:09:48.350 align:start position:0% um you know what uh actually satisfying these<00:09:47.220> goals<00:09:47.519> and<00:09:47.700> you<00:09:47.880> know<00:09:48.000> that's<00:09:48.120> what 00:09:48.350 --> 00:09:48.360 align:start position:0% these goals and you know that's what 00:09:48.360 --> 00:09:50.150 align:start position:0% these goals and you know that's what we're<00:09:48.540> trying<00:09:49.019> to<00:09:49.260> implements<00:09:49.740> and<00:09:49.800> uh<00:09:49.980> roll 00:09:50.150 --> 00:09:50.160 align:start position:0% we're trying to implements and uh roll 00:09:50.160 --> 00:09:52.070 align:start position:0% we're trying to implements and uh roll out<00:09:50.339> today<00:09:50.519> I<00:09:51.120> want<00:09:51.240> you<00:09:51.420> to<00:09:51.540> check<00:09:51.899> my 00:09:52.070 --> 00:09:52.080 align:start position:0% out today I want you to check my 00:09:52.080 --> 00:09:53.150 align:start position:0% out today I want you to check my understanding<00:09:52.500> on<00:09:52.620> this<00:09:52.740> because<00:09:52.860> I<00:09:53.040> actually 00:09:53.150 --> 00:09:53.160 align:start position:0% understanding on this because I actually 00:09:53.160 --> 00:09:55.370 align:start position:0% understanding on this because I actually had<00:09:53.459> to<00:09:53.580> do<00:09:53.700> uh<00:09:54.120> some<00:09:54.360> homework<00:09:54.600> to<00:09:54.959> prepare 00:09:55.370 --> 00:09:55.380 align:start position:0% had to do uh some homework to prepare 00:09:55.380 --> 00:09:56.990 align:start position:0% had to do uh some homework to prepare for<00:09:55.500> this<00:09:55.680> mod<00:09:55.860> this<00:09:56.160> panel<00:09:56.459> because<00:09:56.580> this<00:09:56.880> is 00:09:56.990 --> 00:09:57.000 align:start position:0% for this mod this panel because this is 00:09:57.000 --> 00:09:59.329 align:start position:0% for this mod this panel because this is uh<00:09:57.240> technically<00:09:57.660> challenging<00:09:58.140> for<00:09:58.320> me<00:09:58.440> after 00:09:59.329 --> 00:09:59.339 align:start position:0% uh technically challenging for me after 00:09:59.339 --> 00:10:01.310 align:start position:0% uh technically challenging for me after kind<00:09:59.820> of<00:09:59.880> figuring<00:10:00.240> out<00:10:00.360> when<00:10:00.839> people<00:10:01.080> explain 00:10:01.310 --> 00:10:01.320 align:start position:0% kind of figuring out when people explain 00:10:01.320 --> 00:10:03.050 align:start position:0% kind of figuring out when people explain account<00:10:01.560> abstraction<00:10:02.040> they<00:10:02.279> were<00:10:02.399> like<00:10:02.519> oh<00:10:02.880> it 00:10:03.050 --> 00:10:03.060 align:start position:0% account abstraction they were like oh it 00:10:03.060 --> 00:10:04.790 align:start position:0% account abstraction they were like oh it enables<00:10:03.600> you<00:10:03.720> to<00:10:03.839> do<00:10:04.019> this<00:10:04.140> and<00:10:04.380> then<00:10:04.560> it 00:10:04.790 --> 00:10:04.800 align:start position:0% enables you to do this and then it 00:10:04.800 --> 00:10:06.889 align:start position:0% enables you to do this and then it unlocks<00:10:05.160> this<00:10:05.459> feature<00:10:05.820> and<00:10:06.000> it<00:10:06.300> lets<00:10:06.660> us<00:10:06.720> do 00:10:06.889 --> 00:10:06.899 align:start position:0% unlocks this feature and it lets us do 00:10:06.899 --> 00:10:09.410 align:start position:0% unlocks this feature and it lets us do that<00:10:07.279> but<00:10:08.279> it<00:10:08.459> kind<00:10:08.700> of<00:10:08.760> feels<00:10:09.000> like<00:10:09.120> we're 00:10:09.410 --> 00:10:09.420 align:start position:0% that but it kind of feels like we're 00:10:09.420 --> 00:10:11.810 align:start position:0% that but it kind of feels like we're feeling<00:10:09.720> uh<00:10:10.260> that<00:10:10.440> elephant<00:10:11.339> metaphor<00:10:11.640> where 00:10:11.810 --> 00:10:11.820 align:start position:0% feeling uh that elephant metaphor where 00:10:11.820 --> 00:10:13.070 align:start position:0% feeling uh that elephant metaphor where somebody's<00:10:12.180> feeling<00:10:12.360> the<00:10:12.540> tail<00:10:12.720> and<00:10:12.959> it's 00:10:13.070 --> 00:10:13.080 align:start position:0% somebody's feeling the tail and it's 00:10:13.080 --> 00:10:14.210 align:start position:0% somebody's feeling the tail and it's like<00:10:13.200> a<00:10:13.320> snake<00:10:13.500> and<00:10:13.620> somebody's<00:10:13.920> feeling<00:10:14.040> the 00:10:14.210 --> 00:10:14.220 align:start position:0% like a snake and somebody's feeling the 00:10:14.220 --> 00:10:15.110 align:start position:0% like a snake and somebody's feeling the leg<00:10:14.339> it's<00:10:14.519> like<00:10:14.580> oh<00:10:14.700> it's<00:10:14.820> like<00:10:14.940> a<00:10:15.000> tree 00:10:15.110 --> 00:10:15.120 align:start position:0% leg it's like oh it's like a tree 00:10:15.120 --> 00:10:16.730 align:start position:0% leg it's like oh it's like a tree without<00:10:15.540> actually<00:10:15.839> seeing<00:10:16.260> the<00:10:16.380> whole<00:10:16.560> thing 00:10:16.730 --> 00:10:16.740 align:start position:0% without actually seeing the whole thing 00:10:16.740 --> 00:10:18.769 align:start position:0% without actually seeing the whole thing so<00:10:17.700> I<00:10:17.820> want<00:10:17.940> you<00:10:18.000> to<00:10:18.120> check<00:10:18.300> check<00:10:18.600> this 00:10:18.769 --> 00:10:18.779 align:start position:0% so I want you to check check this 00:10:18.779 --> 00:10:20.150 align:start position:0% so I want you to check check this metaphor<00:10:19.140> with<00:10:19.320> me 00:10:20.150 --> 00:10:20.160 align:start position:0% metaphor with me 00:10:20.160 --> 00:10:21.410 align:start position:0% metaphor with me um<00:10:20.220> an<00:10:20.459> externally<00:10:20.820> owned<00:10:21.060> account<00:10:21.180> there's 00:10:21.410 --> 00:10:21.420 align:start position:0% um an externally owned account there's 00:10:21.420 --> 00:10:23.030 align:start position:0% um an externally owned account there's only<00:10:21.600> two<00:10:21.779> types<00:10:22.140> of<00:10:22.200> accounts<00:10:22.560> on<00:10:22.680> ethereum 00:10:23.030 --> 00:10:23.040 align:start position:0% only two types of accounts on ethereum 00:10:23.040 --> 00:10:24.290 align:start position:0% only two types of accounts on ethereum you<00:10:23.339> have<00:10:23.459> an<00:10:23.580> externally<00:10:23.880> owned<00:10:24.180> account 00:10:24.290 --> 00:10:24.300 align:start position:0% you have an externally owned account 00:10:24.300 --> 00:10:25.850 align:start position:0% you have an externally owned account which<00:10:24.600> is<00:10:24.720> probably<00:10:24.899> what<00:10:25.140> you<00:10:25.260> use<00:10:25.440> when<00:10:25.740> you 00:10:25.850 --> 00:10:25.860 align:start position:0% which is probably what you use when you 00:10:25.860 --> 00:10:28.250 align:start position:0% which is probably what you use when you like<00:10:26.040> buy<00:10:26.279> your<00:10:26.399> nfts<00:10:26.940> you<00:10:27.240> have<00:10:27.480> a<00:10:27.660> private 00:10:28.250 --> 00:10:28.260 align:start position:0% like buy your nfts you have a private 00:10:28.260 --> 00:10:29.870 align:start position:0% like buy your nfts you have a private key<00:10:28.440> and<00:10:28.680> it<00:10:28.800> unlocks<00:10:29.160> a<00:10:29.279> wallet<00:10:29.519> and<00:10:29.820> then 00:10:29.870 --> 00:10:29.880 align:start position:0% key and it unlocks a wallet and then 00:10:29.880 --> 00:10:32.030 align:start position:0% key and it unlocks a wallet and then there's<00:10:30.060> a<00:10:30.240> smart<00:10:30.420> contract<00:10:30.839> and<00:10:31.800> account 00:10:32.030 --> 00:10:32.040 align:start position:0% there's a smart contract and account 00:10:32.040 --> 00:10:34.550 align:start position:0% there's a smart contract and account abstraction<00:10:32.580> is<00:10:33.000> putting<00:10:33.540> what<00:10:33.779> we<00:10:34.019> currently 00:10:34.550 --> 00:10:34.560 align:start position:0% abstraction is putting what we currently 00:10:34.560 --> 00:10:36.290 align:start position:0% abstraction is putting what we currently use<00:10:34.800> which<00:10:35.100> is<00:10:35.220> you<00:10:35.459> know<00:10:35.519> our<00:10:35.700> Ledger<00:10:36.000> or<00:10:36.180> our 00:10:36.290 --> 00:10:36.300 align:start position:0% use which is you know our Ledger or our 00:10:36.300 --> 00:10:38.090 align:start position:0% use which is you know our Ledger or our private<00:10:36.600> keys<00:10:36.899> that<00:10:37.200> unlocks<00:10:37.620> a<00:10:37.740> specific 00:10:38.090 --> 00:10:38.100 align:start position:0% private keys that unlocks a specific 00:10:38.100 --> 00:10:40.130 align:start position:0% private keys that unlocks a specific wallet<00:10:38.519> and<00:10:38.820> it<00:10:38.940> makes<00:10:39.120> our<00:10:39.300> that<00:10:39.540> wallet<00:10:39.959> a 00:10:40.130 --> 00:10:40.140 align:start position:0% wallet and it makes our that wallet a 00:10:40.140 --> 00:10:41.630 align:start position:0% wallet and it makes our that wallet a smart<00:10:40.260> contract<00:10:40.680> which<00:10:40.860> more<00:10:41.160> programmable 00:10:41.630 --> 00:10:41.640 align:start position:0% smart contract which more programmable 00:10:41.640 --> 00:10:45.170 align:start position:0% smart contract which more programmable my<00:10:42.060> mental<00:10:42.360> model<00:10:42.480> for<00:10:42.720> this<00:10:42.899> is<00:10:43.260> that<00:10:44.640> um 00:10:45.170 --> 00:10:45.180 align:start position:0% my mental model for this is that um 00:10:45.180 --> 00:10:47.389 align:start position:0% my mental model for this is that um a<00:10:45.779> smart<00:10:45.959> a<00:10:46.260> account<00:10:46.500> abstraction<00:10:46.980> is<00:10:47.220> like 00:10:47.389 --> 00:10:47.399 align:start position:0% a smart a account abstraction is like 00:10:47.399 --> 00:10:49.790 align:start position:0% a smart a account abstraction is like putting<00:10:47.760> a<00:10:48.060> chip<00:10:48.240> into<00:10:48.720> a<00:10:48.959> wallet<00:10:49.260> and<00:10:49.560> what<00:10:49.740> I 00:10:49.790 --> 00:10:49.800 align:start position:0% putting a chip into a wallet and what I 00:10:49.800 --> 00:10:51.110 align:start position:0% putting a chip into a wallet and what I mean<00:10:49.920> by<00:10:50.040> that<00:10:50.220> is<00:10:50.459> that<00:10:50.640> we<00:10:50.820> have<00:10:50.940> like 00:10:51.110 --> 00:10:51.120 align:start position:0% mean by that is that we have like 00:10:51.120 --> 00:10:52.910 align:start position:0% mean by that is that we have like Bitcoin<00:10:51.660> which<00:10:51.899> the<00:10:52.140> meme<00:10:52.260> is<00:10:52.440> like<00:10:52.560> Bitcoin 00:10:52.910 --> 00:10:52.920 align:start position:0% Bitcoin which the meme is like Bitcoin 00:10:52.920 --> 00:10:54.410 align:start position:0% Bitcoin which the meme is like Bitcoin is<00:10:52.980> a<00:10:53.100> calculator<00:10:53.279> ethereum<00:10:53.880> is<00:10:53.940> a<00:10:54.120> smartphone 00:10:54.410 --> 00:10:54.420 align:start position:0% is a calculator ethereum is a smartphone 00:10:54.420 --> 00:10:56.870 align:start position:0% is a calculator ethereum is a smartphone and<00:10:55.079> I<00:10:55.200> kind<00:10:55.320> of<00:10:55.440> apply<00:10:55.680> that<00:10:55.920> to<00:10:56.220> externally 00:10:56.870 --> 00:10:56.880 align:start position:0% and I kind of apply that to externally 00:10:56.880 --> 00:10:59.210 align:start position:0% and I kind of apply that to externally owned<00:10:57.240> accounts<00:10:57.600> and<00:10:58.079> uh<00:10:58.500> a<00:10:58.740> smart<00:10:58.860> contract 00:10:59.210 --> 00:10:59.220 align:start position:0% owned accounts and uh a smart contract 00:10:59.220 --> 00:11:00.650 align:start position:0% owned accounts and uh a smart contract wallets<00:10:59.519> or<00:10:59.700> account<00:10:59.820> extraction<00:11:00.300> wallets 00:11:00.650 --> 00:11:00.660 align:start position:0% wallets or account extraction wallets 00:11:00.660 --> 00:11:02.569 align:start position:0% wallets or account extraction wallets where<00:11:00.899> it's<00:11:01.440> externally<00:11:01.920> owned<00:11:02.220> accounts<00:11:02.459> are 00:11:02.569 --> 00:11:02.579 align:start position:0% where it's externally owned accounts are 00:11:02.579 --> 00:11:04.130 align:start position:0% where it's externally owned accounts are like<00:11:02.700> Bitcoin<00:11:03.120> they<00:11:03.360> don't<00:11:03.540> really<00:11:03.660> do<00:11:03.839> too 00:11:04.130 --> 00:11:04.140 align:start position:0% like Bitcoin they don't really do too 00:11:04.140 --> 00:11:07.069 align:start position:0% like Bitcoin they don't really do too much<00:11:04.459> and<00:11:05.459> then<00:11:05.579> externally<00:11:06.420> and<00:11:06.899> then 00:11:07.069 --> 00:11:07.079 align:start position:0% much and then externally and then 00:11:07.079 --> 00:11:09.050 align:start position:0% much and then externally and then account<00:11:07.500> extraction<00:11:07.920> wallets<00:11:08.459> are<00:11:08.820> like 00:11:09.050 --> 00:11:09.060 align:start position:0% account extraction wallets are like 00:11:09.060 --> 00:11:11.090 align:start position:0% account extraction wallets are like ethereum<00:11:09.899> where<00:11:10.079> there's<00:11:10.260> a<00:11:10.440> chip<00:11:10.560> in<00:11:10.680> it<00:11:10.860> is 00:11:11.090 --> 00:11:11.100 align:start position:0% ethereum where there's a chip in it is 00:11:11.100 --> 00:11:12.889 align:start position:0% ethereum where there's a chip in it is that<00:11:11.339> metaphor<00:11:11.700> land<00:11:11.880> yeah<00:11:12.300> no<00:11:12.480> no<00:11:12.540> that's<00:11:12.779> a 00:11:12.889 --> 00:11:12.899 align:start position:0% that metaphor land yeah no no that's a 00:11:12.899 --> 00:11:14.329 align:start position:0% that metaphor land yeah no no that's a that's<00:11:13.140> a<00:11:13.260> really<00:11:13.320> fun<00:11:13.500> metaphor<00:11:13.860> I<00:11:14.040> like<00:11:14.160> it 00:11:14.329 --> 00:11:14.339 align:start position:0% that's a really fun metaphor I like it 00:11:14.339 --> 00:11:16.130 align:start position:0% that's a really fun metaphor I like it is<00:11:14.700> there<00:11:14.880> anything<00:11:15.000> incomplete<00:11:15.720> about<00:11:15.899> that 00:11:16.130 --> 00:11:16.140 align:start position:0% is there anything incomplete about that 00:11:16.140 --> 00:11:17.569 align:start position:0% is there anything incomplete about that and<00:11:16.320> and<00:11:16.500> Matt<00:11:16.680> I<00:11:16.920> want<00:11:17.040> to<00:11:17.100> throw<00:11:17.160> this<00:11:17.339> one<00:11:17.459> to 00:11:17.569 --> 00:11:17.579 align:start position:0% and and Matt I want to throw this one to 00:11:17.579 --> 00:11:19.730 align:start position:0% and and Matt I want to throw this one to you<00:11:17.760> uh<00:11:18.360> where<00:11:18.540> you<00:11:18.720> were<00:11:18.839> talking<00:11:18.959> about 00:11:19.730 --> 00:11:19.740 align:start position:0% you uh where you were talking about 00:11:19.740 --> 00:11:22.670 align:start position:0% you uh where you were talking about um<00:11:20.240> validation<00:11:21.240> abstraction<00:11:21.959> can<00:11:22.560> you 00:11:22.670 --> 00:11:22.680 align:start position:0% um validation abstraction can you 00:11:22.680 --> 00:11:24.410 align:start position:0% um validation abstraction can you connect<00:11:22.800> these<00:11:23.160> two<00:11:23.279> metaphors<00:11:23.700> how<00:11:23.940> do<00:11:24.240> those 00:11:24.410 --> 00:11:24.420 align:start position:0% connect these two metaphors how do those 00:11:24.420 --> 00:11:27.710 align:start position:0% connect these two metaphors how do those things<00:11:24.600> relate<00:11:25.500> right<00:11:26.160> so<00:11:26.519> I<00:11:26.700> think<00:11:26.940> you<00:11:27.600> know 00:11:27.710 --> 00:11:27.720 align:start position:0% things relate right so I think you know 00:11:27.720 --> 00:11:29.449 align:start position:0% things relate right so I think you know if<00:11:28.079> you're<00:11:28.200> thinking<00:11:28.500> of<00:11:28.620> the<00:11:28.740> con<00:11:28.980> the 00:11:29.449 --> 00:11:29.459 align:start position:0% if you're thinking of the con the 00:11:29.459 --> 00:11:31.009 align:start position:0% if you're thinking of the con the concept<00:11:29.760> of<00:11:29.880> like<00:11:30.060> putting<00:11:30.300> a<00:11:30.420> chip<00:11:30.540> into<00:11:30.779> a 00:11:31.009 --> 00:11:31.019 align:start position:0% concept of like putting a chip into a 00:11:31.019 --> 00:11:33.650 align:start position:0% concept of like putting a chip into a wallet<00:11:31.320> there's<00:11:32.100> like<00:11:32.399> two<00:11:32.700> important<00:11:33.180> pieces 00:11:33.650 --> 00:11:33.660 align:start position:0% wallet there's like two important pieces 00:11:33.660 --> 00:11:35.810 align:start position:0% wallet there's like two important pieces that<00:11:33.839> the<00:11:34.019> wall<00:11:34.140> is<00:11:34.380> doing<00:11:34.560> and<00:11:35.399> the<00:11:35.640> way<00:11:35.700> that 00:11:35.810 --> 00:11:35.820 align:start position:0% that the wall is doing and the way that 00:11:35.820 --> 00:11:37.850 align:start position:0% that the wall is doing and the way that I<00:11:36.000> think<00:11:36.180> about<00:11:36.300> it<00:11:36.540> is<00:11:36.660> that<00:11:36.839> the<00:11:37.079> chip<00:11:37.260> is 00:11:37.850 --> 00:11:37.860 align:start position:0% I think about it is that the chip is 00:11:37.860 --> 00:11:39.949 align:start position:0% I think about it is that the chip is dealing<00:11:38.160> with<00:11:38.279> the<00:11:38.459> validation<00:11:38.940> logic<00:11:39.420> like<00:11:39.720> I 00:11:39.949 --> 00:11:39.959 align:start position:0% dealing with the validation logic like I 00:11:39.959 --> 00:11:42.710 align:start position:0% dealing with the validation logic like I mentioned<00:11:40.380> when<00:11:40.800> I<00:11:40.920> spoke<00:11:41.279> a<00:11:41.459> minute<00:11:41.700> ago<00:11:41.940> uh 00:11:42.710 --> 00:11:42.720 align:start position:0% mentioned when I spoke a minute ago uh 00:11:42.720 --> 00:11:44.930 align:start position:0% mentioned when I spoke a minute ago uh it's<00:11:42.899> determining<00:11:43.440> like<00:11:43.560> is<00:11:43.920> this<00:11:44.279> uh<00:11:44.700> message 00:11:44.930 --> 00:11:44.940 align:start position:0% it's determining like is this uh message 00:11:44.940 --> 00:11:46.569 align:start position:0% it's determining like is this uh message and<00:11:45.240> signature<00:11:45.660> that's<00:11:45.839> coming<00:11:46.019> from<00:11:46.260> account 00:11:46.569 --> 00:11:46.579 align:start position:0% and signature that's coming from account 00:11:46.579 --> 00:11:49.730 align:start position:0% and signature that's coming from account valid<00:11:47.579> in<00:11:47.760> the<00:11:47.940> context<00:11:48.180> of<00:11:48.420> this<00:11:48.600> account<00:11:48.779> you 00:11:49.730 --> 00:11:49.740 align:start position:0% valid in the context of this account you 00:11:49.740 --> 00:11:51.110 align:start position:0% valid in the context of this account you could<00:11:49.800> also<00:11:50.040> Imagine<00:11:50.220> the<00:11:50.519> chip<00:11:50.700> did<00:11:50.940> other 00:11:51.110 --> 00:11:51.120 align:start position:0% could also Imagine the chip did other 00:11:51.120 --> 00:11:53.750 align:start position:0% could also Imagine the chip did other things<00:11:51.440> uh<00:11:52.440> after<00:11:52.860> you<00:11:53.100> do<00:11:53.220> the<00:11:53.339> validation 00:11:53.750 --> 00:11:53.760 align:start position:0% things uh after you do the validation 00:11:53.760 --> 00:11:54.829 align:start position:0% things uh after you do the validation you<00:11:54.000> would<00:11:54.060> have<00:11:54.180> like<00:11:54.360> the<00:11:54.480> execution 00:11:54.829 --> 00:11:54.839 align:start position:0% you would have like the execution 00:11:54.839 --> 00:11:57.050 align:start position:0% you would have like the execution portion<00:11:55.320> and<00:11:55.500> so<00:11:55.740> a<00:11:56.519> lot<00:11:56.640> of<00:11:56.640> times<00:11:56.820> when<00:11:56.940> we 00:11:57.050 --> 00:11:57.060 align:start position:0% portion and so a lot of times when we 00:11:57.060 --> 00:11:58.370 align:start position:0% portion and so a lot of times when we think<00:11:57.180> about<00:11:57.360> accounts<00:11:57.779> abstraction<00:11:58.079> as<00:11:58.260> like 00:11:58.370 --> 00:11:58.380 align:start position:0% think about accounts abstraction as like 00:11:58.380 --> 00:12:00.290 align:start position:0% think about accounts abstraction as like a<00:11:58.500> general<00:11:58.620> concept<00:11:59.040> we<00:11:59.220> also<00:11:59.459> think<00:11:59.640> it's 00:12:00.290 --> 00:12:00.300 align:start position:0% a general concept we also think it's 00:12:00.300 --> 00:12:02.150 align:start position:0% a general concept we also think it's doing<00:12:00.540> a<00:12:00.779> lot<00:12:00.839> of<00:12:01.019> other<00:12:01.140> stuff<00:12:01.440> now<00:12:01.740> and<00:12:01.980> so 00:12:02.150 --> 00:12:02.160 align:start position:0% doing a lot of other stuff now and so 00:12:02.160 --> 00:12:04.730 align:start position:0% doing a lot of other stuff now and so that<00:12:02.399> chip<00:12:02.640> is<00:12:03.000> now<00:12:03.180> determined<00:12:04.019> like 00:12:04.730 --> 00:12:04.740 align:start position:0% that chip is now determined like 00:12:04.740 --> 00:12:06.590 align:start position:0% that chip is now determined like I<00:12:05.279> want<00:12:05.459> to<00:12:05.579> send<00:12:05.640> a<00:12:05.820> bunch<00:12:05.940> of<00:12:06.060> transactions 00:12:06.590 --> 00:12:06.600 align:start position:0% I want to send a bunch of transactions 00:12:06.600 --> 00:12:08.090 align:start position:0% I want to send a bunch of transactions from<00:12:06.779> this<00:12:06.959> account<00:12:07.140> all<00:12:07.440> or<00:12:07.620> I<00:12:07.800> want<00:12:07.920> to<00:12:07.980> send 00:12:08.090 --> 00:12:08.100 align:start position:0% from this account all or I want to send 00:12:08.100 --> 00:12:09.290 align:start position:0% from this account all or I want to send a<00:12:08.220> bunch<00:12:08.339> of<00:12:08.399> calls<00:12:08.640> from<00:12:08.820> this<00:12:08.940> transaction 00:12:09.290 --> 00:12:09.300 align:start position:0% a bunch of calls from this transaction 00:12:09.300 --> 00:12:10.910 align:start position:0% a bunch of calls from this transaction or<00:12:09.839> from<00:12:10.019> this<00:12:10.200> account's<00:12:10.500> all-in-one 00:12:10.910 --> 00:12:10.920 align:start position:0% or from this account's all-in-one 00:12:10.920 --> 00:12:13.250 align:start position:0% or from this account's all-in-one transaction<00:12:11.220> or<00:12:11.579> I<00:12:11.700> want<00:12:11.880> to<00:12:12.000> recover<00:12:12.300> uh 00:12:13.250 --> 00:12:13.260 align:start position:0% transaction or I want to recover uh 00:12:13.260 --> 00:12:14.930 align:start position:0% transaction or I want to recover uh using<00:12:13.740> like<00:12:13.920> some<00:12:14.100> social<00:12:14.279> Recovery<00:12:14.760> Group 00:12:14.930 --> 00:12:14.940 align:start position:0% using like some social Recovery Group 00:12:14.940 --> 00:12:16.009 align:start position:0% using like some social Recovery Group that<00:12:15.120> I've<00:12:15.240> come<00:12:15.360> up<00:12:15.420> with<00:12:15.540> so<00:12:15.720> that's<00:12:15.839> like 00:12:16.009 --> 00:12:16.019 align:start position:0% that I've come up with so that's like 00:12:16.019 --> 00:12:17.569 align:start position:0% that I've come up with so that's like another<00:12:16.140> part<00:12:16.440> of<00:12:16.560> the<00:12:16.620> chip 00:12:17.569 --> 00:12:17.579 align:start position:0% another part of the chip 00:12:17.579 --> 00:12:19.069 align:start position:0% another part of the chip beautiful<00:12:18.000> beautiful<00:12:18.420> and<00:12:18.660> I<00:12:18.839> want<00:12:18.899> to<00:12:18.959> throw 00:12:19.069 --> 00:12:19.079 align:start position:0% beautiful beautiful and I want to throw 00:12:19.079 --> 00:12:20.930 align:start position:0% beautiful beautiful and I want to throw this<00:12:19.260> one<00:12:19.380> to<00:12:19.440> Julian<00:12:20.040> as<00:12:20.459> somebody<00:12:20.700> who's 00:12:20.930 --> 00:12:20.940 align:start position:0% this one to Julian as somebody who's 00:12:20.940 --> 00:12:22.250 align:start position:0% this one to Julian as somebody who's responsible<00:12:21.360> for<00:12:21.600> actually<00:12:21.720> putting<00:12:22.079> some 00:12:22.250 --> 00:12:22.260 align:start position:0% responsible for actually putting some 00:12:22.260 --> 00:12:23.509 align:start position:0% responsible for actually putting some smart<00:12:22.380> contract<00:12:22.740> while<00:12:22.980> it's<00:12:23.100> in<00:12:23.279> people's 00:12:23.509 --> 00:12:23.519 align:start position:0% smart contract while it's in people's 00:12:23.519 --> 00:12:25.910 align:start position:0% smart contract while it's in people's hands<00:12:23.820> thank<00:12:24.240> you<00:12:24.360> for<00:12:24.480> your<00:12:24.600> service<00:12:24.839> how<00:12:25.740> do 00:12:25.910 --> 00:12:25.920 align:start position:0% hands thank you for your service how do 00:12:25.920 --> 00:12:27.590 align:start position:0% hands thank you for your service how do you<00:12:26.040> think<00:12:26.220> this<00:12:26.760> is<00:12:26.880> going<00:12:27.000> to<00:12:27.120> get<00:12:27.240> rolled 00:12:27.590 --> 00:12:27.600 align:start position:0% you think this is going to get rolled 00:12:27.600 --> 00:12:29.449 align:start position:0% you think this is going to get rolled out<00:12:27.720> uh<00:12:28.440> people<00:12:28.620> in<00:12:28.800> general<00:12:28.920> and<00:12:29.160> we'll<00:12:29.279> get 00:12:29.449 --> 00:12:29.459 align:start position:0% out uh people in general and we'll get 00:12:29.459 --> 00:12:30.769 align:start position:0% out uh people in general and we'll get into<00:12:29.519> the<00:12:29.700> topic<00:12:29.880> as<00:12:30.000> to<00:12:30.180> why<00:12:30.360> people<00:12:30.540> think 00:12:30.769 --> 00:12:30.779 align:start position:0% into the topic as to why people think 00:12:30.779 --> 00:12:34.009 align:start position:0% into the topic as to why people think that<00:12:31.140> everyone<00:12:31.620> will<00:12:32.040> have<00:12:32.339> a<00:12:32.940> a<00:12:33.360> smart 00:12:34.009 --> 00:12:34.019 align:start position:0% that everyone will have a a smart 00:12:34.019 --> 00:12:35.449 align:start position:0% that everyone will have a a smart contract<00:12:34.320> wallet<00:12:34.620> rather<00:12:34.980> than<00:12:35.100> externally 00:12:35.449 --> 00:12:35.459 align:start position:0% contract wallet rather than externally 00:12:35.459 --> 00:12:36.769 align:start position:0% contract wallet rather than externally owned<00:12:35.760> account<00:12:35.820> in<00:12:36.000> the<00:12:36.060> future<00:12:36.180> but<00:12:36.600> what's 00:12:36.769 --> 00:12:36.779 align:start position:0% owned account in the future but what's 00:12:36.779 --> 00:12:38.630 align:start position:0% owned account in the future but what's like<00:12:37.260> what's<00:12:37.560> your<00:12:37.740> idea<00:12:37.980> for<00:12:38.100> how<00:12:38.279> this<00:12:38.399> gets 00:12:38.630 --> 00:12:38.640 align:start position:0% like what's your idea for how this gets 00:12:38.640 --> 00:12:40.069 align:start position:0% like what's your idea for how this gets rolled<00:12:38.820> out<00:12:38.940> into<00:12:39.180> how<00:12:39.600> do<00:12:39.720> we<00:12:39.839> replace 00:12:40.069 --> 00:12:40.079 align:start position:0% rolled out into how do we replace 00:12:40.079 --> 00:12:42.829 align:start position:0% rolled out into how do we replace private<00:12:40.800> keys<00:12:41.100> with<00:12:41.519> externally<00:12:42.060> uh<00:12:42.540> with 00:12:42.829 --> 00:12:42.839 align:start position:0% private keys with externally uh with 00:12:42.839 --> 00:12:45.050 align:start position:0% private keys with externally uh with account<00:12:43.079> extracted<00:12:43.680> wallets 00:12:45.050 --> 00:12:45.060 align:start position:0% account extracted wallets 00:12:45.060 --> 00:12:46.910 align:start position:0% account extracted wallets so<00:12:45.540> that's<00:12:45.720> that's<00:12:45.899> a<00:12:46.079> very<00:12:46.200> good<00:12:46.320> question<00:12:46.500> I 00:12:46.910 --> 00:12:46.920 align:start position:0% so that's that's a very good question I 00:12:46.920 --> 00:12:49.550 align:start position:0% so that's that's a very good question I think<00:12:47.100> the<00:12:47.940> the<00:12:48.120> way<00:12:48.360> I<00:12:48.540> see<00:12:48.720> it<00:12:48.899> is<00:12:49.200> that<00:12:49.380> I 00:12:49.550 --> 00:12:49.560 align:start position:0% think the the way I see it is that I 00:12:49.560 --> 00:12:50.930 align:start position:0% think the the way I see it is that I think<00:12:49.680> I<00:12:49.860> mean<00:12:49.980> vitalik<00:12:50.459> has<00:12:50.579> been<00:12:50.700> pushing 00:12:50.930 --> 00:12:50.940 align:start position:0% think I mean vitalik has been pushing 00:12:50.940 --> 00:12:52.670 align:start position:0% think I mean vitalik has been pushing for<00:12:51.120> a<00:12:51.240> kind<00:12:51.360> of<00:12:51.480> abstraction<00:12:51.779> for<00:12:52.440> a<00:12:52.560> long 00:12:52.670 --> 00:12:52.680 align:start position:0% for a kind of abstraction for a long 00:12:52.680 --> 00:12:55.310 align:start position:0% for a kind of abstraction for a long time<00:12:52.860> and<00:12:53.700> every<00:12:53.940> single<00:12:54.240> proposal<00:12:54.779> has<00:12:55.019> some 00:12:55.310 --> 00:12:55.320 align:start position:0% time and every single proposal has some 00:12:55.320 --> 00:12:56.810 align:start position:0% time and every single proposal has some you<00:12:55.500> know<00:12:55.620> enabled<00:12:56.100> some<00:12:56.279> of<00:12:56.399> the<00:12:56.459> features<00:12:56.700> of 00:12:56.810 --> 00:12:56.820 align:start position:0% you know enabled some of the features of 00:12:56.820 --> 00:12:58.370 align:start position:0% you know enabled some of the features of account<00:12:57.000> abstraction<00:12:57.420> but<00:12:57.660> none<00:12:57.959> of<00:12:58.079> them<00:12:58.139> I 00:12:58.370 --> 00:12:58.380 align:start position:0% account abstraction but none of them I 00:12:58.380 --> 00:13:00.590 align:start position:0% account abstraction but none of them I think<00:12:58.500> is<00:12:58.620> the<00:12:58.860> end<00:12:59.100> game<00:12:59.300> uh<00:13:00.300> and<00:13:00.420> and 00:13:00.590 --> 00:13:00.600 align:start position:0% think is the end game uh and and 00:13:00.600 --> 00:13:02.269 align:start position:0% think is the end game uh and and personally<00:13:00.959> for<00:13:01.260> example<00:13:01.500> I<00:13:01.740> like<00:13:01.860> the<00:13:02.100> last 00:13:02.269 --> 00:13:02.279 align:start position:0% personally for example I like the last 00:13:02.279 --> 00:13:05.090 align:start position:0% personally for example I like the last proposal<00:13:02.720> 4337<00:13:03.720> but<00:13:04.380> the<00:13:04.560> problem<00:13:04.680> is<00:13:04.860> that 00:13:05.090 --> 00:13:05.100 align:start position:0% proposal 4337 but the problem is that 00:13:05.100 --> 00:13:07.069 align:start position:0% proposal 4337 but the problem is that it's<00:13:05.279> still<00:13:05.519> it's<00:13:05.880> at<00:13:06.120> the<00:13:06.300> application<00:13:06.660> layer 00:13:07.069 --> 00:13:07.079 align:start position:0% it's still it's at the application layer 00:13:07.079 --> 00:13:09.470 align:start position:0% it's still it's at the application layer so<00:13:07.380> we<00:13:07.740> are<00:13:07.920> not<00:13:08.160> fixing<00:13:08.760> what<00:13:08.940> I<00:13:09.120> think<00:13:09.180> is<00:13:09.300> the 00:13:09.470 --> 00:13:09.480 align:start position:0% so we are not fixing what I think is the 00:13:09.480 --> 00:13:11.750 align:start position:0% so we are not fixing what I think is the real<00:13:09.600> problem<00:13:09.839> is<00:13:10.139> getting<00:13:10.440> rid<00:13:10.740> of<00:13:10.920> of<00:13:11.220> voas 00:13:11.750 --> 00:13:11.760 align:start position:0% real problem is getting rid of of voas 00:13:11.760 --> 00:13:13.550 align:start position:0% real problem is getting rid of of voas and<00:13:12.360> I<00:13:12.420> understand<00:13:12.600> that<00:13:12.899> on<00:13:13.079> ethereum 00:13:13.550 --> 00:13:13.560 align:start position:0% and I understand that on ethereum 00:13:13.560 --> 00:13:15.829 align:start position:0% and I understand that on ethereum there's<00:13:13.860> so<00:13:14.100> much<00:13:14.220> at<00:13:14.459> stake<00:13:14.820> that<00:13:15.240> such<00:13:15.540> a 00:13:15.829 --> 00:13:15.839 align:start position:0% there's so much at stake that such a 00:13:15.839 --> 00:13:18.230 align:start position:0% there's so much at stake that such a drastic<00:13:16.200> change<00:13:16.620> will<00:13:17.279> take<00:13:17.519> time<00:13:17.700> I<00:13:18.120> think 00:13:18.230 --> 00:13:18.240 align:start position:0% drastic change will take time I think 00:13:18.240 --> 00:13:19.490 align:start position:0% drastic change will take time I think people<00:13:18.420> are<00:13:18.660> recognizing<00:13:19.139> that<00:13:19.260> account 00:13:19.490 --> 00:13:19.500 align:start position:0% people are recognizing that account 00:13:19.500 --> 00:13:21.110 align:start position:0% people are recognizing that account abstraction<00:13:19.920> is<00:13:20.220> the<00:13:20.399> future<00:13:20.579> I<00:13:20.820> think<00:13:20.940> it 00:13:21.110 --> 00:13:21.120 align:start position:0% abstraction is the future I think it 00:13:21.120 --> 00:13:22.970 align:start position:0% abstraction is the future I think it will<00:13:21.300> happen<00:13:21.480> but<00:13:22.019> on<00:13:22.200> ethereum<00:13:22.620> I<00:13:22.800> think<00:13:22.860> it 00:13:22.970 --> 00:13:22.980 align:start position:0% will happen but on ethereum I think it 00:13:22.980 --> 00:13:25.069 align:start position:0% will happen but on ethereum I think it will<00:13:23.100> take<00:13:23.279> time<00:13:23.519> what<00:13:24.360> we've<00:13:24.540> been<00:13:24.720> pushing 00:13:25.069 --> 00:13:25.079 align:start position:0% will take time what we've been pushing 00:13:25.079 --> 00:13:26.569 align:start position:0% will take time what we've been pushing at<00:13:25.380> Urgent<00:13:25.560> is<00:13:25.740> that<00:13:25.860> I<00:13:25.980> think<00:13:26.160> now<00:13:26.279> we<00:13:26.459> are 00:13:26.569 --> 00:13:26.579 align:start position:0% at Urgent is that I think now we are 00:13:26.579 --> 00:13:28.610 align:start position:0% at Urgent is that I think now we are seeing<00:13:26.760> the<00:13:26.940> emergence<00:13:27.480> of<00:13:27.600> layer<00:13:27.899> twos<00:13:28.200> and<00:13:28.500> I 00:13:28.610 --> 00:13:28.620 align:start position:0% seeing the emergence of layer twos and I 00:13:28.620 --> 00:13:29.810 align:start position:0% seeing the emergence of layer twos and I think<00:13:28.680> layer<00:13:28.980> 2's<00:13:29.339> are<00:13:29.399> an<00:13:29.519> amazing 00:13:29.810 --> 00:13:29.820 align:start position:0% think layer 2's are an amazing 00:13:29.820 --> 00:13:32.990 align:start position:0% think layer 2's are an amazing opportunity<00:13:30.360> to<00:13:30.720> actually<00:13:30.899> try<00:13:31.380> to<00:13:31.740> test<00:13:32.579> some 00:13:32.990 --> 00:13:33.000 align:start position:0% opportunity to actually try to test some 00:13:33.000 --> 00:13:34.490 align:start position:0% opportunity to actually try to test some of<00:13:33.120> these<00:13:33.300> you<00:13:33.480> know<00:13:33.600> and<00:13:33.720> try<00:13:33.899> to<00:13:33.959> fix<00:13:34.139> some<00:13:34.440> of 00:13:34.490 --> 00:13:34.500 align:start position:0% of these you know and try to fix some of 00:13:34.500 --> 00:13:36.829 align:start position:0% of these you know and try to fix some of these<00:13:34.680> limitations<00:13:35.220> of<00:13:35.459> the<00:13:35.760> evm<00:13:36.120> that<00:13:36.300> we 00:13:36.829 --> 00:13:36.839 align:start position:0% these limitations of the evm that we 00:13:36.839 --> 00:13:38.449 align:start position:0% these limitations of the evm that we have<00:13:36.959> only<00:13:37.139> one<00:13:37.320> because<00:13:37.560> there's<00:13:37.980> much<00:13:38.220> less 00:13:38.449 --> 00:13:38.459 align:start position:0% have only one because there's much less 00:13:38.459 --> 00:13:41.150 align:start position:0% have only one because there's much less at<00:13:38.700> stake<00:13:38.940> and<00:13:39.660> then<00:13:39.839> each<00:13:40.260> layer<00:13:40.620> two<00:13:40.800> they 00:13:41.150 --> 00:13:41.160 align:start position:0% at stake and then each layer two they 00:13:41.160 --> 00:13:42.949 align:start position:0% at stake and then each layer two they may<00:13:41.519> favor<00:13:41.700> a<00:13:41.880> different<00:13:42.060> type<00:13:42.360> of<00:13:42.480> trade-offs 00:13:42.949 --> 00:13:42.959 align:start position:0% may favor a different type of trade-offs 00:13:42.959 --> 00:13:44.990 align:start position:0% may favor a different type of trade-offs so<00:13:43.079> we<00:13:43.200> can<00:13:43.320> explore<00:13:43.680> on<00:13:43.980> different<00:13:44.220> patterns 00:13:44.990 --> 00:13:45.000 align:start position:0% so we can explore on different patterns 00:13:45.000 --> 00:13:46.910 align:start position:0% so we can explore on different patterns and<00:13:45.600> actually<00:13:45.959> bring<00:13:46.260> alcohol<00:13:46.440> abstraction 00:13:46.910 --> 00:13:46.920 align:start position:0% and actually bring alcohol abstraction 00:13:46.920 --> 00:13:49.069 align:start position:0% and actually bring alcohol abstraction at<00:13:47.220> the<00:13:47.339> at<00:13:47.579> the<00:13:47.880> layer<00:13:48.120> twos<00:13:48.420> right<00:13:48.779> now<00:13:48.899> so 00:13:49.069 --> 00:13:49.079 align:start position:0% at the at the layer twos right now so 00:13:49.079 --> 00:13:50.870 align:start position:0% at the at the layer twos right now so this<00:13:49.320> is<00:13:49.380> what<00:13:49.620> we<00:13:49.740> are<00:13:49.920> pushing<00:13:50.279> and<00:13:50.760> that 00:13:50.870 --> 00:13:50.880 align:start position:0% this is what we are pushing and that 00:13:50.880 --> 00:13:52.670 align:start position:0% this is what we are pushing and that will<00:13:51.000> enable<00:13:51.300> us<00:13:51.480> to<00:13:51.779> better<00:13:51.959> understand<00:13:52.260> you 00:13:52.670 --> 00:13:52.680 align:start position:0% will enable us to better understand you 00:13:52.680 --> 00:13:55.009 align:start position:0% will enable us to better understand you know<00:13:52.740> the<00:13:52.920> limitations<00:13:53.339> what<00:13:53.760> we<00:13:53.940> can<00:13:54.120> do<00:13:54.300> and 00:13:55.009 --> 00:13:55.019 align:start position:0% know the limitations what we can do and 00:13:55.019 --> 00:13:56.810 align:start position:0% know the limitations what we can do and and<00:13:55.200> following<00:13:55.740> that<00:13:55.980> I<00:13:56.279> think<00:13:56.399> then<00:13:56.639> we'll 00:13:56.810 --> 00:13:56.820 align:start position:0% and following that I think then we'll 00:13:56.820 --> 00:13:58.069 align:start position:0% and following that I think then we'll have<00:13:57.000> everything<00:13:57.180> enhanced<00:13:57.720> to<00:13:57.959> actually 00:13:58.069 --> 00:13:58.079 align:start position:0% have everything enhanced to actually 00:13:58.079 --> 00:14:00.590 align:start position:0% have everything enhanced to actually bring<00:13:58.440> that<00:13:58.680> to<00:13:58.920> layer<00:13:59.220> one<00:13:59.399> and<00:13:59.880> push<00:14:00.060> for<00:14:00.300> a 00:14:00.590 --> 00:14:00.600 align:start position:0% bring that to layer one and push for a 00:14:00.600 --> 00:14:02.210 align:start position:0% bring that to layer one and push for a kind<00:14:00.779> of<00:14:00.899> fraction<00:14:01.139> at<00:14:01.440> really<00:14:01.620> the<00:14:01.860> protocol 00:14:02.210 --> 00:14:02.220 align:start position:0% kind of fraction at really the protocol 00:14:02.220 --> 00:14:04.670 align:start position:0% kind of fraction at really the protocol level<00:14:02.459> only<00:14:02.760> one<00:14:03.000> that's<00:14:03.720> the<00:14:03.899> way<00:14:04.019> I<00:14:04.260> see<00:14:04.440> the 00:14:04.670 --> 00:14:04.680 align:start position:0% level only one that's the way I see the 00:14:04.680 --> 00:14:06.050 align:start position:0% level only one that's the way I see the roadmap<00:14:05.040> of<00:14:05.220> account<00:14:05.399> abstraction<00:14:05.880> not 00:14:06.050 --> 00:14:06.060 align:start position:0% roadmap of account abstraction not 00:14:06.060 --> 00:14:07.970 align:start position:0% roadmap of account abstraction not folding<00:14:06.480> beautiful<00:14:06.959> and<00:14:07.320> and<00:14:07.500> you'll<00:14:07.860> have 00:14:07.970 --> 00:14:07.980 align:start position:0% folding beautiful and and you'll have 00:14:07.980 --> 00:14:09.889 align:start position:0% folding beautiful and and you'll have you're<00:14:08.220> a<00:14:08.339> security<00:14:08.459> Reacher<00:14:09.000> at<00:14:09.120> EF<00:14:09.660> so<00:14:09.839> I 00:14:09.889 --> 00:14:09.899 align:start position:0% you're a security Reacher at EF so I 00:14:09.899 --> 00:14:12.050 align:start position:0% you're a security Reacher at EF so I want<00:14:10.019> to<00:14:10.079> tap<00:14:10.200> into<00:14:10.320> your<00:14:10.560> security<00:14:10.740> mind<00:14:11.100> why 00:14:12.050 --> 00:14:12.060 align:start position:0% want to tap into your security mind why 00:14:12.060 --> 00:14:14.329 align:start position:0% want to tap into your security mind why are<00:14:12.420> smart<00:14:12.720> contract<00:14:13.139> wallets<00:14:13.560> more<00:14:14.040> secure 00:14:14.329 --> 00:14:14.339 align:start position:0% are smart contract wallets more secure 00:14:14.339 --> 00:14:16.490 align:start position:0% are smart contract wallets more secure like<00:14:14.700> what<00:14:14.940> security<00:14:15.240> benefits<00:14:15.839> from<00:14:16.079> a<00:14:16.260> user 00:14:16.490 --> 00:14:16.500 align:start position:0% like what security benefits from a user 00:14:16.500 --> 00:14:18.350 align:start position:0% like what security benefits from a user perspective<00:14:16.980> or<00:14:17.639> whoever<00:14:17.940> might<00:14:18.180> else 00:14:18.350 --> 00:14:18.360 align:start position:0% perspective or whoever might else 00:14:18.360 --> 00:14:20.930 align:start position:0% perspective or whoever might else whatever<00:14:18.600> entity<00:14:19.019> might<00:14:19.320> also<00:14:19.560> use<00:14:19.740> a<00:14:20.579> Smart 00:14:20.930 --> 00:14:20.940 align:start position:0% whatever entity might also use a Smart 00:14:20.940 --> 00:14:22.250 align:start position:0% whatever entity might also use a Smart contract<00:14:21.180> wallet<00:14:21.540> why<00:14:21.720> why<00:14:21.839> is<00:14:22.019> it<00:14:22.139> more 00:14:22.250 --> 00:14:22.260 align:start position:0% contract wallet why why is it more 00:14:22.260 --> 00:14:24.889 align:start position:0% contract wallet why why is it more secure<00:14:22.560> than<00:14:22.800> our<00:14:22.980> current<00:14:23.339> wallets 00:14:24.889 --> 00:14:24.899 align:start position:0% secure than our current wallets 00:14:24.899 --> 00:14:27.710 align:start position:0% secure than our current wallets well<00:14:25.500> then<00:14:25.860> uh<00:14:26.339> this<00:14:26.820> is<00:14:26.940> a<00:14:27.060> there<00:14:27.420> are<00:14:27.540> many 00:14:27.710 --> 00:14:27.720 align:start position:0% well then uh this is a there are many 00:14:27.720 --> 00:14:29.389 align:start position:0% well then uh this is a there are many different<00:14:27.959> ways<00:14:28.380> in<00:14:28.440> which<00:14:28.920> it<00:14:29.100> makes<00:14:29.279> you 00:14:29.389 --> 00:14:29.399 align:start position:0% different ways in which it makes you 00:14:29.399 --> 00:14:31.610 align:start position:0% different ways in which it makes you more<00:14:29.579> secure<00:14:29.940> first<00:14:30.600> of<00:14:30.779> all<00:14:30.899> is<00:14:31.139> a<00:14:31.380> key 00:14:31.610 --> 00:14:31.620 align:start position:0% more secure first of all is a key 00:14:31.620 --> 00:14:34.490 align:start position:0% more secure first of all is a key management<00:14:32.120> users<00:14:33.120> users<00:14:33.779> don't<00:14:33.959> know<00:14:34.200> how<00:14:34.380> to 00:14:34.490 --> 00:14:34.500 align:start position:0% management users users don't know how to 00:14:34.500 --> 00:14:37.310 align:start position:0% management users users don't know how to manage<00:14:34.740> Keys<00:14:35.040> even<00:14:35.220> expert<00:14:35.700> users<00:14:36.120> and<00:14:37.079> they 00:14:37.310 --> 00:14:37.320 align:start position:0% manage Keys even expert users and they 00:14:37.320 --> 00:14:40.129 align:start position:0% manage Keys even expert users and they just<00:14:37.620> I<00:14:37.920> think<00:14:38.100> that<00:14:38.220> five<00:14:38.579> years<00:14:38.760> from<00:14:39.000> now<00:14:39.240> if 00:14:40.129 --> 00:14:40.139 align:start position:0% just I think that five years from now if 00:14:40.139 --> 00:14:42.710 align:start position:0% just I think that five years from now if we<00:14:40.380> we<00:14:40.860> recall<00:14:41.279> that<00:14:41.519> we<00:14:41.820> used<00:14:41.940> to<00:14:42.240> secure<00:14:42.540> our 00:14:42.710 --> 00:14:42.720 align:start position:0% we we recall that we used to secure our 00:14:42.720 --> 00:14:45.590 align:start position:0% we we recall that we used to secure our assets<00:14:43.079> by<00:14:43.440> writing<00:14:43.920> 12<00:14:44.579> words<00:14:44.880> on<00:14:45.180> a<00:14:45.360> piece<00:14:45.540> of 00:14:45.590 --> 00:14:45.600 align:start position:0% assets by writing 12 words on a piece of 00:14:45.600 --> 00:14:48.530 align:start position:0% assets by writing 12 words on a piece of paper<00:14:45.779> it<00:14:46.560> will<00:14:46.740> seem<00:14:46.980> unreal<00:14:47.459> to<00:14:47.639> us<00:14:47.760> so<00:14:48.360> I 00:14:48.530 --> 00:14:48.540 align:start position:0% paper it will seem unreal to us so I 00:14:48.540 --> 00:14:51.170 align:start position:0% paper it will seem unreal to us so I think<00:14:48.720> uh<00:14:49.199> for<00:14:49.680> example<00:14:49.920> being<00:14:50.279> able<00:14:50.639> to<00:14:50.760> add 00:14:51.170 --> 00:14:51.180 align:start position:0% think uh for example being able to add 00:14:51.180 --> 00:14:55.009 align:start position:0% think uh for example being able to add devices<00:14:51.779> to<00:14:52.560> add<00:14:52.800> devices<00:14:53.160> to<00:14:53.579> your<00:14:53.760> wallet<00:14:54.180> so 00:14:55.009 --> 00:14:55.019 align:start position:0% devices to add devices to your wallet so 00:14:55.019 --> 00:14:56.990 align:start position:0% devices to add devices to your wallet so the<00:14:55.199> wallet<00:14:55.500> is<00:14:55.620> no<00:14:55.860> longer<00:14:56.040> associated<00:14:56.519> with 00:14:56.990 --> 00:14:57.000 align:start position:0% the wallet is no longer associated with 00:14:57.000 --> 00:14:59.269 align:start position:0% the wallet is no longer associated with some<00:14:57.480> seed<00:14:57.839> phrase<00:14:58.139> you<00:14:58.500> never<00:14:58.680> actually<00:14:58.920> see 00:14:59.269 --> 00:14:59.279 align:start position:0% some seed phrase you never actually see 00:14:59.279 --> 00:15:01.910 align:start position:0% some seed phrase you never actually see but<00:14:59.639> instead<00:15:00.000> you<00:15:00.959> add<00:15:01.079> your<00:15:01.320> phone<00:15:01.560> you<00:15:01.740> add 00:15:01.910 --> 00:15:01.920 align:start position:0% but instead you add your phone you add 00:15:01.920 --> 00:15:03.530 align:start position:0% but instead you add your phone you add your<00:15:02.100> computer<00:15:02.279> then<00:15:02.760> if<00:15:03.000> you<00:15:03.120> lose<00:15:03.300> your 00:15:03.530 --> 00:15:03.540 align:start position:0% your computer then if you lose your 00:15:03.540 --> 00:15:05.329 align:start position:0% your computer then if you lose your phone<00:15:03.720> you<00:15:03.959> remove<00:15:04.139> it<00:15:04.380> and<00:15:04.560> add<00:15:04.800> a<00:15:04.980> new<00:15:05.100> one 00:15:05.329 --> 00:15:05.339 align:start position:0% phone you remove it and add a new one 00:15:05.339 --> 00:15:09.230 align:start position:0% phone you remove it and add a new one using<00:15:05.760> your<00:15:05.940> computer<00:15:06.120> so<00:15:07.560> um<00:15:07.620> and<00:15:08.459> so<00:15:09.060> this 00:15:09.230 --> 00:15:09.240 align:start position:0% using your computer so um and so this 00:15:09.240 --> 00:15:11.569 align:start position:0% using your computer so um and so this allows<00:15:09.600> this<00:15:10.019> obviously<00:15:10.560> improves<00:15:11.399> the 00:15:11.569 --> 00:15:11.579 align:start position:0% allows this obviously improves the 00:15:11.579 --> 00:15:13.009 align:start position:0% allows this obviously improves the security<00:15:11.820> because<00:15:12.360> you<00:15:12.600> don't<00:15:12.660> need<00:15:12.839> to 00:15:13.009 --> 00:15:13.019 align:start position:0% security because you don't need to 00:15:13.019 --> 00:15:15.170 align:start position:0% security because you don't need to manage<00:15:13.260> keys<00:15:13.680> and<00:15:14.040> then<00:15:14.160> there's<00:15:14.459> the<00:15:14.760> uh 00:15:15.170 --> 00:15:15.180 align:start position:0% manage keys and then there's the uh 00:15:15.180 --> 00:15:17.449 align:start position:0% manage keys and then there's the uh there<00:15:15.959> are<00:15:16.079> things<00:15:16.199> like<00:15:16.500> for<00:15:17.040> example<00:15:17.220> you 00:15:17.449 --> 00:15:17.459 align:start position:0% there are things like for example you 00:15:17.459 --> 00:15:20.269 align:start position:0% there are things like for example you could<00:15:17.579> say<00:15:17.820> that<00:15:18.180> your<00:15:18.600> wallet<00:15:18.899> is<00:15:19.139> uh<00:15:19.620> that 00:15:20.269 --> 00:15:20.279 align:start position:0% could say that your wallet is uh that 00:15:20.279 --> 00:15:23.150 align:start position:0% could say that your wallet is uh that you<00:15:21.000> can<00:15:21.120> you<00:15:21.420> can<00:15:21.540> have<00:15:21.720> good<00:15:21.959> usability<00:15:22.500> and 00:15:23.150 --> 00:15:23.160 align:start position:0% you can you can have good usability and 00:15:23.160 --> 00:15:25.370 align:start position:0% you can you can have good usability and spend<00:15:23.519> small<00:15:23.820> amounts<00:15:24.300> easily<00:15:24.660> you<00:15:24.839> using 00:15:25.370 --> 00:15:25.380 align:start position:0% spend small amounts easily you using 00:15:25.380 --> 00:15:27.470 align:start position:0% spend small amounts easily you using your<00:15:25.560> phone<00:15:25.800> but<00:15:26.760> if<00:15:27.000> you<00:15:27.180> are<00:15:27.300> doing 00:15:27.470 --> 00:15:27.480 align:start position:0% your phone but if you are doing 00:15:27.480 --> 00:15:30.230 align:start position:0% your phone but if you are doing something<00:15:28.040> out<00:15:29.040> of<00:15:29.160> the<00:15:29.339> ordinary<00:15:29.699> such<00:15:30.120> as 00:15:30.230 --> 00:15:30.240 align:start position:0% something out of the ordinary such as 00:15:30.240 --> 00:15:32.590 align:start position:0% something out of the ordinary such as sending<00:15:30.720> a<00:15:30.839> very<00:15:31.019> large<00:15:31.199> amount 00:15:32.590 --> 00:15:32.600 align:start position:0% sending a very large amount 00:15:32.600 --> 00:15:35.689 align:start position:0% sending a very large amount in<00:15:33.600> that<00:15:33.720> case<00:15:33.959> in<00:15:34.560> that<00:15:34.680> case<00:15:34.860> you<00:15:35.220> have<00:15:35.339> to<00:15:35.519> go 00:15:35.689 --> 00:15:35.699 align:start position:0% in that case in that case you have to go 00:15:35.699 --> 00:15:37.670 align:start position:0% in that case in that case you have to go get<00:15:35.940> your<00:15:36.180> Ledger<00:15:36.600> or<00:15:36.779> something<00:15:36.959> you<00:15:37.320> had<00:15:37.440> you 00:15:37.670 --> 00:15:37.680 align:start position:0% get your Ledger or something you had you 00:15:37.680 --> 00:15:39.470 align:start position:0% get your Ledger or something you had you have<00:15:37.800> to<00:15:37.860> add<00:15:38.040> another<00:15:38.279> signature<00:15:38.880> so<00:15:39.360> it 00:15:39.470 --> 00:15:39.480 align:start position:0% have to add another signature so it 00:15:39.480 --> 00:15:41.689 align:start position:0% have to add another signature so it allows<00:15:39.779> you<00:15:39.839> to<00:15:40.019> have<00:15:40.320> a<00:15:40.560> security<00:15:40.860> policies 00:15:41.689 --> 00:15:41.699 align:start position:0% allows you to have a security policies 00:15:41.699 --> 00:15:43.730 align:start position:0% allows you to have a security policies to<00:15:42.420> protect<00:15:42.660> yourself 00:15:43.730 --> 00:15:43.740 align:start position:0% to protect yourself 00:15:43.740 --> 00:15:45.650 align:start position:0% to protect yourself and<00:15:44.279> there's<00:15:44.579> the<00:15:44.880> the<00:15:45.060> other<00:15:45.300> Security 00:15:45.650 --> 00:15:45.660 align:start position:0% and there's the the other Security 00:15:45.660 --> 00:15:48.710 align:start position:0% and there's the the other Security benefits<00:15:46.320> of<00:15:46.500> switching<00:15:47.100> of<00:15:47.760> switching<00:15:48.240> to<00:15:48.540> a 00:15:48.710 --> 00:15:48.720 align:start position:0% benefits of switching of switching to a 00:15:48.720 --> 00:15:51.050 align:start position:0% benefits of switching of switching to a better<00:15:48.959> signature<00:15:49.680> scheme<00:15:50.100> which<00:15:50.699> we're 00:15:51.050 --> 00:15:51.060 align:start position:0% better signature scheme which we're 00:15:51.060 --> 00:15:54.530 align:start position:0% better signature scheme which we're going<00:15:51.300> to<00:15:51.420> have<00:15:51.540> to<00:15:51.720> do<00:15:51.899> in<00:15:52.079> the<00:15:52.199> future<00:15:52.320> anyway 00:15:54.530 --> 00:15:54.540 align:start position:0% going to have to do in the future anyway 00:15:54.540 --> 00:15:57.410 align:start position:0% going to have to do in the future anyway um<00:15:54.660> and<00:15:55.380> since<00:15:55.620> since<00:15:55.920> it's<00:15:56.160> programmable<00:15:56.699> you 00:15:57.410 --> 00:15:57.420 align:start position:0% um and since since it's programmable you 00:15:57.420 --> 00:16:00.050 align:start position:0% um and since since it's programmable you can<00:15:57.480> add<00:15:57.779> any<00:15:58.079> any<00:15:58.740> security<00:15:59.100> mechanism<00:15:59.820> you 00:16:00.050 --> 00:16:00.060 align:start position:0% can add any any security mechanism you 00:16:00.060 --> 00:16:02.030 align:start position:0% can add any any security mechanism you come<00:16:00.240> up<00:16:00.420> with<00:16:00.660> and<00:16:01.199> different<00:16:01.440> users<00:16:01.860> will 00:16:02.030 --> 00:16:02.040 align:start position:0% come up with and different users will 00:16:02.040 --> 00:16:03.889 align:start position:0% come up with and different users will have<00:16:02.279> different<00:16:02.579> uh<00:16:03.180> we'll<00:16:03.420> have<00:16:03.600> a<00:16:03.660> different 00:16:03.889 --> 00:16:03.899 align:start position:0% have different uh we'll have a different 00:16:03.899 --> 00:16:06.290 align:start position:0% have different uh we'll have a different requirements<00:16:04.620> so<00:16:05.100> having<00:16:05.339> just<00:16:05.699> a<00:16:05.940> single 00:16:06.290 --> 00:16:06.300 align:start position:0% requirements so having just a single 00:16:06.300 --> 00:16:08.329 align:start position:0% requirements so having just a single security<00:16:06.480> policy<00:16:07.199> for<00:16:07.320> accounts<00:16:07.800> which<00:16:08.220> is 00:16:08.329 --> 00:16:08.339 align:start position:0% security policy for accounts which is 00:16:08.339 --> 00:16:10.310 align:start position:0% security policy for accounts which is what<00:16:08.519> we<00:16:08.699> have<00:16:08.820> with<00:16:09.000> EOS<00:16:09.360> I<00:16:09.779> mean<00:16:09.899> the 00:16:10.310 --> 00:16:10.320 align:start position:0% what we have with EOS I mean the 00:16:10.320 --> 00:16:13.310 align:start position:0% what we have with EOS I mean the security<00:16:10.500> policy<00:16:11.040> for<00:16:11.160> a<00:16:11.339> foreign<00:16:11.639> AOA<00:16:12.060> is<00:16:12.899> if 00:16:13.310 --> 00:16:13.320 align:start position:0% security policy for a foreign AOA is if 00:16:13.320 --> 00:16:15.410 align:start position:0% security policy for a foreign AOA is if you<00:16:13.560> have<00:16:13.680> the<00:16:13.920> key<00:16:14.040> do<00:16:14.459> anything<00:16:14.760> if<00:16:15.300> you 00:16:15.410 --> 00:16:15.420 align:start position:0% you have the key do anything if you 00:16:15.420 --> 00:16:17.389 align:start position:0% you have the key do anything if you don't<00:16:15.540> have<00:16:15.660> the<00:16:15.839> key<00:16:16.019> do<00:16:16.260> nothing<00:16:16.440> this<00:16:17.279> is 00:16:17.389 --> 00:16:17.399 align:start position:0% don't have the key do nothing this is 00:16:17.399 --> 00:16:18.829 align:start position:0% don't have the key do nothing this is not<00:16:17.519> granular<00:16:18.000> enough 00:16:18.829 --> 00:16:18.839 align:start position:0% not granular enough 00:16:18.839 --> 00:16:21.710 align:start position:0% not granular enough so<00:16:19.320> I<00:16:19.440> think<00:16:19.560> being<00:16:19.800> able<00:16:20.160> to<00:16:20.519> have<00:16:20.760> a<00:16:21.000> to<00:16:21.420> have 00:16:21.710 --> 00:16:21.720 align:start position:0% so I think being able to have a to have 00:16:21.720 --> 00:16:24.170 align:start position:0% so I think being able to have a to have personalized<00:16:22.320> security<00:16:22.620> policies<00:16:23.339> will<00:16:24.000> make 00:16:24.170 --> 00:16:24.180 align:start position:0% personalized security policies will make 00:16:24.180 --> 00:16:26.689 align:start position:0% personalized security policies will make ethereum<00:16:24.779> overall<00:16:25.320> more<00:16:25.500> secure 00:16:26.689 --> 00:16:26.699 align:start position:0% ethereum overall more secure 00:16:26.699 --> 00:16:29.810 align:start position:0% ethereum overall more secure I<00:16:27.120> think<00:16:27.779> um<00:16:27.839> the<00:16:28.560> way<00:16:28.740> that<00:16:29.100> I<00:16:29.399> see<00:16:29.519> account 00:16:29.810 --> 00:16:29.820 align:start position:0% I think um the way that I see account 00:16:29.820 --> 00:16:31.430 align:start position:0% I think um the way that I see account objective<00:16:30.360> wallet<00:16:30.600> smart<00:16:30.720> contract<00:16:31.019> wallets 00:16:31.430 --> 00:16:31.440 align:start position:0% objective wallet smart contract wallets 00:16:31.440 --> 00:16:33.110 align:start position:0% objective wallet smart contract wallets there's<00:16:31.860> this<00:16:32.040> unique<00:16:32.459> relationship<00:16:32.880> with 00:16:33.110 --> 00:16:33.120 align:start position:0% there's this unique relationship with 00:16:33.120 --> 00:16:35.689 align:start position:0% there's this unique relationship with devices<00:16:33.540> and<00:16:34.380> we<00:16:34.560> all<00:16:34.860> have<00:16:35.040> a<00:16:35.279> bajillion 00:16:35.689 --> 00:16:35.699 align:start position:0% devices and we all have a bajillion 00:16:35.699 --> 00:16:37.730 align:start position:0% devices and we all have a bajillion devices<00:16:35.940> in<00:16:36.300> our<00:16:36.420> homes<00:16:36.600> uh<00:16:37.259> like<00:16:37.440> when<00:16:37.560> I<00:16:37.680> said 00:16:37.730 --> 00:16:37.740 align:start position:0% devices in our homes uh like when I said 00:16:37.740 --> 00:16:38.930 align:start position:0% devices in our homes uh like when I said on<00:16:37.920> my<00:16:38.040> computer<00:16:38.160> I<00:16:38.459> have<00:16:38.519> my<00:16:38.639> computer<00:16:38.759> in 00:16:38.930 --> 00:16:38.940 align:start position:0% on my computer I have my computer in 00:16:38.940 --> 00:16:40.189 align:start position:0% on my computer I have my computer in front<00:16:39.060> of<00:16:39.180> me<00:16:39.240> I<00:16:39.360> got<00:16:39.540> my<00:16:39.660> phone<00:16:39.779> and<00:16:40.019> then 00:16:40.189 --> 00:16:40.199 align:start position:0% front of me I got my phone and then 00:16:40.199 --> 00:16:41.389 align:start position:0% front of me I got my phone and then maybe<00:16:40.320> there's<00:16:40.500> an<00:16:40.680> iPad<00:16:40.920> and<00:16:41.100> those<00:16:41.279> are 00:16:41.389 --> 00:16:41.399 align:start position:0% maybe there's an iPad and those are 00:16:41.399 --> 00:16:43.550 align:start position:0% maybe there's an iPad and those are three<00:16:41.579> devices<00:16:41.880> each<00:16:42.779> with<00:16:42.959> different<00:16:43.259> levels 00:16:43.550 --> 00:16:43.560 align:start position:0% three devices each with different levels 00:16:43.560 --> 00:16:45.590 align:start position:0% three devices each with different levels of<00:16:43.740> security<00:16:43.980> assumptions<00:16:44.699> around<00:16:45.000> them<00:16:45.300> like 00:16:45.590 --> 00:16:45.600 align:start position:0% of security assumptions around them like 00:16:45.600 --> 00:16:47.810 align:start position:0% of security assumptions around them like my<00:16:45.959> computer<00:16:46.139> is<00:16:46.740> at<00:16:47.040> home<00:16:47.160> it<00:16:47.459> doesn't<00:16:47.579> go 00:16:47.810 --> 00:16:47.820 align:start position:0% my computer is at home it doesn't go 00:16:47.820 --> 00:16:49.550 align:start position:0% my computer is at home it doesn't go anywhere<00:16:48.060> my<00:16:48.300> mobile<00:16:48.600> phone<00:16:48.839> can<00:16:49.079> go<00:16:49.259> anywhere 00:16:49.550 --> 00:16:49.560 align:start position:0% anywhere my mobile phone can go anywhere 00:16:49.560 --> 00:16:51.470 align:start position:0% anywhere my mobile phone can go anywhere in<00:16:49.680> the<00:16:49.800> world<00:16:49.920> but<00:16:50.519> all<00:16:50.699> of<00:16:50.820> these<00:16:51.060> things<00:16:51.180> can 00:16:51.470 --> 00:16:51.480 align:start position:0% in the world but all of these things can 00:16:51.480 --> 00:16:52.850 align:start position:0% in the world but all of these things can you<00:16:51.600> talk<00:16:51.779> about<00:16:51.899> the<00:16:52.139> relationship<00:16:52.560> between 00:16:52.850 --> 00:16:52.860 align:start position:0% you talk about the relationship between 00:16:52.860 --> 00:16:56.290 align:start position:0% you talk about the relationship between a<00:16:53.339> device<00:16:53.519> and<00:16:54.360> the<00:16:54.540> wallet<00:16:54.959> and<00:16:55.440> how<00:16:55.560> that<00:16:55.740> can 00:16:56.290 --> 00:16:56.300 align:start position:0% a device and the wallet and how that can 00:16:56.300 --> 00:16:58.310 align:start position:0% a device and the wallet and how that can relate<00:16:57.300> to<00:16:57.420> a<00:16:57.540> different<00:16:57.720> level<00:16:57.959> of<00:16:58.139> security 00:16:58.310 --> 00:16:58.320 align:start position:0% relate to a different level of security 00:16:58.320 --> 00:17:01.069 align:start position:0% relate to a different level of security of<00:16:58.740> control<00:16:59.160> of<00:16:59.459> access<00:16:59.639> right<00:17:00.000> so<00:17:00.300> maybe<00:17:00.720> I 00:17:01.069 --> 00:17:01.079 align:start position:0% of control of access right so maybe I 00:17:01.079 --> 00:17:02.810 align:start position:0% of control of access right so maybe I only<00:17:01.199> want<00:17:01.560> to<00:17:01.740> send<00:17:01.980> a<00:17:02.160> hundred<00:17:02.399> dollars<00:17:02.579> with 00:17:02.810 --> 00:17:02.820 align:start position:0% only want to send a hundred dollars with 00:17:02.820 --> 00:17:04.909 align:start position:0% only want to send a hundred dollars with my<00:17:03.000> phone<00:17:03.180> but<00:17:03.839> I<00:17:04.079> can<00:17:04.199> send<00:17:04.380> all<00:17:04.559> of<00:17:04.679> my<00:17:04.799> money 00:17:04.909 --> 00:17:04.919 align:start position:0% my phone but I can send all of my money 00:17:04.919 --> 00:17:06.110 align:start position:0% my phone but I can send all of my money with<00:17:05.100> my<00:17:05.280> computer<00:17:05.339> can<00:17:05.640> you<00:17:05.760> talk<00:17:05.880> about<00:17:05.939> the 00:17:06.110 --> 00:17:06.120 align:start position:0% with my computer can you talk about the 00:17:06.120 --> 00:17:07.789 align:start position:0% with my computer can you talk about the relationship<00:17:06.480> with<00:17:06.600> a<00:17:06.780> device<00:17:06.959> and<00:17:07.319> a<00:17:07.439> smart 00:17:07.789 --> 00:17:07.799 align:start position:0% relationship with a device and a smart 00:17:07.799 --> 00:17:10.309 align:start position:0% relationship with a device and a smart contract<00:17:08.100> wallet<00:17:08.819> yes<00:17:09.360> this<00:17:09.660> this<00:17:10.020> should 00:17:10.309 --> 00:17:10.319 align:start position:0% contract wallet yes this this should 00:17:10.319 --> 00:17:11.990 align:start position:0% contract wallet yes this this should definitely<00:17:10.740> be<00:17:11.100> a<00:17:11.280> part<00:17:11.459> of<00:17:11.640> the<00:17:11.819> security 00:17:11.990 --> 00:17:12.000 align:start position:0% definitely be a part of the security 00:17:12.000 --> 00:17:14.390 align:start position:0% definitely be a part of the security policy<00:17:12.660> for<00:17:12.839> your<00:17:12.959> wallet 00:17:14.390 --> 00:17:14.400 align:start position:0% policy for your wallet 00:17:14.400 --> 00:17:16.789 align:start position:0% policy for your wallet um<00:17:14.459> so<00:17:14.640> yes<00:17:14.819> you<00:17:15.120> could<00:17:15.240> say<00:17:15.480> that<00:17:15.839> you<00:17:16.500> can<00:17:16.559> use 00:17:16.789 --> 00:17:16.799 align:start position:0% um so yes you could say that you can use 00:17:16.799 --> 00:17:18.829 align:start position:0% um so yes you could say that you can use your<00:17:17.100> phone<00:17:17.280> to<00:17:17.640> do<00:17:17.760> small<00:17:18.059> things<00:17:18.360> but<00:17:18.660> your 00:17:18.829 --> 00:17:18.839 align:start position:0% your phone to do small things but your 00:17:18.839 --> 00:17:21.350 align:start position:0% your phone to do small things but your computer<00:17:19.079> for<00:17:19.620> a<00:17:19.860> for<00:17:20.640> bigger<00:17:20.880> things<00:17:21.000> I'm 00:17:21.350 --> 00:17:21.360 align:start position:0% computer for a for bigger things I'm 00:17:21.360 --> 00:17:23.750 align:start position:0% computer for a for bigger things I'm actually<00:17:21.600> not<00:17:21.959> sure<00:17:22.199> I'm<00:17:22.980> sometimes<00:17:23.520> your 00:17:23.750 --> 00:17:23.760 align:start position:0% actually not sure I'm sometimes your 00:17:23.760 --> 00:17:26.090 align:start position:0% actually not sure I'm sometimes your phone<00:17:24.179> could<00:17:24.900> actually<00:17:25.140> be<00:17:25.500> more<00:17:25.679> secure 00:17:26.090 --> 00:17:26.100 align:start position:0% phone could actually be more secure 00:17:26.100 --> 00:17:29.270 align:start position:0% phone could actually be more secure because<00:17:26.520> uh<00:17:27.179> on<00:17:27.900> your<00:17:28.199> computer<00:17:28.439> may<00:17:28.860> or<00:17:29.040> may 00:17:29.270 --> 00:17:29.280 align:start position:0% because uh on your computer may or may 00:17:29.280 --> 00:17:31.789 align:start position:0% because uh on your computer may or may not<00:17:29.400> have<00:17:29.700> the<00:17:30.179> capability<00:17:30.540> of<00:17:30.780> security<00:17:31.020> of<00:17:31.500> a 00:17:31.789 --> 00:17:31.799 align:start position:0% not have the capability of security of a 00:17:31.799 --> 00:17:35.810 align:start position:0% not have the capability of security of a on<00:17:32.340> of<00:17:32.640> a<00:17:32.760> secure<00:17:33.120> enclaves<00:17:34.140> but<00:17:34.980> phones 00:17:35.810 --> 00:17:35.820 align:start position:0% on of a secure enclaves but phones 00:17:35.820 --> 00:17:40.010 align:start position:0% on of a secure enclaves but phones modern<00:17:36.780> phones<00:17:37.380> they<00:17:37.620> usually<00:17:38.100> do<00:17:38.780> now<00:17:39.780> the 00:17:40.010 --> 00:17:40.020 align:start position:0% modern phones they usually do now the 00:17:40.020 --> 00:17:41.450 align:start position:0% modern phones they usually do now the problem<00:17:40.200> is<00:17:40.320> that<00:17:40.559> at<00:17:40.860> the<00:17:40.980> moment<00:17:41.100> you 00:17:41.450 --> 00:17:41.460 align:start position:0% problem is that at the moment you 00:17:41.460 --> 00:17:43.250 align:start position:0% problem is that at the moment you couldn't<00:17:41.580> use<00:17:41.940> it<00:17:42.059> within<00:17:42.360> AOA<00:17:42.780> because<00:17:43.020> it 00:17:43.250 --> 00:17:43.260 align:start position:0% couldn't use it within AOA because it 00:17:43.260 --> 00:17:45.230 align:start position:0% couldn't use it within AOA because it doesn't<00:17:43.440> support<00:17:43.860> the<00:17:44.340> signatures<00:17:45.000> the 00:17:45.230 --> 00:17:45.240 align:start position:0% doesn't support the signatures the 00:17:45.240 --> 00:17:47.570 align:start position:0% doesn't support the signatures the ethereum<00:17:45.780> use<00:17:46.020> it<00:17:46.740> doesn't<00:17:46.860> support<00:17:47.100> the<00:17:47.400> same 00:17:47.570 --> 00:17:47.580 align:start position:0% ethereum use it doesn't support the same 00:17:47.580 --> 00:17:51.470 align:start position:0% ethereum use it doesn't support the same curve<00:17:48.600> but<00:17:49.500> with<00:17:50.400> account<00:17:50.580> obstruction<00:17:51.059> it 00:17:51.470 --> 00:17:51.480 align:start position:0% curve but with account obstruction it 00:17:51.480 --> 00:17:53.750 align:start position:0% curve but with account obstruction it becomes<00:17:51.900> it<00:17:52.500> becomes<00:17:52.799> possible<00:17:53.220> and<00:17:53.520> someone 00:17:53.750 --> 00:17:53.760 align:start position:0% becomes it becomes possible and someone 00:17:53.760 --> 00:17:57.049 align:start position:0% becomes it becomes possible and someone actually<00:17:54.059> just<00:17:54.780> built<00:17:55.380> built<00:17:56.280> a<00:17:56.400> nice<00:17:56.460> demo<00:17:56.880> of 00:17:57.049 --> 00:17:57.059 align:start position:0% actually just built built a nice demo of 00:17:57.059 --> 00:17:58.789 align:start position:0% actually just built built a nice demo of such<00:17:57.240> wallet<00:17:57.720> at<00:17:58.020> the<00:17:58.140> hackathon<00:17:58.559> here<00:17:58.740> in 00:17:58.789 --> 00:17:58.799 align:start position:0% such wallet at the hackathon here in 00:17:58.799 --> 00:17:59.690 align:start position:0% such wallet at the hackathon here in Bogota 00:17:59.690 --> 00:17:59.700 align:start position:0% Bogota 00:17:59.700 --> 00:18:02.690 align:start position:0% Bogota so<00:18:00.660> um<00:18:00.720> you<00:18:01.260> can<00:18:01.380> have<00:18:01.559> so<00:18:02.039> if<00:18:02.400> you<00:18:02.580> can 00:18:02.690 --> 00:18:02.700 align:start position:0% so um you can have so if you can 00:18:02.700 --> 00:18:05.090 align:start position:0% so um you can have so if you can associate<00:18:03.179> the<00:18:03.419> fingerprint<00:18:04.020> of<00:18:04.320> a<00:18:04.679> specific 00:18:05.090 --> 00:18:05.100 align:start position:0% associate the fingerprint of a specific 00:18:05.100 --> 00:18:07.130 align:start position:0% associate the fingerprint of a specific device<00:18:05.460> and<00:18:06.120> you<00:18:06.360> can<00:18:06.480> you<00:18:06.720> can<00:18:06.840> have<00:18:07.020> a 00:18:07.130 --> 00:18:07.140 align:start position:0% device and you can you can have a 00:18:07.140 --> 00:18:09.110 align:start position:0% device and you can you can have a fingerprint<00:18:07.620> on<00:18:07.860> your<00:18:08.039> device<00:18:08.340> which<00:18:08.940> is 00:18:09.110 --> 00:18:09.120 align:start position:0% fingerprint on your device which is 00:18:09.120 --> 00:18:11.390 align:start position:0% fingerprint on your device which is actually<00:18:09.299> verified<00:18:09.960> by<00:18:10.320> a<00:18:10.440> secure<00:18:10.740> Enclave<00:18:11.160> on 00:18:11.390 --> 00:18:11.400 align:start position:0% actually verified by a secure Enclave on 00:18:11.400 --> 00:18:13.370 align:start position:0% actually verified by a secure Enclave on your<00:18:11.580> phone<00:18:11.760> and<00:18:12.480> then<00:18:12.660> the<00:18:12.900> signature 00:18:13.370 --> 00:18:13.380 align:start position:0% your phone and then the signature 00:18:13.380 --> 00:18:16.070 align:start position:0% your phone and then the signature happens<00:18:13.620> inside<00:18:14.039> it<00:18:14.480> so<00:18:15.480> your<00:18:15.720> phone<00:18:15.900> actually 00:18:16.070 --> 00:18:16.080 align:start position:0% happens inside it so your phone actually 00:18:16.080 --> 00:18:18.110 align:start position:0% happens inside it so your phone actually gives<00:18:16.500> you<00:18:16.620> a<00:18:16.860> pretty<00:18:16.980> good<00:18:17.280> pretty<00:18:17.880> good 00:18:18.110 --> 00:18:18.120 align:start position:0% gives you a pretty good pretty good 00:18:18.120 --> 00:18:20.750 align:start position:0% gives you a pretty good pretty good security<00:18:18.500> but<00:18:19.500> in<00:18:19.919> any<00:18:20.039> case<00:18:20.280> you<00:18:20.580> have<00:18:20.640> to 00:18:20.750 --> 00:18:20.760 align:start position:0% security but in any case you have to 00:18:20.760 --> 00:18:23.210 align:start position:0% security but in any case you have to evaluate<00:18:21.240> that<00:18:21.600> for<00:18:22.320> example<00:18:22.559> your<00:18:22.860> phone<00:18:23.039> is 00:18:23.210 --> 00:18:23.220 align:start position:0% evaluate that for example your phone is 00:18:23.220 --> 00:18:25.190 align:start position:0% evaluate that for example your phone is coming<00:18:23.400> with<00:18:23.760> you<00:18:23.880> your<00:18:24.120> computer<00:18:24.419> stays<00:18:25.080> at 00:18:25.190 --> 00:18:25.200 align:start position:0% coming with you your computer stays at 00:18:25.200 --> 00:18:27.590 align:start position:0% coming with you your computer stays at home<00:18:25.380> so<00:18:26.100> you<00:18:26.280> have<00:18:26.400> to<00:18:26.520> evaluate<00:18:26.880> your<00:18:27.179> unique 00:18:27.590 --> 00:18:27.600 align:start position:0% home so you have to evaluate your unique 00:18:27.600 --> 00:18:31.310 align:start position:0% home so you have to evaluate your unique situation<00:18:28.140> and<00:18:29.039> set<00:18:29.220> up<00:18:29.400> a<00:18:29.640> policy<00:18:30.059> where<00:18:30.480> you 00:18:31.310 --> 00:18:31.320 align:start position:0% situation and set up a policy where you 00:18:31.320 --> 00:18:33.169 align:start position:0% situation and set up a policy where you decide<00:18:31.620> which<00:18:31.980> device<00:18:32.220> can<00:18:32.580> do<00:18:32.760> what<00:18:32.940> and 00:18:33.169 --> 00:18:33.179 align:start position:0% decide which device can do what and 00:18:33.179 --> 00:18:35.450 align:start position:0% decide which device can do what and maybe<00:18:33.360> sometimes<00:18:33.840> you<00:18:34.080> need<00:18:34.260> the<00:18:34.500> to<00:18:34.919> use<00:18:35.160> two 00:18:35.450 --> 00:18:35.460 align:start position:0% maybe sometimes you need the to use two 00:18:35.460 --> 00:18:37.789 align:start position:0% maybe sometimes you need the to use two of<00:18:35.580> the<00:18:35.760> devices<00:18:36.059> maybe<00:18:37.020> sometimes<00:18:37.440> you<00:18:37.620> need 00:18:37.789 --> 00:18:37.799 align:start position:0% of the devices maybe sometimes you need 00:18:37.799 --> 00:18:40.370 align:start position:0% of the devices maybe sometimes you need to<00:18:37.919> go<00:18:38.039> also<00:18:38.340> get<00:18:38.580> your<00:18:38.760> Ledger<00:18:39.179> from<00:18:39.360> the<00:18:39.539> safe 00:18:40.370 --> 00:18:40.380 align:start position:0% to go also get your Ledger from the safe 00:18:40.380 --> 00:18:43.490 align:start position:0% to go also get your Ledger from the safe so<00:18:41.039> it's<00:18:41.400> up<00:18:41.580> to<00:18:41.700> you<00:18:41.820> to<00:18:42.059> say<00:18:42.179> to<00:18:42.419> decide<00:18:42.780> how 00:18:43.490 --> 00:18:43.500 align:start position:0% so it's up to you to say to decide how 00:18:43.500 --> 00:18:45.110 align:start position:0% so it's up to you to say to decide how each<00:18:43.740> device<00:18:43.980> is<00:18:44.220> going<00:18:44.400> to<00:18:44.520> be<00:18:44.640> used<00:18:44.760> in<00:18:45.000> your 00:18:45.110 --> 00:18:45.120 align:start position:0% each device is going to be used in your 00:18:45.120 --> 00:18:46.190 align:start position:0% each device is going to be used in your wallet 00:18:46.190 --> 00:18:46.200 align:start position:0% wallet 00:18:46.200 --> 00:18:48.110 align:start position:0% wallet I<00:18:46.620> think<00:18:46.919> the<00:18:47.100> important<00:18:47.400> important<00:18:47.820> thing<00:18:47.940> to 00:18:48.110 --> 00:18:48.120 align:start position:0% I think the important important thing to 00:18:48.120 --> 00:18:50.390 align:start position:0% I think the important important thing to take<00:18:48.299> a<00:18:48.720> note<00:18:48.900> from<00:18:49.140> here<00:18:49.320> is<00:18:49.679> that<00:18:49.919> we're 00:18:50.390 --> 00:18:50.400 align:start position:0% take a note from here is that we're 00:18:50.400 --> 00:18:53.029 align:start position:0% take a note from here is that we're using<00:18:50.820> devices<00:18:51.299> to<00:18:51.780> relate<00:18:52.140> to<00:18:52.440> a<00:18:52.679> wallet 00:18:53.029 --> 00:18:53.039 align:start position:0% using devices to relate to a wallet 00:18:53.039 --> 00:18:55.130 align:start position:0% using devices to relate to a wallet differently<00:18:53.460> rather<00:18:54.240> than<00:18:54.419> having<00:18:54.780> a 00:18:55.130 --> 00:18:55.140 align:start position:0% differently rather than having a 00:18:55.140 --> 00:18:56.990 align:start position:0% differently rather than having a different<00:18:55.320> wallet<00:18:55.860> on<00:18:56.220> every<00:18:56.400> single<00:18:56.760> device 00:18:56.990 --> 00:18:57.000 align:start position:0% different wallet on every single device 00:18:57.000 --> 00:18:58.909 align:start position:0% different wallet on every single device and<00:18:57.840> so<00:18:57.960> Julian<00:18:58.260> I<00:18:58.440> want<00:18:58.500> to<00:18:58.620> throw<00:18:58.679> this<00:18:58.860> one 00:18:58.909 --> 00:18:58.919 align:start position:0% and so Julian I want to throw this one 00:18:58.919 --> 00:18:59.930 align:start position:0% and so Julian I want to throw this one to<00:18:59.039> you<00:18:59.100> and<00:18:59.220> now<00:18:59.340> you<00:18:59.460> guys<00:18:59.580> are<00:18:59.700> thinking 00:18:59.930 --> 00:18:59.940 align:start position:0% to you and now you guys are thinking 00:18:59.940 --> 00:19:01.970 align:start position:0% to you and now you guys are thinking this<00:19:00.120> at<00:19:00.299> Argent<00:19:00.840> and<00:19:01.500> check<00:19:01.799> my 00:19:01.970 --> 00:19:01.980 align:start position:0% this at Argent and check my 00:19:01.980 --> 00:19:04.130 align:start position:0% this at Argent and check my understanding<00:19:02.400> here<00:19:02.580> is<00:19:02.700> like<00:19:03.000> I've<00:19:03.660> got<00:19:03.840> I've 00:19:04.130 --> 00:19:04.140 align:start position:0% understanding here is like I've got I've 00:19:04.140 --> 00:19:05.810 align:start position:0% understanding here is like I've got I've got<00:19:04.260> a<00:19:04.380> wallet<00:19:04.620> here<00:19:04.740> on<00:19:04.860> my<00:19:04.980> phone<00:19:05.039> I've<00:19:05.400> got<00:19:05.580> a 00:19:05.810 --> 00:19:05.820 align:start position:0% got a wallet here on my phone I've got a 00:19:05.820 --> 00:19:07.430 align:start position:0% got a wallet here on my phone I've got a wallet<00:19:06.120> on<00:19:06.299> my<00:19:06.419> my<00:19:06.600> metamask<00:19:07.020> on<00:19:07.200> my<00:19:07.380> computer 00:19:07.430 --> 00:19:07.440 align:start position:0% wallet on my my metamask on my computer 00:19:07.440 --> 00:19:09.590 align:start position:0% wallet on my my metamask on my computer I've<00:19:07.860> got<00:19:08.039> a<00:19:08.280> wallet<00:19:08.580> on<00:19:08.760> my<00:19:08.880> ledger<00:19:09.179> there's 00:19:09.590 --> 00:19:09.600 align:start position:0% I've got a wallet on my ledger there's 00:19:09.600 --> 00:19:11.630 align:start position:0% I've got a wallet on my ledger there's three<00:19:09.840> different<00:19:09.960> wallets<00:19:10.380> but<00:19:11.340> now<00:19:11.520> we're 00:19:11.630 --> 00:19:11.640 align:start position:0% three different wallets but now we're 00:19:11.640 --> 00:19:13.310 align:start position:0% three different wallets but now we're talking<00:19:11.820> about<00:19:12.120> three<00:19:12.539> different<00:19:12.720> ways<00:19:13.080> of 00:19:13.310 --> 00:19:13.320 align:start position:0% talking about three different ways of 00:19:13.320 --> 00:19:16.010 align:start position:0% talking about three different ways of interfacing<00:19:14.039> with<00:19:14.340> the<00:19:14.580> same<00:19:14.760> wallet<00:19:15.240> which 00:19:16.010 --> 00:19:16.020 align:start position:0% interfacing with the same wallet which 00:19:16.020 --> 00:19:17.450 align:start position:0% interfacing with the same wallet which is<00:19:16.140> a<00:19:16.320> different<00:19:16.440> different<00:19:16.860> kind<00:19:17.220> of<00:19:17.280> just 00:19:17.450 --> 00:19:17.460 align:start position:0% is a different different kind of just 00:19:17.460 --> 00:19:19.190 align:start position:0% is a different different kind of just organizational<00:19:17.940> structure<00:19:18.419> so<00:19:18.840> do<00:19:18.960> you<00:19:19.080> think 00:19:19.190 --> 00:19:19.200 align:start position:0% organizational structure so do you think 00:19:19.200 --> 00:19:20.810 align:start position:0% organizational structure so do you think that<00:19:19.380> like<00:19:19.679> we're<00:19:20.160> just<00:19:20.280> going<00:19:20.400> to<00:19:20.460> be<00:19:20.580> able<00:19:20.640> to 00:19:20.810 --> 00:19:20.820 align:start position:0% that like we're just going to be able to 00:19:20.820 --> 00:19:22.789 align:start position:0% that like we're just going to be able to kill<00:19:21.120> most<00:19:21.539> of<00:19:21.660> the<00:19:21.780> wallets<00:19:22.080> all<00:19:22.500> these<00:19:22.679> like 00:19:22.789 --> 00:19:22.799 align:start position:0% kill most of the wallets all these like 00:19:22.799 --> 00:19:24.470 align:start position:0% kill most of the wallets all these like throwaway<00:19:23.400> wallets<00:19:23.760> that<00:19:23.940> we<00:19:24.059> use<00:19:24.179> and 00:19:24.470 --> 00:19:24.480 align:start position:0% throwaway wallets that we use and 00:19:24.480 --> 00:19:26.390 align:start position:0% throwaway wallets that we use and instead<00:19:24.960> of<00:19:25.320> like<00:19:25.500> having<00:19:25.740> a<00:19:26.039> little<00:19:26.100> bit<00:19:26.280> of 00:19:26.390 --> 00:19:26.400 align:start position:0% instead of like having a little bit of 00:19:26.400 --> 00:19:27.770 align:start position:0% instead of like having a little bit of cash<00:19:26.520> in<00:19:26.700> some<00:19:26.880> wallet<00:19:27.240> and<00:19:27.360> a<00:19:27.480> medium<00:19:27.600> amount 00:19:27.770 --> 00:19:27.780 align:start position:0% cash in some wallet and a medium amount 00:19:27.780 --> 00:19:29.029 align:start position:0% cash in some wallet and a medium amount of<00:19:27.900> cash<00:19:28.020> in<00:19:28.200> another<00:19:28.320> wallet<00:19:28.679> and<00:19:28.799> then<00:19:28.860> like 00:19:29.029 --> 00:19:29.039 align:start position:0% of cash in another wallet and then like 00:19:29.039 --> 00:19:30.590 align:start position:0% of cash in another wallet and then like cold<00:19:29.220> storage<00:19:29.460> it's<00:19:30.059> actually<00:19:30.240> going<00:19:30.419> to<00:19:30.539> be 00:19:30.590 --> 00:19:30.600 align:start position:0% cold storage it's actually going to be 00:19:30.600 --> 00:19:31.909 align:start position:0% cold storage it's actually going to be the<00:19:30.960> same<00:19:31.080> wallet<00:19:31.380> and<00:19:31.500> we<00:19:31.620> just<00:19:31.740> have 00:19:31.909 --> 00:19:31.919 align:start position:0% the same wallet and we just have 00:19:31.919 --> 00:19:33.710 align:start position:0% the same wallet and we just have different<00:19:32.100> levels<00:19:32.460> of<00:19:32.640> security<00:19:32.820> of<00:19:33.299> how<00:19:33.600> to 00:19:33.710 --> 00:19:33.720 align:start position:0% different levels of security of how to 00:19:33.720 --> 00:19:35.090 align:start position:0% different levels of security of how to access<00:19:33.900> these<00:19:34.380> things<00:19:34.440> how<00:19:34.799> are<00:19:34.980> you 00:19:35.090 --> 00:19:35.100 align:start position:0% access these things how are you 00:19:35.100 --> 00:19:37.789 align:start position:0% access these things how are you designing<00:19:35.460> Argent<00:19:35.940> to<00:19:36.320> work<00:19:37.320> inside<00:19:37.500> of<00:19:37.679> this 00:19:37.789 --> 00:19:37.799 align:start position:0% designing Argent to work inside of this 00:19:37.799 --> 00:19:39.590 align:start position:0% designing Argent to work inside of this Paradigm<00:19:38.340> I<00:19:38.700> think<00:19:38.820> the<00:19:38.940> first<00:19:39.120> thing<00:19:39.299> for<00:19:39.480> me 00:19:39.590 --> 00:19:39.600 align:start position:0% Paradigm I think the first thing for me 00:19:39.600 --> 00:19:41.210 align:start position:0% Paradigm I think the first thing for me and<00:19:39.840> the<00:19:40.020> beauty<00:19:40.140> of<00:19:40.380> account<00:19:40.500> obstruction<00:19:40.919> is 00:19:41.210 --> 00:19:41.220 align:start position:0% and the beauty of account obstruction is 00:19:41.220 --> 00:19:42.890 align:start position:0% and the beauty of account obstruction is that<00:19:41.400> you<00:19:41.640> can<00:19:41.700> choose<00:19:41.940> as<00:19:42.059> a<00:19:42.240> user<00:19:42.480> so<00:19:42.660> I<00:19:42.840> don't 00:19:42.890 --> 00:19:42.900 align:start position:0% that you can choose as a user so I don't 00:19:42.900 --> 00:19:44.450 align:start position:0% that you can choose as a user so I don't think<00:19:43.020> there's<00:19:43.200> one<00:19:43.440> model<00:19:43.679> that<00:19:44.039> fits<00:19:44.340> for 00:19:44.450 --> 00:19:44.460 align:start position:0% think there's one model that fits for 00:19:44.460 --> 00:19:46.130 align:start position:0% think there's one model that fits for anyone<00:19:44.820> there<00:19:45.360> are<00:19:45.480> users<00:19:45.720> that<00:19:45.900> may<00:19:46.020> want 00:19:46.130 --> 00:19:46.140 align:start position:0% anyone there are users that may want 00:19:46.140 --> 00:19:47.630 align:start position:0% anyone there are users that may want ones<00:19:46.620> who<00:19:46.740> have<00:19:46.860> different<00:19:46.980> accounts<00:19:47.460> for 00:19:47.630 --> 00:19:47.640 align:start position:0% ones who have different accounts for 00:19:47.640 --> 00:19:49.789 align:start position:0% ones who have different accounts for privacy<00:19:47.940> reasons<00:19:48.419> for<00:19:48.539> example<00:19:48.780> so<00:19:49.500> I<00:19:49.679> think 00:19:49.789 --> 00:19:49.799 align:start position:0% privacy reasons for example so I think 00:19:49.799 --> 00:19:51.830 align:start position:0% privacy reasons for example so I think there's<00:19:50.160> not<00:19:50.400> one<00:19:50.580> model<00:19:50.760> that<00:19:51.179> that<00:19:51.299> fits<00:19:51.720> all 00:19:51.830 --> 00:19:51.840 align:start position:0% there's not one model that that fits all 00:19:51.840 --> 00:19:54.230 align:start position:0% there's not one model that that fits all but<00:19:52.559> of<00:19:52.740> course<00:19:52.860> in<00:19:53.160> terms<00:19:53.460> of<00:19:53.580> origin<00:19:53.940> we<00:19:54.120> like 00:19:54.230 --> 00:19:54.240 align:start position:0% but of course in terms of origin we like 00:19:54.240 --> 00:19:55.909 align:start position:0% but of course in terms of origin we like to<00:19:54.360> see<00:19:54.419> the<00:19:54.660> origin<00:19:54.960> wallet<00:19:55.260> the<00:19:55.500> main 00:19:55.909 --> 00:19:55.919 align:start position:0% to see the origin wallet the main 00:19:55.919 --> 00:19:58.490 align:start position:0% to see the origin wallet the main account<00:19:56.100> if<00:19:56.400> you<00:19:56.520> want<00:19:56.640> as<00:19:57.419> your<00:19:57.660> identity<00:19:58.020> on 00:19:58.490 --> 00:19:58.500 align:start position:0% account if you want as your identity on 00:19:58.500 --> 00:20:01.730 align:start position:0% account if you want as your identity on chain<00:19:58.679> and<00:19:59.340> so<00:19:59.700> yes<00:19:59.880> having<00:20:00.179> the<00:20:00.419> ability<00:20:00.660> to 00:20:01.730 --> 00:20:01.740 align:start position:0% chain and so yes having the ability to 00:20:01.740 --> 00:20:04.370 align:start position:0% chain and so yes having the ability to choose<00:20:02.580> the<00:20:03.000> security<00:20:03.179> Associated<00:20:03.840> to<00:20:04.200> the 00:20:04.370 --> 00:20:04.380 align:start position:0% choose the security Associated to the 00:20:04.380 --> 00:20:06.770 align:start position:0% choose the security Associated to the key<00:20:04.559> that<00:20:04.919> that's<00:20:05.160> in<00:20:05.520> a<00:20:05.760> different<00:20:06.059> device<00:20:06.360> is 00:20:06.770 --> 00:20:06.780 align:start position:0% key that that's in a different device is 00:20:06.780 --> 00:20:08.870 align:start position:0% key that that's in a different device is of<00:20:06.960> course<00:20:07.080> very<00:20:07.380> very<00:20:07.620> important<00:20:08.100> and<00:20:08.640> so<00:20:08.760> at 00:20:08.870 --> 00:20:08.880 align:start position:0% of course very very important and so at 00:20:08.880 --> 00:20:10.549 align:start position:0% of course very very important and so at Arjun<00:20:09.240> we<00:20:09.419> are<00:20:09.539> researching<00:20:10.020> a<00:20:10.200> lot<00:20:10.440> of 00:20:10.549 --> 00:20:10.559 align:start position:0% Arjun we are researching a lot of 00:20:10.559 --> 00:20:11.870 align:start position:0% Arjun we are researching a lot of different<00:20:10.679> IDs<00:20:11.160> for<00:20:11.280> example<00:20:11.460> now<00:20:11.700> we're 00:20:11.870 --> 00:20:11.880 align:start position:0% different IDs for example now we're 00:20:11.880 --> 00:20:13.549 align:start position:0% different IDs for example now we're exploring<00:20:12.240> something<00:20:12.480> called<00:20:12.720> session<00:20:13.080> Keys 00:20:13.549 --> 00:20:13.559 align:start position:0% exploring something called session Keys 00:20:13.559 --> 00:20:16.549 align:start position:0% exploring something called session Keys is<00:20:13.980> the<00:20:14.220> idea<00:20:14.520> to<00:20:14.640> have<00:20:14.820> an<00:20:15.240> ephemeral<00:20:15.720> keys<00:20:16.140> to 00:20:16.549 --> 00:20:16.559 align:start position:0% is the idea to have an ephemeral keys to 00:20:16.559 --> 00:20:18.289 align:start position:0% is the idea to have an ephemeral keys to which<00:20:16.740> you<00:20:16.860> can<00:20:17.039> attach<00:20:17.400> very<00:20:17.940> strict 00:20:18.289 --> 00:20:18.299 align:start position:0% which you can attach very strict 00:20:18.299 --> 00:20:20.570 align:start position:0% which you can attach very strict policies<00:20:18.780> so<00:20:19.020> you<00:20:19.200> can<00:20:19.320> literally<00:20:19.980> say<00:20:20.340> this 00:20:20.570 --> 00:20:20.580 align:start position:0% policies so you can literally say this 00:20:20.580 --> 00:20:23.390 align:start position:0% policies so you can literally say this key<00:20:20.820> is<00:20:21.000> valid<00:20:21.360> for<00:20:21.660> 24<00:20:21.960> hours<00:20:22.380> and<00:20:23.100> it<00:20:23.220> can 00:20:23.390 --> 00:20:23.400 align:start position:0% key is valid for 24 hours and it can 00:20:23.400 --> 00:20:25.370 align:start position:0% key is valid for 24 hours and it can only<00:20:23.520> call<00:20:23.820> a<00:20:24.299> certain<00:20:24.480> method<00:20:24.900> on<00:20:25.080> a<00:20:25.260> certain 00:20:25.370 --> 00:20:25.380 align:start position:0% only call a certain method on a certain 00:20:25.380 --> 00:20:27.350 align:start position:0% only call a certain method on a certain certain<00:20:25.860> contract<00:20:26.340> and<00:20:26.820> so<00:20:27.000> you<00:20:27.120> can<00:20:27.240> imagine 00:20:27.350 --> 00:20:27.360 align:start position:0% certain contract and so you can imagine 00:20:27.360 --> 00:20:29.090 align:start position:0% certain contract and so you can imagine for<00:20:27.780> example<00:20:27.960> if<00:20:28.200> you<00:20:28.380> consider<00:20:28.679> that<00:20:28.919> your 00:20:29.090 --> 00:20:29.100 align:start position:0% for example if you consider that your 00:20:29.100 --> 00:20:30.529 align:start position:0% for example if you consider that your phone<00:20:29.280> is<00:20:29.460> more<00:20:29.580> secure<00:20:29.880> because<00:20:30.120> I<00:20:30.299> agree 00:20:30.529 --> 00:20:30.539 align:start position:0% phone is more secure because I agree 00:20:30.539 --> 00:20:32.270 align:start position:0% phone is more secure because I agree with<00:20:30.600> you<00:20:30.780> I<00:20:31.200> think<00:20:31.260> my<00:20:31.440> phone<00:20:31.620> is<00:20:31.799> more<00:20:31.980> secure 00:20:32.270 --> 00:20:32.280 align:start position:0% with you I think my phone is more secure 00:20:32.280 --> 00:20:34.610 align:start position:0% with you I think my phone is more secure than<00:20:32.460> my<00:20:32.640> laptop<00:20:32.940> but<00:20:33.780> maybe<00:20:34.020> I<00:20:34.320> can<00:20:34.440> actually 00:20:34.610 --> 00:20:34.620 align:start position:0% than my laptop but maybe I can actually 00:20:34.620 --> 00:20:36.710 align:start position:0% than my laptop but maybe I can actually have<00:20:34.980> a<00:20:35.220> key<00:20:35.640> on<00:20:35.820> my<00:20:35.940> laptop<00:20:36.240> that<00:20:36.600> has 00:20:36.710 --> 00:20:36.720 align:start position:0% have a key on my laptop that has 00:20:36.720 --> 00:20:39.110 align:start position:0% have a key on my laptop that has restricted<00:20:37.380> policies<00:20:37.860> and<00:20:38.160> so<00:20:38.280> that<00:20:38.460> kees<00:20:38.880> can 00:20:39.110 --> 00:20:39.120 align:start position:0% restricted policies and so that kees can 00:20:39.120 --> 00:20:41.570 align:start position:0% restricted policies and so that kees can do<00:20:39.240> certain<00:20:39.419> action<00:20:39.780> but<00:20:40.200> I<00:20:40.799> Define<00:20:40.980> exactly 00:20:41.570 --> 00:20:41.580 align:start position:0% do certain action but I Define exactly 00:20:41.580 --> 00:20:43.549 align:start position:0% do certain action but I Define exactly the<00:20:41.760> type<00:20:41.940> of<00:20:42.120> actions<00:20:42.539> and<00:20:42.840> and<00:20:43.080> the<00:20:43.320> rules 00:20:43.549 --> 00:20:43.559 align:start position:0% the type of actions and and the rules 00:20:43.559 --> 00:20:46.549 align:start position:0% the type of actions and and the rules that<00:20:43.740> are<00:20:43.919> associated<00:20:44.280> to<00:20:44.700> to<00:20:45.179> that<00:20:45.419> key<00:20:45.660> but 00:20:46.549 --> 00:20:46.559 align:start position:0% that are associated to to that key but 00:20:46.559 --> 00:20:47.750 align:start position:0% that are associated to to that key but to<00:20:46.740> answer<00:20:46.860> your<00:20:47.039> question<00:20:47.220> for<00:20:47.520> me<00:20:47.640> it's 00:20:47.750 --> 00:20:47.760 align:start position:0% to answer your question for me it's 00:20:47.760 --> 00:20:49.909 align:start position:0% to answer your question for me it's really<00:20:47.940> about<00:20:48.179> giving<00:20:48.960> the<00:20:49.200> choice<00:20:49.380> to<00:20:49.620> users 00:20:49.909 --> 00:20:49.919 align:start position:0% really about giving the choice to users 00:20:49.919 --> 00:20:51.470 align:start position:0% really about giving the choice to users and<00:20:50.100> I<00:20:50.220> think<00:20:50.340> that's<00:20:50.520> again<00:20:50.880> the<00:20:51.179> beauty<00:20:51.299> of 00:20:51.470 --> 00:20:51.480 align:start position:0% and I think that's again the beauty of 00:20:51.480 --> 00:20:53.090 align:start position:0% and I think that's again the beauty of Icon<00:20:51.780> obstruction<00:20:52.020> is<00:20:52.260> that<00:20:52.380> it<00:20:52.500> opens<00:20:52.919> a 00:20:53.090 --> 00:20:53.100 align:start position:0% Icon obstruction is that it opens a 00:20:53.100 --> 00:20:54.830 align:start position:0% Icon obstruction is that it opens a completely<00:20:53.400> new<00:20:53.640> design<00:20:53.820> space<00:20:54.240> for<00:20:54.480> what<00:20:54.660> an 00:20:54.830 --> 00:20:54.840 align:start position:0% completely new design space for what an 00:20:54.840 --> 00:20:56.750 align:start position:0% completely new design space for what an account<00:20:55.020> can<00:20:55.380> be<00:20:55.500> and<00:20:56.100> I<00:20:56.220> think<00:20:56.340> we<00:20:56.520> are<00:20:56.640> only 00:20:56.750 --> 00:20:56.760 align:start position:0% account can be and I think we are only 00:20:56.760 --> 00:20:58.909 align:start position:0% account can be and I think we are only scratching<00:20:57.240> the<00:20:57.419> surface<00:20:57.780> of<00:20:57.960> of<00:20:58.200> what<00:20:58.559> can<00:20:58.740> be 00:20:58.909 --> 00:20:58.919 align:start position:0% scratching the surface of of what can be 00:20:58.919 --> 00:21:00.830 align:start position:0% scratching the surface of of what can be done<00:20:59.039> at<00:20:59.220> origin<00:20:59.580> we<00:20:59.760> see<00:20:59.940> it<00:21:00.059> as<00:21:00.299> as<00:21:00.600> your 00:21:00.830 --> 00:21:00.840 align:start position:0% done at origin we see it as as your 00:21:00.840 --> 00:21:03.110 align:start position:0% done at origin we see it as as your identity<00:21:01.200> it's<00:21:01.380> your<00:21:01.679> our<00:21:02.100> account<00:21:02.340> you<00:21:03.000> may 00:21:03.110 --> 00:21:03.120 align:start position:0% identity it's your our account you may 00:21:03.120 --> 00:21:04.909 align:start position:0% identity it's your our account you may have<00:21:03.240> multiple<00:21:03.539> accounts<00:21:04.020> with 00:21:04.909 --> 00:21:04.919 align:start position:0% have multiple accounts with 00:21:04.919 --> 00:21:06.890 align:start position:0% have multiple accounts with different<00:21:05.400> rules<00:21:05.820> for<00:21:06.000> example<00:21:06.240> it's<00:21:06.480> a<00:21:06.780> good 00:21:06.890 --> 00:21:06.900 align:start position:0% different rules for example it's a good 00:21:06.900 --> 00:21:08.930 align:start position:0% different rules for example it's a good example<00:21:07.200> if<00:21:07.740> I'm<00:21:07.919> playing<00:21:08.100> an<00:21:08.280> Unchained<00:21:08.760> game 00:21:08.930 --> 00:21:08.940 align:start position:0% example if I'm playing an Unchained game 00:21:08.940 --> 00:21:11.029 align:start position:0% example if I'm playing an Unchained game I<00:21:09.419> may<00:21:09.600> not<00:21:09.780> want<00:21:09.960> to<00:21:10.080> play<00:21:10.320> a<00:21:10.500> non-chained 00:21:11.029 --> 00:21:11.039 align:start position:0% I may not want to play a non-chained 00:21:11.039 --> 00:21:13.190 align:start position:0% I may not want to play a non-chained game<00:21:11.160> on<00:21:11.400> which<00:21:11.580> I<00:21:11.880> have<00:21:12.000> say<00:21:12.179> 50<00:21:12.419> in<00:21:12.900> a<00:21:13.020> certain 00:21:13.190 --> 00:21:13.200 align:start position:0% game on which I have say 50 in a certain 00:21:13.200 --> 00:21:15.890 align:start position:0% game on which I have say 50 in a certain token<00:21:13.679> I<00:21:14.220> don't<00:21:14.340> want<00:21:14.640> to<00:21:14.820> play<00:21:15.360> that<00:21:15.600> game 00:21:15.890 --> 00:21:15.900 align:start position:0% token I don't want to play that game 00:21:15.900 --> 00:21:17.750 align:start position:0% token I don't want to play that game with<00:21:16.380> the<00:21:16.500> same<00:21:16.679> account<00:21:16.919> on<00:21:17.280> which<00:21:17.460> I<00:21:17.640> have 00:21:17.750 --> 00:21:17.760 align:start position:0% with the same account on which I have 00:21:17.760 --> 00:21:20.150 align:start position:0% with the same account on which I have all<00:21:17.940> my<00:21:18.179> savings<00:21:18.539> for<00:21:18.840> example<00:21:19.080> so<00:21:19.799> I<00:21:19.980> think 00:21:20.150 --> 00:21:20.160 align:start position:0% all my savings for example so I think 00:21:20.160 --> 00:21:21.830 align:start position:0% all my savings for example so I think having<00:21:20.400> the<00:21:20.760> ability<00:21:21.000> to<00:21:21.419> have<00:21:21.539> different 00:21:21.830 --> 00:21:21.840 align:start position:0% having the ability to have different 00:21:21.840 --> 00:21:23.690 align:start position:0% having the ability to have different account<00:21:22.200> with<00:21:22.620> different<00:21:22.980> rules<00:21:23.520> and 00:21:23.690 --> 00:21:23.700 align:start position:0% account with different rules and 00:21:23.700 --> 00:21:25.130 align:start position:0% account with different rules and different<00:21:23.880> logic<00:21:24.299> is<00:21:24.480> actually<00:21:24.720> what<00:21:24.960> account 00:21:25.130 --> 00:21:25.140 align:start position:0% different logic is actually what account 00:21:25.140 --> 00:21:26.630 align:start position:0% different logic is actually what account abstraction<00:21:25.620> brings 00:21:26.630 --> 00:21:26.640 align:start position:0% abstraction brings 00:21:26.640 --> 00:21:29.750 align:start position:0% abstraction brings and<00:21:27.179> I<00:21:27.539> I<00:21:27.780> think<00:21:28.020> I<00:21:28.440> just<00:21:28.559> wanted<00:21:28.980> to<00:21:29.159> add<00:21:29.400> that 00:21:29.750 --> 00:21:29.760 align:start position:0% and I I think I just wanted to add that 00:21:29.760 --> 00:21:33.230 align:start position:0% and I I think I just wanted to add that uh<00:21:30.179> for<00:21:30.539> even<00:21:31.080> for<00:21:31.559> privacy<00:21:31.980> reasons<00:21:32.520> you<00:21:33.059> want 00:21:33.230 --> 00:21:33.240 align:start position:0% uh for even for privacy reasons you want 00:21:33.240 --> 00:21:35.090 align:start position:0% uh for even for privacy reasons you want to<00:21:33.360> have<00:21:33.539> multiple<00:21:34.020> wallets<00:21:34.500> because<00:21:34.799> you 00:21:35.090 --> 00:21:35.100 align:start position:0% to have multiple wallets because you 00:21:35.100 --> 00:21:36.710 align:start position:0% to have multiple wallets because you don't<00:21:35.159> want<00:21:35.340> to<00:21:35.460> docs<00:21:35.940> yourself<00:21:36.059> everywhere 00:21:36.710 --> 00:21:36.720 align:start position:0% don't want to docs yourself everywhere 00:21:36.720 --> 00:21:39.770 align:start position:0% don't want to docs yourself everywhere uh<00:21:37.679> it's<00:21:37.919> still<00:21:38.100> the<00:21:38.460> fact<00:21:38.820> that<00:21:38.940> we<00:21:39.179> decouple 00:21:39.770 --> 00:21:39.780 align:start position:0% uh it's still the fact that we decouple 00:21:39.780 --> 00:21:42.230 align:start position:0% uh it's still the fact that we decouple the<00:21:40.200> we<00:21:40.440> decouple<00:21:40.860> the<00:21:41.039> device<00:21:41.220> and<00:21:41.580> the<00:21:41.820> keys 00:21:42.230 --> 00:21:42.240 align:start position:0% the we decouple the device and the keys 00:21:42.240 --> 00:21:44.630 align:start position:0% the we decouple the device and the keys from<00:21:42.480> the<00:21:42.600> wallets<00:21:42.960> means<00:21:43.860> that<00:21:43.980> you<00:21:44.280> can<00:21:44.400> have 00:21:44.630 --> 00:21:44.640 align:start position:0% from the wallets means that you can have 00:21:44.640 --> 00:21:46.370 align:start position:0% from the wallets means that you can have all<00:21:44.940> of<00:21:45.059> them<00:21:45.240> associated<00:21:45.900> with<00:21:46.200> a 00:21:46.370 --> 00:21:46.380 align:start position:0% all of them associated with a 00:21:46.380 --> 00:21:49.310 align:start position:0% all of them associated with a fingerprint<00:21:46.860> on<00:21:47.039> your<00:21:47.220> same<00:21:47.580> phone<00:21:48.120> so<00:21:49.020> you 00:21:49.310 --> 00:21:49.320 align:start position:0% fingerprint on your same phone so you 00:21:49.320 --> 00:21:51.289 align:start position:0% fingerprint on your same phone so you choose<00:21:49.559> which<00:21:49.799> one<00:21:50.039> you're<00:21:50.220> using<00:21:50.640> based<00:21:51.179> on 00:21:51.289 --> 00:21:51.299 align:start position:0% choose which one you're using based on 00:21:51.299 --> 00:21:54.049 align:start position:0% choose which one you're using based on whatever<00:21:51.659> privacy<00:21:52.380> you<00:21:52.860> want<00:21:52.980> to<00:21:53.100> have<00:21:53.220> but 00:21:54.049 --> 00:21:54.059 align:start position:0% whatever privacy you want to have but 00:21:54.059 --> 00:21:56.090 align:start position:0% whatever privacy you want to have but you<00:21:54.299> still<00:21:54.419> use<00:21:54.600> the<00:21:54.840> same<00:21:55.020> device 00:21:56.090 --> 00:21:56.100 align:start position:0% you still use the same device 00:21:56.100 --> 00:21:57.649 align:start position:0% you still use the same device you<00:21:56.580> don't<00:21:56.700> need<00:21:56.880> a<00:21:57.059> different<00:21:57.179> device<00:21:57.419> for 00:21:57.649 --> 00:21:57.659 align:start position:0% you don't need a different device for 00:21:57.659 --> 00:21:59.270 align:start position:0% you don't need a different device for each<00:21:57.840> wallet<00:21:58.200> I'm<00:21:58.679> going<00:21:58.799> to<00:21:58.860> turn<00:21:59.100> this 00:21:59.270 --> 00:21:59.280 align:start position:0% each wallet I'm going to turn this 00:21:59.280 --> 00:22:00.890 align:start position:0% each wallet I'm going to turn this conversation<00:21:59.700> to<00:21:59.940> how<00:22:00.179> we<00:22:00.360> actually<00:22:00.600> get 00:22:00.890 --> 00:22:00.900 align:start position:0% conversation to how we actually get 00:22:00.900 --> 00:22:02.810 align:start position:0% conversation to how we actually get account<00:22:01.140> abstraction<00:22:01.679> implemented<00:22:02.400> at<00:22:02.700> the 00:22:02.810 --> 00:22:02.820 align:start position:0% account abstraction implemented at the 00:22:02.820 --> 00:22:04.190 align:start position:0% account abstraction implemented at the layer<00:22:03.059> one<00:22:03.179> because<00:22:03.360> this<00:22:03.539> is<00:22:03.659> going<00:22:03.780> to<00:22:03.900> take 00:22:04.190 --> 00:22:04.200 align:start position:0% layer one because this is going to take 00:22:04.200 --> 00:22:06.110 align:start position:0% layer one because this is going to take a<00:22:04.679> an<00:22:04.980> EIP<00:22:05.280> this<00:22:05.580> is<00:22:05.700> going<00:22:05.760> to<00:22:05.820> take<00:22:05.940> a<00:22:06.059> hard 00:22:06.110 --> 00:22:06.120 align:start position:0% a an EIP this is going to take a hard 00:22:06.120 --> 00:22:08.630 align:start position:0% a an EIP this is going to take a hard Fork<00:22:06.419> to<00:22:06.539> get<00:22:06.659> this<00:22:06.840> into<00:22:07.080> ethereum<00:22:07.620> uh<00:22:08.400> and<00:22:08.580> I 00:22:08.630 --> 00:22:08.640 align:start position:0% Fork to get this into ethereum uh and I 00:22:08.640 --> 00:22:09.830 align:start position:0% Fork to get this into ethereum uh and I want<00:22:08.760> to<00:22:08.880> throw<00:22:08.940> this<00:22:09.059> one<00:22:09.179> to<00:22:09.299> vitalik<00:22:09.659> our 00:22:09.830 --> 00:22:09.840 align:start position:0% want to throw this one to vitalik our 00:22:09.840 --> 00:22:11.750 align:start position:0% want to throw this one to vitalik our resident<00:22:10.080> crypto<00:22:10.500> philosopher<00:22:10.980> here<00:22:11.220> uh 00:22:11.750 --> 00:22:11.760 align:start position:0% resident crypto philosopher here uh 00:22:11.760 --> 00:22:13.669 align:start position:0% resident crypto philosopher here uh crypto<00:22:12.000> loves<00:22:12.360> tribes<00:22:12.720> we<00:22:13.080> got<00:22:13.260> like<00:22:13.440> the 00:22:13.669 --> 00:22:13.679 align:start position:0% crypto loves tribes we got like the 00:22:13.679 --> 00:22:15.110 align:start position:0% crypto loves tribes we got like the layer<00:22:13.919> one<00:22:13.980> tribes<00:22:14.400> we've<00:22:14.640> got<00:22:14.700> the<00:22:14.760> layer<00:22:15.000> two 00:22:15.110 --> 00:22:15.120 align:start position:0% layer one tribes we've got the layer two 00:22:15.120 --> 00:22:17.810 align:start position:0% layer one tribes we've got the layer two tribes<00:22:15.659> are<00:22:16.320> there<00:22:16.440> like<00:22:16.740> uh<00:22:17.640> account 00:22:17.810 --> 00:22:17.820 align:start position:0% tribes are there like uh account 00:22:17.820 --> 00:22:19.549 align:start position:0% tribes are there like uh account abstraction<00:22:18.299> tribes<00:22:18.780> and<00:22:18.960> if<00:22:19.080> there<00:22:19.260> are<00:22:19.380> what 00:22:19.549 --> 00:22:19.559 align:start position:0% abstraction tribes and if there are what 00:22:19.559 --> 00:22:21.470 align:start position:0% abstraction tribes and if there are what do<00:22:19.740> they<00:22:19.860> fight<00:22:19.980> over 00:22:21.470 --> 00:22:21.480 align:start position:0% do they fight over 00:22:21.480 --> 00:22:24.049 align:start position:0% do they fight over I<00:22:21.900> mean<00:22:22.080> I<00:22:22.200> kind<00:22:22.679> of<00:22:22.799> feel<00:22:22.919> like<00:22:23.100> the<00:22:23.340> tribeness 00:22:24.049 --> 00:22:24.059 align:start position:0% I mean I kind of feel like the tribeness 00:22:24.059 --> 00:22:26.330 align:start position:0% I mean I kind of feel like the tribeness of<00:22:24.179> account<00:22:24.299> abstraction<00:22:24.960> is<00:22:25.320> like<00:22:25.679> a<00:22:26.220> bit 00:22:26.330 --> 00:22:26.340 align:start position:0% of account abstraction is like a bit 00:22:26.340 --> 00:22:29.149 align:start position:0% of account abstraction is like a bit overstated<00:22:26.940> in<00:22:27.600> that<00:22:27.840> I<00:22:28.140> don't<00:22:28.200> like<00:22:28.380> I<00:22:29.100> don't 00:22:29.149 --> 00:22:29.159 align:start position:0% overstated in that I don't like I don't 00:22:29.159 --> 00:22:30.950 align:start position:0% overstated in that I don't like I don't really<00:22:29.340> see<00:22:29.640> many<00:22:29.940> competing<00:22:30.480> camps<00:22:30.900> of 00:22:30.950 --> 00:22:30.960 align:start position:0% really see many competing camps of 00:22:30.960 --> 00:22:33.049 align:start position:0% really see many competing camps of approaches<00:22:31.440> for<00:22:31.740> like<00:22:31.980> let's<00:22:32.159> say<00:22:32.340> how<00:22:32.940> to 00:22:33.049 --> 00:22:33.059 align:start position:0% approaches for like let's say how to 00:22:33.059 --> 00:22:35.570 align:start position:0% approaches for like let's say how to solve<00:22:33.360> the<00:22:33.539> problem<00:22:33.780> of<00:22:34.440> uh<00:22:34.860> I<00:22:35.220> have<00:22:35.340> a<00:22:35.460> smart 00:22:35.570 --> 00:22:35.580 align:start position:0% solve the problem of uh I have a smart 00:22:35.580 --> 00:22:37.490 align:start position:0% solve the problem of uh I have a smart contract<00:22:36.000> as<00:22:36.179> well<00:22:36.240> and<00:22:36.600> I<00:22:36.780> want<00:22:36.960> to<00:22:37.200> be<00:22:37.320> able 00:22:37.490 --> 00:22:37.500 align:start position:0% contract as well and I want to be able 00:22:37.500 --> 00:22:40.190 align:start position:0% contract as well and I want to be able to<00:22:37.679> send<00:22:38.580> things<00:22:39.000> from<00:22:39.360> that<00:22:39.539> smart<00:22:39.720> contract 00:22:40.190 --> 00:22:40.200 align:start position:0% to send things from that smart contract 00:22:40.200 --> 00:22:42.710 align:start position:0% to send things from that smart contract wallet<00:22:40.740> without<00:22:41.179> needing<00:22:42.179> you<00:22:42.419> know<00:22:42.480> some 00:22:42.710 --> 00:22:42.720 align:start position:0% wallet without needing you know some 00:22:42.720 --> 00:22:44.330 align:start position:0% wallet without needing you know some third<00:22:42.900> party<00:22:43.140> to<00:22:43.380> wrap<00:22:43.559> my<00:22:43.740> transaction<00:22:44.100> and 00:22:44.330 --> 00:22:44.340 align:start position:0% third party to wrap my transaction and 00:22:44.340 --> 00:22:46.010 align:start position:0% third party to wrap my transaction and pay<00:22:44.520> 21<00:22:45.059> 000<00:22:45.120> gas<00:22:45.360> overhead<00:22:45.780> or<00:22:45.900> whatever 00:22:46.010 --> 00:22:46.020 align:start position:0% pay 21 000 gas overhead or whatever 00:22:46.020 --> 00:22:49.250 align:start position:0% pay 21 000 gas overhead or whatever right<00:22:46.440> but<00:22:47.039> there's<00:22:47.419> the<00:22:48.419> different<00:22:48.539> camps<00:22:49.140> I 00:22:49.250 --> 00:22:49.260 align:start position:0% right but there's the different camps I 00:22:49.260 --> 00:22:51.830 align:start position:0% right but there's the different camps I think<00:22:49.440> are<00:22:49.679> more<00:22:49.980> kind<00:22:50.280> of<00:22:50.400> just<00:22:50.720> groups<00:22:51.720> of 00:22:51.830 --> 00:22:51.840 align:start position:0% think are more kind of just groups of 00:22:51.840 --> 00:22:54.950 align:start position:0% think are more kind of just groups of people<00:22:52.080> that<00:22:52.740> came<00:22:53.700> into<00:22:54.000> the<00:22:54.299> space<00:22:54.600> of 00:22:54.950 --> 00:22:54.960 align:start position:0% people that came into the space of 00:22:54.960 --> 00:22:56.690 align:start position:0% people that came into the space of improving<00:22:55.620> accounts<00:22:56.100> with<00:22:56.340> different 00:22:56.690 --> 00:22:56.700 align:start position:0% improving accounts with different 00:22:56.700 --> 00:22:59.330 align:start position:0% improving accounts with different emphasis<00:22:57.299> right<00:22:57.600> so<00:22:57.900> like<00:22:58.140> the<00:22:58.740> like<00:22:59.039> the 00:22:59.330 --> 00:22:59.340 align:start position:0% emphasis right so like the like the 00:22:59.340 --> 00:23:01.610 align:start position:0% emphasis right so like the like the emphasis<00:22:59.700> that<00:22:59.820> I<00:23:00.000> came<00:23:00.120> with<00:23:00.360> is<00:23:00.780> solving<00:23:01.380> the 00:23:01.610 --> 00:23:01.620 align:start position:0% emphasis that I came with is solving the 00:23:01.620 --> 00:23:03.950 align:start position:0% emphasis that I came with is solving the yep<00:23:02.039> the<00:23:02.400> the<00:23:02.760> problem<00:23:03.120> of<00:23:03.419> like<00:23:03.600> how<00:23:03.720> to<00:23:03.840> make 00:23:03.950 --> 00:23:03.960 align:start position:0% yep the the problem of like how to make 00:23:03.960 --> 00:23:05.390 align:start position:0% yep the the problem of like how to make it<00:23:04.080> easier<00:23:04.380> for<00:23:04.559> people<00:23:04.799> to<00:23:04.980> have<00:23:05.159> Smart 00:23:05.390 --> 00:23:05.400 align:start position:0% it easier for people to have Smart 00:23:05.400 --> 00:23:06.649 align:start position:0% it easier for people to have Smart contract<00:23:05.760> while<00:23:06.059> it's<00:23:06.179> with<00:23:06.299> arbitrary 00:23:06.649 --> 00:23:06.659 align:start position:0% contract while it's with arbitrary 00:23:06.659 --> 00:23:09.370 align:start position:0% contract while it's with arbitrary validation<00:23:07.140> other<00:23:07.799> people<00:23:08.039> came<00:23:08.340> in<00:23:08.520> with<00:23:08.820> the 00:23:09.370 --> 00:23:09.380 align:start position:0% validation other people came in with the 00:23:09.380 --> 00:23:12.590 align:start position:0% validation other people came in with the emphasis<00:23:10.380> of<00:23:10.740> solving<00:23:11.340> the<00:23:11.520> yeah<00:23:11.880> problem<00:23:12.179> of 00:23:12.590 --> 00:23:12.600 align:start position:0% emphasis of solving the yeah problem of 00:23:12.600 --> 00:23:14.750 align:start position:0% emphasis of solving the yeah problem of how<00:23:13.200> to<00:23:13.320> let<00:23:13.500> people<00:23:13.740> pay<00:23:13.980> for<00:23:14.220> other<00:23:14.400> people's 00:23:14.750 --> 00:23:14.760 align:start position:0% how to let people pay for other people's 00:23:14.760 --> 00:23:17.149 align:start position:0% how to let people pay for other people's accounts<00:23:15.240> or<00:23:15.960> how<00:23:16.200> to<00:23:16.320> let<00:23:16.559> someone<00:23:16.740> who<00:23:16.980> has 00:23:17.149 --> 00:23:17.159 align:start position:0% accounts or how to let someone who has 00:23:17.159 --> 00:23:20.570 align:start position:0% accounts or how to let someone who has usdc<00:23:17.880> only<00:23:18.360> pay<00:23:18.720> other<00:23:19.080> fees<00:23:19.620> in<00:23:19.740> usdc<00:23:20.220> instead 00:23:20.570 --> 00:23:20.580 align:start position:0% usdc only pay other fees in usdc instead 00:23:20.580 --> 00:23:22.430 align:start position:0% usdc only pay other fees in usdc instead of<00:23:20.640> paying<00:23:20.880> fees<00:23:21.120> and<00:23:21.179> if 00:23:22.430 --> 00:23:22.440 align:start position:0% of paying fees and if 00:23:22.440 --> 00:23:25.250 align:start position:0% of paying fees and if um so<00:23:23.220> and<00:23:24.000> then<00:23:24.120> you<00:23:24.480> know<00:23:24.600> there's<00:23:24.840> also<00:23:25.080> the 00:23:25.250 --> 00:23:25.260 align:start position:0% um so and then you know there's also the 00:23:25.260 --> 00:23:27.289 align:start position:0% um so and then you know there's also the idea<00:23:25.679> problem<00:23:25.860> of<00:23:26.220> uh<00:23:26.400> how<00:23:26.700> to<00:23:26.820> let<00:23:26.940> an<00:23:27.179> account 00:23:27.289 --> 00:23:27.299 align:start position:0% idea problem of uh how to let an account 00:23:27.299 --> 00:23:29.210 align:start position:0% idea problem of uh how to let an account to<00:23:27.539> do<00:23:27.720> many<00:23:27.900> operations<00:23:28.320> in<00:23:28.559> one<00:23:28.740> transaction 00:23:29.210 --> 00:23:29.220 align:start position:0% to do many operations in one transaction 00:23:29.220 --> 00:23:32.390 align:start position:0% to do many operations in one transaction and<00:23:29.940> though<00:23:30.419> these<00:23:30.960> are<00:23:31.140> not<00:23:31.500> really<00:23:31.919> yeah 00:23:32.390 --> 00:23:32.400 align:start position:0% and though these are not really yeah 00:23:32.400 --> 00:23:34.549 align:start position:0% and though these are not really yeah they're<00:23:33.240> not<00:23:33.360> competing<00:23:33.900> goals<00:23:34.200> right<00:23:34.380> I 00:23:34.549 --> 00:23:34.559 align:start position:0% they're not competing goals right I 00:23:34.559 --> 00:23:35.870 align:start position:0% they're not competing goals right I think<00:23:34.740> they're<00:23:34.919> goals<00:23:35.280> that<00:23:35.460> like<00:23:35.640> everyone 00:23:35.870 --> 00:23:35.880 align:start position:0% think they're goals that like everyone 00:23:35.880 --> 00:23:39.049 align:start position:0% think they're goals that like everyone here<00:23:36.240> agrees<00:23:36.720> that<00:23:37.020> we<00:23:37.679> need<00:23:37.799> a<00:23:38.220> solution<00:23:38.820> that 00:23:39.049 --> 00:23:39.059 align:start position:0% here agrees that we need a solution that 00:23:39.059 --> 00:23:41.390 align:start position:0% here agrees that we need a solution that covers<00:23:39.419> all<00:23:39.600> of<00:23:39.720> them<00:23:39.840> right<00:23:40.020> and<00:23:40.380> I<00:23:40.559> think<00:23:40.740> you 00:23:41.390 --> 00:23:41.400 align:start position:0% covers all of them right and I think you 00:23:41.400 --> 00:23:43.610 align:start position:0% covers all of them right and I think you know<00:23:41.460> there's<00:23:41.760> uh<00:23:42.059> I<00:23:42.720> mean<00:23:42.840> different<00:23:43.320> ideas 00:23:43.610 --> 00:23:43.620 align:start position:0% know there's uh I mean different ideas 00:23:43.620 --> 00:23:45.110 align:start position:0% know there's uh I mean different ideas that<00:23:43.980> are<00:23:44.100> slowly<00:23:44.520> kind<00:23:44.700> of<00:23:44.760> convert 00:23:45.110 --> 00:23:45.120 align:start position:0% that are slowly kind of convert 00:23:45.120 --> 00:23:46.970 align:start position:0% that are slowly kind of convert converging<00:23:45.720> toward 00:23:46.970 --> 00:23:46.980 align:start position:0% converging toward 00:23:46.980 --> 00:23:49.310 align:start position:0% converging toward um some<00:23:47.460> architecture<00:23:48.299> that<00:23:48.659> can<00:23:48.840> that 00:23:49.310 --> 00:23:49.320 align:start position:0% um some architecture that can that 00:23:49.320 --> 00:23:51.590 align:start position:0% um some architecture that can that actually<00:23:49.620> does<00:23:50.039> kind<00:23:50.640> of<00:23:50.760> do<00:23:50.880> is<00:23:51.419> getting 00:23:51.590 --> 00:23:51.600 align:start position:0% actually does kind of do is getting 00:23:51.600 --> 00:23:52.850 align:start position:0% actually does kind of do is getting better<00:23:51.720> and<00:23:51.900> better<00:23:52.080> at<00:23:52.260> actually<00:23:52.440> fitting 00:23:52.850 --> 00:23:52.860 align:start position:0% better and better at actually fitting 00:23:52.860 --> 00:23:54.049 align:start position:0% better and better at actually fitting together 00:23:54.049 --> 00:23:54.059 align:start position:0% together 00:23:54.059 --> 00:23:56.390 align:start position:0% together um<00:23:54.179> and<00:23:54.659> in<00:23:55.380> service<00:23:55.620> of<00:23:55.860> like<00:23:56.039> how<00:23:56.159> to<00:23:56.280> get 00:23:56.390 --> 00:23:56.400 align:start position:0% um and in service of like how to get 00:23:56.400 --> 00:23:58.370 align:start position:0% um and in service of like how to get from<00:23:56.640> here<00:23:56.760> to<00:23:57.059> there<00:23:57.240> like<00:23:57.419> one<00:23:58.080> of<00:23:58.200> the 00:23:58.370 --> 00:23:58.380 align:start position:0% from here to there like one of the 00:23:58.380 --> 00:23:59.950 align:start position:0% from here to there like one of the differences<00:23:59.039> between 00:23:59.950 --> 00:23:59.960 align:start position:0% differences between 00:23:59.960 --> 00:24:03.890 align:start position:0% differences between eip2938<00:24:00.960> and<00:24:01.280> erc4337<00:24:02.280> right<00:24:02.580> is<00:24:02.760> that<00:24:02.940> 4337 00:24:03.890 --> 00:24:03.900 align:start position:0% eip2938 and erc4337 right is that 4337 00:24:03.900 --> 00:24:07.490 align:start position:0% eip2938 and erc4337 right is that 4337 is<00:24:04.080> an<00:24:04.200> ERC<00:24:04.559> is<00:24:04.740> 2938<00:24:05.400> is<00:24:05.520> an<00:24:05.700> EIP<00:24:05.940> and<00:24:06.480> 2938<00:24:07.320> is 00:24:07.490 --> 00:24:07.500 align:start position:0% is an ERC is 2938 is an EIP and 2938 is 00:24:07.500 --> 00:24:09.529 align:start position:0% is an ERC is 2938 is an EIP and 2938 is a<00:24:07.740> kind<00:24:07.919> of<00:24:08.100> boil<00:24:08.640> the<00:24:08.820> ocean<00:24:08.940> let's<00:24:09.299> change 00:24:09.529 --> 00:24:09.539 align:start position:0% a kind of boil the ocean let's change 00:24:09.539 --> 00:24:11.270 align:start position:0% a kind of boil the ocean let's change the<00:24:09.720> protocol<00:24:09.960> now<00:24:10.260> and<00:24:10.440> like<00:24:10.620> let's<00:24:10.799> you<00:24:11.159> know 00:24:11.270 --> 00:24:11.280 align:start position:0% the protocol now and like let's you know 00:24:11.280 --> 00:24:12.770 align:start position:0% the protocol now and like let's you know set<00:24:11.460> things<00:24:11.640> right<00:24:11.820> in<00:24:12.000> the<00:24:12.120> protocol<00:24:12.360> sort<00:24:12.659> of 00:24:12.770 --> 00:24:12.780 align:start position:0% set things right in the protocol sort of 00:24:12.780 --> 00:24:15.890 align:start position:0% set things right in the protocol sort of solution<00:24:13.520> 4337<00:24:14.520> is<00:24:15.000> an<00:24:15.299> extra<00:24:15.480> protocol 00:24:15.890 --> 00:24:15.900 align:start position:0% solution 4337 is an extra protocol 00:24:15.900 --> 00:24:18.049 align:start position:0% solution 4337 is an extra protocol solution<00:24:16.320> right<00:24:16.620> and<00:24:16.919> it's<00:24:17.039> a 00:24:18.049 --> 00:24:18.059 align:start position:0% solution right and it's a 00:24:18.059 --> 00:24:21.409 align:start position:0% solution right and it's a kind<00:24:18.960> of<00:24:19.280> analogous<00:24:20.280> to<00:24:20.520> sort<00:24:20.940> of<00:24:21.059> the<00:24:21.179> roll-up 00:24:21.409 --> 00:24:21.419 align:start position:0% kind of analogous to sort of the roll-up 00:24:21.419 --> 00:24:23.090 align:start position:0% kind of analogous to sort of the roll-up Centric<00:24:21.780> roadmap<00:24:22.200> in<00:24:22.380> some<00:24:22.500> way<00:24:22.679> right<00:24:22.860> which 00:24:23.090 --> 00:24:23.100 align:start position:0% Centric roadmap in some way right which 00:24:23.100 --> 00:24:25.130 align:start position:0% Centric roadmap in some way right which is<00:24:23.280> you<00:24:23.700> know<00:24:23.880> part<00:24:24.419> of<00:24:24.600> part<00:24:24.900> of<00:24:25.020> the 00:24:25.130 --> 00:24:25.140 align:start position:0% is you know part of part of the 00:24:25.140 --> 00:24:27.169 align:start position:0% is you know part of part of the motivation<00:24:25.500> there<00:24:25.799> is<00:24:26.039> like<00:24:26.220> the<00:24:26.640> core 00:24:27.169 --> 00:24:27.179 align:start position:0% motivation there is like the core 00:24:27.179 --> 00:24:28.669 align:start position:0% motivation there is like the core developers<00:24:27.539> are<00:24:27.780> busy<00:24:28.080> and<00:24:28.200> you<00:24:28.380> know<00:24:28.500> there's 00:24:28.669 --> 00:24:28.679 align:start position:0% developers are busy and you know there's 00:24:28.679 --> 00:24:30.169 align:start position:0% developers are busy and you know there's the<00:24:28.860> merge<00:24:29.220> and<00:24:29.400> there's<00:24:29.520> the<00:24:29.760> Surge<00:24:30.059> and 00:24:30.169 --> 00:24:30.179 align:start position:0% the merge and there's the Surge and 00:24:30.179 --> 00:24:31.909 align:start position:0% the merge and there's the Surge and there's<00:24:30.299> a<00:24:30.539> splurge<00:24:30.900> on<00:24:31.080> The<00:24:31.200> Purge<00:24:31.500> and<00:24:31.679> uh 00:24:31.909 --> 00:24:31.919 align:start position:0% there's a splurge on The Purge and uh 00:24:31.919 --> 00:24:33.409 align:start position:0% there's a splurge on The Purge and uh you<00:24:32.340> know<00:24:32.460> some<00:24:32.640> people<00:24:32.760> wants<00:24:33.179> to<00:24:33.299> call 00:24:33.409 --> 00:24:33.419 align:start position:0% you know some people wants to call 00:24:33.419 --> 00:24:35.990 align:start position:0% you know some people wants to call singles<00:24:33.840> to<00:24:34.020> what<00:24:34.140> finality<00:24:34.559> of<00:24:34.679> the<00:24:34.860> George 00:24:35.990 --> 00:24:36.000 align:start position:0% singles to what finality of the George 00:24:36.000 --> 00:24:37.909 align:start position:0% singles to what finality of the George um<00:24:36.059> but<00:24:36.480> uh 00:24:37.909 --> 00:24:37.919 align:start position:0% um but uh 00:24:37.919 --> 00:24:40.549 align:start position:0% um but uh you<00:24:38.340> know<00:24:38.460> the<00:24:38.700> yeah<00:24:39.059> and<00:24:40.020> then<00:24:40.140> you<00:24:40.500> know 00:24:40.549 --> 00:24:40.559 align:start position:0% you know the yeah and then you know 00:24:40.559 --> 00:24:43.669 align:start position:0% you know the yeah and then you know because<00:24:41.460> uh<00:24:41.820> 4337<00:24:42.480> is<00:24:42.659> an<00:24:42.780> ERC<00:24:43.140> we<00:24:43.380> can<00:24:43.440> kind<00:24:43.620> of 00:24:43.669 --> 00:24:43.679 align:start position:0% because uh 4337 is an ERC we can kind of 00:24:43.679 --> 00:24:45.649 align:start position:0% because uh 4337 is an ERC we can kind of work<00:24:43.860> on<00:24:44.039> it<00:24:44.159> separately<00:24:44.520> get<00:24:44.820> it<00:24:45.000> and<00:24:45.179> you 00:24:45.649 --> 00:24:45.659 align:start position:0% work on it separately get it and you 00:24:45.659 --> 00:24:47.270 align:start position:0% work on it separately get it and you know<00:24:45.720> have<00:24:45.960> a<00:24:46.140> small<00:24:46.260> amount<00:24:46.559> of<00:24:46.740> usage<00:24:47.100> just 00:24:47.270 --> 00:24:47.280 align:start position:0% know have a small amount of usage just 00:24:47.280 --> 00:24:49.310 align:start position:0% know have a small amount of usage just start<00:24:47.520> fairly<00:24:47.940> quickly<00:24:48.240> get<00:24:48.480> it<00:24:48.600> until<00:24:48.780> twos 00:24:49.310 --> 00:24:49.320 align:start position:0% start fairly quickly get it until twos 00:24:49.320 --> 00:24:51.529 align:start position:0% start fairly quickly get it until twos and<00:24:49.919> improve<00:24:50.460> it<00:24:50.520> from<00:24:50.640> there<00:24:50.820> from<00:24:51.360> there 00:24:51.529 --> 00:24:51.539 align:start position:0% and improve it from there from there 00:24:51.539 --> 00:24:54.409 align:start position:0% and improve it from there from there over<00:24:51.720> time<00:24:52.080> but<00:24:52.679> I<00:24:52.860> guess<00:24:52.980> the<00:24:53.220> the<00:24:53.760> one<00:24:54.240> kind 00:24:54.409 --> 00:24:54.419 align:start position:0% over time but I guess the the one kind 00:24:54.419 --> 00:24:55.850 align:start position:0% over time but I guess the the one kind of<00:24:54.539> big<00:24:54.659> difference<00:24:54.840> here<00:24:55.140> is<00:24:55.380> that<00:24:55.500> I<00:24:55.740> think 00:24:55.850 --> 00:24:55.860 align:start position:0% of big difference here is that I think 00:24:55.860 --> 00:24:58.310 align:start position:0% of big difference here is that I think over<00:24:56.700> time<00:24:57.059> like<00:24:57.419> especially<00:24:57.720> over<00:24:57.960> the<00:24:58.140> last 00:24:58.310 --> 00:24:58.320 align:start position:0% over time like especially over the last 00:24:58.320 --> 00:24:59.750 align:start position:0% over time like especially over the last year<00:24:58.500> there<00:24:58.799> has<00:24:58.919> been<00:24:59.100> this<00:24:59.280> realization 00:24:59.750 --> 00:24:59.760 align:start position:0% year there has been this realization 00:24:59.760 --> 00:25:03.649 align:start position:0% year there has been this realization that<00:25:00.240> like<00:25:00.840> we<00:25:01.140> do<00:25:01.320> want<00:25:01.740> eips<00:25:02.640> like<00:25:03.299> as<00:25:03.480> in 00:25:03.649 --> 00:25:03.659 align:start position:0% that like we do want eips like as in 00:25:03.659 --> 00:25:04.909 align:start position:0% that like we do want eips like as in things<00:25:03.960> that<00:25:04.140> hard<00:25:04.260> work<00:25:04.500> change<00:25:04.799> the 00:25:04.909 --> 00:25:04.919 align:start position:0% things that hard work change the 00:25:04.919 --> 00:25:07.070 align:start position:0% things that hard work change the ethereum<00:25:05.280> protocol<00:25:05.640> eventually<00:25:06.539> because 00:25:07.070 --> 00:25:07.080 align:start position:0% ethereum protocol eventually because 00:25:07.080 --> 00:25:09.770 align:start position:0% ethereum protocol eventually because like<00:25:07.380> we<00:25:07.620> do<00:25:07.799> want<00:25:08.039> to<00:25:08.220> upgrade<00:25:09.059> existing<00:25:09.480> EOS 00:25:09.770 --> 00:25:09.780 align:start position:0% like we do want to upgrade existing EOS 00:25:09.780 --> 00:25:12.770 align:start position:0% like we do want to upgrade existing EOS like<00:25:10.440> we<00:25:10.679> want<00:25:10.860> to<00:25:11.039> let<00:25:11.580> existing<00:25:12.120> users<00:25:12.539> that 00:25:12.770 --> 00:25:12.780 align:start position:0% like we want to let existing users that 00:25:12.780 --> 00:25:14.630 align:start position:0% like we want to let existing users that don't<00:25:12.960> want<00:25:13.200> to<00:25:13.440> you<00:25:13.860> know<00:25:13.980> go<00:25:14.159> through<00:25:14.340> the 00:25:14.630 --> 00:25:14.640 align:start position:0% don't want to you know go through the 00:25:14.640 --> 00:25:16.370 align:start position:0% don't want to you know go through the the<00:25:15.000> expense<00:25:15.360> of<00:25:15.539> just<00:25:15.720> completely<00:25:16.020> moving 00:25:16.370 --> 00:25:16.380 align:start position:0% the expense of just completely moving 00:25:16.380 --> 00:25:18.409 align:start position:0% the expense of just completely moving everything<00:25:16.559> from<00:25:16.919> their<00:25:17.100> current<00:25:17.340> account<00:25:17.640> to 00:25:18.409 --> 00:25:18.419 align:start position:0% everything from their current account to 00:25:18.419 --> 00:25:20.029 align:start position:0% everything from their current account to what<00:25:18.840> we<00:25:18.960> want<00:25:19.080> to<00:25:19.140> let<00:25:19.320> them<00:25:19.500> enjoy<00:25:19.860> the 00:25:20.029 --> 00:25:20.039 align:start position:0% what we want to let them enjoy the 00:25:20.039 --> 00:25:22.149 align:start position:0% what we want to let them enjoy the benefits<00:25:20.400> of<00:25:20.520> the<00:25:20.700> AI<00:25:21.179> new<00:25:21.360> system 00:25:22.149 --> 00:25:22.159 align:start position:0% benefits of the AI new system 00:25:22.159 --> 00:25:25.669 align:start position:0% benefits of the AI new system and<00:25:23.360> we<00:25:24.360> might<00:25:24.480> you<00:25:24.659> know<00:25:24.779> we<00:25:24.960> want<00:25:25.140> benefits 00:25:25.669 --> 00:25:25.679 align:start position:0% and we might you know we want benefits 00:25:25.679 --> 00:25:27.950 align:start position:0% and we might you know we want benefits like<00:25:25.980> say<00:25:26.220> yeah<00:25:26.460> you<00:25:27.000> know<00:25:27.120> sensor<00:25:27.779> any 00:25:27.950 --> 00:25:27.960 align:start position:0% like say yeah you know sensor any 00:25:27.960 --> 00:25:29.870 align:start position:0% like say yeah you know sensor any censorship<00:25:28.440> resistance<00:25:28.919> guarantees<00:25:29.580> that<00:25:29.760> we 00:25:29.870 --> 00:25:29.880 align:start position:0% censorship resistance guarantees that we 00:25:29.880 --> 00:25:31.549 align:start position:0% censorship resistance guarantees that we get<00:25:30.000> from<00:25:30.179> inclusionalists<00:25:30.960> so<00:25:31.080> I<00:25:31.140> would<00:25:31.380> want 00:25:31.549 --> 00:25:31.559 align:start position:0% get from inclusionalists so I would want 00:25:31.559 --> 00:25:32.990 align:start position:0% get from inclusionalists so I would want that<00:25:31.679> to<00:25:31.860> apply<00:25:32.039> to<00:25:32.159> account<00:25:32.340> obstructed 00:25:32.990 --> 00:25:33.000 align:start position:0% that to apply to account obstructed 00:25:33.000 --> 00:25:36.409 align:start position:0% that to apply to account obstructed operations<00:25:33.500> and<00:25:34.500> you<00:25:35.220> know<00:25:35.279> if<00:25:35.520> we<00:25:35.700> want<00:25:36.000> these 00:25:36.409 --> 00:25:36.419 align:start position:0% operations and you know if we want these 00:25:36.419 --> 00:25:37.970 align:start position:0% operations and you know if we want these different<00:25:36.779> things<00:25:37.080> to 00:25:37.970 --> 00:25:37.980 align:start position:0% different things to 00:25:37.980 --> 00:25:40.669 align:start position:0% different things to up<00:25:38.580> or<00:25:39.120> like<00:25:39.720> happened<00:25:40.020> then<00:25:40.320> that<00:25:40.500> does 00:25:40.669 --> 00:25:40.679 align:start position:0% up or like happened then that does 00:25:40.679 --> 00:25:42.590 align:start position:0% up or like happened then that does require<00:25:40.860> making<00:25:41.279> a<00:25:41.580> protocol<00:25:41.940> changes<00:25:42.419> right 00:25:42.590 --> 00:25:42.600 align:start position:0% require making a protocol changes right 00:25:42.600 --> 00:25:44.750 align:start position:0% require making a protocol changes right but<00:25:42.840> the<00:25:43.080> yeah<00:25:43.380> the<00:25:43.919> good<00:25:44.039> news<00:25:44.220> is<00:25:44.460> that<00:25:44.640> kind 00:25:44.750 --> 00:25:44.760 align:start position:0% but the yeah the good news is that kind 00:25:44.760 --> 00:25:47.750 align:start position:0% but the yeah the good news is that kind of<00:25:44.820> the<00:25:44.940> ERC<00:25:45.360> comes<00:25:45.779> first<00:25:45.960> and<00:25:46.320> the<00:25:46.679> EIP<00:25:47.460> has 00:25:47.750 --> 00:25:47.760 align:start position:0% of the ERC comes first and the EIP has 00:25:47.760 --> 00:25:49.070 align:start position:0% of the ERC comes first and the EIP has come<00:25:47.880> later<00:25:48.120> and<00:25:48.360> there's<00:25:48.480> a<00:25:48.720> lot<00:25:48.779> of<00:25:48.900> these 00:25:49.070 --> 00:25:49.080 align:start position:0% come later and there's a lot of these 00:25:49.080 --> 00:25:50.570 align:start position:0% come later and there's a lot of these kind<00:25:49.380> of<00:25:49.440> great<00:25:49.620> proposals<00:25:50.100> for<00:25:50.279> how<00:25:50.400> to<00:25:50.520> do 00:25:50.570 --> 00:25:50.580 align:start position:0% kind of great proposals for how to do 00:25:50.580 --> 00:25:53.510 align:start position:0% kind of great proposals for how to do these<00:25:50.820> uh<00:25:51.059> yeah<00:25:51.299> these<00:25:51.720> eips<00:25:52.080> and<00:25:52.500> like<00:25:53.100> there 00:25:53.510 --> 00:25:53.520 align:start position:0% these uh yeah these eips and like there 00:25:53.520 --> 00:25:55.570 align:start position:0% these uh yeah these eips and like there is<00:25:53.640> definitely<00:25:54.059> a<00:25:54.360> kind<00:25:54.539> of<00:25:54.659> a<00:25:55.200> deep 00:25:55.570 --> 00:25:55.580 align:start position:0% is definitely a kind of a deep 00:25:55.580 --> 00:25:58.130 align:start position:0% is definitely a kind of a deep multi-year<00:25:56.580> multi-stage<00:25:57.179> roadmap<00:25:57.659> involved 00:25:58.130 --> 00:25:58.140 align:start position:0% multi-year multi-stage roadmap involved 00:25:58.140 --> 00:25:59.930 align:start position:0% multi-year multi-stage roadmap involved where<00:25:58.380> like<00:25:58.740> it's<00:25:58.919> you<00:25:59.340> know<00:25:59.460> it<00:25:59.520> starts<00:25:59.880> off 00:25:59.930 --> 00:25:59.940 align:start position:0% where like it's you know it starts off 00:25:59.940 --> 00:26:02.810 align:start position:0% where like it's you know it starts off in<00:26:00.419> uh<00:26:00.720> kind<00:26:01.080> of<00:26:01.200> making<00:26:01.679> it<00:26:01.919> friendly<00:26:02.340> for<00:26:02.640> the 00:26:02.810 --> 00:26:02.820 align:start position:0% in uh kind of making it friendly for the 00:26:02.820 --> 00:26:04.850 align:start position:0% in uh kind of making it friendly for the API<00:26:03.179> people<00:26:03.360> that<00:26:03.779> kind<00:26:03.960> of<00:26:04.020> wants<00:26:04.380> to<00:26:04.440> Pioneer 00:26:04.850 --> 00:26:04.860 align:start position:0% API people that kind of wants to Pioneer 00:26:04.860 --> 00:26:06.470 align:start position:0% API people that kind of wants to Pioneer and<00:26:04.980> what<00:26:05.100> and<00:26:05.400> I<00:26:05.640> really<00:26:06.000> care<00:26:06.120> about<00:26:06.240> getting 00:26:06.470 --> 00:26:06.480 align:start position:0% and what and I really care about getting 00:26:06.480 --> 00:26:08.690 align:start position:0% and what and I really care about getting these<00:26:06.720> properties<00:26:07.380> um<00:26:07.380> early<00:26:07.740> and<00:26:08.039> then<00:26:08.220> you 00:26:08.690 --> 00:26:08.700 align:start position:0% these properties um early and then you 00:26:08.700 --> 00:26:10.130 align:start position:0% these properties um early and then you know<00:26:08.880> expanding<00:26:09.419> more<00:26:09.600> and<00:26:09.720> more<00:26:09.900> until 00:26:10.130 --> 00:26:10.140 align:start position:0% know expanding more and more until 00:26:10.140 --> 00:26:12.830 align:start position:0% know expanding more and more until finally<00:26:11.100> um<00:26:11.100> you<00:26:11.279> know<00:26:11.400> eoas<00:26:12.179> may<00:26:12.539> may 00:26:12.830 --> 00:26:12.840 align:start position:0% finally um you know eoas may may 00:26:12.840 --> 00:26:15.470 align:start position:0% finally um you know eoas may may actually<00:26:13.200> uh<00:26:13.620> you<00:26:14.580> know<00:26:14.700> finally<00:26:15.000> kind<00:26:15.240> of<00:26:15.360> go 00:26:15.470 --> 00:26:15.480 align:start position:0% actually uh you know finally kind of go 00:26:15.480 --> 00:26:16.789 align:start position:0% actually uh you know finally kind of go away<00:26:15.600> and<00:26:15.840> we<00:26:15.960> really<00:26:16.080> do<00:26:16.260> just<00:26:16.500> have<00:26:16.620> Smart 00:26:16.789 --> 00:26:16.799 align:start position:0% away and we really do just have Smart 00:26:16.799 --> 00:26:18.169 align:start position:0% away and we really do just have Smart contract<00:26:17.220> wallets<00:26:17.580> and<00:26:17.760> all<00:26:17.820> the<00:26:17.940> benefits 00:26:18.169 --> 00:26:18.179 align:start position:0% contract wallets and all the benefits 00:26:18.179 --> 00:26:20.510 align:start position:0% contract wallets and all the benefits are<00:26:18.299> available<00:26:18.419> for<00:26:18.840> everyone<00:26:18.960> so<00:26:19.860> if<00:26:20.220> I'm 00:26:20.510 --> 00:26:20.520 align:start position:0% are available for everyone so if I'm 00:26:20.520 --> 00:26:21.950 align:start position:0% are available for everyone so if I'm understanding<00:26:21.179> correctly<00:26:21.419> like<00:26:21.659> the<00:26:21.840> current 00:26:21.950 --> 00:26:21.960 align:start position:0% understanding correctly like the current 00:26:21.960 --> 00:26:23.930 align:start position:0% understanding correctly like the current state<00:26:22.320> of<00:26:22.679> account<00:26:22.860> instruction<00:26:23.159> development 00:26:23.930 --> 00:26:23.940 align:start position:0% state of account instruction development 00:26:23.940 --> 00:26:26.210 align:start position:0% state of account instruction development is<00:26:24.179> that<00:26:24.360> we<00:26:24.659> haven't<00:26:24.779> yet<00:26:25.140> come<00:26:25.440> to<00:26:25.679> consensus 00:26:26.210 --> 00:26:26.220 align:start position:0% is that we haven't yet come to consensus 00:26:26.220 --> 00:26:28.730 align:start position:0% is that we haven't yet come to consensus as<00:26:26.520> to<00:26:26.700> what<00:26:26.880> the<00:26:27.059> EIP<00:26:27.419> that<00:26:28.200> we<00:26:28.320> want<00:26:28.440> to<00:26:28.559> put 00:26:28.730 --> 00:26:28.740 align:start position:0% as to what the EIP that we want to put 00:26:28.740 --> 00:26:30.769 align:start position:0% as to what the EIP that we want to put into<00:26:28.919> the<00:26:29.039> ethereum<00:26:29.460> base<00:26:29.700> layer<00:26:30.000> is<00:26:30.120> like<00:26:30.419> we 00:26:30.769 --> 00:26:30.779 align:start position:0% into the ethereum base layer is like we 00:26:30.779 --> 00:26:33.409 align:start position:0% into the ethereum base layer is like we know<00:26:31.100> eip1559<00:26:32.100> we<00:26:32.340> totally<00:26:32.520> wanted<00:26:32.700> that<00:26:33.000> I 00:26:33.409 --> 00:26:33.419 align:start position:0% know eip1559 we totally wanted that I 00:26:33.419 --> 00:26:35.029 align:start position:0% know eip1559 we totally wanted that I don't<00:26:33.600> think<00:26:33.720> there<00:26:33.900> is<00:26:34.020> an<00:26:34.140> equivalent<00:26:34.559> EIP 00:26:35.029 --> 00:26:35.039 align:start position:0% don't think there is an equivalent EIP 00:26:35.039 --> 00:26:36.769 align:start position:0% don't think there is an equivalent EIP for<00:26:35.460> account<00:26:35.700> abstraction<00:26:36.179> that<00:26:36.419> we<00:26:36.600> have 00:26:36.769 --> 00:26:36.779 align:start position:0% for account abstraction that we have 00:26:36.779 --> 00:26:39.110 align:start position:0% for account abstraction that we have there<00:26:37.200> there<00:26:37.380> is<00:26:37.500> an<00:26:37.620> ERC<00:26:37.919> and<00:26:38.520> to<00:26:38.880> be<00:26:39.000> clear 00:26:39.110 --> 00:26:39.120 align:start position:0% there there is an ERC and to be clear 00:26:39.120 --> 00:26:40.610 align:start position:0% there there is an ERC and to be clear right<00:26:39.419> it's<00:26:39.600> important<00:26:40.020> to<00:26:40.080> remember<00:26:40.260> that 00:26:40.610 --> 00:26:40.620 align:start position:0% right it's important to remember that 00:26:40.620 --> 00:26:43.310 align:start position:0% right it's important to remember that like<00:26:40.860> with<00:26:41.460> just<00:26:41.760> the<00:26:41.940> ERC<00:26:42.419> we<00:26:42.960> can<00:26:43.140> already 00:26:43.310 --> 00:26:43.320 align:start position:0% like with just the ERC we can already 00:26:43.320 --> 00:26:44.930 align:start position:0% like with just the ERC we can already get<00:26:43.740> to<00:26:43.860> the<00:26:44.039> point<00:26:44.220> where<00:26:44.520> you<00:26:44.760> know<00:26:44.820> if 00:26:44.930 --> 00:26:44.940 align:start position:0% get to the point where you know if 00:26:44.940 --> 00:26:47.090 align:start position:0% get to the point where you know if people<00:26:45.179> wants<00:26:45.720> to<00:26:45.900> like<00:26:46.320> replace<00:26:46.559> their 00:26:47.090 --> 00:26:47.100 align:start position:0% people wants to like replace their 00:26:47.100 --> 00:26:49.130 align:start position:0% people wants to like replace their entire<00:26:47.580> activity<00:26:48.059> and<00:26:48.240> like<00:26:48.419> run<00:26:48.659> it<00:26:48.840> off<00:26:48.960> of 00:26:49.130 --> 00:26:49.140 align:start position:0% entire activity and like run it off of 00:26:49.140 --> 00:26:50.990 align:start position:0% entire activity and like run it off of account<00:26:49.679> abstracted<00:26:50.279> wallets<00:26:50.640> instead<00:26:50.940> of 00:26:50.990 --> 00:26:51.000 align:start position:0% account abstracted wallets instead of 00:26:51.000 --> 00:26:52.549 align:start position:0% account abstracted wallets instead of regular<00:26:51.240> ones<00:26:51.539> like<00:26:51.720> they<00:26:51.900> can<00:26:52.020> do<00:26:52.200> it<00:26:52.320> and<00:26:52.440> it 00:26:52.549 --> 00:26:52.559 align:start position:0% regular ones like they can do it and it 00:26:52.559 --> 00:26:55.130 align:start position:0% regular ones like they can do it and it works<00:26:52.740> reasonably<00:26:53.159> well<00:26:53.400> right<00:26:53.700> but<00:26:54.360> but<00:26:54.480> the 00:26:55.130 --> 00:26:55.140 align:start position:0% works reasonably well right but but the 00:26:55.140 --> 00:26:56.750 align:start position:0% works reasonably well right but but the EIP<00:26:55.440> is<00:26:55.799> for<00:26:55.919> the<00:26:56.039> second<00:26:56.159> stage<00:26:56.460> of<00:26:56.640> the 00:26:56.750 --> 00:26:56.760 align:start position:0% EIP is for the second stage of the 00:26:56.760 --> 00:26:58.490 align:start position:0% EIP is for the second stage of the roadmap<00:26:57.120> indeed<00:26:57.539> like<00:26:57.659> there<00:26:57.960> are<00:26:58.080> like<00:26:58.380> we 00:26:58.490 --> 00:26:58.500 align:start position:0% roadmap indeed like there are like we 00:26:58.500 --> 00:27:00.769 align:start position:0% roadmap indeed like there are like we didn't<00:26:58.740> there's<00:26:59.100> we<00:26:59.820> do<00:26:59.940> not<00:27:00.059> have<00:27:00.179> those<00:27:00.360> cips 00:27:00.769 --> 00:27:00.779 align:start position:0% didn't there's we do not have those cips 00:27:00.779 --> 00:27:02.450 align:start position:0% didn't there's we do not have those cips yet<00:27:01.080> they're<00:27:01.320> under<00:27:01.500> development<00:27:01.980> there's<00:27:02.460> um 00:27:02.450 --> 00:27:02.460 align:start position:0% yet they're under development there's um 00:27:02.460 --> 00:27:04.070 align:start position:0% yet they're under development there's um lots<00:27:02.820> of<00:27:02.880> different<00:27:03.059> there's<00:27:03.659> lots<00:27:04.020> of 00:27:04.070 --> 00:27:04.080 align:start position:0% lots of different there's lots of 00:27:04.080 --> 00:27:05.690 align:start position:0% lots of different there's lots of different<00:27:04.260> uh<00:27:04.500> different<00:27:04.980> ideas<00:27:05.220> and<00:27:05.520> it's 00:27:05.690 --> 00:27:05.700 align:start position:0% different uh different ideas and it's 00:27:05.700 --> 00:27:07.970 align:start position:0% different uh different ideas and it's still<00:27:05.880> solidifying<00:27:06.480> if<00:27:07.140> I<00:27:07.260> can<00:27:07.380> add<00:27:07.500> to<00:27:07.679> that<00:27:07.799> I 00:27:07.970 --> 00:27:07.980 align:start position:0% still solidifying if I can add to that I 00:27:07.980 --> 00:27:10.310 align:start position:0% still solidifying if I can add to that I think<00:27:08.159> I<00:27:08.880> was<00:27:09.000> I<00:27:09.120> was<00:27:09.299> saying<00:27:09.539> some<00:27:09.720> layer<00:27:10.080> twos 00:27:10.310 --> 00:27:10.320 align:start position:0% think I was I was saying some layer twos 00:27:10.320 --> 00:27:11.990 align:start position:0% think I was I was saying some layer twos are<00:27:10.620> actually<00:27:10.740> experimenting<00:27:11.580> on<00:27:11.700> that<00:27:11.820> if 00:27:11.990 --> 00:27:12.000 align:start position:0% are actually experimenting on that if 00:27:12.000 --> 00:27:13.610 align:start position:0% are actually experimenting on that if for<00:27:12.179> example<00:27:12.360> if<00:27:12.539> you<00:27:12.659> look<00:27:12.779> at<00:27:12.960> starknet<00:27:13.500> and 00:27:13.610 --> 00:27:13.620 align:start position:0% for example if you look at starknet and 00:27:13.620 --> 00:27:15.289 align:start position:0% for example if you look at starknet and zika<00:27:14.100> seeing<00:27:14.400> they<00:27:14.640> are<00:27:14.760> launching<00:27:15.059> with 00:27:15.289 --> 00:27:15.299 align:start position:0% zika seeing they are launching with 00:27:15.299 --> 00:27:17.210 align:start position:0% zika seeing they are launching with Native<00:27:15.480> icon<00:27:15.840> obstruction<00:27:16.140> which<00:27:17.039> is 00:27:17.210 --> 00:27:17.220 align:start position:0% Native icon obstruction which is 00:27:17.220 --> 00:27:20.450 align:start position:0% Native icon obstruction which is actually<00:27:17.340> inspired<00:27:18.000> by<00:27:18.440> erc4337<00:27:19.440> so<00:27:19.799> even<00:27:20.220> if 00:27:20.450 --> 00:27:20.460 align:start position:0% actually inspired by erc4337 so even if 00:27:20.460 --> 00:27:22.130 align:start position:0% actually inspired by erc4337 so even if it's<00:27:20.580> just<00:27:20.700> an<00:27:20.880> ERC<00:27:21.240> finale<00:27:21.539> ethereum<00:27:21.960> it's 00:27:22.130 --> 00:27:22.140 align:start position:0% it's just an ERC finale ethereum it's 00:27:22.140 --> 00:27:24.169 align:start position:0% it's just an ERC finale ethereum it's actually<00:27:22.320> inspiring<00:27:23.220> layer<00:27:23.520> 2's<00:27:23.880> that<00:27:24.000> can 00:27:24.169 --> 00:27:24.179 align:start position:0% actually inspiring layer 2's that can 00:27:24.179 --> 00:27:26.390 align:start position:0% actually inspiring layer 2's that can actually<00:27:24.360> try<00:27:25.020> to<00:27:25.380> implement<00:27:25.799> the<00:27:26.039> next<00:27:26.159> step 00:27:26.390 --> 00:27:26.400 align:start position:0% actually try to implement the next step 00:27:26.400 --> 00:27:28.430 align:start position:0% actually try to implement the next step which<00:27:27.000> I<00:27:27.120> think<00:27:27.240> will<00:27:27.419> come<00:27:27.600> in<00:27:27.720> a<00:27:27.840> later<00:27:27.960> EIP 00:27:28.430 --> 00:27:28.440 align:start position:0% which I think will come in a later EIP 00:27:28.440 --> 00:27:29.810 align:start position:0% which I think will come in a later EIP when<00:27:28.740> we<00:27:28.919> will<00:27:29.039> change<00:27:29.159> that<00:27:29.340> at<00:27:29.520> the<00:27:29.640> protocol 00:27:29.810 --> 00:27:29.820 align:start position:0% when we will change that at the protocol 00:27:29.820 --> 00:27:31.669 align:start position:0% when we will change that at the protocol level<00:27:30.059> on<00:27:30.299> only<00:27:30.480> a<00:27:30.720> one<00:27:30.840> but<00:27:31.260> I<00:27:31.380> think<00:27:31.500> it's 00:27:31.669 --> 00:27:31.679 align:start position:0% level on only a one but I think it's 00:27:31.679 --> 00:27:33.289 align:start position:0% level on only a one but I think it's interesting<00:27:32.220> to<00:27:32.400> realize<00:27:32.640> that<00:27:32.880> it's<00:27:33.059> already 00:27:33.289 --> 00:27:33.299 align:start position:0% interesting to realize that it's already 00:27:33.299 --> 00:27:35.390 align:start position:0% interesting to realize that it's already there<00:27:33.659> on<00:27:33.900> certain<00:27:34.140> Leo<00:27:34.500> tools<00:27:34.860> if<00:27:35.159> you<00:27:35.279> look 00:27:35.390 --> 00:27:35.400 align:start position:0% there on certain Leo tools if you look 00:27:35.400 --> 00:27:36.890 align:start position:0% there on certain Leo tools if you look at<00:27:35.520> stagnet<00:27:36.000> it's<00:27:36.120> still<00:27:36.240> in<00:27:36.419> Alpha<00:27:36.779> but 00:27:36.890 --> 00:27:36.900 align:start position:0% at stagnet it's still in Alpha but 00:27:36.900 --> 00:27:38.450 align:start position:0% at stagnet it's still in Alpha but actually<00:27:37.080> it<00:27:37.260> loans<00:27:37.559> with<00:27:37.620> Native<00:27:37.860> like<00:27:38.220> an 00:27:38.450 --> 00:27:38.460 align:start position:0% actually it loans with Native like an 00:27:38.460 --> 00:27:40.669 align:start position:0% actually it loans with Native like an abstraction<00:27:38.820> so<00:27:39.059> there's<00:27:39.240> no<00:27:39.419> more<00:27:39.539> eras<00:27:40.020> it's 00:27:40.669 --> 00:27:40.679 align:start position:0% abstraction so there's no more eras it's 00:27:40.679 --> 00:27:43.130 align:start position:0% abstraction so there's no more eras it's actually<00:27:40.919> trying<00:27:41.760> to<00:27:41.940> be<00:27:42.120> the<00:27:42.240> end<00:27:42.419> goal<00:27:42.779> and<00:27:42.960> I 00:27:43.130 --> 00:27:43.140 align:start position:0% actually trying to be the end goal and I 00:27:43.140 --> 00:27:44.870 align:start position:0% actually trying to be the end goal and I think<00:27:43.260> that<00:27:43.380> we<00:27:43.620> learn<00:27:43.740> a<00:27:44.100> lot<00:27:44.220> on<00:27:44.640> the<00:27:44.760> Star 00:27:44.870 --> 00:27:44.880 align:start position:0% think that we learn a lot on the Star 00:27:44.880 --> 00:27:46.669 align:start position:0% think that we learn a lot on the Star Credit<00:27:45.120> Simpson<00:27:45.720> that<00:27:46.080> we<00:27:46.200> can<00:27:46.320> then<00:27:46.440> bring 00:27:46.669 --> 00:27:46.679 align:start position:0% Credit Simpson that we can then bring 00:27:46.679 --> 00:27:49.190 align:start position:0% Credit Simpson that we can then bring back<00:27:46.860> to<00:27:47.400> the<00:27:47.520> next<00:27:47.640> CIP<00:27:48.059> that<00:27:48.480> will<00:27:48.659> put 00:27:49.190 --> 00:27:49.200 align:start position:0% back to the next CIP that will put 00:27:49.200 --> 00:27:51.830 align:start position:0% back to the next CIP that will put hopefully<00:27:49.620> 4337<00:27:50.400> to<00:27:50.700> the<00:27:50.880> one<00:27:51.240> layer<00:27:51.480> down<00:27:51.659> to 00:27:51.830 --> 00:27:51.840 align:start position:0% hopefully 4337 to the one layer down to 00:27:51.840 --> 00:27:53.450 align:start position:0% hopefully 4337 to the one layer down to the<00:27:51.960> protocol<00:27:52.140> level 00:27:53.450 --> 00:27:53.460 align:start position:0% the protocol level 00:27:53.460 --> 00:27:55.370 align:start position:0% the protocol level if<00:27:53.880> it's<00:27:54.000> okay<00:27:54.240> if<00:27:54.480> I<00:27:54.779> mean<00:27:54.900> just<00:27:55.080> make<00:27:55.260> a 00:27:55.370 --> 00:27:55.380 align:start position:0% if it's okay if I mean just make a 00:27:55.380 --> 00:27:57.890 align:start position:0% if it's okay if I mean just make a comment<00:27:55.679> on<00:27:55.860> this<00:27:56.039> I<00:27:56.760> think<00:27:56.940> that<00:27:57.240> this<00:27:57.480> idea 00:27:57.890 --> 00:27:57.900 align:start position:0% comment on this I think that this idea 00:27:57.900 --> 00:28:00.970 align:start position:0% comment on this I think that this idea of<00:27:58.440> layer<00:27:58.860> twos<00:27:59.279> experimenting<00:28:00.179> with<00:28:00.539> future 00:28:00.970 --> 00:28:00.980 align:start position:0% of layer twos experimenting with future 00:28:00.980 --> 00:28:03.230 align:start position:0% of layer twos experimenting with future potential<00:28:01.980> core<00:28:02.279> changes<00:28:02.700> to<00:28:02.820> the<00:28:02.940> ethereum 00:28:03.230 --> 00:28:03.240 align:start position:0% potential core changes to the ethereum 00:28:03.240 --> 00:28:04.789 align:start position:0% potential core changes to the ethereum protocol<00:28:03.480> is<00:28:03.659> really<00:28:03.840> interesting<00:28:04.200> and<00:28:04.740> I 00:28:04.789 --> 00:28:04.799 align:start position:0% protocol is really interesting and I 00:28:04.799 --> 00:28:06.890 align:start position:0% protocol is really interesting and I think<00:28:04.919> things<00:28:05.100> like<00:28:05.340> Stark<00:28:05.640> net<00:28:05.940> is<00:28:06.299> a<00:28:06.779> very 00:28:06.890 --> 00:28:06.900 align:start position:0% think things like Stark net is a very 00:28:06.900 --> 00:28:07.730 align:start position:0% think things like Stark net is a very interesting<00:28:07.140> place<00:28:07.320> for<00:28:07.440> it<00:28:07.559> to<00:28:07.620> happen 00:28:07.730 --> 00:28:07.740 align:start position:0% interesting place for it to happen 00:28:07.740 --> 00:28:09.350 align:start position:0% interesting place for it to happen because<00:28:07.980> it's<00:28:08.100> very<00:28:08.340> different<00:28:08.520> than<00:28:09.059> what 00:28:09.350 --> 00:28:09.360 align:start position:0% because it's very different than what 00:28:09.360 --> 00:28:10.789 align:start position:0% because it's very different than what the<00:28:09.419> evm<00:28:09.840> actually<00:28:10.020> looks<00:28:10.320> like<00:28:10.380> and<00:28:10.559> I<00:28:10.679> think 00:28:10.789 --> 00:28:10.799 align:start position:0% the evm actually looks like and I think 00:28:10.799 --> 00:28:12.710 align:start position:0% the evm actually looks like and I think it's<00:28:10.980> probably<00:28:11.220> the<00:28:11.520> right<00:28:11.700> place<00:28:12.000> for<00:28:12.600> those 00:28:12.710 --> 00:28:12.720 align:start position:0% it's probably the right place for those 00:28:12.720 --> 00:28:15.830 align:start position:0% it's probably the right place for those things<00:28:12.960> to<00:28:13.200> happen<00:28:13.340> but<00:28:14.340> I'm<00:28:14.700> still<00:28:15.179> hesitant 00:28:15.830 --> 00:28:15.840 align:start position:0% things to happen but I'm still hesitant 00:28:15.840 --> 00:28:18.110 align:start position:0% things to happen but I'm still hesitant about<00:28:16.279> understanding<00:28:17.279> how<00:28:17.580> this<00:28:17.700> is<00:28:17.820> going<00:28:18.000> to 00:28:18.110 --> 00:28:18.120 align:start position:0% about understanding how this is going to 00:28:18.120 --> 00:28:19.669 align:start position:0% about understanding how this is going to play<00:28:18.299> out<00:28:18.480> across<00:28:19.080> all<00:28:19.380> of<00:28:19.440> the<00:28:19.559> different 00:28:19.669 --> 00:28:19.679 align:start position:0% play out across all of the different 00:28:19.679 --> 00:28:22.250 align:start position:0% play out across all of the different layer<00:28:20.159> twos<00:28:20.400> because<00:28:21.059> we've<00:28:21.659> seen<00:28:21.900> over<00:28:22.080> the 00:28:22.250 --> 00:28:22.260 align:start position:0% layer twos because we've seen over the 00:28:22.260 --> 00:28:24.110 align:start position:0% layer twos because we've seen over the last<00:28:22.440> 18<00:28:22.740> months<00:28:23.159> there's<00:28:23.340> been<00:28:23.520> a<00:28:23.700> huge<00:28:23.880> push 00:28:24.110 --> 00:28:24.120 align:start position:0% last 18 months there's been a huge push 00:28:24.120 --> 00:28:26.690 align:start position:0% last 18 months there's been a huge push for<00:28:24.419> things<00:28:24.720> like<00:28:25.020> evm<00:28:25.799> equivalence<00:28:26.279> and 00:28:26.690 --> 00:28:26.700 align:start position:0% for things like evm equivalence and 00:28:26.700 --> 00:28:28.130 align:start position:0% for things like evm equivalence and having<00:28:27.059> something<00:28:27.299> that's<00:28:27.539> exactly<00:28:27.960> like 00:28:28.130 --> 00:28:28.140 align:start position:0% having something that's exactly like 00:28:28.140 --> 00:28:30.890 align:start position:0% having something that's exactly like ethereum<00:28:28.679> and<00:28:29.580> trying<00:28:30.000> to<00:28:30.179> bring<00:28:30.480> things<00:28:30.720> like 00:28:30.890 --> 00:28:30.900 align:start position:0% ethereum and trying to bring things like 00:28:30.900 --> 00:28:33.049 align:start position:0% ethereum and trying to bring things like 4337<00:28:31.559> into<00:28:31.740> the<00:28:31.919> protocol<00:28:32.159> I'm<00:28:32.460> not<00:28:32.640> sure<00:28:32.820> how 00:28:33.049 --> 00:28:33.059 align:start position:0% 4337 into the protocol I'm not sure how 00:28:33.059 --> 00:28:34.610 align:start position:0% 4337 into the protocol I'm not sure how it's<00:28:33.179> going<00:28:33.419> to<00:28:33.539> play<00:28:33.779> out<00:28:33.960> on<00:28:34.440> those 00:28:34.610 --> 00:28:34.620 align:start position:0% it's going to play out on those 00:28:34.620 --> 00:28:36.830 align:start position:0% it's going to play out on those different<00:28:34.799> types<00:28:35.100> of<00:28:35.159> systems<00:28:35.640> yeah<00:28:36.299> that's<00:28:36.600> a 00:28:36.830 --> 00:28:36.840 align:start position:0% different types of systems yeah that's a 00:28:36.840 --> 00:28:37.909 align:start position:0% different types of systems yeah that's a very<00:28:36.960> good<00:28:37.080> question<00:28:37.260> but<00:28:37.500> I<00:28:37.679> mean<00:28:37.799> we're 00:28:37.909 --> 00:28:37.919 align:start position:0% very good question but I mean we're 00:28:37.919 --> 00:28:39.830 align:start position:0% very good question but I mean we're discussing<00:28:38.460> with<00:28:38.760> some<00:28:39.000> of<00:28:39.120> the<00:28:39.299> team<00:28:39.480> like 00:28:39.830 --> 00:28:39.840 align:start position:0% discussing with some of the team like 00:28:39.840 --> 00:28:42.350 align:start position:0% discussing with some of the team like like<00:28:40.020> Alby<00:28:40.500> Trump<00:28:40.620> optimism<00:28:41.159> want<00:28:42.120> to<00:28:42.240> have 00:28:42.350 --> 00:28:42.360 align:start position:0% like Alby Trump optimism want to have 00:28:42.360 --> 00:28:43.669 align:start position:0% like Alby Trump optimism want to have that<00:28:42.480> evm<00:28:42.840> equivalence<00:28:43.200> but<00:28:43.380> they<00:28:43.500> all 00:28:43.669 --> 00:28:43.679 align:start position:0% that evm equivalence but they all 00:28:43.679 --> 00:28:45.230 align:start position:0% that evm equivalence but they all recognize<00:28:44.100> that<00:28:44.340> they'll<00:28:44.640> also<00:28:44.880> need<00:28:45.000> to<00:28:45.120> have 00:28:45.230 --> 00:28:45.240 align:start position:0% recognize that they'll also need to have 00:28:45.240 --> 00:28:47.390 align:start position:0% recognize that they'll also need to have account<00:28:45.419> abstraction<00:28:45.900> at<00:28:46.200> some<00:28:46.380> point<00:28:46.559> and<00:28:47.220> so 00:28:47.390 --> 00:28:47.400 align:start position:0% account abstraction at some point and so 00:28:47.400 --> 00:28:50.330 align:start position:0% account abstraction at some point and so they<00:28:48.240> want<00:28:48.419> to<00:28:48.600> capture<00:28:49.080> the<00:28:49.440> evm<00:28:49.919> ecosystem 00:28:50.330 --> 00:28:50.340 align:start position:0% they want to capture the evm ecosystem 00:28:50.340 --> 00:28:52.010 align:start position:0% they want to capture the evm ecosystem but<00:28:50.880> at<00:28:51.059> the<00:28:51.179> same<00:28:51.299> time<00:28:51.419> they<00:28:51.659> would<00:28:51.779> want<00:28:51.960> to 00:28:52.010 --> 00:28:52.020 align:start position:0% but at the same time they would want to 00:28:52.020 --> 00:28:53.330 align:start position:0% but at the same time they would want to have<00:28:52.140> a<00:28:52.320> construction<00:28:52.500> and<00:28:52.980> so<00:28:53.039> that 00:28:53.330 --> 00:28:53.340 align:start position:0% have a construction and so that 00:28:53.340 --> 00:28:55.789 align:start position:0% have a construction and so that conversation<00:28:54.120> is<00:28:54.360> on<00:28:54.600> right<00:28:54.900> now<00:28:55.080> and 00:28:55.789 --> 00:28:55.799 align:start position:0% conversation is on right now and 00:28:55.799 --> 00:28:57.409 align:start position:0% conversation is on right now and hopefully<00:28:56.220> we<00:28:56.400> can<00:28:56.520> find<00:28:56.700> a<00:28:56.880> path<00:28:57.120> to<00:28:57.299> make 00:28:57.409 --> 00:28:57.419 align:start position:0% hopefully we can find a path to make 00:28:57.419 --> 00:28:59.210 align:start position:0% hopefully we can find a path to make that<00:28:57.539> happen<00:28:57.720> on<00:28:58.020> on<00:28:58.260> these<00:28:58.679> you<00:28:58.799> know<00:28:58.919> these 00:28:59.210 --> 00:28:59.220 align:start position:0% that happen on on these you know these 00:28:59.220 --> 00:29:01.070 align:start position:0% that happen on on these you know these these<00:28:59.580> layer<00:28:59.760> twos<00:29:00.059> that<00:29:00.419> want<00:29:00.600> to<00:29:00.779> be<00:29:00.900> as 00:29:01.070 --> 00:29:01.080 align:start position:0% these layer twos that want to be as 00:29:01.080 --> 00:29:02.930 align:start position:0% these layer twos that want to be as close<00:29:01.260> as<00:29:01.500> possible<00:29:01.799> to<00:29:02.220> you<00:29:02.580> have<00:29:02.820> an 00:29:02.930 --> 00:29:02.940 align:start position:0% close as possible to you have an 00:29:02.940 --> 00:29:05.149 align:start position:0% close as possible to you have an equivalent<00:29:03.240> UFC<00:29:03.840> casing<00:29:04.200> V2<00:29:04.620> for<00:29:04.860> example 00:29:05.149 --> 00:29:05.159 align:start position:0% equivalent UFC casing V2 for example 00:29:05.159 --> 00:29:07.669 align:start position:0% equivalent UFC casing V2 for example that<00:29:05.520> wants<00:29:05.880> to<00:29:05.880> be<00:29:06.059> equivalent<00:29:07.020> but<00:29:07.260> also 00:29:07.669 --> 00:29:07.679 align:start position:0% that wants to be equivalent but also 00:29:07.679 --> 00:29:09.710 align:start position:0% that wants to be equivalent but also wants<00:29:07.919> to<00:29:07.980> have<00:29:08.100> a<00:29:08.279> kind<00:29:08.400> of<00:29:08.520> abstraction<00:29:08.820> so<00:29:09.539> I 00:29:09.710 --> 00:29:09.720 align:start position:0% wants to have a kind of abstraction so I 00:29:09.720 --> 00:29:12.409 align:start position:0% wants to have a kind of abstraction so I think<00:29:09.900> even<00:29:10.440> if<00:29:10.799> you're<00:29:11.039> going<00:29:11.460> for<00:29:11.820> the<00:29:12.000> evm 00:29:12.409 --> 00:29:12.419 align:start position:0% think even if you're going for the evm 00:29:12.419 --> 00:29:15.529 align:start position:0% think even if you're going for the evm equivalence<00:29:12.960> I<00:29:13.740> think<00:29:13.860> it's<00:29:14.039> good<00:29:14.340> to<00:29:14.700> try<00:29:15.000> to 00:29:15.529 --> 00:29:15.539 align:start position:0% equivalence I think it's good to try to 00:29:15.539 --> 00:29:17.990 align:start position:0% equivalence I think it's good to try to push<00:29:15.960> the<00:29:16.200> I<00:29:16.679> mean<00:29:16.799> modify<00:29:17.220> the<00:29:17.340> evml<00:29:17.760> a<00:29:17.940> little 00:29:17.990 --> 00:29:18.000 align:start position:0% push the I mean modify the evml a little 00:29:18.000 --> 00:29:20.029 align:start position:0% push the I mean modify the evml a little bit<00:29:18.120> so<00:29:18.299> that<00:29:18.480> you<00:29:18.600> can<00:29:18.720> still<00:29:18.899> capture<00:29:19.320> that 00:29:20.029 --> 00:29:20.039 align:start position:0% bit so that you can still capture that 00:29:20.039 --> 00:29:22.250 align:start position:0% bit so that you can still capture that that<00:29:20.279> compatibility<00:29:21.179> and<00:29:21.600> the<00:29:21.720> fact<00:29:21.840> that<00:29:22.080> you 00:29:22.250 --> 00:29:22.260 align:start position:0% that compatibility and the fact that you 00:29:22.260 --> 00:29:23.570 align:start position:0% that compatibility and the fact that you have<00:29:22.380> a<00:29:22.559> common<00:29:22.679> standard<00:29:23.159> with<00:29:23.399> different 00:29:23.570 --> 00:29:23.580 align:start position:0% have a common standard with different 00:29:23.580 --> 00:29:26.690 align:start position:0% have a common standard with different layer<00:29:23.940> tools<00:29:24.299> but<00:29:24.600> still<00:29:24.899> try<00:29:25.200> to<00:29:25.440> fix<00:29:26.340> some<00:29:26.580> of 00:29:26.690 --> 00:29:26.700 align:start position:0% layer tools but still try to fix some of 00:29:26.700 --> 00:29:28.370 align:start position:0% layer tools but still try to fix some of these<00:29:26.880> issues<00:29:27.120> if<00:29:27.360> you<00:29:27.659> can<00:29:27.779> so<00:29:27.960> I<00:29:28.140> think<00:29:28.200> this 00:29:28.370 --> 00:29:28.380 align:start position:0% these issues if you can so I think this 00:29:28.380 --> 00:29:30.289 align:start position:0% these issues if you can so I think this conversation<00:29:28.799> is<00:29:29.039> on<00:29:29.220> right<00:29:29.399> now<00:29:29.580> there's<00:29:30.120> no 00:29:30.289 --> 00:29:30.299 align:start position:0% conversation is on right now there's no 00:29:30.299 --> 00:29:33.529 align:start position:0% conversation is on right now there's no clear<00:29:30.539> path<00:29:31.020> yet<00:29:31.500> for<00:29:31.980> sure<00:29:32.120> but<00:29:33.120> I<00:29:33.299> do<00:29:33.360> think 00:29:33.529 --> 00:29:33.539 align:start position:0% clear path yet for sure but I do think 00:29:33.539 --> 00:29:35.269 align:start position:0% clear path yet for sure but I do think it<00:29:33.779> will<00:29:33.960> probably<00:29:34.200> append<00:29:34.559> on<00:29:34.740> layer<00:29:34.980> 2's 00:29:35.269 --> 00:29:35.279 align:start position:0% it will probably append on layer 2's 00:29:35.279 --> 00:29:37.070 align:start position:0% it will probably append on layer 2's before<00:29:35.340> it<00:29:35.520> will<00:29:35.640> happen<00:29:35.820> earlier<00:29:36.179> once<00:29:36.480> yeah 00:29:37.070 --> 00:29:37.080 align:start position:0% before it will happen earlier once yeah 00:29:37.080 --> 00:29:39.409 align:start position:0% before it will happen earlier once yeah I<00:29:37.200> mean<00:29:37.260> one<00:29:37.559> way<00:29:37.740> to<00:29:37.919> look<00:29:38.279> at<00:29:38.460> like<00:29:39.059> how<00:29:39.360> much 00:29:39.409 --> 00:29:39.419 align:start position:0% I mean one way to look at like how much 00:29:39.419 --> 00:29:41.149 align:start position:0% I mean one way to look at like how much equivalence<00:29:40.020> you<00:29:40.260> need<00:29:40.380> is<00:29:40.559> kind<00:29:40.740> of<00:29:40.799> from<00:29:40.980> the 00:29:41.149 --> 00:29:41.159 align:start position:0% equivalence you need is kind of from the 00:29:41.159 --> 00:29:44.029 align:start position:0% equivalence you need is kind of from the point<00:29:41.700> of<00:29:41.820> view<00:29:41.880> of<00:29:42.059> the<00:29:42.179> user<00:29:42.539> right<00:29:42.779> so<00:29:43.140> like 00:29:44.029 --> 00:29:44.039 align:start position:0% point of view of the user right so like 00:29:44.039 --> 00:29:46.130 align:start position:0% point of view of the user right so like I<00:29:44.399> have<00:29:44.580> you<00:29:44.820> know<00:29:44.880> my<00:29:45.059> ethereum<00:29:45.539> wallet<00:29:46.020> like 00:29:46.130 --> 00:29:46.140 align:start position:0% I have you know my ethereum wallet like 00:29:46.140 --> 00:29:49.669 align:start position:0% I have you know my ethereum wallet like zero<00:29:46.580> xd8da<00:29:47.580> blah<00:29:47.880> blah<00:29:48.059> blah<00:29:48.299> and<00:29:48.720> one<00:29:49.380> of<00:29:49.559> the 00:29:49.669 --> 00:29:49.679 align:start position:0% zero xd8da blah blah blah and one of the 00:29:49.679 --> 00:29:52.850 align:start position:0% zero xd8da blah blah blah and one of the nice<00:29:49.799> things<00:29:50.039> that<00:29:50.820> um<00:29:50.820> the<00:29:51.659> eoas<00:29:52.260> offer<00:29:52.679> is 00:29:52.850 --> 00:29:52.860 align:start position:0% nice things that um the eoas offer is 00:29:52.860 --> 00:29:55.370 align:start position:0% nice things that um the eoas offer is that<00:29:53.279> neck<00:29:53.760> one<00:29:54.120> with<00:29:54.539> just<00:29:54.720> the<00:29:54.899> same<00:29:55.020> wallet 00:29:55.370 --> 00:29:55.380 align:start position:0% that neck one with just the same wallet 00:29:55.380 --> 00:29:57.110 align:start position:0% that neck one with just the same wallet the<00:29:55.620> same<00:29:55.740> code<00:29:55.919> the<00:29:56.220> same<00:29:56.399> key<00:29:56.580> scheme<00:29:56.940> the 00:29:57.110 --> 00:29:57.120 align:start position:0% the same code the same key scheme the 00:29:57.120 --> 00:29:58.669 align:start position:0% the same code the same key scheme the same<00:29:57.240> everything<00:29:57.480> I<00:29:58.140> can<00:29:58.260> just<00:29:58.440> you<00:29:58.559> know 00:29:58.669 --> 00:29:58.679 align:start position:0% same everything I can just you know 00:29:58.679 --> 00:30:01.070 align:start position:0% same everything I can just you know switch<00:29:58.860> to<00:29:59.039> all<00:29:59.220> optimism<00:29:59.640> and<00:30:00.179> with<00:30:00.419> the<00:30:00.600> send 00:30:01.070 --> 00:30:01.080 align:start position:0% switch to all optimism and with the send 00:30:01.080 --> 00:30:02.389 align:start position:0% switch to all optimism and with the send the<00:30:01.200> transaction<00:30:01.440> on<00:30:01.620> optimism<00:30:01.919> switch<00:30:02.220> to 00:30:02.389 --> 00:30:02.399 align:start position:0% the transaction on optimism switch to 00:30:02.399 --> 00:30:04.250 align:start position:0% the transaction on optimism switch to Arbitrage<00:30:02.820> and<00:30:02.940> transaction<00:30:03.299> on<00:30:03.600> arbitrum 00:30:04.250 --> 00:30:04.260 align:start position:0% Arbitrage and transaction on arbitrum 00:30:04.260 --> 00:30:07.250 align:start position:0% Arbitrage and transaction on arbitrum and<00:30:04.740> so<00:30:05.100> forth<00:30:05.340> right<00:30:05.580> the<00:30:06.179> other<00:30:06.600> benefit<00:30:06.899> is 00:30:07.250 --> 00:30:07.260 align:start position:0% and so forth right the other benefit is 00:30:07.260 --> 00:30:08.930 align:start position:0% and so forth right the other benefit is that<00:30:07.500> I<00:30:07.679> get<00:30:07.740> the<00:30:07.919> exact<00:30:08.159> same<00:30:08.340> address<00:30:08.580> like 00:30:08.930 --> 00:30:08.940 align:start position:0% that I get the exact same address like 00:30:08.940 --> 00:30:11.269 align:start position:0% that I get the exact same address like you<00:30:09.179> can<00:30:09.299> go<00:30:09.419> and<00:30:09.600> send<00:30:09.779> things<00:30:09.960> to<00:30:10.200> Xerox<00:30:10.500> d88 00:30:11.269 --> 00:30:11.279 align:start position:0% you can go and send things to Xerox d88 00:30:11.279 --> 00:30:13.190 align:start position:0% you can go and send things to Xerox d88 blah<00:30:11.580> blah<00:30:11.820> and<00:30:11.880> optimism<00:30:12.240> and<00:30:12.840> I'm<00:30:13.080> gonna 00:30:13.190 --> 00:30:13.200 align:start position:0% blah blah and optimism and I'm gonna 00:30:13.200 --> 00:30:14.750 align:start position:0% blah blah and optimism and I'm gonna have<00:30:13.440> them<00:30:13.620> right<00:30:13.799> or 00:30:14.750 --> 00:30:14.760 align:start position:0% have them right or 00:30:14.760 --> 00:30:17.149 align:start position:0% have them right or you<00:30:15.240> could<00:30:15.299> send<00:30:15.480> things<00:30:15.659> to<00:30:15.840> Xerox<00:30:16.260> data<00:30:16.860> blah 00:30:17.149 --> 00:30:17.159 align:start position:0% you could send things to Xerox data blah 00:30:17.159 --> 00:30:18.289 align:start position:0% you could send things to Xerox data blah blah<00:30:17.340> on<00:30:17.399> arbitrary<00:30:17.760> and<00:30:17.880> I'm<00:30:18.059> gonna<00:30:18.179> have 00:30:18.289 --> 00:30:18.299 align:start position:0% blah on arbitrary and I'm gonna have 00:30:18.299 --> 00:30:20.889 align:start position:0% blah on arbitrary and I'm gonna have them<00:30:18.480> right<00:30:18.980> and 00:30:20.889 --> 00:30:20.899 align:start position:0% them right and 00:30:20.899 --> 00:30:23.990 align:start position:0% them right and eip4337<00:30:21.899> like<00:30:22.200> you<00:30:22.320> know<00:30:22.440> it<00:30:22.860> does<00:30:23.039> try<00:30:23.760> hard 00:30:23.990 --> 00:30:24.000 align:start position:0% eip4337 like you know it does try hard 00:30:24.000 --> 00:30:25.549 align:start position:0% eip4337 like you know it does try hard to<00:30:24.240> make<00:30:24.419> that<00:30:24.659> possible<00:30:24.960> Right<00:30:25.200> like<00:30:25.380> it 00:30:25.549 --> 00:30:25.559 align:start position:0% to make that possible Right like it 00:30:25.559 --> 00:30:27.889 align:start position:0% to make that possible Right like it definitely<00:30:25.799> makes<00:30:26.039> it<00:30:26.220> possible<00:30:26.640> to<00:30:27.059> you<00:30:27.840> know 00:30:27.889 --> 00:30:27.899 align:start position:0% definitely makes it possible to you know 00:30:27.899 --> 00:30:30.710 align:start position:0% definitely makes it possible to you know use<00:30:28.200> the<00:30:28.559> same<00:30:28.740> con<00:30:29.399> the<00:30:29.940> same<00:30:30.059> code<00:30:30.240> and<00:30:30.539> have 00:30:30.710 --> 00:30:30.720 align:start position:0% use the same con the same code and have 00:30:30.720 --> 00:30:32.870 align:start position:0% use the same con the same code and have the<00:30:30.899> same<00:30:31.080> type<00:30:31.260> of<00:30:31.440> contract<00:30:31.740> while<00:30:31.980> on<00:30:32.279> all 00:30:32.870 --> 00:30:32.880 align:start position:0% the same type of contract while on all 00:30:32.880 --> 00:30:34.549 align:start position:0% the same type of contract while on all of<00:30:32.940> these<00:30:33.120> Roll-Ups<00:30:33.600> and<00:30:33.779> because<00:30:34.020> the 00:30:34.549 --> 00:30:34.559 align:start position:0% of these Roll-Ups and because the 00:30:34.559 --> 00:30:37.310 align:start position:0% of these Roll-Ups and because the Singleton<00:30:35.460> is<00:30:35.760> created<00:30:36.000> with<00:30:36.179> create<00:30:36.360> two 00:30:37.310 --> 00:30:37.320 align:start position:0% Singleton is created with create two 00:30:37.320 --> 00:30:38.930 align:start position:0% Singleton is created with create two um<00:30:37.380> you<00:30:37.500> it's<00:30:37.860> gonna<00:30:37.980> the<00:30:38.279> Singleton<00:30:38.580> is<00:30:38.760> going 00:30:38.930 --> 00:30:38.940 align:start position:0% um you it's gonna the Singleton is going 00:30:38.940 --> 00:30:40.310 align:start position:0% um you it's gonna the Singleton is going to<00:30:39.000> have<00:30:39.120> the<00:30:39.299> same<00:30:39.480> address<00:30:39.720> on<00:30:40.080> all<00:30:40.200> the 00:30:40.310 --> 00:30:40.320 align:start position:0% to have the same address on all the 00:30:40.320 --> 00:30:41.690 align:start position:0% to have the same address on all the Roll-Ups<00:30:40.740> and<00:30:40.799> so<00:30:40.980> you're<00:30:41.159> going<00:30:41.340> to<00:30:41.460> be<00:30:41.580> able 00:30:41.690 --> 00:30:41.700 align:start position:0% Roll-Ups and so you're going to be able 00:30:41.700 --> 00:30:44.090 align:start position:0% Roll-Ups and so you're going to be able to<00:30:41.820> uh<00:30:42.299> like<00:30:42.899> anything<00:30:43.260> derived<00:30:43.860> from<00:30:43.980> a 00:30:44.090 --> 00:30:44.100 align:start position:0% to uh like anything derived from a 00:30:44.100 --> 00:30:45.830 align:start position:0% to uh like anything derived from a Singleton<00:30:44.520> including<00:30:45.000> people<00:30:45.179> like<00:30:45.419> people's 00:30:45.830 --> 00:30:45.840 align:start position:0% Singleton including people like people's 00:30:45.840 --> 00:30:48.289 align:start position:0% Singleton including people like people's individual<00:30:46.260> wallets<00:30:46.740> are<00:30:47.460> also<00:30:47.820> going<00:30:48.059> to 00:30:48.289 --> 00:30:48.299 align:start position:0% individual wallets are also going to 00:30:48.299 --> 00:30:50.630 align:start position:0% individual wallets are also going to kind<00:30:48.899> of<00:30:49.020> have<00:30:49.140> the<00:30:49.380> same<00:30:49.500> addresses<00:30:49.980> right<00:30:50.220> so 00:30:50.630 --> 00:30:50.640 align:start position:0% kind of have the same addresses right so 00:30:50.640 --> 00:30:53.210 align:start position:0% kind of have the same addresses right so like<00:30:51.240> one<00:30:51.840> one<00:30:52.200> thing<00:30:52.500> that<00:30:52.799> you<00:30:53.039> know<00:30:53.100> like 00:30:53.210 --> 00:30:53.220 align:start position:0% like one one thing that you know like 00:30:53.220 --> 00:30:55.310 align:start position:0% like one one thing that you know like people<00:30:53.520> you<00:30:53.940> know<00:30:54.000> ZK<00:30:54.360> Stark<00:30:54.720> and<00:30:54.899> similar 00:30:55.310 --> 00:30:55.320 align:start position:0% people you know ZK Stark and similar 00:30:55.320 --> 00:30:57.889 align:start position:0% people you know ZK Stark and similar systems<00:30:55.620> could<00:30:55.860> do<00:30:55.980> is<00:30:56.159> like<00:30:56.460> try<00:30:57.179> to<00:30:57.419> achieve 00:30:57.889 --> 00:30:57.899 align:start position:0% systems could do is like try to achieve 00:30:57.899 --> 00:30:59.630 align:start position:0% systems could do is like try to achieve kind<00:30:58.140> of<00:30:58.260> like<00:30:58.440> that<00:30:58.860> code<00:30:59.039> in<00:30:59.220> Azure<00:30:59.460> s 00:30:59.630 --> 00:30:59.640 align:start position:0% kind of like that code in Azure s 00:30:59.640 --> 00:31:01.490 align:start position:0% kind of like that code in Azure s equivalence<00:31:00.120> for<00:31:00.539> example<00:31:00.840> you<00:31:01.200> know<00:31:01.260> even 00:31:01.490 --> 00:31:01.500 align:start position:0% equivalence for example you know even 00:31:01.500 --> 00:31:03.649 align:start position:0% equivalence for example you know even while<00:31:01.940> experimenting<00:31:02.940> what's<00:31:03.240> trying<00:31:03.480> to 00:31:03.649 --> 00:31:03.659 align:start position:0% while experimenting what's trying to 00:31:03.659 --> 00:31:05.149 align:start position:0% while experimenting what's trying to like<00:31:03.779> make<00:31:03.960> the<00:31:04.140> way<00:31:04.260> they<00:31:04.440> handle<00:31:04.740> operations 00:31:05.149 --> 00:31:05.159 align:start position:0% like make the way they handle operations 00:31:05.159 --> 00:31:07.669 align:start position:0% like make the way they handle operations much<00:31:05.460> cleaner<00:31:05.820> and<00:31:05.940> different<00:31:06.120> and<00:31:07.020> just<00:31:07.200> a<00:31:07.440> I 00:31:07.669 --> 00:31:07.679 align:start position:0% much cleaner and different and just a I 00:31:07.679 --> 00:31:09.049 align:start position:0% much cleaner and different and just a I want<00:31:07.980> to<00:31:08.039> go<00:31:08.159> back<00:31:08.220> to<00:31:08.340> what<00:31:08.460> Matt<00:31:08.700> was<00:31:08.880> saying 00:31:09.049 --> 00:31:09.059 align:start position:0% want to go back to what Matt was saying 00:31:09.059 --> 00:31:10.610 align:start position:0% want to go back to what Matt was saying just<00:31:09.299> to<00:31:09.480> really<00:31:09.720> drive<00:31:09.960> this<00:31:10.200> point<00:31:10.320> home 00:31:10.610 --> 00:31:10.620 align:start position:0% just to really drive this point home 00:31:10.620 --> 00:31:12.289 align:start position:0% just to really drive this point home about<00:31:10.919> how<00:31:11.279> layer<00:31:11.580> twos<00:31:11.880> are<00:31:12.059> going<00:31:12.120> to<00:31:12.240> be 00:31:12.289 --> 00:31:12.299 align:start position:0% about how layer twos are going to be 00:31:12.299 --> 00:31:14.330 align:start position:0% about how layer twos are going to be like<00:31:12.419> the<00:31:12.600> testing<00:31:12.899> bed<00:31:13.080> for<00:31:13.679> account 00:31:14.330 --> 00:31:14.340 align:start position:0% like the testing bed for account 00:31:14.340 --> 00:31:16.310 align:start position:0% like the testing bed for account abstract<00:31:14.700> action<00:31:15.120> Matt<00:31:15.659> can<00:31:15.840> you<00:31:16.020> just<00:31:16.140> kind 00:31:16.310 --> 00:31:16.320 align:start position:0% abstract action Matt can you just kind 00:31:16.320 --> 00:31:17.810 align:start position:0% abstract action Matt can you just kind of<00:31:16.380> walk<00:31:16.500> us<00:31:16.740> through<00:31:16.980> into<00:31:17.279> the<00:31:17.460> future<00:31:17.580> about 00:31:17.810 --> 00:31:17.820 align:start position:0% of walk us through into the future about 00:31:17.820 --> 00:31:20.090 align:start position:0% of walk us through into the future about how<00:31:18.120> you<00:31:18.240> think<00:31:18.419> this<00:31:18.600> may<00:31:18.779> play<00:31:18.960> out<00:31:19.140> like<00:31:19.440> ZK 00:31:20.090 --> 00:31:20.100 align:start position:0% how you think this may play out like ZK 00:31:20.100 --> 00:31:22.250 align:start position:0% how you think this may play out like ZK sync<00:31:20.520> does<00:31:20.760> some<00:31:21.059> sort<00:31:21.360> of<00:31:21.779> flavor<00:31:22.020> of<00:31:22.140> account 00:31:22.250 --> 00:31:22.260 align:start position:0% sync does some sort of flavor of account 00:31:22.260 --> 00:31:23.750 align:start position:0% sync does some sort of flavor of account abstractions<00:31:22.980> Dark<00:31:23.220> Knight<00:31:23.399> does<00:31:23.580> a 00:31:23.750 --> 00:31:23.760 align:start position:0% abstractions Dark Knight does a 00:31:23.760 --> 00:31:25.610 align:start position:0% abstractions Dark Knight does a different<00:31:23.880> one<00:31:24.120> the<00:31:24.720> market<00:31:24.899> decides<00:31:25.440> what 00:31:25.610 --> 00:31:25.620 align:start position:0% different one the market decides what 00:31:25.620 --> 00:31:27.350 align:start position:0% different one the market decides what they<00:31:25.740> like<00:31:25.919> we<00:31:26.220> sort<00:31:26.580> of<00:31:26.640> come<00:31:26.820> to<00:31:26.940> consensus 00:31:27.350 --> 00:31:27.360 align:start position:0% they like we sort of come to consensus 00:31:27.360 --> 00:31:29.570 align:start position:0% they like we sort of come to consensus as<00:31:27.600> to<00:31:27.779> what<00:31:27.899> features<00:31:28.320> should<00:31:28.980> be<00:31:29.159> pushed 00:31:29.570 --> 00:31:29.580 align:start position:0% as to what features should be pushed 00:31:29.580 --> 00:31:31.010 align:start position:0% as to what features should be pushed down<00:31:29.700> to<00:31:29.880> the<00:31:29.940> layer<00:31:30.179> one<00:31:30.299> how<00:31:30.539> is<00:31:30.779> this<00:31:30.899> going 00:31:31.010 --> 00:31:31.020 align:start position:0% down to the layer one how is this going 00:31:31.020 --> 00:31:32.389 align:start position:0% down to the layer one how is this going to<00:31:31.140> work<00:31:31.200> out<00:31:31.320> in<00:31:31.440> the<00:31:31.559> future<00:31:31.679> I<00:31:32.340> mean 00:31:32.389 --> 00:31:32.399 align:start position:0% to work out in the future I mean 00:31:32.399 --> 00:31:33.649 align:start position:0% to work out in the future I mean honestly<00:31:32.700> I'm<00:31:32.820> just<00:31:33.000> really<00:31:33.120> curious<00:31:33.419> to<00:31:33.539> see 00:31:33.649 --> 00:31:33.659 align:start position:0% honestly I'm just really curious to see 00:31:33.659 --> 00:31:35.889 align:start position:0% honestly I'm just really curious to see how<00:31:33.840> it<00:31:34.020> plays<00:31:34.320> out<00:31:34.380> in<00:31:34.559> the<00:31:34.679> future<00:31:34.799> I<00:31:35.640> think 00:31:35.889 --> 00:31:35.899 align:start position:0% how it plays out in the future I think 00:31:35.899 --> 00:31:38.570 align:start position:0% how it plays out in the future I think you<00:31:36.899> know<00:31:37.020> my<00:31:37.620> perspective<00:31:37.980> is<00:31:38.159> I'm<00:31:38.399> very 00:31:38.570 --> 00:31:38.580 align:start position:0% you know my perspective is I'm very 00:31:38.580 --> 00:31:40.010 align:start position:0% you know my perspective is I'm very worried<00:31:38.820> about<00:31:38.880> fragmentation<00:31:39.600> of<00:31:39.840> different 00:31:40.010 --> 00:31:40.020 align:start position:0% worried about fragmentation of different 00:31:40.020 --> 00:31:42.110 align:start position:0% worried about fragmentation of different approaches<00:31:40.559> and<00:31:41.220> I<00:31:41.340> think<00:31:41.460> if<00:31:41.640> we<00:31:41.820> think<00:31:41.940> about 00:31:42.110 --> 00:31:42.120 align:start position:0% approaches and I think if we think about 00:31:42.120 --> 00:31:45.169 align:start position:0% approaches and I think if we think about maybe<00:31:42.480> on<00:31:42.720> the<00:31:42.899> longer<00:31:43.799> time<00:31:44.340> skills<00:31:44.700> 10<00:31:44.940> years 00:31:45.169 --> 00:31:45.179 align:start position:0% maybe on the longer time skills 10 years 00:31:45.179 --> 00:31:47.870 align:start position:0% maybe on the longer time skills 10 years maybe<00:31:45.679> eventually<00:31:46.679> we'll<00:31:47.039> come<00:31:47.340> to<00:31:47.580> some 00:31:47.870 --> 00:31:47.880 align:start position:0% maybe eventually we'll come to some 00:31:47.880 --> 00:31:49.909 align:start position:0% maybe eventually we'll come to some Solution<00:31:48.179> that's<00:31:48.480> great<00:31:48.779> and<00:31:49.320> everybody<00:31:49.620> will 00:31:49.909 --> 00:31:49.919 align:start position:0% Solution that's great and everybody will 00:31:49.919 --> 00:31:52.549 align:start position:0% Solution that's great and everybody will do<00:31:50.100> it<00:31:50.220> just<00:31:50.399> because<00:31:50.580> all<00:31:50.940> the<00:31:51.179> other<00:31:51.360> uh<00:31:52.260> you 00:31:52.549 --> 00:31:52.559 align:start position:0% do it just because all the other uh you 00:31:52.559 --> 00:31:53.930 align:start position:0% do it just because all the other uh you know<00:31:52.679> all<00:31:52.919> the<00:31:53.100> other<00:31:53.220> companies<00:31:53.520> will<00:31:53.760> have 00:31:53.930 --> 00:31:53.940 align:start position:0% know all the other companies will have 00:31:53.940 --> 00:31:55.789 align:start position:0% know all the other companies will have have<00:31:54.240> run<00:31:54.480> out<00:31:54.659> of<00:31:54.779> money<00:31:54.960> and<00:31:55.260> you<00:31:55.559> know<00:31:55.679> left 00:31:55.789 --> 00:31:55.799 align:start position:0% have run out of money and you know left 00:31:55.799 --> 00:31:57.169 align:start position:0% have run out of money and you know left the<00:31:56.039> ecosystem 00:31:57.169 --> 00:31:57.179 align:start position:0% the ecosystem 00:31:57.179 --> 00:31:59.630 align:start position:0% the ecosystem but<00:31:57.779> I<00:31:57.960> think<00:31:58.140> I'm<00:31:58.919> very<00:31:59.039> worried<00:31:59.279> about<00:31:59.399> the 00:31:59.630 --> 00:31:59.640 align:start position:0% but I think I'm very worried about the 00:31:59.640 --> 00:32:01.010 align:start position:0% but I think I'm very worried about the like<00:31:59.760> shorter<00:32:00.059> term<00:32:00.179> like<00:32:00.480> three<00:32:00.659> to<00:32:00.840> five 00:32:01.010 --> 00:32:01.020 align:start position:0% like shorter term like three to five 00:32:01.020 --> 00:32:03.110 align:start position:0% like shorter term like three to five years<00:32:01.140> like<00:32:01.440> how<00:32:01.679> how<00:32:02.159> are<00:32:02.399> we<00:32:02.520> going<00:32:02.760> to<00:32:02.880> be 00:32:03.110 --> 00:32:03.120 align:start position:0% years like how how are we going to be 00:32:03.120 --> 00:32:04.970 align:start position:0% years like how how are we going to be able<00:32:03.299> to<00:32:03.720> bring<00:32:04.080> millions<00:32:04.500> of<00:32:04.620> people<00:32:04.740> into 00:32:04.970 --> 00:32:04.980 align:start position:0% able to bring millions of people into 00:32:04.980 --> 00:32:06.769 align:start position:0% able to bring millions of people into this<00:32:05.220> ecosystem<00:32:05.580> and<00:32:05.880> have<00:32:06.059> like<00:32:06.240> really<00:32:06.480> good 00:32:06.769 --> 00:32:06.779 align:start position:0% this ecosystem and have like really good 00:32:06.779 --> 00:32:09.710 align:start position:0% this ecosystem and have like really good experiences<00:32:07.620> using<00:32:08.100> applications<00:32:08.580> if<00:32:09.360> every 00:32:09.710 --> 00:32:09.720 align:start position:0% experiences using applications if every 00:32:09.720 --> 00:32:11.750 align:start position:0% experiences using applications if every single<00:32:10.140> protocol<00:32:10.919> has<00:32:11.220> a<00:32:11.340> different<00:32:11.460> way<00:32:11.640> of 00:32:11.750 --> 00:32:11.760 align:start position:0% single protocol has a different way of 00:32:11.760 --> 00:32:13.549 align:start position:0% single protocol has a different way of doing<00:32:11.880> account<00:32:12.120> abstraction<00:32:12.720> I<00:32:13.440> can't 00:32:13.549 --> 00:32:13.559 align:start position:0% doing account abstraction I can't 00:32:13.559 --> 00:32:15.590 align:start position:0% doing account abstraction I can't imagine<00:32:13.860> trying<00:32:14.460> to<00:32:14.640> support<00:32:14.880> like<00:32:15.360> 10 00:32:15.590 --> 00:32:15.600 align:start position:0% imagine trying to support like 10 00:32:15.600 --> 00:32:16.549 align:start position:0% imagine trying to support like 10 different<00:32:15.840> ways<00:32:16.140> of<00:32:16.260> doing<00:32:16.380> account 00:32:16.549 --> 00:32:16.559 align:start position:0% different ways of doing account 00:32:16.559 --> 00:32:19.549 align:start position:0% different ways of doing account abstraction<00:32:17.100> in<00:32:17.399> ether's<00:32:17.880> JS<00:32:18.179> or<00:32:18.360> web3<00:32:18.659> JS<00:32:19.140> and 00:32:19.549 --> 00:32:19.559 align:start position:0% abstraction in ether's JS or web3 JS and 00:32:19.559 --> 00:32:20.810 align:start position:0% abstraction in ether's JS or web3 JS and so<00:32:19.620> that's<00:32:19.799> kind<00:32:19.980> of<00:32:20.039> like<00:32:20.100> my<00:32:20.340> perspective<00:32:20.640> is 00:32:20.810 --> 00:32:20.820 align:start position:0% so that's kind of like my perspective is 00:32:20.820 --> 00:32:23.210 align:start position:0% so that's kind of like my perspective is like<00:32:21.000> how<00:32:21.120> can<00:32:21.240> we<00:32:21.419> do<00:32:21.539> this<00:32:21.720> in<00:32:21.899> a<00:32:22.020> way<00:32:22.200> that<00:32:23.039> we 00:32:23.210 --> 00:32:23.220 align:start position:0% like how can we do this in a way that we 00:32:23.220 --> 00:32:25.549 align:start position:0% like how can we do this in a way that we avoid<00:32:23.520> the<00:32:23.700> fragmentation<00:32:24.240> and<00:32:24.659> that's<00:32:25.380> why 00:32:25.549 --> 00:32:25.559 align:start position:0% avoid the fragmentation and that's why 00:32:25.559 --> 00:32:27.409 align:start position:0% avoid the fragmentation and that's why my<00:32:25.860> perspective<00:32:26.159> is<00:32:26.399> that<00:32:26.640> we<00:32:26.940> should<00:32:27.240> really 00:32:27.409 --> 00:32:27.419 align:start position:0% my perspective is that we should really 00:32:27.419 --> 00:32:31.070 align:start position:0% my perspective is that we should really consider<00:32:27.960> using<00:32:28.919> the<00:32:29.100> evm<00:32:29.580> on<00:32:30.240> the<00:32:30.600> ethereum 00:32:31.070 --> 00:32:31.080 align:start position:0% consider using the evm on the ethereum 00:32:31.080 --> 00:32:33.889 align:start position:0% consider using the evm on the ethereum mainnet<00:32:31.980> as<00:32:32.399> the<00:32:32.700> shelling<00:32:33.059> point<00:32:33.299> for 00:32:33.889 --> 00:32:33.899 align:start position:0% mainnet as the shelling point for 00:32:33.899 --> 00:32:35.690 align:start position:0% mainnet as the shelling point for coordination<00:32:34.620> amongst<00:32:35.159> all<00:32:35.340> these<00:32:35.580> different 00:32:35.690 --> 00:32:35.700 align:start position:0% coordination amongst all these different 00:32:35.700 --> 00:32:36.889 align:start position:0% coordination amongst all these different protocols 00:32:36.889 --> 00:32:36.899 align:start position:0% protocols 00:32:36.899 --> 00:32:39.529 align:start position:0% protocols is<00:32:37.500> there<00:32:37.980> going<00:32:38.279> to<00:32:38.399> become<00:32:38.640> a<00:32:38.760> moment<00:32:39.059> where 00:32:39.529 --> 00:32:39.539 align:start position:0% is there going to become a moment where 00:32:39.539 --> 00:32:41.810 align:start position:0% is there going to become a moment where at<00:32:40.080> some<00:32:40.260> point<00:32:40.380> this<00:32:40.860> turns<00:32:41.279> from<00:32:41.460> like<00:32:41.640> oh 00:32:41.810 --> 00:32:41.820 align:start position:0% at some point this turns from like oh 00:32:41.820 --> 00:32:43.789 align:start position:0% at some point this turns from like oh we'll<00:32:42.059> talk<00:32:42.539> about<00:32:42.659> account<00:32:43.020> of<00:32:43.260> traction<00:32:43.559> and 00:32:43.789 --> 00:32:43.799 align:start position:0% we'll talk about account of traction and 00:32:43.799 --> 00:32:45.889 align:start position:0% we'll talk about account of traction and we'll<00:32:43.919> ideate<00:32:44.399> on<00:32:44.580> it<00:32:44.700> to<00:32:45.000> like<00:32:45.360> oh<00:32:45.480> we<00:32:45.720> need<00:32:45.840> to 00:32:45.889 --> 00:32:45.899 align:start position:0% we'll ideate on it to like oh we need to 00:32:45.899 --> 00:32:47.510 align:start position:0% we'll ideate on it to like oh we need to pull<00:32:46.020> the<00:32:46.200> fire<00:32:46.440> alarm<00:32:46.559> and<00:32:46.919> ship<00:32:47.100> this<00:32:47.340> thing 00:32:47.510 --> 00:32:47.520 align:start position:0% pull the fire alarm and ship this thing 00:32:47.520 --> 00:32:49.669 align:start position:0% pull the fire alarm and ship this thing is<00:32:47.940> that<00:32:48.059> is<00:32:48.179> there<00:32:48.360> like<00:32:48.539> a<00:32:48.659> fire<00:32:48.779> alarm<00:32:48.960> event 00:32:49.669 --> 00:32:49.679 align:start position:0% is that is there like a fire alarm event 00:32:49.679 --> 00:32:51.649 align:start position:0% is that is there like a fire alarm event potential<00:32:50.520> in<00:32:50.820> the<00:32:50.880> future<00:32:51.000> where<00:32:51.299> like<00:32:51.480> we 00:32:51.649 --> 00:32:51.659 align:start position:0% potential in the future where like we 00:32:51.659 --> 00:32:53.810 align:start position:0% potential in the future where like we need<00:32:51.779> to<00:32:51.899> get<00:32:52.020> this<00:32:52.140> done<00:32:52.399> starting<00:32:53.399> a<00:32:53.640> ship 00:32:53.810 --> 00:32:53.820 align:start position:0% need to get this done starting a ship 00:32:53.820 --> 00:32:56.810 align:start position:0% need to get this done starting a ship already<00:32:54.320> yeah<00:32:55.320> I<00:32:55.500> think<00:32:55.679> I<00:32:56.340> mean<00:32:56.399> we've<00:32:56.580> had<00:32:56.640> no 00:32:56.810 --> 00:32:56.820 align:start position:0% already yeah I think I mean we've had no 00:32:56.820 --> 00:32:59.510 align:start position:0% already yeah I think I mean we've had no safes<00:32:57.360> for<00:32:57.539> a<00:32:57.600> long<00:32:57.720> time<00:32:57.899> as<00:32:58.080> well<00:32:58.260> so<00:32:58.740> the 00:32:59.510 --> 00:32:59.520 align:start position:0% safes for a long time as well so the 00:32:59.520 --> 00:33:01.610 align:start position:0% safes for a long time as well so the smart<00:32:59.940> contract<00:33:00.299> wallets<00:33:00.659> have<00:33:00.779> existed<00:33:01.260> we 00:33:01.610 --> 00:33:01.620 align:start position:0% smart contract wallets have existed we 00:33:01.620 --> 00:33:02.990 align:start position:0% smart contract wallets have existed we want<00:33:01.799> to<00:33:01.980> like<00:33:02.100> improve<00:33:02.460> the<00:33:02.580> experience<00:33:02.820> of 00:33:02.990 --> 00:33:03.000 align:start position:0% want to like improve the experience of 00:33:03.000 --> 00:33:04.490 align:start position:0% want to like improve the experience of using<00:33:03.360> them<00:33:03.480> and<00:33:03.960> I<00:33:04.080> wanted<00:33:04.140> to<00:33:04.320> say<00:33:04.380> like 00:33:04.490 --> 00:33:04.500 align:start position:0% using them and I wanted to say like 00:33:04.500 --> 00:33:05.649 align:start position:0% using them and I wanted to say like earlier<00:33:04.740> like<00:33:04.860> I<00:33:04.980> think<00:33:05.100> it's<00:33:05.159> really<00:33:05.399> cool 00:33:05.649 --> 00:33:05.659 align:start position:0% earlier like I think it's really cool 00:33:05.659 --> 00:33:07.970 align:start position:0% earlier like I think it's really cool understanding<00:33:06.659> all<00:33:06.899> the<00:33:07.080> different<00:33:07.260> uh 00:33:07.970 --> 00:33:07.980 align:start position:0% understanding all the different uh 00:33:07.980 --> 00:33:09.529 align:start position:0% understanding all the different uh security<00:33:08.340> perspectives<00:33:09.000> of<00:33:09.360> account 00:33:09.529 --> 00:33:09.539 align:start position:0% security perspectives of account 00:33:09.539 --> 00:33:11.810 align:start position:0% security perspectives of account obstruction<00:33:10.020> and<00:33:10.440> the<00:33:10.679> different<00:33:10.860> policies 00:33:11.810 --> 00:33:11.820 align:start position:0% obstruction and the different policies 00:33:11.820 --> 00:33:13.310 align:start position:0% obstruction and the different policies of<00:33:12.059> different<00:33:12.240> devices<00:33:12.539> but<00:33:12.840> the<00:33:13.019> way<00:33:13.080> that<00:33:13.200> I 00:33:13.310 --> 00:33:13.320 align:start position:0% of different devices but the way that I 00:33:13.320 --> 00:33:15.049 align:start position:0% of different devices but the way that I think<00:33:13.440> about<00:33:13.559> it<00:33:13.740> a<00:33:13.860> lot<00:33:13.919> more<00:33:14.039> is<00:33:14.340> how<00:33:14.820> can<00:33:14.940> we 00:33:15.049 --> 00:33:15.059 align:start position:0% think about it a lot more is how can we 00:33:15.059 --> 00:33:16.669 align:start position:0% think about it a lot more is how can we improve<00:33:15.419> the<00:33:15.600> user<00:33:15.960> experience<00:33:16.260> of<00:33:16.440> using 00:33:16.669 --> 00:33:16.679 align:start position:0% improve the user experience of using 00:33:16.679 --> 00:33:18.289 align:start position:0% improve the user experience of using ethereum<00:33:17.220> and<00:33:17.700> that's<00:33:17.820> something<00:33:18.000> that<00:33:18.179> I 00:33:18.289 --> 00:33:18.299 align:start position:0% ethereum and that's something that I 00:33:18.299 --> 00:33:19.850 align:start position:0% ethereum and that's something that I think<00:33:18.419> like<00:33:18.600> we're<00:33:18.899> still<00:33:19.140> really<00:33:19.440> lagging 00:33:19.850 --> 00:33:19.860 align:start position:0% think like we're still really lagging 00:33:19.860 --> 00:33:21.649 align:start position:0% think like we're still really lagging behind<00:33:20.100> and<00:33:20.399> to<00:33:20.760> me<00:33:20.880> the<00:33:21.120> reason<00:33:21.299> that<00:33:21.539> we're 00:33:21.649 --> 00:33:21.659 align:start position:0% behind and to me the reason that we're 00:33:21.659 --> 00:33:22.970 align:start position:0% behind and to me the reason that we're lagging<00:33:21.960> behind<00:33:22.260> is<00:33:22.440> because<00:33:22.559> there<00:33:22.860> is 00:33:22.970 --> 00:33:22.980 align:start position:0% lagging behind is because there is 00:33:22.980 --> 00:33:24.889 align:start position:0% lagging behind is because there is fragmentation<00:33:23.519> across<00:33:24.000> different<00:33:24.419> wallets 00:33:24.889 --> 00:33:24.899 align:start position:0% fragmentation across different wallets 00:33:24.899 --> 00:33:26.870 align:start position:0% fragmentation across different wallets different<00:33:25.080> protocols<00:33:25.740> from<00:33:26.399> my<00:33:26.580> point<00:33:26.760> of 00:33:26.870 --> 00:33:26.880 align:start position:0% different protocols from my point of 00:33:26.880 --> 00:33:29.029 align:start position:0% different protocols from my point of view<00:33:27.000> I<00:33:27.240> do<00:33:27.480> see<00:33:27.659> some<00:33:28.019> kind<00:33:28.200> of<00:33:28.380> of<00:33:28.860> urgency 00:33:29.029 --> 00:33:29.039 align:start position:0% view I do see some kind of of urgency 00:33:29.039 --> 00:33:31.370 align:start position:0% view I do see some kind of of urgency because<00:33:29.880> I<00:33:30.240> and<00:33:30.600> for<00:33:30.779> me<00:33:30.899> it's<00:33:31.019> related<00:33:31.260> to 00:33:31.370 --> 00:33:31.380 align:start position:0% because I and for me it's related to 00:33:31.380 --> 00:33:33.649 align:start position:0% because I and for me it's related to self-q<00:33:31.799> study<00:33:32.100> I<00:33:32.340> think<00:33:32.460> self-q<00:33:33.059> study<00:33:33.360> today 00:33:33.649 --> 00:33:33.659 align:start position:0% self-q study I think self-q study today 00:33:33.659 --> 00:33:36.230 align:start position:0% self-q study I think self-q study today because<00:33:34.320> of<00:33:34.620> vlas<00:33:35.100> is<00:33:35.460> really<00:33:35.640> hard<00:33:35.880> we<00:33:36.120> all 00:33:36.230 --> 00:33:36.240 align:start position:0% because of vlas is really hard we all 00:33:36.240 --> 00:33:37.850 align:start position:0% because of vlas is really hard we all know<00:33:36.419> that<00:33:36.539> and<00:33:36.720> we<00:33:36.840> because<00:33:37.200> of<00:33:37.380> that<00:33:37.559> a<00:33:37.740> lot 00:33:37.850 --> 00:33:37.860 align:start position:0% know that and we because of that a lot 00:33:37.860 --> 00:33:39.110 align:start position:0% know that and we because of that a lot of<00:33:37.980> people<00:33:38.100> are<00:33:38.340> actually<00:33:38.519> turning<00:33:39.000> to 00:33:39.110 --> 00:33:39.120 align:start position:0% of people are actually turning to 00:33:39.120 --> 00:33:41.029 align:start position:0% of people are actually turning to centralized<00:33:39.600> solution<00:33:39.960> I<00:33:40.500> mean<00:33:40.620> if<00:33:40.799> we<00:33:40.919> ask 00:33:41.029 --> 00:33:41.039 align:start position:0% centralized solution I mean if we ask 00:33:41.039 --> 00:33:43.070 align:start position:0% centralized solution I mean if we ask the<00:33:41.220> audience<00:33:41.519> most<00:33:42.059> of<00:33:42.240> us<00:33:42.360> here<00:33:42.600> we<00:33:42.840> have<00:33:42.960> a 00:33:43.070 --> 00:33:43.080 align:start position:0% the audience most of us here we have a 00:33:43.080 --> 00:33:44.990 align:start position:0% the audience most of us here we have a binance<00:33:43.440> or<00:33:43.620> an<00:33:43.740> FDX<00:33:44.159> or<00:33:44.340> a<00:33:44.460> coinbase<00:33:44.820> account 00:33:44.990 --> 00:33:45.000 align:start position:0% binance or an FDX or a coinbase account 00:33:45.000 --> 00:33:46.909 align:start position:0% binance or an FDX or a coinbase account even<00:33:45.360> though<00:33:45.539> we<00:33:45.840> are<00:33:45.960> the<00:33:46.080> builders<00:33:46.440> and<00:33:46.620> the 00:33:46.909 --> 00:33:46.919 align:start position:0% even though we are the builders and the 00:33:46.919 --> 00:33:49.730 align:start position:0% even though we are the builders and the early<00:33:47.100> adopters<00:33:47.580> so<00:33:48.419> my<00:33:48.779> fear<00:33:49.019> is<00:33:49.140> that<00:33:49.260> if<00:33:49.500> we 00:33:49.730 --> 00:33:49.740 align:start position:0% early adopters so my fear is that if we 00:33:49.740 --> 00:33:50.509 align:start position:0% early adopters so my fear is that if we don't 00:33:50.509 --> 00:33:50.519 align:start position:0% don't 00:33:50.519 --> 00:33:53.330 align:start position:0% don't find<00:33:51.000> a<00:33:51.179> way<00:33:51.299> to<00:33:51.539> to<00:33:51.840> to<00:33:51.960> have<00:33:52.679> a<00:33:52.860> good<00:33:52.980> user 00:33:53.330 --> 00:33:53.340 align:start position:0% find a way to to to have a good user 00:33:53.340 --> 00:33:55.669 align:start position:0% find a way to to to have a good user experience<00:33:53.640> for<00:33:53.880> self-care<00:33:54.419> study<00:33:54.720> then<00:33:55.260> my 00:33:55.669 --> 00:33:55.679 align:start position:0% experience for self-care study then my 00:33:55.679 --> 00:33:57.350 align:start position:0% experience for self-care study then my fear<00:33:55.980> is<00:33:56.039> that<00:33:56.159> the<00:33:56.279> next<00:33:56.399> wave<00:33:56.580> of<00:33:56.760> users<00:33:57.059> may 00:33:57.350 --> 00:33:57.360 align:start position:0% fear is that the next wave of users may 00:33:57.360 --> 00:33:58.850 align:start position:0% fear is that the next wave of users may turn<00:33:57.539> more<00:33:57.840> and<00:33:57.960> more<00:33:58.080> to<00:33:58.260> centralized 00:33:58.850 --> 00:33:58.860 align:start position:0% turn more and more to centralized 00:33:58.860 --> 00:34:00.289 align:start position:0% turn more and more to centralized solution<00:33:59.100> and<00:33:59.279> then<00:33:59.460> will<00:33:59.640> it<00:33:59.820> fail<00:34:00.000> as<00:34:00.120> an 00:34:00.289 --> 00:34:00.299 align:start position:0% solution and then will it fail as an 00:34:00.299 --> 00:34:02.690 align:start position:0% solution and then will it fail as an ecosystem<00:34:00.679> and<00:34:01.679> in<00:34:02.100> my<00:34:02.220> opinion<00:34:02.519> account 00:34:02.690 --> 00:34:02.700 align:start position:0% ecosystem and in my opinion account 00:34:02.700 --> 00:34:04.549 align:start position:0% ecosystem and in my opinion account abstraction<00:34:03.179> is<00:34:03.360> actually<00:34:03.539> the<00:34:03.840> only<00:34:03.960> way<00:34:04.200> to 00:34:04.549 --> 00:34:04.559 align:start position:0% abstraction is actually the only way to 00:34:04.559 --> 00:34:06.950 align:start position:0% abstraction is actually the only way to to<00:34:04.919> enable<00:34:05.399> this<00:34:05.700> user<00:34:06.000> experience<00:34:06.419> that<00:34:06.840> can 00:34:06.950 --> 00:34:06.960 align:start position:0% to enable this user experience that can 00:34:06.960 --> 00:34:08.930 align:start position:0% to enable this user experience that can big<00:34:07.260> self-q<00:34:07.740> study<00:34:08.099> but<00:34:08.280> still<00:34:08.520> make<00:34:08.700> it 00:34:08.930 --> 00:34:08.940 align:start position:0% big self-q study but still make it 00:34:08.940 --> 00:34:12.649 align:start position:0% big self-q study but still make it simple<00:34:09.419> for<00:34:09.720> user<00:34:10.080> so<00:34:10.800> I<00:34:11.280> do<00:34:11.580> feel<00:34:12.179> a<00:34:12.480> certain 00:34:12.649 --> 00:34:12.659 align:start position:0% simple for user so I do feel a certain 00:34:12.659 --> 00:34:15.050 align:start position:0% simple for user so I do feel a certain sense<00:34:13.260> of<00:34:13.619> urgency<00:34:13.800> yeah 00:34:15.050 --> 00:34:15.060 align:start position:0% sense of urgency yeah 00:34:15.060 --> 00:34:16.909 align:start position:0% sense of urgency yeah that's<00:34:15.480> a<00:34:15.659> good<00:34:15.780> point<00:34:15.960> and<00:34:16.139> I<00:34:16.260> feel<00:34:16.619> like<00:34:16.740> for 00:34:16.909 --> 00:34:16.919 align:start position:0% that's a good point and I feel like for 00:34:16.919 --> 00:34:18.710 align:start position:0% that's a good point and I feel like for me<00:34:17.040> the<00:34:17.339> urgency<00:34:17.520> is<00:34:17.700> like<00:34:17.940> how<00:34:18.119> do<00:34:18.240> we<00:34:18.419> make 00:34:18.710 --> 00:34:18.720 align:start position:0% me the urgency is like how do we make 00:34:18.720 --> 00:34:20.570 align:start position:0% me the urgency is like how do we make smart<00:34:19.320> contract<00:34:19.679> walls<00:34:20.040> the<00:34:20.220> default 00:34:20.570 --> 00:34:20.580 align:start position:0% smart contract walls the default 00:34:20.580 --> 00:34:23.450 align:start position:0% smart contract walls the default everywhere<00:34:21.480> because<00:34:22.139> defaults<00:34:23.040> are<00:34:23.159> sticky 00:34:23.450 --> 00:34:23.460 align:start position:0% everywhere because defaults are sticky 00:34:23.460 --> 00:34:26.750 align:start position:0% everywhere because defaults are sticky and<00:34:23.700> so<00:34:23.879> if<00:34:24.060> I<00:34:24.480> go<00:34:24.780> to<00:34:24.960> minta<00:34:25.379> nft<00:34:25.619> on<00:34:25.919> openc<00:34:26.399> and 00:34:26.750 --> 00:34:26.760 align:start position:0% and so if I go to minta nft on openc and 00:34:26.760 --> 00:34:28.490 align:start position:0% and so if I go to minta nft on openc and I<00:34:27.300> create<00:34:27.540> a<00:34:27.720> metamask<00:34:28.020> following<00:34:28.379> some 00:34:28.490 --> 00:34:28.500 align:start position:0% I create a metamask following some 00:34:28.500 --> 00:34:30.770 align:start position:0% I create a metamask following some tutorial<00:34:28.940> that's<00:34:29.940> the<00:34:30.179> default<00:34:30.480> that<00:34:30.659> I'm 00:34:30.770 --> 00:34:30.780 align:start position:0% tutorial that's the default that I'm 00:34:30.780 --> 00:34:32.030 align:start position:0% tutorial that's the default that I'm stuck<00:34:30.960> with<00:34:31.080> for<00:34:31.260> a<00:34:31.379> long<00:34:31.500> time<00:34:31.619> it's<00:34:31.800> very 00:34:32.030 --> 00:34:32.040 align:start position:0% stuck with for a long time it's very 00:34:32.040 --> 00:34:34.129 align:start position:0% stuck with for a long time it's very hard<00:34:32.339> for<00:34:32.580> me<00:34:32.700> to<00:34:32.879> migrate<00:34:33.300> to<00:34:33.899> the<00:34:34.020> smart 00:34:34.129 --> 00:34:34.139 align:start position:0% hard for me to migrate to the smart 00:34:34.139 --> 00:34:36.710 align:start position:0% hard for me to migrate to the smart contract<00:34:34.560> world<00:34:34.800> and<00:34:35.460> so<00:34:35.639> figuring<00:34:36.359> out<00:34:36.480> how 00:34:36.710 --> 00:34:36.720 align:start position:0% contract world and so figuring out how 00:34:36.720 --> 00:34:38.030 align:start position:0% contract world and so figuring out how to<00:34:36.839> make<00:34:36.960> that<00:34:37.200> the<00:34:37.440> first<00:34:37.560> thing<00:34:37.740> that<00:34:37.919> people 00:34:38.030 --> 00:34:38.040 align:start position:0% to make that the first thing that people 00:34:38.040 --> 00:34:40.129 align:start position:0% to make that the first thing that people see<00:34:38.280> whenever<00:34:38.639> they<00:34:38.879> come<00:34:39.060> onto<00:34:39.720> all<00:34:39.899> of<00:34:40.020> the 00:34:40.129 --> 00:34:40.139 align:start position:0% see whenever they come onto all of the 00:34:40.139 --> 00:34:41.389 align:start position:0% see whenever they come onto all of the different<00:34:40.260> protocols<00:34:40.859> is<00:34:40.980> very<00:34:41.220> very 00:34:41.389 --> 00:34:41.399 align:start position:0% different protocols is very very 00:34:41.399 --> 00:34:44.510 align:start position:0% different protocols is very very important<00:34:41.820> yeah<00:34:42.359> fully<00:34:42.780> agree 00:34:44.510 --> 00:34:44.520 align:start position:0% important yeah fully agree 00:34:44.520 --> 00:34:45.829 align:start position:0% important yeah fully agree no 00:34:45.829 --> 00:34:45.839 align:start position:0% no 00:34:45.839 --> 00:34:48.409 align:start position:0% no um<00:34:45.960> okay<00:34:46.200> so<00:34:46.500> uh<00:34:47.159> to<00:34:47.460> my<00:34:47.700> knowledge<00:34:47.940> the 00:34:48.409 --> 00:34:48.419 align:start position:0% um okay so uh to my knowledge the 00:34:48.419 --> 00:34:51.829 align:start position:0% um okay so uh to my knowledge the current<00:34:48.659> state<00:34:49.020> of<00:34:49.260> Defy<00:34:49.800> is<00:34:50.359> unfriendly<00:34:51.359> to 00:34:51.829 --> 00:34:51.839 align:start position:0% current state of Defy is unfriendly to 00:34:51.839 --> 00:34:53.089 align:start position:0% current state of Defy is unfriendly to account<00:34:52.139> obstructure<00:34:52.679> and<00:34:52.800> in<00:34:52.919> smart 00:34:53.089 --> 00:34:53.099 align:start position:0% account obstructure and in smart 00:34:53.099 --> 00:34:54.649 align:start position:0% account obstructure and in smart contract<00:34:53.399> wallets<00:34:53.760> can<00:34:54.000> one<00:34:54.300> of<00:34:54.480> you<00:34:54.540> guys 00:34:54.649 --> 00:34:54.659 align:start position:0% contract wallets can one of you guys 00:34:54.659 --> 00:34:57.530 align:start position:0% contract wallets can one of you guys explain<00:34:54.839> why<00:34:55.320> that's<00:34:55.560> the<00:34:55.800> case<00:34:56.359> why<00:34:57.359> is<00:34:57.420> that 00:34:57.530 --> 00:34:57.540 align:start position:0% explain why that's the case why is that 00:34:57.540 --> 00:35:00.230 align:start position:0% explain why that's the case why is that the<00:34:57.599> case<00:34:57.720> and<00:34:57.839> how<00:34:57.960> do<00:34:58.080> we<00:34:58.140> fix<00:34:58.260> it<00:34:58.859> yeah<00:34:59.400> so<00:35:00.000> I 00:35:00.230 --> 00:35:00.240 align:start position:0% the case and how do we fix it yeah so I 00:35:00.240 --> 00:35:03.290 align:start position:0% the case and how do we fix it yeah so I wouldn't<00:35:00.599> say<00:35:01.020> that<00:35:01.260> defy<00:35:01.859> in<00:35:01.980> general<00:35:02.160> is<00:35:02.640> is 00:35:03.290 --> 00:35:03.300 align:start position:0% wouldn't say that defy in general is is 00:35:03.300 --> 00:35:05.089 align:start position:0% wouldn't say that defy in general is is not<00:35:03.480> really<00:35:03.660> there<00:35:04.020> are<00:35:04.200> some<00:35:04.380> doubts<00:35:04.920> that 00:35:05.089 --> 00:35:05.099 align:start position:0% not really there are some doubts that 00:35:05.099 --> 00:35:07.190 align:start position:0% not really there are some doubts that are<00:35:05.339> that<00:35:05.760> are<00:35:05.940> summed<00:35:06.240> up<00:35:06.300> that<00:35:06.660> make<00:35:07.080> it 00:35:07.190 --> 00:35:07.200 align:start position:0% are that are summed up that make it 00:35:07.200 --> 00:35:10.250 align:start position:0% are that are summed up that make it difficult<00:35:07.560> for<00:35:08.460> example<00:35:08.760> uh 00:35:10.250 --> 00:35:10.260 align:start position:0% difficult for example uh 00:35:10.260 --> 00:35:13.190 align:start position:0% difficult for example uh um<00:35:10.320> for<00:35:10.619> example<00:35:11.160> they<00:35:11.940> assume<00:35:12.359> that<00:35:12.900> you<00:35:13.079> can 00:35:13.190 --> 00:35:13.200 align:start position:0% um for example they assume that you can 00:35:13.200 --> 00:35:16.190 align:start position:0% um for example they assume that you can sign<00:35:13.500> directly<00:35:14.160> with<00:35:14.520> the<00:35:14.700> address<00:35:14.960> so<00:35:15.960> and 00:35:16.190 --> 00:35:16.200 align:start position:0% sign directly with the address so and 00:35:16.200 --> 00:35:18.109 align:start position:0% sign directly with the address so and contracts<00:35:16.740> cannot<00:35:17.040> sign<00:35:17.280> contacts<00:35:17.880> do<00:35:18.000> not 00:35:18.109 --> 00:35:18.119 align:start position:0% contracts cannot sign contacts do not 00:35:18.119 --> 00:35:19.490 align:start position:0% contracts cannot sign contacts do not have<00:35:18.300> a<00:35:18.480> private<00:35:18.780> key 00:35:19.490 --> 00:35:19.500 align:start position:0% have a private key 00:35:19.500 --> 00:35:22.190 align:start position:0% have a private key so<00:35:20.040> if<00:35:20.579> you<00:35:20.760> need<00:35:20.880> to<00:35:21.119> login<00:35:21.300> for<00:35:21.780> example<00:35:21.960> to 00:35:22.190 --> 00:35:22.200 align:start position:0% so if you need to login for example to 00:35:22.200 --> 00:35:26.089 align:start position:0% so if you need to login for example to openc<00:35:22.680> by<00:35:23.460> using<00:35:23.880> uh<00:35:24.480> if<00:35:25.020> you<00:35:25.500> need<00:35:25.560> to<00:35:25.740> log<00:35:25.859> in 00:35:26.089 --> 00:35:26.099 align:start position:0% openc by using uh if you need to log in 00:35:26.099 --> 00:35:28.069 align:start position:0% openc by using uh if you need to log in by<00:35:26.640> signing<00:35:27.119> a<00:35:27.240> message<00:35:27.420> with<00:35:27.780> your<00:35:27.900> address 00:35:28.069 --> 00:35:28.079 align:start position:0% by signing a message with your address 00:35:28.079 --> 00:35:30.230 align:start position:0% by signing a message with your address then<00:35:28.380> you're<00:35:28.560> unable<00:35:28.920> to<00:35:29.099> log<00:35:29.280> in<00:35:29.460> and<00:35:29.940> we<00:35:30.119> have 00:35:30.230 --> 00:35:30.240 align:start position:0% then you're unable to log in and we have 00:35:30.240 --> 00:35:32.690 align:start position:0% then you're unable to log in and we have an<00:35:30.359> ELC<00:35:30.839> to<00:35:31.079> solve<00:35:31.380> that<00:35:31.560> a<00:35:32.220> very<00:35:32.339> old<00:35:32.520> one 00:35:32.690 --> 00:35:32.700 align:start position:0% an ELC to solve that a very old one 00:35:32.700 --> 00:35:35.210 align:start position:0% an ELC to solve that a very old one actually<00:35:33.000> a<00:35:33.540> 1271 00:35:35.210 --> 00:35:35.220 align:start position:0% actually a 1271 00:35:35.220 --> 00:35:38.030 align:start position:0% actually a 1271 which<00:35:35.880> defines<00:35:36.420> how<00:35:36.960> a<00:35:37.140> contract<00:35:37.560> can 00:35:38.030 --> 00:35:38.040 align:start position:0% which defines how a contract can 00:35:38.040 --> 00:35:40.370 align:start position:0% which defines how a contract can validate<00:35:38.700> that<00:35:38.940> I<00:35:39.119> can<00:35:39.420> say<00:35:39.599> is<00:35:39.900> signature 00:35:40.370 --> 00:35:40.380 align:start position:0% validate that I can say is signature 00:35:40.380 --> 00:35:43.430 align:start position:0% validate that I can say is signature valid<00:35:41.160> so<00:35:41.760> summed<00:35:42.180> up<00:35:42.240> support<00:35:42.599> it<00:35:42.900> some<00:35:43.200> don't 00:35:43.430 --> 00:35:43.440 align:start position:0% valid so summed up support it some don't 00:35:43.440 --> 00:35:45.770 align:start position:0% valid so summed up support it some don't and<00:35:43.800> assume<00:35:44.220> in<00:35:44.400> AOA<00:35:44.880> we<00:35:45.359> need<00:35:45.480> to<00:35:45.660> have 00:35:45.770 --> 00:35:45.780 align:start position:0% and assume in AOA we need to have 00:35:45.780 --> 00:35:47.870 align:start position:0% and assume in AOA we need to have developers<00:35:46.200> to<00:35:46.500> stop<00:35:46.680> it<00:35:46.920> to<00:35:47.220> stop<00:35:47.339> doing<00:35:47.579> this 00:35:47.870 --> 00:35:47.880 align:start position:0% developers to stop it to stop doing this 00:35:47.880 --> 00:35:50.810 align:start position:0% developers to stop it to stop doing this sort<00:35:48.240> of<00:35:48.359> thing<00:35:48.540> and<00:35:49.380> assume<00:35:49.859> that<00:35:50.099> some<00:35:50.640> of 00:35:50.810 --> 00:35:50.820 align:start position:0% sort of thing and assume that some of 00:35:50.820 --> 00:35:52.790 align:start position:0% sort of thing and assume that some of the<00:35:50.940> that<00:35:51.420> some<00:35:51.720> of<00:35:51.839> the<00:35:51.960> addresses<00:35:52.500> are 00:35:52.790 --> 00:35:52.800 align:start position:0% the that some of the addresses are 00:35:52.800 --> 00:35:55.550 align:start position:0% the that some of the addresses are actually<00:35:52.980> contracts<00:35:53.780> uh<00:35:54.780> that's<00:35:55.020> the<00:35:55.260> that's 00:35:55.550 --> 00:35:55.560 align:start position:0% actually contracts uh that's the that's 00:35:55.560 --> 00:35:57.589 align:start position:0% actually contracts uh that's the that's like<00:35:55.740> the<00:35:55.980> minimum<00:35:56.220> requirement<00:35:56.700> in<00:35:57.060> order<00:35:57.240> to 00:35:57.589 --> 00:35:57.599 align:start position:0% like the minimum requirement in order to 00:35:57.599 --> 00:35:59.810 align:start position:0% like the minimum requirement in order to make<00:35:57.839> it<00:35:58.020> the<00:35:58.140> first<00:35:58.320> class<00:35:58.500> citizen<00:35:59.040> so<00:35:59.700> I 00:35:59.810 --> 00:35:59.820 align:start position:0% make it the first class citizen so I 00:35:59.820 --> 00:36:01.130 align:start position:0% make it the first class citizen so I want<00:35:59.940> to<00:36:00.060> run<00:36:00.119> through<00:36:00.359> some<00:36:00.599> potential<00:36:00.960> use 00:36:01.130 --> 00:36:01.140 align:start position:0% want to run through some potential use 00:36:01.140 --> 00:36:03.230 align:start position:0% want to run through some potential use cases<00:36:01.440> just<00:36:01.800> to<00:36:02.040> make<00:36:02.820> things<00:36:03.000> really 00:36:03.230 --> 00:36:03.240 align:start position:0% cases just to make things really 00:36:03.240 --> 00:36:05.150 align:start position:0% cases just to make things really Concrete<00:36:03.720> in<00:36:03.839> the<00:36:03.960> imagination<00:36:04.380> of<00:36:04.680> of<00:36:04.859> the 00:36:05.150 --> 00:36:05.160 align:start position:0% Concrete in the imagination of of the 00:36:05.160 --> 00:36:06.109 align:start position:0% Concrete in the imagination of of the people<00:36:05.220> in<00:36:05.460> the<00:36:05.520> audience<00:36:05.760> here<00:36:05.880> and<00:36:06.000> the 00:36:06.109 --> 00:36:06.119 align:start position:0% people in the audience here and the 00:36:06.119 --> 00:36:08.089 align:start position:0% people in the audience here and the listeners<00:36:06.420> uh<00:36:07.140> so<00:36:07.380> I<00:36:07.500> want<00:36:07.619> you<00:36:07.740> to<00:36:07.859> each<00:36:07.980> of 00:36:08.089 --> 00:36:08.099 align:start position:0% listeners uh so I want you to each of 00:36:08.099 --> 00:36:09.710 align:start position:0% listeners uh so I want you to each of you<00:36:08.220> to<00:36:08.339> think<00:36:08.460> of<00:36:08.700> the<00:36:09.000> most<00:36:09.060> powerful<00:36:09.480> use 00:36:09.710 --> 00:36:09.720 align:start position:0% you to think of the most powerful use 00:36:09.720 --> 00:36:11.690 align:start position:0% you to think of the most powerful use case<00:36:09.960> that<00:36:10.380> account<00:36:10.619> abstraction<00:36:11.160> unlocks 00:36:11.690 --> 00:36:11.700 align:start position:0% case that account abstraction unlocks 00:36:11.700 --> 00:36:14.150 align:start position:0% case that account abstraction unlocks and<00:36:12.240> how<00:36:12.420> that<00:36:12.660> on<00:36:12.900> boards<00:36:13.320> new<00:36:13.500> people<00:36:13.740> new 00:36:14.150 --> 00:36:14.160 align:start position:0% and how that on boards new people new 00:36:14.160 --> 00:36:16.690 align:start position:0% and how that on boards new people new utility<00:36:14.579> into<00:36:15.060> ethereum<00:36:15.720> you<00:36:16.079> each<00:36:16.200> get<00:36:16.440> one 00:36:16.690 --> 00:36:16.700 align:start position:0% utility into ethereum you each get one 00:36:16.700 --> 00:36:19.069 align:start position:0% utility into ethereum you each get one and<00:36:17.700> whoever<00:36:18.300> is<00:36:18.420> going<00:36:18.599> to<00:36:18.720> go<00:36:18.780> first<00:36:18.900> is 00:36:19.069 --> 00:36:19.079 align:start position:0% and whoever is going to go first is 00:36:19.079 --> 00:36:20.210 align:start position:0% and whoever is going to go first is going<00:36:19.260> to<00:36:19.320> have<00:36:19.440> the<00:36:19.619> the<00:36:19.740> opportunity<00:36:20.099> to 00:36:20.210 --> 00:36:20.220 align:start position:0% going to have the the opportunity to 00:36:20.220 --> 00:36:21.890 align:start position:0% going to have the the opportunity to have<00:36:20.339> the<00:36:20.460> best<00:36:20.579> one<00:36:20.700> you're<00:36:21.060> gonna<00:36:21.420> give<00:36:21.780> it 00:36:21.890 --> 00:36:21.900 align:start position:0% have the best one you're gonna give it 00:36:21.900 --> 00:36:23.690 align:start position:0% have the best one you're gonna give it to<00:36:21.960> you<00:36:22.020> what's<00:36:22.200> the<00:36:22.380> what's<00:36:22.619> the<00:36:22.800> best<00:36:23.099> use 00:36:23.690 --> 00:36:23.700 align:start position:0% to you what's the what's the best use 00:36:23.700 --> 00:36:25.310 align:start position:0% to you what's the what's the best use case<00:36:23.880> that<00:36:24.180> account<00:36:24.359> abstraction<00:36:24.780> unlocks 00:36:25.310 --> 00:36:25.320 align:start position:0% case that account abstraction unlocks 00:36:25.320 --> 00:36:28.130 align:start position:0% case that account abstraction unlocks well<00:36:25.980> you<00:36:26.520> know<00:36:26.640> there<00:36:26.880> are<00:36:27.119> there<00:36:28.020> are 00:36:28.130 --> 00:36:28.140 align:start position:0% well you know there are there are 00:36:28.140 --> 00:36:30.589 align:start position:0% well you know there are there are millions<00:36:28.980> of<00:36:29.099> use<00:36:29.400> cases<00:36:29.760> some<00:36:30.119> of<00:36:30.240> them<00:36:30.359> quite 00:36:30.589 --> 00:36:30.599 align:start position:0% millions of use cases some of them quite 00:36:30.599 --> 00:36:33.290 align:start position:0% millions of use cases some of them quite exotic<00:36:31.260> I'm<00:36:32.099> tempted<00:36:32.520> to<00:36:32.640> talk<00:36:32.820> about<00:36:33.000> them 00:36:33.290 --> 00:36:33.300 align:start position:0% exotic I'm tempted to talk about them 00:36:33.300 --> 00:36:36.170 align:start position:0% exotic I'm tempted to talk about them but<00:36:33.599> instead<00:36:33.960> I<00:36:34.140> just<00:36:34.320> repeat<00:36:34.500> that<00:36:35.180> being 00:36:36.170 --> 00:36:36.180 align:start position:0% but instead I just repeat that being 00:36:36.180 --> 00:36:38.270 align:start position:0% but instead I just repeat that being able<00:36:36.480> that<00:36:36.839> being<00:36:37.200> able<00:36:37.440> to<00:36:37.560> obstruct<00:36:38.040> the 00:36:38.270 --> 00:36:38.280 align:start position:0% able that being able to obstruct the 00:36:38.280 --> 00:36:41.089 align:start position:0% able that being able to obstruct the signature<00:36:38.820> and<00:36:39.420> to<00:36:39.540> have<00:36:39.780> as<00:36:40.680> to<00:36:40.859> have 00:36:41.089 --> 00:36:41.099 align:start position:0% signature and to have as to have 00:36:41.099 --> 00:36:44.530 align:start position:0% signature and to have as to have authentication<00:36:42.060> and<00:36:42.359> authorization 00:36:44.530 --> 00:36:44.540 align:start position:0% authentication and authorization 00:36:44.540 --> 00:36:47.690 align:start position:0% authentication and authorization obstructed<00:36:45.540> and<00:36:45.960> let<00:36:46.740> the<00:36:46.920> user<00:36:47.160> control<00:36:47.339> it 00:36:47.690 --> 00:36:47.700 align:start position:0% obstructed and let the user control it 00:36:47.700 --> 00:36:49.910 align:start position:0% obstructed and let the user control it that's<00:36:48.480> the<00:36:48.720> single<00:36:49.020> most<00:36:49.260> important<00:36:49.680> thing 00:36:49.910 --> 00:36:49.920 align:start position:0% that's the single most important thing 00:36:49.920 --> 00:36:51.290 align:start position:0% that's the single most important thing in<00:36:50.339> my<00:36:50.460> opinion 00:36:51.290 --> 00:36:51.300 align:start position:0% in my opinion 00:36:51.300 --> 00:36:53.589 align:start position:0% in my opinion I<00:36:51.839> think<00:36:51.960> just<00:36:52.320> to<00:36:52.440> make<00:36:52.619> the<00:36:52.859> concept<00:36:53.160> of 00:36:53.589 --> 00:36:53.599 align:start position:0% I think just to make the concept of 00:36:53.599 --> 00:36:55.730 align:start position:0% I think just to make the concept of abstraction<00:36:54.599> more<00:36:54.960> concrete<00:36:55.440> for<00:36:55.560> people 00:36:55.730 --> 00:36:55.740 align:start position:0% abstraction more concrete for people 00:36:55.740 --> 00:36:58.130 align:start position:0% abstraction more concrete for people right<00:36:56.040> like<00:36:56.460> one<00:36:57.240> of<00:36:57.420> one<00:36:57.660> of<00:36:57.780> the<00:36:57.839> big<00:36:57.960> use 00:36:58.130 --> 00:36:58.140 align:start position:0% right like one of one of the big use 00:36:58.140 --> 00:37:00.650 align:start position:0% right like one of one of the big use cases<00:36:58.440> is<00:36:58.859> multi-cig<00:36:59.640> wallets<00:37:00.060> and<00:37:00.240> social 00:37:00.650 --> 00:37:00.660 align:start position:0% cases is multi-cig wallets and social 00:37:00.660 --> 00:37:03.109 align:start position:0% cases is multi-cig wallets and social recovery<00:37:01.200> wallets<00:37:01.560> right<00:37:01.740> so<00:37:02.339> multisig 00:37:03.109 --> 00:37:03.119 align:start position:0% recovery wallets right so multisig 00:37:03.119 --> 00:37:05.329 align:start position:0% recovery wallets right so multisig wallet's<00:37:03.540> pretty<00:37:03.660> simple<00:37:03.839> I<00:37:04.140> mean<00:37:04.260> we<00:37:04.440> have<00:37:04.680> n 00:37:05.329 --> 00:37:05.339 align:start position:0% wallet's pretty simple I mean we have n 00:37:05.339 --> 00:37:07.010 align:start position:0% wallet's pretty simple I mean we have n keys<00:37:05.700> and<00:37:05.820> you<00:37:06.000> need<00:37:06.119> you<00:37:06.359> know<00:37:06.480> some<00:37:06.660> n<00:37:06.900> over 00:37:07.010 --> 00:37:07.020 align:start position:0% keys and you need you know some n over 00:37:07.020 --> 00:37:08.569 align:start position:0% keys and you need you know some n over two<00:37:07.260> or<00:37:07.440> some<00:37:07.619> number<00:37:07.740> of<00:37:07.920> them<00:37:08.040> so<00:37:08.280> I<00:37:08.460> for 00:37:08.569 --> 00:37:08.579 align:start position:0% two or some number of them so I for 00:37:08.579 --> 00:37:10.670 align:start position:0% two or some number of them so I for example<00:37:08.820> you<00:37:09.060> have<00:37:09.240> you<00:37:09.900> know<00:37:10.020> six<00:37:10.200> keys<00:37:10.560> and 00:37:10.670 --> 00:37:10.680 align:start position:0% example you have you know six keys and 00:37:10.680 --> 00:37:12.170 align:start position:0% example you have you know six keys and you<00:37:10.800> need<00:37:10.920> four<00:37:11.099> of<00:37:11.280> them<00:37:11.400> in<00:37:11.579> order<00:37:11.700> to<00:37:11.940> assign 00:37:12.170 --> 00:37:12.180 align:start position:0% you need four of them in order to assign 00:37:12.180 --> 00:37:14.210 align:start position:0% you need four of them in order to assign a<00:37:12.359> transaction<00:37:12.720> right<00:37:13.020> like<00:37:13.200> that's<00:37:13.440> uh<00:37:13.740> like 00:37:14.210 --> 00:37:14.220 align:start position:0% a transaction right like that's uh like 00:37:14.220 --> 00:37:15.890 align:start position:0% a transaction right like that's uh like most<00:37:14.520> of<00:37:14.700> my<00:37:14.820> money<00:37:15.000> is<00:37:15.180> in<00:37:15.359> a<00:37:15.480> four<00:37:15.540> of<00:37:15.720> six 00:37:15.890 --> 00:37:15.900 align:start position:0% most of my money is in a four of six 00:37:15.900 --> 00:37:18.290 align:start position:0% most of my money is in a four of six ignosis<00:37:16.500> safe<00:37:16.740> right<00:37:17.040> and<00:37:17.520> like<00:37:17.880> that<00:37:18.060> you 00:37:18.290 --> 00:37:18.300 align:start position:0% ignosis safe right and like that you 00:37:18.300 --> 00:37:19.609 align:start position:0% ignosis safe right and like that you know<00:37:18.359> it's<00:37:18.540> it's<00:37:18.720> public<00:37:19.020> info<00:37:19.380> it's<00:37:19.500> on 00:37:19.609 --> 00:37:19.619 align:start position:0% know it's it's public info it's on 00:37:19.619 --> 00:37:22.370 align:start position:0% know it's it's public info it's on etherscan<00:37:20.220> but 00:37:22.370 --> 00:37:22.380 align:start position:0% etherscan but 00:37:22.380 --> 00:37:25.190 align:start position:0% etherscan but um<00:37:22.700> then<00:37:23.700> the<00:37:23.820> social<00:37:23.940> recovery<00:37:24.599> wallet<00:37:25.020> is 00:37:25.190 --> 00:37:25.200 align:start position:0% um then the social recovery wallet is 00:37:25.200 --> 00:37:28.670 align:start position:0% um then the social recovery wallet is like<00:37:25.440> a<00:37:25.619> wallet<00:37:25.980> where<00:37:26.280> you<00:37:27.119> can<00:37:27.320> sign<00:37:28.320> things 00:37:28.670 --> 00:37:28.680 align:start position:0% like a wallet where you can sign things 00:37:28.680 --> 00:37:31.069 align:start position:0% like a wallet where you can sign things uh<00:37:29.160> with<00:37:29.460> instant<00:37:30.240> transactions<00:37:30.720> with<00:37:30.900> one 00:37:31.069 --> 00:37:31.079 align:start position:0% uh with instant transactions with one 00:37:31.079 --> 00:37:34.250 align:start position:0% uh with instant transactions with one key<00:37:31.320> but<00:37:32.099> if<00:37:32.339> you<00:37:32.520> lose<00:37:32.700> your<00:37:32.940> key<00:37:33.119> then<00:37:33.480> there 00:37:34.250 --> 00:37:34.260 align:start position:0% key but if you lose your key then there 00:37:34.260 --> 00:37:36.349 align:start position:0% key but if you lose your key then there is<00:37:34.440> you<00:37:34.859> know<00:37:34.980> some<00:37:35.280> other<00:37:35.400> mechanism<00:37:35.940> which 00:37:36.349 --> 00:37:36.359 align:start position:0% is you know some other mechanism which 00:37:36.359 --> 00:37:38.030 align:start position:0% is you know some other mechanism which itself<00:37:36.660> probably<00:37:37.020> could<00:37:37.260> be<00:37:37.440> a<00:37:37.560> multi-cig 00:37:38.030 --> 00:37:38.040 align:start position:0% itself probably could be a multi-cig 00:37:38.040 --> 00:37:40.609 align:start position:0% itself probably could be a multi-cig right<00:37:38.280> so<00:37:38.520> uh<00:37:38.820> the<00:37:39.300> like<00:37:40.020> one<00:37:40.260> thing<00:37:40.380> you<00:37:40.500> could 00:37:40.609 --> 00:37:40.619 align:start position:0% right so uh the like one thing you could 00:37:40.619 --> 00:37:42.170 align:start position:0% right so uh the like one thing you could do<00:37:40.740> is<00:37:40.920> like<00:37:41.099> you<00:37:41.280> know<00:37:41.339> choose<00:37:41.700> some<00:37:41.940> like 00:37:42.170 --> 00:37:42.180 align:start position:0% do is like you know choose some like 00:37:42.180 --> 00:37:43.910 align:start position:0% do is like you know choose some like five<00:37:42.359> friends<00:37:42.599> and<00:37:42.900> three<00:37:43.079> and<00:37:43.320> three<00:37:43.740> of<00:37:43.859> them 00:37:43.910 --> 00:37:43.920 align:start position:0% five friends and three and three of them 00:37:43.920 --> 00:37:47.630 align:start position:0% five friends and three and three of them can<00:37:44.480> can<00:37:45.480> kind<00:37:45.839> of<00:37:45.900> make<00:37:45.960> it<00:37:46.140> up<00:37:46.320> and<00:37:46.859> that 00:37:47.630 --> 00:37:47.640 align:start position:0% can can kind of make it up and that 00:37:47.640 --> 00:37:50.210 align:start position:0% can can kind of make it up and that mechanism<00:37:48.060> can<00:37:48.599> change<00:37:49.260> the<00:37:49.560> key<00:37:49.920> of<00:37:50.099> your 00:37:50.210 --> 00:37:50.220 align:start position:0% mechanism can change the key of your 00:37:50.220 --> 00:37:52.010 align:start position:0% mechanism can change the key of your account<00:37:50.400> if<00:37:50.579> you<00:37:50.760> lose<00:37:50.880> it<00:37:51.060> right<00:37:51.420> so<00:37:51.839> the 00:37:52.010 --> 00:37:52.020 align:start position:0% account if you lose it right so the 00:37:52.020 --> 00:37:53.990 align:start position:0% account if you lose it right so the philosophy<00:37:52.560> there<00:37:52.740> is<00:37:52.980> like<00:37:53.220> in<00:37:53.820> practice 00:37:53.990 --> 00:37:54.000 align:start position:0% philosophy there is like in practice 00:37:54.000 --> 00:37:55.910 align:start position:0% philosophy there is like in practice people's<00:37:54.660> accounts<00:37:55.020> getting<00:37:55.140> lost<00:37:55.440> there's<00:37:55.740> a 00:37:55.910 --> 00:37:55.920 align:start position:0% people's accounts getting lost there's a 00:37:55.920 --> 00:37:57.410 align:start position:0% people's accounts getting lost there's a big<00:37:56.040> it<00:37:56.220> happens<00:37:56.400> much<00:37:56.700> more<00:37:56.820> often<00:37:57.060> it's<00:37:57.240> a 00:37:57.410 --> 00:37:57.420 align:start position:0% big it happens much more often it's a 00:37:57.420 --> 00:37:58.490 align:start position:0% big it happens much more often it's a bigger<00:37:57.599> problem<00:37:57.720> than<00:37:58.020> accounts<00:37:58.380> getting 00:37:58.490 --> 00:37:58.500 align:start position:0% bigger problem than accounts getting 00:37:58.500 --> 00:38:00.349 align:start position:0% bigger problem than accounts getting stolen<00:37:58.980> and<00:37:59.160> so<00:37:59.339> you<00:37:59.700> know<00:37:59.760> you<00:37:59.940> can<00:38:00.119> solve 00:38:00.349 --> 00:38:00.359 align:start position:0% stolen and so you know you can solve 00:38:00.359 --> 00:38:01.910 align:start position:0% stolen and so you know you can solve that<00:38:00.540> problem<00:38:00.720> without<00:38:01.079> sacrificing<00:38:01.800> any 00:38:01.910 --> 00:38:01.920 align:start position:0% that problem without sacrificing any 00:38:01.920 --> 00:38:03.770 align:start position:0% that problem without sacrificing any convenience<00:38:02.400> and<00:38:02.640> that<00:38:02.820> makes<00:38:02.940> sense<00:38:03.180> for<00:38:03.480> you 00:38:03.770 --> 00:38:03.780 align:start position:0% convenience and that makes sense for you 00:38:03.780 --> 00:38:06.349 align:start position:0% convenience and that makes sense for you know<00:38:03.900> a<00:38:04.020> lot<00:38:04.200> of<00:38:04.339> smaller<00:38:05.339> and<00:38:05.460> medium<00:38:06.000> value 00:38:06.349 --> 00:38:06.359 align:start position:0% know a lot of smaller and medium value 00:38:06.359 --> 00:38:09.230 align:start position:0% know a lot of smaller and medium value use<00:38:06.660> cases<00:38:07.079> right<00:38:07.440> so<00:38:08.220> the<00:38:08.700> challenge<00:38:08.880> though 00:38:09.230 --> 00:38:09.240 align:start position:0% use cases right so the challenge though 00:38:09.240 --> 00:38:11.030 align:start position:0% use cases right so the challenge though is<00:38:09.420> that<00:38:09.720> you<00:38:10.200> know<00:38:10.260> if<00:38:10.500> you<00:38:10.680> want<00:38:10.859> the 00:38:11.030 --> 00:38:11.040 align:start position:0% is that you know if you want the 00:38:11.040 --> 00:38:13.490 align:start position:0% is that you know if you want the benefits<00:38:11.520> of<00:38:11.940> uh<00:38:12.240> either<00:38:12.720> the<00:38:13.020> security<00:38:13.200> like 00:38:13.490 --> 00:38:13.500 align:start position:0% benefits of uh either the security like 00:38:13.500 --> 00:38:14.990 align:start position:0% benefits of uh either the security like the<00:38:13.680> security<00:38:14.040> the<00:38:14.460> protection<00:38:14.700> against 00:38:14.990 --> 00:38:15.000 align:start position:0% the security the protection against 00:38:15.000 --> 00:38:17.150 align:start position:0% the security the protection against theft<00:38:15.480> and<00:38:15.660> like<00:38:15.780> the<00:38:16.020> kind<00:38:16.619> of<00:38:16.800> you<00:38:16.859> know<00:38:17.040> the 00:38:17.150 --> 00:38:17.160 align:start position:0% theft and like the kind of you know the 00:38:17.160 --> 00:38:19.370 align:start position:0% theft and like the kind of you know the really<00:38:17.640> hardcore<00:38:18.119> and<00:38:18.540> security<00:38:18.839> of<00:38:19.260> a 00:38:19.370 --> 00:38:19.380 align:start position:0% really hardcore and security of a 00:38:19.380 --> 00:38:21.710 align:start position:0% really hardcore and security of a multi-sig<00:38:19.859> wallets<00:38:20.160> or<00:38:20.520> the<00:38:20.700> easier<00:38:21.240> recovery 00:38:21.710 --> 00:38:21.720 align:start position:0% multi-sig wallets or the easier recovery 00:38:21.720 --> 00:38:24.050 align:start position:0% multi-sig wallets or the easier recovery of<00:38:21.960> a<00:38:22.079> social<00:38:22.260> recovery<00:38:22.859> wallets<00:38:23.220> you<00:38:23.820> have<00:38:23.940> to 00:38:24.050 --> 00:38:24.060 align:start position:0% of a social recovery wallets you have to 00:38:24.060 --> 00:38:25.790 align:start position:0% of a social recovery wallets you have to put<00:38:24.240> your<00:38:24.480> funds<00:38:24.780> into<00:38:25.020> a<00:38:25.200> smart<00:38:25.380> contract 00:38:25.790 --> 00:38:25.800 align:start position:0% put your funds into a smart contract 00:38:25.800 --> 00:38:28.790 align:start position:0% put your funds into a smart contract wallet<00:38:26.220> right<00:38:26.400> and<00:38:27.180> smart<00:38:27.960> contracts<00:38:28.500> exist 00:38:28.790 --> 00:38:28.800 align:start position:0% wallet right and smart contracts exist 00:38:28.800 --> 00:38:30.290 align:start position:0% wallet right and smart contracts exist and<00:38:28.980> like<00:38:29.160> you<00:38:29.280> can<00:38:29.400> do<00:38:29.520> this<00:38:29.700> today<00:38:29.820> but<00:38:30.119> the 00:38:30.290 --> 00:38:30.300 align:start position:0% and like you can do this today but the 00:38:30.300 --> 00:38:31.430 align:start position:0% and like you can do this today but the problem<00:38:30.420> is<00:38:30.660> that<00:38:30.839> if<00:38:30.960> you<00:38:31.079> want<00:38:31.200> to<00:38:31.320> actually 00:38:31.430 --> 00:38:31.440 align:start position:0% problem is that if you want to actually 00:38:31.440 --> 00:38:33.530 align:start position:0% problem is that if you want to actually send<00:38:31.800> the<00:38:31.980> transaction<00:38:32.400> then<00:38:33.000> like<00:38:33.240> you<00:38:33.420> have 00:38:33.530 --> 00:38:33.540 align:start position:0% send the transaction then like you have 00:38:33.540 --> 00:38:35.870 align:start position:0% send the transaction then like you have to<00:38:33.720> also<00:38:34.020> have<00:38:34.200> money<00:38:34.440> in<00:38:34.619> an<00:38:34.740> eoa<00:38:35.160> and<00:38:35.280> the<00:38:35.460> eoa 00:38:35.870 --> 00:38:35.880 align:start position:0% to also have money in an eoa and the eoa 00:38:35.880 --> 00:38:38.030 align:start position:0% to also have money in an eoa and the eoa has<00:38:36.060> to<00:38:36.180> pay<00:38:36.300> gas<00:38:36.599> or<00:38:37.440> you<00:38:37.619> know<00:38:37.680> you<00:38:37.800> have<00:38:37.920> to 00:38:38.030 --> 00:38:38.040 align:start position:0% has to pay gas or you know you have to 00:38:38.040 --> 00:38:39.530 align:start position:0% has to pay gas or you know you have to work<00:38:38.220> through<00:38:38.400> an<00:38:38.579> intermediate<00:38:39.119> area<00:38:39.240> then 00:38:39.530 --> 00:38:39.540 align:start position:0% work through an intermediate area then 00:38:39.540 --> 00:38:40.970 align:start position:0% work through an intermediate area then you<00:38:39.660> have<00:38:39.780> to<00:38:39.900> rely<00:38:40.140> on<00:38:40.320> that<00:38:40.440> intermediary 00:38:40.970 --> 00:38:40.980 align:start position:0% you have to rely on that intermediary 00:38:40.980 --> 00:38:42.410 align:start position:0% you have to rely on that intermediary and<00:38:41.220> then<00:38:41.339> what<00:38:41.460> if<00:38:41.820> that<00:38:42.000> intermediary 00:38:42.410 --> 00:38:42.420 align:start position:0% and then what if that intermediary 00:38:42.420 --> 00:38:44.690 align:start position:0% and then what if that intermediary starts<00:38:42.839> censoring<00:38:43.320> and<00:38:43.740> that<00:38:44.040> or<00:38:44.220> or<00:38:44.520> even 00:38:44.690 --> 00:38:44.700 align:start position:0% starts censoring and that or or even 00:38:44.700 --> 00:38:46.849 align:start position:0% starts censoring and that or or even just<00:38:44.880> you<00:38:44.940> know<00:38:45.060> disappears<00:38:45.599> or<00:38:45.780> whatever<00:38:45.900> and 00:38:46.849 --> 00:38:46.859 align:start position:0% just you know disappears or whatever and 00:38:46.859 --> 00:38:49.490 align:start position:0% just you know disappears or whatever and uh<00:38:47.400> it<00:38:48.060> you<00:38:48.300> know<00:38:48.359> that<00:38:48.540> you<00:38:48.780> end<00:38:48.900> up<00:38:49.079> wasting 00:38:49.490 --> 00:38:49.500 align:start position:0% uh it you know that you end up wasting 00:38:49.500 --> 00:38:51.109 align:start position:0% uh it you know that you end up wasting gas<00:38:49.680> and<00:38:49.920> there's<00:38:50.099> just<00:38:50.339> like<00:38:50.460> a<00:38:50.760> lot<00:38:50.880> of<00:38:50.940> extra 00:38:51.109 --> 00:38:51.119 align:start position:0% gas and there's just like a lot of extra 00:38:51.119 --> 00:38:53.030 align:start position:0% gas and there's just like a lot of extra money<00:38:51.359> black<00:38:51.780> City<00:38:52.079> involved<00:38:52.500> which<00:38:52.619> is<00:38:52.800> I 00:38:53.030 --> 00:38:53.040 align:start position:0% money black City involved which is I 00:38:53.040 --> 00:38:55.310 align:start position:0% money black City involved which is I mean<00:38:53.099> what<00:38:53.339> basically<00:38:54.180> you<00:38:54.960> know<00:38:55.020> what<00:38:55.200> we're 00:38:55.310 --> 00:38:55.320 align:start position:0% mean what basically you know what we're 00:38:55.320 --> 00:38:57.410 align:start position:0% mean what basically you know what we're trying<00:38:55.560> to<00:38:55.680> get<00:38:55.800> rid<00:38:55.920> of<00:38:56.040> here<00:38:56.220> right<00:38:56.520> so<00:38:56.820> I 00:38:57.410 --> 00:38:57.420 align:start position:0% trying to get rid of here right so I 00:38:57.420 --> 00:38:58.609 align:start position:0% trying to get rid of here right so I think<00:38:57.480> like<00:38:57.660> you<00:38:57.839> know<00:38:57.960> multi-sigs<00:38:58.560> and 00:38:58.609 --> 00:38:58.619 align:start position:0% think like you know multi-sigs and 00:38:58.619 --> 00:39:02.150 align:start position:0% think like you know multi-sigs and social<00:38:58.740> recoveries<00:38:59.339> are<00:38:59.820> one<00:39:00.359> easy<00:39:00.920> use<00:39:01.920> case 00:39:02.150 --> 00:39:02.160 align:start position:0% social recoveries are one easy use case 00:39:02.160 --> 00:39:03.890 align:start position:0% social recoveries are one easy use case of<00:39:02.339> abstraction<00:39:02.760> but<00:39:03.119> then<00:39:03.240> another<00:39:03.420> one<00:39:03.720> is 00:39:03.890 --> 00:39:03.900 align:start position:0% of abstraction but then another one is 00:39:03.900 --> 00:39:06.050 align:start position:0% of abstraction but then another one is being<00:39:04.260> Quantum<00:39:04.740> proof<00:39:04.980> right<00:39:05.099> like<00:39:05.400> when<00:39:05.880> the 00:39:06.050 --> 00:39:06.060 align:start position:0% being Quantum proof right like when the 00:39:06.060 --> 00:39:08.510 align:start position:0% being Quantum proof right like when the quantum<00:39:06.359> computers<00:39:06.720> come<00:39:06.960> we<00:39:07.680> yeah<00:39:07.920> we<00:39:08.400> all 00:39:08.510 --> 00:39:08.520 align:start position:0% quantum computers come we yeah we all 00:39:08.520 --> 00:39:11.630 align:start position:0% quantum computers come we yeah we all have<00:39:08.760> to<00:39:08.940> like<00:39:09.180> get<00:39:09.420> move<00:39:09.960> get<00:39:10.320> out<00:39:10.500> of<00:39:10.680> ecdsa 00:39:11.630 --> 00:39:11.640 align:start position:0% have to like get move get out of ecdsa 00:39:11.640 --> 00:39:14.930 align:start position:0% have to like get move get out of ecdsa entirely<00:39:12.060> and<00:39:12.780> is<00:39:13.140> there<00:39:13.320> a<00:39:13.440> timeline<00:39:13.619> on<00:39:13.800> that 00:39:14.930 --> 00:39:14.940 align:start position:0% entirely and is there a timeline on that 00:39:14.940 --> 00:39:16.370 align:start position:0% entirely and is there a timeline on that unknown 00:39:16.370 --> 00:39:16.380 align:start position:0% unknown 00:39:16.380 --> 00:39:17.390 align:start position:0% unknown um 00:39:17.390 --> 00:39:17.400 align:start position:0% um 00:39:17.400 --> 00:39:21.050 align:start position:0% um uh<00:39:18.359> it's<00:39:18.540> unknown<00:39:19.200> but<00:39:19.619> uh<00:39:19.980> but<00:39:20.579> what's<00:39:20.760> but 00:39:21.050 --> 00:39:21.060 align:start position:0% uh it's unknown but uh but what's but 00:39:21.060 --> 00:39:23.210 align:start position:0% uh it's unknown but uh but what's but what's<00:39:21.540> great<00:39:21.720> about<00:39:21.960> our<00:39:22.560> current<00:39:22.740> process 00:39:23.210 --> 00:39:23.220 align:start position:0% what's great about our current process 00:39:23.220 --> 00:39:25.970 align:start position:0% what's great about our current process even<00:39:23.520> with<00:39:23.760> the<00:39:23.940> ELC<00:39:24.420> is<00:39:25.140> that<00:39:25.380> we<00:39:25.619> can<00:39:25.740> start 00:39:25.970 --> 00:39:25.980 align:start position:0% even with the ELC is that we can start 00:39:25.980 --> 00:39:27.650 align:start position:0% even with the ELC is that we can start moving<00:39:26.339> away<00:39:26.520> from<00:39:26.700> it<00:39:26.880> we<00:39:27.060> don't<00:39:27.180> have<00:39:27.300> to<00:39:27.540> do 00:39:27.650 --> 00:39:27.660 align:start position:0% moving away from it we don't have to do 00:39:27.660 --> 00:39:30.589 align:start position:0% moving away from it we don't have to do it<00:39:27.839> one<00:39:28.260> day<00:39:28.500> we<00:39:28.859> can<00:39:28.980> uh<00:39:29.280> we<00:39:29.880> can<00:39:29.940> start<00:39:30.119> moving 00:39:30.589 --> 00:39:30.599 align:start position:0% it one day we can uh we can start moving 00:39:30.599 --> 00:39:33.349 align:start position:0% it one day we can uh we can start moving gradually<00:39:31.200> and<00:39:32.040> over<00:39:32.280> time<00:39:32.579> you'll<00:39:32.940> see<00:39:33.119> less 00:39:33.349 --> 00:39:33.359 align:start position:0% gradually and over time you'll see less 00:39:33.359 --> 00:39:35.870 align:start position:0% gradually and over time you'll see less and<00:39:33.540> less<00:39:33.720> wallets<00:39:34.260> relying<00:39:34.920> on<00:39:35.099> relying<00:39:35.760> on 00:39:35.870 --> 00:39:35.880 align:start position:0% and less wallets relying on relying on 00:39:35.880 --> 00:39:37.069 align:start position:0% and less wallets relying on relying on ecdsa 00:39:37.069 --> 00:39:37.079 align:start position:0% ecdsa 00:39:37.079 --> 00:39:40.730 align:start position:0% ecdsa so<00:39:37.920> we<00:39:38.280> can<00:39:38.400> start<00:39:38.640> moving<00:39:39.300> there<00:39:39.480> it's<00:39:40.260> not<00:39:40.440> a 00:39:40.730 --> 00:39:40.740 align:start position:0% so we can start moving there it's not a 00:39:40.740 --> 00:39:42.010 align:start position:0% so we can start moving there it's not a one<00:39:40.920> day 00:39:42.010 --> 00:39:42.020 align:start position:0% one day 00:39:42.020 --> 00:39:44.630 align:start position:0% one day any<00:39:43.020> utilities<00:39:43.619> that<00:39:43.859> vitalik<00:39:44.280> and<00:39:44.400> yov 00:39:44.630 --> 00:39:44.640 align:start position:0% any utilities that vitalik and yov 00:39:44.640 --> 00:39:45.770 align:start position:0% any utilities that vitalik and yov didn't<00:39:44.820> mention<00:39:45.000> that<00:39:45.180> come<00:39:45.359> to<00:39:45.480> mind<00:39:45.599> about 00:39:45.770 --> 00:39:45.780 align:start position:0% didn't mention that come to mind about 00:39:45.780 --> 00:39:47.750 align:start position:0% didn't mention that come to mind about account<00:39:46.079> instruction 00:39:47.750 --> 00:39:47.760 align:start position:0% account instruction 00:39:47.760 --> 00:39:50.510 align:start position:0% account instruction batch<00:39:48.420> transactions 00:39:50.510 --> 00:39:50.520 align:start position:0% batch transactions 00:39:50.520 --> 00:39:52.370 align:start position:0% batch transactions why<00:39:51.180> is<00:39:51.480> that<00:39:51.599> such<00:39:51.720> a<00:39:51.839> big<00:39:51.900> deal<00:39:52.020> why<00:39:52.200> do<00:39:52.320> we 00:39:52.370 --> 00:39:52.380 align:start position:0% why is that such a big deal why do we 00:39:52.380 --> 00:39:54.530 align:start position:0% why is that such a big deal why do we need<00:39:52.500> that<00:39:53.160> have<00:39:53.579> you<00:39:53.820> ever<00:39:54.000> used<00:39:54.300> the 00:39:54.530 --> 00:39:54.540 align:start position:0% need that have you ever used the 00:39:54.540 --> 00:39:57.050 align:start position:0% need that have you ever used the blockchain 00:39:57.050 --> 00:39:57.060 align:start position:0% blockchain 00:39:57.060 --> 00:39:59.270 align:start position:0% blockchain a<00:39:57.540> few<00:39:57.660> times<00:39:57.839> I've<00:39:58.020> been<00:39:58.260> known<00:39:58.380> yeah<00:39:58.680> what 00:39:59.270 --> 00:39:59.280 align:start position:0% a few times I've been known yeah what 00:39:59.280 --> 00:40:02.089 align:start position:0% a few times I've been known yeah what can<00:40:00.000> you<00:40:00.119> uh<00:40:00.540> do<00:40:01.200> it<00:40:01.320> give<00:40:01.440> us<00:40:01.560> a<00:40:01.680> user<00:40:01.920> story 00:40:02.089 --> 00:40:02.099 align:start position:0% can you uh do it give us a user story 00:40:02.099 --> 00:40:03.829 align:start position:0% can you uh do it give us a user story about<00:40:02.280> like<00:40:02.520> how<00:40:02.700> this<00:40:02.880> is<00:40:03.000> a<00:40:03.180> ux<00:40:03.420> Improvement 00:40:03.829 --> 00:40:03.839 align:start position:0% about like how this is a ux Improvement 00:40:03.839 --> 00:40:06.050 align:start position:0% about like how this is a ux Improvement as<00:40:04.500> a<00:40:04.740> good<00:40:04.800> core<00:40:04.920> developer<00:40:05.460> I<00:40:05.640> don't<00:40:05.760> use<00:40:05.940> the 00:40:06.050 --> 00:40:06.060 align:start position:0% as a good core developer I don't use the 00:40:06.060 --> 00:40:08.150 align:start position:0% as a good core developer I don't use the blockchain<00:40:06.420> very<00:40:06.780> often<00:40:07.079> but<00:40:07.560> when<00:40:07.740> I<00:40:07.859> do<00:40:07.980> use 00:40:08.150 --> 00:40:08.160 align:start position:0% blockchain very often but when I do use 00:40:08.160 --> 00:40:10.550 align:start position:0% blockchain very often but when I do use the<00:40:08.400> blockchain<00:40:08.760> I<00:40:09.540> have<00:40:09.660> to<00:40:09.780> sign<00:40:10.020> so<00:40:10.440> many 00:40:10.550 --> 00:40:10.560 align:start position:0% the blockchain I have to sign so many 00:40:10.560 --> 00:40:12.829 align:start position:0% the blockchain I have to sign so many messages<00:40:10.800> to<00:40:11.339> send<00:40:11.520> anything<00:40:11.880> I<00:40:12.540> have<00:40:12.720> to 00:40:12.829 --> 00:40:12.839 align:start position:0% messages to send anything I have to 00:40:12.839 --> 00:40:15.170 align:start position:0% messages to send anything I have to approve<00:40:13.200> my<00:40:13.380> tokens<00:40:13.619> to<00:40:13.859> go<00:40:13.980> to<00:40:14.099> a<00:40:14.339> contract<00:40:14.700> I 00:40:15.170 --> 00:40:15.180 align:start position:0% approve my tokens to go to a contract I 00:40:15.180 --> 00:40:16.310 align:start position:0% approve my tokens to go to a contract I have<00:40:15.300> to<00:40:15.420> send<00:40:15.540> them<00:40:15.660> then<00:40:15.839> I<00:40:15.960> have<00:40:16.020> to<00:40:16.140> approve 00:40:16.310 --> 00:40:16.320 align:start position:0% have to send them then I have to approve 00:40:16.320 --> 00:40:17.329 align:start position:0% have to send them then I have to approve more<00:40:16.440> tokens<00:40:16.740> to<00:40:16.920> go<00:40:16.980> to<00:40:17.099> a<00:40:17.220> different 00:40:17.329 --> 00:40:17.339 align:start position:0% more tokens to go to a different 00:40:17.339 --> 00:40:19.310 align:start position:0% more tokens to go to a different contract<00:40:17.820> all<00:40:18.300> for<00:40:18.540> the<00:40:18.660> same<00:40:18.839> application 00:40:19.310 --> 00:40:19.320 align:start position:0% contract all for the same application 00:40:19.320 --> 00:40:21.470 align:start position:0% contract all for the same application and<00:40:20.220> to<00:40:20.339> me<00:40:20.400> it's<00:40:20.520> like<00:40:20.700> we<00:40:20.880> could<00:40:21.060> be<00:40:21.240> making 00:40:21.470 --> 00:40:21.480 align:start position:0% and to me it's like we could be making 00:40:21.480 --> 00:40:24.190 align:start position:0% and to me it's like we could be making this<00:40:21.720> all<00:40:21.960> a<00:40:22.140> single<00:40:22.500> message<00:40:22.800> to<00:40:23.099> go<00:40:23.220> on<00:40:23.400> chain 00:40:24.190 --> 00:40:24.200 align:start position:0% this all a single message to go on chain 00:40:24.200 --> 00:40:26.410 align:start position:0% this all a single message to go on chain so<00:40:25.200> you're<00:40:25.320> saying<00:40:25.560> that<00:40:25.680> account<00:40:25.859> extraction 00:40:26.410 --> 00:40:26.420 align:start position:0% so you're saying that account extraction 00:40:26.420 --> 00:40:30.010 align:start position:0% so you're saying that account extraction allows<00:40:27.420> us<00:40:27.540> to 00:40:30.010 --> 00:40:30.020 align:start position:0% 00:40:30.020 --> 00:40:32.750 align:start position:0% produce<00:40:31.020> the<00:40:31.260> ux<00:40:31.680> that<00:40:32.040> people<00:40:32.160> kind<00:40:32.640> of 00:40:32.750 --> 00:40:32.760 align:start position:0% produce the ux that people kind of 00:40:32.760 --> 00:40:34.910 align:start position:0% produce the ux that people kind of expect<00:40:33.119> there<00:40:33.720> to<00:40:33.960> be<00:40:34.079> in<00:40:34.380> the<00:40:34.500> long<00:40:34.560> term<00:40:34.680> that 00:40:34.910 --> 00:40:34.920 align:start position:0% expect there to be in the long term that 00:40:34.920 --> 00:40:37.130 align:start position:0% expect there to be in the long term that we<00:40:35.040> don't<00:40:35.160> have<00:40:35.280> today<00:40:35.460> more<00:40:36.119> or<00:40:36.240> less<00:40:36.300> I<00:40:37.079> don't 00:40:37.130 --> 00:40:37.140 align:start position:0% we don't have today more or less I don't 00:40:37.140 --> 00:40:38.690 align:start position:0% we don't have today more or less I don't think<00:40:37.260> it's<00:40:37.380> just<00:40:37.560> a<00:40:37.800> count<00:40:37.980> abstraction<00:40:38.400> like 00:40:38.690 --> 00:40:38.700 align:start position:0% think it's just a count abstraction like 00:40:38.700 --> 00:40:40.430 align:start position:0% think it's just a count abstraction like I<00:40:38.820> think<00:40:38.940> that<00:40:39.119> we<00:40:39.300> could<00:40:39.420> be<00:40:39.599> living<00:40:40.079> in<00:40:40.320> this 00:40:40.430 --> 00:40:40.440 align:start position:0% I think that we could be living in this 00:40:40.440 --> 00:40:42.589 align:start position:0% I think that we could be living in this world<00:40:40.619> today<00:40:40.920> what<00:40:41.760> I<00:40:41.940> would<00:40:42.060> really<00:40:42.180> like<00:40:42.420> to 00:40:42.589 --> 00:40:42.599 align:start position:0% world today what I would really like to 00:40:42.599 --> 00:40:44.990 align:start position:0% world today what I would really like to see<00:40:42.780> is<00:40:43.079> like<00:40:43.260> some<00:40:43.619> sort<00:40:43.800> of<00:40:43.980> mechanism<00:40:44.700> for 00:40:44.990 --> 00:40:45.000 align:start position:0% see is like some sort of mechanism for 00:40:45.000 --> 00:40:46.730 align:start position:0% see is like some sort of mechanism for dapps<00:40:45.480> to<00:40:45.660> let<00:40:45.780> the<00:40:45.960> wallet<00:40:46.260> know<00:40:46.440> that<00:40:46.560> I 00:40:46.730 --> 00:40:46.740 align:start position:0% dapps to let the wallet know that I 00:40:46.740 --> 00:40:48.490 align:start position:0% dapps to let the wallet know that I would<00:40:46.859> like<00:40:46.920> to<00:40:47.099> send<00:40:47.220> a<00:40:47.400> batch<00:40:47.520> of<00:40:47.760> operations 00:40:48.490 --> 00:40:48.500 align:start position:0% would like to send a batch of operations 00:40:48.500 --> 00:40:51.349 align:start position:0% would like to send a batch of operations and<00:40:49.500> the<00:40:49.800> wallet<00:40:50.099> can<00:40:50.280> determine<00:40:50.700> whether<00:40:51.240> or 00:40:51.349 --> 00:40:51.359 align:start position:0% and the wallet can determine whether or 00:40:51.359 --> 00:40:52.910 align:start position:0% and the wallet can determine whether or not<00:40:51.420> it<00:40:51.540> has<00:40:51.660> the<00:40:51.839> capability<00:40:52.260> of<00:40:52.560> sending 00:40:52.910 --> 00:40:52.920 align:start position:0% not it has the capability of sending 00:40:52.920 --> 00:40:54.950 align:start position:0% not it has the capability of sending those<00:40:53.040> in<00:40:53.280> an<00:40:53.400> atomic<00:40:53.760> batch<00:40:54.000> and<00:40:54.420> so<00:40:54.540> like<00:40:54.720> I 00:40:54.950 --> 00:40:54.960 align:start position:0% those in an atomic batch and so like I 00:40:54.960 --> 00:40:56.089 align:start position:0% those in an atomic batch and so like I would<00:40:55.020> imagine<00:40:55.260> that<00:40:55.560> you<00:40:55.740> know<00:40:55.800> you<00:40:55.920> go<00:40:56.040> to 00:40:56.089 --> 00:40:56.099 align:start position:0% would imagine that you know you go to 00:40:56.099 --> 00:40:57.890 align:start position:0% would imagine that you know you go to uniswap<00:40:56.579> and<00:40:56.700> you<00:40:56.820> need<00:40:56.940> to<00:40:57.060> approve<00:40:57.480> and<00:40:57.660> then 00:40:57.890 --> 00:40:57.900 align:start position:0% uniswap and you need to approve and then 00:40:57.900 --> 00:41:00.470 align:start position:0% uniswap and you need to approve and then do<00:40:58.380> a<00:40:58.560> swap<00:40:58.859> rather<00:40:59.520> than<00:40:59.760> having<00:40:59.940> that<00:41:00.240> pop<00:41:00.359> up 00:41:00.470 --> 00:41:00.480 align:start position:0% do a swap rather than having that pop up 00:41:00.480 --> 00:41:02.750 align:start position:0% do a swap rather than having that pop up as<00:41:00.660> two<00:41:00.900> dialogues<00:41:01.500> if<00:41:01.920> you<00:41:01.980> have<00:41:02.099> metamask<00:41:02.520> it 00:41:02.750 --> 00:41:02.760 align:start position:0% as two dialogues if you have metamask it 00:41:02.760 --> 00:41:05.150 align:start position:0% as two dialogues if you have metamask it could<00:41:02.940> show<00:41:03.119> and<00:41:03.359> say<00:41:03.540> I<00:41:04.320> want<00:41:04.440> you<00:41:04.619> to<00:41:04.859> sign 00:41:05.150 --> 00:41:05.160 align:start position:0% could show and say I want you to sign 00:41:05.160 --> 00:41:07.130 align:start position:0% could show and say I want you to sign two<00:41:05.460> different<00:41:05.640> transactions<00:41:06.359> to<00:41:06.780> do<00:41:06.900> these 00:41:07.130 --> 00:41:07.140 align:start position:0% two different transactions to do these 00:41:07.140 --> 00:41:08.569 align:start position:0% two different transactions to do these two<00:41:07.320> things<00:41:07.500> to<00:41:07.800> complete<00:41:08.220> the<00:41:08.339> operation 00:41:08.569 --> 00:41:08.579 align:start position:0% two things to complete the operation 00:41:08.579 --> 00:41:10.609 align:start position:0% two things to complete the operation that<00:41:08.820> you<00:41:08.940> would<00:41:09.060> want<00:41:09.240> and<00:41:09.960> metamask<00:41:10.380> would 00:41:10.609 --> 00:41:10.619 align:start position:0% that you would want and metamask would 00:41:10.619 --> 00:41:12.050 align:start position:0% that you would want and metamask would send<00:41:10.800> out<00:41:10.920> those<00:41:11.040> two<00:41:11.220> transactions<00:41:11.820> and 00:41:12.050 --> 00:41:12.060 align:start position:0% send out those two transactions and 00:41:12.060 --> 00:41:13.670 align:start position:0% send out those two transactions and verify<00:41:12.420> that<00:41:12.540> they<00:41:12.720> both<00:41:12.839> happen<00:41:13.020> if<00:41:13.500> you<00:41:13.560> have 00:41:13.670 --> 00:41:13.680 align:start position:0% verify that they both happen if you have 00:41:13.680 --> 00:41:15.650 align:start position:0% verify that they both happen if you have a<00:41:13.800> noses<00:41:14.160> safe<00:41:14.339> or<00:41:14.520> an<00:41:14.640> Arjun<00:41:14.940> wallet<00:41:15.300> it<00:41:15.540> would 00:41:15.650 --> 00:41:15.660 align:start position:0% a noses safe or an Arjun wallet it would 00:41:15.660 --> 00:41:17.089 align:start position:0% a noses safe or an Arjun wallet it would get<00:41:15.839> that<00:41:15.960> message<00:41:16.200> and<00:41:16.440> it<00:41:16.560> would<00:41:16.680> say<00:41:16.800> I<00:41:17.040> want 00:41:17.089 --> 00:41:17.099 align:start position:0% get that message and it would say I want 00:41:17.099 --> 00:41:18.770 align:start position:0% get that message and it would say I want you<00:41:17.220> to<00:41:17.339> do<00:41:17.520> two<00:41:17.640> operations<00:41:18.060> but<00:41:18.359> you<00:41:18.599> have 00:41:18.770 --> 00:41:18.780 align:start position:0% you to do two operations but you have 00:41:18.780 --> 00:41:20.329 align:start position:0% you to do two operations but you have the<00:41:18.960> ability<00:41:19.200> to<00:41:19.500> send<00:41:19.619> them<00:41:19.800> all<00:41:19.920> in<00:41:20.099> one 00:41:20.329 --> 00:41:20.339 align:start position:0% the ability to send them all in one 00:41:20.339 --> 00:41:22.069 align:start position:0% the ability to send them all in one transaction<00:41:20.820> so<00:41:21.240> now<00:41:21.359> you<00:41:21.540> just<00:41:21.660> sign<00:41:21.839> one 00:41:22.069 --> 00:41:22.079 align:start position:0% transaction so now you just sign one 00:41:22.079 --> 00:41:23.510 align:start position:0% transaction so now you just sign one transaction<00:41:22.500> and<00:41:22.619> send<00:41:22.859> that<00:41:23.040> off<00:41:23.160> that's 00:41:23.510 --> 00:41:23.520 align:start position:0% transaction and send that off that's 00:41:23.520 --> 00:41:24.589 align:start position:0% transaction and send that off that's something<00:41:23.640> that<00:41:23.880> we<00:41:24.000> could<00:41:24.060> just<00:41:24.240> have<00:41:24.359> today 00:41:24.589 --> 00:41:24.599 align:start position:0% something that we could just have today 00:41:24.599 --> 00:41:27.230 align:start position:0% something that we could just have today that<00:41:25.140> I<00:41:25.320> think<00:41:25.440> we're<00:41:25.619> totally<00:41:25.920> missing 00:41:27.230 --> 00:41:27.240 align:start position:0% that I think we're totally missing 00:41:27.240 --> 00:41:29.270 align:start position:0% that I think we're totally missing and<00:41:27.720> actually<00:41:28.020> a<00:41:28.320> good<00:41:28.500> example<00:41:28.740> of<00:41:28.920> that<00:41:29.099> in 00:41:29.270 --> 00:41:29.280 align:start position:0% and actually a good example of that in 00:41:29.280 --> 00:41:30.770 align:start position:0% and actually a good example of that in practice<00:41:29.460> is<00:41:29.760> on<00:41:29.880> the<00:41:30.000> stagnet<00:41:30.359> ecosystem 00:41:30.770 --> 00:41:30.780 align:start position:0% practice is on the stagnet ecosystem 00:41:30.780 --> 00:41:33.829 align:start position:0% practice is on the stagnet ecosystem there's<00:41:31.260> a<00:41:31.500> like<00:41:31.619> nft<00:41:31.920> Marketplace<00:41:32.480> and<00:41:33.480> and 00:41:33.829 --> 00:41:33.839 align:start position:0% there's a like nft Marketplace and and 00:41:33.839 --> 00:41:35.150 align:start position:0% there's a like nft Marketplace and and there<00:41:34.079> they've<00:41:34.320> introduced<00:41:34.680> the<00:41:34.800> concept<00:41:35.040> of 00:41:35.150 --> 00:41:35.160 align:start position:0% there they've introduced the concept of 00:41:35.160 --> 00:41:37.310 align:start position:0% there they've introduced the concept of a<00:41:35.339> shopping<00:41:35.460> cart<00:41:35.760> so<00:41:36.420> when<00:41:36.540> you<00:41:36.720> go<00:41:36.839> you<00:41:37.200> can 00:41:37.310 --> 00:41:37.320 align:start position:0% a shopping cart so when you go you can 00:41:37.320 --> 00:41:39.109 align:start position:0% a shopping cart so when you go you can actually<00:41:37.500> do<00:41:38.040> your<00:41:38.220> shopping<00:41:38.400> in<00:41:38.640> a<00:41:38.820> sand<00:41:38.940> you 00:41:39.109 --> 00:41:39.119 align:start position:0% actually do your shopping in a sand you 00:41:39.119 --> 00:41:40.790 align:start position:0% actually do your shopping in a sand you want<00:41:39.240> to<00:41:39.300> buy<00:41:39.420> that<00:41:39.599> Nifty<00:41:40.079> in<00:41:40.200> that<00:41:40.440> one<00:41:40.500> that 00:41:40.790 --> 00:41:40.800 align:start position:0% want to buy that Nifty in that one that 00:41:40.800 --> 00:41:43.190 align:start position:0% want to buy that Nifty in that one that one<00:41:40.980> and<00:41:41.099> you<00:41:41.280> will<00:41:41.400> pay<00:41:41.640> different<00:41:42.000> token<00:41:42.480> and 00:41:43.190 --> 00:41:43.200 align:start position:0% one and you will pay different token and 00:41:43.200 --> 00:41:45.230 align:start position:0% one and you will pay different token and at<00:41:43.320> the<00:41:43.500> end<00:41:43.619> of<00:41:43.740> your<00:41:43.920> session<00:41:44.280> you<00:41:44.940> go<00:41:45.119> to 00:41:45.230 --> 00:41:45.240 align:start position:0% at the end of your session you go to 00:41:45.240 --> 00:41:46.849 align:start position:0% at the end of your session you go to your<00:41:45.420> shopping<00:41:45.599> cart<00:41:45.839> you<00:41:46.140> say<00:41:46.320> buy<00:41:46.500> these 00:41:46.849 --> 00:41:46.859 align:start position:0% your shopping cart you say buy these 00:41:46.859 --> 00:41:48.770 align:start position:0% your shopping cart you say buy these items<00:41:47.160> now<00:41:47.280> and<00:41:47.940> your<00:41:48.180> smart<00:41:48.420> contract 00:41:48.770 --> 00:41:48.780 align:start position:0% items now and your smart contract 00:41:48.780 --> 00:41:51.050 align:start position:0% items now and your smart contract without<00:41:49.280> orchestrate<00:41:50.280> all<00:41:50.520> these<00:41:50.760> operations 00:41:51.050 --> 00:41:51.060 align:start position:0% without orchestrate all these operations 00:41:51.060 --> 00:41:52.730 align:start position:0% without orchestrate all these operations so<00:41:51.359> it<00:41:51.480> will<00:41:51.599> do<00:41:51.780> all<00:41:51.960> the<00:41:52.140> approved<00:41:52.560> on<00:41:52.680> the 00:41:52.730 --> 00:41:52.740 align:start position:0% so it will do all the approved on the 00:41:52.740 --> 00:41:54.710 align:start position:0% so it will do all the approved on the C20<00:41:53.160> token<00:41:53.579> that<00:41:53.760> are<00:41:53.880> needed<00:41:54.180> and<00:41:54.599> then 00:41:54.710 --> 00:41:54.720 align:start position:0% C20 token that are needed and then 00:41:54.720 --> 00:41:57.170 align:start position:0% C20 token that are needed and then purchase<00:41:55.140> all<00:41:55.380> these<00:41:55.560> nfts<00:41:56.040> also<00:41:56.400> exactly 00:41:57.170 --> 00:41:57.180 align:start position:0% purchase all these nfts also exactly 00:41:57.180 --> 00:41:58.790 align:start position:0% purchase all these nfts also exactly this<00:41:57.359> is<00:41:57.480> I<00:41:57.660> think<00:41:57.780> the<00:41:57.900> multi-code<00:41:58.380> is<00:41:58.500> a 00:41:58.790 --> 00:41:58.800 align:start position:0% this is I think the multi-code is a 00:41:58.800 --> 00:42:01.069 align:start position:0% this is I think the multi-code is a great<00:41:58.920> example<00:41:59.760> social<00:42:00.300> recovery<00:42:00.839> is<00:42:00.960> another 00:42:01.069 --> 00:42:01.079 align:start position:0% great example social recovery is another 00:42:01.079 --> 00:42:03.650 align:start position:0% great example social recovery is another great<00:42:01.440> example<00:42:01.740> so<00:42:01.980> I<00:42:02.220> come<00:42:02.400> last<00:42:02.579> but<00:42:03.240> I<00:42:03.480> still 00:42:03.650 --> 00:42:03.660 align:start position:0% great example so I come last but I still 00:42:03.660 --> 00:42:04.849 align:start position:0% great example so I come last but I still think<00:42:03.780> something<00:42:04.079> that<00:42:04.320> I<00:42:04.500> find<00:42:04.619> very 00:42:04.849 --> 00:42:04.859 align:start position:0% think something that I find very 00:42:04.859 --> 00:42:06.829 align:start position:0% think something that I find very interesting<00:42:05.220> is<00:42:05.820> the<00:42:06.000> idea<00:42:06.240> of<00:42:06.359> off-road 00:42:06.829 --> 00:42:06.839 align:start position:0% interesting is the idea of off-road 00:42:06.839 --> 00:42:08.690 align:start position:0% interesting is the idea of off-road monitoring<00:42:07.320> because<00:42:07.800> I<00:42:08.099> think<00:42:08.280> the<00:42:08.520> problem 00:42:08.690 --> 00:42:08.700 align:start position:0% monitoring because I think the problem 00:42:08.700 --> 00:42:10.970 align:start position:0% monitoring because I think the problem with<00:42:08.940> the<00:42:09.119> blockchain<00:42:09.480> is<00:42:09.839> that<00:42:10.079> I<00:42:10.500> mean<00:42:10.619> we 00:42:10.970 --> 00:42:10.980 align:start position:0% with the blockchain is that I mean we 00:42:10.980 --> 00:42:12.770 align:start position:0% with the blockchain is that I mean we make<00:42:11.220> users<00:42:11.640> or<00:42:11.820> there<00:42:12.000> are<00:42:12.119> Bad<00:42:12.240> actors<00:42:12.599> and 00:42:12.770 --> 00:42:12.780 align:start position:0% make users or there are Bad actors and 00:42:12.780 --> 00:42:14.329 align:start position:0% make users or there are Bad actors and it's<00:42:12.960> sometimes<00:42:13.260> very<00:42:13.500> complicated<00:42:13.980> to<00:42:14.220> know 00:42:14.329 --> 00:42:14.339 align:start position:0% it's sometimes very complicated to know 00:42:14.339 --> 00:42:16.370 align:start position:0% it's sometimes very complicated to know exactly<00:42:14.880> what<00:42:15.660> you<00:42:15.780> are<00:42:15.900> doing<00:42:16.020> as<00:42:16.200> a 00:42:16.370 --> 00:42:16.380 align:start position:0% exactly what you are doing as a 00:42:16.380 --> 00:42:17.930 align:start position:0% exactly what you are doing as a transaction<00:42:16.680> typically<00:42:17.280> you'll<00:42:17.579> see<00:42:17.760> some 00:42:17.930 --> 00:42:17.940 align:start position:0% transaction typically you'll see some 00:42:17.940 --> 00:42:19.190 align:start position:0% transaction typically you'll see some you<00:42:18.119> know<00:42:18.180> some<00:42:18.359> called<00:42:18.540> Data<00:42:18.900> or<00:42:19.020> something 00:42:19.190 --> 00:42:19.200 align:start position:0% you know some called Data or something 00:42:19.200 --> 00:42:21.230 align:start position:0% you know some called Data or something that<00:42:19.440> is<00:42:19.560> very<00:42:19.740> obscure<00:42:20.160> and<00:42:20.760> it's<00:42:20.880> very 00:42:21.230 --> 00:42:21.240 align:start position:0% that is very obscure and it's very 00:42:21.240 --> 00:42:23.030 align:start position:0% that is very obscure and it's very complicated<00:42:21.599> for<00:42:21.900> us<00:42:22.020> as<00:42:22.260> a<00:42:22.440> human<00:42:22.619> to 00:42:23.030 --> 00:42:23.040 align:start position:0% complicated for us as a human to 00:42:23.040 --> 00:42:26.030 align:start position:0% complicated for us as a human to actually<00:42:23.280> you<00:42:23.520> know<00:42:23.640> know<00:42:24.300> the<00:42:24.720> the<00:42:25.040> actions 00:42:26.030 --> 00:42:26.040 align:start position:0% actually you know know the the actions 00:42:26.040 --> 00:42:28.670 align:start position:0% actually you know know the the actions that<00:42:26.220> that<00:42:26.400> we<00:42:26.579> are<00:42:26.700> making<00:42:26.880> and<00:42:27.839> with<00:42:28.320> a<00:42:28.500> smart 00:42:28.670 --> 00:42:28.680 align:start position:0% that that we are making and with a smart 00:42:28.680 --> 00:42:30.290 align:start position:0% that that we are making and with a smart contract<00:42:29.099> our<00:42:29.339> current<00:42:29.579> abstraction<00:42:29.940> you<00:42:30.180> can 00:42:30.290 --> 00:42:30.300 align:start position:0% contract our current abstraction you can 00:42:30.300 --> 00:42:32.630 align:start position:0% contract our current abstraction you can imagine<00:42:30.420> for<00:42:30.839> example<00:42:31.020> that<00:42:31.380> you<00:42:31.500> you<00:42:31.859> program 00:42:32.630 --> 00:42:32.640 align:start position:0% imagine for example that you you program 00:42:32.640 --> 00:42:34.670 align:start position:0% imagine for example that you you program a<00:42:33.000> second<00:42:33.180> key<00:42:33.420> on<00:42:33.660> your<00:42:33.780> account<00:42:33.960> that<00:42:34.440> must 00:42:34.670 --> 00:42:34.680 align:start position:0% a second key on your account that must 00:42:34.680 --> 00:42:36.410 align:start position:0% a second key on your account that must co-sign<00:42:35.220> every<00:42:35.460> transaction<00:42:35.820> so<00:42:36.119> you<00:42:36.300> turn 00:42:36.410 --> 00:42:36.420 align:start position:0% co-sign every transaction so you turn 00:42:36.420 --> 00:42:38.210 align:start position:0% co-sign every transaction so you turn your<00:42:36.599> account<00:42:36.720> in<00:42:37.079> the<00:42:37.200> two<00:42:37.380> of<00:42:37.440> two<00:42:37.619> multisig 00:42:38.210 --> 00:42:38.220 align:start position:0% your account in the two of two multisig 00:42:38.220 --> 00:42:39.950 align:start position:0% your account in the two of two multisig but<00:42:38.640> then<00:42:38.820> you<00:42:38.940> can<00:42:39.060> choose<00:42:39.300> to<00:42:39.420> give<00:42:39.599> that<00:42:39.839> key 00:42:39.950 --> 00:42:39.960 align:start position:0% but then you can choose to give that key 00:42:39.960 --> 00:42:42.589 align:start position:0% but then you can choose to give that key to<00:42:40.200> a<00:42:40.380> service<00:42:40.560> that<00:42:41.460> may<00:42:41.640> monitor<00:42:42.180> the 00:42:42.589 --> 00:42:42.599 align:start position:0% to a service that may monitor the 00:42:42.599 --> 00:42:44.329 align:start position:0% to a service that may monitor the operation<00:42:42.960> that<00:42:43.200> you<00:42:43.320> are<00:42:43.440> about<00:42:43.560> to<00:42:43.800> do<00:42:43.920> and 00:42:44.329 --> 00:42:44.339 align:start position:0% operation that you are about to do and 00:42:44.339 --> 00:42:45.950 align:start position:0% operation that you are about to do and so<00:42:44.460> that<00:42:44.579> service<00:42:44.760> if<00:42:45.060> it<00:42:45.240> takes<00:42:45.480> that<00:42:45.720> the 00:42:45.950 --> 00:42:45.960 align:start position:0% so that service if it takes that the 00:42:45.960 --> 00:42:47.870 align:start position:0% so that service if it takes that the call<00:42:46.140> data<00:42:46.560> is<00:42:46.680> legit<00:42:47.040> it's<00:42:47.339> something<00:42:47.520> that 00:42:47.870 --> 00:42:47.880 align:start position:0% call data is legit it's something that 00:42:47.880 --> 00:42:49.849 align:start position:0% call data is legit it's something that you<00:42:48.000> know<00:42:48.119> is<00:42:48.300> secure<00:42:48.660> you<00:42:49.260> can<00:42:49.440> co-sign 00:42:49.849 --> 00:42:49.859 align:start position:0% you know is secure you can co-sign 00:42:49.859 --> 00:42:51.170 align:start position:0% you know is secure you can co-sign automatically<00:42:50.339> it's<00:42:50.460> transparent<00:42:50.940> to<00:42:51.060> the 00:42:51.170 --> 00:42:51.180 align:start position:0% automatically it's transparent to the 00:42:51.180 --> 00:42:53.750 align:start position:0% automatically it's transparent to the user<00:42:51.540> but<00:42:52.079> now<00:42:52.260> you're<00:42:52.800> making<00:42:52.980> a<00:42:53.339> last 00:42:53.750 --> 00:42:53.760 align:start position:0% user but now you're making a last 00:42:53.760 --> 00:42:55.550 align:start position:0% user but now you're making a last transfer<00:42:54.180> to<00:42:54.420> an<00:42:54.540> address<00:42:54.839> that<00:42:55.200> you've<00:42:55.380> never 00:42:55.550 --> 00:42:55.560 align:start position:0% transfer to an address that you've never 00:42:55.560 --> 00:42:57.710 align:start position:0% transfer to an address that you've never interacted<00:42:56.040> with<00:42:56.280> maybe<00:42:57.000> you<00:42:57.240> can<00:42:57.420> just<00:42:57.540> ask 00:42:57.710 --> 00:42:57.720 align:start position:0% interacted with maybe you can just ask 00:42:57.720 --> 00:42:59.690 align:start position:0% interacted with maybe you can just ask you<00:42:57.900> to<00:42:58.079> confirm<00:42:58.500> who<00:42:58.680> you<00:42:58.859> are<00:42:58.980> with<00:42:59.220> a<00:42:59.339> second 00:42:59.690 --> 00:42:59.700 align:start position:0% you to confirm who you are with a second 00:42:59.700 --> 00:43:02.030 align:start position:0% you to confirm who you are with a second sector<00:43:00.119> like<00:43:00.540> email<00:43:00.720> and<00:43:00.960> SMS<00:43:01.380> or<00:43:01.500> Google<00:43:01.680> load 00:43:02.030 --> 00:43:02.040 align:start position:0% sector like email and SMS or Google load 00:43:02.040 --> 00:43:04.190 align:start position:0% sector like email and SMS or Google load or<00:43:02.160> something<00:43:02.339> so<00:43:02.940> using<00:43:03.300> a<00:43:03.420> construction<00:43:03.660> we 00:43:04.190 --> 00:43:04.200 align:start position:0% or something so using a construction we 00:43:04.200 --> 00:43:06.650 align:start position:0% or something so using a construction we can<00:43:04.380> actually<00:43:04.740> bring<00:43:05.220> the<00:43:05.579> flows<00:43:06.000> that<00:43:06.180> user 00:43:06.650 --> 00:43:06.660 align:start position:0% can actually bring the flows that user 00:43:06.660 --> 00:43:08.990 align:start position:0% can actually bring the flows that user normal<00:43:07.140> user<00:43:07.619> are<00:43:07.800> expecting<00:43:08.220> you<00:43:08.460> know<00:43:08.579> bring 00:43:08.990 --> 00:43:09.000 align:start position:0% normal user are expecting you know bring 00:43:09.000 --> 00:43:11.210 align:start position:0% normal user are expecting you know bring the<00:43:09.240> best<00:43:09.420> of<00:43:09.660> web<00:43:09.900> 2<00:43:10.200> or<00:43:10.500> of<00:43:10.680> the<00:43:10.920> banking 00:43:11.210 --> 00:43:11.220 align:start position:0% the best of web 2 or of the banking 00:43:11.220 --> 00:43:13.370 align:start position:0% the best of web 2 or of the banking world<00:43:11.339> but<00:43:11.579> actually<00:43:11.819> reproduce<00:43:12.420> that<00:43:12.660> purely 00:43:13.370 --> 00:43:13.380 align:start position:0% world but actually reproduce that purely 00:43:13.380 --> 00:43:15.470 align:start position:0% world but actually reproduce that purely on<00:43:13.680> chain<00:43:13.859> so<00:43:14.520> I<00:43:14.640> think<00:43:14.760> yeah<00:43:14.940> for<00:43:15.180> me<00:43:15.300> it's 00:43:15.470 --> 00:43:15.480 align:start position:0% on chain so I think yeah for me it's 00:43:15.480 --> 00:43:17.329 align:start position:0% on chain so I think yeah for me it's really<00:43:15.660> multi-core<00:43:16.319> social<00:43:16.560> recovery<00:43:17.099> and 00:43:17.329 --> 00:43:17.339 align:start position:0% really multi-core social recovery and 00:43:17.339 --> 00:43:20.210 align:start position:0% really multi-core social recovery and and<00:43:17.720> fraud<00:43:18.720> monitoring<00:43:19.200> are<00:43:19.440> three<00:43:19.800> ways<00:43:20.099> that 00:43:20.210 --> 00:43:20.220 align:start position:0% and fraud monitoring are three ways that 00:43:20.220 --> 00:43:21.890 align:start position:0% and fraud monitoring are three ways that we<00:43:20.400> can<00:43:20.520> greatly<00:43:20.880> improve<00:43:21.240> the<00:43:21.420> the<00:43:21.599> user 00:43:21.890 --> 00:43:21.900 align:start position:0% we can greatly improve the the user 00:43:21.900 --> 00:43:23.510 align:start position:0% we can greatly improve the the user experience<00:43:22.140> for<00:43:22.380> users 00:43:23.510 --> 00:43:23.520 align:start position:0% experience for users 00:43:23.520 --> 00:43:25.670 align:start position:0% experience for users one<00:43:24.119> thing<00:43:24.240> I'm<00:43:24.359> still<00:43:24.599> uncertain<00:43:25.020> of<00:43:25.260> is<00:43:25.500> is 00:43:25.670 --> 00:43:25.680 align:start position:0% one thing I'm still uncertain of is is 00:43:25.680 --> 00:43:28.490 align:start position:0% one thing I'm still uncertain of is is how<00:43:26.160> we<00:43:26.819> we<00:43:26.940> want<00:43:27.359> everyone<00:43:27.540> to<00:43:27.839> have<00:43:27.960> a<00:43:28.319> smart 00:43:28.490 --> 00:43:28.500 align:start position:0% how we we want everyone to have a smart 00:43:28.500 --> 00:43:30.410 align:start position:0% how we we want everyone to have a smart contract<00:43:28.800> while<00:43:29.040> we<00:43:29.640> assume<00:43:30.060> that<00:43:30.240> everyone 00:43:30.410 --> 00:43:30.420 align:start position:0% contract while we assume that everyone 00:43:30.420 --> 00:43:31.670 align:start position:0% contract while we assume that everyone will<00:43:30.660> eventually<00:43:30.900> have<00:43:31.079> a<00:43:31.260> smart<00:43:31.380> contract 00:43:31.670 --> 00:43:31.680 align:start position:0% will eventually have a smart contract 00:43:31.680 --> 00:43:33.290 align:start position:0% will eventually have a smart contract while<00:43:31.920> as<00:43:32.220> everyone<00:43:32.339> is<00:43:32.579> in<00:43:32.819> this<00:43:32.940> room<00:43:33.060> and 00:43:33.290 --> 00:43:33.300 align:start position:0% while as everyone is in this room and 00:43:33.300 --> 00:43:35.510 align:start position:0% while as everyone is in this room and also<00:43:33.599> all<00:43:33.839> future<00:43:34.079> users<00:43:34.500> of<00:43:34.619> ethereum<00:43:35.040> how 00:43:35.510 --> 00:43:35.520 align:start position:0% also all future users of ethereum how 00:43:35.520 --> 00:43:37.010 align:start position:0% also all future users of ethereum how does<00:43:35.579> that<00:43:35.760> actually<00:43:35.880> happen<00:43:36.240> as<00:43:36.540> in<00:43:36.720> who<00:43:36.900> are 00:43:37.010 --> 00:43:37.020 align:start position:0% does that actually happen as in who are 00:43:37.020 --> 00:43:38.510 align:start position:0% does that actually happen as in who are the<00:43:37.140> service<00:43:37.319> providers<00:43:37.859> we<00:43:38.220> have<00:43:38.400> somebody 00:43:38.510 --> 00:43:38.520 align:start position:0% the service providers we have somebody 00:43:38.520 --> 00:43:40.250 align:start position:0% the service providers we have somebody like<00:43:38.760> Arjun<00:43:39.180> who's<00:43:39.420> producing<00:43:39.839> a<00:43:40.079> smart 00:43:40.250 --> 00:43:40.260 align:start position:0% like Arjun who's producing a smart 00:43:40.260 --> 00:43:42.349 align:start position:0% like Arjun who's producing a smart contract<00:43:40.619> wallet<00:43:41.040> but<00:43:41.700> what<00:43:41.940> are<00:43:42.119> the<00:43:42.240> other 00:43:42.349 --> 00:43:42.359 align:start position:0% contract wallet but what are the other 00:43:42.359 --> 00:43:45.290 align:start position:0% contract wallet but what are the other categories<00:43:42.960> of<00:43:43.560> how<00:43:44.220> smart<00:43:44.400> contract<00:43:44.880> wallets 00:43:45.290 --> 00:43:45.300 align:start position:0% categories of how smart contract wallets 00:43:45.300 --> 00:43:47.990 align:start position:0% categories of how smart contract wallets get<00:43:45.540> into<00:43:45.720> the<00:43:45.900> hands<00:43:46.140> of<00:43:46.260> users<00:43:46.619> uh<00:43:47.460> like<00:43:47.700> I 00:43:47.990 --> 00:43:48.000 align:start position:0% get into the hands of users uh like I 00:43:48.000 --> 00:43:49.250 align:start position:0% get into the hands of users uh like I could<00:43:48.060> imagine<00:43:48.240> for<00:43:48.599> example<00:43:48.839> like<00:43:49.079> I'm 00:43:49.250 --> 00:43:49.260 align:start position:0% could imagine for example like I'm 00:43:49.260 --> 00:43:51.890 align:start position:0% could imagine for example like I'm logging<00:43:49.619> into<00:43:49.740> some<00:43:50.280> web3<00:43:50.700> game<00:43:51.000> and<00:43:51.540> I<00:43:51.780> need 00:43:51.890 --> 00:43:51.900 align:start position:0% logging into some web3 game and I need 00:43:51.900 --> 00:43:53.569 align:start position:0% logging into some web3 game and I need to<00:43:51.960> use<00:43:52.140> a<00:43:52.319> wallet<00:43:52.560> for<00:43:52.680> that<00:43:52.859> where<00:43:53.280> does<00:43:53.460> that 00:43:53.569 --> 00:43:53.579 align:start position:0% to use a wallet for that where does that 00:43:53.579 --> 00:43:55.250 align:start position:0% to use a wallet for that where does that wallet<00:43:53.880> come<00:43:54.060> from<00:43:54.180> who<00:43:54.480> provides<00:43:55.079> that 00:43:55.250 --> 00:43:55.260 align:start position:0% wallet come from who provides that 00:43:55.260 --> 00:43:57.770 align:start position:0% wallet come from who provides that wallet<00:43:55.680> and<00:43:56.040> maybe<00:43:56.700> maybe<00:43:57.060> that's<00:43:57.300> what<00:43:57.420> Nosa 00:43:57.770 --> 00:43:57.780 align:start position:0% wallet and maybe maybe that's what Nosa 00:43:57.780 --> 00:43:59.329 align:start position:0% wallet and maybe maybe that's what Nosa safe<00:43:57.960> is<00:43:58.140> but<00:43:58.380> maybe<00:43:58.500> not<00:43:58.680> like<00:43:58.859> what<00:43:59.040> are<00:43:59.220> the 00:43:59.329 --> 00:43:59.339 align:start position:0% safe is but maybe not like what are the 00:43:59.339 --> 00:44:02.030 align:start position:0% safe is but maybe not like what are the categories<00:44:00.180> of<00:44:00.480> who's<00:44:01.140> providing<00:44:01.740> all<00:44:01.980> of 00:44:02.030 --> 00:44:02.040 align:start position:0% categories of who's providing all of 00:44:02.040 --> 00:44:04.490 align:start position:0% categories of who's providing all of these<00:44:02.280> wallet<00:44:02.760> uh<00:44:03.300> wallets<00:44:03.780> to<00:44:03.960> us<00:44:04.140> all<00:44:04.380> the 00:44:04.490 --> 00:44:04.500 align:start position:0% these wallet uh wallets to us all the 00:44:04.500 --> 00:44:05.390 align:start position:0% these wallet uh wallets to us all the users<00:44:04.740> like<00:44:04.859> are<00:44:05.040> there<00:44:05.220> different 00:44:05.390 --> 00:44:05.400 align:start position:0% users like are there different 00:44:05.400 --> 00:44:07.010 align:start position:0% users like are there different categories<00:44:05.819> out<00:44:06.060> there 00:44:07.010 --> 00:44:07.020 align:start position:0% categories out there 00:44:07.020 --> 00:44:10.190 align:start position:0% categories out there I<00:44:07.680> think<00:44:07.859> my<00:44:08.640> philosophy<00:44:09.060> on<00:44:09.240> this<00:44:09.480> is<00:44:09.839> that 00:44:10.190 --> 00:44:10.200 align:start position:0% I think my philosophy on this is that 00:44:10.200 --> 00:44:12.650 align:start position:0% I think my philosophy on this is that like<00:44:10.859> one<00:44:11.099> of<00:44:11.220> the<00:44:11.339> really<00:44:11.819> strong<00:44:12.060> ideas<00:44:12.359> here 00:44:12.650 --> 00:44:12.660 align:start position:0% like one of the really strong ideas here 00:44:12.660 --> 00:44:15.230 align:start position:0% like one of the really strong ideas here is<00:44:12.900> that<00:44:13.079> we<00:44:13.200> want<00:44:13.380> to<00:44:13.560> be<00:44:13.859> as<00:44:14.760> a<00:44:15.060> kind<00:44:15.119> of 00:44:15.230 --> 00:44:15.240 align:start position:0% is that we want to be as a kind of 00:44:15.240 --> 00:44:16.910 align:start position:0% is that we want to be as a kind of active<00:44:15.599> intermediary<00:44:16.140> minimized<00:44:16.740> as 00:44:16.910 --> 00:44:16.920 align:start position:0% active intermediary minimized as 00:44:16.920 --> 00:44:18.770 align:start position:0% active intermediary minimized as possible<00:44:17.280> right<00:44:17.579> to<00:44:18.000> the<00:44:18.240> point<00:44:18.359> of<00:44:18.540> like 00:44:18.770 --> 00:44:18.780 align:start position:0% possible right to the point of like 00:44:18.780 --> 00:44:21.230 align:start position:0% possible right to the point of like basically<00:44:19.319> you<00:44:19.980> know<00:44:20.040> in<00:44:20.220> an<00:44:20.400> ideal<00:44:20.640> world<00:44:20.819> not 00:44:21.230 --> 00:44:21.240 align:start position:0% basically you know in an ideal world not 00:44:21.240 --> 00:44:23.569 align:start position:0% basically you know in an ideal world not requiring<00:44:21.720> any<00:44:22.079> active<00:44:22.500> intermediaries<00:44:23.220> that 00:44:23.569 --> 00:44:23.579 align:start position:0% requiring any active intermediaries that 00:44:23.579 --> 00:44:27.589 align:start position:0% requiring any active intermediaries that don't<00:44:24.060> uh<00:44:24.420> already<00:44:24.839> exist<00:44:25.380> in<00:44:25.800> eoa<00:44:26.400> land<00:44:26.579> right 00:44:27.589 --> 00:44:27.599 align:start position:0% don't uh already exist in eoa land right 00:44:27.599 --> 00:44:30.410 align:start position:0% don't uh already exist in eoa land right um<00:44:27.660> so<00:44:28.140> the<00:44:29.040> yeah<00:44:29.339> like<00:44:29.700> you<00:44:29.880> know<00:44:30.000> there<00:44:30.240> are 00:44:30.410 --> 00:44:30.420 align:start position:0% um so the yeah like you know there are 00:44:30.420 --> 00:44:32.630 align:start position:0% um so the yeah like you know there are people<00:44:30.660> there<00:44:31.140> are<00:44:31.260> kind<00:44:31.560> of<00:44:31.680> it's<00:44:32.099> you<00:44:32.520> know 00:44:32.630 --> 00:44:32.640 align:start position:0% people there are kind of it's you know 00:44:32.640 --> 00:44:35.390 align:start position:0% people there are kind of it's you know acts<00:44:33.300> once<00:44:33.599> in<00:44:33.960> that<00:44:34.140> intermediary<00:44:34.980> is<00:44:35.220> what 00:44:35.390 --> 00:44:35.400 align:start position:0% acts once in that intermediary is what 00:44:35.400 --> 00:44:36.710 align:start position:0% acts once in that intermediary is what that<00:44:35.700> could<00:44:35.760> you<00:44:35.940> know<00:44:36.060> do<00:44:36.180> their<00:44:36.359> thing<00:44:36.599> and 00:44:36.710 --> 00:44:36.720 align:start position:0% that could you know do their thing and 00:44:36.720 --> 00:44:38.329 align:start position:0% that could you know do their thing and then<00:44:36.839> disappear<00:44:37.200> which<00:44:37.560> are<00:44:37.740> you<00:44:37.859> know<00:44:37.980> smart 00:44:38.329 --> 00:44:38.339 align:start position:0% then disappear which are you know smart 00:44:38.339 --> 00:44:39.950 align:start position:0% then disappear which are you know smart contract<00:44:38.760> wallet<00:44:39.240> authors<00:44:39.540> wallet 00:44:39.950 --> 00:44:39.960 align:start position:0% contract wallet authors wallet 00:44:39.960 --> 00:44:42.230 align:start position:0% contract wallet authors wallet developers<00:44:40.380> and<00:44:40.619> people<00:44:40.980> like<00:44:41.220> that<00:44:41.400> but<00:44:41.700> look 00:44:42.230 --> 00:44:42.240 align:start position:0% developers and people like that but look 00:44:42.240 --> 00:44:44.510 align:start position:0% developers and people like that but look we<00:44:42.540> don't<00:44:42.660> want<00:44:42.960> to<00:44:43.200> how<00:44:43.560> to 00:44:44.510 --> 00:44:44.520 align:start position:0% we don't want to how to 00:44:44.520 --> 00:44:47.450 align:start position:0% we don't want to how to depend<00:44:45.359> on<00:44:45.660> you<00:44:45.960> know<00:44:46.020> like<00:44:46.260> active<00:44:46.740> a<00:44:47.160> kind<00:44:47.400> of 00:44:47.450 --> 00:44:47.460 align:start position:0% depend on you know like active a kind of 00:44:47.460 --> 00:44:49.250 align:start position:0% depend on you know like active a kind of relaying<00:44:48.000> actors<00:44:48.300> of<00:44:48.480> some<00:44:48.660> kind<00:44:48.780> for<00:44:49.020> example 00:44:49.250 --> 00:44:49.260 align:start position:0% relaying actors of some kind for example 00:44:49.260 --> 00:44:51.170 align:start position:0% relaying actors of some kind for example right<00:44:49.440> which<00:44:49.680> is<00:44:50.040> um<00:44:50.040> you<00:44:50.220> know<00:44:50.280> that<00:44:50.460> like<00:44:50.819> the 00:44:51.170 --> 00:44:51.180 align:start position:0% right which is um you know that like the 00:44:51.180 --> 00:44:53.390 align:start position:0% right which is um you know that like the status<00:44:51.359> quo<00:44:51.599> is<00:44:51.960> that<00:44:52.079> you<00:44:52.260> do<00:44:52.319> need<00:44:52.500> Asia<00:44:52.980> like 00:44:53.390 --> 00:44:53.400 align:start position:0% status quo is that you do need Asia like 00:44:53.400 --> 00:44:54.950 align:start position:0% status quo is that you do need Asia like you<00:44:53.520> do<00:44:53.819> need<00:44:54.060> to<00:44:54.180> talk<00:44:54.420> to<00:44:54.599> a<00:44:54.780> specific 00:44:54.950 --> 00:44:54.960 align:start position:0% you do need to talk to a specific 00:44:54.960 --> 00:44:57.710 align:start position:0% you do need to talk to a specific relaying<00:44:55.560> actor<00:44:55.859> if<00:44:56.040> you<00:44:56.220> want<00:44:56.400> a<00:44:56.880> uh<00:44:57.300> you<00:44:57.599> know 00:44:57.710 --> 00:44:57.720 align:start position:0% relaying actor if you want a uh you know 00:44:57.720 --> 00:44:59.510 align:start position:0% relaying actor if you want a uh you know if<00:44:57.900> you<00:44:58.020> don't<00:44:58.140> have<00:44:58.319> your<00:44:58.560> own<00:44:58.920> um<00:44:58.920> Ela<00:44:59.400> and 00:44:59.510 --> 00:44:59.520 align:start position:0% if you don't have your own um Ela and 00:44:59.520 --> 00:45:01.910 align:start position:0% if you don't have your own um Ela and you<00:44:59.640> want<00:44:59.760> to<00:44:59.819> use<00:44:59.940> a<00:45:00.060> transaction<00:45:00.839> through<00:45:01.260> a 00:45:01.910 --> 00:45:01.920 align:start position:0% you want to use a transaction through a 00:45:01.920 --> 00:45:03.710 align:start position:0% you want to use a transaction through a smart<00:45:02.339> contract<00:45:02.760> well<00:45:02.940> right<00:45:03.240> and<00:45:03.420> I<00:45:03.540> think 00:45:03.710 --> 00:45:03.720 align:start position:0% smart contract well right and I think 00:45:03.720 --> 00:45:05.630 align:start position:0% smart contract well right and I think you<00:45:04.200> know<00:45:04.260> censorship<00:45:04.740> resistance<00:45:05.160> is<00:45:05.339> a<00:45:05.520> good 00:45:05.630 --> 00:45:05.640 align:start position:0% you know censorship resistance is a good 00:45:05.640 --> 00:45:07.490 align:start position:0% you know censorship resistance is a good reason<00:45:05.819> to<00:45:06.180> minimize<00:45:06.599> activities<00:45:07.020> or<00:45:07.319> Media 00:45:07.490 --> 00:45:07.500 align:start position:0% reason to minimize activities or Media 00:45:07.500 --> 00:45:09.410 align:start position:0% reason to minimize activities or Media or<00:45:07.619> it's<00:45:07.740> just<00:45:07.859> kind<00:45:07.980> of<00:45:08.099> Simplicity<00:45:08.520> but<00:45:09.180> it's 00:45:09.410 --> 00:45:09.420 align:start position:0% or it's just kind of Simplicity but it's 00:45:09.420 --> 00:45:11.329 align:start position:0% or it's just kind of Simplicity but it's like<00:45:09.599> it<00:45:10.079> takes<00:45:10.319> a<00:45:10.440> while<00:45:10.560> to<00:45:10.800> get<00:45:10.980> there<00:45:11.099> right 00:45:11.329 --> 00:45:11.339 align:start position:0% like it takes a while to get there right 00:45:11.339 --> 00:45:15.290 align:start position:0% like it takes a while to get there right so<00:45:11.839> erc4337<00:45:12.839> it<00:45:13.380> works<00:45:13.740> through<00:45:14.040> in<00:45:14.819> Mev 00:45:15.290 --> 00:45:15.300 align:start position:0% so erc4337 it works through in Mev 00:45:15.300 --> 00:45:18.050 align:start position:0% so erc4337 it works through in Mev ecosystem<00:45:15.720> so<00:45:16.140> it<00:45:16.319> kind<00:45:16.500> of<00:45:16.619> Acts<00:45:17.280> makes<00:45:17.579> it<00:45:17.819> it 00:45:18.050 --> 00:45:18.060 align:start position:0% ecosystem so it kind of Acts makes it it 00:45:18.060 --> 00:45:19.609 align:start position:0% ecosystem so it kind of Acts makes it it relies<00:45:18.480> on<00:45:18.660> Builders<00:45:19.260> to<00:45:19.380> access 00:45:19.609 --> 00:45:19.619 align:start position:0% relies on Builders to access 00:45:19.619 --> 00:45:21.170 align:start position:0% relies on Builders to access intermediate<00:45:20.280> areas<00:45:20.520> and<00:45:20.700> then<00:45:20.819> you<00:45:20.940> know<00:45:21.060> the 00:45:21.170 --> 00:45:21.180 align:start position:0% intermediate areas and then you know the 00:45:21.180 --> 00:45:23.630 align:start position:0% intermediate areas and then you know the goal<00:45:21.480> of<00:45:21.599> uh<00:45:21.839> the<00:45:22.500> the<00:45:22.980> various<00:45:23.339> kind<00:45:23.579> of 00:45:23.630 --> 00:45:23.640 align:start position:0% goal of uh the the various kind of 00:45:23.640 --> 00:45:25.190 align:start position:0% goal of uh the the various kind of longer<00:45:23.940> term<00:45:24.060> EIP<00:45:24.480> is<00:45:24.720> just<00:45:24.839> to<00:45:24.960> kind<00:45:25.079> of 00:45:25.190 --> 00:45:25.200 align:start position:0% longer term EIP is just to kind of 00:45:25.200 --> 00:45:26.630 align:start position:0% longer term EIP is just to kind of constricts<00:45:25.680> that<00:45:25.800> more<00:45:25.980> and<00:45:26.220> sort<00:45:26.579> of 00:45:26.630 --> 00:45:26.640 align:start position:0% constricts that more and sort of 00:45:26.640 --> 00:45:28.970 align:start position:0% constricts that more and sort of protocolize<00:45:27.240> that<00:45:27.480> I<00:45:28.079> mean<00:45:28.319> more<00:45:28.740> and<00:45:28.859> more 00:45:28.970 --> 00:45:28.980 align:start position:0% protocolize that I mean more and more 00:45:28.980 --> 00:45:30.589 align:start position:0% protocolize that I mean more and more over<00:45:29.160> time 00:45:30.589 --> 00:45:30.599 align:start position:0% over time 00:45:30.599 --> 00:45:33.349 align:start position:0% over time so<00:45:31.260> we<00:45:31.619> are<00:45:31.920> okay<00:45:32.339> five<00:45:32.700> minutes<00:45:32.819> we're<00:45:33.180> gonna 00:45:33.349 --> 00:45:33.359 align:start position:0% so we are okay five minutes we're gonna 00:45:33.359 --> 00:45:35.210 align:start position:0% so we are okay five minutes we're gonna try<00:45:33.660> and<00:45:33.780> find<00:45:33.960> some<00:45:34.380> time<00:45:34.500> for<00:45:34.680> questions<00:45:34.859> so 00:45:35.210 --> 00:45:35.220 align:start position:0% try and find some time for questions so 00:45:35.220 --> 00:45:36.710 align:start position:0% try and find some time for questions so if<00:45:35.400> you<00:45:35.520> have<00:45:35.640> questions<00:45:35.819> start<00:45:36.300> thinking<00:45:36.599> of 00:45:36.710 --> 00:45:36.720 align:start position:0% if you have questions start thinking of 00:45:36.720 --> 00:45:39.170 align:start position:0% if you have questions start thinking of them<00:45:36.839> now<00:45:37.079> but<00:45:37.980> um<00:45:38.040> as<00:45:38.460> we<00:45:38.579> wrap<00:45:38.819> this<00:45:38.940> up<00:45:39.060> I 00:45:39.170 --> 00:45:39.180 align:start position:0% them now but um as we wrap this up I 00:45:39.180 --> 00:45:40.849 align:start position:0% them now but um as we wrap this up I wanted<00:45:39.300> to<00:45:39.480> do<00:45:39.540> some<00:45:39.660> call<00:45:39.839> to<00:45:39.960> actions<00:45:40.380> and 00:45:40.849 --> 00:45:40.859 align:start position:0% wanted to do some call to actions and 00:45:40.859 --> 00:45:42.650 align:start position:0% wanted to do some call to actions and there's<00:45:41.040> a<00:45:41.220> very<00:45:41.339> various<00:45:41.700> different<00:45:41.940> like<00:45:42.240> uh 00:45:42.650 --> 00:45:42.660 align:start position:0% there's a very various different like uh 00:45:42.660 --> 00:45:45.109 align:start position:0% there's a very various different like uh stakeholders<00:45:43.319> in<00:45:43.740> this<00:45:43.980> uh<00:45:44.220> in<00:45:44.460> the<00:45:44.760> world<00:45:44.940> of 00:45:45.109 --> 00:45:45.119 align:start position:0% stakeholders in this uh in the world of 00:45:45.119 --> 00:45:47.210 align:start position:0% stakeholders in this uh in the world of account<00:45:45.240> extraction<00:45:45.720> we<00:45:46.020> got<00:45:46.200> core<00:45:46.680> devs 00:45:47.210 --> 00:45:47.220 align:start position:0% account extraction we got core devs 00:45:47.220 --> 00:45:49.130 align:start position:0% account extraction we got core devs application<00:45:47.819> devs<00:45:48.240> layer<00:45:48.599> two<00:45:48.660> teams<00:45:48.960> and 00:45:49.130 --> 00:45:49.140 align:start position:0% application devs layer two teams and 00:45:49.140 --> 00:45:50.750 align:start position:0% application devs layer two teams and users<00:45:49.500> each<00:45:49.980> of<00:45:50.099> these<00:45:50.280> people<00:45:50.400> have<00:45:50.579> their 00:45:50.750 --> 00:45:50.760 align:start position:0% users each of these people have their 00:45:50.760 --> 00:45:52.130 align:start position:0% users each of these people have their own<00:45:50.880> sort<00:45:51.060> of<00:45:51.119> responsibility<00:45:51.599> for<00:45:51.900> getting 00:45:52.130 --> 00:45:52.140 align:start position:0% own sort of responsibility for getting 00:45:52.140 --> 00:45:54.950 align:start position:0% own sort of responsibility for getting account<00:45:52.920> extraction<00:45:53.400> out<00:45:53.640> into<00:45:53.819> the<00:45:54.060> world 00:45:54.950 --> 00:45:54.960 align:start position:0% account extraction out into the world 00:45:54.960 --> 00:45:57.290 align:start position:0% account extraction out into the world um<00:45:55.079> so<00:45:55.500> uh<00:45:56.220> let's<00:45:56.400> start<00:45:56.520> with<00:45:56.640> the<00:45:56.700> core<00:45:56.940> devs 00:45:57.290 --> 00:45:57.300 align:start position:0% um so uh let's start with the core devs 00:45:57.300 --> 00:45:59.150 align:start position:0% um so uh let's start with the core devs what<00:45:57.420> do<00:45:57.540> the<00:45:57.599> core<00:45:57.720> devs<00:45:58.079> need<00:45:58.200> to<00:45:58.319> do<00:45:58.440> to<00:45:59.040> get 00:45:59.150 --> 00:45:59.160 align:start position:0% what do the core devs need to do to get 00:45:59.160 --> 00:46:00.890 align:start position:0% what do the core devs need to do to get abstraction<00:46:00.119> done<00:46:00.359> what<00:46:00.480> do<00:46:00.599> they<00:46:00.720> need<00:46:00.839> to 00:46:00.890 --> 00:46:00.900 align:start position:0% abstraction done what do they need to 00:46:00.900 --> 00:46:02.450 align:start position:0% abstraction done what do they need to pay<00:46:01.020> attention<00:46:01.319> to<00:46:01.500> we<00:46:01.859> talk<00:46:02.040> I'll<00:46:02.220> throw<00:46:02.339> that 00:46:02.450 --> 00:46:02.460 align:start position:0% pay attention to we talk I'll throw that 00:46:02.460 --> 00:46:04.069 align:start position:0% pay attention to we talk I'll throw that one<00:46:02.579> to<00:46:02.700> you 00:46:04.069 --> 00:46:04.079 align:start position:0% one to you 00:46:04.079 --> 00:46:07.190 align:start position:0% one to you L1<00:46:04.859> core<00:46:05.160> devs<00:46:05.640> not<00:46:06.000> I<00:46:06.300> would<00:46:06.420> say<00:46:06.540> yeah<00:46:06.839> not 00:46:07.190 --> 00:46:07.200 align:start position:0% L1 core devs not I would say yeah not 00:46:07.200 --> 00:46:09.650 align:start position:0% L1 core devs not I would say yeah not much<00:46:07.319> yet<00:46:07.560> okay<00:46:08.099> um<00:46:08.099> L2<00:46:08.460> core<00:46:08.700> devs<00:46:09.119> I<00:46:09.240> think<00:46:09.660> um 00:46:09.650 --> 00:46:09.660 align:start position:0% much yet okay um L2 core devs I think um 00:46:09.660 --> 00:46:12.349 align:start position:0% much yet okay um L2 core devs I think um or<00:46:09.960> are<00:46:10.460> important<00:46:11.460> for<00:46:11.579> them<00:46:11.760> to<00:46:12.000> be<00:46:12.119> yeah 00:46:12.349 --> 00:46:12.359 align:start position:0% or are important for them to be yeah 00:46:12.359 --> 00:46:14.089 align:start position:0% or are important for them to be yeah kind<00:46:12.660> of<00:46:12.720> on<00:46:12.839> the<00:46:13.020> ball<00:46:13.140> earlier<00:46:13.560> because<00:46:13.800> I 00:46:14.089 --> 00:46:14.099 align:start position:0% kind of on the ball earlier because I 00:46:14.099 --> 00:46:14.829 align:start position:0% kind of on the ball earlier because I think 00:46:14.829 --> 00:46:14.839 align:start position:0% think 00:46:14.839 --> 00:46:18.109 align:start position:0% think there's<00:46:15.839> a<00:46:16.020> lot<00:46:16.140> of<00:46:16.260> reasons<00:46:16.680> why<00:46:16.980> l2s<00:46:17.640> are<00:46:17.940> a 00:46:18.109 --> 00:46:18.119 align:start position:0% there's a lot of reasons why l2s are a 00:46:18.119 --> 00:46:21.290 align:start position:0% there's a lot of reasons why l2s are a very<00:46:18.480> natural<00:46:18.839> uh<00:46:19.500> kind<00:46:19.680> of<00:46:19.800> uh<00:46:20.300> testing 00:46:21.290 --> 00:46:21.300 align:start position:0% very natural uh kind of uh testing 00:46:21.300 --> 00:46:23.089 align:start position:0% very natural uh kind of uh testing ground<00:46:21.420> for<00:46:21.720> account<00:46:21.900> obstruction<00:46:22.440> I<00:46:22.920> mean 00:46:23.089 --> 00:46:23.099 align:start position:0% ground for account obstruction I mean 00:46:23.099 --> 00:46:24.410 align:start position:0% ground for account obstruction I mean first<00:46:23.460> uh 00:46:24.410 --> 00:46:24.420 align:start position:0% first uh 00:46:24.420 --> 00:46:27.470 align:start position:0% first uh because<00:46:25.079> uh<00:46:25.500> later<00:46:25.760> look<00:46:26.760> there's<00:46:27.000> just<00:46:27.240> lower 00:46:27.470 --> 00:46:27.480 align:start position:0% because uh later look there's just lower 00:46:27.480 --> 00:46:30.290 align:start position:0% because uh later look there's just lower fees<00:46:27.839> on<00:46:27.960> layer<00:46:28.319> twos<00:46:28.560> and<00:46:29.339> lower<00:46:29.700> two<00:46:30.000> fees 00:46:30.290 --> 00:46:30.300 align:start position:0% fees on layer twos and lower two fees 00:46:30.300 --> 00:46:32.450 align:start position:0% fees on layer twos and lower two fees especially<00:46:30.660> for<00:46:30.900> computation<00:46:31.380> right<00:46:31.920> so<00:46:32.160> the 00:46:32.450 --> 00:46:32.460 align:start position:0% especially for computation right so the 00:46:32.460 --> 00:46:34.609 align:start position:0% especially for computation right so the overhead<00:46:33.060> of<00:46:33.300> accountable<00:46:34.200> to<00:46:34.380> action 00:46:34.609 --> 00:46:34.619 align:start position:0% overhead of accountable to action 00:46:34.619 --> 00:46:36.650 align:start position:0% overhead of accountable to action matters<00:46:34.980> was<00:46:35.220> they<00:46:35.700> can<00:46:35.880> iterate<00:46:36.359> and<00:46:36.540> they 00:46:36.650 --> 00:46:36.660 align:start position:0% matters was they can iterate and they 00:46:36.660 --> 00:46:38.809 align:start position:0% matters was they can iterate and they can<00:46:36.980> develop<00:46:37.980> and<00:46:38.160> build<00:46:38.339> a<00:46:38.520> lot<00:46:38.579> of<00:46:38.700> things 00:46:38.809 --> 00:46:38.819 align:start position:0% can develop and build a lot of things 00:46:38.819 --> 00:46:41.450 align:start position:0% can develop and build a lot of things more<00:46:39.119> quickly<00:46:39.500> also<00:46:40.500> one<00:46:41.040> thing<00:46:41.160> we<00:46:41.280> didn't 00:46:41.450 --> 00:46:41.460 align:start position:0% more quickly also one thing we didn't 00:46:41.460 --> 00:46:43.910 align:start position:0% more quickly also one thing we didn't touch<00:46:41.640> on<00:46:41.819> this<00:46:42.000> panel<00:46:42.300> yet<00:46:42.480> is<00:46:42.599> that<00:46:43.200> um<00:46:43.200> eap4 00:46:43.910 --> 00:46:43.920 align:start position:0% touch on this panel yet is that um eap4 00:46:43.920 --> 00:46:46.430 align:start position:0% touch on this panel yet is that um eap4 or<00:46:44.240> erc4337<00:46:45.240> has<00:46:45.540> this<00:46:45.780> some<00:46:45.960> aggregation 00:46:46.430 --> 00:46:46.440 align:start position:0% or erc4337 has this some aggregation 00:46:46.440 --> 00:46:49.190 align:start position:0% or erc4337 has this some aggregation feature<00:46:46.859> in<00:46:47.040> it<00:46:47.160> which<00:46:47.400> allows<00:46:48.200> basically 00:46:49.190 --> 00:46:49.200 align:start position:0% feature in it which allows basically 00:46:49.200 --> 00:46:50.930 align:start position:0% feature in it which allows basically different<00:46:49.500> uh<00:46:49.800> signatures<00:46:50.339> of<00:46:50.579> different 00:46:50.930 --> 00:46:50.940 align:start position:0% different uh signatures of different 00:46:50.940 --> 00:46:52.670 align:start position:0% different uh signatures of different transactions<00:46:51.599> to<00:46:51.839> get<00:46:51.960> aggregated<00:46:52.380> together 00:46:52.670 --> 00:46:52.680 align:start position:0% transactions to get aggregated together 00:46:52.680 --> 00:46:54.890 align:start position:0% transactions to get aggregated together into<00:46:52.920> one<00:46:53.220> it's<00:46:53.760> the 00:46:54.890 --> 00:46:54.900 align:start position:0% into one it's the 00:46:54.900 --> 00:46:56.930 align:start position:0% into one it's the same<00:46:55.560> sort<00:46:55.740> of<00:46:55.859> stuff<00:46:56.040> as<00:46:56.220> the<00:46:56.460> aggregation 00:46:56.930 --> 00:46:56.940 align:start position:0% same sort of stuff as the aggregation 00:46:56.940 --> 00:47:01.010 align:start position:0% same sort of stuff as the aggregation technology<00:46:57.839> that<00:46:58.319> powers<00:46:59.099> the<00:46:59.520> if<00:47:00.300> the<00:47:00.839> yeah 00:47:01.010 --> 00:47:01.020 align:start position:0% technology that powers the if the yeah 00:47:01.020 --> 00:47:02.870 align:start position:0% technology that powers the if the yeah ethereum<00:47:01.500> a<00:47:01.800> beacon<00:47:02.040> chain<00:47:02.160> and<00:47:02.400> that<00:47:02.579> allows 00:47:02.870 --> 00:47:02.880 align:start position:0% ethereum a beacon chain and that allows 00:47:02.880 --> 00:47:04.970 align:start position:0% ethereum a beacon chain and that allows so<00:47:03.060> many<00:47:03.240> validators<00:47:03.839> to<00:47:04.140> make<00:47:04.740> their 00:47:04.970 --> 00:47:04.980 align:start position:0% so many validators to make their 00:47:04.980 --> 00:47:06.650 align:start position:0% so many validators to make their attestations<00:47:05.460> and<00:47:05.760> for<00:47:05.940> those<00:47:06.060> attestations 00:47:06.650 --> 00:47:06.660 align:start position:0% attestations and for those attestations 00:47:06.660 --> 00:47:08.750 align:start position:0% attestations and for those attestations to<00:47:07.020> be<00:47:07.140> kind<00:47:07.680> of<00:47:07.740> packaged<00:47:08.099> together<00:47:08.220> into<00:47:08.520> one 00:47:08.750 --> 00:47:08.760 align:start position:0% to be kind of packaged together into one 00:47:08.760 --> 00:47:10.190 align:start position:0% to be kind of packaged together into one world<00:47:09.000> thing<00:47:09.240> that<00:47:09.420> can<00:47:09.480> be<00:47:09.599> verified<00:47:09.839> very 00:47:10.190 --> 00:47:10.200 align:start position:0% world thing that can be verified very 00:47:10.200 --> 00:47:13.190 align:start position:0% world thing that can be verified very quickly<00:47:10.640> and<00:47:11.640> that's<00:47:12.300> important<00:47:12.660> like<00:47:12.839> that's 00:47:13.190 --> 00:47:13.200 align:start position:0% quickly and that's important like that's 00:47:13.200 --> 00:47:14.809 align:start position:0% quickly and that's important like that's super<00:47:13.680> important<00:47:13.859> lawyer<00:47:14.460> too<00:47:14.579> is<00:47:14.700> right 00:47:14.809 --> 00:47:14.819 align:start position:0% super important lawyer too is right 00:47:14.819 --> 00:47:16.190 align:start position:0% super important lawyer too is right because<00:47:14.940> some<00:47:15.180> lawyer<00:47:15.420> two<00:47:15.599> is<00:47:15.780> computation 00:47:16.190 --> 00:47:16.200 align:start position:0% because some lawyer two is computation 00:47:16.200 --> 00:47:18.410 align:start position:0% because some lawyer two is computation is<00:47:16.560> or<00:47:16.859> data<00:47:17.400> is<00:47:17.520> even<00:47:17.700> more<00:47:17.819> expensive<00:47:18.180> than 00:47:18.410 --> 00:47:18.420 align:start position:0% is or data is even more expensive than 00:47:18.420 --> 00:47:20.089 align:start position:0% is or data is even more expensive than computation<00:47:18.900> and<00:47:19.140> aggregation<00:47:19.560> like<00:47:19.920> really 00:47:20.089 --> 00:47:20.099 align:start position:0% computation and aggregation like really 00:47:20.099 --> 00:47:23.510 align:start position:0% computation and aggregation like really yeah<00:47:20.400> saves<00:47:21.119> on<00:47:21.240> data<00:47:21.599> right<00:47:21.960> and<00:47:22.619> so<00:47:22.980> for 00:47:23.510 --> 00:47:23.520 align:start position:0% yeah saves on data right and so for 00:47:23.520 --> 00:47:25.309 align:start position:0% yeah saves on data right and so for those<00:47:23.700> reasons<00:47:24.180> that<00:47:24.359> local<00:47:24.599> leader<00:47:24.960> tours 00:47:25.309 --> 00:47:25.319 align:start position:0% those reasons that local leader tours 00:47:25.319 --> 00:47:27.170 align:start position:0% those reasons that local leader tours are<00:47:25.500> an<00:47:25.920> even<00:47:26.040> more<00:47:26.280> natural<00:47:26.520> kind<00:47:26.940> of<00:47:27.000> first 00:47:27.170 --> 00:47:27.180 align:start position:0% are an even more natural kind of first 00:47:27.180 --> 00:47:28.990 align:start position:0% are an even more natural kind of first use<00:47:27.359> case<00:47:27.599> for<00:47:28.140> um 00:47:28.990 --> 00:47:29.000 align:start position:0% use case for um 00:47:29.000 --> 00:47:31.849 align:start position:0% use case for um abstraction<00:47:30.000> and<00:47:30.420> then<00:47:30.660> layer<00:47:31.200> ones<00:47:31.500> and 00:47:31.849 --> 00:47:31.859 align:start position:0% abstraction and then layer ones and 00:47:31.859 --> 00:47:33.890 align:start position:0% abstraction and then layer ones and there's<00:47:32.640> a<00:47:32.819> lot<00:47:32.940> that<00:47:33.060> we<00:47:33.240> were<00:47:33.300> tools<00:47:33.599> can<00:47:33.720> do 00:47:33.890 --> 00:47:33.900 align:start position:0% there's a lot that we were tools can do 00:47:33.900 --> 00:47:35.450 align:start position:0% there's a lot that we were tools can do right<00:47:34.079> like<00:47:34.200> Layer<00:47:34.560> Two<00:47:34.680> is<00:47:34.859> right<00:47:35.099> you<00:47:35.400> know 00:47:35.450 --> 00:47:35.460 align:start position:0% right like Layer Two is right you know 00:47:35.460 --> 00:47:37.250 align:start position:0% right like Layer Two is right you know they<00:47:35.819> run<00:47:36.000> sequencers<00:47:36.599> and<00:47:36.839> they're<00:47:36.960> in<00:47:37.140> the 00:47:37.250 --> 00:47:37.260 align:start position:0% they run sequencers and they're in the 00:47:37.260 --> 00:47:38.510 align:start position:0% they run sequencers and they're in the process<00:47:37.500> of<00:47:37.740> figuring<00:47:38.040> out<00:47:38.220> how<00:47:38.339> to 00:47:38.510 --> 00:47:38.520 align:start position:0% process of figuring out how to 00:47:38.520 --> 00:47:41.150 align:start position:0% process of figuring out how to decentralize<00:47:39.300> those<00:47:39.480> sequencers<00:47:40.079> and<00:47:40.859> as 00:47:41.150 --> 00:47:41.160 align:start position:0% decentralize those sequencers and as 00:47:41.160 --> 00:47:43.670 align:start position:0% decentralize those sequencers and as part<00:47:41.339> of<00:47:41.520> those<00:47:41.700> processes<00:47:42.359> making<00:47:42.780> their 00:47:43.670 --> 00:47:43.680 align:start position:0% part of those processes making their 00:47:43.680 --> 00:47:46.790 align:start position:0% part of those processes making their leaders<00:47:44.339> support<00:47:45.180> account<00:47:45.839> abstraction<00:47:46.500> and 00:47:46.790 --> 00:47:46.800 align:start position:0% leaders support account abstraction and 00:47:46.800 --> 00:47:48.829 align:start position:0% leaders support account abstraction and are<00:47:47.220> accounts<00:47:47.640> abstracted<00:47:48.180> transactions<00:47:48.660> and 00:47:48.829 --> 00:47:48.839 align:start position:0% are accounts abstracted transactions and 00:47:48.839 --> 00:47:51.589 align:start position:0% are accounts abstracted transactions and accounts<00:47:49.260> natively<00:47:49.680> is<00:47:50.400> something<00:47:50.940> that's<00:47:51.300> uh 00:47:51.589 --> 00:47:51.599 align:start position:0% accounts natively is something that's uh 00:47:51.599 --> 00:47:54.589 align:start position:0% accounts natively is something that's uh really<00:47:51.780> important<00:47:52.140> right<00:47:52.579> so<00:47:53.579> and<00:47:54.300> then<00:47:54.420> in 00:47:54.589 --> 00:47:54.599 align:start position:0% really important right so and then in 00:47:54.599 --> 00:47:56.990 align:start position:0% really important right so and then in the<00:47:54.720> one<00:47:54.839> longer<00:47:55.440> term<00:47:55.619> once<00:47:56.099> the<00:47:56.160> Asia<00:47:56.579> layer 00:47:56.990 --> 00:47:57.000 align:start position:0% the one longer term once the Asia layer 00:47:57.000 --> 00:47:59.569 align:start position:0% the one longer term once the Asia layer 1<00:47:57.119> EIP<00:47:57.720> has<00:47:58.079> started<00:47:58.440> coming<00:47:58.619> in<00:47:58.800> then<00:47:59.040> mineral 00:47:59.569 --> 00:47:59.579 align:start position:0% 1 EIP has started coming in then mineral 00:47:59.579 --> 00:48:01.730 align:start position:0% 1 EIP has started coming in then mineral core<00:47:59.700> developers<00:48:00.200> need<00:48:01.200> to<00:48:01.319> start<00:48:01.500> paying 00:48:01.730 --> 00:48:01.740 align:start position:0% core developers need to start paying 00:48:01.740 --> 00:48:03.410 align:start position:0% core developers need to start paying more<00:48:01.800> and<00:48:01.920> more<00:48:02.099> attention<00:48:02.339> to<00:48:02.579> it 00:48:03.410 --> 00:48:03.420 align:start position:0% more and more attention to it 00:48:03.420 --> 00:48:05.510 align:start position:0% more and more attention to it Matt<00:48:03.900> what's<00:48:04.140> your<00:48:04.440> big<00:48:04.560> call<00:48:04.980> to<00:48:05.160> action<00:48:05.339> to 00:48:05.510 --> 00:48:05.520 align:start position:0% Matt what's your big call to action to 00:48:05.520 --> 00:48:07.130 align:start position:0% Matt what's your big call to action to the<00:48:05.700> world<00:48:05.760> what<00:48:06.060> do<00:48:06.180> we<00:48:06.300> need<00:48:06.480> to<00:48:06.599> do<00:48:06.720> to<00:48:06.960> move 00:48:07.130 --> 00:48:07.140 align:start position:0% the world what do we need to do to move 00:48:07.140 --> 00:48:08.750 align:start position:0% the world what do we need to do to move the<00:48:07.319> needle<00:48:07.560> forward<00:48:07.680> on<00:48:07.920> this<00:48:08.040> one 00:48:08.750 --> 00:48:08.760 align:start position:0% the needle forward on this one 00:48:08.760 --> 00:48:09.829 align:start position:0% the needle forward on this one um<00:48:08.819> there's<00:48:08.940> two<00:48:09.180> things<00:48:09.359> I<00:48:09.540> would<00:48:09.660> really 00:48:09.829 --> 00:48:09.839 align:start position:0% um there's two things I would really 00:48:09.839 --> 00:48:12.230 align:start position:0% um there's two things I would really like<00:48:09.960> to<00:48:10.140> see<00:48:10.380> my<00:48:11.040> colleague<00:48:11.400> Sam<00:48:11.640> Wilson<00:48:11.880> has 00:48:12.230 --> 00:48:12.240 align:start position:0% like to see my colleague Sam Wilson has 00:48:12.240 --> 00:48:15.349 align:start position:0% like to see my colleague Sam Wilson has started<00:48:12.599> a<00:48:13.460> bi-monthly<00:48:14.460> call<00:48:14.700> called<00:48:15.060> all 00:48:15.349 --> 00:48:15.359 align:start position:0% started a bi-monthly call called all 00:48:15.359 --> 00:48:17.930 align:start position:0% started a bi-monthly call called all wallet<00:48:15.780> devs<00:48:16.200> I<00:48:16.800> think<00:48:16.980> that<00:48:17.339> if<00:48:17.700> wall 00:48:17.930 --> 00:48:17.940 align:start position:0% wallet devs I think that if wall 00:48:17.940 --> 00:48:20.089 align:start position:0% wallet devs I think that if wall developers<00:48:18.599> are<00:48:18.780> not<00:48:18.960> aware<00:48:19.200> of<00:48:19.380> it<00:48:19.560> it's<00:48:19.740> an 00:48:20.089 --> 00:48:20.099 align:start position:0% developers are not aware of it it's an 00:48:20.099 --> 00:48:23.530 align:start position:0% developers are not aware of it it's an awesome<00:48:20.280> thing<00:48:20.579> to<00:48:20.940> to<00:48:21.300> see<00:48:21.900> what<00:48:22.440> the<00:48:22.920> current 00:48:23.530 --> 00:48:23.540 align:start position:0% awesome thing to to see what the current 00:48:23.540 --> 00:48:25.849 align:start position:0% awesome thing to to see what the current discussions<00:48:24.540> around<00:48:24.780> improving<00:48:25.380> wallets<00:48:25.680> are 00:48:25.849 --> 00:48:25.859 align:start position:0% discussions around improving wallets are 00:48:25.859 --> 00:48:27.230 align:start position:0% discussions around improving wallets are and<00:48:25.980> account<00:48:26.099> abstraction<00:48:26.520> is<00:48:26.760> obviously<00:48:27.060> one 00:48:27.230 --> 00:48:27.240 align:start position:0% and account abstraction is obviously one 00:48:27.240 --> 00:48:29.089 align:start position:0% and account abstraction is obviously one of<00:48:27.359> them<00:48:27.480> and<00:48:27.960> I<00:48:28.140> think<00:48:28.260> the<00:48:28.380> second<00:48:28.560> thing<00:48:28.800> is 00:48:29.089 --> 00:48:29.099 align:start position:0% of them and I think the second thing is 00:48:29.099 --> 00:48:30.710 align:start position:0% of them and I think the second thing is something<00:48:29.280> that<00:48:29.520> we<00:48:29.579> can<00:48:29.700> be<00:48:29.819> doing<00:48:29.940> today<00:48:30.240> to 00:48:30.710 --> 00:48:30.720 align:start position:0% something that we can be doing today to 00:48:30.720 --> 00:48:34.250 align:start position:0% something that we can be doing today to improve<00:48:31.700> the<00:48:32.700> user<00:48:33.060> experience<00:48:33.420> of<00:48:33.660> dapps<00:48:34.079> is 00:48:34.250 --> 00:48:34.260 align:start position:0% improve the user experience of dapps is 00:48:34.260 --> 00:48:35.930 align:start position:0% improve the user experience of dapps is this<00:48:34.440> is<00:48:34.500> like<00:48:34.680> creating<00:48:35.099> a<00:48:35.280> new<00:48:35.400> interface 00:48:35.930 --> 00:48:35.940 align:start position:0% this is like creating a new interface 00:48:35.940 --> 00:48:38.630 align:start position:0% this is like creating a new interface for<00:48:36.540> adapt<00:48:37.140> developers<00:48:37.619> to<00:48:37.920> Define<00:48:38.160> that 00:48:38.630 --> 00:48:38.640 align:start position:0% for adapt developers to Define that 00:48:38.640 --> 00:48:40.609 align:start position:0% for adapt developers to Define that they're<00:48:38.819> trying<00:48:39.000> to<00:48:39.180> do<00:48:39.480> a<00:48:40.260> batch<00:48:40.500> of 00:48:40.609 --> 00:48:40.619 align:start position:0% they're trying to do a batch of 00:48:40.619 --> 00:48:42.470 align:start position:0% they're trying to do a batch of operations<00:48:41.099> together<00:48:41.460> and<00:48:41.819> then<00:48:41.940> allowing 00:48:42.470 --> 00:48:42.480 align:start position:0% operations together and then allowing 00:48:42.480 --> 00:48:44.270 align:start position:0% operations together and then allowing the<00:48:43.020> wallet<00:48:43.319> on<00:48:43.500> the<00:48:43.619> back<00:48:43.680> end<00:48:43.800> to<00:48:44.040> decide 00:48:44.270 --> 00:48:44.280 align:start position:0% the wallet on the back end to decide 00:48:44.280 --> 00:48:45.650 align:start position:0% the wallet on the back end to decide whether<00:48:44.520> to<00:48:44.760> send<00:48:44.940> that<00:48:45.060> as<00:48:45.180> an<00:48:45.359> individual 00:48:45.650 --> 00:48:45.660 align:start position:0% whether to send that as an individual 00:48:45.660 --> 00:48:47.510 align:start position:0% whether to send that as an individual transaction<00:48:46.140> or<00:48:46.319> as<00:48:46.500> multiple<00:48:46.859> transactions 00:48:47.510 --> 00:48:47.520 align:start position:0% transaction or as multiple transactions 00:48:47.520 --> 00:48:49.490 align:start position:0% transaction or as multiple transactions I<00:48:48.000> think<00:48:48.119> if<00:48:48.359> we<00:48:48.480> do<00:48:48.660> that<00:48:48.839> then<00:48:49.020> we<00:48:49.260> start<00:48:49.380> to 00:48:49.490 --> 00:48:49.500 align:start position:0% I think if we do that then we start to 00:48:49.500 --> 00:48:51.410 align:start position:0% I think if we do that then we start to show<00:48:49.680> the<00:48:49.980> core<00:48:50.220> developers<00:48:50.760> that<00:48:51.119> we're 00:48:51.410 --> 00:48:51.420 align:start position:0% show the core developers that we're 00:48:51.420 --> 00:48:53.150 align:start position:0% show the core developers that we're really<00:48:51.720> serious<00:48:52.020> about<00:48:52.140> batch<00:48:52.500> transactions 00:48:53.150 --> 00:48:53.160 align:start position:0% really serious about batch transactions 00:48:53.160 --> 00:48:55.370 align:start position:0% really serious about batch transactions in<00:48:53.339> smart<00:48:53.520> contract<00:48:53.940> wallets<00:48:54.359> and<00:48:54.960> I<00:48:55.140> think 00:48:55.370 --> 00:48:55.380 align:start position:0% in smart contract wallets and I think 00:48:55.380 --> 00:48:57.589 align:start position:0% in smart contract wallets and I think that<00:48:55.500> that<00:48:55.619> will<00:48:55.800> really<00:48:56.040> improve<00:48:56.520> you<00:48:57.480> know 00:48:57.589 --> 00:48:57.599 align:start position:0% that that will really improve you know 00:48:57.599 --> 00:48:59.809 align:start position:0% that that will really improve you know their<00:48:58.020> feelings<00:48:58.859> about<00:48:59.099> changing<00:48:59.700> the 00:48:59.809 --> 00:48:59.819 align:start position:0% their feelings about changing the 00:48:59.819 --> 00:49:01.870 align:start position:0% their feelings about changing the protocol<00:49:00.119> to<00:49:01.020> support<00:49:01.140> that<00:49:01.500> type<00:49:01.680> of 00:49:01.870 --> 00:49:01.880 align:start position:0% protocol to support that type of 00:49:01.880 --> 00:49:04.550 align:start position:0% protocol to support that type of Technology<00:49:03.020> Julian<00:49:04.020> what's<00:49:04.200> your<00:49:04.319> big<00:49:04.440> call 00:49:04.550 --> 00:49:04.560 align:start position:0% Technology Julian what's your big call 00:49:04.560 --> 00:49:06.470 align:start position:0% Technology Julian what's your big call to<00:49:04.740> action<00:49:04.920> yeah<00:49:05.700> I<00:49:05.819> agree<00:49:06.060> with<00:49:06.119> that<00:49:06.180> I<00:49:06.359> was 00:49:06.470 --> 00:49:06.480 align:start position:0% to action yeah I agree with that I was 00:49:06.480 --> 00:49:08.329 align:start position:0% to action yeah I agree with that I was going<00:49:06.599> to<00:49:06.660> say<00:49:06.720> I<00:49:07.140> think<00:49:07.260> that<00:49:07.440> developers<00:49:07.980> as 00:49:08.329 --> 00:49:08.339 align:start position:0% going to say I think that developers as 00:49:08.339 --> 00:49:09.890 align:start position:0% going to say I think that developers as well<00:49:08.520> of<00:49:08.640> course<00:49:08.760> Leo<00:49:09.060> tools<00:49:09.420> I've<00:49:09.599> mentioned 00:49:09.890 --> 00:49:09.900 align:start position:0% well of course Leo tools I've mentioned 00:49:09.900 --> 00:49:11.510 align:start position:0% well of course Leo tools I've mentioned that<00:49:10.020> in<00:49:10.140> vitalik<00:49:10.560> mentioned<00:49:10.859> that<00:49:10.980> but<00:49:11.400> I 00:49:11.510 --> 00:49:11.520 align:start position:0% that in vitalik mentioned that but I 00:49:11.520 --> 00:49:13.849 align:start position:0% that in vitalik mentioned that but I think<00:49:11.640> that<00:49:11.819> developers<00:49:12.359> today<00:49:12.720> could<00:49:13.380> start 00:49:13.849 --> 00:49:13.859 align:start position:0% think that developers today could start 00:49:13.859 --> 00:49:16.250 align:start position:0% think that developers today could start to<00:49:14.099> embrace<00:49:14.460> patterns<00:49:14.940> like<00:49:15.000> EIP<00:49:15.300> 1271<00:49:16.020> just 00:49:16.250 --> 00:49:16.260 align:start position:0% to embrace patterns like EIP 1271 just 00:49:16.260 --> 00:49:18.290 align:start position:0% to embrace patterns like EIP 1271 just to<00:49:16.440> verify<00:49:16.859> option<00:49:17.280> signature<00:49:17.880> I<00:49:18.000> think<00:49:18.119> just 00:49:18.290 --> 00:49:18.300 align:start position:0% to verify option signature I think just 00:49:18.300 --> 00:49:20.569 align:start position:0% to verify option signature I think just making<00:49:18.540> sure<00:49:18.839> that<00:49:19.079> you<00:49:19.200> adapt<00:49:19.560> today<00:49:19.859> is 00:49:20.569 --> 00:49:20.579 align:start position:0% making sure that you adapt today is 00:49:20.579 --> 00:49:22.309 align:start position:0% making sure that you adapt today is compatible<00:49:21.000> with<00:49:21.300> smart<00:49:21.420> contract<00:49:21.839> wallet 00:49:22.309 --> 00:49:22.319 align:start position:0% compatible with smart contract wallet 00:49:22.319 --> 00:49:24.170 align:start position:0% compatible with smart contract wallet and<00:49:22.920> as<00:49:23.160> you<00:49:23.339> mentioned<00:49:23.520> we<00:49:23.700> can<00:49:23.819> extend<00:49:24.060> that 00:49:24.170 --> 00:49:24.180 align:start position:0% and as you mentioned we can extend that 00:49:24.180 --> 00:49:25.790 align:start position:0% and as you mentioned we can extend that to<00:49:24.359> multiple<00:49:24.780> but<00:49:24.960> I<00:49:25.079> think<00:49:25.260> that<00:49:25.440> would<00:49:25.560> that 00:49:25.790 --> 00:49:25.800 align:start position:0% to multiple but I think that would that 00:49:25.800 --> 00:49:27.950 align:start position:0% to multiple but I think that would that would<00:49:25.980> give<00:49:26.160> already<00:49:26.400> a<00:49:26.760> good<00:49:27.000> sign<00:49:27.240> and<00:49:27.839> that 00:49:27.950 --> 00:49:27.960 align:start position:0% would give already a good sign and that 00:49:27.960 --> 00:49:29.809 align:start position:0% would give already a good sign and that also<00:49:28.319> means<00:49:28.680> that 00:49:29.809 --> 00:49:29.819 align:start position:0% also means that 00:49:29.819 --> 00:49:31.210 align:start position:0% also means that if<00:49:30.359> you<00:49:30.540> know 00:49:31.210 --> 00:49:31.220 align:start position:0% if you know 00:49:31.220 --> 00:49:33.950 align:start position:0% if you know erc4337<00:49:32.220> picks<00:49:32.819> up<00:49:32.880> and<00:49:33.119> people<00:49:33.359> build<00:49:33.720> more 00:49:33.950 --> 00:49:33.960 align:start position:0% erc4337 picks up and people build more 00:49:33.960 --> 00:49:35.569 align:start position:0% erc4337 picks up and people build more and<00:49:34.140> more<00:49:34.260> wallet<00:49:34.619> on<00:49:34.800> top<00:49:34.920> of<00:49:35.040> that<00:49:35.160> they<00:49:35.460> will 00:49:35.569 --> 00:49:35.579 align:start position:0% and more wallet on top of that they will 00:49:35.579 --> 00:49:37.550 align:start position:0% and more wallet on top of that they will become<00:49:36.060> more<00:49:36.300> and<00:49:36.420> more<00:49:36.599> first<00:49:36.780> class<00:49:37.020> citizen 00:49:37.550 --> 00:49:37.560 align:start position:0% become more and more first class citizen 00:49:37.560 --> 00:49:40.370 align:start position:0% become more and more first class citizen even<00:49:37.980> on<00:49:38.220> L1<00:49:38.700> I<00:49:39.240> think<00:49:39.420> they've<00:49:39.780> never<00:49:39.960> reached 00:49:40.370 --> 00:49:40.380 align:start position:0% even on L1 I think they've never reached 00:49:40.380 --> 00:49:42.710 align:start position:0% even on L1 I think they've never reached the<00:49:40.500> point<00:49:40.740> of<00:49:40.859> having<00:49:41.160> full<00:49:41.700> first<00:49:41.940> one<00:49:42.180> first 00:49:42.710 --> 00:49:42.720 align:start position:0% the point of having full first one first 00:49:42.720 --> 00:49:44.450 align:start position:0% the point of having full first one first class<00:49:42.960> citizen<00:49:43.380> but<00:49:43.740> making<00:49:44.040> sure<00:49:44.220> every 00:49:44.450 --> 00:49:44.460 align:start position:0% class citizen but making sure every 00:49:44.460 --> 00:49:45.770 align:start position:0% class citizen but making sure every single<00:49:44.700> dab<00:49:44.940> is<00:49:45.119> compatible<00:49:45.420> with<00:49:45.599> smart 00:49:45.770 --> 00:49:45.780 align:start position:0% single dab is compatible with smart 00:49:45.780 --> 00:49:47.270 align:start position:0% single dab is compatible with smart contract<00:49:46.140> wallet<00:49:46.500> I<00:49:46.619> think<00:49:46.740> will<00:49:46.920> make<00:49:47.099> it 00:49:47.270 --> 00:49:47.280 align:start position:0% contract wallet I think will make it 00:49:47.280 --> 00:49:48.829 align:start position:0% contract wallet I think will make it easier<00:49:47.579> to<00:49:47.819> go<00:49:47.940> on<00:49:48.060> that<00:49:48.180> Journey<00:49:48.420> towards 00:49:48.829 --> 00:49:48.839 align:start position:0% easier to go on that Journey towards 00:49:48.839 --> 00:49:50.390 align:start position:0% easier to go on that Journey towards full<00:49:49.020> account<00:49:49.200> abstraction 00:49:50.390 --> 00:49:50.400 align:start position:0% full account abstraction 00:49:50.400 --> 00:49:52.430 align:start position:0% full account abstraction you'll<00:49:51.000> have<00:49:51.119> tickets<00:49:51.359> home<00:49:51.660> and<00:49:51.960> also<00:49:52.200> you 00:49:52.430 --> 00:49:52.440 align:start position:0% you'll have tickets home and also you 00:49:52.440 --> 00:49:53.930 align:start position:0% you'll have tickets home and also you have<00:49:52.680> is<00:49:52.859> the<00:49:53.040> uh<00:49:53.099> the<00:49:53.339> person<00:49:53.460> that<00:49:53.760> actually 00:49:53.930 --> 00:49:53.940 align:start position:0% have is the uh the person that actually 00:49:53.940 --> 00:49:56.510 align:start position:0% have is the uh the person that actually helped<00:49:54.480> educate<00:49:54.960> me<00:49:55.140> a<00:49:55.319> lot<00:49:55.440> on<00:49:55.800> uh<00:49:56.160> for<00:49:56.400> this 00:49:56.510 --> 00:49:56.520 align:start position:0% helped educate me a lot on uh for this 00:49:56.520 --> 00:49:57.589 align:start position:0% helped educate me a lot on uh for this panel<00:49:56.819> because<00:49:56.940> I<00:49:57.119> was<00:49:57.240> definitely<00:49:57.420> not 00:49:57.589 --> 00:49:57.599 align:start position:0% panel because I was definitely not 00:49:57.599 --> 00:49:59.569 align:start position:0% panel because I was definitely not prepared<00:49:57.900> more<00:49:58.079> than<00:49:58.200> a<00:49:58.319> week<00:49:58.440> ago<00:49:58.680> so<00:49:59.099> yoab 00:49:59.569 --> 00:49:59.579 align:start position:0% prepared more than a week ago so yoab 00:49:59.579 --> 00:50:01.490 align:start position:0% prepared more than a week ago so yoab thank<00:49:59.819> you<00:49:59.940> uh<00:50:00.240> for<00:50:00.420> your<00:50:00.540> help<00:50:00.720> what's<00:50:01.319> the 00:50:01.490 --> 00:50:01.500 align:start position:0% thank you uh for your help what's the 00:50:01.500 --> 00:50:03.109 align:start position:0% thank you uh for your help what's the big<00:50:01.619> call<00:50:01.800> to<00:50:01.980> action<00:50:02.160> that<00:50:02.339> you<00:50:02.520> have<00:50:02.640> uh<00:50:03.000> to 00:50:03.109 --> 00:50:03.119 align:start position:0% big call to action that you have uh to 00:50:03.119 --> 00:50:04.670 align:start position:0% big call to action that you have uh to how<00:50:03.240> we<00:50:03.420> get<00:50:03.540> account<00:50:03.839> abstraction<00:50:04.319> into<00:50:04.500> the 00:50:04.670 --> 00:50:04.680 align:start position:0% how we get account abstraction into the 00:50:04.680 --> 00:50:07.670 align:start position:0% how we get account abstraction into the hands<00:50:04.980> of<00:50:05.040> everyone<00:50:05.160> yeah<00:50:05.760> so<00:50:06.359> uh<00:50:06.839> so<00:50:07.560> the 00:50:07.670 --> 00:50:07.680 align:start position:0% hands of everyone yeah so uh so the 00:50:07.680 --> 00:50:09.530 align:start position:0% hands of everyone yeah so uh so the first<00:50:07.800> thing<00:50:07.980> is<00:50:08.160> what<00:50:08.640> everybody<00:50:09.060> here 00:50:09.530 --> 00:50:09.540 align:start position:0% first thing is what everybody here 00:50:09.540 --> 00:50:12.290 align:start position:0% first thing is what everybody here already<00:50:09.839> said<00:50:10.260> that<00:50:11.099> adapts<00:50:11.819> need<00:50:12.000> to<00:50:12.119> be 00:50:12.290 --> 00:50:12.300 align:start position:0% already said that adapts need to be 00:50:12.300 --> 00:50:14.150 align:start position:0% already said that adapts need to be compatible<00:50:12.839> with<00:50:13.079> it<00:50:13.260> and<00:50:13.440> not<00:50:13.619> get<00:50:13.859> in<00:50:14.040> the 00:50:14.150 --> 00:50:14.160 align:start position:0% compatible with it and not get in the 00:50:14.160 --> 00:50:18.230 align:start position:0% compatible with it and not get in the way<00:50:14.339> by<00:50:14.700> requiring<00:50:15.180> signatures<00:50:15.920> and<00:50:17.000> and<00:50:18.000> they 00:50:18.230 --> 00:50:18.240 align:start position:0% way by requiring signatures and and they 00:50:18.240 --> 00:50:20.210 align:start position:0% way by requiring signatures and and they can<00:50:18.420> start<00:50:18.599> thinking<00:50:18.960> about<00:50:19.140> ways<00:50:19.740> of<00:50:20.099> course 00:50:20.210 --> 00:50:20.220 align:start position:0% can start thinking about ways of course 00:50:20.220 --> 00:50:22.309 align:start position:0% can start thinking about ways of course batching<00:50:20.760> batching<00:50:21.300> has<00:50:21.540> met<00:50:21.780> already 00:50:22.309 --> 00:50:22.319 align:start position:0% batching batching has met already 00:50:22.319 --> 00:50:25.490 align:start position:0% batching batching has met already explained<00:50:22.980> but<00:50:23.220> even<00:50:23.819> Beyond<00:50:24.300> batching<00:50:24.839> start 00:50:25.490 --> 00:50:25.500 align:start position:0% explained but even Beyond batching start 00:50:25.500 --> 00:50:28.069 align:start position:0% explained but even Beyond batching start thinking<00:50:25.920> about<00:50:26.040> ways<00:50:26.819> in<00:50:27.300> which<00:50:27.480> a<00:50:27.780> contract 00:50:28.069 --> 00:50:28.079 align:start position:0% thinking about ways in which a contract 00:50:28.079 --> 00:50:30.230 align:start position:0% thinking about ways in which a contract wallet<00:50:28.500> could<00:50:28.680> improve<00:50:29.040> the<00:50:29.220> ux<00:50:29.579> of<00:50:29.819> your<00:50:30.000> way 00:50:30.230 --> 00:50:30.240 align:start position:0% wallet could improve the ux of your way 00:50:30.240 --> 00:50:32.690 align:start position:0% wallet could improve the ux of your way of<00:50:30.420> your<00:50:30.540> application<00:50:31.040> and<00:50:32.040> work<00:50:32.280> with<00:50:32.520> the 00:50:32.690 --> 00:50:32.700 align:start position:0% of your application and work with the 00:50:32.700 --> 00:50:35.630 align:start position:0% of your application and work with the wallet<00:50:33.119> developers<00:50:33.800> in<00:50:34.800> places<00:50:34.980> like<00:50:35.280> in 00:50:35.630 --> 00:50:35.640 align:start position:0% wallet developers in places like in 00:50:35.640 --> 00:50:38.530 align:start position:0% wallet developers in places like in places<00:50:35.819> like<00:50:36.060> all<00:50:36.420> wallet<00:50:36.839> Dev<00:50:37.040> the<00:50:38.040> Discord 00:50:38.530 --> 00:50:38.540 align:start position:0% places like all wallet Dev the Discord 00:50:38.540 --> 00:50:41.270 align:start position:0% places like all wallet Dev the Discord start<00:50:39.540> walking<00:50:39.839> with<00:50:40.260> the<00:50:40.380> world<00:50:40.619> developers 00:50:41.270 --> 00:50:41.280 align:start position:0% start walking with the world developers 00:50:41.280 --> 00:50:43.730 align:start position:0% start walking with the world developers to<00:50:42.060> add<00:50:42.240> the<00:50:42.480> features<00:50:42.900> that<00:50:43.260> to<00:50:43.560> other 00:50:43.730 --> 00:50:43.740 align:start position:0% to add the features that to other 00:50:43.740 --> 00:50:45.470 align:start position:0% to add the features that to other features<00:50:44.099> that<00:50:44.339> become<00:50:44.640> possible<00:50:45.000> with<00:50:45.300> this 00:50:45.470 --> 00:50:45.480 align:start position:0% features that become possible with this 00:50:45.480 --> 00:50:47.990 align:start position:0% features that become possible with this and<00:50:46.200> for<00:50:46.319> all<00:50:46.500> the<00:50:46.740> developers<00:50:47.160> to<00:50:47.819> start 00:50:47.990 --> 00:50:48.000 align:start position:0% and for all the developers to start 00:50:48.000 --> 00:50:50.329 align:start position:0% and for all the developers to start thinking<00:50:48.420> about<00:50:48.660> about 00:50:50.329 --> 00:50:50.339 align:start position:0% thinking about about 00:50:50.339 --> 00:50:52.790 align:start position:0% thinking about about interesting<00:50:51.240> ways<00:50:51.660> to<00:50:51.839> use<00:50:52.020> this<00:50:52.260> to<00:50:52.500> improve 00:50:52.790 --> 00:50:52.800 align:start position:0% interesting ways to use this to improve 00:50:52.800 --> 00:50:54.950 align:start position:0% interesting ways to use this to improve the<00:50:52.920> life<00:50:53.099> of<00:50:53.280> your<00:50:53.460> users<00:50:53.819> such<00:50:54.180> as<00:50:54.300> using<00:50:54.780> gas 00:50:54.950 --> 00:50:54.960 align:start position:0% the life of your users such as using gas 00:50:54.960 --> 00:50:58.190 align:start position:0% the life of your users such as using gas obstruction<00:50:55.380> models<00:50:56.160> maybe<00:50:57.000> you<00:50:57.780> know<00:50:57.839> allow 00:50:58.190 --> 00:50:58.200 align:start position:0% obstruction models maybe you know allow 00:50:58.200 --> 00:51:01.370 align:start position:0% obstruction models maybe you know allow users<00:50:58.619> to<00:50:59.359> allow<00:51:00.359> users<00:51:00.960> who<00:51:01.200> do 00:51:01.370 --> 00:51:01.380 align:start position:0% users to allow users who do 00:51:01.380 --> 00:51:04.190 align:start position:0% users to allow users who do non-financial<00:51:02.160> stuff<00:51:02.579> to<00:51:03.540> pay<00:51:03.660> with<00:51:03.839> a<00:51:04.020> credit 00:51:04.190 --> 00:51:04.200 align:start position:0% non-financial stuff to pay with a credit 00:51:04.200 --> 00:51:07.609 align:start position:0% non-financial stuff to pay with a credit card<00:51:04.500> and<00:51:04.800> not<00:51:04.980> buy<00:51:05.220> crypto<00:51:05.760> at<00:51:06.000> all<00:51:06.180> and<00:51:07.020> there 00:51:07.609 --> 00:51:07.619 align:start position:0% card and not buy crypto at all and there 00:51:07.619 --> 00:51:09.109 align:start position:0% card and not buy crypto at all and there are<00:51:07.740> many<00:51:07.800> things<00:51:07.980> that<00:51:08.220> the<00:51:08.400> wallet<00:51:08.700> could<00:51:08.940> be 00:51:09.109 --> 00:51:09.119 align:start position:0% are many things that the wallet could be 00:51:09.119 --> 00:51:11.569 align:start position:0% are many things that the wallet could be doing<00:51:09.359> using<00:51:10.079> account<00:51:10.260> obstruction<00:51:10.740> to<00:51:11.460> make 00:51:11.569 --> 00:51:11.579 align:start position:0% doing using account obstruction to make 00:51:11.579 --> 00:51:14.569 align:start position:0% doing using account obstruction to make the<00:51:11.760> user's<00:51:12.240> life<00:51:12.420> easier<00:51:13.140> so<00:51:13.920> start<00:51:14.220> thinking 00:51:14.569 --> 00:51:14.579 align:start position:0% the user's life easier so start thinking 00:51:14.579 --> 00:51:15.829 align:start position:0% the user's life easier so start thinking about<00:51:14.700> that 00:51:15.829 --> 00:51:15.839 align:start position:0% about that 00:51:15.839 --> 00:51:20.690 align:start position:0% about that and<00:51:16.680> there's<00:51:17.640> a<00:51:17.880> so<00:51:18.720> I<00:51:19.079> I<00:51:19.460> posted<00:51:20.460> a 00:51:20.690 --> 00:51:20.700 align:start position:0% and there's a so I I posted a 00:51:20.700 --> 00:51:23.630 align:start position:0% and there's a so I I posted a presentation<00:51:21.180> with<00:51:21.720> many<00:51:22.319> with<00:51:23.220> many<00:51:23.460> cool 00:51:23.630 --> 00:51:23.640 align:start position:0% presentation with many with many cool 00:51:23.640 --> 00:51:26.270 align:start position:0% presentation with many with many cool use<00:51:24.119> cases<00:51:24.420> that<00:51:24.720> you<00:51:24.900> could<00:51:25.020> build<00:51:25.200> using<00:51:25.680> it 00:51:26.270 --> 00:51:26.280 align:start position:0% use cases that you could build using it 00:51:26.280 --> 00:51:29.109 align:start position:0% use cases that you could build using it so<00:51:27.420> um<00:51:27.420> so<00:51:28.200> I<00:51:28.319> could 00:51:29.109 --> 00:51:29.119 align:start position:0% so um so I could 00:51:29.119 --> 00:51:31.849 align:start position:0% so um so I could so<00:51:30.119> I<00:51:30.180> think<00:51:30.359> going<00:51:30.780> through<00:51:31.020> this<00:51:31.319> list<00:51:31.559> and 00:51:31.849 --> 00:51:31.859 align:start position:0% so I think going through this list and 00:51:31.859 --> 00:51:33.710 align:start position:0% so I think going through this list and seeing<00:51:32.460> what<00:51:32.700> could<00:51:32.880> help<00:51:33.119> your<00:51:33.359> wallet 00:51:33.710 --> 00:51:33.720 align:start position:0% seeing what could help your wallet 00:51:33.720 --> 00:51:36.470 align:start position:0% seeing what could help your wallet become<00:51:34.020> better<00:51:34.280> maybe<00:51:35.280> interesting<00:51:35.819> and<00:51:36.359> I 00:51:36.470 --> 00:51:36.480 align:start position:0% become better maybe interesting and I 00:51:36.480 --> 00:51:38.870 align:start position:0% become better maybe interesting and I think<00:51:36.660> just<00:51:36.960> again<00:51:37.500> to<00:51:37.859> really<00:51:38.460> just<00:51:38.700> drive 00:51:38.870 --> 00:51:38.880 align:start position:0% think just again to really just drive 00:51:38.880 --> 00:51:40.730 align:start position:0% think just again to really just drive this<00:51:39.119> point<00:51:39.300> home<00:51:39.540> ethereum<00:51:40.079> is<00:51:40.260> a<00:51:40.380> technology 00:51:40.730 --> 00:51:40.740 align:start position:0% this point home ethereum is a technology 00:51:40.740 --> 00:51:44.150 align:start position:0% this point home ethereum is a technology that<00:51:41.339> is<00:51:41.700> working<00:51:41.880> on<00:51:42.119> expressing<00:51:42.599> itself<00:51:42.900> uh 00:51:44.150 --> 00:51:44.160 align:start position:0% that is working on expressing itself uh 00:51:44.160 --> 00:51:46.490 align:start position:0% that is working on expressing itself uh starting<00:51:44.520> in<00:51:44.819> 2015<00:51:45.180> it<00:51:45.599> was<00:51:45.720> limited<00:51:46.079> and<00:51:46.380> now 00:51:46.490 --> 00:51:46.500 align:start position:0% starting in 2015 it was limited and now 00:51:46.500 --> 00:51:47.870 align:start position:0% starting in 2015 it was limited and now we<00:51:46.619> have<00:51:46.740> proof<00:51:47.040> of<00:51:47.040> stake<00:51:47.280> now<00:51:47.400> we<00:51:47.520> have<00:51:47.640> layer 00:51:47.870 --> 00:51:47.880 align:start position:0% we have proof of stake now we have layer 00:51:47.880 --> 00:51:49.849 align:start position:0% we have proof of stake now we have layer twos<00:51:48.180> we<00:51:48.540> have<00:51:48.660> ethereum<00:51:49.140> can<00:51:49.319> express<00:51:49.440> itself 00:51:49.849 --> 00:51:49.859 align:start position:0% twos we have ethereum can express itself 00:51:49.859 --> 00:51:51.410 align:start position:0% twos we have ethereum can express itself a<00:51:50.040> little<00:51:50.099> bit<00:51:50.220> better<00:51:50.339> but<00:51:50.940> it's<00:51:51.119> not<00:51:51.300> going 00:51:51.410 --> 00:51:51.420 align:start position:0% a little bit better but it's not going 00:51:51.420 --> 00:51:53.410 align:start position:0% a little bit better but it's not going to<00:51:51.540> be<00:51:51.660> done<00:51:51.839> expressing<00:51:52.380> itself<00:51:52.680> until 00:51:53.410 --> 00:51:53.420 align:start position:0% to be done expressing itself until 00:51:53.420 --> 00:51:56.510 align:start position:0% to be done expressing itself until wallets<00:51:54.420> themselves<00:51:54.900> are<00:51:55.380> expressive<00:51:55.859> as<00:51:56.339> the 00:51:56.510 --> 00:51:56.520 align:start position:0% wallets themselves are expressive as the 00:51:56.520 --> 00:51:57.770 align:start position:0% wallets themselves are expressive as the Turing<00:51:56.819> complete<00:51:57.180> nature<00:51:57.359> of<00:51:57.420> ethereum 00:51:57.770 --> 00:51:57.780 align:start position:0% Turing complete nature of ethereum 00:51:57.780 --> 00:52:00.349 align:start position:0% Turing complete nature of ethereum itself<00:51:58.079> and<00:51:58.859> so<00:51:59.040> we<00:51:59.280> will<00:51:59.400> actually<00:51:59.579> not<00:51:59.819> see<00:52:00.119> a 00:52:00.349 --> 00:52:00.359 align:start position:0% itself and so we will actually not see a 00:52:00.359 --> 00:52:01.970 align:start position:0% itself and so we will actually not see a complete<00:52:00.660> ethereum<00:52:01.020> until<00:52:01.200> we<00:52:01.500> all<00:52:01.619> have 00:52:01.970 --> 00:52:01.980 align:start position:0% complete ethereum until we all have 00:52:01.980 --> 00:52:04.190 align:start position:0% complete ethereum until we all have Smart<00:52:02.400> contract<00:52:02.819> wallets<00:52:03.240> and<00:52:03.599> that<00:52:03.720> is<00:52:03.900> how<00:52:04.079> I 00:52:04.190 --> 00:52:04.200 align:start position:0% Smart contract wallets and that is how I 00:52:04.200 --> 00:52:05.750 align:start position:0% Smart contract wallets and that is how I will<00:52:04.380> finish<00:52:04.619> this<00:52:04.920> panel<00:52:05.160> panelists<00:52:05.640> thank 00:52:05.750 --> 00:52:05.760 align:start position:0% will finish this panel panelists thank 00:52:05.760 --> 00:52:07.309 align:start position:0% will finish this panel panelists thank you<00:52:05.819> so<00:52:05.940> much<00:52:06.059> for<00:52:06.420> helping<00:52:06.780> me<00:52:06.900> explore<00:52:07.079> this 00:52:07.309 --> 00:52:07.319 align:start position:0% you so much for helping me explore this 00:52:07.319 --> 00:52:09.390 align:start position:0% you so much for helping me explore this world 00:52:09.390 --> 00:52:09.400 align:start position:0% world 00:52:09.400 --> 00:52:11.710 align:start position:0% world [Applause] 00:52:11.710 --> 00:52:11.720 align:start position:0% [Applause] 00:52:11.720 --> 00:52:15.549 align:start position:0% [Applause] foreign 00:52:15.549 --> 00:52:15.559 align:start position:0% 00:52:15.559 --> 00:52:17.750 align:start position:0% I<00:52:16.559> assumed<00:52:16.859> that<00:52:16.920> we<00:52:17.040> actually<00:52:17.160> did<00:52:17.400> not<00:52:17.520> have 00:52:17.750 --> 00:52:17.760 align:start position:0% I assumed that we actually did not have 00:52:17.760 --> 00:52:19.250 align:start position:0% I assumed that we actually did not have time<00:52:17.880> for<00:52:18.059> questions<00:52:18.240> but<00:52:18.540> apparently<00:52:18.839> we<00:52:19.079> do 00:52:19.250 --> 00:52:19.260 align:start position:0% time for questions but apparently we do 00:52:19.260 --> 00:52:21.950 align:start position:0% time for questions but apparently we do so<00:52:19.920> I'm<00:52:20.579> gonna<00:52:20.700> let<00:52:20.940> somebody<00:52:21.180> else<00:52:21.480> Steward 00:52:21.950 --> 00:52:21.960 align:start position:0% so I'm gonna let somebody else Steward 00:52:21.960 --> 00:52:24.890 align:start position:0% so I'm gonna let somebody else Steward that<00:52:22.260> hey<00:52:23.220> thanks<00:52:23.579> I'm<00:52:24.059> just<00:52:24.180> wondering<00:52:24.540> when 00:52:24.890 --> 00:52:24.900 align:start position:0% that hey thanks I'm just wondering when 00:52:24.900 --> 00:52:28.130 align:start position:0% that hey thanks I'm just wondering when is<00:52:25.079> Arjun<00:52:25.559> planning<00:52:25.980> to<00:52:26.280> become<00:52:26.700> ERC<00:52:27.300> 437 00:52:28.130 --> 00:52:28.140 align:start position:0% is Arjun planning to become ERC 437 00:52:28.140 --> 00:52:30.470 align:start position:0% is Arjun planning to become ERC 437 compliance<00:52:29.220> I<00:52:29.520> guess<00:52:29.700> that's<00:52:29.880> a<00:52:30.000> question<00:52:30.180> for 00:52:30.470 --> 00:52:30.480 align:start position:0% compliance I guess that's a question for 00:52:30.480 --> 00:52:32.390 align:start position:0% compliance I guess that's a question for me 00:52:32.390 --> 00:52:32.400 align:start position:0% me 00:52:32.400 --> 00:52:34.430 align:start position:0% me so 00:52:34.430 --> 00:52:34.440 align:start position:0% so 00:52:34.440 --> 00:52:36.170 align:start position:0% so for<00:52:34.800> the<00:52:35.040> moment<00:52:35.220> we<00:52:35.579> something<00:52:35.940> that's 00:52:36.170 --> 00:52:36.180 align:start position:0% for the moment we something that's 00:52:36.180 --> 00:52:37.730 align:start position:0% for the moment we something that's something<00:52:36.420> that<00:52:36.599> we're<00:52:36.780> exploring<00:52:37.200> that<00:52:37.559> that 00:52:37.730 --> 00:52:37.740 align:start position:0% something that we're exploring that that 00:52:37.740 --> 00:52:40.130 align:start position:0% something that we're exploring that that we<00:52:37.980> want<00:52:38.160> to<00:52:38.280> research<00:52:38.700> but<00:52:39.000> our<00:52:39.300> focus<00:52:39.900> is 00:52:40.130 --> 00:52:40.140 align:start position:0% we want to research but our focus is 00:52:40.140 --> 00:52:41.750 align:start position:0% we want to research but our focus is really<00:52:40.440> on<00:52:40.680> I<00:52:40.980> would<00:52:41.160> say<00:52:41.280> native<00:52:41.520> account 00:52:41.750 --> 00:52:41.760 align:start position:0% really on I would say native account 00:52:41.760 --> 00:52:43.490 align:start position:0% really on I would say native account abstraction<00:52:42.240> on<00:52:42.480> Leo<00:52:42.780> twos<00:52:43.079> and<00:52:43.200> that's<00:52:43.260> why 00:52:43.490 --> 00:52:43.500 align:start position:0% abstraction on Leo twos and that's why 00:52:43.500 --> 00:52:45.710 align:start position:0% abstraction on Leo twos and that's why we're<00:52:43.740> building<00:52:44.099> on<00:52:44.400> stock<00:52:44.579> net<00:52:44.819> and<00:52:45.000> ZK<00:52:45.300> Singh 00:52:45.710 --> 00:52:45.720 align:start position:0% we're building on stock net and ZK Singh 00:52:45.720 --> 00:52:47.450 align:start position:0% we're building on stock net and ZK Singh and<00:52:46.020> I<00:52:46.140> think<00:52:46.260> we<00:52:46.500> kind<00:52:46.619> of<00:52:46.740> have<00:52:46.920> our<00:52:47.099> hands 00:52:47.450 --> 00:52:47.460 align:start position:0% and I think we kind of have our hands 00:52:47.460 --> 00:52:49.609 align:start position:0% and I think we kind of have our hands full<00:52:47.640> with<00:52:47.880> that<00:52:48.059> already<00:52:48.240> still<00:52:49.079> discussing 00:52:49.609 --> 00:52:49.619 align:start position:0% full with that already still discussing 00:52:49.619 --> 00:52:51.410 align:start position:0% full with that already still discussing with<00:52:49.800> our<00:52:49.980> earlier<00:52:50.339> twos<00:52:50.760> to<00:52:50.940> see<00:52:51.059> if<00:52:51.119> we<00:52:51.240> can 00:52:51.410 --> 00:52:51.420 align:start position:0% with our earlier twos to see if we can 00:52:51.420 --> 00:52:52.790 align:start position:0% with our earlier twos to see if we can convince<00:52:51.839> them<00:52:51.960> you<00:52:52.140> know<00:52:52.260> to<00:52:52.380> to<00:52:52.619> move 00:52:52.790 --> 00:52:52.800 align:start position:0% convince them you know to to move 00:52:52.800 --> 00:52:55.069 align:start position:0% convince them you know to to move forward<00:52:53.099> with<00:52:53.400> that<00:52:53.579> as<00:52:53.760> well<00:52:53.940> so<00:52:54.720> for<00:52:54.960> the 00:52:55.069 --> 00:52:55.079 align:start position:0% forward with that as well so for the 00:52:55.079 --> 00:52:57.890 align:start position:0% forward with that as well so for the moment<00:52:55.260> we<00:52:55.500> are<00:52:55.680> exploring<00:52:56.099> with<00:52:56.579> Falls<00:52:56.940> 337 00:52:57.890 --> 00:52:57.900 align:start position:0% moment we are exploring with Falls 337 00:52:57.900 --> 00:52:59.809 align:start position:0% moment we are exploring with Falls 337 but<00:52:58.559> again<00:52:58.740> just<00:52:58.980> to<00:52:59.099> highlight<00:52:59.460> that<00:52:59.640> on 00:52:59.809 --> 00:52:59.819 align:start position:0% but again just to highlight that on 00:52:59.819 --> 00:53:01.190 align:start position:0% but again just to highlight that on Stockton<00:53:00.119> and<00:53:00.240> DK<00:53:00.540> Singh<00:53:00.960> it's<00:53:01.020> actually 00:53:01.190 --> 00:53:01.200 align:start position:0% Stockton and DK Singh it's actually 00:53:01.200 --> 00:53:03.109 align:start position:0% Stockton and DK Singh it's actually heavily<00:53:01.619> inspired<00:53:02.040> by<00:53:02.099> 4337<00:53:02.819> so<00:53:03.000> it's 00:53:03.109 --> 00:53:03.119 align:start position:0% heavily inspired by 4337 so it's 00:53:03.119 --> 00:53:05.089 align:start position:0% heavily inspired by 4337 so it's actually<00:53:03.300> what<00:53:03.839> we<00:53:04.020> are<00:53:04.200> already<00:53:04.440> supporting 00:53:05.089 --> 00:53:05.099 align:start position:0% actually what we are already supporting 00:53:05.099 --> 00:53:08.450 align:start position:0% actually what we are already supporting but<00:53:05.520> on<00:53:06.240> on<00:53:06.420> this<00:53:06.660> chain<00:53:06.900> so<00:53:07.619> at<00:53:07.859> the<00:53:07.980> moment<00:53:08.160> no 00:53:08.450 --> 00:53:08.460 align:start position:0% but on on this chain so at the moment no 00:53:08.460 --> 00:53:10.730 align:start position:0% but on on this chain so at the moment no plans<00:53:08.760> but<00:53:09.180> that's<00:53:09.540> for<00:53:09.960> sure<00:53:10.079> something<00:53:10.380> that 00:53:10.730 --> 00:53:10.740 align:start position:0% plans but that's for sure something that 00:53:10.740 --> 00:53:12.049 align:start position:0% plans but that's for sure something that we<00:53:10.859> are<00:53:10.980> discussing<00:53:11.400> internally<00:53:11.819> and 00:53:12.049 --> 00:53:12.059 align:start position:0% we are discussing internally and 00:53:12.059 --> 00:53:13.790 align:start position:0% we are discussing internally and researching 00:53:13.790 --> 00:53:13.800 align:start position:0% researching 00:53:13.800 --> 00:53:17.569 align:start position:0% researching uh<00:53:14.520> jog<00:53:15.119> this<00:53:15.359> question<00:53:15.540> is<00:53:15.780> for<00:53:15.960> you<00:53:16.140> I<00:53:17.099> Tried 00:53:17.569 --> 00:53:17.579 align:start position:0% uh jog this question is for you I Tried 00:53:17.579 --> 00:53:21.230 align:start position:0% uh jog this question is for you I Tried reading<00:53:18.260> erc4337<00:53:19.260> the<00:53:19.500> other<00:53:19.619> day<00:53:19.940> and<00:53:20.940> could 00:53:21.230 --> 00:53:21.240 align:start position:0% reading erc4337 the other day and could 00:53:21.240 --> 00:53:22.790 align:start position:0% reading erc4337 the other day and could you<00:53:21.359> explain<00:53:21.540> a<00:53:21.839> bit<00:53:21.960> why<00:53:22.200> it's<00:53:22.380> such<00:53:22.559> a<00:53:22.680> hard 00:53:22.790 --> 00:53:22.800 align:start position:0% you explain a bit why it's such a hard 00:53:22.800 --> 00:53:26.450 align:start position:0% you explain a bit why it's such a hard read<00:53:23.300> uh<00:53:24.300> well<00:53:24.480> first<00:53:24.780> of<00:53:24.900> all<00:53:25.079> because<00:53:25.380> uh<00:53:26.040> we 00:53:26.450 --> 00:53:26.460 align:start position:0% read uh well first of all because uh we 00:53:26.460 --> 00:53:29.750 align:start position:0% read uh well first of all because uh we are<00:53:26.640> not<00:53:26.700> very<00:53:26.819> good<00:53:27.059> writers<00:53:27.480> I<00:53:27.720> guess<00:53:27.980> but<00:53:28.980> I 00:53:29.750 --> 00:53:29.760 align:start position:0% are not very good writers I guess but I 00:53:29.760 --> 00:53:31.309 align:start position:0% are not very good writers I guess but I mean<00:53:29.940> we<00:53:30.180> could<00:53:30.240> we<00:53:30.599> could<00:53:30.720> have<00:53:30.839> written<00:53:31.140> it 00:53:31.309 --> 00:53:31.319 align:start position:0% mean we could we could have written it 00:53:31.319 --> 00:53:33.710 align:start position:0% mean we could we could have written it in<00:53:31.500> a<00:53:31.619> clearer<00:53:31.980> way<00:53:32.160> and<00:53:32.700> maybe<00:53:32.940> even<00:53:33.119> split<00:53:33.599> it 00:53:33.710 --> 00:53:33.720 align:start position:0% in a clearer way and maybe even split it 00:53:33.720 --> 00:53:36.650 align:start position:0% in a clearer way and maybe even split it to<00:53:33.839> more<00:53:34.079> than<00:53:34.260> one<00:53:34.559> more<00:53:34.980> than<00:53:35.160> one<00:53:35.280> ELC<00:53:35.819> but 00:53:36.650 --> 00:53:36.660 align:start position:0% to more than one more than one ELC but 00:53:36.660 --> 00:53:38.990 align:start position:0% to more than one more than one ELC but the<00:53:37.260> other<00:53:37.380> the<00:53:37.740> other<00:53:37.920> reason<00:53:38.160> is<00:53:38.400> that<00:53:38.700> it 00:53:38.990 --> 00:53:39.000 align:start position:0% the other the other reason is that it 00:53:39.000 --> 00:53:40.870 align:start position:0% the other the other reason is that it really<00:53:39.180> is<00:53:39.480> complicated 00:53:40.870 --> 00:53:40.880 align:start position:0% really is complicated 00:53:40.880 --> 00:53:44.210 align:start position:0% really is complicated so<00:53:41.880> it<00:53:42.119> really<00:53:42.240> is<00:53:42.420> complicated<00:53:42.900> because<00:53:43.680> we 00:53:44.210 --> 00:53:44.220 align:start position:0% so it really is complicated because we 00:53:44.220 --> 00:53:46.970 align:start position:0% so it really is complicated because we paid<00:53:44.520> a<00:53:44.700> lot<00:53:44.760> of<00:53:44.880> attention<00:53:45.240> to<00:53:46.200> to<00:53:46.800> keep 00:53:46.970 --> 00:53:46.980 align:start position:0% paid a lot of attention to to keep 00:53:46.980 --> 00:53:49.549 align:start position:0% paid a lot of attention to to keep things<00:53:47.220> decentralized<00:53:48.180> by<00:53:48.359> having<00:53:48.660> a<00:53:48.960> mempool 00:53:49.549 --> 00:53:49.559 align:start position:0% things decentralized by having a mempool 00:53:49.559 --> 00:53:52.130 align:start position:0% things decentralized by having a mempool and<00:53:50.339> keeping<00:53:50.640> the<00:53:50.760> mempool<00:53:51.180> keeping<00:53:51.900> the<00:53:52.020> main 00:53:52.130 --> 00:53:52.140 align:start position:0% and keeping the mempool keeping the main 00:53:52.140 --> 00:53:54.349 align:start position:0% and keeping the mempool keeping the main pool<00:53:52.440> protected 00:53:54.349 --> 00:53:54.359 align:start position:0% pool protected 00:53:54.359 --> 00:53:58.430 align:start position:0% pool protected so<00:53:55.260> um<00:53:55.400> so<00:53:56.400> to<00:53:56.579> prevent<00:53:56.940> a<00:53:57.180> Dos<00:53:57.660> attacks<00:53:58.200> that 00:53:58.430 --> 00:53:58.440 align:start position:0% so um so to prevent a Dos attacks that 00:53:58.440 --> 00:54:00.950 align:start position:0% so um so to prevent a Dos attacks that would<00:53:58.800> bring<00:53:58.980> the<00:53:59.220> system<00:53:59.400> May<00:53:59.640> on<00:53:59.880> his<00:54:00.000> knees 00:54:00.950 --> 00:54:00.960 align:start position:0% would bring the system May on his knees 00:54:00.960 --> 00:54:04.190 align:start position:0% would bring the system May on his knees so<00:54:01.680> uh<00:54:02.040> this<00:54:02.520> so<00:54:02.940> yeah<00:54:03.059> this<00:54:03.300> this<00:54:03.660> made<00:54:03.960> a 00:54:04.190 --> 00:54:04.200 align:start position:0% so uh this so yeah this this made a 00:54:04.200 --> 00:54:07.250 align:start position:0% so uh this so yeah this this made a difficulty<00:54:04.680> then<00:54:05.099> I<00:54:05.339> understand<00:54:05.460> that<00:54:05.880> uh<00:54:06.780> hi 00:54:07.250 --> 00:54:07.260 align:start position:0% difficulty then I understand that uh hi 00:54:07.260 --> 00:54:10.250 align:start position:0% difficulty then I understand that uh hi everyone<00:54:07.380> uh<00:54:08.220> I<00:54:08.460> work<00:54:08.579> at<00:54:08.819> Diagon<00:54:09.300> and<00:54:09.720> we're 00:54:10.250 --> 00:54:10.260 align:start position:0% everyone uh I work at Diagon and we're 00:54:10.260 --> 00:54:12.650 align:start position:0% everyone uh I work at Diagon and we're working<00:54:10.500> on<00:54:10.800> bringing<00:54:11.220> subscriptions<00:54:12.000> on 00:54:12.650 --> 00:54:12.660 align:start position:0% working on bringing subscriptions on 00:54:12.660 --> 00:54:15.470 align:start position:0% working on bringing subscriptions on ethereum<00:54:13.559> we're<00:54:14.339> currently<00:54:14.700> using<00:54:15.059> meta 00:54:15.470 --> 00:54:15.480 align:start position:0% ethereum we're currently using meta 00:54:15.480 --> 00:54:17.390 align:start position:0% ethereum we're currently using meta transactions<00:54:16.079> do<00:54:16.500> you<00:54:16.740> think<00:54:16.920> metal 00:54:17.390 --> 00:54:17.400 align:start position:0% transactions do you think metal 00:54:17.400 --> 00:54:19.849 align:start position:0% transactions do you think metal transactions<00:54:18.180> will<00:54:18.420> be<00:54:18.540> less<00:54:18.780> relevant<00:54:19.319> when 00:54:19.849 --> 00:54:19.859 align:start position:0% transactions will be less relevant when 00:54:19.859 --> 00:54:23.089 align:start position:0% transactions will be less relevant when when<00:54:20.520> accounts<00:54:21.359> obstructions<00:54:21.900> will<00:54:22.079> go<00:54:22.260> live 00:54:23.089 --> 00:54:23.099 align:start position:0% when accounts obstructions will go live 00:54:23.099 --> 00:54:25.309 align:start position:0% when accounts obstructions will go live so<00:54:23.640> the<00:54:23.819> issue<00:54:24.059> with<00:54:24.240> the<00:54:24.420> meta<00:54:24.839> transactions 00:54:25.309 --> 00:54:25.319 align:start position:0% so the issue with the meta transactions 00:54:25.319 --> 00:54:27.349 align:start position:0% so the issue with the meta transactions right<00:54:25.559> is<00:54:25.800> like<00:54:26.040> one<00:54:26.400> you<00:54:26.640> need<00:54:26.819> some<00:54:27.119> kind<00:54:27.240> of 00:54:27.349 --> 00:54:27.359 align:start position:0% right is like one you need some kind of 00:54:27.359 --> 00:54:30.530 align:start position:0% right is like one you need some kind of mechanism<00:54:27.839> to<00:54:28.260> like<00:54:29.000> figure<00:54:30.000> out<00:54:30.240> you<00:54:30.420> know 00:54:30.530 --> 00:54:30.540 align:start position:0% mechanism to like figure out you know 00:54:30.540 --> 00:54:32.150 align:start position:0% mechanism to like figure out you know who's<00:54:30.720> going<00:54:30.960> to<00:54:31.079> pay<00:54:31.260> on<00:54:31.440> your<00:54:31.559> behalf<00:54:31.920> and 00:54:32.150 --> 00:54:32.160 align:start position:0% who's going to pay on your behalf and 00:54:32.160 --> 00:54:33.710 align:start position:0% who's going to pay on your behalf and connect<00:54:32.400> you<00:54:32.640> to<00:54:32.819> the<00:54:32.940> person<00:54:33.119> paying<00:54:33.480> on<00:54:33.599> your 00:54:33.710 --> 00:54:33.720 align:start position:0% connect you to the person paying on your 00:54:33.720 --> 00:54:37.309 align:start position:0% connect you to the person paying on your behalf<00:54:34.079> and<00:54:34.920> these<00:54:35.339> like<00:54:35.640> if<00:54:36.180> this<00:54:36.359> depends<00:54:37.200> on 00:54:37.309 --> 00:54:37.319 align:start position:0% behalf and these like if this depends on 00:54:37.319 --> 00:54:39.470 align:start position:0% behalf and these like if this depends on specific<00:54:37.740> actors<00:54:38.280> then<00:54:38.579> like<00:54:38.760> that<00:54:39.000> becomes<00:54:39.359> a 00:54:39.470 --> 00:54:39.480 align:start position:0% specific actors then like that becomes a 00:54:39.480 --> 00:54:40.730 align:start position:0% specific actors then like that becomes a censorship<00:54:39.900> vector<00:54:40.319> and<00:54:40.440> they<00:54:40.559> might 00:54:40.730 --> 00:54:40.740 align:start position:0% censorship vector and they might 00:54:40.740 --> 00:54:42.770 align:start position:0% censorship vector and they might disappear<00:54:41.099> and<00:54:41.280> all<00:54:41.400> of<00:54:41.520> these<00:54:41.700> things<00:54:41.819> and 00:54:42.770 --> 00:54:42.780 align:start position:0% disappear and all of these things and 00:54:42.780 --> 00:54:44.809 align:start position:0% disappear and all of these things and also<00:54:43.079> emitted<00:54:43.619> transaction<00:54:43.980> requires<00:54:44.640> like 00:54:44.809 --> 00:54:44.819 align:start position:0% also emitted transaction requires like 00:54:44.819 --> 00:54:47.150 align:start position:0% also emitted transaction requires like this<00:54:45.119> extra<00:54:45.300> gas<00:54:45.660> cost<00:54:45.900> of<00:54:46.200> 21 00:54:47.150 --> 00:54:47.160 align:start position:0% this extra gas cost of 21 00:54:47.160 --> 00:54:49.730 align:start position:0% this extra gas cost of 21 000<00:54:47.280> uh<00:54:48.000> per<00:54:48.180> transaction<00:54:48.660> right<00:54:48.960> on<00:54:49.319> top<00:54:49.440> of<00:54:49.559> a 00:54:49.730 --> 00:54:49.740 align:start position:0% 000 uh per transaction right on top of a 00:54:49.740 --> 00:54:52.490 align:start position:0% 000 uh per transaction right on top of a smart<00:54:49.920> contract<00:54:50.280> overhead<00:54:50.700> so<00:54:51.480> like<00:54:52.200> I<00:54:52.380> think 00:54:52.490 --> 00:54:52.500 align:start position:0% smart contract overhead so like I think 00:54:52.500 --> 00:54:55.010 align:start position:0% smart contract overhead so like I think it's<00:54:52.920> important<00:54:53.220> to<00:54:53.339> remember<00:54:53.520> that<00:54:54.020> erc4337 00:54:55.010 --> 00:54:55.020 align:start position:0% it's important to remember that erc4337 00:54:55.020 --> 00:54:58.069 align:start position:0% it's important to remember that erc4337 like<00:54:55.380> it<00:54:55.980> is<00:54:56.220> similar<00:54:56.760> to<00:54:57.059> meta<00:54:57.540> transactions 00:54:58.069 --> 00:54:58.079 align:start position:0% like it is similar to meta transactions 00:54:58.079 --> 00:54:59.990 align:start position:0% like it is similar to meta transactions in<00:54:58.440> a<00:54:58.559> lot<00:54:58.619> of<00:54:58.740> ways<00:54:58.980> and<00:54:59.099> like<00:54:59.339> it<00:54:59.460> uses<00:54:59.760> very 00:54:59.990 --> 00:55:00.000 align:start position:0% in a lot of ways and like it uses very 00:55:00.000 --> 00:55:03.650 align:start position:0% in a lot of ways and like it uses very similar<00:55:00.540> ideas<00:55:01.319> but<00:55:02.040> like<00:55:02.700> it<00:55:02.940> does<00:55:03.119> add<00:55:03.420> this 00:55:03.650 --> 00:55:03.660 align:start position:0% similar ideas but like it does add this 00:55:03.660 --> 00:55:06.230 align:start position:0% similar ideas but like it does add this like<00:55:03.900> oh<00:55:04.200> open<00:55:04.440> mempool<00:55:04.920> to<00:55:05.220> solve<00:55:05.520> to<00:55:05.880> kind<00:55:06.180> of 00:55:06.230 --> 00:55:06.240 align:start position:0% like oh open mempool to solve to kind of 00:55:06.240 --> 00:55:08.089 align:start position:0% like oh open mempool to solve to kind of remove<00:55:06.359> dependence<00:55:06.900> on<00:55:07.020> specific<00:55:07.380> actors<00:55:07.859> and 00:55:08.089 --> 00:55:08.099 align:start position:0% remove dependence on specific actors and 00:55:08.099 --> 00:55:10.069 align:start position:0% remove dependence on specific actors and it<00:55:08.339> adds<00:55:08.640> this<00:55:08.819> kind<00:55:09.000> of<00:55:09.119> like<00:55:09.599> batching 00:55:10.069 --> 00:55:10.079 align:start position:0% it adds this kind of like batching 00:55:10.079 --> 00:55:12.710 align:start position:0% it adds this kind of like batching problem<00:55:10.559> to<00:55:11.099> like<00:55:11.520> basically<00:55:11.940> cut<00:55:12.240> the<00:55:12.480> yeah 00:55:12.710 --> 00:55:12.720 align:start position:0% problem to like basically cut the yeah 00:55:12.720 --> 00:55:15.290 align:start position:0% problem to like basically cut the yeah 21<00:55:13.440> 000<00:55:13.500> overhead<00:55:13.920> to<00:55:14.160> uh<00:55:14.460> one<00:55:14.640> uh<00:55:14.760> to<00:55:15.000> one<00:55:15.180> per 00:55:15.290 --> 00:55:15.300 align:start position:0% 21 000 overhead to uh one uh to one per 00:55:15.300 --> 00:55:17.329 align:start position:0% 21 000 overhead to uh one uh to one per block<00:55:15.540> so<00:55:15.839> I<00:55:15.960> like<00:55:16.140> I<00:55:16.559> view<00:55:16.680> it<00:55:16.859> as<00:55:16.980> a<00:55:17.160> kind<00:55:17.280> of 00:55:17.329 --> 00:55:17.339 align:start position:0% block so I like I view it as a kind of 00:55:17.339 --> 00:55:20.930 align:start position:0% block so I like I view it as a kind of iteration<00:55:17.760> on<00:55:18.059> the<00:55:18.300> same<00:55:18.420> idea 00:55:20.930 --> 00:55:20.940 align:start position:0% 00:55:20.940 --> 00:55:23.390 align:start position:0% if<00:55:21.480> I<00:55:21.660> can<00:55:21.780> just<00:55:21.960> add<00:55:22.200> on<00:55:22.380> that<00:55:22.559> I<00:55:22.800> think<00:55:22.920> with 00:55:23.390 --> 00:55:23.400 align:start position:0% if I can just add on that I think with 00:55:23.400 --> 00:55:25.190 align:start position:0% if I can just add on that I think with Native<00:55:23.940> account<00:55:24.180> abstraction<00:55:24.720> there's<00:55:25.020> no 00:55:25.190 --> 00:55:25.200 align:start position:0% Native account abstraction there's no 00:55:25.200 --> 00:55:26.569 align:start position:0% Native account abstraction there's no more<00:55:25.380> meta<00:55:25.740> transaction<00:55:25.980> because<00:55:26.339> the 00:55:26.569 --> 00:55:26.579 align:start position:0% more meta transaction because the 00:55:26.579 --> 00:55:28.790 align:start position:0% more meta transaction because the account<00:55:26.760> can<00:55:27.180> pay<00:55:27.420> transaction<00:55:28.140> fee<00:55:28.559> by 00:55:28.790 --> 00:55:28.800 align:start position:0% account can pay transaction fee by 00:55:28.800 --> 00:55:32.089 align:start position:0% account can pay transaction fee by itself<00:55:29.040> so<00:55:30.000> the<00:55:30.480> day<00:55:30.660> if<00:55:30.780> we<00:55:30.960> bring<00:55:31.140> 4337<00:55:31.859> to 00:55:32.089 --> 00:55:32.099 align:start position:0% itself so the day if we bring 4337 to 00:55:32.099 --> 00:55:33.829 align:start position:0% itself so the day if we bring 4337 to the<00:55:32.220> protocol<00:55:32.460> level<00:55:32.760> there<00:55:33.059> is<00:55:33.180> no<00:55:33.300> more<00:55:33.420> meta 00:55:33.829 --> 00:55:33.839 align:start position:0% the protocol level there is no more meta 00:55:33.839 --> 00:55:36.470 align:start position:0% the protocol level there is no more meta transaction<00:55:34.200> because<00:55:34.980> you<00:55:35.579> just<00:55:35.700> sign<00:55:36.059> with 00:55:36.470 --> 00:55:36.480 align:start position:0% transaction because you just sign with 00:55:36.480 --> 00:55:38.630 align:start position:0% transaction because you just sign with the<00:55:36.720> keys<00:55:37.020> you<00:55:37.260> send<00:55:37.619> your<00:55:37.920> transaction<00:55:38.339> and 00:55:38.630 --> 00:55:38.640 align:start position:0% the keys you send your transaction and 00:55:38.640 --> 00:55:39.890 align:start position:0% the keys you send your transaction and then<00:55:38.760> the<00:55:38.940> account<00:55:39.059> will<00:55:39.420> automatically 00:55:39.890 --> 00:55:39.900 align:start position:0% then the account will automatically 00:55:39.900 --> 00:55:42.109 align:start position:0% then the account will automatically validate<00:55:40.559> and<00:55:41.220> if<00:55:41.400> you<00:55:41.520> validate<00:55:41.940> the 00:55:42.109 --> 00:55:42.119 align:start position:0% validate and if you validate the 00:55:42.119 --> 00:55:43.609 align:start position:0% validate and if you validate the transaction<00:55:42.420> we'll<00:55:42.780> pay<00:55:42.960> the<00:55:43.140> fee<00:55:43.319> directly 00:55:43.609 --> 00:55:43.619 align:start position:0% transaction we'll pay the fee directly 00:55:43.619 --> 00:55:45.650 align:start position:0% transaction we'll pay the fee directly to<00:55:43.740> the<00:55:43.859> miner<00:55:44.220> so<00:55:44.400> if<00:55:44.520> we<00:55:44.640> go<00:55:44.760> to<00:55:44.940> full<00:55:45.240> account 00:55:45.650 --> 00:55:45.660 align:start position:0% to the miner so if we go to full account 00:55:45.660 --> 00:55:47.329 align:start position:0% to the miner so if we go to full account abstraction<00:55:46.200> there's<00:55:46.500> no<00:55:46.740> more<00:55:46.859> there's<00:55:47.160> no 00:55:47.329 --> 00:55:47.339 align:start position:0% abstraction there's no more there's no 00:55:47.339 --> 00:55:49.790 align:start position:0% abstraction there's no more there's no more<00:55:47.460> need<00:55:47.700> to<00:55:47.880> have<00:55:48.119> a<00:55:48.540> meta<00:55:48.960> transaction<00:55:49.260> and 00:55:49.790 --> 00:55:49.800 align:start position:0% more need to have a meta transaction and 00:55:49.800 --> 00:55:51.950 align:start position:0% more need to have a meta transaction and we<00:55:49.980> layers<00:55:50.339> here<00:55:50.579> hey<00:55:51.119> everybody 00:55:51.950 --> 00:55:51.960 align:start position:0% we layers here hey everybody 00:55:51.960 --> 00:55:54.049 align:start position:0% we layers here hey everybody um<00:55:52.079> yeah<00:55:52.680> firstly<00:55:53.099> thanks<00:55:53.339> David<00:55:53.520> I'm<00:55:53.819> a<00:55:54.000> big 00:55:54.049 --> 00:55:54.059 align:start position:0% um yeah firstly thanks David I'm a big 00:55:54.059 --> 00:55:55.309 align:start position:0% um yeah firstly thanks David I'm a big fan<00:55:54.180> of<00:55:54.300> bankless 00:55:55.309 --> 00:55:55.319 align:start position:0% fan of bankless 00:55:55.319 --> 00:55:57.230 align:start position:0% fan of bankless um these<00:55:55.800> are<00:55:55.859> great<00:55:56.040> conversations<00:55:56.460> and<00:55:57.059> uh 00:55:57.230 --> 00:55:57.240 align:start position:0% um these are great conversations and uh 00:55:57.240 --> 00:55:58.849 align:start position:0% um these are great conversations and uh vitalik<00:55:57.720> I'm<00:55:57.839> a<00:55:57.960> fan<00:55:58.079> of<00:55:58.140> ethereum<00:55:58.500> so<00:55:58.680> thank 00:55:58.849 --> 00:55:58.859 align:start position:0% vitalik I'm a fan of ethereum so thank 00:55:58.859 --> 00:56:00.230 align:start position:0% vitalik I'm a fan of ethereum so thank you<00:55:58.980> for<00:55:59.099> that 00:56:00.230 --> 00:56:00.240 align:start position:0% you for that 00:56:00.240 --> 00:56:02.589 align:start position:0% you for that um<00:56:00.300> also<00:56:00.720> a<00:56:00.780> fan<00:56:00.900> of<00:56:01.020> ethereum 00:56:02.589 --> 00:56:02.599 align:start position:0% um also a fan of ethereum 00:56:02.599 --> 00:56:04.490 align:start position:0% um also a fan of ethereum somebody<00:56:03.599> mentioned<00:56:04.020> that<00:56:04.140> like<00:56:04.319> more 00:56:04.490 --> 00:56:04.500 align:start position:0% somebody mentioned that like more 00:56:04.500 --> 00:56:07.069 align:start position:0% somebody mentioned that like more wallets<00:56:04.859> are<00:56:05.040> lost<00:56:05.280> than<00:56:05.760> are<00:56:05.940> stolen<00:56:06.420> so<00:56:07.020> I 00:56:07.069 --> 00:56:07.079 align:start position:0% wallets are lost than are stolen so I 00:56:07.079 --> 00:56:08.150 align:start position:0% wallets are lost than are stolen so I kind<00:56:07.200> of<00:56:07.319> want<00:56:07.380> to<00:56:07.500> zoom<00:56:07.680> in<00:56:07.740> on<00:56:07.920> like<00:56:08.040> the 00:56:08.150 --> 00:56:08.160 align:start position:0% kind of want to zoom in on like the 00:56:08.160 --> 00:56:10.190 align:start position:0% kind of want to zoom in on like the social<00:56:08.280> recovery<00:56:08.819> aspect<00:56:09.180> I<00:56:09.780> think<00:56:09.839> if<00:56:10.140> we're 00:56:10.190 --> 00:56:10.200 align:start position:0% social recovery aspect I think if we're 00:56:10.200 --> 00:56:11.690 align:start position:0% social recovery aspect I think if we're going<00:56:10.380> to<00:56:10.440> onboard<00:56:10.680> the<00:56:10.920> next<00:56:11.040> wave<00:56:11.280> of<00:56:11.400> users 00:56:11.690 --> 00:56:11.700 align:start position:0% going to onboard the next wave of users 00:56:11.700 --> 00:56:13.250 align:start position:0% going to onboard the next wave of users we<00:56:12.000> can't<00:56:12.119> expect<00:56:12.300> them<00:56:12.540> to<00:56:12.720> have<00:56:12.839> crypto 00:56:13.250 --> 00:56:13.260 align:start position:0% we can't expect them to have crypto 00:56:13.260 --> 00:56:14.630 align:start position:0% we can't expect them to have crypto friends<00:56:13.500> or<00:56:13.800> Hardware<00:56:14.040> wallets<00:56:14.520> already 00:56:14.630 --> 00:56:14.640 align:start position:0% friends or Hardware wallets already 00:56:14.640 --> 00:56:16.010 align:start position:0% friends or Hardware wallets already right 00:56:16.010 --> 00:56:16.020 align:start position:0% right 00:56:16.020 --> 00:56:16.670 align:start position:0% right um 00:56:16.670 --> 00:56:16.680 align:start position:0% um 00:56:16.680 --> 00:56:18.410 align:start position:0% um so<00:56:17.220> I<00:56:17.400> know<00:56:17.520> that<00:56:17.640> Argent<00:56:18.000> has<00:56:18.240> some 00:56:18.410 --> 00:56:18.420 align:start position:0% so I know that Argent has some 00:56:18.420 --> 00:56:20.270 align:start position:0% so I know that Argent has some functionality<00:56:18.960> where<00:56:19.440> you<00:56:19.680> can<00:56:19.740> kind<00:56:19.920> of<00:56:20.040> back 00:56:20.270 --> 00:56:20.280 align:start position:0% functionality where you can kind of back 00:56:20.280 --> 00:56:21.890 align:start position:0% functionality where you can kind of back up<00:56:20.400> a<00:56:20.579> share<00:56:20.819> of<00:56:20.940> your<00:56:21.059> key<00:56:21.180> to<00:56:21.420> Google<00:56:21.599> Drive 00:56:21.890 --> 00:56:21.900 align:start position:0% up a share of your key to Google Drive 00:56:21.900 --> 00:56:24.710 align:start position:0% up a share of your key to Google Drive I'm<00:56:22.800> from<00:56:22.980> ultimate.money<00:56:23.760> we<00:56:24.359> do<00:56:24.540> something 00:56:24.710 --> 00:56:24.720 align:start position:0% I'm from ultimate.money we do something 00:56:24.720 --> 00:56:26.390 align:start position:0% I'm from ultimate.money we do something similar<00:56:25.079> with<00:56:25.319> Apple<00:56:25.559> iCloud<00:56:26.040> accounts 00:56:26.390 --> 00:56:26.400 align:start position:0% similar with Apple iCloud accounts 00:56:26.400 --> 00:56:28.849 align:start position:0% similar with Apple iCloud accounts because<00:56:26.520> we've<00:56:26.760> read<00:56:26.880> that<00:56:27.059> 95<00:56:27.440> are<00:56:28.440> 2fa 00:56:28.849 --> 00:56:28.859 align:start position:0% because we've read that 95 are 2fa 00:56:28.859 --> 00:56:29.870 align:start position:0% because we've read that 95 are 2fa encrypted 00:56:29.870 --> 00:56:29.880 align:start position:0% encrypted 00:56:29.880 --> 00:56:31.670 align:start position:0% encrypted um<00:56:29.940> so<00:56:30.420> like<00:56:30.540> do<00:56:30.720> we<00:56:30.839> as<00:56:31.020> a<00:56:31.140> community<00:56:31.260> kind<00:56:31.559> of 00:56:31.670 --> 00:56:31.680 align:start position:0% um so like do we as a community kind of 00:56:31.680 --> 00:56:32.930 align:start position:0% um so like do we as a community kind of accept<00:56:31.800> that<00:56:32.099> we're<00:56:32.220> going<00:56:32.339> to<00:56:32.400> stand<00:56:32.579> on<00:56:32.760> one 00:56:32.930 --> 00:56:32.940 align:start position:0% accept that we're going to stand on one 00:56:32.940 --> 00:56:36.230 align:start position:0% accept that we're going to stand on one leg<00:56:33.180> of<00:56:33.960> like<00:56:34.200> either<00:56:35.160> you<00:56:35.640> know<00:56:35.700> Google<00:56:35.880> drive 00:56:36.230 --> 00:56:36.240 align:start position:0% leg of like either you know Google drive 00:56:36.240 --> 00:56:38.450 align:start position:0% leg of like either you know Google drive or<00:56:36.599> Apple<00:56:36.839> iCloud 00:56:38.450 --> 00:56:38.460 align:start position:0% or Apple iCloud 00:56:38.460 --> 00:56:39.410 align:start position:0% or Apple iCloud um<00:56:38.520> you<00:56:38.700> know<00:56:38.819> if<00:56:38.880> we're<00:56:38.940> trying<00:56:39.059> to<00:56:39.180> onboard 00:56:39.410 --> 00:56:39.420 align:start position:0% um you know if we're trying to onboard 00:56:39.420 --> 00:56:41.089 align:start position:0% um you know if we're trying to onboard people<00:56:39.660> that<00:56:39.960> are<00:56:40.140> really<00:56:40.440> like<00:56:40.680> new<00:56:40.920> to 00:56:41.089 --> 00:56:41.099 align:start position:0% people that are really like new to 00:56:41.099 --> 00:56:43.430 align:start position:0% people that are really like new to crypto<00:56:41.460> is<00:56:41.700> that<00:56:41.880> something<00:56:42.059> we<00:56:42.300> accept 00:56:43.430 --> 00:56:43.440 align:start position:0% crypto is that something we accept 00:56:43.440 --> 00:56:46.849 align:start position:0% crypto is that something we accept yeah<00:56:44.040> so<00:56:44.760> um<00:56:44.880> so<00:56:45.359> I<00:56:45.480> think<00:56:45.660> once<00:56:46.319> you<00:56:46.440> have<00:56:46.680> a 00:56:46.849 --> 00:56:46.859 align:start position:0% yeah so um so I think once you have a 00:56:46.859 --> 00:56:49.250 align:start position:0% yeah so um so I think once you have a recovery<00:56:47.339> built<00:56:47.700> into<00:56:47.760> the<00:56:48.000> wallet 00:56:49.250 --> 00:56:49.260 align:start position:0% recovery built into the wallet 00:56:49.260 --> 00:56:50.450 align:start position:0% recovery built into the wallet um<00:56:49.319> you<00:56:49.559> could<00:56:49.680> you<00:56:49.980> could<00:56:50.099> use<00:56:50.220> different 00:56:50.450 --> 00:56:50.460 align:start position:0% um you could you could use different 00:56:50.460 --> 00:56:51.950 align:start position:0% um you could you could use different mechanism<00:56:50.940> first<00:56:51.180> of<00:56:51.300> all<00:56:51.420> if<00:56:51.599> you<00:56:51.720> don't<00:56:51.780> have 00:56:51.950 --> 00:56:51.960 align:start position:0% mechanism first of all if you don't have 00:56:51.960 --> 00:56:53.569 align:start position:0% mechanism first of all if you don't have crypto<00:56:52.319> friends<00:56:52.500> and<00:56:52.800> you<00:56:52.920> don't<00:56:53.040> mind<00:56:53.280> some 00:56:53.569 --> 00:56:53.579 align:start position:0% crypto friends and you don't mind some 00:56:53.579 --> 00:56:56.030 align:start position:0% crypto friends and you don't mind some centralization<00:56:54.500> you<00:56:55.500> could<00:56:55.619> have<00:56:55.800> for 00:56:56.030 --> 00:56:56.040 align:start position:0% centralization you could have for 00:56:56.040 --> 00:56:58.970 align:start position:0% centralization you could have for example<00:56:56.339> you<00:56:57.240> could<00:56:57.300> have<00:56:57.540> a<00:56:57.839> service<00:56:58.260> like<00:56:58.740> a 00:56:58.970 --> 00:56:58.980 align:start position:0% example you could have a service like a 00:56:58.980 --> 00:57:01.250 align:start position:0% example you could have a service like a professional<00:56:59.460> Guardian<00:57:00.000> someone<00:57:00.900> with 00:57:01.250 --> 00:57:01.260 align:start position:0% professional Guardian someone with 00:57:01.260 --> 00:57:04.370 align:start position:0% professional Guardian someone with someone<00:57:01.619> who<00:57:01.859> can<00:57:01.980> verify<00:57:02.460> your<00:57:02.640> identity<00:57:03.380> and 00:57:04.370 --> 00:57:04.380 align:start position:0% someone who can verify your identity and 00:57:04.380 --> 00:57:07.490 align:start position:0% someone who can verify your identity and then<00:57:04.559> recover<00:57:05.099> your<00:57:05.460> wallet<00:57:05.900> and<00:57:06.900> you<00:57:07.380> could 00:57:07.490 --> 00:57:07.500 align:start position:0% then recover your wallet and you could 00:57:07.500 --> 00:57:10.130 align:start position:0% then recover your wallet and you could use<00:57:07.800> a<00:57:08.099> centralized<00:57:08.880> centralized<00:57:09.780> Solutions 00:57:10.130 --> 00:57:10.140 align:start position:0% use a centralized centralized Solutions 00:57:10.140 --> 00:57:13.130 align:start position:0% use a centralized centralized Solutions like<00:57:10.440> a<00:57:10.680> Google<00:57:10.920> drive<00:57:11.220> or<00:57:11.640> apple<00:57:11.880> that's<00:57:12.780> also 00:57:13.130 --> 00:57:13.140 align:start position:0% like a Google drive or apple that's also 00:57:13.140 --> 00:57:16.069 align:start position:0% like a Google drive or apple that's also fine<00:57:13.380> but<00:57:14.220> if<00:57:14.880> you<00:57:15.000> use<00:57:15.119> if<00:57:15.359> you<00:57:15.540> had<00:57:15.720> to<00:57:15.900> use 00:57:16.069 --> 00:57:16.079 align:start position:0% fine but if you use if you had to use 00:57:16.079 --> 00:57:19.130 align:start position:0% fine but if you use if you had to use this<00:57:16.260> within<00:57:16.619> AOA<00:57:17.099> it<00:57:17.819> means<00:57:18.119> that<00:57:18.359> Google<00:57:18.780> has 00:57:19.130 --> 00:57:19.140 align:start position:0% this within AOA it means that Google has 00:57:19.140 --> 00:57:21.230 align:start position:0% this within AOA it means that Google has control<00:57:19.380> over<00:57:19.680> over<00:57:20.280> your<00:57:20.520> account<00:57:20.700> and<00:57:21.059> maybe 00:57:21.230 --> 00:57:21.240 align:start position:0% control over over your account and maybe 00:57:21.240 --> 00:57:22.910 align:start position:0% control over over your account and maybe they<00:57:21.660> lock<00:57:21.839> you<00:57:22.020> out<00:57:22.200> of<00:57:22.260> it<00:57:22.440> at<00:57:22.619> some<00:57:22.800> point 00:57:22.910 --> 00:57:22.920 align:start position:0% they lock you out of it at some point 00:57:22.920 --> 00:57:26.750 align:start position:0% they lock you out of it at some point but<00:57:23.819> but<00:57:24.440> since<00:57:25.440> you<00:57:25.619> can<00:57:25.800> have<00:57:25.980> as<00:57:26.160> many<00:57:26.339> keys 00:57:26.750 --> 00:57:26.760 align:start position:0% but but since you can have as many keys 00:57:26.760 --> 00:57:28.790 align:start position:0% but but since you can have as many keys as<00:57:26.819> you<00:57:27.000> want<00:57:27.119> for<00:57:27.300> the<00:57:27.480> recovery<00:57:27.900> you<00:57:28.680> can 00:57:28.790 --> 00:57:28.800 align:start position:0% as you want for the recovery you can 00:57:28.800 --> 00:57:31.430 align:start position:0% as you want for the recovery you can actually<00:57:28.920> have<00:57:29.280> you<00:57:29.760> can<00:57:29.880> use<00:57:30.180> a<00:57:30.540> centralized 00:57:31.430 --> 00:57:31.440 align:start position:0% actually have you can use a centralized 00:57:31.440 --> 00:57:35.210 align:start position:0% actually have you can use a centralized way<00:57:32.040> for<00:57:32.280> login<00:57:32.460> like<00:57:32.940> log<00:57:33.240> in<00:57:33.420> with<00:57:34.020> Google<00:57:34.260> or 00:57:35.210 --> 00:57:35.220 align:start position:0% way for login like log in with Google or 00:57:35.220 --> 00:57:37.670 align:start position:0% way for login like log in with Google or anything<00:57:35.460> anything<00:57:35.880> of<00:57:36.240> this<00:57:36.420> sort<00:57:36.660> and<00:57:37.500> then 00:57:37.670 --> 00:57:37.680 align:start position:0% anything anything of this sort and then 00:57:37.680 --> 00:57:40.609 align:start position:0% anything anything of this sort and then and<00:57:38.339> still<00:57:38.640> keep<00:57:39.000> a<00:57:39.359> more<00:57:39.780> complex<00:57:40.079> recovery 00:57:40.609 --> 00:57:40.619 align:start position:0% and still keep a more complex recovery 00:57:40.619 --> 00:57:43.370 align:start position:0% and still keep a more complex recovery mechanism<00:57:41.160> for<00:57:42.059> the<00:57:42.240> case<00:57:42.480> where<00:57:42.839> they<00:57:43.140> decide 00:57:43.370 --> 00:57:43.380 align:start position:0% mechanism for the case where they decide 00:57:43.380 --> 00:57:45.349 align:start position:0% mechanism for the case where they decide AI<00:57:43.680> to<00:57:43.920> sensor<00:57:44.280> you<00:57:44.400> for<00:57:44.579> example 00:57:45.349 --> 00:57:45.359 align:start position:0% AI to sensor you for example 00:57:45.359 --> 00:57:48.470 align:start position:0% AI to sensor you for example so<00:57:45.900> you<00:57:46.079> can<00:57:46.200> benefit<00:57:46.380> from<00:57:46.859> both<00:57:47.220> from<00:57:48.119> both 00:57:48.470 --> 00:57:48.480 align:start position:0% so you can benefit from both from both 00:57:48.480 --> 00:57:51.230 align:start position:0% so you can benefit from both from both worlds<00:57:48.839> here<00:57:48.980> my<00:57:49.980> question<00:57:50.160> was<00:57:50.520> for<00:57:50.880> for 00:57:51.230 --> 00:57:51.240 align:start position:0% worlds here my question was for for 00:57:51.240 --> 00:57:54.349 align:start position:0% worlds here my question was for for Julian<00:57:51.780> yeah<00:57:52.559> so<00:57:52.800> the<00:57:53.700> way<00:57:53.819> we<00:57:54.000> see<00:57:54.119> social 00:57:54.349 --> 00:57:54.359 align:start position:0% Julian yeah so the way we see social 00:57:54.359 --> 00:57:56.690 align:start position:0% Julian yeah so the way we see social recovery<00:57:54.900> is<00:57:55.020> kind<00:57:55.500> of<00:57:55.619> in<00:57:56.160> a<00:57:56.280> sense<00:57:56.339> it's<00:57:56.520> a 00:57:56.690 --> 00:57:56.700 align:start position:0% recovery is kind of in a sense it's a 00:57:56.700 --> 00:57:59.750 align:start position:0% recovery is kind of in a sense it's a protocol<00:57:57.000> so<00:57:57.780> every<00:57:58.260> users<00:57:58.740> will<00:57:59.099> want<00:57:59.400> to<00:57:59.520> use 00:57:59.750 --> 00:57:59.760 align:start position:0% protocol so every users will want to use 00:57:59.760 --> 00:58:01.970 align:start position:0% protocol so every users will want to use different<00:58:00.119> mechanism<00:58:00.720> to<00:58:01.079> you<00:58:01.380> know<00:58:01.440> to<00:58:01.619> get 00:58:01.970 --> 00:58:01.980 align:start position:0% different mechanism to you know to get 00:58:01.980 --> 00:58:04.370 align:start position:0% different mechanism to you know to get back<00:58:02.160> access<00:58:02.400> to<00:58:02.819> to<00:58:03.240> the<00:58:03.480> wallet<00:58:03.780> so<00:58:03.960> yeah<00:58:04.200> we 00:58:04.370 --> 00:58:04.380 align:start position:0% back access to to the wallet so yeah we 00:58:04.380 --> 00:58:06.349 align:start position:0% back access to to the wallet so yeah we don't<00:58:04.500> expect<00:58:04.740> people<00:58:05.579> to<00:58:05.880> have<00:58:06.000> crypto 00:58:06.349 --> 00:58:06.359 align:start position:0% don't expect people to have crypto 00:58:06.359 --> 00:58:08.329 align:start position:0% don't expect people to have crypto friends<00:58:06.540> and<00:58:06.960> to<00:58:07.140> rely<00:58:07.500> on<00:58:07.619> your<00:58:07.800> friends<00:58:07.980> but 00:58:08.329 --> 00:58:08.339 align:start position:0% friends and to rely on your friends but 00:58:08.339 --> 00:58:11.270 align:start position:0% friends and to rely on your friends but maybe<00:58:08.640> if<00:58:09.420> you're<00:58:09.660> a<00:58:09.960> more<00:58:10.260> crypto<00:58:10.619> expert<00:58:10.920> you 00:58:11.270 --> 00:58:11.280 align:start position:0% maybe if you're a more crypto expert you 00:58:11.280 --> 00:58:12.950 align:start position:0% maybe if you're a more crypto expert you may<00:58:11.760> just<00:58:11.940> want<00:58:12.059> to<00:58:12.119> use<00:58:12.240> a<00:58:12.359> hardware<00:58:12.480> wallet 00:58:12.950 --> 00:58:12.960 align:start position:0% may just want to use a hardware wallet 00:58:12.960 --> 00:58:14.569 align:start position:0% may just want to use a hardware wallet that<00:58:13.140> you<00:58:13.260> control<00:58:13.500> and<00:58:13.920> you<00:58:14.099> can<00:58:14.220> put<00:58:14.400> that 00:58:14.569 --> 00:58:14.579 align:start position:0% that you control and you can put that 00:58:14.579 --> 00:58:16.490 align:start position:0% that you control and you can put that you<00:58:14.760> know<00:58:14.819> in<00:58:14.940> a<00:58:15.059> safe<00:58:15.180> in<00:58:15.359> a<00:58:15.540> bank<00:58:15.660> and<00:58:16.380> if 00:58:16.490 --> 00:58:16.500 align:start position:0% you know in a safe in a bank and if 00:58:16.500 --> 00:58:18.290 align:start position:0% you know in a safe in a bank and if something<00:58:16.680> bad<00:58:16.920> happens<00:58:17.160> you<00:58:17.760> can<00:58:17.819> use<00:58:18.059> that 00:58:18.290 --> 00:58:18.300 align:start position:0% something bad happens you can use that 00:58:18.300 --> 00:58:19.609 align:start position:0% something bad happens you can use that that's<00:58:18.540> how<00:58:18.720> we<00:58:18.900> want<00:58:19.020> it<00:58:19.200> so<00:58:19.319> that's<00:58:19.440> one 00:58:19.609 --> 00:58:19.619 align:start position:0% that's how we want it so that's one 00:58:19.619 --> 00:58:22.910 align:start position:0% that's how we want it so that's one option<00:58:19.980> you<00:58:20.880> can<00:58:21.059> actually<00:58:21.599> give<00:58:22.020> that<00:58:22.260> key<00:58:22.500> to 00:58:22.910 --> 00:58:22.920 align:start position:0% option you can actually give that key to 00:58:22.920 --> 00:58:25.670 align:start position:0% option you can actually give that key to a<00:58:23.220> centralized<00:58:24.180> service<00:58:24.359> that<00:58:24.900> you<00:58:25.079> trust<00:58:25.319> but 00:58:25.670 --> 00:58:25.680 align:start position:0% a centralized service that you trust but 00:58:25.680 --> 00:58:27.230 align:start position:0% a centralized service that you trust but the<00:58:25.800> day<00:58:25.980> you<00:58:26.160> don't<00:58:26.280> trust<00:58:26.520> it<00:58:26.640> you<00:58:26.880> can<00:58:27.000> just 00:58:27.230 --> 00:58:27.240 align:start position:0% the day you don't trust it you can just 00:58:27.240 --> 00:58:30.170 align:start position:0% the day you don't trust it you can just remove<00:58:27.599> it<00:58:27.920> or<00:58:28.920> or<00:58:29.220> you<00:58:29.400> can<00:58:29.520> actually<00:58:29.700> combine 00:58:30.170 --> 00:58:30.180 align:start position:0% remove it or or you can actually combine 00:58:30.180 --> 00:58:32.210 align:start position:0% remove it or or you can actually combine so<00:58:30.480> you<00:58:30.720> can<00:58:30.839> you<00:58:31.140> can<00:58:31.319> use<00:58:31.500> a<00:58:31.680> centralized 00:58:32.210 --> 00:58:32.220 align:start position:0% so you can you can use a centralized 00:58:32.220 --> 00:58:34.609 align:start position:0% so you can you can use a centralized service<00:58:32.460> and<00:58:33.119> a<00:58:33.240> hardware<00:58:33.359> wallet<00:58:33.900> I<00:58:34.260> think<00:58:34.440> it 00:58:34.609 --> 00:58:34.619 align:start position:0% service and a hardware wallet I think it 00:58:34.619 --> 00:58:36.890 align:start position:0% service and a hardware wallet I think it really<00:58:34.740> depends<00:58:35.220> on<00:58:35.339> on<00:58:35.579> the<00:58:35.880> user<00:58:36.180> if<00:58:36.780> you 00:58:36.890 --> 00:58:36.900 align:start position:0% really depends on on the user if you 00:58:36.900 --> 00:58:39.410 align:start position:0% really depends on on the user if you have<00:58:37.079> fifty<00:58:37.380> dollars<00:58:37.680> it's<00:58:38.099> probably<00:58:38.339> okay<00:58:38.700> to 00:58:39.410 --> 00:58:39.420 align:start position:0% have fifty dollars it's probably okay to 00:58:39.420 --> 00:58:41.510 align:start position:0% have fifty dollars it's probably okay to give<00:58:39.660> that<00:58:40.079> recovery<00:58:40.859> key<00:58:41.040> you<00:58:41.280> know<00:58:41.339> that 00:58:41.510 --> 00:58:41.520 align:start position:0% give that recovery key you know that 00:58:41.520 --> 00:58:44.210 align:start position:0% give that recovery key you know that that<00:58:41.700> to<00:58:42.000> to<00:58:42.240> ask<00:58:42.480> is<00:58:42.839> is<00:58:43.380> centralized<00:58:44.099> service 00:58:44.210 --> 00:58:44.220 align:start position:0% that to to ask is is centralized service 00:58:44.220 --> 00:58:46.609 align:start position:0% that to to ask is is centralized service that<00:58:44.579> you<00:58:44.760> trust<00:58:45.240> to<00:58:45.720> act<00:58:45.900> as<00:58:46.020> your<00:58:46.260> guardian 00:58:46.609 --> 00:58:46.619 align:start position:0% that you trust to act as your guardian 00:58:46.619 --> 00:58:48.349 align:start position:0% that you trust to act as your guardian but<00:58:47.099> of<00:58:47.220> course<00:58:47.339> if<00:58:47.460> you<00:58:47.640> have<00:58:47.700> millions<00:58:48.059> that 00:58:48.349 --> 00:58:48.359 align:start position:0% but of course if you have millions that 00:58:48.359 --> 00:58:50.030 align:start position:0% but of course if you have millions that may<00:58:48.540> not<00:58:48.660> be<00:58:48.839> acceptable<00:58:49.200> so<00:58:49.500> you<00:58:49.680> may<00:58:49.740> want<00:58:49.920> to 00:58:50.030 --> 00:58:50.040 align:start position:0% may not be acceptable so you may want to 00:58:50.040 --> 00:58:51.530 align:start position:0% may not be acceptable so you may want to use<00:58:50.099> two<00:58:50.339> three<00:58:50.520> Hardware<00:58:50.760> wallets<00:58:51.240> that<00:58:51.420> you 00:58:51.530 --> 00:58:51.540 align:start position:0% use two three Hardware wallets that you 00:58:51.540 --> 00:58:53.569 align:start position:0% use two three Hardware wallets that you put<00:58:51.720> in<00:58:51.839> different<00:58:52.020> states<00:58:52.319> so<00:58:52.740> the<00:58:53.220> way<00:58:53.460> we 00:58:53.569 --> 00:58:53.579 align:start position:0% put in different states so the way we 00:58:53.579 --> 00:58:55.309 align:start position:0% put in different states so the way we see<00:58:53.760> is<00:58:53.880> that<00:58:54.059> recovery<00:58:54.540> is<00:58:54.660> really<00:58:54.900> a 00:58:55.309 --> 00:58:55.319 align:start position:0% see is that recovery is really a 00:58:55.319 --> 00:58:59.390 align:start position:0% see is that recovery is really a protocol<00:58:55.859> and<00:58:56.520> and<00:58:57.299> depending<00:58:58.140> on<00:58:58.380> users<00:58:58.859> we 00:58:59.390 --> 00:58:59.400 align:start position:0% protocol and and depending on users we 00:58:59.400 --> 00:59:01.130 align:start position:0% protocol and and depending on users we can<00:58:59.579> build<00:58:59.819> on<00:59:00.119> top<00:59:00.299> of<00:59:00.420> that<00:59:00.540> the<00:59:00.839> user 00:59:01.130 --> 00:59:01.140 align:start position:0% can build on top of that the user 00:59:01.140 --> 00:59:02.990 align:start position:0% can build on top of that the user experience<00:59:01.500> that<00:59:01.799> they<00:59:01.980> need<00:59:02.160> depending<00:59:02.760> on 00:59:02.990 --> 00:59:03.000 align:start position:0% experience that they need depending on 00:59:03.000 --> 00:59:04.849 align:start position:0% experience that they need depending on the<00:59:03.180> use<00:59:03.359> case<00:59:03.540> and<00:59:03.780> where<00:59:04.260> they<00:59:04.440> are<00:59:04.559> in<00:59:04.740> the 00:59:04.849 --> 00:59:04.859 align:start position:0% the use case and where they are in the 00:59:04.859 --> 00:59:07.010 align:start position:0% the use case and where they are in the in<00:59:05.040> the<00:59:05.220> crypto<00:59:05.520> Journey 00:59:07.010 --> 00:59:07.020 align:start position:0% in the crypto Journey 00:59:07.020 --> 00:59:09.170 align:start position:0% in the crypto Journey hi<00:59:07.380> my<00:59:07.559> question<00:59:07.799> is<00:59:07.980> for<00:59:08.160> Julian 00:59:09.170 --> 00:59:09.180 align:start position:0% hi my question is for Julian 00:59:09.180 --> 00:59:11.990 align:start position:0% hi my question is for Julian um<00:59:09.240> about<00:59:09.420> the<00:59:09.720> fraud<00:59:10.140> detection 00:59:11.990 --> 00:59:12.000 align:start position:0% um about the fraud detection 00:59:12.000 --> 00:59:15.289 align:start position:0% um about the fraud detection um<00:59:12.540> option<00:59:13.319> for 00:59:15.289 --> 00:59:15.299 align:start position:0% um option for 00:59:15.299 --> 00:59:16.609 align:start position:0% um option for um<00:59:15.359> the 00:59:16.609 --> 00:59:16.619 align:start position:0% um the 00:59:16.619 --> 00:59:20.630 align:start position:0% um the Urgent<00:59:16.799> wallet<00:59:17.220> and<00:59:18.059> my<00:59:18.540> question<00:59:18.660> is<00:59:19.020> does<00:59:19.920> it 00:59:20.630 --> 00:59:20.640 align:start position:0% Urgent wallet and my question is does it 00:59:20.640 --> 00:59:23.990 align:start position:0% Urgent wallet and my question is does it um<00:59:20.700> does<00:59:21.420> it<00:59:21.540> apply<00:59:21.900> to<00:59:22.020> mvv<00:59:22.859> type<00:59:23.520> attacks 00:59:23.990 --> 00:59:24.000 align:start position:0% um does it apply to mvv type attacks 00:59:24.000 --> 00:59:26.870 align:start position:0% um does it apply to mvv type attacks like<00:59:24.119> bot<00:59:24.780> Suites<00:59:25.079> for<00:59:25.260> example<00:59:25.559> where<00:59:25.980> if<00:59:26.700> a 00:59:26.870 --> 00:59:26.880 align:start position:0% like bot Suites for example where if a 00:59:26.880 --> 00:59:29.329 align:start position:0% like bot Suites for example where if a user<00:59:27.299> has<00:59:27.960> engaged<00:59:28.380> with<00:59:28.500> efficient<00:59:28.920> attempts 00:59:29.329 --> 00:59:29.339 align:start position:0% user has engaged with efficient attempts 00:59:29.339 --> 00:59:32.329 align:start position:0% user has engaged with efficient attempts and<00:59:30.180> then<00:59:30.359> every<00:59:31.260> transaction<00:59:31.740> after<00:59:31.980> that 00:59:32.329 --> 00:59:32.339 align:start position:0% and then every transaction after that 00:59:32.339 --> 00:59:34.250 align:start position:0% and then every transaction after that goes<00:59:32.700> to<00:59:32.819> a<00:59:33.359> multiplicity<00:59:33.900> of<00:59:34.079> different 00:59:34.250 --> 00:59:34.260 align:start position:0% goes to a multiplicity of different 00:59:34.260 --> 00:59:35.270 align:start position:0% goes to a multiplicity of different wallets 00:59:35.270 --> 00:59:35.280 align:start position:0% wallets 00:59:35.280 --> 00:59:36.470 align:start position:0% wallets uh 00:59:36.470 --> 00:59:36.480 align:start position:0% uh 00:59:36.480 --> 00:59:38.630 align:start position:0% uh would<00:59:37.079> that<00:59:37.260> feature<00:59:37.619> be<00:59:37.980> able<00:59:38.160> to<00:59:38.280> detect 00:59:38.630 --> 00:59:38.640 align:start position:0% would that feature be able to detect 00:59:38.640 --> 00:59:41.450 align:start position:0% would that feature be able to detect things<00:59:38.880> on<00:59:39.180> on<00:59:39.540> the<00:59:39.780> mvv<00:59:40.200> level<00:59:40.380> in<00:59:40.619> the<00:59:41.040> pool 00:59:41.450 --> 00:59:41.460 align:start position:0% things on on the mvv level in the pool 00:59:41.460 --> 00:59:44.390 align:start position:0% things on on the mvv level in the pool and<00:59:41.700> then<00:59:41.880> pull<00:59:42.559> that's<00:59:43.559> honestly<00:59:43.920> a<00:59:44.280> very 00:59:44.390 --> 00:59:44.400 align:start position:0% and then pull that's honestly a very 00:59:44.400 --> 00:59:46.010 align:start position:0% and then pull that's honestly a very good<00:59:44.579> question<00:59:44.880> and<00:59:45.299> something<00:59:45.480> we<00:59:45.900> haven't 00:59:46.010 --> 00:59:46.020 align:start position:0% good question and something we haven't 00:59:46.020 --> 00:59:47.990 align:start position:0% good question and something we haven't really<00:59:46.440> thought<00:59:46.740> about<00:59:46.980> so<00:59:47.579> just<00:59:47.700> to<00:59:47.880> make 00:59:47.990 --> 00:59:48.000 align:start position:0% really thought about so just to make 00:59:48.000 --> 00:59:49.309 align:start position:0% really thought about so just to make sure<00:59:48.059> understand<00:59:48.359> your<00:59:48.720> question<00:59:48.960> you're 00:59:49.309 --> 00:59:49.319 align:start position:0% sure understand your question you're 00:59:49.319 --> 00:59:51.829 align:start position:0% sure understand your question you're saying<00:59:49.619> if<00:59:49.799> we<00:59:49.980> enable<00:59:50.460> this<00:59:50.819> cosigner<00:59:51.599> for 00:59:51.829 --> 00:59:51.839 align:start position:0% saying if we enable this cosigner for 00:59:51.839 --> 00:59:54.770 align:start position:0% saying if we enable this cosigner for example<00:59:52.200> can<00:59:52.980> this<00:59:53.280> cosigner<00:59:53.940> anticipate 00:59:54.770 --> 00:59:54.780 align:start position:0% example can this cosigner anticipate 00:59:54.780 --> 00:59:56.770 align:start position:0% example can this cosigner anticipate some<00:59:55.020> kind<00:59:55.200> of<00:59:55.260> Mev<00:59:55.740> extraction 00:59:56.770 --> 00:59:56.780 align:start position:0% some kind of Mev extraction 00:59:56.780 --> 01:00:00.289 align:start position:0% some kind of Mev extraction I<00:59:57.780> guess<00:59:57.900> the<00:59:58.140> answer<00:59:58.260> is<00:59:58.500> probably<00:59:58.859> yes<00:59:59.299> but 01:00:00.289 --> 01:00:00.299 align:start position:0% I guess the answer is probably yes but 01:00:00.299 --> 01:00:01.670 align:start position:0% I guess the answer is probably yes but to<01:00:00.420> be<01:00:00.540> honest<01:00:00.720> we<01:00:00.900> haven't<01:00:01.020> researched<01:00:01.559> that 01:00:01.670 --> 01:00:01.680 align:start position:0% to be honest we haven't researched that 01:00:01.680 --> 01:00:03.530 align:start position:0% to be honest we haven't researched that yeah<01:00:02.099> so<01:00:02.520> that's<01:00:02.640> a<01:00:02.819> that's<01:00:03.059> a<01:00:03.240> good<01:00:03.359> question 01:00:03.530 --> 01:00:03.540 align:start position:0% yeah so that's a that's a good question 01:00:03.540 --> 01:00:06.530 align:start position:0% yeah so that's a that's a good question I<01:00:04.200> I<01:00:04.380> don't<01:00:04.559> see<01:00:04.680> why<01:00:04.859> not<01:00:05.119> because<01:00:06.119> based<01:00:06.480> on 01:00:06.530 --> 01:00:06.540 align:start position:0% I I don't see why not because based on 01:00:06.540 --> 01:00:07.910 align:start position:0% I I don't see why not because based on the<01:00:06.660> type<01:00:06.780> of<01:00:06.900> transaction<01:00:07.260> you<01:00:07.619> can<01:00:07.740> probably 01:00:07.910 --> 01:00:07.920 align:start position:0% the type of transaction you can probably 01:00:07.920 --> 01:00:10.970 align:start position:0% the type of transaction you can probably assume<01:00:08.460> that<01:00:08.579> some<01:00:08.760> Mev<01:00:09.180> will<01:00:09.359> happen<01:00:09.980> but 01:00:10.970 --> 01:00:10.980 align:start position:0% assume that some Mev will happen but 01:00:10.980 --> 01:00:12.710 align:start position:0% assume that some Mev will happen but yeah<01:00:11.339> that's<01:00:11.700> that's<01:00:12.000> an<01:00:12.240> interesting<01:00:12.599> point 01:00:12.710 --> 01:00:12.720 align:start position:0% yeah that's that's an interesting point 01:00:12.720 --> 01:00:13.970 align:start position:0% yeah that's that's an interesting point of<01:00:12.900> view<01:00:13.020> and<01:00:13.140> something<01:00:13.380> interesting<01:00:13.799> to 01:00:13.970 --> 01:00:13.980 align:start position:0% of view and something interesting to 01:00:13.980 --> 01:00:15.890 align:start position:0% of view and something interesting to research<01:00:14.400> I<01:00:15.059> don't<01:00:15.240> know<01:00:15.359> if<01:00:15.480> someone<01:00:15.660> else 01:00:15.890 --> 01:00:15.900 align:start position:0% research I don't know if someone else 01:00:15.900 --> 01:00:18.049 align:start position:0% research I don't know if someone else actually<01:00:16.260> a<01:00:16.559> smarter<01:00:16.859> answer<01:00:16.980> than<01:00:17.280> mine<01:00:17.579> to 01:00:18.049 --> 01:00:18.059 align:start position:0% actually a smarter answer than mine to 01:00:18.059 --> 01:00:21.109 align:start position:0% actually a smarter answer than mine to that<01:00:18.299> question<01:00:18.740> feel<01:00:19.740> free<01:00:19.920> to<01:00:20.099> shoot<01:00:20.280> really 01:00:21.109 --> 01:00:21.119 align:start position:0% that question feel free to shoot really 01:00:21.119 --> 01:00:25.130 align:start position:0% that question feel free to shoot really quick<01:00:21.359> one<01:00:21.540> about<01:00:21.839> MPC<01:00:22.680> wallets<01:00:23.099> so<01:00:23.839> the<01:00:24.839> use 01:00:25.130 --> 01:00:25.140 align:start position:0% quick one about MPC wallets so the use 01:00:25.140 --> 01:00:26.930 align:start position:0% quick one about MPC wallets so the use cases<01:00:25.440> that<01:00:25.680> you<01:00:25.859> describe<01:00:26.220> the<01:00:26.400> main<01:00:26.579> ones 01:00:26.930 --> 01:00:26.940 align:start position:0% cases that you describe the main ones 01:00:26.940 --> 01:00:30.950 align:start position:0% cases that you describe the main ones with<01:00:27.299> uh<01:00:27.980> multisigs<01:00:28.980> social<01:00:29.220> recovery 01:00:30.950 --> 01:00:30.960 align:start position:0% with uh multisigs social recovery 01:00:30.960 --> 01:00:34.250 align:start position:0% with uh multisigs social recovery can<01:00:31.440> be<01:00:32.000> solved<01:00:33.000> a<01:00:33.180> bit<01:00:33.299> in<01:00:33.540> a<01:00:33.720> bit<01:00:33.780> of<01:00:33.839> a<01:00:33.960> hacky 01:00:34.250 --> 01:00:34.260 align:start position:0% can be solved a bit in a bit of a hacky 01:00:34.260 --> 01:00:38.450 align:start position:0% can be solved a bit in a bit of a hacky way<01:00:34.440> with<01:00:35.119> MPC<01:00:36.119> EOS<01:00:36.960> like<01:00:37.740> the<01:00:37.859> one<01:00:38.040> that<01:00:38.280> I 01:00:38.450 --> 01:00:38.460 align:start position:0% way with MPC EOS like the one that I 01:00:38.460 --> 01:00:40.490 align:start position:0% way with MPC EOS like the one that I think<01:00:38.579> coinbase<01:00:38.940> wallet<01:00:39.359> is<01:00:39.480> working<01:00:39.660> on 01:00:40.490 --> 01:00:40.500 align:start position:0% think coinbase wallet is working on 01:00:40.500 --> 01:00:43.010 align:start position:0% think coinbase wallet is working on uh<01:00:41.160> is<01:00:41.460> that<01:00:41.640> good<01:00:41.940> or<01:00:42.119> bad<01:00:42.299> and<01:00:42.540> if<01:00:42.660> it's<01:00:42.839> bad 01:00:43.010 --> 01:00:43.020 align:start position:0% uh is that good or bad and if it's bad 01:00:43.020 --> 01:00:45.410 align:start position:0% uh is that good or bad and if it's bad what<01:00:43.260> do<01:00:43.440> we<01:00:43.500> do<01:00:43.619> about<01:00:43.740> it<01:00:43.980> I<01:00:44.700> mean<01:00:44.880> so<01:00:45.119> yeah 01:00:45.410 --> 01:00:45.420 align:start position:0% what do we do about it I mean so yeah 01:00:45.420 --> 01:00:49.549 align:start position:0% what do we do about it I mean so yeah like<01:00:46.020> one<01:00:46.380> specific<01:00:46.740> thing<01:00:47.099> that<01:00:47.640> uh<01:00:48.000> eeo<01:00:48.960> the 01:00:49.549 --> 01:00:49.559 align:start position:0% like one specific thing that uh eeo the 01:00:49.559 --> 01:00:51.710 align:start position:0% like one specific thing that uh eeo the MPC<01:00:50.160> approach<01:00:50.520> can't<01:00:50.760> solve<01:00:51.119> right<01:00:51.240> is<01:00:51.480> the 01:00:51.710 --> 01:00:51.720 align:start position:0% MPC approach can't solve right is the 01:00:51.720 --> 01:00:53.030 align:start position:0% MPC approach can't solve right is the key<01:00:51.839> is<01:00:51.960> key<01:00:52.140> changes<01:00:52.500> so<01:00:52.619> like<01:00:52.740> they<01:00:52.920> actually 01:00:53.030 --> 01:00:53.040 align:start position:0% key is key changes so like they actually 01:00:53.040 --> 01:00:54.890 align:start position:0% key is key changes so like they actually they<01:00:53.400> can't<01:00:53.640> really<01:00:53.819> solve<01:00:54.240> social<01:00:54.359> recovery 01:00:54.890 --> 01:00:54.900 align:start position:0% they can't really solve social recovery 01:00:54.900 --> 01:00:57.950 align:start position:0% they can't really solve social recovery well<01:00:55.140> right<01:00:55.440> and<01:00:56.160> the<01:00:56.339> reason<01:00:56.520> is<01:00:57.000> that<01:00:57.359> even 01:00:57.950 --> 01:00:57.960 align:start position:0% well right and the reason is that even 01:00:57.960 --> 01:01:02.569 align:start position:0% well right and the reason is that even if<01:00:58.500> you<01:00:59.220> take<01:01:00.180> your<01:01:00.599> key<01:01:01.559> and<01:01:01.980> you<01:01:02.160> split<01:01:02.460> it 01:01:02.569 --> 01:01:02.579 align:start position:0% if you take your key and you split it 01:01:02.579 --> 01:01:04.309 align:start position:0% if you take your key and you split it into<01:01:02.760> five<01:01:03.059> secret<01:01:03.299> shares<01:01:03.839> and<01:01:04.020> you<01:01:04.140> give 01:01:04.309 --> 01:01:04.319 align:start position:0% into five secret shares and you give 01:01:04.319 --> 01:01:06.470 align:start position:0% into five secret shares and you give each<01:01:04.500> year<01:01:04.740> to<01:01:04.980> one<01:01:05.220> of<01:01:05.400> your<01:01:05.460> friends<01:01:05.700> the 01:01:06.470 --> 01:01:06.480 align:start position:0% each year to one of your friends the 01:01:06.480 --> 01:01:09.410 align:start position:0% each year to one of your friends the yeah<01:01:06.720> the<01:01:07.140> problem<01:01:07.500> is<01:01:07.859> that<01:01:08.220> like<01:01:08.460> if<01:01:09.119> your 01:01:09.410 --> 01:01:09.420 align:start position:0% yeah the problem is that like if your 01:01:09.420 --> 01:01:11.569 align:start position:0% yeah the problem is that like if your friends<01:01:09.660> get<01:01:09.960> hacked<01:01:10.680> um<01:01:10.799> you<01:01:10.920> know<01:01:11.040> even<01:01:11.220> five 01:01:11.569 --> 01:01:11.579 align:start position:0% friends get hacked um you know even five 01:01:11.579 --> 01:01:13.130 align:start position:0% friends get hacked um you know even five years<01:01:11.760> later<01:01:11.940> like<01:01:12.299> there's<01:01:12.480> basically<01:01:12.900> no 01:01:13.130 --> 01:01:13.140 align:start position:0% years later like there's basically no 01:01:13.140 --> 01:01:14.569 align:start position:0% years later like there's basically no time<01:01:13.319> limit<01:01:13.500> you<01:01:13.740> have<01:01:13.859> no<01:01:14.040> way<01:01:14.160> to<01:01:14.280> revoke 01:01:14.569 --> 01:01:14.579 align:start position:0% time limit you have no way to revoke 01:01:14.579 --> 01:01:16.490 align:start position:0% time limit you have no way to revoke once<01:01:15.359> enough<01:01:15.480> of<01:01:15.660> them<01:01:15.839> get<01:01:16.020> hacked<01:01:16.319> they'll 01:01:16.490 --> 01:01:16.500 align:start position:0% once enough of them get hacked they'll 01:01:16.500 --> 01:01:18.170 align:start position:0% once enough of them get hacked they'll be<01:01:16.619> able<01:01:16.740> to<01:01:16.799> take<01:01:17.400> control<01:01:17.520> of<01:01:17.760> your<01:01:17.880> key<01:01:18.059> in 01:01:18.170 --> 01:01:18.180 align:start position:0% be able to take control of your key in 01:01:18.180 --> 01:01:20.270 align:start position:0% be able to take control of your key in your<01:01:18.359> account<01:01:18.480> right<01:01:18.780> so<01:01:18.900> that's<01:01:19.079> one<01:01:19.500> uh<01:01:20.099> very 01:01:20.270 --> 01:01:20.280 align:start position:0% your account right so that's one uh very 01:01:20.280 --> 01:01:21.829 align:start position:0% your account right so that's one uh very very<01:01:20.460> big<01:01:20.760> problem<01:01:21.000> and<01:01:21.420> then<01:01:21.540> another 01:01:21.829 --> 01:01:21.839 align:start position:0% very big problem and then another 01:01:21.839 --> 01:01:23.990 align:start position:0% very big problem and then another problem<01:01:22.319> is<01:01:23.040> that 01:01:23.990 --> 01:01:24.000 align:start position:0% problem is that 01:01:24.000 --> 01:01:26.510 align:start position:0% problem is that just<01:01:24.720> for<01:01:24.900> my<01:01:25.020> ux<01:01:25.380> perspective<01:01:25.920> that<01:01:26.280> kind<01:01:26.400> of 01:01:26.510 --> 01:01:26.520 align:start position:0% just for my ux perspective that kind of 01:01:26.520 --> 01:01:29.270 align:start position:0% just for my ux perspective that kind of approach<01:01:26.880> would<01:01:27.180> require<01:01:27.500> the<01:01:28.500> users<01:01:28.859> who 01:01:29.270 --> 01:01:29.280 align:start position:0% approach would require the users who 01:01:29.280 --> 01:01:31.370 align:start position:0% approach would require the users who participate<01:01:30.180> in<01:01:30.480> like<01:01:30.780> basically<01:01:31.079> it<01:01:31.200> will 01:01:31.370 --> 01:01:31.380 align:start position:0% participate in like basically it will 01:01:31.380 --> 01:01:32.930 align:start position:0% participate in like basically it will require<01:01:31.440> your<01:01:31.799> recovery<01:01:32.220> Partners<01:01:32.520> to<01:01:32.760> have 01:01:32.930 --> 01:01:32.940 align:start position:0% require your recovery Partners to have 01:01:32.940 --> 01:01:35.630 align:start position:0% require your recovery Partners to have custom<01:01:33.180> software<01:01:33.780> and<01:01:34.619> account<01:01:34.920> abstraction 01:01:35.630 --> 01:01:35.640 align:start position:0% custom software and account abstraction 01:01:35.640 --> 01:01:37.670 align:start position:0% custom software and account abstraction done<01:01:36.480> with<01:01:36.660> smart<01:01:36.839> contracts<01:01:37.319> is<01:01:37.440> like 01:01:37.670 --> 01:01:37.680 align:start position:0% done with smart contracts is like 01:01:37.680 --> 01:01:39.289 align:start position:0% done with smart contracts is like cleaner<01:01:38.040> because<01:01:38.220> it<01:01:38.940> doesn't<01:01:39.059> require 01:01:39.289 --> 01:01:39.299 align:start position:0% cleaner because it doesn't require 01:01:39.299 --> 01:01:40.970 align:start position:0% cleaner because it doesn't require custom<01:01:39.660> software<01:01:40.200> right<01:01:40.380> like<01:01:40.559> to<01:01:40.740> add<01:01:40.859> a 01:01:40.970 --> 01:01:40.980 align:start position:0% custom software right like to add a 01:01:40.980 --> 01:01:42.289 align:start position:0% custom software right like to add a bunch<01:01:41.099> of<01:01:41.160> recovery<01:01:41.520> Partners<01:01:41.819> you<01:01:42.059> know<01:01:42.180> you 01:01:42.289 --> 01:01:42.299 align:start position:0% bunch of recovery Partners you know you 01:01:42.299 --> 01:01:43.490 align:start position:0% bunch of recovery Partners you know you just<01:01:42.359> like<01:01:42.480> put<01:01:42.660> in<01:01:42.780> what<01:01:42.960> their<01:01:43.079> addresses 01:01:43.490 --> 01:01:43.500 align:start position:0% just like put in what their addresses 01:01:43.500 --> 01:01:46.370 align:start position:0% just like put in what their addresses are<01:01:43.680> and<01:01:43.980> so<01:01:44.220> like<01:01:44.819> it<01:01:45.059> whether<01:01:45.480> they<01:01:46.260> don't 01:01:46.370 --> 01:01:46.380 align:start position:0% are and so like it whether they don't 01:01:46.380 --> 01:01:48.950 align:start position:0% are and so like it whether they don't need<01:01:46.619> to<01:01:46.799> like<01:01:47.220> hold<01:01:47.700> some<01:01:48.180> separate<01:01:48.599> thing 01:01:48.950 --> 01:01:48.960 align:start position:0% need to like hold some separate thing 01:01:48.960 --> 01:01:51.109 align:start position:0% need to like hold some separate thing and<01:01:49.500> then<01:01:49.740> make<01:01:50.040> sure<01:01:50.099> that<01:01:50.339> some<01:01:50.579> some 01:01:51.109 --> 01:01:51.119 align:start position:0% and then make sure that some some 01:01:51.119 --> 01:01:52.730 align:start position:0% and then make sure that some some separate<01:01:51.540> thing<01:01:51.720> is<01:01:51.900> kept<01:01:52.200> safe<01:01:52.319> and<01:01:52.500> like 01:01:52.730 --> 01:01:52.740 align:start position:0% separate thing is kept safe and like 01:01:52.740 --> 01:01:54.230 align:start position:0% separate thing is kept safe and like accidentally<01:01:53.220> lose<01:01:53.460> it<01:01:53.700> because<01:01:53.880> the<01:01:54.119> only 01:01:54.230 --> 01:01:54.240 align:start position:0% accidentally lose it because the only 01:01:54.240 --> 01:01:56.030 align:start position:0% accidentally lose it because the only thing<01:01:54.480> they<01:01:54.599> ever<01:01:54.780> use<01:01:54.960> it<01:01:55.079> for<01:01:55.260> is<01:01:55.440> helping 01:01:56.030 --> 01:01:56.040 align:start position:0% thing they ever use it for is helping 01:01:56.040 --> 01:01:57.410 align:start position:0% thing they ever use it for is helping you<01:01:56.160> recover<01:01:56.460> your<01:01:56.700> accounts<01:01:57.059> and<01:01:57.180> they<01:01:57.299> just 01:01:57.410 --> 01:01:57.420 align:start position:0% you recover your accounts and they just 01:01:57.420 --> 01:01:59.089 align:start position:0% you recover your accounts and they just forget<01:01:57.599> this<01:01:58.260> is<01:01:58.380> something<01:01:58.559> that<01:01:58.799> once<01:01:58.980> you 01:01:59.089 --> 01:01:59.099 align:start position:0% forget this is something that once you 01:01:59.099 --> 01:02:00.770 align:start position:0% forget this is something that once you know<01:01:59.220> literally<01:01:59.520> happened<01:01:59.700> to<01:01:59.940> even<01:02:00.119> me<01:02:00.359> when 01:02:00.770 --> 01:02:00.780 align:start position:0% know literally happened to even me when 01:02:00.780 --> 01:02:03.470 align:start position:0% know literally happened to even me when I<01:02:00.960> yeah<01:02:01.140> was<01:02:01.559> using<01:02:01.980> the<01:02:02.220> HTC<01:02:02.880> Wallet<01:02:03.299> that<01:02:03.359> was 01:02:03.470 --> 01:02:03.480 align:start position:0% I yeah was using the HTC Wallet that was 01:02:03.480 --> 01:02:05.750 align:start position:0% I yeah was using the HTC Wallet that was using<01:02:03.720> NPC<01:02:04.079> recovery<01:02:04.500> by<01:02:04.680> the<01:02:04.799> way<01:02:04.859> right 01:02:05.750 --> 01:02:05.760 align:start position:0% using NPC recovery by the way right 01:02:05.760 --> 01:02:07.549 align:start position:0% using NPC recovery by the way right um<01:02:05.819> the<01:02:06.119> like<01:02:06.420> I<01:02:06.599> even<01:02:06.720> you<01:02:07.140> know<01:02:07.260> I<01:02:07.380> almost 01:02:07.549 --> 01:02:07.559 align:start position:0% um the like I even you know I almost 01:02:07.559 --> 01:02:09.589 align:start position:0% um the like I even you know I almost lost<01:02:07.920> it<01:02:08.160> because<01:02:08.339> a<01:02:08.640> couple<01:02:08.760> of<01:02:08.880> my<01:02:09.119> recovery 01:02:09.589 --> 01:02:09.599 align:start position:0% lost it because a couple of my recovery 01:02:09.599 --> 01:02:11.630 align:start position:0% lost it because a couple of my recovery friends<01:02:09.839> just<01:02:10.140> like<01:02:10.380> upgraded<01:02:11.099> their<01:02:11.280> phones 01:02:11.630 --> 01:02:11.640 align:start position:0% friends just like upgraded their phones 01:02:11.640 --> 01:02:13.849 align:start position:0% friends just like upgraded their phones and<01:02:11.819> you<01:02:11.940> know<01:02:12.059> forgot<01:02:12.420> to<01:02:12.540> upgrade<01:02:12.900> I<01:02:13.200> forgot 01:02:13.849 --> 01:02:13.859 align:start position:0% and you know forgot to upgrade I forgot 01:02:13.859 --> 01:02:15.829 align:start position:0% and you know forgot to upgrade I forgot to<01:02:14.040> carry<01:02:14.280> over<01:02:14.400> the<01:02:14.579> recovery<01:02:15.000> app 01:02:15.829 --> 01:02:15.839 align:start position:0% to carry over the recovery app 01:02:15.839 --> 01:02:18.650 align:start position:0% to carry over the recovery app um<01:02:15.960> so<01:02:16.319> like<01:02:17.160> those<01:02:17.520> are<01:02:17.700> the<01:02:17.940> two<01:02:18.180> problems 01:02:18.650 --> 01:02:18.660 align:start position:0% um so like those are the two problems 01:02:18.660 --> 01:02:21.230 align:start position:0% um so like those are the two problems that<01:02:19.020> you<01:02:19.260> know<01:02:19.319> at<01:02:19.559> least<01:02:19.680> uh<01:02:20.040> I<01:02:20.520> think<01:02:20.579> the 01:02:21.230 --> 01:02:21.240 align:start position:0% that you know at least uh I think the 01:02:21.240 --> 01:02:23.690 align:start position:0% that you know at least uh I think the smart<01:02:22.140> contract<01:02:22.559> based<01:02:23.220> approach<01:02:23.400> has<01:02:23.579> always 01:02:23.690 --> 01:02:23.700 align:start position:0% smart contract based approach has always 01:02:23.700 --> 01:02:25.130 align:start position:0% smart contract based approach has always better<01:02:23.940> and<01:02:24.359> then<01:02:24.540> also<01:02:24.780> just<01:02:24.960> like 01:02:25.130 --> 01:02:25.140 align:start position:0% better and then also just like 01:02:25.140 --> 01:02:27.890 align:start position:0% better and then also just like theoretical<01:02:25.920> cleanness<01:02:26.460> right<01:02:26.700> like<01:02:26.940> ecdsa 01:02:27.890 --> 01:02:27.900 align:start position:0% theoretical cleanness right like ecdsa 01:02:27.900 --> 01:02:29.930 align:start position:0% theoretical cleanness right like ecdsa is<01:02:28.079> just<01:02:28.319> a<01:02:28.559> fundamentally<01:02:29.280> bad<01:02:29.520> algorithm 01:02:29.930 --> 01:02:29.940 align:start position:0% is just a fundamentally bad algorithm 01:02:29.940 --> 01:02:32.089 align:start position:0% is just a fundamentally bad algorithm the<01:02:30.299> only<01:02:30.420> reason<01:02:30.660> it<01:02:30.900> has<01:02:31.140> any<01:02:31.440> prominence<01:02:31.859> at 01:02:32.089 --> 01:02:32.099 align:start position:0% the only reason it has any prominence at 01:02:32.099 --> 01:02:33.890 align:start position:0% the only reason it has any prominence at all<01:02:32.220> in<01:02:32.400> this<01:02:32.520> world<01:02:32.700> is<01:02:32.880> because<01:02:33.059> of<01:02:33.480> stupid 01:02:33.890 --> 01:02:33.900 align:start position:0% all in this world is because of stupid 01:02:33.900 --> 01:02:36.470 align:start position:0% all in this world is because of stupid stuff<01:02:34.200> involving<01:02:34.680> a<01:02:34.859> snore<01:02:35.099> patents<01:02:35.880> um<01:02:35.880> and 01:02:36.470 --> 01:02:36.480 align:start position:0% stuff involving a snore patents um and 01:02:36.480 --> 01:02:38.390 align:start position:0% stuff involving a snore patents um and you<01:02:36.780> know<01:02:36.839> it<01:02:36.960> was<01:02:37.079> ecdsa<01:02:37.740> was<01:02:37.920> invented<01:02:38.280> to 01:02:38.390 --> 01:02:38.400 align:start position:0% you know it was ecdsa was invented to 01:02:38.400 --> 01:02:39.710 align:start position:0% you know it was ecdsa was invented to just<01:02:38.579> get<01:02:38.700> a<01:02:38.880> basically<01:02:39.059> get<01:02:39.359> around<01:02:39.480> the 01:02:39.710 --> 01:02:39.720 align:start position:0% just get a basically get around the 01:02:39.720 --> 01:02:41.930 align:start position:0% just get a basically get around the patents<01:02:40.079> and<01:02:40.200> that<01:02:40.380> patent<01:02:40.680> has<01:02:40.980> expired 01:02:41.930 --> 01:02:41.940 align:start position:0% patents and that patent has expired 01:02:41.940 --> 01:02:44.750 align:start position:0% patents and that patent has expired years<01:02:42.119> ago<01:02:42.359> and<01:02:42.599> so<01:02:42.780> there's<01:02:43.020> a<01:02:43.319> and<01:02:43.740> ecdsa<01:02:44.520> has 01:02:44.750 --> 01:02:44.760 align:start position:0% years ago and so there's a and ecdsa has 01:02:44.760 --> 01:02:46.670 align:start position:0% years ago and so there's a and ecdsa has a<01:02:44.940> lot<01:02:45.000> of<01:02:45.119> like<01:02:45.240> bad<01:02:45.480> mathematical<01:02:46.079> quirks<01:02:46.559> to 01:02:46.670 --> 01:02:46.680 align:start position:0% a lot of like bad mathematical quirks to 01:02:46.680 --> 01:02:49.010 align:start position:0% a lot of like bad mathematical quirks to it<01:02:46.799> that<01:02:46.980> make<01:02:47.160> it<01:02:47.400> much<01:02:48.180> harder<01:02:48.480> than<01:02:48.660> needed 01:02:49.010 --> 01:02:49.020 align:start position:0% it that make it much harder than needed 01:02:49.020 --> 01:02:52.130 align:start position:0% it that make it much harder than needed to<01:02:49.200> MPC<01:02:49.740> and<01:02:50.099> uh<01:02:50.880> I<01:02:51.240> mean<01:02:51.359> you<01:02:51.660> know<01:02:51.780> much<01:02:51.960> more 01:02:52.130 --> 01:02:52.140 align:start position:0% to MPC and uh I mean you know much more 01:02:52.140 --> 01:02:53.750 align:start position:0% to MPC and uh I mean you know much more complicated<01:02:52.559> than<01:02:52.799> needed<01:02:53.160> and<01:02:53.339> though<01:02:53.520> like 01:02:53.750 --> 01:02:53.760 align:start position:0% complicated than needed and though like 01:02:53.760 --> 01:02:55.910 align:start position:0% complicated than needed and though like we<01:02:53.880> really<01:02:54.059> should<01:02:54.299> be<01:02:54.540> yeah<01:02:54.960> upgrading<01:02:55.680> to 01:02:55.910 --> 01:02:55.920 align:start position:0% we really should be yeah upgrading to 01:02:55.920 --> 01:02:58.849 align:start position:0% we really should be yeah upgrading to Schnur<01:02:56.339> or<01:02:57.000> um<01:02:57.000> or<01:02:57.599> other<01:02:57.780> things<01:02:58.020> anyway<01:02:58.319> and 01:02:58.849 --> 01:02:58.859 align:start position:0% Schnur or um or other things anyway and 01:02:58.859 --> 01:03:00.589 align:start position:0% Schnur or um or other things anyway and so<01:02:59.220> you<01:02:59.579> know<01:02:59.700> just<01:03:00.000> from<01:03:00.180> that<01:03:00.359> kind<01:03:00.480> of 01:03:00.589 --> 01:03:00.599 align:start position:0% so you know just from that kind of 01:03:00.599 --> 01:03:02.990 align:start position:0% so you know just from that kind of theoretical<01:03:01.020> Amino<01:03:01.440> trying<01:03:01.680> to<01:03:01.920> kind<01:03:02.579> of<01:03:02.700> make 01:03:02.990 --> 01:03:03.000 align:start position:0% theoretical Amino trying to kind of make 01:03:03.000 --> 01:03:05.750 align:start position:0% theoretical Amino trying to kind of make the<01:03:03.119> Asia<01:03:03.480> ecosystem<01:03:04.400> cleaner<01:03:05.400> overtime 01:03:05.750 --> 01:03:05.760 align:start position:0% the Asia ecosystem cleaner overtime 01:03:05.760 --> 01:03:07.910 align:start position:0% the Asia ecosystem cleaner overtime perspective<01:03:06.299> I<01:03:06.599> think<01:03:06.780> as<01:03:07.380> smart<01:03:07.559> culture 01:03:07.910 --> 01:03:07.920 align:start position:0% perspective I think as smart culture 01:03:07.920 --> 01:03:10.069 align:start position:0% perspective I think as smart culture quality<01:03:08.220> approach<01:03:08.400> is<01:03:08.579> better<01:03:08.700> so<01:03:08.940> like<01:03:09.180> for 01:03:10.069 --> 01:03:10.079 align:start position:0% quality approach is better so like for 01:03:10.079 --> 01:03:12.289 align:start position:0% quality approach is better so like for the<01:03:10.500> solving<01:03:10.920> dealing<01:03:11.339> with<01:03:11.460> people's<01:03:11.880> needs 01:03:12.289 --> 01:03:12.299 align:start position:0% the solving dealing with people's needs 01:03:12.299 --> 01:03:14.690 align:start position:0% the solving dealing with people's needs now<01:03:12.960> um<01:03:13.020> you<01:03:13.200> know<01:03:13.319> it's<01:03:13.619> definitely<01:03:14.280> valuable 01:03:14.690 --> 01:03:14.700 align:start position:0% now um you know it's definitely valuable 01:03:14.700 --> 01:03:16.670 align:start position:0% now um you know it's definitely valuable in<01:03:14.940> some<01:03:15.059> cases<01:03:15.359> but<01:03:15.599> I<01:03:15.720> do<01:03:15.839> think<01:03:16.020> there's<01:03:16.319> you 01:03:16.670 --> 01:03:16.680 align:start position:0% in some cases but I do think there's you 01:03:16.680 --> 01:03:19.309 align:start position:0% in some cases but I do think there's you know<01:03:16.799> value<01:03:16.980> in<01:03:17.280> and<01:03:17.940> like<01:03:18.119> like<01:03:18.480> there<01:03:19.140> are 01:03:19.309 --> 01:03:19.319 align:start position:0% know value in and like like there are 01:03:19.319 --> 01:03:21.170 align:start position:0% know value in and like like there are serious<01:03:19.680> value<01:03:19.859> ads<01:03:20.280> that<01:03:20.579> a<01:03:20.700> smart<01:03:20.819> contract 01:03:21.170 --> 01:03:21.180 align:start position:0% serious value ads that a smart contract 01:03:21.180 --> 01:03:23.870 align:start position:0% serious value ads that a smart contract based<01:03:21.540> approach<01:03:21.780> him<01:03:21.960> AdSense<01:03:22.319> up<01:03:22.559> yeah<01:03:23.280> and 01:03:23.870 --> 01:03:23.880 align:start position:0% based approach him AdSense up yeah and 01:03:23.880 --> 01:03:27.109 align:start position:0% based approach him AdSense up yeah and in<01:03:24.599> order<01:03:24.720> to<01:03:25.020> add<01:03:25.260> that<01:03:25.920> um<01:03:25.920> when<01:03:26.460> you're<01:03:26.640> that 01:03:27.109 --> 01:03:27.119 align:start position:0% in order to add that um when you're that 01:03:27.119 --> 01:03:31.010 align:start position:0% in order to add that um when you're that an<01:03:27.359> MPC<01:03:27.960> aims<01:03:28.859> to<01:03:29.040> solve<01:03:29.520> the<01:03:29.819> aims<01:03:30.660> to<01:03:30.780> solve 01:03:31.010 --> 01:03:31.020 align:start position:0% an MPC aims to solve the aims to solve 01:03:31.020 --> 01:03:33.650 align:start position:0% an MPC aims to solve the aims to solve maybe<01:03:31.200> a<01:03:31.440> recovery<01:03:32.040> or<01:03:32.520> managing<01:03:33.119> the<01:03:33.299> keys 01:03:33.650 --> 01:03:33.660 align:start position:0% maybe a recovery or managing the keys 01:03:33.660 --> 01:03:36.049 align:start position:0% maybe a recovery or managing the keys but<01:03:34.500> it<01:03:34.980> doesn't<01:03:35.099> give<01:03:35.339> you<01:03:35.520> things<01:03:35.760> like 01:03:36.049 --> 01:03:36.059 align:start position:0% but it doesn't give you things like 01:03:36.059 --> 01:03:39.349 align:start position:0% but it doesn't give you things like adding<01:03:36.540> a<01:03:36.720> policies<01:03:37.260> I<01:03:37.980> mean<01:03:38.160> you<01:03:38.640> can<01:03:38.819> uh<01:03:39.119> it 01:03:39.349 --> 01:03:39.359 align:start position:0% adding a policies I mean you can uh it 01:03:39.359 --> 01:03:40.910 align:start position:0% adding a policies I mean you can uh it helps<01:03:39.660> you<01:03:39.720> with<01:03:39.839> the<01:03:39.960> authentication<01:03:40.500> of<01:03:40.740> the 01:03:40.910 --> 01:03:40.920 align:start position:0% helps you with the authentication of the 01:03:40.920 --> 01:03:42.950 align:start position:0% helps you with the authentication of the account<01:03:41.040> but<01:03:41.460> nothing<01:03:41.700> else<01:03:42.000> and<01:03:42.599> there<01:03:42.780> are 01:03:42.950 --> 01:03:42.960 align:start position:0% account but nothing else and there are 01:03:42.960 --> 01:03:45.349 align:start position:0% account but nothing else and there are actually<01:03:43.079> NPC<01:03:43.799> there<01:03:44.220> are<01:03:44.339> some<01:03:44.460> NPC<01:03:44.940> wallets 01:03:45.349 --> 01:03:45.359 align:start position:0% actually NPC there are some NPC wallets 01:03:45.359 --> 01:03:47.750 align:start position:0% actually NPC there are some NPC wallets that<01:03:46.020> use<01:03:46.200> it<01:03:46.440> that<01:03:46.619> run<01:03:46.859> a<01:03:46.980> policy<01:03:47.339> on<01:03:47.579> a 01:03:47.750 --> 01:03:47.760 align:start position:0% that use it that run a policy on a 01:03:47.760 --> 01:03:49.430 align:start position:0% that use it that run a policy on a centralized<01:03:48.180> server<01:03:48.540> so<01:03:48.720> you<01:03:48.900> have<01:03:49.020> a<01:03:49.140> server 01:03:49.430 --> 01:03:49.440 align:start position:0% centralized server so you have a server 01:03:49.440 --> 01:03:52.069 align:start position:0% centralized server so you have a server participating<01:03:50.099> in<01:03:50.400> the<01:03:50.520> MPC<01:03:51.000> and<01:03:51.599> the<01:03:51.780> server 01:03:52.069 --> 01:03:52.079 align:start position:0% participating in the MPC and the server 01:03:52.079 --> 01:03:53.690 align:start position:0% participating in the MPC and the server will<01:03:52.319> make<01:03:52.500> sure<01:03:52.740> that<01:03:52.980> you<01:03:53.099> don't<01:03:53.280> do<01:03:53.520> certain 01:03:53.690 --> 01:03:53.700 align:start position:0% will make sure that you don't do certain 01:03:53.700 --> 01:03:55.789 align:start position:0% will make sure that you don't do certain things<01:03:54.059> but<01:03:54.720> this<01:03:54.839> means<01:03:55.140> that<01:03:55.260> the<01:03:55.440> policy 01:03:55.789 --> 01:03:55.799 align:start position:0% things but this means that the policy 01:03:55.799 --> 01:03:57.650 align:start position:0% things but this means that the policy management<01:03:55.980> is<01:03:56.460> done<01:03:56.640> off<01:03:56.940> chain<01:03:57.240> in<01:03:57.540> a 01:03:57.650 --> 01:03:57.660 align:start position:0% management is done off chain in a 01:03:57.660 --> 01:03:59.630 align:start position:0% management is done off chain in a centralized<01:03:58.140> way<01:03:58.319> and<01:03:58.920> I<01:03:59.040> think<01:03:59.160> being<01:03:59.339> able 01:03:59.630 --> 01:03:59.640 align:start position:0% centralized way and I think being able 01:03:59.640 --> 01:04:01.730 align:start position:0% centralized way and I think being able to<01:03:59.940> enforce<01:04:00.359> a<01:04:00.540> policy<01:04:00.900> on<01:04:01.079> chain<01:04:01.319> is<01:04:01.559> a 01:04:01.730 --> 01:04:01.740 align:start position:0% to enforce a policy on chain is a 01:04:01.740 --> 01:04:04.309 align:start position:0% to enforce a policy on chain is a powerful<01:04:02.040> thing<01:04:02.280> that<01:04:02.700> NPC<01:04:03.660> cannot<01:04:03.960> achieve 01:04:04.309 --> 01:04:04.319 align:start position:0% powerful thing that NPC cannot achieve 01:04:04.319 --> 01:04:07.190 align:start position:0% powerful thing that NPC cannot achieve hey<01:04:04.980> real<01:04:05.280> quick<01:04:05.400> question<01:04:06.020> that<01:04:07.020> that's 01:04:07.190 --> 01:04:07.200 align:start position:0% hey real quick question that that's 01:04:07.200 --> 01:04:08.870 align:start position:0% hey real quick question that that's actually<01:04:07.380> all<01:04:07.619> the<01:04:07.740> time<01:04:07.859> that<01:04:08.099> we<01:04:08.280> have<01:04:08.400> so<01:04:08.700> we 01:04:08.870 --> 01:04:08.880 align:start position:0% actually all the time that we have so we 01:04:08.880 --> 01:04:10.970 align:start position:0% actually all the time that we have so we have<01:04:09.059> to<01:04:09.119> sadly<01:04:09.480> that's<01:04:10.020> two<01:04:10.260> seconds<01:04:10.440> just 01:04:10.970 --> 01:04:10.980 align:start position:0% have to sadly that's two seconds just 01:04:10.980 --> 01:04:12.049 align:start position:0% have to sadly that's two seconds just real<01:04:11.280> quick 01:04:12.049 --> 01:04:12.059 align:start position:0% real quick 01:04:12.059 --> 01:04:13.609 align:start position:0% real quick just<01:04:12.540> wanted<01:04:12.780> to<01:04:12.960> ask<01:04:13.079> I'm<01:04:13.319> not<01:04:13.440> the<01:04:13.559> one 01:04:13.609 --> 01:04:13.619 align:start position:0% just wanted to ask I'm not the one 01:04:13.619 --> 01:04:15.710 align:start position:0% just wanted to ask I'm not the one writing<01:04:13.980> the<01:04:13.980> rules<01:04:14.220> I<01:04:14.400> don't<01:04:14.520> know<01:04:15.119> one<01:04:15.660> more 01:04:15.710 --> 01:04:15.720 align:start position:0% writing the rules I don't know one more 01:04:15.720 --> 01:04:17.630 align:start position:0% writing the rules I don't know one more all<01:04:16.020> right<01:04:16.140> cool<01:04:16.380> we're<01:04:16.920> good<01:04:17.099> we<01:04:17.400> can 01:04:17.630 --> 01:04:17.640 align:start position:0% all right cool we're good we can 01:04:17.640 --> 01:04:19.670 align:start position:0% all right cool we're good we can appreciate<01:04:18.359> that<01:04:18.540> that's<01:04:18.780> love<01:04:19.079> I'm<01:04:19.500> Russ 01:04:19.670 --> 01:04:19.680 align:start position:0% appreciate that that's love I'm Russ 01:04:19.680 --> 01:04:21.589 align:start position:0% appreciate that that's love I'm Russ from<01:04:19.980> 40<01:04:20.160> acres<01:04:20.520> now<01:04:20.760> we're<01:04:21.240> trying<01:04:21.420> to<01:04:21.540> create 01:04:21.589 --> 01:04:21.599 align:start position:0% from 40 acres now we're trying to create 01:04:21.599 --> 01:04:22.849 align:start position:0% from 40 acres now we're trying to create self-sustaining<01:04:22.319> communities<01:04:22.500> of<01:04:22.740> color 01:04:22.849 --> 01:04:22.859 align:start position:0% self-sustaining communities of color 01:04:22.859 --> 01:04:24.710 align:start position:0% self-sustaining communities of color utilizing<01:04:23.400> blockchain<01:04:23.819> and<01:04:24.420> obviously 01:04:24.710 --> 01:04:24.720 align:start position:0% utilizing blockchain and obviously 01:04:24.720 --> 01:04:26.210 align:start position:0% utilizing blockchain and obviously there's<01:04:24.960> a<01:04:25.140> lot<01:04:25.319> of<01:04:25.440> big<01:04:25.559> brains<01:04:25.980> in<01:04:26.099> the 01:04:26.210 --> 01:04:26.220 align:start position:0% there's a lot of big brains in the 01:04:26.220 --> 01:04:27.950 align:start position:0% there's a lot of big brains in the building<01:04:26.400> right<01:04:26.700> now<01:04:26.819> but<01:04:27.420> for<01:04:27.599> the<01:04:27.780> people 01:04:27.950 --> 01:04:27.960 align:start position:0% building right now but for the people 01:04:27.960 --> 01:04:29.990 align:start position:0% building right now but for the people that<01:04:28.319> have<01:04:28.500> no<01:04:28.859> idea<01:04:29.220> what<01:04:29.640> you're<01:04:29.760> talking 01:04:29.990 --> 01:04:30.000 align:start position:0% that have no idea what you're talking 01:04:30.000 --> 01:04:32.809 align:start position:0% that have no idea what you're talking about<01:04:30.359> I'm<01:04:31.020> super<01:04:31.319> curious<01:04:31.859> there<01:04:32.460> was<01:04:32.640> a 01:04:32.809 --> 01:04:32.819 align:start position:0% about I'm super curious there was a 01:04:32.819 --> 01:04:35.270 align:start position:0% about I'm super curious there was a wallet<01:04:33.180> out<01:04:33.359> and<01:04:34.079> you<01:04:34.319> could<01:04:34.440> aggregate<01:04:35.040> you 01:04:35.270 --> 01:04:35.280 align:start position:0% wallet out and you could aggregate you 01:04:35.280 --> 01:04:38.870 align:start position:0% wallet out and you could aggregate you could<01:04:35.400> use<01:04:35.579> D5<01:04:36.119> nft<01:04:36.740> marketplaces<01:04:37.880> I'm 01:04:38.870 --> 01:04:38.880 align:start position:0% could use D5 nft marketplaces I'm 01:04:38.880 --> 01:04:41.870 align:start position:0% could use D5 nft marketplaces I'm curious<01:04:39.500> is<01:04:40.500> there<01:04:40.740> space<01:04:41.099> for<01:04:41.400> things<01:04:41.579> and 01:04:41.870 --> 01:04:41.880 align:start position:0% curious is there space for things and 01:04:41.880 --> 01:04:43.750 align:start position:0% curious is there space for things and products<01:04:42.240> like<01:04:42.480> this<01:04:42.660> in<01:04:42.900> the<01:04:43.020> ethereum<01:04:43.380> space 01:04:43.750 --> 01:04:43.760 align:start position:0% products like this in the ethereum space 01:04:43.760 --> 01:04:46.130 align:start position:0% products like this in the ethereum space and<01:04:44.760> how<01:04:44.940> do<01:04:45.000> we<01:04:45.180> kind<01:04:45.420> of<01:04:45.480> aggregate<01:04:45.900> that 01:04:46.130 --> 01:04:46.140 align:start position:0% and how do we kind of aggregate that 01:04:46.140 --> 01:04:47.510 align:start position:0% and how do we kind of aggregate that information<01:04:46.380> for<01:04:46.920> people<01:04:47.040> who<01:04:47.280> don't<01:04:47.400> even 01:04:47.510 --> 01:04:47.520 align:start position:0% information for people who don't even 01:04:47.520 --> 01:04:49.490 align:start position:0% information for people who don't even know<01:04:47.700> what<01:04:47.880> a<01:04:48.059> smart<01:04:48.119> contract<01:04:48.599> is 01:04:49.490 --> 01:04:49.500 align:start position:0% know what a smart contract is 01:04:49.500 --> 01:04:52.069 align:start position:0% know what a smart contract is course<01:04:50.099> so<01:04:50.760> basically<01:04:51.180> there<01:04:51.480> was<01:04:51.599> a<01:04:51.720> wallet 01:04:52.069 --> 01:04:52.079 align:start position:0% course so basically there was a wallet 01:04:52.079 --> 01:04:54.470 align:start position:0% course so basically there was a wallet out<01:04:52.260> right<01:04:52.500> and<01:04:53.040> you<01:04:53.220> could<01:04:53.339> put<01:04:53.520> there<01:04:53.940> was<01:04:54.119> D5 01:04:54.470 --> 01:04:54.480 align:start position:0% out right and you could put there was D5 01:04:54.480 --> 01:04:56.750 align:start position:0% out right and you could put there was D5 protocols<01:04:55.260> in<01:04:55.500> it<01:04:55.680> there<01:04:56.099> was<01:04:56.339> nft 01:04:56.750 --> 01:04:56.760 align:start position:0% protocols in it there was nft 01:04:56.760 --> 01:05:00.170 align:start position:0% protocols in it there was nft marketplaces<01:04:57.599> All<01:04:57.960> in<01:04:58.200> One<01:04:58.500> Stop<01:04:58.859> Shop<01:04:59.280> and<01:05:00.000> so 01:05:00.170 --> 01:05:00.180 align:start position:0% marketplaces All in One Stop Shop and so 01:05:00.180 --> 01:05:02.809 align:start position:0% marketplaces All in One Stop Shop and so I'm<01:05:00.359> curious<01:05:00.780> is<01:05:01.319> are<01:05:01.740> there<01:05:01.920> other<01:05:02.160> products 01:05:02.809 --> 01:05:02.819 align:start position:0% I'm curious is are there other products 01:05:02.819 --> 01:05:04.849 align:start position:0% I'm curious is are there other products or<01:05:03.059> anything<01:05:03.420> like<01:05:03.780> this<01:05:03.960> being<01:05:04.200> built<01:05:04.740> again 01:05:04.849 --> 01:05:04.859 align:start position:0% or anything like this being built again 01:05:04.859 --> 01:05:07.730 align:start position:0% or anything like this being built again to<01:05:05.400> help<01:05:05.579> those<01:05:05.940> who<01:05:06.180> have<01:05:06.359> no<01:05:06.660> idea<01:05:07.020> what 01:05:07.730 --> 01:05:07.740 align:start position:0% to help those who have no idea what 01:05:07.740 --> 01:05:10.069 align:start position:0% to help those who have no idea what smart<01:05:07.980> contracts<01:05:08.520> are<01:05:08.760> those<01:05:09.359> who<01:05:09.599> just<01:05:09.780> need 01:05:10.069 --> 01:05:10.079 align:start position:0% smart contracts are those who just need 01:05:10.079 --> 01:05:12.470 align:start position:0% smart contracts are those who just need this<01:05:10.500> information<01:05:10.799> the<01:05:11.280> most 01:05:12.470 --> 01:05:12.480 align:start position:0% this information the most 01:05:12.480 --> 01:05:14.630 align:start position:0% this information the most yeah<01:05:12.720> I<01:05:12.960> think<01:05:13.260> smart<01:05:13.440> contract<01:05:13.799> wallets<01:05:14.220> are 01:05:14.630 --> 01:05:14.640 align:start position:0% yeah I think smart contract wallets are 01:05:14.640 --> 01:05:17.690 align:start position:0% yeah I think smart contract wallets are how<01:05:14.880> we<01:05:15.059> get<01:05:15.240> to<01:05:15.420> a<01:05:15.599> point<01:05:15.780> where<01:05:16.220> uh<01:05:17.220> we<01:05:17.520> have 01:05:17.690 --> 01:05:17.700 align:start position:0% how we get to a point where uh we have 01:05:17.700 --> 01:05:20.569 align:start position:0% how we get to a point where uh we have just<01:05:18.059> intuitive<01:05:18.960> ux<01:05:19.380> and<01:05:19.859> so<01:05:20.040> you<01:05:20.339> can<01:05:20.400> just 01:05:20.569 --> 01:05:20.579 align:start position:0% just intuitive ux and so you can just 01:05:20.579 --> 01:05:22.010 align:start position:0% just intuitive ux and so you can just like<01:05:20.819> uh<01:05:21.240> there's<01:05:21.480> something<01:05:21.599> called<01:05:21.839> like 01:05:22.010 --> 01:05:22.020 align:start position:0% like uh there's something called like 01:05:22.020 --> 01:05:23.450 align:start position:0% like uh there's something called like the<01:05:22.140> grandma<01:05:22.319> test<01:05:22.680> where<01:05:22.980> if<01:05:23.099> you<01:05:23.220> can<01:05:23.339> give 01:05:23.450 --> 01:05:23.460 align:start position:0% the grandma test where if you can give 01:05:23.460 --> 01:05:25.130 align:start position:0% the grandma test where if you can give your<01:05:23.640> grandma<01:05:23.760> the<01:05:24.119> thing<01:05:24.480> and<01:05:24.660> she<01:05:24.839> can<01:05:24.960> do<01:05:25.020> it 01:05:25.130 --> 01:05:25.140 align:start position:0% your grandma the thing and she can do it 01:05:25.140 --> 01:05:27.109 align:start position:0% your grandma the thing and she can do it then<01:05:25.319> it<01:05:25.440> passes<01:05:25.740> the<01:05:25.859> ux<01:05:26.160> test<01:05:26.339> and<01:05:26.940> smart 01:05:27.109 --> 01:05:27.119 align:start position:0% then it passes the ux test and smart 01:05:27.119 --> 01:05:29.630 align:start position:0% then it passes the ux test and smart contract<01:05:27.480> walls<01:05:27.839> are<01:05:28.020> how<01:05:28.200> we<01:05:28.319> get<01:05:28.500> there<01:05:28.680> and 01:05:29.630 --> 01:05:29.640 align:start position:0% contract walls are how we get there and 01:05:29.640 --> 01:05:32.390 align:start position:0% contract walls are how we get there and so<01:05:29.880> just<01:05:30.660> like<01:05:30.839> things<01:05:31.500> to<01:05:32.099> make<01:05:32.220> things 01:05:32.390 --> 01:05:32.400 align:start position:0% so just like things to make things 01:05:32.400 --> 01:05:34.789 align:start position:0% so just like things to make things intuitive<01:05:32.940> to<01:05:33.599> get<01:05:33.960> rid<01:05:34.079> of<01:05:34.260> like<01:05:34.440> the<01:05:34.619> whole 01:05:34.789 --> 01:05:34.799 align:start position:0% intuitive to get rid of like the whole 01:05:34.799 --> 01:05:36.890 align:start position:0% intuitive to get rid of like the whole like<01:05:35.040> signing<01:05:35.520> with<01:05:35.940> a<01:05:36.119> private<01:05:36.420> key<01:05:36.540> and 01:05:36.890 --> 01:05:36.900 align:start position:0% like signing with a private key and 01:05:36.900 --> 01:05:38.930 align:start position:0% like signing with a private key and doing<01:05:37.440> and<01:05:37.680> making<01:05:37.920> wallets<01:05:38.280> behave<01:05:38.579> in<01:05:38.760> the 01:05:38.930 --> 01:05:38.940 align:start position:0% doing and making wallets behave in the 01:05:38.940 --> 01:05:40.910 align:start position:0% doing and making wallets behave in the way<01:05:39.059> that<01:05:39.359> we<01:05:39.839> expect<01:05:40.020> them<01:05:40.319> to<01:05:40.500> just<01:05:40.740> as 01:05:40.910 --> 01:05:40.920 align:start position:0% way that we expect them to just as 01:05:40.920 --> 01:05:42.890 align:start position:0% way that we expect them to just as humans<01:05:41.339> smart<01:05:41.880> contracts<01:05:42.299> wallets<01:05:42.599> are<01:05:42.780> how 01:05:42.890 --> 01:05:42.900 align:start position:0% humans smart contracts wallets are how 01:05:42.900 --> 01:05:45.109 align:start position:0% humans smart contracts wallets are how we<01:05:43.020> get<01:05:43.200> there<01:05:43.380> and<01:05:43.740> so<01:05:43.980> I'd<01:05:44.520> say<01:05:44.700> that<01:05:44.880> smart 01:05:45.109 --> 01:05:45.119 align:start position:0% we get there and so I'd say that smart 01:05:45.119 --> 01:05:46.069 align:start position:0% we get there and so I'd say that smart contracts<01:05:45.420> wallets<01:05:45.720> are<01:05:45.839> kind<01:05:45.960> of<01:05:46.020> how 01:05:46.069 --> 01:05:46.079 align:start position:0% contracts wallets are kind of how 01:05:46.079 --> 01:05:47.510 align:start position:0% contracts wallets are kind of how ethereum<01:05:46.500> kind<01:05:46.680> of<01:05:46.740> fits<01:05:46.980> into<01:05:47.040> every<01:05:47.339> single 01:05:47.510 --> 01:05:47.520 align:start position:0% ethereum kind of fits into every single 01:05:47.520 --> 01:05:49.849 align:start position:0% ethereum kind of fits into every single corner<01:05:47.819> of<01:05:47.880> the<01:05:48.000> internet<01:05:48.319> and<01:05:49.319> it's<01:05:49.559> because 01:05:49.849 --> 01:05:49.859 align:start position:0% corner of the internet and it's because 01:05:49.859 --> 01:05:53.390 align:start position:0% corner of the internet and it's because we<01:05:50.339> find<01:05:50.700> ways<01:05:51.180> to<01:05:51.540> hook<01:05:51.900> ethereum<01:05:52.440> into<01:05:52.799> some 01:05:53.390 --> 01:05:53.400 align:start position:0% we find ways to hook ethereum into some 01:05:53.400 --> 01:05:55.670 align:start position:0% we find ways to hook ethereum into some sort<01:05:53.520> of<01:05:53.640> web3<01:05:54.000> app<01:05:54.299> game<01:05:54.720> nft<01:05:55.079> Marketplace 01:05:55.670 --> 01:05:55.680 align:start position:0% sort of web3 app game nft Marketplace 01:05:55.680 --> 01:05:58.250 align:start position:0% sort of web3 app game nft Marketplace and<01:05:56.220> it<01:05:56.400> doesn't<01:05:56.579> feel<01:05:57.059> like<01:05:57.299> ethereum<01:05:57.900> it 01:05:58.250 --> 01:05:58.260 align:start position:0% and it doesn't feel like ethereum it 01:05:58.260 --> 01:06:00.349 align:start position:0% and it doesn't feel like ethereum it just<01:05:58.440> feels<01:05:58.680> like<01:05:58.799> the<01:05:59.099> internet<01:05:59.280> and<01:06:00.119> that's 01:06:00.349 --> 01:06:00.359 align:start position:0% just feels like the internet and that's 01:06:00.359 --> 01:06:01.789 align:start position:0% just feels like the internet and that's and<01:06:00.540> smart<01:06:00.780> contract<01:06:01.140> wallets<01:06:01.500> are 01:06:01.789 --> 01:06:01.799 align:start position:0% and smart contract wallets are 01:06:01.799 --> 01:06:03.410 align:start position:0% and smart contract wallets are definitely<01:06:02.280> how<01:06:02.400> we<01:06:02.520> get<01:06:02.640> there<01:06:02.819> I<01:06:03.119> hope<01:06:03.240> that 01:06:03.410 --> 01:06:03.420 align:start position:0% definitely how we get there I hope that 01:06:03.420 --> 01:06:07.020 align:start position:0% definitely how we get there I hope that answered<01:06:03.720> your<01:06:03.780> question<01:06:03.960> cool<01:06:04.380> thanks<01:06:04.559> guys 01:06:07.020 --> 01:06:07.030 align:start position:0% 01:06:07.030 --> 01:06:10.159 align:start position:0% [Applause]