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:18.470 align:start position:0% [Music] 00:00:18.470 --> 00:00:18.480 align:start position:0% [Music] 00:00:18.480 --> 00:00:21.630 align:start position:0% [Music] hey<00:00:18.680> everybody<00:00:19.600> um<00:00:20.080> yeah<00:00:20.320> my<00:00:20.439> name<00:00:20.560> is<00:00:20.760> Greg<00:00:21.519> uh 00:00:21.630 --> 00:00:21.640 align:start position:0% hey everybody um yeah my name is Greg uh 00:00:21.640 --> 00:00:24.230 align:start position:0% hey everybody um yeah my name is Greg uh or<00:00:21.800> Greg<00:00:22.039> the<00:00:22.119> Greek<00:00:22.400> if<00:00:22.439> you<00:00:22.519> know<00:00:22.680> me<00:00:23.240> online 00:00:24.230 --> 00:00:24.240 align:start position:0% or Greg the Greek if you know me online 00:00:24.240 --> 00:00:26.470 align:start position:0% or Greg the Greek if you know me online uh<00:00:24.640> I'm<00:00:24.880> one<00:00:24.960> of<00:00:25.080> the<00:00:25.199> co-founders<00:00:26.199> chains 00:00:26.470 --> 00:00:26.480 align:start position:0% uh I'm one of the co-founders chains 00:00:26.480 --> 00:00:29.070 align:start position:0% uh I'm one of the co-founders chains saafe<00:00:26.720> and<00:00:26.880> as<00:00:27.000> well<00:00:27.160> as<00:00:27.480> Sprinter<00:00:28.199> we<00:00:28.720> recent 00:00:29.070 --> 00:00:29.080 align:start position:0% saafe and as well as Sprinter we recent 00:00:29.080 --> 00:00:31.630 align:start position:0% saafe and as well as Sprinter we recent Rebrand<00:00:29.480> a<00:00:29.519> few<00:00:29.640> days<00:00:29.759> ago<00:00:30.160> from<00:00:30.599> uh 00:00:31.630 --> 00:00:31.640 align:start position:0% Rebrand a few days ago from uh 00:00:31.640 --> 00:00:33.990 align:start position:0% Rebrand a few days ago from uh Sigma<00:00:32.640> um<00:00:33.239> today<00:00:33.440> I'm<00:00:33.520> going<00:00:33.640> to<00:00:33.719> be<00:00:33.800> talking 00:00:33.990 --> 00:00:34.000 align:start position:0% Sigma um today I'm going to be talking 00:00:34.000 --> 00:00:35.869 align:start position:0% Sigma um today I'm going to be talking about<00:00:34.200> end<00:00:34.399> game<00:00:34.600> the<00:00:34.680> endgame<00:00:35.079> wallet<00:00:35.760> uh 00:00:35.869 --> 00:00:35.879 align:start position:0% about end game the endgame wallet uh 00:00:35.879 --> 00:00:38.069 align:start position:0% about end game the endgame wallet uh this<00:00:36.000> is<00:00:36.160> coming<00:00:36.559> from<00:00:36.920> about<00:00:37.120> a<00:00:37.399> year<00:00:37.800> over 00:00:38.069 --> 00:00:38.079 align:start position:0% this is coming from about a year over 00:00:38.079 --> 00:00:39.549 align:start position:0% this is coming from about a year over well<00:00:38.239> over<00:00:38.520> one<00:00:38.680> to<00:00:38.800> two<00:00:38.960> years<00:00:39.200> wor<00:00:39.399> of 00:00:39.549 --> 00:00:39.559 align:start position:0% well over one to two years wor of 00:00:39.559 --> 00:00:41.229 align:start position:0% well over one to two years wor of Standards<00:00:40.000> work<00:00:40.559> that's<00:00:40.719> something<00:00:40.960> I<00:00:41.039> do<00:00:41.160> a 00:00:41.229 --> 00:00:41.239 align:start position:0% Standards work that's something I do a 00:00:41.239 --> 00:00:43.350 align:start position:0% Standards work that's something I do a lot<00:00:41.360> in<00:00:41.440> my<00:00:41.559> spare<00:00:41.879> time<00:00:42.879> um<00:00:43.079> and<00:00:43.200> it's 00:00:43.350 --> 00:00:43.360 align:start position:0% lot in my spare time um and it's 00:00:43.360 --> 00:00:44.510 align:start position:0% lot in my spare time um and it's something<00:00:43.640> that<00:00:43.760> we<00:00:43.879> focus<00:00:44.160> a<00:00:44.239> lot<00:00:44.360> at 00:00:44.510 --> 00:00:44.520 align:start position:0% something that we focus a lot at 00:00:44.520 --> 00:00:46.630 align:start position:0% something that we focus a lot at Sprinter<00:00:45.079> is<00:00:45.360> driving<00:00:45.960> how<00:00:46.039> we<00:00:46.120> can<00:00:46.239> look<00:00:46.360> at 00:00:46.630 --> 00:00:46.640 align:start position:0% Sprinter is driving how we can look at 00:00:46.640 --> 00:00:49.110 align:start position:0% Sprinter is driving how we can look at like<00:00:47.000> multichain<00:00:48.000> um<00:00:48.320> and<00:00:48.440> getting<00:00:48.680> the<00:00:48.760> ux 00:00:49.110 --> 00:00:49.120 align:start position:0% like multichain um and getting the ux 00:00:49.120 --> 00:00:51.670 align:start position:0% like multichain um and getting the ux there<00:00:49.399> right<00:00:50.039> we<00:00:50.199> don't<00:00:50.559> have<00:00:50.719> a<00:00:50.920> wallet<00:00:51.480> we 00:00:51.670 --> 00:00:51.680 align:start position:0% there right we don't have a wallet we 00:00:51.680 --> 00:00:54.670 align:start position:0% there right we don't have a wallet we don't<00:00:52.199> really<00:00:52.440> do<00:00:52.680> wallet<00:00:53.000> infra<00:00:53.800> we<00:00:54.280> work<00:00:54.480> in 00:00:54.670 --> 00:00:54.680 align:start position:0% don't really do wallet infra we work in 00:00:54.680 --> 00:00:56.349 align:start position:0% don't really do wallet infra we work in solving<00:00:55.399> as<00:00:55.559> well<00:00:55.719> as<00:00:55.879> we've<00:00:56.039> been<00:00:56.160> doing 00:00:56.349 --> 00:00:56.359 align:start position:0% solving as well as we've been doing 00:00:56.359 --> 00:00:58.549 align:start position:0% solving as well as we've been doing multi-<00:00:56.840> Building<00:00:57.120> Bridges<00:00:57.600> since<00:00:57.800> 2018<00:00:58.399> and 00:00:58.549 --> 00:00:58.559 align:start position:0% multi- Building Bridges since 2018 and 00:00:58.559 --> 00:00:59.590 align:start position:0% multi- Building Bridges since 2018 and building<00:00:58.879> Proto<00:00:59.160> we're<00:00:59.280> protocol 00:00:59.590 --> 00:00:59.600 align:start position:0% building Proto we're protocol 00:00:59.600 --> 00:01:01.750 align:start position:0% building Proto we're protocol engineering<00:01:00.280> a<00:01:00.440> chains<00:01:00.719> safe<00:01:01.079> and<00:01:01.280> I<00:01:01.359> was<00:01:01.480> one 00:01:01.750 --> 00:01:01.760 align:start position:0% engineering a chains safe and I was one 00:01:01.760 --> 00:01:03.149 align:start position:0% engineering a chains safe and I was one myself<00:01:02.079> for<00:01:02.280> eth 00:01:03.149 --> 00:01:03.159 align:start position:0% myself for eth 00:01:03.159 --> 00:01:06.149 align:start position:0% myself for eth 2.0<00:01:04.159> um<00:01:04.720> so<00:01:05.199> I'm<00:01:05.320> trying<00:01:05.479> to<00:01:05.600> remove<00:01:05.880> as<00:01:05.960> much 00:01:06.149 --> 00:01:06.159 align:start position:0% 2.0 um so I'm trying to remove as much 00:01:06.159 --> 00:01:08.149 align:start position:0% 2.0 um so I'm trying to remove as much bias<00:01:06.439> as<00:01:06.640> possible<00:01:07.320> I'm<00:01:07.479> objectively<00:01:07.960> looking 00:01:08.149 --> 00:01:08.159 align:start position:0% bias as possible I'm objectively looking 00:01:08.159 --> 00:01:09.870 align:start position:0% bias as possible I'm objectively looking at<00:01:08.240> the<00:01:08.360> standards<00:01:08.680> when<00:01:08.759> we<00:01:08.920> go<00:01:09.040> through 00:01:09.870 --> 00:01:09.880 align:start position:0% at the standards when we go through 00:01:09.880 --> 00:01:13.590 align:start position:0% at the standards when we go through here<00:01:10.880> so<00:01:11.880> where<00:01:12.640> let's<00:01:12.799> do<00:01:12.920> a<00:01:13.080> little<00:01:13.439> I<00:01:13.479> want 00:01:13.590 --> 00:01:13.600 align:start position:0% here so where let's do a little I want 00:01:13.600 --> 00:01:14.990 align:start position:0% here so where let's do a little I want to<00:01:13.680> do<00:01:13.759> a<00:01:13.840> little<00:01:14.000> Memory<00:01:14.280> Lane<00:01:14.600> I<00:01:14.680> want<00:01:14.759> to 00:01:14.990 --> 00:01:15.000 align:start position:0% to do a little Memory Lane I want to 00:01:15.000 --> 00:01:17.550 align:start position:0% to do a little Memory Lane I want to like<00:01:15.200> you<00:01:15.360> know<00:01:15.960> bring<00:01:16.119> it<00:01:16.240> a<00:01:16.360> little<00:01:16.600> pain<00:01:17.439> you 00:01:17.550 --> 00:01:17.560 align:start position:0% like you know bring it a little pain you 00:01:17.560 --> 00:01:19.230 align:start position:0% like you know bring it a little pain you know<00:01:17.880> when<00:01:18.080> was<00:01:18.439> I<00:01:18.520> don't<00:01:18.640> know<00:01:18.759> if<00:01:18.920> many<00:01:19.119> of 00:01:19.230 --> 00:01:19.240 align:start position:0% know when was I don't know if many of 00:01:19.240 --> 00:01:22.830 align:start position:0% know when was I don't know if many of you<00:01:19.439> remember<00:01:19.880> the<00:01:20.000> world<00:01:20.400> before<00:01:20.840> EIP<00:01:21.840> 1193 00:01:22.830 --> 00:01:22.840 align:start position:0% you remember the world before EIP 1193 00:01:22.840 --> 00:01:25.149 align:start position:0% you remember the world before EIP 1193 but<00:01:23.040> this<00:01:23.159> was<00:01:23.439> when<00:01:24.159> you<00:01:24.400> download<00:01:24.759> a<00:01:24.880> new 00:01:25.149 --> 00:01:25.159 align:start position:0% but this was when you download a new 00:01:25.159 --> 00:01:27.350 align:start position:0% but this was when you download a new fancy<00:01:25.759> wallet<00:01:26.320> and<00:01:26.439> then<00:01:26.560> all<00:01:26.640> of<00:01:26.720> a<00:01:26.799> sudden<00:01:27.040> no 00:01:27.350 --> 00:01:27.360 align:start position:0% fancy wallet and then all of a sudden no 00:01:27.360 --> 00:01:28.749 align:start position:0% fancy wallet and then all of a sudden no app<00:01:27.600> would<00:01:27.720> ever<00:01:27.920> be<00:01:28.040> able<00:01:28.200> to<00:01:28.320> work<00:01:28.520> with<00:01:28.640> it 00:01:28.749 --> 00:01:28.759 align:start position:0% app would ever be able to work with it 00:01:28.759 --> 00:01:30.069 align:start position:0% app would ever be able to work with it or<00:01:28.920> communicate<00:01:29.360> with<00:01:29.479> it<00:01:29.680> if<00:01:29.920> if<00:01:29.920> you're<00:01:30.040> in 00:01:30.069 --> 00:01:30.079 align:start position:0% or communicate with it if if you're in 00:01:30.079 --> 00:01:32.510 align:start position:0% or communicate with it if if you're in an<00:01:30.280> app<00:01:30.520> developer<00:01:31.119> you<00:01:31.200> had<00:01:31.360> to<00:01:31.600> manually 00:01:32.510 --> 00:01:32.520 align:start position:0% an app developer you had to manually 00:01:32.520 --> 00:01:35.389 align:start position:0% an app developer you had to manually code<00:01:32.840> in<00:01:33.560> communicate<00:01:34.079> with<00:01:34.240> like<00:01:34.399> metamask 00:01:35.389 --> 00:01:35.399 align:start position:0% code in communicate with like metamask 00:01:35.399 --> 00:01:37.510 align:start position:0% code in communicate with like metamask or<00:01:35.600> communicate<00:01:36.040> with<00:01:36.200> fancy<00:01:36.479> new<00:01:36.680> wallet 00:01:37.510 --> 00:01:37.520 align:start position:0% or communicate with fancy new wallet 00:01:37.520 --> 00:01:39.069 align:start position:0% or communicate with fancy new wallet there<00:01:37.640> was<00:01:37.759> a<00:01:37.960> time<00:01:38.119> when<00:01:38.240> you<00:01:38.360> couldn't<00:01:38.680> even 00:01:39.069 --> 00:01:39.079 align:start position:0% there was a time when you couldn't even 00:01:39.079 --> 00:01:41.950 align:start position:0% there was a time when you couldn't even have<00:01:39.640> multiple<00:01:40.119> browser<00:01:40.799> extensions<00:01:41.799> and 00:01:41.950 --> 00:01:41.960 align:start position:0% have multiple browser extensions and 00:01:41.960 --> 00:01:44.749 align:start position:0% have multiple browser extensions and that<00:01:42.040> was<00:01:42.200> pre<00:01:42.479> multi-<00:01:42.799> injector<00:01:43.759> provider 00:01:44.749 --> 00:01:44.759 align:start position:0% that was pre multi- injector provider 00:01:44.759 --> 00:01:47.429 align:start position:0% that was pre multi- injector provider there<00:01:44.920> was<00:01:45.640> also<00:01:46.640> I<00:01:46.680> mean<00:01:46.880> this<00:01:47.000> is<00:01:47.119> still<00:01:47.280> a 00:01:47.429 --> 00:01:47.439 align:start position:0% there was also I mean this is still a 00:01:47.439 --> 00:01:48.870 align:start position:0% there was also I mean this is still a problem<00:01:47.799> let's<00:01:47.960> be<00:01:48.079> honest<00:01:48.479> we're<00:01:48.640> still 00:01:48.870 --> 00:01:48.880 align:start position:0% problem let's be honest we're still 00:01:48.880 --> 00:01:50.310 align:start position:0% problem let's be honest we're still getting<00:01:49.200> we're<00:01:49.320> getting<00:01:49.520> close<00:01:49.880> aggregate 00:01:50.310 --> 00:01:50.320 align:start position:0% getting we're getting close aggregate 00:01:50.320 --> 00:01:52.310 align:start position:0% getting we're getting close aggregate balances<00:01:50.799> that<00:01:50.920> look<00:01:51.119> nicer<00:01:51.399> so<00:01:51.560> your<00:01:51.680> usdc<00:01:52.200> is 00:01:52.310 --> 00:01:52.320 align:start position:0% balances that look nicer so your usdc is 00:01:52.320 --> 00:01:55.350 align:start position:0% balances that look nicer so your usdc is better<00:01:53.119> or<00:01:53.320> how<00:01:53.439> about<00:01:53.640> Network<00:01:54.119> switching<00:01:55.119> or 00:01:55.350 --> 00:01:55.360 align:start position:0% better or how about Network switching or 00:01:55.360 --> 00:01:57.950 align:start position:0% better or how about Network switching or even<00:01:56.240> you<00:01:56.360> know<00:01:56.520> you<00:01:56.640> go<00:01:56.719> to<00:01:56.840> a<00:01:57.000> Dap<00:01:57.520> immediate 00:01:57.950 --> 00:01:57.960 align:start position:0% even you know you go to a Dap immediate 00:01:57.960 --> 00:02:01.149 align:start position:0% even you know you go to a Dap immediate wallet<00:01:58.320> pop<00:01:58.680> up<00:01:59.680> we<00:01:59.920> we've<00:02:00.079> been<00:02:00.640> iterating 00:02:01.149 --> 00:02:01.159 align:start position:0% wallet pop up we we've been iterating 00:02:01.159 --> 00:02:04.029 align:start position:0% wallet pop up we we've been iterating and<00:02:01.360> fixing<00:02:02.119> a<00:02:02.240> lot<00:02:02.399> of<00:02:02.520> the<00:02:02.640> ux<00:02:02.960> challenges<00:02:03.399> we 00:02:04.029 --> 00:02:04.039 align:start position:0% and fixing a lot of the ux challenges we 00:02:04.039 --> 00:02:06.270 align:start position:0% and fixing a lot of the ux challenges we see<00:02:05.039> and<00:02:05.159> we<00:02:05.320> see<00:02:05.560> that<00:02:05.799> the<00:02:05.880> improvements 00:02:06.270 --> 00:02:06.280 align:start position:0% see and we see that the improvements 00:02:06.280 --> 00:02:07.310 align:start position:0% see and we see that the improvements that<00:02:06.360> have<00:02:06.479> been<00:02:06.600> happening<00:02:06.880> over<00:02:07.039> the<00:02:07.159> last 00:02:07.310 --> 00:02:07.320 align:start position:0% that have been happening over the last 00:02:07.320 --> 00:02:09.869 align:start position:0% that have been happening over the last couple<00:02:07.560> years<00:02:08.360> these<00:02:08.599> iterations<00:02:09.280> have<00:02:09.520> all 00:02:09.869 --> 00:02:09.879 align:start position:0% couple years these iterations have all 00:02:09.879 --> 00:02:11.190 align:start position:0% couple years these iterations have all come 00:02:11.190 --> 00:02:11.200 align:start position:0% come 00:02:11.200 --> 00:02:15.670 align:start position:0% come from<00:02:12.200> erc's<00:02:13.120> eips<00:02:14.040> and<00:02:14.319> capes<00:02:15.319> and<00:02:15.440> that's<00:02:15.560> why 00:02:15.670 --> 00:02:15.680 align:start position:0% from erc's eips and capes and that's why 00:02:15.680 --> 00:02:16.790 align:start position:0% from erc's eips and capes and that's why they're<00:02:15.879> really<00:02:16.000> important<00:02:16.280> that<00:02:16.360> we<00:02:16.480> start 00:02:16.790 --> 00:02:16.800 align:start position:0% they're really important that we start 00:02:16.800 --> 00:02:18.190 align:start position:0% they're really important that we start adopting<00:02:17.200> them<00:02:17.400> but<00:02:17.519> frankly<00:02:17.840> where<00:02:17.959> are<00:02:18.080> we 00:02:18.190 --> 00:02:18.200 align:start position:0% adopting them but frankly where are we 00:02:18.200 --> 00:02:20.110 align:start position:0% adopting them but frankly where are we going<00:02:18.480> right<00:02:18.599> now<00:02:18.760> we're<00:02:18.959> actually<00:02:19.319> like 00:02:20.110 --> 00:02:20.120 align:start position:0% going right now we're actually like 00:02:20.120 --> 00:02:21.430 align:start position:0% going right now we're actually like right<00:02:20.280> now<00:02:20.519> the<00:02:20.599> chain<00:02:20.800> of<00:02:20.920> obstruction<00:02:21.200> space 00:02:21.430 --> 00:02:21.440 align:start position:0% right now the chain of obstruction space 00:02:21.440 --> 00:02:25.150 align:start position:0% right now the chain of obstruction space has<00:02:21.599> kind<00:02:21.680> of<00:02:22.400> us 00:02:25.150 --> 00:02:25.160 align:start position:0% has kind of us 00:02:25.160 --> 00:02:27.630 align:start position:0% has kind of us um<00:02:26.160> we<00:02:26.319> are<00:02:26.519> right<00:02:26.640> now<00:02:26.760> selling<00:02:27.200> application 00:02:27.630 --> 00:02:27.640 align:start position:0% um we are right now selling application 00:02:27.640 --> 00:02:29.309 align:start position:0% um we are right now selling application developers<00:02:28.160> that<00:02:28.400> we<00:02:28.560> they<00:02:28.680> need<00:02:28.840> to<00:02:28.959> deploy<00:02:29.239> a 00:02:29.309 --> 00:02:29.319 align:start position:0% developers that we they need to deploy a 00:02:29.319 --> 00:02:31.910 align:start position:0% developers that we they need to deploy a smart<00:02:29.519> contract<00:02:30.239> for<00:02:31.040> their<00:02:31.239> app<00:02:31.480> to<00:02:31.599> get<00:02:31.760> the 00:02:31.910 --> 00:02:31.920 align:start position:0% smart contract for their app to get the 00:02:31.920 --> 00:02:34.869 align:start position:0% smart contract for their app to get the best<00:02:32.080> features<00:02:32.440> in<00:02:32.560> the<00:02:32.720> guest<00:02:33.400> users<00:02:34.400> if<00:02:34.599> you 00:02:34.869 --> 00:02:34.879 align:start position:0% best features in the guest users if you 00:02:34.879 --> 00:02:36.750 align:start position:0% best features in the guest users if you hear<00:02:35.200> that<00:02:35.440> statement<00:02:35.920> frankly<00:02:36.319> for<00:02:36.560> my 00:02:36.750 --> 00:02:36.760 align:start position:0% hear that statement frankly for my 00:02:36.760 --> 00:02:38.390 align:start position:0% hear that statement frankly for my opinion<00:02:37.200> you're<00:02:37.480> going<00:02:37.720> down<00:02:37.879> a<00:02:38.040> road<00:02:38.280> where 00:02:38.390 --> 00:02:38.400 align:start position:0% opinion you're going down a road where 00:02:38.400 --> 00:02:40.309 align:start position:0% opinion you're going down a road where you're<00:02:38.480> going<00:02:38.599> to<00:02:38.840> have<00:02:38.959> to<00:02:39.080> do<00:02:39.360> a<00:02:39.599> very<00:02:39.920> ugly 00:02:40.309 --> 00:02:40.319 align:start position:0% you're going to have to do a very ugly 00:02:40.319 --> 00:02:42.750 align:start position:0% you're going to have to do a very ugly migration<00:02:40.879> path<00:02:41.080> with<00:02:41.319> when<00:02:41.760> six<00:02:42.080> to<00:02:42.360> 18 00:02:42.750 --> 00:02:42.760 align:start position:0% migration path with when six to 18 00:02:42.760 --> 00:02:44.750 align:start position:0% migration path with when six to 18 months<00:02:43.319> and<00:02:43.519> it's<00:02:43.680> just<00:02:43.840> the<00:02:44.040> wrong<00:02:44.319> way<00:02:44.480> to<00:02:44.640> be 00:02:44.750 --> 00:02:44.760 align:start position:0% months and it's just the wrong way to be 00:02:44.760 --> 00:02:46.990 align:start position:0% months and it's just the wrong way to be dealing<00:02:45.000> with<00:02:45.120> smart<00:02:45.400> contract<00:02:45.720> wets<00:02:46.560> unless 00:02:46.990 --> 00:02:47.000 align:start position:0% dealing with smart contract wets unless 00:02:47.000 --> 00:02:49.910 align:start position:0% dealing with smart contract wets unless you<00:02:47.480> as<00:02:47.680> the<00:02:47.879> app<00:02:48.200> developer<00:02:49.200> are<00:02:49.360> willing<00:02:49.640> to 00:02:49.910 --> 00:02:49.920 align:start position:0% you as the app developer are willing to 00:02:49.920 --> 00:02:52.070 align:start position:0% you as the app developer are willing to deploy<00:02:50.560> wallet<00:02:50.959> infra<00:02:51.560> and<00:02:51.680> when<00:02:51.800> I<00:02:51.879> say 00:02:52.070 --> 00:02:52.080 align:start position:0% deploy wallet infra and when I say 00:02:52.080 --> 00:02:54.270 align:start position:0% deploy wallet infra and when I say wallet<00:02:52.360> infra<00:02:52.760> I'm<00:02:52.840> saying<00:02:53.200> like<00:02:53.360> a<00:02:53.560> my<00:02:53.879> crypto 00:02:54.270 --> 00:02:54.280 align:start position:0% wallet infra I'm saying like a my crypto 00:02:54.280 --> 00:02:56.630 align:start position:0% wallet infra I'm saying like a my crypto website<00:02:54.680> like<00:02:54.800> a<00:02:55.000> full<00:02:55.400> Rage<00:02:55.840> Quit<00:02:56.200> mechanism 00:02:56.630 --> 00:02:56.640 align:start position:0% website like a full Rage Quit mechanism 00:02:56.640 --> 00:02:58.149 align:start position:0% website like a full Rage Quit mechanism so<00:02:56.800> they<00:02:56.920> can<00:02:57.159> migrate<00:02:57.519> to<00:02:57.720> something 00:02:58.149 --> 00:02:58.159 align:start position:0% so they can migrate to something 00:02:58.159 --> 00:03:00.350 align:start position:0% so they can migrate to something different<00:02:58.480> to<00:02:58.640> someone<00:02:59.080> better 00:03:00.350 --> 00:03:00.360 align:start position:0% different to someone better 00:03:00.360 --> 00:03:01.670 align:start position:0% different to someone better you're<00:03:00.560> just<00:03:00.680> vendor<00:03:01.040> locking<00:03:01.280> them<00:03:01.480> inside 00:03:01.670 --> 00:03:01.680 align:start position:0% you're just vendor locking them inside 00:03:01.680 --> 00:03:03.550 align:start position:0% you're just vendor locking them inside your<00:03:01.800> own<00:03:02.040> system<00:03:02.640> maybe<00:03:02.879> inside<00:03:03.120> the<00:03:03.239> wider 00:03:03.550 --> 00:03:03.560 align:start position:0% your own system maybe inside the wider 00:03:03.560 --> 00:03:06.110 align:start position:0% your own system maybe inside the wider system<00:03:03.799> of<00:03:03.959> the<00:03:04.120> deployer<00:03:04.560> who<00:03:04.840> gave<00:03:05.000> you<00:03:05.200> that 00:03:06.110 --> 00:03:06.120 align:start position:0% system of the deployer who gave you that 00:03:06.120 --> 00:03:08.589 align:start position:0% system of the deployer who gave you that because<00:03:06.400> frankly<00:03:07.360> are<00:03:07.519> you<00:03:07.920> well<00:03:08.120> equipped 00:03:08.589 --> 00:03:08.599 align:start position:0% because frankly are you well equipped 00:03:08.599 --> 00:03:10.949 align:start position:0% because frankly are you well equipped enough<00:03:09.239> as<00:03:09.360> an<00:03:09.519> app<00:03:09.760> developer<00:03:10.360> to<00:03:10.560> deploy 00:03:10.949 --> 00:03:10.959 align:start position:0% enough as an app developer to deploy 00:03:10.959 --> 00:03:12.670 align:start position:0% enough as an app developer to deploy preferences<00:03:11.440> for<00:03:11.599> the<00:03:11.680> user<00:03:12.080> smart<00:03:12.360> contract 00:03:12.670 --> 00:03:12.680 align:start position:0% preferences for the user smart contract 00:03:12.680 --> 00:03:15.229 align:start position:0% preferences for the user smart contract wallet<00:03:13.640> if<00:03:13.799> they<00:03:13.920> want<00:03:14.040> to<00:03:14.200> say<00:03:14.760> exess<00:03:15.120> because 00:03:15.229 --> 00:03:15.239 align:start position:0% wallet if they want to say exess because 00:03:15.239 --> 00:03:17.229 align:start position:0% wallet if they want to say exess because we're<00:03:15.360> going<00:03:15.519> down<00:03:15.640> an<00:03:15.840> intense<00:03:16.239> system<00:03:17.120> are 00:03:17.229 --> 00:03:17.239 align:start position:0% we're going down an intense system are 00:03:17.239 --> 00:03:18.830 align:start position:0% we're going down an intense system are you<00:03:17.400> willing<00:03:17.680> to<00:03:17.879> express<00:03:18.159> a<00:03:18.319> preference<00:03:18.680> for 00:03:18.830 --> 00:03:18.840 align:start position:0% you willing to express a preference for 00:03:18.840 --> 00:03:20.030 align:start position:0% you willing to express a preference for them<00:03:19.000> to 00:03:20.030 --> 00:03:20.040 align:start position:0% them to 00:03:20.040 --> 00:03:22.949 align:start position:0% them to ensure<00:03:21.040> that<00:03:21.200> if<00:03:21.360> they<00:03:21.519> say<00:03:21.760> I<00:03:21.840> want<00:03:22.120> one<00:03:22.440> eth 00:03:22.949 --> 00:03:22.959 align:start position:0% ensure that if they say I want one eth 00:03:22.959 --> 00:03:24.949 align:start position:0% ensure that if they say I want one eth always<00:03:23.239> to<00:03:23.440> exist<00:03:23.680> on<00:03:23.879> mainnet<00:03:24.400> never<00:03:24.720> take 00:03:24.949 --> 00:03:24.959 align:start position:0% always to exist on mainnet never take 00:03:24.959 --> 00:03:26.830 align:start position:0% always to exist on mainnet never take away<00:03:25.280> that<00:03:25.400> one<00:03:25.680> eth<00:03:26.080> you<00:03:26.159> know<00:03:26.280> if<00:03:26.360> I<00:03:26.440> have<00:03:26.599> two 00:03:26.830 --> 00:03:26.840 align:start position:0% away that one eth you know if I have two 00:03:26.840 --> 00:03:29.429 align:start position:0% away that one eth you know if I have two it<00:03:26.959> can<00:03:27.080> go<00:03:27.200> down<00:03:27.319> to<00:03:27.799> one<00:03:28.799> are<00:03:28.920> you<00:03:29.120> ready<00:03:29.319> to 00:03:29.429 --> 00:03:29.439 align:start position:0% it can go down to one are you ready to 00:03:29.439 --> 00:03:31.309 align:start position:0% it can go down to one are you ready to deploy<00:03:29.920> that<00:03:30.080> type<00:03:30.200> of<00:03:30.360> preferences<00:03:31.120> and 00:03:31.309 --> 00:03:31.319 align:start position:0% deploy that type of preferences and 00:03:31.319 --> 00:03:33.229 align:start position:0% deploy that type of preferences and those<00:03:31.480> type<00:03:31.640> of<00:03:31.760> feature<00:03:32.120> sets<00:03:32.400> to<00:03:32.560> them<00:03:32.959> CU<00:03:33.120> if 00:03:33.229 --> 00:03:33.239 align:start position:0% those type of feature sets to them CU if 00:03:33.239 --> 00:03:34.949 align:start position:0% those type of feature sets to them CU if you're<00:03:33.480> not<00:03:33.799> you<00:03:33.920> should<00:03:34.280> never<00:03:34.519> be<00:03:34.720> giving 00:03:34.949 --> 00:03:34.959 align:start position:0% you're not you should never be giving 00:03:34.959 --> 00:03:37.190 align:start position:0% you're not you should never be giving them<00:03:35.120> a<00:03:35.319> smart<00:03:35.599> contract<00:03:36.040> wallet<00:03:37.040> you're 00:03:37.190 --> 00:03:37.200 align:start position:0% them a smart contract wallet you're 00:03:37.200 --> 00:03:38.470 align:start position:0% them a smart contract wallet you're setting<00:03:37.480> them<00:03:37.640> up<00:03:37.799> for<00:03:37.959> failure<00:03:38.280> and<00:03:38.360> you're 00:03:38.470 --> 00:03:38.480 align:start position:0% setting them up for failure and you're 00:03:38.480 --> 00:03:40.670 align:start position:0% setting them up for failure and you're sending<00:03:38.760> your<00:03:38.879> users<00:03:39.200> up<00:03:39.360> for<00:03:39.519> a<00:03:39.959> awful<00:03:40.280> ux 00:03:40.670 --> 00:03:40.680 align:start position:0% sending your users up for a awful ux 00:03:40.680 --> 00:03:42.710 align:start position:0% sending your users up for a awful ux experience<00:03:41.080> down<00:03:41.239> the 00:03:42.710 --> 00:03:42.720 align:start position:0% experience down the 00:03:42.720 --> 00:03:45.350 align:start position:0% experience down the road<00:03:43.720> and<00:03:44.560> frankly<00:03:44.920> it<00:03:45.000> just<00:03:45.080> creates 00:03:45.350 --> 00:03:45.360 align:start position:0% road and frankly it just creates 00:03:45.360 --> 00:03:47.110 align:start position:0% road and frankly it just creates fragmented<00:03:45.840> balances<00:03:46.560> and<00:03:46.640> it<00:03:46.760> doesn't<00:03:47.000> get 00:03:47.110 --> 00:03:47.120 align:start position:0% fragmented balances and it doesn't get 00:03:47.120 --> 00:03:48.750 align:start position:0% fragmented balances and it doesn't get us<00:03:47.280> anywhere<00:03:47.959> and<00:03:48.080> the<00:03:48.200> biggest<00:03:48.480> problem<00:03:48.680> we 00:03:48.750 --> 00:03:48.760 align:start position:0% us anywhere and the biggest problem we 00:03:48.760 --> 00:03:50.350 align:start position:0% us anywhere and the biggest problem we still<00:03:48.959> have<00:03:49.120> today<00:03:49.400> is<00:03:49.560> that<00:03:49.840> it<00:03:50.040> do<00:03:50.159> we<00:03:50.239> have 00:03:50.350 --> 00:03:50.360 align:start position:0% still have today is that it do we have 00:03:50.360 --> 00:03:52.270 align:start position:0% still have today is that it do we have any<00:03:50.519> mobile<00:03:50.959> app<00:03:51.159> developers 00:03:52.270 --> 00:03:52.280 align:start position:0% any mobile app developers 00:03:52.280 --> 00:03:54.869 align:start position:0% any mobile app developers here<00:03:53.280> have<00:03:53.400> you<00:03:53.599> ever<00:03:53.959> tried<00:03:54.239> to<00:03:54.360> communicate 00:03:54.869 --> 00:03:54.879 align:start position:0% here have you ever tried to communicate 00:03:54.879 --> 00:03:56.270 align:start position:0% here have you ever tried to communicate with<00:03:55.000> a<00:03:55.120> smart<00:03:55.400> contract<00:03:55.720> wallet<00:03:56.040> that<00:03:56.120> was 00:03:56.270 --> 00:03:56.280 align:start position:0% with a smart contract wallet that was 00:03:56.280 --> 00:03:58.030 align:start position:0% with a smart contract wallet that was deployed<00:03:56.799> by<00:03:56.959> another 00:03:58.030 --> 00:03:58.040 align:start position:0% deployed by another 00:03:58.040 --> 00:04:00.149 align:start position:0% deployed by another team<00:03:59.040> yeah<00:03:59.159> it<00:03:59.280> doesn't<00:03:59.519> work<00:03:59.920> it's 00:04:00.149 --> 00:04:00.159 align:start position:0% team yeah it doesn't work it's 00:04:00.159 --> 00:04:02.429 align:start position:0% team yeah it doesn't work it's impossible<00:04:01.159> we<00:04:01.319> work<00:04:01.519> with<00:04:01.680> game<00:04:01.879> developers 00:04:02.429 --> 00:04:02.439 align:start position:0% impossible we work with game developers 00:04:02.439 --> 00:04:04.789 align:start position:0% impossible we work with game developers they<00:04:02.680> can't<00:04:03.000> connect<00:04:03.360> to<00:04:03.680> remote<00:04:04.120> accounts 00:04:04.789 --> 00:04:04.799 align:start position:0% they can't connect to remote accounts 00:04:04.799 --> 00:04:06.830 align:start position:0% they can't connect to remote accounts it's<00:04:05.239> it's<00:04:05.439> literally<00:04:05.879> impossible<00:04:06.720> and 00:04:06.830 --> 00:04:06.840 align:start position:0% it's it's literally impossible and 00:04:06.840 --> 00:04:08.030 align:start position:0% it's it's literally impossible and that's<00:04:07.040> because<00:04:07.239> we've<00:04:07.400> moved<00:04:07.599> into<00:04:07.799> a<00:04:07.879> world 00:04:08.030 --> 00:04:08.040 align:start position:0% that's because we've moved into a world 00:04:08.040 --> 00:04:10.390 align:start position:0% that's because we've moved into a world of<00:04:08.200> pass<00:04:08.439> Keys<00:04:09.360> pass<00:04:09.599> keys<00:04:09.799> are<00:04:10.000> domain 00:04:10.390 --> 00:04:10.400 align:start position:0% of pass Keys pass keys are domain 00:04:10.400 --> 00:04:12.789 align:start position:0% of pass Keys pass keys are domain separated<00:04:11.400> you<00:04:11.680> if<00:04:11.840> chains<00:04:12.159> saafe<00:04:12.400> issues<00:04:12.680> you 00:04:12.789 --> 00:04:12.799 align:start position:0% separated you if chains saafe issues you 00:04:12.799 --> 00:04:15.229 align:start position:0% separated you if chains saafe issues you a<00:04:12.959> pass<00:04:13.200> key<00:04:13.599> only<00:04:13.840> the<00:04:13.959> chainsa<00:04:14.480> doio<00:04:14.920> domain 00:04:15.229 --> 00:04:15.239 align:start position:0% a pass key only the chainsa doio domain 00:04:15.239 --> 00:04:17.390 align:start position:0% a pass key only the chainsa doio domain can<00:04:15.439> ever<00:04:15.879> access<00:04:16.199> that<00:04:16.320> same<00:04:16.600> Pass<00:04:16.840> key<00:04:17.280> so 00:04:17.390 --> 00:04:17.400 align:start position:0% can ever access that same Pass key so 00:04:17.400 --> 00:04:19.469 align:start position:0% can ever access that same Pass key so you<00:04:17.519> need<00:04:17.680> a<00:04:17.759> way<00:04:17.880> to<00:04:18.040> talk<00:04:18.199> to<00:04:18.400> them<00:04:19.400> and 00:04:19.469 --> 00:04:19.479 align:start position:0% you need a way to talk to them and 00:04:19.479 --> 00:04:21.590 align:start position:0% you need a way to talk to them and that's<00:04:19.639> where<00:04:19.720> I'm<00:04:19.840> going<00:04:19.919> to<00:04:20.000> be<00:04:20.079> going<00:04:20.280> with 00:04:21.590 --> 00:04:21.600 align:start position:0% that's where I'm going to be going with 00:04:21.600 --> 00:04:25.189 align:start position:0% that's where I'm going to be going with this<00:04:22.680> um<00:04:23.680> a<00:04:23.880> quick<00:04:24.080> note<00:04:24.440> and<00:04:24.560> I'm<00:04:24.680> going<00:04:24.759> to<00:04:24.960> be 00:04:25.189 --> 00:04:25.199 align:start position:0% this um a quick note and I'm going to be 00:04:25.199 --> 00:04:27.230 align:start position:0% this um a quick note and I'm going to be very<00:04:25.840> you<00:04:25.960> know<00:04:26.440> this<00:04:26.560> might<00:04:26.720> be<00:04:26.800> a<00:04:26.880> bit<00:04:27.000> of<00:04:27.080> a 00:04:27.230 --> 00:04:27.240 align:start position:0% very you know this might be a bit of a 00:04:27.240 --> 00:04:28.870 align:start position:0% very you know this might be a bit of a lie<00:04:27.720> but<00:04:27.919> like<00:04:28.080> I<00:04:28.160> think<00:04:28.280> we're<00:04:28.440> getting<00:04:28.720> there 00:04:28.870 --> 00:04:28.880 align:start position:0% lie but like I think we're getting there 00:04:28.880 --> 00:04:29.950 align:start position:0% lie but like I think we're getting there within<00:04:29.120> 1<00:04:29.280> to<00:04:29.400> two<00:04:29.520> years<00:04:29.720> years<00:04:29.840> we're 00:04:29.950 --> 00:04:29.960 align:start position:0% within 1 to two years years we're 00:04:29.960 --> 00:04:30.950 align:start position:0% within 1 to two years years we're probably<00:04:30.160> going<00:04:30.240> to<00:04:30.280> see<00:04:30.440> 90%<00:04:30.840> of 00:04:30.950 --> 00:04:30.960 align:start position:0% probably going to see 90% of 00:04:30.960 --> 00:04:33.310 align:start position:0% probably going to see 90% of transactions<00:04:31.600> will<00:04:31.840> be<00:04:32.000> solved<00:04:32.880> there's<00:04:33.080> no 00:04:33.310 --> 00:04:33.320 align:start position:0% transactions will be solved there's no 00:04:33.320 --> 00:04:35.469 align:start position:0% transactions will be solved there's no doubt<00:04:33.560> about<00:04:33.840> that<00:04:34.520> they<00:04:34.720> it<00:04:34.919> we<00:04:35.039> are<00:04:35.240> going 00:04:35.469 --> 00:04:35.479 align:start position:0% doubt about that they it we are going 00:04:35.479 --> 00:04:36.870 align:start position:0% doubt about that they it we are going down<00:04:35.680> that<00:04:35.880> path<00:04:36.080> and<00:04:36.199> that's<00:04:36.400> going<00:04:36.600> to 00:04:36.870 --> 00:04:36.880 align:start position:0% down that path and that's going to 00:04:36.880 --> 00:04:39.430 align:start position:0% down that path and that's going to happen<00:04:37.880> um<00:04:38.120> so<00:04:38.400> with<00:04:38.600> that<00:04:38.759> in<00:04:38.919> mind<00:04:39.199> we<00:04:39.320> have 00:04:39.430 --> 00:04:39.440 align:start position:0% happen um so with that in mind we have 00:04:39.440 --> 00:04:40.749 align:start position:0% happen um so with that in mind we have to<00:04:39.600> think<00:04:39.800> there's<00:04:39.960> this<00:04:40.160> big<00:04:40.320> debate<00:04:40.600> of 00:04:40.749 --> 00:04:40.759 align:start position:0% to think there's this big debate of 00:04:40.759 --> 00:04:43.510 align:start position:0% to think there's this big debate of smart<00:04:41.120> wallet<00:04:41.479> versus<00:04:42.000> like<00:04:42.400> dumb<00:04:42.960> app<00:04:43.240> and<00:04:43.360> so 00:04:43.510 --> 00:04:43.520 align:start position:0% smart wallet versus like dumb app and so 00:04:43.520 --> 00:04:45.710 align:start position:0% smart wallet versus like dumb app and so and<00:04:43.720> so<00:04:43.880> forth<00:04:44.120> frankly<00:04:44.600> if<00:04:44.800> the<00:04:45.120> app<00:04:45.280> is<00:04:45.400> going 00:04:45.710 --> 00:04:45.720 align:start position:0% and so forth frankly if the app is going 00:04:45.720 --> 00:04:48.749 align:start position:0% and so forth frankly if the app is going multi-chain<00:04:46.400> and<00:04:46.520> you're<00:04:46.840> interacting<00:04:47.759> with 00:04:48.749 --> 00:04:48.759 align:start position:0% multi-chain and you're interacting with 00:04:48.759 --> 00:04:51.510 align:start position:0% multi-chain and you're interacting with different<00:04:49.440> contracts<00:04:49.960> on<00:04:50.160> different<00:04:50.520> chains 00:04:51.510 --> 00:04:51.520 align:start position:0% different contracts on different chains 00:04:51.520 --> 00:04:53.990 align:start position:0% different contracts on different chains you<00:04:51.639> are<00:04:51.919> smart<00:04:52.800> you<00:04:53.000> have<00:04:53.120> to<00:04:53.240> be<00:04:53.360> smart<00:04:53.800> you 00:04:53.990 --> 00:04:54.000 align:start position:0% you are smart you have to be smart you 00:04:54.000 --> 00:04:56.070 align:start position:0% you are smart you have to be smart you have<00:04:54.120> to<00:04:54.400> know<00:04:54.800> how<00:04:55.000> to<00:04:55.320> actually<00:04:55.720> make<00:04:55.919> and 00:04:56.070 --> 00:04:56.080 align:start position:0% have to know how to actually make and 00:04:56.080 --> 00:04:57.150 align:start position:0% have to know how to actually make and Bridge<00:04:56.440> those 00:04:57.150 --> 00:04:57.160 align:start position:0% Bridge those 00:04:57.160 --> 00:04:58.990 align:start position:0% Bridge those connections<00:04:58.160> otherwise<00:04:58.560> the<00:04:58.680> wallet's 00:04:58.990 --> 00:04:59.000 align:start position:0% connections otherwise the wallet's 00:04:59.000 --> 00:05:00.670 align:start position:0% connections otherwise the wallet's always<00:04:59.199> smart<00:04:59.440> let's<00:04:59.759> be<00:04:59.880> real<00:05:00.280> they<00:05:00.400> need<00:05:00.520> to 00:05:00.670 --> 00:05:00.680 align:start position:0% always smart let's be real they need to 00:05:00.680 --> 00:05:02.310 align:start position:0% always smart let's be real they need to be<00:05:00.919> the<00:05:01.039> one<00:05:01.199> to<00:05:01.360> ensure<00:05:01.639> that<00:05:01.759> the<00:05:01.880> user<00:05:02.120> is 00:05:02.310 --> 00:05:02.320 align:start position:0% be the one to ensure that the user is 00:05:02.320 --> 00:05:03.909 align:start position:0% be the one to ensure that the user is there<00:05:02.600> because<00:05:02.919> they<00:05:03.039> need<00:05:03.199> to<00:05:03.280> be<00:05:03.479> ping<00:05:03.800> that 00:05:03.909 --> 00:05:03.919 align:start position:0% there because they need to be ping that 00:05:03.919 --> 00:05:06.230 align:start position:0% there because they need to be ping that wall<00:05:04.160> in<00:05:04.320> for<00:05:04.479> I<00:05:04.520> was<00:05:04.680> describing 00:05:06.230 --> 00:05:06.240 align:start position:0% wall in for I was describing 00:05:06.240 --> 00:05:09.749 align:start position:0% wall in for I was describing earlier<00:05:07.240> now<00:05:08.240> let's<00:05:08.400> do<00:05:08.600> this<00:05:08.720> endgame<00:05:09.560> I'm 00:05:09.749 --> 00:05:09.759 align:start position:0% earlier now let's do this endgame I'm 00:05:09.759 --> 00:05:11.469 align:start position:0% earlier now let's do this endgame I'm going<00:05:09.840> to<00:05:10.039> verbally<00:05:10.400> abuse<00:05:10.639> you<00:05:10.759> with<00:05:10.880> erc's 00:05:11.469 --> 00:05:11.479 align:start position:0% going to verbally abuse you with erc's 00:05:11.479 --> 00:05:12.590 align:start position:0% going to verbally abuse you with erc's and<00:05:11.600> that's<00:05:11.759> totally<00:05:12.120> fine<00:05:12.320> there's<00:05:12.479> going<00:05:12.560> to 00:05:12.590 --> 00:05:12.600 align:start position:0% and that's totally fine there's going to 00:05:12.600 --> 00:05:14.270 align:start position:0% and that's totally fine there's going to be<00:05:12.919> there's<00:05:13.240> other<00:05:13.520> sessions<00:05:13.880> today<00:05:14.199> that 00:05:14.270 --> 00:05:14.280 align:start position:0% be there's other sessions today that 00:05:14.280 --> 00:05:16.230 align:start position:0% be there's other sessions today that will<00:05:14.520> help<00:05:14.720> you<00:05:14.960> learn<00:05:15.400> about<00:05:15.680> these<00:05:15.840> erc's 00:05:16.230 --> 00:05:16.240 align:start position:0% will help you learn about these erc's 00:05:16.240 --> 00:05:17.670 align:start position:0% will help you learn about these erc's more<00:05:16.360> in<00:05:16.479> deep<00:05:16.759> I'm<00:05:16.840> going<00:05:16.960> to<00:05:17.080> go<00:05:17.240> over<00:05:17.400> them 00:05:17.670 --> 00:05:17.680 align:start position:0% more in deep I'm going to go over them 00:05:17.680 --> 00:05:20.189 align:start position:0% more in deep I'm going to go over them as<00:05:18.160> quickly<00:05:18.479> as<00:05:18.600> I<00:05:18.759> can<00:05:19.360> as<00:05:19.520> effectively<00:05:20.000> as<00:05:20.080> I 00:05:20.189 --> 00:05:20.199 align:start position:0% as quickly as I can as effectively as I 00:05:20.199 --> 00:05:22.150 align:start position:0% as quickly as I can as effectively as I can<00:05:20.319> and<00:05:20.440> use<00:05:20.639> web<00:05:20.800> two<00:05:21.039> examples<00:05:21.479> so<00:05:21.639> you<00:05:21.759> can 00:05:22.150 --> 00:05:22.160 align:start position:0% can and use web two examples so you can 00:05:22.160 --> 00:05:23.830 align:start position:0% can and use web two examples so you can understand<00:05:22.360> why<00:05:22.520> they're<00:05:22.720> important<00:05:23.680> these 00:05:23.830 --> 00:05:23.840 align:start position:0% understand why they're important these 00:05:23.840 --> 00:05:27.029 align:start position:0% understand why they're important these eips<00:05:24.479> and<00:05:24.600> erc's<00:05:25.240> and<00:05:25.479> capes<00:05:26.160> are<00:05:26.319> ridden<00:05:26.639> by 00:05:27.029 --> 00:05:27.039 align:start position:0% eips and erc's and capes are ridden by 00:05:27.039 --> 00:05:29.110 align:start position:0% eips and erc's and capes are ridden by well<00:05:27.199> over<00:05:27.400> 20<00:05:27.720> plus<00:05:27.960> people<00:05:28.639> so<00:05:28.759> when<00:05:28.880> I<00:05:28.960> say 00:05:29.110 --> 00:05:29.120 align:start position:0% well over 20 plus people so when I say 00:05:29.120 --> 00:05:30.510 align:start position:0% well over 20 plus people so when I say there's<00:05:29.280> like<00:05:29.400> no<00:05:29.720> bias<00:05:30.000> in<00:05:30.120> here<00:05:30.280> I'm<00:05:30.400> just 00:05:30.510 --> 00:05:30.520 align:start position:0% there's like no bias in here I'm just 00:05:30.520 --> 00:05:32.629 align:start position:0% there's like no bias in here I'm just stitching<00:05:30.840> the<00:05:31.000> stuff<00:05:31.319> together<00:05:32.160> that<00:05:32.360> we're 00:05:32.629 --> 00:05:32.639 align:start position:0% stitching the stuff together that we're 00:05:32.639 --> 00:05:34.469 align:start position:0% stitching the stuff together that we're talking<00:05:32.919> about<00:05:33.080> in<00:05:33.199> the<00:05:33.280> wallet<00:05:33.560> meetups<00:05:34.319> at 00:05:34.469 --> 00:05:34.479 align:start position:0% talking about in the wallet meetups at 00:05:34.479 --> 00:05:36.510 align:start position:0% talking about in the wallet meetups at every 00:05:36.510 --> 00:05:36.520 align:start position:0% every 00:05:36.520 --> 00:05:38.550 align:start position:0% every conference<00:05:37.520> okay<00:05:37.840> here's<00:05:38.039> your<00:05:38.199> general 00:05:38.550 --> 00:05:38.560 align:start position:0% conference okay here's your general 00:05:38.560 --> 00:05:42.309 align:start position:0% conference okay here's your general interaction<00:05:39.400> right<00:05:39.639> dap<00:05:40.160> wallet<00:05:40.680> very<00:05:41.319> simple 00:05:42.309 --> 00:05:42.319 align:start position:0% interaction right dap wallet very simple 00:05:42.319 --> 00:05:44.189 align:start position:0% interaction right dap wallet very simple we<00:05:42.479> know<00:05:42.680> we<00:05:42.800> want<00:05:42.919> to<00:05:43.080> deploy<00:05:43.400> 4337 00:05:44.189 --> 00:05:44.199 align:start position:0% we know we want to deploy 4337 00:05:44.199 --> 00:05:46.430 align:start position:0% we know we want to deploy 4337 everywhere<00:05:44.919> that's<00:05:45.039> a<00:05:45.199> given<00:05:45.880> it's<00:05:46.080> the<00:05:46.240> best 00:05:46.430 --> 00:05:46.440 align:start position:0% everywhere that's a given it's the best 00:05:46.440 --> 00:05:47.790 align:start position:0% everywhere that's a given it's the best ux<00:05:46.800> we<00:05:46.919> can<00:05:47.080> get<00:05:47.280> because<00:05:47.400> we<00:05:47.520> can't<00:05:47.680> get 00:05:47.790 --> 00:05:47.800 align:start position:0% ux we can get because we can't get 00:05:47.800 --> 00:05:49.309 align:start position:0% ux we can get because we can't get native<00:05:48.080> account 00:05:49.309 --> 00:05:49.319 align:start position:0% native account 00:05:49.319 --> 00:05:51.590 align:start position:0% native account abstraction<00:05:50.319> we<00:05:50.479> know<00:05:50.840> pass<00:05:51.120> keys<00:05:51.319> are<00:05:51.479> the 00:05:51.590 --> 00:05:51.600 align:start position:0% abstraction we know pass keys are the 00:05:51.600 --> 00:05:53.110 align:start position:0% abstraction we know pass keys are the easiest<00:05:51.919> way<00:05:52.039> to<00:05:52.120> onboard<00:05:52.479> a<00:05:52.560> user<00:05:52.919> because 00:05:53.110 --> 00:05:53.120 align:start position:0% easiest way to onboard a user because 00:05:53.120 --> 00:05:54.950 align:start position:0% easiest way to onboard a user because seed<00:05:53.400> phrases<00:05:53.800> are<00:05:53.919> too<00:05:54.160> complicated<00:05:54.680> private 00:05:54.950 --> 00:05:54.960 align:start position:0% seed phrases are too complicated private 00:05:54.960 --> 00:05:56.870 align:start position:0% seed phrases are too complicated private keys<00:05:55.160> are<00:05:55.600> difficult<00:05:55.919> and<00:05:56.120> frankly<00:05:56.560> the<00:05:56.680> whole 00:05:56.870 --> 00:05:56.880 align:start position:0% keys are difficult and frankly the whole 00:05:56.880 --> 00:05:58.469 align:start position:0% keys are difficult and frankly the whole experience<00:05:57.240> that<00:05:57.319> we've<00:05:57.479> been<00:05:57.600> doing<00:05:57.880> before 00:05:58.469 --> 00:05:58.479 align:start position:0% experience that we've been doing before 00:05:58.479 --> 00:06:01.309 align:start position:0% experience that we've been doing before is<00:05:58.759> just<00:05:59.319> because<00:05:59.680> because<00:06:00.039> we<00:06:00.240> in<00:06:00.440> this<00:06:00.639> room 00:06:01.309 --> 00:06:01.319 align:start position:0% is just because because we in this room 00:06:01.319 --> 00:06:03.909 align:start position:0% is just because because we in this room frankly<00:06:02.000> are<00:06:02.199> ahead<00:06:02.400> of<00:06:02.479> the<00:06:02.639> curve<00:06:03.600> it's<00:06:03.759> not 00:06:03.909 --> 00:06:03.919 align:start position:0% frankly are ahead of the curve it's not 00:06:03.919 --> 00:06:05.749 align:start position:0% frankly are ahead of the curve it's not going<00:06:04.039> to<00:06:04.120> work<00:06:04.280> for<00:06:04.440> most<00:06:04.639> people<00:06:05.280> pass<00:06:05.560> keys 00:06:05.749 --> 00:06:05.759 align:start position:0% going to work for most people pass keys 00:06:05.759 --> 00:06:07.469 align:start position:0% going to work for most people pass keys are<00:06:05.919> a<00:06:06.080> must<00:06:06.400> and<00:06:06.520> they<00:06:06.639> live<00:06:06.800> at<00:06:06.919> the<00:06:07.039> wallet 00:06:07.469 --> 00:06:07.479 align:start position:0% are a must and they live at the wallet 00:06:07.479 --> 00:06:10.070 align:start position:0% are a must and they live at the wallet level<00:06:08.479> the<00:06:08.639> next<00:06:08.880> way<00:06:09.039> to<00:06:09.319> actually<00:06:09.639> broker 00:06:10.070 --> 00:06:10.080 align:start position:0% level the next way to actually broker 00:06:10.080 --> 00:06:11.350 align:start position:0% level the next way to actually broker this<00:06:10.240> system<00:06:10.520> is<00:06:10.639> to<00:06:10.759> realize<00:06:11.080> that<00:06:11.199> your 00:06:11.350 --> 00:06:11.360 align:start position:0% this system is to realize that your 00:06:11.360 --> 00:06:12.870 align:start position:0% this system is to realize that your dap's<00:06:11.720> never<00:06:11.919> going<00:06:12.039> to<00:06:12.280> actually<00:06:12.560> have<00:06:12.680> a 00:06:12.870 --> 00:06:12.880 align:start position:0% dap's never going to actually have a 00:06:12.880 --> 00:06:14.870 align:start position:0% dap's never going to actually have a wallet<00:06:13.440> like<00:06:13.599> a<00:06:13.720> smart<00:06:14.039> account<00:06:14.360> your<00:06:14.560> dap's 00:06:14.870 --> 00:06:14.880 align:start position:0% wallet like a smart account your dap's 00:06:14.880 --> 00:06:17.189 align:start position:0% wallet like a smart account your dap's going<00:06:15.000> to<00:06:15.080> use<00:06:15.240> an<00:06:15.360> embedded<00:06:15.800> wallet<00:06:16.639> why<00:06:17.080> you 00:06:17.189 --> 00:06:17.199 align:start position:0% going to use an embedded wallet why you 00:06:17.199 --> 00:06:19.150 align:start position:0% going to use an embedded wallet why you can<00:06:17.400> blind<00:06:17.720> sign<00:06:18.000> in<00:06:18.160> the<00:06:18.319> background<00:06:18.919> as<00:06:19.000> long 00:06:19.150 --> 00:06:19.160 align:start position:0% can blind sign in the background as long 00:06:19.160 --> 00:06:21.029 align:start position:0% can blind sign in the background as long as<00:06:19.240> you<00:06:19.319> have<00:06:19.520> permission<00:06:20.520> that<00:06:20.639> means<00:06:20.919> you 00:06:21.029 --> 00:06:21.039 align:start position:0% as you have permission that means you 00:06:21.039 --> 00:06:23.909 align:start position:0% as you have permission that means you can<00:06:21.280> actually<00:06:21.599> maintain<00:06:22.120> the<00:06:22.240> same<00:06:22.520> web<00:06:22.919> 2 00:06:23.909 --> 00:06:23.919 align:start position:0% can actually maintain the same web 2 00:06:23.919 --> 00:06:26.110 align:start position:0% can actually maintain the same web 2 experience<00:06:24.440> you<00:06:24.639> thought<00:06:24.840> you<00:06:25.000> needed<00:06:25.919> this 00:06:26.110 --> 00:06:26.120 align:start position:0% experience you thought you needed this 00:06:26.120 --> 00:06:27.909 align:start position:0% experience you thought you needed this means<00:06:26.680> that<00:06:26.800> you<00:06:26.960> don't<00:06:27.160> need<00:06:27.319> to<00:06:27.520> go<00:06:27.639> and<00:06:27.800> make 00:06:27.909 --> 00:06:27.919 align:start position:0% means that you don't need to go and make 00:06:27.919 --> 00:06:30.070 align:start position:0% means that you don't need to go and make a<00:06:28.160> job<00:06:28.400> posting<00:06:28.800> that<00:06:28.960> says<00:06:29.240> hey<00:06:29.360> I<00:06:29.599> need<00:06:29.720> a<00:06:29.840> web 00:06:30.070 --> 00:06:30.080 align:start position:0% a job posting that says hey I need a web 00:06:30.080 --> 00:06:32.830 align:start position:0% a job posting that says hey I need a web 3<00:06:30.599> designer<00:06:31.599> no<00:06:31.840> no<00:06:32.000> you<00:06:32.120> just<00:06:32.280> need<00:06:32.560> a 00:06:32.830 --> 00:06:32.840 align:start position:0% 3 designer no no you just need a 00:06:32.840 --> 00:06:35.230 align:start position:0% 3 designer no no you just need a designer<00:06:33.840> you<00:06:33.960> need<00:06:34.120> a<00:06:34.360> really<00:06:34.639> good<00:06:34.880> designer 00:06:35.230 --> 00:06:35.240 align:start position:0% designer you need a really good designer 00:06:35.240 --> 00:06:36.870 align:start position:0% designer you need a really good designer that<00:06:35.319> knows<00:06:35.520> what<00:06:35.639> they're<00:06:35.840> doing<00:06:36.520> and<00:06:36.680> that's 00:06:36.870 --> 00:06:36.880 align:start position:0% that knows what they're doing and that's 00:06:36.880 --> 00:06:38.469 align:start position:0% that knows what they're doing and that's it<00:06:37.039> you<00:06:37.160> can<00:06:37.319> build<00:06:37.639> Web<00:06:37.800> Two<00:06:37.960> experiences<00:06:38.400> you 00:06:38.469 --> 00:06:38.479 align:start position:0% it you can build Web Two experiences you 00:06:38.479 --> 00:06:40.270 align:start position:0% it you can build Web Two experiences you can<00:06:38.560> get<00:06:38.680> a<00:06:38.800> per<00:06:39.120> desk<00:06:39.400> that<00:06:39.520> looks<00:06:39.720> like<00:06:39.919> Robin 00:06:40.270 --> 00:06:40.280 align:start position:0% can get a per desk that looks like Robin 00:06:40.280 --> 00:06:43.070 align:start position:0% can get a per desk that looks like Robin Hood<00:06:41.039> there's<00:06:41.280> no<00:06:41.479> reason<00:06:41.720> you<00:06:41.919> can't<00:06:42.199> do<00:06:42.440> that 00:06:43.070 --> 00:06:43.080 align:start position:0% Hood there's no reason you can't do that 00:06:43.080 --> 00:06:45.309 align:start position:0% Hood there's no reason you can't do that the<00:06:43.199> embedded<00:06:43.560> wall<00:06:43.759> allows<00:06:43.960> us<00:06:44.080> to<00:06:44.160> have<00:06:44.319> that 00:06:45.309 --> 00:06:45.319 align:start position:0% the embedded wall allows us to have that 00:06:45.319 --> 00:06:48.790 align:start position:0% the embedded wall allows us to have that control<00:06:46.319> we<00:06:46.440> need<00:06:46.560> to<00:06:46.759> know<00:06:47.160> how<00:06:47.960> to<00:06:48.280> register 00:06:48.790 --> 00:06:48.800 align:start position:0% control we need to know how to register 00:06:48.800 --> 00:06:50.270 align:start position:0% control we need to know how to register people<00:06:49.280> now<00:06:49.440> this<00:06:49.560> is<00:06:49.680> one<00:06:49.880> that<00:06:50.000> a<00:06:50.080> lot<00:06:50.199> of 00:06:50.270 --> 00:06:50.280 align:start position:0% people now this is one that a lot of 00:06:50.280 --> 00:06:51.469 align:start position:0% people now this is one that a lot of people<00:06:50.440> don't<00:06:50.599> realize<00:06:50.880> the<00:06:51.000> capes<00:06:51.240> chain 00:06:51.469 --> 00:06:51.479 align:start position:0% people don't realize the capes chain 00:06:51.479 --> 00:06:54.110 align:start position:0% people don't realize the capes chain agnostic<00:06:51.919> Improvement<00:06:52.800> proposals<00:06:53.800> Green 00:06:54.110 --> 00:06:54.120 align:start position:0% agnostic Improvement proposals Green 00:06:54.120 --> 00:06:57.150 align:start position:0% agnostic Improvement proposals Green Field<00:06:54.440> playing<00:06:54.680> field<00:06:54.960> for<00:06:55.639> not<00:06:55.840> just<00:06:56.080> evm<00:06:56.720> but 00:06:57.150 --> 00:06:57.160 align:start position:0% Field playing field for not just evm but 00:06:57.160 --> 00:06:58.550 align:start position:0% Field playing field for not just evm but the<00:06:57.319> whole<00:06:57.599> spectrum<00:06:57.960> of<00:06:58.120> blockchain 00:06:58.550 --> 00:06:58.560 align:start position:0% the whole spectrum of blockchain 00:06:58.560 --> 00:07:01.670 align:start position:0% the whole spectrum of blockchain standards<00:06:59.879> Cape<00:07:00.160> 275<00:07:00.919> basically<00:07:01.280> says<00:07:01.560> how 00:07:01.670 --> 00:07:01.680 align:start position:0% standards Cape 275 basically says how 00:07:01.680 --> 00:07:03.909 align:start position:0% standards Cape 275 basically says how can<00:07:01.800> we<00:07:01.919> get<00:07:02.000> to<00:07:02.160> a<00:07:02.280> one-click<00:07:02.720> onboarding<00:07:03.720> you 00:07:03.909 --> 00:07:03.919 align:start position:0% can we get to a one-click onboarding you 00:07:03.919 --> 00:07:06.390 align:start position:0% can we get to a one-click onboarding you type<00:07:04.280> I<00:07:04.400> type<00:07:04.560> in<00:07:04.680> Greg<00:07:04.919> theeg<00:07:05.199> greek.<00:07:06.199> it 00:07:06.390 --> 00:07:06.400 align:start position:0% type I type in Greg theeg greek. it 00:07:06.400 --> 00:07:08.350 align:start position:0% type I type in Greg theeg greek. it looks<00:07:06.639> up<00:07:06.840> to<00:07:06.960> see<00:07:07.280> who<00:07:07.560> deployed<00:07:07.960> my<00:07:08.080> smart 00:07:08.350 --> 00:07:08.360 align:start position:0% looks up to see who deployed my smart 00:07:08.360 --> 00:07:11.309 align:start position:0% looks up to see who deployed my smart contract<00:07:08.680> wallet<00:07:09.039> for<00:07:09.199> me<00:07:09.960> and<00:07:10.160> from<00:07:10.479> there<00:07:11.160> we 00:07:11.309 --> 00:07:11.319 align:start position:0% contract wallet for me and from there we 00:07:11.319 --> 00:07:14.309 align:start position:0% contract wallet for me and from there we generate<00:07:11.680> a<00:07:11.879> slug<00:07:12.520> for<00:07:12.720> an<00:07:12.919> HTTP<00:07:13.680> request<00:07:14.120> or 00:07:14.309 --> 00:07:14.319 align:start position:0% generate a slug for an HTTP request or 00:07:14.319 --> 00:07:16.629 align:start position:0% generate a slug for an HTTP request or an<00:07:14.520> iframe<00:07:15.039> or<00:07:15.160> whatever<00:07:16.160> and<00:07:16.280> this<00:07:16.400> is<00:07:16.479> where 00:07:16.629 --> 00:07:16.639 align:start position:0% an iframe or whatever and this is where 00:07:16.639 --> 00:07:20.790 align:start position:0% an iframe or whatever and this is where the<00:07:16.759> magic<00:07:17.080> happens<00:07:17.479> ERC<00:07:18.360> 75<00:07:19.360> 75<00:07:20.280> is<00:07:20.440> the<00:07:20.599> same 00:07:20.790 --> 00:07:20.800 align:start position:0% the magic happens ERC 75 75 is the same 00:07:20.800 --> 00:07:23.670 align:start position:0% the magic happens ERC 75 75 is the same thing<00:07:21.000> as<00:07:21.400> ooth<00:07:22.400> it's<00:07:22.599> the<00:07:22.800> idea<00:07:23.280> that<00:07:23.440> it 00:07:23.670 --> 00:07:23.680 align:start position:0% thing as ooth it's the idea that it 00:07:23.680 --> 00:07:25.309 align:start position:0% thing as ooth it's the idea that it links<00:07:24.080> you<00:07:24.319> when<00:07:24.440> you<00:07:24.560> click<00:07:24.800> sign<00:07:25.000> in<00:07:25.160> with 00:07:25.309 --> 00:07:25.319 align:start position:0% links you when you click sign in with 00:07:25.319 --> 00:07:28.550 align:start position:0% links you when you click sign in with Google<00:07:25.639> it<00:07:25.759> links<00:07:26.039> you<00:07:26.240> out<00:07:26.440> to<00:07:26.879> Google<00:07:27.879> right 00:07:28.550 --> 00:07:28.560 align:start position:0% Google it links you out to Google right 00:07:28.560 --> 00:07:29.710 align:start position:0% Google it links you out to Google right we<00:07:28.759> because<00:07:28.960> I<00:07:29.080> looked<00:07:29.280> up<00:07:29.360> in<00:07:29.520> in<00:07:29.599> the 00:07:29.710 --> 00:07:29.720 align:start position:0% we because I looked up in in the 00:07:29.720 --> 00:07:32.670 align:start position:0% we because I looked up in in the registry<00:07:30.240> who<00:07:30.440> deployed<00:07:30.879> this<00:07:31.319> wallet<00:07:32.319> I<00:07:32.440> can 00:07:32.670 --> 00:07:32.680 align:start position:0% registry who deployed this wallet I can 00:07:32.680 --> 00:07:34.830 align:start position:0% registry who deployed this wallet I can actually<00:07:32.960> go<00:07:33.120> in<00:07:33.479> directly<00:07:33.879> to<00:07:34.080> that<00:07:34.240> user<00:07:34.680> so 00:07:34.830 --> 00:07:34.840 align:start position:0% actually go in directly to that user so 00:07:34.840 --> 00:07:36.749 align:start position:0% actually go in directly to that user so I<00:07:34.919> can<00:07:35.080> use<00:07:35.319> that<00:07:35.520> pass<00:07:35.840> key<00:07:36.080> to<00:07:36.199> get<00:07:36.440> access<00:07:36.639> to 00:07:36.749 --> 00:07:36.759 align:start position:0% I can use that pass key to get access to 00:07:36.759 --> 00:07:39.230 align:start position:0% I can use that pass key to get access to that<00:07:36.879> 4337<00:07:37.759> account<00:07:38.360> and<00:07:38.520> now<00:07:38.680> I<00:07:38.759> can<00:07:38.919> use<00:07:39.120> it 00:07:39.230 --> 00:07:39.240 align:start position:0% that 4337 account and now I can use it 00:07:39.240 --> 00:07:41.230 align:start position:0% that 4337 account and now I can use it with<00:07:39.319> the<00:07:39.440> embedded<00:07:39.759> wallet<00:07:40.000> on<00:07:40.120> my 00:07:41.230 --> 00:07:41.240 align:start position:0% with the embedded wallet on my 00:07:41.240 --> 00:07:44.230 align:start position:0% with the embedded wallet on my app<00:07:42.240> but<00:07:42.479> permissions 00:07:44.230 --> 00:07:44.240 align:start position:0% app but permissions 00:07:44.240 --> 00:07:46.909 align:start position:0% app but permissions 7715<00:07:45.240> we<00:07:45.479> stack<00:07:45.759> a<00:07:45.919> permission<00:07:46.400> across<00:07:46.759> the 00:07:46.909 --> 00:07:46.919 align:start position:0% 7715 we stack a permission across the 00:07:46.919 --> 00:07:49.149 align:start position:0% 7715 we stack a permission across the wire<00:07:47.280> protocol<00:07:48.159> by<00:07:48.319> stacking<00:07:48.680> a<00:07:48.800> permission 00:07:49.149 --> 00:07:49.159 align:start position:0% wire protocol by stacking a permission 00:07:49.159 --> 00:07:50.790 align:start position:0% wire protocol by stacking a permission across<00:07:49.440> the<00:07:49.599> wire<00:07:49.879> protocol<00:07:50.319> what<00:07:50.440> you<00:07:50.520> end<00:07:50.680> up 00:07:50.790 --> 00:07:50.800 align:start position:0% across the wire protocol what you end up 00:07:50.800 --> 00:07:53.070 align:start position:0% across the wire protocol what you end up getting<00:07:51.039> now<00:07:51.199> is<00:07:51.400> you<00:07:51.479> can<00:07:51.599> be<00:07:51.919> expressive<00:07:52.919> hey 00:07:53.070 --> 00:07:53.080 align:start position:0% getting now is you can be expressive hey 00:07:53.080 --> 00:07:55.589 align:start position:0% getting now is you can be expressive hey my<00:07:53.240> per<00:07:53.560> desk<00:07:53.759> wants<00:07:53.919> to<00:07:54.000> spend<00:07:54.240> a<00:07:54.360> th000<00:07:54.639> usdc 00:07:55.589 --> 00:07:55.599 align:start position:0% my per desk wants to spend a th000 usdc 00:07:55.599 --> 00:07:59.469 align:start position:0% my per desk wants to spend a th000 usdc per<00:07:55.879> hour<00:07:56.879> and<00:07:57.039> make<00:07:57.199> it<00:07:57.440> expire<00:07:57.840> in<00:07:58.000> 24<00:07:58.440> hours 00:07:59.469 --> 00:07:59.479 align:start position:0% per hour and make it expire in 24 hours 00:07:59.479 --> 00:08:02.070 align:start position:0% per hour and make it expire in 24 hours what<00:07:59.560> does<00:07:59.680> that<00:07:59.840> resemble<00:08:00.759> a<00:08:00.879> jbt<00:08:01.479> token 00:08:02.070 --> 00:08:02.080 align:start position:0% what does that resemble a jbt token 00:08:02.080 --> 00:08:03.790 align:start position:0% what does that resemble a jbt token something<00:08:02.360> we're<00:08:02.520> used<00:08:02.720> to<00:08:03.240> we're<00:08:03.400> making<00:08:03.680> the 00:08:03.790 --> 00:08:03.800 align:start position:0% something we're used to we're making the 00:08:03.800 --> 00:08:05.869 align:start position:0% something we're used to we're making the app<00:08:04.000> development<00:08:04.400> cycle<00:08:04.720> easier 00:08:05.869 --> 00:08:05.879 align:start position:0% app development cycle easier 00:08:05.879 --> 00:08:08.430 align:start position:0% app development cycle easier here<00:08:06.879> finally 00:08:08.430 --> 00:08:08.440 align:start position:0% here finally 00:08:08.440 --> 00:08:12.230 align:start position:0% here finally 7579<00:08:09.440> Ryan<00:08:09.800> Stone<00:08:10.159> team<00:08:10.639> big<00:08:10.840> shout<00:08:11.159> out<00:08:12.080> the 00:08:12.230 --> 00:08:12.240 align:start position:0% 7579 Ryan Stone team big shout out the 00:08:12.240 --> 00:08:14.309 align:start position:0% 7579 Ryan Stone team big shout out the idea<00:08:12.720> here<00:08:13.280> your<00:08:13.479> app<00:08:13.639> wants<00:08:13.840> to<00:08:13.919> be<00:08:14.039> a<00:08:14.159> little 00:08:14.309 --> 00:08:14.319 align:start position:0% idea here your app wants to be a little 00:08:14.319 --> 00:08:16.510 align:start position:0% idea here your app wants to be a little bit<00:08:14.440> more<00:08:14.680> expressive<00:08:15.680> the<00:08:15.840> smart<00:08:16.159> account 00:08:16.510 --> 00:08:16.520 align:start position:0% bit more expressive the smart account 00:08:16.520 --> 00:08:18.909 align:start position:0% bit more expressive the smart account isn't<00:08:16.960> what<00:08:17.120> you<00:08:17.280> want<00:08:17.440> it<00:08:17.599> to<00:08:17.759> be<00:08:18.479> so<00:08:18.639> you<00:08:18.720> can 00:08:18.909 --> 00:08:18.919 align:start position:0% isn't what you want it to be so you can 00:08:18.919 --> 00:08:22.710 align:start position:0% isn't what you want it to be so you can develop<00:08:19.240> a<00:08:19.360> plugin<00:08:20.159> directly<00:08:20.960> link<00:08:21.280> it<00:08:21.919> onto 00:08:22.710 --> 00:08:22.720 align:start position:0% develop a plugin directly link it onto 00:08:22.720 --> 00:08:24.670 align:start position:0% develop a plugin directly link it onto the<00:08:22.879> smart<00:08:23.199> account<00:08:23.720> that<00:08:23.840> you<00:08:24.199> don't<00:08:24.440> really 00:08:24.670 --> 00:08:24.680 align:start position:0% the smart account that you don't really 00:08:24.680 --> 00:08:28.830 align:start position:0% the smart account that you don't really know<00:08:25.360> about<00:08:26.360> finally<00:08:27.039> 7811<00:08:28.039> if<00:08:28.280> anybody<00:08:28.639> keeps 00:08:28.830 --> 00:08:28.840 align:start position:0% know about finally 7811 if anybody keeps 00:08:28.840 --> 00:08:31.189 align:start position:0% know about finally 7811 if anybody keeps up<00:08:29.000> in<00:08:29.120> standard<00:08:29.800> here<00:08:30.400> you<00:08:30.680> probably<00:08:30.919> haven't 00:08:31.189 --> 00:08:31.199 align:start position:0% up in standard here you probably haven't 00:08:31.199 --> 00:08:33.350 align:start position:0% up in standard here you probably haven't kept<00:08:31.440> up<00:08:31.599> with<00:08:31.759> this<00:08:31.879> one<00:08:32.279> it<00:08:32.440> got<00:08:32.839> announced 00:08:33.350 --> 00:08:33.360 align:start position:0% kept up with this one it got announced 00:08:33.360 --> 00:08:34.909 align:start position:0% kept up with this one it got announced last<00:08:33.599> week<00:08:34.200> and<00:08:34.320> there's<00:08:34.440> going<00:08:34.519> to<00:08:34.599> be<00:08:34.680> a<00:08:34.760> lot 00:08:34.909 --> 00:08:34.919 align:start position:0% last week and there's going to be a lot 00:08:34.919 --> 00:08:38.550 align:start position:0% last week and there's going to be a lot built<00:08:35.120> up<00:08:35.320> on<00:08:35.519> top<00:08:35.680> of<00:08:35.839> it<00:08:36.680> the<00:08:36.839> simple<00:08:37.440> gist<00:08:38.440> I 00:08:38.550 --> 00:08:38.560 align:start position:0% built up on top of it the simple gist I 00:08:38.560 --> 00:08:40.509 align:start position:0% built up on top of it the simple gist I want<00:08:38.680> to<00:08:38.880> know<00:08:39.120> from<00:08:39.320> the<00:08:39.519> wallet<00:08:40.200> what<00:08:40.320> are 00:08:40.509 --> 00:08:40.519 align:start position:0% want to know from the wallet what are 00:08:40.519 --> 00:08:42.389 align:start position:0% want to know from the wallet what are the<00:08:40.719> assets<00:08:41.560> I<00:08:41.680> don't<00:08:41.880> want<00:08:41.959> to<00:08:42.120> use<00:08:42.240> an 00:08:42.389 --> 00:08:42.399 align:start position:0% the assets I don't want to use an 00:08:42.399 --> 00:08:44.590 align:start position:0% the assets I don't want to use an indexer<00:08:42.919> anymore<00:08:43.440> I'm<00:08:43.719> tired<00:08:44.039> of<00:08:44.240> having<00:08:44.440> to 00:08:44.590 --> 00:08:44.600 align:start position:0% indexer anymore I'm tired of having to 00:08:44.600 --> 00:08:47.790 align:start position:0% indexer anymore I'm tired of having to go<00:08:44.720> and<00:08:45.120> query<00:08:46.120> you<00:08:46.240> know<00:08:46.440> an<00:08:46.600> RPC<00:08:47.160> node<00:08:47.560> on<00:08:47.680> a 00:08:47.790 --> 00:08:47.800 align:start position:0% go and query you know an RPC node on a 00:08:47.800 --> 00:08:49.790 align:start position:0% go and query you know an RPC node on a for<00:08:48.120> Loop<00:08:48.399> over<00:08:48.600> the<00:08:48.800> assets<00:08:49.160> I<00:08:49.279> want<00:08:49.440> to<00:08:49.600> know 00:08:49.790 --> 00:08:49.800 align:start position:0% for Loop over the assets I want to know 00:08:49.800 --> 00:08:51.910 align:start position:0% for Loop over the assets I want to know about<00:08:50.480> just<00:08:50.600> tell<00:08:50.760> me<00:08:50.920> what<00:08:51.000> do<00:08:51.120> you<00:08:51.279> have 00:08:51.910 --> 00:08:51.920 align:start position:0% about just tell me what do you have 00:08:51.920 --> 00:08:53.630 align:start position:0% about just tell me what do you have what's<00:08:52.080> the<00:08:52.240> balance<00:08:52.560> of<00:08:52.680> it<00:08:53.120> it's<00:08:53.279> single 00:08:53.630 --> 00:08:53.640 align:start position:0% what's the balance of it it's single 00:08:53.640 --> 00:08:55.269 align:start position:0% what's the balance of it it's single chain<00:08:54.120> we're<00:08:54.240> going<00:08:54.360> to<00:08:54.480> take<00:08:54.600> it 00:08:55.269 --> 00:08:55.279 align:start position:0% chain we're going to take it 00:08:55.279 --> 00:08:57.550 align:start position:0% chain we're going to take it multi-chain<00:08:56.279> there's<00:08:56.480> a<00:08:56.600> lot<00:08:56.720> of<00:08:56.839> other<00:08:57.000> erc's 00:08:57.550 --> 00:08:57.560 align:start position:0% multi-chain there's a lot of other erc's 00:08:57.560 --> 00:08:59.230 align:start position:0% multi-chain there's a lot of other erc's that<00:08:57.680> go<00:08:57.800> on<00:08:58.000> this<00:08:58.519> but<00:08:58.680> the<00:08:58.839> interesting 00:08:59.230 --> 00:08:59.240 align:start position:0% that go on this but the interesting 00:08:59.240 --> 00:09:00.910 align:start position:0% that go on this but the interesting thing<00:08:59.480> thing<00:08:59.720> the<00:08:59.839> one<00:09:00.079> thing<00:09:00.240> to<00:09:00.560> keep<00:09:00.760> in 00:09:00.910 --> 00:09:00.920 align:start position:0% thing thing the one thing to keep in 00:09:00.920 --> 00:09:04.910 align:start position:0% thing thing the one thing to keep in mind<00:09:01.760> 7<00:09:02.279> tri5<00:09:03.279> it's<00:09:03.480> super<00:09:03.800> ambitious<00:09:04.640> very 00:09:04.910 --> 00:09:04.920 align:start position:0% mind 7 tri5 it's super ambitious very 00:09:04.920 --> 00:09:06.870 align:start position:0% mind 7 tri5 it's super ambitious very ambitious<00:09:05.800> we're<00:09:05.959> not<00:09:06.160> there<00:09:06.399> yet<00:09:06.640> we're 00:09:06.870 --> 00:09:06.880 align:start position:0% ambitious we're not there yet we're 00:09:06.880 --> 00:09:08.990 align:start position:0% ambitious we're not there yet we're really<00:09:07.120> close<00:09:07.839> we<00:09:07.959> need<00:09:08.240> all<00:09:08.440> these<00:09:08.600> other 00:09:08.990 --> 00:09:09.000 align:start position:0% really close we need all these other 00:09:09.000 --> 00:09:11.710 align:start position:0% really close we need all these other eips<00:09:09.560> to<00:09:09.720> get<00:09:09.880> standardized<00:09:10.440> on<00:09:10.680> top<00:09:11.360> but<00:09:11.519> once 00:09:11.710 --> 00:09:11.720 align:start position:0% eips to get standardized on top but once 00:09:11.720 --> 00:09:14.710 align:start position:0% eips to get standardized on top but once we<00:09:12.040> do<00:09:13.040> the<00:09:13.160> one<00:09:13.320> thing<00:09:13.519> we<00:09:13.760> get<00:09:14.200> is<00:09:14.360> we<00:09:14.519> get 00:09:14.710 --> 00:09:14.720 align:start position:0% we do the one thing we get is we get 00:09:14.720 --> 00:09:16.350 align:start position:0% we do the one thing we get is we get this<00:09:14.880> communication<00:09:15.600> channel<00:09:16.040> that<00:09:16.160> we've 00:09:16.350 --> 00:09:16.360 align:start position:0% this communication channel that we've 00:09:16.360 --> 00:09:19.509 align:start position:0% this communication channel that we've never<00:09:16.720> had<00:09:17.120> to<00:09:17.279> a<00:09:17.440> remote<00:09:18.160> account<00:09:19.160> the<00:09:19.320> same 00:09:19.509 --> 00:09:19.519 align:start position:0% never had to a remote account the same 00:09:19.519 --> 00:09:21.710 align:start position:0% never had to a remote account the same way<00:09:19.680> we<00:09:19.800> do<00:09:19.920> with<00:09:20.079> oos<00:09:20.560> so<00:09:20.680> when<00:09:20.800> a<00:09:20.959> web<00:09:21.160> 2<00:09:21.399> user 00:09:21.710 --> 00:09:21.720 align:start position:0% way we do with oos so when a web 2 user 00:09:21.720 --> 00:09:24.949 align:start position:0% way we do with oos so when a web 2 user comes<00:09:21.920> into<00:09:22.120> the<00:09:22.240> web<00:09:22.440> 3<00:09:23.079> space<00:09:24.079> it<00:09:24.240> looks<00:09:24.560> like 00:09:24.949 --> 00:09:24.959 align:start position:0% comes into the web 3 space it looks like 00:09:24.959 --> 00:09:27.630 align:start position:0% comes into the web 3 space it looks like you<00:09:25.079> know<00:09:25.440> Google<00:09:25.920> asking<00:09:26.240> for<00:09:26.880> an<00:09:27.079> app<00:09:27.320> asking 00:09:27.630 --> 00:09:27.640 align:start position:0% you know Google asking for an app asking 00:09:27.640 --> 00:09:29.069 align:start position:0% you know Google asking for an app asking Google<00:09:28.040> hey<00:09:28.160> can<00:09:28.279> I<00:09:28.360> borrow<00:09:28.640> your<00:09:28.800> calendar 00:09:29.069 --> 00:09:29.079 align:start position:0% Google hey can I borrow your calendar 00:09:29.079 --> 00:09:30.269 align:start position:0% Google hey can I borrow your calendar information 00:09:30.269 --> 00:09:30.279 align:start position:0% information 00:09:30.279 --> 00:09:31.750 align:start position:0% information but<00:09:30.399> in<00:09:30.560> this<00:09:30.760> way<00:09:30.880> it's<00:09:31.040> going<00:09:31.120> to<00:09:31.320> register 00:09:31.750 --> 00:09:31.760 align:start position:0% but in this way it's going to register 00:09:31.760 --> 00:09:33.550 align:start position:0% but in this way it's going to register plugins<00:09:32.200> it's<00:09:32.320> going<00:09:32.440> to<00:09:32.680> ask<00:09:32.880> for<00:09:33.120> permission 00:09:33.550 --> 00:09:33.560 align:start position:0% plugins it's going to ask for permission 00:09:33.560 --> 00:09:36.230 align:start position:0% plugins it's going to ask for permission on<00:09:33.800> how<00:09:33.920> to<00:09:34.279> spend<00:09:34.680> wallets<00:09:35.000> from<00:09:35.160> your<00:09:35.320> funds 00:09:36.230 --> 00:09:36.240 align:start position:0% on how to spend wallets from your funds 00:09:36.240 --> 00:09:39.069 align:start position:0% on how to spend wallets from your funds this<00:09:36.360> way<00:09:36.519> we're<00:09:36.680> not<00:09:36.920> depositing<00:09:37.600> funds<00:09:38.160> into 00:09:39.069 --> 00:09:39.079 align:start position:0% this way we're not depositing funds into 00:09:39.079 --> 00:09:41.829 align:start position:0% this way we're not depositing funds into you<00:09:39.200> know<00:09:39.480> poly<00:09:39.839> Market<00:09:40.680> instead<00:09:41.160> you're<00:09:41.399> just 00:09:41.829 --> 00:09:41.839 align:start position:0% you know poly Market instead you're just 00:09:41.839 --> 00:09:43.389 align:start position:0% you know poly Market instead you're just they're<00:09:42.079> borrowing 00:09:43.389 --> 00:09:43.399 align:start position:0% they're borrowing 00:09:43.399 --> 00:09:45.870 align:start position:0% they're borrowing them<00:09:44.399> and<00:09:44.560> I<00:09:44.680> think<00:09:44.800> I'm<00:09:44.920> running<00:09:45.120> out<00:09:45.240> of<00:09:45.480> time 00:09:45.870 --> 00:09:45.880 align:start position:0% them and I think I'm running out of time 00:09:45.880 --> 00:09:47.590 align:start position:0% them and I think I'm running out of time there's<00:09:46.000> a<00:09:46.200> timeline<00:09:46.600> here<00:09:46.800> I'll<00:09:46.959> skip<00:09:47.200> to 00:09:47.590 --> 00:09:47.600 align:start position:0% there's a timeline here I'll skip to 00:09:47.600 --> 00:09:49.630 align:start position:0% there's a timeline here I'll skip to when<00:09:47.839> end<00:09:48.279> I<00:09:48.360> don't<00:09:48.480> know<00:09:48.640> I<00:09:48.760> got<00:09:48.880> quoted<00:09:49.200> two 00:09:49.630 --> 00:09:49.640 align:start position:0% when end I don't know I got quoted two 00:09:49.640 --> 00:09:52.030 align:start position:0% when end I don't know I got quoted two two<00:09:49.920> years<00:09:50.160> from<00:09:50.399> now<00:09:50.680> the<00:09:50.760> other<00:09:51.040> day<00:09:51.800> I'm<00:09:51.920> not 00:09:52.030 --> 00:09:52.040 align:start position:0% two years from now the other day I'm not 00:09:52.040 --> 00:09:53.430 align:start position:0% two years from now the other day I'm not going<00:09:52.120> to<00:09:52.360> lie<00:09:52.680> I<00:09:52.760> think<00:09:52.880> we<00:09:53.000> can<00:09:53.120> be<00:09:53.240> a<00:09:53.279> bit 00:09:53.430 --> 00:09:53.440 align:start position:0% going to lie I think we can be a bit 00:09:53.440 --> 00:09:55.949 align:start position:0% going to lie I think we can be a bit more<00:09:53.600> ambitious<00:09:54.519> frankly<00:09:55.519> we're<00:09:55.720> not 00:09:55.949 --> 00:09:55.959 align:start position:0% more ambitious frankly we're not 00:09:55.959 --> 00:09:59.430 align:start position:0% more ambitious frankly we're not protocol<00:09:56.519> developers<00:09:57.519> I<00:09:57.680> was<00:09:57.880> one<00:09:58.200> previously 00:09:59.430 --> 00:09:59.440 align:start position:0% protocol developers I was one previously 00:09:59.440 --> 00:10:02.470 align:start position:0% protocol developers I was one previously we<00:09:59.519> don't<00:09:59.720> need<00:09:59.959> to<00:10:00.160> go<00:10:00.399> slow<00:10:01.200> we<00:10:01.320> can<00:10:01.519> go<00:10:01.880> fast 00:10:02.470 --> 00:10:02.480 align:start position:0% we don't need to go slow we can go fast 00:10:02.480 --> 00:10:04.920 align:start position:0% we don't need to go slow we can go fast we<00:10:02.600> can