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:10.190 align:start position:0% [Music] 00:00:10.190 --> 00:00:10.200 align:start position:0% [Music] 00:00:10.200 --> 00:00:12.310 align:start position:0% [Music] really<00:00:10.440> glad<00:00:10.639> to<00:00:10.759> be<00:00:10.960> here<00:00:11.120> today<00:00:11.799> my<00:00:11.960> name<00:00:12.120> is 00:00:12.310 --> 00:00:12.320 align:start position:0% really glad to be here today my name is 00:00:12.320 --> 00:00:15.030 align:start position:0% really glad to be here today my name is Andrew<00:00:13.080> and<00:00:13.480> this<00:00:13.639> is<00:00:13.839> my<00:00:14.599> this<00:00:14.719> is<00:00:14.879> my 00:00:15.030 --> 00:00:15.040 align:start position:0% Andrew and this is my this is my 00:00:15.040 --> 00:00:19.429 align:start position:0% Andrew and this is my this is my coworker<00:00:15.559> DC<00:00:16.080> Posh<00:00:16.920> and<00:00:17.039> we<00:00:17.160> are<00:00:17.400> from<00:00:17.560> the<00:00:17.720> Dao 00:00:19.429 --> 00:00:19.439 align:start position:0% coworker DC Posh and we are from the Dao 00:00:19.439 --> 00:00:21.870 align:start position:0% coworker DC Posh and we are from the Dao team<00:00:20.439> over<00:00:20.640> the<00:00:20.840> past<00:00:21.039> few<00:00:21.279> days<00:00:21.600> there<00:00:21.760> has 00:00:21.870 --> 00:00:21.880 align:start position:0% team over the past few days there has 00:00:21.880 --> 00:00:24.470 align:start position:0% team over the past few days there has been<00:00:22.000> a<00:00:22.119> lot<00:00:22.279> of<00:00:22.439> talk<00:00:22.920> around<00:00:23.920> um<00:00:24.240> the 00:00:24.470 --> 00:00:24.480 align:start position:0% been a lot of talk around um the 00:00:24.480 --> 00:00:27.150 align:start position:0% been a lot of talk around um the fragmentation<00:00:25.480> of<00:00:25.760> ethereum<00:00:26.560> and<00:00:26.720> how<00:00:27.000> all 00:00:27.150 --> 00:00:27.160 align:start position:0% fragmentation of ethereum and how all 00:00:27.160 --> 00:00:29.470 align:start position:0% fragmentation of ethereum and how all the<00:00:27.279> l2s<00:00:27.760> are<00:00:27.960> separate<00:00:28.760> and<00:00:28.920> creates<00:00:29.199> a<00:00:29.320> bad 00:00:29.470 --> 00:00:29.480 align:start position:0% the l2s are separate and creates a bad 00:00:29.480 --> 00:00:31.150 align:start position:0% the l2s are separate and creates a bad user<00:00:29.720> EXP<00:00:29.960> experence<00:00:30.279> for<00:00:30.439> trying<00:00:30.720> to 00:00:31.150 --> 00:00:31.160 align:start position:0% user EXP experence for trying to 00:00:31.160 --> 00:00:33.150 align:start position:0% user EXP experence for trying to interrupt<00:00:31.720> between<00:00:31.960> these 00:00:33.150 --> 00:00:33.160 align:start position:0% interrupt between these 00:00:33.160 --> 00:00:35.110 align:start position:0% interrupt between these l2s<00:00:34.160> the<00:00:34.280> past<00:00:34.440> few<00:00:34.600> months<00:00:34.840> we've<00:00:35.000> been 00:00:35.110 --> 00:00:35.120 align:start position:0% l2s the past few months we've been 00:00:35.120 --> 00:00:37.069 align:start position:0% l2s the past few months we've been working<00:00:35.399> on<00:00:35.559> something<00:00:35.840> new<00:00:36.040> at<00:00:36.200> D<00:00:36.640> that<00:00:36.760> we're 00:00:37.069 --> 00:00:37.079 align:start position:0% working on something new at D that we're 00:00:37.079 --> 00:00:39.709 align:start position:0% working on something new at D that we're excited<00:00:37.399> to<00:00:37.559> show<00:00:37.719> you<00:00:38.040> today<00:00:39.040> this<00:00:39.160> is<00:00:39.280> a<00:00:39.440> step 00:00:39.709 --> 00:00:39.719 align:start position:0% excited to show you today this is a step 00:00:39.719 --> 00:00:43.069 align:start position:0% excited to show you today this is a step forward<00:00:40.360> towards<00:00:40.719> unifying<00:00:41.640> ethereum<00:00:42.640> using 00:00:43.069 --> 00:00:43.079 align:start position:0% forward towards unifying ethereum using 00:00:43.079 --> 00:00:45.790 align:start position:0% forward towards unifying ethereum using technology<00:00:43.640> that<00:00:43.879> already<00:00:44.239> exists<00:00:44.800> today 00:00:45.790 --> 00:00:45.800 align:start position:0% technology that already exists today 00:00:45.800 --> 00:00:47.549 align:start position:0% technology that already exists today while<00:00:46.120> maintaining<00:00:46.640> the<00:00:46.800> core<00:00:47.079> values<00:00:47.399> of 00:00:47.549 --> 00:00:47.559 align:start position:0% while maintaining the core values of 00:00:47.559 --> 00:00:49.229 align:start position:0% while maintaining the core values of permissionless<00:00:48.399> and 00:00:49.229 --> 00:00:49.239 align:start position:0% permissionless and 00:00:49.239 --> 00:00:52.189 align:start position:0% permissionless and trustless<00:00:50.239> and<00:00:50.399> let's<00:00:50.640> get<00:00:50.760> started<00:00:51.199> with<00:00:51.399> DC 00:00:52.189 --> 00:00:52.199 align:start position:0% trustless and let's get started with DC 00:00:52.199 --> 00:00:55.310 align:start position:0% trustless and let's get started with DC introducing<00:00:53.199> the<00:00:53.399> problem<00:00:53.640> of<00:00:54.079> rment<00:00:55.079> and 00:00:55.310 --> 00:00:55.320 align:start position:0% introducing the problem of rment and 00:00:55.320 --> 00:00:58.869 align:start position:0% introducing the problem of rment and what<00:00:55.480> it<00:00:55.600> looks<00:00:55.840> like<00:00:56.399> today<00:00:57.399> sounds<00:00:57.879> great 00:00:58.869 --> 00:00:58.879 align:start position:0% what it looks like today sounds great 00:00:58.879 --> 00:01:00.950 align:start position:0% what it looks like today sounds great hey<00:00:59.079> everyone<00:00:59.719> yes<00:01:00.120> I<00:01:00.199> didn't<00:01:00.440> forget<00:01:00.719> about 00:01:00.950 --> 00:01:00.960 align:start position:0% hey everyone yes I didn't forget about 00:01:00.960 --> 00:01:03.509 align:start position:0% hey everyone yes I didn't forget about this<00:01:01.160> by<00:01:01.280> the<00:01:01.399> way<00:01:02.160> they<00:01:02.480> scheduled<00:01:03.000> us<00:01:03.280> back 00:01:03.509 --> 00:01:03.519 align:start position:0% this by the way they scheduled us back 00:01:03.519 --> 00:01:06.510 align:start position:0% this by the way they scheduled us back to<00:01:03.760> back<00:01:04.040> so<00:01:04.280> I<00:01:04.760> just<00:01:05.159> got<00:01:05.400> off<00:01:05.519> of<00:01:05.640> a<00:01:05.799> panel<00:01:06.400> on 00:01:06.510 --> 00:01:06.520 align:start position:0% to back so I just got off of a panel on 00:01:06.520 --> 00:01:08.990 align:start position:0% to back so I just got off of a panel on the<00:01:06.680> next<00:01:06.880> stage<00:01:07.159> over<00:01:07.720> came<00:01:07.960> straight<00:01:08.240> here 00:01:08.990 --> 00:01:09.000 align:start position:0% the next stage over came straight here 00:01:09.000 --> 00:01:11.830 align:start position:0% the next stage over came straight here glad<00:01:09.200> to<00:01:09.280> see<00:01:09.400> you<00:01:09.759> all<00:01:10.759> um<00:01:11.080> let's<00:01:11.320> talk<00:01:11.520> about 00:01:11.830 --> 00:01:11.840 align:start position:0% glad to see you all um let's talk about 00:01:11.840 --> 00:01:13.270 align:start position:0% glad to see you all um let's talk about this 00:01:13.270 --> 00:01:13.280 align:start position:0% this 00:01:13.280 --> 00:01:16.749 align:start position:0% this so<00:01:14.280> we're<00:01:14.759> gonna<00:01:15.759> oh<00:01:16.000> see<00:01:16.360> do<00:01:16.439> you<00:01:16.560> have<00:01:16.640> the 00:01:16.749 --> 00:01:16.759 align:start position:0% so we're gonna oh see do you have the 00:01:16.759 --> 00:01:19.149 align:start position:0% so we're gonna oh see do you have the clicker<00:01:17.560> yeah<00:01:17.840> perfect<00:01:18.280> thank<00:01:18.439> you<00:01:18.840> so<00:01:19.000> the 00:01:19.149 --> 00:01:19.159 align:start position:0% clicker yeah perfect thank you so the 00:01:19.159 --> 00:01:20.630 align:start position:0% clicker yeah perfect thank you so the problem<00:01:19.439> we're<00:01:19.560> going<00:01:19.640> to<00:01:19.799> talk<00:01:19.960> about<00:01:20.159> today 00:01:20.630 --> 00:01:20.640 align:start position:0% problem we're going to talk about today 00:01:20.640 --> 00:01:22.749 align:start position:0% problem we're going to talk about today is<00:01:20.799> one<00:01:21.000> that<00:01:21.159> I<00:01:21.280> think<00:01:21.720> many<00:01:21.960> of<00:01:22.119> you<00:01:22.439> are 00:01:22.749 --> 00:01:22.759 align:start position:0% is one that I think many of you are 00:01:22.759 --> 00:01:25.749 align:start position:0% is one that I think many of you are going<00:01:22.840> to<00:01:23.040> be<00:01:23.640> very<00:01:24.000> familiar<00:01:24.439> with<00:01:25.360> uh<00:01:25.600> how 00:01:25.749 --> 00:01:25.759 align:start position:0% going to be very familiar with uh how 00:01:25.759 --> 00:01:30.030 align:start position:0% going to be very familiar with uh how many<00:01:25.960> of<00:01:26.079> you<00:01:26.280> here<00:01:26.520> have<00:01:26.680> used<00:01:27.040> poly<00:01:27.360> Market 00:01:30.030 --> 00:01:30.040 align:start position:0% many of you here have used poly Market 00:01:30.040 --> 00:01:31.590 align:start position:0% many of you here have used poly Market how<00:01:30.159> many<00:01:30.360> of<00:01:30.479> you<00:01:30.640> here<00:01:30.799> have<00:01:31.000> ever<00:01:31.159> seen<00:01:31.439> a 00:01:31.590 --> 00:01:31.600 align:start position:0% how many of you here have ever seen a 00:01:31.600 --> 00:01:33.670 align:start position:0% how many of you here have ever seen a screen<00:01:32.000> that<00:01:32.159> says<00:01:32.439> something<00:01:32.880> like<00:01:33.320> you<00:01:33.439> know 00:01:33.670 --> 00:01:33.680 align:start position:0% screen that says something like you know 00:01:33.680 --> 00:01:37.630 align:start position:0% screen that says something like you know only<00:01:34.439> send<00:01:35.439> this<00:01:35.920> token<00:01:36.399> on<00:01:36.640> this<00:01:36.840> chain<00:01:37.439> other 00:01:37.630 --> 00:01:37.640 align:start position:0% only send this token on this chain other 00:01:37.640 --> 00:01:39.870 align:start position:0% only send this token on this chain other funds<00:01:38.040> might<00:01:38.200> be 00:01:39.870 --> 00:01:39.880 align:start position:0% funds might be 00:01:39.880 --> 00:01:43.350 align:start position:0% funds might be lost<00:01:40.880> all<00:01:41.079> right<00:01:41.600> more<00:01:41.799> than<00:01:42.000> half<00:01:42.200> for<00:01:42.360> sure 00:01:43.350 --> 00:01:43.360 align:start position:0% lost all right more than half for sure 00:01:43.360 --> 00:01:45.749 align:start position:0% lost all right more than half for sure um<00:01:44.320> and<00:01:44.479> this<00:01:44.560> is<00:01:44.680> a<00:01:44.840> very<00:01:45.040> common<00:01:45.280> ux<00:01:45.680> right 00:01:45.749 --> 00:01:45.759 align:start position:0% um and this is a very common ux right 00:01:45.759 --> 00:01:48.230 align:start position:0% um and this is a very common ux right now<00:01:46.119> so<00:01:46.280> it's<00:01:46.479> like<00:01:47.280> select<00:01:47.640> polygon<00:01:48.000> as<00:01:48.119> the 00:01:48.230 --> 00:01:48.240 align:start position:0% now so it's like select polygon as the 00:01:48.240 --> 00:01:50.590 align:start position:0% now so it's like select polygon as the network<00:01:48.600> not<00:01:48.840> polygon<00:01:49.240> ZK<00:01:49.920> evm<00:01:50.280> or<00:01:50.360> you<00:01:50.479> may 00:01:50.590 --> 00:01:50.600 align:start position:0% network not polygon ZK evm or you may 00:01:50.600 --> 00:01:53.630 align:start position:0% network not polygon ZK evm or you may lose<00:01:50.960> funds<00:01:51.960> um<00:01:52.280> and<00:01:52.399> it's<00:01:52.680> also<00:01:53.079> a<00:01:53.360> problem 00:01:53.630 --> 00:01:53.640 align:start position:0% lose funds um and it's also a problem 00:01:53.640 --> 00:01:54.910 align:start position:0% lose funds um and it's also a problem that<00:01:53.799> you've<00:01:54.040> probably<00:01:54.240> heard<00:01:54.520> a<00:01:54.600> lot<00:01:54.759> at 00:01:54.910 --> 00:01:54.920 align:start position:0% that you've probably heard a lot at 00:01:54.920 --> 00:01:56.350 align:start position:0% that you've probably heard a lot at Devcon<00:01:55.399> where<00:01:55.560> it's<00:01:55.719> like<00:01:55.840> a<00:01:56.000> lot<00:01:56.119> of<00:01:56.240> the 00:01:56.350 --> 00:01:56.360 align:start position:0% Devcon where it's like a lot of the 00:01:56.360 --> 00:01:58.910 align:start position:0% Devcon where it's like a lot of the talks<00:01:56.600> here<00:01:56.960> like<00:01:57.280> about<00:01:58.280> uh<00:01:58.439> rollup 00:01:58.910 --> 00:01:58.920 align:start position:0% talks here like about uh rollup 00:01:58.920 --> 00:02:01.029 align:start position:0% talks here like about uh rollup fragmentation<00:02:00.000> and<00:02:00.200> about<00:02:00.640> chain 00:02:01.029 --> 00:02:01.039 align:start position:0% fragmentation and about chain 00:02:01.039 --> 00:02:03.469 align:start position:0% fragmentation and about chain abstraction<00:02:01.600> and<00:02:01.759> about<00:02:02.000> things<00:02:02.240> like<00:02:02.479> that 00:02:03.469 --> 00:02:03.479 align:start position:0% abstraction and about things like that 00:02:03.479 --> 00:02:05.270 align:start position:0% abstraction and about things like that and<00:02:03.880> I<00:02:03.960> think<00:02:04.159> the<00:02:04.439> aspect<00:02:04.799> of<00:02:04.960> what<00:02:05.079> we're 00:02:05.270 --> 00:02:05.280 align:start position:0% and I think the aspect of what we're 00:02:05.280 --> 00:02:06.630 align:start position:0% and I think the aspect of what we're about<00:02:05.439> to<00:02:05.560> show<00:02:05.759> you<00:02:05.920> that<00:02:06.000> we're<00:02:06.399> really 00:02:06.630 --> 00:02:06.640 align:start position:0% about to show you that we're really 00:02:06.640 --> 00:02:09.430 align:start position:0% about to show you that we're really excited<00:02:07.079> about<00:02:07.560> is<00:02:07.840> that<00:02:08.840> we're<00:02:09.039> going<00:02:09.119> to 00:02:09.430 --> 00:02:09.440 align:start position:0% excited about is that we're going to 00:02:09.440 --> 00:02:12.470 align:start position:0% excited about is that we're going to only<00:02:09.720> talk<00:02:09.920> about<00:02:10.160> things<00:02:10.440> today<00:02:10.840> that<00:02:11.480> work 00:02:12.470 --> 00:02:12.480 align:start position:0% only talk about things today that work 00:02:12.480 --> 00:02:15.869 align:start position:0% only talk about things today that work today<00:02:13.480> um<00:02:13.760> so<00:02:14.200> so<00:02:14.840> I<00:02:14.920> think<00:02:15.080> there's<00:02:15.239> a<00:02:15.400> lot<00:02:15.560> of 00:02:15.869 --> 00:02:15.879 align:start position:0% today um so so I think there's a lot of 00:02:15.879 --> 00:02:17.190 align:start position:0% today um so so I think there's a lot of interesting<00:02:16.280> sort<00:02:16.480> of<00:02:16.599> forward-looking 00:02:17.190 --> 00:02:17.200 align:start position:0% interesting sort of forward-looking 00:02:17.200 --> 00:02:18.949 align:start position:0% interesting sort of forward-looking things<00:02:17.599> that<00:02:17.760> people<00:02:17.959> are<00:02:18.160> talking<00:02:18.480> about 00:02:18.949 --> 00:02:18.959 align:start position:0% things that people are talking about 00:02:18.959 --> 00:02:22.589 align:start position:0% things that people are talking about around<00:02:19.680> things<00:02:20.080> like<00:02:21.080> uh<00:02:21.720> chain<00:02:22.120> specific 00:02:22.589 --> 00:02:22.599 align:start position:0% around things like uh chain specific 00:02:22.599 --> 00:02:27.150 align:start position:0% around things like uh chain specific addresses<00:02:23.400> around<00:02:23.680> things<00:02:24.480> like<00:02:25.680> uh<00:02:26.680> wallets 00:02:27.150 --> 00:02:27.160 align:start position:0% addresses around things like uh wallets 00:02:27.160 --> 00:02:29.710 align:start position:0% addresses around things like uh wallets that<00:02:27.319> have<00:02:27.519> bridging<00:02:28.040> built<00:02:28.319> into<00:02:28.599> them<00:02:29.560> uh 00:02:29.710 --> 00:02:29.720 align:start position:0% that have bridging built into them uh 00:02:29.720 --> 00:02:30.869 align:start position:0% that have bridging built into them uh but<00:02:29.959> we're<00:02:30.080> going<00:02:30.160> to<00:02:30.280> talk<00:02:30.440> about<00:02:30.640> things 00:02:30.869 --> 00:02:30.879 align:start position:0% but we're going to talk about things 00:02:30.879 --> 00:02:33.309 align:start position:0% but we're going to talk about things that<00:02:31.000> work<00:02:31.400> right<00:02:31.599> now<00:02:32.239> with<00:02:32.480> wallets<00:02:32.959> sort<00:02:33.160> of 00:02:33.309 --> 00:02:33.319 align:start position:0% that work right now with wallets sort of 00:02:33.319 --> 00:02:36.150 align:start position:0% that work right now with wallets sort of on<00:02:33.560> any<00:02:33.800> chain<00:02:34.800> um<00:02:35.200> and<00:02:35.440> even<00:02:35.720> with<00:02:35.879> you<00:02:36.000> know 00:02:36.150 --> 00:02:36.160 align:start position:0% on any chain um and even with you know 00:02:36.160 --> 00:02:37.869 align:start position:0% on any chain um and even with you know custodial<00:02:36.680> apps<00:02:36.959> like<00:02:37.160> coinbase<00:02:37.680> like 00:02:37.869 --> 00:02:37.879 align:start position:0% custodial apps like coinbase like 00:02:37.879 --> 00:02:40.790 align:start position:0% custodial apps like coinbase like binance<00:02:38.319> like<00:02:38.720> lemon<00:02:39.720> um<00:02:40.200> yeah<00:02:40.400> what<00:02:40.560> we're 00:02:40.790 --> 00:02:40.800 align:start position:0% binance like lemon um yeah what we're 00:02:40.800 --> 00:02:42.110 align:start position:0% binance like lemon um yeah what we're what<00:02:40.920> we're<00:02:41.040> shooting<00:02:41.400> for<00:02:41.599> is<00:02:41.760> something 00:02:42.110 --> 00:02:42.120 align:start position:0% what we're shooting for is something 00:02:42.120 --> 00:02:44.149 align:start position:0% what we're shooting for is something like<00:02:42.319> this<00:02:42.400> is<00:02:42.640> from<00:02:43.159> one<00:02:43.319> of<00:02:43.640> vitalik's 00:02:44.149 --> 00:02:44.159 align:start position:0% like this is from one of vitalik's 00:02:44.159 --> 00:02:46.030 align:start position:0% like this is from one of vitalik's recent<00:02:44.440> pieces<00:02:44.760> this<00:02:44.920> idea<00:02:45.159> of<00:02:45.280> one<00:02:45.480> ethereum 00:02:46.030 --> 00:02:46.040 align:start position:0% recent pieces this idea of one ethereum 00:02:46.040 --> 00:02:47.509 align:start position:0% recent pieces this idea of one ethereum something<00:02:46.280> that<00:02:46.400> feels<00:02:46.640> like<00:02:46.760> a<00:02:46.920> cohesive 00:02:47.509 --> 00:02:47.519 align:start position:0% something that feels like a cohesive 00:02:47.519 --> 00:02:49.830 align:start position:0% something that feels like a cohesive ecosystem<00:02:48.519> and<00:02:48.879> what<00:02:49.000> we're<00:02:49.120> shooting<00:02:49.440> for<00:02:49.680> is 00:02:49.830 --> 00:02:49.840 align:start position:0% ecosystem and what we're shooting for is 00:02:49.840 --> 00:02:52.910 align:start position:0% ecosystem and what we're shooting for is something<00:02:50.239> that<00:02:50.760> feels<00:02:51.400> as<00:02:51.640> easy<00:02:51.920> to<00:02:52.120> use<00:02:52.519> as 00:02:52.910 --> 00:02:52.920 align:start position:0% something that feels as easy to use as 00:02:52.920 --> 00:02:54.869 align:start position:0% something that feels as easy to use as smooth<00:02:53.280> as<00:02:53.440> something<00:02:53.720> like<00:02:53.920> Apple<00:02:54.200> pay<00:02:54.680> so 00:02:54.869 --> 00:02:54.879 align:start position:0% smooth as something like Apple pay so 00:02:54.879 --> 00:02:57.270 align:start position:0% smooth as something like Apple pay so you<00:02:55.080> have<00:02:55.480> you<00:02:55.599> know<00:02:55.800> like<00:02:55.959> one<00:02:56.319> action<00:02:57.120> you 00:02:57.270 --> 00:02:57.280 align:start position:0% you have you know like one action you 00:02:57.280 --> 00:02:58.910 align:start position:0% you have you know like one action you click<00:02:57.560> Send<00:02:58.040> and<00:02:58.159> it<00:02:58.319> does<00:02:58.519> whatever<00:02:58.800> you 00:02:58.910 --> 00:02:58.920 align:start position:0% click Send and it does whatever you 00:02:58.920 --> 00:03:01.670 align:start position:0% click Send and it does whatever you wanted<00:02:59.159> it<00:02:59.239> to<00:02:59.400> do 00:03:01.670 --> 00:03:01.680 align:start position:0% wanted it to do 00:03:01.680 --> 00:03:03.190 align:start position:0% wanted it to do yeah<00:03:02.000> I'm<00:03:02.120> going<00:03:02.200> to<00:03:02.319> talk<00:03:02.560> very<00:03:02.800> briefly 00:03:03.190 --> 00:03:03.200 align:start position:0% yeah I'm going to talk very briefly 00:03:03.200 --> 00:03:05.110 align:start position:0% yeah I'm going to talk very briefly about<00:03:03.360> sort<00:03:03.560> of<00:03:03.720> the<00:03:03.959> background<00:03:04.599> of<00:03:04.840> like 00:03:05.110 --> 00:03:05.120 align:start position:0% about sort of the background of like 00:03:05.120 --> 00:03:07.390 align:start position:0% about sort of the background of like create<00:03:05.519> to<00:03:06.280> about<00:03:06.519> cross-chain<00:03:07.080> accounts 00:03:07.390 --> 00:03:07.400 align:start position:0% create to about cross-chain accounts 00:03:07.400 --> 00:03:09.190 align:start position:0% create to about cross-chain accounts about<00:03:07.560> sort<00:03:07.680> of<00:03:07.840> the<00:03:08.040> ideas<00:03:08.400> that<00:03:08.599> inspired 00:03:09.190 --> 00:03:09.200 align:start position:0% about sort of the ideas that inspired 00:03:09.200 --> 00:03:10.830 align:start position:0% about sort of the ideas that inspired this<00:03:10.000> um<00:03:10.120> and<00:03:10.239> then<00:03:10.319> we're<00:03:10.440> going<00:03:10.519> to<00:03:10.680> talk 00:03:10.830 --> 00:03:10.840 align:start position:0% this um and then we're going to talk 00:03:10.840 --> 00:03:12.309 align:start position:0% this um and then we're going to talk about<00:03:11.080> intent<00:03:11.440> addresses<00:03:11.879> which<00:03:12.000> is<00:03:12.080> the<00:03:12.200> new 00:03:12.309 --> 00:03:12.319 align:start position:0% about intent addresses which is the new 00:03:12.319 --> 00:03:15.270 align:start position:0% about intent addresses which is the new thing<00:03:12.480> we're<00:03:12.640> presenting<00:03:13.280> today<00:03:14.280> um<00:03:14.840> how<00:03:15.000> many 00:03:15.270 --> 00:03:15.280 align:start position:0% thing we're presenting today um how many 00:03:15.280 --> 00:03:17.630 align:start position:0% thing we're presenting today um how many people<00:03:15.560> here<00:03:15.879> have<00:03:16.040> heard<00:03:16.280> of<00:03:16.840> or<00:03:17.120> like<00:03:17.400> know 00:03:17.630 --> 00:03:17.640 align:start position:0% people here have heard of or like know 00:03:17.640 --> 00:03:19.630 align:start position:0% people here have heard of or like know what<00:03:17.920> create<00:03:18.280> 2 00:03:19.630 --> 00:03:19.640 align:start position:0% what create 2 00:03:19.640 --> 00:03:22.910 align:start position:0% what create 2 is<00:03:20.640> oh<00:03:20.879> hey<00:03:21.280> wow<00:03:21.640> that<00:03:21.720> is<00:03:22.519> okay<00:03:22.720> very 00:03:22.910 --> 00:03:22.920 align:start position:0% is oh hey wow that is okay very 00:03:22.920 --> 00:03:25.270 align:start position:0% is oh hey wow that is okay very technical<00:03:23.280> audience<00:03:23.599> that's<00:03:23.840> great<00:03:24.280> perfect 00:03:25.270 --> 00:03:25.280 align:start position:0% technical audience that's great perfect 00:03:25.280 --> 00:03:27.630 align:start position:0% technical audience that's great perfect yeah<00:03:25.440> so<00:03:25.560> it<00:03:25.680> lets<00:03:25.879> us<00:03:26.040> commit<00:03:26.360> to<00:03:26.840> a<00:03:27.400> uh<00:03:27.519> it 00:03:27.630 --> 00:03:27.640 align:start position:0% yeah so it lets us commit to a uh it 00:03:27.640 --> 00:03:29.910 align:start position:0% yeah so it lets us commit to a uh it lets<00:03:27.840> us<00:03:28.000> commit<00:03:28.280> to<00:03:28.400> a<00:03:28.519> contract<00:03:29.200> we<00:03:29.319> can<00:03:29.480> make 00:03:29.910 --> 00:03:29.920 align:start position:0% lets us commit to a contract we can make 00:03:29.920 --> 00:03:32.670 align:start position:0% lets us commit to a contract we can make an<00:03:30.120> address<00:03:30.840> that<00:03:31.239> only<00:03:31.599> one<00:03:32.080> specific 00:03:32.670 --> 00:03:32.680 align:start position:0% an address that only one specific 00:03:32.680 --> 00:03:34.910 align:start position:0% an address that only one specific contract<00:03:33.120> with<00:03:33.319> specific<00:03:33.720> functionality<00:03:34.680> can 00:03:34.910 --> 00:03:34.920 align:start position:0% contract with specific functionality can 00:03:34.920 --> 00:03:37.390 align:start position:0% contract with specific functionality can exist<00:03:35.239> at<00:03:35.400> that<00:03:35.720> address<00:03:36.720> the<00:03:36.920> sort<00:03:37.080> of 00:03:37.390 --> 00:03:37.400 align:start position:0% exist at that address the sort of 00:03:37.400 --> 00:03:39.509 align:start position:0% exist at that address the sort of original<00:03:38.000> main<00:03:38.439> use<00:03:38.760> case<00:03:38.959> for<00:03:39.120> this<00:03:39.280> what<00:03:39.439> a 00:03:39.509 --> 00:03:39.519 align:start position:0% original main use case for this what a 00:03:39.519 --> 00:03:41.710 align:start position:0% original main use case for this what a lot<00:03:39.640> of<00:03:39.760> it<00:03:39.879> has<00:03:40.000> been<00:03:40.239> so<00:03:40.439> far<00:03:41.120> is<00:03:41.480> these 00:03:41.710 --> 00:03:41.720 align:start position:0% lot of it has been so far is these 00:03:41.720 --> 00:03:46.270 align:start position:0% lot of it has been so far is these cross-chain<00:03:42.480> accounts<00:03:43.560> um<00:03:44.879> so<00:03:45.879> we<00:03:46.000> should<00:03:46.159> do 00:03:46.270 --> 00:03:46.280 align:start position:0% cross-chain accounts um so we should do 00:03:46.280 --> 00:03:48.670 align:start position:0% cross-chain accounts um so we should do the<00:03:46.439> next<00:03:46.640> slide<00:03:46.879> with<00:03:47.080> the<00:03:47.640> diagram<00:03:48.080> on<00:03:48.200> it 00:03:48.670 --> 00:03:48.680 align:start position:0% the next slide with the diagram on it 00:03:48.680 --> 00:03:51.470 align:start position:0% the next slide with the diagram on it yeah<00:03:49.200> perfect<00:03:50.200> so<00:03:50.480> this<00:03:50.560> is<00:03:50.959> this<00:03:51.120> idea<00:03:51.360> of 00:03:51.470 --> 00:03:51.480 align:start position:0% yeah perfect so this is this idea of 00:03:51.480 --> 00:03:53.869 align:start position:0% yeah perfect so this is this idea of like<00:03:51.680> okay<00:03:51.879> EAS<00:03:52.360> work<00:03:52.640> everywhere<00:03:53.439> you<00:03:53.599> have 00:03:53.869 --> 00:03:53.879 align:start position:0% like okay EAS work everywhere you have 00:03:53.879 --> 00:03:56.350 align:start position:0% like okay EAS work everywhere you have things<00:03:54.120> that<00:03:54.280> only<00:03:54.519> work<00:03:54.720> on<00:03:54.879> certain<00:03:55.360> chains 00:03:56.350 --> 00:03:56.360 align:start position:0% things that only work on certain chains 00:03:56.360 --> 00:03:57.830 align:start position:0% things that only work on certain chains um<00:03:56.640> so<00:03:56.840> for<00:03:57.000> example<00:03:57.319> like<00:03:57.400> if<00:03:57.480> you<00:03:57.599> heard<00:03:57.760> of 00:03:57.830 --> 00:03:57.840 align:start position:0% um so for example like if you heard of 00:03:57.840 --> 00:04:00.309 align:start position:0% um so for example like if you heard of the<00:03:57.920> winter<00:03:58.159> mute<00:03:58.480> hack<00:03:58.680> two<00:03:58.879> years<00:03:59.079> ago<00:04:00.000> um 00:04:00.309 --> 00:04:00.319 align:start position:0% the winter mute hack two years ago um 00:04:00.319 --> 00:04:03.390 align:start position:0% the winter mute hack two years ago um where<00:04:00.920> they<00:04:01.120> had<00:04:01.360> a<00:04:01.680> a<00:04:01.920> Nosa<00:04:02.439> safe<00:04:02.760> that<00:04:02.959> hadn't 00:04:03.390 --> 00:04:03.400 align:start position:0% where they had a a Nosa safe that hadn't 00:04:03.400 --> 00:04:04.990 align:start position:0% where they had a a Nosa safe that hadn't yet<00:04:03.560> been<00:04:03.799> deployed<00:04:04.200> on<00:04:04.319> a<00:04:04.439> different<00:04:04.680> chain 00:04:04.990 --> 00:04:05.000 align:start position:0% yet been deployed on a different chain 00:04:05.000 --> 00:04:06.309 align:start position:0% yet been deployed on a different chain and<00:04:05.079> then<00:04:05.200> someone<00:04:05.439> sent<00:04:05.680> funds<00:04:05.959> to<00:04:06.079> it<00:04:06.159> it<00:04:06.239> was 00:04:06.309 --> 00:04:06.319 align:start position:0% and then someone sent funds to it it was 00:04:06.319 --> 00:04:09.869 align:start position:0% and then someone sent funds to it it was a<00:04:06.439> sa<00:04:06.680> time<00:04:07.680> um<00:04:08.680> with<00:04:08.840> this<00:04:09.360> you<00:04:09.480> know<00:04:09.680> with 00:04:09.869 --> 00:04:09.879 align:start position:0% a sa time um with this you know with 00:04:09.879 --> 00:04:12.149 align:start position:0% a sa time um with this you know with like<00:04:10.319> uh<00:04:10.840> cross-chain<00:04:11.360> accounts<00:04:11.640> Universal 00:04:12.149 --> 00:04:12.159 align:start position:0% like uh cross-chain accounts Universal 00:04:12.159 --> 00:04:14.750 align:start position:0% like uh cross-chain accounts Universal accounts<00:04:12.439> you<00:04:12.560> can<00:04:12.680> use<00:04:13.000> create<00:04:13.319> 2<00:04:13.799> and<00:04:13.959> 4337 00:04:14.750 --> 00:04:14.760 align:start position:0% accounts you can use create 2 and 4337 00:04:14.760 --> 00:04:16.789 align:start position:0% accounts you can use create 2 and 4337 to<00:04:14.879> make<00:04:15.000> an<00:04:15.159> account<00:04:15.360> that<00:04:15.480> just<00:04:15.760> works<00:04:16.280> on 00:04:16.789 --> 00:04:16.799 align:start position:0% to make an account that just works on 00:04:16.799 --> 00:04:19.349 align:start position:0% to make an account that just works on every<00:04:17.079> chain<00:04:18.000> um<00:04:18.199> and<00:04:18.359> even<00:04:18.600> like<00:04:18.759> new<00:04:18.959> evm 00:04:19.349 --> 00:04:19.359 align:start position:0% every chain um and even like new evm 00:04:19.359 --> 00:04:21.629 align:start position:0% every chain um and even like new evm chains<00:04:19.639> that<00:04:19.759> don't<00:04:20.000> exist<00:04:20.400> yet<00:04:20.959> that<00:04:21.280> one 00:04:21.629 --> 00:04:21.639 align:start position:0% chains that don't exist yet that one 00:04:21.639 --> 00:04:23.350 align:start position:0% chains that don't exist yet that one specific<00:04:22.160> contract<00:04:22.520> will<00:04:22.680> be<00:04:22.800> Deployable 00:04:23.350 --> 00:04:23.360 align:start position:0% specific contract will be Deployable 00:04:23.360 --> 00:04:25.310 align:start position:0% specific contract will be Deployable there<00:04:24.280> um<00:04:24.360> there's<00:04:24.520> a<00:04:24.639> whole<00:04:24.800> nice<00:04:25.000> design 00:04:25.310 --> 00:04:25.320 align:start position:0% there um there's a whole nice design 00:04:25.320 --> 00:04:27.110 align:start position:0% there um there's a whole nice design space<00:04:25.560> around<00:04:25.880> that<00:04:26.440> and<00:04:26.560> we<00:04:26.680> thought<00:04:26.919> what<00:04:27.040> if 00:04:27.110 --> 00:04:27.120 align:start position:0% space around that and we thought what if 00:04:27.120 --> 00:04:28.870 align:start position:0% space around that and we thought what if we<00:04:27.240> could<00:04:27.400> go<00:04:27.560> one<00:04:27.800> level<00:04:28.080> deeper<00:04:28.560> what<00:04:28.680> if<00:04:28.759> we 00:04:28.870 --> 00:04:28.880 align:start position:0% we could go one level deeper what if we 00:04:28.880 --> 00:04:32.110 align:start position:0% we could go one level deeper what if we could<00:04:29.039> make<00:04:29.199> this<00:04:29.400> more<00:04:30.000> General<00:04:31.000> um<00:04:31.240> and<00:04:31.400> so 00:04:32.110 --> 00:04:32.120 align:start position:0% could make this more General um and so 00:04:32.120 --> 00:04:36.629 align:start position:0% could make this more General um and so what<00:04:32.280> an<00:04:32.440> intent<00:04:32.800> address<00:04:33.280> is<00:04:34.280> um<00:04:35.160> let's<00:04:35.639> do 00:04:36.629 --> 00:04:36.639 align:start position:0% what an intent address is um let's do 00:04:36.639 --> 00:04:38.629 align:start position:0% what an intent address is um let's do yes<00:04:37.000> perfect<00:04:37.440> so<00:04:37.680> intent<00:04:38.039> address<00:04:38.320> lets<00:04:38.479> you 00:04:38.629 --> 00:04:38.639 align:start position:0% yes perfect so intent address lets you 00:04:38.639 --> 00:04:41.029 align:start position:0% yes perfect so intent address lets you accomplish<00:04:39.000> an<00:04:39.199> arbitrary<00:04:39.800> action<00:04:40.560> just<00:04:40.840> by 00:04:41.029 --> 00:04:41.039 align:start position:0% accomplish an arbitrary action just by 00:04:41.039 --> 00:04:42.909 align:start position:0% accomplish an arbitrary action just by sending<00:04:41.479> funds<00:04:41.840> to<00:04:42.000> that 00:04:42.909 --> 00:04:42.919 align:start position:0% sending funds to that 00:04:42.919 --> 00:04:46.550 align:start position:0% sending funds to that address<00:04:43.919> um<00:04:44.199> so<00:04:45.199> if<00:04:45.320> you<00:04:45.440> can<00:04:45.600> imagine<00:04:46.120> like 00:04:46.550 --> 00:04:46.560 align:start position:0% address um so if you can imagine like 00:04:46.560 --> 00:04:49.670 align:start position:0% address um so if you can imagine like let's<00:04:46.759> say<00:04:47.080> I<00:04:47.199> want<00:04:47.360> to<00:04:48.039> put<00:04:48.320> $70<00:04:49.120> into<00:04:49.360> poly 00:04:49.670 --> 00:04:49.680 align:start position:0% let's say I want to put $70 into poly 00:04:49.680 --> 00:04:52.790 align:start position:0% let's say I want to put $70 into poly Market<00:04:50.639> we<00:04:50.759> can<00:04:51.039> generate<00:04:51.639> an<00:04:51.919> address<00:04:52.560> that 00:04:52.790 --> 00:04:52.800 align:start position:0% Market we can generate an address that 00:04:52.800 --> 00:04:55.230 align:start position:0% Market we can generate an address that represents<00:04:53.400> that<00:04:53.639> intent<00:04:54.639> and<00:04:54.800> then<00:04:54.960> if<00:04:55.080> I 00:04:55.230 --> 00:04:55.240 align:start position:0% represents that intent and then if I 00:04:55.240 --> 00:04:58.390 align:start position:0% represents that intent and then if I send<00:04:55.560> $70<00:04:56.479> worth<00:04:56.720> of<00:04:56.960> any<00:04:57.199> coin<00:04:57.440> on<00:04:57.600> any<00:04:57.800> chain 00:04:58.390 --> 00:04:58.400 align:start position:0% send $70 worth of any coin on any chain 00:04:58.400 --> 00:05:01.189 align:start position:0% send $70 worth of any coin on any chain to<00:04:58.639> that<00:04:58.800> address<00:04:59.840> then<00:05:00.320> a<00:05:00.479> reers<00:05:00.919> will<00:05:01.080> be 00:05:01.189 --> 00:05:01.199 align:start position:0% to that address then a reers will be 00:05:01.199 --> 00:05:03.070 align:start position:0% to that address then a reers will be able<00:05:01.360> to<00:05:01.520> come<00:05:01.680> in<00:05:01.960> and<00:05:02.160> permissionless<00:05:02.880> do 00:05:03.070 --> 00:05:03.080 align:start position:0% able to come in and permissionless do 00:05:03.080 --> 00:05:05.990 align:start position:0% able to come in and permissionless do the<00:05:03.240> rest<00:05:03.800> but<00:05:03.960> only<00:05:04.320> that<00:05:04.600> so<00:05:05.000> there's<00:05:05.240> no<00:05:05.880> you 00:05:05.990 --> 00:05:06.000 align:start position:0% the rest but only that so there's no you 00:05:06.000 --> 00:05:07.390 align:start position:0% the rest but only that so there's no you know<00:05:06.199> counterparty<00:05:06.840> risk<00:05:07.120> you're<00:05:07.240> not 00:05:07.390 --> 00:05:07.400 align:start position:0% know counterparty risk you're not 00:05:07.400 --> 00:05:11.550 align:start position:0% know counterparty risk you're not necessarily<00:05:08.000> trusting<00:05:08.479> anyone<00:05:09.560> um<00:05:10.560> it's<00:05:10.840> just 00:05:11.550 --> 00:05:11.560 align:start position:0% necessarily trusting anyone um it's just 00:05:11.560 --> 00:05:13.150 align:start position:0% necessarily trusting anyone um it's just by<00:05:11.759> sending<00:05:12.080> money<00:05:12.320> to<00:05:12.479> this<00:05:12.680> address<00:05:12.919> you're 00:05:13.150 --> 00:05:13.160 align:start position:0% by sending money to this address you're 00:05:13.160 --> 00:05:15.390 align:start position:0% by sending money to this address you're expressing<00:05:13.520> an<00:05:13.639> intent<00:05:14.039> of<00:05:14.240> like<00:05:14.400> I<00:05:14.520> want<00:05:14.680> $70 00:05:15.390 --> 00:05:15.400 align:start position:0% expressing an intent of like I want $70 00:05:15.400 --> 00:05:18.150 align:start position:0% expressing an intent of like I want $70 to<00:05:15.479> show<00:05:15.759> up<00:05:15.919> in<00:05:16.120> this<00:05:17.039> uh<00:05:17.120> you<00:05:17.240> know<00:05:17.720> uh<00:05:17.880> other 00:05:18.150 --> 00:05:18.160 align:start position:0% to show up in this uh you know uh other 00:05:18.160 --> 00:05:20.029 align:start position:0% to show up in this uh you know uh other place<00:05:18.360> on<00:05:18.560> this<00:05:18.720> specific 00:05:20.029 --> 00:05:20.039 align:start position:0% place on this specific 00:05:20.039 --> 00:05:22.029 align:start position:0% place on this specific chain<00:05:21.039> and<00:05:21.160> so<00:05:21.360> these<00:05:21.479> are<00:05:21.600> the<00:05:21.720> kinds<00:05:21.880> of 00:05:22.029 --> 00:05:22.039 align:start position:0% chain and so these are the kinds of 00:05:22.039 --> 00:05:24.830 align:start position:0% chain and so these are the kinds of things<00:05:22.520> so<00:05:23.280> sending<00:05:23.680> funds<00:05:23.960> via<00:05:24.120> a<00:05:24.240> transfer 00:05:24.830 --> 00:05:24.840 align:start position:0% things so sending funds via a transfer 00:05:24.840 --> 00:05:26.710 align:start position:0% things so sending funds via a transfer via<00:05:25.080> a<00:05:25.240> permit<00:05:25.600> and<00:05:25.720> you<00:05:25.800> can<00:05:26.000> accomplish<00:05:26.520> all 00:05:26.710 --> 00:05:26.720 align:start position:0% via a permit and you can accomplish all 00:05:26.720 --> 00:05:28.670 align:start position:0% via a permit and you can accomplish all kinds<00:05:26.919> of<00:05:27.080> things<00:05:27.360> like<00:05:27.479> a<00:05:27.680> deposit<00:05:28.440> that<00:05:28.560> was 00:05:28.670 --> 00:05:28.680 align:start position:0% kinds of things like a deposit that was 00:05:28.680 --> 00:05:30.510 align:start position:0% kinds of things like a deposit that was the<00:05:28.840> example<00:05:29.120> that<00:05:29.240> I<00:05:29.319> started<00:05:29.880> with<00:05:30.280> you<00:05:30.360> can 00:05:30.510 --> 00:05:30.520 align:start position:0% the example that I started with you can 00:05:30.520 --> 00:05:32.550 align:start position:0% the example that I started with you can do<00:05:30.639> swapping<00:05:31.039> and<00:05:31.199> bridging<00:05:31.840> you<00:05:31.919> can<00:05:32.120> even<00:05:32.280> do 00:05:32.550 --> 00:05:32.560 align:start position:0% do swapping and bridging you can even do 00:05:32.560 --> 00:05:35.909 align:start position:0% do swapping and bridging you can even do arbitrary<00:05:33.080> contract<00:05:33.560> calls<00:05:34.560> um<00:05:35.520> on<00:05:35.639> the 00:05:35.909 --> 00:05:35.919 align:start position:0% arbitrary contract calls um on the 00:05:35.919 --> 00:05:38.070 align:start position:0% arbitrary contract calls um on the receiving<00:05:36.199> side<00:05:36.400> we<00:05:36.560> did<00:05:36.800> a<00:05:37.160> really<00:05:37.840> nice 00:05:38.070 --> 00:05:38.080 align:start position:0% receiving side we did a really nice 00:05:38.080 --> 00:05:40.710 align:start position:0% receiving side we did a really nice launch<00:05:38.400> with<00:05:38.520> our<00:05:38.680> friends<00:05:39.160> at<00:05:39.520> ethereum<00:05:40.039> OS 00:05:40.710 --> 00:05:40.720 align:start position:0% launch with our friends at ethereum OS 00:05:40.720 --> 00:05:42.629 align:start position:0% launch with our friends at ethereum OS uh<00:05:40.840> Freedom<00:05:41.319> Factory<00:05:41.840> you<00:05:41.960> know<00:05:42.160> they<00:05:42.319> make<00:05:42.479> a 00:05:42.629 --> 00:05:42.639 align:start position:0% uh Freedom Factory you know they make a 00:05:42.639 --> 00:05:45.390 align:start position:0% uh Freedom Factory you know they make a new<00:05:43.600> uh<00:05:43.800> a<00:05:43.919> new<00:05:44.039> kind<00:05:44.160> of<00:05:44.280> Hardware<00:05:44.639> wallet<00:05:45.280> and 00:05:45.390 --> 00:05:45.400 align:start position:0% new uh a new kind of Hardware wallet and 00:05:45.400 --> 00:05:46.990 align:start position:0% new uh a new kind of Hardware wallet and the<00:05:45.520> pre-sale<00:05:45.960> for<00:05:46.120> that<00:05:46.280> involves<00:05:46.680> like 00:05:46.990 --> 00:05:47.000 align:start position:0% the pre-sale for that involves like 00:05:47.000 --> 00:05:51.469 align:start position:0% the pre-sale for that involves like minting<00:05:48.000> a<00:05:48.880> pre-order<00:05:50.039> nft<00:05:51.039> and<00:05:51.199> that's<00:05:51.319> an 00:05:51.469 --> 00:05:51.479 align:start position:0% minting a pre-order nft and that's an 00:05:51.479 --> 00:05:52.870 align:start position:0% minting a pre-order nft and that's an arbitrary<00:05:51.960> contract<00:05:52.360> call<00:05:52.560> but<00:05:52.680> you<00:05:52.759> can 00:05:52.870 --> 00:05:52.880 align:start position:0% arbitrary contract call but you can 00:05:52.880 --> 00:05:54.629 align:start position:0% arbitrary contract call but you can still<00:05:53.080> do<00:05:53.240> it<00:05:53.360> via<00:05:53.680> single 00:05:54.629 --> 00:05:54.639 align:start position:0% still do it via single 00:05:54.639 --> 00:05:57.430 align:start position:0% still do it via single transfer<00:05:55.639> um<00:05:56.600> yeah<00:05:56.759> with<00:05:56.919> that<00:05:57.160> I'm<00:05:57.240> going<00:05:57.319> to 00:05:57.430 --> 00:05:57.440 align:start position:0% transfer um yeah with that I'm going to 00:05:57.440 --> 00:05:58.790 align:start position:0% transfer um yeah with that I'm going to hand<00:05:57.600> it<00:05:57.720> back<00:05:57.840> to<00:05:57.960> Andrew<00:05:58.319> and<00:05:58.400> he's<00:05:58.560> going<00:05:58.639> to 00:05:58.790 --> 00:05:58.800 align:start position:0% hand it back to Andrew and he's going to 00:05:58.800 --> 00:06:00.510 align:start position:0% hand it back to Andrew and he's going to walk<00:05:58.960> you<00:05:59.080> through<00:05:59.240> the<00:05:59.360> different<00:05:59.880> steps<00:06:00.319> of 00:06:00.510 --> 00:06:00.520 align:start position:0% walk you through the different steps of 00:06:00.520 --> 00:06:02.270 align:start position:0% walk you through the different steps of like<00:06:00.680> how<00:06:00.800> we<00:06:00.919> can<00:06:01.080> do<00:06:01.319> progressively<00:06:01.960> more 00:06:02.270 --> 00:06:02.280 align:start position:0% like how we can do progressively more 00:06:02.280 --> 00:06:03.710 align:start position:0% like how we can do progressively more with<00:06:02.440> intent 00:06:03.710 --> 00:06:03.720 align:start position:0% with intent 00:06:03.720 --> 00:06:05.629 align:start position:0% with intent addresses<00:06:04.720> one<00:06:04.880> way<00:06:05.039> you<00:06:05.120> can<00:06:05.280> think<00:06:05.440> of 00:06:05.629 --> 00:06:05.639 align:start position:0% addresses one way you can think of 00:06:05.639 --> 00:06:07.589 align:start position:0% addresses one way you can think of intent<00:06:06.039> addresses<00:06:06.639> that<00:06:07.039> would<00:06:07.240> make<00:06:07.360> it 00:06:07.589 --> 00:06:07.599 align:start position:0% intent addresses that would make it 00:06:07.599 --> 00:06:10.390 align:start position:0% intent addresses that would make it easier<00:06:08.160> is<00:06:08.639> think<00:06:08.840> of<00:06:08.960> it<00:06:09.160> as<00:06:09.319> sending<00:06:09.800> funds 00:06:10.390 --> 00:06:10.400 align:start position:0% easier is think of it as sending funds 00:06:10.400 --> 00:06:13.909 align:start position:0% easier is think of it as sending funds to<00:06:10.800> someone's<00:06:11.479> wallet<00:06:12.160> address<00:06:13.160> and<00:06:13.639> they 00:06:13.909 --> 00:06:13.919 align:start position:0% to someone's wallet address and they 00:06:13.919 --> 00:06:16.710 align:start position:0% to someone's wallet address and they execute<00:06:14.400> a<00:06:14.560> contract<00:06:14.919> call<00:06:15.160> on<00:06:15.280> your<00:06:15.720> behalf 00:06:16.710 --> 00:06:16.720 align:start position:0% execute a contract call on your behalf 00:06:16.720 --> 00:06:18.430 align:start position:0% execute a contract call on your behalf now<00:06:17.240> this<00:06:17.400> sounds<00:06:17.680> kind<00:06:17.800> of<00:06:17.919> worrying<00:06:18.319> you're 00:06:18.430 --> 00:06:18.440 align:start position:0% now this sounds kind of worrying you're 00:06:18.440 --> 00:06:20.150 align:start position:0% now this sounds kind of worrying you're sending<00:06:18.840> tokens<00:06:19.240> to<00:06:19.440> someone<00:06:19.840> that<00:06:19.960> you 00:06:20.150 --> 00:06:20.160 align:start position:0% sending tokens to someone that you 00:06:20.160 --> 00:06:22.070 align:start position:0% sending tokens to someone that you potentially<00:06:20.599> don't<00:06:20.800> trust<00:06:21.479> and<00:06:21.639> they<00:06:21.759> can<00:06:21.880> do 00:06:22.070 --> 00:06:22.080 align:start position:0% potentially don't trust and they can do 00:06:22.080 --> 00:06:24.430 align:start position:0% potentially don't trust and they can do anything<00:06:22.400> on<00:06:22.599> chain<00:06:22.919> with<00:06:23.039> your 00:06:24.430 --> 00:06:24.440 align:start position:0% anything on chain with your 00:06:24.440 --> 00:06:26.749 align:start position:0% anything on chain with your funds<00:06:25.440> this<00:06:25.520> is<00:06:25.759> what<00:06:26.080> the<00:06:26.280> problem<00:06:26.560> that 00:06:26.749 --> 00:06:26.759 align:start position:0% funds this is what the problem that 00:06:26.759 --> 00:06:30.629 align:start position:0% funds this is what the problem that intent<00:06:27.360> addresses<00:06:28.000> solve<00:06:29.000> you<00:06:29.160> send 00:06:30.629 --> 00:06:30.639 align:start position:0% intent addresses solve you send 00:06:30.639 --> 00:06:33.550 align:start position:0% intent addresses solve you send uh<00:06:30.800> tokens<00:06:31.199> to<00:06:31.360> an<00:06:31.520> intent<00:06:32.080> address<00:06:33.080> and<00:06:33.319> this 00:06:33.550 --> 00:06:33.560 align:start position:0% uh tokens to an intent address and this 00:06:33.560 --> 00:06:35.629 align:start position:0% uh tokens to an intent address and this intent<00:06:34.039> address<00:06:34.479> permissionless<00:06:35.479> and 00:06:35.629 --> 00:06:35.639 align:start position:0% intent address permissionless and 00:06:35.639 --> 00:06:39.029 align:start position:0% intent address permissionless and trustless<00:06:36.840> guarantees<00:06:37.840> that<00:06:38.280> only<00:06:38.599> one 00:06:39.029 --> 00:06:39.039 align:start position:0% trustless guarantees that only one 00:06:39.039 --> 00:06:41.790 align:start position:0% trustless guarantees that only one action<00:06:39.319> can<00:06:39.479> be<00:06:39.680> executed<00:06:40.160> on<00:06:40.599> chain<00:06:41.599> how<00:06:41.680> do 00:06:41.790 --> 00:06:41.800 align:start position:0% action can be executed on chain how do 00:06:41.800 --> 00:06:45.029 align:start position:0% action can be executed on chain how do we<00:06:41.919> do<00:06:42.120> this<00:06:43.039> we<00:06:43.400> we<00:06:43.479> use<00:06:43.759> create<00:06:44.039> 2<00:06:44.440> like<00:06:44.599> DC 00:06:45.029 --> 00:06:45.039 align:start position:0% we do this we we use create 2 like DC 00:06:45.039 --> 00:06:46.950 align:start position:0% we do this we we use create 2 like DC mentioned<00:06:45.440> to<00:06:45.639> do<00:06:45.840> this<00:06:46.400> for<00:06:46.560> those<00:06:46.680> of<00:06:46.800> you 00:06:46.950 --> 00:06:46.960 align:start position:0% mentioned to do this for those of you 00:06:46.960 --> 00:06:50.749 align:start position:0% mentioned to do this for those of you that<00:06:47.080> don't<00:06:47.280> know<00:06:48.160> create<00:06:48.720> two<00:06:49.720> um<00:06:50.319> is<00:06:50.440> a<00:06:50.599> way 00:06:50.749 --> 00:06:50.759 align:start position:0% that don't know create two um is a way 00:06:50.759 --> 00:06:52.309 align:start position:0% that don't know create two um is a way of<00:06:50.919> deploying<00:06:51.400> smart 00:06:52.309 --> 00:06:52.319 align:start position:0% of deploying smart 00:06:52.319 --> 00:06:55.909 align:start position:0% of deploying smart contracts<00:06:53.319> it<00:06:53.560> takes<00:06:54.080> a<00:06:54.280> hash<00:06:54.720> of<00:06:54.960> your 00:06:55.909 --> 00:06:55.919 align:start position:0% contracts it takes a hash of your 00:06:55.919 --> 00:06:57.869 align:start position:0% contracts it takes a hash of your contract<00:06:56.319> code<00:06:57.160> and<00:06:57.319> generates<00:06:57.720> a 00:06:57.869 --> 00:06:57.879 align:start position:0% contract code and generates a 00:06:57.879 --> 00:06:59.869 align:start position:0% contract code and generates a deterministic<00:06:58.680> address<00:06:59.080> that<00:06:59.160> you<00:06:59.280> know 00:06:59.869 --> 00:06:59.879 align:start position:0% deterministic address that you know 00:06:59.879 --> 00:07:01.909 align:start position:0% deterministic address that you know beforehand<00:07:00.879> if<00:07:00.960> you<00:07:01.080> change<00:07:01.360> the<00:07:01.520> code<00:07:01.759> you 00:07:01.909 --> 00:07:01.919 align:start position:0% beforehand if you change the code you 00:07:01.919 --> 00:07:03.510 align:start position:0% beforehand if you change the code you change<00:07:02.240> the<00:07:02.440> address<00:07:02.800> that<00:07:02.919> the<00:07:03.039> contract<00:07:03.360> is 00:07:03.510 --> 00:07:03.520 align:start position:0% change the address that the contract is 00:07:03.520 --> 00:07:06.710 align:start position:0% change the address that the contract is deployed<00:07:04.039> to<00:07:05.039> this<00:07:05.199> way<00:07:05.319> you<00:07:05.440> know<00:07:05.800> beforehand 00:07:06.710 --> 00:07:06.720 align:start position:0% deployed to this way you know beforehand 00:07:06.720 --> 00:07:09.510 align:start position:0% deployed to this way you know beforehand exactly<00:07:07.720> what<00:07:07.879> the<00:07:08.000> contract<00:07:08.400> is<00:07:08.520> going<00:07:08.680> to<00:07:08.840> do 00:07:09.510 --> 00:07:09.520 align:start position:0% exactly what the contract is going to do 00:07:09.520 --> 00:07:12.189 align:start position:0% exactly what the contract is going to do when<00:07:09.680> you<00:07:09.840> send<00:07:10.520> the<00:07:10.680> tokens<00:07:11.039> to<00:07:11.240> this 00:07:12.189 --> 00:07:12.199 align:start position:0% when you send the tokens to this 00:07:12.199 --> 00:07:14.550 align:start position:0% when you send the tokens to this address<00:07:13.199> so<00:07:13.319> we'll<00:07:13.520> use<00:07:13.680> an<00:07:13.840> example<00:07:14.240> here<00:07:14.440> of 00:07:14.550 --> 00:07:14.560 align:start position:0% address so we'll use an example here of 00:07:14.560 --> 00:07:18.309 align:start position:0% address so we'll use an example here of minting<00:07:14.919> an<00:07:15.280> nft<00:07:16.280> on<00:07:16.960> using 00:07:18.309 --> 00:07:18.319 align:start position:0% minting an nft on using 00:07:18.319 --> 00:07:21.270 align:start position:0% minting an nft on using usdc<00:07:19.319> so<00:07:19.759> I<00:07:19.919> transfer<00:07:20.400> tokens<00:07:20.720> to<00:07:20.879> this<00:07:21.000> create 00:07:21.270 --> 00:07:21.280 align:start position:0% usdc so I transfer tokens to this create 00:07:21.280 --> 00:07:25.110 align:start position:0% usdc so I transfer tokens to this create 2<00:07:21.720> address<00:07:22.720> and<00:07:22.879> then<00:07:23.120> now<00:07:24.120> anyone<00:07:24.759> can<00:07:24.960> come 00:07:25.110 --> 00:07:25.120 align:start position:0% 2 address and then now anyone can come 00:07:25.120 --> 00:07:28.070 align:start position:0% 2 address and then now anyone can come in<00:07:25.680> deploy<00:07:26.080> the<00:07:26.199> contract<00:07:26.560> to<00:07:26.720> the<00:07:27.080> address 00:07:28.070 --> 00:07:28.080 align:start position:0% in deploy the contract to the address 00:07:28.080 --> 00:07:29.990 align:start position:0% in deploy the contract to the address and<00:07:28.319> this<00:07:28.560> contract<00:07:28.919> can<00:07:29.039> only<00:07:29.199> do<00:07:29.560> one<00:07:29.720> thing 00:07:29.990 --> 00:07:30.000 align:start position:0% and this contract can only do one thing 00:07:30.000 --> 00:07:32.990 align:start position:0% and this contract can only do one thing it<00:07:30.080> can<00:07:30.400> only<00:07:30.639> mint<00:07:31.000> an<00:07:31.160> nft<00:07:32.039> with<00:07:32.280> a<00:07:32.479> contract 00:07:32.990 --> 00:07:33.000 align:start position:0% it can only mint an nft with a contract 00:07:33.000 --> 00:07:36.670 align:start position:0% it can only mint an nft with a contract you<00:07:33.879> specify<00:07:34.879> it<00:07:35.039> mints<00:07:35.319> the<00:07:35.440> nft<00:07:35.879> by<00:07:36.039> sending 00:07:36.670 --> 00:07:36.680 align:start position:0% you specify it mints the nft by sending 00:07:36.680 --> 00:07:39.150 align:start position:0% you specify it mints the nft by sending tokens<00:07:37.080> to<00:07:37.319> that<00:07:37.720> contract<00:07:38.680> and<00:07:38.840> gives<00:07:39.039> the 00:07:39.150 --> 00:07:39.160 align:start position:0% tokens to that contract and gives the 00:07:39.160 --> 00:07:41.830 align:start position:0% tokens to that contract and gives the nft<00:07:39.759> back<00:07:40.120> to<00:07:40.360> the 00:07:41.830 --> 00:07:41.840 align:start position:0% nft back to the 00:07:41.840 --> 00:07:43.950 align:start position:0% nft back to the user<00:07:42.840> now<00:07:43.000> what's<00:07:43.160> the<00:07:43.240> point<00:07:43.440> of<00:07:43.520> doing<00:07:43.759> all 00:07:43.950 --> 00:07:43.960 align:start position:0% user now what's the point of doing all 00:07:43.960 --> 00:07:46.070 align:start position:0% user now what's the point of doing all this<00:07:44.280> to<00:07:44.759> all<00:07:44.879> this<00:07:45.039> fancy<00:07:45.479> stuff<00:07:45.639> with<00:07:45.800> create 00:07:46.070 --> 00:07:46.080 align:start position:0% this to all this fancy stuff with create 00:07:46.080 --> 00:07:50.469 align:start position:0% this to all this fancy stuff with create 2<00:07:46.840> when<00:07:47.000> you<00:07:47.120> can<00:07:47.400> just<00:07:47.960> use<00:07:48.280> your<00:07:48.759> EA<00:07:49.479> wallet 00:07:50.469 --> 00:07:50.479 align:start position:0% 2 when you can just use your EA wallet 00:07:50.479 --> 00:07:52.670 align:start position:0% 2 when you can just use your EA wallet the<00:07:50.599> first<00:07:50.800> thing<00:07:50.919> it<00:07:51.080> enables<00:07:51.840> is<00:07:52.199> a<00:07:52.360> single 00:07:52.670 --> 00:07:52.680 align:start position:0% the first thing it enables is a single 00:07:52.680 --> 00:07:56.510 align:start position:0% the first thing it enables is a single wallet<00:07:53.120> popup<00:07:54.039> to<00:07:54.879> uh<00:07:55.080> execute<00:07:55.520> this<00:07:55.720> contract 00:07:56.510 --> 00:07:56.520 align:start position:0% wallet popup to uh execute this contract 00:07:56.520 --> 00:07:58.909 align:start position:0% wallet popup to uh execute this contract interaction<00:07:57.520> the<00:07:57.680> normal<00:07:57.960> flow<00:07:58.400> has<00:07:58.639> always 00:07:58.909 --> 00:07:58.919 align:start position:0% interaction the normal flow has always 00:07:58.919 --> 00:08:02.469 align:start position:0% interaction the normal flow has always been<00:07:59.800> approve<00:08:00.199> the<00:08:00.599> contract<00:08:01.599> then<00:08:02.240> uh 00:08:02.469 --> 00:08:02.479 align:start position:0% been approve the contract then uh 00:08:02.479 --> 00:08:05.110 align:start position:0% been approve the contract then uh execute<00:08:02.879> the<00:08:03.039> contract<00:08:03.840> call<00:08:04.840> this<00:08:04.960> is 00:08:05.110 --> 00:08:05.120 align:start position:0% execute the contract call this is 00:08:05.120 --> 00:08:07.230 align:start position:0% execute the contract call this is something<00:08:05.400> we'<00:08:05.599> become<00:08:05.840> numb<00:08:06.159> to<00:08:06.319> in<00:08:06.440> ethereum 00:08:07.230 --> 00:08:07.240 align:start position:0% something we' become numb to in ethereum 00:08:07.240 --> 00:08:10.029 align:start position:0% something we' become numb to in ethereum and<00:08:07.840> a<00:08:08.000> terrible<00:08:08.400> ux<00:08:08.759> for<00:08:08.960> users<00:08:09.599> that<00:08:09.759> we've 00:08:10.029 --> 00:08:10.039 align:start position:0% and a terrible ux for users that we've 00:08:10.039 --> 00:08:13.309 align:start position:0% and a terrible ux for users that we've just<00:08:10.639> accepted<00:08:11.400> as<00:08:12.319> something<00:08:12.759> that<00:08:13.039> we<00:08:13.199> have 00:08:13.309 --> 00:08:13.319 align:start position:0% just accepted as something that we have 00:08:13.319 --> 00:08:16.350 align:start position:0% just accepted as something that we have to<00:08:13.479> deal<00:08:14.039> with<00:08:15.039> with<00:08:15.199> intent<00:08:15.639> addresses<00:08:16.280> if 00:08:16.350 --> 00:08:16.360 align:start position:0% to deal with with intent addresses if 00:08:16.360 --> 00:08:18.149 align:start position:0% to deal with with intent addresses if you<00:08:16.479> noticed<00:08:16.960> all<00:08:17.080> you<00:08:17.199> have<00:08:17.319> to<00:08:17.520> do<00:08:17.879> all<00:08:18.039> the 00:08:18.149 --> 00:08:18.159 align:start position:0% you noticed all you have to do all the 00:08:18.159 --> 00:08:20.830 align:start position:0% you noticed all you have to do all the user<00:08:18.440> has<00:08:18.599> to<00:08:18.759> sign<00:08:19.120> is<00:08:19.319> one<00:08:19.599> transfer 00:08:20.830 --> 00:08:20.840 align:start position:0% user has to sign is one transfer 00:08:20.840 --> 00:08:23.149 align:start position:0% user has to sign is one transfer interaction<00:08:21.840> no<00:08:22.000> more<00:08:22.199> two<00:08:22.520> popups<00:08:22.960> just<00:08:23.080> a 00:08:23.149 --> 00:08:23.159 align:start position:0% interaction no more two popups just a 00:08:23.159 --> 00:08:27.110 align:start position:0% interaction no more two popups just a single<00:08:23.520> popup<00:08:24.159> to<00:08:25.159> uh<00:08:25.479> execute<00:08:25.840> an<00:08:25.960> on-<00:08:26.120> train 00:08:27.110 --> 00:08:27.120 align:start position:0% single popup to uh execute an on- train 00:08:27.120 --> 00:08:30.390 align:start position:0% single popup to uh execute an on- train call<00:08:28.120> another<00:08:28.479> benefit<00:08:28.840> this<00:08:29.000> gives<00:08:29.199> you<00:08:29.840> is 00:08:30.390 --> 00:08:30.400 align:start position:0% call another benefit this gives you is 00:08:30.400 --> 00:08:32.990 align:start position:0% call another benefit this gives you is it<00:08:30.520> allows<00:08:30.960> people<00:08:31.240> to<00:08:31.520> pay<00:08:32.200> or<00:08:32.399> to<00:08:32.560> interact 00:08:32.990 --> 00:08:33.000 align:start position:0% it allows people to pay or to interact 00:08:33.000 --> 00:08:35.670 align:start position:0% it allows people to pay or to interact with<00:08:33.200> contracts<00:08:33.640> on<00:08:33.880> chain<00:08:34.479> using<00:08:35.000> an 00:08:35.670 --> 00:08:35.680 align:start position:0% with contracts on chain using an 00:08:35.680 --> 00:08:38.790 align:start position:0% with contracts on chain using an exchange<00:08:36.680> so<00:08:36.880> you<00:08:37.000> can<00:08:37.200> now<00:08:37.519> mint<00:08:37.760> and<00:08:37.919> nft 00:08:38.790 --> 00:08:38.800 align:start position:0% exchange so you can now mint and nft 00:08:38.800 --> 00:08:41.110 align:start position:0% exchange so you can now mint and nft interact<00:08:39.240> with<00:08:39.399> any<00:08:39.640> contract<00:08:40.000> on<00:08:40.200> chain<00:08:40.640> with 00:08:41.110 --> 00:08:41.120 align:start position:0% interact with any contract on chain with 00:08:41.120 --> 00:08:43.550 align:start position:0% interact with any contract on chain with a<00:08:41.279> coinbase<00:08:41.719> or<00:08:41.800> a<00:08:41.919> binance<00:08:42.399> account<00:08:43.399> you 00:08:43.550 --> 00:08:43.560 align:start position:0% a coinbase or a binance account you 00:08:43.560 --> 00:08:45.269 align:start position:0% a coinbase or a binance account you transfer<00:08:44.000> funds<00:08:44.320> to<00:08:44.560> a<00:08:44.720> predetermined 00:08:45.269 --> 00:08:45.279 align:start position:0% transfer funds to a predetermined 00:08:45.279 --> 00:08:48.150 align:start position:0% transfer funds to a predetermined create2<00:08:46.279> address<00:08:47.279> and<00:08:47.480> that<00:08:47.680> address 00:08:48.150 --> 00:08:48.160 align:start position:0% create2 address and that address 00:08:48.160 --> 00:08:51.389 align:start position:0% create2 address and that address executes<00:08:48.680> the<00:08:49.120> uh<00:08:49.279> contract<00:08:49.680> call<00:08:49.920> on<00:08:50.040> your 00:08:51.389 --> 00:08:51.399 align:start position:0% executes the uh contract call on your 00:08:51.399 --> 00:08:53.949 align:start position:0% executes the uh contract call on your behalf<00:08:52.399> now<00:08:52.560> how<00:08:52.680> does<00:08:52.839> this<00:08:53.000> move<00:08:53.200> us<00:08:53.480> towards 00:08:53.949 --> 00:08:53.959 align:start position:0% behalf now how does this move us towards 00:08:53.959 --> 00:08:55.870 align:start position:0% behalf now how does this move us towards a<00:08:54.080> unified 00:08:55.870 --> 00:08:55.880 align:start position:0% a unified 00:08:55.880 --> 00:08:59.430 align:start position:0% a unified ethereum<00:08:56.880> one<00:08:57.160> really<00:08:57.399> cool<00:08:57.760> thing<00:08:58.760> uh<00:08:59.200> in 00:08:59.430 --> 00:08:59.440 align:start position:0% ethereum one really cool thing uh in 00:08:59.440 --> 00:09:03.230 align:start position:0% ethereum one really cool thing uh in intent<00:08:59.720> addresses<00:09:00.160> enable<00:09:00.600> you<00:09:00.920> to<00:09:01.160> do<00:09:02.240> is 00:09:03.230 --> 00:09:03.240 align:start position:0% intent addresses enable you to do is 00:09:03.240 --> 00:09:05.790 align:start position:0% intent addresses enable you to do is arbitrary<00:09:03.760> bridging<00:09:04.440> so<00:09:04.720> you<00:09:04.839> can<00:09:05.399> set<00:09:05.640> an 00:09:05.790 --> 00:09:05.800 align:start position:0% arbitrary bridging so you can set an 00:09:05.800 --> 00:09:08.150 align:start position:0% arbitrary bridging so you can set an intent<00:09:06.279> address<00:09:07.040> which<00:09:07.240> sends<00:09:07.720> the<00:09:07.839> funds 00:09:08.150 --> 00:09:08.160 align:start position:0% intent address which sends the funds 00:09:08.160 --> 00:09:11.350 align:start position:0% intent address which sends the funds into<00:09:08.399> a<00:09:08.920> bridge<00:09:09.920> and<00:09:10.079> then<00:09:10.360> on<00:09:10.519> the<00:09:10.720> other<00:09:11.000> side 00:09:11.350 --> 00:09:11.360 align:start position:0% into a bridge and then on the other side 00:09:11.360 --> 00:09:14.150 align:start position:0% into a bridge and then on the other side retrieves<00:09:11.800> the<00:09:11.920> funds<00:09:12.320> out<00:09:12.519> from<00:09:12.680> the<00:09:13.160> bridge 00:09:14.150 --> 00:09:14.160 align:start position:0% retrieves the funds out from the bridge 00:09:14.160 --> 00:09:16.910 align:start position:0% retrieves the funds out from the bridge here's<00:09:14.360> an<00:09:14.560> example<00:09:15.079> of<00:09:15.399> how<00:09:15.560> we<00:09:15.640> can<00:09:15.800> do<00:09:16.000> that 00:09:16.910 --> 00:09:16.920 align:start position:0% here's an example of how we can do that 00:09:16.920 --> 00:09:20.230 align:start position:0% here's an example of how we can do that so<00:09:17.120> now<00:09:17.279> let's<00:09:17.760> say<00:09:18.760> I<00:09:18.839> want<00:09:18.959> to<00:09:19.440> maintain<00:09:19.839> nft 00:09:20.230 --> 00:09:20.240 align:start position:0% so now let's say I want to maintain nft 00:09:20.240 --> 00:09:22.670 align:start position:0% so now let's say I want to maintain nft on<00:09:20.440> base<00:09:21.040> but<00:09:21.200> I<00:09:21.320> only<00:09:21.560> have<00:09:21.760> ethereum<00:09:22.279> on 00:09:22.670 --> 00:09:22.680 align:start position:0% on base but I only have ethereum on 00:09:22.680 --> 00:09:24.670 align:start position:0% on base but I only have ethereum on optimism<00:09:23.680> what<00:09:23.800> can<00:09:23.880> I<00:09:24.000> do<00:09:24.120> with<00:09:24.279> intent 00:09:24.670 --> 00:09:24.680 align:start position:0% optimism what can I do with intent 00:09:24.680 --> 00:09:27.590 align:start position:0% optimism what can I do with intent addresses<00:09:25.079> to<00:09:25.240> do<00:09:25.839> this<00:09:26.839> I'll<00:09:27.000> first<00:09:27.240> transfer 00:09:27.590 --> 00:09:27.600 align:start position:0% addresses to do this I'll first transfer 00:09:27.600 --> 00:09:30.710 align:start position:0% addresses to do this I'll first transfer my<00:09:27.720> ethereum<00:09:28.160> to<00:09:28.360> an<00:09:28.519> intent<00:09:28.920> address 00:09:30.710 --> 00:09:30.720 align:start position:0% my ethereum to an intent address 00:09:30.720 --> 00:09:32.949 align:start position:0% my ethereum to an intent address a<00:09:30.839> relayer<00:09:31.360> comes<00:09:31.640> in 00:09:32.949 --> 00:09:32.959 align:start position:0% a relayer comes in 00:09:32.959 --> 00:09:36.190 align:start position:0% a relayer comes in trustless<00:09:33.959> and<00:09:34.640> swaps<00:09:35.279> the<00:09:35.440> ethereum<00:09:35.839> for<00:09:36.000> me 00:09:36.190 --> 00:09:36.200 align:start position:0% trustless and swaps the ethereum for me 00:09:36.200 --> 00:09:38.949 align:start position:0% trustless and swaps the ethereum for me and<00:09:36.279> sends<00:09:36.519> it<00:09:36.640> to<00:09:36.760> a<00:09:37.079> bridge<00:09:38.079> in<00:09:38.240> the<00:09:38.399> contract 00:09:38.949 --> 00:09:38.959 align:start position:0% and sends it to a bridge in the contract 00:09:38.959 --> 00:09:41.509 align:start position:0% and sends it to a bridge in the contract I<00:09:39.079> can<00:09:39.279> guarantee<00:09:39.920> that<00:09:40.440> at<00:09:40.600> least<00:09:40.959> X<00:09:41.279> dollar 00:09:41.509 --> 00:09:41.519 align:start position:0% I can guarantee that at least X dollar 00:09:41.519 --> 00:09:43.910 align:start position:0% I can guarantee that at least X dollar of<00:09:41.680> usdc<00:09:42.320> must<00:09:42.560> come<00:09:42.680> out<00:09:42.800> of<00:09:42.920> the<00:09:43.040> swap 00:09:43.910 --> 00:09:43.920 align:start position:0% of usdc must come out of the swap 00:09:43.920 --> 00:09:47.030 align:start position:0% of usdc must come out of the swap otherwise<00:09:44.279> the<00:09:44.440> contract<00:09:44.800> reverts<00:09:45.720> and<00:09:46.040> the 00:09:47.030 --> 00:09:47.040 align:start position:0% otherwise the contract reverts and the 00:09:47.040 --> 00:09:50.030 align:start position:0% otherwise the contract reverts and the relayer<00:09:48.040> relayer<00:09:48.519> can't<00:09:48.839> execute<00:09:49.279> that 00:09:50.030 --> 00:09:50.040 align:start position:0% relayer relayer can't execute that 00:09:50.040 --> 00:09:52.110 align:start position:0% relayer relayer can't execute that function<00:09:51.040> so<00:09:51.200> the<00:09:51.279> relayer<00:09:51.680> completes<00:09:52.000> the 00:09:52.110 --> 00:09:52.120 align:start position:0% function so the relayer completes the 00:09:52.120 --> 00:09:55.389 align:start position:0% function so the relayer completes the swap<00:09:52.680> sends<00:09:52.959> it<00:09:53.120> into<00:09:53.360> a<00:09:53.480> bridge<00:09:53.839> like 00:09:55.389 --> 00:09:55.399 align:start position:0% swap sends it into a bridge like 00:09:55.399 --> 00:09:57.710 align:start position:0% swap sends it into a bridge like cctp<00:09:56.399> and<00:09:56.519> the<00:09:56.720> later<00:09:57.160> later<00:09:57.440> on<00:09:57.600> the 00:09:57.710 --> 00:09:57.720 align:start position:0% cctp and the later later on the 00:09:57.720 --> 00:10:00.949 align:start position:0% cctp and the later later on the destination<00:09:58.200> chain<00:09:58.839> this<00:09:58.959> is<00:09:59.079> the<00:09:59.399> cool<00:09:59.959> part 00:10:00.949 --> 00:10:00.959 align:start position:0% destination chain this is the cool part 00:10:00.959 --> 00:10:03.949 align:start position:0% destination chain this is the cool part I<00:10:01.079> can<00:10:01.279> now<00:10:01.519> trustless<00:10:02.399> execute<00:10:03.360> the<00:10:03.560> contract 00:10:03.949 --> 00:10:03.959 align:start position:0% I can now trustless execute the contract 00:10:03.959 --> 00:10:06.829 align:start position:0% I can now trustless execute the contract call<00:10:04.320> on<00:10:04.480> the<00:10:04.680> destination<00:10:05.480> chain<00:10:06.480> how<00:10:06.560> do<00:10:06.720> we 00:10:06.829 --> 00:10:06.839 align:start position:0% call on the destination chain how do we 00:10:06.839 --> 00:10:09.350 align:start position:0% call on the destination chain how do we do<00:10:07.120> this<00:10:08.120> when<00:10:08.240> the<00:10:08.360> bridge<00:10:08.680> completes<00:10:09.240> it 00:10:09.350 --> 00:10:09.360 align:start position:0% do this when the bridge completes it 00:10:09.360 --> 00:10:11.949 align:start position:0% do this when the bridge completes it transfers<00:10:09.839> usdc<00:10:10.640> to<00:10:11.079> the<00:10:11.240> same<00:10:11.480> intent 00:10:11.949 --> 00:10:11.959 align:start position:0% transfers usdc to the same intent 00:10:11.959 --> 00:10:15.790 align:start position:0% transfers usdc to the same intent address<00:10:12.720> on<00:10:12.959> the<00:10:13.120> destination<00:10:14.040> chain<00:10:15.040> this 00:10:15.790 --> 00:10:15.800 align:start position:0% address on the destination chain this 00:10:15.800 --> 00:10:20.350 align:start position:0% address on the destination chain this contract<00:10:16.800> because<00:10:17.959> um<00:10:18.959> optimism<00:10:19.760> and<00:10:20.040> base 00:10:20.350 --> 00:10:20.360 align:start position:0% contract because um optimism and base 00:10:20.360 --> 00:10:22.230 align:start position:0% contract because um optimism and base are<00:10:20.560> both<00:10:20.800> evm 00:10:22.230 --> 00:10:22.240 align:start position:0% are both evm 00:10:22.240 --> 00:10:25.110 align:start position:0% are both evm chains<00:10:23.240> I<00:10:23.399> can<00:10:23.519> use<00:10:23.680> the<00:10:23.839> same<00:10:24.079> contract<00:10:24.480> code 00:10:25.110 --> 00:10:25.120 align:start position:0% chains I can use the same contract code 00:10:25.120 --> 00:10:27.389 align:start position:0% chains I can use the same contract code and<00:10:25.760> have<00:10:25.880> it<00:10:26.079> hash<00:10:26.360> to<00:10:26.519> the<00:10:26.640> same<00:10:26.839> create<00:10:27.120> 2 00:10:27.389 --> 00:10:27.399 align:start position:0% and have it hash to the same create 2 00:10:27.399 --> 00:10:29.750 align:start position:0% and have it hash to the same create 2 address<00:10:27.680> on<00:10:27.839> both<00:10:28.040> chains<00:10:28.880> so<00:10:29.040> the<00:10:29.360> contract 00:10:29.750 --> 00:10:29.760 align:start position:0% address on both chains so the contract 00:10:29.760 --> 00:10:32.750 align:start position:0% address on both chains so the contract on<00:10:29.920> the<00:10:30.079> destination<00:10:30.560> chain<00:10:31.519> will 00:10:32.750 --> 00:10:32.760 align:start position:0% on the destination chain will 00:10:32.760 --> 00:10:36.550 align:start position:0% on the destination chain will now<00:10:33.760> approve<00:10:34.320> the<00:10:34.800> nft<00:10:35.360> contract<00:10:36.160> and<00:10:36.279> make<00:10:36.440> a 00:10:36.550 --> 00:10:36.560 align:start position:0% now approve the nft contract and make a 00:10:36.560 --> 00:10:38.389 align:start position:0% now approve the nft contract and make a call<00:10:36.760> with 00:10:38.389 --> 00:10:38.399 align:start position:0% call with 00:10:38.399 --> 00:10:41.829 align:start position:0% call with usdc<00:10:39.399> you've<00:10:39.639> just<00:10:39.760> seen<00:10:40.440> how<00:10:40.839> I<00:10:41.120> trustless 00:10:41.829 --> 00:10:41.839 align:start position:0% usdc you've just seen how I trustless 00:10:41.839 --> 00:10:45.470 align:start position:0% usdc you've just seen how I trustless sent<00:10:42.440> funds<00:10:42.959> to<00:10:43.920> an<00:10:44.120> intent<00:10:44.519> address<00:10:45.079> and<00:10:45.320> had 00:10:45.470 --> 00:10:45.480 align:start position:0% sent funds to an intent address and had 00:10:45.480 --> 00:10:48.269 align:start position:0% sent funds to an intent address and had my<00:10:45.639> intent<00:10:46.040> completed<00:10:47.040> on<00:10:47.320> the<00:10:47.639> on<00:10:47.760> a<00:10:47.959> separate 00:10:48.269 --> 00:10:48.279 align:start position:0% my intent completed on the on a separate 00:10:48.279 --> 00:10:50.190 align:start position:0% my intent completed on the on a separate chain<00:10:48.600> completely<00:10:48.959> separate<00:10:49.279> chain<00:10:49.880> fully 00:10:50.190 --> 00:10:50.200 align:start position:0% chain completely separate chain fully 00:10:50.200 --> 00:10:52.710 align:start position:0% chain completely separate chain fully trustless<00:10:50.959> fully<00:10:51.399> permissionless<00:10:52.399> anyone 00:10:52.710 --> 00:10:52.720 align:start position:0% trustless fully permissionless anyone 00:10:52.720 --> 00:10:54.829 align:start position:0% trustless fully permissionless anyone can<00:10:52.839> come<00:10:53.000> in<00:10:53.279> to<00:10:53.440> complete<00:10:53.800> this<00:10:54.279> contract 00:10:54.829 --> 00:10:54.839 align:start position:0% can come in to complete this contract 00:10:54.839 --> 00:10:57.190 align:start position:0% can come in to complete this contract call<00:10:55.839> and<00:10:55.959> your<00:10:56.079> funds<00:10:56.320> will<00:10:56.480> never<00:10:56.680> be<00:10:56.800> stuck 00:10:57.190 --> 00:10:57.200 align:start position:0% call and your funds will never be stuck 00:10:57.200 --> 00:11:00.310 align:start position:0% call and your funds will never be stuck because<00:10:57.440> you<00:10:57.639> yourself<00:10:58.040> can<00:10:58.240> complete<00:10:58.519> it 00:11:00.310 --> 00:11:00.320 align:start position:0% because you yourself can complete it 00:11:00.320 --> 00:11:03.509 align:start position:0% because you yourself can complete it what<00:11:00.440> doeses<00:11:00.639> this<00:11:00.800> enable<00:11:01.160> for<00:11:01.399> you<00:11:02.399> well<00:11:03.399> I 00:11:03.509 --> 00:11:03.519 align:start position:0% what doeses this enable for you well I 00:11:03.519 --> 00:11:05.910 align:start position:0% what doeses this enable for you well I don't<00:11:03.720> need<00:11:04.440> uh<00:11:04.680> as<00:11:04.760> a<00:11:04.920> user<00:11:05.320> I<00:11:05.399> don't<00:11:05.519> need<00:11:05.680> to 00:11:05.910 --> 00:11:05.920 align:start position:0% don't need uh as a user I don't need to 00:11:05.920 --> 00:11:08.150 align:start position:0% don't need uh as a user I don't need to have<00:11:06.240> gas<00:11:06.560> on<00:11:06.680> the<00:11:06.839> destination<00:11:07.320> chain<00:11:08.000> if 00:11:08.150 --> 00:11:08.160 align:start position:0% have gas on the destination chain if 00:11:08.160 --> 00:11:10.230 align:start position:0% have gas on the destination chain if someone<00:11:08.399> is<00:11:08.560> building<00:11:08.959> an<00:11:09.160> app<00:11:09.320> with<00:11:09.480> intent 00:11:10.230 --> 00:11:10.240 align:start position:0% someone is building an app with intent 00:11:10.240 --> 00:11:13.389 align:start position:0% someone is building an app with intent addresses<00:11:11.240> the<00:11:11.360> relayer<00:11:12.120> holds<00:11:12.720> gas<00:11:12.920> on<00:11:13.120> both 00:11:13.389 --> 00:11:13.399 align:start position:0% addresses the relayer holds gas on both 00:11:13.399 --> 00:11:16.190 align:start position:0% addresses the relayer holds gas on both chains<00:11:14.399> and<00:11:14.519> the<00:11:14.639> user<00:11:14.920> only<00:11:15.120> needs<00:11:15.399> to<00:11:15.600> hold 00:11:16.190 --> 00:11:16.200 align:start position:0% chains and the user only needs to hold 00:11:16.200 --> 00:11:18.389 align:start position:0% chains and the user only needs to hold gas<00:11:16.519> on<00:11:16.680> the<00:11:16.800> source<00:11:17.120> chain<00:11:17.959> this<00:11:18.079> is<00:11:18.200> because 00:11:18.389 --> 00:11:18.399 align:start position:0% gas on the source chain this is because 00:11:18.399 --> 00:11:20.150 align:start position:0% gas on the source chain this is because the<00:11:18.519> relayer<00:11:19.000> completes<00:11:19.399> the<00:11:19.519> contract<00:11:19.920> call 00:11:20.150 --> 00:11:20.160 align:start position:0% the relayer completes the contract call 00:11:20.160 --> 00:11:23.110 align:start position:0% the relayer completes the contract call for<00:11:20.360> you<00:11:20.560> on<00:11:20.680> the<00:11:20.839> destination 00:11:23.110 --> 00:11:23.120 align:start position:0% for you on the destination 00:11:23.120 --> 00:11:27.190 align:start position:0% for you on the destination chain<00:11:24.120> what's<00:11:24.360> next<00:11:24.600> from<00:11:25.320> here<00:11:26.320> well<00:11:26.519> cctp 00:11:27.190 --> 00:11:27.200 align:start position:0% chain what's next from here well cctp 00:11:27.200 --> 00:11:28.790 align:start position:0% chain what's next from here well cctp and<00:11:27.320> other<00:11:27.519> Bridges<00:11:28.040> often<00:11:28.320> take<00:11:28.519> a<00:11:28.639> few 00:11:28.790 --> 00:11:28.800 align:start position:0% and other Bridges often take a few 00:11:28.800 --> 00:11:31.430 align:start position:0% and other Bridges often take a few minutes<00:11:29.399> for<00:11:29.600> example<00:11:29.959> cctp<00:11:30.720> can<00:11:30.920> take<00:11:31.120> up<00:11:31.240> to 00:11:31.430 --> 00:11:31.440 align:start position:0% minutes for example cctp can take up to 00:11:31.440 --> 00:11:33.629 align:start position:0% minutes for example cctp can take up to 20<00:11:31.720> minutes<00:11:32.360> to<00:11:32.519> complete<00:11:32.839> the 00:11:33.629 --> 00:11:33.639 align:start position:0% 20 minutes to complete the 00:11:33.639 --> 00:11:36.470 align:start position:0% 20 minutes to complete the bridge<00:11:34.639> how<00:11:34.800> can<00:11:34.920> we<00:11:35.040> do<00:11:35.240> this<00:11:35.399> instantly<00:11:36.360> I 00:11:36.470 --> 00:11:36.480 align:start position:0% bridge how can we do this instantly I 00:11:36.480 --> 00:11:38.949 align:start position:0% bridge how can we do this instantly I want<00:11:36.680> to<00:11:37.040> do<00:11:37.360> something<00:11:37.600> on<00:11:37.760> another<00:11:38.040> chain 00:11:38.949 --> 00:11:38.959 align:start position:0% want to do something on another chain 00:11:38.959 --> 00:11:41.870 align:start position:0% want to do something on another chain and<00:11:39.120> have<00:11:39.240> it<00:11:39.440> instantly 00:11:41.870 --> 00:11:41.880 align:start position:0% and have it instantly 00:11:41.880 --> 00:11:44.389 align:start position:0% and have it instantly complete<00:11:42.880> here's<00:11:43.519> how<00:11:43.680> fast<00:11:43.959> finish<00:11:44.240> and 00:11:44.389 --> 00:11:44.399 align:start position:0% complete here's how fast finish and 00:11:44.399 --> 00:11:47.110 align:start position:0% complete here's how fast finish and claiming<00:11:45.279> works<00:11:46.279> on<00:11:46.399> the<00:11:46.519> source<00:11:46.760> chain<00:11:47.040> the 00:11:47.110 --> 00:11:47.120 align:start position:0% claiming works on the source chain the 00:11:47.120 --> 00:11:50.150 align:start position:0% claiming works on the source chain the flow<00:11:47.360> is<00:11:47.480> the<00:11:47.600> same<00:11:48.480> I<00:11:48.600> send<00:11:49.399> eth<00:11:49.720> to<00:11:49.920> a 00:11:50.150 --> 00:11:50.160 align:start position:0% flow is the same I send eth to a 00:11:50.160 --> 00:11:53.310 align:start position:0% flow is the same I send eth to a contract<00:11:50.839> a<00:11:50.959> relayer<00:11:51.800> comes<00:11:52.079> in<00:11:52.440> swaps<00:11:52.839> it<00:11:53.040> and 00:11:53.310 --> 00:11:53.320 align:start position:0% contract a relayer comes in swaps it and 00:11:53.320 --> 00:11:54.870 align:start position:0% contract a relayer comes in swaps it and initiates<00:11:53.680> a<00:11:53.800> bridge<00:11:54.040> for 00:11:54.870 --> 00:11:54.880 align:start position:0% initiates a bridge for 00:11:54.880 --> 00:11:57.949 align:start position:0% initiates a bridge for me<00:11:55.880> now<00:11:56.120> on<00:11:56.240> the<00:11:56.399> destination<00:11:56.920> chain<00:11:57.839> the 00:11:57.949 --> 00:11:57.959 align:start position:0% me now on the destination chain the 00:11:57.959 --> 00:12:00.230 align:start position:0% me now on the destination chain the relayer<00:11:58.600> will<00:11:59.000> as<00:11:59.240> as<00:11:59.320> soon<00:11:59.480> as<00:11:59.639> they<00:11:59.760> start 00:12:00.230 --> 00:12:00.240 align:start position:0% relayer will as as soon as they start 00:12:00.240 --> 00:12:02.750 align:start position:0% relayer will as as soon as they start that<00:12:00.360> Source<00:12:01.120> transaction<00:12:02.120> they<00:12:02.480> have<00:12:02.600> a 00:12:02.750 --> 00:12:02.760 align:start position:0% that Source transaction they have a 00:12:02.760 --> 00:12:04.990 align:start position:0% that Source transaction they have a guarantee<00:12:03.360> that<00:12:03.880> if<00:12:04.040> the<00:12:04.200> bridge<00:12:04.760> if<00:12:04.880> they 00:12:04.990 --> 00:12:05.000 align:start position:0% guarantee that if the bridge if they 00:12:05.000 --> 00:12:07.310 align:start position:0% guarantee that if the bridge if they trust<00:12:05.279> the<00:12:05.399> bridge<00:12:06.320> 20<00:12:06.600> minutes<00:12:06.880> later<00:12:07.200> the 00:12:07.310 --> 00:12:07.320 align:start position:0% trust the bridge 20 minutes later the 00:12:07.320 --> 00:12:10.350 align:start position:0% trust the bridge 20 minutes later the funds<00:12:07.560> will<00:12:07.760> arrive<00:12:08.240> so<00:12:08.399> what<00:12:08.560> they<00:12:08.639> can<00:12:08.839> do<00:12:09.600> is 00:12:10.350 --> 00:12:10.360 align:start position:0% funds will arrive so what they can do is 00:12:10.360 --> 00:12:12.350 align:start position:0% funds will arrive so what they can do is they<00:12:10.480> will<00:12:11.000> they<00:12:11.079> can<00:12:11.320> immediately<00:12:12.000> execute 00:12:12.350 --> 00:12:12.360 align:start position:0% they will they can immediately execute 00:12:12.360 --> 00:12:15.949 align:start position:0% they will they can immediately execute the<00:12:12.519> contract<00:12:12.839> call<00:12:13.040> for<00:12:13.199> me<00:12:13.920> so<00:12:14.720> they<00:12:14.880> call<00:12:15.560> um 00:12:15.949 --> 00:12:15.959 align:start position:0% the contract call for me so they call um 00:12:15.959 --> 00:12:18.389 align:start position:0% the contract call for me so they call um a<00:12:16.120> fast<00:12:16.399> finish<00:12:16.880> function<00:12:17.320> on<00:12:17.440> an<00:12:17.600> escrow 00:12:18.389 --> 00:12:18.399 align:start position:0% a fast finish function on an escrow 00:12:18.399 --> 00:12:21.230 align:start position:0% a fast finish function on an escrow contract<00:12:19.399> and<00:12:19.560> this<00:12:19.680> mins<00:12:20.040> the<00:12:20.120> nft<00:12:20.519> for<00:12:20.639> the 00:12:21.230 --> 00:12:21.240 align:start position:0% contract and this mins the nft for the 00:12:21.240 --> 00:12:24.230 align:start position:0% contract and this mins the nft for the user<00:12:22.240> what<00:12:22.399> the<00:12:22.480> escrow<00:12:22.920> contract<00:12:23.360> does<00:12:23.760> is<00:12:24.079> it 00:12:24.230 --> 00:12:24.240 align:start position:0% user what the escrow contract does is it 00:12:24.240 --> 00:12:27.350 align:start position:0% user what the escrow contract does is it tracks<00:12:24.720> who<00:12:24.959> finished<00:12:25.560> this<00:12:26.440> um<00:12:27.199> this 00:12:27.350 --> 00:12:27.360 align:start position:0% tracks who finished this um this 00:12:27.360 --> 00:12:30.069 align:start position:0% tracks who finished this um this contract<00:12:27.760> call<00:12:27.959> for<00:12:28.120> the<00:12:28.240> user 00:12:30.069 --> 00:12:30.079 align:start position:0% contract call for the user 00:12:30.079 --> 00:12:33.230 align:start position:0% contract call for the user and<00:12:30.279> then<00:12:31.079> later<00:12:31.360> when<00:12:31.480> the<00:12:31.600> bridge<00:12:32.240> completes 00:12:33.230 --> 00:12:33.240 align:start position:0% and then later when the bridge completes 00:12:33.240 --> 00:12:35.350 align:start position:0% and then later when the bridge completes instead<00:12:33.519> of<00:12:33.959> sending<00:12:34.360> that<00:12:34.519> to<00:12:34.680> the<00:12:34.839> contract 00:12:35.350 --> 00:12:35.360 align:start position:0% instead of sending that to the contract 00:12:35.360 --> 00:12:37.310 align:start position:0% instead of sending that to the contract or<00:12:35.600> to<00:12:35.760> the<00:12:35.880> user<00:12:36.600> you<00:12:36.720> send<00:12:36.920> it<00:12:37.040> to<00:12:37.199> the 00:12:37.310 --> 00:12:37.320 align:start position:0% or to the user you send it to the 00:12:37.320 --> 00:12:39.550 align:start position:0% or to the user you send it to the relayer<00:12:37.800> who<00:12:38.199> finished<00:12:38.760> the<00:12:38.920> contract<00:12:39.279> call 00:12:39.550 --> 00:12:39.560 align:start position:0% relayer who finished the contract call 00:12:39.560 --> 00:12:42.189 align:start position:0% relayer who finished the contract call on<00:12:39.720> behalf<00:12:40.000> of<00:12:40.120> the<00:12:40.440> user<00:12:41.440> so<00:12:41.720> if<00:12:41.839> you<00:12:41.959> look<00:12:42.079> at 00:12:42.189 --> 00:12:42.199 align:start position:0% on behalf of the user so if you look at 00:12:42.199 --> 00:12:44.710 align:start position:0% on behalf of the user so if you look at the<00:12:42.320> funds<00:12:42.880> of<00:12:43.120> the<00:12:43.440> relayer<00:12:44.440> on<00:12:44.600> the 00:12:44.710 --> 00:12:44.720 align:start position:0% the funds of the relayer on the 00:12:44.720 --> 00:12:46.949 align:start position:0% the funds of the relayer on the destination<00:12:45.240> chain<00:12:46.240> they<00:12:46.440> execute<00:12:46.800> the 00:12:46.949 --> 00:12:46.959 align:start position:0% destination chain they execute the 00:12:46.959 --> 00:12:49.470 align:start position:0% destination chain they execute the contract<00:12:47.320> call<00:12:48.079> they're<00:12:48.320> down<00:12:48.880> let's<00:12:49.040> say<00:12:49.320> 100 00:12:49.470 --> 00:12:49.480 align:start position:0% contract call they're down let's say 100 00:12:49.480 --> 00:12:53.189 align:start position:0% contract call they're down let's say 100 usdc<00:12:50.199> to<00:12:50.480> Mint<00:12:50.880> the<00:12:51.279> nft<00:12:52.279> and<00:12:52.440> then<00:12:52.639> 20<00:12:52.880> minutes 00:12:53.189 --> 00:12:53.199 align:start position:0% usdc to Mint the nft and then 20 minutes 00:12:53.199 --> 00:12:55.629 align:start position:0% usdc to Mint the nft and then 20 minutes later<00:12:53.440> when<00:12:53.519> the<00:12:53.639> bridge<00:12:54.320> arrives<00:12:55.320> they<00:12:55.480> get 00:12:55.629 --> 00:12:55.639 align:start position:0% later when the bridge arrives they get 00:12:55.639 --> 00:13:00.590 align:start position:0% later when the bridge arrives they get paid<00:12:55.959> back<00:12:56.360> for<00:12:56.560> that<00:12:56.800> 100<00:12:57.040> usdc<00:12:57.920> that<00:12:58.920> um 00:13:00.590 --> 00:13:00.600 align:start position:0% paid back for that 100 usdc that um 00:13:00.600 --> 00:13:03.230 align:start position:0% paid back for that 100 usdc that um they<00:13:00.839> did<00:13:01.160> they<00:13:01.320> executed<00:13:01.800> on<00:13:01.920> behalf<00:13:02.199> of<00:13:02.320> the 00:13:03.230 --> 00:13:03.240 align:start position:0% they did they executed on behalf of the 00:13:03.240 --> 00:13:06.470 align:start position:0% they did they executed on behalf of the user<00:13:04.240> so<00:13:04.399> 20<00:13:04.639> minutes<00:13:04.959> later<00:13:05.839> the<00:13:05.959> bridge 00:13:06.470 --> 00:13:06.480 align:start position:0% user so 20 minutes later the bridge 00:13:06.480 --> 00:13:09.629 align:start position:0% user so 20 minutes later the bridge completes<00:13:07.480> the<00:13:07.600> bridge<00:13:07.959> transfers<00:13:08.680> the<00:13:08.839> usdc 00:13:09.629 --> 00:13:09.639 align:start position:0% completes the bridge transfers the usdc 00:13:09.639 --> 00:13:12.949 align:start position:0% completes the bridge transfers the usdc to<00:13:10.120> in<00:13:10.600> uh<00:13:11.000> the<00:13:11.120> intent<00:13:11.560> address<00:13:12.560> and<00:13:12.680> then<00:13:12.839> now 00:13:12.949 --> 00:13:12.959 align:start position:0% to in uh the intent address and then now 00:13:12.959 --> 00:13:15.030 align:start position:0% to in uh the intent address and then now the<00:13:13.079> relayer<00:13:13.519> can<00:13:13.639> deploy<00:13:14.000> the<00:13:14.079> intent 00:13:15.030 --> 00:13:15.040 align:start position:0% the relayer can deploy the intent 00:13:15.040 --> 00:13:18.470 align:start position:0% the relayer can deploy the intent address<00:13:16.040> and<00:13:16.920> because<00:13:17.320> the<00:13:17.519> relayer<00:13:18.199> address 00:13:18.470 --> 00:13:18.480 align:start position:0% address and because the relayer address 00:13:18.480 --> 00:13:20.629 align:start position:0% address and because the relayer address is<00:13:18.800> tracked<00:13:19.360> in<00:13:19.480> the<00:13:19.600> escrow 00:13:20.629 --> 00:13:20.639 align:start position:0% is tracked in the escrow 00:13:20.639 --> 00:13:22.870 align:start position:0% is tracked in the escrow contract<00:13:21.639> the<00:13:21.760> intent<00:13:22.160> address<00:13:22.480> knows<00:13:22.720> to 00:13:22.870 --> 00:13:22.880 align:start position:0% contract the intent address knows to 00:13:22.880 --> 00:13:25.750 align:start position:0% contract the intent address knows to send<00:13:23.160> the<00:13:23.240> funds<00:13:23.720> to<00:13:24.040> the<00:13:24.160> relayer<00:13:24.720> instead<00:13:25.040> of 00:13:25.750 --> 00:13:25.760 align:start position:0% send the funds to the relayer instead of 00:13:25.760 --> 00:13:29.910 align:start position:0% send the funds to the relayer instead of the<00:13:25.880> user 00:13:29.910 --> 00:13:29.920 align:start position:0% 00:13:29.920 --> 00:13:32.269 align:start position:0% to<00:13:30.120> summarize<00:13:30.720> what<00:13:31.120> intent<00:13:31.519> addresses<00:13:32.040> does 00:13:32.269 --> 00:13:32.279 align:start position:0% to summarize what intent addresses does 00:13:32.279 --> 00:13:34.870 align:start position:0% to summarize what intent addresses does for<00:13:32.480> unifying<00:13:33.120> ethereum<00:13:34.120> it<00:13:34.240> builds<00:13:34.560> a<00:13:34.680> better 00:13:34.870 --> 00:13:34.880 align:start position:0% for unifying ethereum it builds a better 00:13:34.880 --> 00:13:37.389 align:start position:0% for unifying ethereum it builds a better user<00:13:35.279> experience<00:13:36.240> no<00:13:36.399> more<00:13:36.680> two<00:13:37.120> wallet 00:13:37.389 --> 00:13:37.399 align:start position:0% user experience no more two wallet 00:13:37.399 --> 00:13:40.030 align:start position:0% user experience no more two wallet roundtrips<00:13:38.320> only<00:13:38.519> a<00:13:38.639> single<00:13:38.920> wallet<00:13:39.240> popup 00:13:40.030 --> 00:13:40.040 align:start position:0% roundtrips only a single wallet popup 00:13:40.040 --> 00:13:41.590 align:start position:0% roundtrips only a single wallet popup you<00:13:40.160> can<00:13:40.320> pay<00:13:40.480> with<00:13:40.600> your<00:13:40.760> coinbase<00:13:41.240> account 00:13:41.590 --> 00:13:41.600 align:start position:0% you can pay with your coinbase account 00:13:41.600 --> 00:13:44.550 align:start position:0% you can pay with your coinbase account or<00:13:41.760> your<00:13:42.440> binance<00:13:43.240> and<00:13:43.399> this<00:13:43.519> enables<00:13:44.320> a 00:13:44.550 --> 00:13:44.560 align:start position:0% or your binance and this enables a 00:13:44.560 --> 00:13:46.509 align:start position:0% or your binance and this enables a larger<00:13:44.839> user<00:13:45.160> based<00:13:45.399> to<00:13:45.519> interact<00:13:45.880> with<00:13:46.000> your 00:13:46.509 --> 00:13:46.519 align:start position:0% larger user based to interact with your 00:13:46.519 --> 00:13:49.069 align:start position:0% larger user based to interact with your app<00:13:47.519> you<00:13:47.720> sponsor<00:13:48.160> gas<00:13:48.360> on<00:13:48.440> the<00:13:48.600> destination 00:13:49.069 --> 00:13:49.079 align:start position:0% app you sponsor gas on the destination 00:13:49.079 --> 00:13:52.069 align:start position:0% app you sponsor gas on the destination chain<00:13:49.720> so<00:13:50.000> your<00:13:50.160> user<00:13:50.480> no<00:13:50.639> longer<00:13:50.959> has<00:13:51.079> to<00:13:51.240> hold 00:13:52.069 --> 00:13:52.079 align:start position:0% chain so your user no longer has to hold 00:13:52.079 --> 00:13:55.590 align:start position:0% chain so your user no longer has to hold gas<00:13:52.360> on<00:13:52.639> Two<00:13:52.839> Chains<00:13:53.759> to<00:13:54.120> interact<00:13:54.560> with<00:13:54.680> your 00:13:55.590 --> 00:13:55.600 align:start position:0% gas on Two Chains to interact with your 00:13:55.600 --> 00:13:57.829 align:start position:0% gas on Two Chains to interact with your contract<00:13:56.600> better 00:13:57.829 --> 00:13:57.839 align:start position:0% contract better 00:13:57.839 --> 00:13:59.829 align:start position:0% contract better interoperability<00:13:58.839> you<00:13:59.160> user<00:13:59.399> can<00:13:59.519> pay<00:13:59.680> you 00:13:59.829 --> 00:13:59.839 align:start position:0% interoperability you user can pay you 00:13:59.839 --> 00:14:01.910 align:start position:0% interoperability you user can pay you with<00:14:00.000> any<00:14:00.199> coin<00:14:00.440> on<00:14:00.639> any<00:14:00.839> chain<00:14:01.600> and<00:14:01.759> have 00:14:01.910 --> 00:14:01.920 align:start position:0% with any coin on any chain and have 00:14:01.920 --> 00:14:03.910 align:start position:0% with any coin on any chain and have trustless<00:14:02.360> and<00:14:02.519> permissionless<00:14:03.079> guarantees 00:14:03.910 --> 00:14:03.920 align:start position:0% trustless and permissionless guarantees 00:14:03.920 --> 00:14:07.310 align:start position:0% trustless and permissionless guarantees that<00:14:04.920> the<00:14:05.160> intended<00:14:06.040> uh<00:14:06.240> intended<00:14:06.720> action 00:14:07.310 --> 00:14:07.320 align:start position:0% that the intended uh intended action 00:14:07.320 --> 00:14:09.949 align:start position:0% that the intended uh intended action they<00:14:07.560> wanted<00:14:07.839> to<00:14:08.079> execute<00:14:08.800> gets 00:14:09.949 --> 00:14:09.959 align:start position:0% they wanted to execute gets 00:14:09.959 --> 00:14:12.150 align:start position:0% they wanted to execute gets executed<00:14:10.959> funds<00:14:11.240> will<00:14:11.399> never<00:14:11.600> be<00:14:11.720> stuck 00:14:12.150 --> 00:14:12.160 align:start position:0% executed funds will never be stuck 00:14:12.160 --> 00:14:14.269 align:start position:0% executed funds will never be stuck because<00:14:12.440> the<00:14:12.519> user<00:14:12.880> can<00:14:13.199> themsel<00:14:13.800> can 00:14:14.269 --> 00:14:14.279 align:start position:0% because the user can themsel can 00:14:14.279 --> 00:14:16.189 align:start position:0% because the user can themsel can complete<00:14:14.639> the<00:14:14.800> action<00:14:15.199> if<00:14:15.320> no<00:14:15.480> relayer<00:14:15.920> comes 00:14:16.189 --> 00:14:16.199 align:start position:0% complete the action if no relayer comes 00:14:16.199 --> 00:14:18.749 align:start position:0% complete the action if no relayer comes in<00:14:16.440> and<00:14:16.639> does<00:14:16.759> it<00:14:16.880> for 00:14:18.749 --> 00:14:18.759 align:start position:0% in and does it for 00:14:18.759 --> 00:14:20.870 align:start position:0% in and does it for them<00:14:19.759> how<00:14:19.920> have<00:14:20.040> we<00:14:20.160> used<00:14:20.360> this<00:14:20.480> in<00:14:20.560> the<00:14:20.680> real 00:14:20.870 --> 00:14:20.880 align:start position:0% them how have we used this in the real 00:14:20.880 --> 00:14:23.949 align:start position:0% them how have we used this in the real world<00:14:21.240> now<00:14:22.240> one<00:14:22.399> of<00:14:22.519> our<00:14:22.680> partners<00:14:23.639> small 00:14:23.949 --> 00:14:23.959 align:start position:0% world now one of our partners small 00:14:23.959 --> 00:14:26.189 align:start position:0% world now one of our partners small brain<00:14:24.320> Games<00:14:24.720> built<00:14:25.040> this<00:14:25.279> app<00:14:25.639> called 00:14:26.189 --> 00:14:26.199 align:start position:0% brain Games built this app called 00:14:26.199 --> 00:14:28.509 align:start position:0% brain Games built this app called tomorrow<00:14:26.600> news<00:14:27.560> it's<00:14:27.680> a<00:14:27.800> prediction<00:14:28.199> Market 00:14:28.509 --> 00:14:28.519 align:start position:0% tomorrow news it's a prediction Market 00:14:28.519 --> 00:14:30.629 align:start position:0% tomorrow news it's a prediction Market that<00:14:28.639> lets<00:14:28.800> you<00:14:29.160> bet<00:14:29.480> on<00:14:29.680> tomorrow's<00:14:30.199> New<00:14:30.360> York 00:14:30.629 --> 00:14:30.639 align:start position:0% that lets you bet on tomorrow's New York 00:14:30.639 --> 00:14:32.069 align:start position:0% that lets you bet on tomorrow's New York Times 00:14:32.069 --> 00:14:32.079 align:start position:0% Times 00:14:32.079 --> 00:14:34.269 align:start position:0% Times headline<00:14:33.079> you<00:14:33.320> enter<00:14:33.639> in<00:14:33.839> what<00:14:33.920> you<00:14:34.040> think<00:14:34.160> the 00:14:34.269 --> 00:14:34.279 align:start position:0% headline you enter in what you think the 00:14:34.279 --> 00:14:36.350 align:start position:0% headline you enter in what you think the New<00:14:34.399> York<00:14:34.600> Times<00:14:34.839> headline<00:14:35.279> is<00:14:35.759> and<00:14:35.880> the<00:14:36.120> more 00:14:36.350 --> 00:14:36.360 align:start position:0% New York Times headline is and the more 00:14:36.360 --> 00:14:39.150 align:start position:0% New York Times headline is and the more accurate<00:14:36.680> it<00:14:36.839> is<00:14:37.320> the<00:14:37.440> more<00:14:37.600> you<00:14:37.720> get<00:14:37.880> paid 00:14:39.150 --> 00:14:39.160 align:start position:0% accurate it is the more you get paid 00:14:39.160 --> 00:14:42.350 align:start position:0% accurate it is the more you get paid out<00:14:40.160> however<00:14:40.480> they<00:14:40.639> only<00:14:40.959> accept 00:14:42.350 --> 00:14:42.360 align:start position:0% out however they only accept 00:14:42.360 --> 00:14:44.870 align:start position:0% out however they only accept ethereum<00:14:43.360> what<00:14:43.519> we<00:14:43.720> did<00:14:43.920> for<00:14:44.120> them<00:14:44.440> is<00:14:44.720> we 00:14:44.870 --> 00:14:44.880 align:start position:0% ethereum what we did for them is we 00:14:44.880 --> 00:14:47.670 align:start position:0% ethereum what we did for them is we built<00:14:45.360> a<00:14:45.639> a<00:14:45.880> deposit<00:14:46.240> flow<00:14:46.680> that<00:14:46.839> allows<00:14:47.199> users 00:14:47.670 --> 00:14:47.680 align:start position:0% built a a deposit flow that allows users 00:14:47.680 --> 00:14:50.949 align:start position:0% built a a deposit flow that allows users to<00:14:48.199> send<00:14:48.680> any<00:14:48.920> coin<00:14:49.199> on<00:14:49.399> any<00:14:49.639> chain<00:14:50.639> and<00:14:50.759> it 00:14:50.949 --> 00:14:50.959 align:start position:0% to send any coin on any chain and it 00:14:50.959 --> 00:14:53.110 align:start position:0% to send any coin on any chain and it automatically<00:14:51.560> Bridges<00:14:52.160> and<00:14:52.320> swaps<00:14:52.759> using 00:14:53.110 --> 00:14:53.120 align:start position:0% automatically Bridges and swaps using 00:14:53.120 --> 00:14:55.990 align:start position:0% automatically Bridges and swaps using the<00:14:53.240> intent<00:14:53.600> address<00:14:54.079> mechanism<00:14:55.079> to<00:14:55.600> deposit 00:14:55.990 --> 00:14:56.000 align:start position:0% the intent address mechanism to deposit 00:14:56.000 --> 00:14:59.670 align:start position:0% the intent address mechanism to deposit funds<00:14:56.440> into<00:14:56.920> the<00:14:57.120> app 00:14:59.670 --> 00:14:59.680 align:start position:0% funds into the app 00:14:59.680 --> 00:15:02.110 align:start position:0% funds into the app another<00:14:59.959> one<00:15:00.079> of<00:15:00.199> our<00:15:00.360> partners<00:15:01.040> is<00:15:01.519> freedom 00:15:02.110 --> 00:15:02.120 align:start position:0% another one of our partners is freedom 00:15:02.120 --> 00:15:04.389 align:start position:0% another one of our partners is freedom Factory<00:15:03.120> they're<00:15:03.320> building<00:15:03.639> an<00:15:03.800> open<00:15:04.079> source 00:15:04.389 --> 00:15:04.399 align:start position:0% Factory they're building an open source 00:15:04.399 --> 00:15:06.790 align:start position:0% Factory they're building an open source open<00:15:04.720> Hardware<00:15:05.160> Hardware<00:15:05.519> phone<00:15:06.440> Hardware 00:15:06.790 --> 00:15:06.800 align:start position:0% open Hardware Hardware phone Hardware 00:15:06.800 --> 00:15:10.230 align:start position:0% open Hardware Hardware phone Hardware wallet<00:15:07.639> that<00:15:07.759> runs<00:15:08.000> on 00:15:10.230 --> 00:15:10.240 align:start position:0% 00:15:10.240 --> 00:15:12.910 align:start position:0% ethereum<00:15:11.240> they<00:15:11.440> have<00:15:11.560> a<00:15:11.720> checkout<00:15:12.160> page<00:15:12.639> that 00:15:12.910 --> 00:15:12.920 align:start position:0% ethereum they have a checkout page that 00:15:12.920 --> 00:15:16.269 align:start position:0% ethereum they have a checkout page that only<00:15:13.360> accepts<00:15:13.880> usdc<00:15:14.480> on<00:15:14.720> base<00:15:15.680> and<00:15:15.880> what<00:15:16.040> we 00:15:16.269 --> 00:15:16.279 align:start position:0% only accepts usdc on base and what we 00:15:16.279 --> 00:15:19.710 align:start position:0% only accepts usdc on base and what we allow<00:15:16.839> enable<00:15:17.240> them<00:15:17.360> to<00:15:17.519> do<00:15:17.759> is<00:15:18.120> accept<00:15:19.120> um<00:15:19.480> any 00:15:19.710 --> 00:15:19.720 align:start position:0% allow enable them to do is accept um any 00:15:19.720 --> 00:15:21.670 align:start position:0% allow enable them to do is accept um any coin<00:15:19.959> on<00:15:20.160> any<00:15:20.360> chain<00:15:20.639> to<00:15:20.839> pay<00:15:21.000> for<00:15:21.160> their 00:15:21.670 --> 00:15:21.680 align:start position:0% coin on any chain to pay for their 00:15:21.680 --> 00:15:24.269 align:start position:0% coin on any chain to pay for their wallet<00:15:22.680> if<00:15:22.800> a<00:15:22.959> user<00:15:23.199> doesn't<00:15:23.519> have<00:15:23.720> ether<00:15:24.120> D 00:15:24.269 --> 00:15:24.279 align:start position:0% wallet if a user doesn't have ether D 00:15:24.279 --> 00:15:26.150 align:start position:0% wallet if a user doesn't have ether D gen<00:15:24.480> on<00:15:24.639> base<00:15:24.959> they<00:15:25.040> can<00:15:25.279> pay<00:15:25.560> with<00:15:26.000> their 00:15:26.150 --> 00:15:26.160 align:start position:0% gen on base they can pay with their 00:15:26.160 --> 00:15:28.509 align:start position:0% gen on base they can pay with their coins<00:15:26.399> on<00:15:26.600> optimism<00:15:27.240> their<00:15:27.440> coins<00:15:27.880> on 00:15:28.509 --> 00:15:28.519 align:start position:0% coins on optimism their coins on 00:15:28.519 --> 00:15:33.030 align:start position:0% coins on optimism their coins on ethereum<00:15:29.399> their<00:15:29.560> coins<00:15:30.040> on<00:15:30.880> um<00:15:31.319> binance<00:15:31.720> smart 00:15:33.030 --> 00:15:33.040 align:start position:0% ethereum their coins on um binance smart 00:15:33.040 --> 00:15:35.949 align:start position:0% ethereum their coins on um binance smart chain<00:15:34.040> yeah<00:15:34.160> let's<00:15:34.399> play<00:15:34.519> the<00:15:34.639> demo<00:15:35.600> um<00:15:35.880> I 00:15:35.949 --> 00:15:35.959 align:start position:0% chain yeah let's play the demo um I 00:15:35.959 --> 00:15:37.870 align:start position:0% chain yeah let's play the demo um I think<00:15:36.160> they've<00:15:36.399> got 00:15:37.870 --> 00:15:37.880 align:start position:0% think they've got 00:15:37.880 --> 00:15:41.350 align:start position:0% think they've got it<00:15:38.880> here's<00:15:39.120> a<00:15:39.399> quick<00:15:39.680> demo<00:15:40.000> of<00:15:40.199> intent 00:15:41.350 --> 00:15:41.360 align:start position:0% it here's a quick demo of intent 00:15:41.360 --> 00:15:44.269 align:start position:0% it here's a quick demo of intent addresses<00:15:42.360> so<00:15:43.040> oh<00:15:43.160> it's<00:15:43.279> got<00:15:43.440> no<00:15:43.560> audio<00:15:43.839> I'll 00:15:44.269 --> 00:15:44.279 align:start position:0% addresses so oh it's got no audio I'll 00:15:44.279 --> 00:15:47.710 align:start position:0% addresses so oh it's got no audio I'll I'll<00:15:44.399> just<00:15:44.519> narrate<00:15:44.800> it<00:15:45.519> um<00:15:45.880> so<00:15:46.880> this<00:15:47.000> is<00:15:47.639> this 00:15:47.710 --> 00:15:47.720 align:start position:0% I'll just narrate it um so this is this 00:15:47.720 --> 00:15:50.069 align:start position:0% I'll just narrate it um so this is this is<00:15:48.000> the<00:15:48.440> the<00:15:49.199> uh<00:15:49.319> like<00:15:49.440> an<00:15:49.560> example<00:15:49.880> of<00:15:49.959> an 00:15:50.069 --> 00:15:50.079 align:start position:0% is the the uh like an example of an 00:15:50.079 --> 00:15:52.189 align:start position:0% is the the uh like an example of an intent<00:15:50.399> address<00:15:50.680> in<00:15:50.839> action<00:15:51.560> so<00:15:51.959> we're<00:15:52.079> going 00:15:52.189 --> 00:15:52.199 align:start position:0% intent address in action so we're going 00:15:52.199 --> 00:15:54.870 align:start position:0% intent address in action so we're going to<00:15:52.319> click<00:15:52.560> any<00:15:53.040> crypto<00:15:53.600> this<00:15:53.720> is<00:15:53.920> actually<00:15:54.680> uh 00:15:54.870 --> 00:15:54.880 align:start position:0% to click any crypto this is actually uh 00:15:54.880 --> 00:15:58.230 align:start position:0% to click any crypto this is actually uh the<00:15:55.360> Diop<00:15:55.720> pay<00:15:56.040> model<00:15:56.720> um<00:15:56.839> this<00:15:56.959> is<00:15:57.079> our<00:15:57.319> our<00:15:58.120> uh 00:15:58.230 --> 00:15:58.240 align:start position:0% the Diop pay model um this is our our uh 00:15:58.240 --> 00:15:59.230 align:start position:0% the Diop pay model um this is our our uh what<00:15:58.319> we've<00:15:58.480> built<00:15:58.680> around<00:15:58.959> content 00:15:59.230 --> 00:15:59.240 align:start position:0% what we've built around content 00:15:59.240 --> 00:16:00.910 align:start position:0% what we've built around content addresses<00:15:59.759> shows<00:16:00.040> all<00:16:00.160> of<00:16:00.279> the<00:16:00.399> different 00:16:00.910 --> 00:16:00.920 align:start position:0% addresses shows all of the different 00:16:00.920 --> 00:16:02.829 align:start position:0% addresses shows all of the different tokens<00:16:01.920> we're<00:16:02.079> going<00:16:02.160> to<00:16:02.240> do<00:16:02.360> a<00:16:02.519> single 00:16:02.829 --> 00:16:02.839 align:start position:0% tokens we're going to do a single 00:16:02.839 --> 00:16:05.870 align:start position:0% tokens we're going to do a single transfer<00:16:03.360> in<00:16:03.680> in<00:16:04.040> one<00:16:04.279> token<00:16:04.839> oh<00:16:05.360> over<00:16:05.519> to<00:16:05.720> this 00:16:05.870 --> 00:16:05.880 align:start position:0% transfer in in one token oh over to this 00:16:05.880 --> 00:16:08.150 align:start position:0% transfer in in one token oh over to this side<00:16:06.279> okay<00:16:06.600> deal 00:16:08.150 --> 00:16:08.160 align:start position:0% side okay deal 00:16:08.160 --> 00:16:10.749 align:start position:0% side okay deal um<00:16:09.160> and<00:16:09.440> almost<00:16:09.759> immediately<00:16:10.319> you<00:16:10.399> should<00:16:10.600> see 00:16:10.749 --> 00:16:10.759 align:start position:0% um and almost immediately you should see 00:16:10.759 --> 00:16:12.790 align:start position:0% um and almost immediately you should see the<00:16:10.880> safe<00:16:11.120> payment<00:16:11.440> completed<00:16:12.360> as<00:16:12.440> soon<00:16:12.639> as 00:16:12.790 --> 00:16:12.800 align:start position:0% the safe payment completed as soon as 00:16:12.800 --> 00:16:15.550 align:start position:0% the safe payment completed as soon as that<00:16:12.920> shows<00:16:13.639> the<00:16:14.480> fast<00:16:14.759> finish<00:16:15.160> on<00:16:15.319> the 00:16:15.550 --> 00:16:15.560 align:start position:0% that shows the fast finish on the 00:16:15.560 --> 00:16:18.949 align:start position:0% that shows the fast finish on the destination<00:16:16.079> chain<00:16:16.440> has<00:16:16.600> already<00:16:16.880> cleared<00:16:17.959> um 00:16:18.949 --> 00:16:18.959 align:start position:0% destination chain has already cleared um 00:16:18.959 --> 00:16:20.829 align:start position:0% destination chain has already cleared um rollup<00:16:19.399> ethereum<00:16:19.839> is<00:16:20.000> really<00:16:20.240> fast<00:16:20.440> and<00:16:20.560> cheap 00:16:20.829 --> 00:16:20.839 align:start position:0% rollup ethereum is really fast and cheap 00:16:20.839 --> 00:16:22.150 align:start position:0% rollup ethereum is really fast and cheap now<00:16:21.000> we<00:16:21.120> have<00:16:21.279> one<00:16:21.440> cent<00:16:21.720> one<00:16:21.880> second 00:16:22.150 --> 00:16:22.160 align:start position:0% now we have one cent one second 00:16:22.160 --> 00:16:24.030 align:start position:0% now we have one cent one second transactions<00:16:22.720> really<00:16:22.959> beautiful<00:16:23.759> and<00:16:23.839> so<00:16:23.959> you 00:16:24.030 --> 00:16:24.040 align:start position:0% transactions really beautiful and so you 00:16:24.040 --> 00:16:25.829 align:start position:0% transactions really beautiful and so you can<00:16:24.160> see<00:16:24.319> this<00:16:24.440> is<00:16:24.600> already<00:16:24.839> done<00:16:25.440> and<00:16:25.560> then 00:16:25.829 --> 00:16:25.839 align:start position:0% can see this is already done and then 00:16:25.839 --> 00:16:27.910 align:start position:0% can see this is already done and then under<00:16:26.120> the<00:16:26.319> hood<00:16:26.600> 20<00:16:26.880> minutes<00:16:27.199> later<00:16:27.759> the 00:16:27.910 --> 00:16:27.920 align:start position:0% under the hood 20 minutes later the 00:16:27.920 --> 00:16:31.189 align:start position:0% under the hood 20 minutes later the relayer<00:16:28.319> will<00:16:28.480> get<00:16:28.600> paid<00:16:28.800> back<00:16:28.959> back<00:16:29.120> via 00:16:31.189 --> 00:16:31.199 align:start position:0% relayer will get paid back back via 00:16:31.199 --> 00:16:38.629 align:start position:0% relayer will get paid back back via cctp<00:16:32.199> that's<00:16:32.360> all<00:16:32.480> we've<00:16:32.680> got 00:16:38.629 --> 00:16:38.639 align:start position:0% 00:16:38.639 --> 00:16:41.430 align:start position:0% there<00:16:39.639> sweet<00:16:40.079> should<00:16:40.240> we<00:16:40.360> do<00:16:40.600> the<00:16:40.800> the 00:16:41.430 --> 00:16:41.440 align:start position:0% there sweet should we do the the 00:16:41.440 --> 00:16:45.230 align:start position:0% there sweet should we do the the bonuses<00:16:42.560> um<00:16:43.600> perfect<00:16:44.600> uh<00:16:44.720> we<00:16:44.880> have<00:16:45.000> a<00:16:45.079> few 00:16:45.230 --> 00:16:45.240 align:start position:0% bonuses um perfect uh we have a few 00:16:45.240 --> 00:16:46.309 align:start position:0% bonuses um perfect uh we have a few bonus<00:16:45.519> round<00:16:45.759> things<00:16:45.959> where<00:16:46.040> we're<00:16:46.160> going<00:16:46.240> to 00:16:46.309 --> 00:16:46.319 align:start position:0% bonus round things where we're going to 00:16:46.319 --> 00:16:48.110 align:start position:0% bonus round things where we're going to show<00:16:46.600> some<00:16:46.839> other<00:16:47.079> things<00:16:47.319> we<00:16:47.399> can<00:16:47.600> do<00:16:47.880> with 00:16:48.110 --> 00:16:48.120 align:start position:0% show some other things we can do with 00:16:48.120 --> 00:16:49.910 align:start position:0% show some other things we can do with intent<00:16:48.519> addresses<00:16:49.000> beyond<00:16:49.399> all<00:16:49.519> of<00:16:49.639> the<00:16:49.759> stuff 00:16:49.910 --> 00:16:49.920 align:start position:0% intent addresses beyond all of the stuff 00:16:49.920 --> 00:16:51.910 align:start position:0% intent addresses beyond all of the stuff we<00:16:50.040> just<00:16:50.160> showed<00:16:50.440> you<00:16:51.040> so<00:16:51.199> the<00:16:51.319> core<00:16:51.519> of<00:16:51.600> it<00:16:51.759> is 00:16:51.910 --> 00:16:51.920 align:start position:0% we just showed you so the core of it is 00:16:51.920 --> 00:16:53.550 align:start position:0% we just showed you so the core of it is like<00:16:52.360> make<00:16:52.560> an<00:16:52.759> experience<00:16:53.199> that<00:16:53.319> kind<00:16:53.440> of 00:16:53.550 --> 00:16:53.560 align:start position:0% like make an experience that kind of 00:16:53.560 --> 00:16:55.350 align:start position:0% like make an experience that kind of feels<00:16:54.000> as<00:16:54.199> nice<00:16:54.440> as<00:16:54.600> like<00:16:54.759> Apple<00:16:55.040> pay<00:16:55.240> or 00:16:55.350 --> 00:16:55.360 align:start position:0% feels as nice as like Apple pay or 00:16:55.360 --> 00:16:57.269 align:start position:0% feels as nice as like Apple pay or Google<00:16:55.639> pay<00:16:55.839> but<00:16:55.959> it<00:16:56.040> lets<00:16:56.240> you<00:16:56.399> do<00:16:56.680> anything 00:16:57.269 --> 00:16:57.279 align:start position:0% Google pay but it lets you do anything 00:16:57.279 --> 00:17:00.910 align:start position:0% Google pay but it lets you do anything on<00:16:57.480> ethereum<00:16:58.319> from<00:16:58.480> one<00:16:59.079> transfer<00:17:00.079> um<00:17:00.680> but 00:17:00.910 --> 00:17:00.920 align:start position:0% on ethereum from one transfer um but 00:17:00.920 --> 00:17:02.590 align:start position:0% on ethereum from one transfer um but what<00:17:01.000> if<00:17:01.120> you<00:17:01.240> don't<00:17:01.440> even<00:17:01.680> have<00:17:01.880> gas<00:17:02.240> on<00:17:02.399> the 00:17:02.590 --> 00:17:02.600 align:start position:0% what if you don't even have gas on the 00:17:02.600 --> 00:17:04.150 align:start position:0% what if you don't even have gas on the source<00:17:02.920> chain<00:17:03.160> we<00:17:03.279> talked<00:17:03.519> about<00:17:03.720> not<00:17:03.920> having 00:17:04.150 --> 00:17:04.160 align:start position:0% source chain we talked about not having 00:17:04.160 --> 00:17:07.069 align:start position:0% source chain we talked about not having gas<00:17:04.480> on<00:17:04.640> the<00:17:04.799> destination<00:17:05.280> chain<00:17:06.199> um<00:17:06.640> for 00:17:07.069 --> 00:17:07.079 align:start position:0% gas on the destination chain um for 00:17:07.079 --> 00:17:09.949 align:start position:0% gas on the destination chain um for assets<00:17:07.439> that<00:17:07.640> support<00:17:07.959> it<00:17:08.319> like<00:17:08.760> usdc<00:17:09.760> uh<00:17:09.880> we 00:17:09.949 --> 00:17:09.959 align:start position:0% assets that support it like usdc uh we 00:17:09.959 --> 00:17:12.470 align:start position:0% assets that support it like usdc uh we can<00:17:10.120> do<00:17:10.360> entirely<00:17:10.919> gasless<00:17:11.319> intense<00:17:11.760> this<00:17:11.959> way 00:17:12.470 --> 00:17:12.480 align:start position:0% can do entirely gasless intense this way 00:17:12.480 --> 00:17:15.069 align:start position:0% can do entirely gasless intense this way by<00:17:12.679> just<00:17:12.880> having<00:17:13.160> the<00:17:13.280> user<00:17:13.640> sign<00:17:13.880> a<00:17:14.120> message 00:17:15.069 --> 00:17:15.079 align:start position:0% by just having the user sign a message 00:17:15.079 --> 00:17:17.069 align:start position:0% by just having the user sign a message that<00:17:15.360> is<00:17:15.520> a<00:17:15.720> permit<00:17:16.120> for<00:17:16.240> example<00:17:16.480> a<00:17:16.600> usdc 00:17:17.069 --> 00:17:17.079 align:start position:0% that is a permit for example a usdc 00:17:17.079 --> 00:17:19.870 align:start position:0% that is a permit for example a usdc permit<00:17:17.839> message<00:17:18.839> um<00:17:19.160> and<00:17:19.240> then<00:17:19.360> the<00:17:19.480> relayer 00:17:19.870 --> 00:17:19.880 align:start position:0% permit message um and then the relayer 00:17:19.880 --> 00:17:23.270 align:start position:0% permit message um and then the relayer does<00:17:20.079> everything<00:17:20.760> else<00:17:21.760> then<00:17:22.480> uh<00:17:22.919> another 00:17:23.270 --> 00:17:23.280 align:start position:0% does everything else then uh another 00:17:23.280 --> 00:17:24.669 align:start position:0% does everything else then uh another interesting<00:17:23.760> place<00:17:23.959> that<00:17:24.120> we<00:17:24.199> can<00:17:24.360> go<00:17:24.520> with 00:17:24.669 --> 00:17:24.679 align:start position:0% interesting place that we can go with 00:17:24.679 --> 00:17:26.069 align:start position:0% interesting place that we can go with this 00:17:26.069 --> 00:17:26.079 align:start position:0% this 00:17:26.079 --> 00:17:29.070 align:start position:0% this so<00:17:27.079> intent<00:17:27.559> addresses<00:17:28.120> have<00:17:28.280> this<00:17:28.520> property 00:17:29.070 --> 00:17:29.080 align:start position:0% so intent addresses have this property 00:17:29.080 --> 00:17:31.789 align:start position:0% so intent addresses have this property that<00:17:29.160> they<00:17:29.240> are<00:17:29.679> ephemeral<00:17:30.679> um<00:17:31.120> so<00:17:31.400> we<00:17:31.600> create 00:17:31.789 --> 00:17:31.799 align:start position:0% that they are ephemeral um so we create 00:17:31.799 --> 00:17:33.710 align:start position:0% that they are ephemeral um so we create an<00:17:31.919> intent<00:17:32.240> address<00:17:32.720> representing<00:17:33.360> one 00:17:33.710 --> 00:17:33.720 align:start position:0% an intent address representing one 00:17:33.720 --> 00:17:35.150 align:start position:0% an intent address representing one specific<00:17:34.200> action<00:17:34.480> and<00:17:34.600> then<00:17:34.760> once<00:17:35.000> that 00:17:35.150 --> 00:17:35.160 align:start position:0% specific action and then once that 00:17:35.160 --> 00:17:36.470 align:start position:0% specific action and then once that action<00:17:35.360> is<00:17:35.520> done<00:17:35.760> that<00:17:35.919> contract<00:17:36.280> doesn't 00:17:36.470 --> 00:17:36.480 align:start position:0% action is done that contract doesn't 00:17:36.480 --> 00:17:40.789 align:start position:0% action is done that contract doesn't need<00:17:36.600> to<00:17:36.720> exist<00:17:37.360> anymore<00:17:38.400> uh<00:17:39.799> self-destruct 00:17:40.789 --> 00:17:40.799 align:start position:0% need to exist anymore uh self-destruct 00:17:40.799 --> 00:17:41.870 align:start position:0% need to exist anymore uh self-destruct some<00:17:40.919> of<00:17:41.039> you<00:17:41.120> are<00:17:41.280> probably<00:17:41.480> familiar<00:17:41.760> with 00:17:41.870 --> 00:17:41.880 align:start position:0% some of you are probably familiar with 00:17:41.880 --> 00:17:43.230 align:start position:0% some of you are probably familiar with the<00:17:41.960> history<00:17:42.280> but<00:17:42.360> it's<00:17:42.520> been<00:17:42.679> like<00:17:42.760> a<00:17:42.960> problem 00:17:43.230 --> 00:17:43.240 align:start position:0% the history but it's been like a problem 00:17:43.240 --> 00:17:47.070 align:start position:0% the history but it's been like a problem op<00:17:43.520> code<00:17:43.720> in<00:17:43.799> the<00:17:44.160> past<00:17:45.160> um<00:17:46.039> it<00:17:46.520> it<00:17:46.640> used<00:17:46.880> to 00:17:47.070 --> 00:17:47.080 align:start position:0% op code in the past um it it used to 00:17:47.080 --> 00:17:49.789 align:start position:0% op code in the past um it it used to have<00:17:47.360> a<00:17:47.600> gas<00:17:47.960> refund<00:17:48.559> associated<00:17:49.200> with<00:17:49.320> it 00:17:49.789 --> 00:17:49.799 align:start position:0% have a gas refund associated with it 00:17:49.799 --> 00:17:51.230 align:start position:0% have a gas refund associated with it that<00:17:49.960> was<00:17:50.120> deleted<00:17:50.600> because<00:17:50.760> it<00:17:50.880> caused 00:17:51.230 --> 00:17:51.240 align:start position:0% that was deleted because it caused 00:17:51.240 --> 00:17:53.710 align:start position:0% that was deleted because it caused problems<00:17:51.640> but<00:17:51.760> at<00:17:51.919> this<00:17:52.120> point<00:17:52.720> self-destruct 00:17:53.710 --> 00:17:53.720 align:start position:0% problems but at this point self-destruct 00:17:53.720 --> 00:17:56.510 align:start position:0% problems but at this point self-destruct only<00:17:54.160> exists<00:17:54.799> within<00:17:55.679> atomically<00:17:56.240> within<00:17:56.440> a 00:17:56.510 --> 00:17:56.520 align:start position:0% only exists within atomically within a 00:17:56.520 --> 00:17:58.310 align:start position:0% only exists within atomically within a single<00:17:56.799> transaction<00:17:57.559> you<00:17:57.679> can<00:17:57.880> create<00:17:58.159> a 00:17:58.310 --> 00:17:58.320 align:start position:0% single transaction you can create a 00:17:58.320 --> 00:18:00.230 align:start position:0% single transaction you can create a contract<00:17:58.640> you<00:17:58.880> can<00:17:59.000> self-destruct<00:17:59.600> it<00:17:59.799> later 00:18:00.230 --> 00:18:00.240 align:start position:0% contract you can self-destruct it later 00:18:00.240 --> 00:18:02.110 align:start position:0% contract you can self-destruct it later within<00:18:00.559> that<00:18:00.679> same<00:18:00.919> transaction<00:18:01.760> so<00:18:01.960> we 00:18:02.110 --> 00:18:02.120 align:start position:0% within that same transaction so we 00:18:02.120 --> 00:18:03.310 align:start position:0% within that same transaction so we actually<00:18:02.360> think<00:18:02.559> that<00:18:02.720> there's<00:18:02.960> no<00:18:03.080> more 00:18:03.310 --> 00:18:03.320 align:start position:0% actually think that there's no more 00:18:03.320 --> 00:18:05.789 align:start position:0% actually think that there's no more reason<00:18:03.640> to<00:18:03.880> not<00:18:04.080> have<00:18:04.240> the<00:18:04.400> refund<00:18:05.280> and<00:18:05.559> having 00:18:05.789 --> 00:18:05.799 align:start position:0% reason to not have the refund and having 00:18:05.799 --> 00:18:07.750 align:start position:0% reason to not have the refund and having the<00:18:05.960> refund<00:18:06.520> would<00:18:06.720> be<00:18:06.919> really<00:18:07.120> nice<00:18:07.320> for<00:18:07.480> use 00:18:07.750 --> 00:18:07.760 align:start position:0% the refund would be really nice for use 00:18:07.760 --> 00:18:09.029 align:start position:0% the refund would be really nice for use cases<00:18:08.080> like<00:18:08.200> this<00:18:08.320> it<00:18:08.440> would<00:18:08.559> make<00:18:08.679> intent 00:18:09.029 --> 00:18:09.039 align:start position:0% cases like this it would make intent 00:18:09.039 --> 00:18:10.789 align:start position:0% cases like this it would make intent addresses<00:18:09.400> a<00:18:09.520> bit<00:18:09.679> cheaper<00:18:10.360> and<00:18:10.480> it<00:18:10.559> would 00:18:10.789 --> 00:18:10.799 align:start position:0% addresses a bit cheaper and it would 00:18:10.799 --> 00:18:13.190 align:start position:0% addresses a bit cheaper and it would incentivize<00:18:11.799> anyone<00:18:12.120> who's<00:18:12.360> using<00:18:12.679> ephemeral 00:18:13.190 --> 00:18:13.200 align:start position:0% incentivize anyone who's using ephemeral 00:18:13.200 --> 00:18:15.870 align:start position:0% incentivize anyone who's using ephemeral addresses<00:18:14.120> like<00:18:14.360> this<00:18:14.880> to<00:18:15.080> clean<00:18:15.320> up<00:18:15.480> after 00:18:15.870 --> 00:18:15.880 align:start position:0% addresses like this to clean up after 00:18:15.880 --> 00:18:17.510 align:start position:0% addresses like this to clean up after themselves<00:18:16.159> and<00:18:16.280> not<00:18:16.440> pollute<00:18:16.720> the<00:18:16.840> state 00:18:17.510 --> 00:18:17.520 align:start position:0% themselves and not pollute the state 00:18:17.520 --> 00:18:22.310 align:start position:0% themselves and not pollute the state tree<00:18:18.520> um<00:18:18.919> and<00:18:19.080> then<00:18:19.960> lastly<00:18:20.960> uh<00:18:21.120> you<00:18:21.280> know<00:18:22.000> once 00:18:22.310 --> 00:18:22.320 align:start position:0% tree um and then lastly uh you know once 00:18:22.320 --> 00:18:25.789 align:start position:0% tree um and then lastly uh you know once this<00:18:22.440> is<00:18:23.000> more<00:18:24.000> um<00:18:24.799> once<00:18:25.000> this<00:18:25.120> idea<00:18:25.400> has<00:18:25.559> more 00:18:25.789 --> 00:18:25.799 align:start position:0% this is more um once this idea has more 00:18:25.799 --> 00:18:27.669 align:start position:0% this is more um once this idea has more mileage<00:18:26.200> on<00:18:26.320> it<00:18:26.600> and<00:18:26.760> we<00:18:26.880> know<00:18:27.039> the<00:18:27.200> common<00:18:27.440> use 00:18:27.669 --> 00:18:27.679 align:start position:0% mileage on it and we know the common use 00:18:27.679 --> 00:18:29.390 align:start position:0% mileage on it and we know the common use patterns<00:18:28.400> right<00:18:28.520> now<00:18:28.799> is<00:18:28.919> a<00:18:29.000> new<00:18:29.120> thing<00:18:29.240> it's 00:18:29.390 --> 00:18:29.400 align:start position:0% patterns right now is a new thing it's 00:18:29.400 --> 00:18:33.549 align:start position:0% patterns right now is a new thing it's exciting<00:18:30.039> once<00:18:30.280> it's<00:18:30.679> sort<00:18:30.840> of<00:18:31.720> uh<00:18:32.640> more<00:18:32.880> Lindy 00:18:33.549 --> 00:18:33.559 align:start position:0% exciting once it's sort of uh more Lindy 00:18:33.559 --> 00:18:35.590 align:start position:0% exciting once it's sort of uh more Lindy we<00:18:33.679> could<00:18:33.840> write<00:18:34.000> an<00:18:34.159> ERC<00:18:35.039> that<00:18:35.159> allows<00:18:35.400> a 00:18:35.590 --> 00:18:35.600 align:start position:0% we could write an ERC that allows a 00:18:35.600 --> 00:18:37.990 align:start position:0% we could write an ERC that allows a really<00:18:35.799> beautiful<00:18:36.200> Progressive<00:18:36.679> uux<00:18:37.679> where 00:18:37.990 --> 00:18:38.000 align:start position:0% really beautiful Progressive uux where 00:18:38.000 --> 00:18:39.909 align:start position:0% really beautiful Progressive uux where wallets<00:18:38.440> that<00:18:38.559> support<00:18:38.880> it<00:18:39.120> can<00:18:39.360> show<00:18:39.760> the 00:18:39.909 --> 00:18:39.919 align:start position:0% wallets that support it can show the 00:18:39.919 --> 00:18:42.230 align:start position:0% wallets that support it can show the intent<00:18:40.760> where<00:18:40.919> I<00:18:41.039> say<00:18:41.440> I'm<00:18:41.559> sending<00:18:42.000> you<00:18:42.120> know 00:18:42.230 --> 00:18:42.240 align:start position:0% intent where I say I'm sending you know 00:18:42.240 --> 00:18:43.270 align:start position:0% intent where I say I'm sending you know what<00:18:42.360> I'm<00:18:42.520> actually<00:18:42.760> proposing<00:18:43.080> is<00:18:43.200> a 00:18:43.270 --> 00:18:43.280 align:start position:0% what I'm actually proposing is a 00:18:43.280 --> 00:18:44.630 align:start position:0% what I'm actually proposing is a transfer<00:18:43.679> to<00:18:43.760> an<00:18:43.880> address<00:18:44.200> but<00:18:44.280> it<00:18:44.360> will<00:18:44.480> show 00:18:44.630 --> 00:18:44.640 align:start position:0% transfer to an address but it will show 00:18:44.640 --> 00:18:46.549 align:start position:0% transfer to an address but it will show you<00:18:44.880> yeah<00:18:45.000> you're<00:18:45.200> actually<00:18:45.440> sending<00:18:46.440> you 00:18:46.549 --> 00:18:46.559 align:start position:0% you yeah you're actually sending you 00:18:46.559 --> 00:18:49.710 align:start position:0% you yeah you're actually sending you know<00:18:46.880> this<00:18:47.080> much<00:18:47.760> usdc<00:18:48.400> to<00:18:48.600> vitalic<00:18:49.240> eth<00:18:49.520> over 00:18:49.710 --> 00:18:49.720 align:start position:0% know this much usdc to vitalic eth over 00:18:49.720 --> 00:18:52.669 align:start position:0% know this much usdc to vitalic eth over on<00:18:50.280> you<00:18:50.400> know<00:18:50.640> optimism<00:18:51.159> this<00:18:51.280> other<00:18:51.559> chain<00:18:52.559> um 00:18:52.669 --> 00:18:52.679 align:start position:0% on you know optimism this other chain um 00:18:52.679 --> 00:18:53.950 align:start position:0% on you know optimism this other chain um it<00:18:52.799> can<00:18:52.880> surface<00:18:53.159> that<00:18:53.280> to<00:18:53.360> you<00:18:53.480> and<00:18:53.559> then<00:18:53.720> for 00:18:53.950 --> 00:18:53.960 align:start position:0% it can surface that to you and then for 00:18:53.960 --> 00:18:55.470 align:start position:0% it can surface that to you and then for wallets<00:18:54.320> that<00:18:54.440> don't<00:18:54.640> support<00:18:54.919> it<00:18:55.080> it'll<00:18:55.320> just 00:18:55.470 --> 00:18:55.480 align:start position:0% wallets that don't support it it'll just 00:18:55.480 --> 00:18:57.750 align:start position:0% wallets that don't support it it'll just show<00:18:55.799> as<00:18:55.960> a<00:18:56.320> transfer<00:18:56.760> to<00:18:56.840> a<00:18:56.960> be<00:18:57.159> address<00:18:57.640> but 00:18:57.750 --> 00:18:57.760 align:start position:0% show as a transfer to a be address but 00:18:57.760 --> 00:18:59.990 align:start position:0% show as a transfer to a be address but it<00:18:57.840> degrades<00:18:58.200> gracefully<00:18:58.559> at<00:18:58.799> still 00:18:59.990 --> 00:19:00.000 align:start position:0% it degrades gracefully at still 00:19:00.000 --> 00:19:03.510 align:start position:0% it degrades gracefully at still works<00:19:01.320> uh<00:19:02.320> I<00:19:02.440> think<00:19:02.640> that's<00:19:02.960> just<00:19:03.120> about<00:19:03.360> all 00:19:03.510 --> 00:19:03.520 align:start position:0% works uh I think that's just about all 00:19:03.520 --> 00:19:08.510 align:start position:0% works uh I think that's just about all we've<00:19:03.799> got<00:19:04.559> let's<00:19:04.840> go<00:19:05.000> to<00:19:05.559> let's<00:19:05.720> go<00:19:05.840> to 00:19:08.510 --> 00:19:08.520 align:start position:0% 00:19:08.520 --> 00:19:11.750 align:start position:0% questions<00:19:09.520> wow<00:19:09.919> guys<00:19:10.080> you<00:19:10.240> have<00:19:10.480> 15<00:19:10.919> questions 00:19:11.750 --> 00:19:11.760 align:start position:0% questions wow guys you have 15 questions 00:19:11.760 --> 00:19:14.510 align:start position:0% questions wow guys you have 15 questions lined<00:19:12.120> up<00:19:12.640> yeah<00:19:13.200> this<00:19:13.280> is<00:19:13.400> so<00:19:13.600> interesting<00:19:14.360> so 00:19:14.510 --> 00:19:14.520 align:start position:0% lined up yeah this is so interesting so 00:19:14.520 --> 00:19:16.310 align:start position:0% lined up yeah this is so interesting so let's<00:19:14.760> start<00:19:14.960> with<00:19:15.080> the<00:19:15.200> first<00:19:15.400> one<00:19:16.080> uh<00:19:16.200> what 00:19:16.310 --> 00:19:16.320 align:start position:0% let's start with the first one uh what 00:19:16.320 --> 00:19:18.149 align:start position:0% let's start with the first one uh what is<00:19:16.440> the<00:19:16.600> incentive<00:19:17.000> for<00:19:17.200> relayer<00:19:17.640> to<00:19:17.799> deploy 00:19:18.149 --> 00:19:18.159 align:start position:0% is the incentive for relayer to deploy 00:19:18.159 --> 00:19:20.149 align:start position:0% is the incentive for relayer to deploy the<00:19:18.280> create<00:19:18.559> two<00:19:19.120> wallet<00:19:19.480> since<00:19:19.760> deploy 00:19:20.149 --> 00:19:20.159 align:start position:0% the create two wallet since deploy 00:19:20.159 --> 00:19:22.350 align:start position:0% the create two wallet since deploy contract<00:19:20.520> is<00:19:20.640> usually 00:19:22.350 --> 00:19:22.360 align:start position:0% contract is usually 00:19:22.360 --> 00:19:24.430 align:start position:0% contract is usually expensive<00:19:23.360> you<00:19:23.480> want<00:19:23.559> to<00:19:23.679> do<00:19:23.840> that<00:19:24.120> so<00:19:24.320> there 00:19:24.430 --> 00:19:24.440 align:start position:0% expensive you want to do that so there 00:19:24.440 --> 00:19:26.549 align:start position:0% expensive you want to do that so there are<00:19:24.600> two<00:19:24.760> ways<00:19:25.080> you<00:19:25.200> can<00:19:25.360> do<00:19:25.559> this<00:19:26.159> um<00:19:26.480> if 00:19:26.549 --> 00:19:26.559 align:start position:0% are two ways you can do this um if 00:19:26.559 --> 00:19:28.029 align:start position:0% are two ways you can do this um if you're<00:19:26.760> running<00:19:27.039> an<00:19:27.240> app<00:19:27.440> and<00:19:27.559> want<00:19:27.679> to<00:19:27.840> use 00:19:28.029 --> 00:19:28.039 align:start position:0% you're running an app and want to use 00:19:28.039 --> 00:19:30.270 align:start position:0% you're running an app and want to use intent<00:19:28.400> address<00:19:29.000> for<00:19:29.159> your<00:19:29.360> app<00:19:29.840> you<00:19:29.960> can<00:19:30.120> run 00:19:30.270 --> 00:19:30.280 align:start position:0% intent address for your app you can run 00:19:30.280 --> 00:19:32.669 align:start position:0% intent address for your app you can run your<00:19:30.440> own<00:19:30.640> Reay<00:19:31.440> to<00:19:31.679> provide<00:19:31.919> a<00:19:32.039> better<00:19:32.320> user 00:19:32.669 --> 00:19:32.679 align:start position:0% your own Reay to provide a better user 00:19:32.679 --> 00:19:34.990 align:start position:0% your own Reay to provide a better user experience<00:19:33.280> for<00:19:33.480> your<00:19:33.640> users<00:19:34.559> your<00:19:34.720> users 00:19:34.990 --> 00:19:35.000 align:start position:0% experience for your users your users 00:19:35.000 --> 00:19:36.710 align:start position:0% experience for your users your users won't<00:19:35.240> have<00:19:35.360> to<00:19:35.480> pay<00:19:35.720> gas<00:19:36.039> and<00:19:36.120> you<00:19:36.240> can<00:19:36.360> do 00:19:36.710 --> 00:19:36.720 align:start position:0% won't have to pay gas and you can do 00:19:36.720 --> 00:19:39.230 align:start position:0% won't have to pay gas and you can do cross-chain<00:19:37.720> um<00:19:38.159> cross-chain<00:19:38.720> actions<00:19:39.039> on 00:19:39.230 --> 00:19:39.240 align:start position:0% cross-chain um cross-chain actions on 00:19:39.240 --> 00:19:41.950 align:start position:0% cross-chain um cross-chain actions on their<00:19:39.720> behalf<00:19:40.720> another<00:19:41.039> way<00:19:41.159> you<00:19:41.320> can 00:19:41.950 --> 00:19:41.960 align:start position:0% their behalf another way you can 00:19:41.960 --> 00:19:44.870 align:start position:0% their behalf another way you can incentivize<00:19:42.559> relays<00:19:43.200> is<00:19:43.320> to<00:19:43.720> have<00:19:44.520> um<00:19:44.760> a 00:19:44.870 --> 00:19:44.880 align:start position:0% incentivize relays is to have um a 00:19:44.880 --> 00:19:48.149 align:start position:0% incentivize relays is to have um a tipping<00:19:45.280> mechanism<00:19:46.280> so<00:19:47.039> the<00:19:47.159> user<00:19:47.480> sends<00:19:47.960> some 00:19:48.149 --> 00:19:48.159 align:start position:0% tipping mechanism so the user sends some 00:19:48.159 --> 00:19:50.470 align:start position:0% tipping mechanism so the user sends some tokens<00:19:48.480> to<00:19:48.640> the<00:19:48.799> contract<00:19:49.760> and<00:19:49.919> then<00:19:50.200> you<00:19:50.320> can 00:19:50.470 --> 00:19:50.480 align:start position:0% tokens to the contract and then you can 00:19:50.480 --> 00:19:52.549 align:start position:0% tokens to the contract and then you can bake<00:19:50.720> into<00:19:50.960> the<00:19:51.120> contract<00:19:51.720> that<00:19:51.919> the<00:19:52.080> relayer 00:19:52.549 --> 00:19:52.559 align:start position:0% bake into the contract that the relayer 00:19:52.559 --> 00:19:55.230 align:start position:0% bake into the contract that the relayer collects<00:19:53.039> like<00:19:53.120> a<00:19:53.240> 3%<00:19:53.760> fee<00:19:54.400> or<00:19:54.840> however<00:19:55.080> much 00:19:55.230 --> 00:19:55.240 align:start position:0% collects like a 3% fee or however much 00:19:55.240 --> 00:19:58.270 align:start position:0% collects like a 3% fee or however much you<00:19:55.360> want<00:19:55.960> to<00:19:56.360> incentivize<00:19:57.039> relaters<00:19:57.520> to<00:19:57.720> pick 00:19:58.270 --> 00:19:58.280 align:start position:0% you want to incentivize relaters to pick 00:19:58.280 --> 00:20:00.830 align:start position:0% you want to incentivize relaters to pick pick<00:19:58.440> up<00:19:58.880> these<00:19:59.360> uh<00:19:59.520> intents<00:20:00.320> and<00:20:00.480> complete 00:20:00.830 --> 00:20:00.840 align:start position:0% pick up these uh intents and complete 00:20:00.840 --> 00:20:01.909 align:start position:0% pick up these uh intents and complete them<00:20:00.960> for<00:20:01.120> the 00:20:01.909 --> 00:20:01.919 align:start position:0% them for the 00:20:01.919 --> 00:20:04.830 align:start position:0% them for the user<00:20:02.919> yeah<00:20:03.280> another<00:20:03.520> thing<00:20:03.679> i'<00:20:03.760> would<00:20:03.919> say<00:20:04.159> is 00:20:04.830 --> 00:20:04.840 align:start position:0% user yeah another thing i' would say is 00:20:04.840 --> 00:20:06.750 align:start position:0% user yeah another thing i' would say is deploying<00:20:05.280> contracts<00:20:05.679> is<00:20:05.880> actually<00:20:06.200> not<00:20:06.559> that 00:20:06.750 --> 00:20:06.760 align:start position:0% deploying contracts is actually not that 00:20:06.760 --> 00:20:09.430 align:start position:0% deploying contracts is actually not that expensive<00:20:07.320> on<00:20:07.520> L2<00:20:08.520> um<00:20:08.760> which<00:20:08.880> is<00:20:09.080> this<00:20:09.200> system 00:20:09.430 --> 00:20:09.440 align:start position:0% expensive on L2 um which is this system 00:20:09.440 --> 00:20:11.950 align:start position:0% expensive on L2 um which is this system is<00:20:09.600> definitely<00:20:09.960> built<00:20:10.360> for<00:20:10.960> for<00:20:11.320> you<00:20:11.400> know<00:20:11.720> the 00:20:11.950 --> 00:20:11.960 align:start position:0% is definitely built for for you know the 00:20:11.960 --> 00:20:15.190 align:start position:0% is definitely built for for you know the the<00:20:12.120> the<00:20:12.200> rollup<00:20:12.880> Universe<00:20:13.880> um<00:20:14.720> one<00:20:14.960> nice 00:20:15.190 --> 00:20:15.200 align:start position:0% the the rollup Universe um one nice 00:20:15.200 --> 00:20:17.270 align:start position:0% the the rollup Universe um one nice thing<00:20:15.480> there<00:20:15.799> is<00:20:16.000> that<00:20:16.360> these<00:20:16.600> contracts<00:20:17.039> are 00:20:17.270 --> 00:20:17.280 align:start position:0% thing there is that these contracts are 00:20:17.280 --> 00:20:20.390 align:start position:0% thing there is that these contracts are very<00:20:17.600> small<00:20:18.600> because<00:20:19.480> uh<00:20:19.600> we're<00:20:19.799> doing<00:20:20.280> you 00:20:20.390 --> 00:20:20.400 align:start position:0% very small because uh we're doing you 00:20:20.400 --> 00:20:23.390 align:start position:0% very small because uh we're doing you know<00:20:20.640> like<00:20:20.919> minimalist<00:20:21.679> proxy<00:20:22.400> you<00:20:22.520> know<00:20:23.080> uh 00:20:23.390 --> 00:20:23.400 align:start position:0% know like minimalist proxy you know uh 00:20:23.400 --> 00:20:25.070 align:start position:0% know like minimalist proxy you know uh uh<00:20:23.559> contracts<00:20:24.120> that<00:20:24.320> point<00:20:24.600> to<00:20:24.840> like<00:20:24.960> a 00:20:25.070 --> 00:20:25.080 align:start position:0% uh contracts that point to like a 00:20:25.080 --> 00:20:27.470 align:start position:0% uh contracts that point to like a mutable<00:20:25.440> implementation<00:20:26.080> contract<00:20:26.840> and<00:20:27.280> they 00:20:27.470 --> 00:20:27.480 align:start position:0% mutable implementation contract and they 00:20:27.480 --> 00:20:29.270 align:start position:0% mutable implementation contract and they just<00:20:27.679> have<00:20:27.880> Constructor<00:20:28.360> ARG<00:20:28.640> ments<00:20:29.080> that 00:20:29.270 --> 00:20:29.280 align:start position:0% just have Constructor ARG ments that 00:20:29.280 --> 00:20:31.390 align:start position:0% just have Constructor ARG ments that basically<00:20:29.760> encode<00:20:30.159> the<00:20:30.280> parameters<00:20:30.880> of<00:20:31.120> the 00:20:31.390 --> 00:20:31.400 align:start position:0% basically encode the parameters of the 00:20:31.400 --> 00:20:32.789 align:start position:0% basically encode the parameters of the action<00:20:31.679> of<00:20:31.799> the<00:20:31.919> transfer<00:20:32.360> the<00:20:32.440> payment 00:20:32.789 --> 00:20:32.799 align:start position:0% action of the transfer the payment 00:20:32.799 --> 00:20:35.470 align:start position:0% action of the transfer the payment whatever<00:20:33.080> it<00:20:33.200> is<00:20:34.120> and<00:20:34.280> so<00:20:34.760> the<00:20:35.000> size<00:20:35.240> of 00:20:35.470 --> 00:20:35.480 align:start position:0% whatever it is and so the size of 00:20:35.480 --> 00:20:36.830 align:start position:0% whatever it is and so the size of contract<00:20:35.880> code<00:20:36.120> that<00:20:36.200> you're<00:20:36.320> deploying<00:20:36.720> for 00:20:36.830 --> 00:20:36.840 align:start position:0% contract code that you're deploying for 00:20:36.840 --> 00:20:38.630 align:start position:0% contract code that you're deploying for one<00:20:36.919> of<00:20:37.039> these<00:20:37.159> intent<00:20:37.520> addresses<00:20:37.919> is<00:20:38.080> fairly 00:20:38.630 --> 00:20:38.640 align:start position:0% one of these intent addresses is fairly 00:20:38.640 --> 00:20:41.789 align:start position:0% one of these intent addresses is fairly small<00:20:39.720> um<00:20:40.720> I'll<00:20:40.919> answer<00:20:41.200> this<00:20:41.440> next<00:20:41.640> one 00:20:41.789 --> 00:20:41.799 align:start position:0% small um I'll answer this next one 00:20:41.799 --> 00:20:43.750 align:start position:0% small um I'll answer this next one because<00:20:41.960> it's<00:20:42.120> closely<00:20:42.440> related<00:20:43.080> do<00:20:43.360> intent 00:20:43.750 --> 00:20:43.760 align:start position:0% because it's closely related do intent 00:20:43.760 --> 00:20:45.909 align:start position:0% because it's closely related do intent addresses<00:20:44.240> lead<00:20:44.520> to<00:20:44.799> increased<00:20:45.280> chain<00:20:45.640> State 00:20:45.909 --> 00:20:45.919 align:start position:0% addresses lead to increased chain State 00:20:45.919 --> 00:20:49.070 align:start position:0% addresses lead to increased chain State bloat<00:20:46.600> this<00:20:46.679> is<00:20:46.880> why<00:20:47.000> we<00:20:47.120> would<00:20:47.320> like<00:20:47.600> the<00:20:48.200> self 00:20:49.070 --> 00:20:49.080 align:start position:0% bloat this is why we would like the self 00:20:49.080 --> 00:20:53.230 align:start position:0% bloat this is why we would like the self self-destruct<00:20:49.880> refund<00:20:50.320> back<00:20:51.240> um<00:20:51.760> we<00:20:52.320> actually 00:20:53.230 --> 00:20:53.240 align:start position:0% self-destruct refund back um we actually 00:20:53.240 --> 00:20:55.830 align:start position:0% self-destruct refund back um we actually run<00:20:53.799> our<00:20:54.120> intent<00:20:54.520> addresses<00:20:55.039> currently 00:20:55.830 --> 00:20:55.840 align:start position:0% run our intent addresses currently 00:20:55.840 --> 00:20:57.390 align:start position:0% run our intent addresses currently without<00:20:56.400> chain<00:20:56.720> State<00:20:56.960> bloat<00:20:57.280> with 00:20:57.390 --> 00:20:57.400 align:start position:0% without chain State bloat with 00:20:57.400 --> 00:20:59.230 align:start position:0% without chain State bloat with self-destruct<00:20:58.080> at<00:20:58.200> the<00:20:58.280> end 00:20:59.230 --> 00:20:59.240 align:start position:0% self-destruct at the end 00:20:59.240 --> 00:21:00.950 align:start position:0% self-destruct at the end uh<00:20:59.520> but<00:20:59.640> there's<00:20:59.840> currently<00:21:00.200> no<00:21:00.400> incentive<00:21:00.799> to 00:21:00.950 --> 00:21:00.960 align:start position:0% uh but there's currently no incentive to 00:21:00.960 --> 00:21:03.430 align:start position:0% uh but there's currently no incentive to do<00:21:01.200> that<00:21:01.600> you<00:21:01.720> don't<00:21:02.039> actually<00:21:02.679> gain<00:21:03.080> anything 00:21:03.430 --> 00:21:03.440 align:start position:0% do that you don't actually gain anything 00:21:03.440 --> 00:21:06.310 align:start position:0% do that you don't actually gain anything from<00:21:03.600> it<00:21:04.159> um<00:21:04.720> and<00:21:04.880> so<00:21:05.400> having<00:21:05.640> that<00:21:05.840> also<00:21:06.080> come 00:21:06.310 --> 00:21:06.320 align:start position:0% from it um and so having that also come 00:21:06.320 --> 00:21:08.630 align:start position:0% from it um and so having that also come with<00:21:06.480> like<00:21:06.720> a<00:21:07.080> b<00:21:07.280> effectively<00:21:07.840> like<00:21:08.080> a<00:21:08.280> gas 00:21:08.630 --> 00:21:08.640 align:start position:0% with like a b effectively like a gas 00:21:08.640 --> 00:21:10.350 align:start position:0% with like a b effectively like a gas discount<00:21:09.080> for<00:21:09.240> cleaning<00:21:09.559> up<00:21:09.720> after<00:21:09.960> yourself 00:21:10.350 --> 00:21:10.360 align:start position:0% discount for cleaning up after yourself 00:21:10.360 --> 00:21:11.470 align:start position:0% discount for cleaning up after yourself would<00:21:10.480> be 00:21:11.470 --> 00:21:11.480 align:start position:0% would be 00:21:11.480 --> 00:21:14.190 align:start position:0% would be great<00:21:12.480> okay<00:21:12.840> next<00:21:13.039> question<00:21:13.320> is<00:21:13.640> if<00:21:13.799> multiple 00:21:14.190 --> 00:21:14.200 align:start position:0% great okay next question is if multiple 00:21:14.200 --> 00:21:16.269 align:start position:0% great okay next question is if multiple people<00:21:14.559> transfer<00:21:15.000> tokens<00:21:15.400> to<00:21:15.559> an<00:21:15.880> intent 00:21:16.269 --> 00:21:16.279 align:start position:0% people transfer tokens to an intent 00:21:16.279 --> 00:21:18.750 align:start position:0% people transfer tokens to an intent address<00:21:16.919> uh<00:21:17.120> how<00:21:17.360> can<00:21:17.559> the<00:21:17.720> contract<00:21:18.159> know<00:21:18.559> who 00:21:18.750 --> 00:21:18.760 align:start position:0% address uh how can the contract know who 00:21:18.760 --> 00:21:21.990 align:start position:0% address uh how can the contract know who sent<00:21:19.200> what<00:21:19.799> and<00:21:20.360> in<00:21:20.559> order<00:21:20.960> to<00:21:21.200> reward<00:21:21.640> them 00:21:21.990 --> 00:21:22.000 align:start position:0% sent what and in order to reward them 00:21:22.000 --> 00:21:23.510 align:start position:0% sent what and in order to reward them separately 00:21:23.510 --> 00:21:23.520 align:start position:0% separately 00:21:23.520 --> 00:21:26.230 align:start position:0% separately totally<00:21:24.520> so<00:21:24.720> the<00:21:24.880> intended<00:21:25.360> way<00:21:25.600> an<00:21:25.760> intent 00:21:26.230 --> 00:21:26.240 align:start position:0% totally so the intended way an intent 00:21:26.240 --> 00:21:29.549 align:start position:0% totally so the intended way an intent address<00:21:26.960> is<00:21:27.200> to<00:21:27.360> be<00:21:27.520> used<00:21:28.000> is<00:21:28.840> um<00:21:28.960> you<00:21:29.120> generate 00:21:29.549 --> 00:21:29.559 align:start position:0% address is to be used is um you generate 00:21:29.559 --> 00:21:32.390 align:start position:0% address is to be used is um you generate like<00:21:29.679> an<00:21:29.799> intent<00:21:30.240> address<00:21:30.720> per<00:21:30.960> user<00:21:31.799> or<00:21:32.039> per 00:21:32.390 --> 00:21:32.400 align:start position:0% like an intent address per user or per 00:21:32.400 --> 00:21:34.909 align:start position:0% like an intent address per user or per interaction<00:21:33.400> and<00:21:33.600> this<00:21:33.799> way<00:21:34.200> you<00:21:34.360> know<00:21:34.720> like 00:21:34.909 --> 00:21:34.919 align:start position:0% interaction and this way you know like 00:21:34.919 --> 00:21:37.750 align:start position:0% interaction and this way you know like which<00:21:35.120> user<00:21:35.559> is<00:21:35.799> going<00:21:36.039> to<00:21:36.919> send<00:21:37.279> tokens<00:21:37.600> to 00:21:37.750 --> 00:21:37.760 align:start position:0% which user is going to send tokens to 00:21:37.760 --> 00:21:40.350 align:start position:0% which user is going to send tokens to the<00:21:37.919> contract<00:21:38.799> and<00:21:39.120> if<00:21:39.320> other<00:21:39.559> people<00:21:39.760> send<00:21:40.080> it 00:21:40.350 --> 00:21:40.360 align:start position:0% the contract and if other people send it 00:21:40.360 --> 00:21:43.669 align:start position:0% the contract and if other people send it it<00:21:40.760> could<00:21:40.919> be<00:21:41.120> like<00:21:41.279> funding<00:21:42.039> for<00:21:43.039> U<00:21:43.200> the<00:21:43.279> user 00:21:43.669 --> 00:21:43.679 align:start position:0% it could be like funding for U the user 00:21:43.679 --> 00:21:46.789 align:start position:0% it could be like funding for U the user so<00:21:43.840> for<00:21:44.039> example<00:21:44.400> with<00:21:44.559> the<00:21:44.720> nft<00:21:45.600> example<00:21:46.600> for 00:21:46.789 --> 00:21:46.799 align:start position:0% so for example with the nft example for 00:21:46.799 --> 00:21:48.510 align:start position:0% so for example with the nft example for each<00:21:47.000> user<00:21:47.279> that<00:21:47.400> wants<00:21:47.600> to<00:21:47.720> Mint<00:21:47.919> the<00:21:48.039> nft<00:21:48.400> in 00:21:48.510 --> 00:21:48.520 align:start position:0% each user that wants to Mint the nft in 00:21:48.520 --> 00:21:50.350 align:start position:0% each user that wants to Mint the nft in your<00:21:48.679> app<00:21:48.960> you<00:21:49.080> could<00:21:49.279> generate<00:21:49.600> a<00:21:49.720> new<00:21:49.919> intent 00:21:50.350 --> 00:21:50.360 align:start position:0% your app you could generate a new intent 00:21:50.360 --> 00:21:53.149 align:start position:0% your app you could generate a new intent address<00:21:50.919> specifying<00:21:51.520> them<00:21:51.720> as<00:21:51.840> the<00:21:52.159> recipient 00:21:53.149 --> 00:21:53.159 align:start position:0% address specifying them as the recipient 00:21:53.159 --> 00:21:56.070 align:start position:0% address specifying them as the recipient and<00:21:53.720> then<00:21:54.720> you<00:21:54.840> could<00:21:55.039> also<00:21:55.440> for<00:21:55.600> example 00:21:56.070 --> 00:21:56.080 align:start position:0% and then you could also for example 00:21:56.080 --> 00:21:57.950 align:start position:0% and then you could also for example purchase<00:21:56.400> a<00:21:56.559> gift<00:21:56.760> for<00:21:56.960> your<00:21:57.120> friend<00:21:57.520> and 00:21:57.950 --> 00:21:57.960 align:start position:0% purchase a gift for your friend and 00:21:57.960 --> 00:21:59.549 align:start position:0% purchase a gift for your friend and transfer<00:21:58.400> to<00:21:58.600> tokens<00:21:58.880> to<00:21:59.039> that<00:21:59.159> intent 00:21:59.549 --> 00:21:59.559 align:start position:0% transfer to tokens to that intent 00:21:59.559 --> 00:22:01.470 align:start position:0% transfer to tokens to that intent address<00:22:00.000> but<00:22:00.400> the<00:22:00.559> intended<00:22:00.919> way<00:22:01.039> it's<00:22:01.240> to<00:22:01.360> be 00:22:01.470 --> 00:22:01.480 align:start position:0% address but the intended way it's to be 00:22:01.480 --> 00:22:05.230 align:start position:0% address but the intended way it's to be used<00:22:01.919> is<00:22:02.919> once<00:22:03.279> per<00:22:03.760> interaction<00:22:04.440> per<00:22:04.640> user 00:22:05.230 --> 00:22:05.240 align:start position:0% used is once per interaction per user 00:22:05.240 --> 00:22:07.710 align:start position:0% used is once per interaction per user totally<00:22:06.120> and<00:22:06.279> that<00:22:06.480> said<00:22:06.840> it<00:22:07.039> does<00:22:07.279> support 00:22:07.710 --> 00:22:07.720 align:start position:0% totally and that said it does support 00:22:07.720 --> 00:22:09.990 align:start position:0% totally and that said it does support multiple<00:22:08.559> assets<00:22:08.919> going<00:22:09.120> in<00:22:09.520> so<00:22:09.679> you<00:22:09.760> can<00:22:09.880> do 00:22:09.990 --> 00:22:10.000 align:start position:0% multiple assets going in so you can do 00:22:10.000 --> 00:22:11.789 align:start position:0% multiple assets going in so you can do this<00:22:10.159> very<00:22:10.320> nice<00:22:10.480> thing<00:22:10.679> let's<00:22:10.840> say<00:22:11.000> I<00:22:11.080> want<00:22:11.159> to 00:22:11.789 --> 00:22:11.799 align:start position:0% this very nice thing let's say I want to 00:22:11.799 --> 00:22:14.630 align:start position:0% this very nice thing let's say I want to do<00:22:12.000> an<00:22:12.240> action<00:22:12.640> that<00:22:13.039> takes<00:22:13.360> $100<00:22:14.279> I<00:22:14.360> want<00:22:14.480> to 00:22:14.630 --> 00:22:14.640 align:start position:0% do an action that takes $100 I want to 00:22:14.640 --> 00:22:17.710 align:start position:0% do an action that takes $100 I want to place<00:22:14.799> a<00:22:14.919> poly<00:22:15.159> Market<00:22:15.440> bet<00:22:16.440> I<00:22:16.520> can<00:22:16.799> send<00:22:17.559> you 00:22:17.710 --> 00:22:17.720 align:start position:0% place a poly Market bet I can send you 00:22:17.720 --> 00:22:20.750 align:start position:0% place a poly Market bet I can send you know<00:22:17.919> $50<00:22:18.720> vers<00:22:19.200> worth<00:22:19.360> of<00:22:19.480> token<00:22:19.799> a<00:22:20.000> and<00:22:20.120> $50 00:22:20.750 --> 00:22:20.760 align:start position:0% know $50 vers worth of token a and $50 00:22:20.760 --> 00:22:22.750 align:start position:0% know $50 vers worth of token a and $50 worth<00:22:20.960> of<00:22:21.080> token<00:22:21.400> B<00:22:21.799> to<00:22:21.960> an<00:22:22.080> intent<00:22:22.400> address 00:22:22.750 --> 00:22:22.760 align:start position:0% worth of token B to an intent address 00:22:22.760 --> 00:22:25.510 align:start position:0% worth of token B to an intent address over<00:22:22.960> here<00:22:23.159> on<00:22:23.400> on<00:22:23.559> Bas<00:22:23.880> for<00:22:24.039> example<00:22:25.000> and<00:22:25.320> any 00:22:25.510 --> 00:22:25.520 align:start position:0% over here on on Bas for example and any 00:22:25.520 --> 00:22:28.110 align:start position:0% over here on on Bas for example and any realer<00:22:26.000> can<00:22:26.120> come<00:22:26.320> in<00:22:27.159> you<00:22:27.279> know<00:22:27.520> swap<00:22:27.840> those 00:22:28.110 --> 00:22:28.120 align:start position:0% realer can come in you know swap those 00:22:28.120 --> 00:22:28.990 align:start position:0% realer can come in you know swap those however<00:22:28.240> it<00:22:28.360> needs<00:22:28.520> needs<00:22:28.679> the<00:22:28.760> intent 00:22:28.990 --> 00:22:29.000 align:start position:0% however it needs needs the intent 00:22:29.000 --> 00:22:30.710 align:start position:0% however it needs needs the intent address<00:22:29.240> is<00:22:29.360> just<00:22:29.480> going<00:22:29.600> to<00:22:29.799> guarantee<00:22:30.559> that 00:22:30.710 --> 00:22:30.720 align:start position:0% address is just going to guarantee that 00:22:30.720 --> 00:22:33.789 align:start position:0% address is just going to guarantee that like<00:22:30.880> whatever<00:22:31.240> they<00:22:31.440> do<00:22:32.159> $100<00:22:32.919> of<00:22:33.080> usdc<00:22:33.679> have 00:22:33.789 --> 00:22:33.799 align:start position:0% like whatever they do $100 of usdc have 00:22:33.799 --> 00:22:36.029 align:start position:0% like whatever they do $100 of usdc have to<00:22:33.960> go<00:22:34.120> into<00:22:34.320> the<00:22:34.440> bridge<00:22:35.320> and<00:22:35.480> then<00:22:35.799> fast 00:22:36.029 --> 00:22:36.039 align:start position:0% to go into the bridge and then fast 00:22:36.039 --> 00:22:37.430 align:start position:0% to go into the bridge and then fast finish<00:22:36.279> it<00:22:36.400> on<00:22:36.559> the<00:22:36.679> other 00:22:37.430 --> 00:22:37.440 align:start position:0% finish it on the other 00:22:37.440 --> 00:22:39.870 align:start position:0% finish it on the other side<00:22:38.440> so<00:22:38.600> you<00:22:38.679> can<00:22:38.799> do<00:22:38.919> multi<00:22:39.279> payments<00:22:39.679> but 00:22:39.870 --> 00:22:39.880 align:start position:0% side so you can do multi payments but 00:22:39.880 --> 00:22:42.070 align:start position:0% side so you can do multi payments but yeah<00:22:40.080> it's<00:22:40.320> it's<00:22:40.480> not<00:22:41.480> there<00:22:41.640> there's<00:22:41.960> they're 00:22:42.070 --> 00:22:42.080 align:start position:0% yeah it's it's not there there's they're 00:22:42.080 --> 00:22:47.110 align:start position:0% yeah it's it's not there there's they're one<00:22:42.279> per<00:22:42.960> action<00:22:43.960> okay<00:22:44.360> next<00:22:44.799> question<00:22:45.400> is<00:22:46.400> uh 00:22:47.110 --> 00:22:47.120 align:start position:0% one per action okay next question is uh 00:22:47.120 --> 00:22:49.190 align:start position:0% one per action okay next question is uh do<00:22:47.400> these<00:22:47.600> intent<00:22:48.039> addresses<00:22:48.520> look<00:22:48.799> like 00:22:49.190 --> 00:22:49.200 align:start position:0% do these intent addresses look like 00:22:49.200 --> 00:22:53.190 align:start position:0% do these intent addresses look like accounts<00:22:49.520> on<00:22:49.679> a<00:22:49.799> salana<00:22:50.279> except<00:22:50.520> for<00:22:50.640> the 00:22:53.190 --> 00:22:53.200 align:start position:0% 00:22:53.200 --> 00:22:55.590 align:start position:0% relayer<00:22:54.200> the<00:22:54.320> taker<00:22:54.559> is<00:22:54.720> eth<00:22:55.039> I<00:22:55.279> I<00:22:55.360> don't<00:22:55.480> know 00:22:55.590 --> 00:22:55.600 align:start position:0% relayer the taker is eth I I don't know 00:22:55.600 --> 00:22:58.909 align:start position:0% relayer the taker is eth I I don't know about<00:22:55.840> that<00:22:56.679> okay<00:22:57.679> um<00:22:57.960> how<00:22:58.080> much<00:22:58.679> would<00:22:58.799> it 00:22:58.909 --> 00:22:58.919 align:start position:0% about that okay um how much would it 00:22:58.919 --> 00:23:01.630 align:start position:0% about that okay um how much would it cost<00:22:59.120> to<00:22:59.240> incur<00:22:59.600> the<00:22:59.799> trigger<00:23:00.799> uh<00:23:01.039> to<00:23:01.279> to<00:23:01.400> start 00:23:01.630 --> 00:23:01.640 align:start position:0% cost to incur the trigger uh to to start 00:23:01.640 --> 00:23:04.870 align:start position:0% cost to incur the trigger uh to to start to<00:23:01.799> trigger<00:23:02.200> the<00:23:02.520> the<00:23:02.799> action<00:23:03.240> on<00:23:04.039> um<00:23:04.480> intent 00:23:04.870 --> 00:23:04.880 align:start position:0% to trigger the the action on um intent 00:23:04.880 --> 00:23:08.950 align:start position:0% to trigger the the action on um intent address<00:23:05.360> assum<00:23:05.720> it's<00:23:05.919> just<00:23:06.159> ear<00:23:06.480> C20 00:23:08.950 --> 00:23:08.960 align:start position:0% address assum it's just ear C20 00:23:08.960 --> 00:23:12.909 align:start position:0% address assum it's just ear C20 transfer<00:23:09.960> so<00:23:10.279> in<00:23:10.440> our<00:23:11.080> experience<00:23:12.080> uh<00:23:12.720> in 00:23:12.909 --> 00:23:12.919 align:start position:0% transfer so in our experience uh in 00:23:12.919 --> 00:23:16.669 align:start position:0% transfer so in our experience uh in particular<00:23:13.360> on<00:23:13.919> l2s<00:23:14.919> it's<00:23:15.240> really<00:23:15.480> cheap<00:23:15.880> to 00:23:16.669 --> 00:23:16.679 align:start position:0% particular on l2s it's really cheap to 00:23:16.679 --> 00:23:19.110 align:start position:0% particular on l2s it's really cheap to use<00:23:16.919> this<00:23:17.120> intent<00:23:17.600> contract<00:23:18.080> mechanism<00:23:18.919> so 00:23:19.110 --> 00:23:19.120 align:start position:0% use this intent contract mechanism so 00:23:19.120 --> 00:23:21.710 align:start position:0% use this intent contract mechanism so for<00:23:19.360> an<00:23:19.919> the<00:23:20.080> gas<00:23:20.360> cost<00:23:20.600> you<00:23:20.799> pay<00:23:21.000> as<00:23:21.120> a<00:23:21.200> relayer 00:23:21.710 --> 00:23:21.720 align:start position:0% for an the gas cost you pay as a relayer 00:23:21.720 --> 00:23:23.950 align:start position:0% for an the gas cost you pay as a relayer is<00:23:22.000> the<00:23:22.159> cost<00:23:22.360> to<00:23:22.559> deploy<00:23:22.880> the<00:23:23.000> contract<00:23:23.840> and 00:23:23.950 --> 00:23:23.960 align:start position:0% is the cost to deploy the contract and 00:23:23.960 --> 00:23:25.830 align:start position:0% is the cost to deploy the contract and then<00:23:24.120> the<00:23:24.279> cost<00:23:24.559> to<00:23:24.919> execute<00:23:25.279> the<00:23:25.400> function<00:23:25.679> on 00:23:25.830 --> 00:23:25.840 align:start position:0% then the cost to execute the function on 00:23:25.840 --> 00:23:29.470 align:start position:0% then the cost to execute the function on the<00:23:25.960> contract<00:23:26.919> so<00:23:27.159> for<00:23:27.760> in<00:23:28.679> 20<00:23:28.919> transfer 00:23:29.470 --> 00:23:29.480 align:start position:0% the contract so for in 20 transfer 00:23:29.480 --> 00:23:31.470 align:start position:0% the contract so for in 20 transfer that's<00:23:29.799> like<00:23:30.080> much<00:23:30.320> less<00:23:30.480> than<00:23:30.600> a<00:23:30.760> Cent<00:23:31.360> and 00:23:31.470 --> 00:23:31.480 align:start position:0% that's like much less than a Cent and 00:23:31.480 --> 00:23:33.590 align:start position:0% that's like much less than a Cent and the<00:23:31.640> cost<00:23:31.840> of<00:23:32.039> deploying<00:23:32.559> the<00:23:32.720> contract<00:23:33.440> is 00:23:33.590 --> 00:23:33.600 align:start position:0% the cost of deploying the contract is 00:23:33.600 --> 00:23:35.950 align:start position:0% the cost of deploying the contract is also<00:23:33.880> less<00:23:34.039> than<00:23:34.200> a<00:23:34.320> cent<00:23:35.200> so<00:23:35.600> in<00:23:35.720> our 00:23:35.950 --> 00:23:35.960 align:start position:0% also less than a cent so in our 00:23:35.960 --> 00:23:38.430 align:start position:0% also less than a cent so in our experience<00:23:36.559> on<00:23:36.720> l2s<00:23:37.360> it's<00:23:37.520> been<00:23:37.960> less<00:23:38.159> than<00:23:38.279> an 00:23:38.430 --> 00:23:38.440 align:start position:0% experience on l2s it's been less than an 00:23:38.440 --> 00:23:42.110 align:start position:0% experience on l2s it's been less than an incent<00:23:39.279> to<00:23:39.520> use<00:23:40.240> uh<00:23:40.400> intent 00:23:42.110 --> 00:23:42.120 align:start position:0% incent to use uh intent 00:23:42.120 --> 00:23:44.510 align:start position:0% incent to use uh intent addresses<00:23:43.120> totally<00:23:43.840> this<00:23:43.919> is<00:23:44.039> connected<00:23:44.400> to 00:23:44.510 --> 00:23:44.520 align:start position:0% addresses totally this is connected to 00:23:44.520 --> 00:23:46.230 align:start position:0% addresses totally this is connected to the<00:23:44.640> next<00:23:44.880> question<00:23:45.200> which<00:23:45.320> is<00:23:45.799> uh<00:23:45.960> what<00:23:46.080> is 00:23:46.230 --> 00:23:46.240 align:start position:0% the next question which is uh what is 00:23:46.240 --> 00:23:48.070 align:start position:0% the next question which is uh what is the<00:23:46.400> additional<00:23:46.880> cost<00:23:47.080> of<00:23:47.279> deploying 00:23:48.070 --> 00:23:48.080 align:start position:0% the additional cost of deploying 00:23:48.080 --> 00:23:49.950 align:start position:0% the additional cost of deploying contract<00:23:48.480> code<00:23:48.799> for<00:23:49.080> every 00:23:49.950 --> 00:23:49.960 align:start position:0% contract code for every 00:23:49.960 --> 00:23:51.830 align:start position:0% contract code for every transaction<00:23:50.960> um<00:23:51.200> yeah<00:23:51.400> actually<00:23:51.600> I<00:23:51.640> have<00:23:51.760> a 00:23:51.830 --> 00:23:51.840 align:start position:0% transaction um yeah actually I have a 00:23:51.840 --> 00:23:54.870 align:start position:0% transaction um yeah actually I have a two-part<00:23:52.200> answer<00:23:52.400> to<00:23:52.640> this<00:23:53.000> so<00:23:54.000> uh 00:23:54.870 --> 00:23:54.880 align:start position:0% two-part answer to this so uh 00:23:54.880 --> 00:23:56.750 align:start position:0% two-part answer to this so uh currently<00:23:55.880> we<00:23:56.039> know<00:23:56.159> we're<00:23:56.279> seeing<00:23:56.600> these 00:23:56.750 --> 00:23:56.760 align:start position:0% currently we know we're seeing these 00:23:56.760 --> 00:23:58.149 align:start position:0% currently we know we're seeing these intent<00:23:57.120> addresses<00:23:57.520> these<00:23:57.640> intents<00:23:58.000> going 00:23:58.149 --> 00:23:58.159 align:start position:0% intent addresses these intents going 00:23:58.159 --> 00:24:00.190 align:start position:0% intent addresses these intents going through<00:23:58.480> for<00:23:58.760> for<00:23:59.400> you<00:23:59.520> know<00:23:59.640> on<00:23:59.760> the<00:23:59.880> order<00:24:00.080> of 00:24:00.190 --> 00:24:00.200 align:start position:0% through for for you know on the order of 00:24:00.200 --> 00:24:02.909 align:start position:0% through for for you know on the order of a<00:24:00.320> cent<00:24:00.559> in<00:24:00.760> gas<00:24:01.039> costs<00:24:02.000> if<00:24:02.159> blobs<00:24:02.559> go<00:24:02.720> more 00:24:02.909 --> 00:24:02.919 align:start position:0% a cent in gas costs if blobs go more 00:24:02.919 --> 00:24:04.830 align:start position:0% a cent in gas costs if blobs go more into<00:24:03.240> price<00:24:03.720> Discovery<00:24:04.080> and<00:24:04.200> blobs<00:24:04.600> become 00:24:04.830 --> 00:24:04.840 align:start position:0% into price Discovery and blobs become 00:24:04.840 --> 00:24:07.310 align:start position:0% into price Discovery and blobs become more<00:24:05.159> expensive<00:24:06.159> the<00:24:06.679> interesting<00:24:07.120> thing 00:24:07.310 --> 00:24:07.320 align:start position:0% more expensive the interesting thing 00:24:07.320 --> 00:24:09.510 align:start position:0% more expensive the interesting thing here<00:24:07.480> is<00:24:08.440> uh<00:24:08.520> you<00:24:08.640> know<00:24:08.880> all<00:24:09.000> of<00:24:09.120> the<00:24:09.279> other 00:24:09.510 --> 00:24:09.520 align:start position:0% here is uh you know all of the other 00:24:09.520 --> 00:24:11.110 align:start position:0% here is uh you know all of the other things<00:24:09.799> you<00:24:09.919> know<00:24:10.120> compute<00:24:10.720> contract 00:24:11.110 --> 00:24:11.120 align:start position:0% things you know compute contract 00:24:11.120 --> 00:24:12.669 align:start position:0% things you know compute contract deployment<00:24:11.559> all<00:24:11.640> of<00:24:11.760> these<00:24:11.919> things<00:24:12.400> actually 00:24:12.669 --> 00:24:12.679 align:start position:0% deployment all of these things actually 00:24:12.679 --> 00:24:14.870 align:start position:0% deployment all of these things actually stay<00:24:13.000> cheap<00:24:13.240> on<00:24:13.360> L2<00:24:14.080> the 00:24:14.870 --> 00:24:14.880 align:start position:0% stay cheap on L2 the 00:24:14.880 --> 00:24:17.430 align:start position:0% stay cheap on L2 the one<00:24:15.880> scarce<00:24:16.320> resource<00:24:16.720> at<00:24:16.880> that<00:24:17.000> point<00:24:17.240> is 00:24:17.430 --> 00:24:17.440 align:start position:0% one scarce resource at that point is 00:24:17.440 --> 00:24:19.470 align:start position:0% one scarce resource at that point is call<00:24:17.760> data<00:24:18.480> and<00:24:18.600> there's<00:24:18.799> some<00:24:19.000> really<00:24:19.240> nice 00:24:19.470 --> 00:24:19.480 align:start position:0% call data and there's some really nice 00:24:19.480 --> 00:24:21.110 align:start position:0% call data and there's some really nice things<00:24:19.720> we<00:24:19.799> can<00:24:19.960> do<00:24:20.159> to<00:24:20.360> optimize<00:24:20.799> how<00:24:20.960> much 00:24:21.110 --> 00:24:21.120 align:start position:0% things we can do to optimize how much 00:24:21.120 --> 00:24:23.230 align:start position:0% things we can do to optimize how much call<00:24:21.320> data<00:24:21.520> we<00:24:21.679> use<00:24:22.440> so<00:24:22.600> we<00:24:22.720> we<00:24:22.840> anticipate 00:24:23.230 --> 00:24:23.240 align:start position:0% call data we use so we we anticipate 00:24:23.240 --> 00:24:25.230 align:start position:0% call data we use so we we anticipate this<00:24:23.320> is<00:24:23.400> going<00:24:23.520> to<00:24:23.600> Stage<00:24:24.039> okay<00:24:24.559> that's<00:24:24.720> it<00:24:24.960> th 00:24:25.230 --> 00:24:25.240 align:start position:0% this is going to Stage okay that's it th 00:24:25.240 --> 00:24:26.710 align:start position:0% this is going to Stage okay that's it th up<00:24:25.480> thank<00:24:25.600> you<00:24:25.760> very<00:24:25.960> much<00:24:26.440> thank<00:24:26.600> you 00:24:26.710 --> 00:24:26.720 align:start position:0% up thank you very much thank you 00:24:26.720 --> 00:24:29.880 align:start position:0% up thank you very much thank you everyone<00:24:27.559> thanks