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:18.250 align:start position:0% [Music] 00:00:18.250 --> 00:00:18.260 align:start position:0% 00:00:18.260 --> 00:00:21.230 align:start position:0% is<00:00:19.260> kind<00:00:19.380> of<00:00:19.440> a<00:00:19.560> challenge<00:00:19.740> but<00:00:20.279> hopefully 00:00:21.230 --> 00:00:21.240 align:start position:0% is kind of a challenge but hopefully 00:00:21.240 --> 00:00:22.670 align:start position:0% is kind of a challenge but hopefully we'll<00:00:21.420> make<00:00:21.600> it<00:00:21.779> fun 00:00:22.670 --> 00:00:22.680 align:start position:0% we'll make it fun 00:00:22.680 --> 00:00:24.890 align:start position:0% we'll make it fun so<00:00:22.980> my<00:00:23.100> name<00:00:23.220> is<00:00:23.279> julianize<00:00:23.880> I'm<00:00:24.480> one<00:00:24.660> of<00:00:24.779> the 00:00:24.890 --> 00:00:24.900 align:start position:0% so my name is julianize I'm one of the 00:00:24.900 --> 00:00:27.650 align:start position:0% so my name is julianize I'm one of the three<00:00:25.019> co-founder<00:00:25.619> at<00:00:25.800> Arjun<00:00:26.300> and<00:00:27.300> this 00:00:27.650 --> 00:00:27.660 align:start position:0% three co-founder at Arjun and this 00:00:27.660 --> 00:00:28.790 align:start position:0% three co-founder at Arjun and this morning<00:00:27.840> I'll<00:00:28.080> be<00:00:28.260> talking<00:00:28.380> about<00:00:28.560> account 00:00:28.790 --> 00:00:28.800 align:start position:0% morning I'll be talking about account 00:00:28.800 --> 00:00:31.550 align:start position:0% morning I'll be talking about account abstraction<00:00:29.400> why<00:00:30.300> it's<00:00:30.480> it's<00:00:30.779> a<00:00:30.960> game<00:00:31.080> changer 00:00:31.550 --> 00:00:31.560 align:start position:0% abstraction why it's it's a game changer 00:00:31.560 --> 00:00:35.030 align:start position:0% abstraction why it's it's a game changer for<00:00:31.859> the<00:00:31.980> ux<00:00:32.279> of<00:00:32.520> of<00:00:32.759> dapps<00:00:33.300> but<00:00:33.899> I<00:00:34.079> think<00:00:34.260> uh<00:00:34.559> an 00:00:35.030 --> 00:00:35.040 align:start position:0% for the ux of of dapps but I think uh an 00:00:35.040 --> 00:00:37.430 align:start position:0% for the ux of of dapps but I think uh an alternative<00:00:35.399> title<00:00:35.940> of<00:00:36.120> my<00:00:36.420> talk<00:00:36.780> could<00:00:37.140> it<00:00:37.320> be 00:00:37.430 --> 00:00:37.440 align:start position:0% alternative title of my talk could it be 00:00:37.440 --> 00:00:40.069 align:start position:0% alternative title of my talk could it be how<00:00:37.680> to<00:00:37.860> scale<00:00:38.100> self-care<00:00:38.579> study<00:00:38.940> so<00:00:39.780> let<00:00:39.960> me 00:00:40.069 --> 00:00:40.079 align:start position:0% how to scale self-care study so let me 00:00:40.079 --> 00:00:41.590 align:start position:0% how to scale self-care study so let me start<00:00:40.260> with<00:00:40.440> a<00:00:40.620> pretty<00:00:40.800> obvious<00:00:41.160> statement 00:00:41.590 --> 00:00:41.600 align:start position:0% start with a pretty obvious statement 00:00:41.600 --> 00:00:43.850 align:start position:0% start with a pretty obvious statement and<00:00:42.600> I<00:00:42.780> hope<00:00:42.899> we<00:00:43.079> all<00:00:43.200> agree<00:00:43.379> in<00:00:43.559> this<00:00:43.680> room 00:00:43.850 --> 00:00:43.860 align:start position:0% and I hope we all agree in this room 00:00:43.860 --> 00:00:46.549 align:start position:0% and I hope we all agree in this room that<00:00:44.280> self-cue<00:00:44.879> study<00:00:45.239> matters<00:00:46.079> right 00:00:46.549 --> 00:00:46.559 align:start position:0% that self-cue study matters right 00:00:46.559 --> 00:00:49.130 align:start position:0% that self-cue study matters right blockchain<00:00:47.100> is<00:00:47.340> an<00:00:47.520> amazing<00:00:47.820> technology<00:00:48.300> that 00:00:49.130 --> 00:00:49.140 align:start position:0% blockchain is an amazing technology that 00:00:49.140 --> 00:00:50.750 align:start position:0% blockchain is an amazing technology that for<00:00:49.379> the<00:00:49.559> first<00:00:49.620> time<00:00:49.800> can<00:00:50.100> enable<00:00:50.399> true 00:00:50.750 --> 00:00:50.760 align:start position:0% for the first time can enable true 00:00:50.760 --> 00:00:53.630 align:start position:0% for the first time can enable true digital<00:00:51.120> ownership<00:00:51.620> but<00:00:52.620> of<00:00:52.800> course<00:00:52.920> you 00:00:53.630 --> 00:00:53.640 align:start position:0% digital ownership but of course you 00:00:53.640 --> 00:00:55.010 align:start position:0% digital ownership but of course you don't<00:00:53.760> really<00:00:53.940> own<00:00:54.120> an<00:00:54.300> asset<00:00:54.660> if<00:00:54.780> you<00:00:54.899> give 00:00:55.010 --> 00:00:55.020 align:start position:0% don't really own an asset if you give 00:00:55.020 --> 00:00:57.290 align:start position:0% don't really own an asset if you give coustative<00:00:55.559> to<00:00:56.460> someone<00:00:56.579> else<00:00:56.760> to<00:00:57.000> a<00:00:57.180> third 00:00:57.290 --> 00:00:57.300 align:start position:0% coustative to someone else to a third 00:00:57.300 --> 00:00:58.310 align:start position:0% coustative to someone else to a third party 00:00:58.310 --> 00:00:58.320 align:start position:0% party 00:00:58.320 --> 00:01:00.590 align:start position:0% party and<00:00:58.860> I<00:00:58.980> think<00:00:59.100> the<00:00:59.280> the<00:00:59.460> recent<00:00:59.820> event<00:01:00.059> of<00:01:00.420> of 00:01:00.590 --> 00:01:00.600 align:start position:0% and I think the the recent event of of 00:01:00.600 --> 00:01:02.450 align:start position:0% and I think the the recent event of of this<00:01:00.899> summer<00:01:01.079> with<00:01:01.860> the<00:01:01.980> problem<00:01:02.160> with 00:01:02.450 --> 00:01:02.460 align:start position:0% this summer with the problem with 00:01:02.460 --> 00:01:04.850 align:start position:0% this summer with the problem with Celsius<00:01:02.699> is<00:01:03.059> kind<00:01:03.359> of<00:01:03.480> a<00:01:03.719> good<00:01:04.199> wake-up<00:01:04.619> call 00:01:04.850 --> 00:01:04.860 align:start position:0% Celsius is kind of a good wake-up call 00:01:04.860 --> 00:01:08.030 align:start position:0% Celsius is kind of a good wake-up call of<00:01:05.159> what<00:01:05.700> bad<00:01:06.180> things<00:01:06.420> can<00:01:06.780> happen<00:01:06.960> if<00:01:07.500> we<00:01:07.740> rely 00:01:08.030 --> 00:01:08.040 align:start position:0% of what bad things can happen if we rely 00:01:08.040 --> 00:01:10.250 align:start position:0% of what bad things can happen if we rely on<00:01:08.220> custodial<00:01:08.700> Solutions 00:01:10.250 --> 00:01:10.260 align:start position:0% on custodial Solutions 00:01:10.260 --> 00:01:12.230 align:start position:0% on custodial Solutions but<00:01:10.680> of<00:01:10.799> course<00:01:10.920> we<00:01:11.159> all<00:01:11.280> know<00:01:11.400> that<00:01:11.700> self-key 00:01:12.230 --> 00:01:12.240 align:start position:0% but of course we all know that self-key 00:01:12.240 --> 00:01:15.350 align:start position:0% but of course we all know that self-key study<00:01:12.720> is<00:01:13.439> hard<00:01:13.680> right<00:01:14.100> if<00:01:14.400> we<00:01:14.520> look<00:01:14.640> at<00:01:14.880> crypto 00:01:15.350 --> 00:01:15.360 align:start position:0% study is hard right if we look at crypto 00:01:15.360 --> 00:01:16.250 align:start position:0% study is hard right if we look at crypto Twitter 00:01:16.250 --> 00:01:16.260 align:start position:0% Twitter 00:01:16.260 --> 00:01:18.649 align:start position:0% Twitter we'll<00:01:16.799> see<00:01:17.100> everyday<00:01:17.400> users<00:01:18.240> you<00:01:18.600> know 00:01:18.649 --> 00:01:18.659 align:start position:0% we'll see everyday users you know 00:01:18.659 --> 00:01:20.929 align:start position:0% we'll see everyday users you know explaining<00:01:19.560> how<00:01:19.799> they<00:01:19.979> lost<00:01:20.159> access<00:01:20.460> to<00:01:20.759> their 00:01:20.929 --> 00:01:20.939 align:start position:0% explaining how they lost access to their 00:01:20.939 --> 00:01:24.109 align:start position:0% explaining how they lost access to their assets<00:01:21.240> or<00:01:21.540> the<00:01:21.900> assets<00:01:22.200> got<00:01:22.500> got<00:01:22.860> stolen<00:01:23.460> and 00:01:24.109 --> 00:01:24.119 align:start position:0% assets or the assets got got stolen and 00:01:24.119 --> 00:01:26.030 align:start position:0% assets or the assets got got stolen and I<00:01:24.180> mean<00:01:24.360> sometimes<00:01:25.080> these<00:01:25.380> people<00:01:25.500> are<00:01:25.740> are 00:01:26.030 --> 00:01:26.040 align:start position:0% I mean sometimes these people are are 00:01:26.040 --> 00:01:28.429 align:start position:0% I mean sometimes these people are are expert<00:01:26.460> if<00:01:27.180> you<00:01:27.240> look<00:01:27.360> at<00:01:27.540> the<00:01:27.659> tweet<00:01:27.960> on<00:01:28.140> the 00:01:28.429 --> 00:01:28.439 align:start position:0% expert if you look at the tweet on the 00:01:28.439 --> 00:01:31.310 align:start position:0% expert if you look at the tweet on the top<00:01:28.560> right<00:01:28.799> it<00:01:29.040> comes<00:01:29.280> from<00:01:29.400> huge<00:01:29.820> yoga<00:01:30.659> of<00:01:30.960> the 00:01:31.310 --> 00:01:31.320 align:start position:0% top right it comes from huge yoga of the 00:01:31.320 --> 00:01:33.830 align:start position:0% top right it comes from huge yoga of the founder<00:01:31.619> of<00:01:31.740> a<00:01:31.979> well-known<00:01:32.280> D5<00:01:32.700> project<00:01:33.060> so 00:01:33.830 --> 00:01:33.840 align:start position:0% founder of a well-known D5 project so 00:01:33.840 --> 00:01:37.069 align:start position:0% founder of a well-known D5 project so even<00:01:34.080> expert<00:01:34.619> are<00:01:34.920> making<00:01:35.100> mistake<00:01:35.640> and<00:01:36.420> are 00:01:37.069 --> 00:01:37.079 align:start position:0% even expert are making mistake and are 00:01:37.079 --> 00:01:38.450 align:start position:0% even expert are making mistake and are basically<00:01:37.439> struggling<00:01:37.920> with<00:01:38.220> with 00:01:38.450 --> 00:01:38.460 align:start position:0% basically struggling with with 00:01:38.460 --> 00:01:40.010 align:start position:0% basically struggling with with self-custody 00:01:40.010 --> 00:01:40.020 align:start position:0% self-custody 00:01:40.020 --> 00:01:42.950 align:start position:0% self-custody so<00:01:40.560> the<00:01:40.740> question<00:01:40.860> is<00:01:41.220> why<00:01:41.939> circus<00:01:42.360> studies<00:01:42.720> so 00:01:42.950 --> 00:01:42.960 align:start position:0% so the question is why circus studies so 00:01:42.960 --> 00:01:44.030 align:start position:0% so the question is why circus studies so hard 00:01:44.030 --> 00:01:44.040 align:start position:0% hard 00:01:44.040 --> 00:01:47.149 align:start position:0% hard right<00:01:44.640> and<00:01:44.939> and<00:01:45.119> we<00:01:46.020> believe<00:01:46.140> that<00:01:46.380> Arjun<00:01:46.860> that 00:01:47.149 --> 00:01:47.159 align:start position:0% right and and we believe that Arjun that 00:01:47.159 --> 00:01:49.910 align:start position:0% right and and we believe that Arjun that the<00:01:47.400> problem<00:01:47.579> lies<00:01:48.180> in<00:01:49.079> how<00:01:49.320> ethereum 00:01:49.910 --> 00:01:49.920 align:start position:0% the problem lies in how ethereum 00:01:49.920 --> 00:01:52.609 align:start position:0% the problem lies in how ethereum accounts<00:01:50.399> were<00:01:50.640> a<00:01:50.820> design<00:01:51.140> uh<00:01:52.140> at<00:01:52.500> the 00:01:52.609 --> 00:01:52.619 align:start position:0% accounts were a design uh at the 00:01:52.619 --> 00:01:54.469 align:start position:0% accounts were a design uh at the beginning<00:01:52.680> of<00:01:52.979> of<00:01:53.159> ethereum<00:01:53.640> it<00:01:53.820> really<00:01:54.180> lies 00:01:54.469 --> 00:01:54.479 align:start position:0% beginning of of ethereum it really lies 00:01:54.479 --> 00:01:58.190 align:start position:0% beginning of of ethereum it really lies at<00:01:54.659> the<00:01:54.780> heart<00:01:54.960> of<00:01:55.259> of<00:01:55.500> the<00:01:55.860> evm<00:01:56.340> so<00:01:57.180> let<00:01:57.540> me<00:01:57.720> dig 00:01:58.190 --> 00:01:58.200 align:start position:0% at the heart of of the evm so let me dig 00:01:58.200 --> 00:01:59.749 align:start position:0% at the heart of of the evm so let me dig a<00:01:58.380> little<00:01:58.500> bit<00:01:58.619> into<00:01:58.740> ethereum<00:01:59.280> account<00:01:59.460> to 00:01:59.749 --> 00:01:59.759 align:start position:0% a little bit into ethereum account to 00:01:59.759 --> 00:02:02.810 align:start position:0% a little bit into ethereum account to try<00:01:59.939> to<00:02:00.060> understand<00:02:00.740> why<00:02:01.740> there<00:02:02.100> are<00:02:02.340> a 00:02:02.810 --> 00:02:02.820 align:start position:0% try to understand why there are a 00:02:02.820 --> 00:02:04.609 align:start position:0% try to understand why there are a problem<00:02:03.000> and<00:02:03.420> and<00:02:03.600> then<00:02:03.840> Theo<00:02:04.200> we<00:02:04.380> can<00:02:04.500> fix 00:02:04.609 --> 00:02:04.619 align:start position:0% problem and and then Theo we can fix 00:02:04.619 --> 00:02:07.010 align:start position:0% problem and and then Theo we can fix that<00:02:04.860> so<00:02:05.700> this<00:02:05.939> is<00:02:06.060> pretty<00:02:06.240> basic<00:02:06.600> I'm<00:02:06.840> sure 00:02:07.010 --> 00:02:07.020 align:start position:0% that so this is pretty basic I'm sure 00:02:07.020 --> 00:02:08.990 align:start position:0% that so this is pretty basic I'm sure all<00:02:07.200> of<00:02:07.320> you<00:02:07.380> know<00:02:07.680> about<00:02:08.340> ethereum<00:02:08.819> account 00:02:08.990 --> 00:02:09.000 align:start position:0% all of you know about ethereum account 00:02:09.000 --> 00:02:10.550 align:start position:0% all of you know about ethereum account but<00:02:09.300> I<00:02:09.420> think<00:02:09.539> sometimes<00:02:09.840> it's<00:02:10.020> always<00:02:10.259> good 00:02:10.550 --> 00:02:10.560 align:start position:0% but I think sometimes it's always good 00:02:10.560 --> 00:02:12.410 align:start position:0% but I think sometimes it's always good to<00:02:10.679> take<00:02:10.860> a<00:02:10.979> step<00:02:11.160> back<00:02:11.400> and<00:02:11.640> see<00:02:11.879> things<00:02:12.120> with 00:02:12.410 --> 00:02:12.420 align:start position:0% to take a step back and see things with 00:02:12.420 --> 00:02:14.390 align:start position:0% to take a step back and see things with a<00:02:12.660> different<00:02:13.200> perspective 00:02:14.390 --> 00:02:14.400 align:start position:0% a different perspective 00:02:14.400 --> 00:02:16.309 align:start position:0% a different perspective so<00:02:14.940> we<00:02:15.060> all<00:02:15.180> know<00:02:15.300> that<00:02:15.480> on<00:02:15.660> ethereum<00:02:16.080> there's 00:02:16.309 --> 00:02:16.319 align:start position:0% so we all know that on ethereum there's 00:02:16.319 --> 00:02:18.589 align:start position:0% so we all know that on ethereum there's two<00:02:16.560> type<00:02:16.739> of<00:02:16.920> account<00:02:17.360> externally<00:02:18.360> on 00:02:18.589 --> 00:02:18.599 align:start position:0% two type of account externally on 00:02:18.599 --> 00:02:20.570 align:start position:0% two type of account externally on accounts<00:02:19.020> or<00:02:19.200> EOS<00:02:19.500> in<00:02:19.920> short<00:02:20.040> that<00:02:20.459> can 00:02:20.570 --> 00:02:20.580 align:start position:0% accounts or EOS in short that can 00:02:20.580 --> 00:02:22.729 align:start position:0% accounts or EOS in short that can initiate<00:02:21.000> transactions<00:02:21.720> and<00:02:22.319> then<00:02:22.440> you<00:02:22.620> have 00:02:22.729 --> 00:02:22.739 align:start position:0% initiate transactions and then you have 00:02:22.739 --> 00:02:25.490 align:start position:0% initiate transactions and then you have contract<00:02:23.099> accounts<00:02:23.640> that<00:02:23.879> can<00:02:24.060> contain<00:02:24.420> logic 00:02:25.490 --> 00:02:25.500 align:start position:0% contract accounts that can contain logic 00:02:25.500 --> 00:02:27.710 align:start position:0% contract accounts that can contain logic and<00:02:25.920> we<00:02:26.040> know<00:02:26.160> that<00:02:26.340> in<00:02:26.520> eua<00:02:27.060> has<00:02:27.480> an<00:02:27.599> address 00:02:27.710 --> 00:02:27.720 align:start position:0% and we know that in eua has an address 00:02:27.720 --> 00:02:30.110 align:start position:0% and we know that in eua has an address for<00:02:28.020> identification<00:02:28.819> announced<00:02:29.819> to<00:02:30.060> make 00:02:30.110 --> 00:02:30.120 align:start position:0% for identification announced to make 00:02:30.120 --> 00:02:31.690 align:start position:0% for identification announced to make transaction<00:02:30.540> unique 00:02:31.690 --> 00:02:31.700 align:start position:0% transaction unique 00:02:31.700 --> 00:02:34.250 align:start position:0% transaction unique and<00:02:32.700> the<00:02:32.879> balance<00:02:33.180> to<00:02:33.420> in<00:02:33.720> ease<00:02:33.959> to<00:02:34.140> pay 00:02:34.250 --> 00:02:34.260 align:start position:0% and the balance to in ease to pay 00:02:34.260 --> 00:02:36.410 align:start position:0% and the balance to in ease to pay transaction<00:02:34.680> fees<00:02:35.160> and<00:02:35.640> we<00:02:35.819> say<00:02:36.000> that<00:02:36.239> the 00:02:36.410 --> 00:02:36.420 align:start position:0% transaction fees and we say that the 00:02:36.420 --> 00:02:39.470 align:start position:0% transaction fees and we say that the user<00:02:36.840> owns<00:02:37.620> an<00:02:37.800> account<00:02:38.040> through<00:02:38.879> a<00:02:39.180> pair<00:02:39.360> of 00:02:39.470 --> 00:02:39.480 align:start position:0% user owns an account through a pair of 00:02:39.480 --> 00:02:41.869 align:start position:0% user owns an account through a pair of cryptographic<00:02:40.140> keys<00:02:40.500> also<00:02:41.040> called<00:02:41.220> a<00:02:41.459> signer 00:02:41.869 --> 00:02:41.879 align:start position:0% cryptographic keys also called a signer 00:02:41.879 --> 00:02:44.330 align:start position:0% cryptographic keys also called a signer right<00:02:42.540> and<00:02:43.319> what's<00:02:43.500> the<00:02:43.680> link<00:02:43.800> between<00:02:44.040> the 00:02:44.330 --> 00:02:44.340 align:start position:0% right and what's the link between the 00:02:44.340 --> 00:02:46.850 align:start position:0% right and what's the link between the two<00:02:44.519> well<00:02:44.879> the<00:02:45.180> address<00:02:45.900> of<00:02:46.260> the<00:02:46.379> account<00:02:46.560> is 00:02:46.850 --> 00:02:46.860 align:start position:0% two well the address of the account is 00:02:46.860 --> 00:02:48.530 align:start position:0% two well the address of the account is derived<00:02:47.280> from<00:02:47.400> the<00:02:47.580> public<00:02:47.760> key 00:02:48.530 --> 00:02:48.540 align:start position:0% derived from the public key 00:02:48.540 --> 00:02:52.369 align:start position:0% derived from the public key of<00:02:49.080> designer<00:02:49.760> and<00:02:50.760> transaction<00:02:51.720> from<00:02:52.200> the 00:02:52.369 --> 00:02:52.379 align:start position:0% of designer and transaction from the 00:02:52.379 --> 00:02:55.009 align:start position:0% of designer and transaction from the account<00:02:52.560> can<00:02:53.040> only<00:02:53.160> be<00:02:53.400> initiated<00:02:53.879> by<00:02:54.780> the 00:02:55.009 --> 00:02:55.019 align:start position:0% account can only be initiated by the 00:02:55.019 --> 00:02:56.690 align:start position:0% account can only be initiated by the private<00:02:55.319> key<00:02:55.440> of<00:02:55.680> the<00:02:55.800> signer<00:02:56.160> so<00:02:56.519> there's 00:02:56.690 --> 00:02:56.700 align:start position:0% private key of the signer so there's 00:02:56.700 --> 00:02:58.550 align:start position:0% private key of the signer so there's really<00:02:56.940> a<00:02:57.060> link<00:02:57.180> between<00:02:57.360> the<00:02:57.599> two<00:02:57.780> and<00:02:58.379> on 00:02:58.550 --> 00:02:58.560 align:start position:0% really a link between the two and on 00:02:58.560 --> 00:03:00.470 align:start position:0% really a link between the two and on ethereum<00:02:58.920> that<00:02:59.040> cling<00:02:59.340> is<00:02:59.519> not<00:02:59.700> is<00:02:59.940> not<00:03:00.120> random 00:03:00.470 --> 00:03:00.480 align:start position:0% ethereum that cling is not is not random 00:03:00.480 --> 00:03:02.869 align:start position:0% ethereum that cling is not is not random we<00:03:01.140> need<00:03:01.260> to<00:03:01.379> use<00:03:01.560> a<00:03:01.860> very<00:03:01.980> specific<00:03:02.280> signature 00:03:02.869 --> 00:03:02.879 align:start position:0% we need to use a very specific signature 00:03:02.879 --> 00:03:04.850 align:start position:0% we need to use a very specific signature scheme<00:03:03.239> called<00:03:03.360> the<00:03:03.599> cdsa<00:03:04.200> on<00:03:04.500> a<00:03:04.680> very 00:03:04.850 --> 00:03:04.860 align:start position:0% scheme called the cdsa on a very 00:03:04.860 --> 00:03:09.050 align:start position:0% scheme called the cdsa on a very specific<00:03:05.340> elliptic<00:03:06.000> curve<00:03:06.360> SEC<00:03:06.959> p256<00:03:07.860> K1<00:03:08.340> the 00:03:09.050 --> 00:03:09.060 align:start position:0% specific elliptic curve SEC p256 K1 the 00:03:09.060 --> 00:03:10.850 align:start position:0% specific elliptic curve SEC p256 K1 the details<00:03:09.480> are<00:03:09.660> not<00:03:09.780> that<00:03:10.019> important<00:03:10.440> but<00:03:10.680> what 00:03:10.850 --> 00:03:10.860 align:start position:0% details are not that important but what 00:03:10.860 --> 00:03:13.309 align:start position:0% details are not that important but what matters<00:03:11.159> is<00:03:11.400> that<00:03:11.640> all<00:03:12.239> of<00:03:12.360> this<00:03:12.540> is<00:03:12.659> are<00:03:12.900> coded 00:03:13.309 --> 00:03:13.319 align:start position:0% matters is that all of this is are coded 00:03:13.319 --> 00:03:16.490 align:start position:0% matters is that all of this is are coded all<00:03:13.980> of<00:03:14.159> that<00:03:14.340> logic<00:03:14.760> is<00:03:14.940> out<00:03:15.180> coded<00:03:15.659> in<00:03:15.959> DVM 00:03:16.490 --> 00:03:16.500 align:start position:0% all of that logic is out coded in DVM 00:03:16.500 --> 00:03:19.190 align:start position:0% all of that logic is out coded in DVM and<00:03:17.099> so<00:03:17.220> if<00:03:17.340> we<00:03:17.459> take<00:03:17.640> a<00:03:17.760> step<00:03:17.879> back<00:03:18.120> we<00:03:19.019> see 00:03:19.190 --> 00:03:19.200 align:start position:0% and so if we take a step back we see 00:03:19.200 --> 00:03:21.470 align:start position:0% and so if we take a step back we see that<00:03:19.440> in<00:03:19.800> the<00:03:19.920> user<00:03:20.220> space<00:03:20.400> we<00:03:20.760> have<00:03:20.940> designer 00:03:21.470 --> 00:03:21.480 align:start position:0% that in the user space we have designer 00:03:21.480 --> 00:03:24.229 align:start position:0% that in the user space we have designer the<00:03:22.019> key<00:03:22.200> pair<00:03:22.440> and<00:03:23.159> then<00:03:23.280> on<00:03:23.459> ethereum<00:03:23.940> we 00:03:24.229 --> 00:03:24.239 align:start position:0% the key pair and then on ethereum we 00:03:24.239 --> 00:03:27.350 align:start position:0% the key pair and then on ethereum we have<00:03:24.420> the<00:03:24.599> eoa<00:03:25.140> with<00:03:25.800> all<00:03:26.159> the<00:03:26.340> evm<00:03:26.760> logic<00:03:27.120> to 00:03:27.350 --> 00:03:27.360 align:start position:0% have the eoa with all the evm logic to 00:03:27.360 --> 00:03:30.229 align:start position:0% have the eoa with all the evm logic to validate<00:03:27.780> and<00:03:27.959> execute<00:03:28.379> transactions<00:03:29.099> and<00:03:30.060> we 00:03:30.229 --> 00:03:30.239 align:start position:0% validate and execute transactions and we 00:03:30.239 --> 00:03:31.610 align:start position:0% validate and execute transactions and we see<00:03:30.360> that<00:03:30.540> there's<00:03:30.720> video<00:03:30.959> type<00:03:31.260> coupling 00:03:31.610 --> 00:03:31.620 align:start position:0% see that there's video type coupling 00:03:31.620 --> 00:03:33.229 align:start position:0% see that there's video type coupling between<00:03:31.800> the<00:03:32.040> two<00:03:32.220> right<00:03:32.400> these<00:03:33.120> are 00:03:33.229 --> 00:03:33.239 align:start position:0% between the two right these are 00:03:33.239 --> 00:03:35.570 align:start position:0% between the two right these are basically<00:03:33.599> two<00:03:33.959> sides<00:03:34.260> of<00:03:34.379> the<00:03:34.500> same<00:03:34.680> coin 00:03:35.570 --> 00:03:35.580 align:start position:0% basically two sides of the same coin 00:03:35.580 --> 00:03:37.369 align:start position:0% basically two sides of the same coin and<00:03:36.180> that's<00:03:36.360> kind<00:03:36.599> of<00:03:36.720> the<00:03:36.900> problem<00:03:37.080> because 00:03:37.369 --> 00:03:37.379 align:start position:0% and that's kind of the problem because 00:03:37.379 --> 00:03:40.070 align:start position:0% and that's kind of the problem because on<00:03:37.680> ethereum<00:03:38.159> we<00:03:38.940> have<00:03:39.060> merged<00:03:39.480> the<00:03:39.720> concept 00:03:40.070 --> 00:03:40.080 align:start position:0% on ethereum we have merged the concept 00:03:40.080 --> 00:03:42.710 align:start position:0% on ethereum we have merged the concept of<00:03:40.440> designer<00:03:41.099> the<00:03:41.580> object<00:03:41.879> that's<00:03:42.120> authorized 00:03:42.710 --> 00:03:42.720 align:start position:0% of designer the object that's authorized 00:03:42.720 --> 00:03:44.750 align:start position:0% of designer the object that's authorized to<00:03:42.840> spend<00:03:43.080> your<00:03:43.260> token<00:03:43.620> with<00:03:44.159> the<00:03:44.340> concept<00:03:44.580> of 00:03:44.750 --> 00:03:44.760 align:start position:0% to spend your token with the concept of 00:03:44.760 --> 00:03:46.610 align:start position:0% to spend your token with the concept of the<00:03:45.000> account<00:03:45.120> the<00:03:45.599> object<00:03:45.840> all<00:03:46.200> the<00:03:46.379> your 00:03:46.610 --> 00:03:46.620 align:start position:0% the account the object all the your 00:03:46.620 --> 00:03:48.770 align:start position:0% the account the object all the your tokens<00:03:47.159> on<00:03:47.700> ethereum<00:03:48.120> they<00:03:48.420> are<00:03:48.540> basically 00:03:48.770 --> 00:03:48.780 align:start position:0% tokens on ethereum they are basically 00:03:48.780 --> 00:03:50.869 align:start position:0% tokens on ethereum they are basically two<00:03:49.019> sides<00:03:49.319> of<00:03:49.379> the<00:03:49.500> same<00:03:49.620> coin<00:03:49.980> and<00:03:50.519> that's<00:03:50.700> of 00:03:50.869 --> 00:03:50.879 align:start position:0% two sides of the same coin and that's of 00:03:50.879 --> 00:03:53.210 align:start position:0% two sides of the same coin and that's of course<00:03:51.060> a<00:03:51.239> problem<00:03:51.480> because<00:03:52.260> if<00:03:52.560> the<00:03:52.739> signer 00:03:53.210 --> 00:03:53.220 align:start position:0% course a problem because if the signer 00:03:53.220 --> 00:03:55.910 align:start position:0% course a problem because if the signer is<00:03:53.580> the<00:03:53.819> account<00:03:54.000> and<00:03:54.299> vice<00:03:54.540> versa<00:03:54.959> that<00:03:55.620> means 00:03:55.910 --> 00:03:55.920 align:start position:0% is the account and vice versa that means 00:03:55.920 --> 00:03:57.890 align:start position:0% is the account and vice versa that means that<00:03:56.159> if<00:03:56.580> you<00:03:56.700> lose<00:03:56.879> your<00:03:57.060> signer<00:03:57.480> you've<00:03:57.720> lost 00:03:57.890 --> 00:03:57.900 align:start position:0% that if you lose your signer you've lost 00:03:57.900 --> 00:04:01.009 align:start position:0% that if you lose your signer you've lost everything<00:03:58.220> if<00:03:59.220> I<00:03:59.400> have<00:03:59.519> your<00:03:59.700> assigner<00:04:00.239> I 00:04:01.009 --> 00:04:01.019 align:start position:0% everything if I have your assigner I 00:04:01.019 --> 00:04:03.229 align:start position:0% everything if I have your assigner I have<00:04:01.200> your<00:04:01.319> tokens<00:04:01.739> right<00:04:02.400> that<00:04:02.940> basically 00:04:03.229 --> 00:04:03.239 align:start position:0% have your tokens right that basically 00:04:03.239 --> 00:04:05.570 align:start position:0% have your tokens right that basically means<00:04:03.540> that<00:04:03.659> on<00:04:03.900> ethereum<00:04:04.379> the<00:04:05.280> entire 00:04:05.570 --> 00:04:05.580 align:start position:0% means that on ethereum the entire 00:04:05.580 --> 00:04:09.530 align:start position:0% means that on ethereum the entire security<00:04:06.379> relies<00:04:07.379> on<00:04:07.620> users<00:04:08.120> managing<00:04:09.120> a 00:04:09.530 --> 00:04:09.540 align:start position:0% security relies on users managing a 00:04:09.540 --> 00:04:11.929 align:start position:0% security relies on users managing a secret<00:04:09.780> this<00:04:10.560> private<00:04:10.980> key<00:04:11.099> designer<00:04:11.700> at<00:04:11.819> all 00:04:11.929 --> 00:04:11.939 align:start position:0% secret this private key designer at all 00:04:11.939 --> 00:04:14.270 align:start position:0% secret this private key designer at all cost<00:04:12.120> and<00:04:13.019> as<00:04:13.140> a<00:04:13.319> user<00:04:13.560> you<00:04:13.739> cannot<00:04:13.980> make<00:04:14.099> a 00:04:14.270 --> 00:04:14.280 align:start position:0% cost and as a user you cannot make a 00:04:14.280 --> 00:04:15.649 align:start position:0% cost and as a user you cannot make a mistake<00:04:14.519> if<00:04:14.760> you<00:04:14.819> make<00:04:14.939> a<00:04:15.120> mistake<00:04:15.360> you<00:04:15.480> lose 00:04:15.649 --> 00:04:15.659 align:start position:0% mistake if you make a mistake you lose 00:04:15.659 --> 00:04:16.670 align:start position:0% mistake if you make a mistake you lose everything 00:04:16.670 --> 00:04:16.680 align:start position:0% everything 00:04:16.680 --> 00:04:18.409 align:start position:0% everything and<00:04:17.100> I<00:04:17.280> mean<00:04:17.400> if<00:04:17.579> there's<00:04:17.760> one<00:04:18.000> thing<00:04:18.120> we've 00:04:18.409 --> 00:04:18.419 align:start position:0% and I mean if there's one thing we've 00:04:18.419 --> 00:04:20.870 align:start position:0% and I mean if there's one thing we've learned<00:04:18.720> from<00:04:19.500> 40<00:04:19.680> Years<00:04:19.979> of<00:04:20.160> the<00:04:20.340> internet<00:04:20.459> is 00:04:20.870 --> 00:04:20.880 align:start position:0% learned from 40 Years of the internet is 00:04:20.880 --> 00:04:23.330 align:start position:0% learned from 40 Years of the internet is that<00:04:21.120> we<00:04:21.299> humans<00:04:21.780> we<00:04:22.560> suck<00:04:22.680> at<00:04:22.919> managing 00:04:23.330 --> 00:04:23.340 align:start position:0% that we humans we suck at managing 00:04:23.340 --> 00:04:25.670 align:start position:0% that we humans we suck at managing passwords<00:04:23.880> and<00:04:24.240> we<00:04:24.419> humans<00:04:24.780> we<00:04:25.080> make<00:04:25.199> mistake 00:04:25.670 --> 00:04:25.680 align:start position:0% passwords and we humans we make mistake 00:04:25.680 --> 00:04:29.330 align:start position:0% passwords and we humans we make mistake so<00:04:26.400> of<00:04:26.639> course<00:04:26.820> I<00:04:27.600> mean<00:04:27.720> this<00:04:27.900> is<00:04:28.020> absurd<00:04:28.560> and 00:04:29.330 --> 00:04:29.340 align:start position:0% so of course I mean this is absurd and 00:04:29.340 --> 00:04:32.689 align:start position:0% so of course I mean this is absurd and and<00:04:29.520> this<00:04:30.180> this<00:04:30.720> concept<00:04:31.080> is<00:04:31.320> Paradigm<00:04:31.979> will 00:04:32.689 --> 00:04:32.699 align:start position:0% and this this concept is Paradigm will 00:04:32.699 --> 00:04:34.550 align:start position:0% and this this concept is Paradigm will never<00:04:32.880> work<00:04:33.180> for<00:04:33.419> mainstream<00:04:33.960> users<00:04:34.259> I<00:04:34.440> mean 00:04:34.550 --> 00:04:34.560 align:start position:0% never work for mainstream users I mean 00:04:34.560 --> 00:04:36.409 align:start position:0% never work for mainstream users I mean do<00:04:34.800> we<00:04:34.979> really<00:04:35.160> expect<00:04:35.340> the<00:04:35.699> next<00:04:35.820> billions<00:04:36.300> of 00:04:36.409 --> 00:04:36.419 align:start position:0% do we really expect the next billions of 00:04:36.419 --> 00:04:38.810 align:start position:0% do we really expect the next billions of users<00:04:36.900> to<00:04:37.500> basically<00:04:37.800> being<00:04:38.040> able<00:04:38.340> to<00:04:38.460> manage 00:04:38.810 --> 00:04:38.820 align:start position:0% users to basically being able to manage 00:04:38.820 --> 00:04:41.090 align:start position:0% users to basically being able to manage that<00:04:39.060> single<00:04:39.419> Secret<00:04:39.540> at<00:04:39.900> all<00:04:40.020> cost<00:04:40.199> I<00:04:40.979> mean 00:04:41.090 --> 00:04:41.100 align:start position:0% that single Secret at all cost I mean 00:04:41.100 --> 00:04:42.350 align:start position:0% that single Secret at all cost I mean we're<00:04:41.280> pretty<00:04:41.580> convinced<00:04:41.940> that<00:04:42.060> the<00:04:42.240> answer 00:04:42.350 --> 00:04:42.360 align:start position:0% we're pretty convinced that the answer 00:04:42.360 --> 00:04:45.110 align:start position:0% we're pretty convinced that the answer is<00:04:42.600> no<00:04:43.259> so<00:04:43.680> can<00:04:43.860> we<00:04:43.979> do<00:04:44.160> better 00:04:45.110 --> 00:04:45.120 align:start position:0% is no so can we do better 00:04:45.120 --> 00:04:48.590 align:start position:0% is no so can we do better and<00:04:45.720> fortunately<00:04:46.080> yes<00:04:46.500> we<00:04:47.100> can<00:04:47.220> do<00:04:47.400> better<00:04:47.600> and 00:04:48.590 --> 00:04:48.600 align:start position:0% and fortunately yes we can do better and 00:04:48.600 --> 00:04:49.909 align:start position:0% and fortunately yes we can do better and there's<00:04:48.720> something<00:04:49.020> called<00:04:49.380> account 00:04:49.909 --> 00:04:49.919 align:start position:0% there's something called account 00:04:49.919 --> 00:04:51.830 align:start position:0% there's something called account abstraction<00:04:50.520> the<00:04:51.360> idea<00:04:51.600> of<00:04:51.660> account 00:04:51.830 --> 00:04:51.840 align:start position:0% abstraction the idea of account 00:04:51.840 --> 00:04:54.350 align:start position:0% abstraction the idea of account attraction<00:04:52.320> is<00:04:52.620> is<00:04:52.919> really<00:04:53.220> to<00:04:53.580> decouple<00:04:54.120> that 00:04:54.350 --> 00:04:54.360 align:start position:0% attraction is is really to decouple that 00:04:54.360 --> 00:04:56.450 align:start position:0% attraction is is really to decouple that relation<00:04:54.780> between<00:04:55.500> the<00:04:55.740> signer<00:04:56.160> in<00:04:56.340> the 00:04:56.450 --> 00:04:56.460 align:start position:0% relation between the signer in the 00:04:56.460 --> 00:04:58.730 align:start position:0% relation between the signer in the account<00:04:56.580> with<00:04:57.360> account<00:04:57.600> abstraction<00:04:58.080> every 00:04:58.730 --> 00:04:58.740 align:start position:0% account with account abstraction every 00:04:58.740 --> 00:05:00.950 align:start position:0% account with account abstraction every account<00:04:58.919> is<00:04:59.280> a<00:04:59.460> smart<00:04:59.580> contract<00:05:00.000> that<00:05:00.780> can 00:05:00.950 --> 00:05:00.960 align:start position:0% account is a smart contract that can 00:05:00.960 --> 00:05:03.409 align:start position:0% account is a smart contract that can contain<00:05:01.259> its<00:05:01.620> own<00:05:01.680> Logic<00:05:02.040> for<00:05:02.880> example<00:05:03.120> you 00:05:03.409 --> 00:05:03.419 align:start position:0% contain its own Logic for example you 00:05:03.419 --> 00:05:04.790 align:start position:0% contain its own Logic for example you you<00:05:03.720> may<00:05:03.900> want<00:05:04.020> to<00:05:04.139> use<00:05:04.320> a<00:05:04.680> different 00:05:04.790 --> 00:05:04.800 align:start position:0% you may want to use a different 00:05:04.800 --> 00:05:06.890 align:start position:0% you may want to use a different signature<00:05:05.400> scheme<00:05:05.820> or<00:05:06.240> you<00:05:06.479> may<00:05:06.540> want<00:05:06.720> to<00:05:06.780> use 00:05:06.890 --> 00:05:06.900 align:start position:0% signature scheme or you may want to use 00:05:06.900 --> 00:05:08.629 align:start position:0% signature scheme or you may want to use a<00:05:07.139> different<00:05:07.259> elliptic<00:05:07.800> curve<00:05:08.100> or<00:05:08.280> maybe<00:05:08.460> you 00:05:08.629 --> 00:05:08.639 align:start position:0% a different elliptic curve or maybe you 00:05:08.639 --> 00:05:10.670 align:start position:0% a different elliptic curve or maybe you want<00:05:08.820> to<00:05:08.940> use<00:05:09.060> multiple<00:05:09.540> signers<00:05:10.080> to<00:05:10.259> validate 00:05:10.670 --> 00:05:10.680 align:start position:0% want to use multiple signers to validate 00:05:10.680 --> 00:05:12.890 align:start position:0% want to use multiple signers to validate transaction<00:05:11.100> think<00:05:11.699> of<00:05:11.880> a<00:05:12.000> native<00:05:12.240> multisig 00:05:12.890 --> 00:05:12.900 align:start position:0% transaction think of a native multisig 00:05:12.900 --> 00:05:15.950 align:start position:0% transaction think of a native multisig or<00:05:13.560> maybe<00:05:13.740> you<00:05:14.100> want<00:05:14.280> to<00:05:14.940> rotate<00:05:15.300> your<00:05:15.479> signer 00:05:15.950 --> 00:05:15.960 align:start position:0% or maybe you want to rotate your signer 00:05:15.960 --> 00:05:17.570 align:start position:0% or maybe you want to rotate your signer based<00:05:16.259> on<00:05:16.320> some<00:05:16.500> logic<00:05:16.800> that<00:05:17.040> you've<00:05:17.220> defined 00:05:17.570 --> 00:05:17.580 align:start position:0% based on some logic that you've defined 00:05:17.580 --> 00:05:19.670 align:start position:0% based on some logic that you've defined with<00:05:18.240> account<00:05:18.419> abstraction<00:05:18.900> all<00:05:19.199> of<00:05:19.380> this<00:05:19.500> is 00:05:19.670 --> 00:05:19.680 align:start position:0% with account abstraction all of this is 00:05:19.680 --> 00:05:20.570 align:start position:0% with account abstraction all of this is possible 00:05:20.570 --> 00:05:20.580 align:start position:0% possible 00:05:20.580 --> 00:05:22.550 align:start position:0% possible another<00:05:21.120> way<00:05:21.419> to<00:05:21.540> see<00:05:21.660> it<00:05:21.780> is<00:05:21.900> that<00:05:22.080> on<00:05:22.199> a<00:05:22.320> with 00:05:22.550 --> 00:05:22.560 align:start position:0% another way to see it is that on a with 00:05:22.560 --> 00:05:24.529 align:start position:0% another way to see it is that on a with account<00:05:22.800> abstraction<00:05:23.280> every<00:05:23.880> account<00:05:24.120> is<00:05:24.419> a 00:05:24.529 --> 00:05:24.539 align:start position:0% account abstraction every account is a 00:05:24.539 --> 00:05:26.450 align:start position:0% account abstraction every account is a smart<00:05:24.660> contract<00:05:25.020> with<00:05:25.259> custom<00:05:25.500> logic<00:05:26.039> that 00:05:26.450 --> 00:05:26.460 align:start position:0% smart contract with custom logic that 00:05:26.460 --> 00:05:28.810 align:start position:0% smart contract with custom logic that can<00:05:26.699> initiate<00:05:27.180> transaction<00:05:27.600> so<00:05:28.020> no<00:05:28.380> smart 00:05:28.810 --> 00:05:28.820 align:start position:0% can initiate transaction so no smart 00:05:28.820 --> 00:05:32.689 align:start position:0% can initiate transaction so no smart contract<00:05:29.900> can<00:05:30.900> become<00:05:31.380> top<00:05:31.860> level<00:05:32.100> accounts 00:05:32.689 --> 00:05:32.699 align:start position:0% contract can become top level accounts 00:05:32.699 --> 00:05:34.850 align:start position:0% contract can become top level accounts and<00:05:33.360> the<00:05:33.539> good<00:05:33.660> news<00:05:33.780> is<00:05:34.020> that<00:05:34.320> with<00:05:34.560> true 00:05:34.850 --> 00:05:34.860 align:start position:0% and the good news is that with true 00:05:34.860 --> 00:05:36.469 align:start position:0% and the good news is that with true account<00:05:35.160> abstraction<00:05:35.580> there's<00:05:35.880> no<00:05:36.060> more<00:05:36.180> EOS 00:05:36.469 --> 00:05:36.479 align:start position:0% account abstraction there's no more EOS 00:05:36.479 --> 00:05:38.810 align:start position:0% account abstraction there's no more EOS right<00:05:37.139> because<00:05:37.440> every<00:05:37.919> single<00:05:38.220> account<00:05:38.400> is<00:05:38.699> a 00:05:38.810 --> 00:05:38.820 align:start position:0% right because every single account is a 00:05:38.820 --> 00:05:40.070 align:start position:0% right because every single account is a smart<00:05:38.940> contract 00:05:40.070 --> 00:05:40.080 align:start position:0% smart contract 00:05:40.080 --> 00:05:41.450 align:start position:0% smart contract and<00:05:40.500> you<00:05:40.620> may<00:05:40.740> have<00:05:40.860> heard<00:05:41.039> about<00:05:41.280> account 00:05:41.450 --> 00:05:41.460 align:start position:0% and you may have heard about account 00:05:41.460 --> 00:05:43.550 align:start position:0% and you may have heard about account abstraction<00:05:41.940> lately<00:05:42.419> but<00:05:42.960> actually<00:05:43.139> it's<00:05:43.320> not 00:05:43.550 --> 00:05:43.560 align:start position:0% abstraction lately but actually it's not 00:05:43.560 --> 00:05:45.950 align:start position:0% abstraction lately but actually it's not a<00:05:43.740> New<00:05:43.860> Concept<00:05:44.220> if<00:05:45.000> we<00:05:45.120> look<00:05:45.300> back<00:05:45.479> we<00:05:45.840> see 00:05:45.950 --> 00:05:45.960 align:start position:0% a New Concept if we look back we see 00:05:45.960 --> 00:05:47.629 align:start position:0% a New Concept if we look back we see that<00:05:46.199> vitalik<00:05:46.800> started<00:05:47.220> talking<00:05:47.400> about 00:05:47.629 --> 00:05:47.639 align:start position:0% that vitalik started talking about 00:05:47.639 --> 00:05:49.670 align:start position:0% that vitalik started talking about account<00:05:47.880> abstraction<00:05:48.360> as<00:05:48.660> early<00:05:48.840> as<00:05:49.080> 2016 00:05:49.670 --> 00:05:49.680 align:start position:0% account abstraction as early as 2016 00:05:49.680 --> 00:05:52.189 align:start position:0% account abstraction as early as 2016 with<00:05:50.460> the<00:05:50.639> first<00:05:50.759> EIP<00:05:51.180> being<00:05:51.539> proposed<00:05:52.020> early 00:05:52.189 --> 00:05:52.199 align:start position:0% with the first EIP being proposed early 00:05:52.199 --> 00:05:54.409 align:start position:0% with the first EIP being proposed early 2017<00:05:52.800> the<00:05:53.160> ip86 00:05:54.409 --> 00:05:54.419 align:start position:0% 2017 the ip86 00:05:54.419 --> 00:05:57.650 align:start position:0% 2017 the ip86 we<00:05:55.259> at<00:05:55.440> Arjun<00:05:55.919> and<00:05:56.340> people<00:05:56.580> like<00:05:56.940> it<00:05:57.120> knows 00:05:57.650 --> 00:05:57.660 align:start position:0% we at Arjun and people like it knows 00:05:57.660 --> 00:05:59.450 align:start position:0% we at Arjun and people like it knows this<00:05:57.780> with<00:05:57.900> diagnose<00:05:58.199> is<00:05:58.380> safe<00:05:58.620> we<00:05:59.100> started 00:05:59.450 --> 00:05:59.460 align:start position:0% this with diagnose is safe we started 00:05:59.460 --> 00:06:01.810 align:start position:0% this with diagnose is safe we started building<00:05:59.759> smart<00:06:00.240> contract<00:06:00.660> wallet<00:06:01.139> in<00:06:01.320> 2018 00:06:01.810 --> 00:06:01.820 align:start position:0% building smart contract wallet in 2018 00:06:01.820 --> 00:06:04.189 align:start position:0% building smart contract wallet in 2018 which<00:06:02.820> basically<00:06:03.360> were<00:06:03.660> a<00:06:03.780> form<00:06:03.900> of<00:06:04.020> account 00:06:04.189 --> 00:06:04.199 align:start position:0% which basically were a form of account 00:06:04.199 --> 00:06:06.650 align:start position:0% which basically were a form of account abstraction<00:06:04.740> the<00:06:05.100> idea<00:06:05.400> was<00:06:05.580> really<00:06:05.820> to<00:06:06.240> solve 00:06:06.650 --> 00:06:06.660 align:start position:0% abstraction the idea was really to solve 00:06:06.660 --> 00:06:09.170 align:start position:0% abstraction the idea was really to solve these<00:06:07.139> these<00:06:07.740> ux<00:06:08.039> problem<00:06:08.280> for<00:06:08.580> self-custody 00:06:09.170 --> 00:06:09.180 align:start position:0% these these ux problem for self-custody 00:06:09.180 --> 00:06:11.450 align:start position:0% these these ux problem for self-custody using<00:06:09.600> smart<00:06:09.840> contract<00:06:10.320> but<00:06:10.800> we<00:06:10.979> did<00:06:11.100> so<00:06:11.280> at 00:06:11.450 --> 00:06:11.460 align:start position:0% using smart contract but we did so at 00:06:11.460 --> 00:06:13.070 align:start position:0% using smart contract but we did so at the<00:06:11.639> application<00:06:12.060> layer<00:06:12.479> and<00:06:12.600> we<00:06:12.780> came<00:06:12.900> with 00:06:13.070 --> 00:06:13.080 align:start position:0% the application layer and we came with 00:06:13.080 --> 00:06:15.590 align:start position:0% the application layer and we came with ID<00:06:13.259> like<00:06:13.680> social<00:06:14.160> recovery<00:06:14.759> from<00:06:15.000> monitoring 00:06:15.590 --> 00:06:15.600 align:start position:0% ID like social recovery from monitoring 00:06:15.600 --> 00:06:18.469 align:start position:0% ID like social recovery from monitoring and<00:06:15.720> so<00:06:15.900> on<00:06:16.500> in<00:06:16.979> 2020<00:06:17.400> there<00:06:17.759> was<00:06:17.880> a<00:06:18.000> new<00:06:18.120> EIP 00:06:18.469 --> 00:06:18.479 align:start position:0% and so on in 2020 there was a new EIP 00:06:18.479 --> 00:06:23.570 align:start position:0% and so on in 2020 there was a new EIP again<00:06:19.220> led<00:06:20.220> by<00:06:20.340> vitalik<00:06:20.940> EIP<00:06:21.680> 2938<00:06:22.680> where<00:06:23.280> the 00:06:23.570 --> 00:06:23.580 align:start position:0% again led by vitalik EIP 2938 where the 00:06:23.580 --> 00:06:24.830 align:start position:0% again led by vitalik EIP 2938 where the idea<00:06:23.819> was<00:06:23.940> to<00:06:24.120> add<00:06:24.300> a<00:06:24.419> new<00:06:24.539> type<00:06:24.720> of 00:06:24.830 --> 00:06:24.840 align:start position:0% idea was to add a new type of 00:06:24.840 --> 00:06:28.270 align:start position:0% idea was to add a new type of transaction<00:06:25.319> to<00:06:25.800> let<00:06:26.039> smart<00:06:26.940> contract<00:06:27.479> become 00:06:28.270 --> 00:06:28.280 align:start position:0% transaction to let smart contract become 00:06:28.280 --> 00:06:31.430 align:start position:0% transaction to let smart contract become first<00:06:29.280> top<00:06:29.759> level<00:06:30.060> account<00:06:30.360> so<00:06:30.720> enabling 00:06:31.430 --> 00:06:31.440 align:start position:0% first top level account so enabling 00:06:31.440 --> 00:06:33.050 align:start position:0% first top level account so enabling smart<00:06:31.680> contract<00:06:32.160> to<00:06:32.520> basically<00:06:32.819> make 00:06:33.050 --> 00:06:33.060 align:start position:0% smart contract to basically make 00:06:33.060 --> 00:06:34.870 align:start position:0% smart contract to basically make transaction<00:06:33.479> and<00:06:33.720> pay<00:06:33.900> for<00:06:34.020> transaction<00:06:34.380> fees 00:06:34.870 --> 00:06:34.880 align:start position:0% transaction and pay for transaction fees 00:06:34.880 --> 00:06:38.570 align:start position:0% transaction and pay for transaction fees soon<00:06:35.880> after<00:06:36.060> there<00:06:36.419> was<00:06:36.600> the<00:06:36.800> ip3074<00:06:37.800> which 00:06:38.570 --> 00:06:38.580 align:start position:0% soon after there was the ip3074 which 00:06:38.580 --> 00:06:40.010 align:start position:0% soon after there was the ip3074 which took<00:06:38.819> actually<00:06:39.000> the<00:06:39.300> opposite<00:06:39.720> approach 00:06:40.010 --> 00:06:40.020 align:start position:0% took actually the opposite approach 00:06:40.020 --> 00:06:42.110 align:start position:0% took actually the opposite approach which<00:06:40.259> was<00:06:40.500> trying<00:06:40.800> to<00:06:41.100> enable<00:06:41.400> some<00:06:41.759> of<00:06:41.880> the 00:06:42.110 --> 00:06:42.120 align:start position:0% which was trying to enable some of the 00:06:42.120 --> 00:06:45.469 align:start position:0% which was trying to enable some of the smart<00:06:42.300> contract<00:06:42.780> feature<00:06:43.319> on<00:06:43.919> existing<00:06:44.280> EOS 00:06:45.469 --> 00:06:45.479 align:start position:0% smart contract feature on existing EOS 00:06:45.479 --> 00:06:47.450 align:start position:0% smart contract feature on existing EOS and<00:06:46.020> then<00:06:46.139> recently<00:06:46.560> there<00:06:46.860> was<00:06:46.979> a<00:06:47.100> new<00:06:47.160> EIP 00:06:47.450 --> 00:06:47.460 align:start position:0% and then recently there was a new EIP 00:06:47.460 --> 00:06:50.870 align:start position:0% and then recently there was a new EIP again<00:06:47.759> led<00:06:48.060> by<00:06:48.180> his<00:06:48.300> italic<00:06:48.919> eip4337<00:06:49.919> which 00:06:50.870 --> 00:06:50.880 align:start position:0% again led by his italic eip4337 which 00:06:50.880 --> 00:06:52.610 align:start position:0% again led by his italic eip4337 which basically<00:06:51.180> is<00:06:51.419> a<00:06:51.600> generalization<00:06:52.199> of<00:06:52.440> smart 00:06:52.610 --> 00:06:52.620 align:start position:0% basically is a generalization of smart 00:06:52.620 --> 00:06:54.730 align:start position:0% basically is a generalization of smart contract<00:06:53.039> quality<00:06:53.460> the<00:06:53.639> idea<00:06:54.000> is<00:06:54.060> to 00:06:54.730 --> 00:06:54.740 align:start position:0% contract quality the idea is to 00:06:54.740 --> 00:06:56.870 align:start position:0% contract quality the idea is to decentralize<00:06:55.740> some<00:06:56.039> of<00:06:56.160> the<00:06:56.280> infrastructure 00:06:56.870 --> 00:06:56.880 align:start position:0% decentralize some of the infrastructure 00:06:56.880 --> 00:07:00.170 align:start position:0% decentralize some of the infrastructure that<00:06:57.240> is<00:06:57.360> needed<00:06:57.720> to<00:06:58.020> make<00:06:58.199> uh<00:06:58.979> to<00:06:59.160> to<00:06:59.460> write 00:07:00.170 --> 00:07:00.180 align:start position:0% that is needed to make uh to to write 00:07:00.180 --> 00:07:02.689 align:start position:0% that is needed to make uh to to write and<00:07:00.479> to<00:07:00.660> operate<00:07:01.319> orchest<00:07:01.979> Smart<00:07:02.340> contract 00:07:02.689 --> 00:07:02.699 align:start position:0% and to operate orchest Smart contract 00:07:02.699 --> 00:07:04.189 align:start position:0% and to operate orchest Smart contract wallet 00:07:04.189 --> 00:07:04.199 align:start position:0% wallet 00:07:04.199 --> 00:07:07.010 align:start position:0% wallet and<00:07:04.620> I<00:07:04.860> think<00:07:05.060> eip4337<00:07:06.060> is<00:07:06.300> very<00:07:06.600> interesting 00:07:07.010 --> 00:07:07.020 align:start position:0% and I think eip4337 is very interesting 00:07:07.020 --> 00:07:09.830 align:start position:0% and I think eip4337 is very interesting uh<00:07:07.919> for<00:07:08.160> different<00:07:08.280> reasons<00:07:08.759> first<00:07:09.120> of<00:07:09.300> all<00:07:09.419> it 00:07:09.830 --> 00:07:09.840 align:start position:0% uh for different reasons first of all it 00:07:09.840 --> 00:07:11.870 align:start position:0% uh for different reasons first of all it does<00:07:10.020> not<00:07:10.139> require<00:07:10.319> a<00:07:10.620> fork<00:07:11.039> so<00:07:11.220> it<00:07:11.460> lacks 00:07:11.870 --> 00:07:11.880 align:start position:0% does not require a fork so it lacks 00:07:11.880 --> 00:07:13.430 align:start position:0% does not require a fork so it lacks smart<00:07:12.000> contract<00:07:12.300> quality<00:07:12.720> it<00:07:12.960> works<00:07:13.139> at<00:07:13.259> the 00:07:13.430 --> 00:07:13.440 align:start position:0% smart contract quality it works at the 00:07:13.440 --> 00:07:15.650 align:start position:0% smart contract quality it works at the application<00:07:13.800> layer<00:07:14.220> and<00:07:14.880> and<00:07:15.120> it's<00:07:15.360> actually 00:07:15.650 --> 00:07:15.660 align:start position:0% application layer and and it's actually 00:07:15.660 --> 00:07:18.290 align:start position:0% application layer and and it's actually a<00:07:15.960> good<00:07:16.080> architecture<00:07:16.620> I<00:07:16.800> think<00:07:16.979> which<00:07:17.340> can 00:07:18.290 --> 00:07:18.300 align:start position:0% a good architecture I think which can 00:07:18.300 --> 00:07:20.510 align:start position:0% a good architecture I think which can lead<00:07:19.199> us<00:07:19.440> in<00:07:19.800> what<00:07:19.979> Native<00:07:20.280> account 00:07:20.510 --> 00:07:20.520 align:start position:0% lead us in what Native account 00:07:20.520 --> 00:07:23.570 align:start position:0% lead us in what Native account abstraction<00:07:21.060> should<00:07:21.599> be<00:07:21.780> in<00:07:21.900> the<00:07:22.020> future 00:07:23.570 --> 00:07:23.580 align:start position:0% abstraction should be in the future 00:07:23.580 --> 00:07:26.210 align:start position:0% abstraction should be in the future so<00:07:24.120> let<00:07:24.240> me<00:07:24.419> dig<00:07:24.599> a<00:07:24.840> little<00:07:24.960> bit<00:07:25.080> into<00:07:25.259> 4337 00:07:26.210 --> 00:07:26.220 align:start position:0% so let me dig a little bit into 4337 00:07:26.220 --> 00:07:30.290 align:start position:0% so let me dig a little bit into 4337 rapidly<00:07:26.759> so<00:07:27.300> on<00:07:27.539> 4337<00:07:28.319> users<00:07:28.919> they<00:07:29.280> send<00:07:29.520> they 00:07:30.290 --> 00:07:30.300 align:start position:0% rapidly so on 4337 users they send they 00:07:30.300 --> 00:07:31.850 align:start position:0% rapidly so on 4337 users they send they don't<00:07:30.360> make<00:07:30.539> transaction<00:07:30.960> they<00:07:31.319> send<00:07:31.500> user 00:07:31.850 --> 00:07:31.860 align:start position:0% don't make transaction they send user 00:07:31.860 --> 00:07:33.650 align:start position:0% don't make transaction they send user operation<00:07:32.220> and<00:07:32.759> they<00:07:32.880> send<00:07:33.060> this<00:07:33.300> user 00:07:33.650 --> 00:07:33.660 align:start position:0% operation and they send this user 00:07:33.660 --> 00:07:37.249 align:start position:0% operation and they send this user operation<00:07:34.020> to<00:07:34.919> a<00:07:35.280> highly<00:07:35.580> level<00:07:35.759> mempool<00:07:36.360> on 00:07:37.249 --> 00:07:37.259 align:start position:0% operation to a highly level mempool on 00:07:37.259 --> 00:07:40.189 align:start position:0% operation to a highly level mempool on which<00:07:37.440> you<00:07:37.680> have<00:07:37.919> bundlers<00:07:38.699> like<00:07:39.419> miners<00:07:39.900> that 00:07:40.189 --> 00:07:40.199 align:start position:0% which you have bundlers like miners that 00:07:40.199 --> 00:07:43.010 align:start position:0% which you have bundlers like miners that can<00:07:40.319> basically<00:07:40.740> take<00:07:41.220> a<00:07:41.819> bunch<00:07:42.000> of<00:07:42.120> these<00:07:42.539> user 00:07:43.010 --> 00:07:43.020 align:start position:0% can basically take a bunch of these user 00:07:43.020 --> 00:07:44.749 align:start position:0% can basically take a bunch of these user operation<00:07:43.380> and<00:07:43.740> building<00:07:43.979> them<00:07:44.340> into<00:07:44.520> a 00:07:44.749 --> 00:07:44.759 align:start position:0% operation and building them into a 00:07:44.759 --> 00:07:46.969 align:start position:0% operation and building them into a normal<00:07:44.880> L1<00:07:45.419> transaction<00:07:45.960> and<00:07:46.860> that 00:07:46.969 --> 00:07:46.979 align:start position:0% normal L1 transaction and that 00:07:46.979 --> 00:07:48.650 align:start position:0% normal L1 transaction and that transaction<00:07:47.400> is<00:07:47.699> sent<00:07:47.880> to<00:07:48.060> a<00:07:48.240> specific 00:07:48.650 --> 00:07:48.660 align:start position:0% transaction is sent to a specific 00:07:48.660 --> 00:07:51.110 align:start position:0% transaction is sent to a specific contract<00:07:49.139> a<00:07:49.740> single<00:07:50.099> term<00:07:50.280> called<00:07:50.580> the<00:07:50.819> entry 00:07:51.110 --> 00:07:51.120 align:start position:0% contract a single term called the entry 00:07:51.120 --> 00:07:52.010 align:start position:0% contract a single term called the entry point 00:07:52.010 --> 00:07:52.020 align:start position:0% point 00:07:52.020 --> 00:07:53.930 align:start position:0% point when<00:07:52.620> that<00:07:52.800> transaction<00:07:53.160> reach<00:07:53.639> the<00:07:53.699> entry 00:07:53.930 --> 00:07:53.940 align:start position:0% when that transaction reach the entry 00:07:53.940 --> 00:07:55.490 align:start position:0% when that transaction reach the entry point<00:07:54.120> contract<00:07:54.479> the<00:07:54.720> entry<00:07:55.020> point<00:07:55.199> will 00:07:55.490 --> 00:07:55.500 align:start position:0% point contract the entry point will 00:07:55.500 --> 00:07:58.010 align:start position:0% point contract the entry point will basically<00:07:55.919> orchestrate<00:07:56.699> the<00:07:56.880> validation<00:07:57.419> and 00:07:58.010 --> 00:07:58.020 align:start position:0% basically orchestrate the validation and 00:07:58.020 --> 00:08:00.409 align:start position:0% basically orchestrate the validation and the<00:07:58.199> execution<00:07:58.560> of<00:07:58.800> this<00:07:58.979> user<00:07:59.280> operation<00:07:59.699> and 00:08:00.409 --> 00:08:00.419 align:start position:0% the execution of this user operation and 00:08:00.419 --> 00:08:02.510 align:start position:0% the execution of this user operation and it<00:08:00.599> does<00:08:00.780> so<00:08:00.960> by<00:08:01.319> calling<00:08:01.740> two<00:08:01.979> method<00:08:02.340> of<00:08:02.460> the 00:08:02.510 --> 00:08:02.520 align:start position:0% it does so by calling two method of the 00:08:02.520 --> 00:08:04.850 align:start position:0% it does so by calling two method of the on<00:08:02.759> the<00:08:02.880> wallet<00:08:03.180> a<00:08:03.660> first<00:08:03.900> method<00:08:04.319> to<00:08:04.440> validate 00:08:04.850 --> 00:08:04.860 align:start position:0% on the wallet a first method to validate 00:08:04.860 --> 00:08:06.350 align:start position:0% on the wallet a first method to validate the<00:08:05.039> transaction<00:08:05.400> basically<00:08:05.940> asking<00:08:06.240> the 00:08:06.350 --> 00:08:06.360 align:start position:0% the transaction basically asking the 00:08:06.360 --> 00:08:09.230 align:start position:0% the transaction basically asking the wallet<00:08:06.720> are<00:08:07.620> you<00:08:07.800> okay<00:08:07.979> to<00:08:08.460> execute<00:08:09.060> that 00:08:09.230 --> 00:08:09.240 align:start position:0% wallet are you okay to execute that 00:08:09.240 --> 00:08:10.969 align:start position:0% wallet are you okay to execute that operation<00:08:09.720> and<00:08:10.080> will<00:08:10.259> you<00:08:10.440> pay<00:08:10.560> you<00:08:10.800> know<00:08:10.860> will 00:08:10.969 --> 00:08:10.979 align:start position:0% operation and will you pay you know will 00:08:10.979 --> 00:08:13.189 align:start position:0% operation and will you pay you know will you<00:08:11.099> pay<00:08:11.280> the<00:08:11.400> fee<00:08:11.580> to<00:08:11.699> do<00:08:11.880> so<00:08:12.000> and<00:08:12.780> then<00:08:12.900> a 00:08:13.189 --> 00:08:13.199 align:start position:0% you pay the fee to do so and then a 00:08:13.199 --> 00:08:14.990 align:start position:0% you pay the fee to do so and then a second<00:08:13.380> call<00:08:13.680> to<00:08:13.919> execute<00:08:14.400> so<00:08:14.580> we<00:08:14.699> see<00:08:14.819> that 00:08:14.990 --> 00:08:15.000 align:start position:0% second call to execute so we see that 00:08:15.000 --> 00:08:17.150 align:start position:0% second call to execute so we see that with<00:08:15.120> 4337<00:08:15.960> there's<00:08:16.199> a<00:08:16.380> clear<00:08:16.560> separation 00:08:17.150 --> 00:08:17.160 align:start position:0% with 4337 there's a clear separation 00:08:17.160 --> 00:08:20.749 align:start position:0% with 4337 there's a clear separation between<00:08:17.580> validation<00:08:18.360> and<00:08:19.199> execution<00:08:19.740> okay<00:08:20.580> I 00:08:20.749 --> 00:08:20.759 align:start position:0% between validation and execution okay I 00:08:20.759 --> 00:08:23.210 align:start position:0% between validation and execution okay I mean<00:08:20.940> all<00:08:21.060> this<00:08:21.240> is<00:08:21.479> great<00:08:21.720> but<00:08:22.139> is<00:08:22.979> this 00:08:23.210 --> 00:08:23.220 align:start position:0% mean all this is great but is this 00:08:23.220 --> 00:08:25.010 align:start position:0% mean all this is great but is this really<00:08:23.460> the<00:08:23.879> end<00:08:24.000> of<00:08:24.120> account<00:08:24.240> abstraction<00:08:24.780> I 00:08:25.010 --> 00:08:25.020 align:start position:0% really the end of account abstraction I 00:08:25.020 --> 00:08:26.930 align:start position:0% really the end of account abstraction I mean<00:08:25.139> every<00:08:25.319> Ridge<00:08:25.680> the<00:08:25.919> Holy<00:08:26.220> Grail<00:08:26.520> of 00:08:26.930 --> 00:08:26.940 align:start position:0% mean every Ridge the Holy Grail of 00:08:26.940 --> 00:08:28.790 align:start position:0% mean every Ridge the Holy Grail of course<00:08:27.060> the<00:08:27.360> answer<00:08:27.479> is<00:08:27.780> no<00:08:27.960> each<00:08:28.440> of<00:08:28.560> these 00:08:28.790 --> 00:08:28.800 align:start position:0% course the answer is no each of these 00:08:28.800 --> 00:08:30.589 align:start position:0% course the answer is no each of these VIPs<00:08:29.099> that<00:08:29.520> have<00:08:29.639> been<00:08:29.819> proposed<00:08:30.240> over<00:08:30.360> the 00:08:30.589 --> 00:08:30.599 align:start position:0% VIPs that have been proposed over the 00:08:30.599 --> 00:08:31.309 align:start position:0% VIPs that have been proposed over the years 00:08:31.309 --> 00:08:31.319 align:start position:0% years 00:08:31.319 --> 00:08:33.769 align:start position:0% years they<00:08:32.219> all<00:08:32.399> bring<00:08:32.820> some<00:08:33.120> of<00:08:33.240> the<00:08:33.360> features<00:08:33.659> of 00:08:33.769 --> 00:08:33.779 align:start position:0% they all bring some of the features of 00:08:33.779 --> 00:08:35.329 align:start position:0% they all bring some of the features of account<00:08:33.959> abstraction<00:08:34.440> but<00:08:34.740> they<00:08:34.979> also<00:08:35.219> all 00:08:35.329 --> 00:08:35.339 align:start position:0% account abstraction but they also all 00:08:35.339 --> 00:08:39.529 align:start position:0% account abstraction but they also all have<00:08:35.520> limitation<00:08:36.060> if<00:08:36.899> we<00:08:37.020> look<00:08:37.140> at<00:08:37.320> the<00:08:37.380> ip4337 00:08:39.529 --> 00:08:39.539 align:start position:0% have limitation if we look at the ip4337 00:08:39.539 --> 00:08:41.269 align:start position:0% have limitation if we look at the ip4337 the<00:08:40.020> main<00:08:40.080> limitation<00:08:40.560> is<00:08:40.800> that<00:08:40.919> it<00:08:41.039> leaves 00:08:41.269 --> 00:08:41.279 align:start position:0% the main limitation is that it leaves 00:08:41.279 --> 00:08:44.290 align:start position:0% the main limitation is that it leaves that<00:08:41.339> the<00:08:41.520> application<00:08:41.940> layer<00:08:42.719> so<00:08:43.260> basically 00:08:44.290 --> 00:08:44.300 align:start position:0% that the application layer so basically 00:08:44.300 --> 00:08:47.210 align:start position:0% that the application layer so basically e4337<00:08:45.300> wallet<00:08:45.839> lag<00:08:46.200> smart<00:08:46.380> contract<00:08:46.800> wallet 00:08:47.210 --> 00:08:47.220 align:start position:0% e4337 wallet lag smart contract wallet 00:08:47.220 --> 00:08:49.430 align:start position:0% e4337 wallet lag smart contract wallet there<00:08:48.000> are<00:08:48.180> second<00:08:48.360> class<00:08:48.600> citizen<00:08:49.140> because 00:08:49.430 --> 00:08:49.440 align:start position:0% there are second class citizen because 00:08:49.440 --> 00:08:52.009 align:start position:0% there are second class citizen because they<00:08:49.860> still<00:08:50.100> live<00:08:50.279> on<00:08:50.519> a<00:08:50.700> chain<00:08:50.880> which<00:08:51.540> relies 00:08:52.009 --> 00:08:52.019 align:start position:0% they still live on a chain which relies 00:08:52.019 --> 00:08:54.530 align:start position:0% they still live on a chain which relies on<00:08:52.260> the<00:08:52.320> OAS<00:08:52.680> every<00:08:53.580> single<00:08:53.880> depth<00:08:54.300> the 00:08:54.530 --> 00:08:54.540 align:start position:0% on the OAS every single depth the 00:08:54.540 --> 00:08:56.630 align:start position:0% on the OAS every single depth the tooling<00:08:54.899> I<00:08:55.080> mean<00:08:55.200> the<00:08:55.380> way<00:08:55.560> developer<00:08:56.279> thinks 00:08:56.630 --> 00:08:56.640 align:start position:0% tooling I mean the way developer thinks 00:08:56.640 --> 00:08:58.310 align:start position:0% tooling I mean the way developer thinks about<00:08:56.760> account<00:08:57.060> we<00:08:57.480> all<00:08:57.600> think<00:08:57.839> in<00:08:58.019> terms<00:08:58.200> of 00:08:58.310 --> 00:08:58.320 align:start position:0% about account we all think in terms of 00:08:58.320 --> 00:09:00.410 align:start position:0% about account we all think in terms of uas<00:08:58.740> and<00:08:59.339> that<00:08:59.519> makes<00:08:59.700> Smart<00:09:00.000> contract 00:09:00.410 --> 00:09:00.420 align:start position:0% uas and that makes Smart contract 00:09:00.420 --> 00:09:02.750 align:start position:0% uas and that makes Smart contract quality<00:09:00.779> of<00:09:00.899> 437<00:09:01.560> wallet<00:09:02.040> second<00:09:02.519> class 00:09:02.750 --> 00:09:02.760 align:start position:0% quality of 437 wallet second class 00:09:02.760 --> 00:09:04.670 align:start position:0% quality of 437 wallet second class Citizen<00:09:03.240> and<00:09:03.720> that's<00:09:03.839> actually<00:09:04.019> a<00:09:04.320> blocker 00:09:04.670 --> 00:09:04.680 align:start position:0% Citizen and that's actually a blocker 00:09:04.680 --> 00:09:06.350 align:start position:0% Citizen and that's actually a blocker for<00:09:04.860> their<00:09:05.040> adoption 00:09:06.350 --> 00:09:06.360 align:start position:0% for their adoption 00:09:06.360 --> 00:09:08.930 align:start position:0% for their adoption so<00:09:07.200> what<00:09:07.560> can<00:09:07.740> you<00:09:08.100> know<00:09:08.220> what<00:09:08.339> can<00:09:08.459> we<00:09:08.640> do<00:09:08.760> next 00:09:08.930 --> 00:09:08.940 align:start position:0% so what can you know what can we do next 00:09:08.940 --> 00:09:11.030 align:start position:0% so what can you know what can we do next well<00:09:09.180> what<00:09:09.480> would<00:09:09.720> be<00:09:09.899> ideal<00:09:10.200> of<00:09:10.440> course<00:09:10.620> is<00:09:10.800> to 00:09:11.030 --> 00:09:11.040 align:start position:0% well what would be ideal of course is to 00:09:11.040 --> 00:09:13.130 align:start position:0% well what would be ideal of course is to bring<00:09:11.279> four<00:09:11.580> three<00:09:11.820> three<00:09:12.060> seven<00:09:12.300> one<00:09:12.839> layer 00:09:13.130 --> 00:09:13.140 align:start position:0% bring four three three seven one layer 00:09:13.140 --> 00:09:15.350 align:start position:0% bring four three three seven one layer down<00:09:13.320> to<00:09:14.040> bring<00:09:14.220> it<00:09:14.399> from<00:09:14.760> the<00:09:14.940> application 00:09:15.350 --> 00:09:15.360 align:start position:0% down to bring it from the application 00:09:15.360 --> 00:09:18.230 align:start position:0% down to bring it from the application layer<00:09:15.839> to<00:09:16.560> the<00:09:16.740> protocol<00:09:17.040> and<00:09:17.760> actually<00:09:17.940> the 00:09:18.230 --> 00:09:18.240 align:start position:0% layer to the protocol and actually the 00:09:18.240 --> 00:09:20.930 align:start position:0% layer to the protocol and actually the people<00:09:18.360> who<00:09:18.540> propose<00:09:18.899> 4337<00:09:19.740> are<00:09:20.519> working<00:09:20.700> on 00:09:20.930 --> 00:09:20.940 align:start position:0% people who propose 4337 are working on 00:09:20.940 --> 00:09:22.790 align:start position:0% people who propose 4337 are working on that<00:09:21.060> right<00:09:21.300> now<00:09:21.540> but<00:09:22.140> what<00:09:22.320> we<00:09:22.500> think<00:09:22.680> at 00:09:22.790 --> 00:09:22.800 align:start position:0% that right now but what we think at 00:09:22.800 --> 00:09:24.889 align:start position:0% that right now but what we think at origin<00:09:23.220> is<00:09:23.399> that<00:09:23.640> we<00:09:24.300> shouldn't<00:09:24.540> wait<00:09:24.720> for 00:09:24.889 --> 00:09:24.899 align:start position:0% origin is that we shouldn't wait for 00:09:24.899 --> 00:09:27.530 align:start position:0% origin is that we shouldn't wait for that<00:09:25.080> to<00:09:25.200> happen<00:09:25.320> on<00:09:25.620> L1<00:09:25.980> I<00:09:26.820> mean<00:09:26.940> we<00:09:27.360> are 00:09:27.530 --> 00:09:27.540 align:start position:0% that to happen on L1 I mean we are 00:09:27.540 --> 00:09:30.110 align:start position:0% that to happen on L1 I mean we are knowing<00:09:27.959> an<00:09:28.140> era<00:09:28.440> where<00:09:28.620> the<00:09:29.220> layer<00:09:29.700> twos<00:09:29.940> are 00:09:30.110 --> 00:09:30.120 align:start position:0% knowing an era where the layer twos are 00:09:30.120 --> 00:09:31.670 align:start position:0% knowing an era where the layer twos are picking<00:09:30.420> up<00:09:30.540> it's<00:09:30.899> actually<00:09:31.080> an<00:09:31.380> amazing 00:09:31.670 --> 00:09:31.680 align:start position:0% picking up it's actually an amazing 00:09:31.680 --> 00:09:33.470 align:start position:0% picking up it's actually an amazing opportunity<00:09:32.279> to<00:09:32.760> fix<00:09:32.940> some<00:09:33.240> of<00:09:33.300> this 00:09:33.470 --> 00:09:33.480 align:start position:0% opportunity to fix some of this 00:09:33.480 --> 00:09:36.050 align:start position:0% opportunity to fix some of this limitation<00:09:33.959> of<00:09:34.320> of<00:09:34.740> ethereum<00:09:35.220> I<00:09:35.399> mean<00:09:35.519> the<00:09:35.640> evm 00:09:36.050 --> 00:09:36.060 align:start position:0% limitation of of ethereum I mean the evm 00:09:36.060 --> 00:09:38.509 align:start position:0% limitation of of ethereum I mean the evm is<00:09:36.240> a<00:09:36.360> great<00:09:36.480> VM<00:09:36.899> but<00:09:37.560> we<00:09:37.800> know<00:09:37.920> that<00:09:38.160> there<00:09:38.399> are 00:09:38.509 --> 00:09:38.519 align:start position:0% is a great VM but we know that there are 00:09:38.519 --> 00:09:40.190 align:start position:0% is a great VM but we know that there are stuff<00:09:38.820> there<00:09:39.300> are<00:09:39.420> some<00:09:39.540> limitations<00:09:39.959> there 00:09:40.190 --> 00:09:40.200 align:start position:0% stuff there are some limitations there 00:09:40.200 --> 00:09:41.630 align:start position:0% stuff there are some limitations there are<00:09:40.380> stuff<00:09:40.500> that<00:09:40.680> we<00:09:40.860> now<00:09:41.040> know<00:09:41.220> can<00:09:41.459> be 00:09:41.630 --> 00:09:41.640 align:start position:0% are stuff that we now know can be 00:09:41.640 --> 00:09:43.490 align:start position:0% are stuff that we now know can be improved<00:09:42.000> and<00:09:42.360> so<00:09:42.540> we<00:09:42.660> believe<00:09:42.779> that<00:09:43.019> layer<00:09:43.320> 2 00:09:43.490 --> 00:09:43.500 align:start position:0% improved and so we believe that layer 2 00:09:43.500 --> 00:09:45.170 align:start position:0% improved and so we believe that layer 2 is<00:09:43.740> actually<00:09:43.860> the<00:09:44.100> great<00:09:44.339> moment<00:09:44.640> to<00:09:44.880> do<00:09:45.000> so 00:09:45.170 --> 00:09:45.180 align:start position:0% is actually the great moment to do so 00:09:45.180 --> 00:09:47.870 align:start position:0% is actually the great moment to do so and<00:09:46.140> that's<00:09:46.380> why<00:09:46.620> I<00:09:46.800> mean<00:09:46.980> we've<00:09:47.339> been<00:09:47.519> really 00:09:47.870 --> 00:09:47.880 align:start position:0% and that's why I mean we've been really 00:09:47.880 --> 00:09:50.150 align:start position:0% and that's why I mean we've been really excited<00:09:48.300> lately<00:09:48.660> because<00:09:48.839> two<00:09:49.260> of<00:09:49.500> the<00:09:49.860> major 00:09:50.150 --> 00:09:50.160 align:start position:0% excited lately because two of the major 00:09:50.160 --> 00:09:52.910 align:start position:0% excited lately because two of the major layer<00:09:50.700> 2<00:09:50.820> providers<00:09:51.360> namely<00:09:52.019> stocknet<00:09:52.500> and<00:09:52.620> ZK 00:09:52.910 --> 00:09:52.920 align:start position:0% layer 2 providers namely stocknet and ZK 00:09:52.920 --> 00:09:55.970 align:start position:0% layer 2 providers namely stocknet and ZK sync<00:09:53.279> have<00:09:53.820> committed<00:09:54.360> to<00:09:54.779> ship<00:09:55.260> with<00:09:55.620> Native 00:09:55.970 --> 00:09:55.980 align:start position:0% sync have committed to ship with Native 00:09:55.980 --> 00:09:57.949 align:start position:0% sync have committed to ship with Native account<00:09:56.160> abstraction<00:09:56.820> and<00:09:57.360> so<00:09:57.480> at<00:09:57.600> origin 00:09:57.949 --> 00:09:57.959 align:start position:0% account abstraction and so at origin 00:09:57.959 --> 00:09:59.690 align:start position:0% account abstraction and so at origin we've<00:09:58.200> been<00:09:58.260> working<00:09:58.440> with<00:09:58.740> them<00:09:58.920> uh<00:09:59.519> quite 00:09:59.690 --> 00:09:59.700 align:start position:0% we've been working with them uh quite 00:09:59.700 --> 00:10:01.190 align:start position:0% we've been working with them uh quite closely<00:10:00.000> for<00:10:00.180> the<00:10:00.300> past<00:10:00.480> year<00:10:00.660> trying<00:10:01.019> to 00:10:01.190 --> 00:10:01.200 align:start position:0% closely for the past year trying to 00:10:01.200 --> 00:10:03.110 align:start position:0% closely for the past year trying to bring<00:10:01.440> our<00:10:01.740> experience<00:10:02.100> as<00:10:02.399> a<00:10:02.580> smart<00:10:02.700> contract 00:10:03.110 --> 00:10:03.120 align:start position:0% bring our experience as a smart contract 00:10:03.120 --> 00:10:05.570 align:start position:0% bring our experience as a smart contract a<00:10:03.660> wallet<00:10:04.080> company<00:10:04.320> and<00:10:04.740> making<00:10:04.920> sure<00:10:05.220> we<00:10:05.459> can 00:10:05.570 --> 00:10:05.580 align:start position:0% a wallet company and making sure we can 00:10:05.580 --> 00:10:07.610 align:start position:0% a wallet company and making sure we can really<00:10:05.760> design<00:10:05.940> a<00:10:06.120> kind<00:10:06.240> of<00:10:06.300> abstraction<00:10:06.959> the 00:10:07.610 --> 00:10:07.620 align:start position:0% really design a kind of abstraction the 00:10:07.620 --> 00:10:09.829 align:start position:0% really design a kind of abstraction the way<00:10:07.800> it's<00:10:07.980> needed<00:10:08.399> for<00:10:08.820> for<00:10:09.060> users<00:10:09.480> and<00:10:09.660> for 00:10:09.829 --> 00:10:09.839 align:start position:0% way it's needed for for users and for 00:10:09.839 --> 00:10:12.470 align:start position:0% way it's needed for for users and for the<00:10:10.019> next<00:10:10.080> wave<00:10:10.440> of<00:10:10.620> of<00:10:10.980> users<00:10:11.519> so<00:10:12.240> in<00:10:12.360> the 00:10:12.470 --> 00:10:12.480 align:start position:0% the next wave of of users so in the 00:10:12.480 --> 00:10:14.269 align:start position:0% the next wave of of users so in the remaining<00:10:12.779> of<00:10:12.899> the<00:10:13.019> talk<00:10:13.200> I'll<00:10:13.860> basically 00:10:14.269 --> 00:10:14.279 align:start position:0% remaining of the talk I'll basically 00:10:14.279 --> 00:10:16.190 align:start position:0% remaining of the talk I'll basically focus<00:10:14.640> on<00:10:14.820> stacknet<00:10:15.420> and<00:10:15.540> give<00:10:15.720> you<00:10:15.839> some<00:10:16.019> some 00:10:16.190 --> 00:10:16.200 align:start position:0% focus on stacknet and give you some some 00:10:16.200 --> 00:10:18.470 align:start position:0% focus on stacknet and give you some some example<00:10:16.680> in<00:10:16.800> the<00:10:16.920> stagnet<00:10:17.279> ecosystem<00:10:17.700> but 00:10:18.470 --> 00:10:18.480 align:start position:0% example in the stagnet ecosystem but 00:10:18.480 --> 00:10:20.509 align:start position:0% example in the stagnet ecosystem but just<00:10:18.720> remember<00:10:18.899> remember<00:10:19.260> that<00:10:19.800> everything<00:10:20.220> I 00:10:20.509 --> 00:10:20.519 align:start position:0% just remember remember that everything I 00:10:20.519 --> 00:10:23.389 align:start position:0% just remember remember that everything I will<00:10:20.700> say<00:10:20.820> applies<00:10:21.480> to<00:10:21.600> Z<00:10:21.779> casing<00:10:22.200> as<00:10:22.380> well 00:10:23.389 --> 00:10:23.399 align:start position:0% will say applies to Z casing as well 00:10:23.399 --> 00:10:25.850 align:start position:0% will say applies to Z casing as well so<00:10:23.880> with<00:10:24.660> account<00:10:24.959> abstraction<00:10:25.440> every 00:10:25.850 --> 00:10:25.860 align:start position:0% so with account abstraction every 00:10:25.860 --> 00:10:28.070 align:start position:0% so with account abstraction every account<00:10:26.160> is<00:10:26.399> a<00:10:26.519> smart<00:10:26.640> contract<00:10:27.120> but<00:10:27.959> of 00:10:28.070 --> 00:10:28.080 align:start position:0% account is a smart contract but of 00:10:28.080 --> 00:10:29.750 align:start position:0% account is a smart contract but of course<00:10:28.200> it<00:10:28.380> cannot<00:10:28.680> be<00:10:28.860> any<00:10:29.100> smart<00:10:29.339> contract 00:10:29.750 --> 00:10:29.760 align:start position:0% course it cannot be any smart contract 00:10:29.760 --> 00:10:32.210 align:start position:0% course it cannot be any smart contract right<00:10:30.000> the<00:10:30.420> protocol<00:10:30.779> or<00:10:31.140> the<00:10:31.260> VM<00:10:31.560> needs<00:10:32.100> to 00:10:32.210 --> 00:10:32.220 align:start position:0% right the protocol or the VM needs to 00:10:32.220 --> 00:10:34.250 align:start position:0% right the protocol or the VM needs to know<00:10:32.399> how<00:10:32.760> to<00:10:32.940> interact<00:10:33.300> with<00:10:33.600> that<00:10:33.839> account 00:10:34.250 --> 00:10:34.260 align:start position:0% know how to interact with that account 00:10:34.260 --> 00:10:36.410 align:start position:0% know how to interact with that account contract<00:10:34.920> that<00:10:35.580> means<00:10:35.820> that<00:10:36.060> the<00:10:36.300> account 00:10:36.410 --> 00:10:36.420 align:start position:0% contract that means that the account 00:10:36.420 --> 00:10:39.410 align:start position:0% contract that means that the account must<00:10:36.959> comply<00:10:37.320> to<00:10:37.500> a<00:10:37.860> certain<00:10:38.100> interface<00:10:38.700> and 00:10:39.410 --> 00:10:39.420 align:start position:0% must comply to a certain interface and 00:10:39.420 --> 00:10:40.910 align:start position:0% must comply to a certain interface and so<00:10:39.540> we've<00:10:39.720> been<00:10:39.839> working<00:10:40.019> with<00:10:40.320> starknet<00:10:40.860> and 00:10:40.910 --> 00:10:40.920 align:start position:0% so we've been working with starknet and 00:10:40.920 --> 00:10:42.949 align:start position:0% so we've been working with starknet and open<00:10:41.279> Zeppelin<00:10:41.820> and<00:10:42.180> defining<00:10:42.779> that 00:10:42.949 --> 00:10:42.959 align:start position:0% open Zeppelin and defining that 00:10:42.959 --> 00:10:45.170 align:start position:0% open Zeppelin and defining that interface<00:10:43.500> for<00:10:44.100> stacknet<00:10:44.640> and<00:10:44.820> we<00:10:44.880> came<00:10:45.060> up 00:10:45.170 --> 00:10:45.180 align:start position:0% interface for stacknet and we came up 00:10:45.180 --> 00:10:47.449 align:start position:0% interface for stacknet and we came up with<00:10:45.300> the<00:10:45.600> following<00:10:45.899> interface<00:10:46.860> it's 00:10:47.449 --> 00:10:47.459 align:start position:0% with the following interface it's 00:10:47.459 --> 00:10:49.430 align:start position:0% with the following interface it's written<00:10:47.760> in<00:10:47.940> Cairo<00:10:48.360> so<00:10:48.540> don't<00:10:48.720> worry<00:10:48.959> is<00:10:49.140> that 00:10:49.430 --> 00:10:49.440 align:start position:0% written in Cairo so don't worry is that 00:10:49.440 --> 00:10:51.230 align:start position:0% written in Cairo so don't worry is that you<00:10:49.680> know<00:10:49.800> the<00:10:49.920> style<00:10:50.100> might<00:10:50.339> be<00:10:50.519> a<00:10:50.640> bit<00:10:50.760> a<00:10:51.060> bit 00:10:51.230 --> 00:10:51.240 align:start position:0% you know the style might be a bit a bit 00:10:51.240 --> 00:10:53.569 align:start position:0% you know the style might be a bit a bit surprising<00:10:51.720> but<00:10:52.380> what's<00:10:52.860> important<00:10:53.220> to<00:10:53.459> note 00:10:53.569 --> 00:10:53.579 align:start position:0% surprising but what's important to note 00:10:53.579 --> 00:10:56.870 align:start position:0% surprising but what's important to note is<00:10:53.880> that<00:10:54.240> just<00:10:54.779> like<00:10:54.959> in<00:10:55.140> the<00:10:55.339> ip4337<00:10:56.339> we<00:10:56.760> have 00:10:56.870 --> 00:10:56.880 align:start position:0% is that just like in the ip4337 we have 00:10:56.880 --> 00:10:59.750 align:start position:0% is that just like in the ip4337 we have a<00:10:57.060> method<00:10:57.420> to<00:10:57.720> validate<00:10:58.200> a<00:10:58.380> transaction<00:10:58.800> so 00:10:59.750 --> 00:10:59.760 align:start position:0% a method to validate a transaction so 00:10:59.760 --> 00:11:01.790 align:start position:0% a method to validate a transaction so every<00:11:00.060> account<00:11:00.300> must<00:11:00.720> expose<00:11:01.140> a<00:11:01.320> method<00:11:01.620> to 00:11:01.790 --> 00:11:01.800 align:start position:0% every account must expose a method to 00:11:01.800 --> 00:11:05.210 align:start position:0% every account must expose a method to say<00:11:01.980> to<00:11:02.760> to<00:11:03.000> validate<00:11:03.480> and<00:11:03.899> decide<00:11:04.260> what<00:11:05.100> kind 00:11:05.210 --> 00:11:05.220 align:start position:0% say to to validate and decide what kind 00:11:05.220 --> 00:11:07.130 align:start position:0% say to to validate and decide what kind of<00:11:05.339> signature<00:11:05.760> schemes<00:11:06.180> it<00:11:06.300> wants<00:11:06.540> to<00:11:06.600> use<00:11:06.839> you 00:11:07.130 --> 00:11:07.140 align:start position:0% of signature schemes it wants to use you 00:11:07.140 --> 00:11:08.930 align:start position:0% of signature schemes it wants to use you know<00:11:07.260> what<00:11:07.500> kind<00:11:07.680> of<00:11:07.800> nodes<00:11:08.040> mechanism<00:11:08.579> and<00:11:08.760> so 00:11:08.930 --> 00:11:08.940 align:start position:0% know what kind of nodes mechanism and so 00:11:08.940 --> 00:11:11.750 align:start position:0% know what kind of nodes mechanism and so on<00:11:09.060> and<00:11:09.779> there's<00:11:09.959> a<00:11:10.140> method<00:11:10.380> to<00:11:10.560> execute<00:11:10.980> to 00:11:11.750 --> 00:11:11.760 align:start position:0% on and there's a method to execute to 00:11:11.760 --> 00:11:13.610 align:start position:0% on and there's a method to execute to really<00:11:11.880> execute<00:11:12.360> the<00:11:12.540> call<00:11:12.720> and<00:11:13.140> interact 00:11:13.610 --> 00:11:13.620 align:start position:0% really execute the call and interact 00:11:13.620 --> 00:11:16.009 align:start position:0% really execute the call and interact with<00:11:13.920> other<00:11:14.160> contract<00:11:14.640> and<00:11:15.420> because<00:11:15.600> we<00:11:15.899> are 00:11:16.009 --> 00:11:16.019 align:start position:0% with other contract and because we are 00:11:16.019 --> 00:11:17.930 align:start position:0% with other contract and because we are starting<00:11:16.200> with<00:11:16.500> a<00:11:16.680> blank<00:11:16.860> page<00:11:17.100> on<00:11:17.339> stagnet<00:11:17.820> we 00:11:17.930 --> 00:11:17.940 align:start position:0% starting with a blank page on stagnet we 00:11:17.940 --> 00:11:21.110 align:start position:0% starting with a blank page on stagnet we did<00:11:18.060> something<00:11:18.240> very<00:11:18.600> cool<00:11:18.839> is<00:11:19.800> that<00:11:20.399> we 00:11:21.110 --> 00:11:21.120 align:start position:0% did something very cool is that we 00:11:21.120 --> 00:11:23.690 align:start position:0% did something very cool is that we introduce<00:11:21.540> multicol<00:11:22.079> natively<00:11:22.620> so<00:11:23.220> on<00:11:23.399> stock 00:11:23.690 --> 00:11:23.700 align:start position:0% introduce multicol natively so on stock 00:11:23.700 --> 00:11:25.850 align:start position:0% introduce multicol natively so on stock net<00:11:24.000> every<00:11:24.600> transaction<00:11:25.140> is<00:11:25.440> actually<00:11:25.620> a 00:11:25.850 --> 00:11:25.860 align:start position:0% net every transaction is actually a 00:11:25.860 --> 00:11:28.610 align:start position:0% net every transaction is actually a multi-call<00:11:26.339> by<00:11:26.940> definition<00:11:27.120> natively<00:11:28.079> and 00:11:28.610 --> 00:11:28.620 align:start position:0% multi-call by definition natively and 00:11:28.620 --> 00:11:30.769 align:start position:0% multi-call by definition natively and I'll<00:11:28.800> come<00:11:28.980> back<00:11:29.160> on<00:11:29.459> why<00:11:29.880> that<00:11:30.180> is<00:11:30.300> exciting 00:11:30.769 --> 00:11:30.779 align:start position:0% I'll come back on why that is exciting 00:11:30.779 --> 00:11:32.810 align:start position:0% I'll come back on why that is exciting in<00:11:31.380> a<00:11:31.500> few<00:11:31.620> minutes 00:11:32.810 --> 00:11:32.820 align:start position:0% in a few minutes 00:11:32.820 --> 00:11:34.670 align:start position:0% in a few minutes on<00:11:33.300> top<00:11:33.420> of<00:11:33.540> these<00:11:33.720> two<00:11:33.839> method<00:11:34.079> we<00:11:34.320> also<00:11:34.560> have 00:11:34.670 --> 00:11:34.680 align:start position:0% on top of these two method we also have 00:11:34.680 --> 00:11:37.190 align:start position:0% on top of these two method we also have a<00:11:34.800> method<00:11:35.100> to<00:11:35.579> validate<00:11:36.420> the<00:11:36.540> deployment<00:11:36.959> of 00:11:37.190 --> 00:11:37.200 align:start position:0% a method to validate the deployment of 00:11:37.200 --> 00:11:39.470 align:start position:0% a method to validate the deployment of an<00:11:37.320> account<00:11:37.500> that<00:11:37.920> means<00:11:38.160> that<00:11:38.459> no<00:11:38.940> account 00:11:39.470 --> 00:11:39.480 align:start position:0% an account that means that no account 00:11:39.480 --> 00:11:41.509 align:start position:0% an account that means that no account contract<00:11:40.019> on<00:11:40.260> stagnet<00:11:40.800> can<00:11:40.980> pay<00:11:41.160> for<00:11:41.399> their 00:11:41.509 --> 00:11:41.519 align:start position:0% contract on stagnet can pay for their 00:11:41.519 --> 00:11:44.090 align:start position:0% contract on stagnet can pay for their own<00:11:41.700> deployment<00:11:42.120> that<00:11:43.079> again<00:11:43.500> it's<00:11:43.860> something 00:11:44.090 --> 00:11:44.100 align:start position:0% own deployment that again it's something 00:11:44.100 --> 00:11:47.210 align:start position:0% own deployment that again it's something that<00:11:44.519> enables<00:11:45.120> a<00:11:45.300> great<00:11:45.540> user<00:11:45.899> experience<00:11:46.260> and 00:11:47.210 --> 00:11:47.220 align:start position:0% that enables a great user experience and 00:11:47.220 --> 00:11:49.069 align:start position:0% that enables a great user experience and finally<00:11:47.519> we<00:11:47.820> have<00:11:47.940> one<00:11:48.240> last<00:11:48.540> important 00:11:49.069 --> 00:11:49.079 align:start position:0% finally we have one last important 00:11:49.079 --> 00:11:51.650 align:start position:0% finally we have one last important method<00:11:49.440> called<00:11:50.040> is<00:11:50.339> valid<00:11:50.579> signature 00:11:51.650 --> 00:11:51.660 align:start position:0% method called is valid signature 00:11:51.660 --> 00:11:53.630 align:start position:0% method called is valid signature uh<00:11:52.260> in<00:11:52.380> the<00:11:52.500> idea<00:11:52.680> of<00:11:52.740> his<00:11:52.860> body<00:11:53.040> signature<00:11:53.519> is 00:11:53.630 --> 00:11:53.640 align:start position:0% uh in the idea of his body signature is 00:11:53.640 --> 00:11:55.130 align:start position:0% uh in the idea of his body signature is to<00:11:53.820> basically<00:11:54.120> verify<00:11:54.600> off-chain 00:11:55.130 --> 00:11:55.140 align:start position:0% to basically verify off-chain 00:11:55.140 --> 00:11:56.930 align:start position:0% to basically verify off-chain transactions<00:11:55.800> all<00:11:56.160> right<00:11:56.339> again<00:11:56.459> I'll<00:11:56.760> come 00:11:56.930 --> 00:11:56.940 align:start position:0% transactions all right again I'll come 00:11:56.940 --> 00:11:58.910 align:start position:0% transactions all right again I'll come back<00:11:57.060> to<00:11:57.240> that<00:11:57.420> but<00:11:57.899> smart<00:11:58.200> contract<00:11:58.680> they 00:11:58.910 --> 00:11:58.920 align:start position:0% back to that but smart contract they 00:11:58.920 --> 00:12:00.829 align:start position:0% back to that but smart contract they cannot<00:11:59.220> sign<00:11:59.399> but<00:12:00.120> they<00:12:00.300> can<00:12:00.420> delegate 00:12:00.829 --> 00:12:00.839 align:start position:0% cannot sign but they can delegate 00:12:00.839 --> 00:12:03.470 align:start position:0% cannot sign but they can delegate signature<00:12:01.380> to<00:12:01.740> signers<00:12:02.279> to<00:12:02.519> keys<00:12:02.880> but<00:12:03.300> they 00:12:03.470 --> 00:12:03.480 align:start position:0% signature to signers to keys but they 00:12:03.480 --> 00:12:05.269 align:start position:0% signature to signers to keys but they must<00:12:03.660> expose<00:12:04.019> a<00:12:04.200> way<00:12:04.380> to<00:12:04.560> say<00:12:04.680> okay<00:12:04.980> this 00:12:05.269 --> 00:12:05.279 align:start position:0% must expose a way to say okay this 00:12:05.279 --> 00:12:06.910 align:start position:0% must expose a way to say okay this signature<00:12:05.820> is<00:12:05.880> actually<00:12:06.120> valid<00:12:06.540> for<00:12:06.720> myself 00:12:06.910 --> 00:12:06.920 align:start position:0% signature is actually valid for myself 00:12:06.920 --> 00:12:09.350 align:start position:0% signature is actually valid for myself and<00:12:07.920> on<00:12:08.160> on<00:12:08.279> ethereum<00:12:08.760> this<00:12:09.000> is<00:12:09.120> the 00:12:09.350 --> 00:12:09.360 align:start position:0% and on on ethereum this is the 00:12:09.360 --> 00:12:12.769 align:start position:0% and on on ethereum this is the equivalent<00:12:09.899> of<00:12:10.019> VIP<00:12:10.459> 1271.<00:12:11.459> okay<00:12:12.120> since<00:12:12.540> this 00:12:12.769 --> 00:12:12.779 align:start position:0% equivalent of VIP 1271. okay since this 00:12:12.779 --> 00:12:14.870 align:start position:0% equivalent of VIP 1271. okay since this is<00:12:12.959> a<00:12:13.079> developer<00:12:13.500> conference<00:12:14.100> there's 00:12:14.870 --> 00:12:14.880 align:start position:0% is a developer conference there's 00:12:14.880 --> 00:12:16.430 align:start position:0% is a developer conference there's basically<00:12:15.300> five<00:12:15.660> things<00:12:15.899> that<00:12:16.140> you<00:12:16.260> need<00:12:16.380> to 00:12:16.430 --> 00:12:16.440 align:start position:0% basically five things that you need to 00:12:16.440 --> 00:12:18.050 align:start position:0% basically five things that you need to remember<00:12:16.560> as<00:12:16.920> a<00:12:17.040> developer<00:12:17.459> if<00:12:17.760> you<00:12:17.820> want<00:12:17.940> to 00:12:18.050 --> 00:12:18.060 align:start position:0% remember as a developer if you want to 00:12:18.060 --> 00:12:19.790 align:start position:0% remember as a developer if you want to build<00:12:18.180> for<00:12:18.420> account<00:12:18.540> abstraction<00:12:19.079> the<00:12:19.680> first 00:12:19.790 --> 00:12:19.800 align:start position:0% build for account abstraction the first 00:12:19.800 --> 00:12:21.470 align:start position:0% build for account abstraction the first one<00:12:19.980> is<00:12:20.160> that<00:12:20.279> accounts<00:12:20.700> are<00:12:20.760> smart<00:12:21.000> contract 00:12:21.470 --> 00:12:21.480 align:start position:0% one is that accounts are smart contract 00:12:21.480 --> 00:12:23.810 align:start position:0% one is that accounts are smart contract and<00:12:22.079> so<00:12:22.200> they<00:12:22.380> need<00:12:22.500> to<00:12:22.560> be<00:12:22.680> deployed 00:12:23.810 --> 00:12:23.820 align:start position:0% and so they need to be deployed 00:12:23.820 --> 00:12:25.790 align:start position:0% and so they need to be deployed thankfully<00:12:24.480> this<00:12:24.779> is<00:12:24.959> something<00:12:25.140> that<00:12:25.380> wallet 00:12:25.790 --> 00:12:25.800 align:start position:0% thankfully this is something that wallet 00:12:25.800 --> 00:12:27.350 align:start position:0% thankfully this is something that wallet will<00:12:25.980> take<00:12:26.160> care<00:12:26.279> of<00:12:26.399> but<00:12:26.640> you<00:12:26.820> still<00:12:27.000> need<00:12:27.240> to 00:12:27.350 --> 00:12:27.360 align:start position:0% will take care of but you still need to 00:12:27.360 --> 00:12:29.930 align:start position:0% will take care of but you still need to think<00:12:27.660> that<00:12:28.320> there<00:12:28.500> is<00:12:28.680> a<00:12:28.800> an<00:12:29.220> account<00:12:29.399> behind 00:12:29.930 --> 00:12:29.940 align:start position:0% think that there is a an account behind 00:12:29.940 --> 00:12:32.389 align:start position:0% think that there is a an account behind every<00:12:30.240> every<00:12:30.779> wallet<00:12:31.200> the<00:12:31.860> address<00:12:31.980> of<00:12:32.279> this 00:12:32.389 --> 00:12:32.399 align:start position:0% every every wallet the address of this 00:12:32.399 --> 00:12:33.710 align:start position:0% every every wallet the address of this account<00:12:32.579> is<00:12:32.880> computed<00:12:33.300> like<00:12:33.480> a<00:12:33.600> smart 00:12:33.710 --> 00:12:33.720 align:start position:0% account is computed like a smart 00:12:33.720 --> 00:12:35.509 align:start position:0% account is computed like a smart contract<00:12:34.140> so<00:12:34.380> there's<00:12:34.560> no<00:12:34.800> link<00:12:34.980> between<00:12:35.279> the 00:12:35.509 --> 00:12:35.519 align:start position:0% contract so there's no link between the 00:12:35.519 --> 00:12:38.210 align:start position:0% contract so there's no link between the signer<00:12:35.940> like<00:12:36.120> on<00:12:36.300> ethereum<00:12:36.720> it's<00:12:37.440> it's<00:12:37.740> a<00:12:38.100> new 00:12:38.210 --> 00:12:38.220 align:start position:0% signer like on ethereum it's it's a new 00:12:38.220 --> 00:12:40.250 align:start position:0% signer like on ethereum it's it's a new address<00:12:38.519> for<00:12:39.060> a<00:12:39.420> smart<00:12:39.600> contract<00:12:40.019> being 00:12:40.250 --> 00:12:40.260 align:start position:0% address for a smart contract being 00:12:40.260 --> 00:12:42.590 align:start position:0% address for a smart contract being deployed<00:12:41.160> transactions<00:12:42.000> can<00:12:42.180> have<00:12:42.300> multiple 00:12:42.590 --> 00:12:42.600 align:start position:0% deployed transactions can have multiple 00:12:42.600 --> 00:12:45.350 align:start position:0% deployed transactions can have multiple signature<00:12:43.200> so<00:12:43.860> we<00:12:44.040> need<00:12:44.160> to<00:12:44.339> think<00:12:44.579> that<00:12:44.940> you 00:12:45.350 --> 00:12:45.360 align:start position:0% signature so we need to think that you 00:12:45.360 --> 00:12:47.269 align:start position:0% signature so we need to think that you cannot<00:12:45.660> assume<00:12:46.139> that<00:12:46.380> for<00:12:46.620> an<00:12:46.800> account<00:12:46.980> has 00:12:47.269 --> 00:12:47.279 align:start position:0% cannot assume that for an account has 00:12:47.279 --> 00:12:48.650 align:start position:0% cannot assume that for an account has only<00:12:47.459> one<00:12:47.639> signer<00:12:48.060> maybe<00:12:48.240> it's<00:12:48.420> a<00:12:48.540> native 00:12:48.650 --> 00:12:48.660 align:start position:0% only one signer maybe it's a native 00:12:48.660 --> 00:12:50.030 align:start position:0% only one signer maybe it's a native multisig<00:12:49.260> so<00:12:49.380> you<00:12:49.500> shouldn't<00:12:49.740> make<00:12:49.860> any 00:12:50.030 --> 00:12:50.040 align:start position:0% multisig so you shouldn't make any 00:12:50.040 --> 00:12:51.829 align:start position:0% multisig so you shouldn't make any assumption<00:12:50.459> and<00:12:50.700> signatures<00:12:51.300> can<00:12:51.540> basically 00:12:51.829 --> 00:12:51.839 align:start position:0% assumption and signatures can basically 00:12:51.839 --> 00:12:54.470 align:start position:0% assumption and signatures can basically be<00:12:52.019> an<00:12:52.560> array<00:12:52.920> and<00:12:53.820> then<00:12:53.940> if<00:12:54.120> you<00:12:54.180> want<00:12:54.360> to 00:12:54.470 --> 00:12:54.480 align:start position:0% be an array and then if you want to 00:12:54.480 --> 00:12:57.410 align:start position:0% be an array and then if you want to verify<00:12:54.839> option<00:12:55.139> signature<00:12:55.800> you<00:12:56.459> cannot<00:12:56.700> use<00:12:57.000> a 00:12:57.410 --> 00:12:57.420 align:start position:0% verify option signature you cannot use a 00:12:57.420 --> 00:12:59.269 align:start position:0% verify option signature you cannot use a local<00:12:57.600> EC<00:12:58.079> recovery<00:12:58.620> that<00:12:58.800> you've<00:12:58.980> been<00:12:59.100> used 00:12:59.269 --> 00:12:59.279 align:start position:0% local EC recovery that you've been used 00:12:59.279 --> 00:13:01.310 align:start position:0% local EC recovery that you've been used to<00:12:59.459> you<00:13:00.120> need<00:13:00.240> to<00:13:00.360> actually<00:13:00.600> ping<00:13:01.019> the<00:13:01.200> account 00:13:01.310 --> 00:13:01.320 align:start position:0% to you need to actually ping the account 00:13:01.320 --> 00:13:03.829 align:start position:0% to you need to actually ping the account and<00:13:01.680> say<00:13:01.860> is<00:13:02.100> this<00:13:02.339> signature<00:13:02.820> valid 00:13:03.829 --> 00:13:03.839 align:start position:0% and say is this signature valid 00:13:03.839 --> 00:13:06.110 align:start position:0% and say is this signature valid and<00:13:04.380> finally<00:13:04.740> you<00:13:05.040> can<00:13:05.220> and<00:13:05.579> you<00:13:05.820> should<00:13:05.940> use 00:13:06.110 --> 00:13:06.120 align:start position:0% and finally you can and you should use 00:13:06.120 --> 00:13:08.090 align:start position:0% and finally you can and you should use multiples<00:13:06.660> because<00:13:06.959> it<00:13:07.200> improves<00:13:07.620> the<00:13:07.800> user 00:13:08.090 --> 00:13:08.100 align:start position:0% multiples because it improves the user 00:13:08.100 --> 00:13:11.930 align:start position:0% multiples because it improves the user experience<00:13:08.459> by<00:13:08.880> a<00:13:09.660> 10x<00:13:10.139> Factor<00:13:10.560> at<00:13:11.040> least 00:13:11.930 --> 00:13:11.940 align:start position:0% experience by a 10x Factor at least 00:13:11.940 --> 00:13:13.250 align:start position:0% experience by a 10x Factor at least and<00:13:12.300> that's<00:13:12.420> basically<00:13:12.720> all<00:13:12.899> you<00:13:13.019> need<00:13:13.139> to 00:13:13.250 --> 00:13:13.260 align:start position:0% and that's basically all you need to 00:13:13.260 --> 00:13:14.930 align:start position:0% and that's basically all you need to remember<00:13:13.380> so<00:13:13.860> if<00:13:13.980> you<00:13:14.100> are<00:13:14.220> the<00:13:14.399> developer<00:13:14.760> if 00:13:14.930 --> 00:13:14.940 align:start position:0% remember so if you are the developer if 00:13:14.940 --> 00:13:16.970 align:start position:0% remember so if you are the developer if you<00:13:15.060> come<00:13:15.180> out<00:13:15.300> of<00:13:15.420> this<00:13:15.540> talk<00:13:15.779> by<00:13:16.079> remembering 00:13:16.970 --> 00:13:16.980 align:start position:0% you come out of this talk by remembering 00:13:16.980 --> 00:13:19.610 align:start position:0% you come out of this talk by remembering this<00:13:17.220> five<00:13:17.399> point<00:13:17.639> I<00:13:18.000> think<00:13:18.180> we<00:13:18.720> are<00:13:18.899> in<00:13:19.500> good 00:13:19.610 --> 00:13:19.620 align:start position:0% this five point I think we are in good 00:13:19.620 --> 00:13:22.790 align:start position:0% this five point I think we are in good position<00:13:19.860> okay<00:13:20.839> so<00:13:21.839> as<00:13:22.200> I<00:13:22.320> said<00:13:22.440> we've<00:13:22.680> been 00:13:22.790 --> 00:13:22.800 align:start position:0% position okay so as I said we've been 00:13:22.800 --> 00:13:24.650 align:start position:0% position okay so as I said we've been you<00:13:23.040> know<00:13:23.100> working<00:13:23.279> with<00:13:23.579> starknet<00:13:24.180> on<00:13:24.540> the 00:13:24.650 --> 00:13:24.660 align:start position:0% you know working with starknet on the 00:13:24.660 --> 00:13:26.870 align:start position:0% you know working with starknet on the defining<00:13:25.079> account<00:13:25.320> abstraction<00:13:25.860> there<00:13:26.279> and 00:13:26.870 --> 00:13:26.880 align:start position:0% defining account abstraction there and 00:13:26.880 --> 00:13:28.790 align:start position:0% defining account abstraction there and of<00:13:27.000> course<00:13:27.120> we<00:13:27.360> built<00:13:27.720> a<00:13:27.779> wallet<00:13:28.079> because<00:13:28.260> at 00:13:28.790 --> 00:13:28.800 align:start position:0% of course we built a wallet because at 00:13:28.800 --> 00:13:30.710 align:start position:0% of course we built a wallet because at Urgent<00:13:28.920> that's<00:13:29.100> what<00:13:29.279> we<00:13:29.459> do<00:13:29.639> and<00:13:30.360> so<00:13:30.480> we 00:13:30.710 --> 00:13:30.720 align:start position:0% Urgent that's what we do and so we 00:13:30.720 --> 00:13:33.530 align:start position:0% Urgent that's what we do and so we actually<00:13:30.839> built<00:13:31.440> the<00:13:31.680> first<00:13:32.180> wallet<00:13:33.180> with 00:13:33.530 --> 00:13:33.540 align:start position:0% actually built the first wallet with 00:13:33.540 --> 00:13:35.930 align:start position:0% actually built the first wallet with Native<00:13:33.839> account<00:13:34.019> abstraction<00:13:34.560> collagen<00:13:35.220> X<00:13:35.459> I 00:13:35.930 --> 00:13:35.940 align:start position:0% Native account abstraction collagen X I 00:13:35.940 --> 00:13:37.370 align:start position:0% Native account abstraction collagen X I promise<00:13:36.240> you<00:13:36.360> this<00:13:36.540> is<00:13:36.660> the<00:13:36.779> only<00:13:36.899> slide<00:13:37.200> where 00:13:37.370 --> 00:13:37.380 align:start position:0% promise you this is the only slide where 00:13:37.380 --> 00:13:39.410 align:start position:0% promise you this is the only slide where I<00:13:37.500> will<00:13:37.620> chill<00:13:37.800> Argent<00:13:38.220> but<00:13:39.060> it's<00:13:39.300> still 00:13:39.410 --> 00:13:39.420 align:start position:0% I will chill Argent but it's still 00:13:39.420 --> 00:13:41.810 align:start position:0% I will chill Argent but it's still needed<00:13:39.660> since<00:13:39.779> I'm<00:13:40.019> on<00:13:40.139> Main<00:13:40.320> stage<00:13:40.620> so<00:13:41.459> our 00:13:41.810 --> 00:13:41.820 align:start position:0% needed since I'm on Main stage so our 00:13:41.820 --> 00:13:44.210 align:start position:0% needed since I'm on Main stage so our Gen<00:13:42.000> X<00:13:42.180> first<00:13:42.360> wallet<00:13:42.720> on<00:13:42.899> stagnet<00:13:43.380> Native 00:13:44.210 --> 00:13:44.220 align:start position:0% Gen X first wallet on stagnet Native 00:13:44.220 --> 00:13:45.829 align:start position:0% Gen X first wallet on stagnet Native account<00:13:44.399> abstraction<00:13:44.940> which<00:13:45.360> is<00:13:45.420> quite<00:13:45.660> of 00:13:45.829 --> 00:13:45.839 align:start position:0% account abstraction which is quite of 00:13:45.839 --> 00:13:48.290 align:start position:0% account abstraction which is quite of amazing<00:13:46.200> works<00:13:47.100> as<00:13:47.220> a<00:13:47.399> browser<00:13:47.700> extension<00:13:48.120> so 00:13:48.290 --> 00:13:48.300 align:start position:0% amazing works as a browser extension so 00:13:48.300 --> 00:13:50.750 align:start position:0% amazing works as a browser extension so it<00:13:48.480> works<00:13:48.779> on<00:13:48.899> on<00:13:49.079> Chrome<00:13:49.260> and<00:13:49.500> Firefox<00:13:49.980> you 00:13:50.750 --> 00:13:50.760 align:start position:0% it works on on Chrome and Firefox you 00:13:50.760 --> 00:13:52.550 align:start position:0% it works on on Chrome and Firefox you can<00:13:50.880> have<00:13:51.000> multiple<00:13:51.420> accounts<00:13:51.959> it<00:13:52.200> works<00:13:52.440> on 00:13:52.550 --> 00:13:52.560 align:start position:0% can have multiple accounts it works on 00:13:52.560 --> 00:13:55.190 align:start position:0% can have multiple accounts it works on stagnet<00:13:53.100> testnet<00:13:53.459> and<00:13:53.579> stagnet<00:13:54.060> mainnet<00:13:54.540> and 00:13:55.190 --> 00:13:55.200 align:start position:0% stagnet testnet and stagnet mainnet and 00:13:55.200 --> 00:13:57.710 align:start position:0% stagnet testnet and stagnet mainnet and it<00:13:55.380> does<00:13:55.560> the<00:13:56.040> usual<00:13:56.279> over<00:13:56.459> one<00:13:56.700> of<00:13:56.880> a<00:13:57.480> wallet 00:13:57.710 --> 00:13:57.720 align:start position:0% it does the usual over one of a wallet 00:13:57.720 --> 00:13:59.449 align:start position:0% it does the usual over one of a wallet you<00:13:57.899> can<00:13:58.019> send<00:13:58.139> and<00:13:58.380> receive<00:13:58.680> token<00:13:59.100> you<00:13:59.339> can 00:13:59.449 --> 00:13:59.459 align:start position:0% you can send and receive token you can 00:13:59.459 --> 00:14:01.370 align:start position:0% you can send and receive token you can interact<00:13:59.760> with<00:13:59.940> dapps<00:14:00.360> but<00:14:00.720> as<00:14:00.899> I<00:14:01.019> will<00:14:01.200> show 00:14:01.370 --> 00:14:01.380 align:start position:0% interact with dapps but as I will show 00:14:01.380 --> 00:14:03.710 align:start position:0% interact with dapps but as I will show it<00:14:01.920> does<00:14:02.040> much<00:14:02.279> more<00:14:02.459> than<00:14:02.639> that<00:14:02.880> also<00:14:03.240> and 00:14:03.710 --> 00:14:03.720 align:start position:0% it does much more than that also and 00:14:03.720 --> 00:14:05.750 align:start position:0% it does much more than that also and it's<00:14:03.839> 100<00:14:03.959> open<00:14:04.500> source<00:14:04.920> so<00:14:05.339> if<00:14:05.459> you<00:14:05.639> are 00:14:05.750 --> 00:14:05.760 align:start position:0% it's 100 open source so if you are 00:14:05.760 --> 00:14:07.910 align:start position:0% it's 100 open source so if you are interested<00:14:06.060> please<00:14:06.420> check<00:14:06.660> the<00:14:06.839> repo<00:14:07.260> feel 00:14:07.910 --> 00:14:07.920 align:start position:0% interested please check the repo feel 00:14:07.920 --> 00:14:09.650 align:start position:0% interested please check the repo feel free<00:14:08.100> to<00:14:08.279> contribute 00:14:09.650 --> 00:14:09.660 align:start position:0% free to contribute 00:14:09.660 --> 00:14:12.050 align:start position:0% free to contribute and<00:14:10.200> if<00:14:10.320> you<00:14:10.440> haven't<00:14:10.560> tried<00:14:10.860> the<00:14:11.459> wallet<00:14:11.820> do 00:14:12.050 --> 00:14:12.060 align:start position:0% and if you haven't tried the wallet do 00:14:12.060 --> 00:14:14.090 align:start position:0% and if you haven't tried the wallet do so<00:14:12.240> as<00:14:12.480> well<00:14:12.600> and<00:14:13.440> it's<00:14:13.560> been<00:14:13.740> actually<00:14:13.920> an 00:14:14.090 --> 00:14:14.100 align:start position:0% so as well and it's been actually an 00:14:14.100 --> 00:14:17.210 align:start position:0% so as well and it's been actually an amazing<00:14:14.399> ride<00:14:14.519> you<00:14:15.120> may<00:14:15.240> not<00:14:15.420> know<00:14:15.839> uh<00:14:16.680> the 00:14:17.210 --> 00:14:17.220 align:start position:0% amazing ride you may not know uh the 00:14:17.220 --> 00:14:18.829 align:start position:0% amazing ride you may not know uh the stagnant<00:14:17.579> ecosystem<00:14:17.940> is<00:14:18.240> going<00:14:18.420> but<00:14:18.660> actually 00:14:18.829 --> 00:14:18.839 align:start position:0% stagnant ecosystem is going but actually 00:14:18.839 --> 00:14:21.050 align:start position:0% stagnant ecosystem is going but actually since<00:14:19.200> we<00:14:19.380> started<00:14:19.680> our<00:14:19.860> Gen<00:14:20.040> X<00:14:20.220> in<00:14:20.760> January 00:14:21.050 --> 00:14:21.060 align:start position:0% since we started our Gen X in January 00:14:21.060 --> 00:14:23.269 align:start position:0% since we started our Gen X in January we've<00:14:21.420> had<00:14:21.540> more<00:14:21.779> than<00:14:21.899> 250k<00:14:22.620> downloads<00:14:23.160> so 00:14:23.269 --> 00:14:23.279 align:start position:0% we've had more than 250k downloads so 00:14:23.279 --> 00:14:24.530 align:start position:0% we've had more than 250k downloads so that's<00:14:23.399> I<00:14:23.519> think<00:14:23.639> that's<00:14:23.760> kind<00:14:23.940> of<00:14:24.060> impressive 00:14:24.530 --> 00:14:24.540 align:start position:0% that's I think that's kind of impressive 00:14:24.540 --> 00:14:27.170 align:start position:0% that's I think that's kind of impressive and<00:14:25.139> we<00:14:25.320> are<00:14:25.440> securing<00:14:25.920> more<00:14:26.160> than<00:14:26.339> 90<00:14:26.519> of<00:14:27.060> the 00:14:27.170 --> 00:14:27.180 align:start position:0% and we are securing more than 90 of the 00:14:27.180 --> 00:14:29.990 align:start position:0% and we are securing more than 90 of the funds<00:14:27.540> on<00:14:28.139> starknet<00:14:28.680> mainnet<00:14:29.100> today 00:14:29.990 --> 00:14:30.000 align:start position:0% funds on starknet mainnet today 00:14:30.000 --> 00:14:32.750 align:start position:0% funds on starknet mainnet today so<00:14:30.360> all<00:14:30.480> this<00:14:30.660> RJ<00:14:30.959> next<00:14:31.139> work<00:14:31.440> so<00:14:32.160> typically 00:14:32.750 --> 00:14:32.760 align:start position:0% so all this RJ next work so typically 00:14:32.760 --> 00:14:34.430 align:start position:0% so all this RJ next work so typically when<00:14:33.060> you<00:14:33.180> think<00:14:33.360> of<00:14:33.480> a<00:14:33.660> wallet<00:14:33.959> for<00:14:34.200> example 00:14:34.430 --> 00:14:34.440 align:start position:0% when you think of a wallet for example 00:14:34.440 --> 00:14:36.350 align:start position:0% when you think of a wallet for example like<00:14:34.620> metamask<00:14:35.160> you<00:14:35.399> think<00:14:35.579> about<00:14:35.700> the<00:14:36.000> client 00:14:36.350 --> 00:14:36.360 align:start position:0% like metamask you think about the client 00:14:36.360 --> 00:14:38.090 align:start position:0% like metamask you think about the client and<00:14:36.899> you<00:14:37.019> think<00:14:37.200> about<00:14:37.320> the<00:14:37.560> key<00:14:37.740> that<00:14:37.980> can 00:14:38.090 --> 00:14:38.100 align:start position:0% and you think about the key that can 00:14:38.100 --> 00:14:39.530 align:start position:0% and you think about the key that can sign<00:14:38.279> transactions<00:14:38.940> well<00:14:39.120> with<00:14:39.360> account 00:14:39.530 --> 00:14:39.540 align:start position:0% sign transactions well with account 00:14:39.540 --> 00:14:41.269 align:start position:0% sign transactions well with account abstraction<00:14:40.019> you<00:14:40.260> need<00:14:40.440> to<00:14:40.560> think<00:14:40.740> about<00:14:40.980> the 00:14:41.269 --> 00:14:41.279 align:start position:0% abstraction you need to think about the 00:14:41.279 --> 00:14:43.610 align:start position:0% abstraction you need to think about the account<00:14:41.399> contract<00:14:42.000> as<00:14:42.180> well<00:14:42.360> so<00:14:42.779> rgnx<00:14:43.380> is 00:14:43.610 --> 00:14:43.620 align:start position:0% account contract as well so rgnx is 00:14:43.620 --> 00:14:45.350 align:start position:0% account contract as well so rgnx is really<00:14:43.740> these<00:14:43.980> three<00:14:44.160> things<00:14:44.399> a<00:14:45.120> client 00:14:45.350 --> 00:14:45.360 align:start position:0% really these three things a client 00:14:45.360 --> 00:14:47.930 align:start position:0% really these three things a client front-end<00:14:45.980> keys<00:14:46.980> that<00:14:47.100> can<00:14:47.220> sign<00:14:47.459> transaction 00:14:47.930 --> 00:14:47.940 align:start position:0% front-end keys that can sign transaction 00:14:47.940 --> 00:14:50.269 align:start position:0% front-end keys that can sign transaction and<00:14:48.420> then<00:14:48.540> account<00:14:48.720> contracts<00:14:49.440> that<00:14:49.740> live<00:14:50.100> on 00:14:50.269 --> 00:14:50.279 align:start position:0% and then account contracts that live on 00:14:50.279 --> 00:14:51.350 align:start position:0% and then account contracts that live on chain 00:14:51.350 --> 00:14:51.360 align:start position:0% chain 00:14:51.360 --> 00:14:54.470 align:start position:0% chain and<00:14:52.079> it<00:14:52.260> works<00:14:52.620> from<00:14:53.279> a<00:14:53.519> user<00:14:53.880> or<00:14:54.120> tab 00:14:54.470 --> 00:14:54.480 align:start position:0% and it works from a user or tab 00:14:54.480 --> 00:14:55.850 align:start position:0% and it works from a user or tab developer's<00:14:55.079> point<00:14:55.139> of<00:14:55.260> view<00:14:55.380> it<00:14:55.560> works 00:14:55.850 --> 00:14:55.860 align:start position:0% developer's point of view it works 00:14:55.860 --> 00:14:57.889 align:start position:0% developer's point of view it works exactly<00:14:56.279> like<00:14:56.639> like<00:14:57.000> you<00:14:57.240> would<00:14:57.360> expect<00:14:57.540> from 00:14:57.889 --> 00:14:57.899 align:start position:0% exactly like like you would expect from 00:14:57.899 --> 00:14:59.990 align:start position:0% exactly like like you would expect from your<00:14:58.079> metamask<00:14:58.680> for<00:14:58.920> example<00:14:59.160> when<00:14:59.880> you 00:14:59.990 --> 00:15:00.000 align:start position:0% your metamask for example when you 00:15:00.000 --> 00:15:01.790 align:start position:0% your metamask for example when you connect<00:15:00.120> your<00:15:00.480> wallet<00:15:00.839> and<00:15:01.139> you<00:15:01.320> do<00:15:01.440> an<00:15:01.620> action 00:15:01.790 --> 00:15:01.800 align:start position:0% connect your wallet and you do an action 00:15:01.800 --> 00:15:03.949 align:start position:0% connect your wallet and you do an action the<00:15:02.100> wallet<00:15:02.399> will<00:15:02.579> pop<00:15:02.760> up<00:15:02.880> you<00:15:03.660> can<00:15:03.720> review 00:15:03.949 --> 00:15:03.959 align:start position:0% the wallet will pop up you can review 00:15:03.959 --> 00:15:06.949 align:start position:0% the wallet will pop up you can review the<00:15:04.380> action<00:15:04.760> approve<00:15:05.760> the<00:15:06.240> extension<00:15:06.720> will 00:15:06.949 --> 00:15:06.959 align:start position:0% the action approve the extension will 00:15:06.959 --> 00:15:09.889 align:start position:0% the action approve the extension will use<00:15:07.199> a<00:15:07.440> key<00:15:07.560> to<00:15:08.279> sign<00:15:08.459> the<00:15:08.699> authorization<00:15:09.180> all 00:15:09.889 --> 00:15:09.899 align:start position:0% use a key to sign the authorization all 00:15:09.899 --> 00:15:11.569 align:start position:0% use a key to sign the authorization all this<00:15:10.139> is<00:15:10.320> sent<00:15:10.500> to<00:15:10.680> the<00:15:10.800> account<00:15:10.920> contract<00:15:11.399> on 00:15:11.569 --> 00:15:11.579 align:start position:0% this is sent to the account contract on 00:15:11.579 --> 00:15:13.490 align:start position:0% this is sent to the account contract on chain<00:15:11.820> which<00:15:12.180> will<00:15:12.360> validate<00:15:12.839> and<00:15:13.380> then 00:15:13.490 --> 00:15:13.500 align:start position:0% chain which will validate and then 00:15:13.500 --> 00:15:15.350 align:start position:0% chain which will validate and then execute<00:15:13.920> the<00:15:14.100> operation<00:15:14.519> and<00:15:15.000> call<00:15:15.180> the 00:15:15.350 --> 00:15:15.360 align:start position:0% execute the operation and call the 00:15:15.360 --> 00:15:18.490 align:start position:0% execute the operation and call the Target<00:15:15.540> contract<00:15:16.139> okay<00:15:16.920> so<00:15:17.279> now<00:15:17.399> let's 00:15:18.490 --> 00:15:18.500 align:start position:0% Target contract okay so now let's 00:15:18.500 --> 00:15:21.290 align:start position:0% Target contract okay so now let's get<00:15:19.500> to<00:15:19.680> the<00:15:19.800> interesting<00:15:20.220> part<00:15:20.459> the<00:15:21.000> unique 00:15:21.290 --> 00:15:21.300 align:start position:0% get to the interesting part the unique 00:15:21.300 --> 00:15:22.910 align:start position:0% get to the interesting part the unique features<00:15:21.720> that<00:15:21.959> I<00:15:22.139> enabled<00:15:22.560> by<00:15:22.740> account 00:15:22.910 --> 00:15:22.920 align:start position:0% features that I enabled by account 00:15:22.920 --> 00:15:25.069 align:start position:0% features that I enabled by account abstraction<00:15:23.399> so<00:15:24.240> I<00:15:24.420> mentioned<00:15:24.720> that<00:15:24.839> on 00:15:25.069 --> 00:15:25.079 align:start position:0% abstraction so I mentioned that on 00:15:25.079 --> 00:15:27.110 align:start position:0% abstraction so I mentioned that on stacknet<00:15:25.500> we<00:15:25.620> have<00:15:25.740> native<00:15:25.920> multi-call<00:15:26.519> the 00:15:27.110 --> 00:15:27.120 align:start position:0% stacknet we have native multi-call the 00:15:27.120 --> 00:15:28.550 align:start position:0% stacknet we have native multi-call the idea<00:15:27.300> of<00:15:27.420> a<00:15:27.540> multicool<00:15:27.959> is<00:15:28.139> that<00:15:28.260> you<00:15:28.380> can 00:15:28.550 --> 00:15:28.560 align:start position:0% idea of a multicool is that you can 00:15:28.560 --> 00:15:29.569 align:start position:0% idea of a multicool is that you can actually 00:15:29.569 --> 00:15:29.579 align:start position:0% actually 00:15:29.579 --> 00:15:32.569 align:start position:0% actually make<00:15:30.360> a<00:15:30.540> sequence<00:15:30.959> of<00:15:31.139> operation<00:15:31.620> at<00:15:32.040> as<00:15:32.279> one 00:15:32.569 --> 00:15:32.579 align:start position:0% make a sequence of operation at as one 00:15:32.579 --> 00:15:34.129 align:start position:0% make a sequence of operation at as one Atomic<00:15:33.000> transaction 00:15:34.129 --> 00:15:34.139 align:start position:0% Atomic transaction 00:15:34.139 --> 00:15:37.189 align:start position:0% Atomic transaction think<00:15:34.620> for<00:15:34.860> example<00:15:35.160> of<00:15:35.399> the<00:15:35.519> infamous<00:15:36.199> erc20 00:15:37.189 --> 00:15:37.199 align:start position:0% think for example of the infamous erc20 00:15:37.199 --> 00:15:40.189 align:start position:0% think for example of the infamous erc20 approved<00:15:37.920> end<00:15:38.459> call<00:15:38.699> right<00:15:39.240> on<00:15:39.480> ethereum<00:15:39.959> if 00:15:40.189 --> 00:15:40.199 align:start position:0% approved end call right on ethereum if 00:15:40.199 --> 00:15:41.509 align:start position:0% approved end call right on ethereum if you<00:15:40.320> want<00:15:40.380> to<00:15:40.500> interact<00:15:40.800> with<00:15:40.920> adapt<00:15:41.339> that 00:15:41.509 --> 00:15:41.519 align:start position:0% you want to interact with adapt that 00:15:41.519 --> 00:15:43.670 align:start position:0% you want to interact with adapt that requires<00:15:41.940> a<00:15:42.180> token<00:15:42.600> you<00:15:43.079> need<00:15:43.199> to<00:15:43.320> First<00:15:43.440> make 00:15:43.670 --> 00:15:43.680 align:start position:0% requires a token you need to First make 00:15:43.680 --> 00:15:45.410 align:start position:0% requires a token you need to First make a<00:15:43.860> first<00:15:44.040> transaction<00:15:44.459> to<00:15:44.880> approve<00:15:45.240> your 00:15:45.410 --> 00:15:45.420 align:start position:0% a first transaction to approve your 00:15:45.420 --> 00:15:47.810 align:start position:0% a first transaction to approve your token<00:15:45.839> wait<00:15:46.680> for<00:15:46.920> that<00:15:47.040> transaction<00:15:47.399> to<00:15:47.699> be 00:15:47.810 --> 00:15:47.820 align:start position:0% token wait for that transaction to be 00:15:47.820 --> 00:15:49.250 align:start position:0% token wait for that transaction to be mine<00:15:48.000> then<00:15:48.300> you<00:15:48.480> can<00:15:48.600> actually<00:15:48.720> make<00:15:49.079> your 00:15:49.250 --> 00:15:49.260 align:start position:0% mine then you can actually make your 00:15:49.260 --> 00:15:51.350 align:start position:0% mine then you can actually make your call<00:15:49.440> well<00:15:50.100> with<00:15:50.339> multicall<00:15:50.940> because<00:15:51.180> your 00:15:51.350 --> 00:15:51.360 align:start position:0% call well with multicall because your 00:15:51.360 --> 00:15:52.970 align:start position:0% call well with multicall because your account<00:15:51.600> is<00:15:51.899> a<00:15:52.019> smart<00:15:52.079> contract<00:15:52.440> you<00:15:52.800> can 00:15:52.970 --> 00:15:52.980 align:start position:0% account is a smart contract you can 00:15:52.980 --> 00:15:54.410 align:start position:0% account is a smart contract you can orchestrate<00:15:53.639> these<00:15:53.880> different<00:15:54.000> operations 00:15:54.410 --> 00:15:54.420 align:start position:0% orchestrate these different operations 00:15:54.420 --> 00:15:56.750 align:start position:0% orchestrate these different operations in<00:15:54.660> sequence<00:15:55.079> so<00:15:55.560> you<00:15:55.740> can<00:15:55.920> actually<00:15:56.040> in<00:15:56.519> one 00:15:56.750 --> 00:15:56.760 align:start position:0% in sequence so you can actually in one 00:15:56.760 --> 00:15:59.389 align:start position:0% in sequence so you can actually in one transaction<00:15:57.240> do<00:15:57.779> your<00:15:57.959> approve<00:15:58.500> annual<00:15:59.160> call 00:15:59.389 --> 00:15:59.399 align:start position:0% transaction do your approve annual call 00:15:59.399 --> 00:16:01.790 align:start position:0% transaction do your approve annual call or<00:16:00.120> maybe<00:16:00.240> you<00:16:00.480> can<00:16:00.600> do<00:16:00.720> your<00:16:00.899> approve<00:16:01.380> and 00:16:01.790 --> 00:16:01.800 align:start position:0% or maybe you can do your approve and 00:16:01.800 --> 00:16:03.949 align:start position:0% or maybe you can do your approve and then<00:16:01.920> five<00:16:02.220> calls<00:16:02.699> and<00:16:03.300> we're<00:16:03.420> seeing<00:16:03.720> on 00:16:03.949 --> 00:16:03.959 align:start position:0% then five calls and we're seeing on 00:16:03.959 --> 00:16:05.090 align:start position:0% then five calls and we're seeing on stagnet 00:16:05.090 --> 00:16:05.100 align:start position:0% stagnet 00:16:05.100 --> 00:16:07.189 align:start position:0% stagnet the<00:16:05.639> developers<00:16:06.240> are<00:16:06.480> experimenting<00:16:07.079> with 00:16:07.189 --> 00:16:07.199 align:start position:0% the developers are experimenting with 00:16:07.199 --> 00:16:08.990 align:start position:0% the developers are experimenting with that<00:16:07.380> for<00:16:07.680> example<00:16:07.920> if<00:16:08.160> you<00:16:08.339> if<00:16:08.519> you<00:16:08.699> go<00:16:08.820> on 00:16:08.990 --> 00:16:09.000 align:start position:0% that for example if you if you go on 00:16:09.000 --> 00:16:10.850 align:start position:0% that for example if you if you go on aspect<00:16:09.360> which<00:16:09.660> is<00:16:09.720> an<00:16:09.899> nft<00:16:10.139> Marketplace<00:16:10.620> on 00:16:10.850 --> 00:16:10.860 align:start position:0% aspect which is an nft Marketplace on 00:16:10.860 --> 00:16:13.430 align:start position:0% aspect which is an nft Marketplace on Stark<00:16:11.100> net<00:16:11.339> when<00:16:12.060> you<00:16:12.240> want<00:16:12.420> to<00:16:12.540> buy<00:16:12.660> nfts<00:16:13.260> you 00:16:13.430 --> 00:16:13.440 align:start position:0% Stark net when you want to buy nfts you 00:16:13.440 --> 00:16:15.410 align:start position:0% Stark net when you want to buy nfts you can<00:16:13.560> add<00:16:13.800> them<00:16:13.980> to<00:16:14.220> your<00:16:14.399> shopping<00:16:14.579> cart<00:16:14.940> which 00:16:15.410 --> 00:16:15.420 align:start position:0% can add them to your shopping cart which 00:16:15.420 --> 00:16:17.210 align:start position:0% can add them to your shopping cart which is<00:16:15.540> an<00:16:15.720> experience<00:16:15.959> that<00:16:16.199> we<00:16:16.320> all<00:16:16.440> know<00:16:16.620> and<00:16:17.100> so 00:16:17.210 --> 00:16:17.220 align:start position:0% is an experience that we all know and so 00:16:17.220 --> 00:16:18.889 align:start position:0% is an experience that we all know and so you<00:16:17.399> see<00:16:17.519> all<00:16:17.699> the<00:16:17.820> nfts<00:16:18.360> that<00:16:18.480> you<00:16:18.660> want<00:16:18.779> to 00:16:18.889 --> 00:16:18.899 align:start position:0% you see all the nfts that you want to 00:16:18.899 --> 00:16:21.350 align:start position:0% you see all the nfts that you want to buy<00:16:19.079> you<00:16:19.440> finish<00:16:19.620> your<00:16:19.920> session<00:16:20.160> then<00:16:21.000> you<00:16:21.180> go 00:16:21.350 --> 00:16:21.360 align:start position:0% buy you finish your session then you go 00:16:21.360 --> 00:16:23.389 align:start position:0% buy you finish your session then you go and<00:16:21.540> you<00:16:21.720> actually<00:16:21.899> buy<00:16:22.260> this<00:16:22.500> nft<00:16:22.800> in<00:16:23.279> one 00:16:23.389 --> 00:16:23.399 align:start position:0% and you actually buy this nft in one 00:16:23.399 --> 00:16:25.310 align:start position:0% and you actually buy this nft in one transaction<00:16:23.820> because<00:16:24.180> your<00:16:24.540> account<00:16:24.720> will 00:16:25.310 --> 00:16:25.320 align:start position:0% transaction because your account will 00:16:25.320 --> 00:16:26.870 align:start position:0% transaction because your account will orchestrate<00:16:25.980> the<00:16:26.100> buying<00:16:26.339> all<00:16:26.459> of<00:16:26.639> these 00:16:26.870 --> 00:16:26.880 align:start position:0% orchestrate the buying all of these 00:16:26.880 --> 00:16:29.329 align:start position:0% orchestrate the buying all of these these<00:16:27.180> nfts<00:16:27.600> so<00:16:27.720> in<00:16:27.779> terms<00:16:27.899> of<00:16:28.019> ux<00:16:28.440> it's<00:16:29.220> an 00:16:29.329 --> 00:16:29.339 align:start position:0% these nfts so in terms of ux it's an 00:16:29.339 --> 00:16:30.769 align:start position:0% these nfts so in terms of ux it's an amazing<00:16:29.639> Improvement 00:16:30.769 --> 00:16:30.779 align:start position:0% amazing Improvement 00:16:30.779 --> 00:16:33.110 align:start position:0% amazing Improvement another<00:16:31.320> thing<00:16:31.680> that<00:16:32.100> we<00:16:32.459> are<00:16:32.639> doing<00:16:32.880> on 00:16:33.110 --> 00:16:33.120 align:start position:0% another thing that we are doing on 00:16:33.120 --> 00:16:35.389 align:start position:0% another thing that we are doing on stagnet<00:16:33.600> that<00:16:33.720> you<00:16:34.019> can<00:16:34.199> do<00:16:34.380> because<00:16:35.100> of 00:16:35.389 --> 00:16:35.399 align:start position:0% stagnet that you can do because of 00:16:35.399 --> 00:16:37.129 align:start position:0% stagnet that you can do because of account<00:16:35.519> abstraction<00:16:36.000> is<00:16:36.300> social<00:16:36.480> recovery 00:16:37.129 --> 00:16:37.139 align:start position:0% account abstraction is social recovery 00:16:37.139 --> 00:16:39.650 align:start position:0% account abstraction is social recovery the<00:16:37.740> idea<00:16:37.980> of<00:16:38.100> social<00:16:38.279> recovery<00:16:38.880> in<00:16:39.540> a 00:16:39.650 --> 00:16:39.660 align:start position:0% the idea of social recovery in a 00:16:39.660 --> 00:16:41.509 align:start position:0% the idea of social recovery in a nutshell<00:16:39.959> is<00:16:40.139> to<00:16:40.259> get<00:16:40.440> rid<00:16:40.620> of<00:16:40.800> seed<00:16:41.100> phrases 00:16:41.509 --> 00:16:41.519 align:start position:0% nutshell is to get rid of seed phrases 00:16:41.519 --> 00:16:43.490 align:start position:0% nutshell is to get rid of seed phrases oh<00:16:42.120> do<00:16:42.360> you<00:16:42.480> do<00:16:42.600> that<00:16:42.720> because<00:16:43.019> your<00:16:43.320> account 00:16:43.490 --> 00:16:43.500 align:start position:0% oh do you do that because your account 00:16:43.500 --> 00:16:46.009 align:start position:0% oh do you do that because your account is<00:16:43.800> a<00:16:43.920> smart<00:16:44.040> contract<00:16:44.459> you<00:16:45.240> can<00:16:45.360> program<00:16:45.660> it 00:16:46.009 --> 00:16:46.019 align:start position:0% is a smart contract you can program it 00:16:46.019 --> 00:16:48.650 align:start position:0% is a smart contract you can program it to<00:16:46.740> support<00:16:47.040> a<00:16:47.639> second<00:16:47.820> key 00:16:48.650 --> 00:16:48.660 align:start position:0% to support a second key 00:16:48.660 --> 00:16:51.530 align:start position:0% to support a second key and<00:16:49.199> you<00:16:49.380> can<00:16:49.500> Define<00:16:49.740> that<00:16:50.160> that<00:16:50.399> key<00:16:50.699> cannot 00:16:51.530 --> 00:16:51.540 align:start position:0% and you can Define that that key cannot 00:16:51.540 --> 00:16:53.269 align:start position:0% and you can Define that that key cannot transfer<00:16:51.899> token<00:16:52.320> it<00:16:52.560> cannot<00:16:52.860> interact<00:16:53.160> with 00:16:53.269 --> 00:16:53.279 align:start position:0% transfer token it cannot interact with 00:16:53.279 --> 00:16:55.009 align:start position:0% transfer token it cannot interact with depth<00:16:53.579> you<00:16:53.699> can<00:16:53.880> actually<00:16:53.940> only<00:16:54.180> do<00:16:54.480> one<00:16:54.779> thing 00:16:55.009 --> 00:16:55.019 align:start position:0% depth you can actually only do one thing 00:16:55.019 --> 00:16:57.769 align:start position:0% depth you can actually only do one thing which<00:16:55.680> is<00:16:55.860> to<00:16:56.160> replace<00:16:56.339> the<00:16:56.940> signer<00:16:57.360> key<00:16:57.540> in 00:16:57.769 --> 00:16:57.779 align:start position:0% which is to replace the signer key in 00:16:57.779 --> 00:16:59.449 align:start position:0% which is to replace the signer key in case<00:16:57.899> of<00:16:58.079> a<00:16:58.199> problem<00:16:58.380> and<00:16:59.040> you<00:16:59.220> can<00:16:59.279> imagine 00:16:59.449 --> 00:16:59.459 align:start position:0% case of a problem and you can imagine 00:16:59.459 --> 00:17:02.329 align:start position:0% case of a problem and you can imagine that<00:16:59.820> no<00:17:00.000> you<00:17:00.240> give<00:17:00.420> that<00:17:00.779> recovery<00:17:01.680> key<00:17:01.860> to<00:17:02.160> a 00:17:02.329 --> 00:17:02.339 align:start position:0% that no you give that recovery key to a 00:17:02.339 --> 00:17:04.010 align:start position:0% that no you give that recovery key to a party<00:17:02.519> that<00:17:02.880> you<00:17:03.000> trust<00:17:03.240> that<00:17:03.540> we<00:17:03.660> call<00:17:03.779> a 00:17:04.010 --> 00:17:04.020 align:start position:0% party that you trust that we call a 00:17:04.020 --> 00:17:06.049 align:start position:0% party that you trust that we call a guardian<00:17:04.319> think<00:17:04.919> of<00:17:05.160> it<00:17:05.280> for<00:17:05.459> example<00:17:05.699> as<00:17:05.880> a 00:17:06.049 --> 00:17:06.059 align:start position:0% guardian think of it for example as a 00:17:06.059 --> 00:17:07.130 align:start position:0% guardian think of it for example as a service 00:17:07.130 --> 00:17:07.140 align:start position:0% service 00:17:07.140 --> 00:17:09.829 align:start position:0% service and<00:17:07.919> the<00:17:08.339> day<00:17:08.520> you<00:17:08.640> lose<00:17:08.819> your<00:17:09.000> computer<00:17:09.240> you 00:17:09.829 --> 00:17:09.839 align:start position:0% and the day you lose your computer you 00:17:09.839 --> 00:17:12.049 align:start position:0% and the day you lose your computer you lose<00:17:09.959> access<00:17:10.260> to<00:17:10.559> your<00:17:10.740> wallet<00:17:11.040> well<00:17:11.699> instead 00:17:12.049 --> 00:17:12.059 align:start position:0% lose access to your wallet well instead 00:17:12.059 --> 00:17:14.150 align:start position:0% lose access to your wallet well instead of<00:17:12.179> having<00:17:12.480> to<00:17:12.780> think<00:17:13.020> about<00:17:13.199> a<00:17:13.500> seed<00:17:13.860> phrase 00:17:14.150 --> 00:17:14.160 align:start position:0% of having to think about a seed phrase 00:17:14.160 --> 00:17:16.069 align:start position:0% of having to think about a seed phrase private<00:17:14.579> key<00:17:14.640> no<00:17:14.880> you<00:17:15.179> just<00:17:15.360> contact<00:17:15.600> your 00:17:16.069 --> 00:17:16.079 align:start position:0% private key no you just contact your 00:17:16.079 --> 00:17:18.409 align:start position:0% private key no you just contact your guardian<00:17:16.380> this<00:17:16.679> service<00:17:16.980> you<00:17:17.760> authenticate 00:17:18.409 --> 00:17:18.419 align:start position:0% guardian this service you authenticate 00:17:18.419 --> 00:17:20.150 align:start position:0% guardian this service you authenticate with<00:17:18.780> whatever<00:17:18.959> mean<00:17:19.260> you've<00:17:19.620> agreed<00:17:19.980> with 00:17:20.150 --> 00:17:20.160 align:start position:0% with whatever mean you've agreed with 00:17:20.160 --> 00:17:22.429 align:start position:0% with whatever mean you've agreed with him<00:17:20.400> and<00:17:21.240> the<00:17:21.419> service<00:17:21.540> will<00:17:21.900> make<00:17:22.079> the<00:17:22.319> only 00:17:22.429 --> 00:17:22.439 align:start position:0% him and the service will make the only 00:17:22.439 --> 00:17:23.929 align:start position:0% him and the service will make the only transaction<00:17:22.919> it<00:17:23.160> can<00:17:23.339> do<00:17:23.459> on<00:17:23.579> your<00:17:23.760> account 00:17:23.929 --> 00:17:23.939 align:start position:0% transaction it can do on your account 00:17:23.939 --> 00:17:26.150 align:start position:0% transaction it can do on your account and<00:17:24.419> reprogram<00:17:24.959> your<00:17:25.199> account<00:17:25.439> with<00:17:25.919> a<00:17:26.040> new 00:17:26.150 --> 00:17:26.160 align:start position:0% and reprogram your account with a new 00:17:26.160 --> 00:17:27.409 align:start position:0% and reprogram your account with a new key 00:17:27.409 --> 00:17:27.419 align:start position:0% key 00:17:27.419 --> 00:17:30.169 align:start position:0% key and<00:17:28.020> of<00:17:28.199> course<00:17:28.319> you<00:17:28.919> can<00:17:28.980> use<00:17:29.160> a<00:17:29.340> service<00:17:29.580> but 00:17:30.169 --> 00:17:30.179 align:start position:0% and of course you can use a service but 00:17:30.179 --> 00:17:32.210 align:start position:0% and of course you can use a service but you<00:17:30.960> can<00:17:31.020> decide<00:17:31.320> to<00:17:31.440> be<00:17:31.559> your<00:17:31.679> own<00:17:31.740> Guardian 00:17:32.210 --> 00:17:32.220 align:start position:0% you can decide to be your own Guardian 00:17:32.220 --> 00:17:34.610 align:start position:0% you can decide to be your own Guardian you<00:17:32.700> can<00:17:32.820> use<00:17:33.000> a<00:17:33.360> ledger<00:17:33.900> to<00:17:34.140> do<00:17:34.200> so<00:17:34.380> for 00:17:34.610 --> 00:17:34.620 align:start position:0% you can use a ledger to do so for 00:17:34.620 --> 00:17:36.590 align:start position:0% you can use a ledger to do so for example<00:17:34.860> and<00:17:35.280> we<00:17:35.460> are<00:17:35.580> working<00:17:35.760> on<00:17:36.000> ledger<00:17:36.360> to 00:17:36.590 --> 00:17:36.600 align:start position:0% example and we are working on ledger to 00:17:36.600 --> 00:17:38.690 align:start position:0% example and we are working on ledger to enable<00:17:36.900> exactly<00:17:37.799> that 00:17:38.690 --> 00:17:38.700 align:start position:0% enable exactly that 00:17:38.700 --> 00:17:40.909 align:start position:0% enable exactly that so<00:17:39.120> social<00:17:39.299> recovery<00:17:39.900> is<00:17:40.020> really<00:17:40.260> a<00:17:40.500> way<00:17:40.620> to 00:17:40.909 --> 00:17:40.919 align:start position:0% so social recovery is really a way to 00:17:40.919 --> 00:17:43.850 align:start position:0% so social recovery is really a way to get<00:17:41.100> rid<00:17:41.880> of<00:17:42.059> seed<00:17:42.360> phrase<00:17:42.660> to<00:17:42.900> provide<00:17:43.260> a<00:17:43.500> ux 00:17:43.850 --> 00:17:43.860 align:start position:0% get rid of seed phrase to provide a ux 00:17:43.860 --> 00:17:45.289 align:start position:0% get rid of seed phrase to provide a ux that<00:17:44.220> users 00:17:45.289 --> 00:17:45.299 align:start position:0% that users 00:17:45.299 --> 00:17:48.289 align:start position:0% that users normal<00:17:45.960> users<00:17:46.500> can<00:17:46.919> understand<00:17:47.160> and<00:17:48.000> it's<00:17:48.120> 100 00:17:48.289 --> 00:17:48.299 align:start position:0% normal users can understand and it's 100 00:17:48.299 --> 00:17:51.049 align:start position:0% normal users can understand and it's 100 non-custodial<00:17:49.260> because<00:17:49.559> you<00:17:49.980> as<00:17:50.280> the<00:17:50.580> owner 00:17:51.049 --> 00:17:51.059 align:start position:0% non-custodial because you as the owner 00:17:51.059 --> 00:17:53.270 align:start position:0% non-custodial because you as the owner of<00:17:51.240> the<00:17:51.419> the<00:17:51.600> main<00:17:51.840> key<00:17:52.020> you<00:17:52.620> can<00:17:52.679> decide<00:17:53.039> who's 00:17:53.270 --> 00:17:53.280 align:start position:0% of the the main key you can decide who's 00:17:53.280 --> 00:17:54.710 align:start position:0% of the the main key you can decide who's your<00:17:53.580> guardian<00:17:53.880> and<00:17:54.059> you<00:17:54.179> can<00:17:54.299> change<00:17:54.480> that 00:17:54.710 --> 00:17:54.720 align:start position:0% your guardian and you can change that 00:17:54.720 --> 00:17:56.930 align:start position:0% your guardian and you can change that Guardian<00:17:55.140> at<00:17:55.380> any<00:17:55.500> point<00:17:55.679> if<00:17:55.919> you<00:17:56.039> want<00:17:56.160> to 00:17:56.930 --> 00:17:56.940 align:start position:0% Guardian at any point if you want to 00:17:56.940 --> 00:17:59.150 align:start position:0% Guardian at any point if you want to so<00:17:57.419> that's<00:17:57.539> really<00:17:57.720> cool<00:17:57.960> what<00:17:58.500> what<00:17:58.679> else<00:17:58.860> can 00:17:59.150 --> 00:17:59.160 align:start position:0% so that's really cool what what else can 00:17:59.160 --> 00:18:01.909 align:start position:0% so that's really cool what what else can we<00:17:59.280> do<00:17:59.880> well<00:18:00.419> we<00:18:00.660> can<00:18:00.780> do<00:18:00.960> front<00:18:01.320> monitoring 00:18:01.909 --> 00:18:01.919 align:start position:0% we do well we can do front monitoring 00:18:01.919 --> 00:18:04.730 align:start position:0% we do well we can do front monitoring with<00:18:02.160> 2fa<00:18:02.760> imagine<00:18:03.600> that<00:18:04.020> again<00:18:04.200> on<00:18:04.500> your 00:18:04.730 --> 00:18:04.740 align:start position:0% with 2fa imagine that again on your 00:18:04.740 --> 00:18:06.770 align:start position:0% with 2fa imagine that again on your account<00:18:04.860> your<00:18:05.220> program<00:18:05.400> is<00:18:05.700> second<00:18:05.880> key<00:18:06.179> and 00:18:06.770 --> 00:18:06.780 align:start position:0% account your program is second key and 00:18:06.780 --> 00:18:08.390 align:start position:0% account your program is second key and you<00:18:06.960> decide<00:18:07.200> that<00:18:07.380> that<00:18:07.620> second<00:18:07.799> key<00:18:08.100> must 00:18:08.390 --> 00:18:08.400 align:start position:0% you decide that that second key must 00:18:08.400 --> 00:18:10.970 align:start position:0% you decide that that second key must cost<00:18:08.820> Okay<00:18:09.419> so 00:18:10.970 --> 00:18:10.980 align:start position:0% cost Okay so 00:18:10.980 --> 00:18:13.310 align:start position:0% cost Okay so I<00:18:11.580> was<00:18:11.640> talking<00:18:11.820> about<00:18:12.059> the<00:18:12.419> new<00:18:12.600> cool<00:18:12.840> feature 00:18:13.310 --> 00:18:13.320 align:start position:0% I was talking about the new cool feature 00:18:13.320 --> 00:18:16.130 align:start position:0% I was talking about the new cool feature the<00:18:13.559> idea<00:18:13.799> to<00:18:13.980> do<00:18:14.100> fraud<00:18:14.460> monitoring<00:18:14.940> with<00:18:15.299> 2fa 00:18:16.130 --> 00:18:16.140 align:start position:0% the idea to do fraud monitoring with 2fa 00:18:16.140 --> 00:18:17.810 align:start position:0% the idea to do fraud monitoring with 2fa I<00:18:16.559> think<00:18:16.620> I<00:18:16.740> was<00:18:16.860> explaining<00:18:17.280> that<00:18:17.460> you<00:18:17.640> can 00:18:17.810 --> 00:18:17.820 align:start position:0% I think I was explaining that you can 00:18:17.820 --> 00:18:20.210 align:start position:0% I think I was explaining that you can add<00:18:18.000> a<00:18:18.179> key<00:18:18.299> to<00:18:18.539> your<00:18:18.780> account<00:18:18.960> and<00:18:19.860> that<00:18:20.039> key 00:18:20.210 --> 00:18:20.220 align:start position:0% add a key to your account and that key 00:18:20.220 --> 00:18:21.950 align:start position:0% add a key to your account and that key must<00:18:20.460> cosine<00:18:20.880> every<00:18:21.059> transaction<00:18:21.480> so<00:18:21.780> you 00:18:21.950 --> 00:18:21.960 align:start position:0% must cosine every transaction so you 00:18:21.960 --> 00:18:23.330 align:start position:0% must cosine every transaction so you turn<00:18:22.080> your<00:18:22.260> account<00:18:22.440> into<00:18:22.740> a<00:18:22.919> two<00:18:23.039> of<00:18:23.160> two 00:18:23.330 --> 00:18:23.340 align:start position:0% turn your account into a two of two 00:18:23.340 --> 00:18:25.490 align:start position:0% turn your account into a two of two multisig<00:18:23.880> and<00:18:24.480> you<00:18:24.600> can<00:18:24.720> just<00:18:24.900> you<00:18:25.140> can<00:18:25.320> choose 00:18:25.490 --> 00:18:25.500 align:start position:0% multisig and you can just you can choose 00:18:25.500 --> 00:18:27.710 align:start position:0% multisig and you can just you can choose to<00:18:25.620> give<00:18:25.799> that<00:18:26.039> key<00:18:26.160> to<00:18:26.400> a<00:18:26.580> service<00:18:26.760> now 00:18:27.710 --> 00:18:27.720 align:start position:0% to give that key to a service now 00:18:27.720 --> 00:18:29.270 align:start position:0% to give that key to a service now imagine<00:18:27.900> that<00:18:28.320> every<00:18:28.559> time<00:18:28.799> you<00:18:28.980> make<00:18:29.100> a 00:18:29.270 --> 00:18:29.280 align:start position:0% imagine that every time you make a 00:18:29.280 --> 00:18:31.789 align:start position:0% imagine that every time you make a transaction<00:18:29.700> with<00:18:30.660> your<00:18:30.840> origin<00:18:31.200> X<00:18:31.380> wallet 00:18:31.789 --> 00:18:31.799 align:start position:0% transaction with your origin X wallet 00:18:31.799 --> 00:18:34.430 align:start position:0% transaction with your origin X wallet the<00:18:32.400> call<00:18:32.640> data<00:18:33.059> so<00:18:33.360> the<00:18:33.600> raw<00:18:33.840> call<00:18:34.020> that<00:18:34.320> will 00:18:34.430 --> 00:18:34.440 align:start position:0% the call data so the raw call that will 00:18:34.440 --> 00:18:36.470 align:start position:0% the call data so the raw call that will be<00:18:34.559> executed<00:18:35.039> on<00:18:35.220> chain<00:18:35.400> can<00:18:35.700> be<00:18:35.880> sent<00:18:36.059> to<00:18:36.240> that 00:18:36.470 --> 00:18:36.480 align:start position:0% be executed on chain can be sent to that 00:18:36.480 --> 00:18:39.049 align:start position:0% be executed on chain can be sent to that service<00:18:36.660> for<00:18:37.200> analysis<00:18:37.799> and<00:18:38.640> that<00:18:38.760> service 00:18:39.049 --> 00:18:39.059 align:start position:0% service for analysis and that service 00:18:39.059 --> 00:18:41.510 align:start position:0% service for analysis and that service based<00:18:39.600> on<00:18:39.660> some<00:18:40.020> business<00:18:40.620> rules<00:18:41.100> that<00:18:41.400> you 00:18:41.510 --> 00:18:41.520 align:start position:0% based on some business rules that you 00:18:41.520 --> 00:18:44.270 align:start position:0% based on some business rules that you may<00:18:41.640> have<00:18:41.760> decide<00:18:42.120> you<00:18:42.480> know<00:18:42.799> maximum<00:18:43.799> daily 00:18:44.270 --> 00:18:44.280 align:start position:0% may have decide you know maximum daily 00:18:44.280 --> 00:18:47.029 align:start position:0% may have decide you know maximum daily limit<00:18:44.580> or<00:18:45.240> you<00:18:45.539> know<00:18:45.660> trusted<00:18:46.260> up<00:18:46.559> and<00:18:46.740> so<00:18:46.919> on 00:18:47.029 --> 00:18:47.039 align:start position:0% limit or you know trusted up and so on 00:18:47.039 --> 00:18:49.130 align:start position:0% limit or you know trusted up and so on so<00:18:47.220> it<00:18:47.280> can<00:18:47.460> use<00:18:47.640> whatever<00:18:48.299> logic<00:18:48.840> you've 00:18:49.130 --> 00:18:49.140 align:start position:0% so it can use whatever logic you've 00:18:49.140 --> 00:18:52.490 align:start position:0% so it can use whatever logic you've decided<00:18:49.620> to<00:18:50.400> decide<00:18:50.700> if<00:18:51.059> the<00:18:51.419> transaction<00:18:51.900> is 00:18:52.490 --> 00:18:52.500 align:start position:0% decided to decide if the transaction is 00:18:52.500 --> 00:18:54.770 align:start position:0% decided to decide if the transaction is secure<00:18:52.919> it's<00:18:53.580> something<00:18:53.760> that<00:18:54.179> we<00:18:54.419> know<00:18:54.539> is 00:18:54.770 --> 00:18:54.780 align:start position:0% secure it's something that we know is 00:18:54.780 --> 00:18:58.190 align:start position:0% secure it's something that we know is legit<00:18:55.200> or<00:18:55.679> if<00:18:56.400> he<00:18:56.520> doesn't<00:18:56.700> know<00:18:56.940> if<00:18:57.720> we<00:18:57.840> if<00:18:58.080> it 00:18:58.190 --> 00:18:58.200 align:start position:0% legit or if he doesn't know if we if it 00:18:58.200 --> 00:18:59.930 align:start position:0% legit or if he doesn't know if we if it knows<00:18:58.440> the<00:18:58.559> transaction<00:18:58.919> it<00:18:59.220> can<00:18:59.340> co-sign 00:18:59.930 --> 00:18:59.940 align:start position:0% knows the transaction it can co-sign 00:18:59.940 --> 00:19:01.970 align:start position:0% knows the transaction it can co-sign automatically<00:19:00.780> transparent<00:19:01.440> to<00:19:01.559> the<00:19:01.679> user 00:19:01.970 --> 00:19:01.980 align:start position:0% automatically transparent to the user 00:19:01.980 --> 00:19:03.409 align:start position:0% automatically transparent to the user right<00:19:02.100> you've<00:19:02.460> just<00:19:02.580> made<00:19:02.760> one<00:19:02.940> approve 00:19:03.409 --> 00:19:03.419 align:start position:0% right you've just made one approve 00:19:03.419 --> 00:19:06.049 align:start position:0% right you've just made one approve automatically<00:19:04.380> the<00:19:05.160> transaction<00:19:05.580> is<00:19:05.880> sent 00:19:06.049 --> 00:19:06.059 align:start position:0% automatically the transaction is sent 00:19:06.059 --> 00:19:08.470 align:start position:0% automatically the transaction is sent but<00:19:06.720> if<00:19:06.900> for<00:19:07.080> some<00:19:07.200> reason<00:19:07.440> the<00:19:08.280> service 00:19:08.470 --> 00:19:08.480 align:start position:0% but if for some reason the service 00:19:08.480 --> 00:19:10.909 align:start position:0% but if for some reason the service detects<00:19:09.480> that<00:19:09.600> it's<00:19:09.960> a<00:19:10.200> call<00:19:10.320> to<00:19:10.559> a<00:19:10.679> contract 00:19:10.909 --> 00:19:10.919 align:start position:0% detects that it's a call to a contract 00:19:10.919 --> 00:19:13.850 align:start position:0% detects that it's a call to a contract like<00:19:11.580> that<00:19:12.000> he<00:19:12.179> doesn't<00:19:12.360> know<00:19:12.600> for<00:19:12.900> example<00:19:13.140> he 00:19:13.850 --> 00:19:13.860 align:start position:0% like that he doesn't know for example he 00:19:13.860 --> 00:19:16.010 align:start position:0% like that he doesn't know for example he may<00:19:14.039> ask<00:19:14.160> you<00:19:14.340> to<00:19:14.520> confirm<00:19:14.940> who<00:19:15.120> you<00:19:15.299> are<00:19:15.480> using 00:19:16.010 --> 00:19:16.020 align:start position:0% may ask you to confirm who you are using 00:19:16.020 --> 00:19:18.350 align:start position:0% may ask you to confirm who you are using a<00:19:16.140> second<00:19:16.380> Factor<00:19:16.860> just<00:19:17.520> to<00:19:17.700> make<00:19:17.940> sure<00:19:18.059> that 00:19:18.350 --> 00:19:18.360 align:start position:0% a second Factor just to make sure that 00:19:18.360 --> 00:19:20.150 align:start position:0% a second Factor just to make sure that no<00:19:18.480> one<00:19:18.660> is<00:19:18.780> abusing<00:19:19.200> your<00:19:19.380> account<00:19:19.559> so 00:19:20.150 --> 00:19:20.160 align:start position:0% no one is abusing your account so 00:19:20.160 --> 00:19:21.830 align:start position:0% no one is abusing your account so suddenly<00:19:20.460> you<00:19:20.760> can<00:19:20.820> bring<00:19:21.000> fraud<00:19:21.419> monitoring 00:19:21.830 --> 00:19:21.840 align:start position:0% suddenly you can bring fraud monitoring 00:19:21.840 --> 00:19:23.930 align:start position:0% suddenly you can bring fraud monitoring with<00:19:22.020> 2fa<00:19:22.440> on<00:19:22.679> chain<00:19:22.799> thanks<00:19:23.160> to<00:19:23.280> a<00:19:23.460> account 00:19:23.930 --> 00:19:23.940 align:start position:0% with 2fa on chain thanks to a account 00:19:23.940 --> 00:19:25.250 align:start position:0% with 2fa on chain thanks to a account abstraction 00:19:25.250 --> 00:19:25.260 align:start position:0% abstraction 00:19:25.260 --> 00:19:27.470 align:start position:0% abstraction what<00:19:25.740> else<00:19:25.860> this<00:19:26.520> one<00:19:26.700> is<00:19:26.880> something<00:19:27.059> that<00:19:27.360> I'm 00:19:27.470 --> 00:19:27.480 align:start position:0% what else this one is something that I'm 00:19:27.480 --> 00:19:29.270 align:start position:0% what else this one is something that I'm very<00:19:27.720> excited<00:19:28.080> about<00:19:28.200> the<00:19:28.559> idea<00:19:28.799> of<00:19:28.919> session 00:19:29.270 --> 00:19:29.280 align:start position:0% very excited about the idea of session 00:19:29.280 --> 00:19:31.130 align:start position:0% very excited about the idea of session keys<00:19:29.820> and<00:19:30.299> I<00:19:30.419> think<00:19:30.539> it's<00:19:30.720> particularly 00:19:31.130 --> 00:19:31.140 align:start position:0% keys and I think it's particularly 00:19:31.140 --> 00:19:33.590 align:start position:0% keys and I think it's particularly relevant<00:19:31.500> now<00:19:31.679> for<00:19:31.919> on-chain<00:19:32.400> games<00:19:32.640> so<00:19:33.419> if 00:19:33.590 --> 00:19:33.600 align:start position:0% relevant now for on-chain games so if 00:19:33.600 --> 00:19:36.710 align:start position:0% relevant now for on-chain games so if you<00:19:33.720> play<00:19:33.900> non-chained<00:19:34.500> games<00:19:35.000> you've<00:19:36.000> I 00:19:36.710 --> 00:19:36.720 align:start position:0% you play non-chained games you've I 00:19:36.720 --> 00:19:38.990 align:start position:0% you play non-chained games you've I guess<00:19:36.840> all<00:19:37.080> been<00:19:37.260> frustrated<00:19:37.799> by<00:19:38.220> the<00:19:38.400> need<00:19:38.580> to 00:19:38.990 --> 00:19:39.000 align:start position:0% guess all been frustrated by the need to 00:19:39.000 --> 00:19:41.510 align:start position:0% guess all been frustrated by the need to sign<00:19:39.360> transaction<00:19:40.320> every<00:19:40.799> time<00:19:41.039> you<00:19:41.220> make<00:19:41.340> an 00:19:41.510 --> 00:19:41.520 align:start position:0% sign transaction every time you make an 00:19:41.520 --> 00:19:43.850 align:start position:0% sign transaction every time you make an action<00:19:41.760> having<00:19:42.120> your<00:19:42.480> wallet<00:19:42.780> pop-up<00:19:43.140> you 00:19:43.850 --> 00:19:43.860 align:start position:0% action having your wallet pop-up you 00:19:43.860 --> 00:19:45.230 align:start position:0% action having your wallet pop-up you approve<00:19:44.280> and<00:19:44.460> then<00:19:44.580> you<00:19:44.700> come<00:19:44.880> back<00:19:44.940> to<00:19:45.120> the 00:19:45.230 --> 00:19:45.240 align:start position:0% approve and then you come back to the 00:19:45.240 --> 00:19:46.730 align:start position:0% approve and then you come back to the game<00:19:45.360> so<00:19:45.539> Unchained<00:19:46.080> games<00:19:46.200> today<00:19:46.440> is 00:19:46.730 --> 00:19:46.740 align:start position:0% game so Unchained games today is 00:19:46.740 --> 00:19:48.650 align:start position:0% game so Unchained games today is basically<00:19:47.039> going<00:19:47.400> on<00:19:47.880> and<00:19:48.059> off<00:19:48.240> of<00:19:48.360> the<00:19:48.539> game 00:19:48.650 --> 00:19:48.660 align:start position:0% basically going on and off of the game 00:19:48.660 --> 00:19:51.529 align:start position:0% basically going on and off of the game to<00:19:49.320> approve<00:19:49.679> transaction<00:19:50.100> well<00:19:51.000> the<00:19:51.240> idea<00:19:51.419> of 00:19:51.529 --> 00:19:51.539 align:start position:0% to approve transaction well the idea of 00:19:51.539 --> 00:19:54.049 align:start position:0% to approve transaction well the idea of session<00:19:51.720> Keys<00:19:52.140> is<00:19:52.260> to<00:19:52.440> say<00:19:52.620> no<00:19:52.860> imagine<00:19:53.580> that 00:19:54.049 --> 00:19:54.059 align:start position:0% session Keys is to say no imagine that 00:19:54.059 --> 00:19:57.350 align:start position:0% session Keys is to say no imagine that your<00:19:54.240> game<00:19:54.539> the<00:19:54.720> dab<00:19:55.080> the<00:19:55.620> client<00:19:55.919> generates<00:19:56.820> a 00:19:57.350 --> 00:19:57.360 align:start position:0% your game the dab the client generates a 00:19:57.360 --> 00:19:59.750 align:start position:0% your game the dab the client generates a temporary<00:19:57.780> key<00:19:58.080> in<00:19:58.559> your<00:19:58.740> browser<00:19:59.039> and<00:19:59.580> ask 00:19:59.750 --> 00:19:59.760 align:start position:0% temporary key in your browser and ask 00:19:59.760 --> 00:20:02.210 align:start position:0% temporary key in your browser and ask you<00:19:59.940> to<00:20:00.120> approve<00:20:00.539> that<00:20:00.720> key<00:20:00.960> but<00:20:01.679> he<00:20:01.860> asks<00:20:02.100> you 00:20:02.210 --> 00:20:02.220 align:start position:0% you to approve that key but he asks you 00:20:02.220 --> 00:20:03.950 align:start position:0% you to approve that key but he asks you to<00:20:02.340> approve<00:20:02.640> that<00:20:02.820> key<00:20:03.059> with<00:20:03.360> a<00:20:03.539> set<00:20:03.720> of 00:20:03.950 --> 00:20:03.960 align:start position:0% to approve that key with a set of 00:20:03.960 --> 00:20:06.590 align:start position:0% to approve that key with a set of constrained<00:20:04.559> policies<00:20:05.039> for<00:20:05.700> example<00:20:06.000> the<00:20:06.299> DAP 00:20:06.590 --> 00:20:06.600 align:start position:0% constrained policies for example the DAP 00:20:06.600 --> 00:20:09.049 align:start position:0% constrained policies for example the DAP will<00:20:06.780> say<00:20:07.020> I<00:20:07.679> want<00:20:07.799> to<00:20:07.919> sign<00:20:08.160> transaction<00:20:08.640> but 00:20:09.049 --> 00:20:09.059 align:start position:0% will say I want to sign transaction but 00:20:09.059 --> 00:20:11.450 align:start position:0% will say I want to sign transaction but only<00:20:09.360> for<00:20:09.600> 25<00:20:09.840> minutes<00:20:10.260> the<00:20:10.799> duration<00:20:11.100> of<00:20:11.340> a 00:20:11.450 --> 00:20:11.460 align:start position:0% only for 25 minutes the duration of a 00:20:11.460 --> 00:20:13.909 align:start position:0% only for 25 minutes the duration of a session<00:20:11.640> and<00:20:12.299> I<00:20:12.480> will<00:20:12.660> only<00:20:12.840> call<00:20:13.260> this 00:20:13.909 --> 00:20:13.919 align:start position:0% session and I will only call this 00:20:13.919 --> 00:20:15.890 align:start position:0% session and I will only call this contract<00:20:14.340> and<00:20:14.580> that<00:20:14.820> contract<00:20:15.179> and<00:20:15.480> descend 00:20:15.890 --> 00:20:15.900 align:start position:0% contract and that contract and descend 00:20:15.900 --> 00:20:17.870 align:start position:0% contract and that contract and descend that<00:20:16.080> method<00:20:16.440> that's<00:20:17.039> the<00:20:17.280> only<00:20:17.340> thing<00:20:17.520> that<00:20:17.760> I 00:20:17.870 --> 00:20:17.880 align:start position:0% that method that's the only thing that I 00:20:17.880 --> 00:20:20.630 align:start position:0% that method that's the only thing that I want<00:20:17.940> to<00:20:18.059> do<00:20:18.240> as<00:20:19.080> a<00:20:19.260> user<00:20:19.559> you<00:20:19.799> can<00:20:19.919> approve<00:20:20.340> so 00:20:20.630 --> 00:20:20.640 align:start position:0% want to do as a user you can approve so 00:20:20.640 --> 00:20:22.430 align:start position:0% want to do as a user you can approve so yes<00:20:20.880> that's<00:20:21.240> one<00:20:21.480> confirmation<00:20:22.080> with<00:20:22.380> your 00:20:22.430 --> 00:20:22.440 align:start position:0% yes that's one confirmation with your 00:20:22.440 --> 00:20:24.289 align:start position:0% yes that's one confirmation with your wallet<00:20:22.799> you<00:20:22.980> say<00:20:23.100> yeah<00:20:23.280> I<00:20:23.760> want<00:20:23.820> to<00:20:23.940> start<00:20:24.059> a 00:20:24.289 --> 00:20:24.299 align:start position:0% wallet you say yeah I want to start a 00:20:24.299 --> 00:20:26.330 align:start position:0% wallet you say yeah I want to start a session<00:20:24.480> on<00:20:24.720> that<00:20:24.840> game<00:20:25.380> under<00:20:26.039> this 00:20:26.330 --> 00:20:26.340 align:start position:0% session on that game under this 00:20:26.340 --> 00:20:28.130 align:start position:0% session on that game under this condition<00:20:26.580> and<00:20:27.480> next<00:20:27.660> when<00:20:27.840> you<00:20:28.020> start 00:20:28.130 --> 00:20:28.140 align:start position:0% condition and next when you start 00:20:28.140 --> 00:20:29.990 align:start position:0% condition and next when you start playing<00:20:28.380> the<00:20:28.620> game<00:20:28.799> every<00:20:29.280> time<00:20:29.520> you<00:20:29.700> click<00:20:29.940> on 00:20:29.990 --> 00:20:30.000 align:start position:0% playing the game every time you click on 00:20:30.000 --> 00:20:32.630 align:start position:0% playing the game every time you click on a<00:20:30.179> button<00:20:30.480> you<00:20:30.900> make<00:20:31.020> a<00:20:31.200> game<00:20:31.320> action<00:20:31.679> the<00:20:32.340> dab 00:20:32.630 --> 00:20:32.640 align:start position:0% a button you make a game action the dab 00:20:32.640 --> 00:20:34.490 align:start position:0% a button you make a game action the dab can<00:20:32.820> send<00:20:33.120> the<00:20:33.299> transaction<00:20:33.660> directly<00:20:34.260> to 00:20:34.490 --> 00:20:34.500 align:start position:0% can send the transaction directly to 00:20:34.500 --> 00:20:35.390 align:start position:0% can send the transaction directly to your<00:20:34.679> account 00:20:35.390 --> 00:20:35.400 align:start position:0% your account 00:20:35.400 --> 00:20:37.190 align:start position:0% your account and<00:20:35.880> the<00:20:36.059> transaction<00:20:36.360> will<00:20:36.660> be<00:20:36.780> approved<00:20:37.080> so 00:20:37.190 --> 00:20:37.200 align:start position:0% and the transaction will be approved so 00:20:37.200 --> 00:20:38.690 align:start position:0% and the transaction will be approved so you<00:20:37.380> no<00:20:37.620> longer<00:20:37.799> need<00:20:37.980> to<00:20:38.100> sign<00:20:38.280> you're<00:20:38.520> no 00:20:38.690 --> 00:20:38.700 align:start position:0% you no longer need to sign you're no 00:20:38.700 --> 00:20:40.190 align:start position:0% you no longer need to sign you're no longer<00:20:39.120> need<00:20:39.299> to<00:20:39.360> confirm<00:20:39.780> you<00:20:39.900> can<00:20:40.080> actually 00:20:40.190 --> 00:20:40.200 align:start position:0% longer need to confirm you can actually 00:20:40.200 --> 00:20:42.590 align:start position:0% longer need to confirm you can actually focus<00:20:40.740> on<00:20:40.980> playing<00:20:41.220> the<00:20:41.400> game<00:20:41.580> but<00:20:42.299> you<00:20:42.480> know 00:20:42.590 --> 00:20:42.600 align:start position:0% focus on playing the game but you know 00:20:42.600 --> 00:20:44.090 align:start position:0% focus on playing the game but you know that<00:20:42.840> your<00:20:42.960> account<00:20:43.200> and<00:20:43.500> your<00:20:43.620> tokens<00:20:43.919> are 00:20:44.090 --> 00:20:44.100 align:start position:0% that your account and your tokens are 00:20:44.100 --> 00:20:46.490 align:start position:0% that your account and your tokens are secure<00:20:44.520> because<00:20:45.179> the<00:20:45.480> key<00:20:45.600> you<00:20:45.780> approved<00:20:46.260> can 00:20:46.490 --> 00:20:46.500 align:start position:0% secure because the key you approved can 00:20:46.500 --> 00:20:49.190 align:start position:0% secure because the key you approved can only<00:20:46.740> do<00:20:47.100> a<00:20:47.700> very<00:20:47.820> construct<00:20:48.360> set<00:20:48.660> of<00:20:48.780> actions 00:20:49.190 --> 00:20:49.200 align:start position:0% only do a very construct set of actions 00:20:49.200 --> 00:20:51.049 align:start position:0% only do a very construct set of actions that<00:20:49.440> you<00:20:49.679> have<00:20:49.799> approved<00:20:50.280> that's<00:20:50.760> something 00:20:51.049 --> 00:20:51.059 align:start position:0% that you have approved that's something 00:20:51.059 --> 00:20:53.570 align:start position:0% that you have approved that's something that<00:20:51.620> several<00:20:52.620> games<00:20:52.799> are<00:20:53.039> actually<00:20:53.220> now 00:20:53.570 --> 00:20:53.580 align:start position:0% that several games are actually now 00:20:53.580 --> 00:20:56.210 align:start position:0% that several games are actually now integrating<00:20:54.299> into<00:20:54.539> their<00:20:54.780> logic<00:20:55.200> on<00:20:55.740> stagnet 00:20:56.210 --> 00:20:56.220 align:start position:0% integrating into their logic on stagnet 00:20:56.220 --> 00:20:57.470 align:start position:0% integrating into their logic on stagnet so<00:20:56.340> I<00:20:56.460> do<00:20:56.520> believe<00:20:56.640> that<00:20:56.820> that's<00:20:57.000> a<00:20:57.179> pattern 00:20:57.470 --> 00:20:57.480 align:start position:0% so I do believe that that's a pattern 00:20:57.480 --> 00:20:59.510 align:start position:0% so I do believe that that's a pattern that<00:20:57.720> will<00:20:57.840> come<00:20:58.080> and<00:20:58.500> that<00:20:58.620> really<00:20:59.100> will 00:20:59.510 --> 00:20:59.520 align:start position:0% that will come and that really will 00:20:59.520 --> 00:21:01.730 align:start position:0% that will come and that really will enable<00:20:59.820> the<00:21:00.120> ux<00:21:00.480> of<00:21:00.720> of<00:21:01.020> unchain<00:21:01.440> games 00:21:01.730 --> 00:21:01.740 align:start position:0% enable the ux of of unchain games 00:21:01.740 --> 00:21:03.650 align:start position:0% enable the ux of of unchain games another<00:21:02.460> thing<00:21:02.820> is<00:21:02.940> that<00:21:03.179> we<00:21:03.480> are 00:21:03.650 --> 00:21:03.660 align:start position:0% another thing is that we are 00:21:03.660 --> 00:21:05.510 align:start position:0% another thing is that we are experimenting<00:21:04.620> and<00:21:04.799> it's<00:21:04.980> a<00:21:05.160> collaboration 00:21:05.510 --> 00:21:05.520 align:start position:0% experimenting and it's a collaboration 00:21:05.520 --> 00:21:08.450 align:start position:0% experimenting and it's a collaboration with<00:21:05.940> cartridge<00:21:06.419> and<00:21:06.660> Ledger<00:21:07.320> is<00:21:07.860> the<00:21:08.039> idea<00:21:08.280> to 00:21:08.450 --> 00:21:08.460 align:start position:0% with cartridge and Ledger is the idea to 00:21:08.460 --> 00:21:10.730 align:start position:0% with cartridge and Ledger is the idea to make<00:21:08.580> the<00:21:08.760> account<00:21:08.940> much<00:21:09.480> more<00:21:09.660> modular<00:21:10.080> so 00:21:10.730 --> 00:21:10.740 align:start position:0% make the account much more modular so 00:21:10.740 --> 00:21:12.590 align:start position:0% make the account much more modular so imagine<00:21:10.919> that<00:21:11.340> your<00:21:11.520> account<00:21:11.760> is<00:21:12.120> kind<00:21:12.299> of<00:21:12.419> a 00:21:12.590 --> 00:21:12.600 align:start position:0% imagine that your account is kind of a 00:21:12.600 --> 00:21:15.350 align:start position:0% imagine that your account is kind of a base<00:21:12.840> contract<00:21:13.380> on<00:21:14.160> top<00:21:14.520> of<00:21:14.700> which<00:21:14.880> you<00:21:15.240> can 00:21:15.350 --> 00:21:15.360 align:start position:0% base contract on top of which you can 00:21:15.360 --> 00:21:18.110 align:start position:0% base contract on top of which you can add<00:21:15.539> plugins<00:21:16.080> and<00:21:16.799> each<00:21:17.039> plugin<00:21:17.460> can<00:21:17.760> have<00:21:17.940> a 00:21:18.110 --> 00:21:18.120 align:start position:0% add plugins and each plugin can have a 00:21:18.120 --> 00:21:20.090 align:start position:0% add plugins and each plugin can have a different<00:21:18.240> logic<00:21:18.780> to<00:21:19.080> validate<00:21:19.559> and<00:21:19.740> execute 00:21:20.090 --> 00:21:20.100 align:start position:0% different logic to validate and execute 00:21:20.100 --> 00:21:21.830 align:start position:0% different logic to validate and execute transaction<00:21:20.520> so<00:21:21.059> you<00:21:21.179> can<00:21:21.299> imagine<00:21:21.419> that 00:21:21.830 --> 00:21:21.840 align:start position:0% transaction so you can imagine that 00:21:21.840 --> 00:21:23.690 align:start position:0% transaction so you can imagine that there's<00:21:21.960> a<00:21:22.200> plugin<00:21:22.500> which<00:21:22.919> contains<00:21:23.580> the 00:21:23.690 --> 00:21:23.700 align:start position:0% there's a plugin which contains the 00:21:23.700 --> 00:21:25.789 align:start position:0% there's a plugin which contains the session<00:21:23.820> keys<00:21:24.360> that<00:21:24.480> I<00:21:24.660> just<00:21:24.840> showed<00:21:25.140> there's 00:21:25.789 --> 00:21:25.799 align:start position:0% session keys that I just showed there's 00:21:25.799 --> 00:21:28.430 align:start position:0% session keys that I just showed there's another<00:21:26.100> plugin<00:21:26.700> that<00:21:27.179> may<00:21:27.419> work<00:21:27.720> as<00:21:27.900> a<00:21:28.080> new<00:21:28.200> a 00:21:28.430 --> 00:21:28.440 align:start position:0% another plugin that may work as a new a 00:21:28.440 --> 00:21:29.990 align:start position:0% another plugin that may work as a new a just<00:21:28.620> a<00:21:28.799> signer<00:21:29.220> but<00:21:29.520> then<00:21:29.640> there's<00:21:29.820> another 00:21:29.990 --> 00:21:30.000 align:start position:0% just a signer but then there's another 00:21:30.000 --> 00:21:32.870 align:start position:0% just a signer but then there's another plugin<00:21:30.480> which<00:21:30.780> much<00:21:31.080> stronger<00:21:32.039> security<00:21:32.280> that 00:21:32.870 --> 00:21:32.880 align:start position:0% plugin which much stronger security that 00:21:32.880 --> 00:21:34.850 align:start position:0% plugin which much stronger security that we'll<00:21:33.120> use<00:21:33.360> that<00:21:33.780> will<00:21:33.900> be<00:21:34.020> a<00:21:34.140> multi-sig<00:21:34.620> or 00:21:34.850 --> 00:21:34.860 align:start position:0% we'll use that will be a multi-sig or 00:21:34.860 --> 00:21:37.370 align:start position:0% we'll use that will be a multi-sig or that<00:21:34.919> will<00:21:35.039> do<00:21:35.159> social<00:21:35.340> a<00:21:35.760> recovery<00:21:36.240> as<00:21:36.840> a<00:21:37.020> user 00:21:37.370 --> 00:21:37.380 align:start position:0% that will do social a recovery as a user 00:21:37.380 --> 00:21:39.710 align:start position:0% that will do social a recovery as a user you<00:21:37.919> can<00:21:38.039> actually<00:21:38.220> pick<00:21:38.640> and<00:21:38.880> choose<00:21:39.299> the 00:21:39.710 --> 00:21:39.720 align:start position:0% you can actually pick and choose the 00:21:39.720 --> 00:21:41.270 align:start position:0% you can actually pick and choose the plugins<00:21:40.020> that<00:21:40.320> you<00:21:40.440> want<00:21:40.620> for<00:21:40.860> your<00:21:41.039> wallet 00:21:41.270 --> 00:21:41.280 align:start position:0% plugins that you want for your wallet 00:21:41.280 --> 00:21:43.669 align:start position:0% plugins that you want for your wallet and<00:21:41.520> really<00:21:41.700> design<00:21:41.940> your<00:21:42.360> wallet<00:21:42.659> for<00:21:43.500> the 00:21:43.669 --> 00:21:43.679 align:start position:0% and really design your wallet for the 00:21:43.679 --> 00:21:45.169 align:start position:0% and really design your wallet for the purpose<00:21:43.980> the<00:21:44.280> use<00:21:44.460> case<00:21:44.580> that<00:21:44.880> you<00:21:45.000> want<00:21:45.059> to 00:21:45.169 --> 00:21:45.179 align:start position:0% purpose the use case that you want to 00:21:45.179 --> 00:21:47.630 align:start position:0% purpose the use case that you want to use<00:21:45.299> it<00:21:45.480> if<00:21:45.900> a<00:21:46.200> wallet<00:21:46.500> for<00:21:46.679> gaming<00:21:47.039> where<00:21:47.400> you 00:21:47.630 --> 00:21:47.640 align:start position:0% use it if a wallet for gaming where you 00:21:47.640 --> 00:21:49.250 align:start position:0% use it if a wallet for gaming where you know<00:21:47.700> you<00:21:47.880> will<00:21:48.000> spend<00:21:48.240> maximum<00:21:48.659> 50<00:21:48.900> dollars 00:21:49.250 --> 00:21:49.260 align:start position:0% know you will spend maximum 50 dollars 00:21:49.260 --> 00:21:51.230 align:start position:0% know you will spend maximum 50 dollars does<00:21:49.740> may<00:21:50.220> not<00:21:50.340> need<00:21:50.520> the<00:21:50.820> same<00:21:50.940> security 00:21:51.230 --> 00:21:51.240 align:start position:0% does may not need the same security 00:21:51.240 --> 00:21:53.450 align:start position:0% does may not need the same security requirements<00:21:52.080> as<00:21:52.320> your<00:21:52.559> the<00:21:52.799> wallet<00:21:53.159> you<00:21:53.280> use 00:21:53.450 --> 00:21:53.460 align:start position:0% requirements as your the wallet you use 00:21:53.460 --> 00:21:55.789 align:start position:0% requirements as your the wallet you use for<00:21:53.640> trading<00:21:53.940> on<00:21:54.059> D5<00:21:54.419> for<00:21:54.720> example<00:21:54.900> and<00:21:55.559> by 00:21:55.789 --> 00:21:55.799 align:start position:0% for trading on D5 for example and by 00:21:55.799 --> 00:21:57.770 align:start position:0% for trading on D5 for example and by making<00:21:55.980> the<00:21:56.280> account<00:21:56.460> modular<00:21:57.000> user<00:21:57.600> can 00:21:57.770 --> 00:21:57.780 align:start position:0% making the account modular user can 00:21:57.780 --> 00:21:59.930 align:start position:0% making the account modular user can really<00:21:58.020> choose<00:21:58.500> pick<00:21:58.740> and<00:21:58.980> choose<00:21:59.159> the 00:21:59.930 --> 00:21:59.940 align:start position:0% really choose pick and choose the 00:21:59.940 --> 00:22:02.330 align:start position:0% really choose pick and choose the experience<00:22:00.299> that<00:22:00.600> that<00:22:01.080> they<00:22:01.380> want<00:22:01.559> and 00:22:02.330 --> 00:22:02.340 align:start position:0% experience that that they want and 00:22:02.340 --> 00:22:04.190 align:start position:0% experience that that they want and finally<00:22:02.580> one<00:22:02.940> last<00:22:03.059> feature<00:22:03.539> that<00:22:03.840> we<00:22:04.080> are 00:22:04.190 --> 00:22:04.200 align:start position:0% finally one last feature that we are 00:22:04.200 --> 00:22:06.470 align:start position:0% finally one last feature that we are exploring<00:22:04.620> is<00:22:05.400> the<00:22:05.640> ability<00:22:05.880> to<00:22:06.179> use<00:22:06.299> the 00:22:06.470 --> 00:22:06.480 align:start position:0% exploring is the ability to use the 00:22:06.480 --> 00:22:08.450 align:start position:0% exploring is the ability to use the secure<00:22:06.780> Enclave<00:22:07.020> of<00:22:07.320> your<00:22:07.440> phone 00:22:08.450 --> 00:22:08.460 align:start position:0% secure Enclave of your phone 00:22:08.460 --> 00:22:10.730 align:start position:0% secure Enclave of your phone because<00:22:09.059> your<00:22:09.419> account<00:22:09.600> can<00:22:10.080> be<00:22:10.260> programmed 00:22:10.730 --> 00:22:10.740 align:start position:0% because your account can be programmed 00:22:10.740 --> 00:22:12.770 align:start position:0% because your account can be programmed you<00:22:11.039> can<00:22:11.100> actually<00:22:11.280> program<00:22:11.700> it<00:22:12.059> to<00:22:12.299> verify 00:22:12.770 --> 00:22:12.780 align:start position:0% you can actually program it to verify 00:22:12.780 --> 00:22:14.810 align:start position:0% you can actually program it to verify signature<00:22:13.440> on<00:22:13.740> a<00:22:13.860> different<00:22:13.980> elliptic<00:22:14.520> curve 00:22:14.810 --> 00:22:14.820 align:start position:0% signature on a different elliptic curve 00:22:14.820 --> 00:22:18.110 align:start position:0% signature on a different elliptic curve and<00:22:15.360> for<00:22:15.539> example<00:22:15.780> you<00:22:16.200> can<00:22:16.799> use<00:22:17.400> it<00:22:17.580> to<00:22:17.820> verify 00:22:18.110 --> 00:22:18.120 align:start position:0% and for example you can use it to verify 00:22:18.120 --> 00:22:20.810 align:start position:0% and for example you can use it to verify signatures<00:22:18.960> a<00:22:19.799> curve<00:22:20.100> that's<00:22:20.220> approved<00:22:20.700> by 00:22:20.810 --> 00:22:20.820 align:start position:0% signatures a curve that's approved by 00:22:20.820 --> 00:22:22.789 align:start position:0% signatures a curve that's approved by the<00:22:21.059> nist<00:22:21.360> and<00:22:21.780> that<00:22:21.900> is<00:22:22.080> implemented<00:22:22.559> in<00:22:22.740> the 00:22:22.789 --> 00:22:22.799 align:start position:0% the nist and that is implemented in the 00:22:22.799 --> 00:22:24.770 align:start position:0% the nist and that is implemented in the secure<00:22:23.100> Enclave<00:22:23.280> of<00:22:23.580> your<00:22:23.760> phone<00:22:24.000> and 00:22:24.770 --> 00:22:24.780 align:start position:0% secure Enclave of your phone and 00:22:24.780 --> 00:22:26.930 align:start position:0% secure Enclave of your phone and suddenly<00:22:25.140> you<00:22:25.500> are<00:22:25.679> turning<00:22:26.159> every<00:22:26.580> single 00:22:26.930 --> 00:22:26.940 align:start position:0% suddenly you are turning every single 00:22:26.940 --> 00:22:29.270 align:start position:0% suddenly you are turning every single smartphone<00:22:27.480> into<00:22:27.900> a<00:22:28.080> hardware<00:22:28.200> wallet<00:22:28.740> and 00:22:29.270 --> 00:22:29.280 align:start position:0% smartphone into a hardware wallet and 00:22:29.280 --> 00:22:30.649 align:start position:0% smartphone into a hardware wallet and that's<00:22:29.460> actually<00:22:29.700> something<00:22:30.059> that<00:22:30.480> someone 00:22:30.649 --> 00:22:30.659 align:start position:0% that's actually something that someone 00:22:30.659 --> 00:22:33.350 align:start position:0% that's actually something that someone has<00:22:30.900> done<00:22:31.080> on<00:22:31.260> stacknet<00:22:31.799> so<00:22:32.159> he<00:22:32.400> built<00:22:32.880> an 00:22:33.350 --> 00:22:33.360 align:start position:0% has done on stacknet so he built an 00:22:33.360 --> 00:22:35.690 align:start position:0% has done on stacknet so he built an account<00:22:33.539> that<00:22:34.140> uses<00:22:34.740> that<00:22:34.860> logic<00:22:35.220> to<00:22:35.340> verify 00:22:35.690 --> 00:22:35.700 align:start position:0% account that uses that logic to verify 00:22:35.700 --> 00:22:38.090 align:start position:0% account that uses that logic to verify signature<00:22:36.299> so<00:22:36.960> you<00:22:37.140> can<00:22:37.260> really<00:22:37.440> now<00:22:37.799> turn 00:22:38.090 --> 00:22:38.100 align:start position:0% signature so you can really now turn 00:22:38.100 --> 00:22:40.850 align:start position:0% signature so you can really now turn smartphone<00:22:39.000> into<00:22:39.240> Hardware<00:22:39.480> wallet<00:22:40.020> the<00:22:40.679> use 00:22:40.850 --> 00:22:40.860 align:start position:0% smartphone into Hardware wallet the use 00:22:40.860 --> 00:22:42.409 align:start position:0% smartphone into Hardware wallet the use cases<00:22:41.100> that<00:22:41.400> I<00:22:41.580> showed<00:22:41.820> you<00:22:41.880> are<00:22:42.000> the<00:22:42.240> stuff 00:22:42.409 --> 00:22:42.419 align:start position:0% cases that I showed you are the stuff 00:22:42.419 --> 00:22:44.149 align:start position:0% cases that I showed you are the stuff that<00:22:42.659> we<00:22:42.960> are<00:22:43.080> you<00:22:43.500> know<00:22:43.559> building<00:22:43.860> and 00:22:44.149 --> 00:22:44.159 align:start position:0% that we are you know building and 00:22:44.159 --> 00:22:45.890 align:start position:0% that we are you know building and exploring<00:22:44.520> at<00:22:45.059> urgent<00:22:45.240> but<00:22:45.360> I<00:22:45.600> believe<00:22:45.720> that 00:22:45.890 --> 00:22:45.900 align:start position:0% exploring at urgent but I believe that 00:22:45.900 --> 00:22:48.110 align:start position:0% exploring at urgent but I believe that icon<00:22:46.260> abstraction<00:22:46.679> opens<00:22:47.340> a<00:22:47.520> completely<00:22:47.820> new 00:22:48.110 --> 00:22:48.120 align:start position:0% icon abstraction opens a completely new 00:22:48.120 --> 00:22:50.930 align:start position:0% icon abstraction opens a completely new design<00:22:48.299> space<00:22:48.720> for<00:22:49.140> for<00:22:49.500> user<00:22:50.039> experience<00:22:50.400> and 00:22:50.930 --> 00:22:50.940 align:start position:0% design space for for user experience and 00:22:50.940 --> 00:22:52.669 align:start position:0% design space for for user experience and so<00:22:51.059> we're<00:22:51.240> only<00:22:51.419> scratching<00:22:52.020> the<00:22:52.140> surface<00:22:52.500> of 00:22:52.669 --> 00:22:52.679 align:start position:0% so we're only scratching the surface of 00:22:52.679 --> 00:22:55.070 align:start position:0% so we're only scratching the surface of what<00:22:52.860> can<00:22:53.039> be<00:22:53.220> done<00:22:53.340> so<00:22:54.059> I<00:22:54.480> hope<00:22:54.600> that<00:22:54.840> I've 00:22:55.070 --> 00:22:55.080 align:start position:0% what can be done so I hope that I've 00:22:55.080 --> 00:22:57.169 align:start position:0% what can be done so I hope that I've convinced<00:22:55.500> you<00:22:55.620> that<00:22:55.740> icon<00:22:56.039> abstraction<00:22:56.460> is 00:22:57.169 --> 00:22:57.179 align:start position:0% convinced you that icon abstraction is 00:22:57.179 --> 00:22:58.970 align:start position:0% convinced you that icon abstraction is needed<00:22:57.600> for<00:22:57.780> the<00:22:57.900> ux<00:22:58.200> of<00:22:58.440> the<00:22:58.500> blockchain<00:22:58.799> but 00:22:58.970 --> 00:22:58.980 align:start position:0% needed for the ux of the blockchain but 00:22:58.980 --> 00:23:01.070 align:start position:0% needed for the ux of the blockchain but I<00:22:59.159> think<00:22:59.280> more<00:22:59.640> importantly<00:23:00.120> to<00:23:00.539> really<00:23:00.780> scale 00:23:01.070 --> 00:23:01.080 align:start position:0% I think more importantly to really scale 00:23:01.080 --> 00:23:03.529 align:start position:0% I think more importantly to really scale the<00:23:01.380> user<00:23:01.679> experience<00:23:01.980> of<00:23:02.159> self-q<00:23:02.640> study<00:23:03.000> and 00:23:03.529 --> 00:23:03.539 align:start position:0% the user experience of self-q study and 00:23:03.539 --> 00:23:05.750 align:start position:0% the user experience of self-q study and the<00:23:03.720> thing<00:23:03.840> is<00:23:03.960> that<00:23:04.260> if<00:23:04.980> we<00:23:05.159> don't<00:23:05.280> do<00:23:05.520> that 00:23:05.750 --> 00:23:05.760 align:start position:0% the thing is that if we don't do that 00:23:05.760 --> 00:23:08.330 align:start position:0% the thing is that if we don't do that and<00:23:06.299> if<00:23:06.480> we<00:23:06.659> stick<00:23:06.900> to<00:23:07.140> the<00:23:07.320> eoa<00:23:07.740> model<00:23:07.919> that<00:23:08.220> we 00:23:08.330 --> 00:23:08.340 align:start position:0% and if we stick to the eoa model that we 00:23:08.340 --> 00:23:11.330 align:start position:0% and if we stick to the eoa model that we have<00:23:08.460> today<00:23:08.700> my<00:23:09.659> bet<00:23:09.900> is<00:23:10.620> that<00:23:10.799> the<00:23:10.919> next<00:23:11.039> wave 00:23:11.330 --> 00:23:11.340 align:start position:0% have today my bet is that the next wave 00:23:11.340 --> 00:23:13.370 align:start position:0% have today my bet is that the next wave of<00:23:11.580> users<00:23:11.940> they<00:23:12.299> will<00:23:12.480> turn<00:23:12.659> to<00:23:12.840> centralized 00:23:13.370 --> 00:23:13.380 align:start position:0% of users they will turn to centralized 00:23:13.380 --> 00:23:16.250 align:start position:0% of users they will turn to centralized Solutions<00:23:13.740> I<00:23:14.520> mean<00:23:14.700> most<00:23:15.419> of<00:23:15.600> us<00:23:15.720> in<00:23:16.020> this<00:23:16.140> room 00:23:16.250 --> 00:23:16.260 align:start position:0% Solutions I mean most of us in this room 00:23:16.260 --> 00:23:18.890 align:start position:0% Solutions I mean most of us in this room we<00:23:16.440> are<00:23:16.559> using<00:23:16.740> it<00:23:17.520> already<00:23:17.760> a<00:23:18.000> coinbase<00:23:18.419> or<00:23:18.720> an 00:23:18.890 --> 00:23:18.900 align:start position:0% we are using it already a coinbase or an 00:23:18.900 --> 00:23:21.049 align:start position:0% we are using it already a coinbase or an FTX<00:23:19.380> or<00:23:19.620> you<00:23:19.860> know<00:23:19.980> binance<00:23:20.400> account<00:23:20.640> because 00:23:21.049 --> 00:23:21.059 align:start position:0% FTX or you know binance account because 00:23:21.059 --> 00:23:23.570 align:start position:0% FTX or you know binance account because yes<00:23:21.419> it's<00:23:21.659> simpler<00:23:22.140> so<00:23:22.679> can<00:23:22.919> we<00:23:23.100> really<00:23:23.340> expect 00:23:23.570 --> 00:23:23.580 align:start position:0% yes it's simpler so can we really expect 00:23:23.580 --> 00:23:26.210 align:start position:0% yes it's simpler so can we really expect the<00:23:24.000> next<00:23:24.120> wave<00:23:24.360> of<00:23:24.539> billion<00:23:24.900> users<00:23:25.260> to<00:23:25.799> not<00:23:25.980> do 00:23:26.210 --> 00:23:26.220 align:start position:0% the next wave of billion users to not do 00:23:26.220 --> 00:23:28.310 align:start position:0% the next wave of billion users to not do that<00:23:26.340> of<00:23:26.880> course<00:23:27.059> they<00:23:27.299> will<00:23:27.480> so<00:23:27.840> we<00:23:28.020> need<00:23:28.140> to 00:23:28.310 --> 00:23:28.320 align:start position:0% that of course they will so we need to 00:23:28.320 --> 00:23:30.409 align:start position:0% that of course they will so we need to find<00:23:28.919> a<00:23:29.100> way<00:23:29.220> to<00:23:29.400> build<00:23:29.580> a<00:23:29.760> user<00:23:30.120> experience 00:23:30.409 --> 00:23:30.419 align:start position:0% find a way to build a user experience 00:23:30.419 --> 00:23:32.210 align:start position:0% find a way to build a user experience that<00:23:30.720> is<00:23:30.900> on<00:23:31.080> power<00:23:31.260> with<00:23:31.559> these<00:23:31.799> centralized 00:23:32.210 --> 00:23:32.220 align:start position:0% that is on power with these centralized 00:23:32.220 --> 00:23:33.590 align:start position:0% that is on power with these centralized exchanges<00:23:32.700> so<00:23:32.940> that<00:23:33.059> would<00:23:33.240> be<00:23:33.360> big 00:23:33.590 --> 00:23:33.600 align:start position:0% exchanges so that would be big 00:23:33.600 --> 00:23:35.570 align:start position:0% exchanges so that would be big certificate<00:23:34.260> study<00:23:34.500> at<00:23:34.799> the<00:23:34.919> heart<00:23:35.100> of<00:23:35.400> every 00:23:35.570 --> 00:23:35.580 align:start position:0% certificate study at the heart of every 00:23:35.580 --> 00:23:37.549 align:start position:0% certificate study at the heart of every interaction<00:23:36.000> on<00:23:36.179> the<00:23:36.299> blockchain<00:23:36.659> and<00:23:37.380> and 00:23:37.549 --> 00:23:37.559 align:start position:0% interaction on the blockchain and and 00:23:37.559 --> 00:23:39.470 align:start position:0% interaction on the blockchain and and I'm<00:23:38.340> personally<00:23:38.700> convinced<00:23:39.179> that<00:23:39.299> only 00:23:39.470 --> 00:23:39.480 align:start position:0% I'm personally convinced that only 00:23:39.480 --> 00:23:41.630 align:start position:0% I'm personally convinced that only account<00:23:39.720> abstraction<00:23:40.200> can<00:23:40.500> do<00:23:40.679> that 00:23:41.630 --> 00:23:41.640 align:start position:0% account abstraction can do that 00:23:41.640 --> 00:23:44.390 align:start position:0% account abstraction can do that so<00:23:42.539> let's<00:23:43.260> make<00:23:43.500> it<00:23:43.620> happen<00:23:43.799> and<00:23:44.039> build<00:23:44.220> that 00:23:44.390 --> 00:23:44.400 align:start position:0% so let's make it happen and build that 00:23:44.400 --> 00:23:47.270 align:start position:0% so let's make it happen and build that together<00:23:44.580> thank<00:23:45.419> you<00:23:45.620> Julian<00:23:46.620> thank<00:23:47.100> you<00:23:47.220> very 00:23:47.270 --> 00:23:47.280 align:start position:0% together thank you Julian thank you very 00:23:47.280 --> 00:23:49.789 align:start position:0% together thank you Julian thank you very much<00:23:47.460> for<00:23:47.760> this<00:23:48.000> I<00:23:48.720> also<00:23:49.020> was<00:23:49.140> looking<00:23:49.380> at<00:23:49.620> your 00:23:49.789 --> 00:23:49.799 align:start position:0% much for this I also was looking at your 00:23:49.799 --> 00:23:51.770 align:start position:0% much for this I also was looking at your twittering<00:23:50.280> jokes<00:23:50.880> actually<00:23:51.179> wrote<00:23:51.600> that 00:23:51.770 --> 00:23:51.780 align:start position:0% twittering jokes actually wrote that 00:23:51.780 --> 00:23:54.049 align:start position:0% twittering jokes actually wrote that what<00:23:52.200> the<00:23:52.500> is<00:23:52.679> account<00:23:52.860> extraction<00:23:53.400> so 00:23:54.049 --> 00:23:54.059 align:start position:0% what the is account extraction so 00:23:54.059 --> 00:23:55.370 align:start position:0% what the is account extraction so that's<00:23:54.240> super<00:23:54.419> cool<00:23:54.659> if<00:23:54.900> you<00:23:55.020> want<00:23:55.140> to<00:23:55.200> read 00:23:55.370 --> 00:23:55.380 align:start position:0% that's super cool if you want to read 00:23:55.380 --> 00:23:57.770 align:start position:0% that's super cool if you want to read more<00:23:55.559> about<00:23:55.740> it<00:23:55.980> yes<00:23:56.520> just<00:23:57.000> if<00:23:57.360> you<00:23:57.480> if<00:23:57.659> you 00:23:57.770 --> 00:23:57.780 align:start position:0% more about it yes just if you if you 00:23:57.780 --> 00:23:59.510 align:start position:0% more about it yes just if you if you want<00:23:57.840> to<00:23:57.960> know<00:23:58.080> more<00:23:58.200> there's<00:23:58.799> a<00:23:58.980> three-part 00:23:59.510 --> 00:23:59.520 align:start position:0% want to know more there's a three-part 00:23:59.520 --> 00:24:01.010 align:start position:0% want to know more there's a three-part series<00:23:59.760> called<00:24:00.059> what<00:24:00.299> the<00:24:00.539> is<00:24:00.720> a<00:24:00.840> con 00:24:01.010 --> 00:24:01.020 align:start position:0% series called what the is a con 00:24:01.020 --> 00:24:02.510 align:start position:0% series called what the is a con abstraction<00:24:01.440> you<00:24:01.799> can<00:24:01.860> find<00:24:02.039> it<00:24:02.220> on<00:24:02.400> Twitter 00:24:02.510 --> 00:24:02.520 align:start position:0% abstraction you can find it on Twitter 00:24:02.520 --> 00:24:04.669 align:start position:0% abstraction you can find it on Twitter and<00:24:03.419> also<00:24:03.659> if<00:24:03.780> you're<00:24:03.960> interested<00:24:04.320> we<00:24:04.559> are 00:24:04.669 --> 00:24:04.679 align:start position:0% and also if you're interested we are 00:24:04.679 --> 00:24:06.110 align:start position:0% and also if you're interested we are actually<00:24:04.799> having<00:24:05.039> a<00:24:05.280> panel<00:24:05.580> on<00:24:05.760> this<00:24:05.940> main 00:24:06.110 --> 00:24:06.120 align:start position:0% actually having a panel on this main 00:24:06.120 --> 00:24:09.710 align:start position:0% actually having a panel on this main stage<00:24:06.480> at<00:24:06.960> 5<00:24:07.200> pm<00:24:07.559> today<00:24:07.799> with<00:24:08.640> vitalik<00:24:09.299> Dan 00:24:09.710 --> 00:24:09.720 align:start position:0% stage at 5 pm today with vitalik Dan 00:24:09.720 --> 00:24:11.990 align:start position:0% stage at 5 pm today with vitalik Dan Finley<00:24:10.140> from<00:24:10.320> metamask<00:24:10.860> and<00:24:11.520> then<00:24:11.640> you<00:24:11.880> have 00:24:11.990 --> 00:24:12.000 align:start position:0% Finley from metamask and then you have 00:24:12.000 --> 00:24:14.930 align:start position:0% Finley from metamask and then you have which<00:24:12.240> has<00:24:12.360> been<00:24:12.539> pushing<00:24:12.840> for<00:24:13.100> eip4337<00:24:14.100> so<00:24:14.700> if 00:24:14.930 --> 00:24:14.940 align:start position:0% which has been pushing for eip4337 so if 00:24:14.940 --> 00:24:16.010 align:start position:0% which has been pushing for eip4337 so if you<00:24:15.059> want<00:24:15.179> to<00:24:15.299> know<00:24:15.419> more<00:24:15.539> please<00:24:15.840> stick 00:24:16.010 --> 00:24:16.020 align:start position:0% you want to know more please stick 00:24:16.020 --> 00:24:19.430 align:start position:0% you want to know more please stick around<00:24:16.200> and<00:24:16.559> come<00:24:16.919> at<00:24:17.280> 5<00:24:17.460> PM<00:24:17.700> perfect<00:24:18.440> Jillian 00:24:19.430 --> 00:24:19.440 align:start position:0% around and come at 5 PM perfect Jillian 00:24:19.440 --> 00:24:20.990 align:start position:0% around and come at 5 PM perfect Jillian thank<00:24:19.679> you<00:24:19.799> very<00:24:19.860> much<00:24:20.039> co-founder<00:24:20.700> of<00:24:20.820> Art 00:24:20.990 --> 00:24:21.000 align:start position:0% thank you very much co-founder of Art 00:24:21.000 --> 00:24:22.850 align:start position:0% thank you very much co-founder of Art and<00:24:21.360> giving<00:24:21.840> a<00:24:22.080> round<00:24:22.200> of<00:24:22.380> applause<00:24:22.679> again 00:24:22.850 --> 00:24:22.860 align:start position:0% and giving a round of applause again 00:24:22.860 --> 00:24:24.470 align:start position:0% and giving a round of applause again please<00:24:23.159> thank<00:24:23.340> you<00:24:23.520> Julian<00:24:24.000> thank<00:24:24.299> you<00:24:24.360> very 00:24:24.470 --> 00:24:24.480 align:start position:0% please thank you Julian thank you very 00:24:24.480 --> 00:24:26.659 align:start position:0% please thank you Julian thank you very much