WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:15.950 align:start position:0% [Music] 00:00:15.950 --> 00:00:15.960 align:start position:0% 00:00:15.960 --> 00:00:18.830 align:start position:0% good<00:00:16.619> okay 00:00:18.830 --> 00:00:18.840 align:start position:0% good okay 00:00:18.840 --> 00:00:20.450 align:start position:0% good okay so 00:00:20.450 --> 00:00:20.460 align:start position:0% so 00:00:20.460 --> 00:00:23.929 align:start position:0% so uh<00:00:21.060> my<00:00:21.300> name<00:00:21.420> is<00:00:21.660> uh<00:00:22.199> well<00:00:22.920> my<00:00:23.279> name<00:00:23.340> is<00:00:23.400> Makoto 00:00:23.929 --> 00:00:23.939 align:start position:0% uh my name is uh well my name is Makoto 00:00:23.939 --> 00:00:27.650 align:start position:0% uh my name is uh well my name is Makoto by<00:00:24.180> ens<00:00:24.900> is<00:00:25.740> my<00:00:25.980> talking<00:00:26.160> dog<00:00:26.460> is<00:00:26.640> how<00:00:27.539> many 00:00:27.650 --> 00:00:27.660 align:start position:0% by ens is my talking dog is how many 00:00:27.660 --> 00:00:30.349 align:start position:0% by ens is my talking dog is how many people<00:00:27.779> got<00:00:28.080> this<00:00:28.500> swag<00:00:29.099> things 00:00:30.349 --> 00:00:30.359 align:start position:0% people got this swag things 00:00:30.359 --> 00:00:32.990 align:start position:0% people got this swag things great<00:00:31.140> okay<00:00:31.619> so<00:00:32.160> probably<00:00:32.399> support<00:00:32.759> someone 00:00:32.990 --> 00:00:33.000 align:start position:0% great okay so probably support someone 00:00:33.000 --> 00:00:35.090 align:start position:0% great okay so probably support someone with<00:00:33.300> you<00:00:33.420> I<00:00:33.600> was<00:00:33.660> a<00:00:33.840> man<00:00:34.020> behind<00:00:34.500> you<00:00:35.040> know 00:00:35.090 --> 00:00:35.100 align:start position:0% with you I was a man behind you know 00:00:35.100 --> 00:00:38.030 align:start position:0% with you I was a man behind you know between<00:00:35.340> the<00:00:35.820> nice<00:00:36.780> swag<00:00:37.140> and<00:00:37.320> you<00:00:37.559> know<00:00:37.680> that 00:00:38.030 --> 00:00:38.040 align:start position:0% between the nice swag and you know that 00:00:38.040 --> 00:00:39.590 align:start position:0% between the nice swag and you know that you<00:00:38.280> so<00:00:38.520> like<00:00:38.700> you<00:00:38.820> know<00:00:38.940> just<00:00:39.120> making<00:00:39.300> sure 00:00:39.590 --> 00:00:39.600 align:start position:0% you so like you know just making sure 00:00:39.600 --> 00:00:41.090 align:start position:0% you so like you know just making sure you<00:00:39.780> guys<00:00:39.899> are<00:00:40.079> cute<00:00:40.260> alcohol<00:00:40.500> and<00:00:40.739> all<00:00:40.920> that 00:00:41.090 --> 00:00:41.100 align:start position:0% you guys are cute alcohol and all that 00:00:41.100 --> 00:00:44.510 align:start position:0% you guys are cute alcohol and all that stuff<00:00:41.219> but<00:00:41.579> uh<00:00:42.300> I'm<00:00:42.719> hope<00:00:42.899> hoping<00:00:43.440> that<00:00:43.739> now<00:00:44.280> I 00:00:44.510 --> 00:00:44.520 align:start position:0% stuff but uh I'm hope hoping that now I 00:00:44.520 --> 00:00:46.190 align:start position:0% stuff but uh I'm hope hoping that now I don't<00:00:44.579> really<00:00:44.760> have<00:00:45.000> to<00:00:45.120> explain<00:00:45.540> what<00:00:46.020> the 00:00:46.190 --> 00:00:46.200 align:start position:0% don't really have to explain what the 00:00:46.200 --> 00:00:48.950 align:start position:0% don't really have to explain what the ens<00:00:46.920> is<00:00:47.160> so<00:00:47.579> it's<00:00:48.120> a<00:00:48.300> basically<00:00:48.539> Webster 00:00:48.950 --> 00:00:48.960 align:start position:0% ens is so it's a basically Webster 00:00:48.960 --> 00:00:51.770 align:start position:0% ens is so it's a basically Webster username<00:00:49.500> whether<00:00:49.920> you<00:00:50.160> go<00:00:50.280> to<00:00:50.460> uh<00:00:50.940> Co-op<00:00:51.480> or 00:00:51.770 --> 00:00:51.780 align:start position:0% username whether you go to uh Co-op or 00:00:51.780 --> 00:00:55.010 align:start position:0% username whether you go to uh Co-op or Instagram<00:00:52.020> or<00:00:52.559> openc<00:00:52.980> or<00:00:53.520> easy<00:00:54.000> XYZ<00:00:54.539> it's<00:00:54.899> all 00:00:55.010 --> 00:00:55.020 align:start position:0% Instagram or openc or easy XYZ it's all 00:00:55.020 --> 00:00:59.209 align:start position:0% Instagram or openc or easy XYZ it's all my<00:00:55.260> token.is<00:00:55.980> so<00:00:56.520> that's<00:00:56.699> my<00:00:57.059> name<00:00:57.320> and<00:00:58.320> so 00:00:59.209 --> 00:00:59.219 align:start position:0% my token.is so that's my name and so 00:00:59.219 --> 00:01:01.850 align:start position:0% my token.is so that's my name and so today<00:00:59.460> I<00:00:59.820> think<00:00:59.940> this<00:01:00.420> this<00:01:00.840> room<00:01:01.140> is<00:01:01.379> mostly 00:01:01.850 --> 00:01:01.860 align:start position:0% today I think this this room is mostly 00:01:01.860 --> 00:01:05.630 align:start position:0% today I think this this room is mostly in<00:01:02.340> a<00:01:02.579> theme<00:01:02.699> of<00:01:02.940> a<00:01:03.180> L2<00:01:03.899> track<00:01:04.260> so<00:01:04.920> we<00:01:05.339> are<00:01:05.519> going 00:01:05.630 --> 00:01:05.640 align:start position:0% in a theme of a L2 track so we are going 00:01:05.640 --> 00:01:07.370 align:start position:0% in a theme of a L2 track so we are going to<00:01:05.760> talk<00:01:06.000> about 00:01:07.370 --> 00:01:07.380 align:start position:0% to talk about 00:01:07.380 --> 00:01:10.969 align:start position:0% to talk about kind<00:01:07.860> of<00:01:08.100> L2<00:01:08.520> of<00:01:09.119> gen<00:01:09.420> interchange<00:01:10.020> strategy 00:01:10.969 --> 00:01:10.979 align:start position:0% kind of L2 of gen interchange strategy 00:01:10.979 --> 00:01:14.810 align:start position:0% kind of L2 of gen interchange strategy on<00:01:11.280> what<00:01:11.880> ens<00:01:12.360> is<00:01:12.540> doing<00:01:12.720> and<00:01:13.619> we<00:01:14.280> are<00:01:14.520> actually 00:01:14.810 --> 00:01:14.820 align:start position:0% on what ens is doing and we are actually 00:01:14.820 --> 00:01:17.630 align:start position:0% on what ens is doing and we are actually been<00:01:15.240> doing<00:01:15.479> since<00:01:15.780> kind<00:01:16.080> of<00:01:16.260> 2020<00:01:16.740> and<00:01:17.280> there 00:01:17.630 --> 00:01:17.640 align:start position:0% been doing since kind of 2020 and there 00:01:17.640 --> 00:01:22.070 align:start position:0% been doing since kind of 2020 and there was<00:01:17.820> a<00:01:17.939> lot<00:01:18.060> of<00:01:18.240> talk<00:01:19.080> and<00:01:19.939> work<00:01:20.939> going<00:01:21.240> on<00:01:21.479> but 00:01:22.070 --> 00:01:22.080 align:start position:0% was a lot of talk and work going on but 00:01:22.080 --> 00:01:24.109 align:start position:0% was a lot of talk and work going on but people<00:01:22.320> are<00:01:22.560> not<00:01:22.740> quite<00:01:22.979> sure<00:01:23.159> where<00:01:23.520> we<00:01:23.939> are 00:01:24.109 --> 00:01:24.119 align:start position:0% people are not quite sure where we are 00:01:24.119 --> 00:01:27.230 align:start position:0% people are not quite sure where we are at<00:01:24.299> right<00:01:24.600> now<00:01:24.840> and<00:01:25.439> it's<00:01:26.280> actually<00:01:26.460> some<00:01:27.060> of 00:01:27.230 --> 00:01:27.240 align:start position:0% at right now and it's actually some of 00:01:27.240 --> 00:01:29.870 align:start position:0% at right now and it's actually some of the<00:01:27.420> feature<00:01:27.900> it's<00:01:28.619> two<00:01:28.860> and<00:01:29.100> a<00:01:29.220> halfway<00:01:29.520> of 00:01:29.870 --> 00:01:29.880 align:start position:0% the feature it's two and a halfway of 00:01:29.880 --> 00:01:31.609 align:start position:0% the feature it's two and a halfway of the<00:01:30.000> road<00:01:30.240> map<00:01:30.479> but<00:01:30.840> it's<00:01:31.020> some<00:01:31.200> of<00:01:31.320> them<00:01:31.439> are 00:01:31.609 --> 00:01:31.619 align:start position:0% the road map but it's some of them are 00:01:31.619 --> 00:01:33.649 align:start position:0% the road map but it's some of them are already<00:01:31.799> available<00:01:32.040> so<00:01:32.820> first<00:01:33.000> I<00:01:33.360> was<00:01:33.540> going 00:01:33.649 --> 00:01:33.659 align:start position:0% already available so first I was going 00:01:33.659 --> 00:01:36.230 align:start position:0% already available so first I was going to<00:01:33.840> explain<00:01:34.020> what<00:01:34.860> kind<00:01:35.040> of<00:01:35.159> the<00:01:35.579> Cross<00:01:36.000> chain 00:01:36.230 --> 00:01:36.240 align:start position:0% to explain what kind of the Cross chain 00:01:36.240 --> 00:01:38.990 align:start position:0% to explain what kind of the Cross chain example<00:01:36.720> already<00:01:37.320> available<00:01:37.799> to<00:01:38.400> you<00:01:38.520> so<00:01:38.820> this 00:01:38.990 --> 00:01:39.000 align:start position:0% example already available to you so this 00:01:39.000 --> 00:01:40.249 align:start position:0% example already available to you so this one<00:01:39.119> doesn't<00:01:39.360> really<00:01:39.659> require<00:01:39.900> any 00:01:40.249 --> 00:01:40.259 align:start position:0% one doesn't really require any 00:01:40.259 --> 00:01:41.210 align:start position:0% one doesn't really require any technology 00:01:41.210 --> 00:01:41.220 align:start position:0% technology 00:01:41.220 --> 00:01:44.090 align:start position:0% technology technical<00:01:41.939> knowledge<00:01:42.420> then<00:01:43.200> I<00:01:43.500> go<00:01:43.680> a<00:01:43.920> bit 00:01:44.090 --> 00:01:44.100 align:start position:0% technical knowledge then I go a bit 00:01:44.100 --> 00:01:46.850 align:start position:0% technical knowledge then I go a bit deeper<00:01:45.060> to<00:01:45.180> the<00:01:45.299> underhood<00:01:45.960> definitely<00:01:46.619> so 00:01:46.850 --> 00:01:46.860 align:start position:0% deeper to the underhood definitely so 00:01:46.860 --> 00:01:48.649 align:start position:0% deeper to the underhood definitely so probably<00:01:46.979> I<00:01:47.280> I<00:01:47.460> show<00:01:47.640> a<00:01:47.820> bit<00:01:47.939> of<00:01:48.119> code<00:01:48.299> so 00:01:48.649 --> 00:01:48.659 align:start position:0% probably I I show a bit of code so 00:01:48.659 --> 00:01:51.230 align:start position:0% probably I I show a bit of code so mostly<00:01:49.439> for<00:01:49.619> devs<00:01:50.040> and<00:01:50.280> therefore<00:01:50.640> what's 00:01:51.230 --> 00:01:51.240 align:start position:0% mostly for devs and therefore what's 00:01:51.240 --> 00:01:53.450 align:start position:0% mostly for devs and therefore what's next<00:01:51.540> section<00:01:51.840> is<00:01:52.320> yeah<00:01:52.740> what's<00:01:53.220> going<00:01:53.399> to 00:01:53.450 --> 00:01:53.460 align:start position:0% next section is yeah what's going to 00:01:53.460 --> 00:01:55.069 align:start position:0% next section is yeah what's going to happen<00:01:53.579> in<00:01:53.820> the<00:01:54.000> probably<00:01:54.360> a<00:01:54.600> bit<00:01:54.720> technical 00:01:55.069 --> 00:01:55.079 align:start position:0% happen in the probably a bit technical 00:01:55.079 --> 00:01:59.870 align:start position:0% happen in the probably a bit technical okay<00:01:55.860> so<00:01:56.540> uh<00:01:57.540> for<00:01:58.259> some<00:01:58.439> of<00:01:58.619> you<00:01:58.799> may<00:01:59.159> know<00:01:59.399> uh 00:01:59.870 --> 00:01:59.880 align:start position:0% okay so uh for some of you may know uh 00:01:59.880 --> 00:02:02.870 align:start position:0% okay so uh for some of you may know uh coinbase<00:02:00.360> I<00:02:00.960> want<00:02:01.259> the<00:02:01.680> biggest<00:02:01.799> exchange<00:02:02.340> I 00:02:02.870 --> 00:02:02.880 align:start position:0% coinbase I want the biggest exchange I 00:02:02.880 --> 00:02:05.030 align:start position:0% coinbase I want the biggest exchange I recently<00:02:03.299> announced<00:02:03.780> that<00:02:04.020> they<00:02:04.320> decide<00:02:04.860> to 00:02:05.030 --> 00:02:05.040 align:start position:0% recently announced that they decide to 00:02:05.040 --> 00:02:07.910 align:start position:0% recently announced that they decide to issue<00:02:05.460> subdomain<00:02:06.060> to<00:02:06.240> all<00:02:06.719> the<00:02:07.020> users<00:02:07.560> I<00:02:07.799> think 00:02:07.910 --> 00:02:07.920 align:start position:0% issue subdomain to all the users I think 00:02:07.920 --> 00:02:09.650 align:start position:0% issue subdomain to all the users I think there's<00:02:08.039> a<00:02:08.280> couple<00:02:08.340> from<00:02:08.640> the<00:02:08.759> coinbase<00:02:09.179> I'm 00:02:09.650 --> 00:02:09.660 align:start position:0% there's a couple from the coinbase I'm 00:02:09.660 --> 00:02:13.190 align:start position:0% there's a couple from the coinbase I'm gonna<00:02:09.840> raise<00:02:09.959> the<00:02:10.200> hands<00:02:10.440> okay<00:02:10.979> thank<00:02:11.400> you 00:02:13.190 --> 00:02:13.200 align:start position:0% gonna raise the hands okay thank you 00:02:13.200 --> 00:02:15.949 align:start position:0% gonna raise the hands okay thank you and<00:02:14.040> it's<00:02:14.520> great<00:02:14.819> because<00:02:15.120> like<00:02:15.300> whenever<00:02:15.720> you 00:02:15.949 --> 00:02:15.959 align:start position:0% and it's great because like whenever you 00:02:15.959 --> 00:02:17.869 align:start position:0% and it's great because like whenever you go<00:02:16.140> to<00:02:16.319> like<00:02:16.500> you<00:02:16.739> know<00:02:16.860> exchange<00:02:17.520> that<00:02:17.700> you 00:02:17.869 --> 00:02:17.879 align:start position:0% go to like you know exchange that you 00:02:17.879 --> 00:02:21.170 align:start position:0% go to like you know exchange that you change<00:02:18.120> uh<00:02:18.900> you<00:02:19.200> get<00:02:19.319> your<00:02:19.620> fiatu<00:02:20.580> coinbase 00:02:21.170 --> 00:02:21.180 align:start position:0% change uh you get your fiatu coinbase 00:02:21.180 --> 00:02:23.390 align:start position:0% change uh you get your fiatu coinbase then<00:02:21.660> you<00:02:21.840> will<00:02:22.080> not<00:02:22.319> move<00:02:22.620> into<00:02:22.800> somewhere 00:02:23.390 --> 00:02:23.400 align:start position:0% then you will not move into somewhere 00:02:23.400 --> 00:02:25.910 align:start position:0% then you will not move into somewhere for<00:02:23.940> the<00:02:24.120> D5<00:02:24.420> then<00:02:24.840> like<00:02:25.080> passing<00:02:25.500> struggle<00:02:25.860> is 00:02:25.910 --> 00:02:25.920 align:start position:0% for the D5 then like passing struggle is 00:02:25.920 --> 00:02:28.430 align:start position:0% for the D5 then like passing struggle is like<00:02:26.099> oh<00:02:26.280> what's<00:02:27.120> how<00:02:27.540> to<00:02:27.660> send<00:02:27.900> to<00:02:28.080> you<00:02:28.379> know 00:02:28.430 --> 00:02:28.440 align:start position:0% like oh what's how to send to you know 00:02:28.440 --> 00:02:30.350 align:start position:0% like oh what's how to send to you know same<00:02:28.860> address<00:02:29.099> in<00:02:29.400> there<00:02:29.520> I<00:02:29.879> think<00:02:30.000> it's<00:02:30.120> great 00:02:30.350 --> 00:02:30.360 align:start position:0% same address in there I think it's great 00:02:30.360 --> 00:02:32.510 align:start position:0% same address in there I think it's great that<00:02:30.599> it's<00:02:30.780> been<00:02:31.020> uh<00:02:31.739> ens<00:02:32.160> is<00:02:32.340> available 00:02:32.510 --> 00:02:32.520 align:start position:0% that it's been uh ens is available 00:02:32.520 --> 00:02:35.930 align:start position:0% that it's been uh ens is available available<00:02:33.420> from<00:02:34.080> the<00:02:34.379> kind<00:02:34.620> of<00:02:34.800> assurance<00:02:35.220> a 00:02:35.930 --> 00:02:35.940 align:start position:0% available from the kind of assurance a 00:02:35.940 --> 00:02:39.010 align:start position:0% available from the kind of assurance a new<00:02:36.120> user<00:02:36.420> got<00:02:36.660> on<00:02:36.900> board<00:02:37.020> with<00:02:37.260> crypto<00:02:37.680> and<00:02:38.220> uh 00:02:39.010 --> 00:02:39.020 align:start position:0% new user got on board with crypto and uh 00:02:39.020 --> 00:02:41.290 align:start position:0% new user got on board with crypto and uh I<00:02:40.020> got<00:02:40.140> you<00:02:40.379> know<00:02:40.500> when 00:02:41.290 --> 00:02:41.300 align:start position:0% I got you know when 00:02:41.300 --> 00:02:43.670 align:start position:0% I got you know when makoto.cb.id<00:02:42.300> because<00:02:42.720> matokeo<00:02:43.319> is<00:02:43.500> already 00:02:43.670 --> 00:02:43.680 align:start position:0% makoto.cb.id because matokeo is already 00:02:43.680 --> 00:02:46.130 align:start position:0% makoto.cb.id because matokeo is already not<00:02:43.980> available<00:02:44.360> unfortunately<00:02:45.360> but<00:02:45.840> like<00:02:46.019> if 00:02:46.130 --> 00:02:46.140 align:start position:0% not available unfortunately but like if 00:02:46.140 --> 00:02:49.190 align:start position:0% not available unfortunately but like if you<00:02:46.319> go<00:02:46.440> to<00:02:46.560> your<00:02:46.739> in<00:02:47.400> a<00:02:47.640> profile<00:02:47.940> page<00:02:48.300> and 00:02:49.190 --> 00:02:49.200 align:start position:0% you go to your in a profile page and 00:02:49.200 --> 00:02:52.089 align:start position:0% you go to your in a profile page and another<00:02:49.560> thing<00:02:49.860> is<00:02:50.040> so<00:02:50.459> coinbase<00:02:51.000> has<00:02:51.360> I<00:02:51.900> think 00:02:52.089 --> 00:02:52.099 align:start position:0% another thing is so coinbase has I think 00:02:52.099 --> 00:02:55.790 align:start position:0% another thing is so coinbase has I think coinbase.ed<00:02:53.099> eth<00:02:53.700> but<00:02:54.360> they<00:02:54.599> chose<00:02:54.840> uh<00:02:55.080> CB<00:02:55.440> dot 00:02:55.790 --> 00:02:55.800 align:start position:0% coinbase.ed eth but they chose uh CB dot 00:02:55.800 --> 00:02:57.770 align:start position:0% coinbase.ed eth but they chose uh CB dot ID<00:02:55.920> firstly<00:02:56.580> because<00:02:56.760> it's<00:02:57.000> a<00:02:57.180> lot<00:02:57.300> shorter 00:02:57.770 --> 00:02:57.780 align:start position:0% ID firstly because it's a lot shorter 00:02:57.780 --> 00:03:01.790 align:start position:0% ID firstly because it's a lot shorter and<00:02:58.440> another<00:02:59.220> thing<00:02:59.580> is<00:02:59.819> uh<00:03:00.720> ens<00:03:01.200> is<00:03:01.379> just<00:03:01.560> not 00:03:01.790 --> 00:03:01.800 align:start position:0% and another thing is uh ens is just not 00:03:01.800 --> 00:03:03.949 align:start position:0% and another thing is uh ens is just not just<00:03:01.980> about<00:03:02.160> dot<00:03:02.640> eth<00:03:02.940> you<00:03:03.660> can<00:03:03.780> actually 00:03:03.949 --> 00:03:03.959 align:start position:0% just about dot eth you can actually 00:03:03.959 --> 00:03:06.650 align:start position:0% just about dot eth you can actually import<00:03:04.379> the<00:03:04.800> order<00:03:04.980> your<00:03:05.400> Internet<00:03:05.580> domain<00:03:06.180> as 00:03:06.650 --> 00:03:06.660 align:start position:0% import the order your Internet domain as 00:03:06.660 --> 00:03:09.110 align:start position:0% import the order your Internet domain as a<00:03:06.900> ethereum<00:03:07.379> name<00:03:07.560> so<00:03:07.739> like<00:03:07.920> origin<00:03:08.640> wallet 00:03:09.110 --> 00:03:09.120 align:start position:0% a ethereum name so like origin wallet 00:03:09.120 --> 00:03:11.809 align:start position:0% a ethereum name so like origin wallet has<00:03:09.300> a<00:03:09.480> DOT<00:03:09.780> XYZ<00:03:10.200> and<00:03:10.620> you<00:03:10.739> can<00:03:10.920> make<00:03:11.220> or 00:03:11.809 --> 00:03:11.819 align:start position:0% has a DOT XYZ and you can make or 00:03:11.819 --> 00:03:13.850 align:start position:0% has a DOT XYZ and you can make or comment<00:03:12.180> the<00:03:12.360> stuff<00:03:12.540> so<00:03:12.780> they<00:03:12.900> decide<00:03:13.140> to<00:03:13.680> use 00:03:13.850 --> 00:03:13.860 align:start position:0% comment the stuff so they decide to use 00:03:13.860 --> 00:03:17.750 align:start position:0% comment the stuff so they decide to use cb.id<00:03:14.640> to<00:03:15.300> import<00:03:15.540> the<00:03:15.840> DNS<00:03:16.260> to<00:03:16.739> kind<00:03:17.220> of<00:03:17.400> ens 00:03:17.750 --> 00:03:17.760 align:start position:0% cb.id to import the DNS to kind of ens 00:03:17.760 --> 00:03:20.210 align:start position:0% cb.id to import the DNS to kind of ens world<00:03:18.000> then<00:03:18.480> decided<00:03:18.959> to<00:03:19.080> issue<00:03:19.560> subdomains 00:03:20.210 --> 00:03:20.220 align:start position:0% world then decided to issue subdomains 00:03:20.220 --> 00:03:24.550 align:start position:0% world then decided to issue subdomains so<00:03:20.700> once<00:03:21.060> it's<00:03:21.180> done<00:03:21.420> you<00:03:22.319> can<00:03:22.440> see<00:03:23.120> my<00:03:24.120> Q 00:03:24.550 --> 00:03:24.560 align:start position:0% so once it's done you can see my Q 00:03:24.560 --> 00:03:29.930 align:start position:0% so once it's done you can see my Q handwritten<00:03:25.560> Avatar<00:03:26.099> and<00:03:27.200> yeah<00:03:28.280> website<00:03:29.280> and 00:03:29.930 --> 00:03:29.940 align:start position:0% handwritten Avatar and yeah website and 00:03:29.940 --> 00:03:32.030 align:start position:0% handwritten Avatar and yeah website and the<00:03:30.120> email<00:03:30.300> address<00:03:30.599> and<00:03:31.379> if<00:03:31.560> you<00:03:31.680> look<00:03:31.860> into 00:03:32.030 --> 00:03:32.040 align:start position:0% the email address and if you look into 00:03:32.040 --> 00:03:34.850 align:start position:0% the email address and if you look into this<00:03:32.599> our<00:03:33.599> ens<00:03:34.080> manager<00:03:34.440> you<00:03:34.620> can<00:03:34.739> actually 00:03:34.850 --> 00:03:34.860 align:start position:0% this our ens manager you can actually 00:03:34.860 --> 00:03:37.130 align:start position:0% this our ens manager you can actually see<00:03:35.040> the<00:03:35.220> same<00:03:35.400> thing<00:03:35.519> so<00:03:36.060> it's<00:03:36.239> the<00:03:36.599> data 00:03:37.130 --> 00:03:37.140 align:start position:0% see the same thing so it's the data 00:03:37.140 --> 00:03:39.410 align:start position:0% see the same thing so it's the data which<00:03:37.739> is<00:03:37.920> stored<00:03:38.340> in<00:03:38.459> I<00:03:38.879> think<00:03:38.940> it's<00:03:39.060> in<00:03:39.239> a 00:03:39.410 --> 00:03:39.420 align:start position:0% which is stored in I think it's in a 00:03:39.420 --> 00:03:41.449 align:start position:0% which is stored in I think it's in a database<00:03:39.599> in<00:03:39.840> coinbase<00:03:40.319> it's<00:03:40.860> processes 00:03:41.449 --> 00:03:41.459 align:start position:0% database in coinbase it's processes 00:03:41.459 --> 00:03:44.449 align:start position:0% database in coinbase it's processes route<00:03:41.819> uh<00:03:42.780> basically<00:03:43.140> same<00:03:43.500> layer<00:03:44.099> one<00:03:44.220> so 00:03:44.449 --> 00:03:44.459 align:start position:0% route uh basically same layer one so 00:03:44.459 --> 00:03:47.330 align:start position:0% route uh basically same layer one so that<00:03:44.700> any<00:03:45.180> doubts<00:03:45.720> or<00:03:45.840> like<00:03:46.200> a 00:03:47.330 --> 00:03:47.340 align:start position:0% that any doubts or like a 00:03:47.340 --> 00:03:49.789 align:start position:0% that any doubts or like a well<00:03:47.940> that<00:03:48.180> can<00:03:48.480> actually<00:03:48.720> access<00:03:48.959> the<00:03:49.379> data 00:03:49.789 --> 00:03:49.799 align:start position:0% well that can actually access the data 00:03:49.799 --> 00:03:52.130 align:start position:0% well that can actually access the data and<00:03:50.220> the<00:03:50.400> great<00:03:50.519> thing<00:03:50.760> is<00:03:50.940> uh<00:03:51.420> the<00:03:51.840> user 00:03:52.130 --> 00:03:52.140 align:start position:0% and the great thing is uh the user 00:03:52.140 --> 00:03:55.369 align:start position:0% and the great thing is uh the user hasn't<00:03:52.560> paid<00:03:52.920> any<00:03:53.220> single<00:03:53.519> gas 00:03:55.369 --> 00:03:55.379 align:start position:0% hasn't paid any single gas 00:03:55.379 --> 00:03:57.830 align:start position:0% hasn't paid any single gas and<00:03:55.739> another<00:03:55.920> exam<00:03:56.400> interesting<00:03:56.879> example<00:03:57.480> so 00:03:57.830 --> 00:03:57.840 align:start position:0% and another exam interesting example so 00:03:57.840 --> 00:04:00.470 align:start position:0% and another exam interesting example so I<00:03:58.080> think<00:03:58.260> coinbase<00:03:58.680> cases<00:03:59.159> was<00:03:59.459> in<00:03:59.760> a<00:04:00.299> company 00:04:00.470 --> 00:04:00.480 align:start position:0% I think coinbase cases was in a company 00:04:00.480 --> 00:04:03.949 align:start position:0% I think coinbase cases was in a company of<00:04:00.780> chain<00:04:01.019> in<00:04:01.379> the<00:04:01.500> database<00:04:02.060> so<00:04:03.060> lens<00:04:03.420> is 00:04:03.949 --> 00:04:03.959 align:start position:0% of chain in the database so lens is 00:04:03.959 --> 00:04:07.610 align:start position:0% of chain in the database so lens is another<00:04:04.140> kind<00:04:04.560> of<00:04:05.220> uh<00:04:05.459> web3<00:04:06.319> social<00:04:07.319> network 00:04:07.610 --> 00:04:07.620 align:start position:0% another kind of uh web3 social network 00:04:07.620 --> 00:04:10.490 align:start position:0% another kind of uh web3 social network which<00:04:08.280> provide<00:04:08.760> the<00:04:08.879> user<00:04:09.180> profile<00:04:09.420> and<00:04:10.200> how 00:04:10.490 --> 00:04:10.500 align:start position:0% which provide the user profile and how 00:04:10.500 --> 00:04:13.070 align:start position:0% which provide the user profile and how many<00:04:10.620> people<00:04:10.739> have<00:04:10.980> lenses<00:04:11.459> profile<00:04:12.120> okay 00:04:13.070 --> 00:04:13.080 align:start position:0% many people have lenses profile okay 00:04:13.080 --> 00:04:17.710 align:start position:0% many people have lenses profile okay maybe<00:04:13.920> half<00:04:14.159> of<00:04:14.340> it<00:04:14.519> and<00:04:15.120> so<00:04:15.420> this 00:04:17.710 --> 00:04:17.720 align:start position:0% maybe half of it and so this 00:04:17.720 --> 00:04:20.750 align:start position:0% maybe half of it and so this lens<00:04:18.720> actually<00:04:19.019> have<00:04:19.260> a<00:04:19.440> ens<00:04:19.859> Association 00:04:20.750 --> 00:04:20.760 align:start position:0% lens actually have a ens Association 00:04:20.760 --> 00:04:23.570 align:start position:0% lens actually have a ens Association address<00:04:21.239> Associated<00:04:21.900> and<00:04:22.800> something<00:04:23.220> you 00:04:23.570 --> 00:04:23.580 align:start position:0% address Associated and something you 00:04:23.580 --> 00:04:25.670 align:start position:0% address Associated and something you might<00:04:23.759> not<00:04:23.940> know<00:04:24.180> is<00:04:24.600> uh<00:04:25.259> it's<00:04:25.560> actually 00:04:25.670 --> 00:04:25.680 align:start position:0% might not know is uh it's actually 00:04:25.680 --> 00:04:28.850 align:start position:0% might not know is uh it's actually that's<00:04:26.160> also<00:04:26.400> a<00:04:26.639> proxy<00:04:27.060> to<00:04:27.300> the<00:04:27.720> uh 00:04:28.850 --> 00:04:28.860 align:start position:0% that's also a proxy to the uh 00:04:28.860 --> 00:04:32.270 align:start position:0% that's also a proxy to the uh you<00:04:29.400> say<00:04:29.639> I'm<00:04:29.820> L1<00:04:30.240> after<00:04:30.540> ens<00:04:31.199> and<00:04:31.740> on<00:04:31.919> layer 00:04:32.270 --> 00:04:32.280 align:start position:0% you say I'm L1 after ens and on layer 00:04:32.280 --> 00:04:34.490 align:start position:0% you say I'm L1 after ens and on layer one<00:04:32.460> so<00:04:32.699> if<00:04:32.820> you<00:04:33.000> actually<00:04:33.300> look<00:04:33.540> into<00:04:33.720> it<00:04:34.020> you 00:04:34.490 --> 00:04:34.500 align:start position:0% one so if you actually look into it you 00:04:34.500 --> 00:04:36.710 align:start position:0% one so if you actually look into it you can<00:04:34.620> actually<00:04:34.800> see<00:04:35.160> that<00:04:35.400> on<00:04:35.759> our<00:04:35.940> EMS<00:04:36.360> manager 00:04:36.710 --> 00:04:36.720 align:start position:0% can actually see that on our EMS manager 00:04:36.720 --> 00:04:40.730 align:start position:0% can actually see that on our EMS manager and<00:04:37.199> this<00:04:37.979> is<00:04:38.160> kind<00:04:38.340> of<00:04:38.520> recent<00:04:39.139> uh<00:04:40.139> release 00:04:40.730 --> 00:04:40.740 align:start position:0% and this is kind of recent uh release 00:04:40.740 --> 00:04:43.670 align:start position:0% and this is kind of recent uh release but<00:04:41.160> now<00:04:41.580> uh<00:04:42.000> beta<00:04:42.479> mask<00:04:42.600> supports<00:04:43.380> so<00:04:43.560> that 00:04:43.670 --> 00:04:43.680 align:start position:0% but now uh beta mask supports so that 00:04:43.680 --> 00:04:46.010 align:start position:0% but now uh beta mask supports so that like<00:04:43.919> if<00:04:44.100> you<00:04:44.340> try<00:04:44.759> to<00:04:44.940> send 00:04:46.010 --> 00:04:46.020 align:start position:0% like if you try to send 00:04:46.020 --> 00:04:48.290 align:start position:0% like if you try to send no<00:04:46.440> one<00:04:46.560> really<00:04:46.740> has<00:04:46.979> to<00:04:47.100> send<00:04:47.340> ease<00:04:47.820> to<00:04:47.940> study 00:04:48.290 --> 00:04:48.300 align:start position:0% no one really has to send ease to study 00:04:48.300 --> 00:04:51.290 align:start position:0% no one really has to send ease to study you<00:04:48.660> know<00:04:49.040> if<00:04:50.040> you<00:04:50.160> want<00:04:50.400> to<00:04:50.520> you<00:04:50.940> know<00:04:51.060> you<00:04:51.180> go 00:04:51.290 --> 00:04:51.300 align:start position:0% you know if you want to you know you go 00:04:51.300 --> 00:04:54.110 align:start position:0% you know if you want to you know you go to<00:04:51.919> stanley.lens.xyz<00:04:52.919> uh<00:04:53.759> that<00:04:53.940> that's 00:04:54.110 --> 00:04:54.120 align:start position:0% to stanley.lens.xyz uh that that's 00:04:54.120 --> 00:04:56.870 align:start position:0% to stanley.lens.xyz uh that that's already<00:04:54.300> available<00:04:54.919> and<00:04:55.919> this<00:04:56.639> is<00:04:56.759> another 00:04:56.870 --> 00:04:56.880 align:start position:0% already available and this is another 00:04:56.880 --> 00:05:00.050 align:start position:0% already available and this is another interesting<00:04:57.600> things<00:04:58.199> like<00:04:58.680> so<00:04:58.919> optimism<00:04:59.460> uh 00:05:00.050 --> 00:05:00.060 align:start position:0% interesting things like so optimism uh 00:05:00.060 --> 00:05:02.870 align:start position:0% interesting things like so optimism uh there's<00:05:00.360> some<00:05:01.080> Community<00:05:01.680> user<00:05:02.280> just<00:05:02.460> posted 00:05:02.870 --> 00:05:02.880 align:start position:0% there's some Community user just posted 00:05:02.880 --> 00:05:06.050 align:start position:0% there's some Community user just posted on<00:05:03.120> their<00:05:03.440> our<00:05:04.440> Forum<00:05:04.800> that<00:05:04.979> hey<00:05:05.280> we<00:05:05.520> created<00:05:05.820> a 00:05:06.050 --> 00:05:06.060 align:start position:0% on their our Forum that hey we created a 00:05:06.060 --> 00:05:08.450 align:start position:0% on their our Forum that hey we created a name<00:05:06.180> service<00:05:06.419> and<00:05:07.259> they<00:05:07.680> actually<00:05:07.919> just 00:05:08.450 --> 00:05:08.460 align:start position:0% name service and they actually just 00:05:08.460 --> 00:05:11.030 align:start position:0% name service and they actually just spoke<00:05:08.759> the<00:05:09.120> uh<00:05:09.540> what<00:05:10.139> we<00:05:10.259> are<00:05:10.380> doing<00:05:10.560> and<00:05:10.800> they 00:05:11.030 --> 00:05:11.040 align:start position:0% spoke the uh what we are doing and they 00:05:11.040 --> 00:05:13.490 align:start position:0% spoke the uh what we are doing and they create<00:05:11.280> a<00:05:11.520> kind<00:05:11.699> of<00:05:11.820> nft<00:05:12.060> and<00:05:12.780> they<00:05:12.960> decided<00:05:13.440> to 00:05:13.490 --> 00:05:13.500 align:start position:0% create a kind of nft and they decided to 00:05:13.500 --> 00:05:16.070 align:start position:0% create a kind of nft and they decided to issue<00:05:13.919> some<00:05:14.100> domain<00:05:14.460> on<00:05:14.820> their<00:05:15.060> nft<00:05:15.479> and<00:05:15.840> it's 00:05:16.070 --> 00:05:16.080 align:start position:0% issue some domain on their nft and it's 00:05:16.080 --> 00:05:18.350 align:start position:0% issue some domain on their nft and it's actually<00:05:16.259> available<00:05:16.560> on<00:05:16.979> optimism<00:05:17.699> which<00:05:18.180> I 00:05:18.350 --> 00:05:18.360 align:start position:0% actually available on optimism which I 00:05:18.360 --> 00:05:20.150 align:start position:0% actually available on optimism which I didn't<00:05:18.600> even<00:05:18.960> know<00:05:19.199> until<00:05:19.320> he<00:05:19.620> posted<00:05:19.919> which 00:05:20.150 --> 00:05:20.160 align:start position:0% didn't even know until he posted which 00:05:20.160 --> 00:05:23.270 align:start position:0% didn't even know until he posted which was<00:05:20.340> kind<00:05:20.580> of<00:05:20.759> crazy<00:05:21.240> and 00:05:23.270 --> 00:05:23.280 align:start position:0% was kind of crazy and 00:05:23.280 --> 00:05:26.510 align:start position:0% was kind of crazy and I<00:05:23.880> do<00:05:24.060> explain<00:05:24.380> there's<00:05:25.380> some<00:05:25.620> Nuance<00:05:26.100> on<00:05:26.400> the 00:05:26.510 --> 00:05:26.520 align:start position:0% I do explain there's some Nuance on the 00:05:26.520 --> 00:05:29.390 align:start position:0% I do explain there's some Nuance on the difference<00:05:26.699> on<00:05:27.120> how<00:05:27.780> you<00:05:27.960> do<00:05:28.199> she's<00:05:28.979> doing<00:05:29.220> and 00:05:29.390 --> 00:05:29.400 align:start position:0% difference on how you do she's doing and 00:05:29.400 --> 00:05:32.749 align:start position:0% difference on how you do she's doing and that<00:05:29.639> what<00:05:29.880> we<00:05:30.120> could<00:05:30.240> do<00:05:30.479> in<00:05:31.080> uh<00:05:31.860> next<00:05:32.460> chapter 00:05:32.749 --> 00:05:32.759 align:start position:0% that what we could do in uh next chapter 00:05:32.759 --> 00:05:35.450 align:start position:0% that what we could do in uh next chapter and<00:05:33.240> this<00:05:33.660> is<00:05:33.780> a<00:05:34.080> really<00:05:34.259> really<00:05:34.500> crazy<00:05:35.100> thing 00:05:35.450 --> 00:05:35.460 align:start position:0% and this is a really really crazy thing 00:05:35.460 --> 00:05:37.550 align:start position:0% and this is a really really crazy thing is<00:05:35.639> like<00:05:35.880> so<00:05:36.240> we<00:05:36.419> I'm<00:05:36.660> saying<00:05:36.900> like<00:05:37.080> off<00:05:37.259> chain 00:05:37.550 --> 00:05:37.560 align:start position:0% is like so we I'm saying like off chain 00:05:37.560 --> 00:05:40.010 align:start position:0% is like so we I'm saying like off chain which<00:05:38.100> can<00:05:38.280> be<00:05:38.460> anything<00:05:38.759> so<00:05:39.360> I<00:05:39.539> showed<00:05:39.900> like 00:05:40.010 --> 00:05:40.020 align:start position:0% which can be anything so I showed like 00:05:40.020 --> 00:05:43.010 align:start position:0% which can be anything so I showed like database<00:05:40.880> example<00:05:41.880> I<00:05:42.180> showed<00:05:42.479> you<00:05:42.539> the<00:05:42.840> lens 00:05:43.010 --> 00:05:43.020 align:start position:0% database example I showed you the lens 00:05:43.020 --> 00:05:45.110 align:start position:0% database example I showed you the lens is<00:05:43.259> basically<00:05:43.560> the<00:05:43.680> polygon<00:05:44.160> other<00:05:44.580> ebm 00:05:45.110 --> 00:05:45.120 align:start position:0% is basically the polygon other ebm 00:05:45.120 --> 00:05:47.689 align:start position:0% is basically the polygon other ebm example<00:05:45.479> this<00:05:46.080> is<00:05:46.320> literally<00:05:46.740> the<00:05:46.979> Google<00:05:47.160> Doc 00:05:47.689 --> 00:05:47.699 align:start position:0% example this is literally the Google Doc 00:05:47.699 --> 00:05:51.230 align:start position:0% example this is literally the Google Doc and<00:05:48.300> someone<00:05:48.600> put<00:05:49.500> that<00:05:49.860> kind<00:05:50.160> of<00:05:50.340> integration 00:05:51.230 --> 00:05:51.240 align:start position:0% and someone put that kind of integration 00:05:51.240 --> 00:05:54.650 align:start position:0% and someone put that kind of integration so<00:05:52.139> that<00:05:52.320> if<00:05:52.620> you<00:05:52.800> type<00:05:53.039> the<00:05:53.400> data<00:05:54.240> into<00:05:54.419> the 00:05:54.650 --> 00:05:54.660 align:start position:0% so that if you type the data into the 00:05:54.660 --> 00:05:56.390 align:start position:0% so that if you type the data into the Google<00:05:54.780> spreadsheet<00:05:55.500> it<00:05:55.740> actually<00:05:55.919> updates 00:05:56.390 --> 00:05:56.400 align:start position:0% Google spreadsheet it actually updates 00:05:56.400 --> 00:05:59.390 align:start position:0% Google spreadsheet it actually updates which<00:05:57.000> is<00:05:57.120> kind<00:05:57.419> of<00:05:57.600> crazy<00:05:58.199> and<00:05:58.560> yeah<00:05:58.919> some<00:05:59.160> I 00:05:59.390 --> 00:05:59.400 align:start position:0% which is kind of crazy and yeah some I 00:05:59.400 --> 00:06:01.010 align:start position:0% which is kind of crazy and yeah some I only<00:05:59.520> got<00:05:59.759> to<00:05:59.940> know<00:06:00.060> because<00:06:00.240> someone<00:06:00.479> tweeted 00:06:01.010 --> 00:06:01.020 align:start position:0% only got to know because someone tweeted 00:06:01.020 --> 00:06:03.290 align:start position:0% only got to know because someone tweeted it<00:06:01.199> so<00:06:01.740> this<00:06:01.979> is<00:06:02.100> kind<00:06:02.460> yeah<00:06:02.820> it's<00:06:03.060> called 00:06:03.290 --> 00:06:03.300 align:start position:0% it so this is kind yeah it's called 00:06:03.300 --> 00:06:07.790 align:start position:0% it so this is kind yeah it's called sheets<00:06:03.720> though<00:06:03.960> is<00:06:04.199> apparently<00:06:05.340> okay<00:06:05.759> so<00:06:06.800> and 00:06:07.790 --> 00:06:07.800 align:start position:0% sheets though is apparently okay so and 00:06:07.800 --> 00:06:10.969 align:start position:0% sheets though is apparently okay so and so<00:06:08.280> current<00:06:08.639> state<00:06:09.000> is<00:06:09.300> so<00:06:09.960> these<00:06:10.500> things 00:06:10.969 --> 00:06:10.979 align:start position:0% so current state is so these things 00:06:10.979 --> 00:06:13.610 align:start position:0% so current state is so these things we've<00:06:11.880> been<00:06:12.060> doing<00:06:12.300> it's<00:06:12.660> not<00:06:12.840> something<00:06:13.139> you 00:06:13.610 --> 00:06:13.620 align:start position:0% we've been doing it's not something you 00:06:13.620 --> 00:06:15.050 align:start position:0% we've been doing it's not something you can<00:06:13.800> uh 00:06:15.050 --> 00:06:15.060 align:start position:0% can uh 00:06:15.060 --> 00:06:18.230 align:start position:0% can uh you<00:06:15.600> can<00:06:15.660> do<00:06:15.840> it<00:06:15.960> without<00:06:16.320> any<00:06:16.800> integration<00:06:17.340> so 00:06:18.230 --> 00:06:18.240 align:start position:0% you can do it without any integration so 00:06:18.240 --> 00:06:21.350 align:start position:0% you can do it without any integration so we<00:06:19.020> actually<00:06:19.380> talked<00:06:20.220> to<00:06:20.340> many<00:06:20.520> partners<00:06:21.120> and 00:06:21.350 --> 00:06:21.360 align:start position:0% we actually talked to many partners and 00:06:21.360 --> 00:06:23.210 align:start position:0% we actually talked to many partners and the<00:06:21.539> integration<00:06:21.900> Partners<00:06:22.440> to<00:06:22.680> integrate 00:06:23.210 --> 00:06:23.220 align:start position:0% the integration Partners to integrate 00:06:23.220 --> 00:06:25.430 align:start position:0% the integration Partners to integrate this<00:06:23.520> thing<00:06:23.639> first<00:06:23.940> so 00:06:25.430 --> 00:06:25.440 align:start position:0% this thing first so 00:06:25.440 --> 00:06:28.210 align:start position:0% this thing first so if<00:06:25.860> you<00:06:25.979> adapt<00:06:26.340> developer<00:06:26.880> if<00:06:27.720> you<00:06:27.840> want<00:06:28.080> to 00:06:28.210 --> 00:06:28.220 align:start position:0% if you adapt developer if you want to 00:06:28.220 --> 00:06:32.150 align:start position:0% if you adapt developer if you want to have<00:06:29.220> these<00:06:29.819> like<00:06:29.880> a<00:06:30.120> coinbase<00:06:30.840> sub<00:06:31.560> domain<00:06:31.919> or 00:06:32.150 --> 00:06:32.160 align:start position:0% have these like a coinbase sub domain or 00:06:32.160 --> 00:06:35.770 align:start position:0% have these like a coinbase sub domain or land<00:06:32.520> sub<00:06:32.699> domain<00:06:33.120> or<00:06:33.380> uh<00:06:34.380> sheets<00:06:35.100> subdomain 00:06:35.770 --> 00:06:35.780 align:start position:0% land sub domain or uh sheets subdomain 00:06:35.780 --> 00:06:40.249 align:start position:0% land sub domain or uh sheets subdomain as<00:06:36.780> long<00:06:36.900> as<00:06:37.020> your<00:06:37.500> app<00:06:38.220> has<00:06:38.520> He<00:06:39.240> suggests<00:06:39.720> uh 00:06:40.249 --> 00:06:40.259 align:start position:0% as long as your app has He suggests uh 00:06:40.259 --> 00:06:45.550 align:start position:0% as long as your app has He suggests uh later<00:06:40.919> than<00:06:41.280> 560<00:06:41.940> or<00:06:42.720> web3<00:06:43.259> Pi<00:06:43.680> B6<00:06:44.039> or<00:06:44.460> web3<00:06:44.940> JS 00:06:45.550 --> 00:06:45.560 align:start position:0% later than 560 or web3 Pi B6 or web3 JS 00:06:45.560 --> 00:06:49.670 align:start position:0% later than 560 or web3 Pi B6 or web3 JS b493<00:06:46.560> uh<00:06:47.280> you<00:06:47.520> already<00:06:47.699> have<00:06:48.300> the<00:06:48.600> uh 00:06:49.670 --> 00:06:49.680 align:start position:0% b493 uh you already have the uh 00:06:49.680 --> 00:06:52.670 align:start position:0% b493 uh you already have the uh feature<00:06:50.580> integrated<00:06:51.000> and<00:06:51.600> also<00:06:52.020> I<00:06:52.380> think 00:06:52.670 --> 00:06:52.680 align:start position:0% feature integrated and also I think 00:06:52.680 --> 00:06:55.189 align:start position:0% feature integrated and also I think nowadays<00:06:53.280> people<00:06:53.639> use<00:06:53.940> framework<00:06:54.419> kind<00:06:55.020> of 00:06:55.189 --> 00:06:55.199 align:start position:0% nowadays people use framework kind of 00:06:55.199 --> 00:06:58.129 align:start position:0% nowadays people use framework kind of tool<00:06:55.500> like<00:06:55.680> wag<00:06:56.039> me<00:06:56.280> or<00:06:56.520> used<00:06:57.120> up<00:06:57.419> they<00:06:57.720> because 00:06:58.129 --> 00:06:58.139 align:start position:0% tool like wag me or used up they because 00:06:58.139 --> 00:07:00.230 align:start position:0% tool like wag me or used up they because they<00:06:58.380> use<00:06:58.560> esl.js<00:06:59.220> underneath<00:06:59.639> that's 00:07:00.230 --> 00:07:00.240 align:start position:0% they use esl.js underneath that's 00:07:00.240 --> 00:07:02.870 align:start position:0% they use esl.js underneath that's already<00:07:00.479> supported 00:07:02.870 --> 00:07:02.880 align:start position:0% already supported 00:07:02.880 --> 00:07:05.510 align:start position:0% already supported yeah<00:07:03.300> right<00:07:03.479> away<00:07:03.660> and<00:07:04.199> for<00:07:04.440> the<00:07:04.620> wallet<00:07:04.979> side 00:07:05.510 --> 00:07:05.520 align:start position:0% yeah right away and for the wallet side 00:07:05.520 --> 00:07:09.050 align:start position:0% yeah right away and for the wallet side there's<00:07:05.940> a<00:07:06.180> wallets<00:07:06.660> like<00:07:06.840> I'll<00:07:06.960> follow<00:07:07.199> it<00:07:07.440> uh 00:07:09.050 --> 00:07:09.060 align:start position:0% there's a wallets like I'll follow it uh 00:07:09.060 --> 00:07:12.050 align:start position:0% there's a wallets like I'll follow it uh urgent<00:07:09.240> metamask 00:07:12.050 --> 00:07:12.060 align:start position:0% urgent metamask 00:07:12.060 --> 00:07:14.870 align:start position:0% urgent metamask Umbra<00:07:12.319> coinbase<00:07:13.319> trust<00:07:13.919> wallet<00:07:14.220> wallet 00:07:14.870 --> 00:07:14.880 align:start position:0% Umbra coinbase trust wallet wallet 00:07:14.880 --> 00:07:17.809 align:start position:0% Umbra coinbase trust wallet wallet connect<00:07:15.060> and<00:07:15.539> it's<00:07:16.139> a<00:07:16.319> scan<00:07:16.560> they<00:07:17.220> all<00:07:17.460> uh 00:07:17.809 --> 00:07:17.819 align:start position:0% connect and it's a scan they all uh 00:07:17.819 --> 00:07:20.029 align:start position:0% connect and it's a scan they all uh integrate<00:07:18.600> so<00:07:18.780> if<00:07:18.960> you're<00:07:19.080> using<00:07:19.440> this<00:07:19.620> you 00:07:20.029 --> 00:07:20.039 align:start position:0% integrate so if you're using this you 00:07:20.039 --> 00:07:22.670 align:start position:0% integrate so if you're using this you can<00:07:20.160> actually<00:07:20.340> uh<00:07:21.060> send<00:07:21.539> money<00:07:22.020> to<00:07:22.259> basically 00:07:22.670 --> 00:07:22.680 align:start position:0% can actually uh send money to basically 00:07:22.680 --> 00:07:25.490 align:start position:0% can actually uh send money to basically study<00:07:23.099> or<00:07:23.580> like<00:07:23.940> any<00:07:24.240> coinbase<00:07:24.720> user<00:07:25.139> who<00:07:25.319> has 00:07:25.490 --> 00:07:25.500 align:start position:0% study or like any coinbase user who has 00:07:25.500 --> 00:07:29.689 align:start position:0% study or like any coinbase user who has CBI<00:07:25.919> d<00:07:26.099> sub<00:07:26.280> domains<00:07:27.120> if<00:07:27.599> you<00:07:27.780> want<00:07:27.960> to 00:07:29.689 --> 00:07:29.699 align:start position:0% CBI d sub domains if you want to 00:07:29.699 --> 00:07:33.290 align:start position:0% CBI d sub domains if you want to and<00:07:30.479> so<00:07:31.080> yeah<00:07:31.500> what's<00:07:31.800> common<00:07:32.099> across<00:07:32.819> oh<00:07:33.180> yeah 00:07:33.290 --> 00:07:33.300 align:start position:0% and so yeah what's common across oh yeah 00:07:33.300 --> 00:07:34.969 align:start position:0% and so yeah what's common across oh yeah I<00:07:33.780> just<00:07:33.900> realized<00:07:34.199> I<00:07:34.380> can<00:07:34.560> just<00:07:34.680> read<00:07:34.800> that 00:07:34.969 --> 00:07:34.979 align:start position:0% I just realized I can just read that 00:07:34.979 --> 00:07:38.390 align:start position:0% I just realized I can just read that sorry<00:07:35.419> uh<00:07:36.419> okay<00:07:36.960> so<00:07:37.560> what's<00:07:37.740> coming<00:07:37.979> across 00:07:38.390 --> 00:07:38.400 align:start position:0% sorry uh okay so what's coming across 00:07:38.400 --> 00:07:40.309 align:start position:0% sorry uh okay so what's coming across this<00:07:38.520> example<00:07:38.940> is<00:07:39.300> basically<00:07:39.720> storage<00:07:39.960> like 00:07:40.309 --> 00:07:40.319 align:start position:0% this example is basically storage like 00:07:40.319 --> 00:07:42.350 align:start position:0% this example is basically storage like no<00:07:40.680> stick<00:07:40.860> it<00:07:41.160> can<00:07:41.340> be<00:07:41.460> the<00:07:41.699> best<00:07:41.940> polygon 00:07:42.350 --> 00:07:42.360 align:start position:0% no stick it can be the best polygon 00:07:42.360 --> 00:07:44.870 align:start position:0% no stick it can be the best polygon optimistic<00:07:42.960> optimism<00:07:43.800> or<00:07:44.280> Google 00:07:44.870 --> 00:07:44.880 align:start position:0% optimistic optimism or Google 00:07:44.880 --> 00:07:48.170 align:start position:0% optimistic optimism or Google spreadsheet<00:07:45.599> and<00:07:46.639> depends<00:07:47.639> on<00:07:47.699> the<00:07:47.940> storage 00:07:48.170 --> 00:07:48.180 align:start position:0% spreadsheet and depends on the storage 00:07:48.180 --> 00:07:50.990 align:start position:0% spreadsheet and depends on the storage uh<00:07:48.599> yeah<00:07:48.840> if<00:07:49.020> it's<00:07:49.139> in<00:07:49.380> like<00:07:49.740> a<00:07:50.039> L2<00:07:50.699> or<00:07:50.819> side 00:07:50.990 --> 00:07:51.000 align:start position:0% uh yeah if it's in like a L2 or side 00:07:51.000 --> 00:07:52.790 align:start position:0% uh yeah if it's in like a L2 or side chain<00:07:51.240> you<00:07:51.539> might<00:07:51.720> pay<00:07:51.960> a<00:07:52.199> little<00:07:52.319> bit<00:07:52.500> of<00:07:52.680> gas 00:07:52.790 --> 00:07:52.800 align:start position:0% chain you might pay a little bit of gas 00:07:52.800 --> 00:07:55.689 align:start position:0% chain you might pay a little bit of gas if<00:07:53.099> it's<00:07:53.220> enough<00:07:53.460> chain<00:07:53.759> complete<00:07:54.360> uh<00:07:55.020> gasless 00:07:55.689 --> 00:07:55.699 align:start position:0% if it's enough chain complete uh gasless 00:07:55.699 --> 00:07:58.370 align:start position:0% if it's enough chain complete uh gasless and<00:07:56.699> the<00:07:57.419> interesting<00:07:57.780> thing<00:07:57.900> is<00:07:58.020> like<00:07:58.199> I 00:07:58.370 --> 00:07:58.380 align:start position:0% and the interesting thing is like I 00:07:58.380 --> 00:08:00.409 align:start position:0% and the interesting thing is like I think<00:07:58.500> most<00:07:58.680> of<00:07:58.860> stuff<00:07:59.160> I'm<00:07:59.580> lucky 00:08:00.409 --> 00:08:00.419 align:start position:0% think most of stuff I'm lucky 00:08:00.419 --> 00:08:02.330 align:start position:0% think most of stuff I'm lucky if<00:08:00.960> you<00:08:01.080> use<00:08:01.259> different<00:08:01.500> chain<00:08:01.800> first<00:08:02.099> things 00:08:02.330 --> 00:08:02.340 align:start position:0% if you use different chain first things 00:08:02.340 --> 00:08:03.770 align:start position:0% if you use different chain first things you<00:08:02.759> have<00:08:02.880> to<00:08:02.940> do<00:08:03.060> exactly<00:08:03.419> you<00:08:03.599> go<00:08:03.720> to 00:08:03.770 --> 00:08:03.780 align:start position:0% you have to do exactly you go to 00:08:03.780 --> 00:08:05.809 align:start position:0% you have to do exactly you go to metamask<00:08:04.319> and<00:08:04.620> you<00:08:04.919> know<00:08:05.039> change<00:08:05.220> the<00:08:05.460> network 00:08:05.809 --> 00:08:05.819 align:start position:0% metamask and you know change the network 00:08:05.819 --> 00:08:07.730 align:start position:0% metamask and you know change the network ID<00:08:06.120> and<00:08:06.360> the<00:08:06.539> stuff<00:08:06.660> you<00:08:07.080> don't<00:08:07.199> have<00:08:07.380> to<00:08:07.500> do<00:08:07.620> it 00:08:07.730 --> 00:08:07.740 align:start position:0% ID and the stuff you don't have to do it 00:08:07.740 --> 00:08:09.650 align:start position:0% ID and the stuff you don't have to do it because<00:08:08.039> you<00:08:08.580> don't<00:08:08.699> want<00:08:08.819> to<00:08:09.000> know<00:08:09.180> which 00:08:09.650 --> 00:08:09.660 align:start position:0% because you don't want to know which 00:08:09.660 --> 00:08:13.370 align:start position:0% because you don't want to know which chain<00:08:10.620> these<00:08:11.160> users<00:08:11.720> data<00:08:12.720> are<00:08:12.900> and<00:08:13.259> they're 00:08:13.370 --> 00:08:13.380 align:start position:0% chain these users data are and they're 00:08:13.380 --> 00:08:14.570 align:start position:0% chain these users data are and they're like<00:08:13.500> I<00:08:13.740> don't<00:08:13.800> want<00:08:13.919> to<00:08:14.039> know<00:08:14.099> like<00:08:14.280> you<00:08:14.400> know 00:08:14.570 --> 00:08:14.580 align:start position:0% like I don't want to know like you know 00:08:14.580 --> 00:08:17.029 align:start position:0% like I don't want to know like you know where<00:08:14.819> data<00:08:15.240> is<00:08:15.360> for<00:08:15.720> the<00:08:15.960> coinbase<00:08:16.319> users<00:08:16.740> or 00:08:17.029 --> 00:08:17.039 align:start position:0% where data is for the coinbase users or 00:08:17.039 --> 00:08:20.150 align:start position:0% where data is for the coinbase users or lens<00:08:17.819> users<00:08:18.240> so<00:08:18.539> that<00:08:19.139> for<00:08:19.440> the<00:08:19.680> read-only 00:08:20.150 --> 00:08:20.160 align:start position:0% lens users so that for the read-only 00:08:20.160 --> 00:08:23.689 align:start position:0% lens users so that for the read-only purpose<00:08:20.580> data<00:08:21.360> is<00:08:21.539> all<00:08:21.720> available<00:08:21.960> through<00:08:22.500> L1 00:08:23.689 --> 00:08:23.699 align:start position:0% purpose data is all available through L1 00:08:23.699 --> 00:08:26.869 align:start position:0% purpose data is all available through L1 and<00:08:24.240> this<00:08:24.479> one<00:08:24.599> I<00:08:25.259> will<00:08:25.500> explain<00:08:25.740> later<00:08:26.099> but<00:08:26.400> we 00:08:26.869 --> 00:08:26.879 align:start position:0% and this one I will explain later but we 00:08:26.879 --> 00:08:28.610 align:start position:0% and this one I will explain later but we call<00:08:27.060> it<00:08:27.240> kind<00:08:27.419> of<00:08:27.539> trust<00:08:27.660> not<00:08:27.960> minimized 00:08:28.610 --> 00:08:28.620 align:start position:0% call it kind of trust not minimized 00:08:28.620 --> 00:08:33.050 align:start position:0% call it kind of trust not minimized you'll<00:08:29.340> find<00:08:29.520> out<00:08:29.699> a<00:08:29.879> bit<00:08:30.000> more<00:08:30.180> detail 00:08:33.050 --> 00:08:33.060 align:start position:0% 00:08:33.060 --> 00:08:35.870 align:start position:0% okay<00:08:33.599> so<00:08:33.959> under<00:08:34.140> the<00:08:34.440> hood<00:08:34.620> uh 00:08:35.870 --> 00:08:35.880 align:start position:0% okay so under the hood uh 00:08:35.880 --> 00:08:37.909 align:start position:0% okay so under the hood uh so<00:08:36.300> if<00:08:36.419> there's<00:08:36.659> any<00:08:36.899> pretty<00:08:37.380> much<00:08:37.500> all<00:08:37.740> the 00:08:37.909 --> 00:08:37.919 align:start position:0% so if there's any pretty much all the 00:08:37.919 --> 00:08:40.810 align:start position:0% so if there's any pretty much all the things<00:08:38.039> I'm<00:08:38.279> going<00:08:38.520> to<00:08:38.640> say<00:08:38.940> is<00:08:39.719> in<00:08:40.080> this<00:08:40.260> docs 00:08:40.810 --> 00:08:40.820 align:start position:0% things I'm going to say is in this docs 00:08:40.820 --> 00:08:43.490 align:start position:0% things I'm going to say is in this docs ens.domains<00:08:41.820> and<00:08:42.300> there's<00:08:42.539> a<00:08:42.719> QR<00:08:42.959> code<00:08:43.140> so<00:08:43.380> if 00:08:43.490 --> 00:08:43.500 align:start position:0% ens.domains and there's a QR code so if 00:08:43.500 --> 00:08:45.590 align:start position:0% ens.domains and there's a QR code so if you<00:08:43.680> you<00:08:43.860> are<00:08:44.219> interested<00:08:44.459> you<00:08:44.760> can<00:08:44.880> just<00:08:45.120> you 00:08:45.590 --> 00:08:45.600 align:start position:0% you you are interested you can just you 00:08:45.600 --> 00:08:47.389 align:start position:0% you you are interested you can just you know<00:08:45.720> take<00:08:45.839> a<00:08:46.020> shot 00:08:47.389 --> 00:08:47.399 align:start position:0% know take a shot 00:08:47.399 --> 00:08:49.730 align:start position:0% know take a shot and<00:08:47.880> sorry 00:08:49.730 --> 00:08:49.740 align:start position:0% and sorry 00:08:49.740 --> 00:08:51.350 align:start position:0% and sorry yeah<00:08:49.920> okay 00:08:51.350 --> 00:08:51.360 align:start position:0% yeah okay 00:08:51.360 --> 00:08:53.509 align:start position:0% yeah okay four<00:08:51.779> or<00:08:51.959> five<00:08:52.080> years<00:08:52.260> and<00:08:52.860> the<00:08:53.040> basic<00:08:53.339> model 00:08:53.509 --> 00:08:53.519 align:start position:0% four or five years and the basic model 00:08:53.519 --> 00:08:55.430 align:start position:0% four or five years and the basic model is<00:08:53.940> we<00:08:54.180> have<00:08:54.360> three 00:08:55.430 --> 00:08:55.440 align:start position:0% is we have three 00:08:55.440 --> 00:08:58.130 align:start position:0% is we have three well<00:08:55.920> basically<00:08:56.640> two<00:08:56.880> big<00:08:57.120> components<00:08:57.660> one<00:08:57.899> is 00:08:58.130 --> 00:08:58.140 align:start position:0% well basically two big components one is 00:08:58.140 --> 00:09:00.949 align:start position:0% well basically two big components one is called<00:08:58.320> registry<00:08:58.920> where<00:08:59.580> it's<00:08:59.760> a<00:09:00.000> big 00:09:00.949 --> 00:09:00.959 align:start position:0% called registry where it's a big 00:09:00.959 --> 00:09:04.870 align:start position:0% called registry where it's a big gigantic<00:09:01.500> dictionary<00:09:01.980> key<00:09:02.279> Value<00:09:02.519> Store 00:09:04.870 --> 00:09:04.880 align:start position:0% 00:09:04.880 --> 00:09:09.730 align:start position:0% and<00:09:05.880> instead<00:09:06.779> of<00:09:07.160> registry<00:09:08.160> hence<00:09:08.640> the<00:09:09.000> value 00:09:09.730 --> 00:09:09.740 align:start position:0% and instead of registry hence the value 00:09:09.740 --> 00:09:12.530 align:start position:0% and instead of registry hence the value we<00:09:10.740> return<00:09:10.980> so<00:09:11.399> for<00:09:11.580> example<00:09:11.820> in<00:09:12.060> this<00:09:12.180> example 00:09:12.530 --> 00:09:12.540 align:start position:0% we return so for example in this example 00:09:12.540 --> 00:09:17.269 align:start position:0% we return so for example in this example uh<00:09:13.440> you<00:09:13.920> ask<00:09:14.160> uh<00:09:15.060> what's<00:09:15.959> the<00:09:16.260> user<00:09:16.980> says 00:09:17.269 --> 00:09:17.279 align:start position:0% uh you ask uh what's the user says 00:09:17.279 --> 00:09:19.790 align:start position:0% uh you ask uh what's the user says what's<00:09:17.519> the<00:09:17.820> uh 00:09:19.790 --> 00:09:19.800 align:start position:0% what's the uh 00:09:19.800 --> 00:09:22.750 align:start position:0% what's the uh food<00:09:20.160> or<00:09:20.519> is<00:09:20.700> has<00:09:21.000> in<00:09:21.420> example<00:09:21.779> it<00:09:22.019> returns 00:09:22.750 --> 00:09:22.760 align:start position:0% food or is has in example it returns 00:09:22.760 --> 00:09:25.370 align:start position:0% food or is has in example it returns x1234<00:09:23.760> which<00:09:24.000> is<00:09:24.180> some<00:09:24.480> another<00:09:25.080> smart 00:09:25.370 --> 00:09:25.380 align:start position:0% x1234 which is some another smart 00:09:25.380 --> 00:09:27.410 align:start position:0% x1234 which is some another smart contract<00:09:25.800> called<00:09:25.980> resolver<00:09:26.580> and<00:09:27.240> the 00:09:27.410 --> 00:09:27.420 align:start position:0% contract called resolver and the 00:09:27.420 --> 00:09:30.170 align:start position:0% contract called resolver and the resolver<00:09:27.899> is<00:09:28.200> a<00:09:28.440> one<00:09:28.980> if<00:09:29.519> you<00:09:29.700> ask<00:09:29.880> that 00:09:30.170 --> 00:09:30.180 align:start position:0% resolver is a one if you ask that 00:09:30.180 --> 00:09:32.509 align:start position:0% resolver is a one if you ask that resolver<00:09:30.600> what's<00:09:30.899> the<00:09:31.080> address<00:09:31.200> of<00:09:31.519> food.edh 00:09:32.509 --> 00:09:32.519 align:start position:0% resolver what's the address of food.edh 00:09:32.519 --> 00:09:35.389 align:start position:0% resolver what's the address of food.edh that<00:09:33.180> Returns<00:09:33.600> the<00:09:33.779> actual<00:09:34.080> ECM<00:09:34.920> address<00:09:35.040> so 00:09:35.389 --> 00:09:35.399 align:start position:0% that Returns the actual ECM address so 00:09:35.399 --> 00:09:37.850 align:start position:0% that Returns the actual ECM address so that<00:09:35.519> kind<00:09:35.880> of<00:09:36.000> two<00:09:36.120> ways<00:09:36.360> right<00:09:37.320> and<00:09:37.620> the 00:09:37.850 --> 00:09:37.860 align:start position:0% that kind of two ways right and the 00:09:37.860 --> 00:09:40.430 align:start position:0% that kind of two ways right and the reason<00:09:38.220> we<00:09:38.459> did<00:09:38.640> is<00:09:38.880> is<00:09:39.120> the<00:09:39.600> flexibility<00:09:39.959> that 00:09:40.430 --> 00:09:40.440 align:start position:0% reason we did is is the flexibility that 00:09:40.440 --> 00:09:42.610 align:start position:0% reason we did is is the flexibility that uh 00:09:42.610 --> 00:09:42.620 align:start position:0% uh 00:09:42.620 --> 00:09:45.889 align:start position:0% uh once<00:09:43.620> you<00:09:43.980> kind<00:09:44.519> of<00:09:44.640> change<00:09:44.880> it's<00:09:45.720> very 00:09:45.889 --> 00:09:45.899 align:start position:0% once you kind of change it's very 00:09:45.899 --> 00:09:47.509 align:start position:0% once you kind of change it's very difficult<00:09:46.140> to<00:09:46.320> change<00:09:46.440> smart<00:09:46.740> contract<00:09:47.100> once 00:09:47.509 --> 00:09:47.519 align:start position:0% difficult to change smart contract once 00:09:47.519 --> 00:09:49.370 align:start position:0% difficult to change smart contract once you<00:09:47.580> deployed<00:09:48.000> to<00:09:48.360> ask<00:09:48.540> everybody<00:09:48.779> to<00:09:49.200> change 00:09:49.370 --> 00:09:49.380 align:start position:0% you deployed to ask everybody to change 00:09:49.380 --> 00:09:52.610 align:start position:0% you deployed to ask everybody to change point<00:09:49.740> to<00:09:49.920> the<00:09:50.100> new<00:09:50.220> one<00:09:50.779> so<00:09:51.779> but<00:09:52.080> if<00:09:52.260> you<00:09:52.380> have 00:09:52.610 --> 00:09:52.620 align:start position:0% point to the new one so but if you have 00:09:52.620 --> 00:09:55.850 align:start position:0% point to the new one so but if you have a<00:09:52.740> resolver<00:09:53.300> each<00:09:54.300> user<00:09:54.720> or<00:09:54.899> each<00:09:55.260> name<00:09:55.440> owner 00:09:55.850 --> 00:09:55.860 align:start position:0% a resolver each user or each name owner 00:09:55.860 --> 00:09:58.310 align:start position:0% a resolver each user or each name owner this<00:09:56.160> is<00:09:56.279> important<00:09:56.580> to<00:09:56.760> understand<00:09:56.940> is<00:09:57.360> a<00:09:57.660> can 00:09:58.310 --> 00:09:58.320 align:start position:0% this is important to understand is a can 00:09:58.320 --> 00:10:01.310 align:start position:0% this is important to understand is a can swap<00:09:59.040> the<00:09:59.360> resolver<00:10:00.360> and<00:10:00.660> have<00:10:00.899> their<00:10:01.200> own 00:10:01.310 --> 00:10:01.320 align:start position:0% swap the resolver and have their own 00:10:01.320 --> 00:10:04.790 align:start position:0% swap the resolver and have their own custom<00:10:01.620> uh<00:10:02.459> logic<00:10:03.120> or<00:10:03.360> if<00:10:03.839> we<00:10:04.019> release<00:10:04.320> a<00:10:04.620> new 00:10:04.790 --> 00:10:04.800 align:start position:0% custom uh logic or if we release a new 00:10:04.800 --> 00:10:06.590 align:start position:0% custom uh logic or if we release a new feature<00:10:05.160> you<00:10:05.700> can<00:10:05.820> upgrade<00:10:06.180> to<00:10:06.360> the<00:10:06.480> new 00:10:06.590 --> 00:10:06.600 align:start position:0% feature you can upgrade to the new 00:10:06.600 --> 00:10:10.730 align:start position:0% feature you can upgrade to the new feature<00:10:07.160> or<00:10:08.160> by<00:10:08.580> uh<00:10:09.120> by<00:10:09.779> each<00:10:09.959> user<00:10:10.380> by<00:10:10.560> each 00:10:10.730 --> 00:10:10.740 align:start position:0% feature or by uh by each user by each 00:10:10.740 --> 00:10:13.430 align:start position:0% feature or by uh by each user by each domain<00:10:11.160> okay<00:10:11.519> so<00:10:11.820> this<00:10:12.000> is<00:10:12.060> a<00:10:12.300> basic<00:10:12.600> and<00:10:13.260> with 00:10:13.430 --> 00:10:13.440 align:start position:0% domain okay so this is a basic and with 00:10:13.440 --> 00:10:14.630 align:start position:0% domain okay so this is a basic and with this<00:10:13.620> in<00:10:13.860> mind 00:10:14.630 --> 00:10:14.640 align:start position:0% this in mind 00:10:14.640 --> 00:10:19.610 align:start position:0% this in mind uh<00:10:15.600> what<00:10:16.080> we<00:10:16.620> do<00:10:17.100> with<00:10:17.580> this<00:10:18.060> new<00:10:18.899> interchange 00:10:19.610 --> 00:10:19.620 align:start position:0% uh what we do with this new interchange 00:10:19.620 --> 00:10:22.009 align:start position:0% uh what we do with this new interchange of 00:10:22.009 --> 00:10:22.019 align:start position:0% of 00:10:22.019 --> 00:10:24.590 align:start position:0% of across<00:10:22.860> chain<00:10:23.040> uh<00:10:23.519> thing<00:10:24.000> is<00:10:24.300> something 00:10:24.590 --> 00:10:24.600 align:start position:0% across chain uh thing is something 00:10:24.600 --> 00:10:27.850 align:start position:0% across chain uh thing is something called<00:10:24.839> ccip<00:10:25.320> read<00:10:25.820> also<00:10:26.820> known<00:10:27.120> as 00:10:27.850 --> 00:10:27.860 align:start position:0% called ccip read also known as 00:10:27.860 --> 00:10:30.889 align:start position:0% called ccip read also known as eip3668<00:10:28.860> uh<00:10:29.640> secure<00:10:29.940> of<00:10:30.180> chain<00:10:30.420> data 00:10:30.889 --> 00:10:30.899 align:start position:0% eip3668 uh secure of chain data 00:10:30.899 --> 00:10:32.750 align:start position:0% eip3668 uh secure of chain data retrievable<00:10:31.380> and<00:10:31.980> what<00:10:32.220> I'm<00:10:32.399> going<00:10:32.580> to 00:10:32.750 --> 00:10:32.760 align:start position:0% retrievable and what I'm going to 00:10:32.760 --> 00:10:35.509 align:start position:0% retrievable and what I'm going to explain<00:10:33.060> is<00:10:33.360> it's<00:10:34.019> going<00:10:34.260> to<00:10:34.380> the<00:10:34.620> instead<00:10:35.459> of 00:10:35.509 --> 00:10:35.519 align:start position:0% explain is it's going to the instead of 00:10:35.519 --> 00:10:37.850 align:start position:0% explain is it's going to the instead of the<00:10:35.700> two-step<00:10:36.180> model<00:10:36.420> of<00:10:36.899> the<00:10:37.200> existing 00:10:37.850 --> 00:10:37.860 align:start position:0% the two-step model of the existing 00:10:37.860 --> 00:10:43.150 align:start position:0% the two-step model of the existing resolver<00:10:38.339> it's<00:10:38.940> a<00:10:39.240> three-step<00:10:39.899> model<00:10:40.140> and 00:10:43.150 --> 00:10:43.160 align:start position:0% 00:10:43.160 --> 00:10:46.610 align:start position:0% request<00:10:44.160> and<00:10:44.459> a<00:10:44.579> verify 00:10:46.610 --> 00:10:46.620 align:start position:0% request and a verify 00:10:46.620 --> 00:10:49.850 align:start position:0% request and a verify okay<00:10:47.160> so<00:10:47.579> what<00:10:48.120> it<00:10:48.420> does<00:10:48.660> for<00:10:49.320> the<00:10:49.500> first<00:10:49.680> time 00:10:49.850 --> 00:10:49.860 align:start position:0% okay so what it does for the first time 00:10:49.860 --> 00:10:51.829 align:start position:0% okay so what it does for the first time is<00:10:50.040> like<00:10:50.279> for<00:10:50.459> example<00:10:50.640> if<00:10:50.880> you<00:10:51.120> go<00:10:51.300> ask<00:10:51.600> for 00:10:51.829 --> 00:10:51.839 align:start position:0% is like for example if you go ask for 00:10:51.839 --> 00:10:54.290 align:start position:0% is like for example if you go ask for the<00:10:52.140> uh 00:10:54.290 --> 00:10:54.300 align:start position:0% the uh 00:10:54.300 --> 00:10:57.170 align:start position:0% the uh data<00:10:55.079> on<00:10:55.320> the<00:10:55.440> resolver<00:10:55.920> uh<00:10:56.820> instead<00:10:57.120> of 00:10:57.170 --> 00:10:57.180 align:start position:0% data on the resolver uh instead of 00:10:57.180 --> 00:10:59.150 align:start position:0% data on the resolver uh instead of returning<00:10:57.720> the<00:10:57.839> data<00:10:58.079> it<00:10:58.440> actually<00:10:58.620> throw<00:10:58.920> the 00:10:59.150 --> 00:10:59.160 align:start position:0% returning the data it actually throw the 00:10:59.160 --> 00:11:01.970 align:start position:0% returning the data it actually throw the exception<00:10:59.519> called<00:11:00.300> off<00:11:00.540> chain<00:11:00.779> lookup<00:11:01.200> and<00:11:01.740> so 00:11:01.970 --> 00:11:01.980 align:start position:0% exception called off chain lookup and so 00:11:01.980 --> 00:11:04.790 align:start position:0% exception called off chain lookup and so like<00:11:02.240> this<00:11:03.240> error<00:11:03.540> message<00:11:03.720> came<00:11:04.260> from<00:11:04.560> I 00:11:04.790 --> 00:11:04.800 align:start position:0% like this error message came from I 00:11:04.800 --> 00:11:07.730 align:start position:0% like this error message came from I think<00:11:04.920> solidity<00:11:05.519> eight<00:11:05.820> point<00:11:06.060> something<00:11:06.779> and 00:11:07.730 --> 00:11:07.740 align:start position:0% think solidity eight point something and 00:11:07.740 --> 00:11:09.650 align:start position:0% think solidity eight point something and this<00:11:08.519> interesting<00:11:08.880> thing<00:11:09.060> is<00:11:09.300> like<00:11:09.480> a 00:11:09.650 --> 00:11:09.660 align:start position:0% this interesting thing is like a 00:11:09.660 --> 00:11:12.350 align:start position:0% this interesting thing is like a basically<00:11:09.959> it<00:11:10.920> returns<00:11:11.519> a<00:11:11.640> different<00:11:11.820> kind<00:11:12.180> of 00:11:12.350 --> 00:11:12.360 align:start position:0% basically it returns a different kind of 00:11:12.360 --> 00:11:15.590 align:start position:0% basically it returns a different kind of a<00:11:12.480> data<00:11:12.839> type<00:11:13.019> by<00:11:13.860> calling<00:11:14.339> the<00:11:14.519> same<00:11:14.940> function 00:11:15.590 --> 00:11:15.600 align:start position:0% a data type by calling the same function 00:11:15.600 --> 00:11:18.110 align:start position:0% a data type by calling the same function so<00:11:16.260> that<00:11:16.440> like<00:11:16.620> you<00:11:16.860> don't<00:11:17.040> have<00:11:17.160> to<00:11:17.399> client 00:11:18.110 --> 00:11:18.120 align:start position:0% so that like you don't have to client 00:11:18.120 --> 00:11:19.670 align:start position:0% so that like you don't have to client doesn't<00:11:18.480> have<00:11:18.720> to<00:11:18.839> know<00:11:19.019> whether<00:11:19.500> the 00:11:19.670 --> 00:11:19.680 align:start position:0% doesn't have to know whether the 00:11:19.680 --> 00:11:23.509 align:start position:0% doesn't have to know whether the function<00:11:20.100> call<00:11:20.339> is<00:11:20.640> towards<00:11:21.360> L1<00:11:21.779> or<00:11:22.220> L2<00:11:23.220> other 00:11:23.509 --> 00:11:23.519 align:start position:0% function call is towards L1 or L2 other 00:11:23.519 --> 00:11:26.269 align:start position:0% function call is towards L1 or L2 other place<00:11:23.760> it's<00:11:24.000> just<00:11:24.180> like<00:11:24.540> you<00:11:24.720> uh<00:11:25.560> e<00:11:25.800> reverts 00:11:26.269 --> 00:11:26.279 align:start position:0% place it's just like you uh e reverts 00:11:26.279 --> 00:11:28.190 align:start position:0% place it's just like you uh e reverts and<00:11:26.399> it<00:11:26.640> catches<00:11:27.000> and<00:11:27.360> then<00:11:27.480> once<00:11:27.660> you<00:11:27.779> revert 00:11:28.190 --> 00:11:28.200 align:start position:0% and it catches and then once you revert 00:11:28.200 --> 00:11:31.190 align:start position:0% and it catches and then once you revert you<00:11:28.440> catch<00:11:28.740> the<00:11:29.120> revert<00:11:30.120> message<00:11:30.240> it<00:11:30.720> has<00:11:30.959> the 00:11:31.190 --> 00:11:31.200 align:start position:0% you catch the revert message it has the 00:11:31.200 --> 00:11:34.009 align:start position:0% you catch the revert message it has the information<00:11:31.320> about<00:11:31.940> uh<00:11:32.940> this<00:11:33.360> address<00:11:33.600> which 00:11:34.009 --> 00:11:34.019 align:start position:0% information about uh this address which 00:11:34.019 --> 00:11:36.590 align:start position:0% information about uh this address which is<00:11:34.140> a<00:11:34.380> resolver<00:11:35.220> then<00:11:36.000> it<00:11:36.360> has<00:11:36.480> something 00:11:36.590 --> 00:11:36.600 align:start position:0% is a resolver then it has something 00:11:36.600 --> 00:11:39.290 align:start position:0% is a resolver then it has something called<00:11:36.839> URL<00:11:37.320> which<00:11:38.040> is<00:11:38.220> we<00:11:38.579> call<00:11:38.760> a<00:11:38.940> Gateway 00:11:39.290 --> 00:11:39.300 align:start position:0% called URL which is we call a Gateway 00:11:39.300 --> 00:11:43.069 align:start position:0% called URL which is we call a Gateway server<00:11:39.779> and<00:11:40.500> plus<00:11:41.399> the<00:11:41.640> core<00:11:41.820> data<00:11:42.240> which<00:11:42.540> you 00:11:43.069 --> 00:11:43.079 align:start position:0% server and plus the core data which you 00:11:43.079 --> 00:11:45.170 align:start position:0% server and plus the core data which you know<00:11:43.140> you<00:11:43.320> send<00:11:43.500> for<00:11:43.680> the<00:11:43.800> function<00:11:44.040> call<00:11:44.279> and 00:11:45.170 --> 00:11:45.180 align:start position:0% know you send for the function call and 00:11:45.180 --> 00:11:48.290 align:start position:0% know you send for the function call and of<00:11:46.079> gem<00:11:46.380> is<00:11:46.500> over<00:11:46.680> Reservoir<00:11:47.279> so<00:11:47.640> this<00:11:47.880> is<00:11:48.000> I 00:11:48.290 --> 00:11:48.300 align:start position:0% of gem is over Reservoir so this is I 00:11:48.300 --> 00:11:49.910 align:start position:0% of gem is over Reservoir so this is I think 00:11:49.910 --> 00:11:49.920 align:start position:0% think 00:11:49.920 --> 00:11:54.050 align:start position:0% think the<00:11:50.579> function<00:11:50.880> type<00:11:51.240> of<00:11:51.480> the<00:11:51.720> uh 00:11:54.050 --> 00:11:54.060 align:start position:0% the function type of the uh 00:11:54.060 --> 00:11:56.569 align:start position:0% the function type of the uh function<00:11:54.779> which<00:11:55.200> you're<00:11:55.380> gonna<00:11:55.620> call<00:11:55.980> once 00:11:56.569 --> 00:11:56.579 align:start position:0% function which you're gonna call once 00:11:56.579 --> 00:11:59.210 align:start position:0% function which you're gonna call once again<00:11:56.839> once<00:11:57.839> the<00:11:58.019> Gateway<00:11:58.320> returns<00:11:59.040> up 00:11:59.210 --> 00:11:59.220 align:start position:0% again once the Gateway returns up 00:11:59.220 --> 00:12:00.610 align:start position:0% again once the Gateway returns up results 00:12:00.610 --> 00:12:00.620 align:start position:0% results 00:12:00.620 --> 00:12:04.430 align:start position:0% results and<00:12:01.620> what<00:12:02.279> the<00:12:02.760> code<00:12:02.940> is<00:12:03.180> a<00:12:03.300> bit<00:12:03.360> old<00:12:03.540> so<00:12:04.079> there 00:12:04.430 --> 00:12:04.440 align:start position:0% and what the code is a bit old so there 00:12:04.440 --> 00:12:06.410 align:start position:0% and what the code is a bit old so there might<00:12:04.620> be<00:12:04.740> some<00:12:04.920> consistency<00:12:05.459> that<00:12:05.940> so<00:12:06.180> step 00:12:06.410 --> 00:12:06.420 align:start position:0% might be some consistency that so step 00:12:06.420 --> 00:12:10.550 align:start position:0% might be some consistency that so step one<00:12:06.600> revert<00:12:07.800> and<00:12:08.279> that's<00:12:08.519> solidity<00:12:09.060> code 00:12:10.550 --> 00:12:10.560 align:start position:0% one revert and that's solidity code 00:12:10.560 --> 00:12:13.490 align:start position:0% one revert and that's solidity code and<00:12:11.040> the<00:12:11.220> once<00:12:11.519> that's<00:12:11.700> done<00:12:12.060> uh 00:12:13.490 --> 00:12:13.500 align:start position:0% and the once that's done uh 00:12:13.500 --> 00:12:16.790 align:start position:0% and the once that's done uh so<00:12:13.980> this<00:12:14.220> is<00:12:14.339> a<00:12:14.579> web<00:12:14.940> service<00:12:15.180> that<00:12:15.839> URL<00:12:16.320> you 00:12:16.790 --> 00:12:16.800 align:start position:0% so this is a web service that URL you 00:12:16.800 --> 00:12:19.190 align:start position:0% so this is a web service that URL you know<00:12:16.920> you<00:12:17.100> just<00:12:17.279> catch<00:12:17.700> in<00:12:17.880> a<00:12:18.000> revert<00:12:18.540> you<00:12:19.019> call 00:12:19.190 --> 00:12:19.200 align:start position:0% know you just catch in a revert you call 00:12:19.200 --> 00:12:22.190 align:start position:0% know you just catch in a revert you call this<00:12:19.440> uh<00:12:19.680> web<00:12:20.220> services<00:12:20.399> and<00:12:20.940> the<00:12:21.180> uh<00:12:21.839> things 00:12:22.190 --> 00:12:22.200 align:start position:0% this uh web services and the uh things 00:12:22.200 --> 00:12:25.069 align:start position:0% this uh web services and the uh things it<00:12:22.440> does<00:12:22.680> is<00:12:22.920> uh<00:12:23.760> fast<00:12:24.060> line<00:12:24.240> is<00:12:24.540> the<00:12:24.660> Salvador 00:12:25.069 --> 00:12:25.079 align:start position:0% it does is uh fast line is the Salvador 00:12:25.079 --> 00:12:27.470 align:start position:0% it does is uh fast line is the Salvador art<00:12:25.380> is<00:12:25.560> just<00:12:25.800> like<00:12:25.980> a 00:12:27.470 --> 00:12:27.480 align:start position:0% art is just like a 00:12:27.480 --> 00:12:30.370 align:start position:0% art is just like a function<00:12:28.260> uh 00:12:30.370 --> 00:12:30.380 align:start position:0% function uh 00:12:30.380 --> 00:12:33.829 align:start position:0% function uh ccipv<00:12:31.380> server<00:12:31.860> Library<00:12:32.160> offers<00:12:32.640> like<00:12:32.880> any<00:12:33.420> or 00:12:33.829 --> 00:12:33.839 align:start position:0% ccipv server Library offers like any or 00:12:33.839 --> 00:12:35.690 align:start position:0% ccipv server Library offers like any or any<00:12:34.079> of<00:12:34.200> the<00:12:34.380> web<00:12:34.500> services<00:12:34.680> you<00:12:35.100> have<00:12:35.279> you<00:12:35.579> can 00:12:35.690 --> 00:12:35.700 align:start position:0% any of the web services you have you can 00:12:35.700 --> 00:12:37.850 align:start position:0% any of the web services you have you can kind<00:12:35.940> of<00:12:36.060> chuckle<00:12:36.660> in<00:12:36.779> this<00:12:36.959> uh<00:12:37.200> capability 00:12:37.850 --> 00:12:37.860 align:start position:0% kind of chuckle in this uh capability 00:12:37.860 --> 00:12:40.190 align:start position:0% kind of chuckle in this uh capability easily<00:12:38.339> then<00:12:38.760> what<00:12:39.000> you<00:12:39.120> do<00:12:39.360> is<00:12:39.480> you<00:12:39.720> basically 00:12:40.190 --> 00:12:40.200 align:start position:0% easily then what you do is you basically 00:12:40.200 --> 00:12:42.110 align:start position:0% easily then what you do is you basically query<00:12:40.560> the<00:12:40.740> data<00:12:41.100> from<00:12:41.339> somewhere<00:12:41.760> it<00:12:42.000> could 00:12:42.110 --> 00:12:42.120 align:start position:0% query the data from somewhere it could 00:12:42.120 --> 00:12:44.449 align:start position:0% query the data from somewhere it could be<00:12:42.240> database<00:12:42.660> it<00:12:42.899> could<00:12:43.019> be<00:12:43.139> of 00:12:44.449 --> 00:12:44.459 align:start position:0% be database it could be of 00:12:44.459 --> 00:12:46.069 align:start position:0% be database it could be of a side<00:12:45.120> chain<00:12:45.360> it<00:12:45.600> could<00:12:45.720> be<00:12:45.839> Google 00:12:46.069 --> 00:12:46.079 align:start position:0% a side chain it could be Google 00:12:46.079 --> 00:12:49.310 align:start position:0% a side chain it could be Google spreadsheet<00:12:46.860> then<00:12:47.579> after<00:12:48.120> that<00:12:48.420> we<00:12:48.839> basically 00:12:49.310 --> 00:12:49.320 align:start position:0% spreadsheet then after that we basically 00:12:49.320 --> 00:12:53.509 align:start position:0% spreadsheet then after that we basically ask<00:12:49.820> the<00:12:50.820> gateway<00:12:51.240> to<00:12:51.540> sign<00:12:51.839> the<00:12:52.200> data<00:12:52.680> and<00:12:53.220> it 00:12:53.509 --> 00:12:53.519 align:start position:0% ask the gateway to sign the data and it 00:12:53.519 --> 00:12:56.870 align:start position:0% ask the gateway to sign the data and it returns<00:12:54.000> uh<00:12:54.899> back<00:12:55.139> to<00:12:55.320> the<00:12:55.440> client<00:12:55.740> and<00:12:56.459> once 00:12:56.870 --> 00:12:56.880 align:start position:0% returns uh back to the client and once 00:12:56.880 --> 00:13:00.710 align:start position:0% returns uh back to the client and once it's<00:12:57.060> returned<00:12:57.680> uh<00:12:58.680> again<00:12:59.279> this<00:13:00.060> is<00:13:00.180> in<00:13:00.360> L1 00:13:00.710 --> 00:13:00.720 align:start position:0% it's returned uh again this is in L1 00:13:00.720 --> 00:13:04.670 align:start position:0% it's returned uh again this is in L1 that<00:13:01.260> uh<00:13:01.680> it<00:13:02.459> basically<00:13:03.200> calls<00:13:04.200> this<00:13:04.380> function 00:13:04.670 --> 00:13:04.680 align:start position:0% that uh it basically calls this function 00:13:04.680 --> 00:13:08.150 align:start position:0% that uh it basically calls this function to<00:13:04.920> and<00:13:05.399> you<00:13:05.760> decode<00:13:06.240> this<00:13:06.540> signature<00:13:07.380> and<00:13:07.980> you 00:13:08.150 --> 00:13:08.160 align:start position:0% to and you decode this signature and you 00:13:08.160 --> 00:13:10.009 align:start position:0% to and you decode this signature and you check<00:13:08.279> like<00:13:08.519> if<00:13:08.700> we<00:13:08.820> verified<00:13:09.180> and<00:13:09.600> if<00:13:09.779> you 00:13:10.009 --> 00:13:10.019 align:start position:0% check like if we verified and if you 00:13:10.019 --> 00:13:12.410 align:start position:0% check like if we verified and if you it's<00:13:10.740> verified<00:13:11.100> by<00:13:11.399> the<00:13:11.579> Gateway<00:13:11.940> it<00:13:12.240> was 00:13:12.410 --> 00:13:12.420 align:start position:0% it's verified by the Gateway it was 00:13:12.420 --> 00:13:15.889 align:start position:0% it's verified by the Gateway it was specified<00:13:12.779> in<00:13:12.959> revert<00:13:13.560> we<00:13:13.920> say<00:13:14.040> okay<00:13:14.600> we<00:13:15.600> trust 00:13:15.889 --> 00:13:15.899 align:start position:0% specified in revert we say okay we trust 00:13:15.899 --> 00:13:18.170 align:start position:0% specified in revert we say okay we trust this<00:13:16.200> Gateway<00:13:16.800> service<00:13:17.100> so<00:13:17.519> like<00:13:17.700> hence<00:13:17.940> we 00:13:18.170 --> 00:13:18.180 align:start position:0% this Gateway service so like hence we 00:13:18.180 --> 00:13:20.990 align:start position:0% this Gateway service so like hence we return<00:13:18.300> the<00:13:18.660> data<00:13:18.959> so<00:13:19.320> bye<00:13:20.040> by<00:13:20.579> using<00:13:20.880> smart 00:13:20.990 --> 00:13:21.000 align:start position:0% return the data so bye by using smart 00:13:21.000 --> 00:13:23.090 align:start position:0% return the data so bye by using smart contract<00:13:21.420> to<00:13:21.600> be<00:13:21.720> kind<00:13:21.959> of<00:13:22.079> proxy<00:13:22.380> yeah<00:13:22.680> user 00:13:23.090 --> 00:13:23.100 align:start position:0% contract to be kind of proxy yeah user 00:13:23.100 --> 00:13:25.190 align:start position:0% contract to be kind of proxy yeah user can<00:13:23.339> retrieve<00:13:24.120> the<00:13:24.240> off-chain<00:13:24.660> data<00:13:25.019> without 00:13:25.190 --> 00:13:25.200 align:start position:0% can retrieve the off-chain data without 00:13:25.200 --> 00:13:27.350 align:start position:0% can retrieve the off-chain data without switching<00:13:25.680> metamask<00:13:26.160> or<00:13:26.399> not<00:13:26.880> knowing<00:13:27.240> any 00:13:27.350 --> 00:13:27.360 align:start position:0% switching metamask or not knowing any 00:13:27.360 --> 00:13:29.269 align:start position:0% switching metamask or not knowing any other<00:13:27.540> information<00:13:27.779> but<00:13:28.680> all<00:13:28.980> these<00:13:29.160> things 00:13:29.269 --> 00:13:29.279 align:start position:0% other information but all these things 00:13:29.279 --> 00:13:30.949 align:start position:0% other information but all these things are<00:13:29.519> kind<00:13:29.760> of<00:13:29.880> encapsulated<00:13:30.420> especially 00:13:30.949 --> 00:13:30.959 align:start position:0% are kind of encapsulated especially 00:13:30.959 --> 00:13:33.889 align:start position:0% are kind of encapsulated especially using<00:13:31.260> esos.js<00:13:31.980> so<00:13:32.579> most<00:13:32.880> data<00:13:33.300> use<00:13:33.480> you<00:13:33.720> don't 00:13:33.889 --> 00:13:33.899 align:start position:0% using esos.js so most data use you don't 00:13:33.899 --> 00:13:36.110 align:start position:0% using esos.js so most data use you don't actually<00:13:34.139> even<00:13:34.620> see<00:13:34.920> it<00:13:35.100> but<00:13:35.459> if<00:13:35.639> we<00:13:35.820> want<00:13:36.000> to 00:13:36.110 --> 00:13:36.120 align:start position:0% actually even see it but if we want to 00:13:36.120 --> 00:13:38.449 align:start position:0% actually even see it but if we want to do<00:13:36.180> directly<00:13:36.660> with<00:13:37.200> the<00:13:37.500> interactive<00:13:38.160> smart 00:13:38.449 --> 00:13:38.459 align:start position:0% do directly with the interactive smart 00:13:38.459 --> 00:13:40.850 align:start position:0% do directly with the interactive smart contract<00:13:38.820> you<00:13:39.540> kind<00:13:39.720> of<00:13:39.839> have<00:13:39.959> to<00:13:40.139> know 00:13:40.850 --> 00:13:40.860 align:start position:0% contract you kind of have to know 00:13:40.860 --> 00:13:41.810 align:start position:0% contract you kind of have to know yeah 00:13:41.810 --> 00:13:41.820 align:start position:0% yeah 00:13:41.820 --> 00:13:46.490 align:start position:0% yeah and<00:13:42.540> so<00:13:43.019> once<00:13:43.740> the<00:13:44.220> basic<00:13:44.700> logic<00:13:45.420> of<00:13:45.779> the<00:13:46.019> of 00:13:46.490 --> 00:13:46.500 align:start position:0% and so once the basic logic of the of 00:13:46.500 --> 00:13:49.790 align:start position:0% and so once the basic logic of the of generated<00:13:46.980> redrubal<00:13:47.700> is 00:13:49.790 --> 00:13:49.800 align:start position:0% generated redrubal is 00:13:49.800 --> 00:13:51.889 align:start position:0% generated redrubal is explained<00:13:50.639> next<00:13:50.940> thing<00:13:51.060> you<00:13:51.240> also<00:13:51.720> have<00:13:51.839> to 00:13:51.889 --> 00:13:51.899 align:start position:0% explained next thing you also have to 00:13:51.899 --> 00:13:55.250 align:start position:0% explained next thing you also have to know<00:13:52.079> is<00:13:52.260> another<00:13:52.560> EIP<00:13:53.279> called<00:13:53.720> ensip10<00:13:54.720> so 00:13:55.250 --> 00:13:55.260 align:start position:0% know is another EIP called ensip10 so 00:13:55.260 --> 00:13:57.350 align:start position:0% know is another EIP called ensip10 so wild<00:13:55.560> card<00:13:55.740> resolution<00:13:56.220> for<00:13:56.820> issue<00:13:57.180> sub 00:13:57.350 --> 00:13:57.360 align:start position:0% wild card resolution for issue sub 00:13:57.360 --> 00:13:59.449 align:start position:0% wild card resolution for issue sub domain<00:13:57.839> is<00:13:57.959> like<00:13:58.139> one<00:13:58.680> thing<00:13:58.800> you<00:13:58.980> need<00:13:59.220> to 00:13:59.449 --> 00:13:59.459 align:start position:0% domain is like one thing you need to 00:13:59.459 --> 00:14:01.610 align:start position:0% domain is like one thing you need to know<00:13:59.820> in<00:14:00.240> the<00:14:00.360> case<00:14:00.540> of<00:14:00.779> we<00:14:01.260> are<00:14:01.380> talking<00:14:01.500> about 00:14:01.610 --> 00:14:01.620 align:start position:0% know in the case of we are talking about 00:14:01.620 --> 00:14:03.590 align:start position:0% know in the case of we are talking about biggest<00:14:01.860> use<00:14:02.220> case<00:14:02.519> as<00:14:02.880> a<00:14:03.060> issue<00:14:03.480> in 00:14:03.590 --> 00:14:03.600 align:start position:0% biggest use case as a issue in 00:14:03.600 --> 00:14:06.290 align:start position:0% biggest use case as a issue in sub-domains<00:14:04.200> and<00:14:04.620> when<00:14:04.860> it<00:14:05.100> goes<00:14:05.339> to<00:14:05.579> uh<00:14:05.940> for 00:14:06.290 --> 00:14:06.300 align:start position:0% sub-domains and when it goes to uh for 00:14:06.300 --> 00:14:08.290 align:start position:0% sub-domains and when it goes to uh for example<00:14:06.600> cbe.id 00:14:08.290 --> 00:14:08.300 align:start position:0% example cbe.id 00:14:08.300 --> 00:14:12.410 align:start position:0% example cbe.id cbd.id<00:14:09.300> does<00:14:10.019> have<00:14:10.260> a<00:14:10.740> resolver<00:14:11.519> contract<00:14:11.940> on 00:14:12.410 --> 00:14:12.420 align:start position:0% cbd.id does have a resolver contract on 00:14:12.420 --> 00:14:14.750 align:start position:0% cbd.id does have a resolver contract on the<00:14:12.540> L1<00:14:12.899> which<00:14:13.680> basically<00:14:13.980> acts<00:14:14.220> as<00:14:14.339> a<00:14:14.459> Gateway 00:14:14.750 --> 00:14:14.760 align:start position:0% the L1 which basically acts as a Gateway 00:14:14.760 --> 00:14:18.110 align:start position:0% the L1 which basically acts as a Gateway too<00:14:15.000> of<00:14:15.600> chain<00:14:15.899> but<00:14:16.740> use<00:14:17.100> the<00:14:17.459> subdomain 00:14:18.110 --> 00:14:18.120 align:start position:0% too of chain but use the subdomain 00:14:18.120 --> 00:14:20.810 align:start position:0% too of chain but use the subdomain actually<00:14:18.540> doesn't<00:14:18.839> have<00:14:19.019> any<00:14:19.139> data<00:14:19.680> on<00:14:19.800> L1<00:14:20.220> and 00:14:20.810 --> 00:14:20.820 align:start position:0% actually doesn't have any data on L1 and 00:14:20.820 --> 00:14:22.690 align:start position:0% actually doesn't have any data on L1 and what<00:14:21.060> it<00:14:21.240> does<00:14:21.360> is<00:14:21.540> this<00:14:21.779> isn't<00:14:22.079> just<00:14:22.260> another 00:14:22.690 --> 00:14:22.700 align:start position:0% what it does is this isn't just another 00:14:22.700 --> 00:14:25.790 align:start position:0% what it does is this isn't just another rule<00:14:23.700> we<00:14:23.880> Define<00:14:24.120> in<00:14:24.420> a<00:14:24.540> client<00:14:24.779> level<00:14:24.959> that<00:14:25.380> if 00:14:25.790 --> 00:14:25.800 align:start position:0% rule we Define in a client level that if 00:14:25.800 --> 00:14:28.970 align:start position:0% rule we Define in a client level that if I<00:14:26.040> I<00:14:26.220> have<00:14:26.459> a<00:14:26.639> let's<00:14:27.060> say<00:14:27.240> my<00:14:28.019> token<00:14:28.380> in<00:14:28.860> this 00:14:28.970 --> 00:14:28.980 align:start position:0% I I have a let's say my token in this 00:14:28.980 --> 00:14:32.990 align:start position:0% I I have a let's say my token in this example<00:14:29.279> it<00:14:29.459> says<00:14:30.200> eth<00:14:31.200> and<00:14:32.100> the<00:14:32.279> IFA<00:14:32.639> dot 00:14:32.990 --> 00:14:33.000 align:start position:0% example it says eth and the IFA dot 00:14:33.000 --> 00:14:34.970 align:start position:0% example it says eth and the IFA dot matokeo.eth<00:14:33.779> it<00:14:34.079> doesn't<00:14:34.260> exist<00:14:34.560> no<00:14:34.800> one 00:14:34.970 --> 00:14:34.980 align:start position:0% matokeo.eth it doesn't exist no one 00:14:34.980 --> 00:14:37.190 align:start position:0% matokeo.eth it doesn't exist no one doesn't<00:14:35.100> have<00:14:35.339> a<00:14:35.459> resolver<00:14:35.940> at<00:14:36.720> the<00:14:36.899> client 00:14:37.190 --> 00:14:37.200 align:start position:0% doesn't have a resolver at the client 00:14:37.200 --> 00:14:40.850 align:start position:0% doesn't have a resolver at the client library<00:14:37.500> on<00:14:38.940> asked<00:14:39.720> to<00:14:39.779> the<00:14:39.959> parent<00:14:40.139> in<00:14:40.800> that 00:14:40.850 --> 00:14:40.860 align:start position:0% library on asked to the parent in that 00:14:40.860 --> 00:14:43.069 align:start position:0% library on asked to the parent in that case<00:14:41.040> matokundo<00:14:41.820> is<00:14:42.060> to<00:14:42.240> say<00:14:42.480> do<00:14:42.839> you<00:14:42.959> know 00:14:43.069 --> 00:14:43.079 align:start position:0% case matokundo is to say do you know 00:14:43.079 --> 00:14:44.930 align:start position:0% case matokundo is to say do you know anything<00:14:43.260> about<00:14:43.500> your<00:14:43.740> child<00:14:43.980> then<00:14:44.699> that 00:14:44.930 --> 00:14:44.940 align:start position:0% anything about your child then that 00:14:44.940 --> 00:14:48.410 align:start position:0% anything about your child then that child<00:14:45.500> goes<00:14:46.500> to<00:14:46.560> LT<00:14:47.040> or<00:14:47.279> of<00:14:47.519> chain<00:14:47.699> and<00:14:48.240> get 00:14:48.410 --> 00:14:48.420 align:start position:0% child goes to LT or of chain and get 00:14:48.420 --> 00:14:52.490 align:start position:0% child goes to LT or of chain and get data<00:14:48.959> so<00:14:49.500> that's<00:14:50.279> how<00:14:50.639> uh<00:14:51.000> China<00:14:51.360> allows<00:14:52.320> you 00:14:52.490 --> 00:14:52.500 align:start position:0% data so that's how uh China allows you 00:14:52.500 --> 00:14:54.470 align:start position:0% data so that's how uh China allows you to<00:14:52.740> issue<00:14:53.040> subdomains<00:14:53.760> which<00:14:53.880> is<00:14:54.000> gas<00:14:54.240> free 00:14:54.470 --> 00:14:54.480 align:start position:0% to issue subdomains which is gas free 00:14:54.480 --> 00:14:59.090 align:start position:0% to issue subdomains which is gas free because<00:14:54.720> it<00:14:55.139> doesn't<00:14:55.260> exist<00:14:55.560> on<00:14:55.920> L1 00:14:59.090 --> 00:14:59.100 align:start position:0% 00:14:59.100 --> 00:15:00.710 align:start position:0% and 00:15:00.710 --> 00:15:00.720 align:start position:0% and 00:15:00.720 --> 00:15:01.970 align:start position:0% and so 00:15:01.970 --> 00:15:01.980 align:start position:0% so 00:15:01.980 --> 00:15:05.930 align:start position:0% so the<00:15:02.579> consequence<00:15:03.180> of<00:15:03.899> this<00:15:04.199> approach<00:15:04.560> is<00:15:05.100> fast 00:15:05.930 --> 00:15:05.940 align:start position:0% the consequence of this approach is fast 00:15:05.940 --> 00:15:08.689 align:start position:0% the consequence of this approach is fast so<00:15:06.540> no<00:15:06.720> unchain<00:15:07.320> event<00:15:07.620> for<00:15:08.220> issuing 00:15:08.689 --> 00:15:08.699 align:start position:0% so no unchain event for issuing 00:15:08.699 --> 00:15:12.350 align:start position:0% so no unchain event for issuing subdomain<00:15:09.240> or<00:15:09.420> records<00:15:10.019> so<00:15:10.560> quite<00:15:11.339> often<00:15:11.639> when 00:15:12.350 --> 00:15:12.360 align:start position:0% subdomain or records so quite often when 00:15:12.360 --> 00:15:14.990 align:start position:0% subdomain or records so quite often when you<00:15:12.480> build<00:15:12.899> adapts<00:15:13.740> nowadays<00:15:14.279> you<00:15:14.760> kind<00:15:14.880> of 00:15:14.990 --> 00:15:15.000 align:start position:0% you build adapts nowadays you kind of 00:15:15.000 --> 00:15:16.610 align:start position:0% you build adapts nowadays you kind of rely<00:15:15.300> heavily<00:15:15.660> on<00:15:15.839> like<00:15:16.019> something<00:15:16.380> like 00:15:16.610 --> 00:15:16.620 align:start position:0% rely heavily on like something like 00:15:16.620 --> 00:15:19.670 align:start position:0% rely heavily on like something like subgraph<00:15:17.100> to<00:15:17.420> retrieve<00:15:18.440> data<00:15:19.440> with 00:15:19.670 --> 00:15:19.680 align:start position:0% subgraph to retrieve data with 00:15:19.680 --> 00:15:23.150 align:start position:0% subgraph to retrieve data with information<00:15:20.540> uh<00:15:21.540> in<00:15:22.380> current<00:15:22.620> specification 00:15:23.150 --> 00:15:23.160 align:start position:0% information uh in current specification 00:15:23.160 --> 00:15:26.030 align:start position:0% information uh in current specification which<00:15:23.579> don't<00:15:23.880> have<00:15:24.120> that<00:15:24.300> so<00:15:24.600> in<00:15:25.199> our<00:15:25.320> case<00:15:25.620> we 00:15:26.030 --> 00:15:26.040 align:start position:0% which don't have that so in our case we 00:15:26.040 --> 00:15:27.829 align:start position:0% which don't have that so in our case we kind<00:15:26.279> of<00:15:26.399> hard<00:15:26.820> coding<00:15:27.300> like<00:15:27.480> you<00:15:27.660> know 00:15:27.829 --> 00:15:27.839 align:start position:0% kind of hard coding like you know 00:15:27.839 --> 00:15:30.290 align:start position:0% kind of hard coding like you know especially<00:15:28.620> if<00:15:28.800> you<00:15:29.040> have<00:15:29.519> done<00:15:29.760> any<00:15:29.940> coding 00:15:30.290 --> 00:15:30.300 align:start position:0% especially if you have done any coding 00:15:30.300 --> 00:15:33.410 align:start position:0% especially if you have done any coding on<00:15:30.480> the<00:15:30.600> ens<00:15:31.019> for<00:15:31.500> example<00:15:31.740> text<00:15:32.100> record<00:15:32.399> a<00:15:33.240> key 00:15:33.410 --> 00:15:33.420 align:start position:0% on the ens for example text record a key 00:15:33.420 --> 00:15:35.990 align:start position:0% on the ens for example text record a key value<00:15:33.600> store<00:15:33.899> which<00:15:34.620> key<00:15:34.860> has<00:15:35.100> been<00:15:35.279> uh<00:15:35.639> said 00:15:35.990 --> 00:15:36.000 align:start position:0% value store which key has been uh said 00:15:36.000 --> 00:15:38.150 align:start position:0% value store which key has been uh said we<00:15:36.420> actually<00:15:36.600> are<00:15:36.839> or<00:15:37.079> which<00:15:37.380> coin<00:15:37.680> type<00:15:37.800> has 00:15:38.150 --> 00:15:38.160 align:start position:0% we actually are or which coin type has 00:15:38.160 --> 00:15:41.030 align:start position:0% we actually are or which coin type has been<00:15:38.339> said<00:15:38.699> we<00:15:39.060> actually<00:15:39.360> retrieve<00:15:40.019> from 00:15:41.030 --> 00:15:41.040 align:start position:0% been said we actually retrieve from 00:15:41.040 --> 00:15:44.150 align:start position:0% been said we actually retrieve from the<00:15:41.699> subgraph<00:15:42.600> the<00:15:42.899> graph<00:15:43.139> sub<00:15:43.380> graphs<00:15:43.860> and 00:15:44.150 --> 00:15:44.160 align:start position:0% the subgraph the graph sub graphs and 00:15:44.160 --> 00:15:46.430 align:start position:0% the subgraph the graph sub graphs and because<00:15:44.519> it<00:15:44.940> the<00:15:45.420> graph<00:15:45.720> information<00:15:45.959> doesn't 00:15:46.430 --> 00:15:46.440 align:start position:0% because it the graph information doesn't 00:15:46.440 --> 00:15:49.189 align:start position:0% because it the graph information doesn't exist<00:15:46.920> we<00:15:47.760> actually<00:15:48.000> basically<00:15:48.420> hardcore<00:15:48.959> and 00:15:49.189 --> 00:15:49.199 align:start position:0% exist we actually basically hardcore and 00:15:49.199 --> 00:15:51.710 align:start position:0% exist we actually basically hardcore and if<00:15:49.320> you<00:15:49.500> look<00:15:49.620> into<00:15:49.800> the<00:15:50.160> ens<00:15:50.880> manager<00:15:51.300> and<00:15:51.540> if 00:15:51.710 --> 00:15:51.720 align:start position:0% if you look into the ens manager and if 00:15:51.720 --> 00:15:53.509 align:start position:0% if you look into the ens manager and if you<00:15:51.839> look<00:15:52.019> into<00:15:52.199> the<00:15:52.440> subdomain<00:15:52.980> of<00:15:53.220> the 00:15:53.509 --> 00:15:53.519 align:start position:0% you look into the subdomain of the 00:15:53.519 --> 00:15:57.230 align:start position:0% you look into the subdomain of the cbd.id<00:15:54.480> or<00:15:54.959> lens<00:15:55.740> or<00:15:55.860> XYZ<00:15:56.399> you<00:15:56.880> actually<00:15:57.000> see 00:15:57.230 --> 00:15:57.240 align:start position:0% cbd.id or lens or XYZ you actually see 00:15:57.240 --> 00:15:59.150 align:start position:0% cbd.id or lens or XYZ you actually see like<00:15:57.360> it<00:15:57.540> doesn't<00:15:57.660> exist<00:15:58.079> because<00:15:58.440> that<00:15:58.740> whole 00:15:59.150 --> 00:15:59.160 align:start position:0% like it doesn't exist because that whole 00:15:59.160 --> 00:16:02.870 align:start position:0% like it doesn't exist because that whole thing<00:15:59.339> doesn't<00:15:59.519> exist<00:15:59.880> on<00:16:00.060> L1<00:16:00.500> and<00:16:01.500> another 00:16:02.870 --> 00:16:02.880 align:start position:0% thing doesn't exist on L1 and another 00:16:02.880 --> 00:16:06.769 align:start position:0% thing doesn't exist on L1 and another so<00:16:03.300> this<00:16:03.480> is<00:16:03.600> specific<00:16:04.380> to<00:16:04.860> the<00:16:05.220> uh<00:16:06.000> the<00:16:06.300> ccip 00:16:06.769 --> 00:16:06.779 align:start position:0% so this is specific to the uh the ccip 00:16:06.779 --> 00:16:08.810 align:start position:0% so this is specific to the uh the ccip protocol<00:16:07.260> itself<00:16:07.800> but<00:16:08.160> another<00:16:08.339> thing<00:16:08.579> what 00:16:08.810 --> 00:16:08.820 align:start position:0% protocol itself but another thing what 00:16:08.820 --> 00:16:10.610 align:start position:0% protocol itself but another thing what we<00:16:09.000> are<00:16:09.120> doing<00:16:09.240> right<00:16:09.540> now<00:16:09.720> is<00:16:09.899> it's<00:16:10.320> actually 00:16:10.610 --> 00:16:10.620 align:start position:0% we are doing right now is it's actually 00:16:10.620 --> 00:16:11.750 align:start position:0% we are doing right now is it's actually kind<00:16:10.920> of 00:16:11.750 --> 00:16:11.760 align:start position:0% kind of 00:16:11.760 --> 00:16:14.810 align:start position:0% kind of halfway<00:16:12.540> through<00:16:12.720> going<00:16:13.199> to<00:16:13.380> our<00:16:13.680> what<00:16:14.579> we 00:16:14.810 --> 00:16:14.820 align:start position:0% halfway through going to our what we 00:16:14.820 --> 00:16:16.790 align:start position:0% halfway through going to our what we really<00:16:15.000> want<00:16:15.240> to<00:16:15.360> do<00:16:15.480> and<00:16:15.899> currently<00:16:16.380> because 00:16:16.790 --> 00:16:16.800 align:start position:0% really want to do and currently because 00:16:16.800 --> 00:16:19.129 align:start position:0% really want to do and currently because we<00:16:17.339> are<00:16:17.459> rely<00:16:17.820> on<00:16:18.000> this<00:16:18.240> kind<00:16:18.420> of<00:16:18.600> centralized 00:16:19.129 --> 00:16:19.139 align:start position:0% we are rely on this kind of centralized 00:16:19.139 --> 00:16:22.910 align:start position:0% we are rely on this kind of centralized Gateway<00:16:19.800> model<00:16:20.459> to<00:16:21.360> sign<00:16:21.600> the<00:16:21.839> keys<00:16:22.139> so<00:16:22.440> if<00:16:22.740> you 00:16:22.910 --> 00:16:22.920 align:start position:0% Gateway model to sign the keys so if you 00:16:22.920 --> 00:16:26.930 align:start position:0% Gateway model to sign the keys so if you find<00:16:23.459> a<00:16:23.820> key<00:16:24.120> which<00:16:24.660> Gateway<00:16:25.199> is<00:16:25.920> has<00:16:26.639> is 00:16:26.930 --> 00:16:26.940 align:start position:0% find a key which Gateway is has is 00:16:26.940 --> 00:16:30.050 align:start position:0% find a key which Gateway is has is compromised<00:16:27.980> the<00:16:28.980> Mauritius<00:16:29.459> actor<00:16:29.880> could 00:16:30.050 --> 00:16:30.060 align:start position:0% compromised the Mauritius actor could 00:16:30.060 --> 00:16:32.689 align:start position:0% compromised the Mauritius actor could potentially<00:16:30.560> basically<00:16:31.560> we<00:16:32.100> point<00:16:32.220> all<00:16:32.519> the 00:16:32.689 --> 00:16:32.699 align:start position:0% potentially basically we point all the 00:16:32.699 --> 00:16:35.930 align:start position:0% potentially basically we point all the sub<00:16:33.060> domain<00:16:33.480> address<00:16:33.660> to<00:16:34.019> my<00:16:34.860> address<00:16:34.980> so<00:16:35.639> they 00:16:35.930 --> 00:16:35.940 align:start position:0% sub domain address to my address so they 00:16:35.940 --> 00:16:38.350 align:start position:0% sub domain address to my address so they all<00:16:36.180> the<00:16:36.360> money<00:16:36.480> so 00:16:38.350 --> 00:16:38.360 align:start position:0% all the money so 00:16:38.360 --> 00:16:41.210 align:start position:0% all the money so protecting<00:16:39.360> the<00:16:39.540> Gateway<00:16:39.899> it<00:16:40.560> has<00:16:40.860> some 00:16:41.210 --> 00:16:41.220 align:start position:0% protecting the Gateway it has some 00:16:41.220 --> 00:16:44.090 align:start position:0% protecting the Gateway it has some security<00:16:41.459> concern<00:16:42.120> and<00:16:42.540> for<00:16:42.779> that<00:16:42.959> reason<00:16:43.199> if 00:16:44.090 --> 00:16:44.100 align:start position:0% security concern and for that reason if 00:16:44.100 --> 00:16:46.189 align:start position:0% security concern and for that reason if you<00:16:44.339> have<00:16:44.699> a<00:16:44.820> gate<00:16:45.000> where<00:16:45.240> you<00:16:45.540> you<00:16:45.779> have<00:16:46.019> to 00:16:46.189 --> 00:16:46.199 align:start position:0% you have a gate where you you have to 00:16:46.199 --> 00:16:48.230 align:start position:0% you have a gate where you you have to deploy<00:16:46.500> Gateway<00:16:46.920> by<00:16:47.160> yourself<00:16:47.399> you<00:16:47.880> can't<00:16:48.000> let 00:16:48.230 --> 00:16:48.240 align:start position:0% deploy Gateway by yourself you can't let 00:16:48.240 --> 00:16:50.210 align:start position:0% deploy Gateway by yourself you can't let other<00:16:48.420> people<00:16:48.600> to<00:16:48.839> deploy<00:16:49.259> it<00:16:49.440> Gateway<00:16:50.040> and 00:16:50.210 --> 00:16:50.220 align:start position:0% other people to deploy it Gateway and 00:16:50.220 --> 00:16:51.590 align:start position:0% other people to deploy it Gateway and use<00:16:50.459> their<00:16:50.699> own<00:16:50.880> so<00:16:51.120> that's<00:16:51.240> kind<00:16:51.480> of 00:16:51.590 --> 00:16:51.600 align:start position:0% use their own so that's kind of 00:16:51.600 --> 00:16:54.590 align:start position:0% use their own so that's kind of limitation<00:16:52.019> current<00:16:52.440> approach<00:16:52.920> however<00:16:53.759> it 00:16:54.590 --> 00:16:54.600 align:start position:0% limitation current approach however it 00:16:54.600 --> 00:16:57.769 align:start position:0% limitation current approach however it it's<00:16:55.259> here<00:16:55.560> and<00:16:55.800> it's<00:16:55.980> working<00:16:56.220> so<00:16:56.940> another 00:16:57.769 --> 00:16:57.779 align:start position:0% it's here and it's working so another 00:16:57.779 --> 00:17:00.110 align:start position:0% it's here and it's working so another uh<00:16:58.259> photo<00:16:58.500> time<00:16:58.800> is<00:16:59.040> that<00:16:59.220> if<00:16:59.519> you<00:16:59.639> want<00:16:59.820> to<00:16:59.940> try 00:17:00.110 --> 00:17:00.120 align:start position:0% uh photo time is that if you want to try 00:17:00.120 --> 00:17:02.689 align:start position:0% uh photo time is that if you want to try out<00:17:00.360> this<00:17:00.660> approach<00:17:00.959> into<00:17:01.259> uad<00:17:01.740> app<00:17:01.920> this<00:17:02.519> is<00:17:02.579> a 00:17:02.689 --> 00:17:02.699 align:start position:0% out this approach into uad app this is a 00:17:02.699 --> 00:17:05.929 align:start position:0% out this approach into uad app this is a QR<00:17:03.000> code<00:17:03.180> to<00:17:03.540> take<00:17:04.199> a<00:17:04.380> photo<00:17:04.559> with<00:17:05.160> me<00:17:05.459> smiling 00:17:05.929 --> 00:17:05.939 align:start position:0% QR code to take a photo with me smiling 00:17:05.939 --> 00:17:09.230 align:start position:0% QR code to take a photo with me smiling thank<00:17:06.419> you<00:17:06.540> and<00:17:07.140> so<00:17:07.319> what's<00:17:07.559> next<00:17:07.799> and<00:17:08.640> so<00:17:09.059> we 00:17:09.230 --> 00:17:09.240 align:start position:0% thank you and so what's next and so we 00:17:09.240 --> 00:17:11.030 align:start position:0% thank you and so what's next and so we are<00:17:09.480> kind<00:17:09.660> of<00:17:09.720> yeah<00:17:09.959> as<00:17:10.199> I<00:17:10.380> said<00:17:10.559> it's<00:17:10.740> kind<00:17:10.919> of 00:17:11.030 --> 00:17:11.040 align:start position:0% are kind of yeah as I said it's kind of 00:17:11.040 --> 00:17:14.270 align:start position:0% are kind of yeah as I said it's kind of halfway<00:17:11.400> and<00:17:12.360> so<00:17:13.020> we<00:17:13.140> did<00:17:13.380> the<00:17:13.559> off-chain<00:17:13.980> data 00:17:14.270 --> 00:17:14.280 align:start position:0% halfway and so we did the off-chain data 00:17:14.280 --> 00:17:16.909 align:start position:0% halfway and so we did the off-chain data retrieval<00:17:14.819> ticked<00:17:15.660> and<00:17:16.079> basic<00:17:16.380> library<00:17:16.559> and 00:17:16.909 --> 00:17:16.919 align:start position:0% retrieval ticked and basic library and 00:17:16.919 --> 00:17:19.789 align:start position:0% retrieval ticked and basic library and wallets<00:17:17.339> integrated<00:17:17.880> checked<00:17:18.839> and<00:17:19.439> so 00:17:19.789 --> 00:17:19.799 align:start position:0% wallets integrated checked and so 00:17:19.799 --> 00:17:21.949 align:start position:0% wallets integrated checked and so there's<00:17:20.280> three<00:17:20.579> other<00:17:20.819> things<00:17:21.059> we<00:17:21.660> kind<00:17:21.839> of 00:17:21.949 --> 00:17:21.959 align:start position:0% there's three other things we kind of 00:17:21.959 --> 00:17:24.770 align:start position:0% there's three other things we kind of have<00:17:22.079> to<00:17:22.260> solve<00:17:22.620> to<00:17:22.799> to<00:17:23.579> go<00:17:24.179> to<00:17:24.360> where<00:17:24.600> we 00:17:24.770 --> 00:17:24.780 align:start position:0% have to solve to to go to where we 00:17:24.780 --> 00:17:27.590 align:start position:0% have to solve to to go to where we really<00:17:25.020> want<00:17:25.260> to<00:17:25.439> achieve<00:17:25.919> go<00:17:26.339> and<00:17:27.240> the<00:17:27.419> first 00:17:27.590 --> 00:17:27.600 align:start position:0% really want to achieve go and the first 00:17:27.600 --> 00:17:29.930 align:start position:0% really want to achieve go and the first thing<00:17:27.839> is<00:17:28.020> I<00:17:28.559> call<00:17:28.740> CC 00:17:29.930 --> 00:17:29.940 align:start position:0% thing is I call CC 00:17:29.940 --> 00:17:35.930 align:start position:0% thing is I call CC sorry<00:17:30.480> a<00:17:31.160> ccwdp<00:17:32.160> AKA<00:17:33.440> eip559<00:17:34.440> is<00:17:34.919> called<00:17:35.220> cross 00:17:35.930 --> 00:17:35.940 align:start position:0% sorry a ccwdp AKA eip559 is called cross 00:17:35.940 --> 00:17:39.590 align:start position:0% sorry a ccwdp AKA eip559 is called cross chain<00:17:36.299> right<00:17:37.160> deferral<00:17:38.160> protocol<00:17:38.520> but<00:17:39.179> I 00:17:39.590 --> 00:17:39.600 align:start position:0% chain right deferral protocol but I 00:17:39.600 --> 00:17:42.710 align:start position:0% chain right deferral protocol but I think<00:17:39.720> it's<00:17:39.900> the<00:17:40.260> joint<00:17:40.740> uh<00:17:41.400> EIP<00:17:42.179> with<00:17:42.480> I<00:17:42.660> think 00:17:42.710 --> 00:17:42.720 align:start position:0% think it's the joint uh EIP with I think 00:17:42.720 --> 00:17:44.810 align:start position:0% think it's the joint uh EIP with I think coinbase<00:17:43.140> and<00:17:43.320> then<00:17:43.559> Nick<00:17:43.799> Johnson<00:17:44.039> I<00:17:44.700> think 00:17:44.810 --> 00:17:44.820 align:start position:0% coinbase and then Nick Johnson I think 00:17:44.820 --> 00:17:50.029 align:start position:0% coinbase and then Nick Johnson I think is<00:17:45.620> basically<00:17:46.620> so<00:17:46.980> far<00:17:47.220> you<00:17:47.880> saw<00:17:48.539> that<00:17:48.900> uh<00:17:49.679> all 00:17:50.029 --> 00:17:50.039 align:start position:0% is basically so far you saw that uh all 00:17:50.039 --> 00:17:52.070 align:start position:0% is basically so far you saw that uh all the<00:17:50.220> data<00:17:50.520> can<00:17:50.820> be<00:17:51.000> retrieved 00:17:52.070 --> 00:17:52.080 align:start position:0% the data can be retrieved 00:17:52.080 --> 00:17:55.010 align:start position:0% the data can be retrieved on<00:17:52.620> L1<00:17:52.980> so<00:17:53.280> that<00:17:53.520> you<00:17:54.360> don't<00:17:54.419> need<00:17:54.660> to<00:17:54.840> switch 00:17:55.010 --> 00:17:55.020 align:start position:0% on L1 so that you don't need to switch 00:17:55.020 --> 00:17:58.730 align:start position:0% on L1 so that you don't need to switch Network<00:17:55.580> to<00:17:56.580> read<00:17:57.000> the<00:17:57.240> data<00:17:57.660> but 00:17:58.730 --> 00:17:58.740 align:start position:0% Network to read the data but 00:17:58.740 --> 00:18:02.090 align:start position:0% Network to read the data but once<00:17:59.880> the<00:18:00.539> next<00:18:00.600> step<00:18:00.840> is<00:18:01.140> actually<00:18:01.440> you<00:18:01.860> want 00:18:02.090 --> 00:18:02.100 align:start position:0% once the next step is actually you want 00:18:02.100 --> 00:18:05.450 align:start position:0% once the next step is actually you want to<00:18:02.220> let<00:18:02.580> users<00:18:03.179> to<00:18:03.720> update<00:18:04.320> the<00:18:04.559> data<00:18:04.919> and 00:18:05.450 --> 00:18:05.460 align:start position:0% to let users to update the data and 00:18:05.460 --> 00:18:08.990 align:start position:0% to let users to update the data and currently<00:18:06.000> I<00:18:06.600> think<00:18:06.780> uh<00:18:07.400> in<00:18:08.400> case<00:18:08.520> of<00:18:08.700> lens 00:18:08.990 --> 00:18:09.000 align:start position:0% currently I think uh in case of lens 00:18:09.000 --> 00:18:11.810 align:start position:0% currently I think uh in case of lens lens<00:18:09.419> have<00:18:09.660> its<00:18:09.960> own<00:18:10.020> interpersonal<00:18:10.740> L2<00:18:11.580> so 00:18:11.810 --> 00:18:11.820 align:start position:0% lens have its own interpersonal L2 so 00:18:11.820 --> 00:18:13.850 align:start position:0% lens have its own interpersonal L2 so like<00:18:12.059> you<00:18:12.780> have<00:18:12.900> to<00:18:13.020> know<00:18:13.200> that<00:18:13.380> you<00:18:13.620> have<00:18:13.740> to 00:18:13.850 --> 00:18:13.860 align:start position:0% like you have to know that you have to 00:18:13.860 --> 00:18:16.430 align:start position:0% like you have to know that you have to update<00:18:14.160> on<00:18:14.400> lens<00:18:14.640> in<00:18:15.360> case<00:18:15.600> of<00:18:15.780> a<00:18:15.840> coinbase<00:18:16.200> you 00:18:16.430 --> 00:18:16.440 align:start position:0% update on lens in case of a coinbase you 00:18:16.440 --> 00:18:17.930 align:start position:0% update on lens in case of a coinbase you have<00:18:16.620> to<00:18:16.740> know<00:18:17.039> that<00:18:17.160> you<00:18:17.340> have<00:18:17.400> to<00:18:17.520> do<00:18:17.640> in<00:18:17.820> a 00:18:17.930 --> 00:18:17.940 align:start position:0% have to know that you have to do in a 00:18:17.940 --> 00:18:20.930 align:start position:0% have to know that you have to do in a coinbase<00:18:18.360> uh<00:18:18.780> basically<00:18:19.320> extension<00:18:20.220> but<00:18:20.700> this 00:18:20.930 --> 00:18:20.940 align:start position:0% coinbase uh basically extension but this 00:18:20.940 --> 00:18:23.270 align:start position:0% coinbase uh basically extension but this one<00:18:21.120> kind<00:18:21.360> of<00:18:21.539> uses<00:18:22.320> similar<00:18:22.679> approach<00:18:23.100> to 00:18:23.270 --> 00:18:23.280 align:start position:0% one kind of uses similar approach to 00:18:23.280 --> 00:18:27.049 align:start position:0% one kind of uses similar approach to ccip<00:18:24.000> reads<00:18:24.660> to<00:18:25.320> return<00:18:25.559> the<00:18:25.860> like<00:18:26.220> where 00:18:27.049 --> 00:18:27.059 align:start position:0% ccip reads to return the like where 00:18:27.059 --> 00:18:29.510 align:start position:0% ccip reads to return the like where uh<00:18:27.720> you<00:18:27.900> need<00:18:28.140> to<00:18:28.260> kind<00:18:28.559> of<00:18:28.679> be<00:18:28.860> points<00:18:29.280> to<00:18:29.400> your 00:18:29.510 --> 00:18:29.520 align:start position:0% uh you need to kind of be points to your 00:18:29.520 --> 00:18:31.850 align:start position:0% uh you need to kind of be points to your end<00:18:29.820> point<00:18:30.059> or<00:18:30.360> like<00:18:30.539> a<00:18:30.720> URL<00:18:31.140> to<00:18:31.380> update<00:18:31.740> the 00:18:31.850 --> 00:18:31.860 align:start position:0% end point or like a URL to update the 00:18:31.860 --> 00:18:34.909 align:start position:0% end point or like a URL to update the data<00:18:32.220> so<00:18:32.340> this<00:18:32.640> is<00:18:32.880> kind<00:18:33.240> of<00:18:33.419> fresh<00:18:33.900> oh<00:18:34.500> no<00:18:34.740> it's 00:18:34.909 --> 00:18:34.919 align:start position:0% data so this is kind of fresh oh no it's 00:18:34.919 --> 00:18:36.950 align:start position:0% data so this is kind of fresh oh no it's June<00:18:35.340> so<00:18:35.640> it's<00:18:35.760> been<00:18:35.940> there<00:18:36.299> but<00:18:36.539> I<00:18:36.660> only<00:18:36.780> get 00:18:36.950 --> 00:18:36.960 align:start position:0% June so it's been there but I only get 00:18:36.960 --> 00:18:38.210 align:start position:0% June so it's been there but I only get to<00:18:37.080> know<00:18:37.200> like 00:18:38.210 --> 00:18:38.220 align:start position:0% to know like 00:18:38.220 --> 00:18:41.390 align:start position:0% to know like cycle<00:18:38.580> that<00:18:38.880> this<00:18:39.059> existed<00:18:39.539> so<00:18:40.260> uh<00:18:40.679> it's<00:18:40.860> fresh 00:18:41.390 --> 00:18:41.400 align:start position:0% cycle that this existed so uh it's fresh 00:18:41.400 --> 00:18:43.549 align:start position:0% cycle that this existed so uh it's fresh but<00:18:41.700> like<00:18:41.880> there's<00:18:42.539> already<00:18:42.780> draft<00:18:43.080> so<00:18:43.440> you 00:18:43.549 --> 00:18:43.559 align:start position:0% but like there's already draft so you 00:18:43.559 --> 00:18:45.710 align:start position:0% but like there's already draft so you can<00:18:43.679> take<00:18:43.860> a<00:18:43.980> look 00:18:45.710 --> 00:18:45.720 align:start position:0% can take a look 00:18:45.720 --> 00:18:48.950 align:start position:0% can take a look and<00:18:46.320> uh<00:18:46.919> next<00:18:47.160> so<00:18:47.760> yeah<00:18:48.000> trust<00:18:48.360> minimize 00:18:48.950 --> 00:18:48.960 align:start position:0% and uh next so yeah trust minimize 00:18:48.960 --> 00:18:52.430 align:start position:0% and uh next so yeah trust minimize resolver<00:18:49.860> Eco<00:18:50.280> uh<00:18:50.580> Roll-Ups<00:18:51.240> so<00:18:51.539> that<00:18:51.840> so<00:18:52.320> far 00:18:52.430 --> 00:18:52.440 align:start position:0% resolver Eco uh Roll-Ups so that so far 00:18:52.440 --> 00:18:54.049 align:start position:0% resolver Eco uh Roll-Ups so that so far I<00:18:52.679> was<00:18:52.799> talking<00:18:52.919> about<00:18:53.160> quite<00:18:53.580> kind<00:18:53.820> of 00:18:54.049 --> 00:18:54.059 align:start position:0% I was talking about quite kind of 00:18:54.059 --> 00:18:55.669 align:start position:0% I was talking about quite kind of centralized<00:18:54.600> approach<00:18:54.960> like<00:18:55.200> you<00:18:55.380> have<00:18:55.559> to 00:18:55.669 --> 00:18:55.679 align:start position:0% centralized approach like you have to 00:18:55.679 --> 00:18:57.950 align:start position:0% centralized approach like you have to trust<00:18:55.860> the<00:18:55.980> Gateway<00:18:56.400> well<00:18:57.000> we 00:18:57.950 --> 00:18:57.960 align:start position:0% trust the Gateway well we 00:18:57.960 --> 00:19:01.010 align:start position:0% trust the Gateway well we uh<00:18:58.799> have<00:18:59.100> design<00:18:59.400> is<00:18:59.820> going<00:19:00.120> uh<00:19:00.539> so<00:19:00.660> yeah<00:19:00.840> one 00:19:01.010 --> 00:19:01.020 align:start position:0% uh have design is going uh so yeah one 00:19:01.020 --> 00:19:03.289 align:start position:0% uh have design is going uh so yeah one of<00:19:01.200> the<00:19:01.320> stuff<00:19:01.440> of<00:19:01.620> the<00:19:01.799> Roll<00:19:01.919> Up<00:19:02.160> is<00:19:02.880> the<00:19:03.059> fact 00:19:03.289 --> 00:19:03.299 align:start position:0% of the stuff of the Roll Up is the fact 00:19:03.299 --> 00:19:05.510 align:start position:0% of the stuff of the Roll Up is the fact that<00:19:03.539> like<00:19:03.780> you<00:19:04.440> most<00:19:04.919> of<00:19:05.039> the<00:19:05.160> roll<00:19:05.340> up 00:19:05.510 --> 00:19:05.520 align:start position:0% that like you most of the roll up 00:19:05.520 --> 00:19:08.150 align:start position:0% that like you most of the roll up whether<00:19:05.940> it's<00:19:06.120> a<00:19:06.360> kind<00:19:06.660> of<00:19:06.900> uh<00:19:07.320> optimistic<00:19:07.980> or 00:19:08.150 --> 00:19:08.160 align:start position:0% whether it's a kind of uh optimistic or 00:19:08.160 --> 00:19:10.669 align:start position:0% whether it's a kind of uh optimistic or DK<00:19:08.700> that<00:19:09.360> their<00:19:09.600> basic<00:19:09.900> principle<00:19:10.260> is<00:19:10.500> to 00:19:10.669 --> 00:19:10.679 align:start position:0% DK that their basic principle is to 00:19:10.679 --> 00:19:14.090 align:start position:0% DK that their basic principle is to batch<00:19:10.919> right<00:19:11.220> uh<00:19:11.880> L2<00:19:12.240> data<00:19:12.600> to<00:19:13.100> periodically 00:19:14.090 --> 00:19:14.100 align:start position:0% batch right uh L2 data to periodically 00:19:14.100 --> 00:19:17.450 align:start position:0% batch right uh L2 data to periodically in<00:19:14.520> a<00:19:14.640> battery<00:19:14.820> data<00:19:15.419> into<00:19:15.600> L1<00:19:16.140> that<00:19:16.860> means<00:19:17.100> you 00:19:17.450 --> 00:19:17.460 align:start position:0% in a battery data into L1 that means you 00:19:17.460 --> 00:19:20.029 align:start position:0% in a battery data into L1 that means you can<00:19:17.640> actually<00:19:17.880> uh<00:19:18.419> verify<00:19:19.020> the<00:19:19.260> state<00:19:19.440> or<00:19:19.620> belt 00:19:20.029 --> 00:19:20.039 align:start position:0% can actually uh verify the state or belt 00:19:20.039 --> 00:19:24.169 align:start position:0% can actually uh verify the state or belt too<00:19:20.160> on<00:19:20.460> L1<00:19:20.880> using<00:19:21.240> L1<00:19:21.600> Contra<00:19:22.140> uh<00:19:22.860> so<00:19:23.640> yeah 00:19:24.169 --> 00:19:24.179 align:start position:0% too on L1 using L1 Contra uh so yeah 00:19:24.179 --> 00:19:26.930 align:start position:0% too on L1 using L1 Contra uh so yeah optimistic<00:19:24.900> uh<00:19:25.320> roll<00:19:25.799> up<00:19:26.039> uses<00:19:26.340> Cloud<00:19:26.640> proof 00:19:26.930 --> 00:19:26.940 align:start position:0% optimistic uh roll up uses Cloud proof 00:19:26.940 --> 00:19:30.230 align:start position:0% optimistic uh roll up uses Cloud proof and<00:19:27.120> a<00:19:27.360> DK<00:19:27.840> user<00:19:28.140> validity<00:19:28.500> proof<00:19:28.919> and<00:19:29.580> once 00:19:30.230 --> 00:19:30.240 align:start position:0% and a DK user validity proof and once 00:19:30.240 --> 00:19:34.190 align:start position:0% and a DK user validity proof and once and<00:19:31.140> my<00:19:31.860> understanding<00:19:32.340> is<00:19:32.580> that<00:19:32.880> uh<00:19:33.660> optimism 00:19:34.190 --> 00:19:34.200 align:start position:0% and my understanding is that uh optimism 00:19:34.200 --> 00:19:36.470 align:start position:0% and my understanding is that uh optimism or<00:19:34.559> like<00:19:34.799> stock<00:19:35.039> where<00:19:35.340> all<00:19:35.640> these<00:19:35.940> companies 00:19:36.470 --> 00:19:36.480 align:start position:0% or like stock where all these companies 00:19:36.480 --> 00:19:38.630 align:start position:0% or like stock where all these companies listed<00:19:36.900> they<00:19:37.140> do<00:19:37.260> have<00:19:37.440> a<00:19:37.559> basic<00:19:37.860> function<00:19:38.160> so 00:19:38.630 --> 00:19:38.640 align:start position:0% listed they do have a basic function so 00:19:38.640 --> 00:19:40.789 align:start position:0% listed they do have a basic function so once<00:19:39.000> we<00:19:39.120> have<00:19:39.299> that<00:19:39.539> function<00:19:39.960> what<00:19:40.620> we're 00:19:40.789 --> 00:19:40.799 align:start position:0% once we have that function what we're 00:19:40.799 --> 00:19:42.409 align:start position:0% once we have that function what we're gonna<00:19:40.919> do<00:19:41.460> I<00:19:41.640> explain 00:19:42.409 --> 00:19:42.419 align:start position:0% gonna do I explain 00:19:42.419 --> 00:19:46.490 align:start position:0% gonna do I explain how<00:19:42.840> do<00:19:43.020> I<00:19:43.200> here<00:19:43.740> so<00:19:44.640> here<00:19:44.880> it's<00:19:45.660> uh<00:19:46.140> just<00:19:46.380> like 00:19:46.490 --> 00:19:46.500 align:start position:0% how do I here so here it's uh just like 00:19:46.500 --> 00:19:50.150 align:start position:0% how do I here so here it's uh just like retrieving<00:19:47.160> the<00:19:47.280> data<00:19:47.760> and<00:19:48.179> signing<00:19:48.600> the<00:19:48.840> uh 00:19:50.150 --> 00:19:50.160 align:start position:0% retrieving the data and signing the uh 00:19:50.160 --> 00:19:53.090 align:start position:0% retrieving the data and signing the uh message<00:19:50.820> but<00:19:51.240> what<00:19:51.539> you<00:19:51.720> can<00:19:51.840> do<00:19:52.080> on<00:19:52.500> the<00:19:52.679> L2 00:19:53.090 --> 00:19:53.100 align:start position:0% message but what you can do on the L2 00:19:53.100 --> 00:19:55.310 align:start position:0% message but what you can do on the L2 rollup<00:19:53.520> is<00:19:53.640> like<00:19:53.820> you<00:19:54.120> can<00:19:54.240> get<00:19:54.480> basically<00:19:55.020> get 00:19:55.310 --> 00:19:55.320 align:start position:0% rollup is like you can get basically get 00:19:55.320 --> 00:19:59.029 align:start position:0% rollup is like you can get basically get the<00:19:55.559> proof<00:19:55.919> data<00:19:56.640> with<00:19:56.760> the<00:19:56.940> proof<00:19:57.240> and<00:19:58.039> uh 00:19:59.029 --> 00:19:59.039 align:start position:0% the proof data with the proof and uh 00:19:59.039 --> 00:20:03.409 align:start position:0% the proof data with the proof and uh yeah<00:19:59.460> you<00:19:59.700> construct<00:20:00.240> the<00:20:00.480> Marco<00:20:01.039> R3<00:20:02.039> and<00:20:02.580> on 00:20:03.409 --> 00:20:03.419 align:start position:0% yeah you construct the Marco R3 and on 00:20:03.419 --> 00:20:06.470 align:start position:0% yeah you construct the Marco R3 and on this<00:20:03.960> uh<00:20:04.559> verify<00:20:05.160> station<00:20:05.460> on<00:20:05.820> a<00:20:06.179> smart 00:20:06.470 --> 00:20:06.480 align:start position:0% this uh verify station on a smart 00:20:06.480 --> 00:20:09.830 align:start position:0% this uh verify station on a smart contract<00:20:06.960> you<00:20:07.500> can<00:20:07.620> basically<00:20:08.039> call<00:20:08.340> uh<00:20:09.059> I 00:20:09.830 --> 00:20:09.840 align:start position:0% contract you can basically call uh I 00:20:09.840 --> 00:20:12.409 align:start position:0% contract you can basically call uh I forgot<00:20:10.080> the<00:20:10.320> name<00:20:10.559> of<00:20:10.919> the<00:20:11.160> optimism<00:20:11.940> code<00:20:12.179> do 00:20:12.409 --> 00:20:12.419 align:start position:0% forgot the name of the optimism code do 00:20:12.419 --> 00:20:15.230 align:start position:0% forgot the name of the optimism code do you<00:20:12.539> remember<00:20:12.660> verify 00:20:15.230 --> 00:20:15.240 align:start position:0% you remember verify 00:20:15.240 --> 00:20:19.549 align:start position:0% you remember verify was<00:20:15.900> State<00:20:16.200> commitment<00:20:16.860> something<00:20:18.260> called<00:20:19.260> a 00:20:19.549 --> 00:20:19.559 align:start position:0% was State commitment something called a 00:20:19.559 --> 00:20:22.070 align:start position:0% was State commitment something called a function<00:20:19.740> to<00:20:19.980> verify<00:20:20.400> and<00:20:20.700> by<00:20:21.000> doing<00:20:21.240> the<00:20:21.660> uh 00:20:22.070 --> 00:20:22.080 align:start position:0% function to verify and by doing the uh 00:20:22.080 --> 00:20:25.010 align:start position:0% function to verify and by doing the uh even<00:20:22.320> if<00:20:22.620> a<00:20:22.860> Gateway<00:20:23.220> returns<00:20:23.760> just<00:20:24.179> data<00:20:24.660> oh 00:20:25.010 --> 00:20:25.020 align:start position:0% even if a Gateway returns just data oh 00:20:25.020 --> 00:20:28.010 align:start position:0% even if a Gateway returns just data oh my<00:20:25.320> time<00:20:25.440> is<00:20:25.500> already<00:20:25.679> up<00:20:25.980> okay<00:20:26.280> uh 00:20:28.010 --> 00:20:28.020 align:start position:0% my time is already up okay uh 00:20:28.020 --> 00:20:30.710 align:start position:0% my time is already up okay uh you<00:20:28.679> can<00:20:28.860> uh<00:20:29.520> you<00:20:29.880> don't<00:20:30.000> have<00:20:30.120> to<00:20:30.240> trust<00:20:30.480> so 00:20:30.710 --> 00:20:30.720 align:start position:0% you can uh you don't have to trust so 00:20:30.720 --> 00:20:33.049 align:start position:0% you can uh you don't have to trust so that's<00:20:30.960> are<00:20:31.320> you<00:20:31.500> gonna<00:20:31.620> it's<00:20:32.400> a<00:20:32.580> complete<00:20:32.880> app 00:20:33.049 --> 00:20:33.059 align:start position:0% that's are you gonna it's a complete app 00:20:33.059 --> 00:20:37.430 align:start position:0% that's are you gonna it's a complete app of<00:20:33.240> another<00:20:33.419> five<00:20:33.720> minutes<00:20:34.280> okay<00:20:35.280> so<00:20:35.520> uh 00:20:37.430 --> 00:20:37.440 align:start position:0% of another five minutes okay so uh 00:20:37.440 --> 00:20:40.130 align:start position:0% of another five minutes okay so uh I<00:20:37.860> think<00:20:37.980> I<00:20:38.160> already<00:20:38.280> mentioned 00:20:40.130 --> 00:20:40.140 align:start position:0% I think I already mentioned 00:20:40.140 --> 00:20:42.049 align:start position:0% I think I already mentioned and<00:20:40.679> there's<00:20:40.860> a<00:20:41.100> demo<00:20:41.280> which<00:20:41.460> we<00:20:41.640> did<00:20:41.820> two 00:20:42.049 --> 00:20:42.059 align:start position:0% and there's a demo which we did two 00:20:42.059 --> 00:20:44.029 align:start position:0% and there's a demo which we did two years<00:20:42.179> ago<00:20:42.419> for<00:20:42.720> the<00:20:42.900> optimism<00:20:43.380> so<00:20:43.679> optimism 00:20:44.029 --> 00:20:44.039 align:start position:0% years ago for the optimism so optimism 00:20:44.039 --> 00:20:46.250 align:start position:0% years ago for the optimism so optimism we<00:20:44.340> know<00:20:44.460> like<00:20:44.640> how<00:20:44.940> it<00:20:45.059> works<00:20:45.360> and<00:20:45.780> we<00:20:46.080> are 00:20:46.250 --> 00:20:46.260 align:start position:0% we know like how it works and we are 00:20:46.260 --> 00:20:47.690 align:start position:0% we know like how it works and we are right<00:20:46.440> in<00:20:46.620> the<00:20:46.740> middle<00:20:46.799> of<00:20:46.919> updating<00:20:47.340> to<00:20:47.580> the 00:20:47.690 --> 00:20:47.700 align:start position:0% right in the middle of updating to the 00:20:47.700 --> 00:20:51.710 align:start position:0% right in the middle of updating to the latest<00:20:47.940> version<00:20:48.860> and<00:20:50.000> yeah<00:20:51.000> I'll<00:20:51.179> skip<00:20:51.419> that 00:20:51.710 --> 00:20:51.720 align:start position:0% latest version and yeah I'll skip that 00:20:51.720 --> 00:20:54.350 align:start position:0% latest version and yeah I'll skip that order<00:20:52.080> and<00:20:52.440> all<00:20:53.220> the<00:20:53.340> end<00:20:53.460> you<00:20:53.880> know<00:20:54.000> this<00:20:54.179> now 00:20:54.350 --> 00:20:54.360 align:start position:0% order and all the end you know this now 00:20:54.360 --> 00:20:57.529 align:start position:0% order and all the end you know this now YouTube<00:20:54.720> my<00:20:55.320> old<00:20:55.740> photo<00:20:55.980> so<00:20:56.220> sorry<00:20:56.580> so<00:20:57.059> the<00:20:57.240> QR 00:20:57.529 --> 00:20:57.539 align:start position:0% YouTube my old photo so sorry so the QR 00:20:57.539 --> 00:20:59.690 align:start position:0% YouTube my old photo so sorry so the QR code<00:20:57.660> so<00:20:57.900> you<00:20:58.080> should<00:20:58.260> refer<00:20:58.919> to<00:20:59.039> and<00:20:59.340> the<00:20:59.460> more 00:20:59.690 --> 00:20:59.700 align:start position:0% code so you should refer to and the more 00:20:59.700 --> 00:21:01.730 align:start position:0% code so you should refer to and the more important<00:21:00.059> things<00:21:00.299> is<00:21:00.840> yeah<00:21:01.260> we<00:21:01.440> have<00:21:01.559> a<00:21:01.679> set 00:21:01.730 --> 00:21:01.740 align:start position:0% important things is yeah we have a set 00:21:01.740 --> 00:21:05.630 align:start position:0% important things is yeah we have a set of<00:21:01.919> ens<00:21:02.400> by<00:21:02.640> Nick<00:21:02.820> Johnson<00:21:03.059> for<00:21:03.799> salty<00:21:04.799> uh<00:21:05.460> so 00:21:05.630 --> 00:21:05.640 align:start position:0% of ens by Nick Johnson for salty uh so 00:21:05.640 --> 00:21:08.299 align:start position:0% of ens by Nick Johnson for salty uh so yeah<00:21:05.880> that's<00:21:06.120> it