WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.150 align:start position:0% [Music] 00:00:09.150 --> 00:00:09.160 align:start position:0% [Music] 00:00:09.160 --> 00:00:11.910 align:start position:0% [Music] um<00:00:09.519> so<00:00:10.240> my<00:00:10.480> talk<00:00:10.759> here<00:00:11.000> following<00:00:11.400> up<00:00:11.559> on<00:00:11.719> that 00:00:11.910 --> 00:00:11.920 align:start position:0% um so my talk here following up on that 00:00:11.920 --> 00:00:13.990 align:start position:0% um so my talk here following up on that panel<00:00:12.320> an<00:00:12.519> amazing<00:00:12.920> panel<00:00:13.360> and<00:00:13.480> let's<00:00:13.639> give<00:00:13.799> a 00:00:13.990 --> 00:00:14.000 align:start position:0% panel an amazing panel and let's give a 00:00:14.000 --> 00:00:18.390 align:start position:0% panel an amazing panel and let's give a thank<00:00:14.200> you<00:00:14.400> to<00:00:14.920> uh<00:00:15.320> to<00:00:15.640> vitalic<00:00:16.880> to<00:00:17.880> yeah<00:00:18.279> I 00:00:18.390 --> 00:00:18.400 align:start position:0% thank you to uh to vitalic to yeah I 00:00:18.400 --> 00:00:22.910 align:start position:0% thank you to uh to vitalic to yeah I think<00:00:18.600> vitalic<00:00:19.240> but<00:00:19.400> also<00:00:20.359> Ben<00:00:20.760> Jesse<00:00:21.600> step<00:00:22.600> um 00:00:22.910 --> 00:00:22.920 align:start position:0% think vitalic but also Ben Jesse step um 00:00:22.920 --> 00:00:25.029 align:start position:0% think vitalic but also Ben Jesse step um it<00:00:23.039> was<00:00:23.160> an<00:00:23.320> awesome<00:00:23.640> talk<00:00:24.240> so<00:00:24.640> uh<00:00:24.760> we're<00:00:24.920> going 00:00:25.029 --> 00:00:25.039 align:start position:0% it was an awesome talk so uh we're going 00:00:25.039 --> 00:00:27.310 align:start position:0% it was an awesome talk so uh we're going to<00:00:25.199> talk<00:00:25.720> continue<00:00:26.279> the<00:00:26.439> conversation<00:00:27.039> about 00:00:27.310 --> 00:00:27.320 align:start position:0% to talk continue the conversation about 00:00:27.320 --> 00:00:30.150 align:start position:0% to talk continue the conversation about how<00:00:27.480> we<00:00:27.640> unify<00:00:28.199> ethereum<00:00:29.199> uh<00:00:29.320> with<00:00:29.480> intent<00:00:30.039> an 00:00:30.150 --> 00:00:30.160 align:start position:0% how we unify ethereum uh with intent an 00:00:30.160 --> 00:00:31.229 align:start position:0% how we unify ethereum uh with intent an ERC 00:00:31.229 --> 00:00:31.239 align:start position:0% ERC 00:00:31.239 --> 00:00:34.830 align:start position:0% ERC 7683<00:00:32.239> um<00:00:32.520> and<00:00:32.680> so<00:00:32.960> I'm<00:00:33.160> Hart<00:00:33.920> I<00:00:34.040> am<00:00:34.239> the<00:00:34.640> uh 00:00:34.830 --> 00:00:34.840 align:start position:0% 7683 um and so I'm Hart I am the uh 00:00:34.840 --> 00:00:37.270 align:start position:0% 7683 um and so I'm Hart I am the uh co-founder<00:00:35.320> of<00:00:35.399> a<00:00:35.600> cross<00:00:35.920> protocol<00:00:36.920> uh<00:00:37.040> we<00:00:37.160> are 00:00:37.270 --> 00:00:37.280 align:start position:0% co-founder of a cross protocol uh we are 00:00:37.280 --> 00:00:39.350 align:start position:0% co-founder of a cross protocol uh we are an<00:00:37.480> intent<00:00:38.040> based<00:00:38.360> interoperability<00:00:39.239> and 00:00:39.350 --> 00:00:39.360 align:start position:0% an intent based interoperability and 00:00:39.360 --> 00:00:41.470 align:start position:0% an intent based interoperability and bridging<00:00:39.800> protocol<00:00:40.800> um<00:00:40.960> but<00:00:41.079> we're<00:00:41.239> going<00:00:41.320> to 00:00:41.470 --> 00:00:41.480 align:start position:0% bridging protocol um but we're going to 00:00:41.480 --> 00:00:42.910 align:start position:0% bridging protocol um but we're going to talk<00:00:41.640> about<00:00:41.800> the<00:00:42.000> standard<00:00:42.440> and<00:00:42.680> how<00:00:42.800> we 00:00:42.910 --> 00:00:42.920 align:start position:0% talk about the standard and how we 00:00:42.920 --> 00:00:44.430 align:start position:0% talk about the standard and how we developed<00:00:43.320> it<00:00:43.440> and<00:00:43.600> how<00:00:43.680> we<00:00:43.840> built<00:00:44.120> support 00:00:44.430 --> 00:00:44.440 align:start position:0% developed it and how we built support 00:00:44.440 --> 00:00:46.189 align:start position:0% developed it and how we built support for<00:00:44.640> it<00:00:45.200> um<00:00:45.320> which<00:00:45.440> we<00:00:45.559> talked<00:00:45.800> about<00:00:45.960> on<00:00:46.079> that 00:00:46.189 --> 00:00:46.199 align:start position:0% for it um which we talked about on that 00:00:46.199 --> 00:00:47.430 align:start position:0% for it um which we talked about on that panel 00:00:47.430 --> 00:00:47.440 align:start position:0% panel 00:00:47.440 --> 00:00:50.830 align:start position:0% panel too<00:00:48.440> okay<00:00:49.039> so<00:00:49.520> I<00:00:49.640> stole<00:00:50.079> some<00:00:50.199> of<00:00:50.320> the<00:00:50.480> slides 00:00:50.830 --> 00:00:50.840 align:start position:0% too okay so I stole some of the slides 00:00:50.840 --> 00:00:53.189 align:start position:0% too okay so I stole some of the slides from<00:00:51.000> my<00:00:51.160> intro<00:00:51.640> to<00:00:51.800> the<00:00:51.960> panel<00:00:52.800> uh<00:00:52.960> because 00:00:53.189 --> 00:00:53.199 align:start position:0% from my intro to the panel uh because 00:00:53.199 --> 00:00:55.549 align:start position:0% from my intro to the panel uh because they<00:00:53.280> were<00:00:53.559> so<00:00:53.840> good<00:00:54.199> I<00:00:54.359> I<00:00:54.440> needed<00:00:54.680> to<00:00:54.840> use<00:00:55.079> them 00:00:55.549 --> 00:00:55.559 align:start position:0% they were so good I I needed to use them 00:00:55.559 --> 00:00:57.189 align:start position:0% they were so good I I needed to use them but<00:00:55.719> uh<00:00:55.840> I'm<00:00:55.920> going<00:00:56.039> to<00:00:56.160> replay<00:00:56.760> quickly<00:00:57.079> some 00:00:57.189 --> 00:00:57.199 align:start position:0% but uh I'm going to replay quickly some 00:00:57.199 --> 00:00:58.750 align:start position:0% but uh I'm going to replay quickly some of<00:00:57.280> the<00:00:57.399> slides<00:00:57.760> just<00:00:57.840> to<00:00:58.000> set<00:00:58.199> the<00:00:58.320> framework 00:00:58.750 --> 00:00:58.760 align:start position:0% of the slides just to set the framework 00:00:58.760 --> 00:01:00.470 align:start position:0% of the slides just to set the framework for<00:00:59.000> for<00:00:59.120> what<00:00:59.239> we're<00:00:59.359> talking<00:00:59.559> about<00:00:59.760> here<00:01:00.280> so 00:01:00.470 --> 00:01:00.480 align:start position:0% for for what we're talking about here so 00:01:00.480 --> 00:01:03.109 align:start position:0% for for what we're talking about here so four<00:01:00.719> years<00:01:00.960> ago<00:01:01.519> ethereum<00:01:01.960> had<00:01:02.079> the<00:01:02.199> scaling 00:01:03.109 --> 00:01:03.119 align:start position:0% four years ago ethereum had the scaling 00:01:03.119 --> 00:01:05.590 align:start position:0% four years ago ethereum had the scaling problem<00:01:04.119> uh<00:01:04.280> we<00:01:04.400> had<00:01:04.519> 15<00:01:04.839> transaction<00:01:05.360> per 00:01:05.590 --> 00:01:05.600 align:start position:0% problem uh we had 15 transaction per 00:01:05.600 --> 00:01:07.710 align:start position:0% problem uh we had 15 transaction per second<00:01:06.040> at<00:01:06.240> Peak<00:01:06.479> demand<00:01:06.840> ethereum<00:01:07.280> was<00:01:07.479> so 00:01:07.710 --> 00:01:07.720 align:start position:0% second at Peak demand ethereum was so 00:01:07.720 --> 00:01:10.270 align:start position:0% second at Peak demand ethereum was so expensive<00:01:08.240> was<00:01:08.439> basically<00:01:09.080> unusable<00:01:10.080> and 00:01:10.270 --> 00:01:10.280 align:start position:0% expensive was basically unusable and 00:01:10.280 --> 00:01:12.469 align:start position:0% expensive was basically unusable and vitalic<00:01:10.880> helped<00:01:11.159> us<00:01:11.600> align<00:01:11.960> the<00:01:12.080> ethereum 00:01:12.469 --> 00:01:12.479 align:start position:0% vitalic helped us align the ethereum 00:01:12.479 --> 00:01:14.109 align:start position:0% vitalic helped us align the ethereum community<00:01:12.840> around<00:01:13.040> this<00:01:13.159> Ro<00:01:13.360> of<00:01:13.479> centric<00:01:13.799> road 00:01:14.109 --> 00:01:14.119 align:start position:0% community around this Ro of centric road 00:01:14.119 --> 00:01:17.550 align:start position:0% community around this Ro of centric road map<00:01:15.119> and<00:01:15.280> this<00:01:15.520> worked<00:01:16.520> um<00:01:17.000> I<00:01:17.119> walk<00:01:17.360> through 00:01:17.550 --> 00:01:17.560 align:start position:0% map and this worked um I walk through 00:01:17.560 --> 00:01:19.469 align:start position:0% map and this worked um I walk through these<00:01:17.759> slides<00:01:18.520> uh<00:01:18.640> on<00:01:18.759> the<00:01:18.920> panel<00:01:19.200> we<00:01:19.280> were 00:01:19.469 --> 00:01:19.479 align:start position:0% these slides uh on the panel we were 00:01:19.479 --> 00:01:21.550 align:start position:0% these slides uh on the panel we were just<00:01:19.640> on<00:01:20.280> but<00:01:20.520> like<00:01:20.759> look<00:01:20.920> at<00:01:21.040> what<00:01:21.200> we<00:01:21.320> did 00:01:21.550 --> 00:01:21.560 align:start position:0% just on but like look at what we did 00:01:21.560 --> 00:01:23.710 align:start position:0% just on but like look at what we did here<00:01:21.920> right<00:01:22.079> in<00:01:22.240> October<00:01:22.640> 2020<00:01:23.200> we<00:01:23.320> aligned<00:01:23.640> on 00:01:23.710 --> 00:01:23.720 align:start position:0% here right in October 2020 we aligned on 00:01:23.720 --> 00:01:25.149 align:start position:0% here right in October 2020 we aligned on the<00:01:23.799> RO<00:01:24.000> of<00:01:24.079> centric<00:01:24.360> road 00:01:25.149 --> 00:01:25.159 align:start position:0% the RO of centric road 00:01:25.159 --> 00:01:27.789 align:start position:0% the RO of centric road map<00:01:26.159> uh<00:01:26.400> optimism<00:01:26.920> shipped<00:01:27.320> a<00:01:27.400> couple<00:01:27.600> months 00:01:27.789 --> 00:01:27.799 align:start position:0% map uh optimism shipped a couple months 00:01:27.799 --> 00:01:29.510 align:start position:0% map uh optimism shipped a couple months later<00:01:28.200> arbitrum<00:01:28.680> shipped<00:01:29.000> a<00:01:29.079> couple<00:01:29.280> months 00:01:29.510 --> 00:01:29.520 align:start position:0% later arbitrum shipped a couple months 00:01:29.520 --> 00:01:30.710 align:start position:0% later arbitrum shipped a couple months after<00:01:29.759> that 00:01:30.710 --> 00:01:30.720 align:start position:0% after that 00:01:30.720 --> 00:01:33.030 align:start position:0% after that ZK<00:01:31.200> sync<00:01:31.600> shipped<00:01:32.000> a<00:01:32.159> year<00:01:32.399> after<00:01:32.680> that<00:01:32.880> with 00:01:33.030 --> 00:01:33.040 align:start position:0% ZK sync shipped a year after that with 00:01:33.040 --> 00:01:35.990 align:start position:0% ZK sync shipped a year after that with ZK<00:01:33.520> rollups<00:01:34.520> uh<00:01:34.680> we<00:01:34.799> had<00:01:35.040> this<00:01:35.280> like<00:01:35.600> massive 00:01:35.990 --> 00:01:36.000 align:start position:0% ZK rollups uh we had this like massive 00:01:36.000 --> 00:01:38.630 align:start position:0% ZK rollups uh we had this like massive innovation<00:01:36.840> in<00:01:37.040> this<00:01:37.200> rollup<00:01:37.680> Centric 00:01:38.630 --> 00:01:38.640 align:start position:0% innovation in this rollup Centric 00:01:38.640 --> 00:01:40.630 align:start position:0% innovation in this rollup Centric architecture<00:01:39.640> and<00:01:39.759> then<00:01:39.880> of<00:01:40.040> course<00:01:40.240> blobs 00:01:40.630 --> 00:01:40.640 align:start position:0% architecture and then of course blobs 00:01:40.640 --> 00:01:43.389 align:start position:0% architecture and then of course blobs came<00:01:40.840> around<00:01:41.600> just<00:01:41.920> this<00:01:42.159> year<00:01:42.680> so<00:01:42.960> March<00:01:43.240> of 00:01:43.389 --> 00:01:43.399 align:start position:0% came around just this year so March of 00:01:43.399 --> 00:01:45.389 align:start position:0% came around just this year so March of this<00:01:43.600> year<00:01:44.280> and<00:01:44.520> I<00:01:44.600> don't<00:01:44.759> know<00:01:44.920> if<00:01:45.040> you<00:01:45.200> guys 00:01:45.389 --> 00:01:45.399 align:start position:0% this year and I don't know if you guys 00:01:45.399 --> 00:01:47.749 align:start position:0% this year and I don't know if you guys just<00:01:45.560> saw<00:01:46.079> the<00:01:46.240> charts<00:01:46.600> or<00:01:47.040> I<00:01:47.159> I<00:01:47.320> I<00:01:47.439> honestly 00:01:47.749 --> 00:01:47.759 align:start position:0% just saw the charts or I I I honestly 00:01:47.759 --> 00:01:48.990 align:start position:0% just saw the charts or I I I honestly should<00:01:47.920> have<00:01:48.040> included<00:01:48.399> another<00:01:48.600> chart<00:01:48.799> in 00:01:48.990 --> 00:01:49.000 align:start position:0% should have included another chart in 00:01:49.000 --> 00:01:51.190 align:start position:0% should have included another chart in here<00:01:49.719> uh<00:01:49.880> the<00:01:50.040> cost<00:01:50.280> of<00:01:50.479> transactions<00:01:51.040> on 00:01:51.190 --> 00:01:51.200 align:start position:0% here uh the cost of transactions on 00:01:51.200 --> 00:01:53.350 align:start position:0% here uh the cost of transactions on ethereum<00:01:51.640> just<00:01:51.759> plummeted<00:01:52.680> um<00:01:52.840> and<00:01:52.960> now<00:01:53.119> on<00:01:53.240> an 00:01:53.350 --> 00:01:53.360 align:start position:0% ethereum just plummeted um and now on an 00:01:53.360 --> 00:01:56.109 align:start position:0% ethereum just plummeted um and now on an L2<00:01:53.880> you<00:01:53.960> can<00:01:54.079> do<00:01:54.159> a<00:01:54.280> transaction<00:01:54.759> for<00:01:55.119> pennies 00:01:56.109 --> 00:01:56.119 align:start position:0% L2 you can do a transaction for pennies 00:01:56.119 --> 00:01:58.990 align:start position:0% L2 you can do a transaction for pennies um<00:01:56.399> we<00:01:56.600> actually<00:01:56.840> saw<00:01:57.159> this<00:01:57.320> in<00:01:57.439> across's<00:01:58.240> data 00:01:58.990 --> 00:01:59.000 align:start position:0% um we actually saw this in across's data 00:01:59.000 --> 00:02:01.270 align:start position:0% um we actually saw this in across's data the<00:01:59.240> median<00:01:59.920> transaction<00:02:00.479> size<00:02:00.759> dropped<00:02:01.119> from 00:02:01.270 --> 00:02:01.280 align:start position:0% the median transaction size dropped from 00:02:01.280 --> 00:02:03.630 align:start position:0% the median transaction size dropped from about<00:02:01.520> 500<00:02:01.960> bucks<00:02:02.280> going<00:02:02.520> L2<00:02:02.920> to<00:02:03.039> L2<00:02:03.520> when 00:02:03.630 --> 00:02:03.640 align:start position:0% about 500 bucks going L2 to L2 when 00:02:03.640 --> 00:02:06.350 align:start position:0% about 500 bucks going L2 to L2 when you're<00:02:03.840> bridging<00:02:04.520> it's<00:02:04.680> now<00:02:04.920> 50<00:02:05.280> bucks<00:02:06.079> and<00:02:06.200> we 00:02:06.350 --> 00:02:06.360 align:start position:0% you're bridging it's now 50 bucks and we 00:02:06.360 --> 00:02:09.389 align:start position:0% you're bridging it's now 50 bucks and we have<00:02:06.520> real<00:02:06.880> consumer<00:02:07.280> use<00:02:07.600> cases<00:02:08.479> because 00:02:09.389 --> 00:02:09.399 align:start position:0% have real consumer use cases because 00:02:09.399 --> 00:02:12.910 align:start position:0% have real consumer use cases because these<00:02:09.879> these<00:02:10.319> uh<00:02:10.479> l2s<00:02:11.000> are<00:02:11.239> now<00:02:12.080> uh<00:02:12.319> so<00:02:12.599> cheap 00:02:12.910 --> 00:02:12.920 align:start position:0% these these uh l2s are now uh so cheap 00:02:12.920 --> 00:02:15.350 align:start position:0% these these uh l2s are now uh so cheap and<00:02:13.080> usable<00:02:13.680> normal<00:02:14.120> people<00:02:14.519> not<00:02:14.720> just<00:02:14.920> whales 00:02:15.350 --> 00:02:15.360 align:start position:0% and usable normal people not just whales 00:02:15.360 --> 00:02:18.509 align:start position:0% and usable normal people not just whales can<00:02:15.480> use<00:02:16.000> them<00:02:17.000> and<00:02:17.200> so<00:02:17.800> this<00:02:17.920> is<00:02:18.040> a<00:02:18.160> beautiful 00:02:18.509 --> 00:02:18.519 align:start position:0% can use them and so this is a beautiful 00:02:18.519 --> 00:02:21.190 align:start position:0% can use them and so this is a beautiful chart<00:02:19.080> like<00:02:19.239> we<00:02:19.440> really<00:02:19.680> did<00:02:19.920> scale<00:02:20.280> ethereum 00:02:21.190 --> 00:02:21.200 align:start position:0% chart like we really did scale ethereum 00:02:21.200 --> 00:02:22.750 align:start position:0% chart like we really did scale ethereum thanks<00:02:21.440> to<00:02:21.599> the<00:02:21.720> rollup<00:02:22.040> Centric<00:02:22.360> road<00:02:22.560> map 00:02:22.750 --> 00:02:22.760 align:start position:0% thanks to the rollup Centric road map 00:02:22.760 --> 00:02:23.869 align:start position:0% thanks to the rollup Centric road map and<00:02:22.879> some<00:02:23.000> of<00:02:23.120> the<00:02:23.200> people<00:02:23.360> that<00:02:23.440> are<00:02:23.560> just<00:02:23.680> on 00:02:23.869 --> 00:02:23.879 align:start position:0% and some of the people that are just on 00:02:23.879 --> 00:02:26.070 align:start position:0% and some of the people that are just on stage<00:02:24.120> with<00:02:24.280> me<00:02:25.000> there<00:02:25.080> we<00:02:25.280> go<00:02:25.760> scaled 00:02:26.070 --> 00:02:26.080 align:start position:0% stage with me there we go scaled 00:02:26.080 --> 00:02:27.589 align:start position:0% stage with me there we go scaled ethereum<00:02:26.680> and<00:02:26.800> this<00:02:26.879> is<00:02:27.080> something<00:02:27.360> that<00:02:27.519> I 00:02:27.589 --> 00:02:27.599 align:start position:0% ethereum and this is something that I 00:02:27.599 --> 00:02:29.910 align:start position:0% ethereum and this is something that I don't<00:02:27.800> think<00:02:27.959> we<00:02:28.120> celebrate<00:02:28.640> enough<00:02:29.480> uh<00:02:29.640> we 00:02:29.910 --> 00:02:29.920 align:start position:0% don't think we celebrate enough uh we 00:02:29.920 --> 00:02:32.110 align:start position:0% don't think we celebrate enough uh we solve<00:02:30.200> the<00:02:30.319> big<00:02:30.560> hairy<00:02:31.000> problem<00:02:31.680> and<00:02:31.959> uh<00:02:32.040> we 00:02:32.110 --> 00:02:32.120 align:start position:0% solve the big hairy problem and uh we 00:02:32.120 --> 00:02:33.869 align:start position:0% solve the big hairy problem and uh we should<00:02:32.280> be<00:02:32.400> proud<00:02:32.599> of 00:02:33.869 --> 00:02:33.879 align:start position:0% should be proud of 00:02:33.879 --> 00:02:38.309 align:start position:0% should be proud of that<00:02:34.879> new<00:02:35.120> problem<00:02:36.120> ethereum<00:02:36.519> is 00:02:38.309 --> 00:02:38.319 align:start position:0% that new problem ethereum is 00:02:38.319 --> 00:02:41.190 align:start position:0% that new problem ethereum is fragmented<00:02:39.319> it<00:02:39.440> was<00:02:39.800> so<00:02:40.280> simple<00:02:40.800> back<00:02:40.920> in<00:02:41.040> the 00:02:41.190 --> 00:02:41.200 align:start position:0% fragmented it was so simple back in the 00:02:41.200 --> 00:02:42.949 align:start position:0% fragmented it was so simple back in the day<00:02:41.400> when<00:02:41.519> we<00:02:41.680> had<00:02:41.840> one<00:02:42.040> chain<00:02:42.560> it<00:02:42.680> was<00:02:42.800> like 00:02:42.949 --> 00:02:42.959 align:start position:0% day when we had one chain it was like 00:02:42.959 --> 00:02:45.149 align:start position:0% day when we had one chain it was like such<00:02:43.080> a<00:02:43.200> beautiful<00:02:43.599> thing<00:02:43.879> I<00:02:44.000> had<00:02:44.159> metamask<00:02:45.040> I 00:02:45.149 --> 00:02:45.159 align:start position:0% such a beautiful thing I had metamask I 00:02:45.159 --> 00:02:47.070 align:start position:0% such a beautiful thing I had metamask I had<00:02:45.280> one<00:02:45.480> chain<00:02:45.879> I<00:02:46.000> hit<00:02:46.200> one<00:02:46.360> button<00:02:46.760> it<00:02:46.920> did 00:02:47.070 --> 00:02:47.080 align:start position:0% had one chain I hit one button it did 00:02:47.080 --> 00:02:48.910 align:start position:0% had one chain I hit one button it did the<00:02:47.159> thing<00:02:47.319> on<00:02:47.440> ethereum<00:02:48.200> and<00:02:48.360> it<00:02:48.519> it<00:02:48.599> worked 00:02:48.910 --> 00:02:48.920 align:start position:0% the thing on ethereum and it it worked 00:02:48.920 --> 00:02:53.630 align:start position:0% the thing on ethereum and it it worked great<00:02:49.920> um<00:02:50.920> but<00:02:51.519> uh<00:02:51.959> it<00:02:52.080> got<00:02:52.239> more<00:02:52.640> complicated 00:02:53.630 --> 00:02:53.640 align:start position:0% great um but uh it got more complicated 00:02:53.640 --> 00:02:55.790 align:start position:0% great um but uh it got more complicated so<00:02:54.040> our<00:02:54.159> rollup<00:02:54.560> Centric<00:02:54.840> road<00:02:55.080> map<00:02:55.319> now<00:02:55.440> means 00:02:55.790 --> 00:02:55.800 align:start position:0% so our rollup Centric road map now means 00:02:55.800 --> 00:02:59.350 align:start position:0% so our rollup Centric road map now means we<00:02:56.000> have<00:02:56.519> lots<00:02:56.879> and<00:02:57.080> lots<00:02:57.280> of<00:02:57.680> chains<00:02:58.680> um<00:02:59.239> and 00:02:59.350 --> 00:02:59.360 align:start position:0% we have lots and lots of chains um and 00:02:59.360 --> 00:03:00.990 align:start position:0% we have lots and lots of chains um and we<00:02:59.480> got<00:02:59.560> to<00:02:59.680> like<00:02:59.920> do<00:03:00.080> this<00:03:00.200> network<00:03:00.519> switching 00:03:00.990 --> 00:03:01.000 align:start position:0% we got to like do this network switching 00:03:01.000 --> 00:03:02.589 align:start position:0% we got to like do this network switching thing<00:03:01.519> and<00:03:01.760> sure<00:03:02.000> some<00:03:02.159> wallets<00:03:02.480> are 00:03:02.589 --> 00:03:02.599 align:start position:0% thing and sure some wallets are 00:03:02.599 --> 00:03:05.270 align:start position:0% thing and sure some wallets are beginning<00:03:02.879> to<00:03:03.159> hide<00:03:03.360> this<00:03:03.640> for<00:03:03.879> us<00:03:04.519> but<00:03:04.799> man 00:03:05.270 --> 00:03:05.280 align:start position:0% beginning to hide this for us but man 00:03:05.280 --> 00:03:06.869 align:start position:0% beginning to hide this for us but man like<00:03:05.400> switch<00:03:05.720> between<00:03:06.000> all<00:03:06.159> these<00:03:06.280> chains<00:03:06.720> add 00:03:06.869 --> 00:03:06.879 align:start position:0% like switch between all these chains add 00:03:06.879 --> 00:03:09.589 align:start position:0% like switch between all these chains add a<00:03:07.000> new<00:03:07.159> network<00:03:07.440> to<00:03:07.560> metam<00:03:08.040> mask 00:03:09.589 --> 00:03:09.599 align:start position:0% a new network to metam mask 00:03:09.599 --> 00:03:13.190 align:start position:0% a new network to metam mask mess<00:03:10.599> we<00:03:10.840> got<00:03:11.599> so<00:03:11.799> many<00:03:12.080> versions<00:03:12.440> of 00:03:13.190 --> 00:03:13.200 align:start position:0% mess we got so many versions of 00:03:13.200 --> 00:03:15.910 align:start position:0% mess we got so many versions of ethereum<00:03:14.200> there's<00:03:14.440> just<00:03:14.760> so<00:03:14.959> many<00:03:15.200> different 00:03:15.910 --> 00:03:15.920 align:start position:0% ethereum there's just so many different 00:03:15.920 --> 00:03:19.149 align:start position:0% ethereum there's just so many different ones<00:03:16.920> uh<00:03:17.159> it's<00:03:17.560> it's<00:03:17.680> a<00:03:17.840> total<00:03:18.120> mess<00:03:18.760> and<00:03:18.959> I<00:03:19.080> I 00:03:19.149 --> 00:03:19.159 align:start position:0% ones uh it's it's a total mess and I I 00:03:19.159 --> 00:03:22.190 align:start position:0% ones uh it's it's a total mess and I I think<00:03:19.280> it's<00:03:19.440> just<00:03:19.599> worth<00:03:19.920> us<00:03:20.760> um<00:03:21.280> admitting 00:03:22.190 --> 00:03:22.200 align:start position:0% think it's just worth us um admitting 00:03:22.200 --> 00:03:24.670 align:start position:0% think it's just worth us um admitting that<00:03:22.360> we<00:03:22.480> have<00:03:22.640> a<00:03:22.799> major<00:03:23.239> ux<00:03:23.799> problem<00:03:24.239> here 00:03:24.670 --> 00:03:24.680 align:start position:0% that we have a major ux problem here 00:03:24.680 --> 00:03:26.270 align:start position:0% that we have a major ux problem here this<00:03:24.799> is<00:03:25.040> this<00:03:25.159> is<00:03:25.319> not<00:03:25.640> something<00:03:26.000> that<00:03:26.159> the 00:03:26.270 --> 00:03:26.280 align:start position:0% this is this is not something that the 00:03:26.280 --> 00:03:27.509 align:start position:0% this is this is not something that the next<00:03:26.480> billion<00:03:26.799> people<00:03:27.000> are<00:03:27.120> going<00:03:27.200> to<00:03:27.280> be<00:03:27.360> able 00:03:27.509 --> 00:03:27.519 align:start position:0% next billion people are going to be able 00:03:27.519 --> 00:03:29.350 align:start position:0% next billion people are going to be able to<00:03:27.680> use<00:03:28.239> even<00:03:28.439> though<00:03:28.560> it's<00:03:28.720> fast<00:03:28.879> and<00:03:29.080> cheap 00:03:29.350 --> 00:03:29.360 align:start position:0% to use even though it's fast and cheap 00:03:29.360 --> 00:03:31.550 align:start position:0% to use even though it's fast and cheap on<00:03:29.560> any<00:03:29.799> individual<00:03:30.159> roll<00:03:30.400> up<00:03:31.080> this<00:03:31.239> is<00:03:31.439> this 00:03:31.550 --> 00:03:31.560 align:start position:0% on any individual roll up this is this 00:03:31.560 --> 00:03:33.630 align:start position:0% on any individual roll up this is this is<00:03:31.680> a<00:03:31.799> mess<00:03:32.040> for<00:03:32.319> the<00:03:32.640> the<00:03:32.799> the 00:03:33.630 --> 00:03:33.640 align:start position:0% is a mess for the the the 00:03:33.640 --> 00:03:35.750 align:start position:0% is a mess for the the the users<00:03:34.640> what<00:03:34.760> we<00:03:34.840> got<00:03:34.920> to<00:03:35.040> do<00:03:35.159> we<00:03:35.280> got<00:03:35.360> to<00:03:35.439> unify 00:03:35.750 --> 00:03:35.760 align:start position:0% users what we got to do we got to unify 00:03:35.760 --> 00:03:37.270 align:start position:0% users what we got to do we got to unify ethereum<00:03:36.439> this<00:03:36.560> is<00:03:36.799> this<00:03:36.879> should<00:03:37.040> be<00:03:37.159> the 00:03:37.270 --> 00:03:37.280 align:start position:0% ethereum this is this should be the 00:03:37.280 --> 00:03:39.789 align:start position:0% ethereum this is this should be the rallying<00:03:37.760> cry<00:03:38.000> for<00:03:38.159> 2025<00:03:39.120> this<00:03:39.200> is<00:03:39.400> what<00:03:39.599> I 00:03:39.789 --> 00:03:39.799 align:start position:0% rallying cry for 2025 this is what I 00:03:39.799 --> 00:03:42.589 align:start position:0% rallying cry for 2025 this is what I want<00:03:40.680> uh<00:03:40.879> ethereum<00:03:41.400> to<00:03:41.519> be<00:03:41.680> focused<00:03:42.080> on<00:03:42.360> for 00:03:42.589 --> 00:03:42.599 align:start position:0% want uh ethereum to be focused on for 00:03:42.599 --> 00:03:44.710 align:start position:0% want uh ethereum to be focused on for the<00:03:42.799> next<00:03:43.120> year<00:03:43.799> I<00:03:43.920> hope<00:03:44.120> it<00:03:44.200> doesn't<00:03:44.439> take<00:03:44.599> us 00:03:44.710 --> 00:03:44.720 align:start position:0% the next year I hope it doesn't take us 00:03:44.720 --> 00:03:46.589 align:start position:0% the next year I hope it doesn't take us four<00:03:44.959> years<00:03:45.159> to<00:03:45.280> unify<00:03:45.640> ethereum<00:03:46.280> I<00:03:46.360> want<00:03:46.480> it 00:03:46.589 --> 00:03:46.599 align:start position:0% four years to unify ethereum I want it 00:03:46.599 --> 00:03:49.509 align:start position:0% four years to unify ethereum I want it to<00:03:46.720> take<00:03:46.959> one<00:03:47.760> um<00:03:47.879> vitalic<00:03:48.360> seems<00:03:48.640> optimistic 00:03:49.509 --> 00:03:49.519 align:start position:0% to take one um vitalic seems optimistic 00:03:49.519 --> 00:03:51.030 align:start position:0% to take one um vitalic seems optimistic uh<00:03:49.680> I<00:03:49.799> hope<00:03:50.080> I<00:03:50.200> hope<00:03:50.439> we're<00:03:50.720> we're<00:03:50.879> all 00:03:51.030 --> 00:03:51.040 align:start position:0% uh I hope I hope we're we're all 00:03:51.040 --> 00:03:53.110 align:start position:0% uh I hope I hope we're we're all optimistic<00:03:51.560> here<00:03:52.040> and<00:03:52.200> we<00:03:52.319> want<00:03:52.560> ethereum<00:03:53.000> to 00:03:53.110 --> 00:03:53.120 align:start position:0% optimistic here and we want ethereum to 00:03:53.120 --> 00:03:55.910 align:start position:0% optimistic here and we want ethereum to feel<00:03:53.360> like<00:03:53.760> one<00:03:54.040> chain<00:03:54.599> again<00:03:55.439> um<00:03:55.560> we<00:03:55.680> want<00:03:55.799> it 00:03:55.910 --> 00:03:55.920 align:start position:0% feel like one chain again um we want it 00:03:55.920 --> 00:03:59.149 align:start position:0% feel like one chain again um we want it to<00:03:56.040> be<00:03:56.280> like<00:03:56.560> hey<00:03:57.120> I<00:03:57.280> click<00:03:57.599> one<00:03:57.840> button<00:03:58.760> in<00:03:58.959> one 00:03:59.149 --> 00:03:59.159 align:start position:0% to be like hey I click one button in one 00:03:59.159 --> 00:04:01.470 align:start position:0% to be like hey I click one button in one wallet<00:03:59.840> and<00:04:00.000> it<00:04:00.120> does<00:04:00.400> what<00:04:00.519> I<00:04:00.640> want<00:04:00.760> to<00:04:00.959> do<00:04:01.239> on 00:04:01.470 --> 00:04:01.480 align:start position:0% wallet and it does what I want to do on 00:04:01.480 --> 00:04:03.910 align:start position:0% wallet and it does what I want to do on whatever<00:04:01.840> chain<00:04:02.159> I'm<00:04:02.319> on<00:04:03.159> um<00:04:03.319> and<00:04:03.439> Jesse<00:04:03.799> was 00:04:03.910 --> 00:04:03.920 align:start position:0% whatever chain I'm on um and Jesse was 00:04:03.920 --> 00:04:05.309 align:start position:0% whatever chain I'm on um and Jesse was speaking<00:04:04.159> about<00:04:04.360> this<00:04:04.480> on<00:04:04.560> the<00:04:04.680> panel<00:04:04.959> we<00:04:05.120> just 00:04:05.309 --> 00:04:05.319 align:start position:0% speaking about this on the panel we just 00:04:05.319 --> 00:04:07.550 align:start position:0% speaking about this on the panel we just had<00:04:06.040> um<00:04:06.239> so<00:04:06.560> pretty<00:04:06.799> bullish<00:04:07.200> that<00:04:07.360> there's 00:04:07.550 --> 00:04:07.560 align:start position:0% had um so pretty bullish that there's 00:04:07.560 --> 00:04:09.429 align:start position:0% had um so pretty bullish that there's like<00:04:07.959> people<00:04:08.239> running<00:04:08.640> big<00:04:08.840> wallets<00:04:09.239> like 00:04:09.429 --> 00:04:09.439 align:start position:0% like people running big wallets like 00:04:09.439 --> 00:04:11.550 align:start position:0% like people running big wallets like coinbase<00:04:09.879> wallet<00:04:10.560> that<00:04:10.720> are<00:04:10.959> aligned<00:04:11.400> and 00:04:11.550 --> 00:04:11.560 align:start position:0% coinbase wallet that are aligned and 00:04:11.560 --> 00:04:12.910 align:start position:0% coinbase wallet that are aligned and thinking<00:04:11.879> this<00:04:12.040> way 00:04:12.910 --> 00:04:12.920 align:start position:0% thinking this way 00:04:12.920 --> 00:04:15.190 align:start position:0% thinking this way too<00:04:13.920> and<00:04:14.000> so<00:04:14.120> there<00:04:14.239> are<00:04:14.360> a<00:04:14.480> few<00:04:14.640> components<00:04:15.120> I 00:04:15.190 --> 00:04:15.200 align:start position:0% too and so there are a few components I 00:04:15.200 --> 00:04:16.990 align:start position:0% too and so there are a few components I think<00:04:15.360> of<00:04:15.519> how<00:04:15.680> we<00:04:15.920> actually<00:04:16.120> make<00:04:16.639> ethereum 00:04:16.990 --> 00:04:17.000 align:start position:0% think of how we actually make ethereum 00:04:17.000 --> 00:04:19.270 align:start position:0% think of how we actually make ethereum feel<00:04:17.199> unified<00:04:18.079> it's<00:04:18.239> the<00:04:18.400> better<00:04:18.720> wallet<00:04:19.040> and 00:04:19.270 --> 00:04:19.280 align:start position:0% feel unified it's the better wallet and 00:04:19.280 --> 00:04:22.150 align:start position:0% feel unified it's the better wallet and app<00:04:19.919> ux<00:04:20.919> uh<00:04:21.040> I<00:04:21.120> think<00:04:21.239> there's<00:04:21.400> a<00:04:21.680> necessary 00:04:22.150 --> 00:04:22.160 align:start position:0% app ux uh I think there's a necessary 00:04:22.160 --> 00:04:24.629 align:start position:0% app ux uh I think there's a necessary component<00:04:22.600> around<00:04:23.120> account<00:04:23.639> abstraction 00:04:24.629 --> 00:04:24.639 align:start position:0% component around account abstraction 00:04:24.639 --> 00:04:27.270 align:start position:0% component around account abstraction specifically<00:04:25.240> EIP<00:04:25.800> 7702<00:04:26.800> which<00:04:26.919> I'm<00:04:27.040> going<00:04:27.120> to 00:04:27.270 --> 00:04:27.280 align:start position:0% specifically EIP 7702 which I'm going to 00:04:27.280 --> 00:04:29.350 align:start position:0% specifically EIP 7702 which I'm going to talk<00:04:27.479> a<00:04:27.600> bit<00:04:27.759> about<00:04:28.080> later<00:04:28.320> on<00:04:29.080> and<00:04:29.199> then 00:04:29.350 --> 00:04:29.360 align:start position:0% talk a bit about later on and then 00:04:29.360 --> 00:04:30.749 align:start position:0% talk a bit about later on and then there's 00:04:30.749 --> 00:04:30.759 align:start position:0% there's 00:04:30.759 --> 00:04:34.390 align:start position:0% there's speed<00:04:31.840> um<00:04:32.840> to<00:04:33.280> to<00:04:33.440> make<00:04:33.840> ethereum<00:04:34.160> feel 00:04:34.390 --> 00:04:34.400 align:start position:0% speed um to to make ethereum feel 00:04:34.400 --> 00:04:36.590 align:start position:0% speed um to to make ethereum feel unified<00:04:35.160> I<00:04:35.320> think<00:04:35.560> inter<00:04:35.880> op<00:04:36.080> needs<00:04:36.240> to<00:04:36.360> be 00:04:36.590 --> 00:04:36.600 align:start position:0% unified I think inter op needs to be 00:04:36.600 --> 00:04:40.029 align:start position:0% unified I think inter op needs to be fast<00:04:37.560> like<00:04:37.960> really<00:04:38.320> fast<00:04:38.960> and<00:04:39.199> for<00:04:39.400> me<00:04:39.720> fast 00:04:40.029 --> 00:04:40.039 align:start position:0% fast like really fast and for me fast 00:04:40.039 --> 00:04:43.950 align:start position:0% fast like really fast and for me fast means<00:04:40.639> um<00:04:41.199> two<00:04:41.479> seconds<00:04:42.000> fast<00:04:43.000> and<00:04:43.440> it<00:04:43.680> kind<00:04:43.800> of 00:04:43.950 --> 00:04:43.960 align:start position:0% means um two seconds fast and it kind of 00:04:43.960 --> 00:04:45.430 align:start position:0% means um two seconds fast and it kind of seems<00:04:44.199> like<00:04:44.360> I'm<00:04:44.479> making<00:04:44.720> up<00:04:44.880> this<00:04:45.000> two<00:04:45.199> second 00:04:45.430 --> 00:04:45.440 align:start position:0% seems like I'm making up this two second 00:04:45.440 --> 00:04:47.870 align:start position:0% seems like I'm making up this two second number<00:04:45.880> like<00:04:46.000> where<00:04:46.160> is<00:04:46.280> this<00:04:46.479> coming<00:04:46.759> from<00:04:47.639> it 00:04:47.870 --> 00:04:47.880 align:start position:0% number like where is this coming from it 00:04:47.880 --> 00:04:50.590 align:start position:0% number like where is this coming from it isn't<00:04:48.400> totally<00:04:48.840> made<00:04:49.080> up<00:04:49.919> um<00:04:50.080> there's<00:04:50.360> lots 00:04:50.590 --> 00:04:50.600 align:start position:0% isn't totally made up um there's lots 00:04:50.600 --> 00:04:53.590 align:start position:0% isn't totally made up um there's lots and<00:04:50.800> lots<00:04:51.039> of<00:04:51.240> web<00:04:51.479> 2ux<00:04:52.160> research<00:04:53.000> that<00:04:53.199> says 00:04:53.590 --> 00:04:53.600 align:start position:0% and lots of web 2ux research that says 00:04:53.600 --> 00:04:55.070 align:start position:0% and lots of web 2ux research that says if<00:04:53.720> you<00:04:53.840> wait<00:04:54.000> for<00:04:54.160> more<00:04:54.320> than<00:04:54.479> two<00:04:54.759> seconds 00:04:55.070 --> 00:04:55.080 align:start position:0% if you wait for more than two seconds 00:04:55.080 --> 00:04:57.670 align:start position:0% if you wait for more than two seconds for<00:04:55.240> a<00:04:55.360> website<00:04:55.680> to<00:04:55.800> load<00:04:56.280> users<00:04:56.680> Just<00:04:56.880> Bounce 00:04:57.670 --> 00:04:57.680 align:start position:0% for a website to load users Just Bounce 00:04:57.680 --> 00:04:58.710 align:start position:0% for a website to load users Just Bounce like<00:04:57.800> they<00:04:57.919> just<00:04:58.039> don't<00:04:58.160> want<00:04:58.280> to<00:04:58.400> use<00:04:58.560> the 00:04:58.710 --> 00:04:58.720 align:start position:0% like they just don't want to use the 00:04:58.720 --> 00:05:00.430 align:start position:0% like they just don't want to use the thing<00:04:59.400> and<00:04:59.680> I<00:04:59.759> don't<00:04:59.880> know<00:05:00.000> if<00:05:00.080> you<00:05:00.160> guys<00:05:00.280> have 00:05:00.430 --> 00:05:00.440 align:start position:0% thing and I don't know if you guys have 00:05:00.440 --> 00:05:02.430 align:start position:0% thing and I don't know if you guys have like<00:05:00.560> used<00:05:00.840> airplane<00:05:01.400> Wi-Fi<00:05:01.880> when<00:05:02.080> websites 00:05:02.430 --> 00:05:02.440 align:start position:0% like used airplane Wi-Fi when websites 00:05:02.440 --> 00:05:04.310 align:start position:0% like used airplane Wi-Fi when websites load<00:05:02.720> forever<00:05:03.280> it<00:05:03.400> just<00:05:03.520> makes<00:05:03.720> you<00:05:03.919> not<00:05:04.120> want 00:05:04.310 --> 00:05:04.320 align:start position:0% load forever it just makes you not want 00:05:04.320 --> 00:05:06.029 align:start position:0% load forever it just makes you not want to<00:05:04.479> surf<00:05:04.880> the<00:05:05.000> Internet<00:05:05.440> it<00:05:05.560> makes<00:05:05.720> you<00:05:05.880> not 00:05:06.029 --> 00:05:06.039 align:start position:0% to surf the Internet it makes you not 00:05:06.039 --> 00:05:08.110 align:start position:0% to surf the Internet it makes you not want<00:05:06.199> to<00:05:06.400> use<00:05:06.639> the<00:05:06.840> thing<00:05:07.560> and<00:05:07.720> there<00:05:07.840> seems<00:05:08.039> to 00:05:08.110 --> 00:05:08.120 align:start position:0% want to use the thing and there seems to 00:05:08.120 --> 00:05:10.270 align:start position:0% want to use the thing and there seems to be<00:05:08.240> this<00:05:08.400> psychological<00:05:09.039> barrier<00:05:09.720> that<00:05:09.880> I<00:05:10.000> can 00:05:10.270 --> 00:05:10.280 align:start position:0% be this psychological barrier that I can 00:05:10.280 --> 00:05:12.189 align:start position:0% be this psychological barrier that I can I<00:05:10.360> can<00:05:10.520> afford<00:05:10.800> to<00:05:10.960> wait<00:05:11.160> two<00:05:11.440> seconds<00:05:11.840> but<00:05:12.039> any 00:05:12.189 --> 00:05:12.199 align:start position:0% I can afford to wait two seconds but any 00:05:12.199 --> 00:05:13.870 align:start position:0% I can afford to wait two seconds but any longer<00:05:12.520> than<00:05:12.759> that<00:05:13.199> I<00:05:13.320> want<00:05:13.440> to<00:05:13.560> go<00:05:13.680> do 00:05:13.870 --> 00:05:13.880 align:start position:0% longer than that I want to go do 00:05:13.880 --> 00:05:15.909 align:start position:0% longer than that I want to go do something<00:05:14.199> else<00:05:15.120> so<00:05:15.280> if<00:05:15.400> we<00:05:15.479> want<00:05:15.720> the 00:05:15.909 --> 00:05:15.919 align:start position:0% something else so if we want the 00:05:15.919 --> 00:05:17.749 align:start position:0% something else so if we want the experience<00:05:16.560> for<00:05:16.720> the<00:05:16.840> next<00:05:17.039> billion<00:05:17.320> users<00:05:17.639> if 00:05:17.749 --> 00:05:17.759 align:start position:0% experience for the next billion users if 00:05:17.759 --> 00:05:19.670 align:start position:0% experience for the next billion users if we<00:05:17.840> want<00:05:17.919> to<00:05:18.000> compete<00:05:18.280> with<00:05:18.400> web<00:05:18.600> 2<00:05:19.319> I<00:05:19.479> really 00:05:19.670 --> 00:05:19.680 align:start position:0% we want to compete with web 2 I really 00:05:19.680 --> 00:05:21.390 align:start position:0% we want to compete with web 2 I really truly<00:05:20.039> believe<00:05:20.319> we<00:05:20.479> have<00:05:20.560> to<00:05:20.720> hit<00:05:20.880> this<00:05:21.080> two 00:05:21.390 --> 00:05:21.400 align:start position:0% truly believe we have to hit this two 00:05:21.400 --> 00:05:23.710 align:start position:0% truly believe we have to hit this two second<00:05:21.919> interoperability 00:05:23.710 --> 00:05:23.720 align:start position:0% second interoperability 00:05:23.720 --> 00:05:26.990 align:start position:0% second interoperability time<00:05:24.720> and<00:05:24.960> in<00:05:25.199> tents<00:05:26.120> what<00:05:26.280> what<00:05:26.400> we<00:05:26.479> do<00:05:26.639> with<00:05:26.759> a 00:05:26.990 --> 00:05:27.000 align:start position:0% time and in tents what what we do with a 00:05:27.000 --> 00:05:29.270 align:start position:0% time and in tents what what we do with a cross<00:05:27.800> it<00:05:27.919> has<00:05:28.039> a<00:05:28.199> different<00:05:28.520> tent<00:05:28.880> icon 00:05:29.270 --> 00:05:29.280 align:start position:0% cross it has a different tent icon 00:05:29.280 --> 00:05:31.270 align:start position:0% cross it has a different tent icon that's<00:05:29.400> kind<00:05:29.479> of<00:05:29.840> cool<00:05:30.400> um<00:05:30.560> intense<00:05:31.080> what<00:05:31.160> we 00:05:31.270 --> 00:05:31.280 align:start position:0% that's kind of cool um intense what we 00:05:31.280 --> 00:05:33.830 align:start position:0% that's kind of cool um intense what we do<00:05:31.400> with<00:05:31.479> a<00:05:31.680> cross<00:05:32.600> uh<00:05:32.759> are<00:05:33.000> the<00:05:33.120> only<00:05:33.440> viable 00:05:33.830 --> 00:05:33.840 align:start position:0% do with a cross uh are the only viable 00:05:33.840 --> 00:05:35.990 align:start position:0% do with a cross uh are the only viable mechanism<00:05:34.520> to<00:05:34.720> deliver<00:05:35.120> this<00:05:35.240> two-c 00:05:35.990 --> 00:05:36.000 align:start position:0% mechanism to deliver this two-c 00:05:36.000 --> 00:05:38.749 align:start position:0% mechanism to deliver this two-c experience<00:05:37.000> um<00:05:37.520> and<00:05:37.680> we<00:05:37.800> do<00:05:38.039> this<00:05:38.479> I'll<00:05:38.639> go 00:05:38.749 --> 00:05:38.759 align:start position:0% experience um and we do this I'll go 00:05:38.759 --> 00:05:40.830 align:start position:0% experience um and we do this I'll go into<00:05:39.080> how<00:05:39.240> we<00:05:39.360> structure<00:05:39.840> this<00:05:40.400> but<00:05:40.639> like 00:05:40.830 --> 00:05:40.840 align:start position:0% into how we structure this but like 00:05:40.840 --> 00:05:42.710 align:start position:0% into how we structure this but like right<00:05:41.000> now<00:05:41.199> today<00:05:41.639> in<00:05:41.759> the<00:05:41.919> across<00:05:42.280> protocol 00:05:42.710 --> 00:05:42.720 align:start position:0% right now today in the across protocol 00:05:42.720 --> 00:05:44.230 align:start position:0% right now today in the across protocol the<00:05:42.800> median<00:05:43.120> fill<00:05:43.400> time<00:05:43.560> between<00:05:43.800> chains<00:05:44.120> is 00:05:44.230 --> 00:05:44.240 align:start position:0% the median fill time between chains is 00:05:44.240 --> 00:05:46.189 align:start position:0% the median fill time between chains is about<00:05:44.479> 3<00:05:44.759> seconds<00:05:45.360> we'll<00:05:45.520> go<00:05:45.720> into<00:05:45.840> some<00:05:46.000> data 00:05:46.189 --> 00:05:46.199 align:start position:0% about 3 seconds we'll go into some data 00:05:46.199 --> 00:05:49.430 align:start position:0% about 3 seconds we'll go into some data on<00:05:46.400> this<00:05:46.759> but<00:05:46.880> it's<00:05:47.160> fast<00:05:47.960> um<00:05:48.600> and<00:05:48.840> and<00:05:49.080> why<00:05:49.240> is 00:05:49.430 --> 00:05:49.440 align:start position:0% on this but it's fast um and and why is 00:05:49.440 --> 00:05:52.590 align:start position:0% on this but it's fast um and and why is that<00:05:50.360> so<00:05:50.759> it's<00:05:50.919> worth<00:05:51.199> walking<00:05:51.639> through<00:05:52.400> what 00:05:52.590 --> 00:05:52.600 align:start position:0% that so it's worth walking through what 00:05:52.600 --> 00:05:54.870 align:start position:0% that so it's worth walking through what the<00:05:52.880> traditional<00:05:53.440> bridging<00:05:53.880> flow<00:05:54.280> is<00:05:54.759> when 00:05:54.870 --> 00:05:54.880 align:start position:0% the traditional bridging flow is when 00:05:54.880 --> 00:05:56.629 align:start position:0% the traditional bridging flow is when we're<00:05:55.039> connecting<00:05:55.400> blockchains<00:05:56.280> and<00:05:56.440> why 00:05:56.629 --> 00:05:56.639 align:start position:0% we're connecting blockchains and why 00:05:56.639 --> 00:05:58.990 align:start position:0% we're connecting blockchains and why this<00:05:56.800> intent<00:05:57.240> architecture<00:05:57.960> is<00:05:58.240> different 00:05:58.990 --> 00:05:59.000 align:start position:0% this intent architecture is different 00:05:59.000 --> 00:06:00.870 align:start position:0% this intent architecture is different and<00:05:59.240> faster 00:06:00.870 --> 00:06:00.880 align:start position:0% and faster 00:06:00.880 --> 00:06:03.510 align:start position:0% and faster okay<00:06:01.400> so<00:06:01.639> traditional<00:06:02.199> Bridge<00:06:02.960> uh<00:06:03.080> I<00:06:03.199> got<00:06:03.319> two 00:06:03.510 --> 00:06:03.520 align:start position:0% okay so traditional Bridge uh I got two 00:06:03.520 --> 00:06:06.510 align:start position:0% okay so traditional Bridge uh I got two chains<00:06:04.360> A<00:06:04.520> and<00:06:04.680> B<00:06:05.000> I<00:06:05.080> got<00:06:05.240> arbitrum<00:06:06.039> and<00:06:06.160> I<00:06:06.240> got 00:06:06.510 --> 00:06:06.520 align:start position:0% chains A and B I got arbitrum and I got 00:06:06.520 --> 00:06:10.110 align:start position:0% chains A and B I got arbitrum and I got Bas<00:06:07.520> um<00:06:07.960> step<00:06:08.240> one<00:06:09.000> I<00:06:09.080> want<00:06:09.240> to<00:06:09.440> deposit<00:06:09.919> my 00:06:10.110 --> 00:06:10.120 align:start position:0% Bas um step one I want to deposit my 00:06:10.120 --> 00:06:14.070 align:start position:0% Bas um step one I want to deposit my assets<00:06:10.400> on<00:06:10.560> chain<00:06:11.120> a<00:06:12.120> and<00:06:12.240> then<00:06:12.440> I<00:06:12.720> wait<00:06:13.720> I<00:06:13.880> wait 00:06:14.070 --> 00:06:14.080 align:start position:0% assets on chain a and then I wait I wait 00:06:14.080 --> 00:06:16.790 align:start position:0% assets on chain a and then I wait I wait for<00:06:14.319> finality<00:06:15.280> I<00:06:15.440> can't<00:06:15.880> the<00:06:16.039> protocol<00:06:16.560> can't 00:06:16.790 --> 00:06:16.800 align:start position:0% for finality I can't the protocol can't 00:06:16.800 --> 00:06:18.390 align:start position:0% for finality I can't the protocol can't do<00:06:17.080> anything<00:06:17.680> in<00:06:17.800> the<00:06:17.960> traditional 00:06:18.390 --> 00:06:18.400 align:start position:0% do anything in the traditional 00:06:18.400 --> 00:06:20.510 align:start position:0% do anything in the traditional architecture<00:06:19.360> until<00:06:19.639> it<00:06:19.800> knows<00:06:20.160> that<00:06:20.360> those 00:06:20.510 --> 00:06:20.520 align:start position:0% architecture until it knows that those 00:06:20.520 --> 00:06:23.710 align:start position:0% architecture until it knows that those funds<00:06:20.919> are<00:06:21.280> actually<00:06:21.599> on<00:06:21.880> chain<00:06:22.400> a<00:06:23.400> and<00:06:23.599> this 00:06:23.710 --> 00:06:23.720 align:start position:0% funds are actually on chain a and this 00:06:23.720 --> 00:06:27.189 align:start position:0% funds are actually on chain a and this waiting<00:06:24.240> is<00:06:24.400> a<00:06:24.639> a<00:06:24.960> problem<00:06:25.960> um<00:06:26.319> once<00:06:26.800> I'm<00:06:26.960> done 00:06:27.189 --> 00:06:27.199 align:start position:0% waiting is a a problem um once I'm done 00:06:27.199 --> 00:06:29.110 align:start position:0% waiting is a a problem um once I'm done waiting<00:06:27.520> for<00:06:27.800> finality<00:06:28.319> or<00:06:28.400> for<00:06:28.599> a<00:06:28.759> sense<00:06:28.960> of 00:06:29.110 --> 00:06:29.120 align:start position:0% waiting for finality or for a sense of 00:06:29.120 --> 00:06:31.070 align:start position:0% waiting for finality or for a sense of finality<00:06:30.000> then<00:06:30.120> I<00:06:30.240> can<00:06:30.400> go<00:06:30.520> and<00:06:30.680> send<00:06:30.919> my 00:06:31.070 --> 00:06:31.080 align:start position:0% finality then I can go and send my 00:06:31.080 --> 00:06:33.469 align:start position:0% finality then I can go and send my message<00:06:31.360> to<00:06:31.520> chain<00:06:32.039> B<00:06:33.039> and<00:06:33.160> then<00:06:33.280> I<00:06:33.360> can 00:06:33.469 --> 00:06:33.479 align:start position:0% message to chain B and then I can 00:06:33.479 --> 00:06:36.150 align:start position:0% message to chain B and then I can release<00:06:33.800> my<00:06:33.960> funds<00:06:34.319> back<00:06:34.440> to<00:06:34.599> the<00:06:34.919> user<00:06:35.919> and<00:06:36.000> so 00:06:36.150 --> 00:06:36.160 align:start position:0% release my funds back to the user and so 00:06:36.160 --> 00:06:38.790 align:start position:0% release my funds back to the user and so this<00:06:36.280> flow<00:06:36.520> is<00:06:36.639> all<00:06:36.919> fine<00:06:37.080> and<00:06:37.319> good<00:06:38.080> um<00:06:38.479> maybe 00:06:38.790 --> 00:06:38.800 align:start position:0% this flow is all fine and good um maybe 00:06:38.800 --> 00:06:40.510 align:start position:0% this flow is all fine and good um maybe I<00:06:38.919> have<00:06:39.080> some<00:06:39.319> security<00:06:39.759> assumptions<00:06:40.240> around 00:06:40.510 --> 00:06:40.520 align:start position:0% I have some security assumptions around 00:06:40.520 --> 00:06:41.870 align:start position:0% I have some security assumptions around how<00:06:40.639> I'm<00:06:40.759> sending<00:06:41.039> this<00:06:41.240> message<00:06:41.560> maybe<00:06:41.759> I 00:06:41.870 --> 00:06:41.880 align:start position:0% how I'm sending this message maybe I 00:06:41.880 --> 00:06:43.990 align:start position:0% how I'm sending this message maybe I don't<00:06:42.080> love<00:06:42.360> those<00:06:43.080> but<00:06:43.240> generally<00:06:43.639> speaking 00:06:43.990 --> 00:06:44.000 align:start position:0% don't love those but generally speaking 00:06:44.000 --> 00:06:45.070 align:start position:0% don't love those but generally speaking like<00:06:44.160> this<00:06:44.319> architecture<00:06:44.800> is<00:06:44.960> like 00:06:45.070 --> 00:06:45.080 align:start position:0% like this architecture is like 00:06:45.080 --> 00:06:47.670 align:start position:0% like this architecture is like conceptually<00:06:45.680> simple<00:06:46.599> the<00:06:46.800> problem<00:06:47.160> is<00:06:47.479> it's 00:06:47.670 --> 00:06:47.680 align:start position:0% conceptually simple the problem is it's 00:06:47.680 --> 00:06:51.070 align:start position:0% conceptually simple the problem is it's just<00:06:48.280> slow<00:06:49.280> um<00:06:49.560> I<00:06:49.680> have<00:06:49.759> to<00:06:49.919> wait<00:06:50.080> for<00:06:50.479> finality 00:06:51.070 --> 00:06:51.080 align:start position:0% just slow um I have to wait for finality 00:06:51.080 --> 00:06:53.070 align:start position:0% just slow um I have to wait for finality or<00:06:51.199> at<00:06:51.280> least<00:06:51.400> a<00:06:51.560> sense<00:06:51.720> of<00:06:51.880> it<00:06:52.560> I<00:06:52.680> can't<00:06:52.919> get 00:06:53.070 --> 00:06:53.080 align:start position:0% or at least a sense of it I can't get 00:06:53.080 --> 00:06:54.670 align:start position:0% or at least a sense of it I can't get the<00:06:53.199> two<00:06:53.560> second<00:06:53.880> experience<00:06:54.440> with<00:06:54.560> this 00:06:54.670 --> 00:06:54.680 align:start position:0% the two second experience with this 00:06:54.680 --> 00:06:56.749 align:start position:0% the two second experience with this traditional<00:06:55.080> Bridge 00:06:56.749 --> 00:06:56.759 align:start position:0% traditional Bridge 00:06:56.759 --> 00:06:58.950 align:start position:0% traditional Bridge architecture<00:06:57.759> so<00:06:57.919> how<00:06:58.000> do<00:06:58.160> intents<00:06:58.599> work<00:06:58.879> how 00:06:58.950 --> 00:06:58.960 align:start position:0% architecture so how do intents work how 00:06:58.960 --> 00:07:00.589 align:start position:0% architecture so how do intents work how are<00:06:59.080> they<00:06:59.199> different 00:07:00.589 --> 00:07:00.599 align:start position:0% are they different 00:07:00.599 --> 00:07:03.029 align:start position:0% are they different intense<00:07:01.599> I<00:07:01.720> still<00:07:01.919> have<00:07:02.080> users<00:07:02.560> deposit 00:07:03.029 --> 00:07:03.039 align:start position:0% intense I still have users deposit 00:07:03.039 --> 00:07:05.430 align:start position:0% intense I still have users deposit assets<00:07:03.319> On<00:07:03.440> the<00:07:03.520> Origin<00:07:03.840> chain<00:07:04.199> I<00:07:04.280> need<00:07:04.599> that 00:07:05.430 --> 00:07:05.440 align:start position:0% assets On the Origin chain I need that 00:07:05.440 --> 00:07:07.189 align:start position:0% assets On the Origin chain I need that but<00:07:05.680> when<00:07:05.840> they're<00:07:06.120> depositing<00:07:06.639> assets<00:07:07.039> they 00:07:07.189 --> 00:07:07.199 align:start position:0% but when they're depositing assets they 00:07:07.199 --> 00:07:09.390 align:start position:0% but when they're depositing assets they go<00:07:07.440> they<00:07:07.560> get<00:07:07.759> escrowed<00:07:08.319> into<00:07:08.560> a<00:07:08.720> special 00:07:09.390 --> 00:07:09.400 align:start position:0% go they get escrowed into a special 00:07:09.400 --> 00:07:12.390 align:start position:0% go they get escrowed into a special account<00:07:10.400> that<00:07:10.639> broadcasts<00:07:11.360> the<00:07:11.520> intent<00:07:12.080> to<00:07:12.280> a 00:07:12.390 --> 00:07:12.400 align:start position:0% account that broadcasts the intent to a 00:07:12.400 --> 00:07:13.309 align:start position:0% account that broadcasts the intent to a network<00:07:12.680> of 00:07:13.309 --> 00:07:13.319 align:start position:0% network of 00:07:13.319 --> 00:07:15.589 align:start position:0% network of solvers<00:07:14.319> and<00:07:14.440> this<00:07:14.560> network<00:07:14.840> of<00:07:14.919> solvers<00:07:15.360> are 00:07:15.589 --> 00:07:15.599 align:start position:0% solvers and this network of solvers are 00:07:15.599 --> 00:07:18.830 align:start position:0% solvers and this network of solvers are going<00:07:15.840> to<00:07:16.160> then<00:07:16.879> compete<00:07:17.879> to<00:07:18.080> fill<00:07:18.400> the<00:07:18.520> user 00:07:18.830 --> 00:07:18.840 align:start position:0% going to then compete to fill the user 00:07:18.840 --> 00:07:21.270 align:start position:0% going to then compete to fill the user on<00:07:19.000> the<00:07:19.120> destination<00:07:19.599> chain<00:07:20.560> um<00:07:20.759> importantly 00:07:21.270 --> 00:07:21.280 align:start position:0% on the destination chain um importantly 00:07:21.280 --> 00:07:22.469 align:start position:0% on the destination chain um importantly they're<00:07:21.440> filling<00:07:21.720> the<00:07:21.800> user<00:07:22.039> with<00:07:22.120> their<00:07:22.280> own 00:07:22.469 --> 00:07:22.479 align:start position:0% they're filling the user with their own 00:07:22.479 --> 00:07:24.430 align:start position:0% they're filling the user with their own funds<00:07:23.360> so<00:07:23.599> what<00:07:23.720> these<00:07:23.879> guys<00:07:24.039> are<00:07:24.160> doing<00:07:24.360> is 00:07:24.430 --> 00:07:24.440 align:start position:0% funds so what these guys are doing is 00:07:24.440 --> 00:07:26.469 align:start position:0% funds so what these guys are doing is there<00:07:24.639> actually<00:07:24.840> a<00:07:25.160> Marketplace<00:07:26.160> that's 00:07:26.469 --> 00:07:26.479 align:start position:0% there actually a Marketplace that's 00:07:26.479 --> 00:07:28.270 align:start position:0% there actually a Marketplace that's taking<00:07:26.759> on<00:07:27.000> the<00:07:27.120> finality<00:07:27.720> risk<00:07:28.000> of<00:07:28.160> the 00:07:28.270 --> 00:07:28.280 align:start position:0% taking on the finality risk of the 00:07:28.280 --> 00:07:30.710 align:start position:0% taking on the finality risk of the origin<00:07:28.680> chain<00:07:29.520> and<00:07:29.599> they're<00:07:29.840> competing<00:07:30.560> to 00:07:30.710 --> 00:07:30.720 align:start position:0% origin chain and they're competing to 00:07:30.720 --> 00:07:32.390 align:start position:0% origin chain and they're competing to see<00:07:30.919> who's<00:07:31.120> going<00:07:31.240> to<00:07:31.319> be<00:07:31.440> the<00:07:31.599> first<00:07:31.840> one<00:07:32.280> to 00:07:32.390 --> 00:07:32.400 align:start position:0% see who's going to be the first one to 00:07:32.400 --> 00:07:34.950 align:start position:0% see who's going to be the first one to fill<00:07:32.680> the<00:07:32.840> user<00:07:33.680> um<00:07:33.879> in<00:07:34.080> exchange<00:07:34.440> for<00:07:34.639> the<00:07:34.840> the 00:07:34.950 --> 00:07:34.960 align:start position:0% fill the user um in exchange for the the 00:07:34.960 --> 00:07:37.749 align:start position:0% fill the user um in exchange for the the transaction<00:07:35.440> fee<00:07:35.800> or<00:07:35.919> the<00:07:36.039> fee<00:07:36.240> charged<00:07:36.759> here 00:07:37.749 --> 00:07:37.759 align:start position:0% transaction fee or the fee charged here 00:07:37.759 --> 00:07:39.350 align:start position:0% transaction fee or the fee charged here and<00:07:38.039> this<00:07:38.199> architecture<00:07:38.759> if<00:07:38.840> you<00:07:38.960> notice 00:07:39.350 --> 00:07:39.360 align:start position:0% and this architecture if you notice 00:07:39.360 --> 00:07:40.749 align:start position:0% and this architecture if you notice there's<00:07:39.560> no<00:07:39.840> message<00:07:40.240> that<00:07:40.360> gets<00:07:40.520> sent 00:07:40.749 --> 00:07:40.759 align:start position:0% there's no message that gets sent 00:07:40.759 --> 00:07:43.189 align:start position:0% there's no message that gets sent between<00:07:41.240> chains<00:07:42.240> um<00:07:42.400> and<00:07:42.479> the<00:07:42.560> finality<00:07:43.000> risk 00:07:43.189 --> 00:07:43.199 align:start position:0% between chains um and the finality risk 00:07:43.199 --> 00:07:44.710 align:start position:0% between chains um and the finality risk is<00:07:43.360> then<00:07:43.560> being<00:07:43.759> taken<00:07:43.960> on<00:07:44.120> by<00:07:44.240> the<00:07:44.360> solver 00:07:44.710 --> 00:07:44.720 align:start position:0% is then being taken on by the solver 00:07:44.720 --> 00:07:47.869 align:start position:0% is then being taken on by the solver Network<00:07:45.639> so<00:07:45.919> this<00:07:46.039> is<00:07:46.639> fast<00:07:47.240> we<00:07:47.360> can<00:07:47.479> fill<00:07:47.759> the 00:07:47.869 --> 00:07:47.879 align:start position:0% Network so this is fast we can fill the 00:07:47.879 --> 00:07:50.550 align:start position:0% Network so this is fast we can fill the users<00:07:48.240> in<00:07:48.479> in<00:07:48.639> two<00:07:49.039> seconds<00:07:50.039> um<00:07:50.159> and<00:07:50.240> the<00:07:50.360> user 00:07:50.550 --> 00:07:50.560 align:start position:0% users in in two seconds um and the user 00:07:50.560 --> 00:07:51.869 align:start position:0% users in in two seconds um and the user can<00:07:50.680> move<00:07:50.840> on<00:07:50.960> with<00:07:51.080> their<00:07:51.240> day<00:07:51.599> and<00:07:51.680> we 00:07:51.869 --> 00:07:51.879 align:start position:0% can move on with their day and we 00:07:51.879 --> 00:07:53.589 align:start position:0% can move on with their day and we achieve<00:07:52.280> this<00:07:52.479> fast<00:07:52.680> interrupt<00:07:53.280> that<00:07:53.400> can 00:07:53.589 --> 00:07:53.599 align:start position:0% achieve this fast interrupt that can 00:07:53.599 --> 00:07:55.629 align:start position:0% achieve this fast interrupt that can help<00:07:53.800> us<00:07:54.039> unify 00:07:55.629 --> 00:07:55.639 align:start position:0% help us unify 00:07:55.639 --> 00:07:57.469 align:start position:0% help us unify ethereum<00:07:56.639> of<00:07:56.759> course<00:07:56.919> there's<00:07:57.120> still<00:07:57.280> one 00:07:57.469 --> 00:07:57.479 align:start position:0% ethereum of course there's still one 00:07:57.479 --> 00:07:59.029 align:start position:0% ethereum of course there's still one step<00:07:57.759> after<00:07:58.000> this<00:07:58.360> after<00:07:58.560> the<00:07:58.639> user<00:07:58.879> gets 00:07:59.029 --> 00:07:59.039 align:start position:0% step after this after the user gets 00:07:59.039 --> 00:08:01.749 align:start position:0% step after this after the user gets filled<00:07:59.720> we<00:07:59.840> still<00:08:00.000> need<00:08:00.159> to<00:08:00.560> verify<00:08:01.560> uh<00:08:01.680> that 00:08:01.749 --> 00:08:01.759 align:start position:0% filled we still need to verify uh that 00:08:01.759 --> 00:08:03.830 align:start position:0% filled we still need to verify uh that the<00:08:01.879> fill<00:08:02.199> happened<00:08:02.599> and<00:08:02.759> release<00:08:03.159> funds<00:08:03.639> back 00:08:03.830 --> 00:08:03.840 align:start position:0% the fill happened and release funds back 00:08:03.840 --> 00:08:06.390 align:start position:0% the fill happened and release funds back to<00:08:04.199> the<00:08:04.319> solver<00:08:05.319> um<00:08:05.440> but<00:08:05.560> we<00:08:05.680> have<00:08:05.879> time<00:08:06.039> to<00:08:06.240> do 00:08:06.390 --> 00:08:06.400 align:start position:0% to the solver um but we have time to do 00:08:06.400 --> 00:08:08.629 align:start position:0% to the solver um but we have time to do that<00:08:06.639> because<00:08:06.800> the<00:08:06.879> user<00:08:07.120> got<00:08:07.280> their<00:08:07.520> fast 00:08:08.629 --> 00:08:08.639 align:start position:0% that because the user got their fast 00:08:08.639 --> 00:08:12.110 align:start position:0% that because the user got their fast fill<00:08:09.639> so<00:08:09.879> across<00:08:10.879> um<00:08:11.199> you<00:08:11.319> know<00:08:11.560> I'm<00:08:11.720> slightly 00:08:12.110 --> 00:08:12.120 align:start position:0% fill so across um you know I'm slightly 00:08:12.120 --> 00:08:13.830 align:start position:0% fill so across um you know I'm slightly biased<00:08:12.560> but<00:08:12.720> I<00:08:12.800> do<00:08:12.960> think<00:08:13.120> across<00:08:13.560> is<00:08:13.680> the 00:08:13.830 --> 00:08:13.840 align:start position:0% biased but I do think across is the 00:08:13.840 --> 00:08:16.990 align:start position:0% biased but I do think across is the leading<00:08:14.440> intent-based<00:08:14.919> interop<00:08:15.879> protocol<00:08:16.879> um 00:08:16.990 --> 00:08:17.000 align:start position:0% leading intent-based interop protocol um 00:08:17.000 --> 00:08:19.070 align:start position:0% leading intent-based interop protocol um today<00:08:17.280> in<00:08:17.440> production<00:08:18.440> uh<00:08:18.720> how<00:08:18.800> many<00:08:18.960> people 00:08:19.070 --> 00:08:19.080 align:start position:0% today in production uh how many people 00:08:19.080 --> 00:08:20.350 align:start position:0% today in production uh how many people in<00:08:19.159> the<00:08:19.199> audience<00:08:19.440> have<00:08:19.520> used<00:08:19.720> AC<00:08:19.879> cross<00:08:20.240> I'm 00:08:20.350 --> 00:08:20.360 align:start position:0% in the audience have used AC cross I'm 00:08:20.360 --> 00:08:22.350 align:start position:0% in the audience have used AC cross I'm actually<00:08:20.560> kind<00:08:20.680> of<00:08:20.800> curious<00:08:21.639> all<00:08:22.080> that<00:08:22.159> makes 00:08:22.350 --> 00:08:22.360 align:start position:0% actually kind of curious all that makes 00:08:22.360 --> 00:08:26.029 align:start position:0% actually kind of curious all that makes me<00:08:22.440> feel<00:08:22.680> good<00:08:23.319> okay<00:08:23.960> um<00:08:24.280> so<00:08:25.000> across<00:08:25.720> uh<00:08:25.879> we 00:08:26.029 --> 00:08:26.039 align:start position:0% me feel good okay um so across uh we 00:08:26.039 --> 00:08:29.629 align:start position:0% me feel good okay um so across uh we were<00:08:26.159> bridging<00:08:26.520> protocol<00:08:27.560> um<00:08:28.560> if<00:08:28.720> you<00:08:29.039> go<00:08:29.240> and 00:08:29.629 --> 00:08:29.639 align:start position:0% were bridging protocol um if you go and 00:08:29.639 --> 00:08:31.270 align:start position:0% were bridging protocol um if you go and those<00:08:29.759> that<00:08:29.960> haven't<00:08:30.280> if<00:08:30.360> you<00:08:30.440> go<00:08:30.520> to<00:08:30.639> across. 00:08:31.270 --> 00:08:31.280 align:start position:0% those that haven't if you go to across. 00:08:31.280 --> 00:08:33.709 align:start position:0% those that haven't if you go to across. two<00:08:31.879> and<00:08:32.039> bridge<00:08:32.399> between<00:08:32.760> arbitrum<00:08:33.279> and<00:08:33.399> base 00:08:33.709 --> 00:08:33.719 align:start position:0% two and bridge between arbitrum and base 00:08:33.719 --> 00:08:35.750 align:start position:0% two and bridge between arbitrum and base your<00:08:33.839> fill<00:08:34.200> time<00:08:34.399> will<00:08:34.599> be<00:08:35.080> less<00:08:35.320> than<00:08:35.479> three 00:08:35.750 --> 00:08:35.760 align:start position:0% your fill time will be less than three 00:08:35.760 --> 00:08:38.269 align:start position:0% your fill time will be less than three seconds<00:08:36.479> our<00:08:36.680> median<00:08:37.080> fill<00:08:37.399> time<00:08:37.800> is<00:08:38.000> 3 00:08:38.269 --> 00:08:38.279 align:start position:0% seconds our median fill time is 3 00:08:38.279 --> 00:08:40.790 align:start position:0% seconds our median fill time is 3 seconds<00:08:38.959> and<00:08:39.080> we're<00:08:39.479> keep<00:08:39.680> lowering<00:08:40.159> that<00:08:40.640> as 00:08:40.790 --> 00:08:40.800 align:start position:0% seconds and we're keep lowering that as 00:08:40.800 --> 00:08:43.070 align:start position:0% seconds and we're keep lowering that as block<00:08:41.120> CH<00:08:41.519> block<00:08:41.839> times<00:08:42.039> on<00:08:42.159> l2s<00:08:42.599> get<00:08:42.760> faster 00:08:43.070 --> 00:08:43.080 align:start position:0% block CH block times on l2s get faster 00:08:43.080 --> 00:08:44.790 align:start position:0% block CH block times on l2s get faster it's<00:08:43.200> going<00:08:43.279> to<00:08:43.399> get<00:08:43.479> cheaper<00:08:43.719> and<00:08:43.839> cheaper 00:08:44.790 --> 00:08:44.800 align:start position:0% it's going to get cheaper and cheaper 00:08:44.800 --> 00:08:47.829 align:start position:0% it's going to get cheaper and cheaper for<00:08:45.040> transactions<00:08:45.800> less<00:08:46.000> than<00:08:46.560> $10,000<00:08:47.560> our 00:08:47.829 --> 00:08:47.839 align:start position:0% for transactions less than $10,000 our 00:08:47.839 --> 00:08:50.590 align:start position:0% for transactions less than $10,000 our average<00:08:48.279> cost<00:08:48.640> is<00:08:48.959> less<00:08:49.160> than<00:08:49.320> 4<00:08:49.600> cents<00:08:50.440> um 00:08:50.590 --> 00:08:50.600 align:start position:0% average cost is less than 4 cents um 00:08:50.600 --> 00:08:52.269 align:start position:0% average cost is less than 4 cents um it's<00:08:50.800> extremely<00:08:51.240> cheap<00:08:51.800> and<00:08:51.920> there's<00:08:52.080> room 00:08:52.269 --> 00:08:52.279 align:start position:0% it's extremely cheap and there's room 00:08:52.279 --> 00:08:54.230 align:start position:0% it's extremely cheap and there's room for<00:08:52.440> this<00:08:52.519> to<00:08:52.640> get<00:08:52.800> cheaper<00:08:53.120> too<00:08:53.920> and<00:08:54.080> we've 00:08:54.230 --> 00:08:54.240 align:start position:0% for this to get cheaper too and we've 00:08:54.240 --> 00:08:55.870 align:start position:0% for this to get cheaper too and we've done<00:08:54.480> billions<00:08:54.959> billions<00:08:55.279> of<00:08:55.440> dollars<00:08:55.720> in 00:08:55.870 --> 00:08:55.880 align:start position:0% done billions billions of dollars in 00:08:55.880 --> 00:08:57.509 align:start position:0% done billions billions of dollars in volume<00:08:56.320> you<00:08:56.440> know<00:08:56.560> today<00:08:56.839> I<00:08:56.920> think<00:08:57.040> we<00:08:57.120> did<00:08:57.279> 50 00:08:57.509 --> 00:08:57.519 align:start position:0% volume you know today I think we did 50 00:08:57.519 --> 00:08:58.829 align:start position:0% volume you know today I think we did 50 million<00:08:57.760> in<00:08:57.920> volume<00:08:58.200> with<00:08:58.320> 50,000 00:08:58.829 --> 00:08:58.839 align:start position:0% million in volume with 50,000 00:08:58.839 --> 00:09:01.750 align:start position:0% million in volume with 50,000 transactions<00:08:59.519> and<00:08:59.640> it's<00:08:59.959> growing<00:09:00.959> so<00:09:01.600> this 00:09:01.750 --> 00:09:01.760 align:start position:0% transactions and it's growing so this 00:09:01.760 --> 00:09:03.110 align:start position:0% transactions and it's growing so this works<00:09:02.000> in<00:09:02.200> production<00:09:02.640> this<00:09:02.720> isn't<00:09:02.959> a 00:09:03.110 --> 00:09:03.120 align:start position:0% works in production this isn't a 00:09:03.120 --> 00:09:06.310 align:start position:0% works in production this isn't a theoretical<00:09:03.839> architecture<00:09:04.760> this<00:09:04.880> is 00:09:06.310 --> 00:09:06.320 align:start position:0% theoretical architecture this is 00:09:06.320 --> 00:09:09.829 align:start position:0% theoretical architecture this is working<00:09:07.320> but<00:09:07.640> you<00:09:07.760> know<00:09:08.320> we<00:09:09.320> we're<00:09:09.480> looking<00:09:09.720> at 00:09:09.829 --> 00:09:09.839 align:start position:0% working but you know we we're looking at 00:09:09.839 --> 00:09:11.430 align:start position:0% working but you know we we're looking at AC<00:09:10.000> cross<00:09:10.279> and<00:09:10.519> I<00:09:10.600> don't<00:09:10.880> believe<00:09:11.279> that 00:09:11.430 --> 00:09:11.440 align:start position:0% AC cross and I don't believe that 00:09:11.440 --> 00:09:12.990 align:start position:0% AC cross and I don't believe that interoperability<00:09:12.279> is<00:09:12.399> going<00:09:12.480> to<00:09:12.560> be<00:09:12.640> solved 00:09:12.990 --> 00:09:13.000 align:start position:0% interoperability is going to be solved 00:09:13.000 --> 00:09:15.550 align:start position:0% interoperability is going to be solved by<00:09:13.120> one<00:09:13.399> protocol<00:09:14.399> like<00:09:14.600> sure<00:09:14.959> I<00:09:15.040> might<00:09:15.240> like 00:09:15.550 --> 00:09:15.560 align:start position:0% by one protocol like sure I might like 00:09:15.560 --> 00:09:17.790 align:start position:0% by one protocol like sure I might like that<00:09:15.800> but<00:09:15.959> I<00:09:16.040> don't<00:09:16.240> think<00:09:16.440> that's<00:09:16.640> the<00:09:16.880> path 00:09:17.790 --> 00:09:17.800 align:start position:0% that but I don't think that's the path 00:09:17.800 --> 00:09:19.430 align:start position:0% that but I don't think that's the path and<00:09:18.000> go<00:09:18.160> back<00:09:18.320> and<00:09:18.480> think<00:09:18.640> about<00:09:18.880> the<00:09:19.000> rollup 00:09:19.430 --> 00:09:19.440 align:start position:0% and go back and think about the rollup 00:09:19.440 --> 00:09:21.150 align:start position:0% and go back and think about the rollup Centric<00:09:19.720> road<00:09:19.959> map<00:09:20.200> that<00:09:20.360> vitalic<00:09:20.800> set<00:09:21.000> for 00:09:21.150 --> 00:09:21.160 align:start position:0% Centric road map that vitalic set for 00:09:21.160 --> 00:09:24.269 align:start position:0% Centric road map that vitalic set for scaling<00:09:21.560> ethereum<00:09:22.440> it<00:09:22.600> wasn't<00:09:22.920> solved<00:09:23.399> by<00:09:23.680> one 00:09:24.269 --> 00:09:24.279 align:start position:0% scaling ethereum it wasn't solved by one 00:09:24.279 --> 00:09:26.030 align:start position:0% scaling ethereum it wasn't solved by one team<00:09:24.680> it<00:09:24.800> wasn't<00:09:25.000> solved<00:09:25.320> by<00:09:25.480> optimism<00:09:25.959> it 00:09:26.030 --> 00:09:26.040 align:start position:0% team it wasn't solved by optimism it 00:09:26.040 --> 00:09:27.190 align:start position:0% team it wasn't solved by optimism it wasn't<00:09:26.240> solved<00:09:26.440> by<00:09:26.519> arbitrum<00:09:26.959> it<00:09:27.040> wasn't 00:09:27.190 --> 00:09:27.200 align:start position:0% wasn't solved by arbitrum it wasn't 00:09:27.200 --> 00:09:28.670 align:start position:0% wasn't solved by arbitrum it wasn't solved<00:09:27.399> by<00:09:27.519> ZK<00:09:27.839> sync<00:09:28.360> it<00:09:28.440> was<00:09:28.560> an 00:09:28.670 --> 00:09:28.680 align:start position:0% solved by ZK sync it was an 00:09:28.680 --> 00:09:29.870 align:start position:0% solved by ZK sync it was an architectural<00:09:29.160> decis<00:09:29.440> ision<00:09:29.600> that<00:09:29.720> many 00:09:29.870 --> 00:09:29.880 align:start position:0% architectural decis ision that many 00:09:29.880 --> 00:09:31.910 align:start position:0% architectural decis ision that many teams<00:09:30.120> innovated<00:09:30.560> on<00:09:31.279> and<00:09:31.399> I<00:09:31.480> think<00:09:31.640> the<00:09:31.760> same 00:09:31.910 --> 00:09:31.920 align:start position:0% teams innovated on and I think the same 00:09:31.920 --> 00:09:34.470 align:start position:0% teams innovated on and I think the same is<00:09:32.040> true<00:09:32.200> for<00:09:32.640> interop<00:09:33.640> um<00:09:33.839> and<00:09:33.920> so<00:09:34.079> to<00:09:34.279> make 00:09:34.470 --> 00:09:34.480 align:start position:0% is true for interop um and so to make 00:09:34.480 --> 00:09:37.470 align:start position:0% is true for interop um and so to make this<00:09:34.640> intent<00:09:35.560> architecture<00:09:36.560> uh<00:09:36.800> really<00:09:37.200> like 00:09:37.470 --> 00:09:37.480 align:start position:0% this intent architecture uh really like 00:09:37.480 --> 00:09:40.990 align:start position:0% this intent architecture uh really like win<00:09:38.000> we<00:09:38.120> got<00:09:38.240> to<00:09:38.399> define<00:09:38.640> a<00:09:38.839> standard<00:09:39.800> um<00:09:40.800> and 00:09:40.990 --> 00:09:41.000 align:start position:0% win we got to define a standard um and 00:09:41.000 --> 00:09:42.949 align:start position:0% win we got to define a standard um and so<00:09:41.440> we<00:09:41.560> worked<00:09:41.959> together<00:09:42.240> the<00:09:42.440> cross<00:09:42.720> team 00:09:42.949 --> 00:09:42.959 align:start position:0% so we worked together the cross team 00:09:42.959 --> 00:09:44.750 align:start position:0% so we worked together the cross team worked<00:09:43.240> with<00:09:43.360> the<00:09:43.480> Unis<00:09:43.800> swap<00:09:44.040> team<00:09:44.560> to 00:09:44.750 --> 00:09:44.760 align:start position:0% worked with the Unis swap team to 00:09:44.760 --> 00:09:47.350 align:start position:0% worked with the Unis swap team to develop<00:09:45.079> your<00:09:45.680> 7683<00:09:46.680> which<00:09:46.760> is<00:09:46.880> a<00:09:47.040> standard 00:09:47.350 --> 00:09:47.360 align:start position:0% develop your 7683 which is a standard 00:09:47.360 --> 00:09:49.509 align:start position:0% develop your 7683 which is a standard for<00:09:47.560> cross<00:09:47.839> chain<00:09:48.079> intents<00:09:49.079> um<00:09:49.240> it's<00:09:49.360> not 00:09:49.509 --> 00:09:49.519 align:start position:0% for cross chain intents um it's not 00:09:49.519 --> 00:09:51.269 align:start position:0% for cross chain intents um it's not owned<00:09:49.760> by<00:09:49.880> across<00:09:50.360> it's<00:09:50.480> not<00:09:50.600> owned<00:09:50.839> by<00:09:50.920> Unis 00:09:51.269 --> 00:09:51.279 align:start position:0% owned by across it's not owned by Unis 00:09:51.279 --> 00:09:54.670 align:start position:0% owned by across it's not owned by Unis swap<00:09:51.519> it<00:09:51.600> is<00:09:51.720> a<00:09:51.959> true<00:09:52.680> uh<00:09:53.000> ERC<00:09:54.000> uh<00:09:54.160> that's<00:09:54.560> a 00:09:54.670 --> 00:09:54.680 align:start position:0% swap it is a true uh ERC uh that's a 00:09:54.680 --> 00:09:55.870 align:start position:0% swap it is a true uh ERC uh that's a public 00:09:55.870 --> 00:09:55.880 align:start position:0% public 00:09:55.880 --> 00:09:59.110 align:start position:0% public good<00:09:56.880> and<00:09:57.000> it's<00:09:57.160> worth<00:09:57.399> going<00:09:57.640> into<00:09:58.040> like<00:09:58.600> hey 00:09:59.110 --> 00:09:59.120 align:start position:0% good and it's worth going into like hey 00:09:59.120 --> 00:10:01.190 align:start position:0% good and it's worth going into like hey what<00:09:59.720> what<00:09:59.839> does<00:10:00.079> this<00:10:00.279> thing<00:10:00.480> do<00:10:00.880> what<00:10:01.000> is 00:10:01.190 --> 00:10:01.200 align:start position:0% what what does this thing do what is 00:10:01.200 --> 00:10:04.829 align:start position:0% what what does this thing do what is this<00:10:01.600> ERC<00:10:02.600> um<00:10:03.120> and<00:10:03.279> my<00:10:03.399> mental<00:10:03.800> model<00:10:04.399> the<00:10:04.560> way 00:10:04.829 --> 00:10:04.839 align:start position:0% this ERC um and my mental model the way 00:10:04.839 --> 00:10:06.430 align:start position:0% this ERC um and my mental model the way I<00:10:05.000> I<00:10:05.160> kind<00:10:05.279> of<00:10:05.560> think<00:10:05.760> y<00:10:05.920> all<00:10:06.079> should<00:10:06.279> think 00:10:06.430 --> 00:10:06.440 align:start position:0% I I kind of think y all should think 00:10:06.440 --> 00:10:09.670 align:start position:0% I I kind of think y all should think about<00:10:06.720> this<00:10:07.360> is<00:10:07.480> it's<00:10:07.680> like<00:10:07.760> an<00:10:07.880> order<00:10:08.680> ticket 00:10:09.670 --> 00:10:09.680 align:start position:0% about this is it's like an order ticket 00:10:09.680 --> 00:10:11.870 align:start position:0% about this is it's like an order ticket um<00:10:10.120> you<00:10:10.240> can<00:10:10.480> almost<00:10:10.839> imagine<00:10:11.240> this<00:10:11.399> if<00:10:11.519> we<00:10:11.640> go 00:10:11.870 --> 00:10:11.880 align:start position:0% um you can almost imagine this if we go 00:10:11.880 --> 00:10:15.190 align:start position:0% um you can almost imagine this if we go way<00:10:12.120> back<00:10:12.360> like<00:10:12.560> 1980s<00:10:13.480> Finance<00:10:14.160> like<00:10:14.600> w<00:10:14.959> Wolf 00:10:15.190 --> 00:10:15.200 align:start position:0% way back like 1980s Finance like w Wolf 00:10:15.200 --> 00:10:17.630 align:start position:0% way back like 1980s Finance like w Wolf of<00:10:15.360> Wall<00:10:15.560> Street<00:10:15.839> stuff<00:10:16.640> you<00:10:16.880> like<00:10:17.320> had<00:10:17.440> a 00:10:17.630 --> 00:10:17.640 align:start position:0% of Wall Street stuff you like had a 00:10:17.640 --> 00:10:19.269 align:start position:0% of Wall Street stuff you like had a paper<00:10:17.959> order<00:10:18.320> ticket<00:10:18.640> that<00:10:18.760> your<00:10:18.920> broker 00:10:19.269 --> 00:10:19.279 align:start position:0% paper order ticket that your broker 00:10:19.279 --> 00:10:21.470 align:start position:0% paper order ticket that your broker filled<00:10:19.640> out<00:10:19.880> with<00:10:20.079> like<00:10:20.279> I<00:10:20.360> want<00:10:20.480> to<00:10:20.959> you<00:10:21.079> know 00:10:21.470 --> 00:10:21.480 align:start position:0% filled out with like I want to you know 00:10:21.480 --> 00:10:23.710 align:start position:0% filled out with like I want to you know sell<00:10:21.880> Apple<00:10:22.200> stock<00:10:22.519> and<00:10:22.680> buy<00:10:22.959> Google<00:10:23.360> stock 00:10:23.710 --> 00:10:23.720 align:start position:0% sell Apple stock and buy Google stock 00:10:23.720 --> 00:10:25.190 align:start position:0% sell Apple stock and buy Google stock although<00:10:24.040> Apple<00:10:24.279> and<00:10:24.399> Google<00:10:24.640> didn't<00:10:24.920> exist 00:10:25.190 --> 00:10:25.200 align:start position:0% although Apple and Google didn't exist 00:10:25.200 --> 00:10:26.509 align:start position:0% although Apple and Google didn't exist back<00:10:25.320> then<00:10:25.480> but<00:10:25.600> you<00:10:25.680> get<00:10:25.800> what<00:10:25.880> I'm<00:10:26.000> saying 00:10:26.509 --> 00:10:26.519 align:start position:0% back then but you get what I'm saying 00:10:26.519 --> 00:10:28.069 align:start position:0% back then but you get what I'm saying and<00:10:26.600> then<00:10:26.720> they'd<00:10:26.920> like<00:10:27.160> send<00:10:27.399> it<00:10:27.480> to<00:10:27.600> a<00:10:27.720> floor 00:10:28.069 --> 00:10:28.079 align:start position:0% and then they'd like send it to a floor 00:10:28.079 --> 00:10:29.550 align:start position:0% and then they'd like send it to a floor floor<00:10:28.440> and<00:10:28.600> some<00:10:28.760> guy<00:10:28.880> on<00:10:28.920> the<00:10:29.000> trading<00:10:29.399> flow 00:10:29.550 --> 00:10:29.560 align:start position:0% floor and some guy on the trading flow 00:10:29.560 --> 00:10:31.230 align:start position:0% floor and some guy on the trading flow would<00:10:29.680> make<00:10:29.839> like<00:10:30.040> hand<00:10:30.320> signals<00:10:30.760> to<00:10:30.880> go<00:10:31.000> and 00:10:31.230 --> 00:10:31.240 align:start position:0% would make like hand signals to go and 00:10:31.240 --> 00:10:34.269 align:start position:0% would make like hand signals to go and like<00:10:31.760> execute<00:10:32.160> the<00:10:32.760> thing<00:10:33.760> but<00:10:33.920> they<00:10:34.040> had<00:10:34.120> a 00:10:34.269 --> 00:10:34.279 align:start position:0% like execute the thing but they had a 00:10:34.279 --> 00:10:35.990 align:start position:0% like execute the thing but they had a format<00:10:34.640> they<00:10:34.760> had<00:10:34.839> a<00:10:35.040> standard<00:10:35.480> for<00:10:35.639> how<00:10:35.800> they 00:10:35.990 --> 00:10:36.000 align:start position:0% format they had a standard for how they 00:10:36.000 --> 00:10:39.030 align:start position:0% format they had a standard for how they express<00:10:36.480> this<00:10:36.639> trade<00:10:37.279> ticket<00:10:38.279> um<00:10:38.680> and<00:10:38.760> so<00:10:38.959> you 00:10:39.030 --> 00:10:39.040 align:start position:0% express this trade ticket um and so you 00:10:39.040 --> 00:10:41.670 align:start position:0% express this trade ticket um and so you can<00:10:39.200> think<00:10:39.399> about<00:10:39.720> ERC<00:10:40.200> 7683<00:10:41.040> is<00:10:41.160> defining<00:10:41.519> a 00:10:41.670 --> 00:10:41.680 align:start position:0% can think about ERC 7683 is defining a 00:10:41.680 --> 00:10:44.269 align:start position:0% can think about ERC 7683 is defining a common<00:10:42.079> format<00:10:43.000> to<00:10:43.320> express<00:10:43.760> this<00:10:43.920> user 00:10:44.269 --> 00:10:44.279 align:start position:0% common format to express this user 00:10:44.279 --> 00:10:47.990 align:start position:0% common format to express this user intent<00:10:45.279> this<00:10:45.440> trade<00:10:46.120> ticket<00:10:47.120> and<00:10:47.440> what<00:10:47.560> you<00:10:47.680> do 00:10:47.990 --> 00:10:48.000 align:start position:0% intent this trade ticket and what you do 00:10:48.000 --> 00:10:49.829 align:start position:0% intent this trade ticket and what you do what<00:10:48.120> a<00:10:48.279> developer<00:10:48.920> does<00:10:49.200> is<00:10:49.399> they<00:10:49.519> go<00:10:49.720> and 00:10:49.829 --> 00:10:49.839 align:start position:0% what a developer does is they go and 00:10:49.839 --> 00:10:51.870 align:start position:0% what a developer does is they go and they<00:10:50.000> fill<00:10:50.279> in<00:10:50.440> their<00:10:50.600> trade<00:10:50.920> ticket<00:10:51.519> origin 00:10:51.870 --> 00:10:51.880 align:start position:0% they fill in their trade ticket origin 00:10:51.880 --> 00:10:53.670 align:start position:0% they fill in their trade ticket origin chain<00:10:52.160> origin<00:10:52.519> amount<00:10:52.959> destination<00:10:53.440> chain 00:10:53.670 --> 00:10:53.680 align:start position:0% chain origin amount destination chain 00:10:53.680 --> 00:10:57.430 align:start position:0% chain origin amount destination chain destination<00:10:54.360> amount<00:10:55.360> um<00:10:56.360> and<00:10:56.519> then<00:10:57.160> we<00:10:57.279> got<00:10:57.360> a 00:10:57.430 --> 00:10:57.440 align:start position:0% destination amount um and then we got a 00:10:57.440 --> 00:10:58.670 align:start position:0% destination amount um and then we got a couple<00:10:57.639> other<00:10:57.760> fields<00:10:58.079> here<00:10:58.320> that<00:10:58.399> I<00:10:58.480> want<00:10:58.560> to 00:10:58.670 --> 00:10:58.680 align:start position:0% couple other fields here that I want to 00:10:58.680 --> 00:11:00.750 align:start position:0% couple other fields here that I want to talk<00:10:58.839> about<00:10:59.079> but<00:10:59.680> you<00:10:59.839> fill<00:11:00.120> this<00:11:00.279> out<00:11:00.560> and<00:11:00.639> you 00:11:00.750 --> 00:11:00.760 align:start position:0% talk about but you fill this out and you 00:11:00.760 --> 00:11:02.310 align:start position:0% talk about but you fill this out and you send<00:11:00.959> it<00:11:01.079> to<00:11:01.200> the<00:11:01.320> solver<00:11:01.680> Network<00:11:02.079> and<00:11:02.200> it 00:11:02.310 --> 00:11:02.320 align:start position:0% send it to the solver Network and it 00:11:02.320 --> 00:11:04.110 align:start position:0% send it to the solver Network and it just<00:11:02.480> gets<00:11:02.720> done<00:11:03.040> it<00:11:03.200> just 00:11:04.110 --> 00:11:04.120 align:start position:0% just gets done it just 00:11:04.120 --> 00:11:07.030 align:start position:0% just gets done it just works<00:11:05.120> so<00:11:05.760> I<00:11:05.880> got<00:11:06.040> these<00:11:06.200> two<00:11:06.360> other<00:11:06.560> fields<00:11:06.880> in 00:11:07.030 --> 00:11:07.040 align:start position:0% works so I got these two other fields in 00:11:07.040 --> 00:11:08.509 align:start position:0% works so I got these two other fields in here<00:11:07.279> fill<00:11:07.480> instructions<00:11:07.880> and<00:11:08.079> settlement 00:11:08.509 --> 00:11:08.519 align:start position:0% here fill instructions and settlement 00:11:08.519 --> 00:11:10.550 align:start position:0% here fill instructions and settlement system<00:11:09.519> um<00:11:09.760> and<00:11:09.880> this<00:11:10.000> is<00:11:10.160> a<00:11:10.240> little<00:11:10.360> bit 00:11:10.550 --> 00:11:10.560 align:start position:0% system um and this is a little bit 00:11:10.560 --> 00:11:13.389 align:start position:0% system um and this is a little bit stylized<00:11:11.279> the<00:11:11.880> just<00:11:12.120> how<00:11:12.279> this<00:11:12.440> works<00:11:12.839> but 00:11:13.389 --> 00:11:13.399 align:start position:0% stylized the just how this works but 00:11:13.399 --> 00:11:15.269 align:start position:0% stylized the just how this works but fill<00:11:13.760> instructions<00:11:14.360> you<00:11:14.480> can<00:11:14.639> think<00:11:14.839> of<00:11:15.040> as 00:11:15.269 --> 00:11:15.279 align:start position:0% fill instructions you can think of as 00:11:15.279 --> 00:11:17.949 align:start position:0% fill instructions you can think of as like<00:11:15.440> a<00:11:15.600> memo<00:11:15.959> field<00:11:16.800> where<00:11:17.000> I<00:11:17.079> can<00:11:17.320> include 00:11:17.949 --> 00:11:17.959 align:start position:0% like a memo field where I can include 00:11:17.959 --> 00:11:20.550 align:start position:0% like a memo field where I can include extra<00:11:18.440> information<00:11:19.440> about<00:11:19.760> what<00:11:19.959> I<00:11:20.079> want<00:11:20.279> to 00:11:20.550 --> 00:11:20.560 align:start position:0% extra information about what I want to 00:11:20.560 --> 00:11:24.590 align:start position:0% extra information about what I want to have<00:11:20.839> happen<00:11:21.560> in<00:11:21.839> this<00:11:22.560> intent<00:11:23.560> um<00:11:24.000> and 00:11:24.590 --> 00:11:24.600 align:start position:0% have happen in this intent um and 00:11:24.600 --> 00:11:27.030 align:start position:0% have happen in this intent um and remember<00:11:25.040> the<00:11:25.200> solver<00:11:25.839> is<00:11:26.000> the<00:11:26.160> one<00:11:26.760> that's 00:11:27.030 --> 00:11:27.040 align:start position:0% remember the solver is the one that's 00:11:27.040 --> 00:11:28.710 align:start position:0% remember the solver is the one that's moving<00:11:27.440> the<00:11:27.600> assets<00:11:27.959> to<00:11:28.079> the<00:11:28.240> destination 00:11:28.710 --> 00:11:28.720 align:start position:0% moving the assets to the destination 00:11:28.720 --> 00:11:31.069 align:start position:0% moving the assets to the destination chain<00:11:29.399> and<00:11:29.519> sending<00:11:29.839> them<00:11:29.959> to<00:11:30.079> the<00:11:30.200> user<00:11:30.880> so 00:11:31.069 --> 00:11:31.079 align:start position:0% chain and sending them to the user so 00:11:31.079 --> 00:11:32.470 align:start position:0% chain and sending them to the user so there's<00:11:31.360> nothing<00:11:31.680> that<00:11:31.880> prevents<00:11:32.320> that 00:11:32.470 --> 00:11:32.480 align:start position:0% there's nothing that prevents that 00:11:32.480 --> 00:11:36.350 align:start position:0% there's nothing that prevents that solver<00:11:33.320> from<00:11:33.639> executing<00:11:34.279> arbitrary<00:11:35.200> code<00:11:36.200> so 00:11:36.350 --> 00:11:36.360 align:start position:0% solver from executing arbitrary code so 00:11:36.360 --> 00:11:38.269 align:start position:0% solver from executing arbitrary code so the<00:11:36.480> fill<00:11:36.720> instructions<00:11:37.120> can<00:11:37.279> be<00:11:37.480> say<00:11:37.920> hey 00:11:38.269 --> 00:11:38.279 align:start position:0% the fill instructions can be say hey 00:11:38.279 --> 00:11:40.470 align:start position:0% the fill instructions can be say hey let's<00:11:38.480> Bridge<00:11:38.760> one<00:11:38.959> eth<00:11:39.800> and<00:11:39.920> then<00:11:40.040> swap<00:11:40.360> it 00:11:40.470 --> 00:11:40.480 align:start position:0% let's Bridge one eth and then swap it 00:11:40.480 --> 00:11:42.430 align:start position:0% let's Bridge one eth and then swap it for<00:11:40.600> frog<00:11:40.959> token<00:11:41.720> once<00:11:41.920> you<00:11:42.079> get<00:11:42.160> to<00:11:42.320> the 00:11:42.430 --> 00:11:42.440 align:start position:0% for frog token once you get to the 00:11:42.440 --> 00:11:44.670 align:start position:0% for frog token once you get to the destination<00:11:42.920> chain<00:11:43.760> totally<00:11:44.200> possible 00:11:44.670 --> 00:11:44.680 align:start position:0% destination chain totally possible 00:11:44.680 --> 00:11:45.829 align:start position:0% destination chain totally possible that's<00:11:44.880> actually<00:11:45.079> something<00:11:45.399> you<00:11:45.480> can<00:11:45.600> do 00:11:45.829 --> 00:11:45.839 align:start position:0% that's actually something you can do 00:11:45.839 --> 00:11:46.910 align:start position:0% that's actually something you can do with<00:11:45.959> the<00:11:46.120> cross 00:11:46.910 --> 00:11:46.920 align:start position:0% with the cross 00:11:46.920 --> 00:11:49.069 align:start position:0% with the cross today<00:11:47.920> and<00:11:48.000> it<00:11:48.079> could<00:11:48.200> be<00:11:48.279> Bridge<00:11:48.519> 1<00:11:48.639> Ethan<00:11:48.920> buy 00:11:49.069 --> 00:11:49.079 align:start position:0% today and it could be Bridge 1 Ethan buy 00:11:49.079 --> 00:11:51.550 align:start position:0% today and it could be Bridge 1 Ethan buy an<00:11:49.360> nft<00:11:50.360> and<00:11:50.480> it<00:11:50.600> could<00:11:50.680> be<00:11:50.800> Bridge<00:11:51.040> 1<00:11:51.200> Ethan 00:11:51.550 --> 00:11:51.560 align:start position:0% an nft and it could be Bridge 1 Ethan 00:11:51.560 --> 00:11:53.629 align:start position:0% an nft and it could be Bridge 1 Ethan deposit<00:11:51.920> in<00:11:52.200> a<00:11:52.680> or<00:11:52.800> whatever<00:11:53.040> your<00:11:53.279> D5 00:11:53.629 --> 00:11:53.639 align:start position:0% deposit in a or whatever your D5 00:11:53.639 --> 00:11:56.389 align:start position:0% deposit in a or whatever your D5 protocol<00:11:54.079> is<00:11:54.959> and<00:11:55.120> this<00:11:55.240> can<00:11:55.440> happen<00:11:55.760> in<00:11:56.000> one 00:11:56.389 --> 00:11:56.399 align:start position:0% protocol is and this can happen in one 00:11:56.399 --> 00:11:59.230 align:start position:0% protocol is and this can happen in one click<00:11:56.959> remember<00:11:57.680> so<00:11:58.000> in<00:11:58.160> one<00:11:58.440> click<00:11:58.680> on<00:11:58.800> my<00:11:58.959> or 00:11:59.230 --> 00:11:59.240 align:start position:0% click remember so in one click on my or 00:11:59.240 --> 00:12:01.230 align:start position:0% click remember so in one click on my or origin<00:11:59.480> chain<00:11:59.839> let's<00:12:00.000> say<00:12:00.120> it's<00:12:00.240> arbitrum<00:12:01.000> one 00:12:01.230 --> 00:12:01.240 align:start position:0% origin chain let's say it's arbitrum one 00:12:01.240 --> 00:12:03.310 align:start position:0% origin chain let's say it's arbitrum one click<00:12:01.399> on<00:12:01.560> Origin<00:12:01.839> chain<00:12:02.040> on<00:12:02.160> arbitrum<00:12:02.920> I<00:12:03.000> can 00:12:03.310 --> 00:12:03.320 align:start position:0% click on Origin chain on arbitrum I can 00:12:03.320 --> 00:12:05.069 align:start position:0% click on Origin chain on arbitrum I can have<00:12:03.560> this<00:12:03.760> action<00:12:04.079> happen<00:12:04.440> inside<00:12:04.839> two 00:12:05.069 --> 00:12:05.079 align:start position:0% have this action happen inside two 00:12:05.079 --> 00:12:07.230 align:start position:0% have this action happen inside two seconds<00:12:05.399> on<00:12:05.519> my<00:12:05.839> destination<00:12:06.839> which<00:12:06.959> I<00:12:07.079> think 00:12:07.230 --> 00:12:07.240 align:start position:0% seconds on my destination which I think 00:12:07.240 --> 00:12:09.509 align:start position:0% seconds on my destination which I think is<00:12:07.600> pretty<00:12:07.839> cool<00:12:08.560> um<00:12:08.680> and<00:12:08.800> I<00:12:08.880> think<00:12:09.040> this<00:12:09.200> look 00:12:09.509 --> 00:12:09.519 align:start position:0% is pretty cool um and I think this look 00:12:09.519 --> 00:12:11.470 align:start position:0% is pretty cool um and I think this look really<00:12:09.760> does<00:12:09.959> lay<00:12:10.240> the<00:12:10.360> groundwork<00:12:11.079> for<00:12:11.320> how 00:12:11.470 --> 00:12:11.480 align:start position:0% really does lay the groundwork for how 00:12:11.480 --> 00:12:13.990 align:start position:0% really does lay the groundwork for how we<00:12:11.760> unify<00:12:12.240> ethereum<00:12:13.079> and<00:12:13.199> make<00:12:13.399> these<00:12:13.600> chains 00:12:13.990 --> 00:12:14.000 align:start position:0% we unify ethereum and make these chains 00:12:14.000 --> 00:12:17.750 align:start position:0% we unify ethereum and make these chains feel<00:12:14.360> like<00:12:14.560> one<00:12:15.320> thing<00:12:16.320> um<00:12:17.160> but<00:12:17.360> I<00:12:17.480> mentioned 00:12:17.750 --> 00:12:17.760 align:start position:0% feel like one thing um but I mentioned 00:12:17.760 --> 00:12:19.350 align:start position:0% feel like one thing um but I mentioned this<00:12:17.920> earlier<00:12:18.440> one<00:12:18.560> of<00:12:18.680> the<00:12:18.800> things<00:12:19.000> I<00:12:19.160> get 00:12:19.350 --> 00:12:19.360 align:start position:0% this earlier one of the things I get 00:12:19.360 --> 00:12:21.629 align:start position:0% this earlier one of the things I get super<00:12:19.680> excited<00:12:20.120> about<00:12:20.480> is<00:12:20.639> once<00:12:20.839> we<00:12:21.079> combine 00:12:21.629 --> 00:12:21.639 align:start position:0% super excited about is once we combine 00:12:21.639 --> 00:12:24.590 align:start position:0% super excited about is once we combine this<00:12:22.360> with<00:12:22.720> uh<00:12:22.920> ubiquitous<00:12:23.720> account 00:12:24.590 --> 00:12:24.600 align:start position:0% this with uh ubiquitous account 00:12:24.600 --> 00:12:28.550 align:start position:0% this with uh ubiquitous account abstraction<00:12:25.880> um<00:12:26.880> this<00:12:27.000> would<00:12:27.160> be<00:12:27.600> an<00:12:27.839> entire 00:12:28.550 --> 00:12:28.560 align:start position:0% abstraction um this would be an entire 00:12:28.560 --> 00:12:31.310 align:start position:0% abstraction um this would be an entire other<00:12:29.360> talk<00:12:30.199> uh<00:12:30.320> so<00:12:30.480> I'll<00:12:30.639> just<00:12:30.760> keep<00:12:30.920> it<00:12:31.079> high 00:12:31.310 --> 00:12:31.320 align:start position:0% other talk uh so I'll just keep it high 00:12:31.320 --> 00:12:35.030 align:start position:0% other talk uh so I'll just keep it high level<00:12:32.240> um<00:12:32.480> but<00:12:32.680> EIP<00:12:33.240> 7702<00:12:34.240> for<00:12:34.480> those<00:12:34.639> of<00:12:34.760> you 00:12:35.030 --> 00:12:35.040 align:start position:0% level um but EIP 7702 for those of you 00:12:35.040 --> 00:12:37.230 align:start position:0% level um but EIP 7702 for those of you that<00:12:35.360> that<00:12:35.639> aren't<00:12:36.040> familiar<00:12:36.600> with<00:12:36.800> for 00:12:37.230 --> 00:12:37.240 align:start position:0% that that aren't familiar with for 00:12:37.240 --> 00:12:39.990 align:start position:0% that that aren't familiar with for digigit<00:12:37.560> EIP<00:12:38.040> numbers<00:12:39.040> uh<00:12:39.199> it's<00:12:39.399> actually<00:12:39.720> a 00:12:39.990 --> 00:12:40.000 align:start position:0% digigit EIP numbers uh it's actually a 00:12:40.000 --> 00:12:42.509 align:start position:0% digigit EIP numbers uh it's actually a EIP<00:12:40.399> that<00:12:40.519> vitalic<00:12:40.959> wrote<00:12:41.680> an<00:12:41.880> improvement<00:12:42.360> on 00:12:42.509 --> 00:12:42.519 align:start position:0% EIP that vitalic wrote an improvement on 00:12:42.519 --> 00:12:45.310 align:start position:0% EIP that vitalic wrote an improvement on some<00:12:42.680> other<00:12:42.880> Technologies<00:12:43.519> like<00:12:44.199> 3705<00:12:45.199> I 00:12:45.310 --> 00:12:45.320 align:start position:0% some other Technologies like 3705 I 00:12:45.320 --> 00:12:48.990 align:start position:0% some other Technologies like 3705 I believe<00:12:46.320> um<00:12:47.040> that<00:12:47.279> will<00:12:47.880> uh<00:12:48.079> bring<00:12:48.519> smart 00:12:48.990 --> 00:12:49.000 align:start position:0% believe um that will uh bring smart 00:12:49.000 --> 00:12:51.670 align:start position:0% believe um that will uh bring smart account<00:12:49.600> uh<00:12:49.800> capabilities<00:12:50.519> to<00:12:50.839> everyone's 00:12:51.670 --> 00:12:51.680 align:start position:0% account uh capabilities to everyone's 00:12:51.680 --> 00:12:54.030 align:start position:0% account uh capabilities to everyone's eoa<00:12:52.680> and<00:12:52.800> this<00:12:52.920> is<00:12:53.160> going<00:12:53.320> to<00:12:53.440> ship<00:12:53.760> this<00:12:53.920> is 00:12:54.030 --> 00:12:54.040 align:start position:0% eoa and this is going to ship this is 00:12:54.040 --> 00:12:55.750 align:start position:0% eoa and this is going to ship this is scheduled<00:12:54.440> to<00:12:54.560> ship<00:12:54.880> as<00:12:55.040> part<00:12:55.199> of<00:12:55.279> the<00:12:55.399> Petra 00:12:55.750 --> 00:12:55.760 align:start position:0% scheduled to ship as part of the Petra 00:12:55.760 --> 00:12:57.949 align:start position:0% scheduled to ship as part of the Petra hard<00:12:56.000> fork<00:12:56.720> in<00:12:56.880> the<00:12:57.000> first<00:12:57.199> quarter<00:12:57.519> of<00:12:57.680> next 00:12:57.949 --> 00:12:57.959 align:start position:0% hard fork in the first quarter of next 00:12:57.959 --> 00:13:00.910 align:start position:0% hard fork in the first quarter of next year<00:12:58.959> and<00:12:59.199> so<00:12:59.360> what<00:12:59.480> this<00:12:59.600> means<00:12:59.959> now<00:13:00.519> is<00:13:00.680> that 00:13:00.910 --> 00:13:00.920 align:start position:0% year and so what this means now is that 00:13:00.920 --> 00:13:03.389 align:start position:0% year and so what this means now is that anyone's<00:13:01.480> account<00:13:02.399> can<00:13:02.680> you<00:13:02.800> can<00:13:02.959> send<00:13:03.199> a 00:13:03.389 --> 00:13:03.399 align:start position:0% anyone's account can you can send a 00:13:03.399 --> 00:13:05.150 align:start position:0% anyone's account can you can send a message<00:13:03.800> and<00:13:03.920> somebody<00:13:04.199> else<00:13:04.440> can<00:13:04.680> execute 00:13:05.150 --> 00:13:05.160 align:start position:0% message and somebody else can execute 00:13:05.160 --> 00:13:07.910 align:start position:0% message and somebody else can execute that<00:13:05.360> message<00:13:06.199> like<00:13:06.440> it<00:13:06.560> was<00:13:06.720> being<00:13:06.880> sent<00:13:07.199> from 00:13:07.910 --> 00:13:07.920 align:start position:0% that message like it was being sent from 00:13:07.920 --> 00:13:11.629 align:start position:0% that message like it was being sent from eoa<00:13:08.920> um<00:13:09.399> and<00:13:09.600> what<00:13:09.760> this<00:13:10.000> means<00:13:10.680> is<00:13:10.880> that<00:13:11.240> I<00:13:11.360> can 00:13:11.629 --> 00:13:11.639 align:start position:0% eoa um and what this means is that I can 00:13:11.639 --> 00:13:15.470 align:start position:0% eoa um and what this means is that I can now<00:13:12.040> remote<00:13:12.560> control<00:13:13.519> any<00:13:13.880> remote<00:13:14.240> chain<00:13:14.920> from 00:13:15.470 --> 00:13:15.480 align:start position:0% now remote control any remote chain from 00:13:15.480 --> 00:13:18.389 align:start position:0% now remote control any remote chain from my<00:13:15.680> home<00:13:16.079> chain<00:13:17.079> and<00:13:17.279> how<00:13:17.519> this<00:13:17.639> would<00:13:17.839> work<00:13:18.240> is 00:13:18.389 --> 00:13:18.399 align:start position:0% my home chain and how this would work is 00:13:18.399 --> 00:13:21.310 align:start position:0% my home chain and how this would work is I<00:13:18.480> would<00:13:18.720> sign<00:13:18.959> an<00:13:19.160> intent<00:13:20.000> a<00:13:20.199> 7702<00:13:21.000> message 00:13:21.310 --> 00:13:21.320 align:start position:0% I would sign an intent a 7702 message 00:13:21.320 --> 00:13:22.910 align:start position:0% I would sign an intent a 7702 message for<00:13:21.519> the<00:13:21.720> action<00:13:22.000> I<00:13:22.120> want<00:13:22.240> to<00:13:22.399> have<00:13:22.600> happen<00:13:22.800> on 00:13:22.910 --> 00:13:22.920 align:start position:0% for the action I want to have happen on 00:13:22.920 --> 00:13:25.430 align:start position:0% for the action I want to have happen on my<00:13:23.160> remote<00:13:23.399> chain<00:13:24.199> and<00:13:24.320> I<00:13:24.440> would<00:13:24.639> include<00:13:25.000> it 00:13:25.430 --> 00:13:25.440 align:start position:0% my remote chain and I would include it 00:13:25.440 --> 00:13:27.829 align:start position:0% my remote chain and I would include it as<00:13:25.519> a<00:13:25.760> payload<00:13:26.639> in<00:13:26.839> this<00:13:26.959> fill<00:13:27.320> instructions 00:13:27.829 --> 00:13:27.839 align:start position:0% as a payload in this fill instructions 00:13:27.839 --> 00:13:31.550 align:start position:0% as a payload in this fill instructions field<00:13:28.839> um<00:13:29.120> in<00:13:29.240> our<00:13:29.480> 7683<00:13:30.360> standard<00:13:31.240> and<00:13:31.320> then<00:13:31.480> I 00:13:31.550 --> 00:13:31.560 align:start position:0% field um in our 7683 standard and then I 00:13:31.560 --> 00:13:33.829 align:start position:0% field um in our 7683 standard and then I would<00:13:31.760> use<00:13:32.040> the<00:13:32.199> solver<00:13:32.639> Network<00:13:33.120> the<00:13:33.240> intense 00:13:33.829 --> 00:13:33.839 align:start position:0% would use the solver Network the intense 00:13:33.839 --> 00:13:35.829 align:start position:0% would use the solver Network the intense solver<00:13:34.279> Network<00:13:34.880> to<00:13:35.079> basically<00:13:35.440> bring<00:13:35.680> the 00:13:35.829 --> 00:13:35.839 align:start position:0% solver Network to basically bring the 00:13:35.839 --> 00:13:37.790 align:start position:0% solver Network to basically bring the gas<00:13:36.040> money<00:13:36.320> over<00:13:36.519> to<00:13:36.639> go<00:13:36.760> and<00:13:36.959> execute<00:13:37.639> this 00:13:37.790 --> 00:13:37.800 align:start position:0% gas money over to go and execute this 00:13:37.800 --> 00:13:38.949 align:start position:0% gas money over to go and execute this arbitrary 00:13:38.949 --> 00:13:38.959 align:start position:0% arbitrary 00:13:38.959 --> 00:13:40.829 align:start position:0% arbitrary transaction<00:13:39.959> um<00:13:40.120> and<00:13:40.320> again<00:13:40.519> we'll<00:13:40.720> be 00:13:40.829 --> 00:13:40.839 align:start position:0% transaction um and again we'll be 00:13:40.839 --> 00:13:42.030 align:start position:0% transaction um and again we'll be talking<00:13:41.120> more<00:13:41.320> about<00:13:41.560> this<00:13:41.720> there's<00:13:41.880> a 00:13:42.030 --> 00:13:42.040 align:start position:0% talking more about this there's a 00:13:42.040 --> 00:13:43.990 align:start position:0% talking more about this there's a probably<00:13:42.240> a<00:13:42.360> whole<00:13:42.600> other<00:13:42.920> conversation<00:13:43.639> or 00:13:43.990 --> 00:13:44.000 align:start position:0% probably a whole other conversation or 00:13:44.000 --> 00:13:46.230 align:start position:0% probably a whole other conversation or talk<00:13:44.240> to<00:13:44.519> have<00:13:45.160> but<00:13:45.279> there's<00:13:45.440> this<00:13:45.680> very<00:13:45.920> cool 00:13:46.230 --> 00:13:46.240 align:start position:0% talk to have but there's this very cool 00:13:46.240 --> 00:13:47.949 align:start position:0% talk to have but there's this very cool way<00:13:46.560> that<00:13:46.680> we've<00:13:46.839> got<00:13:47.040> all<00:13:47.160> the<00:13:47.320> Lego<00:13:47.639> blocks 00:13:47.949 --> 00:13:47.959 align:start position:0% way that we've got all the Lego blocks 00:13:47.959 --> 00:13:50.230 align:start position:0% way that we've got all the Lego blocks and<00:13:48.160> pieces<00:13:48.959> when<00:13:49.160> we<00:13:49.360> add<00:13:49.720> together 00:13:50.230 --> 00:13:50.240 align:start position:0% and pieces when we add together 00:13:50.240 --> 00:13:53.670 align:start position:0% and pieces when we add together four-digit<00:13:50.800> numbers<00:13:51.360> like<00:13:51.519> 772<00:13:52.240> and<00:13:52.440> 7683<00:13:53.440> we 00:13:53.670 --> 00:13:53.680 align:start position:0% four-digit numbers like 772 and 7683 we 00:13:53.680 --> 00:13:55.350 align:start position:0% four-digit numbers like 772 and 7683 we add<00:13:53.880> them<00:13:54.199> together<00:13:54.800> and<00:13:54.920> we're<00:13:55.040> going<00:13:55.160> to 00:13:55.350 --> 00:13:55.360 align:start position:0% add them together and we're going to 00:13:55.360 --> 00:13:56.749 align:start position:0% add them together and we're going to have<00:13:55.639> this<00:13:55.839> like<00:13:56.000> I<00:13:56.079> really<00:13:56.240> do<00:13:56.399> think<00:13:56.560> of<00:13:56.639> it 00:13:56.749 --> 00:13:56.759 align:start position:0% have this like I really do think of it 00:13:56.759 --> 00:13:58.470 align:start position:0% have this like I really do think of it as<00:13:56.880> like<00:13:57.000> a<00:13:57.120> remote<00:13:57.399> control<00:13:57.959> where<00:13:58.160> from<00:13:58.320> my 00:13:58.470 --> 00:13:58.480 align:start position:0% as like a remote control where from my 00:13:58.480 --> 00:14:00.749 align:start position:0% as like a remote control where from my home<00:13:58.639> chain<00:13:59.120> I<00:13:59.199> can<00:13:59.279> do<00:13:59.399> an<00:13:59.560> arbitrary<00:14:00.120> action 00:14:00.749 --> 00:14:00.759 align:start position:0% home chain I can do an arbitrary action 00:14:00.759 --> 00:14:03.710 align:start position:0% home chain I can do an arbitrary action on<00:14:00.880> the<00:14:01.040> destination 00:14:03.710 --> 00:14:03.720 align:start position:0% 00:14:03.720 --> 00:14:07.990 align:start position:0% chain<00:14:04.720> this<00:14:05.000> standard<00:14:05.680> also<00:14:07.000> modularizes 00:14:07.990 --> 00:14:08.000 align:start position:0% chain this standard also modularizes 00:14:08.000 --> 00:14:10.269 align:start position:0% chain this standard also modularizes it's<00:14:08.120> a<00:14:08.240> hard<00:14:08.399> word<00:14:08.600> to<00:14:08.759> say<00:14:09.079> it<00:14:09.320> modularizes 00:14:10.269 --> 00:14:10.279 align:start position:0% it's a hard word to say it modularizes 00:14:10.279 --> 00:14:13.550 align:start position:0% it's a hard word to say it modularizes the<00:14:10.399> settlement<00:14:10.920> system<00:14:11.399> too<00:14:12.399> um<00:14:13.040> so<00:14:13.320> what<00:14:13.440> do 00:14:13.550 --> 00:14:13.560 align:start position:0% the settlement system too um so what do 00:14:13.560 --> 00:14:15.710 align:start position:0% the settlement system too um so what do I<00:14:13.639> mean<00:14:13.880> by<00:14:14.079> that<00:14:14.759> if<00:14:14.880> you<00:14:15.079> guys<00:14:15.279> go<00:14:15.440> back<00:14:15.560> on 00:14:15.710 --> 00:14:15.720 align:start position:0% I mean by that if you guys go back on 00:14:15.720 --> 00:14:17.310 align:start position:0% I mean by that if you guys go back on the<00:14:15.800> other<00:14:16.000> slides<00:14:16.320> where<00:14:16.440> I<00:14:16.519> was<00:14:16.680> kind<00:14:16.800> of 00:14:17.310 --> 00:14:17.320 align:start position:0% the other slides where I was kind of 00:14:17.320 --> 00:14:19.470 align:start position:0% the other slides where I was kind of walking<00:14:17.639> through<00:14:17.839> the<00:14:17.959> intent<00:14:18.480> architecture 00:14:19.470 --> 00:14:19.480 align:start position:0% walking through the intent architecture 00:14:19.480 --> 00:14:21.870 align:start position:0% walking through the intent architecture user<00:14:19.839> funds<00:14:20.199> get<00:14:20.440> escrowed<00:14:21.240> on<00:14:21.399> the<00:14:21.519> origin 00:14:21.870 --> 00:14:21.880 align:start position:0% user funds get escrowed on the origin 00:14:21.880 --> 00:14:23.790 align:start position:0% user funds get escrowed on the origin chain<00:14:22.639> and<00:14:22.720> then<00:14:22.839> they<00:14:22.959> only<00:14:23.240> get<00:14:23.360> released<00:14:23.680> to 00:14:23.790 --> 00:14:23.800 align:start position:0% chain and then they only get released to 00:14:23.800 --> 00:14:26.590 align:start position:0% chain and then they only get released to the<00:14:23.959> solver<00:14:24.639> when<00:14:24.800> we<00:14:25.079> verify<00:14:25.639> that<00:14:25.800> fill 00:14:26.590 --> 00:14:26.600 align:start position:0% the solver when we verify that fill 00:14:26.600 --> 00:14:29.189 align:start position:0% the solver when we verify that fill happened<00:14:27.600> um<00:14:28.320> I'm<00:14:28.480> calling<00:14:28.759> that<00:14:28.920> the 00:14:29.189 --> 00:14:29.199 align:start position:0% happened um I'm calling that the 00:14:29.199 --> 00:14:31.389 align:start position:0% happened um I'm calling that the settlement<00:14:29.600> system<00:14:30.240> the<00:14:30.440> system<00:14:30.959> that<00:14:31.320> it 00:14:31.389 --> 00:14:31.399 align:start position:0% settlement system the system that it 00:14:31.399 --> 00:14:34.629 align:start position:0% settlement system the system that it serves<00:14:31.720> two<00:14:32.040> purposes<00:14:33.040> it<00:14:33.720> it<00:14:34.040> keeps<00:14:34.360> user 00:14:34.629 --> 00:14:34.639 align:start position:0% serves two purposes it it keeps user 00:14:34.639 --> 00:14:37.069 align:start position:0% serves two purposes it it keeps user funds<00:14:35.120> safe<00:14:35.759> where<00:14:35.880> it<00:14:36.079> doesn't<00:14:36.399> release<00:14:36.720> user 00:14:37.069 --> 00:14:37.079 align:start position:0% funds safe where it doesn't release user 00:14:37.079 --> 00:14:39.509 align:start position:0% funds safe where it doesn't release user funds<00:14:37.440> to<00:14:37.600> a<00:14:37.759> solver<00:14:38.639> uh<00:14:38.759> until<00:14:39.079> the<00:14:39.160> fill 00:14:39.509 --> 00:14:39.519 align:start position:0% funds to a solver uh until the fill 00:14:39.519 --> 00:14:42.430 align:start position:0% funds to a solver uh until the fill happens<00:14:40.320> and<00:14:40.440> it<00:14:40.600> also<00:14:40.800> keeps<00:14:41.120> solvers<00:14:41.839> safe 00:14:42.430 --> 00:14:42.440 align:start position:0% happens and it also keeps solvers safe 00:14:42.440 --> 00:14:43.949 align:start position:0% happens and it also keeps solvers safe where<00:14:42.560> it<00:14:42.680> doesn't<00:14:42.880> let<00:14:43.040> solvers<00:14:43.440> get<00:14:43.560> rugged 00:14:43.949 --> 00:14:43.959 align:start position:0% where it doesn't let solvers get rugged 00:14:43.959 --> 00:14:45.269 align:start position:0% where it doesn't let solvers get rugged by 00:14:45.269 --> 00:14:45.279 align:start position:0% by 00:14:45.279 --> 00:14:47.910 align:start position:0% by users<00:14:46.279> so<00:14:46.600> in<00:14:46.800> this<00:14:47.040> standard<00:14:47.759> that 00:14:47.910 --> 00:14:47.920 align:start position:0% users so in this standard that 00:14:47.920 --> 00:14:50.150 align:start position:0% users so in this standard that settlement<00:14:48.360> system<00:14:48.759> is<00:14:49.000> is<00:14:49.079> a<00:14:49.199> module<00:14:49.959> and<00:14:50.079> you 00:14:50.150 --> 00:14:50.160 align:start position:0% settlement system is is a module and you 00:14:50.160 --> 00:14:52.910 align:start position:0% settlement system is is a module and you can<00:14:50.279> plug<00:14:50.480> in<00:14:50.639> what<00:14:50.759> you<00:14:50.920> want<00:14:51.759> uh<00:14:51.920> across<00:14:52.639> has 00:14:52.910 --> 00:14:52.920 align:start position:0% can plug in what you want uh across has 00:14:52.920 --> 00:14:54.870 align:start position:0% can plug in what you want uh across has a<00:14:53.199> version<00:14:53.600> of<00:14:53.839> this<00:14:54.440> that<00:14:54.560> we've<00:14:54.720> been 00:14:54.870 --> 00:14:54.880 align:start position:0% a version of this that we've been 00:14:54.880 --> 00:14:56.069 align:start position:0% a version of this that we've been operating<00:14:55.199> for<00:14:55.360> two<00:14:55.519> years<00:14:55.720> that<00:14:55.839> works 00:14:56.069 --> 00:14:56.079 align:start position:0% operating for two years that works 00:14:56.079 --> 00:14:58.350 align:start position:0% operating for two years that works pretty<00:14:56.320> well<00:14:56.959> but<00:14:57.120> it's<00:14:57.279> by<00:14:57.440> no<00:14:57.600> means<00:14:57.880> the<00:14:58.040> end 00:14:58.350 --> 00:14:58.360 align:start position:0% pretty well but it's by no means the end 00:14:58.360 --> 00:15:00.790 align:start position:0% pretty well but it's by no means the end state<00:14:59.480> and<00:14:59.720> what<00:14:59.839> I<00:14:59.959> think<00:15:00.120> is<00:15:00.279> super<00:15:00.560> cool 00:15:00.790 --> 00:15:00.800 align:start position:0% state and what I think is super cool 00:15:00.800 --> 00:15:02.509 align:start position:0% state and what I think is super cool about<00:15:01.040> this<00:15:01.240> and<00:15:01.440> and<00:15:01.639> Jesse<00:15:02.000> on<00:15:02.120> the<00:15:02.240> panel 00:15:02.509 --> 00:15:02.519 align:start position:0% about this and and Jesse on the panel 00:15:02.519 --> 00:15:04.389 align:start position:0% about this and and Jesse on the panel beforehand<00:15:03.000> was<00:15:03.240> was<00:15:03.399> talking<00:15:03.759> exactly<00:15:04.120> about 00:15:04.389 --> 00:15:04.399 align:start position:0% beforehand was was talking exactly about 00:15:04.399 --> 00:15:07.629 align:start position:0% beforehand was was talking exactly about this<00:15:04.920> idea<00:15:05.920> if<00:15:06.079> I<00:15:06.279> have<00:15:06.480> two<00:15:06.680> chains<00:15:07.240> if<00:15:07.440> my 00:15:07.629 --> 00:15:07.639 align:start position:0% this idea if I have two chains if my 00:15:07.639 --> 00:15:09.790 align:start position:0% this idea if I have two chains if my origin<00:15:08.040> chain<00:15:08.320> and<00:15:08.480> my<00:15:08.639> destination<00:15:09.160> chain 00:15:09.790 --> 00:15:09.800 align:start position:0% origin chain and my destination chain 00:15:09.800 --> 00:15:12.350 align:start position:0% origin chain and my destination chain are<00:15:10.040> both<00:15:10.279> super<00:15:10.800> chains<00:15:11.800> I<00:15:11.880> could<00:15:12.040> use<00:15:12.199> a 00:15:12.350 --> 00:15:12.360 align:start position:0% are both super chains I could use a 00:15:12.360 --> 00:15:15.749 align:start position:0% are both super chains I could use a settlement<00:15:12.839> system<00:15:13.399> that<00:15:13.600> uses<00:15:14.440> uh<00:15:14.759> optimism 00:15:15.749 --> 00:15:15.759 align:start position:0% settlement system that uses uh optimism 00:15:15.759 --> 00:15:18.710 align:start position:0% settlement system that uses uh optimism uh<00:15:15.880> super<00:15:16.240> chain<00:15:16.440> native<00:15:17.079> interop<00:15:18.079> um<00:15:18.560> and 00:15:18.710 --> 00:15:18.720 align:start position:0% uh super chain native interop um and 00:15:18.720 --> 00:15:21.230 align:start position:0% uh super chain native interop um and that<00:15:18.839> could<00:15:19.000> be<00:15:19.240> faster<00:15:20.120> to<00:15:20.360> repay<00:15:20.720> the<00:15:20.800> solver 00:15:21.230 --> 00:15:21.240 align:start position:0% that could be faster to repay the solver 00:15:21.240 --> 00:15:22.910 align:start position:0% that could be faster to repay the solver faster<00:15:21.759> which<00:15:21.880> would<00:15:22.079> make<00:15:22.240> the<00:15:22.360> intent 00:15:22.910 --> 00:15:22.920 align:start position:0% faster which would make the intent 00:15:22.920 --> 00:15:25.230 align:start position:0% faster which would make the intent cheaper<00:15:23.920> so<00:15:24.079> I<00:15:24.199> have<00:15:24.399> all<00:15:24.560> the<00:15:24.680> flexibility<00:15:25.160> in 00:15:25.230 --> 00:15:25.240 align:start position:0% cheaper so I have all the flexibility in 00:15:25.240 --> 00:15:27.470 align:start position:0% cheaper so I have all the flexibility in the<00:15:25.320> world<00:15:25.519> to<00:15:25.680> choose<00:15:26.320> to<00:15:26.480> to<00:15:26.639> to<00:15:26.839> just 00:15:27.470 --> 00:15:27.480 align:start position:0% the world to choose to to to just 00:15:27.480 --> 00:15:30.269 align:start position:0% the world to choose to to to just optimize<00:15:28.480> uh<00:15:28.600> my<00:15:29.279> system<00:15:29.720> based<00:15:30.000> on<00:15:30.160> the 00:15:30.269 --> 00:15:30.279 align:start position:0% optimize uh my system based on the 00:15:30.279 --> 00:15:32.990 align:start position:0% optimize uh my system based on the origin<00:15:30.639> and<00:15:30.800> destination<00:15:31.720> chains<00:15:32.720> and<00:15:32.839> this 00:15:32.990 --> 00:15:33.000 align:start position:0% origin and destination chains and this 00:15:33.000 --> 00:15:36.990 align:start position:0% origin and destination chains and this works<00:15:33.319> with<00:15:34.079> um<00:15:34.519> egay<00:15:35.519> uh<00:15:35.720> polygon<00:15:36.639> can<00:15:36.800> we<00:15:36.880> can 00:15:36.990 --> 00:15:37.000 align:start position:0% works with um egay uh polygon can we can 00:15:37.000 --> 00:15:38.629 align:start position:0% works with um egay uh polygon can we can use<00:15:37.160> the<00:15:37.240> polygon<00:15:37.600> a<00:15:37.839> layer<00:15:38.120> system<00:15:38.399> where<00:15:38.519> if 00:15:38.629 --> 00:15:38.639 align:start position:0% use the polygon a layer system where if 00:15:38.639 --> 00:15:40.150 align:start position:0% use the polygon a layer system where if I<00:15:38.759> have<00:15:38.880> my<00:15:39.040> origin<00:15:39.360> and<00:15:39.519> destination<00:15:39.920> chain 00:15:40.150 --> 00:15:40.160 align:start position:0% I have my origin and destination chain 00:15:40.160 --> 00:15:42.670 align:start position:0% I have my origin and destination chain is<00:15:40.360> both<00:15:40.560> EG<00:15:40.839> layer<00:15:41.160> enabled<00:15:41.639> chains<00:15:42.440> I<00:15:42.519> can 00:15:42.670 --> 00:15:42.680 align:start position:0% is both EG layer enabled chains I can 00:15:42.680 --> 00:15:44.309 align:start position:0% is both EG layer enabled chains I can write<00:15:42.839> a<00:15:42.959> settlement<00:15:43.360> system<00:15:43.639> that<00:15:43.759> uses<00:15:44.040> EG 00:15:44.309 --> 00:15:44.319 align:start position:0% write a settlement system that uses EG 00:15:44.319 --> 00:15:48.829 align:start position:0% write a settlement system that uses EG layer<00:15:44.959> to<00:15:45.360> to<00:15:46.199> uh<00:15:46.600> to<00:15:46.880> speed<00:15:47.240> up<00:15:47.519> solver 00:15:48.829 --> 00:15:48.839 align:start position:0% layer to to uh to speed up solver 00:15:48.839 --> 00:15:51.949 align:start position:0% layer to to uh to speed up solver repayment<00:15:49.839> and<00:15:50.040> Jesse<00:15:50.440> talked<00:15:50.759> about<00:15:51.480> uh 00:15:51.949 --> 00:15:51.959 align:start position:0% repayment and Jesse talked about uh 00:15:51.959 --> 00:15:54.790 align:start position:0% repayment and Jesse talked about uh coinbase's<00:15:52.639> push<00:15:53.079> coinbase<00:15:53.800> uh<00:15:54.040> Wilson<00:15:54.399> kusk 00:15:54.790 --> 00:15:54.800 align:start position:0% coinbase's push coinbase uh Wilson kusk 00:15:54.800 --> 00:15:56.629 align:start position:0% coinbase's push coinbase uh Wilson kusk and<00:15:54.880> Jack<00:15:55.079> Kuma<00:15:55.399> from<00:15:55.560> coinbase<00:15:55.959> are<00:15:56.399> doing 00:15:56.629 --> 00:15:56.639 align:start position:0% and Jack Kuma from coinbase are doing 00:15:56.639 --> 00:15:59.670 align:start position:0% and Jack Kuma from coinbase are doing this<00:15:56.800> really<00:15:56.959> Innovative<00:15:57.440> push<00:15:57.759> for<00:15:58.120> rip7<00:15:58.959> 755 00:15:59.670 --> 00:15:59.680 align:start position:0% this really Innovative push for rip7 755 00:15:59.680 --> 00:16:01.949 align:start position:0% this really Innovative push for rip7 755 which<00:15:59.759> is<00:15:59.880> like<00:16:00.000> a<00:16:00.160> trust<00:16:00.480> minimize<00:16:01.480> nested 00:16:01.949 --> 00:16:01.959 align:start position:0% which is like a trust minimize nested 00:16:01.959 --> 00:16:04.230 align:start position:0% which is like a trust minimize nested storage<00:16:02.440> proof<00:16:02.720> messaging<00:16:03.240> idea<00:16:03.920> we<00:16:04.040> could 00:16:04.230 --> 00:16:04.240 align:start position:0% storage proof messaging idea we could 00:16:04.240 --> 00:16:06.309 align:start position:0% storage proof messaging idea we could plug<00:16:04.560> that<00:16:04.720> in<00:16:04.920> as<00:16:05.000> a<00:16:05.120> settlement<00:16:05.600> system<00:16:06.199> and 00:16:06.309 --> 00:16:06.319 align:start position:0% plug that in as a settlement system and 00:16:06.319 --> 00:16:07.590 align:start position:0% plug that in as a settlement system and we're<00:16:06.600> actually<00:16:06.800> working<00:16:07.160> with<00:16:07.240> the<00:16:07.360> base 00:16:07.590 --> 00:16:07.600 align:start position:0% we're actually working with the base 00:16:07.600 --> 00:16:10.790 align:start position:0% we're actually working with the base team<00:16:07.800> on<00:16:07.920> a<00:16:08.040> proof<00:16:08.240> of<00:16:08.440> concept<00:16:09.360> to<00:16:09.519> do<00:16:09.880> just 00:16:10.790 --> 00:16:10.800 align:start position:0% team on a proof of concept to do just 00:16:10.800 --> 00:16:14.230 align:start position:0% team on a proof of concept to do just this<00:16:11.800> and<00:16:12.000> so<00:16:12.880> uh<00:16:13.120> what<00:16:13.279> I<00:16:13.399> find<00:16:13.720> super 00:16:14.230 --> 00:16:14.240 align:start position:0% this and so uh what I find super 00:16:14.240 --> 00:16:18.670 align:start position:0% this and so uh what I find super powerful<00:16:15.240> is<00:16:15.360> that<00:16:15.680> 7683<00:16:16.680> supports<00:16:17.639> any<00:16:17.920> settl 00:16:18.670 --> 00:16:18.680 align:start position:0% powerful is that 7683 supports any settl 00:16:18.680 --> 00:16:22.470 align:start position:0% powerful is that 7683 supports any settl system<00:16:19.680> uh<00:16:20.000> super<00:16:20.319> chain<00:16:20.920> 7755<00:16:21.720> egay<00:16:22.120> elastic 00:16:22.470 --> 00:16:22.480 align:start position:0% system uh super chain 7755 egay elastic 00:16:22.480 --> 00:16:26.749 align:start position:0% system uh super chain 7755 egay elastic chain<00:16:23.480> chain<00:16:23.920> clusters<00:16:24.920> succinct<00:16:25.560> sp1<00:16:26.560> if<00:16:26.639> I 00:16:26.749 --> 00:16:26.759 align:start position:0% chain chain clusters succinct sp1 if I 00:16:26.759 --> 00:16:27.990 align:start position:0% chain chain clusters succinct sp1 if I want<00:16:26.880> to<00:16:27.000> write<00:16:27.160> a<00:16:27.240> settlement<00:16:27.639> system<00:16:27.880> that 00:16:27.990 --> 00:16:28.000 align:start position:0% want to write a settlement system that 00:16:28.000 --> 00:16:30.230 align:start position:0% want to write a settlement system that uses<00:16:28.279> ZK<00:16:28.680> proof<00:16:28.920> Pro<00:16:29.480> to<00:16:29.680> prove<00:16:29.959> that<00:16:30.079> an 00:16:30.230 --> 00:16:30.240 align:start position:0% uses ZK proof Pro to prove that an 00:16:30.240 --> 00:16:33.269 align:start position:0% uses ZK proof Pro to prove that an intents<00:16:30.519> were<00:16:30.680> filled<00:16:31.079> I<00:16:31.160> can<00:16:31.319> do<00:16:32.000> that<00:16:33.000> if<00:16:33.120> you 00:16:33.269 --> 00:16:33.279 align:start position:0% intents were filled I can do that if you 00:16:33.279 --> 00:16:35.230 align:start position:0% intents were filled I can do that if you want<00:16:33.440> to<00:16:33.680> use<00:16:34.160> one<00:16:34.279> of<00:16:34.440> the<00:16:34.560> other<00:16:34.759> generalized 00:16:35.230 --> 00:16:35.240 align:start position:0% want to use one of the other generalized 00:16:35.240 --> 00:16:36.749 align:start position:0% want to use one of the other generalized messaging<00:16:35.639> passing<00:16:35.920> Frameworks<00:16:36.360> like<00:16:36.480> ler 00:16:36.749 --> 00:16:36.759 align:start position:0% messaging passing Frameworks like ler 00:16:36.759 --> 00:16:39.110 align:start position:0% messaging passing Frameworks like ler zero<00:16:36.959> hyperlane<00:16:37.319> Wormhole<00:16:37.959> chain<00:16:38.199> link<00:16:38.399> ccip 00:16:39.110 --> 00:16:39.120 align:start position:0% zero hyperlane Wormhole chain link ccip 00:16:39.120 --> 00:16:42.829 align:start position:0% zero hyperlane Wormhole chain link ccip completely<00:16:39.519> compatible<00:16:40.160> too<00:16:41.160> um<00:16:41.519> and<00:16:41.759> so<00:16:42.480> this 00:16:42.829 --> 00:16:42.839 align:start position:0% completely compatible too um and so this 00:16:42.839 --> 00:16:45.910 align:start position:0% completely compatible too um and so this standard<00:16:43.839> transparently<00:16:44.680> upgrades<00:16:45.680> with 00:16:45.910 --> 00:16:45.920 align:start position:0% standard transparently upgrades with 00:16:45.920 --> 00:16:48.749 align:start position:0% standard transparently upgrades with whatever<00:16:46.680> the<00:16:46.880> latest<00:16:47.319> and<00:16:47.560> greatest<00:16:48.120> interop 00:16:48.749 --> 00:16:48.759 align:start position:0% whatever the latest and greatest interop 00:16:48.759 --> 00:16:51.629 align:start position:0% whatever the latest and greatest interop techniques<00:16:49.360> are<00:16:50.360> and<00:16:50.720> uh<00:16:50.880> Ben<00:16:51.120> Jones<00:16:51.480> was 00:16:51.629 --> 00:16:51.639 align:start position:0% techniques are and uh Ben Jones was 00:16:51.639 --> 00:16:52.990 align:start position:0% techniques are and uh Ben Jones was talking<00:16:51.839> about<00:16:52.000> this<00:16:52.120> being<00:16:52.240> a<00:16:52.360> mullet<00:16:52.759> right 00:16:52.990 --> 00:16:53.000 align:start position:0% talking about this being a mullet right 00:16:53.000 --> 00:16:55.069 align:start position:0% talking about this being a mullet right we<00:16:53.120> put<00:16:53.279> the<00:16:53.399> standard<00:16:53.759> in<00:16:53.880> the<00:16:54.000> front<00:16:54.800> and<00:16:54.959> I 00:16:55.069 --> 00:16:55.079 align:start position:0% we put the standard in the front and I 00:16:55.079 --> 00:16:57.710 align:start position:0% we put the standard in the front and I got<00:16:55.240> this<00:16:55.360> party<00:16:55.639> in<00:16:55.720> the<00:16:55.920> back<00:16:56.560> with<00:16:56.839> whatever 00:16:57.710 --> 00:16:57.720 align:start position:0% got this party in the back with whatever 00:16:57.720 --> 00:17:01.829 align:start position:0% got this party in the back with whatever whatever<00:16:58.720> uh<00:16:59.319> infrastructure<00:17:00.319> best<00:17:00.839> serves 00:17:01.829 --> 00:17:01.839 align:start position:0% whatever uh infrastructure best serves 00:17:01.839 --> 00:17:04.470 align:start position:0% whatever uh infrastructure best serves verifying<00:17:02.440> that<00:17:02.639> intent<00:17:03.480> we<00:17:03.639> can<00:17:03.800> seamlessly 00:17:04.470 --> 00:17:04.480 align:start position:0% verifying that intent we can seamlessly 00:17:04.480 --> 00:17:07.309 align:start position:0% verifying that intent we can seamlessly upgrade<00:17:05.120> and<00:17:05.280> utilize 00:17:07.309 --> 00:17:07.319 align:start position:0% upgrade and utilize 00:17:07.319 --> 00:17:10.590 align:start position:0% upgrade and utilize that<00:17:08.319> why<00:17:08.439> is<00:17:08.559> this<00:17:08.720> standard<00:17:09.360> helpful<00:17:10.360> so 00:17:10.590 --> 00:17:10.600 align:start position:0% that why is this standard helpful so 00:17:10.600 --> 00:17:12.829 align:start position:0% that why is this standard helpful so Developers<00:17:11.400> for<00:17:11.600> both<00:17:11.760> the<00:17:11.880> app<00:17:12.039> and<00:17:12.160> wallet 00:17:12.829 --> 00:17:12.839 align:start position:0% Developers for both the app and wallet 00:17:12.839 --> 00:17:15.029 align:start position:0% Developers for both the app and wallet we<00:17:13.000> now<00:17:13.199> have<00:17:13.319> a<00:17:13.520> single<00:17:13.959> common<00:17:14.280> format<00:17:14.679> to<00:17:14.880> do 00:17:15.029 --> 00:17:15.039 align:start position:0% we now have a single common format to do 00:17:15.039 --> 00:17:18.029 align:start position:0% we now have a single common format to do anything<00:17:15.319> cross<00:17:15.640> chain<00:17:16.559> developers<00:17:17.280> should 00:17:18.029 --> 00:17:18.039 align:start position:0% anything cross chain developers should 00:17:18.039 --> 00:17:21.429 align:start position:0% anything cross chain developers should implement<00:17:18.439> this<00:17:18.559> standard<00:17:19.480> just<00:17:20.000> works<00:17:21.000> um 00:17:21.429 --> 00:17:21.439 align:start position:0% implement this standard just works um 00:17:21.439 --> 00:17:22.549 align:start position:0% implement this standard just works um and<00:17:21.640> again<00:17:22.000> it<00:17:22.160> is<00:17:22.280> going<00:17:22.360> to<00:17:22.439> be 00:17:22.549 --> 00:17:22.559 align:start position:0% and again it is going to be 00:17:22.559 --> 00:17:24.390 align:start position:0% and again it is going to be transparently<00:17:23.199> upgradeable<00:17:23.799> as<00:17:23.919> we<00:17:24.079> get 00:17:24.390 --> 00:17:24.400 align:start position:0% transparently upgradeable as we get 00:17:24.400 --> 00:17:26.510 align:start position:0% transparently upgradeable as we get better<00:17:25.199> Technologies<00:17:25.880> to<00:17:26.079> verify<00:17:26.439> the 00:17:26.510 --> 00:17:26.520 align:start position:0% better Technologies to verify the 00:17:26.520 --> 00:17:29.430 align:start position:0% better Technologies to verify the settlement<00:17:27.079> layer<00:17:28.079> for<00:17:28.240> solvers 00:17:29.430 --> 00:17:29.440 align:start position:0% settlement layer for solvers 00:17:29.440 --> 00:17:32.669 align:start position:0% settlement layer for solvers solvers<00:17:30.039> now<00:17:30.880> um<00:17:31.080> don't<00:17:31.600> listen<00:17:31.919> to<00:17:32.120> like<00:17:32.320> one 00:17:32.669 --> 00:17:32.679 align:start position:0% solvers now um don't listen to like one 00:17:32.679 --> 00:17:34.510 align:start position:0% solvers now um don't listen to like one common<00:17:33.080> format<00:17:33.640> without<00:17:33.880> needing<00:17:34.200> custom 00:17:34.510 --> 00:17:34.520 align:start position:0% common format without needing custom 00:17:34.520 --> 00:17:36.870 align:start position:0% common format without needing custom Integrations<00:17:35.080> for<00:17:35.240> each<00:17:35.440> new<00:17:35.640> protocol<00:17:36.600> so 00:17:36.870 --> 00:17:36.880 align:start position:0% Integrations for each new protocol so 00:17:36.880 --> 00:17:38.990 align:start position:0% Integrations for each new protocol so solvers<00:17:37.240> just<00:17:37.400> listen<00:17:37.720> to<00:17:37.840> the<00:17:37.960> 7683<00:17:38.720> order 00:17:38.990 --> 00:17:39.000 align:start position:0% solvers just listen to the 7683 order 00:17:39.000 --> 00:17:41.110 align:start position:0% solvers just listen to the 7683 order standard<00:17:39.600> and<00:17:39.799> any<00:17:40.120> intent<00:17:40.480> based<00:17:40.760> protocol 00:17:41.110 --> 00:17:41.120 align:start position:0% standard and any intent based protocol 00:17:41.120 --> 00:17:43.909 align:start position:0% standard and any intent based protocol that<00:17:41.200> builds<00:17:41.480> on<00:17:41.679> top<00:17:41.840> of<00:17:42.000> it<00:17:42.679> um<00:17:43.200> uh<00:17:43.440> is<00:17:43.720> is 00:17:43.909 --> 00:17:43.919 align:start position:0% that builds on top of it um uh is is 00:17:43.919 --> 00:17:45.750 align:start position:0% that builds on top of it um uh is is they're<00:17:44.160> able<00:17:44.360> to 00:17:45.750 --> 00:17:45.760 align:start position:0% they're able to 00:17:45.760 --> 00:17:51.549 align:start position:0% they're able to serve<00:17:46.760> okay<00:17:47.559> so<00:17:49.039> um<00:17:50.039> across<00:17:50.600> and<00:17:50.760> Unis<00:17:51.160> swap 00:17:51.549 --> 00:17:51.559 align:start position:0% serve okay so um across and Unis swap 00:17:51.559 --> 00:17:53.470 align:start position:0% serve okay so um across and Unis swap work<00:17:52.039> together<00:17:52.320> to<00:17:52.480> develop<00:17:52.880> this<00:17:53.039> initial 00:17:53.470 --> 00:17:53.480 align:start position:0% work together to develop this initial 00:17:53.480 --> 00:17:55.510 align:start position:0% work together to develop this initial standard<00:17:54.480> uh<00:17:54.600> we<00:17:54.720> got<00:17:54.880> a<00:17:55.000> lot<00:17:55.159> of<00:17:55.320> great 00:17:55.510 --> 00:17:55.520 align:start position:0% standard uh we got a lot of great 00:17:55.520 --> 00:17:58.190 align:start position:0% standard uh we got a lot of great feedback<00:17:56.320> um<00:17:56.440> from<00:17:56.600> many<00:17:56.799> people<00:17:57.000> in<00:17:57.240> space<00:17:58.080> uh 00:17:58.190 --> 00:17:58.200 align:start position:0% feedback um from many people in space uh 00:17:58.200 --> 00:17:59.590 align:start position:0% feedback um from many people in space uh that<00:17:58.320> feedback<00:17:58.640> was<00:17:58.919> actually<00:17:59.080> merged<00:17:59.400> in 00:17:59.590 --> 00:17:59.600 align:start position:0% that feedback was actually merged in 00:17:59.600 --> 00:18:00.990 align:start position:0% that feedback was actually merged in about<00:17:59.799> two<00:17:59.960> weeks<00:18:00.159> ago<00:18:00.400> so<00:18:00.559> anybody<00:18:00.840> who's 00:18:00.990 --> 00:18:01.000 align:start position:0% about two weeks ago so anybody who's 00:18:01.000 --> 00:18:02.789 align:start position:0% about two weeks ago so anybody who's read<00:18:01.159> the<00:18:01.280> standard<00:18:01.720> go<00:18:01.960> read<00:18:02.120> it<00:18:02.320> again<00:18:02.640> it's 00:18:02.789 --> 00:18:02.799 align:start position:0% read the standard go read it again it's 00:18:02.799 --> 00:18:04.710 align:start position:0% read the standard go read it again it's been<00:18:02.960> updated<00:18:03.840> uh<00:18:03.960> and<00:18:04.039> if<00:18:04.120> you<00:18:04.240> want<00:18:04.320> to<00:18:04.480> read 00:18:04.710 --> 00:18:04.720 align:start position:0% been updated uh and if you want to read 00:18:04.720 --> 00:18:09.630 align:start position:0% been updated uh and if you want to read more<00:18:05.240> ERC<00:18:05.960> 7683<00:18:06.960> org<00:18:07.360> has<00:18:07.520> all<00:18:07.679> the<00:18:08.159> details<00:18:09.159> um 00:18:09.630 --> 00:18:09.640 align:start position:0% more ERC 7683 org has all the details um 00:18:09.640 --> 00:18:11.310 align:start position:0% more ERC 7683 org has all the details um but<00:18:09.840> we've<00:18:10.039> been<00:18:10.159> trying<00:18:10.360> to<00:18:10.640> build<00:18:10.960> support 00:18:11.310 --> 00:18:11.320 align:start position:0% but we've been trying to build support 00:18:11.320 --> 00:18:14.909 align:start position:0% but we've been trying to build support for<00:18:11.520> the<00:18:12.039> standard<00:18:13.039> and<00:18:13.360> uh<00:18:13.520> optimism<00:18:14.440> um<00:18:14.600> was 00:18:14.909 --> 00:18:14.919 align:start position:0% for the standard and uh optimism um was 00:18:14.919 --> 00:18:17.750 align:start position:0% for the standard and uh optimism um was an<00:18:15.159> early<00:18:15.600> adopter<00:18:16.600> uh<00:18:16.960> they<00:18:17.320> uh<00:18:17.559> they 00:18:17.750 --> 00:18:17.760 align:start position:0% an early adopter uh they uh they 00:18:17.760 --> 00:18:19.070 align:start position:0% an early adopter uh they uh they understood<00:18:18.360> that<00:18:18.559> even<00:18:18.760> though<00:18:18.919> they're 00:18:19.070 --> 00:18:19.080 align:start position:0% understood that even though they're 00:18:19.080 --> 00:18:21.310 align:start position:0% understood that even though they're working<00:18:19.360> on<00:18:19.559> Super<00:18:19.840> chain<00:18:20.080> native<00:18:20.360> interop 00:18:21.310 --> 00:18:21.320 align:start position:0% working on Super chain native interop 00:18:21.320 --> 00:18:23.029 align:start position:0% working on Super chain native interop they<00:18:21.440> don't<00:18:21.760> just<00:18:21.919> want<00:18:22.159> interoperability 00:18:23.029 --> 00:18:23.039 align:start position:0% they don't just want interoperability 00:18:23.039 --> 00:18:24.750 align:start position:0% they don't just want interoperability between<00:18:23.280> the<00:18:23.400> super<00:18:23.720> chain<00:18:24.360> they<00:18:24.520> need 00:18:24.750 --> 00:18:24.760 align:start position:0% between the super chain they need 00:18:24.760 --> 00:18:26.549 align:start position:0% between the super chain they need interoperability<00:18:25.600> so<00:18:25.840> like<00:18:26.039> users<00:18:26.360> on 00:18:26.549 --> 00:18:26.559 align:start position:0% interoperability so like users on 00:18:26.559 --> 00:18:28.830 align:start position:0% interoperability so like users on arbitrum<00:18:27.120> can<00:18:27.280> come<00:18:27.440> to<00:18:27.559> the<00:18:27.679> super<00:18:27.960> chain<00:18:28.280> and 00:18:28.830 --> 00:18:28.840 align:start position:0% arbitrum can come to the super chain and 00:18:28.840 --> 00:18:30.710 align:start position:0% arbitrum can come to the super chain and what<00:18:29.039> have<00:18:29.240> you<00:18:29.840> and<00:18:29.960> they<00:18:30.080> also<00:18:30.559> understand 00:18:30.710 --> 00:18:30.720 align:start position:0% what have you and they also understand 00:18:30.720 --> 00:18:33.070 align:start position:0% what have you and they also understand that<00:18:30.880> the<00:18:31.120> standard<00:18:31.960> you<00:18:32.080> know<00:18:32.320> it<00:18:32.440> can<00:18:32.600> use 00:18:33.070 --> 00:18:33.080 align:start position:0% that the standard you know it can use 00:18:33.080 --> 00:18:34.669 align:start position:0% that the standard you know it can use super<00:18:33.400> chain<00:18:33.559> native<00:18:33.799> interop<00:18:34.240> on<00:18:34.360> the<00:18:34.520> back 00:18:34.669 --> 00:18:34.679 align:start position:0% super chain native interop on the back 00:18:34.679 --> 00:18:36.789 align:start position:0% super chain native interop on the back end<00:18:35.240> to<00:18:35.440> allow<00:18:35.679> for<00:18:35.880> faster<00:18:36.159> intent 00:18:36.789 --> 00:18:36.799 align:start position:0% end to allow for faster intent 00:18:36.799 --> 00:18:38.710 align:start position:0% end to allow for faster intent verification<00:18:37.799> so<00:18:38.000> they<00:18:38.159> thought<00:18:38.320> this<00:18:38.440> was<00:18:38.600> a 00:18:38.710 --> 00:18:38.720 align:start position:0% verification so they thought this was a 00:18:38.720 --> 00:18:41.350 align:start position:0% verification so they thought this was a good<00:18:38.880> idea<00:18:39.760> and<00:18:40.120> the<00:18:40.280> polygon<00:18:40.760> team<00:18:41.159> thought 00:18:41.350 --> 00:18:41.360 align:start position:0% good idea and the polygon team thought 00:18:41.360 --> 00:18:44.149 align:start position:0% good idea and the polygon team thought this<00:18:41.480> was<00:18:41.559> a<00:18:41.679> good<00:18:41.840> idea<00:18:42.720> and<00:18:42.880> I'm<00:18:43.080> going<00:18:43.159> to 00:18:44.149 --> 00:18:44.159 align:start position:0% this was a good idea and I'm going to 00:18:44.159 --> 00:18:45.710 align:start position:0% this was a good idea and I'm going to read<00:18:44.360> out<00:18:44.520> some<00:18:44.679> names<00:18:44.960> for<00:18:45.080> a<00:18:45.200> second<00:18:45.480> we<00:18:45.600> got 00:18:45.710 --> 00:18:45.720 align:start position:0% read out some names for a second we got 00:18:45.720 --> 00:18:48.549 align:start position:0% read out some names for a second we got Linea<00:18:46.400> we<00:18:46.520> got<00:18:46.640> Alchemy<00:18:47.280> we<00:18:47.400> got<00:18:47.559> blast<00:18:48.400> got 00:18:48.549 --> 00:18:48.559 align:start position:0% Linea we got Alchemy we got blast got 00:18:48.559 --> 00:18:52.590 align:start position:0% Linea we got Alchemy we got blast got conduit<00:18:49.200> Manta<00:18:50.159> grow<00:18:50.440> the<00:18:50.640> pie<00:18:51.120> mantle<00:18:51.799> mode 00:18:52.590 --> 00:18:52.600 align:start position:0% conduit Manta grow the pie mantle mode 00:18:52.600 --> 00:18:57.430 align:start position:0% conduit Manta grow the pie mantle mode Tao<00:18:53.760> suped<00:18:54.760> World<00:18:55.200> coin<00:18:55.760> Cony<00:18:56.320> stack<00:18:57.320> uh 00:18:57.430 --> 00:18:57.440 align:start position:0% Tao suped World coin Cony stack uh 00:18:57.440 --> 00:18:59.510 align:start position:0% Tao suped World coin Cony stack uh scroll<00:18:58.159> nethermind<00:18:58.880> I'm<00:18:59.000> almost<00:18:59.200> done<00:18:59.400> don't 00:18:59.510 --> 00:18:59.520 align:start position:0% scroll nethermind I'm almost done don't 00:18:59.520 --> 00:19:01.110 align:start position:0% scroll nethermind I'm almost done don't worry<00:19:00.120> um<00:19:00.280> alt 00:19:01.110 --> 00:19:01.120 align:start position:0% worry um alt 00:19:01.120 --> 00:19:02.630 align:start position:0% worry um alt layer 00:19:02.630 --> 00:19:02.640 align:start position:0% layer 00:19:02.640 --> 00:19:06.190 align:start position:0% layer aori<00:19:03.640> fluent<00:19:04.120> sub<00:19:04.400> wallet<00:19:05.039> open<00:19:05.360> social<00:19:05.880> zero 00:19:06.190 --> 00:19:06.200 align:start position:0% aori fluent sub wallet open social zero 00:19:06.200 --> 00:19:08.510 align:start position:0% aori fluent sub wallet open social zero Dev<00:19:06.480> Rin<00:19:06.840> Stone<00:19:07.559> we<00:19:07.679> had<00:19:07.840> a<00:19:07.960> whole<00:19:08.159> bunch<00:19:08.360> of 00:19:08.510 --> 00:19:08.520 align:start position:0% Dev Rin Stone we had a whole bunch of 00:19:08.520 --> 00:19:10.149 align:start position:0% Dev Rin Stone we had a whole bunch of teams<00:19:09.000> come<00:19:09.200> and<00:19:09.360> announce<00:19:09.679> support<00:19:09.919> for<00:19:10.039> the 00:19:10.149 --> 00:19:10.159 align:start position:0% teams come and announce support for the 00:19:10.159 --> 00:19:12.750 align:start position:0% teams come and announce support for the standard<00:19:10.679> which<00:19:11.280> honestly<00:19:11.760> guys<00:19:12.039> like<00:19:12.679> I 00:19:12.750 --> 00:19:12.760 align:start position:0% standard which honestly guys like I 00:19:12.760 --> 00:19:14.470 align:start position:0% standard which honestly guys like I didn't<00:19:13.240> really<00:19:13.640> think<00:19:13.880> this<00:19:14.000> would<00:19:14.200> happen 00:19:14.470 --> 00:19:14.480 align:start position:0% didn't really think this would happen 00:19:14.480 --> 00:19:17.110 align:start position:0% didn't really think this would happen that<00:19:14.640> well<00:19:14.880> and<00:19:15.240> it<00:19:15.360> did<00:19:15.559> it<00:19:15.640> was<00:19:16.000> pretty<00:19:16.240> cool 00:19:17.110 --> 00:19:17.120 align:start position:0% that well and it did it was pretty cool 00:19:17.120 --> 00:19:21.990 align:start position:0% that well and it did it was pretty cool um 00:19:21.990 --> 00:19:22.000 align:start position:0% 00:19:22.000 --> 00:19:24.350 align:start position:0% oh<00:19:23.000> I<00:19:23.080> will<00:19:23.280> tell<00:19:23.440> you<00:19:23.640> guys<00:19:23.799> so<00:19:23.960> we<00:19:24.080> had<00:19:24.200> this 00:19:24.350 --> 00:19:24.360 align:start position:0% oh I will tell you guys so we had this 00:19:24.360 --> 00:19:26.390 align:start position:0% oh I will tell you guys so we had this hole<00:19:24.720> here<00:19:25.200> right<00:19:25.480> so<00:19:25.679> this<00:19:25.760> is<00:19:25.880> a<00:19:26.000> hole<00:19:26.200> here 00:19:26.390 --> 00:19:26.400 align:start position:0% hole here right so this is a hole here 00:19:26.400 --> 00:19:28.350 align:start position:0% hole here right so this is a hole here as<00:19:26.520> of<00:19:26.720> like<00:19:26.880> two<00:19:27.080> days<00:19:27.280> ago<00:19:27.840> and<00:19:27.960> it<00:19:28.120> kind<00:19:28.240> of 00:19:28.350 --> 00:19:28.360 align:start position:0% as of like two days ago and it kind of 00:19:28.360 --> 00:19:30.390 align:start position:0% as of like two days ago and it kind of it<00:19:28.480> made<00:19:28.600> the<00:19:28.799> the<00:19:28.919> chart<00:19:29.159> look<00:19:29.480> more<00:19:29.720> annoying 00:19:30.390 --> 00:19:30.400 align:start position:0% it made the the chart look more annoying 00:19:30.400 --> 00:19:31.710 align:start position:0% it made the the chart look more annoying and<00:19:30.520> this<00:19:30.640> should<00:19:30.840> also<00:19:31.039> all<00:19:31.159> be<00:19:31.320> in<00:19:31.400> a<00:19:31.520> big 00:19:31.710 --> 00:19:31.720 align:start position:0% and this should also all be in a big 00:19:31.720 --> 00:19:33.350 align:start position:0% and this should also all be in a big tent<00:19:32.159> I<00:19:32.240> want<00:19:32.440> these<00:19:32.600> guys<00:19:32.760> all<00:19:32.840> in<00:19:32.919> a<00:19:33.039> big<00:19:33.159> tent 00:19:33.350 --> 00:19:33.360 align:start position:0% tent I want these guys all in a big tent 00:19:33.360 --> 00:19:36.270 align:start position:0% tent I want these guys all in a big tent but<00:19:33.440> it<00:19:33.520> didn't<00:19:33.679> fit<00:19:33.840> on<00:19:33.960> screen<00:19:34.400> so<00:19:35.280> um<00:19:35.880> I'm 00:19:36.270 --> 00:19:36.280 align:start position:0% but it didn't fit on screen so um I'm 00:19:36.280 --> 00:19:37.590 align:start position:0% but it didn't fit on screen so um I'm what's<00:19:36.480> cool<00:19:36.760> those<00:19:36.960> you<00:19:37.039> come<00:19:37.159> to<00:19:37.320> place<00:19:37.480> like 00:19:37.590 --> 00:19:37.600 align:start position:0% what's cool those you come to place like 00:19:37.600 --> 00:19:39.630 align:start position:0% what's cool those you come to place like Devcon<00:19:38.120> and<00:19:38.280> you<00:19:38.400> you<00:19:38.520> meet<00:19:38.760> people<00:19:39.080> and<00:19:39.240> you 00:19:39.630 --> 00:19:39.640 align:start position:0% Devcon and you you meet people and you 00:19:39.640 --> 00:19:40.669 align:start position:0% Devcon and you you meet people and you kind<00:19:39.760> of<00:19:39.880> get<00:19:40.000> them<00:19:40.120> over<00:19:40.280> the<00:19:40.400> line<00:19:40.559> and 00:19:40.669 --> 00:19:40.679 align:start position:0% kind of get them over the line and 00:19:40.679 --> 00:19:42.230 align:start position:0% kind of get them over the line and explain<00:19:40.960> what<00:19:41.080> you're<00:19:41.200> working<00:19:41.440> on<00:19:42.000> and<00:19:42.080> so 00:19:42.230 --> 00:19:42.240 align:start position:0% explain what you're working on and so 00:19:42.240 --> 00:19:44.909 align:start position:0% explain what you're working on and so now<00:19:42.400> we<00:19:42.559> have<00:19:42.919> both<00:19:43.480> arbitrum<00:19:44.280> with<00:19:44.440> offchain 00:19:44.909 --> 00:19:44.919 align:start position:0% now we have both arbitrum with offchain 00:19:44.919 --> 00:19:48.710 align:start position:0% now we have both arbitrum with offchain labs<00:19:45.679> and<00:19:45.880> ZK<00:19:46.280> sync<00:19:47.159> uh<00:19:47.280> M<00:19:47.600> lamb<00:19:47.799> ZK<00:19:48.120> sync<00:19:48.440> also 00:19:48.710 --> 00:19:48.720 align:start position:0% labs and ZK sync uh M lamb ZK sync also 00:19:48.720 --> 00:19:50.510 align:start position:0% labs and ZK sync uh M lamb ZK sync also supporting<00:19:49.120> the<00:19:49.280> standard<00:19:50.039> which<00:19:50.159> means<00:19:50.400> we 00:19:50.510 --> 00:19:50.520 align:start position:0% supporting the standard which means we 00:19:50.520 --> 00:19:52.350 align:start position:0% supporting the standard which means we have<00:19:50.720> like<00:19:50.919> complete<00:19:51.360> coverage<00:19:51.880> of<00:19:52.000> the<00:19:52.120> major 00:19:52.350 --> 00:19:52.360 align:start position:0% have like complete coverage of the major 00:19:52.360 --> 00:19:55.350 align:start position:0% have like complete coverage of the major L2<00:19:52.799> ecosystems<00:19:53.799> saying<00:19:54.400> you<00:19:54.559> know<00:19:55.039> hey<00:19:55.240> we 00:19:55.350 --> 00:19:55.360 align:start position:0% L2 ecosystems saying you know hey we 00:19:55.360 --> 00:19:56.830 align:start position:0% L2 ecosystems saying you know hey we think<00:19:55.559> this<00:19:55.640> is<00:19:55.760> a<00:19:55.880> good<00:19:56.080> idea<00:19:56.520> just<00:19:56.640> like 00:19:56.830 --> 00:19:56.840 align:start position:0% think this is a good idea just like 00:19:56.840 --> 00:19:59.230 align:start position:0% think this is a good idea just like erc20<00:19:57.520> is<00:19:57.640> defined<00:19:57.919> a<00:19:58.039> token<00:19:58.280> standard<00:19:59.120> we 00:19:59.230 --> 00:19:59.240 align:start position:0% erc20 is defined a token standard we 00:19:59.240 --> 00:20:00.430 align:start position:0% erc20 is defined a token standard we think<00:19:59.440> this<00:19:59.520> is<00:19:59.640> a<00:19:59.760> pretty<00:19:59.960> cool<00:20:00.159> way<00:20:00.280> to 00:20:00.430 --> 00:20:00.440 align:start position:0% think this is a pretty cool way to 00:20:00.440 --> 00:20:01.990 align:start position:0% think this is a pretty cool way to define<00:20:00.679> a<00:20:00.760> standard<00:20:01.039> for 00:20:01.990 --> 00:20:02.000 align:start position:0% define a standard for 00:20:02.000 --> 00:20:05.270 align:start position:0% define a standard for intents<00:20:03.000> um<00:20:03.919> okay<00:20:04.080> so<00:20:04.320> I'm<00:20:04.480> almost<00:20:04.720> done<00:20:05.039> so 00:20:05.270 --> 00:20:05.280 align:start position:0% intents um okay so I'm almost done so 00:20:05.280 --> 00:20:08.950 align:start position:0% intents um okay so I'm almost done so what's<00:20:05.559> next<00:20:06.480> um<00:20:06.880> we<00:20:07.000> have<00:20:07.360> broad<00:20:07.679> support<00:20:08.679> um 00:20:08.950 --> 00:20:08.960 align:start position:0% what's next um we have broad support um 00:20:08.960 --> 00:20:10.390 align:start position:0% what's next um we have broad support um I've<00:20:09.240> I've<00:20:09.400> never<00:20:09.600> tried<00:20:09.799> to<00:20:09.919> build<00:20:10.159> support 00:20:10.390 --> 00:20:10.400 align:start position:0% I've I've never tried to build support 00:20:10.400 --> 00:20:12.270 align:start position:0% I've I've never tried to build support for<00:20:10.640> standard<00:20:11.000> before<00:20:11.559> working<00:20:11.840> with<00:20:11.960> Unis 00:20:12.270 --> 00:20:12.280 align:start position:0% for standard before working with Unis 00:20:12.280 --> 00:20:14.190 align:start position:0% for standard before working with Unis swap<00:20:12.480> it's<00:20:12.600> been<00:20:12.799> great<00:20:13.240> but<00:20:13.640> many<00:20:13.880> people<00:20:14.080> in 00:20:14.190 --> 00:20:14.200 align:start position:0% swap it's been great but many people in 00:20:14.200 --> 00:20:16.110 align:start position:0% swap it's been great but many people in this<00:20:14.320> ecoystem<00:20:14.880> are<00:20:15.039> just<00:20:15.159> like<00:20:15.400> hey<00:20:15.679> yeah 00:20:16.110 --> 00:20:16.120 align:start position:0% this ecoystem are just like hey yeah 00:20:16.120 --> 00:20:17.750 align:start position:0% this ecoystem are just like hey yeah there's<00:20:16.400> good<00:20:16.640> Social<00:20:17.039> Capital<00:20:17.400> to<00:20:17.520> try<00:20:17.640> to 00:20:17.750 --> 00:20:17.760 align:start position:0% there's good Social Capital to try to 00:20:17.760 --> 00:20:19.750 align:start position:0% there's good Social Capital to try to unify<00:20:18.159> ethereum<00:20:18.960> and<00:20:19.080> this<00:20:19.159> is<00:20:19.280> a<00:20:19.360> lightweight 00:20:19.750 --> 00:20:19.760 align:start position:0% unify ethereum and this is a lightweight 00:20:19.760 --> 00:20:21.110 align:start position:0% unify ethereum and this is a lightweight standard<00:20:20.039> that<00:20:20.159> lets<00:20:20.320> us<00:20:20.440> do<00:20:20.640> this<00:20:20.799> so<00:20:20.960> we've 00:20:21.110 --> 00:20:21.120 align:start position:0% standard that lets us do this so we've 00:20:21.120 --> 00:20:24.350 align:start position:0% standard that lets us do this so we've got<00:20:21.400> broad<00:20:21.799> support<00:20:22.679> um<00:20:23.039> from<00:20:23.360> the<00:20:23.520> L2 00:20:24.350 --> 00:20:24.360 align:start position:0% got broad support um from the L2 00:20:24.360 --> 00:20:26.830 align:start position:0% got broad support um from the L2 ecosystems<00:20:25.360> we<00:20:25.480> need<00:20:25.640> to<00:20:25.840> figure<00:20:26.120> out<00:20:26.480> better 00:20:26.830 --> 00:20:26.840 align:start position:0% ecosystems we need to figure out better 00:20:26.840 --> 00:20:29.669 align:start position:0% ecosystems we need to figure out better dap<00:20:27.159> and<00:20:27.320> wallet<00:20:27.640> ux<00:20:28.000> patterns<00:20:29.039> um<00:20:29.400> that's 00:20:29.669 --> 00:20:29.679 align:start position:0% dap and wallet ux patterns um that's 00:20:29.679 --> 00:20:32.590 align:start position:0% dap and wallet ux patterns um that's like<00:20:29.840> the<00:20:30.039> next<00:20:30.400> step<00:20:31.200> here<00:20:32.200> and<00:20:32.280> then<00:20:32.440> we 00:20:32.590 --> 00:20:32.600 align:start position:0% like the next step here and then we 00:20:32.600 --> 00:20:33.830 align:start position:0% like the next step here and then we really<00:20:32.799> want<00:20:32.919> to<00:20:33.080> do<00:20:33.280> this<00:20:33.440> like<00:20:33.600> full 00:20:33.830 --> 00:20:33.840 align:start position:0% really want to do this like full 00:20:33.840 --> 00:20:35.870 align:start position:0% really want to do this like full integration<00:20:34.360> with<00:20:34.520> 7702<00:20:35.400> what<00:20:35.480> I<00:20:35.559> was<00:20:35.679> talking 00:20:35.870 --> 00:20:35.880 align:start position:0% integration with 7702 what I was talking 00:20:35.880 --> 00:20:37.750 align:start position:0% integration with 7702 what I was talking about<00:20:36.080> before<00:20:36.720> for<00:20:36.919> this<00:20:37.080> beautiful<00:20:37.440> chain 00:20:37.750 --> 00:20:37.760 align:start position:0% about before for this beautiful chain 00:20:37.760 --> 00:20:41.270 align:start position:0% about before for this beautiful chain abstraction<00:20:38.760> where<00:20:39.000> I<00:20:39.240> I<00:20:39.400> use<00:20:39.760> a 00:20:41.270 --> 00:20:41.280 align:start position:0% abstraction where I I use a 00:20:41.280 --> 00:20:45.310 align:start position:0% abstraction where I I use a 7702<00:20:42.280> kind<00:20:42.360> of<00:20:42.520> user<00:20:42.880> op<00:20:43.520> payload<00:20:44.360> to<00:20:44.799> have<00:20:45.159> uh 00:20:45.310 --> 00:20:45.320 align:start position:0% 7702 kind of user op payload to have uh 00:20:45.320 --> 00:20:47.270 align:start position:0% 7702 kind of user op payload to have uh the<00:20:45.440> ability<00:20:45.880> to<00:20:46.039> do<00:20:46.280> a<00:20:46.520> a<00:20:46.600> remote<00:20:46.919> control 00:20:47.270 --> 00:20:47.280 align:start position:0% the ability to do a a remote control 00:20:47.280 --> 00:20:48.870 align:start position:0% the ability to do a a remote control where<00:20:47.400> I<00:20:47.480> can<00:20:47.640> remotely<00:20:48.080> execute<00:20:48.480> any<00:20:48.679> action 00:20:48.870 --> 00:20:48.880 align:start position:0% where I can remotely execute any action 00:20:48.880 --> 00:20:50.870 align:start position:0% where I can remotely execute any action on<00:20:49.000> a<00:20:49.159> destination<00:20:50.039> uh 00:20:50.870 --> 00:20:50.880 align:start position:0% on a destination uh 00:20:50.880 --> 00:20:53.669 align:start position:0% on a destination uh chain<00:20:51.880> um<00:20:52.679> and<00:20:52.760> so<00:20:52.919> guys<00:20:53.120> that's<00:20:53.360> that's<00:20:53.520> my 00:20:53.669 --> 00:20:53.679 align:start position:0% chain um and so guys that's that's my 00:20:53.679 --> 00:20:54.669 align:start position:0% chain um and so guys that's that's my pitch<00:20:53.919> for<00:20:54.039> how<00:20:54.120> we're<00:20:54.200> going<00:20:54.280> to<00:20:54.360> unify 00:20:54.669 --> 00:20:54.679 align:start position:0% pitch for how we're going to unify 00:20:54.679 --> 00:20:55.789 align:start position:0% pitch for how we're going to unify ethereum<00:20:55.120> and<00:20:55.200> how<00:20:55.280> we're<00:20:55.400> going<00:20:55.480> to<00:20:55.559> do<00:20:55.679> it 00:20:55.789 --> 00:20:55.799 align:start position:0% ethereum and how we're going to do it 00:20:55.799 --> 00:20:58.350 align:start position:0% ethereum and how we're going to do it quickly<00:20:56.520> in<00:20:56.760> 2025<00:20:57.760> it's<00:20:57.919> not<00:20:58.039> going<00:20:58.120> to<00:20:58.240> take 00:20:58.350 --> 00:20:58.360 align:start position:0% quickly in 2025 it's not going to take 00:20:58.360 --> 00:21:00.549 align:start position:0% quickly in 2025 it's not going to take us<00:20:58.679> four<00:20:58.919> years<00:20:59.480> we're<00:20:59.600> going<00:20:59.679> to<00:20:59.760> use<00:20:59.960> intense 00:21:00.549 --> 00:21:00.559 align:start position:0% us four years we're going to use intense 00:21:00.559 --> 00:21:03.909 align:start position:0% us four years we're going to use intense and<00:21:00.679> the<00:21:00.799> 7683<00:21:01.559> standard<00:21:02.120> to<00:21:02.280> unify<00:21:02.919> ethereum 00:21:03.909 --> 00:21:03.919 align:start position:0% and the 7683 standard to unify ethereum 00:21:03.919 --> 00:21:06.270 align:start position:0% and the 7683 standard to unify ethereum um<00:21:04.120> you<00:21:04.200> can<00:21:04.360> follow<00:21:04.559> me<00:21:04.640> on<00:21:04.760> Twitter<00:21:05.159> at<00:21:05.320> h01 00:21:06.270 --> 00:21:06.280 align:start position:0% um you can follow me on Twitter at h01 00:21:06.280 --> 00:21:07.880 align:start position:0% um you can follow me on Twitter at h01 and<00:21:06.400> thank<00:21:06.559> you<00:21:06.679> very 00:21:07.880 --> 00:21:07.890 align:start position:0% and thank you very 00:21:07.890 --> 00:21:16.590 align:start position:0% and thank you very [Applause] 00:21:16.590 --> 00:21:16.600 align:start position:0% 00:21:16.600 --> 00:21:23.470 align:start position:0% much<00:21:17.600> you<00:21:17.760> want<00:21:18.320> want<00:21:18.480> me<00:21:18.559> to<00:21:18.679> do 00:21:23.470 --> 00:21:23.480 align:start position:0% 00:21:23.480 --> 00:21:25.909 align:start position:0% it<00:21:24.480> yeah<00:21:24.720> I<00:21:24.840> think<00:21:24.919> it's<00:21:25.039> running<00:21:25.320> out<00:21:25.480> of<00:21:25.640> the 00:21:25.909 --> 00:21:25.919 align:start position:0% it yeah I think it's running out of the 00:21:25.919 --> 00:21:29.190 align:start position:0% it yeah I think it's running out of the battery<00:21:26.799> maybe<00:21:27.799> yes<00:21:27.960> can<00:21:28.080> you<00:21:28.159> check<00:21:28.360> it 00:21:29.190 --> 00:21:29.200 align:start position:0% battery maybe yes can you check it 00:21:29.200 --> 00:21:31.750 align:start position:0% battery maybe yes can you check it thank<00:21:29.400> you<00:21:30.159> I'm<00:21:30.400> personally<00:21:30.960> excited<00:21:31.520> about 00:21:31.750 --> 00:21:31.760 align:start position:0% thank you I'm personally excited about 00:21:31.760 --> 00:21:35.029 align:start position:0% thank you I'm personally excited about what<00:21:31.880> you're<00:21:32.039> just<00:21:32.200> sharing<00:21:32.760> it's<00:21:33.799> huge<00:21:34.799> it's 00:21:35.029 --> 00:21:35.039 align:start position:0% what you're just sharing it's huge it's 00:21:35.039 --> 00:21:37.990 align:start position:0% what you're just sharing it's huge it's huge<00:21:35.400> all<00:21:35.520> right<00:21:35.679> let's<00:21:35.880> talk<00:21:36.039> about<00:21:36.679> uh<00:21:37.000> Q&A 00:21:37.990 --> 00:21:38.000 align:start position:0% huge all right let's talk about uh Q&A 00:21:38.000 --> 00:21:40.750 align:start position:0% huge all right let's talk about uh Q&A uh<00:21:38.240> will<00:21:38.559> this<00:21:38.880> new<00:21:39.080> standard<00:21:39.559> support 00:21:40.750 --> 00:21:40.760 align:start position:0% uh will this new standard support 00:21:40.760 --> 00:21:43.390 align:start position:0% uh will this new standard support nft<00:21:41.760> okay<00:21:42.080> I<00:21:42.200> gotta<00:21:42.520> I<00:21:42.600> gotta<00:21:42.840> go<00:21:43.000> deeper<00:21:43.279> on 00:21:43.390 --> 00:21:43.400 align:start position:0% nft okay I gotta I gotta go deeper on 00:21:43.400 --> 00:21:46.390 align:start position:0% nft okay I gotta I gotta go deeper on some<00:21:43.480> of<00:21:43.600> this<00:21:43.720> will<00:21:43.880> 7683<00:21:44.640> support<00:21:45.000> 721<00:21:45.640> and 00:21:46.390 --> 00:21:46.400 align:start position:0% some of this will 7683 support 721 and 00:21:46.400 --> 00:21:49.149 align:start position:0% some of this will 7683 support 721 and 1155<00:21:47.400> guys<00:21:47.760> I<00:21:47.880> can't<00:21:48.159> remember<00:21:48.480> all<00:21:48.640> the<00:21:48.760> EIP 00:21:49.149 --> 00:21:49.159 align:start position:0% 1155 guys I can't remember all the EIP 00:21:49.159 --> 00:21:51.350 align:start position:0% 1155 guys I can't remember all the EIP numbers<00:21:49.520> I<00:21:49.640> try<00:21:49.919> really<00:21:50.159> hard<00:21:50.720> um<00:21:50.919> I<00:21:51.000> got<00:21:51.080> to<00:21:51.240> go 00:21:51.350 --> 00:21:51.360 align:start position:0% numbers I try really hard um I got to go 00:21:51.360 --> 00:21:54.029 align:start position:0% numbers I try really hard um I got to go deeper<00:21:51.640> on<00:21:51.840> this<00:21:52.200> so<00:21:52.840> um<00:21:53.080> we<00:21:53.200> will<00:21:53.600> get<00:21:53.799> back<00:21:53.960> to 00:21:54.029 --> 00:21:54.039 align:start position:0% deeper on this so um we will get back to 00:21:54.039 --> 00:21:55.830 align:start position:0% deeper on this so um we will get back to you<00:21:54.159> on<00:21:54.320> Twitter<00:21:54.799> with<00:21:55.000> that<00:21:55.240> and<00:21:55.440> or<00:21:55.640> I<00:21:55.720> can 00:21:55.830 --> 00:21:55.840 align:start position:0% you on Twitter with that and or I can 00:21:55.840 --> 00:21:57.269 align:start position:0% you on Twitter with that and or I can talk<00:21:56.000> to<00:21:56.120> you 00:21:57.269 --> 00:21:57.279 align:start position:0% talk to you 00:21:57.279 --> 00:22:00.909 align:start position:0% talk to you um<00:21:58.279> oh<00:21:58.919> fungible<00:21:59.360> nfts<00:21:59.919> no<00:22:00.240> we<00:22:00.400> can't<00:22:00.600> support 00:22:00.909 --> 00:22:00.919 align:start position:0% um oh fungible nfts no we can't support 00:22:00.919 --> 00:22:02.990 align:start position:0% um oh fungible nfts no we can't support nfts<00:22:01.440> I'm<00:22:01.559> sorry<00:22:02.080> um<00:22:02.279> remember<00:22:02.679> that<00:22:02.840> the 00:22:02.990 --> 00:22:03.000 align:start position:0% nfts I'm sorry um remember that the 00:22:03.000 --> 00:22:05.549 align:start position:0% nfts I'm sorry um remember that the intense<00:22:03.600> architecture<00:22:04.600> relies<00:22:05.159> on<00:22:05.360> the 00:22:05.549 --> 00:22:05.559 align:start position:0% intense architecture relies on the 00:22:05.559 --> 00:22:07.590 align:start position:0% intense architecture relies on the solver<00:22:06.279> filling<00:22:06.880> the<00:22:07.000> user<00:22:07.320> on<00:22:07.440> the 00:22:07.590 --> 00:22:07.600 align:start position:0% solver filling the user on the 00:22:07.600 --> 00:22:09.870 align:start position:0% solver filling the user on the destination<00:22:08.080> chain<00:22:08.400> with<00:22:08.520> their<00:22:08.679> own<00:22:08.880> funds 00:22:09.870 --> 00:22:09.880 align:start position:0% destination chain with their own funds 00:22:09.880 --> 00:22:13.390 align:start position:0% destination chain with their own funds and<00:22:10.039> nfts<00:22:10.640> are<00:22:11.080> nonf<00:22:11.480> fungible<00:22:12.320> so<00:22:12.799> the<00:22:12.919> intent 00:22:13.390 --> 00:22:13.400 align:start position:0% and nfts are nonf fungible so the intent 00:22:13.400 --> 00:22:16.149 align:start position:0% and nfts are nonf fungible so the intent architecture<00:22:14.000> relies<00:22:14.400> on<00:22:15.000> fungibility<00:22:16.000> um 00:22:16.149 --> 00:22:16.159 align:start position:0% architecture relies on fungibility um 00:22:16.159 --> 00:22:17.549 align:start position:0% architecture relies on fungibility um that's<00:22:16.320> actually<00:22:16.520> one<00:22:16.640> of<00:22:16.720> the<00:22:16.840> core<00:22:17.120> insights 00:22:17.549 --> 00:22:17.559 align:start position:0% that's actually one of the core insights 00:22:17.559 --> 00:22:21.750 align:start position:0% that's actually one of the core insights that<00:22:17.720> allowed<00:22:18.039> us<00:22:18.159> to<00:22:18.279> be<00:22:18.440> so<00:22:18.720> fast<00:22:19.679> so<00:22:20.400> um<00:22:21.360> nonf 00:22:21.750 --> 00:22:21.760 align:start position:0% that allowed us to be so fast so um nonf 00:22:21.760 --> 00:22:24.190 align:start position:0% that allowed us to be so fast so um nonf fungible<00:22:22.200> assets<00:22:22.640> do<00:22:22.960> require<00:22:23.520> a<00:22:23.760> different 00:22:24.190 --> 00:22:24.200 align:start position:0% fungible assets do require a different 00:22:24.200 --> 00:22:25.990 align:start position:0% fungible assets do require a different thing<00:22:24.840> and<00:22:24.960> I<00:22:25.080> think<00:22:25.279> that's<00:22:25.600> uh<00:22:25.799> that's 00:22:25.990 --> 00:22:26.000 align:start position:0% thing and I think that's uh that's 00:22:26.000 --> 00:22:28.310 align:start position:0% thing and I think that's uh that's important<00:22:26.400> to<00:22:26.679> to<00:22:26.799> kind<00:22:26.919> of<00:22:27.279> understand<00:22:28.159> all 00:22:28.310 --> 00:22:28.320 align:start position:0% important to to kind of understand all 00:22:28.320 --> 00:22:30.029 align:start position:0% important to to kind of understand all right<00:22:28.559> right<00:22:28.760> thank<00:22:28.919> you<00:22:29.360> next<00:22:29.520> one<00:22:29.840> uh<00:22:29.919> can 00:22:30.029 --> 00:22:30.039 align:start position:0% right right thank you next one uh can 00:22:30.039 --> 00:22:32.430 align:start position:0% right right thank you next one uh can you<00:22:30.200> compare<00:22:30.520> and<00:22:30.720> contrast<00:22:31.200> maybe<00:22:31.960> like<00:22:32.120> a 00:22:32.430 --> 00:22:32.440 align:start position:0% you compare and contrast maybe like a 00:22:32.440 --> 00:22:35.310 align:start position:0% you compare and contrast maybe like a general<00:22:32.799> M<00:22:33.159> chain<00:22:33.440> intense<00:22:34.000> that<00:22:34.520> we<00:22:34.840> existed 00:22:35.310 --> 00:22:35.320 align:start position:0% general M chain intense that we existed 00:22:35.320 --> 00:22:38.190 align:start position:0% general M chain intense that we existed on<00:22:35.440> the<00:22:35.600> market<00:22:36.159> with<00:22:36.360> the 00:22:38.190 --> 00:22:38.200 align:start position:0% on the market with the 00:22:38.200 --> 00:22:41.110 align:start position:0% on the market with the 7683<00:22:39.200> um<00:22:40.159> so 00:22:41.110 --> 00:22:41.120 align:start position:0% 7683 um so 00:22:41.120 --> 00:22:43.789 align:start position:0% 7683 um so Suave<00:22:42.120> I'm<00:22:42.240> a<00:22:42.360> huge<00:22:42.640> fan<00:22:42.799> of<00:22:42.960> suave<00:22:43.480> and<00:22:43.640> what 00:22:43.789 --> 00:22:43.799 align:start position:0% Suave I'm a huge fan of suave and what 00:22:43.799 --> 00:22:45.789 align:start position:0% Suave I'm a huge fan of suave and what the<00:22:43.880> flash<00:22:44.159> bot<00:22:44.279> SC<00:22:44.480> is<00:22:44.600> working<00:22:44.840> on<00:22:45.360> um<00:22:45.520> I<00:22:45.640> look 00:22:45.789 --> 00:22:45.799 align:start position:0% the flash bot SC is working on um I look 00:22:45.799 --> 00:22:47.990 align:start position:0% the flash bot SC is working on um I look at<00:22:45.919> Suave<00:22:46.320> as<00:22:46.440> like<00:22:46.640> computation<00:22:47.279> for<00:22:47.679> like<00:22:47.799> a 00:22:47.990 --> 00:22:48.000 align:start position:0% at Suave as like computation for like a 00:22:48.000 --> 00:22:50.750 align:start position:0% at Suave as like computation for like a te<00:22:48.520> trusted<00:22:48.880> Enclave<00:22:49.360> to<00:22:49.520> compute<00:22:50.360> all<00:22:50.520> sorts 00:22:50.750 --> 00:22:50.760 align:start position:0% te trusted Enclave to compute all sorts 00:22:50.760 --> 00:22:53.630 align:start position:0% te trusted Enclave to compute all sorts of<00:22:51.039> interesting<00:22:51.480> and<00:22:51.679> private<00:22:52.039> things<00:22:53.039> um 00:22:53.630 --> 00:22:53.640 align:start position:0% of interesting and private things um 00:22:53.640 --> 00:22:56.510 align:start position:0% of interesting and private things um lost<00:22:53.960> the<00:22:54.080> screen<00:22:54.480> but<00:22:54.960> um<00:22:55.960> they're<00:22:56.120> not<00:22:56.279> in 00:22:56.510 --> 00:22:56.520 align:start position:0% lost the screen but um they're not in 00:22:56.520 --> 00:22:58.070 align:start position:0% lost the screen but um they're not in competition<00:22:57.080> I<00:22:57.200> actually<00:22:57.440> think<00:22:57.600> Suave<00:22:58.000> is 00:22:58.070 --> 00:22:58.080 align:start position:0% competition I actually think Suave is 00:22:58.080 --> 00:23:00.750 align:start position:0% competition I actually think Suave is something<00:22:58.600> been<00:22:58.720> looked<00:22:58.919> at<00:22:59.480> quite<00:22:59.760> carefully 00:23:00.750 --> 00:23:00.760 align:start position:0% something been looked at quite carefully 00:23:00.760 --> 00:23:04.390 align:start position:0% something been looked at quite carefully uh<00:23:01.039> to<00:23:01.520> build<00:23:02.320> better<00:23:02.760> auction<00:23:03.279> mechanisms<00:23:04.240> to 00:23:04.390 --> 00:23:04.400 align:start position:0% uh to build better auction mechanisms to 00:23:04.400 --> 00:23:06.190 align:start position:0% uh to build better auction mechanisms to let<00:23:04.520> us<00:23:04.760> have<00:23:04.960> like<00:23:05.120> trustless<00:23:05.600> auctions<00:23:06.000> to 00:23:06.190 --> 00:23:06.200 align:start position:0% let us have like trustless auctions to 00:23:06.200 --> 00:23:08.350 align:start position:0% let us have like trustless auctions to auction<00:23:06.600> off<00:23:06.840> intense<00:23:07.799> so<00:23:07.960> I<00:23:08.080> think<00:23:08.200> these 00:23:08.350 --> 00:23:08.360 align:start position:0% auction off intense so I think these 00:23:08.360 --> 00:23:10.830 align:start position:0% auction off intense so I think these things<00:23:08.559> are<00:23:08.919> very<00:23:09.480> complimentary<00:23:10.480> uh<00:23:10.640> where 00:23:10.830 --> 00:23:10.840 align:start position:0% things are very complimentary uh where 00:23:10.840 --> 00:23:13.830 align:start position:0% things are very complimentary uh where you<00:23:11.000> can<00:23:11.720> uh<00:23:11.880> use<00:23:12.159> 7683<00:23:12.960> as<00:23:13.039> a<00:23:13.240> common<00:23:13.520> order 00:23:13.830 --> 00:23:13.840 align:start position:0% you can uh use 7683 as a common order 00:23:13.840 --> 00:23:15.990 align:start position:0% you can uh use 7683 as a common order standard<00:23:14.159> for<00:23:14.279> an<00:23:14.480> intent<00:23:15.240> and<00:23:15.360> use<00:23:15.679> something 00:23:15.990 --> 00:23:16.000 align:start position:0% standard for an intent and use something 00:23:16.000 --> 00:23:19.430 align:start position:0% standard for an intent and use something like<00:23:16.159> Suave<00:23:17.159> to<00:23:17.960> uh<00:23:18.120> to<00:23:18.360> achieve<00:23:18.840> optimal 00:23:19.430 --> 00:23:19.440 align:start position:0% like Suave to uh to achieve optimal 00:23:19.440 --> 00:23:21.669 align:start position:0% like Suave to uh to achieve optimal execution<00:23:20.440> of<00:23:20.679> that 00:23:21.669 --> 00:23:21.679 align:start position:0% execution of that 00:23:21.679 --> 00:23:25.269 align:start position:0% execution of that intent<00:23:22.679> okay<00:23:23.039> all<00:23:23.200> right<00:23:23.679> uh<00:23:23.840> next<00:23:24.039> one<00:23:24.960> uh<00:23:25.120> can 00:23:25.269 --> 00:23:25.279 align:start position:0% intent okay all right uh next one uh can 00:23:25.279 --> 00:23:27.830 align:start position:0% intent okay all right uh next one uh can we<00:23:25.600> use<00:23:25.880> this<00:23:26.080> new<00:23:26.279> standard<00:23:26.760> for<00:23:27.000> the<00:23:27.200> ndei 00:23:27.830 --> 00:23:27.840 align:start position:0% we use this new standard for the ndei 00:23:27.840 --> 00:23:30.269 align:start position:0% we use this new standard for the ndei protocol<00:23:28.520> like<00:23:28.640> enss<00:23:29.039> social<00:23:29.480> F<00:23:30.000> what<00:23:30.080> do<00:23:30.200> you 00:23:30.269 --> 00:23:30.279 align:start position:0% protocol like enss social F what do you 00:23:30.279 --> 00:23:31.990 align:start position:0% protocol like enss social F what do you think<00:23:30.440> about<00:23:30.600> it<00:23:31.200> so<00:23:31.400> I<00:23:31.480> think<00:23:31.640> this<00:23:31.760> goes<00:23:31.919> a 00:23:31.990 --> 00:23:32.000 align:start position:0% think about it so I think this goes a 00:23:32.000 --> 00:23:34.029 align:start position:0% think about it so I think this goes a little<00:23:32.159> bit<00:23:32.320> back<00:23:32.440> to<00:23:32.640> like<00:23:32.760> the<00:23:32.840> nft<00:23:33.400> question 00:23:34.029 --> 00:23:34.039 align:start position:0% little bit back to like the nft question 00:23:34.039 --> 00:23:38.190 align:start position:0% little bit back to like the nft question yeah<00:23:34.320> so<00:23:35.480> um<00:23:36.480> the<00:23:36.679> intent<00:23:37.159> architecture<00:23:37.919> is 00:23:38.190 --> 00:23:38.200 align:start position:0% yeah so um the intent architecture is 00:23:38.200 --> 00:23:40.909 align:start position:0% yeah so um the intent architecture is not<00:23:38.520> for<00:23:38.960> passing<00:23:39.440> generalized<00:23:40.039> messages 00:23:40.909 --> 00:23:40.919 align:start position:0% not for passing generalized messages 00:23:40.919 --> 00:23:43.110 align:start position:0% not for passing generalized messages that's<00:23:41.120> the<00:23:41.320> backend<00:23:41.760> part<00:23:41.919> of<00:23:42.080> this<00:23:42.720> right 00:23:43.110 --> 00:23:43.120 align:start position:0% that's the backend part of this right 00:23:43.120 --> 00:23:44.630 align:start position:0% that's the backend part of this right the<00:23:43.240> intent<00:23:43.559> architecture<00:23:44.080> is<00:23:44.240> I<00:23:44.360> want<00:23:44.520> to 00:23:44.630 --> 00:23:44.640 align:start position:0% the intent architecture is I want to 00:23:44.640 --> 00:23:46.909 align:start position:0% the intent architecture is I want to move<00:23:44.880> funds<00:23:45.279> quickly<00:23:46.039> and<00:23:46.200> maybe<00:23:46.440> I<00:23:46.559> want<00:23:46.679> to 00:23:46.909 --> 00:23:46.919 align:start position:0% move funds quickly and maybe I want to 00:23:46.919 --> 00:23:48.549 align:start position:0% move funds quickly and maybe I want to do<00:23:47.159> something<00:23:47.520> with<00:23:47.720> those<00:23:47.880> funds<00:23:48.279> on<00:23:48.400> the 00:23:48.549 --> 00:23:48.559 align:start position:0% do something with those funds on the 00:23:48.559 --> 00:23:51.470 align:start position:0% do something with those funds on the destination<00:23:49.039> chain<00:23:50.039> um<00:23:50.360> so<00:23:50.640> if<00:23:50.760> you're<00:23:51.120> trying 00:23:51.470 --> 00:23:51.480 align:start position:0% destination chain um so if you're trying 00:23:51.480 --> 00:23:55.070 align:start position:0% destination chain um so if you're trying to<00:23:52.480> uh<00:23:52.679> move<00:23:52.919> nfts<00:23:53.480> around<00:23:54.200> or<00:23:54.400> trying<00:23:54.640> to<00:23:54.760> move 00:23:55.070 --> 00:23:55.080 align:start position:0% to uh move nfts around or trying to move 00:23:55.080 --> 00:23:58.230 align:start position:0% to uh move nfts around or trying to move like<00:23:55.600> ens<00:23:56.159> names<00:23:56.840> that<00:23:56.960> are<00:23:57.320> sort<00:23:57.559> of<00:23:57.840> that<00:23:57.960> are 00:23:58.230 --> 00:23:58.240 align:start position:0% like ens names that are sort of that are 00:23:58.240 --> 00:24:01.269 align:start position:0% like ens names that are sort of that are are<00:23:58.720> are<00:23:59.279> conceptualized<00:23:59.919> as<00:24:00.039> an<00:24:00.120> nft<00:24:01.120> you 00:24:01.269 --> 00:24:01.279 align:start position:0% are are conceptualized as an nft you 00:24:01.279 --> 00:24:04.310 align:start position:0% are are conceptualized as an nft you need<00:24:01.559> something<00:24:01.919> else<00:24:02.760> right<00:24:03.279> we<00:24:03.520> can<00:24:03.799> do 00:24:04.310 --> 00:24:04.320 align:start position:0% need something else right we can do 00:24:04.320 --> 00:24:06.669 align:start position:0% need something else right we can do things<00:24:04.760> like<00:24:05.120> hey<00:24:05.320> you<00:24:05.440> want<00:24:05.520> to<00:24:05.720> buy<00:24:05.919> your<00:24:06.120> ens 00:24:06.669 --> 00:24:06.679 align:start position:0% things like hey you want to buy your ens 00:24:06.679 --> 00:24:09.549 align:start position:0% things like hey you want to buy your ens name<00:24:07.679> um<00:24:08.240> you<00:24:08.360> can<00:24:08.520> go<00:24:08.679> and<00:24:08.840> pay<00:24:09.080> for<00:24:09.279> it<00:24:09.400> from 00:24:09.549 --> 00:24:09.559 align:start position:0% name um you can go and pay for it from 00:24:09.559 --> 00:24:11.750 align:start position:0% name um you can go and pay for it from any<00:24:09.799> chain<00:24:10.240> and<00:24:10.360> make<00:24:10.520> that<00:24:10.679> be<00:24:10.880> one<00:24:11.159> click<00:24:11.559> so 00:24:11.750 --> 00:24:11.760 align:start position:0% any chain and make that be one click so 00:24:11.760 --> 00:24:14.070 align:start position:0% any chain and make that be one click so I<00:24:11.880> take<00:24:12.080> my<00:24:12.520> arbitrum<00:24:13.080> funds<00:24:13.360> or<00:24:13.520> my<00:24:13.640> optimism 00:24:14.070 --> 00:24:14.080 align:start position:0% I take my arbitrum funds or my optimism 00:24:14.080 --> 00:24:16.230 align:start position:0% I take my arbitrum funds or my optimism funds<00:24:14.400> and<00:24:14.520> I<00:24:14.600> go<00:24:14.720> and<00:24:14.840> I<00:24:14.960> buy<00:24:15.159> my<00:24:15.279> ens<00:24:15.720> name<00:24:15.960> on 00:24:16.230 --> 00:24:16.240 align:start position:0% funds and I go and I buy my ens name on 00:24:16.240 --> 00:24:18.149 align:start position:0% funds and I go and I buy my ens name on like<00:24:16.400> eth<00:24:16.640> main<00:24:16.880> net<00:24:17.320> and<00:24:17.440> it's<00:24:17.600> one<00:24:17.840> click<00:24:18.039> to 00:24:18.149 --> 00:24:18.159 align:start position:0% like eth main net and it's one click to 00:24:18.159 --> 00:24:19.630 align:start position:0% like eth main net and it's one click to go<00:24:18.279> and<00:24:18.440> execute<00:24:18.880> that<00:24:19.240> but<00:24:19.360> these<00:24:19.480> are 00:24:19.630 --> 00:24:19.640 align:start position:0% go and execute that but these are 00:24:19.640 --> 00:24:22.390 align:start position:0% go and execute that but these are slightly<00:24:19.960> different<00:24:20.760> concepts<00:24:21.760> and<00:24:22.000> what<00:24:22.240> why 00:24:22.390 --> 00:24:22.400 align:start position:0% slightly different concepts and what why 00:24:22.400 --> 00:24:24.350 align:start position:0% slightly different concepts and what why sorry<00:24:22.799> my<00:24:22.919> questions<00:24:23.360> like<00:24:23.720> why<00:24:23.919> just<00:24:24.240> why 00:24:24.350 --> 00:24:24.360 align:start position:0% sorry my questions like why just why 00:24:24.360 --> 00:24:26.029 align:start position:0% sorry my questions like why just why cannot<00:24:24.679> we<00:24:24.840> just<00:24:25.000> like<00:24:25.200> merge<00:24:25.520> it<00:24:25.760> together 00:24:26.029 --> 00:24:26.039 align:start position:0% cannot we just like merge it together 00:24:26.039 --> 00:24:27.070 align:start position:0% cannot we just like merge it together into<00:24:26.240> the<00:24:26.360> same 00:24:27.070 --> 00:24:27.080 align:start position:0% into the same 00:24:27.080 --> 00:24:31.389 align:start position:0% into the same standard<00:24:28.080> so<00:24:28.440> so<00:24:29.440> um<00:24:30.440> go<00:24:30.640> back<00:24:30.799> to<00:24:30.919> the<00:24:31.039> idea<00:24:31.279> of 00:24:31.389 --> 00:24:31.399 align:start position:0% standard so so um go back to the idea of 00:24:31.399 --> 00:24:33.470 align:start position:0% standard so so um go back to the idea of how<00:24:31.520> the<00:24:31.600> intent<00:24:31.919> architecture<00:24:32.480> works<00:24:33.320> you 00:24:33.470 --> 00:24:33.480 align:start position:0% how the intent architecture works you 00:24:33.480 --> 00:24:35.389 align:start position:0% how the intent architecture works you are<00:24:33.640> going<00:24:33.760> to<00:24:33.919> have<00:24:34.080> these<00:24:34.279> solvers<00:24:34.919> front 00:24:35.389 --> 00:24:35.399 align:start position:0% are going to have these solvers front 00:24:35.399 --> 00:24:37.870 align:start position:0% are going to have these solvers front the<00:24:35.559> user<00:24:35.960> funds<00:24:36.960> uh<00:24:37.039> on<00:24:37.200> the<00:24:37.360> destination 00:24:37.870 --> 00:24:37.880 align:start position:0% the user funds uh on the destination 00:24:37.880 --> 00:24:40.669 align:start position:0% the user funds uh on the destination chain<00:24:38.679> I<00:24:38.840> can't<00:24:39.120> front<00:24:39.559> them<00:24:39.760> in<00:24:39.960> nft<00:24:40.520> that's 00:24:40.669 --> 00:24:40.679 align:start position:0% chain I can't front them in nft that's 00:24:40.679 --> 00:24:42.750 align:start position:0% chain I can't front them in nft that's on<00:24:40.840> some<00:24:41.080> chain<00:24:41.520> I<00:24:41.640> need<00:24:41.760> to<00:24:42.000> create<00:24:42.360> another 00:24:42.750 --> 00:24:42.760 align:start position:0% on some chain I need to create another 00:24:42.760 --> 00:24:45.990 align:start position:0% on some chain I need to create another representation<00:24:43.440> of<00:24:43.559> it<00:24:43.720> like<00:24:44.200> trustless<00:24:45.200> so 00:24:45.990 --> 00:24:46.000 align:start position:0% representation of it like trustless so 00:24:46.000 --> 00:24:47.909 align:start position:0% representation of it like trustless so fungibility<00:24:47.000> the<00:24:47.159> fact<00:24:47.320> that<00:24:47.480> we<00:24:47.640> have 00:24:47.909 --> 00:24:47.919 align:start position:0% fungibility the fact that we have 00:24:47.919 --> 00:24:50.190 align:start position:0% fungibility the fact that we have fungibility<00:24:48.919> is<00:24:49.080> what<00:24:49.279> allows<00:24:49.640> the<00:24:49.799> intent 00:24:50.190 --> 00:24:50.200 align:start position:0% fungibility is what allows the intent 00:24:50.200 --> 00:24:53.389 align:start position:0% fungibility is what allows the intent architecture<00:24:50.720> to<00:24:50.919> work<00:24:51.399> so<00:24:52.120> well<00:24:53.120> if<00:24:53.240> I'm 00:24:53.389 --> 00:24:53.399 align:start position:0% architecture to work so well if I'm 00:24:53.399 --> 00:24:55.230 align:start position:0% architecture to work so well if I'm trying<00:24:53.600> to<00:24:53.799> do<00:24:54.080> something<00:24:54.520> that<00:24:54.799> can't<00:24:55.080> be 00:24:55.230 --> 00:24:55.240 align:start position:0% trying to do something that can't be 00:24:55.240 --> 00:24:57.710 align:start position:0% trying to do something that can't be fungible<00:24:56.000> like<00:24:56.200> money<00:24:56.480> money<00:24:56.760> is<00:24:56.880> fungible<00:24:57.559> or 00:24:57.710 --> 00:24:57.720 align:start position:0% fungible like money money is fungible or 00:24:57.720 --> 00:24:58.830 align:start position:0% fungible like money money is fungible or tokens<00:24:58.000> are<00:24:58.080> f 00:24:58.830 --> 00:24:58.840 align:start position:0% tokens are f 00:24:58.840 --> 00:25:00.909 align:start position:0% tokens are f if<00:24:58.960> it's<00:24:59.159> not<00:24:59.360> fible<00:25:00.240> then<00:25:00.399> I'm<00:25:00.559> going<00:25:00.640> to<00:25:00.760> need 00:25:00.909 --> 00:25:00.919 align:start position:0% if it's not fible then I'm going to need 00:25:00.919 --> 00:25:03.149 align:start position:0% if it's not fible then I'm going to need to<00:25:01.159> like<00:25:01.399> send<00:25:01.679> a<00:25:01.799> lower<00:25:02.120> level<00:25:02.440> message<00:25:03.000> to 00:25:03.149 --> 00:25:03.159 align:start position:0% to like send a lower level message to 00:25:03.159 --> 00:25:06.350 align:start position:0% to like send a lower level message to make<00:25:03.320> that<00:25:03.480> happen<00:25:04.240> Okay<00:25:05.039> uh<00:25:05.240> we<00:25:05.399> got<00:25:05.559> 10<00:25:05.960> 15 00:25:06.350 --> 00:25:06.360 align:start position:0% make that happen Okay uh we got 10 15 00:25:06.360 --> 00:25:08.389 align:start position:0% make that happen Okay uh we got 10 15 seconds<00:25:06.679> but<00:25:06.919> yeah<00:25:07.279> can<00:25:07.440> you<00:25:07.799> can<00:25:07.960> you<00:25:08.080> answer 00:25:08.389 --> 00:25:08.399 align:start position:0% seconds but yeah can you can you answer 00:25:08.399 --> 00:25:11.669 align:start position:0% seconds but yeah can you can you answer the<00:25:08.679> the<00:25:08.799> top<00:25:09.039> one<00:25:09.760> uh<00:25:10.120> how<00:25:10.279> can<00:25:10.600> 763<00:25:11.440> prevent 00:25:11.669 --> 00:25:11.679 align:start position:0% the the top one uh how can 763 prevent 00:25:11.679 --> 00:25:12.710 align:start position:0% the the top one uh how can 763 prevent devs<00:25:11.880> from<00:25:11.960> messing<00:25:12.159> around<00:25:12.320> with<00:25:12.399> the<00:25:12.480> intend 00:25:12.710 --> 00:25:12.720 align:start position:0% devs from messing around with the intend 00:25:12.720 --> 00:25:17.029 align:start position:0% devs from messing around with the intend the<00:25:12.799> user<00:25:13.240> pass<00:25:13.399> f<00:25:14.240> um<00:25:14.760> so 00:25:17.029 --> 00:25:17.039 align:start position:0% the user pass f um so 00:25:17.039 --> 00:25:22.350 align:start position:0% the user pass f um so uh<00:25:18.039> so<00:25:18.960> the<00:25:19.520> the<00:25:19.880> um<00:25:20.279> the<00:25:20.480> user<00:25:21.080> and<00:25:21.279> the<00:25:21.440> solver 00:25:22.350 --> 00:25:22.360 align:start position:0% uh so the the um the user and the solver 00:25:22.360 --> 00:25:24.470 align:start position:0% uh so the the um the user and the solver both<00:25:22.640> have<00:25:22.760> to<00:25:23.000> agree<00:25:23.399> and<00:25:23.679> Trust<00:25:24.320> the 00:25:24.470 --> 00:25:24.480 align:start position:0% both have to agree and Trust the 00:25:24.480 --> 00:25:27.029 align:start position:0% both have to agree and Trust the settlement<00:25:25.000> system<00:25:25.720> okay<00:25:26.120> if<00:25:26.240> you<00:25:26.399> write<00:25:26.799> a 00:25:27.029 --> 00:25:27.039 align:start position:0% settlement system okay if you write a 00:25:27.039 --> 00:25:28.830 align:start position:0% settlement system okay if you write a dodgy<00:25:27.440> settlement<00:25:27.919> system 00:25:28.830 --> 00:25:28.840 align:start position:0% dodgy settlement system 00:25:28.840 --> 00:25:30.549 align:start position:0% dodgy settlement system um<00:25:29.159> in<00:25:29.320> my<00:25:29.600> example<00:25:30.000> there<00:25:30.200> yeah<00:25:30.320> you<00:25:30.440> could 00:25:30.549 --> 00:25:30.559 align:start position:0% um in my example there yeah you could 00:25:30.559 --> 00:25:32.710 align:start position:0% um in my example there yeah you could still<00:25:30.799> use<00:25:30.960> her<00:25:31.120> funds<00:25:31.360> and<00:25:31.520> that's<00:25:31.760> bad<00:25:32.440> um<00:25:32.559> do 00:25:32.710 --> 00:25:32.720 align:start position:0% still use her funds and that's bad um do 00:25:32.720 --> 00:25:34.789 align:start position:0% still use her funds and that's bad um do I<00:25:32.880> expect<00:25:33.120> the<00:25:33.279> user<00:25:33.720> to<00:25:34.039> to<00:25:34.200> sanity<00:25:34.600> check 00:25:34.789 --> 00:25:34.799 align:start position:0% I expect the user to to sanity check 00:25:34.799 --> 00:25:36.950 align:start position:0% I expect the user to to sanity check their<00:25:34.919> settlement<00:25:35.279> systems<00:25:35.960> no<00:25:36.480> but<00:25:36.640> I<00:25:36.720> do 00:25:36.950 --> 00:25:36.960 align:start position:0% their settlement systems no but I do 00:25:36.960 --> 00:25:39.510 align:start position:0% their settlement systems no but I do expect<00:25:37.320> wallets<00:25:38.279> or<00:25:38.600> other<00:25:38.919> applications 00:25:39.510 --> 00:25:39.520 align:start position:0% expect wallets or other applications 00:25:39.520 --> 00:25:41.750 align:start position:0% expect wallets or other applications that<00:25:39.679> implement<00:25:40.159> this<00:25:40.679> to<00:25:40.960> sanity<00:25:41.399> check<00:25:41.640> that 00:25:41.750 --> 00:25:41.760 align:start position:0% that implement this to sanity check that 00:25:41.760 --> 00:25:43.590 align:start position:0% that implement this to sanity check that settlement<00:25:42.159> system<00:25:42.640> and<00:25:42.799> or<00:25:43.200> you<00:25:43.320> know<00:25:43.440> we'll 00:25:43.590 --> 00:25:43.600 align:start position:0% settlement system and or you know we'll 00:25:43.600 --> 00:25:45.880 align:start position:0% settlement system and or you know we'll create