WEBVTT Kind: captions Language: en 00:00:01.010 --> 00:00:06.630 align:start position:0% [Music] 00:00:06.630 --> 00:00:06.640 align:start position:0% [Music] 00:00:06.640 --> 00:00:10.589 align:start position:0% [Music] hello<00:00:07.280> everyone<00:00:08.280> um<00:00:08.840> excited<00:00:09.200> to<00:00:09.360> be<00:00:09.599> here<00:00:10.320> uh 00:00:10.589 --> 00:00:10.599 align:start position:0% hello everyone um excited to be here uh 00:00:10.599 --> 00:00:13.589 align:start position:0% hello everyone um excited to be here uh I<00:00:10.719> am<00:00:11.040> the<00:00:11.240> CEO<00:00:11.679> of<00:00:11.799> polygon<00:00:12.280> labs<00:00:13.200> for<00:00:13.440> those 00:00:13.589 --> 00:00:13.599 align:start position:0% I am the CEO of polygon labs for those 00:00:13.599 --> 00:00:16.269 align:start position:0% I am the CEO of polygon labs for those of<00:00:13.719> you<00:00:13.920> who<00:00:14.120> don't<00:00:14.360> know<00:00:14.599> polygon<00:00:15.120> Labs<00:00:15.920> or 00:00:16.269 --> 00:00:16.279 align:start position:0% of you who don't know polygon Labs or 00:00:16.279 --> 00:00:17.910 align:start position:0% of you who don't know polygon Labs or specifically<00:00:16.720> who<00:00:16.880> don't<00:00:17.039> know<00:00:17.240> what<00:00:17.480> polygon 00:00:17.910 --> 00:00:17.920 align:start position:0% specifically who don't know what polygon 00:00:17.920 --> 00:00:20.550 align:start position:0% specifically who don't know what polygon Labs<00:00:18.279> does<00:00:18.760> because<00:00:18.960> we<00:00:19.080> do<00:00:19.279> many<00:00:19.560> things<00:00:20.439> uh 00:00:20.550 --> 00:00:20.560 align:start position:0% Labs does because we do many things uh 00:00:20.560 --> 00:00:22.950 align:start position:0% Labs does because we do many things uh we<00:00:20.680> are<00:00:20.880> a<00:00:21.080> core<00:00:21.320> contributor<00:00:21.920> to<00:00:22.199> the<00:00:22.359> Ager 00:00:22.950 --> 00:00:22.960 align:start position:0% we are a core contributor to the Ager 00:00:22.960 --> 00:00:25.230 align:start position:0% we are a core contributor to the Ager along<00:00:23.279> with<00:00:23.519> many<00:00:23.720> others<00:00:24.519> we've<00:00:24.800> also 00:00:25.230 --> 00:00:25.240 align:start position:0% along with many others we've also 00:00:25.240 --> 00:00:27.310 align:start position:0% along with many others we've also developed<00:00:25.840> multiple<00:00:26.320> blockchains<00:00:27.000> being 00:00:27.310 --> 00:00:27.320 align:start position:0% developed multiple blockchains being 00:00:27.320 --> 00:00:29.230 align:start position:0% developed multiple blockchains being polygon<00:00:27.800> POS<00:00:28.400> that<00:00:28.560> pretty<00:00:28.720> much<00:00:28.920> everyone 00:00:29.230 --> 00:00:29.240 align:start position:0% polygon POS that pretty much everyone 00:00:29.240 --> 00:00:32.150 align:start position:0% polygon POS that pretty much everyone knows<00:00:29.759> as<00:00:29.960> as<00:00:30.119> well<00:00:30.320> as<00:00:30.720> uh<00:00:30.920> polygon 00:00:32.150 --> 00:00:32.160 align:start position:0% knows as as well as uh polygon 00:00:32.160 --> 00:00:35.150 align:start position:0% knows as as well as uh polygon zkm<00:00:33.160> so<00:00:34.120> I'm<00:00:34.239> going<00:00:34.320> to<00:00:34.480> go<00:00:34.640> through<00:00:34.840> like<00:00:34.960> a 00:00:35.150 --> 00:00:35.160 align:start position:0% zkm so I'm going to go through like a 00:00:35.160 --> 00:00:37.990 align:start position:0% zkm so I'm going to go through like a little<00:00:35.399> bit<00:00:35.680> of<00:00:35.960> of<00:00:36.239> History<00:00:36.920> before<00:00:37.559> actually 00:00:37.990 --> 00:00:38.000 align:start position:0% little bit of of History before actually 00:00:38.000 --> 00:00:41.190 align:start position:0% little bit of of History before actually kind<00:00:38.120> of<00:00:38.320> attacking<00:00:39.120> what<00:00:39.640> exactly<00:00:40.640> we<00:00:40.840> mean 00:00:41.190 --> 00:00:41.200 align:start position:0% kind of attacking what exactly we mean 00:00:41.200 --> 00:00:44.150 align:start position:0% kind of attacking what exactly we mean by<00:00:41.800> aggregation<00:00:42.800> um<00:00:43.360> and<00:00:43.640> specifically<00:00:44.039> when 00:00:44.150 --> 00:00:44.160 align:start position:0% by aggregation um and specifically when 00:00:44.160 --> 00:00:46.709 align:start position:0% by aggregation um and specifically when I<00:00:44.280> want<00:00:44.399> to<00:00:44.559> look<00:00:44.719> at<00:00:45.680> and<00:00:45.960> people<00:00:46.239> talk<00:00:46.440> a<00:00:46.520> lot 00:00:46.709 --> 00:00:46.719 align:start position:0% I want to look at and people talk a lot 00:00:46.719 --> 00:00:48.630 align:start position:0% I want to look at and people talk a lot about<00:00:46.960> like<00:00:47.120> not<00:00:47.800> kind<00:00:47.920> of<00:00:48.160> looking<00:00:48.440> at 00:00:48.630 --> 00:00:48.640 align:start position:0% about like not kind of looking at 00:00:48.640 --> 00:00:50.990 align:start position:0% about like not kind of looking at analogies<00:00:49.440> but<00:00:50.000> if<00:00:50.120> we<00:00:50.239> think<00:00:50.399> of<00:00:50.559> like<00:00:50.719> what 00:00:50.990 --> 00:00:51.000 align:start position:0% analogies but if we think of like what 00:00:51.000 --> 00:00:53.950 align:start position:0% analogies but if we think of like what we<00:00:51.280> want<00:00:51.600> web<00:00:51.800> 3<00:00:52.039> to<00:00:52.199> be<00:00:53.039> um<00:00:53.320> we<00:00:53.480> really<00:00:53.640> want<00:00:53.800> it 00:00:53.950 --> 00:00:53.960 align:start position:0% we want web 3 to be um we really want it 00:00:53.960 --> 00:00:56.670 align:start position:0% we want web 3 to be um we really want it to<00:00:54.120> eat<00:00:54.359> as<00:00:54.520> much<00:00:54.680> of<00:00:55.039> web<00:00:55.280> 2<00:00:55.680> up<00:00:55.960> as<00:00:56.199> possible 00:00:56.670 --> 00:00:56.680 align:start position:0% to eat as much of web 2 up as possible 00:00:56.680 --> 00:00:58.150 align:start position:0% to eat as much of web 2 up as possible Right<00:00:56.920> like<00:00:57.039> we<00:00:57.120> should<00:00:57.320> be<00:00:57.440> able<00:00:57.600> to<00:00:57.800> scale 00:00:58.150 --> 00:00:58.160 align:start position:0% Right like we should be able to scale 00:00:58.160 --> 00:01:01.189 align:start position:0% Right like we should be able to scale web<00:00:58.359> 3<00:00:58.600> to<00:00:58.800> the<00:00:59.039> size<00:00:59.440> of<00:00:59.600> web<00:01:00.000> too<00:01:00.760> and<00:01:00.840> so<00:01:01.079> the 00:01:01.189 --> 00:01:01.199 align:start position:0% web 3 to the size of web too and so the 00:01:01.199 --> 00:01:03.389 align:start position:0% web 3 to the size of web too and so the question<00:01:01.519> then<00:01:01.719> becomes<00:01:02.480> well<00:01:03.000> you<00:01:03.079> know<00:01:03.280> how 00:01:03.389 --> 00:01:03.399 align:start position:0% question then becomes well you know how 00:01:03.399 --> 00:01:05.670 align:start position:0% question then becomes well you know how did<00:01:03.559> the<00:01:03.719> internet<00:01:04.199> become<00:01:04.519> the<00:01:04.680> internet<00:01:05.360> and 00:01:05.670 --> 00:01:05.680 align:start position:0% did the internet become the internet and 00:01:05.680 --> 00:01:07.350 align:start position:0% did the internet become the internet and if<00:01:05.799> you<00:01:05.960> think<00:01:06.159> about<00:01:06.400> it<00:01:06.840> the<00:01:06.960> internet 00:01:07.350 --> 00:01:07.360 align:start position:0% if you think about it the internet 00:01:07.360 --> 00:01:10.469 align:start position:0% if you think about it the internet actually<00:01:07.600> started<00:01:08.360> very<00:01:09.000> fragmented<00:01:10.000> um<00:01:10.200> it 00:01:10.469 --> 00:01:10.479 align:start position:0% actually started very fragmented um it 00:01:10.479 --> 00:01:12.510 align:start position:0% actually started very fragmented um it very<00:01:10.680> disconnected<00:01:11.400> with<00:01:11.560> multiple<00:01:11.960> networks 00:01:12.510 --> 00:01:12.520 align:start position:0% very disconnected with multiple networks 00:01:12.520 --> 00:01:15.270 align:start position:0% very disconnected with multiple networks unable<00:01:12.880> to<00:01:13.560> communicate<00:01:14.560> and<00:01:14.720> then<00:01:15.000> new 00:01:15.270 --> 00:01:15.280 align:start position:0% unable to communicate and then new 00:01:15.280 --> 00:01:19.550 align:start position:0% unable to communicate and then new protocols<00:01:16.080> came<00:01:16.400> along<00:01:17.400> um<00:01:18.000> and<00:01:18.680> specifically 00:01:19.550 --> 00:01:19.560 align:start position:0% protocols came along um and specifically 00:01:19.560 --> 00:01:24.069 align:start position:0% protocols came along um and specifically things<00:01:19.840> like<00:01:20.240> TCP<00:01:21.240> IP<00:01:22.119> came<00:01:22.360> along<00:01:23.200> and<00:01:23.960> what 00:01:24.069 --> 00:01:24.079 align:start position:0% things like TCP IP came along and what 00:01:24.079 --> 00:01:26.310 align:start position:0% things like TCP IP came along and what you<00:01:24.240> now<00:01:24.479> had<00:01:24.640> what<00:01:24.720> you<00:01:24.840> suddenly<00:01:25.320> had<00:01:25.680> was 00:01:26.310 --> 00:01:26.320 align:start position:0% you now had what you suddenly had was 00:01:26.320 --> 00:01:29.910 align:start position:0% you now had what you suddenly had was this<00:01:27.040> diversity<00:01:28.040> in<00:01:29.000> uh<00:01:29.159> what<00:01:29.280> could<00:01:29.439> be<00:01:29.640> built 00:01:29.910 --> 00:01:29.920 align:start position:0% this diversity in uh what could be built 00:01:29.920 --> 00:01:32.510 align:start position:0% this diversity in uh what could be built bu<00:01:30.400> on<00:01:30.600> the<00:01:30.799> internet<00:01:31.799> um<00:01:32.159> and<00:01:32.360> the 00:01:32.510 --> 00:01:32.520 align:start position:0% bu on the internet um and the 00:01:32.520 --> 00:01:34.749 align:start position:0% bu on the internet um and the infrastructure<00:01:33.280> underlying<00:01:33.840> it<00:01:34.399> but<00:01:34.600> with 00:01:34.749 --> 00:01:34.759 align:start position:0% infrastructure underlying it but with 00:01:34.759 --> 00:01:37.910 align:start position:0% infrastructure underlying it but with some<00:01:35.360> common<00:01:36.360> protocols<00:01:37.360> um<00:01:37.680> and 00:01:37.910 --> 00:01:37.920 align:start position:0% some common protocols um and 00:01:37.920 --> 00:01:40.109 align:start position:0% some common protocols um and specifically<00:01:38.360> what<00:01:38.439> you<00:01:38.600> get<00:01:38.799> there<00:01:39.079> is 00:01:40.109 --> 00:01:40.119 align:start position:0% specifically what you get there is 00:01:40.119 --> 00:01:42.630 align:start position:0% specifically what you get there is tcpip<00:01:41.119> and<00:01:41.720> it's<00:01:42.040> very<00:01:42.200> important<00:01:42.479> to 00:01:42.630 --> 00:01:42.640 align:start position:0% tcpip and it's very important to 00:01:42.640 --> 00:01:44.350 align:start position:0% tcpip and it's very important to actually<00:01:43.119> understand<00:01:43.360> this<00:01:43.600> because<00:01:44.119> a<00:01:44.240> lot 00:01:44.350 --> 00:01:44.360 align:start position:0% actually understand this because a lot 00:01:44.360 --> 00:01:46.109 align:start position:0% actually understand this because a lot of<00:01:44.479> people<00:01:44.799> say<00:01:45.119> like<00:01:45.320> how<00:01:45.479> are<00:01:45.560> we<00:01:45.680> going<00:01:45.920> to 00:01:46.109 --> 00:01:46.119 align:start position:0% of people say like how are we going to 00:01:46.119 --> 00:01:48.630 align:start position:0% of people say like how are we going to bring<00:01:46.600> together<00:01:47.320> all<00:01:47.479> of<00:01:47.680> web<00:01:47.920> 3<00:01:48.280> when<00:01:48.399> you've 00:01:48.630 --> 00:01:48.640 align:start position:0% bring together all of web 3 when you've 00:01:48.640 --> 00:01:50.990 align:start position:0% bring together all of web 3 when you've got<00:01:48.840> so<00:01:49.040> much<00:01:49.520> disperate<00:01:50.040> technology<00:01:50.600> in<00:01:50.799> web 00:01:50.990 --> 00:01:51.000 align:start position:0% got so much disperate technology in web 00:01:51.000 --> 00:01:53.590 align:start position:0% got so much disperate technology in web 3<00:01:51.600> you've<00:01:51.840> got<00:01:52.079> different<00:01:52.520> Stacks<00:01:53.119> you've<00:01:53.360> got 00:01:53.590 --> 00:01:53.600 align:start position:0% 3 you've got different Stacks you've got 00:01:53.600 --> 00:01:56.389 align:start position:0% 3 you've got different Stacks you've got different<00:01:54.119> VMS<00:01:54.840> like<00:01:55.479> everything<00:01:55.960> looks 00:01:56.389 --> 00:01:56.399 align:start position:0% different VMS like everything looks 00:01:56.399 --> 00:01:58.270 align:start position:0% different VMS like everything looks different<00:01:57.360> but<00:01:57.479> we<00:01:57.640> actually<00:01:57.920> have<00:01:58.079> an 00:01:58.270 --> 00:01:58.280 align:start position:0% different but we actually have an 00:01:58.280 --> 00:02:00.109 align:start position:0% different but we actually have an example<00:01:58.799> of<00:01:58.920> bringing<00:01:59.360> together<00:01:59.640> different 00:02:00.109 --> 00:02:00.119 align:start position:0% example of bringing together different 00:02:00.119 --> 00:02:02.350 align:start position:0% example of bringing together different technology<00:02:00.719> in<00:02:00.799> a<00:02:00.960> way<00:02:01.159> that<00:02:01.320> like<00:02:01.479> unifies<00:02:02.039> it 00:02:02.350 --> 00:02:02.360 align:start position:0% technology in a way that like unifies it 00:02:02.360 --> 00:02:05.190 align:start position:0% technology in a way that like unifies it and<00:02:02.600> actually<00:02:03.000> feels<00:02:03.439> like<00:02:03.840> one<00:02:04.840> so<00:02:05.039> let's 00:02:05.190 --> 00:02:05.200 align:start position:0% and actually feels like one so let's 00:02:05.200 --> 00:02:06.749 align:start position:0% and actually feels like one so let's talk<00:02:05.360> about<00:02:05.560> like<00:02:05.799> specific<00:02:06.200> problems<00:02:06.520> we<00:02:06.600> see 00:02:06.749 --> 00:02:06.759 align:start position:0% talk about like specific problems we see 00:02:06.759 --> 00:02:08.790 align:start position:0% talk about like specific problems we see in<00:02:06.880> web<00:02:07.079> 3<00:02:07.280> and<00:02:07.439> why<00:02:07.600> this<00:02:07.719> is<00:02:07.960> actually<00:02:08.399> very 00:02:08.790 --> 00:02:08.800 align:start position:0% in web 3 and why this is actually very 00:02:08.800 --> 00:02:11.229 align:start position:0% in web 3 and why this is actually very relevant<00:02:09.800> right<00:02:10.080> we've<00:02:10.319> got<00:02:10.599> fragmentation 00:02:11.229 --> 00:02:11.239 align:start position:0% relevant right we've got fragmentation 00:02:11.239 --> 00:02:12.830 align:start position:0% relevant right we've got fragmentation as<00:02:11.360> an<00:02:11.560> issue<00:02:12.040> I<00:02:12.120> think<00:02:12.280> this<00:02:12.360> is<00:02:12.440> an<00:02:12.599> obvious 00:02:12.830 --> 00:02:12.840 align:start position:0% as an issue I think this is an obvious 00:02:12.840 --> 00:02:16.150 align:start position:0% as an issue I think this is an obvious one<00:02:13.000> for<00:02:13.160> everyone<00:02:14.080> scalability<00:02:15.160> security 00:02:16.150 --> 00:02:16.160 align:start position:0% one for everyone scalability security 00:02:16.160 --> 00:02:19.869 align:start position:0% one for everyone scalability security and<00:02:16.640> frankly<00:02:17.080> just<00:02:17.319> poor<00:02:17.720> ux<00:02:18.720> if<00:02:18.840> we<00:02:19.120> look<00:02:19.319> at 00:02:19.869 --> 00:02:19.879 align:start position:0% and frankly just poor ux if we look at 00:02:19.879 --> 00:02:21.869 align:start position:0% and frankly just poor ux if we look at each<00:02:20.040> of<00:02:20.239> these<00:02:20.480> one<00:02:20.720> by<00:02:20.879> one<00:02:21.360> what<00:02:21.440> do<00:02:21.560> we<00:02:21.680> have 00:02:21.869 --> 00:02:21.879 align:start position:0% each of these one by one what do we have 00:02:21.879 --> 00:02:24.229 align:start position:0% each of these one by one what do we have right<00:02:22.000> now<00:02:22.120> we've<00:02:22.280> got<00:02:22.400> a<00:02:22.480> bunch<00:02:22.640> of<00:02:22.800> chains<00:02:23.800> uh 00:02:24.229 --> 00:02:24.239 align:start position:0% right now we've got a bunch of chains uh 00:02:24.239 --> 00:02:26.350 align:start position:0% right now we've got a bunch of chains uh and<00:02:24.440> liquidity<00:02:24.920> is<00:02:25.120> fragmented<00:02:25.800> across<00:02:26.239> all 00:02:26.350 --> 00:02:26.360 align:start position:0% and liquidity is fragmented across all 00:02:26.360 --> 00:02:29.070 align:start position:0% and liquidity is fragmented across all of<00:02:26.519> these<00:02:26.720> chains<00:02:27.720> we<00:02:27.920> really<00:02:28.200> have<00:02:28.480> no<00:02:28.800> good 00:02:29.070 --> 00:02:29.080 align:start position:0% of these chains we really have no good 00:02:29.080 --> 00:02:32.830 align:start position:0% of these chains we really have no good way<00:02:29.640> of<00:02:30.040> bringing<00:02:30.319> them<00:02:30.680> together<00:02:31.400> at<00:02:31.840> all 00:02:32.830 --> 00:02:32.840 align:start position:0% way of bringing them together at all 00:02:32.840 --> 00:02:34.750 align:start position:0% way of bringing them together at all similarly<00:02:33.680> we've<00:02:33.840> got<00:02:33.959> a<00:02:34.080> scalability 00:02:34.750 --> 00:02:34.760 align:start position:0% similarly we've got a scalability 00:02:34.760 --> 00:02:37.710 align:start position:0% similarly we've got a scalability problem<00:02:35.480> if<00:02:35.640> we<00:02:35.840> want<00:02:36.160> web<00:02:36.400> 3<00:02:36.680> to<00:02:37.000> scale<00:02:37.360> to<00:02:37.519> the 00:02:37.710 --> 00:02:37.720 align:start position:0% problem if we want web 3 to scale to the 00:02:37.720 --> 00:02:40.229 align:start position:0% problem if we want web 3 to scale to the size<00:02:38.400> of<00:02:38.640> the<00:02:38.760> internet<00:02:39.720> then<00:02:39.920> we<00:02:40.000> should 00:02:40.229 --> 00:02:40.239 align:start position:0% size of the internet then we should 00:02:40.239 --> 00:02:41.990 align:start position:0% size of the internet then we should probably<00:02:40.560> compare<00:02:40.879> to<00:02:41.080> like<00:02:41.319> what<00:02:41.519> currently 00:02:41.990 --> 00:02:42.000 align:start position:0% probably compare to like what currently 00:02:42.000 --> 00:02:44.470 align:start position:0% probably compare to like what currently is<00:02:42.120> using<00:02:42.440> the<00:02:42.800> internet<00:02:43.800> and<00:02:44.080> when<00:02:44.200> we<00:02:44.360> look 00:02:44.470 --> 00:02:44.480 align:start position:0% is using the internet and when we look 00:02:44.480 --> 00:02:46.949 align:start position:0% is using the internet and when we look at<00:02:44.640> that<00:02:44.800> what<00:02:44.920> we<00:02:45.040> see<00:02:45.319> things<00:02:45.640> is<00:02:45.959> Mastercard 00:02:46.949 --> 00:02:46.959 align:start position:0% at that what we see things is Mastercard 00:02:46.959 --> 00:02:52.430 align:start position:0% at that what we see things is Mastercard Visa<00:02:48.159> NASDAQ<00:02:49.159> um<00:02:49.680> and<00:02:50.519> I<00:02:51.519> do<00:02:51.720> not<00:02:51.920> believe<00:02:52.239> we 00:02:52.430 --> 00:02:52.440 align:start position:0% Visa NASDAQ um and I do not believe we 00:02:52.440 --> 00:02:54.030 align:start position:0% Visa NASDAQ um and I do not believe we actually<00:02:52.720> have<00:02:52.879> a<00:02:53.040> network<00:02:53.440> that<00:02:53.560> can<00:02:53.720> handle 00:02:54.030 --> 00:02:54.040 align:start position:0% actually have a network that can handle 00:02:54.040 --> 00:02:56.550 align:start position:0% actually have a network that can handle the<00:02:54.120> load<00:02:54.360> of<00:02:54.560> any<00:02:54.720> of<00:02:55.000> those<00:02:56.000> I<00:02:56.120> think<00:02:56.319> we've 00:02:56.550 --> 00:02:56.560 align:start position:0% the load of any of those I think we've 00:02:56.560 --> 00:02:58.710 align:start position:0% the load of any of those I think we've heard<00:02:56.920> many<00:02:57.319> state<00:02:57.840> that<00:02:58.159> they<00:02:58.360> want 00:02:58.710 --> 00:02:58.720 align:start position:0% heard many state that they want 00:02:58.720 --> 00:03:01.790 align:start position:0% heard many state that they want blockchains<00:02:59.280> to<00:02:59.400> be<00:02:59.560> able<00:02:59.959> to<00:03:00.280> handle<00:03:01.280> um<00:03:01.680> you 00:03:01.790 --> 00:03:01.800 align:start position:0% blockchains to be able to handle um you 00:03:01.800 --> 00:03:06.789 align:start position:0% blockchains to be able to handle um you know<00:03:02.319> a<00:03:02.680> a<00:03:03.080> load<00:03:03.720> like<00:03:04.159> NASDAQ<00:03:05.159> and<00:03:05.680> that<00:03:05.799> is 00:03:06.789 --> 00:03:06.799 align:start position:0% know a a load like NASDAQ and that is 00:03:06.799 --> 00:03:10.589 align:start position:0% know a a load like NASDAQ and that is 250,000<00:03:07.799> transactions<00:03:08.799> per<00:03:09.080> second<00:03:10.000> which<00:03:10.319> no 00:03:10.589 --> 00:03:10.599 align:start position:0% 250,000 transactions per second which no 00:03:10.599 --> 00:03:12.990 align:start position:0% 250,000 transactions per second which no network<00:03:11.000> is<00:03:11.200> even<00:03:11.799> close<00:03:12.239> to<00:03:12.440> being<00:03:12.680> able<00:03:12.840> to 00:03:12.990 --> 00:03:13.000 align:start position:0% network is even close to being able to 00:03:13.000 --> 00:03:15.470 align:start position:0% network is even close to being able to handle<00:03:13.319> in<00:03:13.480> any<00:03:13.680> way<00:03:14.120> whatsoever<00:03:15.120> uh<00:03:15.319> I 00:03:15.470 --> 00:03:15.480 align:start position:0% handle in any way whatsoever uh I 00:03:15.480 --> 00:03:17.710 align:start position:0% handle in any way whatsoever uh I actually<00:03:15.879> just<00:03:16.120> as<00:03:16.200> a<00:03:16.640> little<00:03:16.920> side<00:03:17.159> note<00:03:17.560> I'll 00:03:17.710 --> 00:03:17.720 align:start position:0% actually just as a little side note I'll 00:03:17.720 --> 00:03:18.990 align:start position:0% actually just as a little side note I'll give<00:03:17.840> you<00:03:17.920> a<00:03:18.000> few<00:03:18.200> side<00:03:18.400> notes<00:03:18.640> during<00:03:18.840> this 00:03:18.990 --> 00:03:19.000 align:start position:0% give you a few side notes during this 00:03:19.000 --> 00:03:20.350 align:start position:0% give you a few side notes during this presentation<00:03:19.519> but<00:03:19.640> this<00:03:19.760> is<00:03:19.879> a<00:03:20.080> little 00:03:20.350 --> 00:03:20.360 align:start position:0% presentation but this is a little 00:03:20.360 --> 00:03:22.509 align:start position:0% presentation but this is a little interesting<00:03:20.879> fact<00:03:21.239> is<00:03:21.680> let's<00:03:21.920> just<00:03:22.159> assume 00:03:22.509 --> 00:03:22.519 align:start position:0% interesting fact is let's just assume 00:03:22.519 --> 00:03:24.869 align:start position:0% interesting fact is let's just assume that<00:03:22.680> we<00:03:22.799> could<00:03:23.120> actually<00:03:24.120> scale<00:03:24.680> a 00:03:24.869 --> 00:03:24.879 align:start position:0% that we could actually scale a 00:03:24.879 --> 00:03:27.830 align:start position:0% that we could actually scale a blockchain<00:03:25.480> to<00:03:25.720> the<00:03:25.879> size<00:03:26.120> of<00:03:26.519> NASDAQ<00:03:27.519> um 00:03:27.830 --> 00:03:27.840 align:start position:0% blockchain to the size of NASDAQ um 00:03:27.840 --> 00:03:29.789 align:start position:0% blockchain to the size of NASDAQ um NASDAQ<00:03:28.360> can<00:03:28.560> execute<00:03:29.000> transactions<00:03:29.480> with 00:03:29.789 --> 00:03:29.799 align:start position:0% NASDAQ can execute transactions with 00:03:29.799 --> 00:03:33.229 align:start position:0% NASDAQ can execute transactions with latency<00:03:30.239> of<00:03:30.439> 50<00:03:30.879> microc<00:03:31.599> seconds<00:03:32.599> um<00:03:32.840> you<00:03:33.000> are 00:03:33.229 --> 00:03:33.239 align:start position:0% latency of 50 microc seconds um you are 00:03:33.239 --> 00:03:35.149 align:start position:0% latency of 50 microc seconds um you are not<00:03:33.519> going<00:03:33.720> to<00:03:33.959> execute<00:03:34.400> any<00:03:34.599> transaction<00:03:35.040> on 00:03:35.149 --> 00:03:35.159 align:start position:0% not going to execute any transaction on 00:03:35.159 --> 00:03:37.990 align:start position:0% not going to execute any transaction on a<00:03:35.360> blockchain<00:03:36.040> in<00:03:36.280> 50<00:03:36.640> microc<00:03:37.040> seconds<00:03:37.799> so<00:03:37.920> I 00:03:37.990 --> 00:03:38.000 align:start position:0% a blockchain in 50 microc seconds so I 00:03:38.000 --> 00:03:39.869 align:start position:0% a blockchain in 50 microc seconds so I think<00:03:38.120> our<00:03:38.280> dreams<00:03:38.599> of<00:03:38.720> bringing<00:03:39.080> NASDAQ<00:03:39.599> on 00:03:39.869 --> 00:03:39.879 align:start position:0% think our dreams of bringing NASDAQ on 00:03:39.879 --> 00:03:41.830 align:start position:0% think our dreams of bringing NASDAQ on chain<00:03:40.400> should<00:03:40.720> probably<00:03:41.040> recognize<00:03:41.560> the<00:03:41.680> fact 00:03:41.830 --> 00:03:41.840 align:start position:0% chain should probably recognize the fact 00:03:41.840 --> 00:03:42.869 align:start position:0% chain should probably recognize the fact that<00:03:41.959> there's<00:03:42.159> some<00:03:42.360> things<00:03:42.560> that<00:03:42.680> are 00:03:42.869 --> 00:03:42.879 align:start position:0% that there's some things that are 00:03:42.879 --> 00:03:45.429 align:start position:0% that there's some things that are actually<00:03:43.239> better<00:03:43.920> in<00:03:44.040> a<00:03:44.280> centralized<00:03:44.920> State 00:03:45.429 --> 00:03:45.439 align:start position:0% actually better in a centralized State 00:03:45.439 --> 00:03:46.910 align:start position:0% actually better in a centralized State and<00:03:45.560> there's<00:03:45.840> some<00:03:46.000> things<00:03:46.200> that<00:03:46.319> are<00:03:46.480> better 00:03:46.910 --> 00:03:46.920 align:start position:0% and there's some things that are better 00:03:46.920 --> 00:03:49.869 align:start position:0% and there's some things that are better in<00:03:47.319> a<00:03:47.640> decentralized<00:03:48.400> state<00:03:49.360> obviously<00:03:49.760> this 00:03:49.869 --> 00:03:49.879 align:start position:0% in a decentralized state obviously this 00:03:49.879 --> 00:03:51.110 align:start position:0% in a decentralized state obviously this does<00:03:50.040> not<00:03:50.239> mean<00:03:50.480> that<00:03:50.599> we<00:03:50.680> don't<00:03:50.879> want 00:03:51.110 --> 00:03:51.120 align:start position:0% does not mean that we don't want 00:03:51.120 --> 00:03:52.869 align:start position:0% does not mean that we don't want decentralized<00:03:51.799> exchanges<00:03:52.400> it<00:03:52.519> means<00:03:52.760> that 00:03:52.869 --> 00:03:52.879 align:start position:0% decentralized exchanges it means that 00:03:52.879 --> 00:03:55.110 align:start position:0% decentralized exchanges it means that there's<00:03:53.319> specific<00:03:54.120> technologies<00:03:54.680> that<00:03:54.799> serve 00:03:55.110 --> 00:03:55.120 align:start position:0% there's specific technologies that serve 00:03:55.120 --> 00:03:57.270 align:start position:0% there's specific technologies that serve specific<00:03:55.519> purposes<00:03:56.480> and<00:03:56.720> you<00:03:56.840> know<00:03:57.000> we<00:03:57.079> should 00:03:57.270 --> 00:03:57.280 align:start position:0% specific purposes and you know we should 00:03:57.280 --> 00:03:59.270 align:start position:0% specific purposes and you know we should probably<00:03:57.599> focus<00:03:57.920> on<00:03:58.200> like<00:03:58.360> more<00:03:58.599> longtail 00:03:59.270 --> 00:03:59.280 align:start position:0% probably focus on like more longtail 00:03:59.280 --> 00:04:01.670 align:start position:0% probably focus on like more longtail assets<00:03:59.959> in<00:04:00.079> a<00:04:00.239> decentralized<00:04:01.079> way<00:04:01.360> when<00:04:01.519> we 00:04:01.670 --> 00:04:01.680 align:start position:0% assets in a decentralized way when we 00:04:01.680 --> 00:04:04.429 align:start position:0% assets in a decentralized way when we want<00:04:02.000> perfect<00:04:02.599> performance<00:04:03.239> execution<00:04:04.239> uh 00:04:04.429 --> 00:04:04.439 align:start position:0% want perfect performance execution uh 00:04:04.439 --> 00:04:05.830 align:start position:0% want perfect performance execution uh and<00:04:04.560> then<00:04:04.680> when<00:04:04.840> we<00:04:05.000> just<00:04:05.120> want<00:04:05.319> censorship 00:04:05.830 --> 00:04:05.840 align:start position:0% and then when we just want censorship 00:04:05.840 --> 00:04:07.589 align:start position:0% and then when we just want censorship resistance<00:04:06.439> then<00:04:06.760> we<00:04:06.840> should<00:04:07.079> probably<00:04:07.360> bring 00:04:07.589 --> 00:04:07.599 align:start position:0% resistance then we should probably bring 00:04:07.599 --> 00:04:10.149 align:start position:0% resistance then we should probably bring that<00:04:08.040> onchain<00:04:09.040> third<00:04:09.239> one<00:04:09.360> is<00:04:09.519> security<00:04:10.000> right 00:04:10.149 --> 00:04:10.159 align:start position:0% that onchain third one is security right 00:04:10.159 --> 00:04:11.949 align:start position:0% that onchain third one is security right now<00:04:10.640> you<00:04:10.760> know<00:04:10.879> when<00:04:11.000> you<00:04:11.159> look<00:04:11.319> at<00:04:11.519> like<00:04:11.680> many 00:04:11.949 --> 00:04:11.959 align:start position:0% now you know when you look at like many 00:04:11.959 --> 00:04:13.509 align:start position:0% now you know when you look at like many different<00:04:12.280> networks<00:04:12.680> and<00:04:12.840> how<00:04:13.000> they<00:04:13.159> come 00:04:13.509 --> 00:04:13.519 align:start position:0% different networks and how they come 00:04:13.519 --> 00:04:15.229 align:start position:0% different networks and how they come together<00:04:14.120> you<00:04:14.200> know<00:04:14.360> we<00:04:14.599> talk<00:04:14.799> about<00:04:14.959> concepts 00:04:15.229 --> 00:04:15.239 align:start position:0% together you know we talk about concepts 00:04:15.239 --> 00:04:17.150 align:start position:0% together you know we talk about concepts of<00:04:15.319> like<00:04:15.439> shared<00:04:15.680> sequencers<00:04:16.280> and<00:04:16.479> intents 00:04:17.150 --> 00:04:17.160 align:start position:0% of like shared sequencers and intents 00:04:17.160 --> 00:04:19.509 align:start position:0% of like shared sequencers and intents and<00:04:17.359> bridges<00:04:18.079> and<00:04:18.320> like<00:04:18.519> most<00:04:18.680> of<00:04:18.880> that<00:04:19.040> is<00:04:19.199> not 00:04:19.509 --> 00:04:19.519 align:start position:0% and bridges and like most of that is not 00:04:19.519 --> 00:04:21.710 align:start position:0% and bridges and like most of that is not actually<00:04:19.919> very<00:04:20.199> secure<00:04:20.959> even<00:04:21.280> though<00:04:21.519> it 00:04:21.710 --> 00:04:21.720 align:start position:0% actually very secure even though it 00:04:21.720 --> 00:04:25.710 align:start position:0% actually very secure even though it actually<00:04:22.040> works<00:04:23.000> decently<00:04:24.000> in<00:04:24.240> in<00:04:24.400> some<00:04:24.720> cases 00:04:25.710 --> 00:04:25.720 align:start position:0% actually works decently in in some cases 00:04:25.720 --> 00:04:28.590 align:start position:0% actually works decently in in some cases and<00:04:25.919> lastly<00:04:26.240> the<00:04:26.360> ux<00:04:26.759> challenge<00:04:27.560> we've<00:04:27.840> got<00:04:28.280> a 00:04:28.590 --> 00:04:28.600 align:start position:0% and lastly the ux challenge we've got a 00:04:28.600 --> 00:04:30.629 align:start position:0% and lastly the ux challenge we've got a a<00:04:28.759> ux<00:04:29.160> problem<00:04:29.400> whether<00:04:29.560> it's<00:04:29.919> cross<00:04:30.199> wallets 00:04:30.629 --> 00:04:30.639 align:start position:0% a ux problem whether it's cross wallets 00:04:30.639 --> 00:04:34.189 align:start position:0% a ux problem whether it's cross wallets Bridges<00:04:31.000> and<00:04:31.240> intents<00:04:32.440> chains<00:04:33.440> um<00:04:33.800> basically 00:04:34.189 --> 00:04:34.199 align:start position:0% Bridges and intents chains um basically 00:04:34.199 --> 00:04:36.230 align:start position:0% Bridges and intents chains um basically what<00:04:34.320> you<00:04:34.520> get<00:04:34.720> is<00:04:35.000> this<00:04:35.320> this<00:04:35.520> fragmented 00:04:36.230 --> 00:04:36.240 align:start position:0% what you get is this this fragmented 00:04:36.240 --> 00:04:39.070 align:start position:0% what you get is this this fragmented feeling<00:04:37.240> um<00:04:37.600> across<00:04:38.000> the<00:04:38.120> board<00:04:38.639> and<00:04:38.759> so<00:04:38.919> then 00:04:39.070 --> 00:04:39.080 align:start position:0% feeling um across the board and so then 00:04:39.080 --> 00:04:41.110 align:start position:0% feeling um across the board and so then the<00:04:39.240> question<00:04:39.600> becomes<00:04:40.479> what<00:04:40.560> do<00:04:40.680> you<00:04:40.880> do 00:04:41.110 --> 00:04:41.120 align:start position:0% the question becomes what do you do 00:04:41.120 --> 00:04:44.990 align:start position:0% the question becomes what do you do about<00:04:41.440> this<00:04:42.440> um<00:04:43.039> and<00:04:43.880> the<00:04:44.039> first<00:04:44.360> answer<00:04:44.840> that 00:04:44.990 --> 00:04:45.000 align:start position:0% about this um and the first answer that 00:04:45.000 --> 00:04:47.310 align:start position:0% about this um and the first answer that we<00:04:45.199> tried<00:04:45.680> to<00:04:45.919> give<00:04:46.080> or<00:04:46.240> that<00:04:46.400> many<00:04:46.680> do<00:04:46.919> still 00:04:47.310 --> 00:04:47.320 align:start position:0% we tried to give or that many do still 00:04:47.320 --> 00:04:49.749 align:start position:0% we tried to give or that many do still give<00:04:47.919> is<00:04:48.479> let's<00:04:48.680> just<00:04:48.840> use<00:04:49.039> a<00:04:49.240> monolithic 00:04:49.749 --> 00:04:49.759 align:start position:0% give is let's just use a monolithic 00:04:49.759 --> 00:04:52.749 align:start position:0% give is let's just use a monolithic chain<00:04:50.440> salana<00:04:51.000> can<00:04:51.160> solve<00:04:51.520> this<00:04:51.720> for<00:04:51.919> you 00:04:52.749 --> 00:04:52.759 align:start position:0% chain salana can solve this for you 00:04:52.759 --> 00:04:56.110 align:start position:0% chain salana can solve this for you because<00:04:53.759> something<00:04:54.160> something<00:04:54.560> something<00:04:55.560> um 00:04:56.110 --> 00:04:56.120 align:start position:0% because something something something um 00:04:56.120 --> 00:04:57.510 align:start position:0% because something something something um well<00:04:56.400> you<00:04:56.520> know<00:04:56.680> most<00:04:56.840> of<00:04:56.960> the<00:04:57.080> time<00:04:57.280> that 00:04:57.510 --> 00:04:57.520 align:start position:0% well you know most of the time that 00:04:57.520 --> 00:04:59.310 align:start position:0% well you know most of the time that something<00:04:58.039> isn't<00:04:58.280> going<00:04:58.360> to<00:04:58.479> be<00:04:58.639> good<00:04:58.880> enough 00:04:59.310 --> 00:04:59.320 align:start position:0% something isn't going to be good enough 00:04:59.320 --> 00:05:01.950 align:start position:0% something isn't going to be good enough because<00:05:00.039> literally<00:05:00.759> we<00:05:01.160> have<00:05:01.320> seen<00:05:01.639> that<00:05:01.800> we 00:05:01.950 --> 00:05:01.960 align:start position:0% because literally we have seen that we 00:05:01.960 --> 00:05:04.590 align:start position:0% because literally we have seen that we can't<00:05:02.199> even<00:05:02.440> scale<00:05:03.120> to<00:05:03.360> some<00:05:03.479> of<00:05:03.680> the<00:05:04.039> the<00:05:04.240> the 00:05:04.590 --> 00:05:04.600 align:start position:0% can't even scale to some of the the the 00:05:04.600 --> 00:05:06.909 align:start position:0% can't even scale to some of the the the smallest<00:05:05.600> networks<00:05:06.199> that<00:05:06.280> are<00:05:06.520> good<00:05:06.680> for 00:05:06.909 --> 00:05:06.919 align:start position:0% smallest networks that are good for 00:05:06.919 --> 00:05:08.990 align:start position:0% smallest networks that are good for payments<00:05:07.479> in<00:05:07.639> the<00:05:07.800> world<00:05:08.280> or<00:05:08.520> the<00:05:08.639> biggest 00:05:08.990 --> 00:05:09.000 align:start position:0% payments in the world or the biggest 00:05:09.000 --> 00:05:11.629 align:start position:0% payments in the world or the biggest ones<00:05:09.960> uh<00:05:10.120> and<00:05:10.240> so<00:05:10.520> like<00:05:10.720> the<00:05:10.880> idea<00:05:11.360> that<00:05:11.520> like 00:05:11.629 --> 00:05:11.639 align:start position:0% ones uh and so like the idea that like 00:05:11.639 --> 00:05:13.070 align:start position:0% ones uh and so like the idea that like we're<00:05:11.800> going<00:05:11.919> to<00:05:12.039> throw<00:05:12.360> everything<00:05:12.680> on<00:05:12.840> one 00:05:13.070 --> 00:05:13.080 align:start position:0% we're going to throw everything on one 00:05:13.080 --> 00:05:16.150 align:start position:0% we're going to throw everything on one chain<00:05:13.639> is<00:05:13.960> not<00:05:14.240> happening<00:05:15.039> and<00:05:15.240> so<00:05:15.680> we<00:05:15.800> need<00:05:15.919> to 00:05:16.150 --> 00:05:16.160 align:start position:0% chain is not happening and so we need to 00:05:16.160 --> 00:05:18.189 align:start position:0% chain is not happening and so we need to go<00:05:16.400> look<00:05:16.880> at<00:05:17.199> another 00:05:18.189 --> 00:05:18.199 align:start position:0% go look at another 00:05:18.199 --> 00:05:22.110 align:start position:0% go look at another solution<00:05:19.199> uh<00:05:19.360> the<00:05:19.479> other<00:05:19.840> solution<00:05:20.840> um<00:05:21.319> was 00:05:22.110 --> 00:05:22.120 align:start position:0% solution uh the other solution um was 00:05:22.120 --> 00:05:24.550 align:start position:0% solution uh the other solution um was why<00:05:22.240> don't<00:05:22.440> we<00:05:22.639> just<00:05:22.919> scale<00:05:23.680> through<00:05:24.120> modular 00:05:24.550 --> 00:05:24.560 align:start position:0% why don't we just scale through modular 00:05:24.560 --> 00:05:27.070 align:start position:0% why don't we just scale through modular chains<00:05:25.560> right<00:05:25.880> but<00:05:26.039> the<00:05:26.199> problem<00:05:26.479> is<00:05:26.680> modular 00:05:27.070 --> 00:05:27.080 align:start position:0% chains right but the problem is modular 00:05:27.080 --> 00:05:29.230 align:start position:0% chains right but the problem is modular chains<00:05:27.680> increase<00:05:28.120> fragmentation<00:05:28.800> we<00:05:28.919> see<00:05:29.120> it 00:05:29.230 --> 00:05:29.240 align:start position:0% chains increase fragmentation we see it 00:05:29.240 --> 00:05:32.150 align:start position:0% chains increase fragmentation we see it today<00:05:29.720> you've<00:05:29.960> got<00:05:30.360> you<00:05:30.479> know<00:05:30.720> polygon<00:05:31.440> zkm 00:05:32.150 --> 00:05:32.160 align:start position:0% today you've got you know polygon zkm 00:05:32.160 --> 00:05:35.270 align:start position:0% today you've got you know polygon zkm polygon<00:05:32.560> POS<00:05:33.319> you've<00:05:33.560> got<00:05:34.000> ZK<00:05:34.400> sync<00:05:34.720> era 00:05:35.270 --> 00:05:35.280 align:start position:0% polygon POS you've got ZK sync era 00:05:35.280 --> 00:05:37.150 align:start position:0% polygon POS you've got ZK sync era you've<00:05:35.600> got<00:05:35.880> you<00:05:35.960> know<00:05:36.120> arbitrum<00:05:36.639> one<00:05:36.960> you've 00:05:37.150 --> 00:05:37.160 align:start position:0% you've got you know arbitrum one you've 00:05:37.160 --> 00:05:39.029 align:start position:0% you've got you know arbitrum one you've got<00:05:37.319> open<00:05:37.680> main<00:05:37.960> net<00:05:38.160> you<00:05:38.280> could<00:05:38.440> keep<00:05:38.720> going 00:05:39.029 --> 00:05:39.039 align:start position:0% got open main net you could keep going 00:05:39.039 --> 00:05:42.110 align:start position:0% got open main net you could keep going on<00:05:39.240> and<00:05:39.400> on<00:05:40.319> and<00:05:40.680> like<00:05:40.960> great<00:05:41.319> this<00:05:41.400> is<00:05:41.680> nice 00:05:42.110 --> 00:05:42.120 align:start position:0% on and on and like great this is nice 00:05:42.120 --> 00:05:44.710 align:start position:0% on and on and like great this is nice like<00:05:42.720> being<00:05:43.039> able<00:05:43.319> to<00:05:43.639> choose<00:05:44.240> how<00:05:44.400> you<00:05:44.560> want 00:05:44.710 --> 00:05:44.720 align:start position:0% like being able to choose how you want 00:05:44.720 --> 00:05:47.749 align:start position:0% like being able to choose how you want to<00:05:44.960> spin<00:05:45.240> up<00:05:45.400> a<00:05:45.639> chain<00:05:46.639> is<00:05:46.919> great<00:05:47.280> it<00:05:47.440> actually 00:05:47.749 --> 00:05:47.759 align:start position:0% to spin up a chain is great it actually 00:05:47.759 --> 00:05:49.830 align:start position:0% to spin up a chain is great it actually solves<00:05:48.319> the<00:05:48.479> scalability<00:05:49.199> issue<00:05:49.560> right 00:05:49.830 --> 00:05:49.840 align:start position:0% solves the scalability issue right 00:05:49.840 --> 00:05:51.270 align:start position:0% solves the scalability issue right because<00:05:50.120> now<00:05:50.280> when<00:05:50.400> you<00:05:50.520> need<00:05:50.759> more<00:05:50.960> block 00:05:51.270 --> 00:05:51.280 align:start position:0% because now when you need more block 00:05:51.280 --> 00:05:53.430 align:start position:0% because now when you need more block space<00:05:52.160> What<00:05:52.240> do<00:05:52.319> you<00:05:52.479> do<00:05:52.639> you<00:05:52.800> spin<00:05:53.039> up<00:05:53.160> a<00:05:53.280> new 00:05:53.430 --> 00:05:53.440 align:start position:0% space What do you do you spin up a new 00:05:53.440 --> 00:05:55.990 align:start position:0% space What do you do you spin up a new chain<00:05:54.280> and<00:05:54.520> with<00:05:54.800> time<00:05:55.360> this<00:05:55.479> is<00:05:55.720> actually 00:05:55.990 --> 00:05:56.000 align:start position:0% chain and with time this is actually 00:05:56.000 --> 00:05:58.270 align:start position:0% chain and with time this is actually going<00:05:56.160> to<00:05:56.400> get<00:05:56.639> easier<00:05:57.039> and<00:05:57.199> easier<00:05:58.039> right 00:05:58.270 --> 00:05:58.280 align:start position:0% going to get easier and easier right 00:05:58.280 --> 00:06:00.110 align:start position:0% going to get easier and easier right like<00:05:58.520> right<00:05:58.720> now<00:05:59.120> people<00:05:59.360> want<00:05:59.639> to<00:05:59.759> sell<00:06:00.000> you 00:06:00.110 --> 00:06:00.120 align:start position:0% like right now people want to sell you 00:06:00.120 --> 00:06:01.990 align:start position:0% like right now people want to sell you on<00:06:00.280> the<00:06:00.440> idea<00:06:00.800> that<00:06:00.919> spinning<00:06:01.280> up<00:06:01.400> a<00:06:01.560> new<00:06:01.720> chain 00:06:01.990 --> 00:06:02.000 align:start position:0% on the idea that spinning up a new chain 00:06:02.000 --> 00:06:04.189 align:start position:0% on the idea that spinning up a new chain is<00:06:02.199> easy<00:06:02.919> like<00:06:03.080> frankly<00:06:03.440> it's<00:06:03.639> actually<00:06:03.960> not 00:06:04.189 --> 00:06:04.199 align:start position:0% is easy like frankly it's actually not 00:06:04.199 --> 00:06:06.430 align:start position:0% is easy like frankly it's actually not that<00:06:04.360> easy<00:06:05.120> uh<00:06:05.280> but<00:06:05.400> if<00:06:05.479> you<00:06:05.680> fast<00:06:05.880> forward<00:06:06.199> 12 00:06:06.430 --> 00:06:06.440 align:start position:0% that easy uh but if you fast forward 12 00:06:06.440 --> 00:06:08.189 align:start position:0% that easy uh but if you fast forward 12 months<00:06:06.720> from<00:06:06.880> now<00:06:07.080> and<00:06:07.240> 24<00:06:07.759> months<00:06:07.960> from<00:06:08.080> now 00:06:08.189 --> 00:06:08.199 align:start position:0% months from now and 24 months from now 00:06:08.199 --> 00:06:09.950 align:start position:0% months from now and 24 months from now and<00:06:08.319> 36<00:06:08.720> months<00:06:09.000> from<00:06:09.160> now<00:06:09.599> you're<00:06:09.720> going<00:06:09.840> to 00:06:09.950 --> 00:06:09.960 align:start position:0% and 36 months from now you're going to 00:06:09.960 --> 00:06:11.830 align:start position:0% and 36 months from now you're going to get<00:06:10.039> to<00:06:10.199> a<00:06:10.360> point<00:06:10.680> where<00:06:11.080> spinning<00:06:11.440> up<00:06:11.560> a<00:06:11.680> new 00:06:11.830 --> 00:06:11.840 align:start position:0% get to a point where spinning up a new 00:06:11.840 --> 00:06:14.230 align:start position:0% get to a point where spinning up a new chain<00:06:12.120> is<00:06:12.280> actually<00:06:12.639> incredibly<00:06:13.240> easy<00:06:13.960> and 00:06:14.230 --> 00:06:14.240 align:start position:0% chain is actually incredibly easy and 00:06:14.240 --> 00:06:17.350 align:start position:0% chain is actually incredibly easy and when<00:06:14.360> you<00:06:14.520> need<00:06:14.720> to<00:06:15.440> increase<00:06:16.440> um<00:06:16.720> throughput 00:06:17.350 --> 00:06:17.360 align:start position:0% when you need to increase um throughput 00:06:17.360 --> 00:06:18.990 align:start position:0% when you need to increase um throughput and<00:06:17.520> increase<00:06:17.960> block<00:06:18.199> space<00:06:18.639> then<00:06:18.800> you're 00:06:18.990 --> 00:06:19.000 align:start position:0% and increase block space then you're 00:06:19.000 --> 00:06:21.670 align:start position:0% and increase block space then you're going<00:06:19.199> to<00:06:19.800> spin<00:06:20.080> up<00:06:20.160> a<00:06:20.319> new<00:06:20.479> chain<00:06:20.960> to<00:06:21.400> actually 00:06:21.670 --> 00:06:21.680 align:start position:0% going to spin up a new chain to actually 00:06:21.680 --> 00:06:24.670 align:start position:0% going to spin up a new chain to actually be<00:06:21.840> able<00:06:22.039> to<00:06:22.199> do<00:06:22.440> that<00:06:23.199> um<00:06:23.400> and<00:06:23.599> so<00:06:24.360> through 00:06:24.670 --> 00:06:24.680 align:start position:0% be able to do that um and so through 00:06:24.680 --> 00:06:27.430 align:start position:0% be able to do that um and so through like<00:06:24.840> kind<00:06:24.960> of<00:06:25.160> the<00:06:25.360> the<00:06:25.520> modular<00:06:26.319> approach<00:06:27.319> we 00:06:27.430 --> 00:06:27.440 align:start position:0% like kind of the the modular approach we 00:06:27.440 --> 00:06:30.110 align:start position:0% like kind of the the modular approach we can<00:06:27.639> actually<00:06:27.960> solve<00:06:28.599> scalability<00:06:29.880> the 00:06:30.110 --> 00:06:30.120 align:start position:0% can actually solve scalability the 00:06:30.120 --> 00:06:33.070 align:start position:0% can actually solve scalability the problem<00:06:30.479> is<00:06:31.319> we<00:06:31.520> still<00:06:31.800> don't<00:06:32.160> have<00:06:32.479> one 00:06:33.070 --> 00:06:33.080 align:start position:0% problem is we still don't have one 00:06:33.080 --> 00:06:36.990 align:start position:0% problem is we still don't have one unified<00:06:34.080> web<00:06:34.360> three<00:06:35.000> if<00:06:35.120> we<00:06:35.280> do<00:06:35.520> that<00:06:36.360> and<00:06:36.560> so 00:06:36.990 --> 00:06:37.000 align:start position:0% unified web three if we do that and so 00:06:37.000 --> 00:06:39.350 align:start position:0% unified web three if we do that and so the<00:06:37.160> answer<00:06:37.360> to<00:06:37.560> this<00:06:38.000> is<00:06:38.199> just<00:06:38.440> aggregate<00:06:39.199> all 00:06:39.350 --> 00:06:39.360 align:start position:0% the answer to this is just aggregate all 00:06:39.360 --> 00:06:42.550 align:start position:0% the answer to this is just aggregate all the<00:06:39.599> chains<00:06:40.599> and<00:06:40.800> so<00:06:41.479> what<00:06:41.639> does<00:06:41.919> aggregation 00:06:42.550 --> 00:06:42.560 align:start position:0% the chains and so what does aggregation 00:06:42.560 --> 00:06:45.070 align:start position:0% the chains and so what does aggregation actually<00:06:42.840> allow<00:06:43.160> for<00:06:44.160> it<00:06:44.360> actually<00:06:44.560> allows<00:06:44.919> us 00:06:45.070 --> 00:06:45.080 align:start position:0% actually allow for it actually allows us 00:06:45.080 --> 00:06:47.830 align:start position:0% actually allow for it actually allows us to<00:06:45.319> scale<00:06:45.800> web<00:06:46.000> 3<00:06:46.400> to<00:06:46.759> the<00:06:46.960> size<00:06:47.479> of<00:06:47.680> the 00:06:47.830 --> 00:06:47.840 align:start position:0% to scale web 3 to the size of the 00:06:47.840 --> 00:06:49.469 align:start position:0% to scale web 3 to the size of the internet<00:06:48.599> what<00:06:48.720> are<00:06:48.840> the<00:06:49.000> things<00:06:49.199> that<00:06:49.319> we 00:06:49.469 --> 00:06:49.479 align:start position:0% internet what are the things that we 00:06:49.479 --> 00:06:51.670 align:start position:0% internet what are the things that we need<00:06:49.720> to<00:06:49.919> do<00:06:50.160> this<00:06:50.759> first<00:06:51.039> we<00:06:51.160> need 00:06:51.670 --> 00:06:51.680 align:start position:0% need to do this first we need 00:06:51.680 --> 00:06:55.510 align:start position:0% need to do this first we need practically<00:06:52.560> infinite<00:06:53.960> scalability<00:06:54.960> and 00:06:55.510 --> 00:06:55.520 align:start position:0% practically infinite scalability and 00:06:55.520 --> 00:06:57.909 align:start position:0% practically infinite scalability and that's<00:06:56.039> what<00:06:56.199> you<00:06:56.479> get<00:06:57.000> when<00:06:57.160> you<00:06:57.280> can<00:06:57.479> spin<00:06:57.720> up 00:06:57.909 --> 00:06:57.919 align:start position:0% that's what you get when you can spin up 00:06:57.919 --> 00:07:00.589 align:start position:0% that's what you get when you can spin up new<00:06:58.120> chains<00:06:58.639> very<00:06:58.879> easily<00:06:59.360> when<00:06:59.840> more<00:07:00.080> demand 00:07:00.589 --> 00:07:00.599 align:start position:0% new chains very easily when more demand 00:07:00.599 --> 00:07:02.790 align:start position:0% new chains very easily when more demand is<00:07:00.800> needed<00:07:01.680> because<00:07:02.000> there's<00:07:02.360> or<00:07:02.560> when<00:07:02.680> there 00:07:02.790 --> 00:07:02.800 align:start position:0% is needed because there's or when there 00:07:02.800 --> 00:07:04.550 align:start position:0% is needed because there's or when there is<00:07:02.960> more<00:07:03.120> demand<00:07:03.520> and<00:07:03.599> so<00:07:03.800> more<00:07:04.039> block<00:07:04.280> space 00:07:04.550 --> 00:07:04.560 align:start position:0% is more demand and so more block space 00:07:04.560 --> 00:07:06.629 align:start position:0% is more demand and so more block space is<00:07:04.680> needed<00:07:05.560> uh<00:07:05.680> and<00:07:05.759> then<00:07:05.919> the<00:07:06.039> second<00:07:06.280> one<00:07:06.520> is 00:07:06.629 --> 00:07:06.639 align:start position:0% is needed uh and then the second one is 00:07:06.639 --> 00:07:09.110 align:start position:0% is needed uh and then the second one is you<00:07:06.759> need<00:07:06.879> to<00:07:06.960> be<00:07:07.080> able<00:07:07.240> to<00:07:07.360> like<00:07:07.560> unify<00:07:08.120> State 00:07:09.110 --> 00:07:09.120 align:start position:0% you need to be able to like unify State 00:07:09.120 --> 00:07:10.670 align:start position:0% you need to be able to like unify State liquidity 00:07:10.670 --> 00:07:10.680 align:start position:0% liquidity 00:07:10.680 --> 00:07:12.990 align:start position:0% liquidity users<00:07:11.680> and<00:07:11.800> if<00:07:11.919> you<00:07:12.080> really<00:07:12.280> think<00:07:12.440> of<00:07:12.639> like 00:07:12.990 --> 00:07:13.000 align:start position:0% users and if you really think of like 00:07:13.000 --> 00:07:14.950 align:start position:0% users and if you really think of like the<00:07:13.199> north<00:07:13.560> star<00:07:13.960> of<00:07:14.199> what<00:07:14.400> we<00:07:14.520> should<00:07:14.759> be 00:07:14.950 --> 00:07:14.960 align:start position:0% the north star of what we should be 00:07:14.960 --> 00:07:17.390 align:start position:0% the north star of what we should be targeting<00:07:15.919> we<00:07:16.039> should<00:07:16.400> really<00:07:16.759> want<00:07:17.000> to<00:07:17.199> be 00:07:17.390 --> 00:07:17.400 align:start position:0% targeting we should really want to be 00:07:17.400 --> 00:07:22.430 align:start position:0% targeting we should really want to be able<00:07:17.639> to<00:07:18.000> have<00:07:19.160> a<00:07:20.160> web<00:07:20.440> 3<00:07:21.400> and<00:07:21.560> an<00:07:21.720> ethereum 00:07:22.430 --> 00:07:22.440 align:start position:0% able to have a web 3 and an ethereum 00:07:22.440 --> 00:07:25.350 align:start position:0% able to have a web 3 and an ethereum that<00:07:22.919> scales<00:07:23.919> as<00:07:24.080> much<00:07:24.280> as<00:07:24.360> you<00:07:24.520> need<00:07:25.080> in<00:07:25.199> a 00:07:25.350 --> 00:07:25.360 align:start position:0% that scales as much as you need in a 00:07:25.360 --> 00:07:27.869 align:start position:0% that scales as much as you need in a unified<00:07:26.000> way<00:07:26.599> making<00:07:26.879> you<00:07:27.120> believe<00:07:27.599> that<00:07:27.720> you 00:07:27.869 --> 00:07:27.879 align:start position:0% unified way making you believe that you 00:07:27.879 --> 00:07:31.110 align:start position:0% unified way making you believe that you are<00:07:28.080> using<00:07:28.800> one<00:07:29.039> chain<00:07:29.720> while<00:07:29.960> you<00:07:30.080> are<00:07:30.319> using 00:07:31.110 --> 00:07:31.120 align:start position:0% are using one chain while you are using 00:07:31.120 --> 00:07:33.550 align:start position:0% are using one chain while you are using 100,000<00:07:31.960> different<00:07:32.280> chains<00:07:32.759> at<00:07:32.919> any<00:07:33.160> point<00:07:33.360> in 00:07:33.550 --> 00:07:33.560 align:start position:0% 100,000 different chains at any point in 00:07:33.560 --> 00:07:36.670 align:start position:0% 100,000 different chains at any point in time<00:07:34.520> and<00:07:34.879> that<00:07:35.039> that<00:07:35.240> 100,000<00:07:36.000> chains<00:07:36.479> can 00:07:36.670 --> 00:07:36.680 align:start position:0% time and that that 100,000 chains can 00:07:36.680 --> 00:07:39.550 align:start position:0% time and that that 100,000 chains can become<00:07:37.479> 125,000<00:07:38.400> chains<00:07:38.840> at<00:07:38.960> any<00:07:39.160> point<00:07:39.360> in 00:07:39.550 --> 00:07:39.560 align:start position:0% become 125,000 chains at any point in 00:07:39.560 --> 00:07:42.110 align:start position:0% become 125,000 chains at any point in time<00:07:39.919> and<00:07:40.039> it<00:07:40.199> still<00:07:40.440> feels<00:07:40.960> like<00:07:41.240> one 00:07:42.110 --> 00:07:42.120 align:start position:0% time and it still feels like one 00:07:42.120 --> 00:07:44.430 align:start position:0% time and it still feels like one internet<00:07:43.120> so<00:07:43.599> when<00:07:43.800> we've<00:07:44.039> thought<00:07:44.240> about 00:07:44.430 --> 00:07:44.440 align:start position:0% internet so when we've thought about 00:07:44.440 --> 00:07:45.869 align:start position:0% internet so when we've thought about this<00:07:44.639> problem<00:07:44.919> and<00:07:45.080> how<00:07:45.199> we<00:07:45.319> want<00:07:45.440> to<00:07:45.599> solve 00:07:45.869 --> 00:07:45.879 align:start position:0% this problem and how we want to solve 00:07:45.879 --> 00:07:48.790 align:start position:0% this problem and how we want to solve this<00:07:46.080> problem<00:07:46.560> exactly<00:07:47.560> um<00:07:48.199> we<00:07:48.400> started 00:07:48.790 --> 00:07:48.800 align:start position:0% this problem exactly um we started 00:07:48.800 --> 00:07:51.110 align:start position:0% this problem exactly um we started thinking<00:07:49.199> about<00:07:49.440> it<00:07:50.080> um<00:07:50.360> and<00:07:50.479> we<00:07:50.639> realized 00:07:51.110 --> 00:07:51.120 align:start position:0% thinking about it um and we realized 00:07:51.120 --> 00:07:53.629 align:start position:0% thinking about it um and we realized that<00:07:51.280> we<00:07:51.400> needed<00:07:51.680> to<00:07:51.919> create<00:07:52.319> like<00:07:52.440> a<00:07:52.680> neutral 00:07:53.629 --> 00:07:53.639 align:start position:0% that we needed to create like a neutral 00:07:53.639 --> 00:07:56.869 align:start position:0% that we needed to create like a neutral platform<00:07:54.639> um<00:07:54.919> and<00:07:55.120> so<00:07:55.759> this<00:07:55.919> is<00:07:56.400> concept<00:07:56.720> of 00:07:56.869 --> 00:07:56.879 align:start position:0% platform um and so this is concept of 00:07:56.879 --> 00:07:59.589 align:start position:0% platform um and so this is concept of the<00:07:57.000> a<00:07:57.599> layer<00:07:58.599> polygon<00:07:58.960> Labs<00:07:59.159> is<00:07:59.240> a 00:07:59.589 --> 00:07:59.599 align:start position:0% the a layer polygon Labs is a 00:07:59.599 --> 00:08:01.309 align:start position:0% the a layer polygon Labs is a contributor<00:08:00.199> along<00:08:00.440> with<00:08:00.599> many<00:08:00.840> others<00:08:01.159> that 00:08:01.309 --> 00:08:01.319 align:start position:0% contributor along with many others that 00:08:01.319 --> 00:08:03.550 align:start position:0% contributor along with many others that I<00:08:01.400> will<00:08:01.599> show<00:08:01.840> you<00:08:02.319> uh<00:08:02.440> a<00:08:02.520> little<00:08:02.720> bit<00:08:02.919> later 00:08:03.550 --> 00:08:03.560 align:start position:0% I will show you uh a little bit later 00:08:03.560 --> 00:08:05.270 align:start position:0% I will show you uh a little bit later later<00:08:03.879> but<00:08:04.000> the<00:08:04.159> general<00:08:04.479> idea<00:08:04.840> was<00:08:05.000> that<00:08:05.120> we 00:08:05.270 --> 00:08:05.280 align:start position:0% later but the general idea was that we 00:08:05.280 --> 00:08:07.589 align:start position:0% later but the general idea was that we need<00:08:05.599> some<00:08:05.840> kind<00:08:05.960> of<00:08:06.199> like<00:08:06.599> neutral 00:08:07.589 --> 00:08:07.599 align:start position:0% need some kind of like neutral 00:08:07.599 --> 00:08:09.629 align:start position:0% need some kind of like neutral cross-chain<00:08:08.319> settlement<00:08:08.919> platform<00:08:09.520> that 00:08:09.629 --> 00:08:09.639 align:start position:0% cross-chain settlement platform that 00:08:09.639 --> 00:08:12.790 align:start position:0% cross-chain settlement platform that unifies<00:08:10.159> liquidity<00:08:10.680> users<00:08:11.039> and<00:08:11.360> state<00:08:12.360> um<00:08:12.639> and 00:08:12.790 --> 00:08:12.800 align:start position:0% unifies liquidity users and state um and 00:08:12.800 --> 00:08:17.390 align:start position:0% unifies liquidity users and state um and that<00:08:13.479> ultimately<00:08:14.479> has<00:08:14.800> finality<00:08:15.599> on<00:08:16.400> ethereum 00:08:17.390 --> 00:08:17.400 align:start position:0% that ultimately has finality on ethereum 00:08:17.400 --> 00:08:20.390 align:start position:0% that ultimately has finality on ethereum now<00:08:18.080> very<00:08:18.400> importantly<00:08:19.400> the<00:08:19.560> a<00:08:19.800> layer<00:08:20.080> is 00:08:20.390 --> 00:08:20.400 align:start position:0% now very importantly the a layer is 00:08:20.400 --> 00:08:23.309 align:start position:0% now very importantly the a layer is actually<00:08:20.840> not<00:08:21.120> intended<00:08:21.800> to<00:08:22.080> scale<00:08:22.680> only 00:08:23.309 --> 00:08:23.319 align:start position:0% actually not intended to scale only 00:08:23.319 --> 00:08:26.189 align:start position:0% actually not intended to scale only ethereum<00:08:24.319> and<00:08:24.680> there's<00:08:24.840> a<00:08:25.000> reason<00:08:25.280> for<00:08:25.479> this 00:08:26.189 --> 00:08:26.199 align:start position:0% ethereum and there's a reason for this 00:08:26.199 --> 00:08:30.270 align:start position:0% ethereum and there's a reason for this which<00:08:26.360> is<00:08:26.680> that<00:08:27.280> as<00:08:27.720> amazing<00:08:28.400> as<00:08:28.680> ethereum<00:08:29.240> is 00:08:30.270 --> 00:08:30.280 align:start position:0% which is that as amazing as ethereum is 00:08:30.280 --> 00:08:32.670 align:start position:0% which is that as amazing as ethereum is what<00:08:30.400> do<00:08:30.599> people<00:08:30.919> actually<00:08:31.240> value<00:08:31.599> in<00:08:31.759> web<00:08:32.000> 3 00:08:32.670 --> 00:08:32.680 align:start position:0% what do people actually value in web 3 00:08:32.680 --> 00:08:35.469 align:start position:0% what do people actually value in web 3 they<00:08:32.880> value<00:08:33.519> assets<00:08:34.519> and<00:08:34.880> there's<00:08:35.200> always 00:08:35.469 --> 00:08:35.479 align:start position:0% they value assets and there's always 00:08:35.479 --> 00:08:39.509 align:start position:0% they value assets and there's always going<00:08:35.640> to<00:08:35.800> be<00:08:36.200> assets<00:08:37.039> outside<00:08:38.039> of<00:08:38.519> ethereum 00:08:39.509 --> 00:08:39.519 align:start position:0% going to be assets outside of ethereum 00:08:39.519 --> 00:08:42.350 align:start position:0% going to be assets outside of ethereum and<00:08:40.000> we<00:08:40.159> need<00:08:40.320> to<00:08:40.479> be<00:08:40.680> able<00:08:40.959> to<00:08:41.399> get<00:08:41.599> people<00:08:41.880> to 00:08:42.350 --> 00:08:42.360 align:start position:0% and we need to be able to get people to 00:08:42.360 --> 00:08:46.190 align:start position:0% and we need to be able to get people to come<00:08:42.560> to<00:08:42.760> ethereum<00:08:43.719> and<00:08:44.039> stay<00:08:44.760> on<00:08:45.200> ethereum 00:08:46.190 --> 00:08:46.200 align:start position:0% come to ethereum and stay on ethereum 00:08:46.200 --> 00:08:48.269 align:start position:0% come to ethereum and stay on ethereum and<00:08:46.440> the<00:08:46.600> only<00:08:46.839> way<00:08:46.959> to<00:08:47.120> do<00:08:47.360> that<00:08:47.640> is<00:08:47.800> to<00:08:48.000> allow 00:08:48.269 --> 00:08:48.279 align:start position:0% and the only way to do that is to allow 00:08:48.279 --> 00:08:52.550 align:start position:0% and the only way to do that is to allow them<00:08:48.519> to<00:08:48.839> use<00:08:49.480> or<00:08:49.640> to<00:08:49.920> receive<00:08:50.760> or<00:08:51.000> send<00:08:51.560> assets 00:08:52.550 --> 00:08:52.560 align:start position:0% them to use or to receive or send assets 00:08:52.560 --> 00:08:56.389 align:start position:0% them to use or to receive or send assets to<00:08:53.000> another<00:08:53.279> chain<00:08:53.959> that<00:08:54.120> is<00:08:54.399> not<00:08:55.399> ethereum 00:08:56.389 --> 00:08:56.399 align:start position:0% to another chain that is not ethereum 00:08:56.399 --> 00:08:58.750 align:start position:0% to another chain that is not ethereum and<00:08:56.880> the<00:08:57.000> only<00:08:57.200> way<00:08:57.360> to<00:08:57.519> do<00:08:57.720> that<00:08:58.000> is<00:08:58.200> to 00:08:58.750 --> 00:08:58.760 align:start position:0% and the only way to do that is to 00:08:58.760 --> 00:09:01.230 align:start position:0% and the only way to do that is to aggregate<00:08:59.240> those<00:08:59.640> chains<00:09:00.360> along<00:09:00.760> with 00:09:01.230 --> 00:09:01.240 align:start position:0% aggregate those chains along with 00:09:01.240 --> 00:09:04.310 align:start position:0% aggregate those chains along with ethereum<00:09:01.720> and<00:09:01.880> all<00:09:02.200> chains<00:09:02.640> on<00:09:02.839> them<00:09:03.680> and<00:09:03.839> so 00:09:04.310 --> 00:09:04.320 align:start position:0% ethereum and all chains on them and so 00:09:04.320 --> 00:09:06.509 align:start position:0% ethereum and all chains on them and so that<00:09:04.440> is<00:09:04.600> a<00:09:04.800> big<00:09:05.079> part<00:09:05.519> of<00:09:05.760> kind<00:09:05.880> of<00:09:05.959> the<00:09:06.079> Ager 00:09:06.509 --> 00:09:06.519 align:start position:0% that is a big part of kind of the Ager 00:09:06.519 --> 00:09:08.630 align:start position:0% that is a big part of kind of the Ager is<00:09:06.680> really<00:09:06.880> bringing<00:09:07.480> everything<00:09:08.000> together 00:09:08.630 --> 00:09:08.640 align:start position:0% is really bringing everything together 00:09:08.640 --> 00:09:10.870 align:start position:0% is really bringing everything together and<00:09:08.760> ultimately<00:09:09.279> having<00:09:09.560> finality<00:09:10.040> on 00:09:10.870 --> 00:09:10.880 align:start position:0% and ultimately having finality on 00:09:10.880 --> 00:09:13.030 align:start position:0% and ultimately having finality on ethereum<00:09:11.880> maybe<00:09:12.120> let<00:09:12.240> me<00:09:12.480> talk<00:09:12.640> to<00:09:12.720> you<00:09:12.880> about 00:09:13.030 --> 00:09:13.040 align:start position:0% ethereum maybe let me talk to you about 00:09:13.040 --> 00:09:15.150 align:start position:0% ethereum maybe let me talk to you about kind<00:09:13.160> of<00:09:13.279> like<00:09:13.399> the<00:09:13.560> different<00:09:13.959> components<00:09:14.920> of 00:09:15.150 --> 00:09:15.160 align:start position:0% kind of like the different components of 00:09:15.160 --> 00:09:17.670 align:start position:0% kind of like the different components of the<00:09:15.480> agay<00:09:16.480> really<00:09:16.760> think<00:09:16.920> about<00:09:17.120> it<00:09:17.240> in<00:09:17.440> like 00:09:17.670 --> 00:09:17.680 align:start position:0% the agay really think about it in like 00:09:17.680 --> 00:09:21.670 align:start position:0% the agay really think about it in like four<00:09:18.160> different<00:09:18.680> parts<00:09:20.000> um<00:09:21.000> a<00:09:21.120> lot<00:09:21.240> of<00:09:21.399> times 00:09:21.670 --> 00:09:21.680 align:start position:0% four different parts um a lot of times 00:09:21.680 --> 00:09:23.829 align:start position:0% four different parts um a lot of times when<00:09:21.839> people<00:09:22.120> hear<00:09:22.360> the<00:09:22.480> agay<00:09:23.200> or<00:09:23.519> anything 00:09:23.829 --> 00:09:23.839 align:start position:0% when people hear the agay or anything 00:09:23.839 --> 00:09:25.069 align:start position:0% when people hear the agay or anything that<00:09:24.040> has<00:09:24.160> to<00:09:24.279> do<00:09:24.399> with 00:09:25.069 --> 00:09:25.079 align:start position:0% that has to do with 00:09:25.079 --> 00:09:27.069 align:start position:0% that has to do with interoperability<00:09:26.079> they<00:09:26.480> immediately 00:09:27.069 --> 00:09:27.079 align:start position:0% interoperability they immediately 00:09:27.079 --> 00:09:30.030 align:start position:0% interoperability they immediately default<00:09:27.519> to<00:09:28.079> it's<00:09:28.240> a<00:09:28.399> bridge<00:09:29.440> it's<00:09:29.680> nothing 00:09:30.030 --> 00:09:30.040 align:start position:0% default to it's a bridge it's nothing 00:09:30.040 --> 00:09:32.470 align:start position:0% default to it's a bridge it's nothing but<00:09:30.360> a<00:09:30.519> bridge<00:09:31.320> and<00:09:31.480> this<00:09:31.600> is<00:09:31.760> simply<00:09:32.120> because 00:09:32.470 --> 00:09:32.480 align:start position:0% but a bridge and this is simply because 00:09:32.480 --> 00:09:33.670 align:start position:0% but a bridge and this is simply because when<00:09:32.600> we<00:09:32.720> think<00:09:32.880> of<00:09:33.000> the<00:09:33.160> forms<00:09:33.480> of 00:09:33.670 --> 00:09:33.680 align:start position:0% when we think of the forms of 00:09:33.680 --> 00:09:36.030 align:start position:0% when we think of the forms of interoperability<00:09:34.519> that<00:09:34.680> we<00:09:34.800> have<00:09:35.120> had<00:09:35.560> to<00:09:35.760> go 00:09:36.030 --> 00:09:36.040 align:start position:0% interoperability that we have had to go 00:09:36.040 --> 00:09:38.670 align:start position:0% interoperability that we have had to go cross<00:09:36.399> chain<00:09:37.120> over<00:09:37.519> the<00:09:37.640> last<00:09:37.839> many<00:09:38.120> years<00:09:38.480> we 00:09:38.670 --> 00:09:38.680 align:start position:0% cross chain over the last many years we 00:09:38.680 --> 00:09:41.389 align:start position:0% cross chain over the last many years we default<00:09:39.120> to<00:09:39.320> Bridges<00:09:40.320> layer<00:09:40.680> zeros<00:09:41.240> the 00:09:41.389 --> 00:09:41.399 align:start position:0% default to Bridges layer zeros the 00:09:41.399 --> 00:09:44.069 align:start position:0% default to Bridges layer zeros the wormholes<00:09:42.240> things<00:09:42.519> like<00:09:42.720> that<00:09:43.600> um<00:09:43.880> and<00:09:43.959> then 00:09:44.069 --> 00:09:44.079 align:start position:0% wormholes things like that um and then 00:09:44.079 --> 00:09:45.870 align:start position:0% wormholes things like that um and then more<00:09:44.279> recently<00:09:44.720> people<00:09:44.920> start<00:09:45.200> thinking<00:09:45.600> of 00:09:45.870 --> 00:09:45.880 align:start position:0% more recently people start thinking of 00:09:45.880 --> 00:09:48.310 align:start position:0% more recently people start thinking of cross<00:09:46.200> chain<00:09:46.800> transactions<00:09:47.640> as<00:09:47.800> being<00:09:48.079> things 00:09:48.310 --> 00:09:48.320 align:start position:0% cross chain transactions as being things 00:09:48.320 --> 00:09:51.990 align:start position:0% cross chain transactions as being things driven<00:09:48.839> by<00:09:49.640> intents<00:09:50.640> um<00:09:51.200> but<00:09:51.399> people<00:09:51.680> don't 00:09:51.990 --> 00:09:52.000 align:start position:0% driven by intents um but people don't 00:09:52.000 --> 00:09:53.590 align:start position:0% driven by intents um but people don't really<00:09:52.240> think<00:09:52.560> holistically<00:09:53.160> about 00:09:53.590 --> 00:09:53.600 align:start position:0% really think holistically about 00:09:53.600 --> 00:09:55.990 align:start position:0% really think holistically about everything<00:09:53.959> that<00:09:54.079> you<00:09:54.279> need<00:09:54.720> to<00:09:55.040> get<00:09:55.680> like 00:09:55.990 --> 00:09:56.000 align:start position:0% everything that you need to get like 00:09:56.000 --> 00:09:58.389 align:start position:0% everything that you need to get like safety<00:09:56.920> when<00:09:57.200> fragmenting<00:09:57.959> when<00:09:58.079> there's<00:09:58.240> a 00:09:58.389 --> 00:09:58.399 align:start position:0% safety when fragmenting when there's a 00:09:58.399 --> 00:10:00.269 align:start position:0% safety when fragmenting when there's a fragmented<00:09:58.880> web<00:09:59.040> 3<00:09:59.440> that<00:09:59.519> you<00:09:59.640> want<00:09:59.720> to<00:09:59.880> bring 00:10:00.269 --> 00:10:00.279 align:start position:0% fragmented web 3 that you want to bring 00:10:00.279 --> 00:10:02.350 align:start position:0% fragmented web 3 that you want to bring together<00:10:01.279> so<00:10:01.399> let<00:10:01.519> me<00:10:01.680> talk<00:10:01.880> through<00:10:02.079> kind<00:10:02.200> of 00:10:02.350 --> 00:10:02.360 align:start position:0% together so let me talk through kind of 00:10:02.360 --> 00:10:04.750 align:start position:0% together so let me talk through kind of these<00:10:02.720> four<00:10:02.959> different<00:10:03.240> components<00:10:04.160> of<00:10:04.320> the<00:10:04.480> a 00:10:04.750 --> 00:10:04.760 align:start position:0% these four different components of the a 00:10:04.760 --> 00:10:07.829 align:start position:0% these four different components of the a layer<00:10:05.680> uh<00:10:05.959> first<00:10:06.240> one<00:10:06.720> is<00:10:07.079> the<00:10:07.279> pessimistic 00:10:07.829 --> 00:10:07.839 align:start position:0% layer uh first one is the pessimistic 00:10:07.839 --> 00:10:09.310 align:start position:0% layer uh first one is the pessimistic proof 00:10:09.310 --> 00:10:09.320 align:start position:0% proof 00:10:09.320 --> 00:10:11.910 align:start position:0% proof so<00:10:10.320> the<00:10:10.480> most<00:10:10.760> important<00:10:11.200> thing<00:10:11.560> if<00:10:11.680> you<00:10:11.800> want 00:10:11.910 --> 00:10:11.920 align:start position:0% so the most important thing if you want 00:10:11.920 --> 00:10:15.110 align:start position:0% so the most important thing if you want to<00:10:12.120> bring<00:10:12.399> chains<00:10:12.959> together<00:10:13.839> is<00:10:14.000> to<00:10:14.279> ensure 00:10:15.110 --> 00:10:15.120 align:start position:0% to bring chains together is to ensure 00:10:15.120 --> 00:10:18.710 align:start position:0% to bring chains together is to ensure that<00:10:15.440> no<00:10:15.680> one<00:10:16.040> chain<00:10:16.959> can<00:10:17.200> rug<00:10:17.560> another<00:10:17.839> chain 00:10:18.710 --> 00:10:18.720 align:start position:0% that no one chain can rug another chain 00:10:18.720 --> 00:10:21.269 align:start position:0% that no one chain can rug another chain right<00:10:18.959> like<00:10:19.200> if<00:10:19.440> I<00:10:19.680> have<00:10:20.320> gone<00:10:20.519> to<00:10:20.680> a<00:10:20.800> chain<00:10:21.200> I 00:10:21.269 --> 00:10:21.279 align:start position:0% right like if I have gone to a chain I 00:10:21.279 --> 00:10:22.870 align:start position:0% right like if I have gone to a chain I have<00:10:21.480> decided<00:10:21.959> this<00:10:22.040> is<00:10:22.160> a<00:10:22.279> chain<00:10:22.560> that<00:10:22.680> I 00:10:22.870 --> 00:10:22.880 align:start position:0% have decided this is a chain that I 00:10:22.880 --> 00:10:26.269 align:start position:0% have decided this is a chain that I trust<00:10:23.800> um<00:10:24.160> or<00:10:24.680> like<00:10:24.920> many<00:10:25.680> frankly<00:10:26.040> haven't 00:10:26.269 --> 00:10:26.279 align:start position:0% trust um or like many frankly haven't 00:10:26.279 --> 00:10:28.630 align:start position:0% trust um or like many frankly haven't paid<00:10:26.480> attention<00:10:27.000> but<00:10:27.320> I'm<00:10:27.720> still<00:10:28.160> assuming 00:10:28.630 --> 00:10:28.640 align:start position:0% paid attention but I'm still assuming 00:10:28.640 --> 00:10:33.110 align:start position:0% paid attention but I'm still assuming Trust<00:10:29.360> on<00:10:29.600> that<00:10:29.800> chain<00:10:30.800> and<00:10:31.600> when<00:10:31.839> I<00:10:32.040> send<00:10:32.760> a 00:10:33.110 --> 00:10:33.120 align:start position:0% Trust on that chain and when I send a 00:10:33.120 --> 00:10:34.710 align:start position:0% Trust on that chain and when I send a transaction<00:10:33.640> cross<00:10:33.880> chain<00:10:34.040> or<00:10:34.160> I'm<00:10:34.480> receiving 00:10:34.710 --> 00:10:34.720 align:start position:0% transaction cross chain or I'm receiving 00:10:34.720 --> 00:10:38.550 align:start position:0% transaction cross chain or I'm receiving an<00:10:34.959> asset<00:10:35.800> from<00:10:36.200> another<00:10:36.760> chain<00:10:37.760> I<00:10:37.959> need<00:10:38.120> to<00:10:38.279> be 00:10:38.550 --> 00:10:38.560 align:start position:0% an asset from another chain I need to be 00:10:38.560 --> 00:10:40.590 align:start position:0% an asset from another chain I need to be 100%<00:10:39.120> sure<00:10:39.519> that<00:10:39.639> the<00:10:39.839> only<00:10:40.160> thing<00:10:40.360> I<00:10:40.440> am 00:10:40.590 --> 00:10:40.600 align:start position:0% 100% sure that the only thing I am 00:10:40.600 --> 00:10:43.310 align:start position:0% 100% sure that the only thing I am trusting<00:10:41.160> is<00:10:41.320> that<00:10:41.519> chain<00:10:41.800> that<00:10:41.959> I<00:10:42.079> am<00:10:42.279> on<00:10:43.160> and 00:10:43.310 --> 00:10:43.320 align:start position:0% trusting is that chain that I am on and 00:10:43.320 --> 00:10:44.790 align:start position:0% trusting is that chain that I am on and this<00:10:43.399> is<00:10:43.600> basically<00:10:44.000> what<00:10:44.120> the<00:10:44.279> pessimistic 00:10:44.790 --> 00:10:44.800 align:start position:0% this is basically what the pessimistic 00:10:44.800 --> 00:10:47.430 align:start position:0% this is basically what the pessimistic proof<00:10:45.160> does<00:10:46.160> what<00:10:46.240> it<00:10:46.399> does<00:10:46.600> is<00:10:46.720> it<00:10:46.880> looks<00:10:47.079> at 00:10:47.430 --> 00:10:47.440 align:start position:0% proof does what it does is it looks at 00:10:47.440 --> 00:10:49.910 align:start position:0% proof does what it does is it looks at all<00:10:47.880> assets<00:10:48.240> that<00:10:48.399> come<00:10:48.600> into<00:10:48.839> a<00:10:48.959> chain<00:10:49.760> it 00:10:49.910 --> 00:10:49.920 align:start position:0% all assets that come into a chain it 00:10:49.920 --> 00:10:52.069 align:start position:0% all assets that come into a chain it looks<00:10:50.160> at<00:10:50.440> all<00:10:50.800> assets<00:10:51.240> that<00:10:51.320> are<00:10:51.519> leaving<00:10:51.839> a 00:10:52.069 --> 00:10:52.079 align:start position:0% looks at all assets that are leaving a 00:10:52.079 --> 00:10:55.030 align:start position:0% looks at all assets that are leaving a chain<00:10:53.079> and<00:10:53.760> we<00:10:53.920> call<00:10:54.160> this<00:10:54.360> chain<00:10:54.720> level 00:10:55.030 --> 00:10:55.040 align:start position:0% chain and we call this chain level 00:10:55.040 --> 00:10:56.509 align:start position:0% chain and we call this chain level accounting<00:10:55.839> and<00:10:56.000> basically<00:10:56.320> what<00:10:56.399> the 00:10:56.509 --> 00:10:56.519 align:start position:0% accounting and basically what the 00:10:56.519 --> 00:10:58.150 align:start position:0% accounting and basically what the pessimistic<00:10:57.000> proof<00:10:57.279> does<00:10:57.480> it<00:10:57.639> then<00:10:57.800> ensures 00:10:58.150 --> 00:10:58.160 align:start position:0% pessimistic proof does it then ensures 00:10:58.160 --> 00:10:59.670 align:start position:0% pessimistic proof does it then ensures that<00:10:58.279> when<00:10:58.399> an<00:10:58.560> asset<00:10:58.800> wants<00:10:59.000> to<00:10:59.320> leave<00:10:59.519> a 00:10:59.670 --> 00:10:59.680 align:start position:0% that when an asset wants to leave a 00:10:59.680 --> 00:11:02.990 align:start position:0% that when an asset wants to leave a chain<00:11:00.680> it<00:11:00.800> is<00:11:01.079> not<00:11:01.480> an<00:11:01.720> asset<00:11:02.000> that<00:11:02.200> is<00:11:02.600> in 00:11:02.990 --> 00:11:03.000 align:start position:0% chain it is not an asset that is in 00:11:03.000 --> 00:11:05.110 align:start position:0% chain it is not an asset that is in excess<00:11:03.639> of<00:11:03.839> any<00:11:04.079> assets<00:11:04.399> that<00:11:04.480> have<00:11:04.639> come<00:11:04.839> into 00:11:05.110 --> 00:11:05.120 align:start position:0% excess of any assets that have come into 00:11:05.120 --> 00:11:07.990 align:start position:0% excess of any assets that have come into it<00:11:05.360> so<00:11:05.560> if<00:11:05.680> you've<00:11:06.000> had<00:11:06.480> you<00:11:06.600> know<00:11:06.839> 10<00:11:07.440> eth<00:11:07.800> come 00:11:07.990 --> 00:11:08.000 align:start position:0% it so if you've had you know 10 eth come 00:11:08.000 --> 00:11:10.470 align:start position:0% it so if you've had you know 10 eth come into<00:11:08.200> a<00:11:08.360> chain<00:11:09.240> then<00:11:09.440> you<00:11:09.639> can't<00:11:09.959> have<00:11:10.240> more 00:11:10.470 --> 00:11:10.480 align:start position:0% into a chain then you can't have more 00:11:10.480 --> 00:11:12.829 align:start position:0% into a chain then you can't have more than<00:11:10.680> 10<00:11:11.040> eth<00:11:11.480> leave<00:11:11.760> that<00:11:11.920> chain<00:11:12.480> and<00:11:12.600> this<00:11:12.720> is 00:11:12.829 --> 00:11:12.839 align:start position:0% than 10 eth leave that chain and this is 00:11:12.839 --> 00:11:15.269 align:start position:0% than 10 eth leave that chain and this is what<00:11:12.959> the<00:11:13.079> pessimistic<00:11:13.560> proof<00:11:13.839> enforces<00:11:14.839> now 00:11:15.269 --> 00:11:15.279 align:start position:0% what the pessimistic proof enforces now 00:11:15.279 --> 00:11:16.150 align:start position:0% what the pessimistic proof enforces now the<00:11:15.360> interesting<00:11:15.720> thing<00:11:15.839> about<00:11:16.040> this 00:11:16.150 --> 00:11:16.160 align:start position:0% the interesting thing about this 00:11:16.160 --> 00:11:19.350 align:start position:0% the interesting thing about this pessimistic<00:11:16.639> proof<00:11:16.920> is<00:11:17.120> that<00:11:17.680> it<00:11:17.800> is<00:11:18.120> not<00:11:18.519> just 00:11:19.350 --> 00:11:19.360 align:start position:0% pessimistic proof is that it is not just 00:11:19.360 --> 00:11:21.509 align:start position:0% pessimistic proof is that it is not just enforcing<00:11:20.360> uh<00:11:20.639> it<00:11:20.720> is<00:11:20.839> not<00:11:20.959> just<00:11:21.120> enforcing 00:11:21.509 --> 00:11:21.519 align:start position:0% enforcing uh it is not just enforcing 00:11:21.519 --> 00:11:24.150 align:start position:0% enforcing uh it is not just enforcing this<00:11:21.680> for<00:11:21.839> chains<00:11:22.320> that<00:11:22.600> have<00:11:23.120> proofs<00:11:24.000> right 00:11:24.150 --> 00:11:24.160 align:start position:0% this for chains that have proofs right 00:11:24.160 --> 00:11:26.150 align:start position:0% this for chains that have proofs right so<00:11:24.399> so<00:11:24.560> a<00:11:24.639> lot<00:11:24.760> of<00:11:24.880> times<00:11:25.200> people<00:11:25.440> think<00:11:25.839> okay 00:11:26.150 --> 00:11:26.160 align:start position:0% so so a lot of times people think okay 00:11:26.160 --> 00:11:28.670 align:start position:0% so so a lot of times people think okay the<00:11:26.320> the<00:11:26.720> layer<00:11:27.079> or<00:11:27.880> that<00:11:28.000> polygon<00:11:28.360> is<00:11:28.440> working 00:11:28.670 --> 00:11:28.680 align:start position:0% the the layer or that polygon is working 00:11:28.680 --> 00:11:32.150 align:start position:0% the the layer or that polygon is working on<00:11:28.839> like<00:11:29.680> ZK<00:11:30.160> technology<00:11:31.160> so<00:11:31.440> like<00:11:31.639> you<00:11:32.000> you 00:11:32.150 --> 00:11:32.160 align:start position:0% on like ZK technology so like you you 00:11:32.160 --> 00:11:33.990 align:start position:0% on like ZK technology so like you you you<00:11:32.279> look<00:11:32.399> at<00:11:32.560> polygon<00:11:32.920> zkm<00:11:33.360> or<00:11:33.560> exay<00:11:33.920> and 00:11:33.990 --> 00:11:34.000 align:start position:0% you look at polygon zkm or exay and 00:11:34.000 --> 00:11:35.389 align:start position:0% you look at polygon zkm or exay and you're<00:11:34.120> like<00:11:34.279> hey<00:11:34.399> this<00:11:34.519> uses<00:11:34.880> execution 00:11:35.389 --> 00:11:35.399 align:start position:0% you're like hey this uses execution 00:11:35.399 --> 00:11:37.910 align:start position:0% you're like hey this uses execution proofs<00:11:35.959> and<00:11:36.079> so<00:11:36.240> the<00:11:36.399> AG<00:11:36.839> requires<00:11:37.399> execution 00:11:37.910 --> 00:11:37.920 align:start position:0% proofs and so the AG requires execution 00:11:37.920 --> 00:11:40.269 align:start position:0% proofs and so the AG requires execution proofs<00:11:38.760> the<00:11:38.959> reality<00:11:39.320> is<00:11:39.440> the<00:11:39.560> AG<00:11:39.920> is<00:11:40.040> actually 00:11:40.269 --> 00:11:40.279 align:start position:0% proofs the reality is the AG is actually 00:11:40.279 --> 00:11:43.110 align:start position:0% proofs the reality is the AG is actually completely<00:11:40.959> agnostic<00:11:41.800> to<00:11:42.040> that<00:11:42.720> um<00:11:42.880> you<00:11:43.000> could 00:11:43.110 --> 00:11:43.120 align:start position:0% completely agnostic to that um you could 00:11:43.120 --> 00:11:44.509 align:start position:0% completely agnostic to that um you could have<00:11:43.320> execution<00:11:43.720> proofs<00:11:44.040> you<00:11:44.120> could<00:11:44.320> have 00:11:44.509 --> 00:11:44.519 align:start position:0% have execution proofs you could have 00:11:44.519 --> 00:11:47.069 align:start position:0% have execution proofs you could have fraud<00:11:44.920> proofs<00:11:45.680> you<00:11:45.800> can<00:11:46.000> have<00:11:46.240> some<00:11:46.519> form<00:11:46.800> of 00:11:47.069 --> 00:11:47.079 align:start position:0% fraud proofs you can have some form of 00:11:47.079 --> 00:11:49.350 align:start position:0% fraud proofs you can have some form of consensus<00:11:47.800> that<00:11:47.920> can<00:11:48.040> be<00:11:48.200> proven<00:11:48.920> or<00:11:49.079> you<00:11:49.160> can 00:11:49.350 --> 00:11:49.360 align:start position:0% consensus that can be proven or you can 00:11:49.360 --> 00:11:51.350 align:start position:0% consensus that can be proven or you can straight<00:11:49.639> up<00:11:49.920> have<00:11:50.440> a 00:11:51.350 --> 00:11:51.360 align:start position:0% straight up have a 00:11:51.360 --> 00:11:53.670 align:start position:0% straight up have a database<00:11:52.360> pessimistic<00:11:52.839> proof<00:11:53.040> doesn't<00:11:53.360> care 00:11:53.670 --> 00:11:53.680 align:start position:0% database pessimistic proof doesn't care 00:11:53.680 --> 00:11:55.190 align:start position:0% database pessimistic proof doesn't care it's<00:11:53.839> going<00:11:54.000> to<00:11:54.160> look<00:11:54.279> at<00:11:54.440> what<00:11:54.600> assets<00:11:54.959> came 00:11:55.190 --> 00:11:55.200 align:start position:0% it's going to look at what assets came 00:11:55.200 --> 00:11:58.350 align:start position:0% it's going to look at what assets came in<00:11:55.800> what<00:11:55.959> assets<00:11:56.279> have<00:11:56.519> left<00:11:57.360> and<00:11:57.839> whether<00:11:58.160> an 00:11:58.350 --> 00:11:58.360 align:start position:0% in what assets have left and whether an 00:11:58.360 --> 00:12:00.629 align:start position:0% in what assets have left and whether an asset<00:11:58.600> that<00:11:58.720> wants<00:11:58.959> to<00:11:59.360> leave<00:11:59.880> or<00:12:00.360> be<00:12:00.519> be 00:12:00.629 --> 00:12:00.639 align:start position:0% asset that wants to leave or be be 00:12:00.639 --> 00:12:03.509 align:start position:0% asset that wants to leave or be be removed<00:12:00.959> from<00:12:01.120> there<00:12:01.440> can<00:12:02.360> and<00:12:02.600> so<00:12:03.279> that's 00:12:03.509 --> 00:12:03.519 align:start position:0% removed from there can and so that's 00:12:03.519 --> 00:12:04.949 align:start position:0% removed from there can and so that's kind<00:12:03.639> of<00:12:03.760> like<00:12:03.880> the<00:12:04.000> guarantee<00:12:04.399> you<00:12:04.519> get<00:12:04.639> the 00:12:04.949 --> 00:12:04.959 align:start position:0% kind of like the guarantee you get the 00:12:04.959 --> 00:12:07.550 align:start position:0% kind of like the guarantee you get the pessimistic<00:12:05.519> proof<00:12:06.079> is<00:12:06.240> that<00:12:06.480> regardless<00:12:07.120> of 00:12:07.550 --> 00:12:07.560 align:start position:0% pessimistic proof is that regardless of 00:12:07.560 --> 00:12:10.269 align:start position:0% pessimistic proof is that regardless of what<00:12:08.000> it<00:12:08.200> is<00:12:09.040> that<00:12:09.200> a<00:12:09.360> chain<00:12:09.720> like<00:12:09.839> the<00:12:09.959> form<00:12:10.200> of 00:12:10.269 --> 00:12:10.279 align:start position:0% what it is that a chain like the form of 00:12:10.279 --> 00:12:13.990 align:start position:0% what it is that a chain like the form of a<00:12:10.440> chain<00:12:11.279> you<00:12:11.399> can<00:12:11.959> prove<00:12:12.959> um<00:12:13.399> facts<00:12:13.760> about 00:12:13.990 --> 00:12:14.000 align:start position:0% a chain you can prove um facts about 00:12:14.000 --> 00:12:16.470 align:start position:0% a chain you can prove um facts about that<00:12:14.160> chain<00:12:14.680> and<00:12:14.920> specifically<00:12:15.920> on<00:12:16.279> on 00:12:16.470 --> 00:12:16.480 align:start position:0% that chain and specifically on on 00:12:16.480 --> 00:12:19.350 align:start position:0% that chain and specifically on on something<00:12:16.920> like<00:12:17.279> a<00:12:18.040> a<00:12:18.199> polygon<00:12:18.639> POS<00:12:19.120> that<00:12:19.279> has 00:12:19.350 --> 00:12:19.360 align:start position:0% something like a a polygon POS that has 00:12:19.360 --> 00:12:21.230 align:start position:0% something like a a polygon POS that has a<00:12:19.480> validator<00:12:20.000> set<00:12:20.480> you<00:12:20.600> can<00:12:20.800> prove<00:12:21.079> the 00:12:21.230 --> 00:12:21.240 align:start position:0% a validator set you can prove the 00:12:21.240 --> 00:12:24.470 align:start position:0% a validator set you can prove the consensus<00:12:22.000> of<00:12:22.199> polygon<00:12:22.720> POS<00:12:23.199> so<00:12:23.399> that<00:12:23.560> you<00:12:23.720> can 00:12:24.470 --> 00:12:24.480 align:start position:0% consensus of polygon POS so that you can 00:12:24.480 --> 00:12:26.470 align:start position:0% consensus of polygon POS so that you can confidently<00:12:25.279> actually<00:12:25.600> have<00:12:25.800> transactions 00:12:26.470 --> 00:12:26.480 align:start position:0% confidently actually have transactions 00:12:26.480 --> 00:12:28.829 align:start position:0% confidently actually have transactions go<00:12:26.760> go<00:12:26.920> cross<00:12:27.199> chain<00:12:28.079> uh<00:12:28.279> next<00:12:28.399> one<00:12:28.519> is<00:12:28.639> proof 00:12:28.829 --> 00:12:28.839 align:start position:0% go go cross chain uh next one is proof 00:12:28.839 --> 00:12:30.030 align:start position:0% go go cross chain uh next one is proof aggregation 00:12:30.030 --> 00:12:30.040 align:start position:0% aggregation 00:12:30.040 --> 00:12:31.509 align:start position:0% aggregation a<00:12:30.079> lot<00:12:30.199> of<00:12:30.320> people<00:12:30.519> think<00:12:30.720> the<00:12:30.839> proof<00:12:31.040> agation 00:12:31.509 --> 00:12:31.519 align:start position:0% a lot of people think the proof agation 00:12:31.519 --> 00:12:34.189 align:start position:0% a lot of people think the proof agation is<00:12:31.639> whatow<00:12:32.079> the<00:12:32.279> interoperability<00:12:33.279> in<00:12:33.399> the 00:12:34.189 --> 00:12:34.199 align:start position:0% is whatow the interoperability in the 00:12:34.199 --> 00:12:37.910 align:start position:0% is whatow the interoperability in the all<00:12:34.440> proof<00:12:34.680> agregation<00:12:35.600> is<00:12:35.720> it<00:12:35.880> lowers<00:12:36.560> C<00:12:37.519> of 00:12:37.910 --> 00:12:37.920 align:start position:0% all proof agregation is it lowers C of 00:12:37.920 --> 00:12:39.870 align:start position:0% all proof agregation is it lowers C of transacting<00:12:38.720> on<00:12:38.959> chains<00:12:39.320> connected<00:12:39.680> to<00:12:39.760> the 00:12:39.870 --> 00:12:39.880 align:start position:0% transacting on chains connected to the 00:12:39.880 --> 00:12:42.389 align:start position:0% transacting on chains connected to the AG<00:12:40.399> and<00:12:40.519> using<00:12:40.760> the<00:12:40.880> AG<00:12:41.639> specifically<00:12:42.160> what<00:12:42.240> it 00:12:42.389 --> 00:12:42.399 align:start position:0% AG and using the AG specifically what it 00:12:42.399 --> 00:12:44.389 align:start position:0% AG and using the AG specifically what it does<00:12:42.639> is<00:12:42.800> you<00:12:43.000> get<00:12:43.199> a<00:12:43.360> ZK<00:12:43.880> proof<00:12:44.160> and<00:12:44.279> this 00:12:44.389 --> 00:12:44.399 align:start position:0% does is you get a ZK proof and this 00:12:44.399 --> 00:12:45.629 align:start position:0% does is you get a ZK proof and this could<00:12:44.519> be<00:12:44.639> the<00:12:44.760> pessimistic<00:12:45.279> proof<00:12:45.480> or<00:12:45.600> it 00:12:45.629 --> 00:12:45.639 align:start position:0% could be the pessimistic proof or it 00:12:45.639 --> 00:12:47.550 align:start position:0% could be the pessimistic proof or it could<00:12:45.760> be<00:12:45.839> an<00:12:46.000> execution<00:12:46.480> proof<00:12:46.720> on<00:12:46.800> a<00:12:46.920> chain 00:12:47.550 --> 00:12:47.560 align:start position:0% could be an execution proof on a chain 00:12:47.560 --> 00:12:48.990 align:start position:0% could be an execution proof on a chain and<00:12:47.720> what<00:12:47.839> it<00:12:47.959> does<00:12:48.160> is<00:12:48.279> it<00:12:48.440> wraps<00:12:48.839> those 00:12:48.990 --> 00:12:49.000 align:start position:0% and what it does is it wraps those 00:12:49.000 --> 00:12:50.710 align:start position:0% and what it does is it wraps those proofs<00:12:49.440> together<00:12:50.079> and<00:12:50.160> then<00:12:50.320> wraps<00:12:50.600> those 00:12:50.710 --> 00:12:50.720 align:start position:0% proofs together and then wraps those 00:12:50.720 --> 00:12:51.870 align:start position:0% proofs together and then wraps those proofs<00:12:51.040> together<00:12:51.279> and<00:12:51.360> then<00:12:51.480> wraps<00:12:51.760> those 00:12:51.870 --> 00:12:51.880 align:start position:0% proofs together and then wraps those 00:12:51.880 --> 00:12:53.310 align:start position:0% proofs together and then wraps those proofs<00:12:52.199> together<00:12:52.519> and<00:12:52.600> then<00:12:52.720> submits<00:12:53.040> them<00:12:53.199> to 00:12:53.310 --> 00:12:53.320 align:start position:0% proofs together and then submits them to 00:12:53.320 --> 00:12:55.150 align:start position:0% proofs together and then submits them to ethereum<00:12:53.959> if<00:12:54.079> you<00:12:54.160> were<00:12:54.279> to<00:12:54.399> submit<00:12:54.800> each<00:12:54.959> of 00:12:55.150 --> 00:12:55.160 align:start position:0% ethereum if you were to submit each of 00:12:55.160 --> 00:12:57.430 align:start position:0% ethereum if you were to submit each of those<00:12:55.360> proofs<00:12:55.639> to<00:12:55.800> ethereum<00:12:56.639> on<00:12:56.800> their<00:12:56.959> own<00:12:57.320> it 00:12:57.430 --> 00:12:57.440 align:start position:0% those proofs to ethereum on their own it 00:12:57.440 --> 00:12:59.310 align:start position:0% those proofs to ethereum on their own it would<00:12:57.560> be<00:12:57.720> incredibly<00:12:58.240> expensive<00:12:58.880> and<00:12:59.199> so 00:12:59.310 --> 00:12:59.320 align:start position:0% would be incredibly expensive and so 00:12:59.320 --> 00:13:00.829 align:start position:0% would be incredibly expensive and so this<00:12:59.399> is<00:12:59.519> how<00:12:59.639> you're<00:12:59.839> able<00:13:00.040> to<00:13:00.240> lower<00:13:00.600> the 00:13:00.829 --> 00:13:00.839 align:start position:0% this is how you're able to lower the 00:13:00.839 --> 00:13:03.310 align:start position:0% this is how you're able to lower the cost<00:13:01.240> so<00:13:01.399> that<00:13:01.560> it<00:13:01.639> is<00:13:01.839> incredibly<00:13:02.480> cheap<00:13:03.079> to 00:13:03.310 --> 00:13:03.320 align:start position:0% cost so that it is incredibly cheap to 00:13:03.320 --> 00:13:05.870 align:start position:0% cost so that it is incredibly cheap to execute<00:13:03.720> these<00:13:03.920> cross-chain<00:13:04.880> transactions 00:13:05.870 --> 00:13:05.880 align:start position:0% execute these cross-chain transactions 00:13:05.880 --> 00:13:07.550 align:start position:0% execute these cross-chain transactions next<00:13:06.040> thing<00:13:06.199> is<00:13:06.279> there's<00:13:06.440> a<00:13:06.560> unified<00:13:06.959> bridge 00:13:07.550 --> 00:13:07.560 align:start position:0% next thing is there's a unified bridge 00:13:07.560 --> 00:13:11.310 align:start position:0% next thing is there's a unified bridge this<00:13:07.680> is<00:13:07.800> a<00:13:08.000> bridge<00:13:08.519> on<00:13:09.240> uh<00:13:09.519> ethereum<00:13:10.519> and<00:13:11.079> that 00:13:11.310 --> 00:13:11.320 align:start position:0% this is a bridge on uh ethereum and that 00:13:11.320 --> 00:13:14.629 align:start position:0% this is a bridge on uh ethereum and that bridge<00:13:12.240> is<00:13:13.120> uh<00:13:13.240> the<00:13:13.360> bridge<00:13:13.680> used<00:13:14.000> to<00:13:14.240> create 00:13:14.629 --> 00:13:14.639 align:start position:0% bridge is uh the bridge used to create 00:13:14.639 --> 00:13:17.710 align:start position:0% bridge is uh the bridge used to create canonical<00:13:15.360> assets<00:13:16.360> that<00:13:16.519> allows<00:13:17.000> for<00:13:17.480> all 00:13:17.710 --> 00:13:17.720 align:start position:0% canonical assets that allows for all 00:13:17.720 --> 00:13:19.910 align:start position:0% canonical assets that allows for all transactions<00:13:18.360> going<00:13:18.600> across<00:13:18.880> the<00:13:19.040> agay<00:13:19.519> to<00:13:19.720> be 00:13:19.910 --> 00:13:19.920 align:start position:0% transactions going across the agay to be 00:13:19.920 --> 00:13:22.069 align:start position:0% transactions going across the agay to be done<00:13:20.240> in<00:13:20.440> fungible<00:13:21.120> assets<00:13:21.519> meaning<00:13:21.839> that<00:13:21.959> you 00:13:22.069 --> 00:13:22.079 align:start position:0% done in fungible assets meaning that you 00:13:22.079 --> 00:13:23.910 align:start position:0% done in fungible assets meaning that you don't<00:13:22.320> have<00:13:22.480> wrapped<00:13:22.839> assets<00:13:23.639> and<00:13:23.760> then 00:13:23.910 --> 00:13:23.920 align:start position:0% don't have wrapped assets and then 00:13:23.920 --> 00:13:27.110 align:start position:0% don't have wrapped assets and then unwrapped<00:13:24.760> assets<00:13:25.760> and<00:13:25.880> then<00:13:26.079> lastly<00:13:26.880> there's 00:13:27.110 --> 00:13:27.120 align:start position:0% unwrapped assets and then lastly there's 00:13:27.120 --> 00:13:29.670 align:start position:0% unwrapped assets and then lastly there's this<00:13:27.320> concept<00:13:27.639> of<00:13:27.800> fast<00:13:28.000> interupt<00:13:29.240> the<00:13:29.440> a 00:13:29.670 --> 00:13:29.680 align:start position:0% this concept of fast interupt the a 00:13:29.680 --> 00:13:32.310 align:start position:0% this concept of fast interupt the a layer<00:13:30.399> with<00:13:30.760> nothing<00:13:31.079> else<00:13:31.600> going<00:13:31.959> between 00:13:32.310 --> 00:13:32.320 align:start position:0% layer with nothing else going between 00:13:32.320 --> 00:13:35.269 align:start position:0% layer with nothing else going between two<00:13:32.519> chains<00:13:33.240> especially<00:13:33.560> two<00:13:33.720> l2s<00:13:34.680> is<00:13:35.040> going 00:13:35.269 --> 00:13:35.279 align:start position:0% two chains especially two l2s is going 00:13:35.279 --> 00:13:37.990 align:start position:0% two chains especially two l2s is going to<00:13:35.839> settle<00:13:36.360> at<00:13:36.480> the<00:13:36.639> speed<00:13:37.000> of<00:13:37.399> of<00:13:37.680> you<00:13:37.800> know 00:13:37.990 --> 00:13:38.000 align:start position:0% to settle at the speed of of you know 00:13:38.000 --> 00:13:39.350 align:start position:0% to settle at the speed of of you know ethereum<00:13:38.399> settlement<00:13:38.920> and<00:13:39.000> so<00:13:39.160> we're<00:13:39.279> going 00:13:39.350 --> 00:13:39.360 align:start position:0% ethereum settlement and so we're going 00:13:39.360 --> 00:13:40.790 align:start position:0% ethereum settlement and so we're going to<00:13:39.480> be<00:13:39.639> looking<00:13:39.839> at<00:13:40.000> like 00:13:40.790 --> 00:13:40.800 align:start position:0% to be looking at like 00:13:40.800 --> 00:13:43.150 align:start position:0% to be looking at like 15minute<00:13:41.800> um<00:13:42.040> cross<00:13:42.279> chain<00:13:42.519> transactions 00:13:43.150 --> 00:13:43.160 align:start position:0% 15minute um cross chain transactions 00:13:43.160 --> 00:13:45.310 align:start position:0% 15minute um cross chain transactions which<00:13:43.279> isn't<00:13:43.560> good<00:13:43.720> enough<00:13:44.519> and<00:13:44.639> so<00:13:44.880> the<00:13:45.079> goal 00:13:45.310 --> 00:13:45.320 align:start position:0% which isn't good enough and so the goal 00:13:45.320 --> 00:13:46.790 align:start position:0% which isn't good enough and so the goal with<00:13:45.480> fast<00:13:45.720> interrupt<00:13:46.160> is<00:13:46.240> to<00:13:46.399> lower<00:13:46.680> that 00:13:46.790 --> 00:13:46.800 align:start position:0% with fast interrupt is to lower that 00:13:46.800 --> 00:13:50.910 align:start position:0% with fast interrupt is to lower that Lany<00:13:47.440> to<00:13:47.680> just<00:13:47.839> a<00:13:48.000> few<00:13:48.360> seconds<00:13:49.360> rather<00:13:49.720> than 00:13:50.910 --> 00:13:50.920 align:start position:0% Lany to just a few seconds rather than 00:13:50.920 --> 00:13:53.870 align:start position:0% Lany to just a few seconds rather than minutes<00:13:51.920> so<00:13:52.120> like<00:13:52.279> what<00:13:52.360> are<00:13:52.519> the<00:13:52.720> benefits<00:13:53.639> of 00:13:53.870 --> 00:13:53.880 align:start position:0% minutes so like what are the benefits of 00:13:53.880 --> 00:13:56.829 align:start position:0% minutes so like what are the benefits of this<00:13:54.800> um<00:13:55.399> first<00:13:55.639> of<00:13:55.800> all<00:13:56.120> is<00:13:56.320> you<00:13:56.480> get<00:13:56.639> these 00:13:56.829 --> 00:13:56.839 align:start position:0% this um first of all is you get these 00:13:56.839 --> 00:14:01.310 align:start position:0% this um first of all is you get these native<00:13:57.160> tokens<00:13:58.160> um<00:13:59.480> look<00:14:00.040> I<00:14:00.360> I<00:14:00.560> think<00:14:00.880> Cosmos 00:14:01.310 --> 00:14:01.320 align:start position:0% native tokens um look I I think Cosmos 00:14:01.320 --> 00:14:02.910 align:start position:0% native tokens um look I I think Cosmos has<00:14:01.440> done<00:14:01.680> many<00:14:02.000> correct<00:14:02.360> things<00:14:02.680> but<00:14:02.800> when 00:14:02.910 --> 00:14:02.920 align:start position:0% has done many correct things but when 00:14:02.920 --> 00:14:05.829 align:start position:0% has done many correct things but when you<00:14:03.040> go<00:14:03.199> and<00:14:03.360> you<00:14:03.480> use<00:14:03.759> Cosmos<00:14:04.720> um<00:14:05.440> the 00:14:05.829 --> 00:14:05.839 align:start position:0% you go and you use Cosmos um the 00:14:05.839 --> 00:14:08.590 align:start position:0% you go and you use Cosmos um the experience<00:14:06.360> of<00:14:06.600> having<00:14:07.440> many<00:14:07.759> many<00:14:08.000> unwrapped 00:14:08.590 --> 00:14:08.600 align:start position:0% experience of having many many unwrapped 00:14:08.600 --> 00:14:11.350 align:start position:0% experience of having many many unwrapped tokens<00:14:09.240> uh<00:14:09.360> WRA<00:14:09.680> tokens<00:14:10.639> uh<00:14:10.759> and<00:14:10.839> moving<00:14:11.160> those 00:14:11.350 --> 00:14:11.360 align:start position:0% tokens uh WRA tokens uh and moving those 00:14:11.360 --> 00:14:12.430 align:start position:0% tokens uh WRA tokens uh and moving those around<00:14:11.560> and<00:14:11.720> figuring<00:14:12.000> out<00:14:12.120> what<00:14:12.279> these 00:14:12.430 --> 00:14:12.440 align:start position:0% around and figuring out what these 00:14:12.440 --> 00:14:15.110 align:start position:0% around and figuring out what these assets<00:14:12.759> are<00:14:13.160> and<00:14:13.440> the<00:14:13.560> same<00:14:13.759> has<00:14:13.959> become<00:14:14.320> true 00:14:15.110 --> 00:14:15.120 align:start position:0% assets are and the same has become true 00:14:15.120 --> 00:14:17.269 align:start position:0% assets are and the same has become true uh<00:14:15.320> within<00:14:15.519> the<00:14:15.639> ethereum<00:14:16.079> ecosystem<00:14:16.639> as<00:14:16.759> well 00:14:17.269 --> 00:14:17.279 align:start position:0% uh within the ethereum ecosystem as well 00:14:17.279 --> 00:14:20.069 align:start position:0% uh within the ethereum ecosystem as well like<00:14:17.440> that<00:14:17.560> is<00:14:17.800> not<00:14:18.079> a<00:14:18.320> good<00:14:18.519> user<00:14:19.079> experience 00:14:20.069 --> 00:14:20.079 align:start position:0% like that is not a good user experience 00:14:20.079 --> 00:14:21.910 align:start position:0% like that is not a good user experience second<00:14:20.399> is<00:14:20.519> we<00:14:20.639> need<00:14:20.920> safe<00:14:21.360> cross-chain 00:14:21.910 --> 00:14:21.920 align:start position:0% second is we need safe cross-chain 00:14:21.920 --> 00:14:23.949 align:start position:0% second is we need safe cross-chain transactions<00:14:22.839> you<00:14:22.959> know<00:14:23.240> as<00:14:23.320> of<00:14:23.560> right<00:14:23.720> now 00:14:23.949 --> 00:14:23.959 align:start position:0% transactions you know as of right now 00:14:23.959 --> 00:14:25.710 align:start position:0% transactions you know as of right now when<00:14:24.079> we<00:14:24.240> use<00:14:24.440> bridges<00:14:24.839> that<00:14:24.959> we<00:14:25.120> use<00:14:25.519> like 00:14:25.710 --> 00:14:25.720 align:start position:0% when we use bridges that we use like 00:14:25.720 --> 00:14:27.150 align:start position:0% when we use bridges that we use like most<00:14:25.880> of<00:14:25.959> the<00:14:26.079> time<00:14:26.240> these<00:14:26.360> are<00:14:26.560> not<00:14:26.759> actually 00:14:27.150 --> 00:14:27.160 align:start position:0% most of the time these are not actually 00:14:27.160 --> 00:14:30.550 align:start position:0% most of the time these are not actually very<00:14:27.480> safe<00:14:28.160> for<00:14:28.639> inter<00:14:29.160> operability<00:14:30.120> and<00:14:30.360> we 00:14:30.550 --> 00:14:30.560 align:start position:0% very safe for inter operability and we 00:14:30.560 --> 00:14:33.310 align:start position:0% very safe for inter operability and we actually<00:14:30.839> need<00:14:31.120> something<00:14:31.399> to<00:14:31.720> add<00:14:32.040> safety<00:14:33.040> um 00:14:33.310 --> 00:14:33.320 align:start position:0% actually need something to add safety um 00:14:33.320 --> 00:14:34.389 align:start position:0% actually need something to add safety um sometimes<00:14:33.519> we<00:14:33.639> talk<00:14:33.839> about<00:14:34.000> like<00:14:34.120> shared 00:14:34.389 --> 00:14:34.399 align:start position:0% sometimes we talk about like shared 00:14:34.399 --> 00:14:36.550 align:start position:0% sometimes we talk about like shared sequencers<00:14:35.000> as<00:14:35.199> providing<00:14:36.040> like<00:14:36.199> Atomic 00:14:36.550 --> 00:14:36.560 align:start position:0% sequencers as providing like Atomic 00:14:36.560 --> 00:14:38.829 align:start position:0% sequencers as providing like Atomic composability<00:14:37.199> again<00:14:38.199> you<00:14:38.360> need<00:14:38.560> something 00:14:38.829 --> 00:14:38.839 align:start position:0% composability again you need something 00:14:38.839 --> 00:14:41.350 align:start position:0% composability again you need something to<00:14:39.120> actually<00:14:39.480> make<00:14:39.759> that<00:14:40.199> safe<00:14:40.519> and 00:14:41.350 --> 00:14:41.360 align:start position:0% to actually make that safe and 00:14:41.360 --> 00:14:43.550 align:start position:0% to actually make that safe and trustless<00:14:42.360> and<00:14:42.680> importantly<00:14:43.240> this<00:14:43.320> is<00:14:43.440> where 00:14:43.550 --> 00:14:43.560 align:start position:0% trustless and importantly this is where 00:14:43.560 --> 00:14:45.949 align:start position:0% trustless and importantly this is where you<00:14:43.680> get<00:14:43.800> the<00:14:43.920> concept<00:14:44.199> of<00:14:44.639> compatibility<00:14:45.639> is 00:14:45.949 --> 00:14:45.959 align:start position:0% you get the concept of compatibility is 00:14:45.959 --> 00:14:48.550 align:start position:0% you get the concept of compatibility is the<00:14:46.120> AG<00:14:46.399> layer<00:14:46.839> often<00:14:47.120> is<00:14:47.279> viewed<00:14:47.639> as<00:14:47.839> like 00:14:48.550 --> 00:14:48.560 align:start position:0% the AG layer often is viewed as like 00:14:48.560 --> 00:14:51.030 align:start position:0% the AG layer often is viewed as like competitive<00:14:49.560> with<00:14:50.160> all<00:14:50.320> of<00:14:50.519> these<00:14:50.720> different 00:14:51.030 --> 00:14:51.040 align:start position:0% competitive with all of these different 00:14:51.040 --> 00:14:52.470 align:start position:0% competitive with all of these different options<00:14:51.399> that<00:14:51.560> people<00:14:51.800> hear<00:14:52.040> about<00:14:52.279> for 00:14:52.470 --> 00:14:52.480 align:start position:0% options that people hear about for 00:14:52.480 --> 00:14:54.829 align:start position:0% options that people hear about for interoperability<00:14:53.360> purposes<00:14:54.320> um<00:14:54.519> but<00:14:54.639> it 00:14:54.829 --> 00:14:54.839 align:start position:0% interoperability purposes um but it 00:14:54.839 --> 00:14:56.990 align:start position:0% interoperability purposes um but it actually<00:14:55.160> really<00:14:55.399> isn't<00:14:55.920> it's<00:14:56.199> a<00:14:56.480> very 00:14:56.990 --> 00:14:57.000 align:start position:0% actually really isn't it's a very 00:14:57.000 --> 00:15:00.550 align:start position:0% actually really isn't it's a very low-level<00:14:57.839> base<00:14:58.120> layer<00:14:59.199> that<00:14:59.600> is<00:14:59.959> compatible 00:15:00.550 --> 00:15:00.560 align:start position:0% low-level base layer that is compatible 00:15:00.560 --> 00:15:03.189 align:start position:0% low-level base layer that is compatible with<00:15:00.720> most<00:15:00.880> of<00:15:01.079> these<00:15:01.360> so<00:15:01.959> if<00:15:02.120> you<00:15:02.360> want<00:15:02.839> to<00:15:03.000> do 00:15:03.189 --> 00:15:03.199 align:start position:0% with most of these so if you want to do 00:15:03.199 --> 00:15:04.949 align:start position:0% with most of these so if you want to do an<00:15:03.360> asynchronous<00:15:03.920> transaction<00:15:04.440> you<00:15:04.600> use<00:15:04.800> the 00:15:04.949 --> 00:15:04.959 align:start position:0% an asynchronous transaction you use the 00:15:04.959 --> 00:15:06.389 align:start position:0% an asynchronous transaction you use the AG<00:15:05.199> layer<00:15:05.480> but<00:15:05.560> if<00:15:05.639> you<00:15:05.720> want<00:15:05.800> a<00:15:05.920> synchronous 00:15:06.389 --> 00:15:06.399 align:start position:0% AG layer but if you want a synchronous 00:15:06.399 --> 00:15:07.910 align:start position:0% AG layer but if you want a synchronous transaction<00:15:07.120> then<00:15:07.240> you<00:15:07.320> would<00:15:07.519> actually<00:15:07.720> use 00:15:07.910 --> 00:15:07.920 align:start position:0% transaction then you would actually use 00:15:07.920 --> 00:15:09.470 align:start position:0% transaction then you would actually use a<00:15:08.000> shared<00:15:08.320> sequencer<00:15:08.880> with<00:15:09.000> the<00:15:09.120> added 00:15:09.470 --> 00:15:09.480 align:start position:0% a shared sequencer with the added 00:15:09.480 --> 00:15:12.470 align:start position:0% a shared sequencer with the added security<00:15:10.160> of<00:15:10.360> the<00:15:10.680> agay<00:15:11.680> um<00:15:12.040> if<00:15:12.160> you<00:15:12.240> want<00:15:12.360> to 00:15:12.470 --> 00:15:12.480 align:start position:0% security of the agay um if you want to 00:15:12.480 --> 00:15:14.829 align:start position:0% security of the agay um if you want to use<00:15:12.839> intents<00:15:13.839> those<00:15:13.959> are<00:15:14.199> expensive<00:15:14.720> they 00:15:14.829 --> 00:15:14.839 align:start position:0% use intents those are expensive they 00:15:14.839 --> 00:15:16.590 align:start position:0% use intents those are expensive they require<00:15:15.360> capital<00:15:15.680> on<00:15:15.800> two<00:15:16.000> different<00:15:16.199> pools 00:15:16.590 --> 00:15:16.600 align:start position:0% require capital on two different pools 00:15:16.600 --> 00:15:18.629 align:start position:0% require capital on two different pools you<00:15:16.680> need<00:15:16.800> to<00:15:17.040> rebalance<00:15:17.680> that<00:15:17.920> Capital 00:15:18.629 --> 00:15:18.639 align:start position:0% you need to rebalance that Capital 00:15:18.639 --> 00:15:21.069 align:start position:0% you need to rebalance that Capital rebalancing<00:15:19.240> that<00:15:19.480> Capital<00:15:19.920> has<00:15:20.240> risk<00:15:20.800> and 00:15:21.069 --> 00:15:21.079 align:start position:0% rebalancing that Capital has risk and 00:15:21.079 --> 00:15:22.910 align:start position:0% rebalancing that Capital has risk and time<00:15:21.440> associated<00:15:22.000> with<00:15:22.120> it<00:15:22.279> you<00:15:22.360> can<00:15:22.519> lower 00:15:22.910 --> 00:15:22.920 align:start position:0% time associated with it you can lower 00:15:22.920 --> 00:15:24.710 align:start position:0% time associated with it you can lower that<00:15:23.120> risk<00:15:23.360> in<00:15:23.600> time<00:15:24.160> allowing<00:15:24.480> for 00:15:24.710 --> 00:15:24.720 align:start position:0% that risk in time allowing for 00:15:24.720 --> 00:15:26.710 align:start position:0% that risk in time allowing for rebalancing<00:15:25.480> much<00:15:25.680> quicker<00:15:26.160> allowing<00:15:26.480> for 00:15:26.710 --> 00:15:26.720 align:start position:0% rebalancing much quicker allowing for 00:15:26.720 --> 00:15:28.509 align:start position:0% rebalancing much quicker allowing for users<00:15:27.040> to<00:15:27.199> get<00:15:27.399> transactions<00:15:27.920> at<00:15:28.040> a<00:15:28.160> cheaper 00:15:28.509 --> 00:15:28.519 align:start position:0% users to get transactions at a cheaper 00:15:28.519 --> 00:15:29.590 align:start position:0% users to get transactions at a cheaper cost 00:15:29.590 --> 00:15:29.600 align:start position:0% cost 00:15:29.600 --> 00:15:31.990 align:start position:0% cost um<00:15:29.920> and<00:15:30.120> so<00:15:30.800> good<00:15:31.040> good<00:15:31.240> experience<00:15:31.720> there<00:15:31.920> and 00:15:31.990 --> 00:15:32.000 align:start position:0% um and so good good experience there and 00:15:32.000 --> 00:15:33.629 align:start position:0% um and so good good experience there and so<00:15:32.160> the<00:15:32.360> goal<00:15:32.880> when<00:15:33.120> when<00:15:33.240> we're<00:15:33.440> thinking 00:15:33.629 --> 00:15:33.639 align:start position:0% so the goal when when we're thinking 00:15:33.639 --> 00:15:35.189 align:start position:0% so the goal when when we're thinking about<00:15:33.800> building<00:15:34.040> the<00:15:34.120> Ager<00:15:34.759> with<00:15:34.880> the<00:15:34.959> other 00:15:35.189 --> 00:15:35.199 align:start position:0% about building the Ager with the other 00:15:35.199 --> 00:15:36.829 align:start position:0% about building the Ager with the other contributors<00:15:35.800> is<00:15:36.000> really<00:15:36.319> like<00:15:36.440> how<00:15:36.560> do<00:15:36.680> we 00:15:36.829 --> 00:15:36.839 align:start position:0% contributors is really like how do we 00:15:36.839 --> 00:15:39.670 align:start position:0% contributors is really like how do we make<00:15:37.199> this<00:15:37.800> the<00:15:38.120> best<00:15:39.000> uh<00:15:39.199> experience 00:15:39.670 --> 00:15:39.680 align:start position:0% make this the best uh experience 00:15:39.680 --> 00:15:41.150 align:start position:0% make this the best uh experience possible<00:15:40.000> and<00:15:40.120> that<00:15:40.199> includes<00:15:40.560> from<00:15:40.680> a<00:15:40.839> cost 00:15:41.150 --> 00:15:41.160 align:start position:0% possible and that includes from a cost 00:15:41.160 --> 00:15:42.629 align:start position:0% possible and that includes from a cost perspective<00:15:41.680> when<00:15:41.880> working<00:15:42.199> with<00:15:42.399> other 00:15:42.629 --> 00:15:42.639 align:start position:0% perspective when working with other 00:15:42.639 --> 00:15:46.309 align:start position:0% perspective when working with other Solutions<00:15:43.079> out<00:15:43.720> there<00:15:44.720> next<00:15:45.160> like<00:15:45.560> the<00:15:45.720> Ager 00:15:46.309 --> 00:15:46.319 align:start position:0% Solutions out there next like the Ager 00:15:46.319 --> 00:15:47.790 align:start position:0% Solutions out there next like the Ager if<00:15:46.399> you<00:15:46.560> think<00:15:46.720> about<00:15:46.880> it<00:15:47.040> is<00:15:47.240> really<00:15:47.440> like<00:15:47.600> an 00:15:47.790 --> 00:15:47.800 align:start position:0% if you think about it is really like an 00:15:47.800 --> 00:15:49.269 align:start position:0% if you think about it is really like an asset<00:15:48.120> first<00:15:48.440> protocol<00:15:48.800> you're<00:15:48.959> actually 00:15:49.269 --> 00:15:49.279 align:start position:0% asset first protocol you're actually 00:15:49.279 --> 00:15:51.030 align:start position:0% asset first protocol you're actually passing<00:15:49.759> assets<00:15:50.160> from<00:15:50.319> one<00:15:50.440> chain<00:15:50.639> to<00:15:50.800> another 00:15:51.030 --> 00:15:51.040 align:start position:0% passing assets from one chain to another 00:15:51.040 --> 00:15:52.710 align:start position:0% passing assets from one chain to another and<00:15:51.160> this<00:15:51.279> is<00:15:51.480> different<00:15:51.959> from<00:15:52.519> other 00:15:52.710 --> 00:15:52.720 align:start position:0% and this is different from other 00:15:52.720 --> 00:15:54.030 align:start position:0% and this is different from other interoperability<00:15:53.480> solutions<00:15:53.839> that<00:15:53.920> are 00:15:54.030 --> 00:15:54.040 align:start position:0% interoperability solutions that are 00:15:54.040 --> 00:15:56.670 align:start position:0% interoperability solutions that are generally<00:15:54.399> passing<00:15:54.680> messages<00:15:55.639> but<00:15:55.920> the<00:15:56.079> AG 00:15:56.670 --> 00:15:56.680 align:start position:0% generally passing messages but the AG 00:15:56.680 --> 00:15:59.069 align:start position:0% generally passing messages but the AG does<00:15:57.199> allow<00:15:57.480> for<00:15:57.720> passing<00:15:58.079> messages<00:15:58.560> as<00:15:58.720> well 00:15:59.069 --> 00:15:59.079 align:start position:0% does allow for passing messages as well 00:15:59.079 --> 00:16:01.069 align:start position:0% does allow for passing messages as well which<00:15:59.199> is<00:15:59.440> necessary<00:16:00.360> and<00:16:00.639> something<00:16:00.920> that 00:16:01.069 --> 00:16:01.079 align:start position:0% which is necessary and something that 00:16:01.079 --> 00:16:04.110 align:start position:0% which is necessary and something that can<00:16:01.240> be<00:16:01.600> done<00:16:02.600> um<00:16:02.920> next<00:16:03.240> is<00:16:03.720> it<00:16:03.880> actually 00:16:04.110 --> 00:16:04.120 align:start position:0% can be done um next is it actually 00:16:04.120 --> 00:16:05.949 align:start position:0% can be done um next is it actually enables<00:16:04.920> the<00:16:05.079> concept<00:16:05.440> of<00:16:05.600> like<00:16:05.720> chain 00:16:05.949 --> 00:16:05.959 align:start position:0% enables the concept of like chain 00:16:05.959 --> 00:16:07.430 align:start position:0% enables the concept of like chain abstraction<00:16:06.440> I<00:16:06.519> think<00:16:06.600> chain<00:16:06.839> abstraction<00:16:07.319> is 00:16:07.430 --> 00:16:07.440 align:start position:0% abstraction I think chain abstraction is 00:16:07.440 --> 00:16:10.189 align:start position:0% abstraction I think chain abstraction is a<00:16:07.680> very<00:16:08.360> nebulous<00:16:09.079> concept<00:16:09.600> that<00:16:09.720> if<00:16:09.800> you<00:16:10.000> ask 00:16:10.189 --> 00:16:10.199 align:start position:0% a very nebulous concept that if you ask 00:16:10.199 --> 00:16:11.749 align:start position:0% a very nebulous concept that if you ask 10<00:16:10.399> people<00:16:10.639> what<00:16:10.759> is<00:16:10.880> chain<00:16:11.079> abstraction<00:16:11.560> 10 00:16:11.749 --> 00:16:11.759 align:start position:0% 10 people what is chain abstraction 10 00:16:11.759 --> 00:16:13.550 align:start position:0% 10 people what is chain abstraction 10 people<00:16:11.920> will<00:16:12.079> give<00:16:12.199> you<00:16:12.319> different<00:16:12.600> answers 00:16:13.550 --> 00:16:13.560 align:start position:0% people will give you different answers 00:16:13.560 --> 00:16:15.389 align:start position:0% people will give you different answers um<00:16:13.959> the<00:16:14.120> way<00:16:14.279> that<00:16:14.399> I<00:16:14.560> often<00:16:14.800> think<00:16:15.040> about<00:16:15.199> it 00:16:15.389 --> 00:16:15.399 align:start position:0% um the way that I often think about it 00:16:15.399 --> 00:16:19.470 align:start position:0% um the way that I often think about it is<00:16:15.639> like<00:16:15.800> the<00:16:16.600> the<00:16:16.720> AG<00:16:16.959> layer<00:16:17.319> allows<00:16:18.319> for<00:16:19.160> um 00:16:19.470 --> 00:16:19.480 align:start position:0% is like the the AG layer allows for um 00:16:19.480 --> 00:16:21.389 align:start position:0% is like the the AG layer allows for um easy<00:16:19.880> use<00:16:20.079> of<00:16:20.240> chain<00:16:20.480> abstraction<00:16:21.120> and<00:16:21.279> like 00:16:21.389 --> 00:16:21.399 align:start position:0% easy use of chain abstraction and like 00:16:21.399 --> 00:16:23.670 align:start position:0% easy use of chain abstraction and like one<00:16:21.639> example<00:16:22.079> of<00:16:22.319> this<00:16:22.720> is<00:16:23.000> a<00:16:23.160> library<00:16:23.600> that 00:16:23.670 --> 00:16:23.680 align:start position:0% one example of this is a library that 00:16:23.680 --> 00:16:25.150 align:start position:0% one example of this is a library that we've<00:16:23.880> built<00:16:24.120> that<00:16:24.240> we<00:16:24.360> refer<00:16:24.639> to<00:16:24.839> as<00:16:24.959> bridge 00:16:25.150 --> 00:16:25.160 align:start position:0% we've built that we refer to as bridge 00:16:25.160 --> 00:16:27.910 align:start position:0% we've built that we refer to as bridge and<00:16:25.360> call<00:16:26.199> um<00:16:26.440> and<00:16:26.560> so<00:16:26.759> this<00:16:26.839> is<00:16:26.959> a<00:16:27.160> library 00:16:27.910 --> 00:16:27.920 align:start position:0% and call um and so this is a library 00:16:27.920 --> 00:16:31.749 align:start position:0% and call um and so this is a library that<00:16:28.600> uh<00:16:28.959> allows<00:16:29.480> for<00:16:30.440> uh<00:16:30.639> users<00:16:31.040> to<00:16:31.240> basically 00:16:31.749 --> 00:16:31.759 align:start position:0% that uh allows for uh users to basically 00:16:31.759 --> 00:16:34.590 align:start position:0% that uh allows for uh users to basically execute<00:16:32.600> uh<00:16:32.720> one<00:16:32.920> transaction<00:16:33.560> themselves<00:16:34.399> um 00:16:34.590 --> 00:16:34.600 align:start position:0% execute uh one transaction themselves um 00:16:34.600 --> 00:16:35.870 align:start position:0% execute uh one transaction themselves um but<00:16:34.720> they're<00:16:34.920> actually<00:16:35.120> executing<00:16:35.519> multiple 00:16:35.870 --> 00:16:35.880 align:start position:0% but they're actually executing multiple 00:16:35.880 --> 00:16:37.790 align:start position:0% but they're actually executing multiple transactions<00:16:36.399> across<00:16:36.680> chain<00:16:37.040> so<00:16:37.360> imagine 00:16:37.790 --> 00:16:37.800 align:start position:0% transactions across chain so imagine 00:16:37.800 --> 00:16:41.309 align:start position:0% transactions across chain so imagine that<00:16:37.920> you<00:16:38.079> wanted<00:16:38.480> to<00:16:39.480> um<00:16:39.800> Bridge<00:16:40.399> funds<00:16:40.920> from 00:16:41.309 --> 00:16:41.319 align:start position:0% that you wanted to um Bridge funds from 00:16:41.319 --> 00:16:44.110 align:start position:0% that you wanted to um Bridge funds from ethereum<00:16:41.959> to<00:16:42.240> polygon<00:16:42.639> Z<00:16:42.880> KVM<00:16:43.800> and<00:16:43.920> then<00:16:44.000> you 00:16:44.110 --> 00:16:44.120 align:start position:0% ethereum to polygon Z KVM and then you 00:16:44.120 --> 00:16:47.749 align:start position:0% ethereum to polygon Z KVM and then you wanted<00:16:44.360> to<00:16:44.560> swap<00:16:45.279> those<00:16:46.160> assets<00:16:47.160> um<00:16:47.440> into 00:16:47.749 --> 00:16:47.759 align:start position:0% wanted to swap those assets um into 00:16:47.759 --> 00:16:49.710 align:start position:0% wanted to swap those assets um into different<00:16:48.160> assets<00:16:48.800> and<00:16:48.920> then<00:16:49.079> transfer<00:16:49.519> them 00:16:49.710 --> 00:16:49.720 align:start position:0% different assets and then transfer them 00:16:49.720 --> 00:16:53.230 align:start position:0% different assets and then transfer them over<00:16:49.959> to<00:16:50.279> X<00:16:50.600> layer<00:16:51.240> and<00:16:51.360> then<00:16:51.560> buy<00:16:51.759> an<00:16:52.160> nft<00:16:53.160> with 00:16:53.230 --> 00:16:53.240 align:start position:0% over to X layer and then buy an nft with 00:16:53.240 --> 00:16:55.309 align:start position:0% over to X layer and then buy an nft with the<00:16:53.360> bridge<00:16:53.600> and<00:16:53.759> call<00:16:54.079> function<00:16:54.839> you<00:16:54.959> can<00:16:55.120> do 00:16:55.309 --> 00:16:55.319 align:start position:0% the bridge and call function you can do 00:16:55.319 --> 00:16:56.990 align:start position:0% the bridge and call function you can do that<00:16:55.560> and<00:16:55.639> so<00:16:55.759> you<00:16:55.839> can<00:16:56.040> imagine<00:16:56.399> a<00:16:56.560> wallet 00:16:56.990 --> 00:16:57.000 align:start position:0% that and so you can imagine a wallet 00:16:57.000 --> 00:16:58.350 align:start position:0% that and so you can imagine a wallet that<00:16:57.160> abstracts<00:16:57.639> that<00:16:57.759> all<00:16:57.920> away<00:16:58.199> and 00:16:58.350 --> 00:16:58.360 align:start position:0% that abstracts that all away and 00:16:58.360 --> 00:17:00.509 align:start position:0% that abstracts that all away and basically<00:16:59.000> says<00:16:59.519> hey<00:16:59.639> do<00:16:59.759> you<00:16:59.839> want<00:16:59.920> to<00:17:00.079> do<00:17:00.399> you 00:17:00.509 --> 00:17:00.519 align:start position:0% basically says hey do you want to do you 00:17:00.519 --> 00:17:03.710 align:start position:0% basically says hey do you want to do you know<00:17:01.040> this<00:17:01.560> this<00:17:01.759> bridge<00:17:02.560> transfer<00:17:03.319> and<00:17:03.480> then 00:17:03.710 --> 00:17:03.720 align:start position:0% know this this bridge transfer and then 00:17:03.720 --> 00:17:06.069 align:start position:0% know this this bridge transfer and then this<00:17:04.079> Swap<00:17:04.880> and<00:17:04.959> then<00:17:05.160> transfer<00:17:05.600> it<00:17:05.839> and<00:17:05.919> then 00:17:06.069 --> 00:17:06.079 align:start position:0% this Swap and then transfer it and then 00:17:06.079 --> 00:17:09.429 align:start position:0% this Swap and then transfer it and then buy<00:17:06.280> this<00:17:06.400> nft<00:17:07.360> click<00:17:07.679> one<00:17:07.959> button<00:17:08.600> and<00:17:09.319> you 00:17:09.429 --> 00:17:09.439 align:start position:0% buy this nft click one button and you 00:17:09.439 --> 00:17:10.829 align:start position:0% buy this nft click one button and you know<00:17:09.640> it's<00:17:09.799> calling<00:17:10.079> multiple<00:17:10.439> functions<00:17:10.760> in 00:17:10.829 --> 00:17:10.839 align:start position:0% know it's calling multiple functions in 00:17:10.839 --> 00:17:13.189 align:start position:0% know it's calling multiple functions in the<00:17:11.000> background<00:17:11.880> and<00:17:12.319> you've<00:17:12.640> abstracted 00:17:13.189 --> 00:17:13.199 align:start position:0% the background and you've abstracted 00:17:13.199 --> 00:17:14.949 align:start position:0% the background and you've abstracted away<00:17:13.439> the<00:17:13.559> entire<00:17:13.919> kind<00:17:14.039> of<00:17:14.160> cross-chain 00:17:14.949 --> 00:17:14.959 align:start position:0% away the entire kind of cross-chain 00:17:14.959 --> 00:17:17.189 align:start position:0% away the entire kind of cross-chain experience<00:17:15.959> um<00:17:16.400> and<00:17:16.520> then<00:17:16.720> lastly<00:17:17.039> it 00:17:17.189 --> 00:17:17.199 align:start position:0% experience um and then lastly it 00:17:17.199 --> 00:17:19.189 align:start position:0% experience um and then lastly it provides<00:17:17.480> for<00:17:17.679> this<00:17:17.880> low<00:17:18.280> interoperability 00:17:19.189 --> 00:17:19.199 align:start position:0% provides for this low interoperability 00:17:19.199 --> 00:17:21.189 align:start position:0% provides for this low interoperability uh<00:17:19.360> low<00:17:19.520> latency<00:17:20.480> in<00:17:20.640> terms<00:17:20.880> of<00:17:21.039> these 00:17:21.189 --> 00:17:21.199 align:start position:0% uh low latency in terms of these 00:17:21.199 --> 00:17:23.549 align:start position:0% uh low latency in terms of these cross-chain<00:17:22.240> transactions<00:17:23.240> again<00:17:23.439> it 00:17:23.549 --> 00:17:23.559 align:start position:0% cross-chain transactions again it 00:17:23.559 --> 00:17:25.470 align:start position:0% cross-chain transactions again it doesn't<00:17:23.839> provide<00:17:24.280> synchronous<00:17:25.280> um 00:17:25.470 --> 00:17:25.480 align:start position:0% doesn't provide synchronous um 00:17:25.480 --> 00:17:27.309 align:start position:0% doesn't provide synchronous um interoperability<00:17:26.360> that's<00:17:26.559> something<00:17:26.880> that 00:17:27.309 --> 00:17:27.319 align:start position:0% interoperability that's something that 00:17:27.319 --> 00:17:28.990 align:start position:0% interoperability that's something that by<00:17:27.480> working<00:17:27.760> with<00:17:27.880> shared<00:17:28.199> sequencers 00:17:28.990 --> 00:17:29.000 align:start position:0% by working with shared sequencers 00:17:29.000 --> 00:17:31.950 align:start position:0% by working with shared sequencers secured<00:17:29.360> by<00:17:29.480> the<00:17:29.600> AG<00:17:29.840> layer<00:17:30.840> you<00:17:31.000> can<00:17:31.240> receive 00:17:31.950 --> 00:17:31.960 align:start position:0% secured by the AG layer you can receive 00:17:31.960 --> 00:17:33.310 align:start position:0% secured by the AG layer you can receive but<00:17:32.080> it's<00:17:32.240> not<00:17:32.400> something<00:17:32.640> that<00:17:32.760> the<00:17:32.919> AG<00:17:33.080> layer 00:17:33.310 --> 00:17:33.320 align:start position:0% but it's not something that the AG layer 00:17:33.320 --> 00:17:34.230 align:start position:0% but it's not something that the AG layer gives 00:17:34.230 --> 00:17:34.240 align:start position:0% gives 00:17:34.240 --> 00:17:36.750 align:start position:0% gives natively<00:17:35.240> this<00:17:35.400> is<00:17:35.559> the<00:17:35.679> AG<00:17:35.840> layer<00:17:36.120> ecosystem 00:17:36.750 --> 00:17:36.760 align:start position:0% natively this is the AG layer ecosystem 00:17:36.760 --> 00:17:38.750 align:start position:0% natively this is the AG layer ecosystem multiple<00:17:37.280> contributors<00:17:38.280> um<00:17:38.400> we're<00:17:38.559> always 00:17:38.750 --> 00:17:38.760 align:start position:0% multiple contributors um we're always 00:17:38.760 --> 00:17:40.710 align:start position:0% multiple contributors um we're always looking<00:17:38.960> to<00:17:39.160> work<00:17:39.360> with<00:17:39.520> more<00:17:39.760> folks<00:17:40.039> on<00:17:40.280> this 00:17:40.710 --> 00:17:40.720 align:start position:0% looking to work with more folks on this 00:17:40.720 --> 00:17:42.150 align:start position:0% looking to work with more folks on this one<00:17:40.840> thing<00:17:41.000> you'll<00:17:41.160> notice<00:17:41.440> is<00:17:41.559> the<00:17:41.679> agair<00:17:42.039> is 00:17:42.150 --> 00:17:42.160 align:start position:0% one thing you'll notice is the agair is 00:17:42.160 --> 00:17:44.430 align:start position:0% one thing you'll notice is the agair is not<00:17:42.280> called<00:17:42.480> the<00:17:42.600> polygon<00:17:42.960> agair<00:17:43.960> uh<00:17:44.160> this<00:17:44.240> is 00:17:44.430 --> 00:17:44.440 align:start position:0% not called the polygon agair uh this is 00:17:44.440 --> 00:17:47.029 align:start position:0% not called the polygon agair uh this is very<00:17:44.640> intentional<00:17:45.480> we've<00:17:45.840> talked<00:17:46.160> to<00:17:46.799> every 00:17:47.029 --> 00:17:47.039 align:start position:0% very intentional we've talked to every 00:17:47.039 --> 00:17:49.270 align:start position:0% very intentional we've talked to every big<00:17:47.200> team<00:17:47.400> in<00:17:47.520> the<00:17:47.600> ethereum<00:17:48.080> ecosystem<00:17:48.960> and 00:17:49.270 --> 00:17:49.280 align:start position:0% big team in the ethereum ecosystem and 00:17:49.280 --> 00:17:51.549 align:start position:0% big team in the ethereum ecosystem and most<00:17:49.559> outside<00:17:49.960> of<00:17:50.120> it<00:17:50.840> goal<00:17:51.120> is<00:17:51.240> to<00:17:51.360> get 00:17:51.549 --> 00:17:51.559 align:start position:0% most outside of it goal is to get 00:17:51.559 --> 00:17:53.310 align:start position:0% most outside of it goal is to get everybody<00:17:51.880> to<00:17:52.120> contribute<00:17:52.559> so<00:17:52.720> that<00:17:52.880> we<00:17:53.000> can 00:17:53.310 --> 00:17:53.320 align:start position:0% everybody to contribute so that we can 00:17:53.320 --> 00:17:56.870 align:start position:0% everybody to contribute so that we can have<00:17:54.000> a<00:17:54.520> non-fragmented<00:17:55.240> web<00:17:55.640> 3<00:17:55.960> as<00:17:56.080> a<00:17:56.240> whole 00:17:56.870 --> 00:17:56.880 align:start position:0% have a non-fragmented web 3 as a whole 00:17:56.880 --> 00:17:59.669 align:start position:0% have a non-fragmented web 3 as a whole allowing<00:17:57.280> for<00:17:57.480> ethereum<00:17:58.120> to<00:17:58.280> grow<00:17:58.559> and<00:17:59.039> used 00:17:59.669 --> 00:17:59.679 align:start position:0% allowing for ethereum to grow and used 00:17:59.679 --> 00:18:02.270 align:start position:0% allowing for ethereum to grow and used without<00:18:00.080> actually<00:18:00.480> needing<00:18:00.840> to<00:18:01.200> to<00:18:01.400> leave 00:18:02.270 --> 00:18:02.280 align:start position:0% without actually needing to to leave 00:18:02.280 --> 00:18:05.390 align:start position:0% without actually needing to to leave ethereum<00:18:03.320> um<00:18:04.320> a<00:18:04.480> very<00:18:04.679> important<00:18:05.000> point<00:18:05.280> is 00:18:05.390 --> 00:18:05.400 align:start position:0% ethereum um a very important point is 00:18:05.400 --> 00:18:08.149 align:start position:0% ethereum um a very important point is that<00:18:05.559> Ager<00:18:06.039> is<00:18:06.120> not<00:18:06.280> rcking<00:18:07.280> like<00:18:07.440> if<00:18:07.600> you<00:18:07.840> look 00:18:08.149 --> 00:18:08.159 align:start position:0% that Ager is not rcking like if you look 00:18:08.159 --> 00:18:10.990 align:start position:0% that Ager is not rcking like if you look at<00:18:08.919> a<00:18:09.240> lot<00:18:09.440> of<00:18:09.679> different<00:18:09.960> interoperability 00:18:10.990 --> 00:18:11.000 align:start position:0% at a lot of different interoperability 00:18:11.000 --> 00:18:13.270 align:start position:0% at a lot of different interoperability Solutions<00:18:12.000> uh<00:18:12.120> and<00:18:12.200> a<00:18:12.320> lot<00:18:12.440> of<00:18:12.600> different<00:18:13.120> of 00:18:13.270 --> 00:18:13.280 align:start position:0% Solutions uh and a lot of different of 00:18:13.280 --> 00:18:15.230 align:start position:0% Solutions uh and a lot of different of other<00:18:13.480> ecosystems<00:18:14.120> building<00:18:14.480> out 00:18:15.230 --> 00:18:15.240 align:start position:0% other ecosystems building out 00:18:15.240 --> 00:18:17.029 align:start position:0% other ecosystems building out interoperability<00:18:16.240> um<00:18:16.440> what<00:18:16.559> you<00:18:16.679> end<00:18:16.840> up 00:18:17.029 --> 00:18:17.039 align:start position:0% interoperability um what you end up 00:18:17.039 --> 00:18:21.789 align:start position:0% interoperability um what you end up seeing<00:18:17.799> is<00:18:18.679> um<00:18:19.000> some<00:18:19.240> form<00:18:19.600> of<00:18:19.960> of<00:18:20.280> fee<00:18:21.280> um<00:18:21.600> that 00:18:21.789 --> 00:18:21.799 align:start position:0% seeing is um some form of of fee um that 00:18:21.799 --> 00:18:25.590 align:start position:0% seeing is um some form of of fee um that is<00:18:22.679> uh<00:18:23.320> placed<00:18:23.679> on<00:18:23.880> on<00:18:24.039> every<00:18:24.480> transaction<00:18:25.480> uh 00:18:25.590 --> 00:18:25.600 align:start position:0% is uh placed on on every transaction uh 00:18:25.600 --> 00:18:27.470 align:start position:0% is uh placed on on every transaction uh and<00:18:25.720> it<00:18:25.960> really<00:18:26.480> looks<00:18:26.720> like<00:18:26.919> kind<00:18:27.039> of<00:18:27.200> like<00:18:27.320> a 00:18:27.470 --> 00:18:27.480 align:start position:0% and it really looks like kind of like a 00:18:27.480 --> 00:18:31.270 align:start position:0% and it really looks like kind of like a middleman<00:18:28.280> form<00:18:29.039> of<00:18:29.280> rent<00:18:29.559> seeking<00:18:30.559> um<00:18:30.919> the<00:18:31.039> a 00:18:31.270 --> 00:18:31.280 align:start position:0% middleman form of rent seeking um the a 00:18:31.280 --> 00:18:35.430 align:start position:0% middleman form of rent seeking um the a layer<00:18:31.640> has<00:18:32.120> no<00:18:33.120> fee<00:18:33.640> for<00:18:33.919> joining<00:18:34.360> the<00:18:34.520> a<00:18:34.760> layer 00:18:35.430 --> 00:18:35.440 align:start position:0% layer has no fee for joining the a layer 00:18:35.440 --> 00:18:37.990 align:start position:0% layer has no fee for joining the a layer there's<00:18:35.720> actually<00:18:36.039> no<00:18:36.320> fee<00:18:36.760> per<00:18:37.080> transaction 00:18:37.990 --> 00:18:38.000 align:start position:0% there's actually no fee per transaction 00:18:38.000 --> 00:18:40.789 align:start position:0% there's actually no fee per transaction on<00:18:38.240> the<00:18:38.400> AG<00:18:38.679> layer<00:18:39.480> instead<00:18:39.880> what<00:18:40.000> it<00:18:40.200> is<00:18:40.559> is 00:18:40.789 --> 00:18:40.799 align:start position:0% on the AG layer instead what it is is 00:18:40.799 --> 00:18:44.510 align:start position:0% on the AG layer instead what it is is that<00:18:41.039> chains<00:18:41.840> are<00:18:42.039> going<00:18:42.240> to<00:18:42.799> create<00:18:43.799> uh<00:18:44.360> with 00:18:44.510 --> 00:18:44.520 align:start position:0% that chains are going to create uh with 00:18:44.520 --> 00:18:47.029 align:start position:0% that chains are going to create uh with as<00:18:44.679> many<00:18:44.960> transactions<00:18:45.480> as<00:18:45.640> they<00:18:45.760> can<00:18:46.039> include 00:18:47.029 --> 00:18:47.039 align:start position:0% as many transactions as they can include 00:18:47.039 --> 00:18:50.110 align:start position:0% as many transactions as they can include um<00:18:47.480> in<00:18:47.919> in<00:18:48.159> their<00:18:48.480> in<00:18:48.640> their<00:18:48.880> consensus<00:18:49.400> or<00:18:49.720> or 00:18:50.110 --> 00:18:50.120 align:start position:0% um in in their in their consensus or or 00:18:50.120 --> 00:18:52.029 align:start position:0% um in in their in their consensus or or that's<00:18:50.320> part<00:18:50.440> of<00:18:50.640> like<00:18:50.919> the<00:18:51.440> consensus<00:18:51.880> being 00:18:52.029 --> 00:18:52.039 align:start position:0% that's part of like the consensus being 00:18:52.039 --> 00:18:53.310 align:start position:0% that's part of like the consensus being satisfied<00:18:52.440> or<00:18:52.520> as<00:18:52.600> part<00:18:52.720> of<00:18:52.799> an<00:18:52.919> execution 00:18:53.310 --> 00:18:53.320 align:start position:0% satisfied or as part of an execution 00:18:53.320 --> 00:18:54.510 align:start position:0% satisfied or as part of an execution proof<00:18:53.760> and<00:18:53.840> they're<00:18:53.960> going<00:18:54.039> to<00:18:54.159> submit<00:18:54.440> that 00:18:54.510 --> 00:18:54.520 align:start position:0% proof and they're going to submit that 00:18:54.520 --> 00:18:56.230 align:start position:0% proof and they're going to submit that to<00:18:54.600> the<00:18:54.720> agare<00:18:55.280> they<00:18:55.360> could<00:18:55.520> choose<00:18:55.720> to<00:18:55.919> submit 00:18:56.230 --> 00:18:56.240 align:start position:0% to the agare they could choose to submit 00:18:56.240 --> 00:18:57.390 align:start position:0% to the agare they could choose to submit that<00:18:56.360> once<00:18:56.520> a<00:18:56.640> month<00:18:56.919> they<00:18:57.000> could<00:18:57.120> choose<00:18:57.280> to 00:18:57.390 --> 00:18:57.400 align:start position:0% that once a month they could choose to 00:18:57.400 --> 00:18:59.350 align:start position:0% that once a month they could choose to submit<00:18:57.679> that<00:18:57.840> every<00:18:58.000> two<00:18:58.240> seconds<00:18:59.080> they<00:18:59.240> get 00:18:59.350 --> 00:18:59.360 align:start position:0% submit that every two seconds they get 00:18:59.360 --> 00:19:01.070 align:start position:0% submit that every two seconds they get to<00:18:59.559> choose<00:18:59.919> how<00:19:00.120> often<00:19:00.440> they<00:19:00.640> actually<00:19:00.880> want 00:19:01.070 --> 00:19:01.080 align:start position:0% to choose how often they actually want 00:19:01.080 --> 00:19:05.270 align:start position:0% to choose how often they actually want to<00:19:01.360> submit<00:19:02.000> a<00:19:02.159> trans<00:19:02.799> a<00:19:03.000> a<00:19:03.240> a<00:19:03.559> proof<00:19:04.520> um<00:19:04.720> to<00:19:05.039> the 00:19:05.270 --> 00:19:05.280 align:start position:0% to submit a trans a a a proof um to the 00:19:05.280 --> 00:19:09.070 align:start position:0% to submit a trans a a a proof um to the Ager<00:19:06.280> um<00:19:06.520> and<00:19:06.679> that<00:19:06.880> allows<00:19:07.320> for<00:19:07.799> chains<00:19:08.440> to 00:19:09.070 --> 00:19:09.080 align:start position:0% Ager um and that allows for chains to 00:19:09.080 --> 00:19:11.669 align:start position:0% Ager um and that allows for chains to continue<00:19:09.480> to<00:19:09.799> remain<00:19:10.799> uh<00:19:10.960> Sovereign<00:19:11.520> for 00:19:11.669 --> 00:19:11.679 align:start position:0% continue to remain uh Sovereign for 00:19:11.679 --> 00:19:13.070 align:start position:0% continue to remain uh Sovereign for example<00:19:12.000> you<00:19:12.080> could<00:19:12.240> think<00:19:12.360> of<00:19:12.520> like<00:19:12.640> a<00:19:12.760> gaming 00:19:13.070 --> 00:19:13.080 align:start position:0% example you could think of like a gaming 00:19:13.080 --> 00:19:15.830 align:start position:0% example you could think of like a gaming chain<00:19:13.880> gaming<00:19:14.159> chain<00:19:14.400> is<00:19:14.600> going<00:19:14.720> to<00:19:15.000> say<00:19:15.520> hey 00:19:15.830 --> 00:19:15.840 align:start position:0% chain gaming chain is going to say hey 00:19:15.840 --> 00:19:20.149 align:start position:0% chain gaming chain is going to say hey our<00:19:16.159> users<00:19:16.720> don't<00:19:17.159> actually<00:19:18.159> care<00:19:18.919> how<00:19:19.280> often 00:19:20.149 --> 00:19:20.159 align:start position:0% our users don't actually care how often 00:19:20.159 --> 00:19:23.789 align:start position:0% our users don't actually care how often we<00:19:20.640> finalize<00:19:21.320> this<00:19:21.480> chain<00:19:22.400> or<00:19:23.360> they're<00:19:23.720> going 00:19:23.789 --> 00:19:23.799 align:start position:0% we finalize this chain or they're going 00:19:23.799 --> 00:19:28.070 align:start position:0% we finalize this chain or they're going to<00:19:24.080> accept<00:19:24.880> lower<00:19:25.760> security<00:19:26.799> requirements<00:19:27.799> um 00:19:28.070 --> 00:19:28.080 align:start position:0% to accept lower security requirements um 00:19:28.080 --> 00:19:30.070 align:start position:0% to accept lower security requirements um for<00:19:28.240> some<00:19:28.440> per<00:19:28.720> perod<00:19:28.919> of<00:19:29.120> time<00:19:29.720> and<00:19:29.840> so<00:19:29.960> we're 00:19:30.070 --> 00:19:30.080 align:start position:0% for some per perod of time and so we're 00:19:30.080 --> 00:19:32.230 align:start position:0% for some per perod of time and so we're going<00:19:30.159> to<00:19:30.320> submit<00:19:30.760> proofs<00:19:31.679> much<00:19:31.960> less 00:19:32.230 --> 00:19:32.240 align:start position:0% going to submit proofs much less 00:19:32.240 --> 00:19:34.270 align:start position:0% going to submit proofs much less frequently<00:19:32.960> than<00:19:33.159> like<00:19:33.280> a<00:19:33.440> defi<00:19:33.840> chain<00:19:34.120> that's 00:19:34.270 --> 00:19:34.280 align:start position:0% frequently than like a defi chain that's 00:19:34.280 --> 00:19:35.630 align:start position:0% frequently than like a defi chain that's going<00:19:34.360> to<00:19:34.440> say<00:19:34.679> hey<00:19:34.799> I<00:19:34.880> want<00:19:34.960> to<00:19:35.080> submit<00:19:35.360> proofs 00:19:35.630 --> 00:19:35.640 align:start position:0% going to say hey I want to submit proofs 00:19:35.640 --> 00:19:37.909 align:start position:0% going to say hey I want to submit proofs every<00:19:35.799> 2<00:19:36.000> seconds<00:19:36.840> uh<00:19:37.000> and<00:19:37.120> so<00:19:37.400> by<00:19:37.559> having<00:19:37.760> this 00:19:37.909 --> 00:19:37.919 align:start position:0% every 2 seconds uh and so by having this 00:19:37.919 --> 00:19:41.070 align:start position:0% every 2 seconds uh and so by having this flexibility<00:19:38.520> in<00:19:38.640> the<00:19:38.760> a<00:19:39.200> layer<00:19:40.200> um<00:19:40.440> it<00:19:40.600> allows 00:19:41.070 --> 00:19:41.080 align:start position:0% flexibility in the a layer um it allows 00:19:41.080 --> 00:19:43.430 align:start position:0% flexibility in the a layer um it allows for<00:19:42.000> um<00:19:42.320> people<00:19:42.480> to<00:19:42.600> be<00:19:42.720> able<00:19:42.880> to<00:19:43.080> execute 00:19:43.430 --> 00:19:43.440 align:start position:0% for um people to be able to execute 00:19:43.440 --> 00:19:46.110 align:start position:0% for um people to be able to execute these<00:19:43.600> transactions<00:19:44.240> basically<00:19:44.960> freely<00:19:45.960> uh 00:19:46.110 --> 00:19:46.120 align:start position:0% these transactions basically freely uh 00:19:46.120 --> 00:19:47.830 align:start position:0% these transactions basically freely uh and<00:19:46.200> so<00:19:46.360> basically<00:19:46.679> what<00:19:46.799> we<00:19:46.919> see<00:19:47.200> here<00:19:47.520> is 00:19:47.830 --> 00:19:47.840 align:start position:0% and so basically what we see here is 00:19:47.840 --> 00:19:50.190 align:start position:0% and so basically what we see here is that<00:19:48.000> we've<00:19:48.280> solved<00:19:48.960> fragmented<00:19:49.480> liquidity 00:19:50.190 --> 00:19:50.200 align:start position:0% that we've solved fragmented liquidity 00:19:50.200 --> 00:19:52.190 align:start position:0% that we've solved fragmented liquidity you've<00:19:50.400> got<00:19:50.600> fungible<00:19:51.240> assets<00:19:51.640> across<00:19:51.960> the 00:19:52.190 --> 00:19:52.200 align:start position:0% you've got fungible assets across the 00:19:52.200 --> 00:19:54.789 align:start position:0% you've got fungible assets across the ecosystem<00:19:53.200> you've<00:19:53.440> solved<00:19:53.880> scalability 00:19:54.789 --> 00:19:54.799 align:start position:0% ecosystem you've solved scalability 00:19:54.799 --> 00:19:56.750 align:start position:0% ecosystem you've solved scalability because<00:19:55.120> you<00:19:55.280> have<00:19:55.480> chains<00:19:56.000> that<00:19:56.080> can<00:19:56.240> be<00:19:56.400> spun 00:19:56.750 --> 00:19:56.760 align:start position:0% because you have chains that can be spun 00:19:56.760 --> 00:19:58.789 align:start position:0% because you have chains that can be spun up<00:19:56.919> at<00:19:57.039> any<00:19:57.200> point<00:19:57.400> in<00:19:57.600> time<00:19:58.159> you've<00:19:58.320> solved 00:19:58.789 --> 00:19:58.799 align:start position:0% up at any point in time you've solved 00:19:58.799 --> 00:20:00.390 align:start position:0% up at any point in time you've solved security<00:19:59.200> with<00:19:59.280> the<00:19:59.440> pessimistic<00:19:59.960> proof<00:20:00.280> that 00:20:00.390 --> 00:20:00.400 align:start position:0% security with the pessimistic proof that 00:20:00.400 --> 00:20:03.149 align:start position:0% security with the pessimistic proof that you<00:20:00.520> can<00:20:00.720> safely<00:20:01.159> go<00:20:01.559> between<00:20:01.960> chains<00:20:02.960> and 00:20:03.149 --> 00:20:03.159 align:start position:0% you can safely go between chains and 00:20:03.159 --> 00:20:05.909 align:start position:0% you can safely go between chains and you've<00:20:03.400> solved<00:20:04.080> the<00:20:04.240> ux<00:20:04.720> issue<00:20:05.480> because<00:20:05.760> you 00:20:05.909 --> 00:20:05.919 align:start position:0% you've solved the ux issue because you 00:20:05.919 --> 00:20:08.549 align:start position:0% you've solved the ux issue because you can<00:20:06.159> now<00:20:06.679> seamlessly<00:20:07.520> interoperate<00:20:08.240> between 00:20:08.549 --> 00:20:08.559 align:start position:0% can now seamlessly interoperate between 00:20:08.559 --> 00:20:11.149 align:start position:0% can now seamlessly interoperate between these<00:20:08.720> chains<00:20:09.640> with<00:20:09.880> some<00:20:10.039> of<00:20:10.280> the<00:20:10.679> kind<00:20:10.760> of 00:20:11.149 --> 00:20:11.159 align:start position:0% these chains with some of the kind of 00:20:11.159 --> 00:20:12.510 align:start position:0% these chains with some of the kind of greatest<00:20:11.520> Technologies<00:20:12.039> around<00:20:12.240> Shar 00:20:12.510 --> 00:20:12.520 align:start position:0% greatest Technologies around Shar 00:20:12.520 --> 00:20:14.070 align:start position:0% greatest Technologies around Shar sequencing<00:20:12.960> and<00:20:13.120> intent<00:20:13.600> that<00:20:13.679> are<00:20:13.799> going<00:20:13.919> to 00:20:14.070 --> 00:20:14.080 align:start position:0% sequencing and intent that are going to 00:20:14.080 --> 00:20:15.510 align:start position:0% sequencing and intent that are going to be<00:20:14.440> part<00:20:14.679> of 00:20:15.510 --> 00:20:15.520 align:start position:0% be part of 00:20:15.520 --> 00:20:19.110 align:start position:0% be part of this<00:20:16.520> and<00:20:16.640> what<00:20:16.760> you<00:20:16.880> end<00:20:17.080> up<00:20:17.360> with<00:20:17.840> is<00:20:18.640> really 00:20:19.110 --> 00:20:19.120 align:start position:0% this and what you end up with is really 00:20:19.120 --> 00:20:22.909 align:start position:0% this and what you end up with is really a<00:20:19.520> unified<00:20:20.480> kind<00:20:20.600> of<00:20:20.799> web<00:20:21.080> three<00:20:21.960> allowing<00:20:22.400> for 00:20:22.909 --> 00:20:22.919 align:start position:0% a unified kind of web three allowing for 00:20:22.919 --> 00:20:25.669 align:start position:0% a unified kind of web three allowing for users<00:20:23.280> to<00:20:23.480> stay<00:20:23.679> in<00:20:23.840> ethereum<00:20:24.600> benefit<00:20:25.200> from 00:20:25.669 --> 00:20:25.679 align:start position:0% users to stay in ethereum benefit from 00:20:25.679 --> 00:20:29.070 align:start position:0% users to stay in ethereum benefit from assets<00:20:26.200> across<00:20:26.640> every<00:20:26.919> ecosystem 00:20:29.070 --> 00:20:29.080 align:start position:0% assets across every ecosystem 00:20:29.080 --> 00:20:32.430 align:start position:0% assets across every ecosystem and<00:20:29.240> what<00:20:29.360> you<00:20:29.520> see<00:20:30.120> is<00:20:30.440> a<00:20:30.600> web<00:20:30.840> 3<00:20:31.640> that<00:20:31.840> ends<00:20:32.120> up 00:20:32.430 --> 00:20:32.440 align:start position:0% and what you see is a web 3 that ends up 00:20:32.440 --> 00:20:36.310 align:start position:0% and what you see is a web 3 that ends up actually<00:20:32.919> being<00:20:33.480> united<00:20:34.080> under<00:20:34.360> some<00:20:34.679> common 00:20:36.310 --> 00:20:36.320 align:start position:0% actually being united under some common 00:20:36.320 --> 00:20:41.070 align:start position:0% actually being united under some common protocol<00:20:37.320> thank 00:20:41.070 --> 00:20:41.080 align:start position:0% 00:20:41.080 --> 00:20:43.830 align:start position:0% you<00:20:42.080> thank<00:20:42.280> you<00:20:42.440> Mark<00:20:42.880> that<00:20:43.000> was<00:20:43.240> quite 00:20:43.830 --> 00:20:43.840 align:start position:0% you thank you Mark that was quite 00:20:43.840 --> 00:20:46.149 align:start position:0% you thank you Mark that was quite insightful<00:20:44.840> uh<00:20:44.919> we<00:20:45.039> do<00:20:45.200> have<00:20:45.320> a<00:20:45.440> few<00:20:45.679> questions 00:20:46.149 --> 00:20:46.159 align:start position:0% insightful uh we do have a few questions 00:20:46.159 --> 00:20:49.070 align:start position:0% insightful uh we do have a few questions here<00:20:46.679> so<00:20:46.960> who<00:20:47.200> will<00:20:47.600> aggregate<00:20:48.200> the 00:20:49.070 --> 00:20:49.080 align:start position:0% here so who will aggregate the 00:20:49.080 --> 00:20:51.390 align:start position:0% here so who will aggregate the aggregators<00:20:50.080> that's<00:20:50.200> a<00:20:50.320> good<00:20:50.520> question<00:20:50.919> um<00:20:51.240> I 00:20:51.390 --> 00:20:51.400 align:start position:0% aggregators that's a good question um I 00:20:51.400 --> 00:20:53.430 align:start position:0% aggregators that's a good question um I don't<00:20:51.720> know<00:20:52.400> um<00:20:52.640> we<00:20:52.720> see<00:20:52.919> this<00:20:53.039> all<00:20:53.120> the<00:20:53.240> time 00:20:53.430 --> 00:20:53.440 align:start position:0% don't know um we see this all the time 00:20:53.440 --> 00:20:55.830 align:start position:0% don't know um we see this all the time of<00:20:53.559> course<00:20:54.360> I<00:20:54.919> I<00:20:55.000> have<00:20:55.159> not<00:20:55.280> been<00:20:55.400> able<00:20:55.600> to<00:20:55.720> have 00:20:55.830 --> 00:20:55.840 align:start position:0% of course I I have not been able to have 00:20:55.840 --> 00:20:58.310 align:start position:0% of course I I have not been able to have anyone<00:20:56.159> point<00:20:56.360> to<00:20:56.520> me<00:20:57.120> to<00:20:57.559> another<00:20:57.919> team<00:20:58.200> that 00:20:58.310 --> 00:20:58.320 align:start position:0% anyone point to me to another team that 00:20:58.320 --> 00:21:01.430 align:start position:0% anyone point to me to another team that is<00:20:58.640> actually<00:20:58.919> trying<00:20:59.240> to<00:20:59.960> aggregate<00:21:00.919> um<00:21:01.240> all 00:21:01.430 --> 00:21:01.440 align:start position:0% is actually trying to aggregate um all 00:21:01.440 --> 00:21:06.110 align:start position:0% is actually trying to aggregate um all of<00:21:01.679> web<00:21:01.919> 3<00:21:02.840> um<00:21:03.159> and<00:21:03.360> so<00:21:04.280> there<00:21:04.480> is<00:21:04.880> nothing<00:21:05.679> that 00:21:06.110 --> 00:21:06.120 align:start position:0% of web 3 um and so there is nothing that 00:21:06.120 --> 00:21:09.669 align:start position:0% of web 3 um and so there is nothing that prevents<00:21:07.120> the<00:21:07.360> a<00:21:07.640> layer<00:21:08.280> from<00:21:09.120> um<00:21:09.440> being 00:21:09.669 --> 00:21:09.679 align:start position:0% prevents the a layer from um being 00:21:09.679 --> 00:21:12.430 align:start position:0% prevents the a layer from um being connected<00:21:10.240> to<00:21:10.559> a<00:21:10.679> chain<00:21:10.919> in<00:21:11.039> the<00:21:11.120> super<00:21:11.440> chain 00:21:12.430 --> 00:21:12.440 align:start position:0% connected to a chain in the super chain 00:21:12.440 --> 00:21:14.350 align:start position:0% connected to a chain in the super chain um<00:21:12.760> you<00:21:12.880> will<00:21:13.120> actually<00:21:13.360> see<00:21:13.600> that<00:21:13.799> happen 00:21:14.350 --> 00:21:14.360 align:start position:0% um you will actually see that happen 00:21:14.360 --> 00:21:16.549 align:start position:0% um you will actually see that happen there<00:21:14.559> is<00:21:14.760> nothing<00:21:15.039> that<00:21:15.240> prevents<00:21:15.840> the<00:21:16.000> agair 00:21:16.549 --> 00:21:16.559 align:start position:0% there is nothing that prevents the agair 00:21:16.559 --> 00:21:18.029 align:start position:0% there is nothing that prevents the agair from<00:21:16.760> being<00:21:16.960> connected<00:21:17.320> to<00:21:17.440> a<00:21:17.559> chain<00:21:17.799> on<00:21:17.919> the 00:21:18.029 --> 00:21:18.039 align:start position:0% from being connected to a chain on the 00:21:18.039 --> 00:21:19.909 align:start position:0% from being connected to a chain on the elastic<00:21:18.440> chain<00:21:19.240> there<00:21:19.360> is<00:21:19.520> nothing<00:21:19.760> that 00:21:19.909 --> 00:21:19.919 align:start position:0% elastic chain there is nothing that 00:21:19.919 --> 00:21:21.789 align:start position:0% elastic chain there is nothing that prevents<00:21:20.240> it<00:21:20.480> from<00:21:20.760> connecting<00:21:21.159> to<00:21:21.440> a<00:21:21.640> an 00:21:21.789 --> 00:21:21.799 align:start position:0% prevents it from connecting to a an 00:21:21.799 --> 00:21:25.269 align:start position:0% prevents it from connecting to a an orbit<00:21:22.120> chain<00:21:22.840> and<00:21:23.039> so<00:21:23.840> um<00:21:24.679> given<00:21:24.919> that<00:21:25.039> it's<00:21:25.159> a 00:21:25.269 --> 00:21:25.279 align:start position:0% orbit chain and so um given that it's a 00:21:25.279 --> 00:21:27.590 align:start position:0% orbit chain and so um given that it's a low-level<00:21:25.880> solution<00:21:26.440> you<00:21:26.559> can<00:21:26.760> call<00:21:26.960> it<00:21:27.279> the 00:21:27.590 --> 00:21:27.600 align:start position:0% low-level solution you can call it the 00:21:27.600 --> 00:21:30.990 align:start position:0% low-level solution you can call it the aggregator<00:21:28.279> of<00:21:28.960> aggregators<00:21:29.960> um<00:21:30.400> and<00:21:30.600> so 00:21:30.990 --> 00:21:31.000 align:start position:0% aggregator of aggregators um and so 00:21:31.000 --> 00:21:33.870 align:start position:0% aggregator of aggregators um and so that's<00:21:31.400> what<00:21:31.559> the<00:21:31.679> AG<00:21:32.440> provides<00:21:33.440> all<00:21:33.640> right 00:21:33.870 --> 00:21:33.880 align:start position:0% that's what the AG provides all right 00:21:33.880 --> 00:21:36.710 align:start position:0% that's what the AG provides all right and<00:21:34.080> what<00:21:34.200> is<00:21:34.360> the<00:21:34.559> difference<00:21:35.279> with 00:21:36.710 --> 00:21:36.720 align:start position:0% and what is the difference with 00:21:36.720 --> 00:21:39.669 align:start position:0% and what is the difference with ccip<00:21:37.720> yeah<00:21:38.159> uh<00:21:38.279> that's<00:21:38.400> a<00:21:38.559> good<00:21:38.799> question<00:21:39.120> so<00:21:39.600> I 00:21:39.669 --> 00:21:39.679 align:start position:0% ccip yeah uh that's a good question so I 00:21:39.679 --> 00:21:41.430 align:start position:0% ccip yeah uh that's a good question so I would<00:21:39.880> think<00:21:40.039> of<00:21:40.159> ccip<00:21:40.919> more<00:21:41.159> on<00:21:41.279> the 00:21:41.430 --> 00:21:41.440 align:start position:0% would think of ccip more on the 00:21:41.440 --> 00:21:42.909 align:start position:0% would think of ccip more on the messaging<00:21:41.960> side<00:21:42.120> of<00:21:42.240> things<00:21:42.520> than<00:21:42.640> on<00:21:42.760> the 00:21:42.909 --> 00:21:42.919 align:start position:0% messaging side of things than on the 00:21:42.919 --> 00:21:45.710 align:start position:0% messaging side of things than on the asset<00:21:43.240> transfer<00:21:43.679> side<00:21:43.840> of<00:21:44.000> things<00:21:44.840> um<00:21:45.120> and<00:21:45.279> so 00:21:45.710 --> 00:21:45.720 align:start position:0% asset transfer side of things um and so 00:21:45.720 --> 00:21:47.909 align:start position:0% asset transfer side of things um and so specifically<00:21:46.440> like<00:21:46.600> when<00:21:46.760> you<00:21:47.159> think<00:21:47.440> about 00:21:47.909 --> 00:21:47.919 align:start position:0% specifically like when you think about 00:21:47.919 --> 00:21:50.630 align:start position:0% specifically like when you think about the<00:21:48.279> the<00:21:48.480> bridges<00:21:48.960> that<00:21:49.080> I<00:21:49.200> was<00:21:49.400> referring<00:21:49.799> to 00:21:50.630 --> 00:21:50.640 align:start position:0% the the bridges that I was referring to 00:21:50.640 --> 00:21:53.510 align:start position:0% the the bridges that I was referring to um<00:21:51.200> that's<00:21:51.520> kind<00:21:51.679> of<00:21:52.080> what<00:21:52.320> currently<00:21:52.840> exists 00:21:53.510 --> 00:21:53.520 align:start position:0% um that's kind of what currently exists 00:21:53.520 --> 00:21:55.789 align:start position:0% um that's kind of what currently exists is<00:21:53.760> is<00:21:54.000> ccip<00:21:55.000> one<00:21:55.080> of<00:21:55.200> the<00:21:55.320> things<00:21:55.520> that<00:21:55.600> we're 00:21:55.789 --> 00:21:55.799 align:start position:0% is is ccip one of the things that we're 00:21:55.799 --> 00:21:57.870 align:start position:0% is is ccip one of the things that we're actually<00:21:56.080> working<00:21:56.360> on<00:21:56.600> right<00:21:56.760> now<00:21:57.039> on<00:21:57.120> the<00:21:57.279> AG 00:21:57.870 --> 00:21:57.880 align:start position:0% actually working on right now on the AG 00:21:57.880 --> 00:22:00.110 align:start position:0% actually working on right now on the AG is<00:21:58.039> trying<00:21:58.320> to<00:21:58.720> bring<00:21:59.039> kind<00:21:59.200> of<00:21:59.520> bridge 00:22:00.110 --> 00:22:00.120 align:start position:0% is trying to bring kind of bridge 00:22:00.120 --> 00:22:02.630 align:start position:0% is trying to bring kind of bridge standards<00:22:01.120> within<00:22:01.400> the<00:22:01.520> Ager<00:22:02.360> there's 00:22:02.630 --> 00:22:02.640 align:start position:0% standards within the Ager there's 00:22:02.640 --> 00:22:05.190 align:start position:0% standards within the Ager there's actually<00:22:03.159> nothing<00:22:03.679> that<00:22:03.960> prevents<00:22:04.440> the<00:22:04.559> Ager 00:22:05.190 --> 00:22:05.200 align:start position:0% actually nothing that prevents the Ager 00:22:05.200 --> 00:22:06.909 align:start position:0% actually nothing that prevents the Ager from<00:22:05.400> using<00:22:05.880> some<00:22:06.039> of<00:22:06.159> the<00:22:06.240> bridge<00:22:06.559> standards 00:22:06.909 --> 00:22:06.919 align:start position:0% from using some of the bridge standards 00:22:06.919 --> 00:22:09.350 align:start position:0% from using some of the bridge standards that<00:22:07.039> we<00:22:07.159> currently<00:22:07.559> see<00:22:08.400> um<00:22:08.600> and<00:22:08.840> adding<00:22:09.159> to 00:22:09.350 --> 00:22:09.360 align:start position:0% that we currently see um and adding to 00:22:09.360 --> 00:22:11.710 align:start position:0% that we currently see um and adding to it<00:22:09.559> a<00:22:09.720> level<00:22:09.960> of<00:22:10.240> security<00:22:10.880> that<00:22:11.039> currently 00:22:11.710 --> 00:22:11.720 align:start position:0% it a level of security that currently 00:22:11.720 --> 00:22:13.789 align:start position:0% it a level of security that currently doesn't<00:22:12.120> actually<00:22:12.480> exist<00:22:13.320> uh<00:22:13.440> and<00:22:13.520> so<00:22:13.679> the 00:22:13.789 --> 00:22:13.799 align:start position:0% doesn't actually exist uh and so the 00:22:13.799 --> 00:22:15.830 align:start position:0% doesn't actually exist uh and so the goal<00:22:14.039> is<00:22:14.200> actually<00:22:14.400> to<00:22:14.640> work<00:22:15.159> with<00:22:15.720> um 00:22:15.830 --> 00:22:15.840 align:start position:0% goal is actually to work with um 00:22:15.840 --> 00:22:19.110 align:start position:0% goal is actually to work with um something<00:22:16.120> like<00:22:16.360> ccip<00:22:17.360> rather<00:22:17.679> than<00:22:18.480> um 00:22:19.110 --> 00:22:19.120 align:start position:0% something like ccip rather than um 00:22:19.120 --> 00:22:20.430 align:start position:0% something like ccip rather than um compete<00:22:19.480> with 00:22:20.430 --> 00:22:20.440 align:start position:0% compete with 00:22:20.440 --> 00:22:24.269 align:start position:0% compete with it<00:22:21.440> all<00:22:21.640> right<00:22:22.080> where<00:22:22.360> does<00:22:22.720> Ager<00:22:23.320> run<00:22:23.720> and<00:22:24.000> who 00:22:24.269 --> 00:22:24.279 align:start position:0% it all right where does Ager run and who 00:22:24.279 --> 00:22:26.470 align:start position:0% it all right where does Ager run and who are<00:22:24.520> the<00:22:24.720> actors<00:22:25.720> yeah<00:22:26.000> that's<00:22:26.120> a<00:22:26.279> good 00:22:26.470 --> 00:22:26.480 align:start position:0% are the actors yeah that's a good 00:22:26.480 --> 00:22:29.470 align:start position:0% are the actors yeah that's a good question<00:22:26.880> so<00:22:27.559> um<00:22:27.840> the<00:22:27.960> AG's<00:22:28.520> going<00:22:28.600> to<00:22:28.720> be<00:22:28.960> live 00:22:29.470 --> 00:22:29.480 align:start position:0% question so um the AG's going to be live 00:22:29.480 --> 00:22:32.909 align:start position:0% question so um the AG's going to be live in<00:22:30.000> 3<00:22:30.240> to<00:22:30.360> 4<00:22:30.640> weeks<00:22:31.640> and<00:22:32.159> in<00:22:32.279> its<00:22:32.520> current<00:22:32.799> in 00:22:32.909 --> 00:22:32.919 align:start position:0% in 3 to 4 weeks and in its current in 00:22:32.919 --> 00:22:34.870 align:start position:0% in 3 to 4 weeks and in its current in its<00:22:33.279> its<00:22:33.520> initial<00:22:33.840> form<00:22:34.240> it's<00:22:34.400> run<00:22:34.600> in<00:22:34.720> a 00:22:34.870 --> 00:22:34.880 align:start position:0% its its initial form it's run in a 00:22:34.880 --> 00:22:38.390 align:start position:0% its its initial form it's run in a centralized<00:22:35.480> way<00:22:36.279> um<00:22:37.000> the<00:22:37.159> nice<00:22:37.480> thing<00:22:37.760> though 00:22:38.390 --> 00:22:38.400 align:start position:0% centralized way um the nice thing though 00:22:38.400 --> 00:22:40.350 align:start position:0% centralized way um the nice thing though is<00:22:38.760> that<00:22:39.240> with<00:22:39.400> ZK 00:22:40.350 --> 00:22:40.360 align:start position:0% is that with ZK 00:22:40.360 --> 00:22:43.430 align:start position:0% is that with ZK technology<00:22:41.360> you<00:22:41.559> can<00:22:41.960> be<00:22:42.159> running<00:22:42.880> a 00:22:43.430 --> 00:22:43.440 align:start position:0% technology you can be running a 00:22:43.440 --> 00:22:46.710 align:start position:0% technology you can be running a centralized<00:22:44.120> system<00:22:44.840> in<00:22:44.960> a<00:22:45.120> trustless<00:22:45.720> manner 00:22:46.710 --> 00:22:46.720 align:start position:0% centralized system in a trustless manner 00:22:46.720 --> 00:22:48.789 align:start position:0% centralized system in a trustless manner and<00:22:47.120> that's<00:22:47.400> kind<00:22:47.520> of<00:22:47.720> what<00:22:47.919> the<00:22:48.200> agir<00:22:48.640> is 00:22:48.789 --> 00:22:48.799 align:start position:0% and that's kind of what the agir is 00:22:48.799 --> 00:22:51.230 align:start position:0% and that's kind of what the agir is going<00:22:48.919> to<00:22:49.120> look<00:22:49.360> like<00:22:49.600> in<00:22:49.760> its<00:22:50.039> initial<00:22:50.400> form 00:22:51.230 --> 00:22:51.240 align:start position:0% going to look like in its initial form 00:22:51.240 --> 00:22:54.070 align:start position:0% going to look like in its initial form but<00:22:52.159> I<00:22:52.480> fundamentally<00:22:53.039> believe<00:22:53.559> that<00:22:53.919> not 00:22:54.070 --> 00:22:54.080 align:start position:0% but I fundamentally believe that not 00:22:54.080 --> 00:22:55.669 align:start position:0% but I fundamentally believe that not withstanding<00:22:54.720> how<00:22:54.919> centralized<00:22:55.520> we're 00:22:55.669 --> 00:22:55.679 align:start position:0% withstanding how centralized we're 00:22:55.679 --> 00:22:57.990 align:start position:0% withstanding how centralized we're seeing<00:22:56.159> everything<00:22:56.480> in<00:22:56.559> the<00:22:56.720> space<00:22:57.039> right<00:22:57.200> now 00:22:57.990 --> 00:22:58.000 align:start position:0% seeing everything in the space right now 00:22:58.000 --> 00:22:59.750 align:start position:0% seeing everything in the space right now um<00:22:58.480> pretty<00:22:58.640> much<00:22:58.799> everything<00:22:59.039> is<00:22:59.200> going<00:22:59.360> to 00:22:59.750 --> 00:22:59.760 align:start position:0% um pretty much everything is going to 00:22:59.760 --> 00:23:02.190 align:start position:0% um pretty much everything is going to decentralize<00:23:00.760> and<00:23:01.320> this<00:23:01.440> is<00:23:01.600> either<00:23:01.840> going<00:23:01.960> to 00:23:02.190 --> 00:23:02.200 align:start position:0% decentralize and this is either going to 00:23:02.200 --> 00:23:05.230 align:start position:0% decentralize and this is either going to happen<00:23:02.720> because<00:23:03.400> it's<00:23:03.600> going<00:23:03.760> to<00:23:04.000> be<00:23:04.480> forced 00:23:05.230 --> 00:23:05.240 align:start position:0% happen because it's going to be forced 00:23:05.240 --> 00:23:08.710 align:start position:0% happen because it's going to be forced by<00:23:05.559> some<00:23:06.120> government<00:23:06.720> actors<00:23:07.200> in<00:23:07.400> some<00:23:07.679> way<00:23:08.480> um 00:23:08.710 --> 00:23:08.720 align:start position:0% by some government actors in some way um 00:23:08.720 --> 00:23:11.310 align:start position:0% by some government actors in some way um or<00:23:08.919> it's<00:23:09.120> going<00:23:09.279> to<00:23:09.520> happen<00:23:09.960> because<00:23:10.919> critical 00:23:11.310 --> 00:23:11.320 align:start position:0% or it's going to happen because critical 00:23:11.320 --> 00:23:12.350 align:start position:0% or it's going to happen because critical issues<00:23:11.559> are<00:23:11.720> going<00:23:11.840> to<00:23:12.000> happen<00:23:12.200> in 00:23:12.350 --> 00:23:12.360 align:start position:0% issues are going to happen in 00:23:12.360 --> 00:23:13.590 align:start position:0% issues are going to happen in centralized<00:23:12.840> systems<00:23:13.159> and<00:23:13.279> we're<00:23:13.400> all<00:23:13.520> going 00:23:13.590 --> 00:23:13.600 align:start position:0% centralized systems and we're all going 00:23:13.600 --> 00:23:15.029 align:start position:0% centralized systems and we're all going to<00:23:13.720> be<00:23:13.880> reminded<00:23:14.360> why<00:23:14.520> it<00:23:14.640> is<00:23:14.799> that<00:23:14.919> we 00:23:15.029 --> 00:23:15.039 align:start position:0% to be reminded why it is that we 00:23:15.039 --> 00:23:17.470 align:start position:0% to be reminded why it is that we actually<00:23:15.240> have<00:23:15.400> decentralized<00:23:16.159> systems<00:23:17.159> um 00:23:17.470 --> 00:23:17.480 align:start position:0% actually have decentralized systems um 00:23:17.480 --> 00:23:20.110 align:start position:0% actually have decentralized systems um and<00:23:17.640> so<00:23:18.120> our<00:23:18.400> goal<00:23:19.000> and<00:23:19.159> it's<00:23:19.279> on<00:23:19.400> the<00:23:19.520> road<00:23:19.760> map 00:23:20.110 --> 00:23:20.120 align:start position:0% and so our goal and it's on the road map 00:23:20.120 --> 00:23:21.149 align:start position:0% and so our goal and it's on the road map and<00:23:20.279> it's<00:23:20.480> actually<00:23:20.640> a<00:23:20.720> lot<00:23:20.799> of<00:23:20.919> work<00:23:21.039> is 00:23:21.149 --> 00:23:21.159 align:start position:0% and it's actually a lot of work is 00:23:21.159 --> 00:23:23.029 align:start position:0% and it's actually a lot of work is already<00:23:21.400> being<00:23:21.600> done<00:23:22.080> is<00:23:22.200> to<00:23:22.480> decentralize 00:23:23.029 --> 00:23:23.039 align:start position:0% already being done is to decentralize 00:23:23.039 --> 00:23:24.510 align:start position:0% already being done is to decentralize the<00:23:23.159> agal<00:23:23.600> and<00:23:23.760> not<00:23:23.960> keep<00:23:24.120> it<00:23:24.240> in<00:23:24.360> a 00:23:24.510 --> 00:23:24.520 align:start position:0% the agal and not keep it in a 00:23:24.520 --> 00:23:26.710 align:start position:0% the agal and not keep it in a centralized 00:23:26.710 --> 00:23:26.720 align:start position:0% centralized 00:23:26.720 --> 00:23:29.149 align:start position:0% centralized form<00:23:27.720> all<00:23:28.000> right 00:23:29.149 --> 00:23:29.159 align:start position:0% form all right 00:23:29.159 --> 00:23:31.110 align:start position:0% form all right uh<00:23:29.440> is<00:23:29.559> there<00:23:29.840> any<00:23:30.080> hope<00:23:30.360> of<00:23:30.559> optimistic 00:23:31.110 --> 00:23:31.120 align:start position:0% uh is there any hope of optimistic 00:23:31.120 --> 00:23:33.669 align:start position:0% uh is there any hope of optimistic networks<00:23:31.600> to<00:23:31.760> get<00:23:31.960> aggregated<00:23:32.440> into<00:23:32.679> the<00:23:32.799> Ager 00:23:33.669 --> 00:23:33.679 align:start position:0% networks to get aggregated into the Ager 00:23:33.679 --> 00:23:35.549 align:start position:0% networks to get aggregated into the Ager their<00:23:33.919> optimistic<00:23:34.440> nature<00:23:34.880> that<00:23:35.000> is<00:23:35.240> waiting 00:23:35.549 --> 00:23:35.559 align:start position:0% their optimistic nature that is waiting 00:23:35.559 --> 00:23:37.789 align:start position:0% their optimistic nature that is waiting periods<00:23:35.960> Etc<00:23:36.480> seems<00:23:36.720> to<00:23:36.880> be<00:23:37.080> fundamentally 00:23:37.789 --> 00:23:37.799 align:start position:0% periods Etc seems to be fundamentally 00:23:37.799 --> 00:23:39.909 align:start position:0% periods Etc seems to be fundamentally incompatible<00:23:38.640> with<00:23:38.840> composability 00:23:39.909 --> 00:23:39.919 align:start position:0% incompatible with composability 00:23:39.919 --> 00:23:41.950 align:start position:0% incompatible with composability yes<00:23:40.919> uh<00:23:41.080> this<00:23:41.159> is<00:23:41.240> a<00:23:41.400> good<00:23:41.559> question<00:23:41.840> and 00:23:41.950 --> 00:23:41.960 align:start position:0% yes uh this is a good question and 00:23:41.960 --> 00:23:43.390 align:start position:0% yes uh this is a good question and something<00:23:42.200> we<00:23:42.360> spent<00:23:42.559> a<00:23:42.679> lot<00:23:42.799> of<00:23:42.880> time<00:23:43.080> about 00:23:43.390 --> 00:23:43.400 align:start position:0% something we spent a lot of time about 00:23:43.400 --> 00:23:45.909 align:start position:0% something we spent a lot of time about so<00:23:43.559> I<00:23:43.640> got<00:23:43.799> two<00:23:44.000> answers<00:23:44.279> for<00:23:44.480> you<00:23:44.640> on<00:23:44.840> that<00:23:45.600> um 00:23:45.909 --> 00:23:45.919 align:start position:0% so I got two answers for you on that um 00:23:45.919 --> 00:23:47.350 align:start position:0% so I got two answers for you on that um answer<00:23:46.159> number<00:23:46.360> one<00:23:46.559> is<00:23:46.720> all<00:23:46.919> optimistic 00:23:47.350 --> 00:23:47.360 align:start position:0% answer number one is all optimistic 00:23:47.360 --> 00:23:49.350 align:start position:0% answer number one is all optimistic Roll-Ups<00:23:47.720> will<00:23:47.840> be<00:23:47.919> ZK<00:23:48.279> rollups<00:23:48.960> it's<00:23:49.120> just<00:23:49.240> a 00:23:49.350 --> 00:23:49.360 align:start position:0% Roll-Ups will be ZK rollups it's just a 00:23:49.360 --> 00:23:52.190 align:start position:0% Roll-Ups will be ZK rollups it's just a matter<00:23:49.559> of<00:23:49.760> time<00:23:50.120> everybody<00:23:50.520> knows<00:23:50.760> it<00:23:51.480> um<00:23:51.880> all 00:23:52.190 --> 00:23:52.200 align:start position:0% matter of time everybody knows it um all 00:23:52.200 --> 00:23:53.750 align:start position:0% matter of time everybody knows it um all optimistic<00:23:52.720> rups<00:23:53.039> are<00:23:53.159> working<00:23:53.400> on<00:23:53.559> that 00:23:53.750 --> 00:23:53.760 align:start position:0% optimistic rups are working on that 00:23:53.760 --> 00:23:56.029 align:start position:0% optimistic rups are working on that already<00:23:54.159> it's<00:23:54.320> just<00:23:54.440> a<00:23:54.640> question<00:23:54.880> of<00:23:55.080> time<00:23:55.799> um 00:23:56.029 --> 00:23:56.039 align:start position:0% already it's just a question of time um 00:23:56.039 --> 00:23:58.909 align:start position:0% already it's just a question of time um and<00:23:56.200> that<00:23:56.320> frankly<00:23:56.720> is<00:23:56.960> what<00:23:57.440> will<00:23:57.880> create<00:23:58.240> the 00:23:58.909 --> 00:23:58.919 align:start position:0% and that frankly is what will create the 00:23:58.919 --> 00:24:00.350 align:start position:0% and that frankly is what will create the ideal<00:23:59.440> user 00:24:00.350 --> 00:24:00.360 align:start position:0% ideal user 00:24:00.360 --> 00:24:02.789 align:start position:0% ideal user experience<00:24:01.360> um<00:24:01.640> another<00:24:01.960> alternative<00:24:02.640> would 00:24:02.789 --> 00:24:02.799 align:start position:0% experience um another alternative would 00:24:02.799 --> 00:24:06.390 align:start position:0% experience um another alternative would be<00:24:03.240> to<00:24:03.520> actually<00:24:03.919> just<00:24:04.480> just<00:24:04.880> uh<00:24:05.520> uh<00:24:05.720> prove<00:24:06.240> the 00:24:06.390 --> 00:24:06.400 align:start position:0% be to actually just just uh uh prove the 00:24:06.400 --> 00:24:08.510 align:start position:0% be to actually just just uh uh prove the fraud<00:24:06.760> proof<00:24:07.480> okay<00:24:07.679> that's<00:24:08.080> the<00:24:08.240> exact 00:24:08.510 --> 00:24:08.520 align:start position:0% fraud proof okay that's the exact 00:24:08.520 --> 00:24:09.789 align:start position:0% fraud proof okay that's the exact question<00:24:08.799> like<00:24:08.919> you<00:24:09.039> can't<00:24:09.240> wait<00:24:09.400> seven<00:24:09.640> days 00:24:09.789 --> 00:24:09.799 align:start position:0% question like you can't wait seven days 00:24:09.799 --> 00:24:11.710 align:start position:0% question like you can't wait seven days to<00:24:09.880> go<00:24:10.039> across<00:24:10.320> train<00:24:10.559> that's<00:24:10.720> horrible<00:24:11.520> um 00:24:11.710 --> 00:24:11.720 align:start position:0% to go across train that's horrible um 00:24:11.720 --> 00:24:13.710 align:start position:0% to go across train that's horrible um but<00:24:11.880> what<00:24:11.960> I<00:24:12.080> was<00:24:12.240> also<00:24:12.480> saying<00:24:12.840> is<00:24:13.080> that<00:24:13.480> we 00:24:13.710 --> 00:24:13.720 align:start position:0% but what I was also saying is that we 00:24:13.720 --> 00:24:16.269 align:start position:0% but what I was also saying is that we don't<00:24:14.000> just<00:24:14.200> need<00:24:14.520> to<00:24:15.039> prove<00:24:15.480> proofs<00:24:16.000> we<00:24:16.080> can 00:24:16.269 --> 00:24:16.279 align:start position:0% don't just need to prove proofs we can 00:24:16.279 --> 00:24:19.430 align:start position:0% don't just need to prove proofs we can prove<00:24:16.559> other<00:24:16.799> things<00:24:17.600> for<00:24:17.919> example<00:24:18.919> um<00:24:19.320> you 00:24:19.430 --> 00:24:19.440 align:start position:0% prove other things for example um you 00:24:19.440 --> 00:24:21.830 align:start position:0% prove other things for example um you know<00:24:19.799> the<00:24:20.240> the<00:24:20.400> centralized<00:24:20.960> sequencers<00:24:21.720> that 00:24:21.830 --> 00:24:21.840 align:start position:0% know the the centralized sequencers that 00:24:21.840 --> 00:24:24.950 align:start position:0% know the the centralized sequencers that we<00:24:21.960> have<00:24:22.240> right<00:24:22.480> now<00:24:22.760> do<00:24:23.080> reach<00:24:23.720> consensus<00:24:24.720> uh 00:24:24.950 --> 00:24:24.960 align:start position:0% we have right now do reach consensus uh 00:24:24.960 --> 00:24:27.430 align:start position:0% we have right now do reach consensus uh in<00:24:25.200> in<00:24:25.320> a<00:24:25.520> centralized<00:24:26.200> way<00:24:26.840> and<00:24:27.039> you<00:24:27.200> can 00:24:27.430 --> 00:24:27.440 align:start position:0% in in a centralized way and you can 00:24:27.440 --> 00:24:30.909 align:start position:0% in in a centralized way and you can actually<00:24:27.919> prove<00:24:28.240> that<00:24:28.520> consensus<00:24:29.520> using<00:24:30.159> the 00:24:30.909 --> 00:24:30.919 align:start position:0% actually prove that consensus using the 00:24:30.919 --> 00:24:32.870 align:start position:0% actually prove that consensus using the uh<00:24:31.080> pessimistic<00:24:31.640> proof<00:24:32.399> that's<00:24:32.559> why<00:24:32.679> I<00:24:32.760> was 00:24:32.870 --> 00:24:32.880 align:start position:0% uh pessimistic proof that's why I was 00:24:32.880 --> 00:24:35.310 align:start position:0% uh pessimistic proof that's why I was saying<00:24:33.200> that<00:24:33.399> even<00:24:34.039> in<00:24:34.200> this<00:24:34.360> current<00:24:34.760> state 00:24:35.310 --> 00:24:35.320 align:start position:0% saying that even in this current state 00:24:35.320 --> 00:24:37.870 align:start position:0% saying that even in this current state where<00:24:35.480> you've<00:24:35.679> got<00:24:35.840> fraud<00:24:36.159> proofs<00:24:36.720> on<00:24:36.960> chains 00:24:37.870 --> 00:24:37.880 align:start position:0% where you've got fraud proofs on chains 00:24:37.880 --> 00:24:40.789 align:start position:0% where you've got fraud proofs on chains that<00:24:38.000> we<00:24:38.159> will<00:24:38.399> still<00:24:38.840> see<00:24:39.159> them<00:24:39.559> on<00:24:39.679> the<00:24:39.840> agay 00:24:40.789 --> 00:24:40.799 align:start position:0% that we will still see them on the agay 00:24:40.799 --> 00:24:43.870 align:start position:0% that we will still see them on the agay because<00:24:41.080> we<00:24:41.200> can<00:24:41.440> protect<00:24:42.159> against<00:24:43.159> the<00:24:43.559> the 00:24:43.870 --> 00:24:43.880 align:start position:0% because we can protect against the the 00:24:43.880 --> 00:24:48.230 align:start position:0% because we can protect against the the the<00:24:44.720> risk<00:24:45.600> of<00:24:46.039> any<00:24:47.000> um<00:24:47.440> of<00:24:47.600> anything<00:24:47.919> happening 00:24:48.230 --> 00:24:48.240 align:start position:0% the risk of any um of anything happening 00:24:48.240 --> 00:24:50.070 align:start position:0% the risk of any um of anything happening within<00:24:48.440> the<00:24:48.520> fraud<00:24:48.840> proof<00:24:49.080> window<00:24:49.679> using<00:24:49.960> the 00:24:50.070 --> 00:24:50.080 align:start position:0% within the fraud proof window using the 00:24:50.080 --> 00:24:52.870 align:start position:0% within the fraud proof window using the pessimistic<00:24:50.600> proof<00:24:51.600> all<00:24:51.799> right<00:24:52.360> we<00:24:52.480> only<00:24:52.679> have 00:24:52.870 --> 00:24:52.880 align:start position:0% pessimistic proof all right we only have 00:24:52.880 --> 00:24:54.830 align:start position:0% pessimistic proof all right we only have time<00:24:53.039> for<00:24:53.240> one<00:24:53.399> more<00:24:53.679> question<00:24:54.159> is<00:24:54.320> my 00:24:54.830 --> 00:24:54.840 align:start position:0% time for one more question is my 00:24:54.840 --> 00:24:56.750 align:start position:0% time for one more question is my understanding<00:24:55.159> correct<00:24:55.679> that<00:24:55.880> existing<00:24:56.200> l2s 00:24:56.750 --> 00:24:56.760 align:start position:0% understanding correct that existing l2s 00:24:56.760 --> 00:24:58.669 align:start position:0% understanding correct that existing l2s need<00:24:56.880> to<00:24:57.080> migrate<00:24:57.520> over<00:24:57.840> all<00:24:58.039> their<00:24:58.440> AET 00:24:58.669 --> 00:24:58.679 align:start position:0% need to migrate over all their AET 00:24:58.679 --> 00:25:00.630 align:start position:0% need to migrate over all their AET strings<00:24:59.360> in<00:24:59.480> the<00:24:59.640> native<00:25:00.039> Bridges<00:25:00.360> to<00:25:00.520> the 00:25:00.630 --> 00:25:00.640 align:start position:0% strings in the native Bridges to the 00:25:00.640 --> 00:25:03.310 align:start position:0% strings in the native Bridges to the unified<00:25:01.159> Bridge<00:25:02.120> yeah<00:25:02.399> that<00:25:02.520> is<00:25:02.640> a<00:25:02.880> very<00:25:03.080> good 00:25:03.310 --> 00:25:03.320 align:start position:0% unified Bridge yeah that is a very good 00:25:03.320 --> 00:25:04.990 align:start position:0% unified Bridge yeah that is a very good question<00:25:04.120> um<00:25:04.279> it's<00:25:04.399> something<00:25:04.600> we<00:25:04.720> spend<00:25:04.919> a 00:25:04.990 --> 00:25:05.000 align:start position:0% question um it's something we spend a 00:25:05.000 --> 00:25:08.070 align:start position:0% question um it's something we spend a lot<00:25:05.120> of<00:25:05.240> time<00:25:05.399> on<00:25:05.679> so<00:25:06.120> I<00:25:06.200> would<00:25:06.480> say<00:25:06.720> there's<00:25:07.120> um 00:25:08.070 --> 00:25:08.080 align:start position:0% lot of time on so I would say there's um 00:25:08.080 --> 00:25:09.590 align:start position:0% lot of time on so I would say there's um there's<00:25:08.320> the<00:25:08.480> ideal<00:25:08.880> State<00:25:09.200> and<00:25:09.279> there's<00:25:09.440> the 00:25:09.590 --> 00:25:09.600 align:start position:0% there's the ideal State and there's the 00:25:09.600 --> 00:25:11.630 align:start position:0% there's the ideal State and there's the less<00:25:09.840> the<00:25:09.960> ideal<00:25:10.320> State<00:25:10.880> as<00:25:11.039> I've<00:25:11.200> mentioned<00:25:11.559> a 00:25:11.630 --> 00:25:11.640 align:start position:0% less the ideal State as I've mentioned a 00:25:11.640 --> 00:25:14.389 align:start position:0% less the ideal State as I've mentioned a few<00:25:11.840> times<00:25:12.480> we<00:25:12.600> can<00:25:13.000> currently<00:25:13.440> connect<00:25:14.039> any 00:25:14.389 --> 00:25:14.399 align:start position:0% few times we can currently connect any 00:25:14.399 --> 00:25:15.830 align:start position:0% few times we can currently connect any existing<00:25:14.679> chain<00:25:14.919> and<00:25:15.039> you<00:25:15.120> will<00:25:15.240> see<00:25:15.520> existing 00:25:15.830 --> 00:25:15.840 align:start position:0% existing chain and you will see existing 00:25:15.840 --> 00:25:18.149 align:start position:0% existing chain and you will see existing chains<00:25:16.520> get<00:25:16.679> connected<00:25:17.159> without<00:25:17.480> migrating 00:25:18.149 --> 00:25:18.159 align:start position:0% chains get connected without migrating 00:25:18.159 --> 00:25:21.029 align:start position:0% chains get connected without migrating assets<00:25:18.679> over<00:25:19.039> to<00:25:19.360> the<00:25:19.520> Ager<00:25:20.480> um<00:25:20.640> and<00:25:20.760> what<00:25:20.840> will 00:25:21.029 --> 00:25:21.039 align:start position:0% assets over to the Ager um and what will 00:25:21.039 --> 00:25:22.990 align:start position:0% assets over to the Ager um and what will happen<00:25:21.279> when<00:25:21.440> that<00:25:21.600> happens<00:25:21.960> is<00:25:22.399> basically 00:25:22.990 --> 00:25:23.000 align:start position:0% happen when that happens is basically 00:25:23.000 --> 00:25:25.710 align:start position:0% happen when that happens is basically you'll<00:25:23.240> start<00:25:23.559> issuing<00:25:24.039> new<00:25:24.360> assets<00:25:24.960> on<00:25:25.279> that 00:25:25.710 --> 00:25:25.720 align:start position:0% you'll start issuing new assets on that 00:25:25.720 --> 00:25:27.470 align:start position:0% you'll start issuing new assets on that canonical<00:25:26.360> that<00:25:26.480> new<00:25:26.679> canonical<00:25:27.159> Bridge 00:25:27.470 --> 00:25:27.480 align:start position:0% canonical that new canonical Bridge 00:25:27.480 --> 00:25:30.190 align:start position:0% canonical that new canonical Bridge being<00:25:27.640> the<00:25:27.760> AG<00:25:28.159> brid<00:25:28.320> bridge<00:25:29.320> for<00:25:29.520> any<00:25:29.679> chains 00:25:30.190 --> 00:25:30.200 align:start position:0% being the AG brid bridge for any chains 00:25:30.200 --> 00:25:32.389 align:start position:0% being the AG brid bridge for any chains that<00:25:30.360> want<00:25:30.720> the<00:25:31.039> what<00:25:31.159> I'll<00:25:31.360> call<00:25:31.640> Ideal<00:25:32.039> user 00:25:32.389 --> 00:25:32.399 align:start position:0% that want the what I'll call Ideal user 00:25:32.399 --> 00:25:34.190 align:start position:0% that want the what I'll call Ideal user experience<00:25:33.200> you<00:25:33.320> would<00:25:33.559> actually<00:25:33.799> want<00:25:34.000> to 00:25:34.190 --> 00:25:34.200 align:start position:0% experience you would actually want to 00:25:34.200 --> 00:25:36.590 align:start position:0% experience you would actually want to have<00:25:34.399> them<00:25:34.640> migrate<00:25:35.200> all<00:25:35.360> the<00:25:35.559> assets<00:25:35.919> over 00:25:36.590 --> 00:25:36.600 align:start position:0% have them migrate all the assets over 00:25:36.600 --> 00:25:39.070 align:start position:0% have them migrate all the assets over this<00:25:36.760> is<00:25:37.200> actually<00:25:37.679> something<00:25:38.240> that<00:25:38.679> um<00:25:38.919> you 00:25:39.070 --> 00:25:39.080 align:start position:0% this is actually something that um you 00:25:39.080 --> 00:25:42.630 align:start position:0% this is actually something that um you will<00:25:39.320> see<00:25:39.799> happening<00:25:40.399> with<00:25:40.679> polygon<00:25:41.240> POS<00:25:42.240> um 00:25:42.630 --> 00:25:42.640 align:start position:0% will see happening with polygon POS um 00:25:42.640 --> 00:25:44.950 align:start position:0% will see happening with polygon POS um we<00:25:42.880> have 00:25:44.950 --> 00:25:44.960 align:start position:0% we have 00:25:44.960 --> 00:25:48.510 align:start position:0% we have 6,500<00:25:45.960> or<00:25:46.120> so<00:25:46.440> assets<00:25:46.760> on<00:25:46.960> polygon<00:25:47.399> POS<00:25:48.399> they 00:25:48.510 --> 00:25:48.520 align:start position:0% 6,500 or so assets on polygon POS they 00:25:48.520 --> 00:25:50.789 align:start position:0% 6,500 or so assets on polygon POS they will<00:25:48.799> all<00:25:49.039> get<00:25:49.279> migrated<00:25:49.919> over<00:25:50.240> to<00:25:50.640> the 00:25:50.789 --> 00:25:50.799 align:start position:0% will all get migrated over to the 00:25:50.799 --> 00:25:53.110 align:start position:0% will all get migrated over to the unified<00:25:51.279> bridge<00:25:51.960> and<00:25:52.120> there<00:25:52.720> we're<00:25:52.880> going<00:25:53.000> to 00:25:53.110 --> 00:25:53.120 align:start position:0% unified bridge and there we're going to 00:25:53.120 --> 00:25:56.269 align:start position:0% unified bridge and there we're going to be<00:25:53.320> the<00:25:53.480> first<00:25:53.840> example<00:25:54.559> of<00:25:55.520> probably<00:25:56.080> one<00:25:56.159> of 00:25:56.269 --> 00:25:56.279 align:start position:0% be the first example of probably one of 00:25:56.279 --> 00:25:57.789 align:start position:0% be the first example of probably one of the<00:25:56.399> biggest<00:25:56.679> chains<00:25:57.440> definitely<00:25:57.720> the 00:25:57.789 --> 00:25:57.799 align:start position:0% the biggest chains definitely the 00:25:57.799 --> 00:25:59.389 align:start position:0% the biggest chains definitely the biggest<00:25:58.000> chains<00:25:58.360> the<00:25:58.480> world<00:25:58.760> from<00:25:58.880> an<00:25:59.039> assets 00:25:59.389 --> 00:25:59.399 align:start position:0% biggest chains the world from an assets 00:25:59.399 --> 00:26:01.230 align:start position:0% biggest chains the world from an assets perspective<00:26:00.080> actually<00:26:00.399> migrating<00:26:00.919> all<00:26:01.039> of 00:26:01.230 --> 00:26:01.240 align:start position:0% perspective actually migrating all of 00:26:01.240 --> 00:26:02.350 align:start position:0% perspective actually migrating all of those<00:26:01.480> assets 00:26:02.350 --> 00:26:02.360 align:start position:0% those assets 00:26:02.360 --> 00:26:04.909 align:start position:0% those assets over<00:26:03.360> all<00:26:03.559> right<00:26:03.880> thank<00:26:04.039> you<00:26:04.240> again<00:26:04.480> so<00:26:04.640> much 00:26:04.909 --> 00:26:04.919 align:start position:0% over all right thank you again so much 00:26:04.919 --> 00:26:06.870 align:start position:0% over all right thank you again so much can<00:26:05.039> we<00:26:05.159> get<00:26:05.279> a<00:26:05.440> round<00:26:05.640> of<00:26:05.840> applause<00:26:06.279> for<00:26:06.440> Mark 00:26:06.870 --> 00:26:06.880 align:start position:0% can we get a round of applause for Mark 00:26:06.880 --> 00:26:09.880 align:start position:0% can we get a round of applause for Mark please