WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:14.549 align:start position:0% [Music] 00:00:14.549 --> 00:00:14.559 align:start position:0% 00:00:14.559 --> 00:00:17.310 align:start position:0% he<00:00:15.559> sorry<00:00:16.039> about 00:00:17.310 --> 00:00:17.320 align:start position:0% he sorry about 00:00:17.320 --> 00:00:19.870 align:start position:0% he sorry about this<00:00:18.320> okay<00:00:18.680> hello<00:00:18.960> everybody<00:00:19.480> thanks<00:00:19.680> for 00:00:19.870 --> 00:00:19.880 align:start position:0% this okay hello everybody thanks for 00:00:19.880 --> 00:00:21.630 align:start position:0% this okay hello everybody thanks for being<00:00:20.199> there<00:00:20.480> I<00:00:20.600> know<00:00:20.720> it's<00:00:20.880> the<00:00:21.000> lunch<00:00:21.279> break 00:00:21.630 --> 00:00:21.640 align:start position:0% being there I know it's the lunch break 00:00:21.640 --> 00:00:24.630 align:start position:0% being there I know it's the lunch break so<00:00:22.160> thanks<00:00:22.480> really<00:00:22.920> for<00:00:23.240> for<00:00:23.480> being<00:00:23.800> there<00:00:24.439> so 00:00:24.630 --> 00:00:24.640 align:start position:0% so thanks really for for being there so 00:00:24.640 --> 00:00:26.950 align:start position:0% so thanks really for for being there so my<00:00:24.800> name<00:00:25.000> is<00:00:25.199> arur<00:00:25.800> I'm<00:00:25.920> a<00:00:26.080> product<00:00:26.400> manager<00:00:26.800> at 00:00:26.950 --> 00:00:26.960 align:start position:0% my name is arur I'm a product manager at 00:00:26.960 --> 00:00:29.230 align:start position:0% my name is arur I'm a product manager at Linea<00:00:27.720> and<00:00:27.840> so<00:00:28.160> like<00:00:28.320> today<00:00:28.640> I<00:00:28.760> will<00:00:29.039> be 00:00:29.230 --> 00:00:29.240 align:start position:0% Linea and so like today I will be 00:00:29.240 --> 00:00:32.150 align:start position:0% Linea and so like today I will be talking<00:00:29.599> about<00:00:30.039> YC<00:00:30.439> 30 00:00:32.150 --> 00:00:32.160 align:start position:0% talking about YC 30 00:00:32.160 --> 00:00:35.549 align:start position:0% talking about YC 30 3668<00:00:33.160> um<00:00:33.879> so<00:00:34.480> yeah<00:00:34.719> let's<00:00:34.960> get<00:00:35.120> started 00:00:35.549 --> 00:00:35.559 align:start position:0% 3668 um so yeah let's get started 00:00:35.559 --> 00:00:37.430 align:start position:0% 3668 um so yeah let's get started basically<00:00:36.000> the<00:00:36.440> agenda<00:00:36.840> is<00:00:37.040> quite 00:00:37.430 --> 00:00:37.440 align:start position:0% basically the agenda is quite 00:00:37.440 --> 00:00:39.950 align:start position:0% basically the agenda is quite straightforward<00:00:38.440> I<00:00:38.520> will<00:00:38.800> explain<00:00:39.600> what<00:00:39.760> it 00:00:39.950 --> 00:00:39.960 align:start position:0% straightforward I will explain what it 00:00:39.960 --> 00:00:43.950 align:start position:0% straightforward I will explain what it is<00:00:40.719> uh<00:00:40.920> why<00:00:41.079> do<00:00:41.239> we<00:00:41.360> need<00:00:41.600> it<00:00:41.960> right<00:00:42.760> um<00:00:43.120> and<00:00:43.800> how 00:00:43.950 --> 00:00:43.960 align:start position:0% is uh why do we need it right um and how 00:00:43.960 --> 00:00:46.630 align:start position:0% is uh why do we need it right um and how does<00:00:44.239> it<00:00:44.440> work<00:00:44.920> the<00:00:45.079> use<00:00:45.399> cases<00:00:45.760> behind<00:00:46.120> it<00:00:46.399> and 00:00:46.630 --> 00:00:46.640 align:start position:0% does it work the use cases behind it and 00:00:46.640 --> 00:00:49.229 align:start position:0% does it work the use cases behind it and I<00:00:46.719> will<00:00:47.000> spend<00:00:47.320> some<00:00:47.600> time<00:00:48.399> uh<00:00:48.559> talking<00:00:48.960> about 00:00:49.229 --> 00:00:49.239 align:start position:0% I will spend some time uh talking about 00:00:49.239 --> 00:00:51.590 align:start position:0% I will spend some time uh talking about the<00:00:49.680> cool<00:00:50.039> integration<00:00:50.960> that<00:00:51.120> we<00:00:51.239> did<00:00:51.440> at 00:00:51.590 --> 00:00:51.600 align:start position:0% the cool integration that we did at 00:00:51.600 --> 00:00:56.470 align:start position:0% the cool integration that we did at linear<00:00:52.480> to<00:00:52.840> benefit<00:00:53.320> from<00:00:54.000> this<00:00:54.680> standard<00:00:55.680> so 00:00:56.470 --> 00:00:56.480 align:start position:0% linear to benefit from this standard so 00:00:56.480 --> 00:00:58.910 align:start position:0% linear to benefit from this standard so maybe<00:00:56.760> to<00:00:56.920> set<00:00:57.199> the<00:00:57.359> context<00:00:58.160> let's<00:00:58.440> just<00:00:58.680> talk 00:00:58.910 --> 00:00:58.920 align:start position:0% maybe to set the context let's just talk 00:00:58.920 --> 00:01:01.830 align:start position:0% maybe to set the context let's just talk about<00:00:59.239> how<00:00:59.440> we<00:00:59.559> can<00:01:00.039> access<00:01:00.640> external<00:01:01.160> data<00:01:01.719> I 00:01:01.830 --> 00:01:01.840 align:start position:0% about how we can access external data I 00:01:01.840 --> 00:01:04.710 align:start position:0% about how we can access external data I think<00:01:02.120> most<00:01:02.320> of<00:01:02.480> you<00:01:03.039> knows<00:01:03.480> but<00:01:04.000> natively 00:01:04.710 --> 00:01:04.720 align:start position:0% think most of you knows but natively 00:01:04.720 --> 00:01:07.429 align:start position:0% think most of you knows but natively right<00:01:04.920> a<00:01:05.080> chain<00:01:05.479> cannot<00:01:05.880> access<00:01:06.840> data<00:01:07.200> from 00:01:07.429 --> 00:01:07.439 align:start position:0% right a chain cannot access data from 00:01:07.439 --> 00:01:10.310 align:start position:0% right a chain cannot access data from the<00:01:08.040> external<00:01:08.560> World<00:01:09.200> whether<00:01:09.479> it's<00:01:09.960> over 00:01:10.310 --> 00:01:10.320 align:start position:0% the external World whether it's over 00:01:10.320 --> 00:01:13.870 align:start position:0% the external World whether it's over chains<00:01:11.240> or<00:01:11.439> the<00:01:11.680> web<00:01:12.400> but<00:01:12.799> like<00:01:13.119> over<00:01:13.400> the<00:01:13.600> time 00:01:13.870 --> 00:01:13.880 align:start position:0% chains or the web but like over the time 00:01:13.880 --> 00:01:16.990 align:start position:0% chains or the web but like over the time we<00:01:14.320> build<00:01:14.680> some<00:01:14.960> other<00:01:15.960> protocols<00:01:16.479> that<00:01:16.640> solve 00:01:16.990 --> 00:01:17.000 align:start position:0% we build some other protocols that solve 00:01:17.000 --> 00:01:19.990 align:start position:0% we build some other protocols that solve those<00:01:17.240> problems<00:01:17.799> so<00:01:18.799> the<00:01:19.200> the<00:01:19.320> main<00:01:19.560> one<00:01:19.759> are 00:01:19.990 --> 00:01:20.000 align:start position:0% those problems so the the main one are 00:01:20.000 --> 00:01:23.469 align:start position:0% those problems so the the main one are bridges<00:01:20.640> right<00:01:21.000> if<00:01:21.159> you<00:01:22.159> most<00:01:22.439> known<00:01:22.720> to<00:01:23.360> if 00:01:23.469 --> 00:01:23.479 align:start position:0% bridges right if you most known to if 00:01:23.479 --> 00:01:26.670 align:start position:0% bridges right if you most known to if you<00:01:23.560> want<00:01:23.759> to<00:01:23.960> bridge<00:01:24.360> assets<00:01:25.000> so<00:01:25.560> coins<00:01:26.040> nfts 00:01:26.670 --> 00:01:26.680 align:start position:0% you want to bridge assets so coins nfts 00:01:26.680 --> 00:01:28.830 align:start position:0% you want to bridge assets so coins nfts but<00:01:26.880> there<00:01:27.200> are<00:01:27.520> also<00:01:27.880> message<00:01:28.240> bridge<00:01:28.680> that 00:01:28.830 --> 00:01:28.840 align:start position:0% but there are also message bridge that 00:01:28.840 --> 00:01:31.990 align:start position:0% but there are also message bridge that let<00:01:29.040> you<00:01:29.439> send<00:01:29.720> a<00:01:30.000> transaction<00:01:30.560> on<00:01:30.799> chain<00:01:31.280> a 00:01:31.990 --> 00:01:32.000 align:start position:0% let you send a transaction on chain a 00:01:32.000 --> 00:01:34.950 align:start position:0% let you send a transaction on chain a and<00:01:32.280> it<00:01:32.520> execute<00:01:32.960> a<00:01:33.119> transaction<00:01:33.640> on<00:01:33.799> chain<00:01:34.119> B 00:01:34.950 --> 00:01:34.960 align:start position:0% and it execute a transaction on chain B 00:01:34.960 --> 00:01:37.630 align:start position:0% and it execute a transaction on chain B um<00:01:35.399> there<00:01:35.520> are<00:01:35.840> also<00:01:36.200> oracles<00:01:37.159> that<00:01:37.280> are<00:01:37.479> well 00:01:37.630 --> 00:01:37.640 align:start position:0% um there are also oracles that are well 00:01:37.640 --> 00:01:40.950 align:start position:0% um there are also oracles that are well known<00:01:37.960> for<00:01:38.799> like<00:01:39.280> price<00:01:39.600> feed<00:01:40.000> most<00:01:40.439> mostly 00:01:40.950 --> 00:01:40.960 align:start position:0% known for like price feed most mostly 00:01:40.960 --> 00:01:43.749 align:start position:0% known for like price feed most mostly but<00:01:41.520> most<00:01:41.759> recently<00:01:42.360> they<00:01:42.479> have<00:01:43.079> creating 00:01:43.749 --> 00:01:43.759 align:start position:0% but most recently they have creating 00:01:43.759 --> 00:01:46.429 align:start position:0% but most recently they have creating more<00:01:44.040> generalized<00:01:45.000> implementation<00:01:46.000> such<00:01:46.240> as 00:01:46.429 --> 00:01:46.439 align:start position:0% more generalized implementation such as 00:01:46.439 --> 00:01:49.270 align:start position:0% more generalized implementation such as like<00:01:46.600> chain<00:01:46.840> link<00:01:47.079> functions<00:01:47.560> and<00:01:47.759> other<00:01:48.680> and 00:01:49.270 --> 00:01:49.280 align:start position:0% like chain link functions and other and 00:01:49.280 --> 00:01:52.149 align:start position:0% like chain link functions and other and lately<00:01:49.840> we<00:01:50.000> have<00:01:50.240> also<00:01:51.079> uh<00:01:51.280> co-processors 00:01:52.149 --> 00:01:52.159 align:start position:0% lately we have also uh co-processors 00:01:52.159 --> 00:01:55.350 align:start position:0% lately we have also uh co-processors that<00:01:52.280> are<00:01:53.200> uh<00:01:53.399> enabling<00:01:54.040> those<00:01:54.240> kind<00:01:54.399> of<00:01:54.520> use 00:01:55.350 --> 00:01:55.360 align:start position:0% that are uh enabling those kind of use 00:01:55.360 --> 00:01:58.270 align:start position:0% that are uh enabling those kind of use cases<00:01:56.360> um<00:01:56.840> so<00:01:57.119> the<00:01:57.320> question<00:01:57.640> you<00:01:57.799> might<00:01:58.039> ask 00:01:58.270 --> 00:01:58.280 align:start position:0% cases um so the question you might ask 00:01:58.280 --> 00:02:01.149 align:start position:0% cases um so the question you might ask yourself<00:01:58.759> is<00:01:59.119> okay<00:01:59.360> why<00:01:59.479> do<00:01:59.640> we<00:02:00.000> need<00:02:00.680> another 00:02:01.149 --> 00:02:01.159 align:start position:0% yourself is okay why do we need another 00:02:01.159 --> 00:02:05.109 align:start position:0% yourself is okay why do we need another solution<00:02:02.159> and<00:02:02.840> basically<00:02:03.840> ERC 00:02:05.109 --> 00:02:05.119 align:start position:0% solution and basically ERC 00:02:05.119 --> 00:02:09.669 align:start position:0% solution and basically ERC 3668<00:02:06.119> uh<00:02:06.399> also<00:02:06.680> known<00:02:07.159> as<00:02:07.360> a<00:02:07.560> CCP<00:02:08.360> read<00:02:09.000> was<00:02:09.520> a 00:02:09.669 --> 00:02:09.679 align:start position:0% 3668 uh also known as a CCP read was a 00:02:09.679 --> 00:02:11.949 align:start position:0% 3668 uh also known as a CCP read was a standard<00:02:10.200> proposed<00:02:10.599> by<00:02:10.800> the<00:02:10.959> ens<00:02:11.400> team 00:02:11.949 --> 00:02:11.959 align:start position:0% standard proposed by the ens team 00:02:11.959 --> 00:02:14.790 align:start position:0% standard proposed by the ens team especially<00:02:12.440> Nick<00:02:13.280> because<00:02:13.640> they<00:02:13.800> had<00:02:14.280> like 00:02:14.790 --> 00:02:14.800 align:start position:0% especially Nick because they had like 00:02:14.800 --> 00:02:18.990 align:start position:0% especially Nick because they had like unique<00:02:15.200> use<00:02:15.560> cases<00:02:16.080> where<00:02:16.360> they<00:02:16.800> wanted<00:02:17.239> to<00:02:18.160> um 00:02:18.990 --> 00:02:19.000 align:start position:0% unique use cases where they wanted to um 00:02:19.000 --> 00:02:22.390 align:start position:0% unique use cases where they wanted to um access<00:02:20.000> um<00:02:20.599> the<00:02:20.840> information<00:02:21.400> for<00:02:21.640> L2 00:02:22.390 --> 00:02:22.400 align:start position:0% access um the information for L2 00:02:22.400 --> 00:02:25.190 align:start position:0% access um the information for L2 especially<00:02:22.879> for<00:02:23.319> managing<00:02:23.959> like<00:02:24.160> domain<00:02:24.519> name 00:02:25.190 --> 00:02:25.200 align:start position:0% especially for managing like domain name 00:02:25.200 --> 00:02:29.390 align:start position:0% especially for managing like domain name in<00:02:25.400> a<00:02:25.879> with<00:02:26.120> cheaper<00:02:26.879> like<00:02:27.080> gas<00:02:27.360> cost<00:02:28.200> but<00:02:28.840> uh 00:02:29.390 --> 00:02:29.400 align:start position:0% in a with cheaper like gas cost but uh 00:02:29.400 --> 00:02:31.750 align:start position:0% in a with cheaper like gas cost but uh the<00:02:30.319> they<00:02:30.440> have<00:02:30.599> some<00:02:30.840> constraint<00:02:31.400> and<00:02:31.560> the 00:02:31.750 --> 00:02:31.760 align:start position:0% the they have some constraint and the 00:02:31.760 --> 00:02:34.670 align:start position:0% the they have some constraint and the design<00:02:32.120> is<00:02:32.319> reflecting<00:02:32.959> that<00:02:33.560> so<00:02:34.160> the<00:02:34.319> first 00:02:34.670 --> 00:02:34.680 align:start position:0% design is reflecting that so the first 00:02:34.680 --> 00:02:37.630 align:start position:0% design is reflecting that so the first benefit<00:02:35.280> is<00:02:35.480> that<00:02:35.720> it<00:02:35.840> doesn't<00:02:36.239> require<00:02:36.760> any 00:02:37.630 --> 00:02:37.640 align:start position:0% benefit is that it doesn't require any 00:02:37.640 --> 00:02:41.309 align:start position:0% benefit is that it doesn't require any trans<00:02:38.440> transaction<00:02:39.000> to<00:02:39.319> send<00:02:39.599> on<00:02:40.319> chain 00:02:41.309 --> 00:02:41.319 align:start position:0% trans transaction to send on chain 00:02:41.319 --> 00:02:43.550 align:start position:0% trans transaction to send on chain compared<00:02:41.680> to<00:02:41.920> over<00:02:42.319> all<00:02:42.519> the<00:02:42.640> other<00:02:43.000> solutions 00:02:43.550 --> 00:02:43.560 align:start position:0% compared to over all the other solutions 00:02:43.560 --> 00:02:48.149 align:start position:0% compared to over all the other solutions that<00:02:43.800> we<00:02:44.599> mentioned<00:02:45.599> um<00:02:46.480> so<00:02:47.040> this<00:02:47.200> is<00:02:47.760> more 00:02:48.149 --> 00:02:48.159 align:start position:0% that we mentioned um so this is more 00:02:48.159 --> 00:02:50.350 align:start position:0% that we mentioned um so this is more efficient<00:02:48.599> in<00:02:48.760> a<00:02:48.959> way<00:02:49.200> if<00:02:49.319> you<00:02:49.519> don't<00:02:49.760> need<00:02:50.239> to 00:02:50.350 --> 00:02:50.360 align:start position:0% efficient in a way if you don't need to 00:02:50.360 --> 00:02:52.270 align:start position:0% efficient in a way if you don't need to store<00:02:50.680> the<00:02:50.840> data<00:02:51.080> on<00:02:51.239> chain<00:02:51.920> because<00:02:52.159> you 00:02:52.270 --> 00:02:52.280 align:start position:0% store the data on chain because you 00:02:52.280 --> 00:02:55.710 align:start position:0% store the data on chain because you don't<00:02:52.519> have<00:02:52.640> to<00:02:52.800> pay<00:02:53.000> the<00:02:53.120> gas<00:02:53.400> cost<00:02:54.280> you<00:02:55.040> also 00:02:55.710 --> 00:02:55.720 align:start position:0% don't have to pay the gas cost you also 00:02:55.720 --> 00:02:58.750 align:start position:0% don't have to pay the gas cost you also avoid<00:02:56.319> external<00:02:56.840> depend<00:02:57.800> dependency<00:02:58.440> sorry 00:02:58.750 --> 00:02:58.760 align:start position:0% avoid external depend dependency sorry 00:02:58.760 --> 00:03:01.350 align:start position:0% avoid external depend dependency sorry on<00:02:59.000> external<00:02:59.599> prod<00:02:59.840> protocols<00:03:00.800> because<00:03:01.200> it's 00:03:01.350 --> 00:03:01.360 align:start position:0% on external prod protocols because it's 00:03:01.360 --> 00:03:05.670 align:start position:0% on external prod protocols because it's an<00:03:01.560> ERC<00:03:02.280> and<00:03:02.599> it's<00:03:03.599> uh<00:03:03.879> like<00:03:04.599> B<00:03:04.840> on<00:03:05.040> top<00:03:05.280> of<00:03:05.519> the 00:03:05.670 --> 00:03:05.680 align:start position:0% an ERC and it's uh like B on top of the 00:03:05.680 --> 00:03:07.470 align:start position:0% an ERC and it's uh like B on top of the protocol<00:03:06.159> but<00:03:06.360> doesn't<00:03:06.760> have<00:03:07.239> those 00:03:07.470 --> 00:03:07.480 align:start position:0% protocol but doesn't have those 00:03:07.480 --> 00:03:10.390 align:start position:0% protocol but doesn't have those dependency<00:03:08.280> and<00:03:08.640> extern<00:03:09.480> additional<00:03:09.959> trust 00:03:10.390 --> 00:03:10.400 align:start position:0% dependency and extern additional trust 00:03:10.400 --> 00:03:14.270 align:start position:0% dependency and extern additional trust assumption<00:03:10.959> as<00:03:11.360> well<00:03:12.360> so<00:03:13.040> let<00:03:13.200> me<00:03:13.799> tell<00:03:14.000> you<00:03:14.120> a 00:03:14.270 --> 00:03:14.280 align:start position:0% assumption as well so let me tell you a 00:03:14.280 --> 00:03:16.710 align:start position:0% assumption as well so let me tell you a bit<00:03:14.480> how<00:03:14.640> it<00:03:14.799> works<00:03:15.640> there<00:03:15.840> is<00:03:15.959> three<00:03:16.280> part<00:03:16.480> to 00:03:16.710 --> 00:03:16.720 align:start position:0% bit how it works there is three part to 00:03:16.720 --> 00:03:19.589 align:start position:0% bit how it works there is three part to it<00:03:17.480> um<00:03:17.840> it<00:03:18.000> starts<00:03:18.319> with<00:03:18.480> the<00:03:18.680> client<00:03:19.239> and<00:03:19.400> here 00:03:19.589 --> 00:03:19.599 align:start position:0% it um it starts with the client and here 00:03:19.599 --> 00:03:21.830 align:start position:0% it um it starts with the client and here we<00:03:19.720> are<00:03:19.879> not<00:03:20.360> talking<00:03:20.760> about<00:03:21.200> execution 00:03:21.830 --> 00:03:21.840 align:start position:0% we are not talking about execution 00:03:21.840 --> 00:03:24.910 align:start position:0% we are not talking about execution client<00:03:22.519> or<00:03:22.760> consensus<00:03:23.319> client<00:03:23.680> but<00:03:23.879> more<00:03:24.159> like 00:03:24.910 --> 00:03:24.920 align:start position:0% client or consensus client but more like 00:03:24.920 --> 00:03:27.229 align:start position:0% client or consensus client but more like the<00:03:25.080> uis<00:03:25.760> or<00:03:26.080> like<00:03:26.280> backends<00:03:26.840> that<00:03:27.000> are 00:03:27.229 --> 00:03:27.239 align:start position:0% the uis or like backends that are 00:03:27.239 --> 00:03:30.630 align:start position:0% the uis or like backends that are calling<00:03:27.760> the<00:03:28.080> the<00:03:28.280> blockchain<00:03:29.280> and<00:03:30.040> uh<00:03:30.439> like 00:03:30.630 --> 00:03:30.640 align:start position:0% calling the the blockchain and uh like 00:03:30.640 --> 00:03:34.350 align:start position:0% calling the the blockchain and uh like the<00:03:30.840> client<00:03:31.480> will<00:03:31.920> uh<00:03:32.319> call<00:03:33.239> a<00:03:33.400> smart<00:03:33.720> contract 00:03:34.350 --> 00:03:34.360 align:start position:0% the client will uh call a smart contract 00:03:34.360 --> 00:03:37.949 align:start position:0% the client will uh call a smart contract right<00:03:35.000> standard<00:03:35.439> if<00:03:35.720> call<00:03:36.319> to<00:03:36.680> to<00:03:36.920> get<00:03:37.480> some 00:03:37.949 --> 00:03:37.959 align:start position:0% right standard if call to to get some 00:03:37.959 --> 00:03:40.229 align:start position:0% right standard if call to to get some information<00:03:38.959> uh<00:03:39.239> something<00:03:39.640> that<00:03:39.799> happens 00:03:40.229 --> 00:03:40.239 align:start position:0% information uh something that happens 00:03:40.239 --> 00:03:45.350 align:start position:0% information uh something that happens quite<00:03:41.040> generally<00:03:41.959> and<00:03:42.920> the<00:03:43.439> main<00:03:44.239> um<00:03:45.000> part<00:03:45.200> of 00:03:45.350 --> 00:03:45.360 align:start position:0% quite generally and the main um part of 00:03:45.360 --> 00:03:50.110 align:start position:0% quite generally and the main um part of the<00:03:45.480> design<00:03:45.959> from<00:03:46.439> ERC<00:03:47.239> 4668<00:03:48.239> is<00:03:48.480> this<00:03:49.360> uh 00:03:50.110 --> 00:03:50.120 align:start position:0% the design from ERC 4668 is this uh 00:03:50.120 --> 00:03:53.429 align:start position:0% the design from ERC 4668 is this uh allows<00:03:50.640> the<00:03:50.959> contract<00:03:51.720> to<00:03:52.439> revert<00:03:53.000> with<00:03:53.159> an 00:03:53.429 --> 00:03:53.439 align:start position:0% allows the contract to revert with an 00:03:53.439 --> 00:03:55.949 align:start position:0% allows the contract to revert with an error<00:03:53.920> that's<00:03:54.319> basically<00:03:54.760> tell<00:03:55.000> the<00:03:55.159> client 00:03:55.949 --> 00:03:55.959 align:start position:0% error that's basically tell the client 00:03:55.959 --> 00:03:58.149 align:start position:0% error that's basically tell the client actually<00:03:56.360> you<00:03:56.840> need<00:03:57.040> to<00:03:57.239> give<00:03:57.400> me<00:03:57.560> a<00:03:57.720> bit<00:03:57.879> more 00:03:58.149 --> 00:03:58.159 align:start position:0% actually you need to give me a bit more 00:03:58.159 --> 00:04:00.589 align:start position:0% actually you need to give me a bit more data<00:03:58.439> so<00:03:58.680> that<00:03:58.840> I<00:03:58.959> can<00:03:59.120> do<00:03:59.319> my<00:03:59.480> job 00:04:00.589 --> 00:04:00.599 align:start position:0% data so that I can do my job 00:04:00.599 --> 00:04:04.630 align:start position:0% data so that I can do my job so<00:04:01.599> uh<00:04:02.040> at<00:04:02.239> this<00:04:02.439> point<00:04:02.879> so<00:04:03.120> the<00:04:03.280> client<00:04:03.720> will 00:04:04.630 --> 00:04:04.640 align:start position:0% so uh at this point so the client will 00:04:04.640 --> 00:04:07.589 align:start position:0% so uh at this point so the client will uh<00:04:04.879> add<00:04:05.120> the<00:04:05.280> job<00:04:05.560> to<00:04:06.120> fetch<00:04:06.560> the<00:04:06.760> data<00:04:07.239> on<00:04:07.400> a 00:04:07.589 --> 00:04:07.599 align:start position:0% uh add the job to fetch the data on a 00:04:07.599 --> 00:04:12.630 align:start position:0% uh add the job to fetch the data on a Gateway<00:04:08.200> so<00:04:08.760> a<00:04:09.159> standard<00:04:09.680> HTTP<00:04:10.439> call<00:04:11.280> and<00:04:11.840> uh 00:04:12.630 --> 00:04:12.640 align:start position:0% Gateway so a standard HTTP call and uh 00:04:12.640 --> 00:04:14.229 align:start position:0% Gateway so a standard HTTP call and uh of<00:04:12.760> course<00:04:12.959> the<00:04:13.120> Gateway<00:04:13.519> will<00:04:13.760> send<00:04:14.079> the 00:04:14.229 --> 00:04:14.239 align:start position:0% of course the Gateway will send the 00:04:14.239 --> 00:04:18.670 align:start position:0% of course the Gateway will send the result<00:04:15.079> and<00:04:15.280> then<00:04:15.599> you<00:04:16.320> the<00:04:16.799> the<00:04:16.959> client<00:04:17.519> is<00:04:17.919> uh 00:04:18.670 --> 00:04:18.680 align:start position:0% result and then you the the client is uh 00:04:18.680 --> 00:04:21.629 align:start position:0% result and then you the the client is uh like<00:04:19.320> giving<00:04:19.759> back<00:04:20.320> the<00:04:20.639> information<00:04:21.239> to<00:04:21.400> the 00:04:21.629 --> 00:04:21.639 align:start position:0% like giving back the information to the 00:04:21.639 --> 00:04:26.310 align:start position:0% like giving back the information to the contract<00:04:22.639> uh<00:04:23.000> through<00:04:23.440> a<00:04:23.840> callback<00:04:25.320> function 00:04:26.310 --> 00:04:26.320 align:start position:0% contract uh through a callback function 00:04:26.320 --> 00:04:28.150 align:start position:0% contract uh through a callback function and<00:04:26.800> at<00:04:26.919> the<00:04:27.040> end<00:04:27.199> of<00:04:27.360> the<00:04:27.520> day<00:04:27.639> you<00:04:27.800> have<00:04:27.960> an 00:04:28.150 --> 00:04:28.160 align:start position:0% and at the end of the day you have an 00:04:28.160 --> 00:04:30.629 align:start position:0% and at the end of the day you have an answer<00:04:28.800> so<00:04:29.080> here<00:04:29.240> I<00:04:29.440> talk<00:04:29.840> about<00:04:30.080> call<00:04:30.400> but 00:04:30.629 --> 00:04:30.639 align:start position:0% answer so here I talk about call but 00:04:30.639 --> 00:04:32.430 align:start position:0% answer so here I talk about call but actually<00:04:31.039> the<00:04:31.160> call<00:04:31.440> back<00:04:31.639> function<00:04:32.080> can<00:04:32.240> be 00:04:32.430 --> 00:04:32.440 align:start position:0% actually the call back function can be 00:04:32.440 --> 00:04:35.590 align:start position:0% actually the call back function can be also<00:04:32.680> sent<00:04:33.320> in<00:04:33.440> a<00:04:33.680> transaction<00:04:34.479> so<00:04:35.080> that<00:04:35.240> means 00:04:35.590 --> 00:04:35.600 align:start position:0% also sent in a transaction so that means 00:04:35.600 --> 00:04:37.710 align:start position:0% also sent in a transaction so that means that<00:04:36.320> at<00:04:36.440> the<00:04:36.520> end<00:04:36.680> of<00:04:36.840> the<00:04:37.000> day<00:04:37.160> you<00:04:37.320> have<00:04:37.440> some 00:04:37.710 --> 00:04:37.720 align:start position:0% that at the end of the day you have some 00:04:37.720 --> 00:04:40.070 align:start position:0% that at the end of the day you have some logic<00:04:38.120> that<00:04:38.240> can<00:04:38.400> be<00:04:38.600> executed<00:04:39.120> on<00:04:39.280> Shain<00:04:39.680> in<00:04:39.759> a 00:04:40.070 --> 00:04:40.080 align:start position:0% logic that can be executed on Shain in a 00:04:40.080 --> 00:04:43.909 align:start position:0% logic that can be executed on Shain in a block<00:04:41.160> um<00:04:42.160> the<00:04:42.840> nice<00:04:43.120> thing<00:04:43.400> about<00:04:43.680> this 00:04:43.909 --> 00:04:43.919 align:start position:0% block um the nice thing about this 00:04:43.919 --> 00:04:47.110 align:start position:0% block um the nice thing about this design<00:04:44.440> is<00:04:44.639> that<00:04:45.400> if<00:04:45.600> you<00:04:45.840> look<00:04:46.080> at<00:04:46.600> the 00:04:47.110 --> 00:04:47.120 align:start position:0% design is that if you look at the 00:04:47.120 --> 00:04:51.230 align:start position:0% design is that if you look at the offchain<00:04:48.120> data<00:04:49.080> um<00:04:49.800> error<00:04:50.400> there<00:04:50.520> is<00:04:50.800> all<00:04:51.000> the 00:04:51.230 --> 00:04:51.240 align:start position:0% offchain data um error there is all the 00:04:51.240 --> 00:04:54.510 align:start position:0% offchain data um error there is all the information<00:04:51.759> store<00:04:52.080> on<00:04:52.400> there<00:04:52.880> there<00:04:53.199> to<00:04:54.160> uh 00:04:54.510 --> 00:04:54.520 align:start position:0% information store on there there to uh 00:04:54.520 --> 00:04:56.870 align:start position:0% information store on there there to uh explain<00:04:54.919> to<00:04:55.199> the<00:04:55.720> client<00:04:56.160> what<00:04:56.280> he<00:04:56.440> needs<00:04:56.680> to 00:04:56.870 --> 00:04:56.880 align:start position:0% explain to the client what he needs to 00:04:56.880 --> 00:04:59.270 align:start position:0% explain to the client what he needs to do<00:04:57.360> so<00:04:57.680> in<00:04:57.880> advance<00:04:58.320> the<00:04:58.479> client<00:04:58.840> doesn't<00:04:59.120> need 00:04:59.270 --> 00:04:59.280 align:start position:0% do so in advance the client doesn't need 00:04:59.280 --> 00:05:02.550 align:start position:0% do so in advance the client doesn't need to<00:04:59.440> have<00:04:59.800> any<00:05:00.039> information<00:05:00.960> about<00:05:01.960> what<00:05:02.400> what 00:05:02.550 --> 00:05:02.560 align:start position:0% to have any information about what what 00:05:02.560 --> 00:05:04.670 align:start position:0% to have any information about what what are<00:05:02.759> the<00:05:03.000> gateway<00:05:03.520> to<00:05:03.800> call<00:05:04.199> what<00:05:04.320> is<00:05:04.479> the 00:05:04.670 --> 00:05:04.680 align:start position:0% are the gateway to call what is the 00:05:04.680 --> 00:05:07.150 align:start position:0% are the gateway to call what is the information<00:05:05.400> that<00:05:05.600> I<00:05:06.080> need<00:05:06.280> to<00:05:06.520> send<00:05:06.840> to<00:05:07.000> the 00:05:07.150 --> 00:05:07.160 align:start position:0% information that I need to send to the 00:05:07.160 --> 00:05:10.070 align:start position:0% information that I need to send to the Gateway<00:05:07.680> which<00:05:07.840> is<00:05:08.039> the<00:05:08.320> call<00:05:08.639> data<00:05:09.639> uh<00:05:09.800> or 00:05:10.070 --> 00:05:10.080 align:start position:0% Gateway which is the call data uh or 00:05:10.080 --> 00:05:12.749 align:start position:0% Gateway which is the call data uh or what<00:05:10.199> are<00:05:10.360> the<00:05:10.479> Callback<00:05:10.919> function<00:05:11.479> and<00:05:11.600> so<00:05:11.800> on 00:05:12.749 --> 00:05:12.759 align:start position:0% what are the Callback function and so on 00:05:12.759 --> 00:05:15.150 align:start position:0% what are the Callback function and so on so<00:05:13.160> this<00:05:13.320> mean<00:05:13.800> that<00:05:13.960> the<00:05:14.120> client<00:05:14.560> can<00:05:14.759> have<00:05:14.919> a 00:05:15.150 --> 00:05:15.160 align:start position:0% so this mean that the client can have a 00:05:15.160 --> 00:05:17.390 align:start position:0% so this mean that the client can have a standard<00:05:15.919> implementation<00:05:16.800> and<00:05:16.960> you<00:05:17.080> don't 00:05:17.390 --> 00:05:17.400 align:start position:0% standard implementation and you don't 00:05:17.400 --> 00:05:19.909 align:start position:0% standard implementation and you don't need<00:05:17.600> to<00:05:18.280> integrate<00:05:19.039> each<00:05:19.280> time<00:05:19.560> like<00:05:19.720> a 00:05:19.909 --> 00:05:19.919 align:start position:0% need to integrate each time like a 00:05:19.919 --> 00:05:22.670 align:start position:0% need to integrate each time like a specific<00:05:20.400> use<00:05:20.759> case<00:05:21.000> so<00:05:21.560> if<00:05:21.680> you<00:05:21.960> want<00:05:22.160> to 00:05:22.670 --> 00:05:22.680 align:start position:0% specific use case so if you want to 00:05:22.680 --> 00:05:25.550 align:start position:0% specific use case so if you want to integrate<00:05:23.319> like<00:05:23.840> a<00:05:24.000> chain<00:05:24.440> like<00:05:25.039> I<00:05:25.120> don't<00:05:25.319> know 00:05:25.550 --> 00:05:25.560 align:start position:0% integrate like a chain like I don't know 00:05:25.560 --> 00:05:28.550 align:start position:0% integrate like a chain like I don't know optimism<00:05:26.199> and<00:05:26.319> a<00:05:26.440> chain<00:05:26.720> like<00:05:26.919> linear<00:05:27.720> you 00:05:28.550 --> 00:05:28.560 align:start position:0% optimism and a chain like linear you 00:05:28.560 --> 00:05:31.110 align:start position:0% optimism and a chain like linear you don't<00:05:28.880> have<00:05:29.039> to<00:05:29.319> do<00:05:29.479> it 00:05:31.110 --> 00:05:31.120 align:start position:0% don't have to do it 00:05:31.120 --> 00:05:35.230 align:start position:0% don't have to do it twice<00:05:32.160> um<00:05:33.160> so<00:05:33.440> if<00:05:33.560> you<00:05:33.639> are<00:05:33.800> following<00:05:34.479> like 00:05:35.230 --> 00:05:35.240 align:start position:0% twice um so if you are following like 00:05:35.240 --> 00:05:37.510 align:start position:0% twice um so if you are following like attentively<00:05:36.000> you<00:05:36.319> might<00:05:36.600> ask<00:05:36.800> yourself<00:05:37.280> but 00:05:37.510 --> 00:05:37.520 align:start position:0% attentively you might ask yourself but 00:05:37.520 --> 00:05:39.510 align:start position:0% attentively you might ask yourself but okay<00:05:37.960> like<00:05:38.440> it<00:05:38.560> seems<00:05:38.880> that<00:05:39.080> you<00:05:39.240> have<00:05:39.360> to 00:05:39.510 --> 00:05:39.520 align:start position:0% okay like it seems that you have to 00:05:39.520 --> 00:05:41.990 align:start position:0% okay like it seems that you have to trust<00:05:39.800> the<00:05:39.960> Gateway<00:05:40.479> and<00:05:40.759> like<00:05:41.199> thanks<00:05:41.440> to 00:05:41.990 --> 00:05:42.000 align:start position:0% trust the Gateway and like thanks to 00:05:42.000 --> 00:05:44.189 align:start position:0% trust the Gateway and like thanks to during<00:05:42.280> the<00:05:42.479> introduction<00:05:43.160> we<00:05:43.440> said<00:05:43.759> it<00:05:43.919> was 00:05:44.189 --> 00:05:44.199 align:start position:0% during the introduction we said it was 00:05:44.199 --> 00:05:47.749 align:start position:0% during the introduction we said it was like<00:05:44.360> a<00:05:44.600> secure<00:05:45.039> and<00:05:45.240> Trust<00:05:45.560> minimize<00:05:46.199> way<00:05:46.800> to 00:05:47.749 --> 00:05:47.759 align:start position:0% like a secure and Trust minimize way to 00:05:47.759 --> 00:05:50.550 align:start position:0% like a secure and Trust minimize way to um<00:05:48.160> fetch<00:05:48.600> data<00:05:49.319> and<00:05:49.639> actually<00:05:50.199> you<00:05:50.319> don't 00:05:50.550 --> 00:05:50.560 align:start position:0% um fetch data and actually you don't 00:05:50.560 --> 00:05:53.189 align:start position:0% um fetch data and actually you don't have<00:05:50.680> to<00:05:50.840> trust<00:05:51.160> the<00:05:51.319> Gateway<00:05:52.280> uh<00:05:52.479> necessarily 00:05:53.189 --> 00:05:53.199 align:start position:0% have to trust the Gateway uh necessarily 00:05:53.199 --> 00:05:56.189 align:start position:0% have to trust the Gateway uh necessarily if<00:05:53.319> the<00:05:53.479> Gateway<00:05:54.000> provide<00:05:54.360> also<00:05:54.759> proof<00:05:55.280> of<00:05:55.520> the 00:05:56.189 --> 00:05:56.199 align:start position:0% if the Gateway provide also proof of the 00:05:56.199 --> 00:05:59.670 align:start position:0% if the Gateway provide also proof of the information<00:05:57.199> uh<00:05:57.440> that<00:05:57.880> were<00:05:58.199> given<00:05:58.919> and<00:05:59.280> the 00:05:59.670 --> 00:05:59.680 align:start position:0% information uh that were given and the 00:05:59.680 --> 00:06:01.990 align:start position:0% information uh that were given and the nice<00:05:59.880> thing<00:06:00.120> about<00:06:00.400> it<00:06:00.680> is<00:06:00.880> that<00:06:01.440> you<00:06:01.600> know 00:06:01.990 --> 00:06:02.000 align:start position:0% nice thing about it is that you know 00:06:02.000 --> 00:06:04.590 align:start position:0% nice thing about it is that you know that<00:06:02.280> l2s<00:06:03.240> like<00:06:03.400> in<00:06:03.520> the<00:06:03.720> design<00:06:04.000> of<00:06:04.160> rollup 00:06:04.590 --> 00:06:04.600 align:start position:0% that l2s like in the design of rollup 00:06:04.600 --> 00:06:06.950 align:start position:0% that l2s like in the design of rollup are<00:06:04.720> posting<00:06:05.080> their<00:06:05.280> state<00:06:05.720> on<00:06:06.000> the<00:06:06.639> on<00:06:06.800> the 00:06:06.950 --> 00:06:06.960 align:start position:0% are posting their state on the on the 00:06:06.960 --> 00:06:10.230 align:start position:0% are posting their state on the on the layer<00:06:07.280> one<00:06:07.840> and<00:06:07.960> so<00:06:08.280> you<00:06:08.479> can<00:06:09.039> like<00:06:09.319> just<00:06:09.919> fetch 00:06:10.230 --> 00:06:10.240 align:start position:0% layer one and so you can like just fetch 00:06:10.240 --> 00:06:14.390 align:start position:0% layer one and so you can like just fetch a<00:06:10.479> storage<00:06:11.000> proof<00:06:11.720> on<00:06:11.919> the<00:06:12.039> L2<00:06:12.919> and<00:06:13.120> then<00:06:13.560> like 00:06:14.390 --> 00:06:14.400 align:start position:0% a storage proof on the L2 and then like 00:06:14.400 --> 00:06:17.390 align:start position:0% a storage proof on the L2 and then like verify<00:06:14.880> it<00:06:15.039> on<00:06:15.199> the<00:06:15.440> layer<00:06:15.840> one<00:06:16.520> uh<00:06:16.680> so<00:06:16.960> that 00:06:17.390 --> 00:06:17.400 align:start position:0% verify it on the layer one uh so that 00:06:17.400 --> 00:06:19.270 align:start position:0% verify it on the layer one uh so that you<00:06:17.560> can<00:06:17.720> be<00:06:17.880> sure<00:06:18.240> that<00:06:18.479> the<00:06:18.800> data<00:06:19.080> is 00:06:19.270 --> 00:06:19.280 align:start position:0% you can be sure that the data is 00:06:19.280 --> 00:06:23.110 align:start position:0% you can be sure that the data is accurate<00:06:20.160> so<00:06:20.479> that's<00:06:21.000> what<00:06:21.199> is<00:06:21.639> uh<00:06:22.000> shown<00:06:22.479> here 00:06:23.110 --> 00:06:23.120 align:start position:0% accurate so that's what is uh shown here 00:06:23.120 --> 00:06:25.510 align:start position:0% accurate so that's what is uh shown here when<00:06:23.280> you<00:06:23.400> are<00:06:23.680> doing<00:06:24.400> when<00:06:24.680> the<00:06:24.919> Gateway<00:06:25.360> is 00:06:25.510 --> 00:06:25.520 align:start position:0% when you are doing when the Gateway is 00:06:25.520 --> 00:06:27.950 align:start position:0% when you are doing when the Gateway is doing<00:06:25.840> the<00:06:26.000> HTTP<00:06:26.720> request<00:06:27.319> actually<00:06:27.800> the 00:06:27.950 --> 00:06:27.960 align:start position:0% doing the HTTP request actually the 00:06:27.960 --> 00:06:32.150 align:start position:0% doing the HTTP request actually the Gateway<00:06:28.840> will<00:06:29.319> uh<00:06:29.639> call<00:06:29.960> L2<00:06:30.360> RPC<00:06:31.360> will<00:06:31.720> ask<00:06:31.919> for 00:06:32.150 --> 00:06:32.160 align:start position:0% Gateway will uh call L2 RPC will ask for 00:06:32.160 --> 00:06:34.629 align:start position:0% Gateway will uh call L2 RPC will ask for the<00:06:32.360> information<00:06:32.919> for<00:06:33.360> if<00:06:33.599> call<00:06:34.199> and<00:06:34.360> then 00:06:34.629 --> 00:06:34.639 align:start position:0% the information for if call and then 00:06:34.639 --> 00:06:36.909 align:start position:0% the information for if call and then also<00:06:35.240> like<00:06:35.400> do<00:06:35.680> something<00:06:36.080> like<00:06:36.240> a<00:06:36.400> if<00:06:36.680> get 00:06:36.909 --> 00:06:36.919 align:start position:0% also like do something like a if get 00:06:36.919 --> 00:06:39.950 align:start position:0% also like do something like a if get proof<00:06:37.680> to<00:06:38.000> to<00:06:38.199> get<00:06:38.360> the<00:06:38.479> storage<00:06:38.919> proof<00:06:39.720> and 00:06:39.950 --> 00:06:39.960 align:start position:0% proof to to get the storage proof and 00:06:39.960 --> 00:06:42.350 align:start position:0% proof to to get the storage proof and then<00:06:40.319> when<00:06:40.599> the<00:06:40.919> contract<00:06:41.800> receive<00:06:42.199> the 00:06:42.350 --> 00:06:42.360 align:start position:0% then when the contract receive the 00:06:42.360 --> 00:06:45.189 align:start position:0% then when the contract receive the information<00:06:43.360> it<00:06:43.479> will<00:06:43.759> call<00:06:44.160> the<00:06:44.680> rollup 00:06:45.189 --> 00:06:45.199 align:start position:0% information it will call the rollup 00:06:45.199 --> 00:06:48.150 align:start position:0% information it will call the rollup contract<00:06:46.039> which<00:06:46.599> can<00:06:46.840> verify<00:06:47.280> the<00:06:47.479> proof<00:06:48.039> at 00:06:48.150 --> 00:06:48.160 align:start position:0% contract which can verify the proof at 00:06:48.160 --> 00:06:49.390 align:start position:0% contract which can verify the proof at the<00:06:48.360> high 00:06:49.390 --> 00:06:49.400 align:start position:0% the high 00:06:49.400 --> 00:06:53.230 align:start position:0% the high level<00:06:50.400> so<00:06:51.280> I<00:06:51.400> think<00:06:52.000> like<00:06:52.560> the<00:06:52.759> design<00:06:53.080> is 00:06:53.230 --> 00:06:53.240 align:start position:0% level so I think like the design is 00:06:53.240 --> 00:06:55.550 align:start position:0% level so I think like the design is quite<00:06:53.479> of<00:06:53.680> cool<00:06:54.000> but<00:06:54.479> uh<00:06:54.720> what<00:06:54.840> can<00:06:55.000> we<00:06:55.160> do<00:06:55.400> with 00:06:55.550 --> 00:06:55.560 align:start position:0% quite of cool but uh what can we do with 00:06:55.560 --> 00:06:58.350 align:start position:0% quite of cool but uh what can we do with it<00:06:56.319> um<00:06:56.800> as<00:06:56.960> mentioned<00:06:57.360> in<00:06:57.479> the<00:06:57.639> introduction 00:06:58.350 --> 00:06:58.360 align:start position:0% it um as mentioned in the introduction 00:06:58.360 --> 00:07:00.510 align:start position:0% it um as mentioned in the introduction like<00:06:58.560> ens<00:06:59.000> was<00:06:59.160> the<00:06:59.240> one<00:06:59.639> proposing<00:07:00.080> it<00:07:00.280> and 00:07:00.510 --> 00:07:00.520 align:start position:0% like ens was the one proposing it and 00:07:00.520 --> 00:07:02.629 align:start position:0% like ens was the one proposing it and actually<00:07:01.199> they<00:07:01.319> have<00:07:01.879> they<00:07:02.039> had<00:07:02.199> a<00:07:02.360> very 00:07:02.629 --> 00:07:02.639 align:start position:0% actually they have they had a very 00:07:02.639 --> 00:07:04.990 align:start position:0% actually they have they had a very specific<00:07:03.080> use<00:07:03.400> case<00:07:03.560> in<00:07:03.720> mind<00:07:04.080> which<00:07:04.319> was<00:07:04.800> to 00:07:04.990 --> 00:07:05.000 align:start position:0% specific use case in mind which was to 00:07:05.000 --> 00:07:08.589 align:start position:0% specific use case in mind which was to enable<00:07:05.599> to<00:07:06.000> manage<00:07:07.000> like<00:07:07.160> domains<00:07:07.560> on<00:07:07.759> L2<00:07:08.199> for 00:07:08.589 --> 00:07:08.599 align:start position:0% enable to manage like domains on L2 for 00:07:08.599 --> 00:07:12.110 align:start position:0% enable to manage like domains on L2 for cheaper<00:07:09.599> like<00:07:09.960> gas<00:07:10.280> cost<00:07:11.080> and<00:07:11.759> that's<00:07:11.960> the 00:07:12.110 --> 00:07:12.120 align:start position:0% cheaper like gas cost and that's the 00:07:12.120 --> 00:07:14.589 align:start position:0% cheaper like gas cost and that's the main<00:07:12.319> use<00:07:12.639> case<00:07:12.879> that<00:07:13.039> we<00:07:13.120> are<00:07:13.280> seeing<00:07:13.720> today 00:07:14.589 --> 00:07:14.599 align:start position:0% main use case that we are seeing today 00:07:14.599 --> 00:07:17.629 align:start position:0% main use case that we are seeing today uh<00:07:14.800> one<00:07:15.080> example<00:07:15.720> is<00:07:16.160> the<00:07:16.599> linear<00:07:17.120> names<00:07:17.479> that 00:07:17.629 --> 00:07:17.639 align:start position:0% uh one example is the linear names that 00:07:17.639 --> 00:07:20.629 align:start position:0% uh one example is the linear names that we<00:07:17.960> introduce<00:07:18.960> on<00:07:19.120> linear<00:07:19.840> where<00:07:20.000> you<00:07:20.319> can 00:07:20.629 --> 00:07:20.639 align:start position:0% we introduce on linear where you can 00:07:20.639 --> 00:07:23.309 align:start position:0% we introduce on linear where you can have<00:07:20.919> like<00:07:21.319> names<00:07:21.680> like<00:07:21.840> brian.<00:07:22.479> linear.<00:07:23.039> if 00:07:23.309 --> 00:07:23.319 align:start position:0% have like names like brian. linear. if 00:07:23.319 --> 00:07:28.589 align:start position:0% have like names like brian. linear. if or<00:07:23.800> a.l.<00:07:25.120> if<00:07:26.120> um<00:07:26.960> it's<00:07:27.199> something<00:07:27.639> that<00:07:27.960> uh<00:07:28.240> we 00:07:28.589 --> 00:07:28.599 align:start position:0% or a.l. if um it's something that uh we 00:07:28.599 --> 00:07:31.350 align:start position:0% or a.l. if um it's something that uh we built<00:07:29.120> and<00:07:29.319> that<00:07:29.800> can<00:07:29.960> be<00:07:30.160> reused<00:07:30.639> by<00:07:30.919> like<00:07:31.080> the 00:07:31.350 --> 00:07:31.360 align:start position:0% built and that can be reused by like the 00:07:31.360 --> 00:07:35.150 align:start position:0% built and that can be reused by like the ecosystem<00:07:32.080> to<00:07:32.240> build<00:07:32.680> any<00:07:33.680> uh<00:07:34.479> integration 00:07:35.150 --> 00:07:35.160 align:start position:0% ecosystem to build any uh integration 00:07:35.160 --> 00:07:39.270 align:start position:0% ecosystem to build any uh integration with<00:07:35.400> ens<00:07:36.240> and<00:07:36.680> if<00:07:37.240> it<00:07:37.479> works<00:07:37.840> like<00:07:38.280> everywhere 00:07:39.270 --> 00:07:39.280 align:start position:0% with ens and if it works like everywhere 00:07:39.280 --> 00:07:43.469 align:start position:0% with ens and if it works like everywhere ens<00:07:39.800> is<00:07:40.560> resolved<00:07:41.560> as<00:07:41.879> an<00:07:42.120> example<00:07:42.840> like<00:07:43.319> we 00:07:43.469 --> 00:07:43.479 align:start position:0% ens is resolved as an example like we 00:07:43.479 --> 00:07:45.909 align:start position:0% ens is resolved as an example like we have<00:07:43.639> a<00:07:43.879> nft<00:07:44.400> collection<00:07:44.879> on<00:07:45.120> Linea<00:07:45.599> which<00:07:45.720> are 00:07:45.909 --> 00:07:45.919 align:start position:0% have a nft collection on Linea which are 00:07:45.919 --> 00:07:49.029 align:start position:0% have a nft collection on Linea which are called<00:07:46.159> eogs<00:07:47.039> that<00:07:47.199> wanted<00:07:47.560> to<00:07:48.080> give<00:07:48.560> ens 00:07:49.029 --> 00:07:49.039 align:start position:0% called eogs that wanted to give ens 00:07:49.039 --> 00:07:51.909 align:start position:0% called eogs that wanted to give ens domains<00:07:49.520> to<00:07:49.759> all<00:07:50.039> the<00:07:50.240> holders<00:07:51.240> so<00:07:51.680> for 00:07:51.909 --> 00:07:51.919 align:start position:0% domains to all the holders so for 00:07:51.919 --> 00:07:55.309 align:start position:0% domains to all the holders so for instance<00:07:52.440> know<00:07:52.759> if<00:07:52.879> you<00:07:53.039> have<00:07:53.199> a<00:07:54.039> um<00:07:54.360> you<00:07:54.639> type 00:07:55.309 --> 00:07:55.319 align:start position:0% instance know if you have a um you type 00:07:55.319 --> 00:08:00.309 align:start position:0% instance know if you have a um you type 743<00:07:56.319> if.<00:07:57.039> if<00:07:57.479> it's<00:07:58.199> it<00:07:58.680> resol<00:07:59.159> to<00:07:59.280> the 00:08:00.309 --> 00:08:00.319 align:start position:0% 743 if. if it's it resol to the 00:08:00.319 --> 00:08:02.749 align:start position:0% 743 if. if it's it resol to the owner<00:08:00.680> of<00:08:00.919> this<00:08:01.199> nft<00:08:01.720> and<00:08:01.919> if<00:08:02.080> the<00:08:02.199> nft<00:08:02.599> is 00:08:02.749 --> 00:08:02.759 align:start position:0% owner of this nft and if the nft is 00:08:02.759 --> 00:08:05.629 align:start position:0% owner of this nft and if the nft is transfer<00:08:03.759> like<00:08:04.280> the<00:08:04.919> the<00:08:05.080> name<00:08:05.479> is 00:08:05.629 --> 00:08:05.639 align:start position:0% transfer like the the name is 00:08:05.639 --> 00:08:07.909 align:start position:0% transfer like the the name is transferred<00:08:06.199> with<00:08:06.360> it<00:08:06.560> as<00:08:06.680> well<00:08:07.199> so<00:08:07.560> this<00:08:07.680> is 00:08:07.909 --> 00:08:07.919 align:start position:0% transferred with it as well so this is 00:08:07.919 --> 00:08:11.390 align:start position:0% transferred with it as well so this is kind<00:08:08.120> of<00:08:08.280> cool<00:08:09.080> but<00:08:09.840> it's<00:08:10.120> just<00:08:10.280> a<00:08:10.440> first<00:08:11.039> size 00:08:11.390 --> 00:08:11.400 align:start position:0% kind of cool but it's just a first size 00:08:11.400 --> 00:08:14.550 align:start position:0% kind of cool but it's just a first size and<00:08:11.560> it<00:08:11.720> doesn't<00:08:12.080> stop<00:08:12.440> there<00:08:13.000> like<00:08:13.720> um<00:08:14.240> it<00:08:14.360> can 00:08:14.550 --> 00:08:14.560 align:start position:0% and it doesn't stop there like um it can 00:08:14.560 --> 00:08:15.950 align:start position:0% and it doesn't stop there like um it can be<00:08:14.720> used<00:08:15.000> for 00:08:15.950 --> 00:08:15.960 align:start position:0% be used for 00:08:15.960 --> 00:08:20.029 align:start position:0% be used for any<00:08:16.960> type<00:08:17.240> of<00:08:17.639> um<00:08:18.199> use<00:08:18.560> cases<00:08:19.039> where<00:08:19.240> basically 00:08:20.029 --> 00:08:20.039 align:start position:0% any type of um use cases where basically 00:08:20.039 --> 00:08:22.790 align:start position:0% any type of um use cases where basically you<00:08:20.199> want<00:08:20.440> to<00:08:21.000> either<00:08:21.360> compute<00:08:21.919> or<00:08:22.080> store<00:08:22.520> data 00:08:22.790 --> 00:08:22.800 align:start position:0% you want to either compute or store data 00:08:22.800 --> 00:08:25.390 align:start position:0% you want to either compute or store data on<00:08:22.960> the<00:08:23.080> layer<00:08:23.479> two<00:08:23.840> or<00:08:24.039> even<00:08:24.360> of<00:08:24.560> chain<00:08:25.159> and 00:08:25.390 --> 00:08:25.400 align:start position:0% on the layer two or even of chain and 00:08:25.400 --> 00:08:27.990 align:start position:0% on the layer two or even of chain and access<00:08:25.720> it<00:08:25.919> on<00:08:26.080> on<00:08:26.280> layer<00:08:26.599> one<00:08:26.879> so<00:08:27.680> some 00:08:27.990 --> 00:08:28.000 align:start position:0% access it on on layer one so some 00:08:28.000 --> 00:08:31.350 align:start position:0% access it on on layer one so some example<00:08:28.840> include<00:08:29.840> like<00:08:30.080> Dow<00:08:30.400> governance 00:08:31.350 --> 00:08:31.360 align:start position:0% example include like Dow governance 00:08:31.360 --> 00:08:35.670 align:start position:0% example include like Dow governance where<00:08:31.800> with<00:08:32.080> solution<00:08:32.640> like<00:08:33.640> um<00:08:34.640> sorry<00:08:35.479> we 00:08:35.670 --> 00:08:35.680 align:start position:0% where with solution like um sorry we 00:08:35.680 --> 00:08:37.670 align:start position:0% where with solution like um sorry we with<00:08:36.279> like<00:08:36.479> governance<00:08:37.000> solution<00:08:37.479> like 00:08:37.670 --> 00:08:37.680 align:start position:0% with like governance solution like 00:08:37.680 --> 00:08:40.909 align:start position:0% with like governance solution like snapshot<00:08:38.279> X<00:08:38.800> that<00:08:38.919> are<00:08:39.760> providing<00:08:40.760> like 00:08:40.909 --> 00:08:40.919 align:start position:0% snapshot X that are providing like 00:08:40.919 --> 00:08:43.709 align:start position:0% snapshot X that are providing like voting<00:08:41.240> on<00:08:41.440> chain<00:08:42.080> you<00:08:42.200> can<00:08:42.399> vote<00:08:42.839> on<00:08:43.080> linear 00:08:43.709 --> 00:08:43.719 align:start position:0% voting on chain you can vote on linear 00:08:43.719 --> 00:08:46.190 align:start position:0% voting on chain you can vote on linear or<00:08:43.919> other<00:08:44.279> L<00:08:44.480> tools<00:08:44.880> that<00:08:45.000> are<00:08:45.120> much<00:08:45.399> Sher<00:08:46.000> in 00:08:46.190 --> 00:08:46.200 align:start position:0% or other L tools that are much Sher in 00:08:46.200 --> 00:08:48.389 align:start position:0% or other L tools that are much Sher in gas<00:08:46.920> and<00:08:47.120> then<00:08:47.399> you<00:08:47.560> can<00:08:47.800> just<00:08:48.000> take<00:08:48.200> the 00:08:48.389 --> 00:08:48.399 align:start position:0% gas and then you can just take the 00:08:48.399 --> 00:08:51.590 align:start position:0% gas and then you can just take the result<00:08:49.279> and<00:08:49.920> use<00:08:50.240> this<00:08:50.560> call<00:08:50.839> this<00:08:51.040> result<00:08:51.360> to 00:08:51.590 --> 00:08:51.600 align:start position:0% result and use this call this result to 00:08:51.600 --> 00:08:54.269 align:start position:0% result and use this call this result to execute<00:08:52.080> transaction<00:08:52.560> on<00:08:52.760> the<00:08:52.880> layer<00:08:53.160> one<00:08:54.080> one 00:08:54.269 --> 00:08:54.279 align:start position:0% execute transaction on the layer one one 00:08:54.279 --> 00:08:56.509 align:start position:0% execute transaction on the layer one one other<00:08:54.880> interesting<00:08:55.320> use<00:08:55.640> case<00:08:55.839> for<00:08:56.000> instance 00:08:56.509 --> 00:08:56.519 align:start position:0% other interesting use case for instance 00:08:56.519 --> 00:08:58.829 align:start position:0% other interesting use case for instance is<00:08:56.640> to<00:08:57.399> like<00:08:57.800> gate<00:08:58.120> access<00:08:58.360> to<00:08:58.519> Smart 00:08:58.829 --> 00:08:58.839 align:start position:0% is to like gate access to Smart 00:08:58.839 --> 00:09:01.269 align:start position:0% is to like gate access to Smart contracts<00:08:59.440> so<00:08:59.680> for<00:08:59.920> instance<00:09:00.440> like<00:09:01.040> if<00:09:01.160> you 00:09:01.269 --> 00:09:01.279 align:start position:0% contracts so for instance like if you 00:09:01.279 --> 00:09:04.150 align:start position:0% contracts so for instance like if you are<00:09:01.480> doing<00:09:01.720> an<00:09:01.959> airdrop<00:09:02.560> or<00:09:02.800> nft<00:09:03.279> mins<00:09:03.800> you<00:09:03.959> can 00:09:04.150 --> 00:09:04.160 align:start position:0% are doing an airdrop or nft mins you can 00:09:04.160 --> 00:09:06.030 align:start position:0% are doing an airdrop or nft mins you can require<00:09:04.680> people<00:09:04.959> to<00:09:05.120> have<00:09:05.360> specific 00:09:06.030 --> 00:09:06.040 align:start position:0% require people to have specific 00:09:06.040 --> 00:09:09.430 align:start position:0% require people to have specific credentials<00:09:07.040> that<00:09:07.240> are<00:09:08.000> minted<00:09:08.440> on<00:09:08.640> Layer<00:09:08.959> Two 00:09:09.430 --> 00:09:09.440 align:start position:0% credentials that are minted on Layer Two 00:09:09.440 --> 00:09:12.069 align:start position:0% credentials that are minted on Layer Two for<00:09:09.640> in<00:09:09.839> attestation<00:09:10.600> for 00:09:12.069 --> 00:09:12.079 align:start position:0% for in attestation for 00:09:12.079 --> 00:09:16.110 align:start position:0% for in attestation for instance<00:09:13.079> um<00:09:13.680> so<00:09:14.440> okay<00:09:14.920> you<00:09:15.079> might<00:09:15.680> ask<00:09:15.920> your 00:09:16.110 --> 00:09:16.120 align:start position:0% instance um so okay you might ask your 00:09:16.120 --> 00:09:18.230 align:start position:0% instance um so okay you might ask your question<00:09:16.640> how<00:09:16.920> how<00:09:17.040> do<00:09:17.200> I<00:09:17.320> need<00:09:17.519> to<00:09:17.720> implement 00:09:18.230 --> 00:09:18.240 align:start position:0% question how how do I need to implement 00:09:18.240 --> 00:09:20.750 align:start position:0% question how how do I need to implement that<00:09:18.519> it<00:09:18.640> seems<00:09:19.000> really<00:09:19.760> complicated<00:09:20.480> you're 00:09:20.750 --> 00:09:20.760 align:start position:0% that it seems really complicated you're 00:09:20.760 --> 00:09:24.069 align:start position:0% that it seems really complicated you're talking<00:09:21.440> about<00:09:21.760> proof<00:09:22.160> and<00:09:22.320> so<00:09:22.519> on<00:09:23.240> um<00:09:23.880> the 00:09:24.069 --> 00:09:24.079 align:start position:0% talking about proof and so on um the 00:09:24.079 --> 00:09:26.430 align:start position:0% talking about proof and so on um the nice<00:09:24.360> thing<00:09:24.640> is<00:09:24.839> that<00:09:25.640> we<00:09:25.959> already 00:09:26.430 --> 00:09:26.440 align:start position:0% nice thing is that we already 00:09:26.440 --> 00:09:29.030 align:start position:0% nice thing is that we already implemented<00:09:27.079> all<00:09:27.279> the<00:09:27.440> smart<00:09:27.880> contracts<00:09:28.880> uh 00:09:29.030 --> 00:09:29.040 align:start position:0% implemented all the smart contracts uh 00:09:29.040 --> 00:09:33.430 align:start position:0% implemented all the smart contracts uh so<00:09:29.399> so<00:09:30.000> like<00:09:30.959> all<00:09:31.240> this<00:09:31.920> complicated<00:09:32.640> logic<00:09:33.160> or 00:09:33.430 --> 00:09:33.440 align:start position:0% so so like all this complicated logic or 00:09:33.440 --> 00:09:36.990 align:start position:0% so so like all this complicated logic or not<00:09:33.600> so<00:09:33.839> complicated<00:09:34.480> but<00:09:35.279> all<00:09:35.480> this<00:09:35.720> logic<00:09:36.720> is 00:09:36.990 --> 00:09:37.000 align:start position:0% not so complicated but all this logic is 00:09:37.000 --> 00:09:39.230 align:start position:0% not so complicated but all this logic is already<00:09:37.480> taken<00:09:37.839> care<00:09:38.079> of<00:09:38.399> we<00:09:38.519> have<00:09:38.640> a<00:09:38.839> Gateway 00:09:39.230 --> 00:09:39.240 align:start position:0% already taken care of we have a Gateway 00:09:39.240 --> 00:09:41.110 align:start position:0% already taken care of we have a Gateway that<00:09:39.360> is<00:09:39.519> running<00:09:40.240> we<00:09:40.360> have<00:09:40.480> all<00:09:40.680> the<00:09:40.800> smart 00:09:41.110 --> 00:09:41.120 align:start position:0% that is running we have all the smart 00:09:41.120 --> 00:09:43.310 align:start position:0% that is running we have all the smart contracts<00:09:41.760> the<00:09:41.880> one<00:09:42.160> that<00:09:42.279> are<00:09:42.600> verifying<00:09:43.160> the 00:09:43.310 --> 00:09:43.320 align:start position:0% contracts the one that are verifying the 00:09:43.320 --> 00:09:46.509 align:start position:0% contracts the one that are verifying the proof<00:09:44.079> which<00:09:44.480> for<00:09:44.760> Z<00:09:45.000> kol<00:09:45.399> up<00:09:45.600> is<00:09:45.920> esec 00:09:46.509 --> 00:09:46.519 align:start position:0% proof which for Z kol up is esec 00:09:46.519 --> 00:09:49.990 align:start position:0% proof which for Z kol up is esec especially<00:09:47.399> difficult<00:09:47.760> because<00:09:48.680> uh<00:09:48.920> the<00:09:49.880> the 00:09:49.990 --> 00:09:50.000 align:start position:0% especially difficult because uh the the 00:09:50.000 --> 00:09:52.590 align:start position:0% especially difficult because uh the the ZK<00:09:50.360> layer<00:09:50.640> 2<00:09:50.959> usually<00:09:51.399> have<00:09:51.560> a<00:09:51.839> different<00:09:52.320> way 00:09:52.590 --> 00:09:52.600 align:start position:0% ZK layer 2 usually have a different way 00:09:52.600 --> 00:09:57.230 align:start position:0% ZK layer 2 usually have a different way to<00:09:53.279> uh<00:09:53.480> store<00:09:53.920> data<00:09:54.880> uh<00:09:55.120> because<00:09:55.560> like<00:09:56.279> um<00:09:57.040> the 00:09:57.230 --> 00:09:57.240 align:start position:0% to uh store data uh because like um the 00:09:57.240 --> 00:09:59.670 align:start position:0% to uh store data uh because like um the standard<00:09:57.680> Ash<00:09:57.959> function<00:09:58.360> can<00:09:58.560> be<00:09:58.920> a<00:09:59.040> bit 00:09:59.670 --> 00:09:59.680 align:start position:0% standard Ash function can be a bit 00:09:59.680 --> 00:10:02.509 align:start position:0% standard Ash function can be a bit complicated<00:10:00.279> for<00:10:00.519> ZK<00:10:01.320> so<00:10:01.800> for<00:10:02.040> instance<00:10:02.360> on 00:10:02.509 --> 00:10:02.519 align:start position:0% complicated for ZK so for instance on 00:10:02.519 --> 00:10:04.949 align:start position:0% complicated for ZK so for instance on linear<00:10:03.000> we<00:10:03.079> have<00:10:03.360> like<00:10:03.720> Spar<00:10:04.160> Vel<00:10:04.560> tree 00:10:04.949 --> 00:10:04.959 align:start position:0% linear we have like Spar Vel tree 00:10:04.959 --> 00:10:08.310 align:start position:0% linear we have like Spar Vel tree instead<00:10:05.279> of<00:10:05.440> merel<00:10:06.079> tree<00:10:07.079> but<00:10:07.560> basically<00:10:08.160> all 00:10:08.310 --> 00:10:08.320 align:start position:0% instead of merel tree but basically all 00:10:08.320 --> 00:10:10.630 align:start position:0% instead of merel tree but basically all of<00:10:08.519> that<00:10:08.680> is<00:10:08.839> to<00:10:09.040> say<00:10:09.360> that<00:10:10.040> uh<00:10:10.279> we<00:10:10.440> have 00:10:10.630 --> 00:10:10.640 align:start position:0% of that is to say that uh we have 00:10:10.640 --> 00:10:12.389 align:start position:0% of that is to say that uh we have contracts<00:10:11.160> that<00:10:11.279> are<00:10:11.480> open<00:10:11.760> source<00:10:12.040> and<00:10:12.240> that 00:10:12.389 --> 00:10:12.399 align:start position:0% contracts that are open source and that 00:10:12.399 --> 00:10:16.269 align:start position:0% contracts that are open source and that can<00:10:12.560> be<00:10:12.720> called<00:10:13.079> to<00:10:14.079> verify<00:10:14.680> the<00:10:14.920> the<00:10:15.079> data<00:10:15.839> to 00:10:16.269 --> 00:10:16.279 align:start position:0% can be called to verify the the data to 00:10:16.279 --> 00:10:18.509 align:start position:0% can be called to verify the the data to also<00:10:16.560> fetch<00:10:16.959> the<00:10:17.160> data<00:10:17.480> directly<00:10:18.000> so 00:10:18.509 --> 00:10:18.519 align:start position:0% also fetch the data directly so 00:10:18.519 --> 00:10:21.110 align:start position:0% also fetch the data directly so basically<00:10:19.519> uh<00:10:19.640> on<00:10:19.839> the<00:10:20.000> smart<00:10:20.320> contract<00:10:20.760> level 00:10:21.110 --> 00:10:21.120 align:start position:0% basically uh on the smart contract level 00:10:21.120 --> 00:10:24.550 align:start position:0% basically uh on the smart contract level it's<00:10:21.480> much<00:10:21.680> more<00:10:21.959> simpler<00:10:22.959> and<00:10:23.800> uh<00:10:23.920> on<00:10:24.120> top<00:10:24.320> of 00:10:24.550 --> 00:10:24.560 align:start position:0% it's much more simpler and uh on top of 00:10:24.560 --> 00:10:27.230 align:start position:0% it's much more simpler and uh on top of that<00:10:24.959> there<00:10:25.079> have<00:10:25.240> been<00:10:25.480> team<00:10:25.880> like<00:10:26.079> the<00:10:26.480> unrug 00:10:27.230 --> 00:10:27.240 align:start position:0% that there have been team like the unrug 00:10:27.240 --> 00:10:29.990 align:start position:0% that there have been team like the unrug team<00:10:27.720> that<00:10:27.839> have<00:10:28.040> built<00:10:28.839> additional<00:10:29.519> layer<00:10:29.800> of 00:10:29.990 --> 00:10:30.000 align:start position:0% team that have built additional layer of 00:10:30.000 --> 00:10:32.590 align:start position:0% team that have built additional layer of abstraction<00:10:30.640> that<00:10:30.920> simplify<00:10:31.480> it<00:10:31.680> even<00:10:32.000> more 00:10:32.590 --> 00:10:32.600 align:start position:0% abstraction that simplify it even more 00:10:32.600 --> 00:10:35.069 align:start position:0% abstraction that simplify it even more and<00:10:33.279> Abstract<00:10:33.720> the<00:10:33.839> chain<00:10:34.200> so<00:10:34.560> it<00:10:34.839> can 00:10:35.069 --> 00:10:35.079 align:start position:0% and Abstract the chain so it can 00:10:35.079 --> 00:10:38.190 align:start position:0% and Abstract the chain so it can seamlessly<00:10:35.839> like<00:10:36.120> work<00:10:37.079> on<00:10:37.320> different 00:10:38.190 --> 00:10:38.200 align:start position:0% seamlessly like work on different 00:10:38.200 --> 00:10:42.030 align:start position:0% seamlessly like work on different chain<00:10:39.200> so<00:10:39.519> to<00:10:39.760> summarize<00:10:40.320> the<00:10:40.519> benefits<00:10:41.519> uh 00:10:42.030 --> 00:10:42.040 align:start position:0% chain so to summarize the benefits uh 00:10:42.040 --> 00:10:46.310 align:start position:0% chain so to summarize the benefits uh like<00:10:42.760> ERC<00:10:43.600> 3668<00:10:44.600> is<00:10:44.880> efficient<00:10:45.480> because<00:10:46.120> you 00:10:46.310 --> 00:10:46.320 align:start position:0% like ERC 3668 is efficient because you 00:10:46.320 --> 00:10:48.910 align:start position:0% like ERC 3668 is efficient because you don't<00:10:46.760> have<00:10:46.920> to<00:10:47.160> send<00:10:47.480> a<00:10:47.680> transaction<00:10:48.200> on<00:10:48.399> L1 00:10:48.910 --> 00:10:48.920 align:start position:0% don't have to send a transaction on L1 00:10:48.920 --> 00:10:51.310 align:start position:0% don't have to send a transaction on L1 when<00:10:49.120> you<00:10:49.240> don't<00:10:49.480> need<00:10:49.680> to<00:10:50.320> it's<00:10:50.560> secure 00:10:51.310 --> 00:10:51.320 align:start position:0% when you don't need to it's secure 00:10:51.320 --> 00:10:53.670 align:start position:0% when you don't need to it's secure especially<00:10:51.880> when<00:10:52.040> you<00:10:52.160> are<00:10:52.360> working<00:10:52.800> like<00:10:53.480> on 00:10:53.670 --> 00:10:53.680 align:start position:0% especially when you are working like on 00:10:53.680 --> 00:10:56.629 align:start position:0% especially when you are working like on a<00:10:53.880> layer<00:10:54.200> two<00:10:54.639> with<00:10:55.519> like<00:10:55.959> zero<00:10:56.320> knowledge 00:10:56.629 --> 00:10:56.639 align:start position:0% a layer two with like zero knowledge 00:10:56.639 --> 00:10:58.750 align:start position:0% a layer two with like zero knowledge proof<00:10:57.040> like<00:10:57.200> like<00:10:57.440> Linea<00:10:58.160> you<00:10:58.279> don't 00:10:58.750 --> 00:10:58.760 align:start position:0% proof like like Linea you don't 00:10:58.760 --> 00:11:01.509 align:start position:0% proof like like Linea you don't introduce<00:10:59.440> additional<00:11:00.000> dependency<00:11:00.760> to<00:11:01.120> over 00:11:01.509 --> 00:11:01.519 align:start position:0% introduce additional dependency to over 00:11:01.519 --> 00:11:05.750 align:start position:0% introduce additional dependency to over protocol<00:11:02.519> and<00:11:02.880> like<00:11:03.399> the<00:11:04.160> development<00:11:05.160> uh 00:11:05.750 --> 00:11:05.760 align:start position:0% protocol and like the development uh 00:11:05.760 --> 00:11:07.710 align:start position:0% protocol and like the development uh overhead<00:11:06.279> is<00:11:06.440> minimal<00:11:07.000> because<00:11:07.360> all<00:11:07.560> the 00:11:07.710 --> 00:11:07.720 align:start position:0% overhead is minimal because all the 00:11:07.720 --> 00:11:10.110 align:start position:0% overhead is minimal because all the contracts<00:11:08.440> the<00:11:08.600> Gateway<00:11:09.480> everything<00:11:09.920> is 00:11:10.110 --> 00:11:10.120 align:start position:0% contracts the Gateway everything is 00:11:10.120 --> 00:11:12.990 align:start position:0% contracts the Gateway everything is already<00:11:10.519> for<00:11:10.800> you<00:11:11.320> to<00:11:11.560> to<00:11:11.720> build 00:11:12.990 --> 00:11:13.000 align:start position:0% already for you to to build 00:11:13.000 --> 00:11:16.629 align:start position:0% already for you to to build on<00:11:14.000> um<00:11:14.399> and<00:11:14.519> so<00:11:14.800> if<00:11:14.880> you<00:11:15.000> want<00:11:15.279> to<00:11:15.440> get<00:11:15.639> started 00:11:16.629 --> 00:11:16.639 align:start position:0% on um and so if you want to get started 00:11:16.639 --> 00:11:18.829 align:start position:0% on um and so if you want to get started uh<00:11:16.959> those<00:11:17.120> are<00:11:17.320> some<00:11:17.519> links<00:11:17.880> to<00:11:18.040> our<00:11:18.360> doc 00:11:18.829 --> 00:11:18.839 align:start position:0% uh those are some links to our doc 00:11:18.839 --> 00:11:21.670 align:start position:0% uh those are some links to our doc documentation<00:11:19.560> open<00:11:19.880> source<00:11:20.200> Trio<00:11:21.200> uh<00:11:21.360> but 00:11:21.670 --> 00:11:21.680 align:start position:0% documentation open source Trio uh but 00:11:21.680 --> 00:11:23.990 align:start position:0% documentation open source Trio uh but most<00:11:21.959> importantly<00:11:22.600> we<00:11:22.680> are<00:11:22.839> doing<00:11:23.200> a<00:11:23.800> a 00:11:23.990 --> 00:11:24.000 align:start position:0% most importantly we are doing a a 00:11:24.000 --> 00:11:26.269 align:start position:0% most importantly we are doing a a workshop<00:11:24.880> just<00:11:25.079> after<00:11:25.320> the<00:11:25.440> lunch<00:11:25.800> break 00:11:26.269 --> 00:11:26.279 align:start position:0% workshop just after the lunch break 00:11:26.279 --> 00:11:29.750 align:start position:0% workshop just after the lunch break where<00:11:26.920> we<00:11:27.079> will<00:11:27.560> Deep<00:11:27.839> dive<00:11:28.160> into<00:11:28.760> really<00:11:29.440> code 00:11:29.750 --> 00:11:29.760 align:start position:0% where we will Deep dive into really code 00:11:29.760 --> 00:11:33.030 align:start position:0% where we will Deep dive into really code example<00:11:30.399> and<00:11:30.880> you<00:11:31.519> will<00:11:31.760> be<00:11:31.959> able<00:11:32.240> to<00:11:32.440> have<00:11:32.560> a 00:11:33.030 --> 00:11:33.040 align:start position:0% example and you will be able to have a 00:11:33.040 --> 00:11:35.870 align:start position:0% example and you will be able to have a live<00:11:33.320> version<00:11:34.279> running<00:11:34.760> on<00:11:34.959> on<00:11:35.120> your<00:11:35.320> laptop 00:11:35.870 --> 00:11:35.880 align:start position:0% live version running on on your laptop 00:11:35.880 --> 00:11:38.910 align:start position:0% live version running on on your laptop at<00:11:36.000> the<00:11:36.079> end<00:11:36.279> of<00:11:36.399> the 00:11:38.910 --> 00:11:38.920 align:start position:0% 00:11:38.920 --> 00:11:45.110 align:start position:0% session<00:11:39.920> so<00:11:40.240> yeah<00:11:40.959> that's<00:11:41.160> it<00:11:41.480> thanks<00:11:41.720> a 00:11:45.110 --> 00:11:45.120 align:start position:0% 00:11:45.120 --> 00:11:47.829 align:start position:0% lot<00:11:46.120> just<00:11:46.240> a<00:11:46.399> reminder<00:11:46.920> guys<00:11:47.279> uh<00:11:47.399> if<00:11:47.480> you<00:11:47.639> guys 00:11:47.829 --> 00:11:47.839 align:start position:0% lot just a reminder guys uh if you guys 00:11:47.839 --> 00:11:50.110 align:start position:0% lot just a reminder guys uh if you guys have<00:11:48.079> any<00:11:48.360> questions<00:11:49.040> you<00:11:49.160> can<00:11:49.720> ask<00:11:49.959> them 00:11:50.110 --> 00:11:50.120 align:start position:0% have any questions you can ask them 00:11:50.120 --> 00:11:53.590 align:start position:0% have any questions you can ask them through<00:11:50.279> mircat<00:11:50.839> scan<00:11:51.120> the<00:11:51.240> QR<00:11:51.639> code<00:11:52.639> um<00:11:53.440> looks 00:11:53.590 --> 00:11:53.600 align:start position:0% through mircat scan the QR code um looks 00:11:53.600 --> 00:11:55.069 align:start position:0% through mircat scan the QR code um looks like<00:11:53.720> we<00:11:53.839> already<00:11:54.000> have<00:11:54.120> some<00:11:54.240> more<00:11:54.440> coming<00:11:54.680> in 00:11:55.069 --> 00:11:55.079 align:start position:0% like we already have some more coming in 00:11:55.079 --> 00:11:56.710 align:start position:0% like we already have some more coming in uh<00:11:55.240> the<00:11:55.360> first<00:11:55.600> question<00:11:56.000> is<00:11:56.079> it<00:11:56.320> possible<00:11:56.600> to 00:11:56.710 --> 00:11:56.720 align:start position:0% uh the first question is it possible to 00:11:56.720 --> 00:12:00.629 align:start position:0% uh the first question is it possible to read<00:11:56.959> L1<00:11:57.440> data<00:11:57.680> from<00:11:58.000> L2<00:11:59.000> and<00:11:59.600> so<00:12:00.240> yeah<00:12:00.480> in 00:12:00.629 --> 00:12:00.639 align:start position:0% read L1 data from L2 and so yeah in 00:12:00.639 --> 00:12:02.750 align:start position:0% read L1 data from L2 and so yeah in theory<00:12:01.040> it's<00:12:01.320> POS<00:12:01.600> it's<00:12:01.800> totally<00:12:02.279> possible 00:12:02.750 --> 00:12:02.760 align:start position:0% theory it's POS it's totally possible 00:12:02.760 --> 00:12:04.310 align:start position:0% theory it's POS it's totally possible like<00:12:03.000> RC 00:12:04.310 --> 00:12:04.320 align:start position:0% like RC 00:12:04.320 --> 00:12:07.550 align:start position:0% like RC 3668<00:12:05.320> allows<00:12:05.639> to<00:12:05.800> fetch<00:12:06.200> any<00:12:06.480> data<00:12:07.200> the<00:12:07.320> only 00:12:07.550 --> 00:12:07.560 align:start position:0% 3668 allows to fetch any data the only 00:12:07.560 --> 00:12:09.629 align:start position:0% 3668 allows to fetch any data the only thing<00:12:07.839> is<00:12:08.000> that<00:12:08.240> you<00:12:08.560> you<00:12:08.680> need<00:12:08.920> to<00:12:09.120> have<00:12:09.360> like 00:12:09.629 --> 00:12:09.639 align:start position:0% thing is that you you need to have like 00:12:09.639 --> 00:12:11.629 align:start position:0% thing is that you you need to have like the<00:12:09.839> state<00:12:10.600> of<00:12:10.720> the<00:12:10.880> blockchain<00:12:11.399> that<00:12:11.519> you 00:12:11.629 --> 00:12:11.639 align:start position:0% the state of the blockchain that you 00:12:11.639 --> 00:12:15.310 align:start position:0% the state of the blockchain that you want<00:12:11.880> to<00:12:12.200> to<00:12:12.399> query<00:12:12.800> onor<00:12:13.760> on<00:12:14.040> the<00:12:14.360> Chain<00:12:14.839> where 00:12:15.310 --> 00:12:15.320 align:start position:0% want to to query onor on the Chain where 00:12:15.320 --> 00:12:19.110 align:start position:0% want to to query onor on the Chain where you<00:12:15.440> want<00:12:15.680> to<00:12:16.360> from<00:12:16.760> which<00:12:16.959> you<00:12:17.120> want<00:12:17.320> to<00:12:18.120> sorry 00:12:19.110 --> 00:12:19.120 align:start position:0% you want to from which you want to sorry 00:12:19.120 --> 00:12:22.110 align:start position:0% you want to from which you want to sorry I<00:12:19.199> will<00:12:19.560> go<00:12:19.839> go<00:12:20.079> again<00:12:20.920> uh<00:12:21.160> but<00:12:21.519> you<00:12:21.760> you<00:12:21.920> need 00:12:22.110 --> 00:12:22.120 align:start position:0% I will go go again uh but you you need 00:12:22.120 --> 00:12:24.629 align:start position:0% I will go go again uh but you you need to<00:12:22.839> on<00:12:23.040> the<00:12:23.199> blockchain<00:12:23.639> that<00:12:23.760> is<00:12:23.920> quaring<00:12:24.440> the 00:12:24.629 --> 00:12:24.639 align:start position:0% to on the blockchain that is quaring the 00:12:24.639 --> 00:12:26.990 align:start position:0% to on the blockchain that is quaring the information<00:12:25.199> you<00:12:25.480> need<00:12:25.680> to<00:12:25.839> have<00:12:26.120> the<00:12:26.839> the 00:12:26.990 --> 00:12:27.000 align:start position:0% information you need to have the the 00:12:27.000 --> 00:12:29.389 align:start position:0% information you need to have the the state<00:12:27.480> of<00:12:27.720> the<00:12:28.120> blockchain<00:12:28.720> that<00:12:28.839> is<00:12:29.199> being 00:12:29.389 --> 00:12:29.399 align:start position:0% state of the blockchain that is being 00:12:29.399 --> 00:12:33.230 align:start position:0% state of the blockchain that is being queried<00:12:30.279> and<00:12:30.440> so<00:12:30.959> like<00:12:31.560> it's<00:12:31.800> not<00:12:32.440> most<00:12:32.760> collup 00:12:33.230 --> 00:12:33.240 align:start position:0% queried and so like it's not most collup 00:12:33.240 --> 00:12:35.350 align:start position:0% queried and so like it's not most collup doesn't<00:12:33.560> have<00:12:33.800> that<00:12:34.079> at<00:12:34.199> the<00:12:34.320> moment<00:12:34.959> maybe<00:12:35.240> at 00:12:35.350 --> 00:12:35.360 align:start position:0% doesn't have that at the moment maybe at 00:12:35.360 --> 00:12:38.310 align:start position:0% doesn't have that at the moment maybe at some<00:12:35.560> point<00:12:35.839> we<00:12:36.000> will<00:12:36.199> see<00:12:36.880> like<00:12:37.360> Oracle<00:12:37.880> fun 00:12:38.310 --> 00:12:38.320 align:start position:0% some point we will see like Oracle fun 00:12:38.320 --> 00:12:40.790 align:start position:0% some point we will see like Oracle fun Oracle<00:12:38.839> that<00:12:39.000> are<00:12:39.560> uh<00:12:39.800> streaming<00:12:40.440> this<00:12:40.639> kind 00:12:40.790 --> 00:12:40.800 align:start position:0% Oracle that are uh streaming this kind 00:12:40.800 --> 00:12:44.750 align:start position:0% Oracle that are uh streaming this kind of<00:12:41.000> data<00:12:41.279> on<00:12:41.480> Shain<00:12:42.480> um<00:12:43.160> but<00:12:43.880> it's<00:12:44.279> it<00:12:44.399> would<00:12:44.560> be 00:12:44.750 --> 00:12:44.760 align:start position:0% of data on Shain um but it's it would be 00:12:44.760 --> 00:12:47.230 align:start position:0% of data on Shain um but it's it would be something<00:12:45.199> really<00:12:45.399> cool<00:12:45.639> to 00:12:47.230 --> 00:12:47.240 align:start position:0% something really cool to 00:12:47.240 --> 00:12:49.470 align:start position:0% something really cool to build<00:12:48.240> uh<00:12:48.399> the<00:12:48.600> last<00:12:48.880> question<00:12:49.160> we<00:12:49.320> have 00:12:49.470 --> 00:12:49.480 align:start position:0% build uh the last question we have 00:12:49.480 --> 00:12:51.910 align:start position:0% build uh the last question we have doesn't<00:12:49.720> it<00:12:49.920> make<00:12:50.120> the<00:12:50.320> process<00:12:50.720> more 00:12:51.910 --> 00:12:51.920 align:start position:0% doesn't it make the process more 00:12:51.920 --> 00:12:54.870 align:start position:0% doesn't it make the process more centralized<00:12:52.920> so<00:12:53.320> indeed<00:12:54.000> like<00:12:54.360> the<00:12:54.519> point<00:12:54.720> of 00:12:54.870 --> 00:12:54.880 align:start position:0% centralized so indeed like the point of 00:12:54.880 --> 00:12:58.269 align:start position:0% centralized so indeed like the point of centralization<00:12:55.880> here<00:12:56.040> is<00:12:56.199> the<00:12:56.440> Gateway<00:12:57.440> uh 00:12:58.269 --> 00:12:58.279 align:start position:0% centralization here is the Gateway uh 00:12:58.279 --> 00:13:02.150 align:start position:0% centralization here is the Gateway uh but<00:12:58.880> uh<00:12:59.240> if<00:12:59.360> we<00:12:59.519> come<00:12:59.760> back<00:12:59.959> to<00:13:00.639> okay<00:13:01.360> um 00:13:02.150 --> 00:13:02.160 align:start position:0% but uh if we come back to okay um 00:13:02.160 --> 00:13:04.110 align:start position:0% but uh if we come back to okay um actually<00:13:02.639> like<00:13:02.760> the<00:13:02.880> smart<00:13:03.199> contract<00:13:03.639> can 00:13:04.110 --> 00:13:04.120 align:start position:0% actually like the smart contract can 00:13:04.120 --> 00:13:06.750 align:start position:0% actually like the smart contract can like<00:13:04.320> pass<00:13:04.600> multiple<00:13:05.160> URLs<00:13:06.000> so<00:13:06.279> you<00:13:06.440> have<00:13:06.560> a 00:13:06.750 --> 00:13:06.760 align:start position:0% like pass multiple URLs so you have a 00:13:06.760 --> 00:13:08.990 align:start position:0% like pass multiple URLs so you have a kind<00:13:06.920> of<00:13:07.160> redundancy<00:13:08.000> here<00:13:08.440> because<00:13:08.680> you<00:13:08.800> can 00:13:08.990 --> 00:13:09.000 align:start position:0% kind of redundancy here because you can 00:13:09.000 --> 00:13:12.150 align:start position:0% kind of redundancy here because you can have<00:13:09.360> multiple<00:13:10.360> different<00:13:10.800> Gateway<00:13:11.800> not<00:13:11.959> to 00:13:12.150 --> 00:13:12.160 align:start position:0% have multiple different Gateway not to 00:13:12.160 --> 00:13:15.470 align:start position:0% have multiple different Gateway not to rely<00:13:12.480> on<00:13:12.760> a<00:13:12.920> single<00:13:13.320> point<00:13:13.519> of<00:13:13.680> failure<00:13:14.519> but 00:13:15.470 --> 00:13:15.480 align:start position:0% rely on a single point of failure but 00:13:15.480 --> 00:13:17.710 align:start position:0% rely on a single point of failure but since<00:13:15.720> the<00:13:15.920> Gateway<00:13:16.279> is<00:13:16.440> passing<00:13:16.760> a<00:13:16.959> proof 00:13:17.710 --> 00:13:17.720 align:start position:0% since the Gateway is passing a proof 00:13:17.720 --> 00:13:20.910 align:start position:0% since the Gateway is passing a proof like<00:13:18.360> it<00:13:18.560> cannot<00:13:18.880> be<00:13:19.040> tempered<00:13:19.600> with<00:13:20.199> uh<00:13:20.560> so 00:13:20.910 --> 00:13:20.920 align:start position:0% like it cannot be tempered with uh so 00:13:20.920 --> 00:13:22.949 align:start position:0% like it cannot be tempered with uh so there<00:13:21.040> is<00:13:21.240> no<00:13:21.440> additional<00:13:22.000> trans<00:13:22.360> assumption 00:13:22.949 --> 00:13:22.959 align:start position:0% there is no additional trans assumption 00:13:22.959 --> 00:13:27.750 align:start position:0% there is no additional trans assumption regarding<00:13:23.600> like<00:13:24.399> the<00:13:25.399> um<00:13:25.880> accuracy<00:13:26.480> of<00:13:26.639> the 00:13:27.750 --> 00:13:27.760 align:start position:0% regarding like the um accuracy of the 00:13:27.760 --> 00:13:30.470 align:start position:0% regarding like the um accuracy of the data<00:13:28.760> we<00:13:28.880> have<00:13:29.440> uh<00:13:29.639> another<00:13:29.959> question<00:13:30.279> keep 00:13:30.470 --> 00:13:30.480 align:start position:0% data we have uh another question keep 00:13:30.480 --> 00:13:32.430 align:start position:0% data we have uh another question keep them<00:13:30.639> coming<00:13:31.000> guys<00:13:31.199> we<00:13:31.360> we<00:13:31.440> still<00:13:31.639> have<00:13:31.880> time 00:13:32.430 --> 00:13:32.440 align:start position:0% them coming guys we we still have time 00:13:32.440 --> 00:13:36.030 align:start position:0% them coming guys we we still have time um<00:13:33.120> does<00:13:33.279> it<00:13:33.480> open<00:13:33.839> up<00:13:34.399> to<00:13:34.639> a<00:13:34.839> temporal<00:13:35.440> attack 00:13:36.030 --> 00:13:36.040 align:start position:0% um does it open up to a temporal attack 00:13:36.040 --> 00:13:38.509 align:start position:0% um does it open up to a temporal attack if<00:13:36.199> the<00:13:36.320> L2<00:13:36.760> storage<00:13:37.199> proof<00:13:37.480> is<00:13:37.680> not<00:13:37.920> posted<00:13:38.320> on 00:13:38.509 --> 00:13:38.519 align:start position:0% if the L2 storage proof is not posted on 00:13:38.519 --> 00:13:42.150 align:start position:0% if the L2 storage proof is not posted on L1<00:13:39.120> yet<00:13:40.120> yeah<00:13:40.560> that<00:13:40.760> that's<00:13:40.920> a<00:13:41.120> very<00:13:41.440> good<00:13:41.880> good 00:13:42.150 --> 00:13:42.160 align:start position:0% L1 yet yeah that that's a very good good 00:13:42.160 --> 00:13:45.069 align:start position:0% L1 yet yeah that that's a very good good question<00:13:42.720> so<00:13:43.279> you<00:13:43.440> are<00:13:43.600> aware<00:13:44.000> that<00:13:44.360> like<00:13:44.560> l2s 00:13:45.069 --> 00:13:45.079 align:start position:0% question so you are aware that like l2s 00:13:45.079 --> 00:13:48.110 align:start position:0% question so you are aware that like l2s are<00:13:45.240> not<00:13:45.519> finalizing<00:13:46.399> like<00:13:47.279> like<00:13:47.600> every 00:13:48.110 --> 00:13:48.120 align:start position:0% are not finalizing like like every 00:13:48.120 --> 00:13:51.069 align:start position:0% are not finalizing like like every second<00:13:48.480> or<00:13:48.680> minutes<00:13:49.519> on<00:13:49.680> on<00:13:49.839> L1<00:13:50.680> and<00:13:50.800> so 00:13:51.069 --> 00:13:51.079 align:start position:0% second or minutes on on L1 and so 00:13:51.079 --> 00:13:53.470 align:start position:0% second or minutes on on L1 and so basically<00:13:51.800> you<00:13:51.959> don't<00:13:52.240> have<00:13:52.519> the<00:13:53.000> the<00:13:53.199> state 00:13:53.470 --> 00:13:53.480 align:start position:0% basically you don't have the the state 00:13:53.480 --> 00:13:56.189 align:start position:0% basically you don't have the the state of<00:13:53.800> L2<00:13:54.800> uh<00:13:55.079> like<00:13:55.240> before<00:13:55.639> is<00:13:55.839> getting 00:13:56.189 --> 00:13:56.199 align:start position:0% of L2 uh like before is getting 00:13:56.199 --> 00:14:00.189 align:start position:0% of L2 uh like before is getting finalized<00:13:57.079> so<00:13:57.440> on<00:13:57.720> the<00:13:57.959> like<00:13:58.120> Z<00:13:58.519> rollup<00:13:59.199> can<00:13:59.360> be 00:14:00.189 --> 00:14:00.199 align:start position:0% finalized so on the like Z rollup can be 00:14:00.199 --> 00:14:02.910 align:start position:0% finalized so on the like Z rollup can be uh<00:14:00.639> from<00:14:00.959> a<00:14:01.160> few<00:14:01.360> minutes<00:14:01.759> to<00:14:02.160> to<00:14:02.440> hours 00:14:02.910 --> 00:14:02.920 align:start position:0% uh from a few minutes to to hours 00:14:02.920 --> 00:14:05.150 align:start position:0% uh from a few minutes to to hours depending<00:14:03.600> on<00:14:03.759> the<00:14:04.000> layer<00:14:04.320> tools<00:14:04.920> on 00:14:05.150 --> 00:14:05.160 align:start position:0% depending on the layer tools on 00:14:05.160 --> 00:14:07.150 align:start position:0% depending on the layer tools on optimistic<00:14:05.680> rollup<00:14:06.199> it's<00:14:06.440> like<00:14:06.600> the<00:14:06.720> seven 00:14:07.150 --> 00:14:07.160 align:start position:0% optimistic rollup it's like the seven 00:14:07.160 --> 00:14:10.509 align:start position:0% optimistic rollup it's like the seven days<00:14:07.880> so<00:14:08.480> this<00:14:08.639> means<00:14:09.040> that<00:14:09.320> you<00:14:09.480> need<00:14:09.680> to<00:14:10.199> to 00:14:10.509 --> 00:14:10.519 align:start position:0% days so this means that you need to to 00:14:10.519 --> 00:14:13.870 align:start position:0% days so this means that you need to to wait<00:14:11.240> this<00:14:11.480> period<00:14:12.079> in<00:14:12.199> order<00:14:12.560> to<00:14:13.320> fetch<00:14:13.680> the 00:14:13.870 --> 00:14:13.880 align:start position:0% wait this period in order to fetch the 00:14:13.880 --> 00:14:16.790 align:start position:0% wait this period in order to fetch the data<00:14:14.279> so<00:14:14.680> there<00:14:14.839> is<00:14:15.079> this<00:14:15.360> latency<00:14:16.360> uh<00:14:16.519> but 00:14:16.790 --> 00:14:16.800 align:start position:0% data so there is this latency uh but 00:14:16.800 --> 00:14:19.910 align:start position:0% data so there is this latency uh but like<00:14:17.440> as<00:14:17.680> the<00:14:18.040> space<00:14:18.440> evolve<00:14:18.839> and<00:14:19.079> we<00:14:19.199> are 00:14:19.910 --> 00:14:19.920 align:start position:0% like as the space evolve and we are 00:14:19.920 --> 00:14:23.069 align:start position:0% like as the space evolve and we are going<00:14:20.240> to<00:14:20.639> faster<00:14:21.440> finality<00:14:22.440> uh<00:14:22.560> hopefully 00:14:23.069 --> 00:14:23.079 align:start position:0% going to faster finality uh hopefully 00:14:23.079 --> 00:14:25.069 align:start position:0% going to faster finality uh hopefully this<00:14:23.199> will<00:14:23.399> get<00:14:23.600> better<00:14:24.360> I<00:14:24.480> don't<00:14:24.720> think<00:14:24.959> there 00:14:25.069 --> 00:14:25.079 align:start position:0% this will get better I don't think there 00:14:25.079 --> 00:14:28.629 align:start position:0% this will get better I don't think there is<00:14:25.240> an<00:14:25.519> attack<00:14:26.440> uh<00:14:26.920> it's<00:14:27.120> just<00:14:27.399> that<00:14:27.720> like<00:14:28.000> the 00:14:28.629 --> 00:14:28.639 align:start position:0% is an attack uh it's just that like the 00:14:28.639 --> 00:14:31.509 align:start position:0% is an attack uh it's just that like the client<00:14:29.199> and<00:14:29.440> smart<00:14:30.440> contract<00:14:30.880> need<00:14:31.079> to<00:14:31.240> be 00:14:31.509 --> 00:14:31.519 align:start position:0% client and smart contract need to be 00:14:31.519 --> 00:14:34.629 align:start position:0% client and smart contract need to be aware<00:14:31.839> of<00:14:32.040> this<00:14:32.240> limitation<00:14:33.040> and<00:14:33.480> like<00:14:34.320> work 00:14:34.629 --> 00:14:34.639 align:start position:0% aware of this limitation and like work 00:14:34.639 --> 00:14:36.150 align:start position:0% aware of this limitation and like work with<00:14:34.800> it<00:14:35.000> at<00:14:35.120> the 00:14:36.150 --> 00:14:36.160 align:start position:0% with it at the 00:14:36.160 --> 00:14:39.069 align:start position:0% with it at the moment<00:14:37.160> what<00:14:37.399> libraries<00:14:38.000> already<00:14:38.560> implement 00:14:39.069 --> 00:14:39.079 align:start position:0% moment what libraries already implement 00:14:39.079 --> 00:14:39.829 align:start position:0% moment what libraries already implement this 00:14:39.829 --> 00:14:39.839 align:start position:0% this 00:14:39.839 --> 00:14:44.069 align:start position:0% this behavior<00:14:40.839> um<00:14:41.360> if<00:14:41.639> if<00:14:42.120> that<00:14:42.320> GS<00:14:42.920> for<00:14:43.120> sure<00:14:43.839> uh 00:14:44.069 --> 00:14:44.079 align:start position:0% behavior um if if that GS for sure uh 00:14:44.079 --> 00:14:47.910 align:start position:0% behavior um if if that GS for sure uh wag<00:14:44.320> me<00:14:44.519> as<00:14:44.720> well<00:14:45.440> uh<00:14:45.639> unrug<00:14:46.560> is<00:14:46.759> creating<00:14:47.279> a 00:14:47.910 --> 00:14:47.920 align:start position:0% wag me as well uh unrug is creating a 00:14:47.920 --> 00:14:50.790 align:start position:0% wag me as well uh unrug is creating a like<00:14:48.800> higher<00:14:49.160> level<00:14:49.519> abstraction<00:14:50.320> to<00:14:50.519> work 00:14:50.790 --> 00:14:50.800 align:start position:0% like higher level abstraction to work 00:14:50.800 --> 00:14:52.790 align:start position:0% like higher level abstraction to work across<00:14:51.120> chain<00:14:51.440> so<00:14:51.680> you<00:14:51.800> don't<00:14:52.079> even<00:14:52.480> have<00:14:52.600> to 00:14:52.790 --> 00:14:52.800 align:start position:0% across chain so you don't even have to 00:14:52.800 --> 00:14:57.269 align:start position:0% across chain so you don't even have to worry<00:14:53.199> about<00:14:54.040> like<00:14:54.560> uh<00:14:54.880> the<00:14:55.120> specific<00:14:55.959> of<00:14:56.279> the 00:14:57.269 --> 00:14:57.279 align:start position:0% worry about like uh the specific of the 00:14:57.279 --> 00:14:59.749 align:start position:0% worry about like uh the specific of the um<00:14:57.680> each<00:14:57.959> gateways<00:14:58.519> and<00:14:58.680> so<00:14:58.800> on<00:14:59.079> as<00:14:59.160> a<00:14:59.279> builder 00:14:59.749 --> 00:14:59.759 align:start position:0% um each gateways and so on as a builder 00:14:59.759 --> 00:15:02.350 align:start position:0% um each gateways and so on as a builder that<00:14:59.880> wants<00:15:00.120> to<00:15:00.440> to<00:15:00.639> rely<00:15:01.320> on<00:15:01.440> your<00:15:01.639> own 00:15:02.350 --> 00:15:02.360 align:start position:0% that wants to to rely on your own 00:15:02.360 --> 00:15:05.749 align:start position:0% that wants to to rely on your own Gateway<00:15:03.360> um<00:15:04.160> those<00:15:04.320> are<00:15:04.560> the<00:15:04.720> libraries<00:15:05.320> I 00:15:05.749 --> 00:15:05.759 align:start position:0% Gateway um those are the libraries I 00:15:05.759 --> 00:15:09.110 align:start position:0% Gateway um those are the libraries I know<00:15:06.759> is<00:15:07.000> there<00:15:07.240> any<00:15:07.560> L<00:15:07.839> work<00:15:08.320> latency<00:15:08.959> when 00:15:09.110 --> 00:15:09.120 align:start position:0% know is there any L work latency when 00:15:09.120 --> 00:15:10.990 align:start position:0% know is there any L work latency when reading 00:15:10.990 --> 00:15:11.000 align:start position:0% reading 00:15:11.000 --> 00:15:13.829 align:start position:0% reading data<00:15:12.000> um<00:15:12.480> so<00:15:12.759> yeah<00:15:13.040> the<00:15:13.279> it's<00:15:13.519> the 00:15:13.829 --> 00:15:13.839 align:start position:0% data um so yeah the it's the 00:15:13.839 --> 00:15:16.509 align:start position:0% data um so yeah the it's the finalization<00:15:14.639> latent<00:15:15.160> latency<00:15:15.839> so<00:15:16.240> as<00:15:16.360> I 00:15:16.509 --> 00:15:16.519 align:start position:0% finalization latent latency so as I 00:15:16.519 --> 00:15:19.470 align:start position:0% finalization latent latency so as I mentioned<00:15:17.440> like<00:15:17.880> from<00:15:18.079> a<00:15:18.240> few<00:15:18.440> minutes<00:15:18.800> to 00:15:19.470 --> 00:15:19.480 align:start position:0% mentioned like from a few minutes to 00:15:19.480 --> 00:15:22.470 align:start position:0% mentioned like from a few minutes to seven<00:15:19.880> days<00:15:20.120> if<00:15:20.240> you're<00:15:20.440> on<00:15:20.800> optimistic 00:15:22.470 --> 00:15:22.480 align:start position:0% seven days if you're on optimistic 00:15:22.480 --> 00:15:26.110 align:start position:0% seven days if you're on optimistic rollup<00:15:23.480> but<00:15:23.880> like<00:15:24.199> from<00:15:24.440> the<00:15:24.639> network<00:15:25.360> latency 00:15:26.110 --> 00:15:26.120 align:start position:0% rollup but like from the network latency 00:15:26.120 --> 00:15:30.269 align:start position:0% rollup but like from the network latency really<00:15:26.720> like<00:15:27.160> it's<00:15:27.720> really<00:15:28.720> uh<00:15:29.120> quick<00:15:29.880> like 00:15:30.269 --> 00:15:30.279 align:start position:0% really like it's really uh quick like 00:15:30.279 --> 00:15:32.629 align:start position:0% really like it's really uh quick like usually<00:15:30.839> less<00:15:31.120> than<00:15:31.240> a<00:15:31.440> second<00:15:31.839> or<00:15:32.079> even<00:15:32.399> less 00:15:32.629 --> 00:15:32.639 align:start position:0% usually less than a second or even less 00:15:32.639 --> 00:15:36.389 align:start position:0% usually less than a second or even less so<00:15:33.319> you<00:15:33.519> you<00:15:33.680> can<00:15:33.880> test<00:15:34.160> it<00:15:34.360> and<00:15:34.720> like<00:15:35.360> type<00:15:36.120> for 00:15:36.389 --> 00:15:36.399 align:start position:0% so you you can test it and like type for 00:15:36.399 --> 00:15:40.269 align:start position:0% so you you can test it and like type for instance<00:15:36.839> like<00:15:37.440> arur<00:15:37.880> do.if<00:15:38.880> on<00:15:39.160> the<00:15:39.880> on<00:15:40.079> your 00:15:40.269 --> 00:15:40.279 align:start position:0% instance like arur do.if on the on your 00:15:40.279 --> 00:15:43.030 align:start position:0% instance like arur do.if on the on your metamask<00:15:40.959> or<00:15:41.120> on<00:15:41.360> the<00:15:41.600> ens<00:15:42.079> website<00:15:42.480> and<00:15:42.720> you 00:15:43.030 --> 00:15:43.040 align:start position:0% metamask or on the ens website and you 00:15:43.040 --> 00:15:45.550 align:start position:0% metamask or on the ens website and you you<00:15:43.120> will<00:15:43.279> see<00:15:43.600> like<00:15:44.040> the<00:15:44.319> answer<00:15:44.680> is<00:15:45.079> almost 00:15:45.550 --> 00:15:45.560 align:start position:0% you will see like the answer is almost 00:15:45.560 --> 00:15:47.839 align:start position:0% you will see like the answer is almost uh