WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:11.230 align:start position:0% [Music] 00:00:11.230 --> 00:00:11.240 align:start position:0% 00:00:11.240 --> 00:00:12.190 align:start position:0% thank 00:00:12.190 --> 00:00:12.200 align:start position:0% thank 00:00:12.200 --> 00:00:15.350 align:start position:0% thank you<00:00:13.200> thank<00:00:13.360> you<00:00:13.599> thank<00:00:13.759> you<00:00:14.559> and<00:00:14.839> thanks<00:00:15.040> to<00:00:15.200> my 00:00:15.350 --> 00:00:15.360 align:start position:0% you thank you thank you and thanks to my 00:00:15.360 --> 00:00:17.029 align:start position:0% you thank you thank you and thanks to my fellow<00:00:15.679> Portuguese<00:00:16.199> for<00:00:16.440> pronouncing<00:00:16.880> my 00:00:17.029 --> 00:00:17.039 align:start position:0% fellow Portuguese for pronouncing my 00:00:17.039 --> 00:00:19.710 align:start position:0% fellow Portuguese for pronouncing my name<00:00:17.320> correctly<00:00:17.800> for<00:00:17.960> the<00:00:18.119> first<00:00:18.400> time<00:00:18.720> in<00:00:18.840> a 00:00:19.710 --> 00:00:19.720 align:start position:0% name correctly for the first time in a 00:00:19.720 --> 00:00:21.950 align:start position:0% name correctly for the first time in a conference<00:00:20.720> so<00:00:20.960> as<00:00:21.039> you<00:00:21.199> heard<00:00:21.480> my<00:00:21.640> name<00:00:21.800> is 00:00:21.950 --> 00:00:21.960 align:start position:0% conference so as you heard my name is 00:00:21.960 --> 00:00:24.029 align:start position:0% conference so as you heard my name is Pedro<00:00:22.320> Gom<00:00:22.760> I'm<00:00:22.880> the<00:00:23.000> founder<00:00:23.320> and<00:00:23.560> director 00:00:24.029 --> 00:00:24.039 align:start position:0% Pedro Gom I'm the founder and director 00:00:24.039 --> 00:00:26.029 align:start position:0% Pedro Gom I'm the founder and director of<00:00:24.160> the<00:00:24.279> Walla<00:00:24.560> connect<00:00:24.840> foundation<00:00:25.640> and<00:00:25.800> I'm 00:00:26.029 --> 00:00:26.039 align:start position:0% of the Walla connect foundation and I'm 00:00:26.039 --> 00:00:28.189 align:start position:0% of the Walla connect foundation and I'm really<00:00:26.320> thrilled<00:00:26.760> to<00:00:26.920> be<00:00:27.519> talking<00:00:27.840> to<00:00:28.000> you 00:00:28.189 --> 00:00:28.199 align:start position:0% really thrilled to be talking to you 00:00:28.199 --> 00:00:30.509 align:start position:0% really thrilled to be talking to you more<00:00:28.679> about<00:00:28.960> the<00:00:29.080> future<00:00:29.400> of<00:00:29.599> Walla 00:00:30.509 --> 00:00:30.519 align:start position:0% more about the future of Walla 00:00:30.519 --> 00:00:32.790 align:start position:0% more about the future of Walla how<00:00:30.759> we're<00:00:30.920> going<00:00:31.039> to<00:00:31.279> change<00:00:31.679> the<00:00:31.920> experience 00:00:32.790 --> 00:00:32.800 align:start position:0% how we're going to change the experience 00:00:32.800 --> 00:00:35.790 align:start position:0% how we're going to change the experience for<00:00:33.040> users<00:00:33.800> and<00:00:34.079> most<00:00:34.440> importantly<00:00:35.440> how<00:00:35.600> we're 00:00:35.790 --> 00:00:35.800 align:start position:0% for users and most importantly how we're 00:00:35.800 --> 00:00:38.910 align:start position:0% for users and most importantly how we're going<00:00:35.920> to<00:00:36.520> have<00:00:36.840> Smart<00:00:37.280> accounts<00:00:38.200> use<00:00:38.559> Smart 00:00:38.910 --> 00:00:38.920 align:start position:0% going to have Smart accounts use Smart 00:00:38.920 --> 00:00:41.830 align:start position:0% going to have Smart accounts use Smart sessions<00:00:39.600> and<00:00:39.920> why<00:00:40.879> why<00:00:41.000> do<00:00:41.200> they<00:00:41.360> even<00:00:41.600> need 00:00:41.830 --> 00:00:41.840 align:start position:0% sessions and why why do they even need 00:00:41.840 --> 00:00:44.950 align:start position:0% sessions and why why do they even need smart<00:00:42.160> sessions<00:00:43.039> obviously<00:00:44.000> I<00:00:44.079> don't<00:00:44.440> expect 00:00:44.950 --> 00:00:44.960 align:start position:0% smart sessions obviously I don't expect 00:00:44.960 --> 00:00:47.189 align:start position:0% smart sessions obviously I don't expect people<00:00:45.239> to<00:00:45.440> know<00:00:45.879> what<00:00:46.079> smart<00:00:46.360> accounts<00:00:46.680> are 00:00:47.189 --> 00:00:47.199 align:start position:0% people to know what smart accounts are 00:00:47.199 --> 00:00:49.430 align:start position:0% people to know what smart accounts are or<00:00:47.399> what<00:00:47.559> smart<00:00:47.879> sessions<00:00:48.320> are<00:00:49.000> and<00:00:49.120> I<00:00:49.239> feel 00:00:49.430 --> 00:00:49.440 align:start position:0% or what smart sessions are and I feel 00:00:49.440 --> 00:00:51.709 align:start position:0% or what smart sessions are and I feel like<00:00:49.600> we<00:00:49.719> need<00:00:49.879> to<00:00:50.079> kind<00:00:50.160> of<00:00:50.320> go<00:00:50.520> on<00:00:50.640> a<00:00:50.840> journey 00:00:51.709 --> 00:00:51.719 align:start position:0% like we need to kind of go on a journey 00:00:51.719 --> 00:00:54.590 align:start position:0% like we need to kind of go on a journey why<00:00:52.079> wallets<00:00:52.600> work<00:00:52.840> in<00:00:53.039> the<00:00:53.160> way<00:00:53.359> they<00:00:53.480> are<00:00:54.359> so 00:00:54.590 --> 00:00:54.600 align:start position:0% why wallets work in the way they are so 00:00:54.600 --> 00:00:56.670 align:start position:0% why wallets work in the way they are so let's<00:00:54.840> start<00:00:55.199> with<00:00:55.399> breaking<00:00:55.760> down<00:00:55.920> the<00:00:56.039> lingo 00:00:56.670 --> 00:00:56.680 align:start position:0% let's start with breaking down the lingo 00:00:56.680 --> 00:00:58.750 align:start position:0% let's start with breaking down the lingo like<00:00:56.879> when<00:00:57.000> you<00:00:57.160> think<00:00:57.440> about<00:00:57.840> wallets<00:00:58.559> you 00:00:58.750 --> 00:00:58.760 align:start position:0% like when you think about wallets you 00:00:58.760 --> 00:01:01.189 align:start position:0% like when you think about wallets you might<00:00:59.000> think<00:00:59.359> about<00:01:00.160> the<00:01:00.280> leather<00:01:00.640> wallets<00:01:01.039> in 00:01:01.189 --> 00:01:01.199 align:start position:0% might think about the leather wallets in 00:01:01.199 --> 00:01:03.549 align:start position:0% might think about the leather wallets in your<00:01:01.440> pockets<00:01:02.079> or<00:01:02.640> you<00:01:02.800> might<00:01:03.000> think<00:01:03.320> about 00:01:03.549 --> 00:01:03.559 align:start position:0% your pockets or you might think about 00:01:03.559 --> 00:01:06.230 align:start position:0% your pockets or you might think about the<00:01:03.719> digital<00:01:04.159> wallet<00:01:04.519> in<00:01:04.680> your<00:01:04.960> phone<00:01:05.960> and<00:01:06.080> you 00:01:06.230 --> 00:01:06.240 align:start position:0% the digital wallet in your phone and you 00:01:06.240 --> 00:01:09.149 align:start position:0% the digital wallet in your phone and you might<00:01:06.439> even<00:01:06.720> think<00:01:07.040> about<00:01:07.640> metamask<00:01:08.600> rainbow 00:01:09.149 --> 00:01:09.159 align:start position:0% might even think about metamask rainbow 00:01:09.159 --> 00:01:11.789 align:start position:0% might even think about metamask rainbow zarion<00:01:09.799> trust<00:01:10.200> wallet<00:01:10.720> all<00:01:10.840> of<00:01:11.080> these 00:01:11.789 --> 00:01:11.799 align:start position:0% zarion trust wallet all of these 00:01:11.799 --> 00:01:14.429 align:start position:0% zarion trust wallet all of these blockchain<00:01:12.400> wallets<00:01:13.000> but<00:01:13.560> what<00:01:13.759> makes<00:01:14.119> them 00:01:14.429 --> 00:01:14.439 align:start position:0% blockchain wallets but what makes them 00:01:14.439 --> 00:01:17.230 align:start position:0% blockchain wallets but what makes them so<00:01:14.840> different<00:01:15.400> as<00:01:15.560> a<00:01:15.720> blockchain<00:01:16.200> wallet<00:01:17.080> it 00:01:17.230 --> 00:01:17.240 align:start position:0% so different as a blockchain wallet it 00:01:17.240 --> 00:01:19.749 align:start position:0% so different as a blockchain wallet it really<00:01:17.560> comes<00:01:17.840> down<00:01:18.000> to<00:01:18.200> this<00:01:18.439> experience<00:01:19.080> of 00:01:19.749 --> 00:01:19.759 align:start position:0% really comes down to this experience of 00:01:19.759 --> 00:01:21.950 align:start position:0% really comes down to this experience of before<00:01:20.200> we<00:01:20.360> used<00:01:20.640> to<00:01:21.040> log<00:01:21.320> in<00:01:21.640> into 00:01:21.950 --> 00:01:21.960 align:start position:0% before we used to log in into 00:01:21.960 --> 00:01:25.990 align:start position:0% before we used to log in into applications<00:01:22.680> and<00:01:22.840> now<00:01:23.079> we<00:01:23.759> connect<00:01:24.799> but<00:01:25.799> it's 00:01:25.990 --> 00:01:26.000 align:start position:0% applications and now we connect but it's 00:01:26.000 --> 00:01:28.510 align:start position:0% applications and now we connect but it's not<00:01:26.240> just<00:01:26.439> the<00:01:26.720> change<00:01:27.159> of<00:01:27.439> the<00:01:27.600> word<00:01:28.079> itself 00:01:28.510 --> 00:01:28.520 align:start position:0% not just the change of the word itself 00:01:28.520 --> 00:01:31.190 align:start position:0% not just the change of the word itself it<00:01:28.720> really<00:01:29.000> changes<00:01:29.759> the<00:01:30.000> the<00:01:30.200> infrastructure 00:01:31.190 --> 00:01:31.200 align:start position:0% it really changes the the infrastructure 00:01:31.200 --> 00:01:34.069 align:start position:0% it really changes the the infrastructure and<00:01:31.400> the<00:01:31.600> technology<00:01:32.240> behind<00:01:32.560> it<00:01:33.240> that 00:01:34.069 --> 00:01:34.079 align:start position:0% and the technology behind it that 00:01:34.079 --> 00:01:36.789 align:start position:0% and the technology behind it that completely<00:01:35.280> revolutionized<00:01:36.280> what<00:01:36.439> is<00:01:36.680> going 00:01:36.789 --> 00:01:36.799 align:start position:0% completely revolutionized what is going 00:01:36.799 --> 00:01:39.429 align:start position:0% completely revolutionized what is going to<00:01:37.000> be<00:01:37.560> the<00:01:37.880> future<00:01:38.320> of<00:01:38.479> the<00:01:38.640> internet<00:01:39.159> and<00:01:39.320> all 00:01:39.429 --> 00:01:39.439 align:start position:0% to be the future of the internet and all 00:01:39.439 --> 00:01:42.030 align:start position:0% to be the future of the internet and all of<00:01:39.560> these<00:01:40.000> applications<00:01:41.000> so<00:01:41.360> you<00:01:41.479> see<00:01:41.759> all<00:01:41.920> of 00:01:42.030 --> 00:01:42.040 align:start position:0% of these applications so you see all of 00:01:42.040 --> 00:01:44.310 align:start position:0% of these applications so you see all of these<00:01:42.320> terms<00:01:42.680> throwing<00:01:43.200> around<00:01:43.720> like<00:01:43.960> dabs 00:01:44.310 --> 00:01:44.320 align:start position:0% these terms throwing around like dabs 00:01:44.320 --> 00:01:46.550 align:start position:0% these terms throwing around like dabs and<00:01:44.520> wallets<00:01:44.840> and<00:01:45.000> smart<00:01:45.320> sessions<00:01:46.079> but<00:01:46.439> it 00:01:46.550 --> 00:01:46.560 align:start position:0% and wallets and smart sessions but it 00:01:46.560 --> 00:01:48.830 align:start position:0% and wallets and smart sessions but it all<00:01:46.719> comes<00:01:46.960> down<00:01:47.159> to<00:01:47.640> authentication<00:01:48.640> like 00:01:48.830 --> 00:01:48.840 align:start position:0% all comes down to authentication like 00:01:48.840 --> 00:01:50.990 align:start position:0% all comes down to authentication like authentication<00:01:49.600> means<00:01:50.000> it's<00:01:50.240> the<00:01:50.439> process<00:01:50.799> of 00:01:50.990 --> 00:01:51.000 align:start position:0% authentication means it's the process of 00:01:51.000 --> 00:01:54.670 align:start position:0% authentication means it's the process of proving<00:01:51.560> who<00:01:51.759> you<00:01:51.920> are<00:01:52.320> and<00:01:52.600> what<00:01:52.799> you<00:01:53.079> own<00:01:54.079> and 00:01:54.670 --> 00:01:54.680 align:start position:0% proving who you are and what you own and 00:01:54.680 --> 00:01:56.709 align:start position:0% proving who you are and what you own and in<00:01:54.880> a<00:01:55.040> short<00:01:55.360> word<00:01:55.680> when<00:01:56.000> user<00:01:56.360> sees 00:01:56.709 --> 00:01:56.719 align:start position:0% in a short word when user sees 00:01:56.719 --> 00:01:58.590 align:start position:0% in a short word when user sees authentication<00:01:57.560> it<00:01:57.680> just<00:01:57.840> means<00:01:58.240> that<00:01:58.439> you 00:01:58.590 --> 00:01:58.600 align:start position:0% authentication it just means that you 00:01:58.600 --> 00:02:01.429 align:start position:0% authentication it just means that you want<00:01:58.920> to<00:01:59.240> get<00:01:59.399> in<00:01:59.719> like<00:02:00.119> let<00:02:00.320> me<00:02:00.560> in<00:02:01.000> I<00:02:01.119> want<00:02:01.240> to 00:02:01.429 --> 00:02:01.439 align:start position:0% want to get in like let me in I want to 00:02:01.439 --> 00:02:03.630 align:start position:0% want to get in like let me in I want to get<00:02:01.600> into<00:02:01.840> the<00:02:02.039> application<00:02:03.039> that<00:02:03.159> I<00:02:03.320> don't 00:02:03.630 --> 00:02:03.640 align:start position:0% get into the application that I don't 00:02:03.640 --> 00:02:06.029 align:start position:0% get into the application that I don't really<00:02:03.960> care<00:02:04.320> and<00:02:04.880> if<00:02:05.000> you<00:02:05.159> don't<00:02:05.479> really<00:02:05.759> care 00:02:06.029 --> 00:02:06.039 align:start position:0% really care and if you don't really care 00:02:06.039 --> 00:02:07.670 align:start position:0% really care and if you don't really care you<00:02:06.240> really<00:02:06.439> want<00:02:06.600> to<00:02:06.719> make<00:02:06.880> sure<00:02:07.079> that<00:02:07.240> you<00:02:07.399> do 00:02:07.670 --> 00:02:07.680 align:start position:0% you really want to make sure that you do 00:02:07.680 --> 00:02:09.550 align:start position:0% you really want to make sure that you do as<00:02:07.920> less<00:02:08.119> clicks<00:02:08.440> as<00:02:08.640> possible<00:02:09.039> like<00:02:09.280> less 00:02:09.550 --> 00:02:09.560 align:start position:0% as less clicks as possible like less 00:02:09.560 --> 00:02:12.110 align:start position:0% as less clicks as possible like less clicks<00:02:09.879> is<00:02:10.080> more<00:02:10.800> this<00:02:10.920> is<00:02:11.039> our<00:02:11.319> mission<00:02:11.879> for 00:02:12.110 --> 00:02:12.120 align:start position:0% clicks is more this is our mission for 00:02:12.120 --> 00:02:14.910 align:start position:0% clicks is more this is our mission for building<00:02:12.480> a<00:02:13.000> great<00:02:13.319> better<00:02:13.599> user<00:02:14.040> experience 00:02:14.910 --> 00:02:14.920 align:start position:0% building a great better user experience 00:02:14.920 --> 00:02:17.190 align:start position:0% building a great better user experience a<00:02:15.120> wallet<00:02:15.480> is<00:02:15.640> better<00:02:16.160> the<00:02:16.360> less<00:02:16.640> you<00:02:16.840> have<00:02:17.000> to 00:02:17.190 --> 00:02:17.200 align:start position:0% a wallet is better the less you have to 00:02:17.200 --> 00:02:20.270 align:start position:0% a wallet is better the less you have to click<00:02:17.640> around<00:02:18.280> but<00:02:18.599> a<00:02:18.800> wallet<00:02:19.160> is<00:02:19.360> also<00:02:20.160> a 00:02:20.270 --> 00:02:20.280 align:start position:0% click around but a wallet is also a 00:02:20.280 --> 00:02:22.589 align:start position:0% click around but a wallet is also a little<00:02:20.560> bit<00:02:21.000> more<00:02:21.319> insecure<00:02:22.040> if<00:02:22.160> you<00:02:22.319> don't 00:02:22.589 --> 00:02:22.599 align:start position:0% little bit more insecure if you don't 00:02:22.599 --> 00:02:24.670 align:start position:0% little bit more insecure if you don't approve<00:02:23.000> everything<00:02:23.560> and<00:02:23.760> that's<00:02:24.080> where<00:02:24.480> the 00:02:24.670 --> 00:02:24.680 align:start position:0% approve everything and that's where the 00:02:24.680 --> 00:02:26.990 align:start position:0% approve everything and that's where the tricky<00:02:25.080> part<00:02:25.280> of<00:02:25.519> balancing<00:02:26.120> convenience<00:02:26.599> and 00:02:26.990 --> 00:02:27.000 align:start position:0% tricky part of balancing convenience and 00:02:27.000 --> 00:02:29.949 align:start position:0% tricky part of balancing convenience and security<00:02:28.000> so<00:02:28.360> why<00:02:28.480> is<00:02:28.680> web<00:02:28.920> 3<00:02:29.200> different<00:02:29.640> like 00:02:29.949 --> 00:02:29.959 align:start position:0% security so why is web 3 different like 00:02:29.959 --> 00:02:31.750 align:start position:0% security so why is web 3 different like we<00:02:30.080> talked<00:02:30.480> that<00:02:30.760> there<00:02:30.879> are<00:02:31.360> physical 00:02:31.750 --> 00:02:31.760 align:start position:0% we talked that there are physical 00:02:31.760 --> 00:02:33.670 align:start position:0% we talked that there are physical leather<00:02:32.120> wallets<00:02:32.879> uh<00:02:33.040> there<00:02:33.120> are<00:02:33.319> digital 00:02:33.670 --> 00:02:33.680 align:start position:0% leather wallets uh there are digital 00:02:33.680 --> 00:02:36.110 align:start position:0% leather wallets uh there are digital wallets<00:02:34.000> in<00:02:34.120> your<00:02:34.280> phones<00:02:35.160> uh<00:02:35.319> why<00:02:35.519> are<00:02:35.800> web 00:02:36.110 --> 00:02:36.120 align:start position:0% wallets in your phones uh why are web 00:02:36.120 --> 00:02:38.589 align:start position:0% wallets in your phones uh why are web three<00:02:36.440> wallets<00:02:36.920> or<00:02:37.400> blockchain<00:02:37.920> wallets<00:02:38.319> any 00:02:38.589 --> 00:02:38.599 align:start position:0% three wallets or blockchain wallets any 00:02:38.599 --> 00:02:41.229 align:start position:0% three wallets or blockchain wallets any different<00:02:39.599> I<00:02:39.760> like<00:02:39.920> to<00:02:40.080> always<00:02:40.360> bring 00:02:41.229 --> 00:02:41.239 align:start position:0% different I like to always bring 00:02:41.239 --> 00:02:43.790 align:start position:0% different I like to always bring probably<00:02:41.920> one<00:02:42.040> of<00:02:42.200> my<00:02:42.400> oldest<00:02:42.920> diagrams<00:02:43.599> I've 00:02:43.790 --> 00:02:43.800 align:start position:0% probably one of my oldest diagrams I've 00:02:43.800 --> 00:02:45.790 align:start position:0% probably one of my oldest diagrams I've been<00:02:44.040> presenting<00:02:44.480> this<00:02:44.680> diagram<00:02:45.120> for<00:02:45.560> more 00:02:45.790 --> 00:02:45.800 align:start position:0% been presenting this diagram for more 00:02:45.800 --> 00:02:49.390 align:start position:0% been presenting this diagram for more than<00:02:46.040> 5<00:02:46.360> years<00:02:47.319> and<00:02:47.760> this<00:02:48.000> kind<00:02:48.159> of<00:02:48.400> explains 00:02:49.390 --> 00:02:49.400 align:start position:0% than 5 years and this kind of explains 00:02:49.400 --> 00:02:51.830 align:start position:0% than 5 years and this kind of explains uh<00:02:49.560> very<00:02:49.800> simply<00:02:50.360> how<00:02:50.640> the<00:02:51.200> infrastructure 00:02:51.830 --> 00:02:51.840 align:start position:0% uh very simply how the infrastructure 00:02:51.840 --> 00:02:54.470 align:start position:0% uh very simply how the infrastructure had<00:02:52.000> changed<00:02:52.360> from<00:02:52.560> web<00:02:52.760> 2<00:02:52.959> to<00:02:53.120> web<00:02:53.360> 3<00:02:54.159> before 00:02:54.470 --> 00:02:54.480 align:start position:0% had changed from web 2 to web 3 before 00:02:54.480 --> 00:02:57.350 align:start position:0% had changed from web 2 to web 3 before we<00:02:54.680> had<00:02:54.879> a<00:02:55.080> server<00:02:55.840> that<00:02:56.280> was<00:02:56.560> powering<00:02:56.959> your 00:02:57.350 --> 00:02:57.360 align:start position:0% we had a server that was powering your 00:02:57.360 --> 00:03:01.030 align:start position:0% we had a server that was powering your application<00:02:58.360> but<00:02:58.599> these<00:02:58.840> servers<00:03:00.120> um<00:03:00.400> inside 00:03:01.030 --> 00:03:01.040 align:start position:0% application but these servers um inside 00:03:01.040 --> 00:03:03.710 align:start position:0% application but these servers um inside have<00:03:01.319> this<00:03:01.840> module<00:03:02.640> that's<00:03:02.920> called 00:03:03.710 --> 00:03:03.720 align:start position:0% have this module that's called 00:03:03.720 --> 00:03:05.750 align:start position:0% have this module that's called authentication<00:03:04.720> um<00:03:04.879> some<00:03:05.080> people<00:03:05.360> even<00:03:05.599> call 00:03:05.750 --> 00:03:05.760 align:start position:0% authentication um some people even call 00:03:05.760 --> 00:03:07.589 align:start position:0% authentication um some people even call it<00:03:06.000> identity<00:03:06.640> but<00:03:06.760> this<00:03:06.879> is<00:03:07.040> basically<00:03:07.440> what 00:03:07.589 --> 00:03:07.599 align:start position:0% it identity but this is basically what 00:03:07.599 --> 00:03:09.750 align:start position:0% it identity but this is basically what your<00:03:07.879> login<00:03:08.239> looks<00:03:08.519> like<00:03:08.720> your<00:03:08.959> login<00:03:09.440> lives 00:03:09.750 --> 00:03:09.760 align:start position:0% your login looks like your login lives 00:03:09.760 --> 00:03:12.550 align:start position:0% your login looks like your login lives in<00:03:09.920> the<00:03:10.120> server<00:03:11.080> and<00:03:11.280> blockchain<00:03:11.959> obviously 00:03:12.550 --> 00:03:12.560 align:start position:0% in the server and blockchain obviously 00:03:12.560 --> 00:03:14.670 align:start position:0% in the server and blockchain obviously does<00:03:12.799> not<00:03:13.120> have<00:03:13.280> a<00:03:13.480> server<00:03:14.080> and<00:03:14.239> you<00:03:14.400> can't 00:03:14.670 --> 00:03:14.680 align:start position:0% does not have a server and you can't 00:03:14.680 --> 00:03:17.190 align:start position:0% does not have a server and you can't just<00:03:14.840> put<00:03:15.080> login<00:03:15.440> in<00:03:15.640> there<00:03:16.400> so<00:03:16.799> it<00:03:16.920> was 00:03:17.190 --> 00:03:17.200 align:start position:0% just put login in there so it was 00:03:17.200 --> 00:03:19.509 align:start position:0% just put login in there so it was cleverly<00:03:17.760> designed<00:03:18.319> that<00:03:18.519> we<00:03:18.720> put<00:03:19.000> the<00:03:19.159> wallet 00:03:19.509 --> 00:03:19.519 align:start position:0% cleverly designed that we put the wallet 00:03:19.519 --> 00:03:21.830 align:start position:0% cleverly designed that we put the wallet on<00:03:19.720> the<00:03:19.879> user<00:03:20.400> side<00:03:20.720> so<00:03:21.080> as<00:03:21.159> you<00:03:21.280> can<00:03:21.440> see<00:03:21.720> the 00:03:21.830 --> 00:03:21.840 align:start position:0% on the user side so as you can see the 00:03:21.840 --> 00:03:23.910 align:start position:0% on the user side so as you can see the wallet<00:03:22.159> sits<00:03:22.560> on<00:03:22.720> the<00:03:22.879> bottom<00:03:23.280> no<00:03:23.440> longer<00:03:23.799> in 00:03:23.910 --> 00:03:23.920 align:start position:0% wallet sits on the bottom no longer in 00:03:23.920 --> 00:03:26.229 align:start position:0% wallet sits on the bottom no longer in the<00:03:24.040> blockchain<00:03:25.040> and<00:03:25.280> that<00:03:25.400> means<00:03:25.720> that<00:03:25.920> now 00:03:26.229 --> 00:03:26.239 align:start position:0% the blockchain and that means that now 00:03:26.239 --> 00:03:29.390 align:start position:0% the blockchain and that means that now the<00:03:26.480> wallet<00:03:27.440> is<00:03:27.959> your<00:03:28.280> authentication<00:03:29.280> which 00:03:29.390 --> 00:03:29.400 align:start position:0% the wallet is your authentication which 00:03:29.400 --> 00:03:31.990 align:start position:0% the wallet is your authentication which is<00:03:29.920> from<00:03:30.159> the<00:03:30.319> app<00:03:30.959> but<00:03:31.080> it<00:03:31.200> has<00:03:31.400> also<00:03:31.640> created 00:03:31.990 --> 00:03:32.000 align:start position:0% is from the app but it has also created 00:03:32.000 --> 00:03:33.750 align:start position:0% is from the app but it has also created the<00:03:32.080> inconvenience<00:03:32.720> of<00:03:32.959> now<00:03:33.319> every<00:03:33.480> time<00:03:33.640> you 00:03:33.750 --> 00:03:33.760 align:start position:0% the inconvenience of now every time you 00:03:33.760 --> 00:03:36.830 align:start position:0% the inconvenience of now every time you use<00:03:33.920> an<00:03:34.120> app<00:03:34.439> you<00:03:34.560> need<00:03:34.920> a<00:03:35.120> second<00:03:35.519> app<00:03:36.400> which 00:03:36.830 --> 00:03:36.840 align:start position:0% use an app you need a second app which 00:03:36.840 --> 00:03:38.910 align:start position:0% use an app you need a second app which you<00:03:37.000> know<00:03:37.319> it<00:03:37.480> does<00:03:37.760> have<00:03:37.879> its<00:03:38.120> advantages<00:03:38.799> but 00:03:38.910 --> 00:03:38.920 align:start position:0% you know it does have its advantages but 00:03:38.920 --> 00:03:41.550 align:start position:0% you know it does have its advantages but it<00:03:39.080> also<00:03:39.480> adds<00:03:40.120> more<00:03:40.439> clicks<00:03:41.040> which<00:03:41.159> is 00:03:41.550 --> 00:03:41.560 align:start position:0% it also adds more clicks which is 00:03:41.560 --> 00:03:44.070 align:start position:0% it also adds more clicks which is against<00:03:42.080> our<00:03:42.360> mission<00:03:42.840> here<00:03:43.519> so<00:03:43.879> when<00:03:43.959> you 00:03:44.070 --> 00:03:44.080 align:start position:0% against our mission here so when you 00:03:44.080 --> 00:03:46.030 align:start position:0% against our mission here so when you think<00:03:44.280> about<00:03:44.480> the<00:03:44.640> wallet<00:03:45.200> it<00:03:45.400> kind<00:03:45.519> of<00:03:45.760> comes 00:03:46.030 --> 00:03:46.040 align:start position:0% think about the wallet it kind of comes 00:03:46.040 --> 00:03:48.509 align:start position:0% think about the wallet it kind of comes down<00:03:46.239> to<00:03:46.840> like<00:03:47.239> credential<00:03:47.920> signing<00:03:48.239> in 00:03:48.509 --> 00:03:48.519 align:start position:0% down to like credential signing in 00:03:48.519 --> 00:03:50.670 align:start position:0% down to like credential signing in account<00:03:49.280> and<00:03:49.400> I<00:03:49.519> kind<00:03:49.599> of<00:03:49.760> try<00:03:49.959> to<00:03:50.120> break<00:03:50.400> down 00:03:50.670 --> 00:03:50.680 align:start position:0% account and I kind of try to break down 00:03:50.680 --> 00:03:53.509 align:start position:0% account and I kind of try to break down here<00:03:51.000> what<00:03:51.159> it<00:03:51.319> looks<00:03:52.239> for<00:03:52.519> different<00:03:52.840> wallets 00:03:53.509 --> 00:03:53.519 align:start position:0% here what it looks for different wallets 00:03:53.519 --> 00:03:55.030 align:start position:0% here what it looks for different wallets it<00:03:53.760> really<00:03:53.959> doesn't<00:03:54.280> matter<00:03:54.640> like<00:03:54.760> if<00:03:54.879> you 00:03:55.030 --> 00:03:55.040 align:start position:0% it really doesn't matter like if you 00:03:55.040 --> 00:03:57.069 align:start position:0% it really doesn't matter like if you have<00:03:55.200> a<00:03:55.360> mobile<00:03:55.720> wallet<00:03:56.040> a<00:03:56.159> browser<00:03:56.519> wallet<00:03:56.920> a 00:03:57.069 --> 00:03:57.079 align:start position:0% have a mobile wallet a browser wallet a 00:03:57.079 --> 00:03:58.869 align:start position:0% have a mobile wallet a browser wallet a hardware<00:03:57.519> device<00:03:57.840> or<00:03:58.040> even<00:03:58.239> if<00:03:58.360> you<00:03:58.439> use<00:03:58.680> a 00:03:58.869 --> 00:03:58.879 align:start position:0% hardware device or even if you use a 00:03:58.879 --> 00:04:00.429 align:start position:0% hardware device or even if you use a cloud<00:03:59.159> or<00:03:59.319> NPC 00:04:00.429 --> 00:04:00.439 align:start position:0% cloud or NPC 00:04:00.439 --> 00:04:02.550 align:start position:0% cloud or NPC like<00:04:00.680> they<00:04:00.840> all<00:04:01.040> come<00:04:01.280> down<00:04:01.480> to<00:04:01.840> like 00:04:02.550 --> 00:04:02.560 align:start position:0% like they all come down to like 00:04:02.560 --> 00:04:04.390 align:start position:0% like they all come down to like something<00:04:02.959> you<00:04:03.120> know<00:04:03.680> something<00:04:04.079> that<00:04:04.239> you 00:04:04.390 --> 00:04:04.400 align:start position:0% something you know something that you 00:04:04.400 --> 00:04:07.069 align:start position:0% something you know something that you are<00:04:04.720> and<00:04:04.959> something<00:04:05.360> that<00:04:05.560> you<00:04:05.920> have<00:04:06.680> and<00:04:06.840> it 00:04:07.069 --> 00:04:07.079 align:start position:0% are and something that you have and it 00:04:07.079 --> 00:04:08.750 align:start position:0% are and something that you have and it basically<00:04:07.480> breaks<00:04:07.799> down<00:04:08.000> in<00:04:08.239> credential 00:04:08.750 --> 00:04:08.760 align:start position:0% basically breaks down in credential 00:04:08.760 --> 00:04:11.390 align:start position:0% basically breaks down in credential signing<00:04:09.079> in<00:04:09.319> accounts<00:04:10.000> and<00:04:10.560> you<00:04:10.680> can<00:04:10.879> see<00:04:11.159> here 00:04:11.390 --> 00:04:11.400 align:start position:0% signing in accounts and you can see here 00:04:11.400 --> 00:04:12.869 align:start position:0% signing in accounts and you can see here that<00:04:11.599> one<00:04:11.799> thing<00:04:12.000> that<00:04:12.159> they<00:04:12.280> all<00:04:12.480> have<00:04:12.680> in 00:04:12.869 --> 00:04:12.879 align:start position:0% that one thing that they all have in 00:04:12.879 --> 00:04:15.229 align:start position:0% that one thing that they all have in common<00:04:13.280> is<00:04:13.480> this<00:04:13.720> concept<00:04:14.200> of<00:04:14.519> an<00:04:14.720> external 00:04:15.229 --> 00:04:15.239 align:start position:0% common is this concept of an external 00:04:15.239 --> 00:04:17.390 align:start position:0% common is this concept of an external account<00:04:16.079> which<00:04:16.479> is<00:04:16.600> going<00:04:16.720> to<00:04:16.840> be<00:04:17.000> important 00:04:17.390 --> 00:04:17.400 align:start position:0% account which is going to be important 00:04:17.400 --> 00:04:19.349 align:start position:0% account which is going to be important for<00:04:17.560> you<00:04:17.680> to<00:04:17.919> remember<00:04:18.519> that<00:04:18.799> no<00:04:18.959> matter<00:04:19.199> what 00:04:19.349 --> 00:04:19.359 align:start position:0% for you to remember that no matter what 00:04:19.359 --> 00:04:22.390 align:start position:0% for you to remember that no matter what w<00:04:19.720> you<00:04:19.919> have<00:04:20.280> they<00:04:20.479> all<00:04:20.799> have<00:04:21.160> an<00:04:21.359> external 00:04:22.390 --> 00:04:22.400 align:start position:0% w you have they all have an external 00:04:22.400 --> 00:04:25.790 align:start position:0% w you have they all have an external account<00:04:23.400> but<00:04:23.560> before<00:04:23.880> we<00:04:24.000> get<00:04:24.160> into<00:04:24.440> that<00:04:25.160> um<00:04:25.680> I 00:04:25.790 --> 00:04:25.800 align:start position:0% account but before we get into that um I 00:04:25.800 --> 00:04:29.469 align:start position:0% account but before we get into that um I did<00:04:26.040> say<00:04:26.400> that<00:04:26.720> connecting<00:04:27.639> is<00:04:28.000> this<00:04:28.400> new<00:04:28.919> verb 00:04:29.469 --> 00:04:29.479 align:start position:0% did say that connecting is this new verb 00:04:29.479 --> 00:04:33.070 align:start position:0% did say that connecting is this new verb that<00:04:29.880> we<00:04:30.000> moved<00:04:30.360> away<00:04:30.600> from<00:04:30.840> the<00:04:31.280> login<00:04:32.280> but<00:04:32.919> we 00:04:33.070 --> 00:04:33.080 align:start position:0% that we moved away from the login but we 00:04:33.080 --> 00:04:35.629 align:start position:0% that we moved away from the login but we did<00:04:33.360> try<00:04:33.600> to<00:04:33.800> recreate<00:04:34.400> login<00:04:35.320> uh<00:04:35.440> with 00:04:35.629 --> 00:04:35.639 align:start position:0% did try to recreate login uh with 00:04:35.639 --> 00:04:38.590 align:start position:0% did try to recreate login uh with blockchain<00:04:36.520> and<00:04:36.880> basically<00:04:37.880> didn't<00:04:38.280> work 00:04:38.590 --> 00:04:38.600 align:start position:0% blockchain and basically didn't work 00:04:38.600 --> 00:04:40.790 align:start position:0% blockchain and basically didn't work really<00:04:38.880> well<00:04:39.479> until<00:04:39.800> someone<00:04:40.160> came<00:04:40.440> with<00:04:40.560> a 00:04:40.790 --> 00:04:40.800 align:start position:0% really well until someone came with a 00:04:40.800 --> 00:04:42.350 align:start position:0% really well until someone came with a standard<00:04:41.280> which<00:04:41.400> is<00:04:41.520> called<00:04:41.759> sign<00:04:42.000> in<00:04:42.160> with 00:04:42.350 --> 00:04:42.360 align:start position:0% standard which is called sign in with 00:04:42.360 --> 00:04:44.550 align:start position:0% standard which is called sign in with ethereum<00:04:43.360> and<00:04:43.560> sign<00:04:43.759> in<00:04:43.880> with<00:04:44.039> ethereum 00:04:44.550 --> 00:04:44.560 align:start position:0% ethereum and sign in with ethereum 00:04:44.560 --> 00:04:47.189 align:start position:0% ethereum and sign in with ethereum actually<00:04:44.840> is<00:04:45.039> just<00:04:45.320> this<00:04:46.039> uh<00:04:46.199> it's<00:04:46.320> a<00:04:46.560> text 00:04:47.189 --> 00:04:47.199 align:start position:0% actually is just this uh it's a text 00:04:47.199 --> 00:04:49.670 align:start position:0% actually is just this uh it's a text message<00:04:48.199> it's<00:04:48.440> actually<00:04:48.720> very<00:04:49.039> simple<00:04:49.520> like 00:04:49.670 --> 00:04:49.680 align:start position:0% message it's actually very simple like 00:04:49.680 --> 00:04:51.430 align:start position:0% message it's actually very simple like when<00:04:49.800> you<00:04:49.919> think<00:04:50.160> about<00:04:50.320> it<00:04:50.520> it<00:04:50.639> just<00:04:50.800> says 00:04:51.430 --> 00:04:51.440 align:start position:0% when you think about it it just says 00:04:51.440 --> 00:04:52.950 align:start position:0% when you think about it it just says this<00:04:51.639> website<00:04:52.000> wants<00:04:52.240> to<00:04:52.440> access<00:04:52.720> your 00:04:52.950 --> 00:04:52.960 align:start position:0% this website wants to access your 00:04:52.960 --> 00:04:54.550 align:start position:0% this website wants to access your account<00:04:53.400> and<00:04:53.520> then<00:04:53.800> we<00:04:53.960> added<00:04:54.280> some 00:04:54.550 --> 00:04:54.560 align:start position:0% account and then we added some 00:04:54.560 --> 00:04:58.189 align:start position:0% account and then we added some parameters<00:04:55.199> that<00:04:55.360> says<00:04:56.199> like<00:04:57.199> you<00:04:57.360> can<00:04:57.800> access 00:04:58.189 --> 00:04:58.199 align:start position:0% parameters that says like you can access 00:04:58.199 --> 00:05:00.469 align:start position:0% parameters that says like you can access this<00:04:58.400> chain<00:04:58.880> for<00:04:59.160> this<00:04:59.320> amount<00:04:59.720> of<00:04:59.919> period<00:05:00.320> and 00:05:00.469 --> 00:05:00.479 align:start position:0% this chain for this amount of period and 00:05:00.479 --> 00:05:02.790 align:start position:0% this chain for this amount of period and so<00:05:00.639> on<00:05:00.840> and<00:05:01.000> so<00:05:01.199> forth<00:05:01.800> and<00:05:01.960> even<00:05:02.240> throw<00:05:02.560> in 00:05:02.790 --> 00:05:02.800 align:start position:0% so on and so forth and even throw in 00:05:02.800 --> 00:05:04.670 align:start position:0% so on and so forth and even throw in some<00:05:03.120> terms<00:05:03.360> and<00:05:03.720> conditions<00:05:04.080> to<00:05:04.240> make<00:05:04.400> it 00:05:04.670 --> 00:05:04.680 align:start position:0% some terms and conditions to make it 00:05:04.680 --> 00:05:06.830 align:start position:0% some terms and conditions to make it look<00:05:04.919> very<00:05:05.199> familiar<00:05:06.000> but<00:05:06.160> this<00:05:06.240> is<00:05:06.440> actually 00:05:06.830 --> 00:05:06.840 align:start position:0% look very familiar but this is actually 00:05:06.840 --> 00:05:09.029 align:start position:0% look very familiar but this is actually more<00:05:07.160> familiar<00:05:07.680> because<00:05:08.120> if<00:05:08.240> you<00:05:08.400> do<00:05:08.720> Google 00:05:09.029 --> 00:05:09.039 align:start position:0% more familiar because if you do Google 00:05:09.039 --> 00:05:12.029 align:start position:0% more familiar because if you do Google login<00:05:09.759> it's<00:05:09.960> the<00:05:10.120> same<00:05:10.400> thing<00:05:10.840> but<00:05:11.320> we're<00:05:11.680> so 00:05:12.029 --> 00:05:12.039 align:start position:0% login it's the same thing but we're so 00:05:12.039 --> 00:05:15.189 align:start position:0% login it's the same thing but we're so early<00:05:12.520> into<00:05:13.440> blockchain<00:05:14.280> that<00:05:14.600> we<00:05:14.759> don't<00:05:15.000> have 00:05:15.189 --> 00:05:15.199 align:start position:0% early into blockchain that we don't have 00:05:15.199 --> 00:05:17.430 align:start position:0% early into blockchain that we don't have this<00:05:15.360> beautiful<00:05:15.919> UI<00:05:16.240> on<00:05:16.360> the<00:05:16.560> right<00:05:16.919> we<00:05:17.080> have<00:05:17.199> a 00:05:17.430 --> 00:05:17.440 align:start position:0% this beautiful UI on the right we have a 00:05:17.440 --> 00:05:20.510 align:start position:0% this beautiful UI on the right we have a text<00:05:17.800> message<00:05:18.639> so<00:05:19.039> wallets<00:05:19.479> are<00:05:19.800> slowly 00:05:20.510 --> 00:05:20.520 align:start position:0% text message so wallets are slowly 00:05:20.520 --> 00:05:22.629 align:start position:0% text message so wallets are slowly adopting<00:05:20.960> signo<00:05:21.400> ethereum<00:05:21.800> to<00:05:22.000> not<00:05:22.199> just<00:05:22.319> be<00:05:22.479> a 00:05:22.629 --> 00:05:22.639 align:start position:0% adopting signo ethereum to not just be a 00:05:22.639 --> 00:05:25.029 align:start position:0% adopting signo ethereum to not just be a text<00:05:22.880> message<00:05:23.240> and<00:05:23.400> to<00:05:23.560> actually<00:05:24.000> be<00:05:24.600> like<00:05:24.720> a 00:05:25.029 --> 00:05:25.039 align:start position:0% text message and to actually be like a 00:05:25.039 --> 00:05:27.790 align:start position:0% text message and to actually be like a concise<00:05:25.560> and<00:05:25.800> compact<00:05:26.720> display<00:05:27.360> that<00:05:27.520> allows 00:05:27.790 --> 00:05:27.800 align:start position:0% concise and compact display that allows 00:05:27.800 --> 00:05:30.150 align:start position:0% concise and compact display that allows you<00:05:27.919> to<00:05:28.160> connect<00:05:29.000> and<00:05:29.199> eventually<00:05:29.840> you<00:05:29.960> might 00:05:30.150 --> 00:05:30.160 align:start position:0% you to connect and eventually you might 00:05:30.160 --> 00:05:32.270 align:start position:0% you to connect and eventually you might even<00:05:30.440> have<00:05:30.720> this<00:05:31.080> like<00:05:31.280> you<00:05:31.680> actually<00:05:31.960> have<00:05:32.080> a 00:05:32.270 --> 00:05:32.280 align:start position:0% even have this like you actually have a 00:05:32.280 --> 00:05:35.029 align:start position:0% even have this like you actually have a s<00:05:32.880> ethereum<00:05:33.880> here<00:05:34.080> I<00:05:34.240> just<00:05:34.440> modified 00:05:35.029 --> 00:05:35.039 align:start position:0% s ethereum here I just modified 00:05:35.039 --> 00:05:36.950 align:start position:0% s ethereum here I just modified literally<00:05:35.400> the<00:05:35.560> Google<00:05:35.880> one<00:05:36.240> and<00:05:36.360> I<00:05:36.520> put<00:05:36.800> like 00:05:36.950 --> 00:05:36.960 align:start position:0% literally the Google one and I put like 00:05:36.960 --> 00:05:40.150 align:start position:0% literally the Google one and I put like some<00:05:37.280> ethereum<00:05:37.960> stuff<00:05:38.639> but<00:05:39.039> it<00:05:39.240> in<00:05:39.520> concept 00:05:40.150 --> 00:05:40.160 align:start position:0% some ethereum stuff but it in concept 00:05:40.160 --> 00:05:42.390 align:start position:0% some ethereum stuff but it in concept it's<00:05:40.400> the<00:05:40.600> same<00:05:40.960> thing<00:05:41.319> it's<00:05:41.560> the<00:05:41.759> exact<00:05:42.120> same 00:05:42.390 --> 00:05:42.400 align:start position:0% it's the same thing it's the exact same 00:05:42.400 --> 00:05:44.950 align:start position:0% it's the same thing it's the exact same thing<00:05:42.600> that<00:05:42.759> s<00:05:43.520> tries<00:05:43.759> to<00:05:43.919> achieve<00:05:44.600> with<00:05:44.759> a 00:05:44.950 --> 00:05:44.960 align:start position:0% thing that s tries to achieve with a 00:05:44.960 --> 00:05:46.550 align:start position:0% thing that s tries to achieve with a difference<00:05:45.360> that<00:05:45.520> you<00:05:45.759> still<00:05:46.039> have<00:05:46.240> to 00:05:46.550 --> 00:05:46.560 align:start position:0% difference that you still have to 00:05:46.560 --> 00:05:49.909 align:start position:0% difference that you still have to connect<00:05:47.120> to<00:05:47.400> then<00:05:47.840> sign<00:05:48.800> which<00:05:49.080> doesn't<00:05:49.479> feel 00:05:49.909 --> 00:05:49.919 align:start position:0% connect to then sign which doesn't feel 00:05:49.919 --> 00:05:53.150 align:start position:0% connect to then sign which doesn't feel very<00:05:50.280> great<00:05:50.759> like<00:05:51.680> it's<00:05:51.960> like<00:05:52.120> a<00:05:52.319> twostep<00:05:53.000> to 00:05:53.150 --> 00:05:53.160 align:start position:0% very great like it's like a twostep to 00:05:53.160 --> 00:05:56.390 align:start position:0% very great like it's like a twostep to do<00:05:53.319> something<00:05:53.720> that<00:05:53.880> was<00:05:54.639> before<00:05:54.960> a<00:05:55.120> one<00:05:55.440> step 00:05:56.390 --> 00:05:56.400 align:start position:0% do something that was before a one step 00:05:56.400 --> 00:05:58.909 align:start position:0% do something that was before a one step so<00:05:56.720> I'm<00:05:56.880> part<00:05:57.039> of<00:05:57.280> this<00:05:57.800> uh<00:05:57.960> Community<00:05:58.600> called 00:05:58.909 --> 00:05:58.919 align:start position:0% so I'm part of this uh Community called 00:05:58.919 --> 00:06:01.670 align:start position:0% so I'm part of this uh Community called the<00:05:59.039> chain<00:05:59.680> agnostic<00:06:00.039> Improvement<00:06:00.680> proposals 00:06:01.670 --> 00:06:01.680 align:start position:0% the chain agnostic Improvement proposals 00:06:01.680 --> 00:06:03.350 align:start position:0% the chain agnostic Improvement proposals that<00:06:01.960> and<00:06:02.120> we<00:06:02.319> propos<00:06:02.800> this<00:06:03.000> wallet 00:06:03.350 --> 00:06:03.360 align:start position:0% that and we propos this wallet 00:06:03.360 --> 00:06:05.510 align:start position:0% that and we propos this wallet authenticate<00:06:04.319> which<00:06:04.560> basically<00:06:05.039> tries<00:06:05.319> to 00:06:05.510 --> 00:06:05.520 align:start position:0% authenticate which basically tries to 00:06:05.520 --> 00:06:08.749 align:start position:0% authenticate which basically tries to bring<00:06:05.880> back<00:06:06.880> uh<00:06:07.039> the<00:06:07.199> login<00:06:07.800> experience<00:06:08.520> and 00:06:08.749 --> 00:06:08.759 align:start position:0% bring back uh the login experience and 00:06:08.759 --> 00:06:10.990 align:start position:0% bring back uh the login experience and basically<00:06:09.199> that<00:06:09.319> meant<00:06:09.639> that<00:06:09.919> we<00:06:10.520> what<00:06:10.680> if<00:06:10.800> we 00:06:10.990 --> 00:06:11.000 align:start position:0% basically that meant that we what if we 00:06:11.000 --> 00:06:12.870 align:start position:0% basically that meant that we what if we just<00:06:11.199> don't<00:06:11.520> connect<00:06:12.039> anymore<00:06:12.400> we<00:06:12.560> just<00:06:12.720> like 00:06:12.870 --> 00:06:12.880 align:start position:0% just don't connect anymore we just like 00:06:12.880 --> 00:06:15.070 align:start position:0% just don't connect anymore we just like go<00:06:13.080> straight<00:06:13.319> to<00:06:13.479> the<00:06:13.680> signature<00:06:14.639> so<00:06:14.880> if<00:06:14.960> you 00:06:15.070 --> 00:06:15.080 align:start position:0% go straight to the signature so if you 00:06:15.080 --> 00:06:17.230 align:start position:0% go straight to the signature so if you could<00:06:15.240> just<00:06:15.400> do<00:06:15.680> sign<00:06:16.000> with<00:06:16.199> ethereum<00:06:17.039> like 00:06:17.230 --> 00:06:17.240 align:start position:0% could just do sign with ethereum like 00:06:17.240 --> 00:06:19.430 align:start position:0% could just do sign with ethereum like you<00:06:17.360> could<00:06:17.599> actually<00:06:17.880> get<00:06:18.120> this<00:06:18.400> like<00:06:19.000> Google 00:06:19.430 --> 00:06:19.440 align:start position:0% you could actually get this like Google 00:06:19.440 --> 00:06:21.870 align:start position:0% you could actually get this like Google login<00:06:19.960> experience<00:06:20.479> with<00:06:20.639> your<00:06:20.840> wallet<00:06:21.639> and<00:06:21.759> it 00:06:21.870 --> 00:06:21.880 align:start position:0% login experience with your wallet and it 00:06:21.880 --> 00:06:23.670 align:start position:0% login experience with your wallet and it would<00:06:22.080> be<00:06:22.280> even<00:06:22.479> more<00:06:22.720> secure<00:06:23.199> because<00:06:23.479> when 00:06:23.670 --> 00:06:23.680 align:start position:0% would be even more secure because when 00:06:23.680 --> 00:06:25.670 align:start position:0% would be even more secure because when you're<00:06:23.880> signing<00:06:24.360> your<00:06:24.560> wallet<00:06:25.400> and 00:06:25.670 --> 00:06:25.680 align:start position:0% you're signing your wallet and 00:06:25.680 --> 00:06:27.390 align:start position:0% you're signing your wallet and connecting<00:06:26.160> at<00:06:26.280> the<00:06:26.440> same<00:06:26.680> time<00:06:27.160> you're 00:06:27.390 --> 00:06:27.400 align:start position:0% connecting at the same time you're 00:06:27.400 --> 00:06:29.029 align:start position:0% connecting at the same time you're actually<00:06:27.680> verifying<00:06:28.280> ownership<00:06:28.720> of<00:06:28.880> your 00:06:29.029 --> 00:06:29.039 align:start position:0% actually verifying ownership of your 00:06:29.039 --> 00:06:31.550 align:start position:0% actually verifying ownership of your wallet<00:06:29.759> so<00:06:30.199> this<00:06:30.400> was<00:06:30.639> actually<00:06:30.880> pretty<00:06:31.160> cool 00:06:31.550 --> 00:06:31.560 align:start position:0% wallet so this was actually pretty cool 00:06:31.560 --> 00:06:35.629 align:start position:0% wallet so this was actually pretty cool and<00:06:31.880> this<00:06:32.080> got<00:06:32.360> us<00:06:32.759> like<00:06:33.360> you<00:06:33.599> know<00:06:34.599> like<00:06:35.319> less 00:06:35.629 --> 00:06:35.639 align:start position:0% and this got us like you know like less 00:06:35.639 --> 00:06:38.029 align:start position:0% and this got us like you know like less clicks<00:06:35.960> is<00:06:36.160> more<00:06:36.639> but<00:06:36.919> is<00:06:37.080> that<00:06:37.360> enough<00:06:37.880> like 00:06:38.029 --> 00:06:38.039 align:start position:0% clicks is more but is that enough like 00:06:38.039 --> 00:06:39.350 align:start position:0% clicks is more but is that enough like because<00:06:38.280> at<00:06:38.360> the<00:06:38.440> end<00:06:38.560> of<00:06:38.680> the<00:06:38.800> day<00:06:39.039> most 00:06:39.350 --> 00:06:39.360 align:start position:0% because at the end of the day most 00:06:39.360 --> 00:06:41.230 align:start position:0% because at the end of the day most wallets<00:06:39.759> are<00:06:40.000> used<00:06:40.319> for<00:06:40.560> transaction 00:06:41.230 --> 00:06:41.240 align:start position:0% wallets are used for transaction 00:06:41.240 --> 00:06:43.830 align:start position:0% wallets are used for transaction purposes<00:06:42.240> and<00:06:42.400> logging<00:06:42.800> in<00:06:43.039> is<00:06:43.240> just<00:06:43.440> one<00:06:43.680> part 00:06:43.830 --> 00:06:43.840 align:start position:0% purposes and logging in is just one part 00:06:43.840 --> 00:06:46.909 align:start position:0% purposes and logging in is just one part of<00:06:44.000> it<00:06:44.280> so<00:06:44.919> yes<00:06:45.160> we<00:06:45.360> reduced<00:06:45.880> connect<00:06:46.199> and<00:06:46.520> sign 00:06:46.909 --> 00:06:46.919 align:start position:0% of it so yes we reduced connect and sign 00:06:46.919 --> 00:06:50.790 align:start position:0% of it so yes we reduced connect and sign into<00:06:47.160> a<00:06:47.360> single<00:06:47.759> step<00:06:48.599> but<00:06:49.440> after<00:06:49.800> you<00:06:50.080> log<00:06:50.440> in 00:06:50.790 --> 00:06:50.800 align:start position:0% into a single step but after you log in 00:06:50.800 --> 00:06:52.629 align:start position:0% into a single step but after you log in or<00:06:51.000> you<00:06:51.160> connect<00:06:51.560> with<00:06:51.720> your<00:06:51.919> wallet<00:06:52.479> you 00:06:52.629 --> 00:06:52.639 align:start position:0% or you connect with your wallet you 00:06:52.639 --> 00:06:55.029 align:start position:0% or you connect with your wallet you still<00:06:52.919> need<00:06:53.120> to<00:06:53.319> perform<00:06:53.720> some<00:06:54.039> transactions 00:06:55.029 --> 00:06:55.039 align:start position:0% still need to perform some transactions 00:06:55.039 --> 00:06:57.390 align:start position:0% still need to perform some transactions and<00:06:55.240> this<00:06:55.479> looks<00:06:55.879> as<00:06:56.440> you<00:06:56.560> know<00:06:56.840> switching<00:06:57.240> to 00:06:57.390 --> 00:06:57.400 align:start position:0% and this looks as you know switching to 00:06:57.400 --> 00:06:58.909 align:start position:0% and this looks as you know switching to the<00:06:57.560> wallet<00:06:57.919> and<00:06:58.120> everything<00:06:58.520> approving 00:06:58.909 --> 00:06:58.919 align:start position:0% the wallet and everything approving 00:06:58.919 --> 00:07:00.110 align:start position:0% the wallet and everything approving transactions 00:07:00.110 --> 00:07:00.120 align:start position:0% transactions 00:07:00.120 --> 00:07:02.390 align:start position:0% transactions and<00:07:00.319> when<00:07:00.479> you<00:07:00.759> think<00:07:01.039> about<00:07:01.960> signing 00:07:02.390 --> 00:07:02.400 align:start position:0% and when you think about signing 00:07:02.400 --> 00:07:05.070 align:start position:0% and when you think about signing transactions<00:07:03.360> there's<00:07:03.560> a<00:07:03.800> lot<00:07:04.280> of<00:07:04.479> new<00:07:04.759> on 00:07:05.070 --> 00:07:05.080 align:start position:0% transactions there's a lot of new on 00:07:05.080 --> 00:07:08.390 align:start position:0% transactions there's a lot of new on here<00:07:05.560> like<00:07:06.560> the<00:07:06.960> beautiful<00:07:07.720> thing<00:07:08.039> about 00:07:08.390 --> 00:07:08.400 align:start position:0% here like the beautiful thing about 00:07:08.400 --> 00:07:11.029 align:start position:0% here like the beautiful thing about ethereum<00:07:09.280> is<00:07:09.599> that<00:07:10.000> it's<00:07:10.199> a<00:07:10.360> smart<00:07:10.680> contract 00:07:11.029 --> 00:07:11.039 align:start position:0% ethereum is that it's a smart contract 00:07:11.039 --> 00:07:12.430 align:start position:0% ethereum is that it's a smart contract blockchain<00:07:11.520> which<00:07:11.639> means<00:07:11.840> you<00:07:11.960> can<00:07:12.160> do 00:07:12.430 --> 00:07:12.440 align:start position:0% blockchain which means you can do 00:07:12.440 --> 00:07:14.749 align:start position:0% blockchain which means you can do everything<00:07:13.400> the<00:07:13.680> disadvantage<00:07:14.360> of<00:07:14.520> being 00:07:14.749 --> 00:07:14.759 align:start position:0% everything the disadvantage of being 00:07:14.759 --> 00:07:16.390 align:start position:0% everything the disadvantage of being able<00:07:14.960> to<00:07:15.120> do<00:07:15.319> everything<00:07:15.840> is<00:07:16.000> that<00:07:16.199> these 00:07:16.390 --> 00:07:16.400 align:start position:0% able to do everything is that these 00:07:16.400 --> 00:07:19.869 align:start position:0% able to do everything is that these transactions<00:07:16.960> can<00:07:17.199> be<00:07:18.000> incredibly<00:07:19.000> complex 00:07:19.869 --> 00:07:19.879 align:start position:0% transactions can be incredibly complex 00:07:19.879 --> 00:07:21.510 align:start position:0% transactions can be incredibly complex and<00:07:20.879> understanding<00:07:21.160> what<00:07:21.360> these 00:07:21.510 --> 00:07:21.520 align:start position:0% and understanding what these 00:07:21.520 --> 00:07:24.469 align:start position:0% and understanding what these transactions<00:07:22.160> look<00:07:22.479> like<00:07:23.319> um<00:07:23.879> can<00:07:24.120> be<00:07:24.360> a 00:07:24.469 --> 00:07:24.479 align:start position:0% transactions look like um can be a 00:07:24.479 --> 00:07:26.390 align:start position:0% transactions look like um can be a little<00:07:24.759> daunting<00:07:25.440> and<00:07:25.840> at<00:07:25.960> the<00:07:26.039> end<00:07:26.160> of<00:07:26.280> the 00:07:26.390 --> 00:07:26.400 align:start position:0% little daunting and at the end of the 00:07:26.400 --> 00:07:27.830 align:start position:0% little daunting and at the end of the day<00:07:26.560> people<00:07:26.840> just<00:07:27.039> like<00:07:27.240> close<00:07:27.520> their<00:07:27.680> eyes 00:07:27.830 --> 00:07:27.840 align:start position:0% day people just like close their eyes 00:07:27.840 --> 00:07:30.150 align:start position:0% day people just like close their eyes and<00:07:28.080> they<00:07:28.280> just<00:07:28.400> like<00:07:28.639> approve<00:07:29.120> you<00:07:29.240> know<00:07:29.639> you 00:07:30.150 --> 00:07:30.160 align:start position:0% and they just like approve you know you 00:07:30.160 --> 00:07:31.749 align:start position:0% and they just like approve you know you let's<00:07:30.360> be<00:07:30.560> honest<00:07:30.800> with<00:07:30.960> ourselves<00:07:31.479> like<00:07:31.639> if 00:07:31.749 --> 00:07:31.759 align:start position:0% let's be honest with ourselves like if 00:07:31.759 --> 00:07:33.909 align:start position:0% let's be honest with ourselves like if it's<00:07:32.039> not<00:07:32.360> transferring<00:07:32.879> a<00:07:33.120> token<00:07:33.599> most 00:07:33.909 --> 00:07:33.919 align:start position:0% it's not transferring a token most 00:07:33.919 --> 00:07:37.070 align:start position:0% it's not transferring a token most people<00:07:34.440> are<00:07:34.840> not<00:07:35.840> actually<00:07:36.280> looking<00:07:36.680> into 00:07:37.070 --> 00:07:37.080 align:start position:0% people are not actually looking into 00:07:37.080 --> 00:07:40.350 align:start position:0% people are not actually looking into this<00:07:37.599> and<00:07:37.919> the<00:07:38.039> reason<00:07:38.319> for<00:07:38.520> that<00:07:38.720> is<00:07:39.360> because 00:07:40.350 --> 00:07:40.360 align:start position:0% this and the reason for that is because 00:07:40.360 --> 00:07:42.270 align:start position:0% this and the reason for that is because there's<00:07:40.800> applications<00:07:41.440> out<00:07:41.680> there<00:07:41.960> that<00:07:42.120> we 00:07:42.270 --> 00:07:42.280 align:start position:0% there's applications out there that we 00:07:42.280 --> 00:07:45.149 align:start position:0% there's applications out there that we don't<00:07:42.479> know<00:07:42.759> about<00:07:42.960> it<00:07:43.599> so<00:07:44.400> but<00:07:44.599> we<00:07:44.759> also<00:07:45.000> don't 00:07:45.149 --> 00:07:45.159 align:start position:0% don't know about it so but we also don't 00:07:45.159 --> 00:07:47.469 align:start position:0% don't know about it so but we also don't want<00:07:45.280> to<00:07:45.479> scare<00:07:45.800> people<00:07:46.039> away<00:07:46.879> and<00:07:47.120> this<00:07:47.360> kind 00:07:47.469 --> 00:07:47.479 align:start position:0% want to scare people away and this kind 00:07:47.479 --> 00:07:50.309 align:start position:0% want to scare people away and this kind of<00:07:48.120> balancing<00:07:48.919> convenience<00:07:49.440> and<00:07:49.680> security<00:07:50.120> is 00:07:50.309 --> 00:07:50.319 align:start position:0% of balancing convenience and security is 00:07:50.319 --> 00:07:51.790 align:start position:0% of balancing convenience and security is kind<00:07:50.440> of<00:07:50.599> hard<00:07:51.039> right<00:07:51.240> that's<00:07:51.400> kind<00:07:51.520> of<00:07:51.639> like 00:07:51.790 --> 00:07:51.800 align:start position:0% kind of hard right that's kind of like 00:07:51.800 --> 00:07:54.390 align:start position:0% kind of hard right that's kind of like the<00:07:52.039> magic<00:07:52.440> of<00:07:52.599> building<00:07:52.919> a<00:07:53.039> great<00:07:53.479> wallet 00:07:54.390 --> 00:07:54.400 align:start position:0% the magic of building a great wallet 00:07:54.400 --> 00:07:56.589 align:start position:0% the magic of building a great wallet where<00:07:54.720> you<00:07:54.960> have<00:07:55.120> to<00:07:55.560> allow<00:07:55.919> people<00:07:56.240> to 00:07:56.589 --> 00:07:56.599 align:start position:0% where you have to allow people to 00:07:56.599 --> 00:07:58.830 align:start position:0% where you have to allow people to explore<00:07:57.280> every<00:07:57.639> application<00:07:58.120> that<00:07:58.360> exists 00:07:58.830 --> 00:07:58.840 align:start position:0% explore every application that exists 00:07:58.840 --> 00:08:00.629 align:start position:0% explore every application that exists and<00:07:59.000> at<00:07:59.080> the<00:07:59.199> same<00:07:59.639> time<00:07:59.800> make<00:08:00.000> sure<00:08:00.199> they're 00:08:00.629 --> 00:08:00.639 align:start position:0% and at the same time make sure they're 00:08:00.639 --> 00:08:02.950 align:start position:0% and at the same time make sure they're secure<00:08:01.639> and<00:08:02.199> I'm<00:08:02.280> not<00:08:02.440> saying<00:08:02.639> that<00:08:02.800> we 00:08:02.950 --> 00:08:02.960 align:start position:0% secure and I'm not saying that we 00:08:02.960 --> 00:08:06.029 align:start position:0% secure and I'm not saying that we haven't<00:08:03.199> done<00:08:03.400> a<00:08:03.560> good<00:08:03.840> job<00:08:04.479> but<00:08:05.319> we<00:08:05.720> still 00:08:06.029 --> 00:08:06.039 align:start position:0% haven't done a good job but we still 00:08:06.039 --> 00:08:08.390 align:start position:0% haven't done a good job but we still have<00:08:06.159> to<00:08:06.400> continue<00:08:06.840> to<00:08:07.080> focus<00:08:07.560> on<00:08:07.840> doing<00:08:08.159> less 00:08:08.390 --> 00:08:08.400 align:start position:0% have to continue to focus on doing less 00:08:08.400 --> 00:08:11.510 align:start position:0% have to continue to focus on doing less clicks<00:08:08.720> is<00:08:08.919> more<00:08:09.639> and<00:08:09.800> at<00:08:09.960> the<00:08:10.120> same<00:08:10.479> time<00:08:11.280> we 00:08:11.510 --> 00:08:11.520 align:start position:0% clicks is more and at the same time we 00:08:11.520 --> 00:08:14.629 align:start position:0% clicks is more and at the same time we actually<00:08:11.879> have<00:08:12.080> to<00:08:12.759> give<00:08:13.039> people<00:08:13.639> security 00:08:14.629 --> 00:08:14.639 align:start position:0% actually have to give people security 00:08:14.639 --> 00:08:16.629 align:start position:0% actually have to give people security and<00:08:14.800> I<00:08:14.879> think<00:08:15.120> this<00:08:15.240> is<00:08:15.479> where<00:08:15.639> we<00:08:15.800> go<00:08:16.039> back<00:08:16.280> to 00:08:16.629 --> 00:08:16.639 align:start position:0% and I think this is where we go back to 00:08:16.639 --> 00:08:18.230 align:start position:0% and I think this is where we go back to the<00:08:16.800> definition<00:08:17.240> of<00:08:17.360> a<00:08:17.520> wallet<00:08:17.960> that<00:08:18.120> I 00:08:18.230 --> 00:08:18.240 align:start position:0% the definition of a wallet that I 00:08:18.240 --> 00:08:21.629 align:start position:0% the definition of a wallet that I mentioned<00:08:18.840> it's<00:08:19.560> credentials<00:08:20.560> signing<00:08:21.280> and 00:08:21.629 --> 00:08:21.639 align:start position:0% mentioned it's credentials signing and 00:08:21.639 --> 00:08:24.909 align:start position:0% mentioned it's credentials signing and an<00:08:21.919> accounts<00:08:22.879> and<00:08:23.240> all<00:08:23.599> wallets<00:08:23.960> today<00:08:24.520> have 00:08:24.909 --> 00:08:24.919 align:start position:0% an accounts and all wallets today have 00:08:24.919 --> 00:08:28.230 align:start position:0% an accounts and all wallets today have external<00:08:25.599> accounts<00:08:26.319> so<00:08:26.879> that's<00:08:27.199> why<00:08:27.520> we<00:08:28.000> then 00:08:28.230 --> 00:08:28.240 align:start position:0% external accounts so that's why we then 00:08:28.240 --> 00:08:30.510 align:start position:0% external accounts so that's why we then have<00:08:28.440> the<00:08:28.599> concept<00:08:28.919> of<00:08:29.039> smart<00:08:29.520> accounts 00:08:30.510 --> 00:08:30.520 align:start position:0% have the concept of smart accounts 00:08:30.520 --> 00:08:32.029 align:start position:0% have the concept of smart accounts technically<00:08:30.960> speaking<00:08:31.360> they're<00:08:31.560> not<00:08:31.800> called 00:08:32.029 --> 00:08:32.039 align:start position:0% technically speaking they're not called 00:08:32.039 --> 00:08:34.230 align:start position:0% technically speaking they're not called smart<00:08:32.399> accounts<00:08:33.080> uh<00:08:33.200> neither<00:08:33.479> are<00:08:33.760> external 00:08:34.230 --> 00:08:34.240 align:start position:0% smart accounts uh neither are external 00:08:34.240 --> 00:08:36.509 align:start position:0% smart accounts uh neither are external accounts<00:08:34.599> they're<00:08:34.800> called<00:08:35.279> externally<00:08:36.000> owned 00:08:36.509 --> 00:08:36.519 align:start position:0% accounts they're called externally owned 00:08:36.519 --> 00:08:40.230 align:start position:0% accounts they're called externally owned accounts<00:08:37.200> most<00:08:37.959> commonly<00:08:38.399> referred<00:08:38.839> as<00:08:39.240> EAS 00:08:40.230 --> 00:08:40.240 align:start position:0% accounts most commonly referred as EAS 00:08:40.240 --> 00:08:42.750 align:start position:0% accounts most commonly referred as EAS and<00:08:40.360> then<00:08:40.519> we<00:08:40.680> have<00:08:40.919> Smart<00:08:41.360> contract<00:08:41.839> accounts 00:08:42.750 --> 00:08:42.760 align:start position:0% and then we have Smart contract accounts 00:08:42.760 --> 00:08:43.590 align:start position:0% and then we have Smart contract accounts or 00:08:43.590 --> 00:08:43.600 align:start position:0% or 00:08:43.600 --> 00:08:46.509 align:start position:0% or scas<00:08:44.600> but<00:08:45.240> no<00:08:45.600> honestly<00:08:46.080> like<00:08:46.200> when<00:08:46.279> I<00:08:46.399> have 00:08:46.509 --> 00:08:46.519 align:start position:0% scas but no honestly like when I have 00:08:46.519 --> 00:08:47.870 align:start position:0% scas but no honestly like when I have conversation<00:08:46.959> with<00:08:47.120> people<00:08:47.320> we<00:08:47.440> just<00:08:47.560> call<00:08:47.720> it 00:08:47.870 --> 00:08:47.880 align:start position:0% conversation with people we just call it 00:08:47.880 --> 00:08:49.269 align:start position:0% conversation with people we just call it external<00:08:48.279> account<00:08:48.480> and<00:08:48.600> smart<00:08:48.880> account<00:08:49.160> like 00:08:49.269 --> 00:08:49.279 align:start position:0% external account and smart account like 00:08:49.279 --> 00:08:51.870 align:start position:0% external account and smart account like that's<00:08:49.480> kind<00:08:49.600> of<00:08:49.800> like<00:08:49.920> the<00:08:50.040> easy<00:08:50.360> way<00:08:50.640> so<00:08:51.560> most 00:08:51.870 --> 00:08:51.880 align:start position:0% that's kind of like the easy way so most 00:08:51.880 --> 00:08:55.509 align:start position:0% that's kind of like the easy way so most wallets<00:08:52.320> today<00:08:52.880> like<00:08:53.040> 95<00:08:53.839> or<00:08:54.000> 99%<00:08:54.880> of<00:08:55.000> the<00:08:55.279> time 00:08:55.509 --> 00:08:55.519 align:start position:0% wallets today like 95 or 99% of the time 00:08:55.519 --> 00:08:58.030 align:start position:0% wallets today like 95 or 99% of the time are<00:08:55.800> external<00:08:56.320> accounts<00:08:57.120> and<00:08:57.320> we're<00:08:57.519> in<00:08:57.720> this 00:08:58.030 --> 00:08:58.040 align:start position:0% are external accounts and we're in this 00:08:58.040 --> 00:08:59.430 align:start position:0% are external accounts and we're in this process<00:08:58.480> of<00:08:58.720> making<00:08:59.000> the<00:08:59.120> experience 00:08:59.430 --> 00:08:59.440 align:start position:0% process of making the experience 00:08:59.440 --> 00:09:00.990 align:start position:0% process of making the experience experience<00:08:59.760> better<00:09:00.120> by<00:09:00.279> turning<00:09:00.640> them<00:09:00.800> into 00:09:00.990 --> 00:09:01.000 align:start position:0% experience better by turning them into 00:09:01.000 --> 00:09:02.389 align:start position:0% experience better by turning them into smart<00:09:01.320> accounts<00:09:01.720> which<00:09:01.839> means<00:09:02.120> that<00:09:02.240> they're 00:09:02.389 --> 00:09:02.399 align:start position:0% smart accounts which means that they're 00:09:02.399 --> 00:09:04.310 align:start position:0% smart accounts which means that they're going<00:09:02.480> to<00:09:02.600> be<00:09:02.720> more<00:09:03.040> programmable<00:09:04.040> but<00:09:04.160> it 00:09:04.310 --> 00:09:04.320 align:start position:0% going to be more programmable but it 00:09:04.320 --> 00:09:06.750 align:start position:0% going to be more programmable but it also<00:09:04.560> means<00:09:04.920> that<00:09:05.160> like<00:09:05.920> you<00:09:06.200> now<00:09:06.440> have<00:09:06.560> to 00:09:06.750 --> 00:09:06.760 align:start position:0% also means that like you now have to 00:09:06.760 --> 00:09:08.790 align:start position:0% also means that like you now have to deploy<00:09:07.120> a<00:09:07.279> smart<00:09:07.600> contract<00:09:08.079> so<00:09:08.360> if<00:09:08.480> you<00:09:08.640> have 00:09:08.790 --> 00:09:08.800 align:start position:0% deploy a smart contract so if you have 00:09:08.800 --> 00:09:11.310 align:start position:0% deploy a smart contract so if you have to<00:09:09.000> deploy<00:09:09.440> a<00:09:09.640> smart<00:09:10.000> contract<00:09:10.839> you're<00:09:11.120> no 00:09:11.310 --> 00:09:11.320 align:start position:0% to deploy a smart contract you're no 00:09:11.320 --> 00:09:13.790 align:start position:0% to deploy a smart contract you're no longer<00:09:11.680> thinking<00:09:12.079> of<00:09:12.279> your<00:09:12.480> wallet<00:09:13.040> as<00:09:13.399> just 00:09:13.790 --> 00:09:13.800 align:start position:0% longer thinking of your wallet as just 00:09:13.800 --> 00:09:16.750 align:start position:0% longer thinking of your wallet as just one<00:09:14.200> key<00:09:14.640> that<00:09:14.760> is<00:09:14.959> managed<00:09:15.519> by<00:09:16.000> your<00:09:16.279> secret 00:09:16.750 --> 00:09:16.760 align:start position:0% one key that is managed by your secret 00:09:16.760 --> 00:09:18.670 align:start position:0% one key that is managed by your secret recovery<00:09:17.240> phrase<00:09:17.920> you<00:09:18.120> actually<00:09:18.399> have<00:09:18.560> a 00:09:18.670 --> 00:09:18.680 align:start position:0% recovery phrase you actually have a 00:09:18.680 --> 00:09:21.069 align:start position:0% recovery phrase you actually have a smart<00:09:19.000> contract<00:09:19.480> and<00:09:19.680> that<00:09:19.880> is<00:09:20.600> like<00:09:20.839> the 00:09:21.069 --> 00:09:21.079 align:start position:0% smart contract and that is like the 00:09:21.079 --> 00:09:23.509 align:start position:0% smart contract and that is like the account<00:09:21.600> that<00:09:21.720> your<00:09:21.920> wallet<00:09:22.279> manages<00:09:23.160> but<00:09:23.399> if 00:09:23.509 --> 00:09:23.519 align:start position:0% account that your wallet manages but if 00:09:23.519 --> 00:09:27.190 align:start position:0% account that your wallet manages but if you<00:09:23.680> don't<00:09:24.279> have<00:09:24.959> an<00:09:25.920> a<00:09:26.120> key<00:09:26.519> you<00:09:26.680> don't<00:09:26.880> have<00:09:27.040> a 00:09:27.190 --> 00:09:27.200 align:start position:0% you don't have an a key you don't have a 00:09:27.200 --> 00:09:29.389 align:start position:0% you don't have an a key you don't have a signature<00:09:27.760> so<00:09:28.120> how<00:09:28.320> am<00:09:28.519> I<00:09:28.880> actually<00:09:29.160> going 00:09:29.389 --> 00:09:29.399 align:start position:0% signature so how am I actually going 00:09:29.399 --> 00:09:31.190 align:start position:0% signature so how am I actually going want<00:09:29.519> to<00:09:29.760> sign<00:09:30.160> like<00:09:30.320> the<00:09:30.440> whole<00:09:30.720> purpose<00:09:31.040> of 00:09:31.190 --> 00:09:31.200 align:start position:0% want to sign like the whole purpose of 00:09:31.200 --> 00:09:33.910 align:start position:0% want to sign like the whole purpose of this<00:09:31.360> was<00:09:31.519> to<00:09:31.760> sign<00:09:32.600> so<00:09:32.959> what<00:09:33.120> is<00:09:33.399> actually 00:09:33.910 --> 00:09:33.920 align:start position:0% this was to sign so what is actually 00:09:33.920 --> 00:09:37.790 align:start position:0% this was to sign so what is actually controlling<00:09:34.760> your<00:09:34.959> smart<00:09:35.320> account<00:09:36.640> so<00:09:37.640> there 00:09:37.790 --> 00:09:37.800 align:start position:0% controlling your smart account so there 00:09:37.800 --> 00:09:39.949 align:start position:0% controlling your smart account so there was<00:09:38.000> a<00:09:38.240> standard<00:09:38.640> that<00:09:38.800> was<00:09:38.959> created<00:09:39.440> which<00:09:39.560> is 00:09:39.949 --> 00:09:39.959 align:start position:0% was a standard that was created which is 00:09:39.959 --> 00:09:42.190 align:start position:0% was a standard that was created which is how<00:09:40.160> can<00:09:40.360> we<00:09:40.640> actually<00:09:41.000> validate<00:09:41.600> ownership 00:09:42.190 --> 00:09:42.200 align:start position:0% how can we actually validate ownership 00:09:42.200 --> 00:09:44.630 align:start position:0% how can we actually validate ownership over<00:09:42.920> contracts<00:09:43.560> because<00:09:43.880> while<00:09:44.440> with 00:09:44.630 --> 00:09:44.640 align:start position:0% over contracts because while with 00:09:44.640 --> 00:09:46.430 align:start position:0% over contracts because while with signing<00:09:44.959> with<00:09:45.079> theerum<00:09:45.600> was<00:09:45.760> very<00:09:45.959> simple<00:09:46.279> you 00:09:46.430 --> 00:09:46.440 align:start position:0% signing with theerum was very simple you 00:09:46.440 --> 00:09:48.910 align:start position:0% signing with theerum was very simple you signed<00:09:46.760> this<00:09:46.959> text<00:09:47.279> message<00:09:47.880> and<00:09:48.079> now<00:09:48.640> I<00:09:48.760> can 00:09:48.910 --> 00:09:48.920 align:start position:0% signed this text message and now I can 00:09:48.920 --> 00:09:50.550 align:start position:0% signed this text message and now I can just<00:09:49.120> verify<00:09:49.440> that<00:09:49.600> the<00:09:49.760> signature<00:09:50.200> matches 00:09:50.550 --> 00:09:50.560 align:start position:0% just verify that the signature matches 00:09:50.560 --> 00:09:52.829 align:start position:0% just verify that the signature matches your<00:09:50.760> address<00:09:51.200> but<00:09:51.360> with<00:09:51.480> a<00:09:51.600> smart<00:09:51.959> contract<00:09:52.720> I 00:09:52.829 --> 00:09:52.839 align:start position:0% your address but with a smart contract I 00:09:52.839 --> 00:09:54.990 align:start position:0% your address but with a smart contract I don't<00:09:53.079> really<00:09:53.440> know<00:09:53.640> how<00:09:53.800> to<00:09:53.959> validate<00:09:54.320> it<00:09:54.800> so 00:09:54.990 --> 00:09:55.000 align:start position:0% don't really know how to validate it so 00:09:55.000 --> 00:09:57.590 align:start position:0% don't really know how to validate it so ERC<00:09:55.440> 1271<00:09:56.440> created<00:09:56.839> like<00:09:56.959> a<00:09:57.079> very<00:09:57.279> simple 00:09:57.590 --> 00:09:57.600 align:start position:0% ERC 1271 created like a very simple 00:09:57.600 --> 00:10:00.350 align:start position:0% ERC 1271 created like a very simple interface<00:09:58.079> that<00:09:58.200> says<00:09:58.880> is<00:09:59.040> valid<00:09:59.600> signature 00:10:00.350 --> 00:10:00.360 align:start position:0% interface that says is valid signature 00:10:00.360 --> 00:10:02.710 align:start position:0% interface that says is valid signature it<00:10:00.720> like<00:10:01.440> you<00:10:01.560> know<00:10:01.959> sometimes<00:10:02.200> people<00:10:02.440> think 00:10:02.710 --> 00:10:02.720 align:start position:0% it like you know sometimes people think 00:10:02.720 --> 00:10:04.430 align:start position:0% it like you know sometimes people think like<00:10:02.920> this<00:10:03.200> code<00:10:03.480> things<00:10:03.760> are<00:10:04.120> very 00:10:04.430 --> 00:10:04.440 align:start position:0% like this code things are very 00:10:04.440 --> 00:10:06.269 align:start position:0% like this code things are very complicated<00:10:05.120> but<00:10:05.360> this<00:10:05.440> is<00:10:05.680> literally<00:10:06.120> the 00:10:06.269 --> 00:10:06.279 align:start position:0% complicated but this is literally the 00:10:06.279 --> 00:10:09.630 align:start position:0% complicated but this is literally the whole<00:10:06.519> spec<00:10:07.519> like<00:10:08.079> it's<00:10:08.360> like<00:10:08.720> very<00:10:09.040> long<00:10:09.399> to 00:10:09.630 --> 00:10:09.640 align:start position:0% whole spec like it's like very long to 00:10:09.640 --> 00:10:13.110 align:start position:0% whole spec like it's like very long to read<00:10:10.160> but<00:10:10.360> then<00:10:10.720> it's<00:10:11.480> is<00:10:11.839> valid<00:10:12.200> signature<00:10:12.880> is 00:10:13.110 --> 00:10:13.120 align:start position:0% read but then it's is valid signature is 00:10:13.120 --> 00:10:15.550 align:start position:0% read but then it's is valid signature is the<00:10:13.320> whole<00:10:13.640> code<00:10:14.480> like<00:10:14.720> and<00:10:14.920> this<00:10:15.079> basically 00:10:15.550 --> 00:10:15.560 align:start position:0% the whole code like and this basically 00:10:15.560 --> 00:10:18.790 align:start position:0% the whole code like and this basically takes<00:10:15.800> a<00:10:16.200> signature<00:10:16.839> and<00:10:17.079> throws<00:10:17.800> a<00:10:18.240> true<00:10:18.519> or 00:10:18.790 --> 00:10:18.800 align:start position:0% takes a signature and throws a true or 00:10:18.800 --> 00:10:21.230 align:start position:0% takes a signature and throws a true or false<00:10:19.240> so<00:10:19.440> it<00:10:19.560> basically<00:10:19.920> it's<00:10:20.040> a<00:10:20.200> binary<00:10:21.079> that 00:10:21.230 --> 00:10:21.240 align:start position:0% false so it basically it's a binary that 00:10:21.240 --> 00:10:23.590 align:start position:0% false so it basically it's a binary that says<00:10:21.880> yes<00:10:22.160> it<00:10:22.279> is<00:10:22.399> a<00:10:22.560> valid<00:10:22.839> signature<00:10:23.360> so<00:10:23.480> your 00:10:23.590 --> 00:10:23.600 align:start position:0% says yes it is a valid signature so your 00:10:23.600 --> 00:10:26.310 align:start position:0% says yes it is a valid signature so your smart<00:10:23.880> contract<00:10:24.240> is<00:10:24.399> basically<00:10:24.800> saying<00:10:25.640> that 00:10:26.310 --> 00:10:26.320 align:start position:0% smart contract is basically saying that 00:10:26.320 --> 00:10:29.590 align:start position:0% smart contract is basically saying that this<00:10:26.600> signature<00:10:27.519> was<00:10:28.120> done<00:10:28.640> by<00:10:28.880> someone<00:10:29.440> was 00:10:29.590 --> 00:10:29.600 align:start position:0% this signature was done by someone was 00:10:29.600 --> 00:10:32.990 align:start position:0% this signature was done by someone was authorized<00:10:30.200> to<00:10:30.360> control<00:10:31.079> my<00:10:31.440> account<00:10:32.240> so<00:10:32.800> now 00:10:32.990 --> 00:10:33.000 align:start position:0% authorized to control my account so now 00:10:33.000 --> 00:10:34.509 align:start position:0% authorized to control my account so now we<00:10:33.120> have<00:10:33.240> to<00:10:33.399> get<00:10:33.640> a<00:10:33.720> little<00:10:33.959> on<00:10:34.079> the<00:10:34.200> nitty 00:10:34.509 --> 00:10:34.519 align:start position:0% we have to get a little on the nitty 00:10:34.519 --> 00:10:36.910 align:start position:0% we have to get a little on the nitty grid<00:10:34.800> and<00:10:35.040> actually<00:10:35.720> break<00:10:36.079> down<00:10:36.399> what<00:10:36.639> it 00:10:36.910 --> 00:10:36.920 align:start position:0% grid and actually break down what it 00:10:36.920 --> 00:10:40.350 align:start position:0% grid and actually break down what it means<00:10:37.560> to<00:10:37.800> have<00:10:37.959> an<00:10:38.200> account<00:10:38.880> so<00:10:39.440> the<00:10:39.600> same<00:10:39.880> way 00:10:40.350 --> 00:10:40.360 align:start position:0% means to have an account so the same way 00:10:40.360 --> 00:10:42.269 align:start position:0% means to have an account so the same way a<00:10:40.519> wallet<00:10:40.839> is<00:10:41.040> credential<00:10:41.639> signing<00:10:42.000> an 00:10:42.269 --> 00:10:42.279 align:start position:0% a wallet is credential signing an 00:10:42.279 --> 00:10:46.030 align:start position:0% a wallet is credential signing an account<00:10:42.920> an<00:10:43.160> account<00:10:43.639> then<00:10:44.000> is<00:10:44.760> defined<00:10:45.399> by 00:10:46.030 --> 00:10:46.040 align:start position:0% account an account then is defined by 00:10:46.040 --> 00:10:49.110 align:start position:0% account an account then is defined by who<00:10:46.240> is<00:10:46.440> the<00:10:46.639> signer<00:10:47.639> who<00:10:47.839> is<00:10:48.000> the<00:10:48.200> payer<00:10:48.920> and 00:10:49.110 --> 00:10:49.120 align:start position:0% who is the signer who is the payer and 00:10:49.120 --> 00:10:52.230 align:start position:0% who is the signer who is the payer and what<00:10:49.279> kind<00:10:49.440> of<00:10:49.600> cryptography<00:10:50.519> is<00:10:50.800> involved<00:10:51.800> um 00:10:52.230 --> 00:10:52.240 align:start position:0% what kind of cryptography is involved um 00:10:52.240 --> 00:10:54.230 align:start position:0% what kind of cryptography is involved um in<00:10:52.399> an<00:10:52.600> external<00:10:53.040> account<00:10:53.639> it's<00:10:53.839> pretty 00:10:54.230 --> 00:10:54.240 align:start position:0% in an external account it's pretty 00:10:54.240 --> 00:10:56.629 align:start position:0% in an external account it's pretty straightforward<00:10:55.040> like<00:10:55.160> you<00:10:55.360> have<00:10:56.079> the<00:10:56.279> same 00:10:56.629 --> 00:10:56.639 align:start position:0% straightforward like you have the same 00:10:56.639 --> 00:10:58.790 align:start position:0% straightforward like you have the same signer<00:10:57.200> you<00:10:57.360> have<00:10:57.560> the<00:10:57.720> same<00:10:58.040> payer<00:10:58.519> and<00:10:58.639> you 00:10:58.790 --> 00:10:58.800 align:start position:0% signer you have the same payer and you 00:10:58.800 --> 00:11:00.949 align:start position:0% signer you have the same payer and you have<00:10:58.920> the<00:10:59.279> cryptography<00:11:00.000> which<00:11:00.279> on<00:11:00.480> ethereum 00:11:00.949 --> 00:11:00.959 align:start position:0% have the cryptography which on ethereum 00:11:00.959 --> 00:11:06.150 align:start position:0% have the cryptography which on ethereum is<00:11:02.079> scsp<00:11:03.079> 256<00:11:03.800> K1<00:11:04.800> and<00:11:05.320> that's<00:11:05.560> it<00:11:05.920> like<00:11:06.079> you 00:11:06.150 --> 00:11:06.160 align:start position:0% is scsp 256 K1 and that's it like you 00:11:06.160 --> 00:11:07.670 align:start position:0% is scsp 256 K1 and that's it like you don't<00:11:06.440> have<00:11:06.600> an<00:11:06.760> option<00:11:07.040> this<00:11:07.160> is<00:11:07.399> what<00:11:07.519> an 00:11:07.670 --> 00:11:07.680 align:start position:0% don't have an option this is what an 00:11:07.680 --> 00:11:09.949 align:start position:0% don't have an option this is what an external<00:11:08.079> account<00:11:08.399> is<00:11:08.600> on<00:11:08.839> ethereum<00:11:09.519> and<00:11:09.839> this 00:11:09.949 --> 00:11:09.959 align:start position:0% external account is on ethereum and this 00:11:09.959 --> 00:11:11.269 align:start position:0% external account is on ethereum and this is<00:11:10.160> what<00:11:10.279> your<00:11:10.440> external<00:11:10.839> account<00:11:11.079> is<00:11:11.200> going 00:11:11.269 --> 00:11:11.279 align:start position:0% is what your external account is going 00:11:11.279 --> 00:11:13.509 align:start position:0% is what your external account is going to<00:11:11.440> do<00:11:12.160> with<00:11:12.360> a<00:11:12.480> smart<00:11:12.800> account<00:11:13.120> actually<00:11:13.399> this 00:11:13.509 --> 00:11:13.519 align:start position:0% to do with a smart account actually this 00:11:13.519 --> 00:11:15.110 align:start position:0% to do with a smart account actually this is<00:11:13.639> a<00:11:13.760> little<00:11:13.920> bit<00:11:14.079> more<00:11:14.279> flexible<00:11:14.839> now<00:11:15.000> we 00:11:15.110 --> 00:11:15.120 align:start position:0% is a little bit more flexible now we 00:11:15.120 --> 00:11:16.629 align:start position:0% is a little bit more flexible now we have<00:11:15.320> a<00:11:15.440> smart<00:11:15.720> contract<00:11:16.160> where<00:11:16.320> we<00:11:16.440> can 00:11:16.629 --> 00:11:16.639 align:start position:0% have a smart contract where we can 00:11:16.639 --> 00:11:18.949 align:start position:0% have a smart contract where we can encode<00:11:17.160> logic<00:11:17.920> that<00:11:18.079> allows<00:11:18.440> you<00:11:18.600> to<00:11:18.800> have 00:11:18.949 --> 00:11:18.959 align:start position:0% encode logic that allows you to have 00:11:18.959 --> 00:11:20.670 align:start position:0% encode logic that allows you to have more<00:11:19.480> programmability<00:11:20.480> this 00:11:20.670 --> 00:11:20.680 align:start position:0% more programmability this 00:11:20.680 --> 00:11:22.790 align:start position:0% more programmability this programmability<00:11:21.360> can<00:11:21.480> be<00:11:21.720> many<00:11:22.000> things<00:11:22.519> but 00:11:22.790 --> 00:11:22.800 align:start position:0% programmability can be many things but 00:11:22.800 --> 00:11:24.870 align:start position:0% programmability can be many things but at<00:11:22.959> the<00:11:23.200> core<00:11:23.639> of<00:11:23.839> smart<00:11:24.160> accounts<00:11:24.519> it<00:11:24.639> means 00:11:24.870 --> 00:11:24.880 align:start position:0% at the core of smart accounts it means 00:11:24.880 --> 00:11:26.870 align:start position:0% at the core of smart accounts it means that<00:11:25.000> you<00:11:25.079> can<00:11:25.200> have<00:11:25.360> multiple<00:11:25.880> signers 00:11:26.870 --> 00:11:26.880 align:start position:0% that you can have multiple signers 00:11:26.880 --> 00:11:28.829 align:start position:0% that you can have multiple signers multiple<00:11:27.240> signers<00:11:27.680> does<00:11:27.839> not<00:11:28.240> necessarily 00:11:28.829 --> 00:11:28.839 align:start position:0% multiple signers does not necessarily 00:11:28.839 --> 00:11:31.069 align:start position:0% multiple signers does not necessarily mean<00:11:29.320> that's<00:11:29.440> a<00:11:29.560> multisig<00:11:30.279> the<00:11:30.440> reason<00:11:30.720> I<00:11:30.880> try 00:11:31.069 --> 00:11:31.079 align:start position:0% mean that's a multisig the reason I try 00:11:31.079 --> 00:11:32.790 align:start position:0% mean that's a multisig the reason I try to<00:11:31.240> not<00:11:31.480> call<00:11:31.639> it<00:11:31.760> a<00:11:31.839> multisig<00:11:32.519> because 00:11:32.790 --> 00:11:32.800 align:start position:0% to not call it a multisig because 00:11:32.800 --> 00:11:34.790 align:start position:0% to not call it a multisig because there's<00:11:33.000> a<00:11:33.200> preconception<00:11:33.959> about<00:11:34.160> multisig 00:11:34.790 --> 00:11:34.800 align:start position:0% there's a preconception about multisig 00:11:34.800 --> 00:11:37.550 align:start position:0% there's a preconception about multisig being<00:11:35.399> multi-party<00:11:36.399> and<00:11:36.600> that<00:11:36.720> means<00:11:37.040> oh<00:11:37.320> you 00:11:37.550 --> 00:11:37.560 align:start position:0% being multi-party and that means oh you 00:11:37.560 --> 00:11:39.910 align:start position:0% being multi-party and that means oh you have<00:11:38.120> multiple<00:11:38.680> people<00:11:39.040> signing<00:11:39.480> for<00:11:39.800> the 00:11:39.910 --> 00:11:39.920 align:start position:0% have multiple people signing for the 00:11:39.920 --> 00:11:42.230 align:start position:0% have multiple people signing for the smart<00:11:40.240> account<00:11:40.560> therefore<00:11:41.000> this<00:11:41.120> is<00:11:41.320> like<00:11:41.920> a 00:11:42.230 --> 00:11:42.240 align:start position:0% smart account therefore this is like a 00:11:42.240 --> 00:11:44.150 align:start position:0% smart account therefore this is like a business<00:11:42.760> account<00:11:43.200> no<00:11:43.360> it's<00:11:43.519> not<00:11:43.639> a<00:11:43.800> business 00:11:44.150 --> 00:11:44.160 align:start position:0% business account no it's not a business 00:11:44.160 --> 00:11:47.030 align:start position:0% business account no it's not a business account<00:11:44.920> you<00:11:45.200> would<00:11:45.519> have<00:11:46.040> a<00:11:46.279> multiple 00:11:47.030 --> 00:11:47.040 align:start position:0% account you would have a multiple 00:11:47.040 --> 00:11:50.430 align:start position:0% account you would have a multiple signatures<00:11:47.920> by<00:11:48.560> using<00:11:49.079> your<00:11:49.600> account<00:11:50.120> in<00:11:50.279> a 00:11:50.430 --> 00:11:50.440 align:start position:0% signatures by using your account in a 00:11:50.440 --> 00:11:52.230 align:start position:0% signatures by using your account in a mobile<00:11:50.720> phone<00:11:50.959> and<00:11:51.120> a<00:11:51.279> desktop<00:11:51.880> that<00:11:52.079> in 00:11:52.230 --> 00:11:52.240 align:start position:0% mobile phone and a desktop that in 00:11:52.240 --> 00:11:54.550 align:start position:0% mobile phone and a desktop that in itself<00:11:52.600> already<00:11:52.959> provides<00:11:53.440> you<00:11:53.600> with<00:11:53.800> like<00:11:54.320> a 00:11:54.550 --> 00:11:54.560 align:start position:0% itself already provides you with like a 00:11:54.560 --> 00:11:56.430 align:start position:0% itself already provides you with like a good<00:11:54.839> reason<00:11:55.240> why<00:11:55.360> you<00:11:55.480> need<00:11:55.639> a<00:11:55.800> smart<00:11:56.079> account 00:11:56.430 --> 00:11:56.440 align:start position:0% good reason why you need a smart account 00:11:56.440 --> 00:11:58.030 align:start position:0% good reason why you need a smart account because<00:11:56.639> you<00:11:56.760> don't<00:11:56.880> want<00:11:57.000> to<00:11:57.200> move<00:11:57.480> your<00:11:57.720> keys 00:11:58.030 --> 00:11:58.040 align:start position:0% because you don't want to move your keys 00:11:58.040 --> 00:11:59.790 align:start position:0% because you don't want to move your keys around<00:11:58.399> with<00:11:58.560> different<00:11:58.839> devices 00:11:59.790 --> 00:11:59.800 align:start position:0% around with different devices 00:11:59.800 --> 00:12:01.670 align:start position:0% around with different devices or<00:12:00.079> you<00:12:00.240> might<00:12:00.480> even<00:12:00.680> want<00:12:00.839> to<00:12:01.040> do<00:12:01.399> something 00:12:01.670 --> 00:12:01.680 align:start position:0% or you might even want to do something 00:12:01.680 --> 00:12:04.430 align:start position:0% or you might even want to do something more<00:12:01.920> complex<00:12:02.560> where<00:12:02.839> you<00:12:03.079> have<00:12:03.800> a<00:12:04.000> secret 00:12:04.430 --> 00:12:04.440 align:start position:0% more complex where you have a secret 00:12:04.440 --> 00:12:07.110 align:start position:0% more complex where you have a secret recovery<00:12:04.880> phrase<00:12:05.440> that<00:12:05.639> you<00:12:06.160> own<00:12:06.639> in<00:12:06.760> a<00:12:06.920> piece 00:12:07.110 --> 00:12:07.120 align:start position:0% recovery phrase that you own in a piece 00:12:07.120 --> 00:12:09.949 align:start position:0% recovery phrase that you own in a piece of<00:12:07.360> paper<00:12:07.680> for<00:12:08.000> security<00:12:08.959> and<00:12:09.079> then<00:12:09.240> you<00:12:09.560> have 00:12:09.949 --> 00:12:09.959 align:start position:0% of paper for security and then you have 00:12:09.959 --> 00:12:12.230 align:start position:0% of paper for security and then you have like<00:12:10.200> one<00:12:10.399> in<00:12:10.560> your<00:12:10.839> device<00:12:11.480> and<00:12:11.720> one<00:12:11.920> in<00:12:12.040> the 00:12:12.230 --> 00:12:12.240 align:start position:0% like one in your device and one in the 00:12:12.240 --> 00:12:13.870 align:start position:0% like one in your device and one in the desktop<00:12:12.680> and<00:12:12.800> you<00:12:12.880> use<00:12:13.120> like<00:12:13.240> two<00:12:13.480> Factor 00:12:13.870 --> 00:12:13.880 align:start position:0% desktop and you use like two Factor 00:12:13.880 --> 00:12:16.310 align:start position:0% desktop and you use like two Factor authentication<00:12:14.880> so<00:12:15.120> this<00:12:15.760> idea<00:12:16.120> of 00:12:16.310 --> 00:12:16.320 align:start position:0% authentication so this idea of 00:12:16.320 --> 00:12:19.430 align:start position:0% authentication so this idea of programmability<00:12:17.279> makes<00:12:17.639> for<00:12:18.320> more<00:12:18.760> security 00:12:19.430 --> 00:12:19.440 align:start position:0% programmability makes for more security 00:12:19.440 --> 00:12:21.629 align:start position:0% programmability makes for more security and<00:12:19.760> convenience<00:12:20.279> at<00:12:20.399> the<00:12:20.519> same<00:12:20.800> time<00:12:21.279> so<00:12:21.480> we 00:12:21.629 --> 00:12:21.639 align:start position:0% and convenience at the same time so we 00:12:21.639 --> 00:12:23.750 align:start position:0% and convenience at the same time so we really<00:12:21.880> find<00:12:22.160> the<00:12:22.320> balance<00:12:22.760> here<00:12:22.959> with<00:12:23.199> smart 00:12:23.750 --> 00:12:23.760 align:start position:0% really find the balance here with smart 00:12:23.760 --> 00:12:26.470 align:start position:0% really find the balance here with smart accounts<00:12:24.760> another<00:12:25.160> convenience<00:12:25.720> feature<00:12:26.279> is 00:12:26.470 --> 00:12:26.480 align:start position:0% accounts another convenience feature is 00:12:26.480 --> 00:12:29.629 align:start position:0% accounts another convenience feature is that<00:12:27.040> we<00:12:27.240> now<00:12:27.680> detached<00:12:28.320> ourselves<00:12:28.839> from<00:12:29.440> the 00:12:29.629 --> 00:12:29.639 align:start position:0% that we now detached ourselves from the 00:12:29.639 --> 00:12:32.350 align:start position:0% that we now detached ourselves from the signer<00:12:30.199> always<00:12:30.560> have<00:12:30.800> to<00:12:31.079> pay<00:12:31.839> and<00:12:32.000> what<00:12:32.160> does 00:12:32.350 --> 00:12:32.360 align:start position:0% signer always have to pay and what does 00:12:32.360 --> 00:12:34.670 align:start position:0% signer always have to pay and what does that<00:12:32.519> mean<00:12:32.920> you<00:12:33.079> know<00:12:33.480> everyone<00:12:34.399> understands 00:12:34.670 --> 00:12:34.680 align:start position:0% that mean you know everyone understands 00:12:34.680 --> 00:12:36.509 align:start position:0% that mean you know everyone understands here<00:12:34.880> that<00:12:35.040> blockchains<00:12:35.600> have<00:12:35.800> fees<00:12:36.320> and 00:12:36.509 --> 00:12:36.519 align:start position:0% here that blockchains have fees and 00:12:36.519 --> 00:12:39.230 align:start position:0% here that blockchains have fees and these<00:12:36.720> fees<00:12:36.959> are<00:12:37.240> called<00:12:37.680> gas<00:12:38.560> and<00:12:38.800> in<00:12:38.959> order 00:12:39.230 --> 00:12:39.240 align:start position:0% these fees are called gas and in order 00:12:39.240 --> 00:12:41.910 align:start position:0% these fees are called gas and in order for<00:12:39.480> you<00:12:39.720> to<00:12:39.959> pay<00:12:40.199> for<00:12:40.600> that<00:12:40.880> gas<00:12:41.320> you<00:12:41.600> have<00:12:41.760> to 00:12:41.910 --> 00:12:41.920 align:start position:0% for you to pay for that gas you have to 00:12:41.920 --> 00:12:44.670 align:start position:0% for you to pay for that gas you have to be<00:12:42.240> both<00:12:42.519> the<00:12:42.720> signature<00:12:43.279> and<00:12:43.399> the<00:12:43.560> payer<00:12:44.440> but 00:12:44.670 --> 00:12:44.680 align:start position:0% be both the signature and the payer but 00:12:44.680 --> 00:12:46.829 align:start position:0% be both the signature and the payer but what<00:12:44.839> if<00:12:44.959> you<00:12:45.199> could<00:12:45.440> actually<00:12:45.760> have<00:12:46.360> another 00:12:46.829 --> 00:12:46.839 align:start position:0% what if you could actually have another 00:12:46.839 --> 00:12:49.790 align:start position:0% what if you could actually have another account<00:12:47.199> pay<00:12:47.639> or<00:12:48.000> maybe<00:12:48.360> even<00:12:48.720> you<00:12:49.120> pay<00:12:49.639> but 00:12:49.790 --> 00:12:49.800 align:start position:0% account pay or maybe even you pay but 00:12:49.800 --> 00:12:51.750 align:start position:0% account pay or maybe even you pay but with<00:12:49.959> a<00:12:50.120> different<00:12:50.480> token<00:12:51.240> with<00:12:51.440> smart 00:12:51.750 --> 00:12:51.760 align:start position:0% with a different token with smart 00:12:51.760 --> 00:12:53.350 align:start position:0% with a different token with smart accounts<00:12:52.040> you<00:12:52.160> can<00:12:52.320> actually<00:12:52.600> program<00:12:53.000> that 00:12:53.350 --> 00:12:53.360 align:start position:0% accounts you can actually program that 00:12:53.360 --> 00:12:55.670 align:start position:0% accounts you can actually program that information<00:12:54.360> so<00:12:54.639> smart<00:12:55.000> accounts<00:12:55.320> not<00:12:55.440> only 00:12:55.670 --> 00:12:55.680 align:start position:0% information so smart accounts not only 00:12:55.680 --> 00:12:57.550 align:start position:0% information so smart accounts not only allows<00:12:55.920> you<00:12:56.040> to<00:12:56.160> have<00:12:56.320> flexibility<00:12:56.959> of<00:12:57.360> having 00:12:57.550 --> 00:12:57.560 align:start position:0% allows you to have flexibility of having 00:12:57.560 --> 00:13:00.069 align:start position:0% allows you to have flexibility of having multiple<00:12:57.959> signers<00:12:58.760> but<00:12:58.880> then<00:12:59.199> it<00:12:59.360> also<00:12:59.600> means 00:13:00.069 --> 00:13:00.079 align:start position:0% multiple signers but then it also means 00:13:00.079 --> 00:13:02.389 align:start position:0% multiple signers but then it also means that<00:13:00.279> you<00:13:00.399> can<00:13:00.680> have<00:13:01.079> a<00:13:01.279> different<00:13:01.680> payer<00:13:02.199> than 00:13:02.389 --> 00:13:02.399 align:start position:0% that you can have a different payer than 00:13:02.399 --> 00:13:04.670 align:start position:0% that you can have a different payer than the<00:13:02.600> signer<00:13:03.240> and<00:13:03.399> maybe<00:13:03.680> even<00:13:04.000> you<00:13:04.120> don't<00:13:04.399> pay 00:13:04.670 --> 00:13:04.680 align:start position:0% the signer and maybe even you don't pay 00:13:04.680 --> 00:13:07.269 align:start position:0% the signer and maybe even you don't pay someone<00:13:04.959> else<00:13:05.240> pays<00:13:06.120> and<00:13:06.399> finally<00:13:07.160> the 00:13:07.269 --> 00:13:07.279 align:start position:0% someone else pays and finally the 00:13:07.279 --> 00:13:09.269 align:start position:0% someone else pays and finally the cryptography<00:13:08.160> like<00:13:08.519> the<00:13:08.800> actual 00:13:09.269 --> 00:13:09.279 align:start position:0% cryptography like the actual 00:13:09.279 --> 00:13:12.310 align:start position:0% cryptography like the actual cryptographic<00:13:10.000> curves<00:13:10.560> can<00:13:10.760> be<00:13:11.320> infinite 00:13:12.310 --> 00:13:12.320 align:start position:0% cryptographic curves can be infinite 00:13:12.320 --> 00:13:14.430 align:start position:0% cryptographic curves can be infinite well<00:13:12.639> infinite<00:13:13.079> not<00:13:13.240> so<00:13:13.480> much<00:13:13.800> because<00:13:14.279> the 00:13:14.430 --> 00:13:14.440 align:start position:0% well infinite not so much because the 00:13:14.440 --> 00:13:16.790 align:start position:0% well infinite not so much because the more<00:13:15.279> contract<00:13:15.720> logic<00:13:16.120> that<00:13:16.240> you<00:13:16.399> add<00:13:16.639> into 00:13:16.790 --> 00:13:16.800 align:start position:0% more contract logic that you add into 00:13:16.800 --> 00:13:18.509 align:start position:0% more contract logic that you add into your<00:13:16.959> smart<00:13:17.240> contract<00:13:17.680> the<00:13:17.800> higher<00:13:18.079> the<00:13:18.240> gas 00:13:18.509 --> 00:13:18.519 align:start position:0% your smart contract the higher the gas 00:13:18.519 --> 00:13:20.389 align:start position:0% your smart contract the higher the gas cost<00:13:18.880> but<00:13:19.120> you<00:13:19.240> get<00:13:19.360> the<00:13:19.560> picture<00:13:19.920> it's<00:13:20.240> way 00:13:20.389 --> 00:13:20.399 align:start position:0% cost but you get the picture it's way 00:13:20.399 --> 00:13:22.550 align:start position:0% cost but you get the picture it's way more<00:13:20.639> flexible<00:13:21.519> and<00:13:21.639> if<00:13:21.760> it's<00:13:21.920> more<00:13:22.120> flexible 00:13:22.550 --> 00:13:22.560 align:start position:0% more flexible and if it's more flexible 00:13:22.560 --> 00:13:23.750 align:start position:0% more flexible and if it's more flexible it<00:13:22.680> means<00:13:22.880> that<00:13:23.000> we<00:13:23.079> can<00:13:23.279> actually<00:13:23.519> get<00:13:23.680> a 00:13:23.750 --> 00:13:23.760 align:start position:0% it means that we can actually get a 00:13:23.760 --> 00:13:25.910 align:start position:0% it means that we can actually get a little<00:13:23.959> more<00:13:24.240> creative<00:13:24.880> like<00:13:25.440> I<00:13:25.519> don't<00:13:25.680> know 00:13:25.910 --> 00:13:25.920 align:start position:0% little more creative like I don't know 00:13:25.920 --> 00:13:27.750 align:start position:0% little more creative like I don't know how<00:13:26.079> much<00:13:26.240> you<00:13:26.399> know<00:13:26.639> about<00:13:26.920> cryptography<00:13:27.600> but 00:13:27.750 --> 00:13:27.760 align:start position:0% how much you know about cryptography but 00:13:27.760 --> 00:13:30.870 align:start position:0% how much you know about cryptography but 256<00:13:28.560> K1<00:13:29.399> the<00:13:29.560> curve<00:13:29.760> of<00:13:29.920> ethereum<00:13:30.399> is<00:13:30.600> actually 00:13:30.870 --> 00:13:30.880 align:start position:0% 256 K1 the curve of ethereum is actually 00:13:30.880 --> 00:13:33.590 align:start position:0% 256 K1 the curve of ethereum is actually not<00:13:31.240> that<00:13:31.519> popular<00:13:32.199> that's<00:13:32.399> how<00:13:33.079> we<00:13:33.279> like<00:13:33.440> to 00:13:33.590 --> 00:13:33.600 align:start position:0% not that popular that's how we like to 00:13:33.600 --> 00:13:35.350 align:start position:0% not that popular that's how we like to reinvent<00:13:34.120> the<00:13:34.240> wheel<00:13:34.560> kind<00:13:34.720> of<00:13:34.880> thing<00:13:35.079> we<00:13:35.240> kind 00:13:35.350 --> 00:13:35.360 align:start position:0% reinvent the wheel kind of thing we kind 00:13:35.360 --> 00:13:37.790 align:start position:0% reinvent the wheel kind of thing we kind of<00:13:35.519> like<00:13:35.680> to<00:13:35.839> use<00:13:36.600> things<00:13:36.920> that<00:13:37.199> nobody<00:13:37.560> else 00:13:37.790 --> 00:13:37.800 align:start position:0% of like to use things that nobody else 00:13:37.800 --> 00:13:40.389 align:start position:0% of like to use things that nobody else uses<00:13:38.320> but<00:13:38.560> all<00:13:38.720> of<00:13:38.839> your<00:13:39.000> phones<00:13:39.480> actually<00:13:39.760> use 00:13:40.389 --> 00:13:40.399 align:start position:0% uses but all of your phones actually use 00:13:40.399 --> 00:13:42.110 align:start position:0% uses but all of your phones actually use uh<00:13:40.519> other<00:13:40.800> crypto<00:13:41.160> caric<00:13:41.480> curves<00:13:41.839> like<00:13:41.959> for 00:13:42.110 --> 00:13:42.120 align:start position:0% uh other crypto caric curves like for 00:13:42.120 --> 00:13:45.550 align:start position:0% uh other crypto caric curves like for example<00:13:42.880> one<00:13:43.120> that's<00:13:43.320> called<00:13:44.040> p256<00:13:45.040> uh<00:13:45.320> which 00:13:45.550 --> 00:13:45.560 align:start position:0% example one that's called p256 uh which 00:13:45.560 --> 00:13:47.590 align:start position:0% example one that's called p256 uh which most<00:13:45.800> people<00:13:46.120> now<00:13:46.360> know<00:13:46.639> today<00:13:46.959> as<00:13:47.120> the<00:13:47.320> curve 00:13:47.590 --> 00:13:47.600 align:start position:0% most people now know today as the curve 00:13:47.600 --> 00:13:49.590 align:start position:0% most people now know today as the curve that's<00:13:47.800> used<00:13:48.000> for<00:13:48.199> pass<00:13:48.519> keys<00:13:49.120> so<00:13:49.279> what<00:13:49.399> if<00:13:49.519> you 00:13:49.590 --> 00:13:49.600 align:start position:0% that's used for pass keys so what if you 00:13:49.600 --> 00:13:51.470 align:start position:0% that's used for pass keys so what if you could<00:13:49.839> actually<00:13:50.079> use<00:13:50.440> pass<00:13:50.759> keys<00:13:51.000> to<00:13:51.160> control 00:13:51.470 --> 00:13:51.480 align:start position:0% could actually use pass keys to control 00:13:51.480 --> 00:13:53.389 align:start position:0% could actually use pass keys to control your<00:13:51.600> smart<00:13:51.959> account<00:13:52.560> now<00:13:52.720> we're<00:13:52.880> getting 00:13:53.389 --> 00:13:53.399 align:start position:0% your smart account now we're getting 00:13:53.399 --> 00:13:55.269 align:start position:0% your smart account now we're getting really<00:13:53.720> convenient<00:13:54.360> because<00:13:54.600> now<00:13:54.720> I<00:13:54.839> can<00:13:55.040> have 00:13:55.269 --> 00:13:55.279 align:start position:0% really convenient because now I can have 00:13:55.279 --> 00:13:57.670 align:start position:0% really convenient because now I can have pass<00:13:55.600> keys<00:13:56.120> in<00:13:56.360> different<00:13:56.680> devices<00:13:57.360> they<00:13:57.480> all 00:13:57.670 --> 00:13:57.680 align:start position:0% pass keys in different devices they all 00:13:57.680 --> 00:14:00.030 align:start position:0% pass keys in different devices they all control<00:13:58.079> the<00:13:58.240> SM<00:13:58.600> the<00:13:58.680> same<00:13:59.120> smart<00:13:59.399> account 00:14:00.030 --> 00:14:00.040 align:start position:0% control the SM the same smart account 00:14:00.040 --> 00:14:02.269 align:start position:0% control the SM the same smart account and<00:14:00.199> I<00:14:00.320> don't<00:14:00.519> even<00:14:00.720> need<00:14:00.880> to<00:14:01.040> pay<00:14:01.199> for<00:14:01.360> the<00:14:01.519> gas 00:14:02.269 --> 00:14:02.279 align:start position:0% and I don't even need to pay for the gas 00:14:02.279 --> 00:14:04.310 align:start position:0% and I don't even need to pay for the gas this<00:14:02.440> is<00:14:02.639> getting<00:14:02.959> a<00:14:03.079> little<00:14:03.399> too<00:14:03.639> good<00:14:03.800> to<00:14:03.959> be 00:14:04.310 --> 00:14:04.320 align:start position:0% this is getting a little too good to be 00:14:04.320 --> 00:14:06.829 align:start position:0% this is getting a little too good to be true<00:14:05.320> uh<00:14:05.600> but<00:14:05.880> at<00:14:06.000> the<00:14:06.079> end<00:14:06.240> of<00:14:06.320> the<00:14:06.519> day<00:14:06.759> you 00:14:06.829 --> 00:14:06.839 align:start position:0% true uh but at the end of the day you 00:14:06.839 --> 00:14:09.269 align:start position:0% true uh but at the end of the day you could<00:14:07.120> imagine<00:14:07.560> that<00:14:07.839> like<00:14:08.639> you<00:14:08.759> would<00:14:09.040> have 00:14:09.269 --> 00:14:09.279 align:start position:0% could imagine that like you would have 00:14:09.279 --> 00:14:11.110 align:start position:0% could imagine that like you would have like<00:14:09.480> multiple<00:14:10.040> wallets<00:14:10.720> and<00:14:10.839> you<00:14:10.959> would 00:14:11.110 --> 00:14:11.120 align:start position:0% like multiple wallets and you would 00:14:11.120 --> 00:14:12.710 align:start position:0% like multiple wallets and you would interact<00:14:11.480> with<00:14:11.639> multiple<00:14:12.040> apps<00:14:12.360> but<00:14:12.480> they're 00:14:12.710 --> 00:14:12.720 align:start position:0% interact with multiple apps but they're 00:14:12.720 --> 00:14:15.870 align:start position:0% interact with multiple apps but they're all<00:14:12.920> under<00:14:13.279> the<00:14:13.480> same<00:14:13.880> blockchain<00:14:14.880> but<00:14:15.720> what 00:14:15.870 --> 00:14:15.880 align:start position:0% all under the same blockchain but what 00:14:15.880 --> 00:14:18.150 align:start position:0% all under the same blockchain but what if<00:14:16.040> you<00:14:16.199> could<00:14:16.399> just<00:14:16.680> have<00:14:16.959> like<00:14:17.279> one<00:14:17.720> smart 00:14:18.150 --> 00:14:18.160 align:start position:0% if you could just have like one smart 00:14:18.160 --> 00:14:20.590 align:start position:0% if you could just have like one smart account<00:14:18.800> everywhere<00:14:19.320> it<00:14:19.440> just<00:14:19.600> kind<00:14:19.720> of<00:14:19.959> like 00:14:20.590 --> 00:14:20.600 align:start position:0% account everywhere it just kind of like 00:14:20.600 --> 00:14:23.670 align:start position:0% account everywhere it just kind of like covered<00:14:21.320> everything<00:14:22.320> that<00:14:22.519> you<00:14:22.680> would<00:14:23.079> touch 00:14:23.670 --> 00:14:23.680 align:start position:0% covered everything that you would touch 00:14:23.680 --> 00:14:25.870 align:start position:0% covered everything that you would touch because<00:14:23.920> you<00:14:24.079> have<00:14:24.399> multiple<00:14:25.000> devices<00:14:25.680> with 00:14:25.870 --> 00:14:25.880 align:start position:0% because you have multiple devices with 00:14:25.880 --> 00:14:28.590 align:start position:0% because you have multiple devices with like<00:14:26.199> multiple<00:14:26.680> signers<00:14:27.399> and<00:14:27.800> you<00:14:28.000> share<00:14:28.399> the 00:14:28.590 --> 00:14:28.600 align:start position:0% like multiple signers and you share the 00:14:28.600 --> 00:14:31.350 align:start position:0% like multiple signers and you share the gas<00:14:29.160> you<00:14:29.240> can<00:14:29.360> use<00:14:29.600> passies<00:14:30.160> if<00:14:30.279> you<00:14:30.399> want<00:14:31.160> it 00:14:31.350 --> 00:14:31.360 align:start position:0% gas you can use passies if you want it 00:14:31.360 --> 00:14:33.150 align:start position:0% gas you can use passies if you want it really<00:14:31.560> would<00:14:31.839> become<00:14:32.240> this<00:14:32.440> like<00:14:32.720> truly 00:14:33.150 --> 00:14:33.160 align:start position:0% really would become this like truly 00:14:33.160 --> 00:14:35.150 align:start position:0% really would become this like truly Universal<00:14:33.800> account<00:14:34.199> which<00:14:34.360> smart<00:14:34.759> accounts 00:14:35.150 --> 00:14:35.160 align:start position:0% Universal account which smart accounts 00:14:35.160 --> 00:14:37.230 align:start position:0% Universal account which smart accounts really<00:14:35.399> enable<00:14:35.880> that<00:14:36.120> experience<00:14:36.959> and<00:14:37.120> this 00:14:37.230 --> 00:14:37.240 align:start position:0% really enable that experience and this 00:14:37.240 --> 00:14:38.470 align:start position:0% really enable that experience and this is<00:14:37.360> where<00:14:37.480> the<00:14:37.600> terminology<00:14:38.240> account 00:14:38.470 --> 00:14:38.480 align:start position:0% is where the terminology account 00:14:38.480 --> 00:14:40.069 align:start position:0% is where the terminology account obstruction<00:14:38.920> comes<00:14:39.160> in<00:14:39.440> like<00:14:39.800> account 00:14:40.069 --> 00:14:40.079 align:start position:0% obstruction comes in like account 00:14:40.079 --> 00:14:43.069 align:start position:0% obstruction comes in like account abstraction<00:14:40.560> in<00:14:40.680> a<00:14:40.880> way<00:14:41.160> it's<00:14:41.399> like<00:14:41.519> a<00:14:42.079> mindset 00:14:43.069 --> 00:14:43.079 align:start position:0% abstraction in a way it's like a mindset 00:14:43.079 --> 00:14:45.230 align:start position:0% abstraction in a way it's like a mindset it's<00:14:43.199> a<00:14:43.440> framework<00:14:43.920> for<00:14:44.079> you<00:14:44.199> to<00:14:44.440> think<00:14:44.800> about 00:14:45.230 --> 00:14:45.240 align:start position:0% it's a framework for you to think about 00:14:45.240 --> 00:14:47.910 align:start position:0% it's a framework for you to think about how<00:14:45.440> can<00:14:45.720> we<00:14:46.040> detach<00:14:47.040> As<00:14:47.240> Much<00:14:47.519> from<00:14:47.720> the 00:14:47.910 --> 00:14:47.920 align:start position:0% how can we detach As Much from the 00:14:47.920 --> 00:14:49.829 align:start position:0% how can we detach As Much from the limitations<00:14:48.560> of<00:14:48.720> the<00:14:48.839> blockchain<00:14:49.399> such<00:14:49.639> that 00:14:49.829 --> 00:14:49.839 align:start position:0% limitations of the blockchain such that 00:14:49.839 --> 00:14:52.030 align:start position:0% limitations of the blockchain such that my<00:14:50.079> account<00:14:50.440> can<00:14:50.600> be<00:14:50.759> more<00:14:51.040> programmable<00:14:51.759> more 00:14:52.030 --> 00:14:52.040 align:start position:0% my account can be more programmable more 00:14:52.040 --> 00:14:54.990 align:start position:0% my account can be more programmable more convenient<00:14:52.680> and<00:14:52.839> still<00:14:53.519> secure<00:14:54.519> and<00:14:54.680> this<00:14:54.800> all 00:14:54.990 --> 00:14:55.000 align:start position:0% convenient and still secure and this all 00:14:55.000 --> 00:14:57.629 align:start position:0% convenient and still secure and this all started<00:14:55.600> about<00:14:56.320> two<00:14:56.560> or<00:14:56.720> 3<00:14:56.920> years<00:14:57.160> ago<00:14:57.480> with 00:14:57.629 --> 00:14:57.639 align:start position:0% started about two or 3 years ago with 00:14:57.639 --> 00:14:59.150 align:start position:0% started about two or 3 years ago with 4237 00:14:59.150 --> 00:14:59.160 align:start position:0% 4237 00:14:59.160 --> 00:15:01.389 align:start position:0% 4237 um<00:14:59.440> which<00:14:59.759> basically<00:15:00.160> its<00:15:00.399> title<00:15:00.759> says 00:15:01.389 --> 00:15:01.399 align:start position:0% um which basically its title says 00:15:01.399 --> 00:15:03.990 align:start position:0% um which basically its title says account<00:15:01.759> obstruction<00:15:02.279> using<00:15:02.560> alt<00:15:02.839> mle<00:15:03.600> which 00:15:03.990 --> 00:15:04.000 align:start position:0% account obstruction using alt mle which 00:15:04.000 --> 00:15:05.509 align:start position:0% account obstruction using alt mle which I<00:15:04.079> don't<00:15:04.240> think<00:15:04.399> we<00:15:04.560> really<00:15:04.759> need<00:15:04.920> to<00:15:05.079> get<00:15:05.240> into 00:15:05.509 --> 00:15:05.519 align:start position:0% I don't think we really need to get into 00:15:05.519 --> 00:15:07.990 align:start position:0% I don't think we really need to get into that<00:15:06.079> but<00:15:06.360> in<00:15:06.480> the<00:15:06.680> diagram<00:15:07.360> what<00:15:07.480> it<00:15:07.600> means 00:15:07.990 --> 00:15:08.000 align:start position:0% that but in the diagram what it means 00:15:08.000 --> 00:15:10.550 align:start position:0% that but in the diagram what it means that<00:15:08.279> before<00:15:08.680> remember<00:15:09.199> we<00:15:09.399> had<00:15:09.600> the<00:15:09.839> triangle 00:15:10.550 --> 00:15:10.560 align:start position:0% that before remember we had the triangle 00:15:10.560 --> 00:15:13.110 align:start position:0% that before remember we had the triangle of<00:15:10.720> the<00:15:10.880> app<00:15:11.320> wallet<00:15:11.680> and<00:15:12.000> blockchain<00:15:13.000> uh 00:15:13.110 --> 00:15:13.120 align:start position:0% of the app wallet and blockchain uh 00:15:13.120 --> 00:15:14.189 align:start position:0% of the app wallet and blockchain uh things<00:15:13.279> are<00:15:13.440> starting<00:15:13.720> to<00:15:13.839> get<00:15:14.000> more 00:15:14.189 --> 00:15:14.199 align:start position:0% things are starting to get more 00:15:14.199 --> 00:15:16.509 align:start position:0% things are starting to get more complicated<00:15:14.759> now<00:15:15.120> right<00:15:15.320> because<00:15:15.560> I<00:15:15.680> told<00:15:15.959> you 00:15:16.509 --> 00:15:16.519 align:start position:0% complicated now right because I told you 00:15:16.519 --> 00:15:18.189 align:start position:0% complicated now right because I told you now<00:15:16.680> we<00:15:16.800> have<00:15:16.920> multiple<00:15:17.279> signers<00:15:17.720> so<00:15:17.880> now<00:15:18.079> the 00:15:18.189 --> 00:15:18.199 align:start position:0% now we have multiple signers so now the 00:15:18.199 --> 00:15:20.749 align:start position:0% now we have multiple signers so now the signer<00:15:18.880> doesn't<00:15:19.320> necessarily<00:15:19.959> need<00:15:20.199> to<00:15:20.399> be<00:15:20.600> in 00:15:20.749 --> 00:15:20.759 align:start position:0% signer doesn't necessarily need to be in 00:15:20.759 --> 00:15:23.990 align:start position:0% signer doesn't necessarily need to be in the<00:15:20.959> wallet<00:15:21.600> so<00:15:21.959> it's<00:15:22.199> its<00:15:22.440> own<00:15:22.800> component<00:15:23.759> and 00:15:23.990 --> 00:15:24.000 align:start position:0% the wallet so it's its own component and 00:15:24.000 --> 00:15:26.670 align:start position:0% the wallet so it's its own component and you<00:15:24.240> also<00:15:24.519> are<00:15:24.759> not<00:15:24.959> a<00:15:25.160> payer<00:15:25.560> so<00:15:25.800> now<00:15:26.360> in 00:15:26.670 --> 00:15:26.680 align:start position:0% you also are not a payer so now in 00:15:26.680 --> 00:15:28.069 align:start position:0% you also are not a payer so now in account<00:15:26.959> abstraction<00:15:27.399> we<00:15:27.519> introduced<00:15:27.920> the 00:15:28.069 --> 00:15:28.079 align:start position:0% account abstraction we introduced the 00:15:28.079 --> 00:15:30.509 align:start position:0% account abstraction we introduced the concept<00:15:28.360> of<00:15:28.480> a<00:15:28.680> pay<00:15:29.160> master<00:15:29.880> so<00:15:30.079> the<00:15:30.240> pay 00:15:30.509 --> 00:15:30.519 align:start position:0% concept of a pay master so the pay 00:15:30.519 --> 00:15:32.670 align:start position:0% concept of a pay master so the pay Master<00:15:30.839> is<00:15:30.959> now<00:15:31.160> the<00:15:31.319> payer<00:15:31.800> the<00:15:31.920> signer<00:15:32.519> is 00:15:32.670 --> 00:15:32.680 align:start position:0% Master is now the payer the signer is 00:15:32.680 --> 00:15:33.949 align:start position:0% Master is now the payer the signer is the<00:15:32.800> one<00:15:33.000> who<00:15:33.199> actually<00:15:33.440> does<00:15:33.680> the 00:15:33.949 --> 00:15:33.959 align:start position:0% the one who actually does the 00:15:33.959 --> 00:15:37.470 align:start position:0% the one who actually does the transaction<00:15:34.959> and<00:15:35.240> the<00:15:35.480> wallet<00:15:36.240> is<00:15:36.839> you<00:15:37.040> know 00:15:37.470 --> 00:15:37.480 align:start position:0% transaction and the wallet is you know 00:15:37.480 --> 00:15:40.269 align:start position:0% transaction and the wallet is you know the<00:15:37.680> thing<00:15:38.000> that<00:15:38.160> you<00:15:38.480> actually<00:15:38.839> control<00:15:39.839> so 00:15:40.269 --> 00:15:40.279 align:start position:0% the thing that you actually control so 00:15:40.279 --> 00:15:42.910 align:start position:0% the thing that you actually control so now<00:15:40.480> we<00:15:40.600> have<00:15:40.880> two<00:15:41.199> extra<00:15:41.600> components<00:15:42.560> uh<00:15:42.720> we 00:15:42.910 --> 00:15:42.920 align:start position:0% now we have two extra components uh we 00:15:42.920 --> 00:15:44.790 align:start position:0% now we have two extra components uh we made<00:15:43.160> the<00:15:43.360> experience<00:15:43.839> much<00:15:44.079> better<00:15:44.519> but<00:15:44.639> we 00:15:44.790 --> 00:15:44.800 align:start position:0% made the experience much better but we 00:15:44.800 --> 00:15:47.509 align:start position:0% made the experience much better but we also<00:15:45.120> made<00:15:45.360> everything<00:15:45.759> more<00:15:46.079> complex<00:15:47.079> and<00:15:47.360> in 00:15:47.509 --> 00:15:47.519 align:start position:0% also made everything more complex and in 00:15:47.519 --> 00:15:49.350 align:start position:0% also made everything more complex and in the<00:15:47.720> title<00:15:48.120> you<00:15:48.240> saw<00:15:48.519> that<00:15:48.639> it<00:15:48.759> said<00:15:49.040> account 00:15:49.350 --> 00:15:49.360 align:start position:0% the title you saw that it said account 00:15:49.360 --> 00:15:52.230 align:start position:0% the title you saw that it said account obstruction<00:15:49.920> using<00:15:50.240> an<00:15:50.480> ALT<00:15:50.800> men<00:15:51.120> pool<00:15:52.079> uh 00:15:52.230 --> 00:15:52.240 align:start position:0% obstruction using an ALT men pool uh 00:15:52.240 --> 00:15:54.230 align:start position:0% obstruction using an ALT men pool uh that<00:15:52.440> essentially<00:15:52.959> means<00:15:53.319> that<00:15:53.519> there's<00:15:54.040> a 00:15:54.230 --> 00:15:54.240 align:start position:0% that essentially means that there's a 00:15:54.240 --> 00:15:56.710 align:start position:0% that essentially means that there's a pool<00:15:54.600> of<00:15:54.839> transactions<00:15:55.720> that<00:15:55.880> are<00:15:56.319> ready<00:15:56.560> to 00:15:56.710 --> 00:15:56.720 align:start position:0% pool of transactions that are ready to 00:15:56.720 --> 00:15:58.550 align:start position:0% pool of transactions that are ready to go<00:15:56.920> into<00:15:57.120> the<00:15:57.240> blockchain<00:15:58.120> and<00:15:58.279> that's<00:15:58.440> the 00:15:58.550 --> 00:15:58.560 align:start position:0% go into the blockchain and that's the 00:15:58.560 --> 00:16:00.749 align:start position:0% go into the blockchain and that's the reason<00:15:59.079> called<00:15:59.319> alternative<00:16:00.120> is<00:16:00.319> because<00:16:00.600> it 00:16:00.749 --> 00:16:00.759 align:start position:0% reason called alternative is because it 00:16:00.759 --> 00:16:02.550 align:start position:0% reason called alternative is because it has<00:16:00.920> to<00:16:01.040> go<00:16:01.240> through<00:16:01.440> a<00:16:01.560> bundler<00:16:02.079> you<00:16:02.199> can<00:16:02.399> no 00:16:02.550 --> 00:16:02.560 align:start position:0% has to go through a bundler you can no 00:16:02.560 --> 00:16:05.150 align:start position:0% has to go through a bundler you can no longer<00:16:02.880> send<00:16:03.160> transactions<00:16:03.839> directly<00:16:04.199> to<00:16:04.360> the 00:16:05.150 --> 00:16:05.160 align:start position:0% longer send transactions directly to the 00:16:05.160 --> 00:16:07.670 align:start position:0% longer send transactions directly to the blockchain<00:16:06.160> anyway<00:16:06.639> it<00:16:06.759> this<00:16:07.079> gets<00:16:07.360> really 00:16:07.670 --> 00:16:07.680 align:start position:0% blockchain anyway it this gets really 00:16:07.680 --> 00:16:10.150 align:start position:0% blockchain anyway it this gets really complicated<00:16:08.600> but<00:16:08.800> I<00:16:09.000> promise<00:16:09.360> you<00:16:09.759> that<00:16:09.880> we're 00:16:10.150 --> 00:16:10.160 align:start position:0% complicated but I promise you that we're 00:16:10.160 --> 00:16:11.590 align:start position:0% complicated but I promise you that we're working<00:16:10.519> really<00:16:10.759> hard<00:16:11.040> and<00:16:11.240> bringing 00:16:11.590 --> 00:16:11.600 align:start position:0% working really hard and bringing 00:16:11.600 --> 00:16:13.230 align:start position:0% working really hard and bringing standardization<00:16:12.560> and<00:16:12.639> we're<00:16:12.839> going<00:16:12.920> to<00:16:13.079> go 00:16:13.230 --> 00:16:13.240 align:start position:0% standardization and we're going to go 00:16:13.240 --> 00:16:14.749 align:start position:0% standardization and we're going to go through<00:16:13.440> this<00:16:13.600> journey<00:16:14.079> of<00:16:14.240> how<00:16:14.440> smart 00:16:14.749 --> 00:16:14.759 align:start position:0% through this journey of how smart 00:16:14.759 --> 00:16:17.470 align:start position:0% through this journey of how smart sessions<00:16:15.160> are<00:16:15.319> going<00:16:15.399> to<00:16:15.560> fix<00:16:15.839> that<00:16:16.639> so<00:16:17.319> the 00:16:17.470 --> 00:16:17.480 align:start position:0% sessions are going to fix that so the 00:16:17.480 --> 00:16:19.230 align:start position:0% sessions are going to fix that so the first<00:16:17.720> thing<00:16:17.920> you<00:16:18.079> might<00:16:18.279> think<00:16:18.600> is<00:16:18.839> like<00:16:19.120> how 00:16:19.230 --> 00:16:19.240 align:start position:0% first thing you might think is like how 00:16:19.240 --> 00:16:21.509 align:start position:0% first thing you might think is like how do<00:16:19.360> you<00:16:19.600> actually<00:16:19.880> detect<00:16:20.720> uh<00:16:20.880> if<00:16:21.040> a<00:16:21.240> wallet 00:16:21.509 --> 00:16:21.519 align:start position:0% do you actually detect uh if a wallet 00:16:21.519 --> 00:16:23.910 align:start position:0% do you actually detect uh if a wallet supports<00:16:21.920> smart<00:16:22.199> accounts<00:16:22.639> because<00:16:23.600> your 00:16:23.910 --> 00:16:23.920 align:start position:0% supports smart accounts because your 00:16:23.920 --> 00:16:25.829 align:start position:0% supports smart accounts because your application<00:16:24.480> now<00:16:24.759> has<00:16:24.880> to<00:16:25.120> consider<00:16:25.680> that 00:16:25.829 --> 00:16:25.839 align:start position:0% application now has to consider that 00:16:25.839 --> 00:16:27.749 align:start position:0% application now has to consider that your<00:16:26.040> wallet<00:16:26.360> doesn't<00:16:26.680> work<00:16:27.040> like<00:16:27.440> most 00:16:27.749 --> 00:16:27.759 align:start position:0% your wallet doesn't work like most 00:16:27.759 --> 00:16:29.230 align:start position:0% your wallet doesn't work like most wallets<00:16:28.160> you<00:16:28.279> don't<00:16:28.440> have<00:16:28.560> an<00:16:28.680> EXT<00:16:28.920> external 00:16:29.230 --> 00:16:29.240 align:start position:0% wallets you don't have an EXT external 00:16:29.240 --> 00:16:31.110 align:start position:0% wallets you don't have an EXT external account<00:16:29.519> how<00:16:29.639> do<00:16:29.720> you<00:16:29.920> actually<00:16:30.240> provide<00:16:30.639> that 00:16:31.110 --> 00:16:31.120 align:start position:0% account how do you actually provide that 00:16:31.120 --> 00:16:33.189 align:start position:0% account how do you actually provide that uh<00:16:31.600> identification<00:16:32.600> uh<00:16:32.720> there's<00:16:32.959> this 00:16:33.189 --> 00:16:33.199 align:start position:0% uh identification uh there's this 00:16:33.199 --> 00:16:35.670 align:start position:0% uh identification uh there's this concept<00:16:33.639> of<00:16:33.959> wallet<00:16:34.360> call<00:16:34.600> apis<00:16:35.120> it's<00:16:35.240> a<00:16:35.399> new 00:16:35.670 --> 00:16:35.680 align:start position:0% concept of wallet call apis it's a new 00:16:35.680 --> 00:16:37.629 align:start position:0% concept of wallet call apis it's a new standard<00:16:36.240> of<00:16:36.399> how<00:16:36.560> we<00:16:36.720> actually<00:16:37.000> going<00:16:37.120> to 00:16:37.629 --> 00:16:37.639 align:start position:0% standard of how we actually going to 00:16:37.639 --> 00:16:39.990 align:start position:0% standard of how we actually going to start<00:16:38.160> interfacing<00:16:38.880> applications<00:16:39.720> with 00:16:39.990 --> 00:16:40.000 align:start position:0% start interfacing applications with 00:16:40.000 --> 00:16:42.069 align:start position:0% start interfacing applications with wallets<00:16:40.480> differently<00:16:41.319> and<00:16:41.440> it<00:16:41.639> basically 00:16:42.069 --> 00:16:42.079 align:start position:0% wallets differently and it basically 00:16:42.079 --> 00:16:46.309 align:start position:0% wallets differently and it basically composes<00:16:42.800> into<00:16:43.399> four<00:16:44.040> new<00:16:44.959> methods<00:16:45.959> um<00:16:46.199> the 00:16:46.309 --> 00:16:46.319 align:start position:0% composes into four new methods um the 00:16:46.319 --> 00:16:48.110 align:start position:0% composes into four new methods um the most<00:16:46.560> important<00:16:46.959> of<00:16:47.160> these<00:16:47.360> methods<00:16:47.839> I<00:16:47.920> would 00:16:48.110 --> 00:16:48.120 align:start position:0% most important of these methods I would 00:16:48.120 --> 00:16:51.110 align:start position:0% most important of these methods I would say<00:16:48.560> is<00:16:48.920> this<00:16:49.079> one<00:16:49.399> the<00:16:49.560> wallet<00:16:49.880> send<00:16:50.160> calls 00:16:51.110 --> 00:16:51.120 align:start position:0% say is this one the wallet send calls 00:16:51.120 --> 00:16:53.030 align:start position:0% say is this one the wallet send calls and<00:16:51.360> this<00:16:51.560> basically<00:16:52.079> changes<00:16:52.560> how<00:16:52.759> we 00:16:53.030 --> 00:16:53.040 align:start position:0% and this basically changes how we 00:16:53.040 --> 00:16:55.350 align:start position:0% and this basically changes how we actually<00:16:53.399> think<00:16:53.920> about<00:16:54.279> the<00:16:54.440> wallet<00:16:54.759> sending 00:16:55.350 --> 00:16:55.360 align:start position:0% actually think about the wallet sending 00:16:55.360 --> 00:16:58.309 align:start position:0% actually think about the wallet sending transactions<00:16:56.360> uh<00:16:56.480> we<00:16:56.639> no<00:16:56.800> longer<00:16:57.160> think<00:16:57.480> about 00:16:58.309 --> 00:16:58.319 align:start position:0% transactions uh we no longer think about 00:16:58.319 --> 00:17:00.389 align:start position:0% transactions uh we no longer think about telling<00:16:58.959> the<00:16:59.079> wallet<00:16:59.440> send<00:16:59.680> me<00:16:59.839> an<00:16:59.959> ethereum 00:17:00.389 --> 00:17:00.399 align:start position:0% telling the wallet send me an ethereum 00:17:00.399 --> 00:17:02.870 align:start position:0% telling the wallet send me an ethereum transaction<00:17:01.079> I'm<00:17:01.199> telling<00:17:01.560> you<00:17:02.240> I<00:17:02.399> want<00:17:02.600> to 00:17:02.870 --> 00:17:02.880 align:start position:0% transaction I'm telling you I want to 00:17:02.880 --> 00:17:06.470 align:start position:0% transaction I'm telling you I want to take<00:17:03.199> these<00:17:03.559> actions<00:17:04.559> and<00:17:04.839> here's<00:17:05.120> a<00:17:05.880> multiple 00:17:06.470 --> 00:17:06.480 align:start position:0% take these actions and here's a multiple 00:17:06.480 --> 00:17:08.829 align:start position:0% take these actions and here's a multiple actions<00:17:07.079> and<00:17:07.240> I<00:17:07.400> want<00:17:07.600> you<00:17:07.760> to<00:17:08.160> actually 00:17:08.829 --> 00:17:08.839 align:start position:0% actions and I want you to actually 00:17:08.839 --> 00:17:11.590 align:start position:0% actions and I want you to actually execute<00:17:09.360> them<00:17:09.760> and<00:17:09.959> you<00:17:10.199> as<00:17:10.319> a<00:17:10.559> wallet<00:17:11.400> whether 00:17:11.590 --> 00:17:11.600 align:start position:0% execute them and you as a wallet whether 00:17:11.600 --> 00:17:13.669 align:start position:0% execute them and you as a wallet whether you're<00:17:11.760> a<00:17:11.919> smart<00:17:12.280> account<00:17:12.559> or<00:17:12.720> not<00:17:13.160> you<00:17:13.319> should 00:17:13.669 --> 00:17:13.679 align:start position:0% you're a smart account or not you should 00:17:13.679 --> 00:17:16.909 align:start position:0% you're a smart account or not you should just<00:17:13.959> be<00:17:14.319> able<00:17:14.640> to<00:17:14.919> do<00:17:15.120> so<00:17:15.880> and<00:17:16.199> this<00:17:16.439> comes 00:17:16.909 --> 00:17:16.919 align:start position:0% just be able to do so and this comes 00:17:16.919 --> 00:17:19.230 align:start position:0% just be able to do so and this comes with<00:17:17.160> this<00:17:17.520> idea<00:17:18.079> of<00:17:18.240> the<00:17:18.400> introduction<00:17:18.919> of 00:17:19.230 --> 00:17:19.240 align:start position:0% with this idea of the introduction of 00:17:19.240 --> 00:17:21.309 align:start position:0% with this idea of the introduction of capabilities<00:17:20.120> and<00:17:20.280> this<00:17:20.360> is<00:17:20.559> how<00:17:20.760> you 00:17:21.309 --> 00:17:21.319 align:start position:0% capabilities and this is how you 00:17:21.319 --> 00:17:24.029 align:start position:0% capabilities and this is how you discover<00:17:22.160> if<00:17:22.439> a<00:17:22.640> wallet<00:17:23.240> actually<00:17:23.760> can 00:17:24.029 --> 00:17:24.039 align:start position:0% discover if a wallet actually can 00:17:24.039 --> 00:17:26.990 align:start position:0% discover if a wallet actually can support<00:17:24.439> smart<00:17:24.760> accounts<00:17:25.520> so<00:17:26.079> the<00:17:26.240> wallet<00:17:26.600> get 00:17:26.990 --> 00:17:27.000 align:start position:0% support smart accounts so the wallet get 00:17:27.000 --> 00:17:29.190 align:start position:0% support smart accounts so the wallet get capabilities<00:17:28.000> actually<00:17:28.360> allows<00:17:28.679> you<00:17:28.960> to 00:17:29.190 --> 00:17:29.200 align:start position:0% capabilities actually allows you to 00:17:29.200 --> 00:17:32.470 align:start position:0% capabilities actually allows you to detect<00:17:29.919> that<00:17:30.520> oh<00:17:30.840> on<00:17:31.120> this<00:17:31.480> different<00:17:31.840> chains 00:17:32.470 --> 00:17:32.480 align:start position:0% detect that oh on this different chains 00:17:32.480 --> 00:17:34.470 align:start position:0% detect that oh on this different chains this<00:17:32.720> wallet<00:17:33.080> has<00:17:33.240> the<00:17:33.440> capability<00:17:33.960> of<00:17:34.160> pay 00:17:34.470 --> 00:17:34.480 align:start position:0% this wallet has the capability of pay 00:17:34.480 --> 00:17:36.549 align:start position:0% this wallet has the capability of pay master<00:17:34.840> or<00:17:35.000> session<00:17:35.440> Keys<00:17:35.880> like<00:17:36.000> you<00:17:36.120> can<00:17:36.360> add 00:17:36.549 --> 00:17:36.559 align:start position:0% master or session Keys like you can add 00:17:36.559 --> 00:17:38.750 align:start position:0% master or session Keys like you can add multiple<00:17:37.039> features<00:17:37.440> in<00:17:37.679> there<00:17:38.200> that<00:17:38.400> allow 00:17:38.750 --> 00:17:38.760 align:start position:0% multiple features in there that allow 00:17:38.760 --> 00:17:41.310 align:start position:0% multiple features in there that allow your<00:17:38.960> wallet<00:17:39.320> to<00:17:39.559> say<00:17:39.919> to<00:17:40.160> the<00:17:40.320> application 00:17:41.310 --> 00:17:41.320 align:start position:0% your wallet to say to the application 00:17:41.320 --> 00:17:43.510 align:start position:0% your wallet to say to the application you<00:17:41.520> can<00:17:41.840> actually<00:17:42.240> behave<00:17:42.919> in<00:17:43.039> a<00:17:43.200> more 00:17:43.510 --> 00:17:43.520 align:start position:0% you can actually behave in a more 00:17:43.520 --> 00:17:46.230 align:start position:0% you can actually behave in a more convenient<00:17:44.120> way<00:17:44.320> for<00:17:44.559> your<00:17:44.880> user<00:17:45.640> if<00:17:45.799> you<00:17:45.960> use 00:17:46.230 --> 00:17:46.240 align:start position:0% convenient way for your user if you use 00:17:46.240 --> 00:17:48.350 align:start position:0% convenient way for your user if you use these<00:17:46.440> features<00:17:47.280> so<00:17:47.559> this<00:17:47.640> is<00:17:47.840> actually<00:17:48.160> quite 00:17:48.350 --> 00:17:48.360 align:start position:0% these features so this is actually quite 00:17:48.360 --> 00:17:50.669 align:start position:0% these features so this is actually quite useful<00:17:48.880> because<00:17:49.200> now<00:17:49.440> we<00:17:49.600> notice<00:17:50.080> that<00:17:50.480> the 00:17:50.669 --> 00:17:50.679 align:start position:0% useful because now we notice that the 00:17:50.679 --> 00:17:52.669 align:start position:0% useful because now we notice that the triangle<00:17:51.280> of<00:17:51.440> the<00:17:51.640> wallet<00:17:52.039> blockchain<00:17:52.440> and 00:17:52.669 --> 00:17:52.679 align:start position:0% triangle of the wallet blockchain and 00:17:52.679 --> 00:17:55.630 align:start position:0% triangle of the wallet blockchain and app<00:17:53.160> broke<00:17:53.520> down<00:17:53.720> into<00:17:54.000> multiple<00:17:54.520> pieces<00:17:55.400> and 00:17:55.630 --> 00:17:55.640 align:start position:0% app broke down into multiple pieces and 00:17:55.640 --> 00:17:57.830 align:start position:0% app broke down into multiple pieces and the<00:17:55.840> application<00:17:56.400> now<00:17:56.640> has<00:17:56.840> the<00:17:57.039> ability<00:17:57.520> to 00:17:57.830 --> 00:17:57.840 align:start position:0% the application now has the ability to 00:17:57.840 --> 00:18:00.870 align:start position:0% the application now has the ability to detect<00:17:58.919> but<00:17:59.200> one<00:17:59.400> thing<00:17:59.640> I<00:17:59.799> did<00:18:00.000> not<00:18:00.200> tell<00:18:00.440> you 00:18:00.870 --> 00:18:00.880 align:start position:0% detect but one thing I did not tell you 00:18:00.880 --> 00:18:03.230 align:start position:0% detect but one thing I did not tell you and<00:18:01.039> I<00:18:01.159> did<00:18:01.320> not<00:18:01.480> show<00:18:01.720> you<00:18:01.880> the<00:18:02.080> spec<00:18:02.400> of<00:18:02.520> the 00:18:03.230 --> 00:18:03.240 align:start position:0% and I did not show you the spec of the 00:18:03.240 --> 00:18:06.029 align:start position:0% and I did not show you the spec of the 4337<00:18:04.240> is<00:18:04.400> that<00:18:04.640> despite<00:18:04.960> the<00:18:05.120> spec<00:18:05.440> being<00:18:05.679> a 00:18:06.029 --> 00:18:06.039 align:start position:0% 4337 is that despite the spec being a 00:18:06.039 --> 00:18:08.590 align:start position:0% 4337 is that despite the spec being a very<00:18:06.440> very<00:18:06.919> long<00:18:07.200> and<00:18:07.440> complicated<00:18:07.960> spec<00:18:08.400> is 00:18:08.590 --> 00:18:08.600 align:start position:0% very very long and complicated spec is 00:18:08.600 --> 00:18:10.870 align:start position:0% very very long and complicated spec is actually<00:18:08.840> missing<00:18:09.200> a<00:18:09.320> lot<00:18:09.480> of<00:18:09.640> stuff<00:18:10.039> like 00:18:10.870 --> 00:18:10.880 align:start position:0% actually missing a lot of stuff like 00:18:10.880 --> 00:18:13.630 align:start position:0% actually missing a lot of stuff like it's<00:18:11.039> not<00:18:11.240> telling<00:18:11.559> you<00:18:12.480> um<00:18:12.880> how<00:18:13.120> the<00:18:13.280> wallet 00:18:13.630 --> 00:18:13.640 align:start position:0% it's not telling you um how the wallet 00:18:13.640 --> 00:18:16.070 align:start position:0% it's not telling you um how the wallet supports<00:18:14.240> and<00:18:14.520> which<00:18:14.799> pay<00:18:15.000> Master<00:18:15.360> supports 00:18:16.070 --> 00:18:16.080 align:start position:0% supports and which pay Master supports 00:18:16.080 --> 00:18:18.909 align:start position:0% supports and which pay Master supports and<00:18:16.679> what<00:18:16.799> is<00:18:17.039> the<00:18:17.360> interface<00:18:18.000> of<00:18:18.159> pay<00:18:18.440> masters 00:18:18.909 --> 00:18:18.919 align:start position:0% and what is the interface of pay masters 00:18:18.919 --> 00:18:20.590 align:start position:0% and what is the interface of pay masters and<00:18:19.080> we<00:18:19.240> basically<00:18:19.600> kind<00:18:19.720> of<00:18:19.919> just<00:18:20.080> decided 00:18:20.590 --> 00:18:20.600 align:start position:0% and we basically kind of just decided 00:18:20.600 --> 00:18:22.230 align:start position:0% and we basically kind of just decided you<00:18:20.720> know<00:18:20.880> the<00:18:21.039> community<00:18:21.480> will<00:18:21.679> figure<00:18:22.000> out 00:18:22.230 --> 00:18:22.240 align:start position:0% you know the community will figure out 00:18:22.240 --> 00:18:24.750 align:start position:0% you know the community will figure out one<00:18:22.480> day<00:18:23.240> and<00:18:23.360> that<00:18:23.480> was<00:18:23.679> kind<00:18:23.799> of<00:18:24.240> okay<00:18:24.480> at<00:18:24.600> the 00:18:24.750 --> 00:18:24.760 align:start position:0% one day and that was kind of okay at the 00:18:24.760 --> 00:18:26.990 align:start position:0% one day and that was kind of okay at the beginning<00:18:25.240> like<00:18:25.360> if<00:18:25.480> you<00:18:25.600> go<00:18:25.799> back<00:18:25.919> to<00:18:26.120> 2022 00:18:26.990 --> 00:18:27.000 align:start position:0% beginning like if you go back to 2022 00:18:27.000 --> 00:18:29.390 align:start position:0% beginning like if you go back to 2022 2023<00:18:27.880> people<00:18:28.080> were<00:18:28.240> building<00:18:28.799> pay<00:18:29.000> masters 00:18:29.390 --> 00:18:29.400 align:start position:0% 2023 people were building pay masters 00:18:29.400 --> 00:18:31.950 align:start position:0% 2023 people were building pay masters and<00:18:29.640> sponsoring<00:18:30.200> transactions<00:18:30.760> for<00:18:31.039> everyone 00:18:31.950 --> 00:18:31.960 align:start position:0% and sponsoring transactions for everyone 00:18:31.960 --> 00:18:33.750 align:start position:0% and sponsoring transactions for everyone but<00:18:32.159> this<00:18:32.320> was<00:18:32.520> also<00:18:32.720> an<00:18:32.919> opportunity<00:18:33.440> for 00:18:33.750 --> 00:18:33.760 align:start position:0% but this was also an opportunity for 00:18:33.760 --> 00:18:35.549 align:start position:0% but this was also an opportunity for fragmentation<00:18:34.600> where<00:18:34.799> everyone<00:18:35.200> had<00:18:35.400> their 00:18:35.549 --> 00:18:35.559 align:start position:0% fragmentation where everyone had their 00:18:35.559 --> 00:18:37.669 align:start position:0% fragmentation where everyone had their own<00:18:35.840> pay<00:18:36.120> master<00:18:36.760> and<00:18:36.880> everyone<00:18:37.200> done 00:18:37.669 --> 00:18:37.679 align:start position:0% own pay master and everyone done 00:18:37.679 --> 00:18:40.870 align:start position:0% own pay master and everyone done something<00:18:38.039> a<00:18:38.159> little<00:18:38.480> different<00:18:39.360> so<00:18:39.720> in<00:18:39.880> 2024 00:18:40.870 --> 00:18:40.880 align:start position:0% something a little different so in 2024 00:18:40.880 --> 00:18:43.549 align:start position:0% something a little different so in 2024 we<00:18:41.080> realized<00:18:41.760> guys<00:18:42.039> we<00:18:42.159> need<00:18:42.320> to<00:18:42.520> stop<00:18:42.919> this<00:18:43.440> uh 00:18:43.549 --> 00:18:43.559 align:start position:0% we realized guys we need to stop this uh 00:18:43.559 --> 00:18:46.190 align:start position:0% we realized guys we need to stop this uh we<00:18:43.679> need<00:18:43.840> to<00:18:44.080> all<00:18:44.440> agree<00:18:45.240> to<00:18:45.400> do<00:18:45.600> pay<00:18:45.840> masters 00:18:46.190 --> 00:18:46.200 align:start position:0% we need to all agree to do pay masters 00:18:46.200 --> 00:18:47.710 align:start position:0% we need to all agree to do pay masters in<00:18:46.320> the<00:18:46.480> same<00:18:46.720> way<00:18:47.039> and<00:18:47.120> we<00:18:47.240> wrote<00:18:47.559> the 00:18:47.710 --> 00:18:47.720 align:start position:0% in the same way and we wrote the 00:18:47.720 --> 00:18:48.909 align:start position:0% in the same way and we wrote the standard 00:18:48.909 --> 00:18:48.919 align:start position:0% standard 00:18:48.919 --> 00:18:51.789 align:start position:0% standard 7677<00:18:49.919> which<00:18:50.120> created<00:18:51.080> this<00:18:51.280> part<00:18:51.440> is<00:18:51.600> not 00:18:51.789 --> 00:18:51.799 align:start position:0% 7677 which created this part is not 00:18:51.799 --> 00:18:54.070 align:start position:0% 7677 which created this part is not really<00:18:52.080> that<00:18:52.280> interesting<00:18:53.280> um<00:18:53.640> I<00:18:53.760> just<00:18:53.960> kind 00:18:54.070 --> 00:18:54.080 align:start position:0% really that interesting um I just kind 00:18:54.080 --> 00:18:55.909 align:start position:0% really that interesting um I just kind of<00:18:54.400> wanted<00:18:54.600> to<00:18:54.720> give<00:18:54.840> you<00:18:54.919> a<00:18:55.039> picture<00:18:55.440> how<00:18:55.760> a 00:18:55.909 --> 00:18:55.919 align:start position:0% of wanted to give you a picture how a 00:18:55.919 --> 00:18:58.350 align:start position:0% of wanted to give you a picture how a few<00:18:56.280> lines<00:18:56.600> of<00:18:56.840> code<00:18:57.559> can<00:18:57.799> make<00:18:57.960> a<00:18:58.159> big 00:18:58.350 --> 00:18:58.360 align:start position:0% few lines of code can make a big 00:18:58.360 --> 00:19:01.470 align:start position:0% few lines of code can make a big difference<00:18:59.000> of<00:18:59.240> how<00:18:59.440> we<00:18:59.559> can<00:18:59.799> make<00:19:00.200> this<00:19:00.960> world 00:19:01.470 --> 00:19:01.480 align:start position:0% difference of how we can make this world 00:19:01.480 --> 00:19:03.789 align:start position:0% difference of how we can make this world a<00:19:01.640> little<00:19:01.919> bit<00:19:02.159> better<00:19:02.760> by<00:19:02.919> not<00:19:03.159> having<00:19:03.520> pay 00:19:03.789 --> 00:19:03.799 align:start position:0% a little bit better by not having pay 00:19:03.799 --> 00:19:06.590 align:start position:0% a little bit better by not having pay masters<00:19:04.640> uh<00:19:04.840> capture<00:19:05.440> value<00:19:05.960> of<00:19:06.159> locking 00:19:06.590 --> 00:19:06.600 align:start position:0% masters uh capture value of locking 00:19:06.600 --> 00:19:08.950 align:start position:0% masters uh capture value of locking users<00:19:07.000> into<00:19:07.240> their<00:19:07.440> pay<00:19:07.679> master<00:19:08.240> and<00:19:08.440> can<00:19:08.679> have 00:19:08.950 --> 00:19:08.960 align:start position:0% users into their pay master and can have 00:19:08.960 --> 00:19:11.549 align:start position:0% users into their pay master and can have all<00:19:09.240> pay<00:19:09.480> masters<00:19:09.919> working<00:19:10.320> the<00:19:10.480> same<00:19:10.760> way<00:19:11.440> it 00:19:11.549 --> 00:19:11.559 align:start position:0% all pay masters working the same way it 00:19:11.559 --> 00:19:14.470 align:start position:0% all pay masters working the same way it was<00:19:11.720> a<00:19:11.880> very<00:19:12.159> small<00:19:12.559> thing<00:19:12.919> but<00:19:13.080> it<00:19:13.200> made<00:19:13.400> a<00:19:13.559> big 00:19:14.470 --> 00:19:14.480 align:start position:0% was a very small thing but it made a big 00:19:14.480 --> 00:19:16.430 align:start position:0% was a very small thing but it made a big difference<00:19:15.480> another<00:19:15.760> thing<00:19:15.919> that<00:19:16.000> we<00:19:16.120> didn't 00:19:16.430 --> 00:19:16.440 align:start position:0% difference another thing that we didn't 00:19:16.440 --> 00:19:19.190 align:start position:0% difference another thing that we didn't talk<00:19:16.720> is<00:19:16.919> about<00:19:17.600> the<00:19:17.880> actual<00:19:18.280> smart<00:19:18.720> contract 00:19:19.190 --> 00:19:19.200 align:start position:0% talk is about the actual smart contract 00:19:19.200 --> 00:19:21.669 align:start position:0% talk is about the actual smart contract design<00:19:19.679> you<00:19:19.799> know<00:19:20.480> like<00:19:20.640> I<00:19:20.760> mentioned<00:19:21.159> before 00:19:21.669 --> 00:19:21.679 align:start position:0% design you know like I mentioned before 00:19:21.679 --> 00:19:23.630 align:start position:0% design you know like I mentioned before ethereum<00:19:22.159> allows<00:19:22.440> you<00:19:22.520> to<00:19:22.640> do<00:19:22.960> pretty<00:19:23.159> much 00:19:23.630 --> 00:19:23.640 align:start position:0% ethereum allows you to do pretty much 00:19:23.640 --> 00:19:26.630 align:start position:0% ethereum allows you to do pretty much everything<00:19:24.400> like<00:19:24.640> so<00:19:25.440> what<00:19:25.600> would<00:19:25.880> change 00:19:26.630 --> 00:19:26.640 align:start position:0% everything like so what would change 00:19:26.640 --> 00:19:28.789 align:start position:0% everything like so what would change because<00:19:27.000> in<00:19:27.240> external<00:19:27.760> accounts<00:19:28.320> every 00:19:28.789 --> 00:19:28.799 align:start position:0% because in external accounts every 00:19:28.799 --> 00:19:31.070 align:start position:0% because in external accounts every account<00:19:29.120> work<00:19:29.400> the<00:19:29.559> same<00:19:30.200> but<00:19:30.360> with<00:19:30.559> smart 00:19:31.070 --> 00:19:31.080 align:start position:0% account work the same but with smart 00:19:31.080 --> 00:19:33.750 align:start position:0% account work the same but with smart contracts<00:19:32.039> that<00:19:32.480> kind<00:19:32.640> of<00:19:33.080> gives<00:19:33.360> a<00:19:33.520> little 00:19:33.750 --> 00:19:33.760 align:start position:0% contracts that kind of gives a little 00:19:33.760 --> 00:19:36.350 align:start position:0% contracts that kind of gives a little bit<00:19:33.919> too<00:19:34.120> much<00:19:34.360> flexibility<00:19:35.200> And<00:19:35.720> if<00:19:36.000> every 00:19:36.350 --> 00:19:36.360 align:start position:0% bit too much flexibility And if every 00:19:36.360 --> 00:19:38.549 align:start position:0% bit too much flexibility And if every wallet<00:19:36.840> Works<00:19:37.280> slightly<00:19:37.880> different<00:19:38.400> then 00:19:38.549 --> 00:19:38.559 align:start position:0% wallet Works slightly different then 00:19:38.559 --> 00:19:39.990 align:start position:0% wallet Works slightly different then we're<00:19:38.720> going<00:19:38.840> to<00:19:39.000> have<00:19:39.120> to<00:19:39.280> start<00:19:39.640> having 00:19:39.990 --> 00:19:40.000 align:start position:0% we're going to have to start having 00:19:40.000 --> 00:19:42.149 align:start position:0% we're going to have to start having problems<00:19:40.760> we<00:19:40.919> standardize<00:19:41.559> how<00:19:41.799> account 00:19:42.149 --> 00:19:42.159 align:start position:0% problems we standardize how account 00:19:42.159 --> 00:19:43.830 align:start position:0% problems we standardize how account obstruction<00:19:42.799> framework<00:19:43.360> works<00:19:43.679> we 00:19:43.830 --> 00:19:43.840 align:start position:0% obstruction framework works we 00:19:43.840 --> 00:19:46.190 align:start position:0% obstruction framework works we standardize<00:19:44.360> how<00:19:44.480> the<00:19:44.679> paym<00:19:45.240> works<00:19:45.880> but<00:19:46.039> what 00:19:46.190 --> 00:19:46.200 align:start position:0% standardize how the paym works but what 00:19:46.200 --> 00:19:48.350 align:start position:0% standardize how the paym works but what about<00:19:46.480> your<00:19:46.840> actual<00:19:47.320> smart<00:19:47.679> contract<00:19:48.200> what 00:19:48.350 --> 00:19:48.360 align:start position:0% about your actual smart contract what 00:19:48.360 --> 00:19:50.390 align:start position:0% about your actual smart contract what can<00:19:48.520> I<00:19:48.760> do<00:19:49.240> with<00:19:49.400> your<00:19:49.600> smart<00:19:49.960> contract 00:19:50.390 --> 00:19:50.400 align:start position:0% can I do with your smart contract 00:19:50.400 --> 00:19:54.230 align:start position:0% can I do with your smart contract accounts<00:19:51.280> so<00:19:51.559> this<00:19:51.679> is<00:19:51.880> where<00:19:52.520> 7579<00:19:53.520> came<00:19:53.720> in 00:19:54.230 --> 00:19:54.240 align:start position:0% accounts so this is where 7579 came in 00:19:54.240 --> 00:19:56.830 align:start position:0% accounts so this is where 7579 came in and<00:19:54.360> it<00:19:54.559> provided<00:19:54.960> a<00:19:55.280> very<00:19:55.640> minimal<00:19:56.280> framework 00:19:56.830 --> 00:19:56.840 align:start position:0% and it provided a very minimal framework 00:19:56.840 --> 00:19:59.590 align:start position:0% and it provided a very minimal framework for<00:19:57.120> how<00:19:57.280> to<00:19:57.480> create<00:19:57.880> modules<00:19:58.880> and<00:19:59.120> in<00:19:59.360> these 00:19:59.590 --> 00:19:59.600 align:start position:0% for how to create modules and in these 00:19:59.600 --> 00:20:01.830 align:start position:0% for how to create modules and in these modules<00:20:00.120> you<00:20:00.240> can<00:20:00.440> essentially<00:20:00.919> think<00:20:01.360> that 00:20:01.830 --> 00:20:01.840 align:start position:0% modules you can essentially think that 00:20:01.840 --> 00:20:06.230 align:start position:0% modules you can essentially think that we<00:20:02.000> can<00:20:02.280> use<00:20:02.840> the<00:20:03.720> basic<00:20:04.600> like<00:20:05.080> smart<00:20:05.520> contract 00:20:06.230 --> 00:20:06.240 align:start position:0% we can use the basic like smart contract 00:20:06.240 --> 00:20:09.549 align:start position:0% we can use the basic like smart contract codes<00:20:06.840> that<00:20:07.000> we<00:20:07.280> all<00:20:07.640> agree<00:20:08.240> is<00:20:08.520> the<00:20:08.799> consensus 00:20:09.549 --> 00:20:09.559 align:start position:0% codes that we all agree is the consensus 00:20:09.559 --> 00:20:12.149 align:start position:0% codes that we all agree is the consensus of<00:20:09.840> what<00:20:09.960> a<00:20:10.120> smart<00:20:10.480> contract<00:20:11.000> account<00:20:11.320> is<00:20:12.000> and 00:20:12.149 --> 00:20:12.159 align:start position:0% of what a smart contract account is and 00:20:12.159 --> 00:20:14.909 align:start position:0% of what a smart contract account is and then<00:20:12.360> we<00:20:12.480> can<00:20:12.840> all<00:20:13.280> install<00:20:13.919> modules<00:20:14.520> so<00:20:14.799> you 00:20:14.909 --> 00:20:14.919 align:start position:0% then we can all install modules so you 00:20:14.919 --> 00:20:16.669 align:start position:0% then we can all install modules so you can<00:20:15.080> think<00:20:15.320> of<00:20:15.520> these<00:20:15.880> like<00:20:16.080> almost<00:20:16.360> as 00:20:16.669 --> 00:20:16.679 align:start position:0% can think of these like almost as 00:20:16.679 --> 00:20:18.909 align:start position:0% can think of these like almost as plugins<00:20:17.120> for<00:20:17.320> your<00:20:17.520> account<00:20:18.159> adding<00:20:18.559> new 00:20:18.909 --> 00:20:18.919 align:start position:0% plugins for your account adding new 00:20:18.919 --> 00:20:21.149 align:start position:0% plugins for your account adding new functionality<00:20:19.760> and<00:20:19.919> becoming<00:20:20.440> this<00:20:20.679> more 00:20:21.149 --> 00:20:21.159 align:start position:0% functionality and becoming this more 00:20:21.159 --> 00:20:23.990 align:start position:0% functionality and becoming this more vibrant<00:20:21.960> ecosystem<00:20:22.919> where<00:20:23.200> everyone<00:20:23.720> adds 00:20:23.990 --> 00:20:24.000 align:start position:0% vibrant ecosystem where everyone adds 00:20:24.000 --> 00:20:26.470 align:start position:0% vibrant ecosystem where everyone adds new<00:20:24.200> features<00:20:24.760> these<00:20:24.919> features<00:20:25.360> could<00:20:25.559> be<00:20:26.320> uh 00:20:26.470 --> 00:20:26.480 align:start position:0% new features these features could be uh 00:20:26.480 --> 00:20:29.310 align:start position:0% new features these features could be uh for<00:20:26.960> example<00:20:27.960> recovery<00:20:28.679> like<00:20:28.799> you<00:20:28.880> want<00:20:28.960> to<00:20:29.080> do 00:20:29.310 --> 00:20:29.320 align:start position:0% for example recovery like you want to do 00:20:29.320 --> 00:20:31.710 align:start position:0% for example recovery like you want to do recovery<00:20:29.840> in<00:20:30.280> interesting<00:20:30.840> ways<00:20:31.280> like<00:20:31.480> where 00:20:31.710 --> 00:20:31.720 align:start position:0% recovery in interesting ways like where 00:20:31.720 --> 00:20:34.270 align:start position:0% recovery in interesting ways like where you<00:20:31.880> include<00:20:32.880> uh<00:20:33.000> your<00:20:33.280> family<00:20:33.600> and<00:20:33.840> friends 00:20:34.270 --> 00:20:34.280 align:start position:0% you include uh your family and friends 00:20:34.280 --> 00:20:36.950 align:start position:0% you include uh your family and friends or<00:20:34.440> you<00:20:34.559> can<00:20:35.200> include<00:20:35.520> a<00:20:35.679> third<00:20:36.000> party<00:20:36.840> it 00:20:36.950 --> 00:20:36.960 align:start position:0% or you can include a third party it 00:20:36.960 --> 00:20:39.549 align:start position:0% or you can include a third party it could<00:20:37.120> also<00:20:37.360> be<00:20:37.679> features<00:20:38.280> like<00:20:38.799> you<00:20:38.960> know 00:20:39.549 --> 00:20:39.559 align:start position:0% could also be features like you know 00:20:39.559 --> 00:20:41.950 align:start position:0% could also be features like you know proving<00:20:40.240> different<00:20:40.760> credentials<00:20:41.559> in<00:20:41.760> your 00:20:41.950 --> 00:20:41.960 align:start position:0% proving different credentials in your 00:20:41.960 --> 00:20:44.390 align:start position:0% proving different credentials in your modules<00:20:42.559> it<00:20:42.679> could<00:20:42.840> be<00:20:43.080> some<00:20:43.320> features<00:20:43.760> around 00:20:44.390 --> 00:20:44.400 align:start position:0% modules it could be some features around 00:20:44.400 --> 00:20:46.630 align:start position:0% modules it could be some features around how<00:20:44.640> you<00:20:44.799> define<00:20:45.320> policies<00:20:46.000> of<00:20:46.280> how<00:20:46.440> you 00:20:46.630 --> 00:20:46.640 align:start position:0% how you define policies of how you 00:20:46.640 --> 00:20:48.310 align:start position:0% how you define policies of how you actually<00:20:46.960> manage<00:20:47.360> your<00:20:47.600> account<00:20:48.000> under 00:20:48.310 --> 00:20:48.320 align:start position:0% actually manage your account under 00:20:48.320 --> 00:20:52.270 align:start position:0% actually manage your account under certain<00:20:49.159> conditions<00:20:50.159> and<00:20:50.919> for<00:20:51.159> me<00:20:51.640> personally 00:20:52.270 --> 00:20:52.280 align:start position:0% certain conditions and for me personally 00:20:52.280 --> 00:20:53.950 align:start position:0% certain conditions and for me personally the<00:20:52.400> one<00:20:52.640> that<00:20:52.760> I<00:20:52.960> got<00:20:53.200> a<00:20:53.320> little<00:20:53.520> bit<00:20:53.679> more 00:20:53.950 --> 00:20:53.960 align:start position:0% the one that I got a little bit more 00:20:53.960 --> 00:20:57.270 align:start position:0% the one that I got a little bit more curious<00:20:54.360> about<00:20:54.720> was<00:20:55.360> hm<00:20:56.039> if<00:20:56.200> I<00:20:56.360> can<00:20:56.640> control 00:20:57.270 --> 00:20:57.280 align:start position:0% curious about was hm if I can control 00:20:57.280 --> 00:20:59.110 align:start position:0% curious about was hm if I can control how<00:20:57.520> my<00:20:57.760> account<00:20:58.039> is<00:20:58.200> used<00:20:58.600> under<00:20:58.840> some 00:20:59.110 --> 00:20:59.120 align:start position:0% how my account is used under some 00:20:59.120 --> 00:21:01.990 align:start position:0% how my account is used under some policies<00:20:59.720> I'm<00:21:00.200> essentially<00:21:01.200> giving<00:21:01.760> the 00:21:01.990 --> 00:21:02.000 align:start position:0% policies I'm essentially giving the 00:21:02.000 --> 00:21:04.549 align:start position:0% policies I'm essentially giving the ability<00:21:02.720> for<00:21:02.960> the<00:21:03.120> smart<00:21:03.600> contract<00:21:04.159> account 00:21:04.549 --> 00:21:04.559 align:start position:0% ability for the smart contract account 00:21:04.559 --> 00:21:07.830 align:start position:0% ability for the smart contract account to<00:21:04.840> manage<00:21:05.280> itself<00:21:06.120> because<00:21:06.440> I<00:21:06.760> say<00:21:07.480> I<00:21:07.600> don't 00:21:07.830 --> 00:21:07.840 align:start position:0% to manage itself because I say I don't 00:21:07.840 --> 00:21:10.350 align:start position:0% to manage itself because I say I don't want<00:21:08.039> you<00:21:08.200> to<00:21:08.360> be<00:21:08.559> able<00:21:08.760> to<00:21:09.039> spend<00:21:09.880> this<00:21:10.080> amount 00:21:10.350 --> 00:21:10.360 align:start position:0% want you to be able to spend this amount 00:21:10.360 --> 00:21:12.990 align:start position:0% want you to be able to spend this amount of<00:21:10.520> tokens<00:21:11.039> within<00:21:11.440> this<00:21:11.679> window<00:21:12.039> of<00:21:12.240> time<00:21:12.880> and 00:21:12.990 --> 00:21:13.000 align:start position:0% of tokens within this window of time and 00:21:13.000 --> 00:21:15.549 align:start position:0% of tokens within this window of time and if<00:21:13.159> I<00:21:13.279> can<00:21:13.480> do<00:21:13.760> that<00:21:14.120> I'm<00:21:14.400> starting<00:21:14.720> to<00:21:14.880> think 00:21:15.549 --> 00:21:15.559 align:start position:0% if I can do that I'm starting to think 00:21:15.559 --> 00:21:19.350 align:start position:0% if I can do that I'm starting to think what<00:21:15.679> if<00:21:15.880> we<00:21:16.120> actually<00:21:16.640> had<00:21:17.279> the<00:21:18.120> app<00:21:18.960> actually 00:21:19.350 --> 00:21:19.360 align:start position:0% what if we actually had the app actually 00:21:19.360 --> 00:21:23.350 align:start position:0% what if we actually had the app actually sign<00:21:20.120> the<00:21:20.320> actual<00:21:20.960> operations<00:21:21.960> on<00:21:22.200> my<00:21:22.480> behalf 00:21:23.350 --> 00:21:23.360 align:start position:0% sign the actual operations on my behalf 00:21:23.360 --> 00:21:25.669 align:start position:0% sign the actual operations on my behalf then<00:21:24.159> if<00:21:24.480> that's<00:21:24.679> going<00:21:24.799> to<00:21:24.960> be<00:21:25.120> the<00:21:25.320> case<00:21:25.600> then 00:21:25.669 --> 00:21:25.679 align:start position:0% then if that's going to be the case then 00:21:25.679 --> 00:21:27.430 align:start position:0% then if that's going to be the case then we're<00:21:25.840> going<00:21:25.960> to<00:21:26.120> start<00:21:26.400> thinking<00:21:26.919> wait<00:21:27.240> if 00:21:27.430 --> 00:21:27.440 align:start position:0% we're going to start thinking wait if 00:21:27.440 --> 00:21:30.149 align:start position:0% we're going to start thinking wait if the<00:21:27.720> app<00:21:28.039> signs<00:21:28.600> on<00:21:28.720> my<00:21:28.880> behalf<00:21:29.440> I<00:21:29.600> no<00:21:29.799> longer 00:21:30.149 --> 00:21:30.159 align:start position:0% the app signs on my behalf I no longer 00:21:30.159 --> 00:21:32.510 align:start position:0% the app signs on my behalf I no longer have<00:21:30.320> to<00:21:30.720> return<00:21:31.000> to<00:21:31.200> my<00:21:31.400> wallet<00:21:31.679> to<00:21:31.880> approve 00:21:32.510 --> 00:21:32.520 align:start position:0% have to return to my wallet to approve 00:21:32.520 --> 00:21:34.510 align:start position:0% have to return to my wallet to approve every<00:21:32.960> transaction<00:21:33.960> and<00:21:34.159> this<00:21:34.279> would 00:21:34.510 --> 00:21:34.520 align:start position:0% every transaction and this would 00:21:34.520 --> 00:21:36.549 align:start position:0% every transaction and this would actually<00:21:34.799> create<00:21:35.120> the<00:21:35.320> best<00:21:35.679> picture<00:21:36.159> because 00:21:36.549 --> 00:21:36.559 align:start position:0% actually create the best picture because 00:21:36.559 --> 00:21:39.269 align:start position:0% actually create the best picture because now<00:21:37.400> I've<00:21:38.000> told<00:21:38.240> you<00:21:38.400> at<00:21:38.480> the<00:21:38.640> beginning<00:21:39.120> that 00:21:39.269 --> 00:21:39.279 align:start position:0% now I've told you at the beginning that 00:21:39.279 --> 00:21:41.870 align:start position:0% now I've told you at the beginning that we<00:21:39.400> were<00:21:39.720> able<00:21:40.039> to<00:21:40.640> create<00:21:40.919> sign<00:21:41.279> with<00:21:41.440> etherum 00:21:41.870 --> 00:21:41.880 align:start position:0% we were able to create sign with etherum 00:21:41.880 --> 00:21:43.710 align:start position:0% we were able to create sign with etherum in<00:21:42.000> a<00:21:42.159> single<00:21:42.559> click<00:21:42.960> by<00:21:43.120> removing<00:21:43.559> the 00:21:43.710 --> 00:21:43.720 align:start position:0% in a single click by removing the 00:21:43.720 --> 00:21:46.630 align:start position:0% in a single click by removing the connect<00:21:44.600> but<00:21:44.760> now<00:21:44.919> I'm<00:21:45.120> telling<00:21:45.480> you<00:21:46.080> that<00:21:46.360> the 00:21:46.630 --> 00:21:46.640 align:start position:0% connect but now I'm telling you that the 00:21:46.640 --> 00:21:48.630 align:start position:0% connect but now I'm telling you that the app<00:21:46.919> itself<00:21:47.279> would<00:21:47.440> be<00:21:47.559> able<00:21:47.760> to<00:21:47.960> sign<00:21:48.240> on<00:21:48.440> my 00:21:48.630 --> 00:21:48.640 align:start position:0% app itself would be able to sign on my 00:21:48.640 --> 00:21:50.590 align:start position:0% app itself would be able to sign on my behalf<00:21:49.159> because<00:21:49.440> I<00:21:49.600> have<00:21:49.760> a<00:21:49.880> smart<00:21:50.200> contract 00:21:50.590 --> 00:21:50.600 align:start position:0% behalf because I have a smart contract 00:21:50.600 --> 00:21:52.789 align:start position:0% behalf because I have a smart contract account<00:21:51.400> and<00:21:51.600> this<00:21:51.720> is<00:21:51.960> essentially<00:21:52.640> what 00:21:52.789 --> 00:21:52.799 align:start position:0% account and this is essentially what 00:21:52.799 --> 00:21:55.590 align:start position:0% account and this is essentially what would<00:21:52.960> be<00:21:53.320> the<00:21:53.520> end<00:21:53.840> goal<00:21:54.400> where<00:21:54.720> you<00:21:55.000> log<00:21:55.279> in 00:21:55.590 --> 00:21:55.600 align:start position:0% would be the end goal where you log in 00:21:55.600 --> 00:21:58.590 align:start position:0% would be the end goal where you log in once<00:21:56.360> and<00:21:56.559> then<00:21:56.760> you<00:21:57.159> actually<00:21:57.720> have<00:21:57.960> the<00:21:58.159> app 00:21:58.590 --> 00:21:58.600 align:start position:0% once and then you actually have the app 00:21:58.600 --> 00:22:00.990 align:start position:0% once and then you actually have the app do<00:21:58.760> all<00:21:58.880> of<00:21:59.039> the<00:21:59.200> work<00:22:00.039> but<00:22:00.200> it<00:22:00.400> gets<00:22:00.600> a<00:22:00.720> little 00:22:00.990 --> 00:22:01.000 align:start position:0% do all of the work but it gets a little 00:22:01.000 --> 00:22:03.830 align:start position:0% do all of the work but it gets a little complicated<00:22:01.679> because<00:22:02.320> um<00:22:02.720> as<00:22:02.840> I<00:22:03.000> told<00:22:03.279> you 00:22:03.830 --> 00:22:03.840 align:start position:0% complicated because um as I told you 00:22:03.840 --> 00:22:06.710 align:start position:0% complicated because um as I told you like<00:22:04.840> the<00:22:05.039> app<00:22:05.360> doesn't<00:22:05.760> really<00:22:06.120> have<00:22:06.400> this 00:22:06.710 --> 00:22:06.720 align:start position:0% like the app doesn't really have this 00:22:06.720 --> 00:22:09.390 align:start position:0% like the app doesn't really have this concept<00:22:07.159> of<00:22:07.760> how<00:22:07.919> to<00:22:08.200> actually<00:22:08.480> create<00:22:09.039> the 00:22:09.390 --> 00:22:09.400 align:start position:0% concept of how to actually create the 00:22:09.400 --> 00:22:11.149 align:start position:0% concept of how to actually create the transactions<00:22:10.039> for<00:22:10.240> your<00:22:10.400> smart<00:22:10.760> contract 00:22:11.149 --> 00:22:11.159 align:start position:0% transactions for your smart contract 00:22:11.159 --> 00:22:13.310 align:start position:0% transactions for your smart contract account<00:22:11.480> because<00:22:12.120> you<00:22:12.279> might<00:22:12.480> have<00:22:12.679> installed 00:22:13.310 --> 00:22:13.320 align:start position:0% account because you might have installed 00:22:13.320 --> 00:22:15.789 align:start position:0% account because you might have installed certain<00:22:13.799> modules<00:22:14.559> and<00:22:14.760> those<00:22:14.960> modules<00:22:15.640> have 00:22:15.789 --> 00:22:15.799 align:start position:0% certain modules and those modules have 00:22:15.799 --> 00:22:18.350 align:start position:0% certain modules and those modules have to<00:22:16.120> actually<00:22:16.440> operate<00:22:16.919> very<00:22:17.240> differently<00:22:18.240> uh 00:22:18.350 --> 00:22:18.360 align:start position:0% to actually operate very differently uh 00:22:18.360 --> 00:22:19.950 align:start position:0% to actually operate very differently uh so<00:22:18.520> we're<00:22:18.840> currently<00:22:19.279> working<00:22:19.720> and<00:22:19.840> the 00:22:19.950 --> 00:22:19.960 align:start position:0% so we're currently working and the 00:22:19.960 --> 00:22:22.549 align:start position:0% so we're currently working and the reason<00:22:20.240> it<00:22:20.360> says<00:22:20.640> XXX<00:22:21.480> because<00:22:22.080> it's<00:22:22.240> is 00:22:22.549 --> 00:22:22.559 align:start position:0% reason it says XXX because it's is 00:22:22.559 --> 00:22:25.430 align:start position:0% reason it says XXX because it's is really<00:22:22.760> work<00:22:23.000> in<00:22:23.279> progress<00:22:24.159> uh<00:22:24.320> this<00:22:24.520> new<00:22:24.840> API 00:22:25.430 --> 00:22:25.440 align:start position:0% really work in progress uh this new API 00:22:25.440 --> 00:22:27.950 align:start position:0% really work in progress uh this new API that<00:22:25.640> actually<00:22:25.960> allows<00:22:26.360> you<00:22:26.520> to<00:22:27.240> delegate<00:22:27.760> to 00:22:27.950 --> 00:22:27.960 align:start position:0% that actually allows you to delegate to 00:22:27.960 --> 00:22:30.190 align:start position:0% that actually allows you to delegate to the<00:22:28.080> application<00:22:28.720> to<00:22:28.960> prepare<00:22:29.360> the<00:22:29.520> calls<00:22:30.000> and 00:22:30.190 --> 00:22:30.200 align:start position:0% the application to prepare the calls and 00:22:30.200 --> 00:22:32.950 align:start position:0% the application to prepare the calls and actually<00:22:30.640> generate<00:22:31.559> the<00:22:31.760> signatures 00:22:32.950 --> 00:22:32.960 align:start position:0% actually generate the signatures 00:22:32.960 --> 00:22:36.269 align:start position:0% actually generate the signatures independently<00:22:33.960> so<00:22:34.559> we<00:22:35.000> come<00:22:35.640> almost<00:22:35.960> to<00:22:36.159> the 00:22:36.269 --> 00:22:36.279 align:start position:0% independently so we come almost to the 00:22:36.279 --> 00:22:39.789 align:start position:0% independently so we come almost to the end<00:22:36.880> where<00:22:37.240> now<00:22:37.480> we<00:22:37.679> have<00:22:37.880> Smart<00:22:38.240> sessions<00:22:39.120> so 00:22:39.789 --> 00:22:39.799 align:start position:0% end where now we have Smart sessions so 00:22:39.799 --> 00:22:41.990 align:start position:0% end where now we have Smart sessions so you<00:22:40.200> now<00:22:40.520> have<00:22:40.679> a<00:22:40.840> smart<00:22:41.200> account<00:22:41.600> you've<00:22:41.840> been 00:22:41.990 --> 00:22:42.000 align:start position:0% you now have a smart account you've been 00:22:42.000 --> 00:22:44.669 align:start position:0% you now have a smart account you've been able<00:22:42.240> to<00:22:42.440> log<00:22:42.679> in<00:22:42.840> in<00:22:42.960> a<00:22:43.120> single<00:22:43.559> click<00:22:44.240> you 00:22:44.669 --> 00:22:44.679 align:start position:0% able to log in in a single click you 00:22:44.679 --> 00:22:46.870 align:start position:0% able to log in in a single click you have<00:22:44.960> a<00:22:45.159> pay<00:22:45.440> master<00:22:45.799> that<00:22:45.960> subsidizes<00:22:46.600> your 00:22:46.870 --> 00:22:46.880 align:start position:0% have a pay master that subsidizes your 00:22:46.880 --> 00:22:49.870 align:start position:0% have a pay master that subsidizes your gas<00:22:47.520> and<00:22:47.720> now<00:22:48.000> the<00:22:48.200> application<00:22:49.120> using<00:22:49.520> the 00:22:49.870 --> 00:22:49.880 align:start position:0% gas and now the application using the 00:22:49.880 --> 00:22:52.470 align:start position:0% gas and now the application using the previous<00:22:50.400> standard<00:22:50.840> or<00:22:51.000> wallet<00:22:51.320> prepar<00:22:51.679> calls 00:22:52.470 --> 00:22:52.480 align:start position:0% previous standard or wallet prepar calls 00:22:52.480 --> 00:22:55.029 align:start position:0% previous standard or wallet prepar calls has<00:22:52.679> the<00:22:52.880> ability<00:22:53.480> of<00:22:53.720> signing<00:22:54.279> signatures<00:22:54.840> on 00:22:55.029 --> 00:22:55.039 align:start position:0% has the ability of signing signatures on 00:22:55.039 --> 00:22:58.590 align:start position:0% has the ability of signing signatures on your<00:22:55.279> behalf<00:22:56.240> uh<00:22:56.400> because<00:22:57.200> using<00:22:57.640> this<00:22:57.880> API 00:22:58.590 --> 00:22:58.600 align:start position:0% your behalf uh because using this API 00:22:58.600 --> 00:23:00.510 align:start position:0% your behalf uh because using this API they<00:22:58.720> know<00:22:59.000> exactly<00:22:59.440> how<00:22:59.559> to<00:22:59.799> operate 00:23:00.510 --> 00:23:00.520 align:start position:0% they know exactly how to operate 00:23:00.520 --> 00:23:02.789 align:start position:0% they know exactly how to operate independently<00:23:01.520> uh<00:23:01.640> we<00:23:01.840> basically<00:23:02.320> reduce 00:23:02.789 --> 00:23:02.799 align:start position:0% independently uh we basically reduce 00:23:02.799 --> 00:23:05.230 align:start position:0% independently uh we basically reduce less<00:23:03.039> clicks<00:23:03.360> is<00:23:03.559> more<00:23:04.240> now<00:23:04.480> the<00:23:04.679> only<00:23:05.000> thing 00:23:05.230 --> 00:23:05.240 align:start position:0% less clicks is more now the only thing 00:23:05.240 --> 00:23:07.789 align:start position:0% less clicks is more now the only thing we<00:23:05.440> need<00:23:05.600> to<00:23:05.760> tell<00:23:06.000> to<00:23:06.200> this<00:23:06.360> application<00:23:07.080> is 00:23:07.789 --> 00:23:07.799 align:start position:0% we need to tell to this application is 00:23:07.799 --> 00:23:10.430 align:start position:0% we need to tell to this application is what<00:23:08.159> can<00:23:08.400> you<00:23:08.640> do<00:23:09.159> with<00:23:09.360> this<00:23:10.000> uh<00:23:10.120> smart 00:23:10.430 --> 00:23:10.440 align:start position:0% what can you do with this uh smart 00:23:10.440 --> 00:23:12.110 align:start position:0% what can you do with this uh smart session<00:23:10.960> and<00:23:11.120> this<00:23:11.240> is<00:23:11.400> where<00:23:11.600> the<00:23:11.799> final 00:23:12.110 --> 00:23:12.120 align:start position:0% session and this is where the final 00:23:12.120 --> 00:23:14.149 align:start position:0% session and this is where the final standard<00:23:12.559> comes<00:23:12.799> in<00:23:13.320> which<00:23:13.440> is<00:23:13.720> Grant 00:23:14.149 --> 00:23:14.159 align:start position:0% standard comes in which is Grant 00:23:14.159 --> 00:23:16.990 align:start position:0% standard comes in which is Grant permissions<00:23:14.799> from<00:23:15.080> wallets<00:23:15.760> so<00:23:16.480> the 00:23:16.990 --> 00:23:17.000 align:start position:0% permissions from wallets so the 00:23:17.000 --> 00:23:18.630 align:start position:0% permissions from wallets so the application<00:23:17.520> is<00:23:17.720> able<00:23:17.960> to<00:23:18.200> request 00:23:18.630 --> 00:23:18.640 align:start position:0% application is able to request 00:23:18.640 --> 00:23:20.310 align:start position:0% application is able to request permissions<00:23:19.240> the<00:23:19.360> user<00:23:19.720> approves<00:23:20.120> those 00:23:20.310 --> 00:23:20.320 align:start position:0% permissions the user approves those 00:23:20.320 --> 00:23:22.470 align:start position:0% permissions the user approves those permissions<00:23:21.159> and<00:23:21.320> those<00:23:21.520> permissions<00:23:22.000> can<00:23:22.159> be 00:23:22.470 --> 00:23:22.480 align:start position:0% permissions and those permissions can be 00:23:22.480 --> 00:23:24.669 align:start position:0% permissions and those permissions can be encoded<00:23:23.120> as<00:23:23.240> we<00:23:23.360> saw<00:23:23.559> with<00:23:23.720> the<00:23:23.840> Google<00:23:24.120> login 00:23:24.669 --> 00:23:24.679 align:start position:0% encoded as we saw with the Google login 00:23:24.679 --> 00:23:26.870 align:start position:0% encoded as we saw with the Google login as<00:23:24.919> part<00:23:25.080> of<00:23:25.200> the<00:23:25.360> sign<00:23:25.640> with<00:23:25.880> ethereum<00:23:26.760> and 00:23:26.870 --> 00:23:26.880 align:start position:0% as part of the sign with ethereum and 00:23:26.880 --> 00:23:29.269 align:start position:0% as part of the sign with ethereum and then<00:23:27.120> once<00:23:27.279> you<00:23:27.640> return<00:23:27.919> that<00:23:28.120> cont<00:23:28.760> to<00:23:28.960> the 00:23:29.269 --> 00:23:29.279 align:start position:0% then once you return that cont to the 00:23:29.279 --> 00:23:31.190 align:start position:0% then once you return that cont to the application<00:23:29.919> the<00:23:30.039> application<00:23:30.480> can<00:23:30.679> send<00:23:30.960> it 00:23:31.190 --> 00:23:31.200 align:start position:0% application the application can send it 00:23:31.200 --> 00:23:33.430 align:start position:0% application the application can send it directly<00:23:31.559> to<00:23:31.679> the<00:23:31.799> bundler<00:23:32.640> so<00:23:32.880> now<00:23:33.080> we<00:23:33.200> don't 00:23:33.430 --> 00:23:33.440 align:start position:0% directly to the bundler so now we don't 00:23:33.440 --> 00:23:35.669 align:start position:0% directly to the bundler so now we don't even<00:23:33.760> need<00:23:34.039> to<00:23:34.240> have<00:23:34.400> the<00:23:34.559> wallet<00:23:34.880> in<00:23:35.000> the<00:23:35.120> loop 00:23:35.669 --> 00:23:35.679 align:start position:0% even need to have the wallet in the loop 00:23:35.679 --> 00:23:37.310 align:start position:0% even need to have the wallet in the loop and<00:23:35.840> the<00:23:36.000> application<00:23:36.480> is<00:23:36.640> able<00:23:36.840> to<00:23:36.960> use<00:23:37.159> the 00:23:37.310 --> 00:23:37.320 align:start position:0% and the application is able to use the 00:23:37.320 --> 00:23:41.029 align:start position:0% and the application is able to use the smart<00:23:37.640> session<00:23:38.159> to<00:23:38.600> operate<00:23:39.600> your<00:23:40.400> uh<00:23:40.520> wallet 00:23:41.029 --> 00:23:41.039 align:start position:0% smart session to operate your uh wallet 00:23:41.039 --> 00:23:43.110 align:start position:0% smart session to operate your uh wallet because<00:23:41.320> you<00:23:41.720> basically<00:23:42.159> said<00:23:42.480> you<00:23:42.640> can<00:23:42.799> only 00:23:43.110 --> 00:23:43.120 align:start position:0% because you basically said you can only 00:23:43.120 --> 00:23:45.310 align:start position:0% because you basically said you can only do<00:23:43.679> this<00:23:43.880> much<00:23:44.159> for<00:23:44.480> this<00:23:44.679> amount<00:23:44.880> of<00:23:45.080> time 00:23:45.310 --> 00:23:45.320 align:start position:0% do this much for this amount of time 00:23:45.320 --> 00:23:47.390 align:start position:0% do this much for this amount of time with<00:23:45.520> this<00:23:45.679> amount<00:23:45.880> of<00:23:46.039> tokens<00:23:46.960> and<00:23:47.120> you 00:23:47.390 --> 00:23:47.400 align:start position:0% with this amount of tokens and you 00:23:47.400 --> 00:23:49.110 align:start position:0% with this amount of tokens and you basically<00:23:47.799> created<00:23:48.200> the<00:23:48.440> rules<00:23:48.760> for<00:23:48.960> the 00:23:49.110 --> 00:23:49.120 align:start position:0% basically created the rules for the 00:23:49.120 --> 00:23:51.710 align:start position:0% basically created the rules for the bundler<00:23:49.600> to<00:23:50.200> understand<00:23:50.840> that<00:23:51.120> this<00:23:51.320> app<00:23:51.559> can 00:23:51.710 --> 00:23:51.720 align:start position:0% bundler to understand that this app can 00:23:51.720 --> 00:23:54.789 align:start position:0% bundler to understand that this app can sign<00:23:52.000> on<00:23:52.200> your<00:23:52.400> behalf<00:23:53.080> with<00:23:53.200> a<00:23:53.360> smart<00:23:53.799> account 00:23:54.789 --> 00:23:54.799 align:start position:0% sign on your behalf with a smart account 00:23:54.799 --> 00:23:57.070 align:start position:0% sign on your behalf with a smart account but<00:23:54.960> there's<00:23:55.279> some<00:23:55.520> concerns<00:23:56.000> about<00:23:56.640> you<00:23:56.799> know 00:23:57.070 --> 00:23:57.080 align:start position:0% but there's some concerns about you know 00:23:57.080 --> 00:23:59.390 align:start position:0% but there's some concerns about you know if<00:23:57.279> the<00:23:57.559> app<00:23:57.960> actually 00:23:59.390 --> 00:23:59.400 align:start position:0% if the app actually 00:23:59.400 --> 00:24:02.149 align:start position:0% if the app actually has<00:23:59.760> control<00:24:00.279> of<00:24:00.440> a<00:24:00.720> signer<00:24:01.480> that<00:24:01.679> controls 00:24:02.149 --> 00:24:02.159 align:start position:0% has control of a signer that controls 00:24:02.159 --> 00:24:04.269 align:start position:0% has control of a signer that controls your<00:24:02.400> wallet<00:24:03.320> uh<00:24:03.440> it<00:24:03.559> can<00:24:03.720> cause<00:24:04.000> some 00:24:04.269 --> 00:24:04.279 align:start position:0% your wallet uh it can cause some 00:24:04.279 --> 00:24:05.750 align:start position:0% your wallet uh it can cause some problems<00:24:04.679> I<00:24:04.760> don't<00:24:04.919> know<00:24:05.080> how<00:24:05.240> much<00:24:05.440> you<00:24:05.640> guys 00:24:05.750 --> 00:24:05.760 align:start position:0% problems I don't know how much you guys 00:24:05.760 --> 00:24:08.230 align:start position:0% problems I don't know how much you guys know<00:24:06.000> about<00:24:06.240> web<00:24:06.600> security<00:24:07.200> but<00:24:07.440> browsers<00:24:08.000> are 00:24:08.230 --> 00:24:08.240 align:start position:0% know about web security but browsers are 00:24:08.240 --> 00:24:11.029 align:start position:0% know about web security but browsers are not<00:24:08.520> very<00:24:08.760> secure<00:24:09.559> so<00:24:09.919> this<00:24:10.039> is<00:24:10.279> where<00:24:10.600> I<00:24:10.760> also 00:24:11.029 --> 00:24:11.039 align:start position:0% not very secure so this is where I also 00:24:11.039 --> 00:24:13.269 align:start position:0% not very secure so this is where I also wanted<00:24:11.320> to<00:24:11.559> bring<00:24:11.880> back<00:24:12.200> the<00:24:12.360> concept<00:24:12.720> of<00:24:12.919> pass 00:24:13.269 --> 00:24:13.279 align:start position:0% wanted to bring back the concept of pass 00:24:13.279 --> 00:24:16.950 align:start position:0% wanted to bring back the concept of pass keys<00:24:13.960> because<00:24:14.400> now<00:24:15.120> your<00:24:15.520> app<00:24:15.880> can<00:24:16.279> generate<00:24:16.720> a 00:24:16.950 --> 00:24:16.960 align:start position:0% keys because now your app can generate a 00:24:16.960 --> 00:24:18.950 align:start position:0% keys because now your app can generate a pass<00:24:17.200> key<00:24:17.440> for<00:24:17.640> your<00:24:17.799> smart<00:24:18.159> account<00:24:18.720> and 00:24:18.950 --> 00:24:18.960 align:start position:0% pass key for your smart account and 00:24:18.960 --> 00:24:21.029 align:start position:0% pass key for your smart account and control<00:24:19.400> it<00:24:19.760> under<00:24:20.120> the<00:24:20.240> certain<00:24:20.600> permissions 00:24:21.029 --> 00:24:21.039 align:start position:0% control it under the certain permissions 00:24:21.039 --> 00:24:23.630 align:start position:0% control it under the certain permissions that<00:24:21.159> you<00:24:21.360> give<00:24:22.080> and<00:24:22.240> this<00:24:22.640> then<00:24:22.919> looks<00:24:23.279> like 00:24:23.630 --> 00:24:23.640 align:start position:0% that you give and this then looks like 00:24:23.640 --> 00:24:26.470 align:start position:0% that you give and this then looks like you<00:24:23.760> know<00:24:24.760> these<00:24:25.080> pass<00:24:25.399> keys<00:24:25.799> and<00:24:25.960> then<00:24:26.200> your 00:24:26.470 --> 00:24:26.480 align:start position:0% you know these pass keys and then your 00:24:26.480 --> 00:24:28.710 align:start position:0% you know these pass keys and then your wallet<00:24:26.960> essentially<00:24:27.440> becomes<00:24:27.760> a<00:24:27.960> pass<00:24:28.200> key 00:24:28.710 --> 00:24:28.720 align:start position:0% wallet essentially becomes a pass key 00:24:28.720 --> 00:24:30.830 align:start position:0% wallet essentially becomes a pass key for<00:24:29.039> that<00:24:29.279> specific<00:24:29.760> app<00:24:30.159> under<00:24:30.480> certain 00:24:30.830 --> 00:24:30.840 align:start position:0% for that specific app under certain 00:24:30.840 --> 00:24:33.070 align:start position:0% for that specific app under certain permissions<00:24:31.840> so<00:24:32.399> the<00:24:32.480> only<00:24:32.720> thing<00:24:32.840> that<00:24:32.960> we 00:24:33.070 --> 00:24:33.080 align:start position:0% permissions so the only thing that we 00:24:33.080 --> 00:24:34.750 align:start position:0% permissions so the only thing that we need<00:24:33.200> to<00:24:33.360> do<00:24:33.600> now<00:24:33.799> is<00:24:33.960> actually<00:24:34.240> upgrade<00:24:34.640> the 00:24:34.750 --> 00:24:34.760 align:start position:0% need to do now is actually upgrade the 00:24:34.760 --> 00:24:38.430 align:start position:0% need to do now is actually upgrade the evm<00:24:35.399> because<00:24:36.080> one<00:24:36.399> thing<00:24:36.679> that<00:24:37.080> the<00:24:37.240> evm<00:24:37.880> has<00:24:38.120> a 00:24:38.430 --> 00:24:38.440 align:start position:0% evm because one thing that the evm has a 00:24:38.440 --> 00:24:40.669 align:start position:0% evm because one thing that the evm has a problem<00:24:38.880> is<00:24:39.159> actually<00:24:39.600> with<00:24:40.000> Computing 00:24:40.669 --> 00:24:40.679 align:start position:0% problem is actually with Computing 00:24:40.679 --> 00:24:44.350 align:start position:0% problem is actually with Computing different<00:24:41.000> crypto<00:24:41.840> curves<00:24:42.600> so<00:24:42.919> if<00:24:43.120> we<00:24:43.480> add<00:24:44.000> the 00:24:44.350 --> 00:24:44.360 align:start position:0% different crypto curves so if we add the 00:24:44.360 --> 00:24:46.430 align:start position:0% different crypto curves so if we add the actual<00:24:44.760> curve<00:24:45.039> for<00:24:45.240> passys<00:24:45.919> into<00:24:46.279> the 00:24:46.430 --> 00:24:46.440 align:start position:0% actual curve for passys into the 00:24:46.440 --> 00:24:48.909 align:start position:0% actual curve for passys into the blockchain<00:24:47.240> then<00:24:47.480> we<00:24:47.720> actually<00:24:48.200> would<00:24:48.520> have 00:24:48.909 --> 00:24:48.919 align:start position:0% blockchain then we actually would have 00:24:48.919 --> 00:24:52.710 align:start position:0% blockchain then we actually would have um<00:24:49.200> even<00:24:50.000> cheaper<00:24:50.640> gas<00:24:51.080> for<00:24:51.399> everyone<00:24:52.399> however 00:24:52.710 --> 00:24:52.720 align:start position:0% um even cheaper gas for everyone however 00:24:52.720 --> 00:24:54.269 align:start position:0% um even cheaper gas for everyone however this<00:24:52.799> is<00:24:53.039> actually<00:24:53.559> something<00:24:53.919> that's<00:24:54.120> been 00:24:54.269 --> 00:24:54.279 align:start position:0% this is actually something that's been 00:24:54.279 --> 00:24:56.630 align:start position:0% this is actually something that's been in<00:24:54.480> progress<00:24:54.799> with<00:24:54.960> some<00:24:55.120> rollups<00:24:56.000> but<00:24:56.240> not 00:24:56.630 --> 00:24:56.640 align:start position:0% in progress with some rollups but not 00:24:56.640 --> 00:24:59.230 align:start position:0% in progress with some rollups but not necessarily<00:24:57.399> for<00:24:57.720> the 00:24:59.230 --> 00:24:59.240 align:start position:0% necessarily for the 00:24:59.240 --> 00:25:01.870 align:start position:0% necessarily for the so<00:24:59.720> you<00:24:59.880> might<00:25:00.159> think<00:25:00.640> that<00:25:01.279> I'm<00:25:01.399> from<00:25:01.600> wallet 00:25:01.870 --> 00:25:01.880 align:start position:0% so you might think that I'm from wallet 00:25:01.880 --> 00:25:04.310 align:start position:0% so you might think that I'm from wallet connect<00:25:02.320> if<00:25:02.679> the<00:25:03.240> app<00:25:03.559> does<00:25:03.799> everything<00:25:04.120> for 00:25:04.310 --> 00:25:04.320 align:start position:0% connect if the app does everything for 00:25:04.320 --> 00:25:05.990 align:start position:0% connect if the app does everything for the<00:25:04.480> wallet<00:25:04.799> what<00:25:04.919> is<00:25:05.120> actually<00:25:05.399> being 00:25:05.990 --> 00:25:06.000 align:start position:0% the wallet what is actually being 00:25:06.000 --> 00:25:08.750 align:start position:0% the wallet what is actually being connected<00:25:07.000> realistically<00:25:08.000> you've 00:25:08.750 --> 00:25:08.760 align:start position:0% connected realistically you've 00:25:08.760 --> 00:25:12.029 align:start position:0% connected realistically you've essentially<00:25:09.600> logged<00:25:10.000> in<00:25:10.159> into<00:25:10.559> your<00:25:11.320> app<00:25:11.840> and 00:25:12.029 --> 00:25:12.039 align:start position:0% essentially logged in into your app and 00:25:12.039 --> 00:25:14.430 align:start position:0% essentially logged in into your app and you've<00:25:12.399> passed<00:25:12.760> on<00:25:13.039> the<00:25:13.240> wallet<00:25:13.760> inside<00:25:14.159> your 00:25:14.430 --> 00:25:14.440 align:start position:0% you've passed on the wallet inside your 00:25:14.440 --> 00:25:15.909 align:start position:0% you've passed on the wallet inside your app<00:25:14.720> it's<00:25:14.840> almost<00:25:15.120> like<00:25:15.240> you<00:25:15.520> have<00:25:15.720> the 00:25:15.909 --> 00:25:15.919 align:start position:0% app it's almost like you have the 00:25:15.919 --> 00:25:18.750 align:start position:0% app it's almost like you have the concept<00:25:16.279> of<00:25:16.360> a<00:25:16.520> mini<00:25:16.880> wallet<00:25:17.600> so<00:25:18.080> we<00:25:18.279> basically 00:25:18.750 --> 00:25:18.760 align:start position:0% concept of a mini wallet so we basically 00:25:18.760 --> 00:25:20.669 align:start position:0% concept of a mini wallet so we basically have<00:25:19.080> almost<00:25:19.360> like<00:25:19.520> what<00:25:19.679> we<00:25:19.840> had<00:25:19.960> in<00:25:20.120> web<00:25:20.320> 2 00:25:20.669 --> 00:25:20.679 align:start position:0% have almost like what we had in web 2 00:25:20.679 --> 00:25:22.630 align:start position:0% have almost like what we had in web 2 but<00:25:20.840> now<00:25:21.039> the<00:25:21.159> authentication<00:25:21.880> lives<00:25:22.360> on<00:25:22.480> the 00:25:22.630 --> 00:25:22.640 align:start position:0% but now the authentication lives on the 00:25:22.640 --> 00:25:24.950 align:start position:0% but now the authentication lives on the app<00:25:23.159> under<00:25:23.520> certain<00:25:24.120> condition<00:25:24.520> so<00:25:24.640> you<00:25:24.799> might 00:25:24.950 --> 00:25:24.960 align:start position:0% app under certain condition so you might 00:25:24.960 --> 00:25:27.310 align:start position:0% app under certain condition so you might be<00:25:25.080> thinking<00:25:25.520> are<00:25:25.640> we<00:25:25.840> done<00:25:26.559> is<00:25:26.720> this<00:25:26.880> the<00:25:27.080> end 00:25:27.310 --> 00:25:27.320 align:start position:0% be thinking are we done is this the end 00:25:27.320 --> 00:25:28.990 align:start position:0% be thinking are we done is this the end game<00:25:27.640> we<00:25:27.880> fixed 00:25:28.990 --> 00:25:29.000 align:start position:0% game we fixed 00:25:29.000 --> 00:25:32.070 align:start position:0% game we fixed everything<00:25:30.000> um<00:25:30.480> not<00:25:30.760> really<00:25:31.279> because<00:25:31.840> one 00:25:32.070 --> 00:25:32.080 align:start position:0% everything um not really because one 00:25:32.080 --> 00:25:34.549 align:start position:0% everything um not really because one thing<00:25:32.399> that<00:25:32.960> I<00:25:33.120> didn't<00:25:33.480> explain<00:25:34.000> is<00:25:34.159> that<00:25:34.360> this 00:25:34.549 --> 00:25:34.559 align:start position:0% thing that I didn't explain is that this 00:25:34.559 --> 00:25:37.470 align:start position:0% thing that I didn't explain is that this only<00:25:34.880> works<00:25:35.320> in<00:25:35.440> the<00:25:35.600> same<00:25:35.880> blockchain<00:25:36.640> and<00:25:37.200> we 00:25:37.470 --> 00:25:37.480 align:start position:0% only works in the same blockchain and we 00:25:37.480 --> 00:25:40.310 align:start position:0% only works in the same blockchain and we currently<00:25:38.080> have<00:25:39.000> I<00:25:39.080> forgot<00:25:39.440> the<00:25:39.559> number<00:25:40.039> like 00:25:40.310 --> 00:25:40.320 align:start position:0% currently have I forgot the number like 00:25:40.320 --> 00:25:42.710 align:start position:0% currently have I forgot the number like 500<00:25:40.919> rollups<00:25:41.440> or<00:25:41.600> something<00:25:42.080> like<00:25:42.240> it<00:25:42.480> gets 00:25:42.710 --> 00:25:42.720 align:start position:0% 500 rollups or something like it gets 00:25:42.720 --> 00:25:44.990 align:start position:0% 500 rollups or something like it gets really<00:25:43.000> complicated<00:25:43.919> so<00:25:44.360> what<00:25:44.480> if<00:25:44.679> smart 00:25:44.990 --> 00:25:45.000 align:start position:0% really complicated so what if smart 00:25:45.000 --> 00:25:46.990 align:start position:0% really complicated so what if smart sessions<00:25:45.440> could<00:25:45.640> actually<00:25:45.960> function<00:25:46.480> across 00:25:46.990 --> 00:25:47.000 align:start position:0% sessions could actually function across 00:25:47.000 --> 00:25:49.630 align:start position:0% sessions could actually function across all<00:25:47.320> chains<00:25:48.200> so<00:25:48.399> I'm<00:25:48.520> going<00:25:48.640> to<00:25:49.120> bring<00:25:49.399> some 00:25:49.630 --> 00:25:49.640 align:start position:0% all chains so I'm going to bring some 00:25:49.640 --> 00:25:51.669 align:start position:0% all chains so I'm going to bring some new<00:25:49.840> lingo<00:25:50.480> into<00:25:50.720> the<00:25:50.880> table<00:25:51.320> and<00:25:51.440> we're<00:25:51.600> going 00:25:51.669 --> 00:25:51.679 align:start position:0% new lingo into the table and we're going 00:25:51.679 --> 00:25:54.029 align:start position:0% new lingo into the table and we're going to<00:25:51.880> talk<00:25:52.120> about<00:25:52.480> chain<00:25:52.919> abstraction<00:25:53.919> I'm 00:25:54.029 --> 00:25:54.039 align:start position:0% to talk about chain abstraction I'm 00:25:54.039 --> 00:25:55.149 align:start position:0% to talk about chain abstraction I'm joking<00:25:54.360> we're<00:25:54.520> not<00:25:54.640> going<00:25:54.720> to<00:25:54.880> talk<00:25:55.000> about 00:25:55.149 --> 00:25:55.159 align:start position:0% joking we're not going to talk about 00:25:55.159 --> 00:25:56.830 align:start position:0% joking we're not going to talk about chain<00:25:55.440> abstraction<00:25:56.000> but<00:25:56.120> this<00:25:56.240> is<00:25:56.360> the<00:25:56.520> next 00:25:56.830 --> 00:25:56.840 align:start position:0% chain abstraction but this is the next 00:25:56.840 --> 00:25:59.190 align:start position:0% chain abstraction but this is the next game<00:25:57.240> right<00:25:57.720> we<00:25:57.919> basically<00:25:58.279> Bally<00:25:58.880> have 00:25:59.190 --> 00:25:59.200 align:start position:0% game right we basically Bally have 00:25:59.200 --> 00:26:01.630 align:start position:0% game right we basically Bally have wallets<00:25:59.640> moving<00:25:59.919> to<00:26:00.120> Smart<00:26:00.480> accounts<00:26:01.080> we<00:26:01.279> now 00:26:01.630 --> 00:26:01.640 align:start position:0% wallets moving to Smart accounts we now 00:26:01.640 --> 00:26:03.830 align:start position:0% wallets moving to Smart accounts we now as<00:26:01.799> part<00:26:01.960> of<00:26:02.080> wallet<00:26:02.399> connect<00:26:03.200> we<00:26:03.440> have<00:26:03.679> the 00:26:03.830 --> 00:26:03.840 align:start position:0% as part of wallet connect we have the 00:26:03.840 --> 00:26:06.269 align:start position:0% as part of wallet connect we have the ability<00:26:04.279> to<00:26:04.840> introduce<00:26:05.399> smart<00:26:05.720> sessions<00:26:06.080> to 00:26:06.269 --> 00:26:06.279 align:start position:0% ability to introduce smart sessions to 00:26:06.279 --> 00:26:08.190 align:start position:0% ability to introduce smart sessions to make<00:26:06.440> the<00:26:06.559> user<00:26:06.880> experience<00:26:07.360> better<00:26:08.039> and 00:26:08.190 --> 00:26:08.200 align:start position:0% make the user experience better and 00:26:08.200 --> 00:26:10.909 align:start position:0% make the user experience better and chain<00:26:08.480> abstraction<00:26:09.000> is<00:26:09.159> the<00:26:09.320> next<00:26:09.640> game<00:26:10.320> where 00:26:10.909 --> 00:26:10.919 align:start position:0% chain abstraction is the next game where 00:26:10.919 --> 00:26:13.269 align:start position:0% chain abstraction is the next game where bringing<00:26:11.399> interruptable<00:26:12.200> tokens<00:26:12.840> magic 00:26:13.269 --> 00:26:13.279 align:start position:0% bringing interruptable tokens magic 00:26:13.279 --> 00:26:17.149 align:start position:0% bringing interruptable tokens magic spend<00:26:14.159> uh<00:26:14.640> 7702<00:26:15.640> and<00:26:16.240> like<00:26:16.520> Bridges<00:26:17.000> and 00:26:17.149 --> 00:26:17.159 align:start position:0% spend uh 7702 and like Bridges and 00:26:17.159 --> 00:26:19.350 align:start position:0% spend uh 7702 and like Bridges and solvers<00:26:17.600> and<00:26:17.720> bundlers<00:26:18.320> we<00:26:18.399> can<00:26:18.760> really<00:26:19.159> have 00:26:19.350 --> 00:26:19.360 align:start position:0% solvers and bundlers we can really have 00:26:19.360 --> 00:26:22.029 align:start position:0% solvers and bundlers we can really have the<00:26:19.520> chain<00:26:20.080> abstraction<00:26:21.080> uh<00:26:21.240> improve<00:26:21.679> the 00:26:22.029 --> 00:26:22.039 align:start position:0% the chain abstraction uh improve the 00:26:22.039 --> 00:26:24.510 align:start position:0% the chain abstraction uh improve the experience<00:26:23.039> and<00:26:23.520> then<00:26:23.720> you<00:26:23.880> might<00:26:24.080> think<00:26:24.399> what 00:26:24.510 --> 00:26:24.520 align:start position:0% experience and then you might think what 00:26:24.520 --> 00:26:26.590 align:start position:0% experience and then you might think what is<00:26:24.720> the<00:26:24.919> future<00:26:25.240> of<00:26:25.440> wallets<00:26:25.919> like<00:26:26.120> before<00:26:26.440> you 00:26:26.590 --> 00:26:26.600 align:start position:0% is the future of wallets like before you 00:26:26.600 --> 00:26:28.830 align:start position:0% is the future of wallets like before you just<00:26:26.760> had<00:26:26.960> like<00:26:27.240> apps<00:26:27.520> and<00:26:27.679> wallets<00:26:28.600> through 00:26:28.830 --> 00:26:28.840 align:start position:0% just had like apps and wallets through 00:26:28.840 --> 00:26:31.070 align:start position:0% just had like apps and wallets through wall<00:26:29.159> connect<00:26:29.880> and<00:26:30.039> now<00:26:30.279> you<00:26:30.480> have<00:26:30.840> like 00:26:31.070 --> 00:26:31.080 align:start position:0% wall connect and now you have like 00:26:31.080 --> 00:26:34.029 align:start position:0% wall connect and now you have like sessions<00:26:31.559> and<00:26:31.720> signs<00:26:32.159> in<00:26:32.360> Pay<00:26:32.760> Master<00:26:33.760> most 00:26:34.029 --> 00:26:34.039 align:start position:0% sessions and signs in Pay Master most 00:26:34.039 --> 00:26:36.470 align:start position:0% sessions and signs in Pay Master most importantly<00:26:34.919> we<00:26:35.480> want<00:26:35.760> to<00:26:35.960> work<00:26:36.279> on 00:26:36.470 --> 00:26:36.480 align:start position:0% importantly we want to work on 00:26:36.480 --> 00:26:38.549 align:start position:0% importantly we want to work on redefining<00:26:37.200> what<00:26:37.320> is<00:26:37.480> the<00:26:37.640> wallet<00:26:38.080> experience 00:26:38.549 --> 00:26:38.559 align:start position:0% redefining what is the wallet experience 00:26:38.559 --> 00:26:42.149 align:start position:0% redefining what is the wallet experience for<00:26:38.799> web<00:26:39.080> 3<00:26:39.799> and<00:26:40.000> making<00:26:40.320> it<00:26:40.760> as<00:26:41.440> convenient 00:26:42.149 --> 00:26:42.159 align:start position:0% for web 3 and making it as convenient 00:26:42.159 --> 00:26:44.190 align:start position:0% for web 3 and making it as convenient and<00:26:42.360> secure<00:26:42.760> as<00:26:43.000> possible<00:26:43.720> but<00:26:43.919> most 00:26:44.190 --> 00:26:44.200 align:start position:0% and secure as possible but most 00:26:44.200 --> 00:26:46.149 align:start position:0% and secure as possible but most importantly<00:26:44.840> we<00:26:44.960> want<00:26:45.039> to<00:26:45.200> make<00:26:45.360> sure<00:26:45.720> that 00:26:46.149 --> 00:26:46.159 align:start position:0% importantly we want to make sure that 00:26:46.159 --> 00:26:49.590 align:start position:0% importantly we want to make sure that less<00:26:46.480> clicks<00:26:46.919> is<00:26:47.159> more<00:26:47.679> and<00:26:47.919> people<00:26:48.480> have<00:26:49.320> the 00:26:49.590 --> 00:26:49.600 align:start position:0% less clicks is more and people have the 00:26:49.600 --> 00:26:51.990 align:start position:0% less clicks is more and people have the time<00:26:49.960> to<00:26:50.240> really<00:26:50.600> enjoy<00:26:51.080> the<00:26:51.279> benefits<00:26:51.799> of 00:26:51.990 --> 00:26:52.000 align:start position:0% time to really enjoy the benefits of 00:26:52.000 --> 00:26:53.110 align:start position:0% time to really enjoy the benefits of these 00:26:53.110 --> 00:26:53.120 align:start position:0% these 00:26:53.120 --> 00:26:59.669 align:start position:0% these applications<00:26:54.120> thank<00:26:54.320> you 00:26:59.669 --> 00:26:59.679 align:start position:0% 00:26:59.679 --> 00:27:02.470 align:start position:0% thank<00:26:59.840> you<00:26:59.960> so<00:27:00.200> much<00:27:00.520> Pedro<00:27:01.200> we<00:27:01.559> already<00:27:02.279> have 00:27:02.470 --> 00:27:02.480 align:start position:0% thank you so much Pedro we already have 00:27:02.480 --> 00:27:04.269 align:start position:0% thank you so much Pedro we already have a<00:27:02.640> couple<00:27:02.919> of<00:27:03.159> questions<00:27:03.600> here<00:27:03.840> not<00:27:03.960> sure<00:27:04.159> if 00:27:04.269 --> 00:27:04.279 align:start position:0% a couple of questions here not sure if 00:27:04.279 --> 00:27:06.909 align:start position:0% a couple of questions here not sure if we'll<00:27:04.520> be<00:27:04.679> able<00:27:04.919> to<00:27:05.279> cover<00:27:05.880> all<00:27:06.080> of<00:27:06.320> them<00:27:06.760> but 00:27:06.909 --> 00:27:06.919 align:start position:0% we'll be able to cover all of them but 00:27:06.919 --> 00:27:09.430 align:start position:0% we'll be able to cover all of them but let's<00:27:07.360> going<00:27:07.520> to<00:27:07.799> start<00:27:08.320> with<00:27:08.520> the<00:27:08.679> most<00:27:08.960> voted 00:27:09.430 --> 00:27:09.440 align:start position:0% let's going to start with the most voted 00:27:09.440 --> 00:27:12.470 align:start position:0% let's going to start with the most voted here<00:27:09.960> Pedro<00:27:10.679> is<00:27:10.799> it<00:27:10.960> already<00:27:11.480> possible<00:27:11.919> to<00:27:12.120> use 00:27:12.470 --> 00:27:12.480 align:start position:0% here Pedro is it already possible to use 00:27:12.480 --> 00:27:15.549 align:start position:0% here Pedro is it already possible to use the<00:27:12.720> same<00:27:13.080> account<00:27:13.520> abstraction<00:27:14.520> account<00:27:15.279> oh 00:27:15.549 --> 00:27:15.559 align:start position:0% the same account abstraction account oh 00:27:15.559 --> 00:27:19.070 align:start position:0% the same account abstraction account oh sorry<00:27:16.559> across<00:27:17.000> all<00:27:17.399> your<00:27:17.559> two<00:27:17.919> if<00:27:18.120> not<00:27:18.679> when<00:27:18.960> do 00:27:19.070 --> 00:27:19.080 align:start position:0% sorry across all your two if not when do 00:27:19.080 --> 00:27:22.630 align:start position:0% sorry across all your two if not when do you<00:27:19.240> think<00:27:19.440> it<00:27:19.559> will<00:27:19.760> be<00:27:20.120> possible<00:27:21.120> so<00:27:21.640> it<00:27:21.799> is 00:27:22.630 --> 00:27:22.640 align:start position:0% you think it will be possible so it is 00:27:22.640 --> 00:27:24.789 align:start position:0% you think it will be possible so it is possible<00:27:23.080> to<00:27:23.240> some<00:27:23.520> extent<00:27:24.080> but<00:27:24.240> as<00:27:24.360> you<00:27:24.520> saw 00:27:24.789 --> 00:27:24.799 align:start position:0% possible to some extent but as you saw 00:27:24.799 --> 00:27:27.510 align:start position:0% possible to some extent but as you saw smart<00:27:25.159> accounts<00:27:25.520> are<00:27:26.039> deployed<00:27:26.720> contracts<00:27:27.360> so 00:27:27.510 --> 00:27:27.520 align:start position:0% smart accounts are deployed contracts so 00:27:27.520 --> 00:27:29.470 align:start position:0% smart accounts are deployed contracts so you<00:27:27.720> actually<00:27:27.960> have<00:27:28.320> to<00:27:28.440> deploy<00:27:28.799> the<00:27:28.960> contract 00:27:29.470 --> 00:27:29.480 align:start position:0% you actually have to deploy the contract 00:27:29.480 --> 00:27:32.190 align:start position:0% you actually have to deploy the contract in<00:27:29.760> every<00:27:30.159> L2<00:27:30.720> that<00:27:30.960> exists<00:27:31.720> so<00:27:31.880> if<00:27:31.960> you<00:27:32.080> have 00:27:32.190 --> 00:27:32.200 align:start position:0% in every L2 that exists so if you have 00:27:32.200 --> 00:27:34.230 align:start position:0% in every L2 that exists so if you have to<00:27:32.360> deploy<00:27:32.679> the<00:27:32.760> smart<00:27:33.039> contract<00:27:33.360> in<00:27:33.520> every<00:27:33.720> L2 00:27:34.230 --> 00:27:34.240 align:start position:0% to deploy the smart contract in every L2 00:27:34.240 --> 00:27:36.190 align:start position:0% to deploy the smart contract in every L2 that<00:27:34.440> exists<00:27:35.000> that<00:27:35.120> means<00:27:35.440> that<00:27:35.559> you<00:27:35.760> have<00:27:35.880> to 00:27:36.190 --> 00:27:36.200 align:start position:0% that exists that means that you have to 00:27:36.200 --> 00:27:39.029 align:start position:0% that exists that means that you have to manage<00:27:36.960> multiple<00:27:37.559> accounts<00:27:38.320> and<00:27:38.440> it<00:27:38.559> gets 00:27:39.029 --> 00:27:39.039 align:start position:0% manage multiple accounts and it gets 00:27:39.039 --> 00:27:41.110 align:start position:0% manage multiple accounts and it gets really<00:27:39.440> really<00:27:39.720> inconvenient<00:27:40.640> people<00:27:40.880> are 00:27:41.110 --> 00:27:41.120 align:start position:0% really really inconvenient people are 00:27:41.120 --> 00:27:43.430 align:start position:0% really really inconvenient people are working<00:27:41.519> on<00:27:41.799> how<00:27:41.960> you<00:27:42.120> can<00:27:42.399> manage<00:27:43.039> account 00:27:43.430 --> 00:27:43.440 align:start position:0% working on how you can manage account 00:27:43.440 --> 00:27:45.509 align:start position:0% working on how you can manage account across<00:27:43.760> multiple<00:27:44.159> chains<00:27:44.840> and<00:27:44.960> I<00:27:45.080> think<00:27:45.240> chain 00:27:45.509 --> 00:27:45.519 align:start position:0% across multiple chains and I think chain 00:27:45.519 --> 00:27:48.070 align:start position:0% across multiple chains and I think chain abstraction<00:27:46.320> is<00:27:46.679> the<00:27:46.880> next<00:27:47.200> level<00:27:47.640> I<00:27:47.720> think<00:27:47.919> of 00:27:48.070 --> 00:27:48.080 align:start position:0% abstraction is the next level I think of 00:27:48.080 --> 00:27:50.149 align:start position:0% abstraction is the next level I think of chain<00:27:48.320> abstraction<00:27:48.840> as<00:27:49.039> almost<00:27:49.760> like 00:27:50.149 --> 00:27:50.159 align:start position:0% chain abstraction as almost like 00:27:50.159 --> 00:27:53.190 align:start position:0% chain abstraction as almost like cross-chain<00:27:50.840> smart<00:27:51.159> accounts<00:27:51.679> So<00:27:52.440> eventually 00:27:53.190 --> 00:27:53.200 align:start position:0% cross-chain smart accounts So eventually 00:27:53.200 --> 00:27:56.630 align:start position:0% cross-chain smart accounts So eventually very 00:27:56.630 --> 00:27:56.640 align:start position:0% 00:27:56.640 --> 00:28:00.310 align:start position:0% soon<00:27:57.640> another<00:27:58.279> question 00:28:00.310 --> 00:28:00.320 align:start position:0% soon another question 00:28:00.320 --> 00:28:02.950 align:start position:0% soon another question here<00:28:01.320> wouldn't<00:28:01.760> giving<00:28:02.039> a<00:28:02.240> session<00:28:02.600> to<00:28:02.799> the 00:28:02.950 --> 00:28:02.960 align:start position:0% here wouldn't giving a session to the 00:28:02.960 --> 00:28:05.909 align:start position:0% here wouldn't giving a session to the DAP<00:28:03.279> makes<00:28:03.600> scammer<00:28:04.159> DB's<00:28:04.679> life<00:28:05.000> so<00:28:05.240> much 00:28:05.909 --> 00:28:05.919 align:start position:0% DAP makes scammer DB's life so much 00:28:05.919 --> 00:28:09.470 align:start position:0% DAP makes scammer DB's life so much easier<00:28:06.960> well<00:28:07.960> obviously<00:28:08.640> that's<00:28:08.760> a<00:28:09.000> topic<00:28:09.240> for 00:28:09.470 --> 00:28:09.480 align:start position:0% easier well obviously that's a topic for 00:28:09.480 --> 00:28:12.950 align:start position:0% easier well obviously that's a topic for discussion<00:28:10.200> like<00:28:10.440> smart<00:28:10.880> sessions<00:28:11.679> is<00:28:12.200> about 00:28:12.950 --> 00:28:12.960 align:start position:0% discussion like smart sessions is about 00:28:12.960 --> 00:28:15.750 align:start position:0% discussion like smart sessions is about 9<00:28:13.360> months<00:28:13.679> old<00:28:14.559> uh<00:28:14.720> we<00:28:14.880> have<00:28:15.080> done<00:28:15.320> some 00:28:15.750 --> 00:28:15.760 align:start position:0% 9 months old uh we have done some 00:28:15.760 --> 00:28:17.950 align:start position:0% 9 months old uh we have done some experimentation<00:28:16.760> how<00:28:17.000> much<00:28:17.399> permission 00:28:17.950 --> 00:28:17.960 align:start position:0% experimentation how much permission 00:28:17.960 --> 00:28:20.110 align:start position:0% experimentation how much permission should<00:28:18.240> you<00:28:18.720> have<00:28:18.919> to<00:28:19.080> give<00:28:19.279> to<00:28:19.440> the<00:28:19.600> app<00:28:19.960> that 00:28:20.110 --> 00:28:20.120 align:start position:0% should you have to give to the app that 00:28:20.120 --> 00:28:22.389 align:start position:0% should you have to give to the app that it's<00:28:20.360> convenient<00:28:20.919> for<00:28:21.200> you<00:28:21.760> but<00:28:21.919> it's<00:28:22.159> still 00:28:22.389 --> 00:28:22.399 align:start position:0% it's convenient for you but it's still 00:28:22.399 --> 00:28:24.549 align:start position:0% it's convenient for you but it's still makes<00:28:22.600> you<00:28:22.880> secure<00:28:23.760> like<00:28:24.000> The<00:28:24.159> Current 00:28:24.549 --> 00:28:24.559 align:start position:0% makes you secure like The Current 00:28:24.559 --> 00:28:27.070 align:start position:0% makes you secure like The Current Designs<00:28:25.440> currently<00:28:25.880> focus<00:28:26.240> on<00:28:26.480> spending 00:28:27.070 --> 00:28:27.080 align:start position:0% Designs currently focus on spending 00:28:27.080 --> 00:28:28.990 align:start position:0% Designs currently focus on spending policies<00:28:27.840> and<00:28:27.960> that<00:28:28.120> that<00:28:28.240> has<00:28:28.360> been<00:28:28.559> most<00:28:28.840> of 00:28:28.990 --> 00:28:29.000 align:start position:0% policies and that that has been most of 00:28:29.000 --> 00:28:32.070 align:start position:0% policies and that that has been most of the<00:28:29.120> conversation<00:28:30.039> but<00:28:30.760> in<00:28:30.960> my<00:28:31.240> opinion<00:28:31.960> it 00:28:32.070 --> 00:28:32.080 align:start position:0% the conversation but in my opinion it 00:28:32.080 --> 00:28:35.149 align:start position:0% the conversation but in my opinion it should<00:28:32.399> not<00:28:32.760> make<00:28:32.919> it<00:28:33.120> easier<00:28:33.960> uh<00:28:34.120> because<00:28:34.960> you 00:28:35.149 --> 00:28:35.159 align:start position:0% should not make it easier uh because you 00:28:35.159 --> 00:28:36.870 align:start position:0% should not make it easier uh because you can<00:28:35.440> actually<00:28:35.679> have<00:28:35.880> more<00:28:36.200> control<00:28:36.640> because 00:28:36.870 --> 00:28:36.880 align:start position:0% can actually have more control because 00:28:36.880 --> 00:28:40.310 align:start position:0% can actually have more control because of<00:28:37.039> smart<00:28:37.279> accounts<00:28:37.559> give<00:28:37.720> you 00:28:40.310 --> 00:28:40.320 align:start position:0% 00:28:40.320 --> 00:28:42.870 align:start position:0% programmability<00:28:41.320> is<00:28:41.600> smart<00:28:42.000> sessions<00:28:42.679> a 00:28:42.870 --> 00:28:42.880 align:start position:0% programmability is smart sessions a 00:28:42.880 --> 00:28:46.990 align:start position:0% programmability is smart sessions a smart<00:28:43.720> account<00:28:44.720> so<00:28:45.640> smart<00:28:45.960> if<00:28:46.120> smart<00:28:46.399> ches<00:28:46.799> our 00:28:46.990 --> 00:28:47.000 align:start position:0% smart account so smart if smart ches our 00:28:47.000 --> 00:28:49.149 align:start position:0% smart account so smart if smart ches our smart<00:28:47.320> contract<00:28:48.039> is<00:28:48.240> another<00:28:48.640> topic<00:28:48.919> of 00:28:49.149 --> 00:28:49.159 align:start position:0% smart contract is another topic of 00:28:49.159 --> 00:28:52.430 align:start position:0% smart contract is another topic of discussion<00:28:49.760> if<00:28:49.880> you<00:28:50.000> go<00:28:50.200> to<00:28:50.440> the<00:28:50.640> spec<00:28:51.000> of<00:28:51.440> 7715 00:28:52.430 --> 00:28:52.440 align:start position:0% discussion if you go to the spec of 7715 00:28:52.440 --> 00:28:54.750 align:start position:0% discussion if you go to the spec of 7715 there's<00:28:52.720> two<00:28:53.120> versions<00:28:54.120> uh<00:28:54.240> there's<00:28:54.519> one 00:28:54.750 --> 00:28:54.760 align:start position:0% there's two versions uh there's one 00:28:54.760 --> 00:28:57.269 align:start position:0% there's two versions uh there's one that's<00:28:55.000> called<00:28:55.360> session<00:28:55.840> key<00:28:56.440> smart<00:28:56.799> sessions 00:28:57.269 --> 00:28:57.279 align:start position:0% that's called session key smart sessions 00:28:57.279 --> 00:28:58.590 align:start position:0% that's called session key smart sessions and<00:28:57.399> there's<00:28:57.600> one<00:28:57.760> that's<00:28:57.880> called<00:28:58.159> called 00:28:58.590 --> 00:28:58.600 align:start position:0% and there's one that's called called 00:28:58.600 --> 00:29:01.430 align:start position:0% and there's one that's called called session<00:28:59.200> account<00:28:59.640> smart<00:28:59.960> session<00:29:00.399> so<00:29:00.640> there's 00:29:01.430 --> 00:29:01.440 align:start position:0% session account smart session so there's 00:29:01.440 --> 00:29:03.470 align:start position:0% session account smart session so there's a<00:29:01.600> little<00:29:01.840> bit<00:29:02.080> of<00:29:02.480> a<00:29:02.679> difference<00:29:03.039> of<00:29:03.279> how 00:29:03.470 --> 00:29:03.480 align:start position:0% a little bit of a difference of how 00:29:03.480 --> 00:29:06.590 align:start position:0% a little bit of a difference of how people<00:29:03.880> think<00:29:04.159> about<00:29:04.360> it<00:29:05.200> um<00:29:05.799> but<00:29:06.000> yes<00:29:06.320> I<00:29:06.440> guess 00:29:06.590 --> 00:29:06.600 align:start position:0% people think about it um but yes I guess 00:29:06.600 --> 00:29:09.710 align:start position:0% people think about it um but yes I guess you<00:29:06.760> could<00:29:06.919> say<00:29:07.440> the<00:29:07.640> easy<00:29:07.960> answer<00:29:08.240> is 00:29:09.710 --> 00:29:09.720 align:start position:0% you could say the easy answer is 00:29:09.720 --> 00:29:12.269 align:start position:0% you could say the easy answer is yes<00:29:10.720> and<00:29:10.880> then<00:29:11.080> one<00:29:11.399> last<00:29:11.679> question<00:29:12.000> do<00:29:12.159> you 00:29:12.269 --> 00:29:12.279 align:start position:0% yes and then one last question do you 00:29:12.279 --> 00:29:15.269 align:start position:0% yes and then one last question do you think<00:29:12.679> of<00:29:13.000> sessions<00:29:13.760> as<00:29:14.080> longlasting<00:29:14.519> or 00:29:15.269 --> 00:29:15.279 align:start position:0% think of sessions as longlasting or 00:29:15.279 --> 00:29:16.830 align:start position:0% think of sessions as longlasting or short 00:29:16.830 --> 00:29:16.840 align:start position:0% short 00:29:16.840 --> 00:29:18.389 align:start position:0% short lived 00:29:18.389 --> 00:29:18.399 align:start position:0% lived 00:29:18.399 --> 00:29:22.070 align:start position:0% lived um<00:29:19.399> look<00:29:19.799> when<00:29:19.919> you<00:29:20.080> think<00:29:20.320> about<00:29:20.760> login<00:29:21.760> uh 00:29:22.070 --> 00:29:22.080 align:start position:0% um look when you think about login uh 00:29:22.080 --> 00:29:25.029 align:start position:0% um look when you think about login uh login<00:29:22.519> actually<00:29:22.960> is<00:29:23.679> on<00:29:23.960> average<00:29:24.519> people<00:29:24.799> log 00:29:25.029 --> 00:29:25.039 align:start position:0% login actually is on average people log 00:29:25.039 --> 00:29:27.430 align:start position:0% login actually is on average people log in<00:29:25.200> into<00:29:25.440> a<00:29:25.600> website<00:29:26.159> and<00:29:26.360> those<00:29:26.640> sessions<00:29:27.120> are 00:29:27.430 --> 00:29:27.440 align:start position:0% in into a website and those sessions are 00:29:27.440 --> 00:29:28.750 align:start position:0% in into a website and those sessions are 7<00:29:27.799> days 00:29:28.750 --> 00:29:28.760 align:start position:0% 7 days 00:29:28.760 --> 00:29:31.230 align:start position:0% 7 days but<00:29:29.039> what<00:29:29.240> web2<00:29:29.799> has<00:29:30.080> successfully<00:29:30.679> done<00:29:31.080> is 00:29:31.230 --> 00:29:31.240 align:start position:0% but what web2 has successfully done is 00:29:31.240 --> 00:29:33.710 align:start position:0% but what web2 has successfully done is that<00:29:31.399> they<00:29:31.559> can<00:29:31.880> renew<00:29:32.440> those<00:29:32.679> sessions<00:29:33.480> so 00:29:33.710 --> 00:29:33.720 align:start position:0% that they can renew those sessions so 00:29:33.720 --> 00:29:35.830 align:start position:0% that they can renew those sessions so essentially<00:29:34.240> at<00:29:34.519> every<00:29:34.840> seven<00:29:35.240> days<00:29:35.519> you<00:29:35.679> have 00:29:35.830 --> 00:29:35.840 align:start position:0% essentially at every seven days you have 00:29:35.840 --> 00:29:38.430 align:start position:0% essentially at every seven days you have the<00:29:36.120> ability<00:29:36.559> to<00:29:36.760> renew<00:29:37.159> the<00:29:37.279> smart<00:29:37.600> session 00:29:38.430 --> 00:29:38.440 align:start position:0% the ability to renew the smart session 00:29:38.440 --> 00:29:40.590 align:start position:0% the ability to renew the smart session so<00:29:38.760> we<00:29:38.880> don't<00:29:39.200> have<00:29:39.440> this<00:29:39.760> capability<00:29:40.360> of 00:29:40.590 --> 00:29:40.600 align:start position:0% so we don't have this capability of 00:29:40.600 --> 00:29:42.389 align:start position:0% so we don't have this capability of automatically<00:29:41.240> renewing<00:29:41.760> smart<00:29:42.039> sessions 00:29:42.389 --> 00:29:42.399 align:start position:0% automatically renewing smart sessions 00:29:42.399 --> 00:29:45.190 align:start position:0% automatically renewing smart sessions today<00:29:43.320> but<00:29:43.480> that's<00:29:43.640> how<00:29:43.799> we<00:29:44.080> envision<00:29:44.640> us<00:29:45.080> kind 00:29:45.190 --> 00:29:45.200 align:start position:0% today but that's how we envision us kind 00:29:45.200 --> 00:29:48.110 align:start position:0% today but that's how we envision us kind of<00:29:45.399> inheriting<00:29:46.320> that<00:29:46.600> design<00:29:47.000> from<00:29:47.240> web<00:29:47.480> 2 00:29:48.110 --> 00:29:48.120 align:start position:0% of inheriting that design from web 2 00:29:48.120 --> 00:29:49.870 align:start position:0% of inheriting that design from web 2 where<00:29:48.279> smart<00:29:48.600> sessions<00:29:48.960> would<00:29:49.120> be<00:29:49.360> one<00:29:49.600> week 00:29:49.870 --> 00:29:49.880 align:start position:0% where smart sessions would be one week 00:29:49.880 --> 00:29:51.549 align:start position:0% where smart sessions would be one week old<00:29:50.320> and<00:29:50.480> then<00:29:50.600> you<00:29:50.679> would<00:29:50.880> just<00:29:51.080> renew<00:29:51.440> it 00:29:51.549 --> 00:29:51.559 align:start position:0% old and then you would just renew it 00:29:51.559 --> 00:29:53.230 align:start position:0% old and then you would just renew it automatically<00:29:52.200> without<00:29:52.399> you<00:29:52.600> having<00:29:52.799> to<00:29:53.000> log 00:29:53.230 --> 00:29:53.240 align:start position:0% automatically without you having to log 00:29:53.240 --> 00:29:55.110 align:start position:0% automatically without you having to log in<00:29:53.480> every 00:29:55.110 --> 00:29:55.120 align:start position:0% in every 00:29:55.120 --> 00:29:57.870 align:start position:0% in every time<00:29:56.120> ped<00:29:56.519> thank<00:29:56.679> you<00:29:56.880> so<00:29:57.120> much<00:29:57.519> that<00:29:57.640> was<00:29:57.760> a 00:29:57.870 --> 00:29:57.880 align:start position:0% time ped thank you so much that was a 00:29:57.880 --> 00:29:59.549 align:start position:0% time ped thank you so much that was a great<00:29:58.080> great<00:29:58.399> presentation<00:29:59.120> thank<00:29:59.279> you<00:29:59.399> so 00:29:59.549 --> 00:29:59.559 align:start position:0% great great presentation thank you so 00:29:59.559 --> 00:30:04.399 align:start position:0% great great presentation thank you so much<00:29:59.840> everyone<00:30:00.720> adding<00:30:01.200> so<00:30:01.679> many<00:30:02.120> question